Find the tool. Understand the workflow.

Physical Digital Twin

A place for every fiber.

Head End / PoP → rack → shelf/drawer → cassette → position. H14T1-B-02-12 identifies rack H14T1, drawer B, cassette 02, position 12. Manholes connect assets, ports, cables, tubes and fibers. Configurable asset types, colors and dependent network selection keep physical context explicit.

FiberCircuit

Follow optical continuity. Preserve every change.

FiberCircuit / FiberRoute is the current optical path; CablePath is physical cable traversal; RouteGeometry is geographic shape. Scoped local gates validate named circuits and completion-bound splice publication. A committed MH15 cross updates affected current connectivity while preserving previous topology, actor and work evidence.

Route Import

Review geography before committing it.

Bounded GeoJSON, KML and KMZ adapters and a reviewed import wizard passed scoped local gates. Upload → detect → geometry and ordered manholes → customer/site → source rack, drawer, cassette, position → cable/tube/fiber → destination → validate → commit. Original source and geographic versions remain intact. Other formats require their own evidence.

Unified Network Search

Find identities, assets and their context.

Locally validated search covers physical inventory, canonical position, cable/tube/fiber labels, customer/site, registered circuits, routes and addresses, with filters and paging. Nearby search has a separate spatial gate. Smart Work and Barcode/QR resolution across every domain must not be inferred from this scope.

Engineering Map Workspace

Geography and connectivity remain distinct.

Scoped local validation covers recorded PostGIS points, active routes, bounded viewport layers, nearby queries and authorized record navigation. This coordinate workspace is not a configured street basemap. Circuit, cable, asset, customer, job, fault and authorized technician layers are extended as their domains mature. External navigation does not replace the engineering database.

Work Orders / Manager

Work order ↔ network identity ↔ field team ↔ history.

Local checkpoints cover planning and completion-bound splice evidence. Jobs retain Smart Work Number, type, priority, status, customer/contact/site, network selection, multiple technicians and responsible supervisors, and an optional primary supervisor. Assignment, dispatch, on-site work and completion preserve context. Full operational release acceptance remains open.

Technician / Supervisor

Every intervention carries its evidence.

Assigned jobs, Start / Stop / Resume / Complete, Live / Not Live, notes, photos, splice pairs and staged evidence are implemented in scoped slices. Stop Work is a job-linked supervisor escalation, not an isolated timer. Approvals, controlled replanning and completion gates remain subject to permissions and further acceptance.

Notifications

Deliver the right event to the right role.

Company/job-aware recipient rules and an inbox/email outbox have focused local checks. Assignment, supervisor alerts, priority changes, completion, report-ready and approval events are part of the intended event model. Real SMTP delivery, native push and full realtime transport acceptance remain open.

Fault Locator

Turn measured distance into network context.

A deterministic read-only preview correlates the selected current circuit, explicit route and measured distance, with configurable launch/slack/overlength. Missing or ambiguous connectivity and insufficient geometry must withhold a coordinate. Saved source-linked analysis is in development; no survey-grade certainty is promised.

Testing & Measurements

Original evidence stays with the analysis.

OTDR, iOLM, OLTS, IL, ORL, OPM/PPM, FIP, CD and PMD are represented through a documented neutral measurement model. Original file, normalized record, raw metadata and analysis remain distinct. SOR and proprietary iOLM are attachment-only in the reviewed implementation: no vendor parsing or universal device compatibility is claimed.

Universal Import Hub

Detect. Preview. Validate. Commit.

The developing inbox handles bounded single/multiple sources and ZIP batches, preserving original files. Adapter classification, preview, relationship resolution and sealed reports keep results explicit. Scoped CSV/XLSX/XLSM data-only mapping does not imply support for all spreadsheets. Macros and active content never execute.

Lasschema

Keep instructions separate from fiber identity.

Source-linked worksheet and physical-row mappings support work planning and current schema export in development. Blue work highlighting is not Blue Fiber. Confirmed operations inform current splice/free state while originals and history remain preserved. Universal Excel layout or formatting compatibility is not promised.

