How to accept infrastructure after installation without confusing it with machine acceptance ART-170

Two objects, two outcomes

Infrastructure acceptance answers whether the prepared systems provide agreed conditions at the machine connection points, are safe and have proper as-built documentation. Machine acceptance answers whether the delivered equipment is correctly installed, its functions work and contractual criteria are met under established and accepted external conditions.

The first process produces a package of accepted interfaces with a residual punch list. The second produces a SAT protocol or another agreed machine acceptance record. They are dependent: full SAT must not rely on unverified infrastructure. But dependency does not mean identity.

Bystronic publicly describes preparation, delivery, installation and commissioning as separate laser-project phases. This is a vendor-specific service description, not a universal contractual model, but it clearly demonstrates the need for different checkpoints.

Build a responsibility-boundary matrix

Start with a list of demarcation points: physical or information boundaries where the customer's system hands a resource over to the machine. For each boundary, identify the design owner, installer, testing party, criterion, evidence and party accepting the result.

Typical boundaries:

• power supply inlet or terminals defined by the OEM;
• protective bonding point and external grounding system;
• shutoff assembly and connection for each industrial gas;
• compressed-air outlet providing the required quality;
• extraction connection flange or branch;
• external cooling supply and return, where specified;
• Ethernet port or controlled network segment;
• mechanical interface with a loader, storage system or conveyor;
• positioning datum and verified base.

IEC 60204-1 states that the machine electrical equipment it covers begins at the supply connection point. This is a useful boundary principle, but manufacturer documents and the local design define the exact point for the delivery. Do not automatically transfer the electrical boundary to gases, extraction or data.

Acceptance of the base and geometric positioning

After installation, check that actual module positions match the approved layout and have not compromised service or logistics areas. As-built coordinates, elevations, anchors, grout and base condition are accepted through the building or structural process against the design. Machine leveling, when performed by the OEM, belongs to machine installation.

Do not confuse “the base complies with the design” with “the machine is leveled according to the manufacturer's procedure.” As-built and construction documents confirm the first; an installation protocol confirms the second. If the OEM compensates for a small deviation through permitted adjustment, this must not conceal an unaccepted structural nonconformity.

Separately check access to anchors, filters, reservoirs, cabinets, replaceable cassettes and major-service assemblies. ART-162 explains lifecycle envelopes; acceptance only confirms that agreed areas have actually been retained.

Electrical-infrastructure acceptance

The electrical package must confirm more than “voltage is present.” An up-to-date single-line diagram, cable and device identification, test results, accessible disconnection, coordinated protection, protective conductors and absence of unapproved temporary arrangements are needed. The local design, current regulations and OEM package define criteria and methods.

The machine installer then records conditions at the connection point and performs its own pre-start checks within the delivery scope. If voltage drops or supply instability occur during SAT, the incident should not automatically be called a machine defect. First compare demarcation-point data with accepted criteria and the event log.

Changing a circuit breaker, cable or transformer after acceptance creates a new configuration. It requires rechecking relevant criteria, not a handwritten correction to the old certificate.

Gas and compressed-air acceptance

For each medium, check identification, system condition, leak-tightness under an approved procedure, parameters at the point of use and behavior under representative flow. A static gauge does not prove that pressure will hold during cutting. A gas-batch certificate does not confirm purity after the main. This is precisely why infrastructure records must be separated from trial cutting.

Machine SAT may use the agreed gas for process samples and confirm the process result. But if the material or gas differs from the contractual matrix, a successful sample does not close the original criterion. Record the source, grade, actual parameters, material and settings in the protocol.

An oxygen system has separate compatibility and cleanliness requirements. This article provides no testing or purging procedure; that is work for competent parties under the design and local requirements.

Extraction and microclimate acceptance

Accept extraction as a system: fan or filter, ductwork, dampers, discharge or recirculation, electrical supply, automation and the agreed machine interface. Fan rotation alone is insufficient. A functional test in defined modes, recorded settings and filter condition, and confirmation that the system creates no unacceptable indoor conditions are required.

During machine SAT, check the machine with the accepted extraction system on agreed materials. If the filter is already contaminated with construction dust or a duct is temporarily open, the test is not representative. Record temperature and humidity throughout the test, rather than reconstructing them later from memory.

