For the operator, the network owner and the prime contractor
Equipment installed? PHIBCOM handles commissioning, testing, base configuration, verifying concordance with the specifications, and documenting it.
PHIBCOM handles commissioning, site by site, separately from the installation contract — without tying up your installation crews, and with a follow-up file delivered for every site.
No stake in equipment manufacturers, installers or operatorsThe observation
Installing, troubleshooting and commissioning: different services and different tooling from installing the equipment.
When both sit inside a single contract, commissioning becomes the last step of a rushed project. The equipment ends up working, but the file that should prove it is never produced — and it is missing on the day someone has to separate an installation deficiency from an operational degradation.
The proof does not exist
Without dated measurements and without a per-addition record of installation compliance, compliance on delivery gets argued from memory. Six months later the argument is lost before it starts, and the cost of going back to verify is incurred.
Two fields of competence, not one
Installation belongs to the physical field — supports, pathways, mechanical connections. Commissioning belongs to a more computing-oriented field — configuration, addressing, reading counters and alarms. The contractor should not have to carry both.
The measurement is captured, not interpreted
A recorded trace is not a trace that has been read. The gap that matters is in the interpretation — handling errors, events, cumulative losses, margins against the requirement.
The mandate
What is delivered, site by site
The work is the same everywhere: verify, commission, document. The batch sets the pace; the file sets the proof.
Preliminary verification
Concordance between the engineering order and the installation as built: anchoring, positioning, fibre ducts, grounding, labelling. Power polarity checks before energizing. Deviations recorded and correction requests written before the equipment is powered.
Start-up and initial configuration
Software version, management IP addressing and routing, console access, inter-equipment connections, absence of failure on delivery. Initial configuration to the network owner's standard. The equipment is handed back reachable on its owner's network.
Connection and link validation
Connector cleaning and inspection, transmitted and received power and — on the links that require it — reflectometry, iOLM, chromatic dispersion and PMD. Results compared against the requirement, not merely recorded.
Commissioning file per site
Measurements, photos, the configuration retained, deviations recorded with reference to the requirement, and the status of the site. One file per site, delivered to the network owner as needed.
The file is what makes the batch defensible. Produced by the party that installed, it stands against no one. Produced by a third party with no interest in the work, it becomes opposable — and it protects the contractor as much as the owner, by isolating what was not compliant on arrival.
Execution
Pace, mobilization and scope
The pace of a batch is not promised blind. The number of sites handled in a day depends on the nature of the work, the distance between sites and how hard they are to reach. PHIBCOM commits to a pace in the quote, once the batch is described — and holds it.
PHIBCOM is a registered trade name of 9572-3474 Québec inc. · NEQ 1182380502 · Listed in the Répertoire des fournisseurs du gouvernement du Québec and in SEAO · Québec (Québec), Canada
Describe the batch
Number of sites, type of equipment, target deadline and access constraints. A quote follows, with the committed execution pace.