Short answer. ICARUS Ops EES has a formal version control and approval process, defined by the customer. The system ensures only the current approved version ever reaches the field for execution.
Definition. Version control means tracking every change to a procedure, who made it, and who approved it. ICARUS Ops EES handles all of this automatically.
Why version control matters
An out-of-date procedure version in the field is a common failure point. When copies multiply, as printouts, emailed PDFs or files on laptops, no one can be sure which one a crew used.
One approved version in the field
Only the released and approved version will reach devices. Older versions will be retired so they cannot be opened by mistake.
Who can edit
Each company defines who has editing and approval authority in its ICARUS Ops EES workflow.
How changes are approved
An authorized author drafts the change. Reviewers are assigned by the customer, for example engineering, safety, or the site commissioning lead. An approver releases the new version. A manager assigns it to a person or department for execution at the correct site.
How field feedback becomes a new version
Crews find unclear or impossible steps. Give them a simple way to report the step and the problem, then route it to the author for the next approved version.
Audit trail
Keep every version, the change, the author, the approver and the date, and record which version each crew ran.
Where ICARUS Ops fits
The ICARUS Ops Error Elimination System (EES) keeps authoring at HQ, with review, approval and version control in the ICARUS Ops web portal. Only the approved version goes to the field, and any field user can tap Suggest on a step to send a marked-up photo and note to leadership to correct the procedure.
See a sample ICARUS Ops EES procedure
See a sample ICARUS Ops EES procedure
Demos are for teams actively evaluating software for deployment.