Extraction calculation and selection belong to ART-157 and ART-158; acceptance does not redesign the system but compares actual results with approved criteria.

Network and digital-interface acceptance

The IT team confirms the segment, addressing, time synchronization, asset identification, backups and controlled service access. A successful ping does not prove readiness for production operation. Permitted flows, roles, logs, recovery and temporary supplier-access procedures must be checked.

Meanwhile, machine SAT checks only agreed delivery functions: program transfer, licensing, telemetry, integration with permitted software or remote diagnostics. Do not require the OEM to sign off the corporate network architecture unless it is in the contract; similarly, IT cannot confirm CNC functionality merely because a cable is connected. ART-163 covers architectural decisions.

Establish the energization sequence

A joint hold point is needed before energy is first applied. Infrastructure owners confirm resource and protective-measure readiness; the machine installer confirms completion of its scope; the coordinator confirms a safe area and permission for the next step. All temporary jumpers, removed guards or unfinished connections must be explicitly listed.

OSHA 1910.147 is a US rule illustrating the importance of defined hazardous-energy control during servicing and isolation verification. It does not replace a Ukrainian procedure or OEM instructions. Competent parties define local LOTO procedures, roles and equipment. Agree these before operation, because customer personnel will control energy sources after handover.

Machine SAT starts with controlled conditions

Before SAT, record a baseline: software and parameter versions, option configuration, material, gas, consumables, temperature, extraction condition and external resources. Otherwise, a failed test becomes an argument about causes and a successful one is difficult to reproduce.

SAT must follow the agreed protocol. Depending on the contract, it may include safety functions, axis movements, automation, accuracy, part quality, productivity, alarm handling and recovery. This article specifies no universal tolerances or test parts. The contract, OEM procedure and standards explicitly included in scope define them.

Do not add a criterion after seeing the result. If a new test is needed, document a change with its purpose, method, resources and the parties' decision.

Maintain two punch lists

One deviation list for the entire project is convenient only on a summary dashboard. Acceptance needs at least two logical processes: an infrastructure punch list and a machine punch list. Every item has an observation description, criterion reference, evidence, criticality, owner, deadline, temporary control and closure condition.

Category `A` blocks safe energization or the main acceptance test. Category `B` permits limited continuation under conditions agreed in writing. Category `C` does not affect safety or contractual operability but must close before final handover. Category names may differ; consistent logic in the contract and protocols is what matters.

An item is not closed by the word “fixed.” It needs retesting against the same criterion, evidence and an authorized party's signature. If a repair changes another interface, check dependent tests.

Do not accept causality without data

When cutting is unstable, it is easy to blame the machine, gas or voltage intuitively. The correct sequence is to preserve the event, avoid changing several factors at once, collect boundary data and compare it with the baseline. If gas pressure at the point of use met the criterion, this narrows the search but does not yet prove a head fault. Stable voltage does not rule out an internal electrical problem.

A useful incident record contains the time, program, material, operation, alarms, environmental conditions, infrastructure readings and changes before the event. Such a record helps distinguish a warranty defect, external condition, setup error or workpiece instability.

Operational handover package

The final handover package must let another competent team understand what has been accepted and in which configuration. It includes the approved layout, as-built diagrams, infrastructure reports, parameter baseline, SAT, closed and open punch lists, OEM instructions, training, backups, consumables list and configuration-change rules.

ISO 12100 provides the general lifecycle framework for risk assessment and reduction. A significant change to an interface, automation or operating method after acceptance must therefore undergo controlled impact analysis. The public ISO page does not replace the full standard or assessment of a specific machine.

Handover does not mean all observations must necessarily be closed if the contract permits residual items. It means their criticality, owners, deadlines and restrictions are transparent, and equipment is not operated outside the accepted state.

A practical boundary check

Before signing, ask one question of each piece of evidence: does it confirm an external condition or a machine function? A dynamic gas-pressure report at the connection point is infrastructure. The cutting result with agreed gas is the machine and process. A base acceptance record is infrastructure. A leveling protocol under the OEM procedure is machine installation. A configured VLAN is IT infrastructure. Successful NC-program transfer is a delivery function.

