Skip to content

Module of the Service Engine · Build and field operations

Reperio Project Manager

Programme and phase tracking, contractor workflow, progress claims and clean handover into service.

What it does

PM runs the build. Programmes break into phases and work packages, contractors work to issued packages, progress is claimed against verified quantities, and handover into service is a controlled transition rather than an email with attachments.

Phases and work packages are first-class Service Engine objects, so serviceability, activation readiness and reporting update as the build progresses.

Capabilities

Inside Reperio Project Manager

Programme and phase tracking

Premises, spans and milestones tracked per phase with forecast and actual dates.

Contractor workflow

Work package issue, acceptance, variation and completion across multiple contractors.

Milestone and progress claims

Claims assembled from verified quantities and quality acceptance, not from separate spreadsheets.

As-built capture and handover

As-builts captured at completion and promoted into the service inventory on acceptance.

Handover is where value leaks

Networks are frequently built well and handed over badly. PM ties acceptance, as-builts and quality evidence into one gate, so a phase becomes serviceable with records the operations team can actually use.

One programme across many contractors

Multi-contractor builds fragment reporting. PM keeps one programme view while each contractor works only within their own packages and claims.

Exposed through

TM Forum API domains this module surfaces in

Whatever the module does internally, external consumers reach it through the same conformant interfaces as the rest of the platform.

See the platform against your own operation

A demo walks the architecture, the modules you would actually use and the TM Forum interfaces your partners would integrate against. Bring your operating model and we will map it.