COMMON QUESTIONS
Asked plainly.
Does CIPAA actually apply to oil and gas work?
Section 4 of Act 746 defines construction work to include gas, oil and petrochemical work as well as pipeline work, so contracts for that work fall within the Act on the face of the definition. The courts have applied it broadly: in MIR Valve Sdn Bhd v TH Heavy Engineering Bhd [2018] 7 MLJ 796 the High Court held that conversion of a ship into a floating production, storage and offloading vessel was construction work under CIPAA, a position affirmed in E.A Technique (M) Bhd v Malaysia Marine and Heavy Engineering. Whether it applies to your specific contract still depends on that contract and where the work is carried out, which is a question for your own adviser and not something software should answer for you.
We work under PETRONAS or bespoke contract forms, not JKR or PAM. Does the platform still fit?
Yes, because the claim engine is built on the contract you signed rather than on a named form. It works from priced lines, quantities, the rate in force when a line was claimed, retention on your terms, and variations that revise the line they relate to. JKR and PAM are output formats we already carry; your own form is configured during the build. The ledger underneath is the same either way.
Are you PETRONAS licensed, and do you have oil and gas clients?
No to both, and you should discount anyone in this market who answers otherwise without naming the client. Moorstack holds no PETRONAS licence and no PETRONAS Technical Standards conformance, and has no oil and gas reference case. What it has is a claims, variation and payment engine built for Malaysian statutory workflow, and CIPAA covers your work as clearly as it covers a building contractor's. If licensing or technical-standards conformance is what you need from a vendor, we are not it.
What about offshore work?
That is where we stop. Offshore and upstream EPCIC work sits behind vendor prequalification, HSE regimes and procurement cycles that a two-person firm has no business claiming to satisfy, and the operators in that space run enterprise systems for good reasons. There is also a live question about how far the Act reaches for work carried out outside Malaysian territory, which is a matter for your legal adviser. Onshore plant, terminals, tank farms and turnaround work executed by CIDB-registered contractors is the work we are built for.
Why is a turnaround different from ordinary contract work?
Because the scope grows while the clock runs and nobody stops to paper it. A three-week shutdown discovers corrosion, seized valves and failed tests that were never in the order, the crew does the work because the plant has to restart, and the argument about what it was worth happens months later against whatever anyone wrote down at the time. That is a variation problem wearing a schedule costume. An approved variation folds into the line it revises, an unapproved one cannot be claimed, and both stay on the record with the date they were raised.
Does this replace our maintenance system?
No. If you run SAP PM, Maximo or another CMMS, keep it. That governs assets and work orders. Moorstack governs what you are contractually entitled to be paid for the work those orders produced, and whether you can prove it. The two answer different questions and are commonly run side by side.
Statutory scope: Construction Industry Payment and Adjudication Act 2012 (Act 746), section 4. Case references: MIR Valve Sdn Bhd v TH Heavy Engineering Bhd [2018] 7 MLJ 796, and E.A Technique (M) Bhd v Malaysia Marine and Heavy Engineering Sdn Bhd. General information about the statute, not legal advice on your contract. Whether the Act reaches a particular contract depends on that contract and on where the work is carried out.