Barcode / QR

Verify the asset, not just the label.

Persistent asset identities have a scoped local gate. Start / cassette / final scans and explicit bypass requests are being integrated. Authorized supervisor/manager approval or rejection requires a reason and audit evidence. Desktop workflow and broader acceptance remain open.

History & Evidence

Who changed what, where, when and why?

Typed history brings jobs, fibers, circuits, cables, assets, faults, tests, splices, photos, documents, actors and timestamps into context. Optical before/after evidence is validated; the unified history workspace and additional evidence domains continue through focused implementation checks.

Reports & PDF Templates

Generate documents from the records behind the work.

Choose a real data source with Generate from data. Report families cover assets, manholes, cables, routes, measurements, customers, employees, hours, costs, imports, reviews and QR. Job reports share their actual report engine and attachments. As-Built excludes proposed and planned work. Layout samples remain distinct from reports populated with company data.

Company Branding

Your identity on company output.

Versioned company profile and branding support legal/trading name, logo, address, phone, email, tax details, website and report/invoice footer. Company output retains XANDER identity. These locally implemented report and invoice features are not a generally available release.

Ask XANDER AI

Grounded assistance, controlled actions.

An optional read-only assistant framework uses selected, authorized evidence with explicit external-processing consent and review. Network/fault questions, import mapping, history, report drafts and billing analysis are assistance directions. A live provider is not verified. Sensitive actions remain governed by deterministic rules, permissions, confirmation and audit; AI cannot autonomously change critical network data.

Fusion Splicers & Devices

Adapters with explicit boundaries.

A versioned device registry and manual/neutral JSON splice evidence support expected-versus-actual pair review in a local implementation. Physical hardware, vendor SDKs, Bluetooth, USB/Serial and Wi-Fi/LAN drivers are not verified. Device registration or file upload is not a live instrument connection.

Company Access & Permissions

Keep each operation in its authorized company context.

R354.7 endpoints check company context and role or granular permissions. Engineering edits, financial operations, job assignment and supervisor approval have separate access rules. Company subscriptions also control sign-in availability. These are source-observed controls, not a security certification or a claim that production isolation has passed a new audit.

One Platform, Multiple Clients

Shared data and business rules across office and field.

Windows, Web, iPhone, Android and tablet share the platform direction. Locally validated Web workflows are distinct from shells, signed packages and hardware-tested native clients. Native release, full parity and offline acceptance are not claimed. Central settings keep company, users, network, imports, reports, billing and AI consistent.

Fast by Design

Load the context you need.

Optimized assets, indexed queries, pagination, caching, progressive loading and suitable background processing guide development. Engineering maps use bounded viewport queries. Representative final load, recovery and performance acceptance remain open; engineering targets are not public service-level guarantees.

Offline Strategy

Make synchronization state explicit.

Planned selective offline support must distinguish server-confirmed data, local pending changes and failed/conflicted synchronization. Native hardware and recovery tests are required before operational offline availability can be claimed.

Assets

Know every asset. Keep its context.

A unified asset workspace connects recorded Head Ends, manholes, closures and network assets with their network context. Search the inventory, inspect the asset and follow its registered relationships. QR Library provides asset labels and PDF/SVG export; the 2D/3D concept remains a design proposal.

1. Find the asset by code or family.
2. Inspect its identity, recorded relationships and available location.
3. Open its network context or prepare its QR label.

Fiber Engineering Studio

Engineer from the network you actually have.

Explore inventory in a 2D connectivity workbench with asset search, route filters, zoom and an inspector. See disconnected assets and missing coordinates before planning. Open the design canvas for route/trench, duct, cable and point objects, measurement, layers, undo/redo, draft saving and a design quantity summary. The connectivity view is schematic; proposed design objects do not themselves change live assets.

