Request to install.
Moves, adds, changes and disconnects run as one internal workflow that ends at the carrier boundary. The handoff reference and the acknowledgement are kept as evidence.
Request a pilot
- What it does
- Runs a request from draft through group IT review, budget check, approval and procurement to the carrier handoff, then tracks the install on its own separate state machine until it is verified.
- What it reads
- The service being changed, its contract, its notice period and early-termination basis, and the budget line the change lands against, in transaction, functional and presentation currency with rate ids.
- What stays yours
- The carrier relationship. Ordering, changing and ceasing stay with your team, because regional incumbents expose very few ordering APIs, and disconnects are gated by term commitments and early-termination fees that carriers hold privately. What crosses the boundary is an email or a portal submission, and both are recorded.
- Where it shows up
- Budget variance, the cease-verification clock after a disconnect, and the evidence trail behind a dispute months later.
Who uses it
- The reader
- Regional IT, who raise and track changes, group IT, who review them, and finance, who hold the budget line.
- The question
- What has been asked for, who approved it, what it will cost in three currencies, and did the carrier actually do it?
- What they get
- One workflow from request to verified install, a budget check that prices the change with rate ids, a recorded handoff to the carrier, and a clock on every disconnect until the charge leaves the invoice.
- Where it starts
- A request against a service already in the inventory, with a reason and a target date.
How it is built
Two state machines
Commercial progress and install progress are tracked separately, so a request waiting on site readiness reads differently from a request waiting on approval. Any open state can be cancelled with a mandatory reason, which is what keeps an abandoned install from stranding a request forever.
Separation of duties
Approval is enforced, not conventional. Group IT review needs the approval permission; the budget check needs the billing permission and writes its own record comparing the projected recurring-charge delta against the budget line.
A disconnect carries its exposure
A disconnect cannot pass the budget check without an early-termination exposure figure read from the contract. That is the number that decides whether ceasing a circuit actually saves anything.
The cease-verification clock
A completed disconnect arms a clock. If the recurring charge is still on the invoice two months later, that raises its own finding, with the carrier handoff reference attached as evidence.
What you get
Approvals that are enforced
Group IT review needs the approval permission and the budget check needs the billing permission. A request moves through states rather than around them, and each transition records who moved it.
A disconnect that proves itself
A completed disconnect arms a clock, and a charge still on the invoice two months later raises a finding with the handoff reference attached. The saving is claimed when the invoice shows it.
Evidence for the dispute
The channel, the external reference, the time sent and the carrier's acknowledgement are kept on the request. Months later, when the charge is questioned, the case opens with the trail already in it.
How it works
- RequestAn operating company raises a move, add, change or disconnect against services already in the inventory, with the reason and the target date.
- Review and budgetGroup IT reviews; the budget check reprices the change against the budget line in three currency layers, each naming its rate id. A budget check repriced with today's rate is not a budget check.
- Hand offProcurement sends the order by email or through the carrier portal. The channel, the external reference, the time sent and the acknowledgement artifact are all recorded.
- Track and verifyInstall milestones run to verified, and a disconnect stays open until the charge actually leaves the invoice. Billing complaints and SLA credit claims route to disputes, which is where they belong.
One change, end to end
An upgrade from 50 to 100 Mbps at a regional office, followed from the request to the verified install.
- Request
- Regional IT raises a change against the existing service, with the reason, the target date and the contract's notice terms read from the inventory.
- Review
- Group IT reviews the request and approves it. The transition is recorded with the reviewer, the time and the state it moved from.
- Budget check
- The recurring-charge delta is priced as billed, in the entity's functional currency and in the group's presentation currency, each naming its rate id, and compared against the budget line. The check writes its own record.
- Handoff
- Procurement submits the order through the carrier portal. The channel, the reference the portal returned, the time and the acknowledgement PDF are attached to the request.
- Install
- The install runs on its own state machine: scheduled, in progress, verified. Once monitoring is connected, verification is where the bandwidth capability reads 100 Mbps delivered on the bound interface.
- Billing
- The next invoice carries the new charge. The line joins the service, the budget variance closes, and the request is complete.
Questions about MACD
Do you place orders with carriers for us?
Ordering stays with your team, and the workflow ends at the carrier boundary by design. What crosses it is an email or a portal submission, and both are recorded with their reference and acknowledgement.
Can a request be cancelled?
Any open state can be cancelled with a mandatory reason, which is what keeps an abandoned install from stranding a request forever. The cancellation is a recorded transition like any other.
How does a disconnect know what it saves?
It reads the early-termination exposure from the contract before the budget check, so a cease that costs more than it saves is visible before it is approved. The saving itself is confirmed by the invoice, two months on.
Where do billing complaints go?
To disputes, which is a separate track. A change request moves a service and a dispute questions a charge, and keeping the two apart is what stops one delaying the other.
Related capabilities
