For equipment integration, fit-out, implementation, and line rebuilds, the pain is not “having a project.” It is executing the contract: did the prepay land, did a scope change get a document, can you invoice if acceptance slipped, when does warranty start. An Excel Gantt can draw a plan. It cannot hold change and money. The system needs each milestone to have evidence, amount, and an owner. Slip is visible. Change leaves a trail. The plan bar may reshuffle weekly. The actual bar and invoice dots cannot be dragged for a pretty report or the Gantt is a poster.
A milestone must match money, not mood
Each node writes: deliverable, who signs, contract amount, whether you may invoice. Sales and finance must see the same contract. See Sales and finance looking at the same customers and contracts. Order-to-cash on a project is milestone-to-cash. See From order to cash. Audit wants change orders and acceptance, not the project group chat. See What the system does when you reconcile or audit.
Change is daily on projects. More scope is a new milestone or a new amount — not “do it while you are there” in the group. Otherwise the Gantt stays green and cost is already red. Factories split work orders; projects split milestones. Do not force one production ticket. See how an order splits into work orders. With a system vs. without: when the PM is out, can someone else chase acceptance. See how the work path differs.
Phase one is calendar and evidence, not a fancy resource chart
First: split the contract, plan vs. actual bars, slip warning, acceptance attachments, invoice by node. Resource load and earned value can wait. Packaged project modules often demand a full PMO the floor will not use. See a packaged ERP nobody uses. DaXi draws Gantt fields from your payment clauses. To run project delivery, go to Business systems service page with a redacted contract outline. The build sequence is in from brief to launch. The plan bar may edit. The actual bar only reports done and attaches evidence, so a PM cannot paint slip as on time.
Warranty and invoice nodes hang on milestones
Warranty start hangs on final accept — not “we’ll talk after accept.” Parallel projects can use a simple occupancy calendar. Do not start with complex resource leveling. A customer signer change is recorded on the node or final accept cannot find a person. Success is finance asking why this order cannot invoice and the system pointing at the unsigned node.
Prepay, arrival, and accept shares sit in node amounts and must sum to the contract. Recalc after change so the balance is not a mystery remainder. A site variation attaches to the bar that triggered it — not a shared-drive pile by project name. Pause is a state. The Gantt freezes. Bars do not keep walking after people leave site. Write the factory boundary: equipment arrival/install can be a milestone; shop-made parts still report on work orders. Two progresses roll up at the contract. Do not force the shop to report hours in project software. Black dots are visible to finance. The shop sees work orders. Two views, one contract, so nobody draws their own progress.