1. Select a route or search an asset.
2. Inspect its connections and engineering attention items.
3. Choose endpoints for analysis or open the design canvas.

Auto Route

Turn endpoints into a reviewed route proposal.

Choose a start and destination to analyze registered manholes, cables and fibers. Review physical traversal, optical connectivity, available capacity and missing information, then save a proposal and preview a work package. Co-location is not proof of a splice. Missing cables, unknown splice positions and surveyed lengths are never invented.

1. Choose two different recorded endpoints.
2. Analyze the route and resolve incomplete network information.
3. Save the proposal and preview the complete work package.

Work Packages & Approval

A controlled handover from engineering to the field.

Prepare location-by-location diagrams with instructions and proposed connections. Review PDF/SVG sheets and download the complete ZIP, or assign the package to a job with a technician and supervisor. Technician completion records evidence; assigned-supervisor approval applies the defined changes and preserves before/after asset versions. Conflicts stop the transaction.

1. Review the scope, drawings and proposed disconnections.
2. Assign the package and record sheet completion in the job.
3. Submit for supervisor review before live asset changes.

Work Cost & Rate Card

See what each job costs—and what it earns.

Closed Start/Resume → Stop/Complete intervals supply actual labor hours. Recorded completion supplies splice and cable-entry quantities. Company rate cards hold separate unit cost, selling price, tax, currency and billable status, by role, individual or custom work type. Review actual cost, billable net and estimated margin. Missing rates stay visible; running timers remain provisional and invoiced entries stay locked.

1. Configure role, person, splice, cable-entry and custom rates.
2. Review recorded hours, completed quantities and manual expenses.
3. Resolve missing rates and review cost, billable net and margin.

Job Invoices

From recorded work to a traceable customer invoice.

Select unbilled, billable cost entries from a job to create a customer invoice draft. Review quantities, prices, line tax, customer details and due date. Issue a numbered invoice with a retained issuer identity, download its PDF and record partial or full payments. Issued invoices are immutable. Recording a payment is a controlled ledger action, not an integrated bank settlement.

1. Select the job’s unbilled, billable entries.
2. Review the draft and issue the numbered invoice.
3. Export PDF and record payments against the remaining balance.

Platform Billing & Subscriptions

Manage the commercial relationship with each company.

Platform billing is separate from invoices for field work. Manage company plans, subscription dates, seat and device limits and access status. Draft and issue subscription invoices, track balances and overdue records, and record payments or credit notes. Renewal preference does not itself charge a payment method.

1. Review the company plan, access status and subscription period.
2. Prepare and issue the platform invoice.
3. Track its balance, payments and credit notes.

Planning & On Call

Put the right people into the plan.

Daily, weekly, monthly and timeline views bring shifts, primary/backup duty, absence and availability into one planning workspace. Search employees and filter by role or department. Company-specific Excel templates support planning and on-call imports, with row validation, time-conflict checks and repeat-import protection.

1. Find the employee and choose the planning period.
2. Create or import shifts and review availability conflicts.
3. Update assignments and follow the recorded planning changes.

Mail & Communication

Keep the conversation attached to the work.

Internal mail includes inbox, sent, drafts, starred and archive, with recipients, replies, attachments and job context. Automated messages cover account events, assignments, approved completion, invoices and recorded payments. Communication Settings expose queue state and delivery attempts. External delivery requires a configured provider; local Capture mode does not send email.

1. Compose an internal message with the relevant job or report.
2. Review recipients and attachments before sending.
3. Use Communication Settings to inspect automated delivery status.

Closure Studio

Prepare the splice work. Preserve the network record.

Work diagrams retain the assigned Closure Studio snapshot and distinguish planned work from the recorded network. Technicians complete the assigned scope with evidence. Supervisor approval applies the reviewed changes and preserves the previous asset version; planned markings are removed only from the completed scope.

1. Prepare and review the closure work diagram.
2. Assign the saved snapshot to a job and complete its scope.
3. Submit for supervisor approval and retain the resulting evidence.