Oil & gas
Completions software for scopes where the dossier is as scrutinised as the plant.
Brownfield tie-ins, FPSO topsides, LNG trains and onshore processing all end at the same gate: an operator's completions team deciding whether the evidence is good enough to take care and custody. Deskely holds that evidence tag by tag, subsystem by subsystem, from the first hydrotest to the final handover certificate.
Choose your project type
The problem
Volume is the problem, and volume breaks spreadsheets.
A single processing train can carry twenty thousand tags and several hundred thousand individual checks. Those records are produced by an EPC, three or four subcontractors and a dozen vendor packages, each working in its own file, with its own tag conventions and its own idea of what "complete" means.
Nobody set out to build four registers. It happens because each party needs to report on its own scope, and the master spreadsheet cannot be edited by everyone at once. By the time the completions lead needs a single number for subsystem 21-02, that number has to be reconciled by hand — and it is stale before the meeting ends.
The cost of that reconciliation is not the hours spent on it. It is the decisions made on figures that were wrong: a walkdown called too early, a certificate issued over an open Category A punch, a preservation gap discovered during a warranty dispute two years later.
Where oil and gas scopes differ
Six pressures that a generic project tool never has to handle.
Tag volume overwhelms the register
Extracting tags from P&IDs, line lists, cable schedules and equipment lists and mapping them to subsystems consumes months of engineering time before a single ITR is signed.
Revisions land after the register is built
A P&ID goes to revision C and nobody can say which subsystems, ITRs and test packs the change touched until someone reads the drawings again.
Preservation runs for years
Rotating equipment and instruments installed long before start-up need recurring routines, and missed cycles turn into warranty disputes at handover.
Certification is layered
MC, RFSU and handover each depend on the layer beneath, and proving that dependency by hand across hundreds of subsystems is where schedules are lost.
Punch decides the start-up date
Category A items block acceptance and Category B items travel with the plant, but the split is argued in meetings rather than derived from the record.
Operators audit the trail
Care and custody transfer is conditional on evidence being complete, correct, signed by an authorised person and retrievable in minutes — not merely claimed.
Scope types
The same completions model, from tie-in to LNG train.
What changes between oil and gas scopes is the shape of the subsystem breakdown and who signs. The record types, the certification ladder and the audit trail behind them do not.
FPSO and floating production
Topsides modules built in one yard, hull in another, integration and commissioning in a third. Records follow the module rather than the location, so a package tested at the fabricator keeps its history through sail-away and offshore hook-up.
- Module-level test packs
- Yard-to-offshore continuity
- Vendor package scopes
Fixed platforms and jackets
Weather windows and bed space decide what can be closed out offshore. Subsystem readiness has to be provable onshore so the offshore campaign is spent on the work that genuinely cannot be finished at the quayside.
- Offshore punch carry-over
- POB-limited walkdowns
- Category A / B discipline
Subsea tie-backs
Umbilicals, jumpers and control systems are tested in stages by different parties. The register keeps the flowline, control and topsides interface records under one subsystem so the interface is not the place where evidence disappears.
- Interface test records
- Umbilical continuity
- SIT-to-field traceability
LNG trains and gas processing
Cryogenic and rotating scopes with long preservation windows and dense loop testing. Every loop, valve and machine carries its own record set, and RFSU is gated per train rather than declared for the plant.
- Loop and machine ITRs
- Multi-year preservation
- Per-train RFSU
Refineries and petrochemical
Live plant next to new build. Commissioning documentation has to satisfy both the project and the operating organisation, including the pre-start-up safety review and the records the site retains long after the contractor leaves.
- PSSR evidence pack
- Operator retention format
- Brownfield interfaces
Brownfield tie-ins and turnarounds
Short duration, high scrutiny, no room for reconciliation. Scopes are planned as subsystems in advance, executed on tablets during the window, and closed out with a certificate package before the plant is handed back.
- Window-length execution
- Offline field capture
- Same-day close-out
Pipelines and compressor stations
A linear spread where the crews move on long before acceptance. Hydrotest, gauging and drying evidence stays with the test section it belongs to, and stations are certified as the plants they are.
- Test section acceptance
- Weld and NDT linkage
- Station subsystems
Terminals, tank farms and jetties
Much of the gating evidence is issued by someone else — calibration companies, provers, fire specialists. Third-party documents sit under the tag they qualify, and metering is gated on its own ladder.
- Third-party evidence
- Custody transfer gating
- Tank-by-tank handover
Hydrogen, ammonia and carbon capture
First-of-a-kind plants built by teams from four industries, financed on milestones and permitted on leakage conditions. One register serves the operator, the lender's adviser and the verifier.
- Tightness and purity
- Measurement traceability
- Configurable ITR sets
Decommissioning and late life
Commissioning in reverse. Systems earn isolation, hydrocarbon free and clear for removal from signed records, and the regulator's close-out report is an export rather than a rewrite.
- Made-safe certification
- Hazard and NORM findings
- Waste traceability
Setting up the register
The first three months of a project are transcription.
Before a single ITR can be issued, somebody has to turn P&IDs, line lists, cable schedules and equipment lists into a tag register mapped to systems and subsystems. On a topsides scope that is months of senior engineering time spent typing what the drawings already say.
Deskely's parser reads the document set and drafts that register for you, normalising tag formats and holding the drawing reference behind each tag. Where documents disagree — a line list that says one thing and a P&ID revision that says another — the conflict is surfaced side by side, with sources, for an engineer to settle in one click.
Nothing enters the project unreviewed. The output is a draft your completions lead corrects, not a black box you inherit. The register that comes out is the one every ITR, punch item and certificate afterwards hangs from.
Certification
MC, RFSU and handover are layers — each one earns the next.
A mechanical completion certificate is only as good as the records under it. RFSU is only as good as the MC beneath it. On paper that dependency is proven by someone cross-checking several lists, which is exactly where schedules quietly disappear.
Deskely enforces the ladder. A certificate cannot be issued while an A-ITR under it is unsigned, a Category A punch is open, or a preservation routine on one of its tags is overdue. The gate is the data, not a reviewer's memory.
The result is that an issued certificate means something. When the operator asks what permitted it, the answer is a list of signed records, not a signature on a cover sheet.
Running the scope
Subsystem readiness that comes from the records, not from a status meeting.
Every signature in the field moves the number above it. MC, commissioning and handover progress for each subsystem are derived from the records beneath them, so the completions lead and the operator's representative are reading the same figure at the same moment.
Punch sits in the same view, split by category, because that split is what decides the date. A Category A item blocks the certificate above it outright. A Category B item is carried, visible, and still owned by someone after handover.
When a subsystem is genuinely ready, the walkdown is scheduled against evidence rather than optimism — and the certificate that follows can be issued the same day.
Preservation
Equipment installed in year one still has to be warranty-clean in year three.
Rotating equipment, motors and instruments go in long before start-up and then sit. Each needs its own routine on its own cadence — monthly shaft rotation, quarterly insulation resistance, six-monthly desiccant changes — running in parallel with everything else on the project.
In Deskely those routines are defined per tag and run independently of the commissioning sequence. Overdue cycles surface continuously instead of being discovered during a handover review, and every completed cycle carries a name, a role and a timestamp.
That history is what settles a warranty argument. Not a claim that preservation was performed, but two years of signed cycles that can be filtered to the tag in question.
Handover and audit
Care and custody transfers on evidence, never on assertion.
An operator's completions team does not audit your process. They audit a tag. They pick one, ask what happened to it, and expect the installation check, the calibration, the preservation history, the punch position and the test result to appear with the names of the people who signed them.
Because certificates in Deskely are issued from the records rather than alongside them, that chain already exists. Open the tag, see every record, follow the link up to the certificate those records permitted and down to the drawing the tag came from.
The handover dossier is therefore not a document produced at the end of the project. It is exportable per subsystem on any day of the project, including the ones where the answer is uncomfortable.
What you get
The full completions stack, at project scale.
Every record type an oil and gas scope needs, on one relational model, with AI to compress the register and structure work that normally consumes the first months of the project.
AI drawing parser
Extract tags from P&IDs and flag conflicts between drawings, line lists and the register before they propagate into thousands of records.
Learn moreAI project population
Build the system, subsystem and ITR structure from the EPC document set as a reviewable draft your completions lead corrects rather than types.
Learn moreA, B and C ITRs
Static, dynamic and commissioning test records signed against tags, rolled up to subsystems and exportable per test pack.
Learn morePreservation routines
Per-tag cycles with their own cadence, overdue visibility and a signed history that survives a multi-year construction period.
Learn moreCategory A and B punch
Defects raised at the tag with photos, categorised by whether they block MC or RFSU, and gating the certificate above them.
Learn moreMC, RFSU and handover
Layered certificates that only issue when the records, punch and preservation beneath them permit it — no manual cross-check.
Learn moreSubsystem walkdowns
Structured joint inspections with the client, with punch raised on the walk and the MC certificate built from the result.
Learn moreSigning rights by role
Discipline and role-based authority over what can be signed, with contractor and vendor access scoped to their own records.
Learn moreWho works in it
One register, six different jobs to do in it.
Everyone on an oil and gas completions scope needs a different view of the same records. Deskely scopes what each role can see, edit and sign rather than giving everyone a copy of the file.
Owns the number
Completions lead
Sees subsystem readiness derived from signed records instead of assembling it from four contractor reports the night before the progress meeting.
Certification modelOwns the evidence
QA / QC engineer
Reviews and rejects ITRs at the tag, sees which forms are outstanding per test pack, and exports the pack in the operator's required structure.
ITR recordsOwns the sequence
Commissioning engineer
Runs B and C records and commissioning procedures against subsystems that have already earned MC, with prerequisites visible before mobilising a crew.
CommissioningOwns the cadence
Preservation coordinator
Works from a live overdue list per tag rather than a spreadsheet reconstructed from memory, and can prove every completed cycle years later.
PreservationOwns acceptance
Operator representative
Walks down subsystems with the contractor, raises punch on the spot with photos, and accepts care and custody against a dossier that already exists.
WalkdownsOwns their package
Vendor and subcontractor
Completes and signs only its own records, scoped by access rights, while the progress still rolls up into the project register without a manual import.
Access controlHow it runs
The sequence an operator expects to see.
- 01
Build the register
Tags extracted from the drawing set and mapped to systems and subsystems, with drawing-to-register conflicts resolved before construction records start.
- 02
Construct and preserve
A-ITRs signed as installation completes, preservation running on everything installed and idle, punch raised at the tag from day one.
- 03
Mechanical completion
Subsystem walkdown with the client, Category A punch cleared, MC certificate issued only when the underlying records permit it.
- 04
Commission and RFSU
B and C records and commissioning procedures executed, RFSU issued per subsystem, care and custody transferred on evidence rather than assertion.
The difference
Register reconciliation versus one relational model.
At oil and gas scale the difference is not convenience — it is whether the handover date is achievable at all.
| Aspect | Multiple registers | Deskely |
|---|---|---|
| Tag setup | Months of manual extraction and mapping. | AI-drafted register that engineers review and correct. |
| Drawing revisions | Re-read the drawings to find what changed. | Conflicts flagged against the register when the revision lands. |
| Subsystem changes | Find-and-replace across several files. | Change once; dependent records follow. |
| Preservation | A separate spreadsheet nobody opens until an audit. | Scheduled routines with overdue items surfaced continuously. |
| Punch categories | Argued in the handover meeting. | Categorised at capture and gating the certificate directly. |
| Certificate integrity | Issued on a manual check of several lists. | Blocked until prerequisites are demonstrably satisfied. |
| Audit response | Days of searching folders. | Filter to the tag, open the signed record. |
What changes
Tens of thousands
of tags handled on one register
Multi-year
preservation tracked without a separate system
Layered
MC, RFSU and handover certification enforced
Auditable
signature trail on every record
Terminology
The completions vocabulary an operator will use.
Terms differ slightly between operators and regions, but the sequence behind them does not. These are the definitions Deskely is built around.
- Inspection and test recordITR
- The signed form proving one check on one tag. A-ITRs cover static installation checks, B-ITRs dynamic and functional testing, and C-ITRs commissioning and performance testing.
- Test pack
- The bundle of ITRs, drawings and certificates covering a defined portion of a system — typically the unit an operator reviews and signs rather than an individual form.
- Mechanical completionMC
- Confirmation that a subsystem is built and installed in accordance with drawings and specifications, with static testing complete and no Category A punch outstanding.
- Ready for start-upRFSU
- Confirmation that a subsystem has been commissioned and is safe and ready to be introduced to process. RFSU sits above MC and cannot be issued before it.
- Pre-start-up safety reviewPSSR
- The operator's final review before hydrocarbons are introduced, checking that documentation, safety systems, procedures and training are in place.
- Care, custody and controlCCC
- The point at which responsibility for a subsystem transfers from the contractor to the operator — conditional on the evidence being complete and retrievable.
- Category A punch
- A defect that must be corrected before the certificate above it can be issued, because it affects safety, function or the ability to operate the subsystem.
- Category B punch
- A defect that does not prevent start-up and is carried forward past handover, remaining on the outstanding list with an owner and a target date.
- Preservation routine
- A recurring maintenance activity — shaft rotation, nitrogen purge, insulation resistance, desiccant change — performed on installed but idle equipment until start-up.
- Subsystem
- The smallest independently commissionable portion of a system. Certification, punch, readiness and handover in oil and gas are all managed at this level.
- Handover dossierMDR
- The compiled documentation package transferred to the operator — certificates, signed records, as-builts and vendor data — usually retained for the life of the asset.
- Punch list walkdown
- A joint inspection of a subsystem by contractor and operator, during which remaining defects are raised, categorised and agreed before the certificate is issued.
New to the sequence? Read the plain-language guide to commissioning and completions.
FAQ
