Knowledge
Practical reference material for defining system status, preparing controlled tests, coordinating interfaces and building a defensible handover record.
This is field-oriented guidance drawn from commissioning and project-delivery experience. It explains useful working distinctions without claiming that one sequence, certificate set or acceptance gate applies to every project.
Reference 01
Use this page to frame a technical discussion, test a readiness claim or identify the evidence that should exist at a project gate. The controlling definition must still come from the actual contract, system, asset and jurisdiction.
This reference does not replace applicable legislation, contract requirements, approved project procedures, engineering calculations, original equipment manufacturer (OEM) instructions, Flag or classification-society requirements, client standards, risk assessments, permits, isolations or competent engineering judgement.
Terminology and acceptance gates vary between clients, contracts, asset types and jurisdictions. A familiar label should never be taken as proof that the underlying scope, authority or evidence is equivalent.
Reference 02
The sequence below shows a common relationship between project stages. Projects may combine, rename, repeat or reorder stages, and responsibility may transfer at different points.
| Phase | Typical entry condition | Principal purpose and activity | Expected evidence | Normal exit or transfer |
|---|---|---|---|---|
| Systemisation and boundary definition | Design and scope sufficiently developed | Break the asset into controllable systems and define physical, functional and responsibility boundaries | System list, marked drawings, boundary and interface records | Agreed basis for completion and commissioning control |
| Construction completion | Installation work released for inspection | Finish and inspect the defined construction scope | Inspection and test records, redlines, defect and punch records | Defined scope available for mechanical-completion review |
| Mechanical completion | Required construction and inspection records available | Confirm the agreed boundary is installed and inspected, subject to accepted exceptions | Inspection and test records (ITRs), walkdown record, punch list and certificate | Accepted release for specified pre-commissioning work |
| Pre-commissioning | Mechanical-completion prerequisites and controls accepted | Prepare and prove equipment or systems before functional operation, using the approved scope | Cleaning, calibration, continuity, pressure, loop or other project-defined records | Defined system condition available for commissioning |
| Commissioning | Approved procedure, utilities, interfaces and readiness evidence available | Demonstrate integrated function within a controlled test envelope | Functional tests, settings, exceptions, trends and witnessed results | Accepted readiness for the next defined operating state |
| Start-up or initial operation | Required commissioning and operational-readiness gates accepted | Introduce the system to its intended operating state under authorised control | Start-up record, operating parameters, deviations and stabilisation evidence | Stable condition for continued operation or performance testing |
| Performance testing | Stable configuration and agreed test conditions established | Compare measured performance with contract or project acceptance criteria | Test method, calibrated data, conditions, calculations and accepted result | Performance result accepted, rejected or conditionally closed |
| Acceptance | Required technical evidence and exceptions presented | Make the defined technical or contractual acceptance decision | Certificate, approval, reservations and action ownership | Accepted status and responsibilities recorded |
| Turnover and handover | Transfer boundary, evidence and receiving authority agreed | Transfer the system, its known condition, records and remaining obligations | Dossier, turnover package, operating information and handover record | Receiving organisation assumes the stated responsibility |
Sequence boundary: Certificate titles and gates are project-specific. Completion of one row does not automatically authorise the next activity.
Reference 03
These terms are often used as if they were interchangeable. The practical difference is usually the boundary, evidence or decision being controlled.
| Distinction | Practical difference | Question that exposes the boundary |
|---|---|---|
| Construction completion / mechanical completion | Construction completion describes finished installation work; mechanical completion is an accepted status for a defined boundary, supported by inspection evidence and controlled exceptions. | Who accepts the boundary and which incomplete items may remain? |
| Mechanical completion / pre-commissioning | Mechanical completion establishes an installed condition; pre-commissioning performs the approved preparation and proving work needed before functional commissioning. | What activity is now permitted, and what energy or test medium may be introduced? |
| Pre-commissioning / commissioning | Pre-commissioning prepares individual equipment and systems; commissioning demonstrates functional and integrated behaviour within an authorised test scope. | Is the test proving preparation, component function or integrated system performance? |
| Commissioning / start-up | Commissioning proves defined functions; start-up moves the system into an intended operating state. Some projects overlap the terms, so the authorised transition matters more than the label. | What operating state will change, and who authorises it? |
| Site acceptance test / performance test | A site acceptance test (SAT) demonstrates agreed functions after installation; a performance test measures whether the system meets specified output or efficiency criteria under defined conditions. | Are we accepting functionality, measured performance, or both? |
| Ready for test / ready for operation | A controlled test may tolerate temporary arrangements and a narrow boundary that would be unacceptable for sustained operation. | Which conditions are valid only for the test, and what must be reinstated? |
| Punch closure / system acceptance | Closing individual punch items removes recorded exceptions; acceptance is a broader decision about the system condition and evidence. | Does the remaining evidence support acceptance, even when the punch count is low? |
| Turnover / final handover | Turnover may transfer a system or dossier between delivery functions; final handover may transfer wider operational or contractual responsibility. | What exactly transfers, to whom, and with which remaining obligations? |
| Technical completion / commercial completion | Technical completion concerns physical condition, function and evidence; commercial completion concerns contractual entitlement, payment or liability and may follow different rules. | Is this an engineering decision or a contract decision? |
| System boundary / physical equipment boundary | A system boundary follows the function being completed or tested and may cross equipment packages, disciplines and locations; an equipment boundary follows the physical package. | Which supplies, controls, protections and downstream functions are needed for the intended test? |
Reference 04
A readiness review should answer a defined question: whether a particular system can undertake a particular activity in a stated condition. It should expose missing prerequisites rather than convert them into an optimistic percentage.
Authority boundary: A checklist supports a readiness decision. Completing it does not itself authorise testing, energisation, operation or acceptance.
Reference 05
A credible handover record connects the physical item to the system decision. Each level should be traceable without hiding failed, superseded or incomplete evidence.
A completions-management system can control identifiers, workflow, status and document links. It does not replace field verification, technical review or competent judgement, and its reported status is only as reliable as the underlying records and configuration.
See ITRs and Verification Records and Systems Completion and Turnover.
Reference 06
Readiness depends on the right information reaching the right authority in the correct sequence. A technically complete package can still be unready when connected systems, witnesses, operating control or acceptance responsibilities are unclear.
| Interface | Information or decision needed | Common readiness risk |
|---|---|---|
| Construction | Installed condition, access, completion evidence and remaining work | Work continues inside an accepted or energised boundary |
| Engineering | Current design basis, approved changes, settings and technical queries | Testing proceeds against superseded information |
| Commissioning | Test sequence, prerequisites, configuration, results and restoration | Individual tests do not prove the integrated function |
| Vendors and OEMs | Manufacturer limits, specialist attendance, configuration and defect advice | Attendance is mistaken for project acceptance authority |
| Quality | Inspection status, nonconformities, records and traceability | Document closure is disconnected from field condition |
| Health, safety and environment | Hazards, controls, permits, simultaneous work and emergency arrangements | Changing system state invalidates existing controls |
| Marine operations | Vessel condition, weather/operation window, stability, movements and marine authority | Technical testing conflicts with marine operations |
| Class or Flag | Applicable survey, witness, certification and outstanding conditions | Project completion is confused with statutory or Class acceptance |
| Client representatives | Contract criteria, witness points, reservations and acceptance route | Technical and commercial decisions are combined without clarity |
| Operations and maintenance | Operating state, competence, procedures, spares, limitations and support | A system is handed over without sustainable operating readiness |
| Document control | Revision, status, distribution, retrieval and final record location | The team cannot establish which evidence is current |
Responsibility boundary: Participation in an interface does not by itself establish contractual authority. The project must define who supplies information, who reviews it and who makes each decision.
Reference 07
Troubleshooting boundary: This model does not authorise energisation, live work, bypassing, protection defeat or operation outside approved limits. Use the project's safe system of work and competent technical authority.
For a fuller investigation framework, use the Structured Troubleshooting Method.
Reference 08
Use measured line values and the actual system configuration. The relationships below assume a balanced three-phase system and line-to-line voltage.
S = √3 × V × I ÷ 1000
P = √3 × V × I × PF × η ÷ 1000
kVA describes voltage-and-current loading; kW describes useful real power. For a balanced load, kW is approximately kVA multiplied by power factor. Equipment ratings, harmonics and unbalanced conditions require project-specific review.
Before a generator breaker is closed under an approved test, voltage, frequency, phase sequence and phase angle must be compatible with the live bus. Automatic synchronisers and check-synchronising protection require verified settings and functional testing.
Prime-mover governing primarily controls real-power sharing; excitation and automatic voltage regulation (AVR) primarily affect reactive-power sharing and voltage. Compensation, droop, communication links and power-management logic vary by installation.
Trip testing should prove the intended function without creating uncontrolled risk. A blackout-recovery test requires an approved sequence, stable starting supplies, verified protection and clear stop criteria. Simulated signals must not be confused with full end-to-end proof.
Electrical boundary: These simplified relationships support checking and estimation. Verify wiring configuration, phase balance, ratings, protection, efficiency basis and manufacturer information before operational use.
Use the three-phase power calculator within the Electrical Engineering Calculators workspace.
Reference 09
| Check | Purpose | Typical evidence | Important boundary |
|---|---|---|---|
| Rotation | Confirm intended direction before loaded operation | Marked direction, witnessed bump test, driven-equipment check | Uncoupled testing may not prove the complete train |
| Lubrication | Establish correct oil, level, circulation and cleanliness | Approved lubricant, flushing record, pressure/flow indication | Manufacturer requirements and preservation state govern |
| Alignment | Control shaft and coupling condition | Cold alignment record, soft-foot result, final installation condition | Thermal growth and pipe strain may alter operating alignment |
| Flushing and cleanliness | Remove construction debris and commissioning contamination | Acceptance record, filter or strainer inspection, sample result | Acceptance method depends on system sensitivity |
| Pressure and leak testing | Demonstrate containment for the approved test boundary | Test pack, calibrated instruments, reinstatement record | Test medium, pressure and exclusions require engineered control |
| Temporary strainers | Protect equipment during initial circulation | Location register, differential pressure, inspection and removal record | Temporary items need visible ownership and removal criteria |
Mechanical boundary: This list does not define a test pressure, alignment tolerance, lubricant, cleanliness criterion or safe operating limit. Use approved project and manufacturer requirements.
Reference 10
Prove the path from field device through marshalling, control logic, display and final element as applicable. Record range, engineering units, indication, action and any part simulated rather than physically proven.
Test each initiating condition against the approved matrix, including sequence, delays, voting and reset behaviour. Confirm that authorised inhibits or bypasses are controlled and restored.
Verify alarm priority and acknowledgement separately from protective action. Permissives allow an action when conditions are satisfied; interlocks prevent or change action when defined conditions exist. Project terminology may differ.
Simulation can prove logic safely, but it may exclude the sensor, cabling, process connection or final element. The test record should state exactly where the signal was introduced and what remained outside the test.
Record tag, range, units, test points, expected result, actual result, instrument identity, configuration, exceptions and acceptance. Preserve before-and-after settings for authorised changes. A screenshot without tag, time and test context is weak evidence.
Controls boundary: Changes to trips, voting, permissives, protection or safety functions require authorised project-specific control. A simulated test is not automatically equivalent to full functional proof.
Reference 11
Classify each item before selecting its controls. Equipment that lifts, supports, suspends, connects or measures a load may require different design information, markings, records, examinations and competent-person decisions.
| Equipment family | Representative examples | Review focus |
|---|---|---|
| Lifting machines and appliances | Pedestal, mobile and overhead cranes; hoists; lifting winches; workplace davits; forklifts; personnel or goods lifts; mobile elevating work platforms; jacks | Identity, intended use, rated capacity or load chart, installed configuration, controls, brakes, limits and current status |
| Integral, supporting and load-carrier items | Hook and sheave blocks, hoist ropes and terminations, beam trolleys, runways, gantries, fixed padeyes and containers designed as loads for lifting | Define whether each item is part of the lifting machine, a structure or the load; then verify its design, support, marking, condition and operating limits |
| Lifting accessories | Wire-rope, chain and synthetic slings; shackles; accessory hooks; removable eyebolts; lifting and spreader beams; purpose-designed detachable lifting clamps and lifting-rated turnbuckles | Unique identification, manufacturer working load limit or rated capacity, applicable safe working load, size and grade, assembly, orientation, compatibility, damage and discard criteria |
| Load-indicating and protective devices | Dynamometers, crane weighers, load cells, safe-load indicators and rated-capacity indicators | Range, units, calibration or verification status, configuration, functional checks, alarms, limiting functions and relationship to the load path |
| Marine, offshore and personnel-lifting arrangements | Lifeboat davits and blocks, man-riding winches, stabbing boards, diving or man-riding ropes, offshore containers and detachable lifting sets | Confirm whether workplace, merchant-shipping, Flag, Class, owner or equipment-specific requirements apply; control personnel lifting and emergency functions separately |
| Control | What it establishes | Important boundary |
|---|---|---|
| Pre-use check | A user check for identification, visible condition, assembly and obvious defects before operation | Does not replace planned inspection, maintenance or thorough examination |
| Inspection | A planned condition check with a defined scope, method and record | Is not automatically a thorough examination; the required competence and purpose must be clear |
| Maintenance | Work intended to preserve or restore condition and function | Does not by itself confirm examination status or fitness for a particular lifting arrangement |
| Thorough examination | A systematic assessment by a competent person for defects affecting safe use, under the applicable examination basis | Does not remove the need for pre-use checks, maintenance or defect control between examinations |
| Testing | Functional, load or proof evidence produced to an approved method when required by the applicable design, installation, repair or examination basis | Test loads, acceptance criteria and timing must never be inferred from a generic equipment summary |
| Calibration or functional verification | Evidence that an indicator or protective device responds correctly over its required range, units, configuration and alarm or limiting points | Is distinct from proof testing and thorough examination |
Lifting boundary: Verify the actual equipment, intended use, applicable legislation, equipment-specific examination scheme, manufacturer instructions, standards, markings, test basis and competent-person decisions. Quarantine equipment when identity, condition, rating or status is uncertain.
Use the LOLER Examination Reference for examination categories and limitations, and the Best Rigging Practices guide for lift planning and execution controls.
Reference 12
Marine and offshore readiness may include jacking trials, sea trials, rig moves, load-outs, marine-system testing, Class or Flag attendance and operational-readiness reviews. These activities can change the unit's physical condition, operating authority and exposure to connected operations.
This reference does not provide an operating procedure for those activities. Each requires asset-specific engineering, approved procedures, competent personnel, formal controls, defined weather and operating limits where applicable, and the governing marine, Class, Flag, client and regulatory requirements.
For document-control context, see Sailaway Documentation Readiness and the Sailaway Documentation Reference.