If a document tries to confirm everything at once, divide it into sections with their own criteria and signatures. This reduces disputes, accelerates diagnostics and creates a reliable service baseline. Acceptance becomes a controlled transition from construction and installation to responsible operation, not a final ritual.

Prepare the acceptance plan before testing

Agree criteria, methods and roles before the team sees the first result. The acceptance plan contains systems, test dependencies, required instruments, materials, recording format, hold points and stop authority. State prerequisites for each test: for example, the gas system is already accepted, the filter is operational, the software version is recorded and unrelated work has been cleared from the area.

The plan also determines who supplies test sheets or tubes, assist gases, measuring equipment and operators. If the customer's material has unknown geometry or certification, do not quietly make it the sole basis for a conclusion about the machine. Record departures from agreed prerequisites before testing and decide whether the result remains valid.

A convenient sequence is document review, visual inspection, safe application of individual resources, infrastructure functional checks, machine pre-start checks, dry run, process samples, automation tests, recovery and final review. The actual sequence depends on the OEM; do not mechanically transfer this list into a specific delivery procedure.

A test sheet must be reproducible

Each test sheet must let someone repeat the check without the author's explanation. Record the requirement ID, source revision, equipment condition, instrument and its validity, measurement points, actual values, permitted criterion, result, time and signatures. For a functional test, add the initial state, action, expected response and actual response.

A photograph is useful for valve position, labeling or general condition, but does not replace measurement. An alarm screenshot may confirm a message, but without time, configuration and operator action it does not show the full sequence. Video must not be the only carrier of criteria. Store numerical data in a controlled format with units.

If a test fails, do not erase the original record after correction. Create a new attempt linked to the deviation, change description and retest result. This preserves the causal chain and shows whether compliance was achieved through an arbitrary setting.

Conditional acceptance needs restrictions

`ACCEPTED WITH OPEN ITEMS` is permissible only under agreed rules. The document must state which modes are allowed, which functions are blocked, the condition's expiry date, who monitors compliance and what happens after the deadline. A verbal “you can work carefully” is not a control.

For example, an unfinished report that does not affect safety or function may remain an administrative item. Unstable gas pressure, a missing protective element, an untested emergency disconnect or undefined energy isolation must not be downgraded to a cosmetic category to meet the startup date.

During conditional operation, collect data specifically for the interface at risk. If the temporary control fails or conditions change, permission to use the affected mode is withdrawn until reassessment.

Preserve the baseline after handover

The accepted configuration must be protected against unnoticed changes. Maintain a modification log for electrical systems, gas settings, extraction, network rules, software, automation and mechanical interfaces. Each change must have a reason, impact assessment, verification plan and updated documentation.

During the first production weeks, it is useful to compare actual resource peaks and alarms with the acceptance baseline. This is not endless SAT, but early detection of systematic differences between the test mix and real mix. If the operating profile differs substantially from the agreed one, review assumptions rather than expecting a short SAT to guarantee an untested mode.

Conduct a one-page boundary review

Before final signing, consolidate all demarcation points into a compact map. For each point, show the upstream system, physical interface, downstream equipment, operating owner, criterion document, latest test result and open deviations. The map does not replace protocols but reveals gaps between them.

If a row lacks a clear upstream owner, a failure will be passed between contractors. Without a downstream owner, no one confirms that the resource is suitable for the machine. If the criterion references an obsolete OEM-package revision, review the test. If proof exists only verbally, the status cannot be `ACCEPTED`.

Invite boundary owners rather than all project participants: structural, electrical, gas, ventilation, IT, OEM and future operations. Review every row and separately record which post-test changes may have invalidated the evidence. This matters especially when building work continued alongside commissioning.

Separate warranty from the acceptance fact

A signed SAT proves the agreed result under recorded conditions, but does not rewrite warranty terms or create unspecified obligations. Similarly, infrastructure acceptance does not release a contractor from a hidden defect if the contract provides otherwise. The contract determines legal consequences, while the technical package must preserve facts without arbitrary interpretation.

In the protocol, separate `observed result`, `acceptance decision`, `open obligation` and `operational restriction`. This reduces the risk of a successful test being read as closing every issue, or a minor open item unjustifiably blocking safe operation.

Need service advice?