Fiber Service Area Setup Checklist

Plant Records

Plant records should be reviewed first, since they help define the physical network information that may need to be represented in Vision. This may include records from integrated plant management systems such as 3-GIS, IQGeo, OZMap, or Vetro, depending on what your company uses for plant design and fiber records.

Items to review:

Which plant record system is being used?
Are plant records available for this service area?
Are service area boundaries, drops, cabinets, patch panels, or other relevant assets available?
Are there known differences between the plant records and the actual field setup?

Locations (optional)

Addresses should be reviewed and can be mass imported if the dataset is available. This Vision can recognize addresses in the service area. This may include serviceable addresses, test addresses, lead subscriber locations, or locations used for validating drops and plant records.

A subscriber location should be available in the new service area. This can be a simple test address or an actual lead subscriber. Regardless of which is used, a drop should be imported in the area so the patch panel modeled in your plant records software can be created in Vision.

Items to review:

Are the service area addresses already in Vision?
Do locations need to be imported?
Is a test address or lead subscriber needed?
Are subscriber locations tied to the correct service area?
Are drops or plant records connected to the correct locations?
Are addresses formatted and standardized correctly?

Inventory and Hardware

Inventory and hardware records should be reviewed so Vision has the correct equipment information for the service area. This may include warehouses, cabinets, OLTs, cards, ONTs, splitters, and other hardware items.

The address information for the new fiber cabinet or CO should be tracked in Vision as a warehouse. Hardware details for the new OLT and any installed cards should also be added. These details may be entered manually or, in some cases, pulled from AOE if the device is online and the setup is being backfilled.

Items to review:

Does a warehouse need to be created for the cabinet, CO, or service area?
Does new hardware need to be added to Vision?
Are serial numbers, MAC addresses, model names, IP addresses, and device names available?
Are installed cards, ports, or related hardware details needed?
Is hardware tied to the correct warehouse or location?
Will devices in this area need to be monitored in Vision for network status, hardware health, light levels, alerts, outage workflows, or other network-related activity?

Provisioning

Provisioning setup should be reviewed for any systems or hardware platforms that will be integrated in the service area. This may include Adtran, Calix, Nokia, or other speed shaping systems.

Items to review:

What provisioning system or systems will be used?
Are the needed servers or integrations already configured?
Will this area use a different provisioning system than other areas?
Are any provisioning rules, profiles, or templates needed?
Will this area use the same provisioning process as existing areas, or does anything need to be created or changed?

Authentication and IP Management

Authentication and IP management should be reviewed if the company tracks or assigns IP information through Vision or related systems. This section may be optional if the client does not track IPs in Vision or does not need IP-related setup for the service area.

Items to review:

Will IP addresses be tracked for this area?
Are IP pools needed?
Are there authentication requirements tied to the network or service packages?
Are any IP management integrations or settings needed before launch?

Patch Panels and Cross-Connects

After the necessary drop and patch panel information exists in Vision, any known cross-connect relationships can be modeled. This may include relationships between patch panel ports and PON ports.

Items to review:

Has the patch panel been created in Vision?
Are patch panel port relationships known?
Are the PON port relationships known?
Do cross-connects need to be modeled before launch?
Has the physical setup been confirmed against the records in Vision?

Service Areas, Packages, Service Items, and Offers

Once the foundational network, location, hardware, and patch panel information has been reviewed, the next step is preparing the area for service availability and sales. Service areas, packages, service items, and offers determine which services are available to customers in the new area.

Items to review:

Do service area shapes need to be created or imported?
Which packages should be available in this area?
Do new packages need to be created?
Do existing packages need to be updated for this area?
Which service items should be included in each package?
Are offers needed for the shopping cart?
Are the correct offers tied to the correct service area shapes?

Online Sales and Marketing

Online sales and marketing setup should be reviewed before the service area is opened for customer interest or customer signups.

In some cases, the first step may be lead generation rather than direct package selection. For example, customers may submit interest through a form so your team can gather demand, track interested addresses, and follow up when service becomes available.

Items to review:

Will this area be open for live sales or lead generation only?
Should customers be able to select packages in the shopping cart?
Should customers only be able to submit interest at first?
Is there a form, landing page, or campaign needed for this area?
Should customer interest submissions notify the internal team by email?
Are there marketing materials, postcards, ads, or website updates needed before launch?

Workflow and Installation Process

The installation workflow should be reviewed before launching the service area. If an installation workflow already exists, confirm whether it can be reused as-is or if changes are needed for this specific area.

Items to review:

Is there already an installation workflow in Vision?
Are any workflow steps different for this area?
Are additional tasks needed for fiber drops, hardware assignment, provisioning, testing, or customer communication?
Are technician instructions, task forms, or required fields up to date?
Has the full installation process been tested from order creation through completion?

Calendar and Scheduling

Calendar and scheduling setup should be reviewed so that installs and field work can be assigned correctly once the service area is ready.

Items to review:

Are the correct timeslots and technician schedules added?
Are service areas tied to the correct scheduling resources?
Do appointment windows need to be created or updated?
Are there capacity limits for this area?
Can customers self-schedule through the shopping cart or customer portal?
Has scheduling been tested from the customer-facing and internal user side?

Final Testing and Launch Review

Before opening the service area for lead generation, sales, or scheduling, review the full setup with the appropriate teams.

Final launch questions:

Are plant records ready?
Are locations and test addresses validating correctly?
Are hardware and inventory records complete?
Are provisioning and monitoring systems ready?
Are patch panels and cross-connects modeled where needed?
Are service areas, packages, service items, and offers configured?
Are customer-facing sales or lead generation tools working?
Is the installation workflow ready?
Is scheduling ready?
Has the full customer path been tested from address lookup to order or lead submission?
Has the workflow been tested from order creation to installation completion?