PS 606 · PRODUCTION SUPPORT
How do you support Project System in production?
Trace project structure, execution evidence, and financial outcome separately. Start with the last project object whose state you trust, then follow the next expected evidence until the first broken boundary appears.
PS EVIDENCE CHAIN
Follow the reusable project-control spine
PS is a reusable capability, not one fixed business process. The scenario changes the outcome; the support method stays the same.
- 01Project & WBSMandate
- 02Plan / budget / statusAuthority
- 03ExecutionWork
- 04ActualsCost
- 05Period endClose
- 06Settlement / closeOutcome
SUPPORT OPERATING LOOP
Diagnose the owning layer before correcting it
State what is blocked
Record the project object, scenario, business impact, scope, and whether execution, billing, settlement, or close is affected.
Find the last trusted object
Follow project definition → WBS → network or activity → plan and status → execution → actuals → period end → receiver.
Choose the support layer
Separate structure, planning, budget or status, procurement, execution, cost or revenue, period end, and close or integration.
Locate the failed boundary
Test the transition that should have produced the next expected project, logistics, or financial evidence.
Correct from the owner outward
Use the supported correction, reversal, reassignment, or rerun; then prove the complete scenario agrees again.
Turn repeats into controls
Monitor structural integrity, schedule health, budget blocks, open commitments, financial exceptions, and incomplete closure.
FIRST PS DECISION
Which evidence layer stopped agreeing?
Do not treat every incident as a WBS issue. A project can be structurally correct while release, procurement, confirmation, billing, settlement, or closure is broken.
Project definition, WBS, network, activity, billing element, responsibility, and account-assignment ownership.
Procurement, materials, production, services, confirmations, progress, delivery, and quantity evidence.
Cost, revenue, WIP, Result Analysis, revenue recognition, settlement, receiver, and close evidence.
PS DIAGNOSTIC PLAYBOOKS
Follow the path that matches the symptom
01 · WBS exists but cannot be released
Trace: project profile → WBS status → authority → availability control → dependent objects. Resolve the actual status, budget, approval, or authorization condition; do not bypass it.
02 · Cost or revenue is on the wrong WBS
Trace: source document → account assignment → actual posting → WBS role → settlement. Correct the source and use supported reversal, reassignment, or reposting.
03 · Network dates or activity confirmation are wrong
Trace: activity → relationships → duration and work center → status → confirmation → milestone. Separate planning logic from execution evidence.
04 · Project demand does not produce procurement or material evidence
Trace: WBS or activity → component or account assignment → PR, PO, reservation, project stock, service, or goods movement. Follow the native logistics document chain.
05 · Billing, revenue recognition, or settlement is wrong
Trace: billing element or sales document → execution evidence → actual revenue → period-end rule → settlement profile and receiver. Correct the rule before rerunning period end.
06 · Project is complete but cannot close
Trace: open activities → commitments → balances → billing → settlement → downstream asset, maintenance, production, or delivery ownership. Closure must be operational and financial.
PS SUPPORT MOMENT
Project status looks complete, but the financial story is not
Do not close by changing status alone. Prove that commitments, confirmations, cost, revenue, period-end processing, settlement, and the scenario-specific receiver are complete and reconciled.
- Begin with the last project object whose state is trustworthy.
- Correct from the owning object outward; preserve project history.
- Prove project structure, execution evidence, and financial outcome tell the same story.
Use 101 for the lifecycle, 202 for structures and controls, 303 for scenario patterns, and 404 for design proof.