One delivery.
A connected process.
People own the actions. Shared records carry the context from project setup to field evidence, review and service acceptance.
Know who acts, and what changes.
Establish the project
Administrator + project teamChoose the customer, project, workflow and templates. Import sites and create DUs. Assign eligible people, teams and reviewers.
ResultThe delivery structure is ready to plan. Setup acknowledgement is a proposed capability, not an enforced creation approval.
Plan and dispatch
Project coordinatorSet milestone dates in the rollout matrix. Dispatch to a person or group using the owner modal.
ResultA WO captures its template and review route. Later configuration edits affect new dispatches; existing evidence keeps its context.
Execute and submit
Assigned resource or teamConfirm the site, clock in, fill KCPs and attach photo evidence. Resolve validation issues, save and submit.
ResultA numbered submission is available for review. Inputs lock during review; authorized clock-out can still finish the work session.
Review the work
Configured WO reviewersInspect the evidence and return specific sections when correction is needed. Approved KCPs stay locked.
ResultFinal closure can write back to the milestone. Without a WO template, the milestone is managed through authorized manual updates.
Review service revenue
Service team + revenue reviewersImport PO lines, map service codes and publish to DUs. Milestone closure or a manual request can issue an eFlow. Check evidence and decide eligible items.
ResultApproved items record revenue in MSDP. A reversal retains the original decision and creates a linked negative adjustment after approval.
The exceptions matter too.
Is the revenue reviewer the work-order approver?
Revenue reviewers are configured separately on the milestone. A milestone can have revenue review without a WO or WO approval. An empty named configuration uses eligible project revenue reviewers.
What if only some eFlow items are accepted?
Decide the eligible items individually. Approved and rejected captured rows are settled; returned items can receive corrected evidence and be resubmitted. Inspect pending values as well as the case label.
Can we correct an incorrect publication or request?
Eligible services can be unpublished after blocking cases are resolved. Cancel an unapproved request; use a linked reversal for approved revenue. Preserve the earlier records.
What should a pilot prove?
Use agreed sample source data and authorized participants. Verify a normal delivery, a return and correction, a partial revenue decision and a reversal. Agree the evidence and reporting definitions before wider use.
Start with one
complete business scenario.
Pricing is quote-based. Scope the users, source data, workflow, acceptance criteria and support arrangement together.