Equipment Commissioning

Equipment Commissioning connects a delivered serial number to installation checks, repeated test attempts and a manager-approved in-service handover. Inventory remains responsible for physical movements. Maintenance remains responsible for equipment records and subsequent maintenance work.

Installation and requirements

Install corvus_equipment_commissioning on Odoo 20.0 with the standard Inventory (stock), Maintenance (maintenance) and Discuss/mail (mail) dependencies. Add the folder to the configured addons path, update the Apps list and install Equipment Commissioning. Installation creates numbering sequences and the General equipment handover test profile. No external account, hardware connection, scheduled job or outbound integration is needed.

Tested on Odoo 20 Enterprise, including installation with and without demo data and focused workflow checks. Community edition has not been qualified. No compatibility with earlier Odoo versions is claimed.

Optional demonstration data includes fictional pump deliveries, a failed pressure test followed by acceptance, a partially completed repeat attempt, a draft and a cancelled installation. Demo stock is received and delivered using native stock movements. Enable demo only in a suitable demonstration database.

Roles and company access

An administrator assigns roles under Settings → Users → Equipment Commissioning.

Engineer Create records from eligible deliveries, select the site/profile, record attempts, link existing maintenance equipment, prepare handover evidence and read reports. This role also implies native Inventory user access.

Manager All engineer actions, plus profile configuration, native maintenance equipment creation, acceptance, cancellation, resume and deletion of unused drafts.

No commissioning role No access to commissioning business records or reports.

Records, attempts and readings follow the user's allowed companies. A private installation contact from another company cannot be linked. Profiles may be shared by leaving Company empty, or restricted to a company. Shared contacts remain usable in accordance with native Odoo contact access. This module does not introduce separate per-site membership or portal access.

A commissioning manager can create a native equipment record; this does not grant general maintenance administration or permission to edit existing equipment. A maintenance administrator handles later changes in the Maintenance application.

Set up a test profile

Open Commissioning → Test Profiles as a manager. The supplied general profile contains serial identity, installation/function and operator-handover checks. Adapt it to your equipment or create a separate profile.

1. Name the profile and optionally set its company.
2. Choose its default warranty reference basis: Delivery date, In-service date or Manual reference.
3. Add checks in the desired order. At least one check must be required.
4. Choose Pass / fail check for an inspection or Measurement for a numeric reading.
5. For measurements, enter a unit such as bar, V or °C, and inclusive minimum and maximum limits. These are engineering labels; the module does not convert units.
6. Add practical instructions and save.

The profile's warranty basis is copied when a commissioning record is created. Selecting another profile later does not silently change that record's warranty basis; review it on the Handover and warranty reference page.

Each new attempt receives its own copy of the profile's names, instructions, required flags, units and limits. Editing a profile never changes previous attempts. Removing all required checks prevents new attempts from starting.

Create or reopen a delivered serial

Complete the normal Inventory delivery first. The product must use serial-number tracking; the operation must be a completed outgoing delivery to a Customer location, with a positive delivered quantity and a customer/contact.

Open the completed delivery and select Commission equipment. A record is created for each eligible serial, using the delivery contact as the installation site. If a record already exists for the same company and serial, the action opens that record, including an archived record. Repeating the action does not create duplicates. Multiple delivered serials open a filtered list.

Alternatively, use Commissioning → Equipment → New, select an eligible completed delivery line, installation site and profile, and save. One record is permitted per company and serial. The original delivery identity and a copy of the serial plate text are fixed when the record is created. A later re-delivery of the same serial reopens its existing history; it does not create a second commissioning episode.

Before starting tests, verify the site, engineer, profile and warranty reference basis. The installation site becomes fixed when the first attempt starts. Use Installation notes for preparation details.

Record an attempt

Select New attempt. The record changes from Draft to Testing and opens the copied checklist.

• Carry out each required check and tick Recorded when it is complete.
• For a Measurement, enter the numeric Reading in the displayed unit. Zero is a valid reading when Recorded is ticked. A value at either limit passes.
• For a Pass / fail check, tick Check passed only when the requirement is met.
• Add a row note where useful. The Instructions column can be enabled from the list's column selector.
• Enter Findings and corrective work if any recorded check fails.

Select Submit results. Missing required checks prevent submission. All recorded checks, including optional ones, must pass for the attempt to be marked Passed. Otherwise it is marked Failed. Submitted rows, definitions and findings are retained unchanged. Another attempt cannot start while an existing attempt is open.

If a reading is wrong before submission, correct it on the open attempt. After submission, start a new attempt and record the corrected results. Failed attempts remain visible in Test history and in the commissioning report. A manager may change a profile before the next attempt; the next attempt uses those updated checks.

Worked example: failed pressure test to acceptance

The optional demonstration record for serial HF-PUMP-101 at Harbour Foods — Demonstration Site illustrates this sequence.

1. Deliver the serialized transfer pump using Inventory.
2. Create its commissioning record and select Transfer pump — installation checks.
3. Verify the serial plate. Record outlet pressure of 4.1 bar against a 5–6 bar range, and complete the operator check.
4. Explain that the inlet strainer needs attention and submit. The attempt becomes Failed.
5. Perform corrective work, start another attempt and record 5.4 bar. Complete the other required checks and submit. The attempt becomes Passed.
6. Link matching native maintenance equipment, or have a manager select Create maintenance equipment.
7. Set the actual In-service date, attach the handover document and describe the recipient and material provided in Handover summary.
8. A manager selects Accept in service and confirms. The record becomes In service; the accepting user, timestamp and accepted attempt are retained.

