Project-to-O&M handover
A handover step that turns the project’s as-built assets, manuals and snags into the O&M contract’s starting records.
Many Saudi contractors win the building and then the contract to run it. When the two divisions sit on separate systems, the handover is a spreadsheet, the warranty period is a memory, and nobody can say which side made the money. We build one Odoo that carries a project from first BOQ to its last maintenance visit.
At handover, a project produces exactly what the O&M team needs to start: the as-built asset list, equipment serial numbers, supplier warranties, O&M manuals and the snag list. On two systems, that information is re-typed — or lost — and the maintenance team starts the contract blind.
Then comes the defects liability period. A fault in the first year may be the contractor’s cost, a supplier’s warranty claim, or a chargeable O&M call — and the answer depends on records that live in the project, not the maintenance system.
In one Odoo, the project’s assets become the O&M contract’s asset register at the click of a handover, warranty dates travel with each asset, and each division keeps its own profit and loss while sharing people, equipment and stores.
What changes when construction and O&M share one database.
A handover step that turns the project’s as-built assets, manuals and snags into the O&M contract’s starting records.
Warranty end dates per asset and a defects log that decides — by date and cause — who pays for each fault.
Construction and O&M as separate business units with their own P&L, sharing customers, suppliers and stores.
Engineers, technicians, vehicles and tools allocated to projects or contracts, with costs charged to whoever used them.
Asset data from completed projects feeds the scope and price of the O&M proposal for the same building.
Backlog, margin and cash by division and by client — in Arabic and English — from one database.
How projects are billed, how O&M contracts are run, and where the two touch today.
One Odoo with two business units, shared contacts, stores, HR and accounting.
Contracting billing on one side, O&M contracts, PPM and SLAs on the other.
Asset, warranty and defects flow from a completed project into its O&M contract — tested on one real building.
One division first, the other second, so neither stops working while the system changes.
Because the handover data, warranties and defects that decide O&M costs are created during the project. One system keeps them attached to each asset, and lets each division keep its own P&L.
At practical completion, the project’s as-built assets, serial numbers, warranty dates and open snags are transferred into the O&M contract’s asset register, ready for the first PPM plan.
Yes. Each fault in the period is logged against the asset and classified as a contractor defect, a supplier warranty claim or a chargeable O&M call.
Yes. Construction and O&M run as separate business units in one ledger, so you see each division’s margin monthly and the group total without consolidation spreadsheets.
Yes. People, vehicles and tools are allocated where they work, and their cost is charged to the project or contract that used them.
A few lines on how projects are billed, how O&M contracts are run and where the handover happens. We’ll show one Odoo for both, with a phased, fixed scope.
We reply within one business day.