The second Harbour Foods serial, HF-PUMP-102, has a failed attempt and an open repeat attempt awaiting its final operator briefing. The Orchard Works examples show Draft and Cancelled states.

Maintenance equipment and acceptance

Select an existing Maintenance equipment record whose serial number exactly matches the retained delivered serial. A manager may use Create maintenance equipment to create and link one with the product and serial as its name. Repeating creation is blocked once a record is linked. The module does not create maintenance requests or maintenance schedules.

Acceptance requires all of the following:

• The record is Testing and its most recent attempt is submitted and Passed.
• The In-service date is on or after the delivery date and not in the future.
• Matching native maintenance equipment is linked.
• A handover file and Handover summary are present.
• A manual warranty reference date is present when Manual reference is selected.
• The acting user has the Manager role.

Only the latest attempt controls acceptance. Starting a new attempt after a passed attempt makes the record ineligible until the new attempt is completed and passed. Approval does not post invoices or create any financial obligation.

Accepted business details and their retained handover file are locked, including direct attachment changes. Chatter and activities remain available for follow-up. Accepted records cannot be reopened for further commissioning or assigned to a different delivery. Keep subsequent servicing in Maintenance. The handover upload is document retention; it is not an electronic-signature service or an independent document-authenticity check.

Warranty reference

The record displays one informational warranty-start reference:

• Delivery date: the date of the original completed delivery.
• In-service date: the proposed in-service date, approved when the record is accepted.
• Manual reference: an explicitly entered reference date.

Before acceptance, the date is provisional. The module does not calculate warranty duration, determine eligibility, adjudicate claims, renew coverage or create accounting entries. Interpret the reference according to your separate commercial agreement.

Cancellation, resume, archiving and corrections

A manager can enter a Cancellation reason and select Cancel on a Draft or Testing record. Existing attempts and evidence are retained. A manager can later select Resume on the same record. It returns to Testing if it has attempts, otherwise to Draft; the reason remains available and status changes are recorded in chatter. Complete any existing open attempt before starting another.

Archive records to remove them from the normal list. The Archived search filter finds them again, and the delivery action still reopens the existing record. Only unused drafts can be deleted by a manager; records with attempts must be retained. Submitted attempts and their checks cannot be removed.

Correct the site before the first test. After testing has begun, the site is fixed to avoid applying one site's evidence to another location. The product is designed for an initial commissioning history per serial/company, not relocations or multiple independent commissioning episodes.

Lists, search and reports

The Equipment list shows product, serial, installation site, engineer, status, attempt count and in-service date. Add the delivery or warranty reference date through the optional column selector. Search by record number, serial, product, site or engineer; use My equipment, Draft, Testing, In service, Cancelled and Archived filters. Group by status, site, engineer or company.

Open Attempts from the record's smart button to search its attempts. The Test history tab provides direct navigation to each attempt. Use native chatter and activities to assign a follow-up or record a discussion.

Select Commissioning report, or Print → Commissioning Evidence, to request the native report with delivery identity, site, engineer, maintenance link, acceptance details, handover summary and every attempt's readings and preserved limits. Reports for records not in service display an explicit unaccepted notice. The handover filename is listed; its contents are not embedded in the report. Open the retained file separately from the record. Report access follows commissioning record and company permissions.

HTML report rendering is verified. Server PDF output requires a working native Odoo PDF engine in your deployment. PDF output was not qualified in the tested runtime.

Upgrades and data retention

Back up the database and filestore using your normal Odoo procedure before upgrading. The installed sequence and general profile use protected reference data, so routine module upgrades preserve user edits to their names, prefixes, warranty basis and checklist configuration. Existing attempt snapshots also remain unchanged. Test custom integrations against the current workflow: direct state writes, imports of approval fields and arbitrary creation of attempt rows are rejected.

Retain the database and filestore together to preserve uploaded handover evidence. Uninstalling the application removes its business data according to Odoo's normal uninstall behavior; archive records for day-to-day retention instead.

Troubleshooting

No Commission equipment action Check the commissioning role, completed delivery status and outgoing operation type.

No eligible equipment Check product serial tracking, assigned lot/serial, positive delivered quantity and Customer destination.

Duplicate serial message Open the existing commissioning record; include archived records in the search.

Cannot submit Complete every required check. For failed results, enter Findings and corrective work.

A numeric result fails unexpectedly Check the entered unit, value and inclusive limits retained on that attempt. Unit conversion is not automatic.

Cannot accept Check latest attempt status, equipment serial, handover file/summary, date range, manual reference and Manager role.

Cannot create equipment Use a commissioning manager. Engineers can select an existing matching record.

Company or site access error Select an allowed company and a shared or same-company contact/equipment/profile. Ask an administrator to correct legitimate access.

Another user is updating the record Allow the other operation to finish, refresh and retry once.

Cannot edit submitted evidence Start a new attempt before acceptance. Accepted records are retained unchanged.

Report is marked unaccepted Only an In service record represents an approved handover; draft, testing and cancelled reports are clearly identified.

Support and scope

Contact Corvus Nexus Technologies LTD at support@corvusnexus.com, or visit https://corvusnexus.com. Include the Odoo version, module version, affected record reference, expected result and reproducible steps. Share customer data only through an agreed support channel.

This module provides manual commissioning records and evidence. It does not include hardware acquisition, automatic delivery rules, Field Service scheduling, billing, digital signatures, warranty adjudication, a statutory safety certificate, portal access or an offline application.

Availability

This guide covers the Odoo 20 package. Older-version packages are not part of this release.

Browse the Corvus Odoo Apps catalogue.