SynC™

SynC · Historical revision

Process Control Networks

Revision4
EditedSep 14, 2026
StatusSuperseded
Contents

View changes in this revision   Revision history

Historical revision. This is editorial revision 4, kept so citations to it stay resolvable. It is not the current text of this standard — see the current revision.

SynC Standards Team — Specifier (Platform Standards) ✓ OfficialDiscloses employment SynC (SynC Platform Team)
Remake for template neutrality (from-scratch field inventory, five-state defaults, parameters and derived fields, schedule deferrals)

1 Scope

NOTE This standard governs the active devices, media, segmentation, redundancy, time distribution, telemetry, and security hardening of the process control network: the operational technology communications network that carries data between controllers, remote I/O, networked field devices, and the supervisory layer. (1.1)
NOTE The scope begins at the network port of each controller, I/O adapter, networked instrument, server, and workstation, and ends at the enterprise-side interface of the boundary device that separates the OT network from the enterprise network; it includes every switch, router, firewall, gateway, media converter, radio, time server, and network cable between those points. (1.2)
NOTE A process control network fails differently from an office network. A dropped office packet is retried and no one notices; a dropped control packet is a controller that has lost its I/O, a pump that has stopped, or an operator who cannot see the process. The provisions in this standard that look like excess caution beside enterprise practice exist because the consequence of a network fault here is physical. (1.3)
NOTE The following are governed elsewhere and are outside this standard: (1.4)
  • the controllers, I/O, and their application programs
  • the SCADA and HMI software, the historian, and operator workstations
  • the field instruments, analyzers, and final control elements connected to the network
  • the control panels, enclosures, and cabinets that house network hardware
  • integration, sequence programming, factory and site acceptance of the assembled control system
  • cable construction, jacket ratings, raceway, tray, and pathway
  • the building grounding electrode system and the telecommunications bonding backbone
  • enterprise local area networks, office cabling, and data-center cabling beyond the boundary device
1.5 The location of every active network device shall be as indicated on the network architecture drawings.
1.6 Network architecture, zones, and conduits shall comply with the ISA/IEC 62443 series and the segmentation guidance of NIST SP 800-82.
1.7 Wiring methods for network cabling shall comply with NFPA 70, including Article 725 for Class 2 and Class 3 circuits and Chapter 8 for communications circuits.
1.8 The Contractor shall coordinate the network with the controllers under Programmable Logic ControllersProgrammable Logic ControllersResolves to the current adopted revision.sync/programmable-logic-controllers, the supervisory layer under SCADA And HMI SystemsSCADA and HMI SystemsResolves to the current adopted revision.sync/scada-and-hmi-systems, the panels under Industrial Control PanelsIndustrial Control PanelsResolves to the current adopted revision.sync/industrial-control-panels, and the integration and acceptance work under Control Systems IntegrationControl Systems Integration and TestingResolves to the current adopted revision.sync/control-systems-integration.
1.9 Network cable materials and pathways shall comply with Conductors And CablesConductors and CablesResolves to the current adopted revision.sync/conductors-and-cables and Raceways And ConduitRaceways and ConduitResolves to the current adopted revision.sync/raceways-and-conduit, and the bonding of network equipment and cable shields shall comply with Grounding And BondingGrounding and Bonding for Electrical SystemsResolves to the current adopted revision.sync/grounding-and-bonding.

2 Referenced Standards

2.1 Equipment, materials, configuration, and installation shall comply with the latest adopted edition of each of the following unless a specific edition is cited.
2.2 Where the contract documents, the Authority Having Jurisdiction, or two referenced standards impose conflicting requirements, the more stringent requirement shall govern unless the Engineer of Record directs otherwise in writing.
Standard Title
ANSI/ISA-95.00.01 Enterprise-Control System Integration, Part 1: Models and Terminology
ISA/IEC 62443-1-1 Security for Industrial Automation and Control Systems: Terminology, Concepts, and Models
ISA/IEC 62443-2-1 Security Program Requirements for IACS Asset Owners
ISA/IEC 62443-2-4 Security Program Requirements for IACS Service Providers
ISA/IEC 62443-3-2 Security Risk Assessment for System Design
ISA/IEC 62443-3-3 System Security Requirements and Security Levels
ISA/IEC 62443-4-2 Technical Security Requirements for IACS Components
NIST SP 800-82 Guide to Operational Technology Security
AWWA G430 Security Practices for Operations and Management
ANSI/ISA-71.04 Environmental Conditions for Process Measurement and Control Systems: Airborne Contaminants
IEC 61158 Industrial Communication Networks: Fieldbus Specifications
IEC 61784-1 and IEC 61784-2 Industrial Communication Networks: Profiles
IEC 61784-5 Industrial Communication Networks: Installation Profiles
IEC 61918 Industrial Communication Networks: Installation of Communication Networks in Industrial Premises
ISO/IEC 24702 Information Technology: Generic Cabling for Industrial Premises
ANSI/TIA-568 Telecommunications Cabling Standard series
ANSI/TIA-1005 Telecommunications Infrastructure Standard for Industrial Premises
ANSI/TIA-607 Generic Telecommunications Bonding and Grounding for Customer Premises
IEEE 802.3 Ethernet, including Power over Ethernet and single-pair Ethernet clauses
IEEE 802.1Q Bridges and Bridged Networks
IEEE 802.1AB Station and Media Access Control Connectivity Discovery
IEEE 802.1AS Timing and Synchronization for Time-Sensitive Applications
IEEE 1588 Precision Clock Synchronization Protocol for Networked Measurement and Control Systems
IEEE C37.238 Precision Time Protocol Power Profile
IETF RFC 5905 Network Time Protocol Version 4
IEC 62439-2 Media Redundancy Protocol
IEC 62439-3 Parallel Redundancy Protocol and High-Availability Seamless Redundancy
IEC 62541 OPC Unified Architecture
Eclipse Sparkplug Sparkplug Specification for MQTT Topic Namespace and Payload
IEEE 1815 Electric Power Systems Communications: Distributed Network Protocol (DNP3)
IEC 60870-5-104 Telecontrol Equipment and Systems: Network Access for IEC 60870-5-101
NFPA 70 National Electrical Code
47 CFR Part 90 Private Land Mobile Radio Services
47 CFR Part 15 Radio Frequency Devices

3 Submittals

3.1 Action Submittals

3.1.1 The Contractor shall submit the following for review before active network devices are procured:
  • a network architecture drawing showing the Purdue level assignment of every device, the zones, the conduits, the boundary between the OT network and the enterprise network, and the services hosted in the demilitarized zone
  • a zone and conduit register listing each zone, the assets in it, the conduits that connect it, and the target security level assigned to each
  • an addressing plan and VLAN assignment listing the subnet and VLAN of every zone and the address of every device
  • product data for every active network device, giving port count and media, supported redundancy protocols, supported management protocols, operating temperature range, power input, environmental rating, and any ISA/IEC 62443-4-2 certification claimed
  • a protocol register listing every industrial protocol in use and the devices and conduits on which each operates
  • a media register identifying the media, category or grade, and length of each backbone and device-level segment
  • a redundancy design identifying the topology, the redundancy protocol, the ring manager assignment, and the recovery time to be demonstrated
  • a time synchronization design identifying the time reference, the distribution protocol on each segment, and the accuracy to be demonstrated
  • a telemetry design for each remote site, identifying the primary and backup bearer, the protocol, the polling strategy, and the behavior on loss of communications
  • a bill of materials and cable schedule coordinated with the cable and raceway standards
Action Submittal Packagecheckbox
☑ Network architecture drawing
☑ Zone and conduit register
☑ Addressing plan and VLAN assignment
☑ Active network device product data
☑ Protocol register
☑ Media register
☑ Redundancy design
☑ Time synchronization design
☐ Remote site telemetry design
☑ Bill of materials and cable schedule
3.1.2 Active network devices shall not be procured and network cabling shall not be installed until the corresponding action submittals have been reviewed and returned.

3.2 Informational Submittals

3.2.1 The Contractor shall submit the following qualifications, assessments, and plans with or before the action submittals:
  • the integrator's experience record and the certifications held by the personnel who will configure switches, boundary devices, radios, and time servers
  • the certification held by each person who will terminate and test optical fiber
  • the risk assessment performed under ISA/IEC 62443-3-2 from which the target security level of each zone was derived
  • the cybersecurity hardening plan, identifying the hardening measures, the account model, the conduit rule set, the patch qualification and application process, the logging design, and the backup procedure
  • the network test plan, identifying the cable test levels, the functional tests, the failover tests, the time synchronization verification, and the security acceptance method
  • the radio path study and the frequency license or license application for each radio telemetry link
Informational Submittal Packagecheckbox
☑ Integrator experience record and personnel certifications
☑ Fiber termination and test certifications
☑ ISA/IEC 62443-3-2 risk assessment
☑ Cybersecurity hardening plan
☑ Network test plan
☐ Radio path study and frequency license

3.3 Closeout Submittals

3.3.1 The Contractor shall submit the following before the network is accepted:
  • as-built network architecture and topology drawings recording every field change, the final port assignment of every device, and the patch record of every cross-connect
  • the as-configured configuration of every switch, router, firewall, gateway, radio, and time server, exported in the device's native format and in a human-readable form
  • the as-commissioned addressing plan and VLAN assignment
  • the cable test records for every copper and fiber link
  • the functional, failover, time synchronization, and telemetry test records
  • the security acceptance record, listing the as-built hardening measures, the accounts on every device, the conduit rule set, the disabled ports and services, and the firmware version of every device
  • the configuration backup media and the written restore procedure for each device class
  • operation and maintenance data for every active network device
  • warranty documentation for the devices and for the configuration work
  • a signed receipt from the Owner for the spare parts delivered
Closeout Submittal Packagecheckbox
☑ As-built architecture and topology drawings
☑ As-configured device configurations
☑ As-commissioned addressing plan and VLAN assignment
☑ Cable test records
☑ Functional, failover, time, and telemetry test records
☑ Security acceptance record
☑ Configuration backup media and restore procedure
☑ Operation and maintenance data
☑ Warranty documentation
☑ Spare parts receipt

4 Quality Assurance

4.1 Integrator Qualifications

4.1.1 The network shall be designed, configured, and commissioned by an integrator that has delivered OT networks of comparable scale and architecture for not less than the period indicated in the datasheet.
Minimum Integrator Experience with OT Networksrange
years
2351015
4.1.2 The personnel who configure switches, boundary devices, radios, and time servers shall hold the credentials indicated in the datasheet.
Network Configuration Personnel Credentialscheckbox
☑ Manufacturer certification on the switch and firewall products furnished
☐ Vendor-neutral industrial network certification
☐ ISA/IEC 62443 cybersecurity certificate
☐ Radio manufacturer certification for the telemetry products furnished
4.1.3 Every individual who terminates or tests optical fiber shall hold a recognized fiber installer certification current at the time of the work.
4.1.4 The integrator's conformance to the service provider requirements of ISA/IEC 62443-2-4 shall be as indicated in the datasheet.
Integrator Security Program Conformanceradio
○ Not required
○ Self-declared conformance to ISA/IEC 62443-2-4
○ Third-party certification to ISA/IEC 62443-2-4
4.1.5 Where the network includes remote sites served by telemetry, the integrator shall demonstrate prior delivery of a wide-area telemetry system using the bearer and protocol selected for this project.

4.2 Component Security Certification

4.2.1 The active network devices that are required to hold ISA/IEC 62443-4-2 component certification shall be as indicated in the datasheet.
Network Device Security Certification Scoperadio
○ Not required
○ Required for zone boundary devices
○ Required for all active network devices
4.2.2 Where certification is required, each device within the selected scope shall be certified to ISA/IEC 62443-4-2 for its component type at a capability security level not lower than the target security level of the zone it serves.
4.2.3 Every active network device, whether certified or not, shall be hardened in accordance with the OT Cybersecurity Baseline section of this standard before it is placed in service.
NOTE Component certification is independent evidence that a device carries the native capabilities the security level calls for, so that the level is reached through the device itself rather than through compensating controls placed around it; an uncertified device reaches the same level only where the hardening plan demonstrates each required capability another way. (4.2.4)

4.3 Staged Factory Acceptance Test

4.3.1 Whether the active network devices are configured and tested as a staged system before shipment shall be as indicated in the datasheet.
Staged Network Factory Acceptance Testradio
○ Required
○ Not required
4.3.2 Where a staged test is required, it shall verify device addressing, VLAN membership, the conduit rule set, redundancy failover, and time distribution on the assembled devices before they leave the staging location.
4.3.3 The manner in which the staged test is witnessed shall be as indicated in the datasheet.
Staged Test Witnessingradio
○ Witnessed in person by the Engineer of Record or the Owner
○ Witnessed remotely
○ Recorded and submitted without witnessing

4.4 Pre-Installation Conference

4.4.1 A pre-installation conference shall be held before network installation begins, attended by the network integrator, the electrical contractor, the SCADA integrator, the Owner's operations and information technology representatives, and the commissioning agent.
4.4.2 The conference shall settle in writing the ownership of the demilitarized zone, the authority over the conduit rule set, the authority over address assignment, and the schedule of the commissioning and security acceptance.
NOTE The seam between the OT organization and the enterprise organization is where the most project disputes originate, because each assumes the other owns the boundary; naming the owner of the DMZ and the rule set before anything is installed removes that assumption. (4.4.3)

5 Environmental and Service Conditions

5.1 Installation Environment Classification

NOTE The environment a network device or cable occupies is described by the MICE classification of ISO/IEC 24702 and ANSI/TIA-1005, which grades mechanical, ingress, climatic, and electromagnetic severity separately so that the hardware is matched to each. (5.1.1)
5.1.2 Devices and cabling shall be rated for the environmental classification of the location in which they are installed.
5.1.3 A network device installed in a classified hazardous location shall be listed for the area classification indicated on the hazardous area classification drawings.

5.2 Temperature Rating of Devices Outside Conditioned Spaces

5.2.1 The minimum operating temperature rating of active network devices installed outside conditioned spaces shall be as indicated in the datasheet.
Minimum Operating Temperature Rating Outside Conditioned Spacesrange
°C
-40-30-25-20-10
Derived — Site Ambient Temperature MinimumSite Ambient Temperature MinimumParameterEach project supplies its own value.site-ambient-temperature-minimum less the margin the enclosure heating provision does not cover (by default)
5.2.2 The maximum operating temperature rating of active network devices installed outside conditioned spaces shall be as indicated in the datasheet.
Maximum Operating Temperature Rating Outside Conditioned Spacesrange
°C
4045505560707585
Derived — Site Ambient Temperature MaximumSite Ambient Temperature MaximumParameterEach project supplies its own value.site-ambient-temperature-maximum plus the temperature rise inside the enclosure in which the device is mounted, including solar gain on an outdoor enclosure (by default)
NOTE The air inside a sealed enclosure in direct sun runs well above the ambient outside it, and the air around a switch mounted above a power supply runs above the enclosure average, so the rating is set from the temperature at the device and not from the weather station. (5.2.3)
NOTE A device installed inside a conditioned control room or server room is rated for the room and carries no requirement under this article. (5.2.4)

5.3 Corrosive and Wet Locations

5.3.1 The protection of network device electronics against corrosive atmospheres shall be as indicated in the datasheet.
Corrosive Atmosphere Protection for Network Device Electronicsselect
None
Conformal-coated electronics rated to ANSI/ISA-71.04 severity level G2
Conformal-coated electronics rated to ANSI/ISA-71.04 severity level G3
Conformal-coated electronics rated to ANSI/ISA-71.04 severity level GX
NOTE Hydrogen sulfide in a wastewater headworks or a lift station attacks the copper and silver on a circuit board at concentrations too low to smell, and the failure it causes is an intermittent contact that no diagnostic reports; conformal coating is the difference between a switch that lasts its rated life in that air and one that does not. (5.3.2)
5.3.3 The connector type for network devices in wet and washdown locations shall be as indicated in the datasheet.
Network Connector Type in Wet and Washdown Locationsradio
○ Sealed M12 connectors at the device
○ RJ45 connectors within a sealed enclosure

5.4 Device Power

5.4.1 The power source for active network devices shall be as indicated in the datasheet.
Network Device Power Sourceradio
● DC control power
○ AC branch circuit
5.4.2 Where DC control power is selected, the DC supply voltage shall be as indicated in the datasheet.
DC Supply Voltage for Network Devicesrange
VDC
122448
5.4.3 Where an AC branch circuit is selected, the AC supply voltage shall be as indicated in the datasheet.
AC Supply Voltage for Network Devicesrange
VAC
120208230240
5.4.4 Whether active network devices are furnished with redundant power inputs shall be as indicated in the datasheet.
Redundant Power Input on Network Devicesradio
○ Required
○ Not required
5.4.5 Where redundant power inputs are required, each input shall be fed from a separate power supply.
5.4.6 The Power over Ethernet class delivered from switches to powered field devices shall be as indicated in the datasheet.
Power over Ethernet Delivered to Field Devicesselect
Not provided
IEEE 802.3af Type 1
IEEE 802.3at Type 2
IEEE 802.3bt Type 3
IEEE 802.3bt Type 4
5.4.7 Active network devices shall be powered from the backed-up control power source that serves the controllers they connect, in accordance with Uninterruptible Power Supply SystemsUninterruptible Power Supply SystemsResolves to the current adopted revision.sync/uninterruptible-power-supply-systems where a UPS serves that source.
NOTE A network that drops while the controllers ride through a power disturbance leaves every controller running blind and every operator screen frozen, which is the outcome a backed-up controller supply was bought to prevent. (5.4.8)

6 Network Architecture

6.1 Reference Model and Level Assignment

6.1.1 The network shall be organized on the Purdue reference model as described in ANSI/ISA-95.00.01, with every device assigned to a level: Level 0 for field instruments and final elements, Level 1 for controllers and I/O, Level 2 for supervisory control and local operator interface, Level 3 for site operations, the historian, and engineering workstations, and Level 4 for the enterprise.
6.1.2 The level of every device shall be shown on the network architecture drawing.
NOTE Trust decreases and consequence increases moving down the levels, so the model places every control on the path between levels and gives the network a place to enforce it; a device that has no assigned level has no assigned trust and is the device an attacker looks for. (6.1.3)

6.2 OT and Enterprise Boundary

6.2.1 The enforcement architecture at the boundary between the OT network and the enterprise network shall be as indicated in the datasheet.
OT and Enterprise Boundary Enforcementselect
Single firewall with a DMZ interface
Two firewalls in series with the DMZ between them
Two firewalls in series from different manufacturers
Unidirectional gateway
No connection to the enterprise network
6.2.2 The services hosted in the demilitarized zone shall be as indicated in the datasheet.
Services Hosted in the DMZcheckbox
☐ Historian replica serving enterprise clients
☐ Remote access jump host
☐ Patch and antivirus update relay
☐ File transfer relay
☐ Time relay
☐ Domain services replica
☐ None
6.2.3 No connection shall be initiated from an enterprise host directly to a device on the OT network, and every exchange between the two shall terminate on a service in the DMZ.
6.2.4 Where a unidirectional gateway is selected, data shall flow only from the OT network toward the enterprise, and no return path shall exist through the gateway.
6.2.5 Where two firewalls in series are selected, the OT-side firewall shall be administered from the OT network and the enterprise-side firewall from the enterprise network, so that no single administrative credential opens both.
NOTE A brokered DMZ lets enterprise users read plant data from a replica without ever reaching the network the replica came from, and the replica is the only host both sides talk to; a unidirectional gateway removes even that host from the attack surface at the cost of any capability that needs a reply, which rules out remote support and patch delivery through it. (6.2.6)
NOTE Where the boundary provides no connection to the enterprise network, the DMZ services field records the services that are not provided, and the remote access, patch relay, and time relay provisions of this standard that depend on the boundary do not apply. (6.2.7)

6.3 Zones and Conduits

6.3.1 The network shall be partitioned into security zones and conduits in accordance with ISA/IEC 62443-3-2, with each zone grouping assets that share security requirements and each conduit carrying the controlled traffic between two zones.
6.3.2 The target security level of the control zones shall be as indicated in the datasheet.
Target Security Level for Control Zonesrange
1234
Derived — the documented risk assessment performed for each zone under ISA/IEC 62443-3-2 (by default)
6.3.3 The network controls on each zone and conduit shall satisfy the system requirements of ISA/IEC 62443-3-3 for the target security level assigned to it.
6.3.4 Traffic between zones shall pass only through a conduit whose enforcement device permits it, and traffic within a zone shall not be required to leave the zone.
NOTE The target level is an output of the risk assessment rather than an input to it: the assessment weighs the consequence of a compromise in each zone against the capability of the threat the Owner chooses to defend against, and the level follows from that comparison, so two assessors given the same consequences and the same threat arrive at the same number. (6.3.5)
NOTE Where the facility is a public water or wastewater system, the Owner's security practices under AWWA G430 and any applicable regulatory guidance form part of the inputs to the risk assessment. (6.3.6)

6.4 Segmentation Within the OT Network

6.4.1 The method by which zones are separated within the OT network shall be as indicated in the datasheet.
Zone Segmentation Methodselect
VLANs on shared managed switches
Physically separate switches for each zone
Physically separate switches at zone boundaries with VLANs within each
6.4.2 The device that enforces the conduit rules between zones inside the OT network shall be as indicated in the datasheet.
Conduit Enforcement Device Between OT Zonesselect
Stateful industrial firewall
Stateful industrial firewall with industrial protocol inspection
Layer 3 switch with access control lists
Router with access control lists
6.4.3 The conduit rule set shall deny by default and shall permit only the protocols, source and destination pairs, and ports listed for that conduit in the zone and conduit register.
6.4.4 Traffic between VLANs shall be routed and filtered by the conduit enforcement device and shall not be bridged.
6.4.5 Broadcast and multicast traffic shall be confined to the zone that originates it, and multicast groups used by the control protocol shall be pruned by IGMP snooping so that a producer's traffic reaches only its consumers.
NOTE A VLAN separates zones on a shared switch fabric and costs one switch per location; physically separate switches remove the fabric itself from the boundary, so a misconfigured trunk cannot join two zones, at the cost of a switch per zone per location. Protocol inspection in the enforcement device examines the industrial protocol inside the packet and can reject a write to a controller on a conduit that permits reads, which an address and port rule cannot distinguish. (6.4.6)
6.4.7 The address assignment method for OT devices shall be as indicated in the datasheet.
Address Assignment for OT Devicesradio
● Static addressing
○ DHCP with reserved leases from a server within the OT network
6.4.8 Every OT device shall hold the address assigned to it in the addressing plan, and no OT device shall obtain an address from a server outside the OT network.

6.5 Remote Access

6.5.1 The provision for interactive remote access into the OT network shall be as indicated in the datasheet.
Remote Access into the OT Networkselect
Not provided
Jump host in the DMZ reached through the enterprise network
Dedicated remote access appliance in the DMZ
Out-of-band cellular gateway to a jump host
6.5.2 Where remote access is provided, every session shall terminate on the DMZ host, shall require multi-factor authentication, and shall reach a control device only through a second, separately authenticated hop from that host.
6.5.3 Where remote access is provided, an operator on site shall be able to disable it, and the state of the remote access path shall be annunciated to the supervisory system.

7 Industrial Protocols

7.1 Ethernet Control Protocol

7.1.1 The primary control protocol on the Ethernet network shall be as indicated in the datasheet.
Primary Ethernet Control Protocolselect
EtherNet/IP
PROFINET
Modbus TCP
EtherCAT
CC-Link IE
Derived — the native network protocol of the controller platform furnished under the programmable logic controllers standard (by default)
7.1.2 The secondary Ethernet protocols permitted within control zones for the integration of devices that do not speak the primary protocol shall be as indicated in the datasheet.
Secondary Ethernet Protocols Permitted in Control Zonescheckbox
☐ Modbus TCP
☐ EtherNet/IP
☐ PROFINET
☐ OPC UA
☐ None
NOTE The primary control protocol follows from the controller rather than from a network preference: each controller family carries one protocol natively, and choosing a different one on the network means a gateway in every I/O path. (7.1.3)
NOTE EtherNet/IP carries the Common Industrial Protocol over standard Ethernet and multicasts its cyclic I/O; PROFINET provides a real-time class that bypasses the IP stack and an isochronous class for motion; Modbus TCP is a register-read protocol with no cyclic producer model, which is what makes it simple to implement and unsuitable as the sole transport for time-critical I/O. (7.1.4)
7.1.5 A protocol not selected as primary or permitted as secondary shall not be placed on a control zone, and a device that speaks only such a protocol shall be connected through a gateway at a defined point shown on the architecture drawing.

7.2 Serial Field Protocols

7.2.1 The serial field protocols present on the project shall be as indicated in the datasheet.
Serial Field Protocols Presentcheckbox
☐ Modbus RTU over RS-485
☐ PROFIBUS DP
☐ PROFIBUS PA
☐ FOUNDATION Fieldbus H1
☐ DeviceNet
☐ None
7.2.2 Each serial segment shall be brought onto the Ethernet network through a gateway at a defined point, and a serial trunk shall not be extended between buildings or between panels in different zones.
7.2.3 An RS-485 multidrop segment shall be wired as a single daisy chain with no stubs or star branches, terminated at both physical ends with the characteristic impedance of the cable, and biased at one point in accordance with the device requirements.
7.2.4 A serial segment that leaves a panel shall be galvanically isolated and surge protected at the panel boundary, coordinated with Surge Protective DevicesSurge Protective DevicesResolves to the current adopted revision.sync/surge-protective-devices.
NOTE A star-wired or unterminated RS-485 segment reflects every transition back onto the line, and the faults it produces come and go with temperature and cable length, which is why they are found by inspection of the topology rather than by any protocol diagnostic. (7.2.5)

7.3 Cross-Domain Integration Protocol

7.3.1 The protocol used to move structured data from the control layer to the historian, the DMZ services, and enterprise systems shall be as indicated in the datasheet.
Cross-Domain Integration Protocolselect
OPC UA
MQTT with Sparkplug B payloads
Historian-native replication
Modbus TCP through a broker
7.3.2 Cross-domain connections shall use the authentication, signing, and encryption the selected protocol provides, and shall cross the OT and enterprise boundary only through a DMZ service.
NOTE OPC UA carries a typed information model and a security model of its own and is served from the control side on request; MQTT with Sparkplug B publishes state changes to a broker in the DMZ so that the control side never accepts an inbound connection, which suits a unidirectional boundary and a low-bandwidth telemetry bearer alike. Neither is a real-time control protocol, and neither replaces the primary control protocol on a control zone. (7.3.3)

8 Transmission Media

8.1 Media by Segment Class

8.1.1 The media for backbone segments between switches shall be as indicated in the datasheet.
Backbone Segment Mediaselect
Single-mode optical fiber
Multimode optical fiber
Balanced twisted-pair copper
8.1.2 The media for device-level segments between an access switch and a controller, I/O adapter, or networked instrument shall be as indicated in the datasheet.
Device-Level Segment Mediaselect
Balanced twisted-pair copper
Multimode optical fiber
Single-pair Ethernet 10BASE-T1L
8.1.3 The media for any segment that passes between separately grounded structures shall be as indicated in the datasheet.
Media for Segments Between Separately Grounded Structuresradio
● Optical fiber
○ Balanced twisted-pair copper with isolating surge protection at both ends
8.1.4 A balanced twisted-pair copper segment shall not exceed the 100 m channel length of ANSI/TIA-568.
8.1.5 Where copper is selected between separately grounded structures, the surge protection at each end shall be bonded to the local grounding electrode system and shall be rated for the data rate of the segment.
NOTE Copper is limited by the 100 m channel and by the noise it picks up along its route, so its reach and its immunity both fall as the route passes medium-voltage gear, drives, or long parallel power runs; fiber has no distance limit at plant scale and no coupling to any of those, so the question a segment asks is whether its route stays inside those copper limits. (8.1.7)

8.2 Copper Cabling

8.2.1 The performance category of balanced twisted-pair copper cabling shall be as indicated in the datasheet.
Balanced Twisted-Pair Copper Categoryselect
Category 5e
Category 6
Category 6A
8.2.2 The shielding construction of balanced twisted-pair copper cabling shall be as indicated in the datasheet.
Copper Cable Shielding Constructionselect
Unshielded
Overall foil shield
Overall braid shield with foil-shielded pairs
NOTE Category 5e and Category 6 both carry 1 Gb/s over the full channel; Category 6A is what carries 10 Gb/s over the full channel and carries 2.5 Gb/s and 5 Gb/s with margin, so the category follows from the backbone data rate where copper is used for the backbone. (8.2.3)
NOTE A shield lowers the noise coupled into the pairs where the route runs near drives and switching power, at the cost of a bond at every termination that has to be made consistently or the shield becomes an antenna; an unshielded cable in a quiet route has no bond to get wrong. (8.2.4)
8.2.5 Copper connecting hardware shall be rated for the category of the cable it terminates.

8.3 Optical Fiber Cabling

8.3.1 The grade of multimode optical fiber shall be as indicated in the datasheet.
Multimode Fiber Gradeselect
OM3
OM4
OM5
8.3.2 Single-mode optical fiber shall be OS2 in accordance with ANSI/TIA-568.
8.3.3 The optical fiber connector type shall be as indicated in the datasheet.
Optical Fiber Connector Typeselect
LC
SC
ST
8.3.5 Every fiber strand shall be terminated at both ends on connecting hardware in a patch panel or enclosure, and an unterminated strand shall be capped.

8.4 Backbone Data Rate

8.4.1 The data rate of backbone segments between switches shall be as indicated in the datasheet.
Backbone Segment Data Raterange
Gb/s
0.112.510
8.4.2 Every backbone segment shall be furnished with transceivers and connecting hardware rated for the selected rate over the installed length.

8.5 Cable Installation

8.5.1 Network cable routing and segment lengths shall be as indicated on the cable-route drawings.
8.5.2 Network cabling shall be separated from power conductors by the distance the cable manufacturer publishes for the category and shielding furnished, and in no case by less than NFPA 70 requires.
8.5.3 Network cabling shall be installed within the bend radius and pulling tension published for the cable, and a cable that has been kinked or over-tensioned shall be replaced rather than repaired.
8.5.4 Network cabling that passes through a fire-rated assembly shall be firestopped in accordance with FirestoppingFirestoppingResolves to the current adopted revision.sync/firestopping.

9 Switches and Boundary Devices

9.1 Switch Classes

9.1.1 The management class of switches at the core and distribution layers shall be as indicated in the datasheet.
Core and Distribution Switch Classradio
○ Layer 2 managed
○ Layer 3 managed
9.1.2 The management class of access switches serving controllers, I/O, and field devices shall be as indicated in the datasheet.
Access Switch Classradio
● Layer 2 managed
○ Lightly managed
○ Unmanaged
9.1.3 An unmanaged switch shall not be placed on a segment that participates in a redundancy ring or that spans a zone boundary, because it cannot participate in the ring protocol and cannot enforce the boundary.
9.1.4 A lightly managed switch shall not be placed on a segment that participates in a redundancy ring unless it supports the selected redundancy protocol, and shall not be placed on a segment that spans a zone boundary.
NOTE A Layer 3 core routes between VLANs in the switch itself, which keeps inter-zone traffic off the firewall and moves the rule set into access control lists; a Layer 2 core hands every inter-VLAN packet to the firewall, which keeps one rule set in one place at the cost of the firewall's throughput. A lightly managed switch offers VLAN membership and diagnostics without the full management interface, and an unmanaged switch offers neither, which is why the latter two are confined to the edge. (9.1.6)

9.2 Required Switch Capabilities

9.2.1 Managed switches shall provide the capabilities indicated in the datasheet.
Managed Switch Capabilities Requiredcheckbox
☑ IEEE 802.1Q VLAN tagging and trunking
☑ The selected redundancy protocol
☑ IGMP snooping and querier
☑ IEEE 802.1p traffic prioritization
☑ Port security by MAC address
☑ SNMPv3 management
☑ IEEE 802.1AB link layer discovery
☑ Port mirroring
☐ Small form-factor pluggable transceiver ports
☐ Relay contact output on fault
☐ Local event log
9.2.2 Each switch shall retain not fewer than the number of spare ports indicated in the datasheet after every scheduled connection to it is made.
Spare Ports per Switch After Commissioningrange
ports
1248

9.3 Media Converters and Protocol Gateways

9.3.2 An unmanaged media converter shall be used only on a point-to-point segment that neither participates in a ring nor spans a zone boundary.
9.3.3 A protocol gateway shall be placed at a defined point shown on the architecture drawing, shall be assigned to a zone, and shall be hardened as an active network device.

10 Redundancy and Determinism

10.1 Backbone Topology

10.1.1 The backbone topology shall be as indicated in the datasheet.
Backbone Topologyselect
Single ring
Coupled rings
Redundant star
Dual parallel networks
Non-redundant
10.1.2 Where a redundant topology is selected, a single cable or switch failure shall not separate any controller from the supervisory layer or from its remote I/O.
10.1.3 Where a non-redundant topology is selected, the single points of failure shall be identified on the architecture drawing and accepted in writing by the Owner before installation.

10.2 Redundancy Protocol

10.2.1 The redundancy protocol shall be as indicated in the datasheet.
Redundancy Protocolselect
Rapid Spanning Tree Protocol
Multiple Spanning Tree Protocol
Media Redundancy Protocol
Device Level Ring
Parallel Redundancy Protocol
High-Availability Seamless Redundancy
Switch manufacturer ring protocol
None
10.2.2 The maximum time within which the network shall restore communication after a single cable or switch failure shall be as indicated in the datasheet.
Maximum Recovery Time After a Single Failurerange
ms
3305020050020006000
10.2.3 The selected protocol shall be capable of the selected recovery time at the number of switches in the ring, and the recovery time shall be demonstrated during commissioning.
10.2.4 A ring shall have exactly one ring manager, its identity shall be recorded on the architecture drawing, and every other switch in the ring shall be configured as a ring client.
10.2.5 Two redundancy protocols shall not be run on one ring, and a ring shall not be closed until every switch in it has been configured for the selected protocol.
NOTE The protocols recover on different time scales: spanning tree reconverges in seconds, a media redundancy ring in tens to a few hundred milliseconds depending on the ring size and the profile, a device level ring in a few milliseconds, and the parallel and seamless protocols in zero time because every frame is already sent on both paths. The recovery time the process tolerates is what selects the protocol, and a controller whose I/O connection times out faster than the ring recovers faults on every failover. (10.2.6)
NOTE The parallel and seamless protocols double every frame and every port, which costs a second network interface on every attached device or a redundancy box in front of it; the ring protocols cost nothing at the device and one blocked port at the ring manager. (10.2.7)

10.3 Traffic Prioritization and Loading

10.3.1 Control traffic shall be marked and prioritized above non-control traffic on every shared segment, using IEEE 802.1p priority and, where the selected protocol provides one, its real-time class.
10.3.2 The maximum utilization of any control segment under worst-case traffic shall not exceed the value indicated in the datasheet, and the utilization shall be measured during commissioning.
Maximum Control Segment Utilizationrange
%
10203040506080
NOTE Latency on a switched network is bounded only while the queues stay short, and a historian backfill or a file copy fills them; prioritization keeps control frames ahead of the bulk traffic, and a utilization ceiling keeps the queues from filling with control frames alone. (10.3.3)

11 Time Synchronization

11.1 Time Reference

11.1.1 The time reference for the OT network shall be as indicated in the datasheet.
OT Network Time Referenceselect
GNSS-disciplined grandmaster clock on site
Site time server disciplined by a GNSS receiver
Site time server on a free-running oscillator
Time relayed from the enterprise network through a DMZ time relay
11.1.2 Every device on the OT network that keeps time shall take it from the selected reference, and no OT device shall query a time server outside the OT network directly.
11.1.3 Where time is relayed from the enterprise network, the DMZ time relay shall query the enterprise source and serve the OT network, and the conduit rule shall permit time traffic in that direction alone.
NOTE A free-running site reference keeps every device on the OT network agreeing with each other while drifting together from true time; a GNSS reference holds the network to true time, which is what lets an event on the plant network be correlated with a utility outage or a security log from outside. A relayed enterprise source depends on the boundary being up and on the enterprise clock being trustworthy, and it is the one reference that an attacker on the enterprise side can move. (11.1.4)

11.2 Time Distribution Protocol

11.2.1 The protocol that distributes time to controllers, servers, workstations, and switches shall be as indicated in the datasheet.
General Time Distribution Protocolradio
● NTP
○ SNTP
○ PTP
11.2.2 The sub-microsecond time distribution provided on segments that require it shall be as indicated in the datasheet.
Sub-Microsecond Time Distributionselect
Not required
PTP default profile
PTP power profile IEEE C37.238
IEEE 802.1AS
11.2.3 The time agreement to be maintained between every pair of timestamping devices shall be as indicated in the datasheet.
Required Time Agreement Between Devicesrange
ms
0.0010.010.11101001000
Derived — the finest sequence-of-events resolution required by the connected controllers and by the supervisory alarm and event journal (by default)
11.2.4 Where PTP is selected on a segment, every switch on that segment shall be a PTP-aware boundary or transparent clock.
NOTE NTP holds devices within a few milliseconds over a routed network, which resolves the order of alarms and events on a supervisory journal; PTP with hardware timestamping holds them within a microsecond, which is what a sequence-of-events recorder, a synchrophasor, or a motion axis needs, and it needs every switch in the path to participate. (11.2.5)
NOTE Two devices that disagree on the time produce a journal in which the effect is logged before the cause, and an upset reconstructed from that journal points at the wrong equipment. (11.2.6)

12 Remote Site Telemetry

12.1 Telemetry Applicability

12.1.1 The remote sites served by wide-area telemetry rather than plant cabling shall be those indicated on the system architecture drawings.
NOTE A remote pump station, lift station, well, tank, or metering site is separated from the plant by distance, by a public right of way, and by a bearer that is slower and less reliable than a plant cable, and the provisions in this section exist so that the site keeps running when that bearer is down. (12.1.2)
NOTE Where the project has no remote sites, the telemetry fields in this section are recorded as not applicable and this section imposes no requirement. (12.1.3)

12.2 Telemetry Bearer

12.2.1 The primary telemetry bearer serving remote sites shall be as indicated in the datasheet.
Primary Telemetry Bearerselect
Licensed narrowband radio
Unlicensed spread-spectrum radio
Cellular
Leased line
Owner-furnished fiber
Satellite
Not applicable
12.2.2 The backup telemetry bearer serving remote sites shall be as indicated in the datasheet.
Backup Telemetry Bearerselect
None
Licensed narrowband radio
Unlicensed spread-spectrum radio
Cellular
Satellite
Not applicable
12.2.3 Where a backup bearer is selected, the remote site equipment shall fail over to it without operator action and shall return to the primary bearer when the primary is restored, and both transitions shall be annunciated to the supervisory system.
12.2.4 Licensed radio shall operate under a license held by the Owner in accordance with 47 CFR Part 90, and unlicensed radio shall comply with 47 CFR Part 15.

12.3 Telemetry Protocol and Polling

12.3.1 The telemetry protocol between the supervisory system and remote sites shall be as indicated in the datasheet.
Telemetry Protocolselect
DNP3
IEC 60870-5-104
Modbus TCP
MQTT with Sparkplug B payloads
OPC UA
Controller manufacturer native protocol
Not applicable
12.3.2 The data collection strategy over the telemetry bearer shall be as indicated in the datasheet.
Telemetry Data Collection Strategyradio
○ Polled at a fixed interval
○ Report by exception with a periodic integrity poll
○ Unsolicited reporting
○ Not applicable
12.3.3 The protection applied to telemetry traffic on the bearer shall be as indicated in the datasheet.
Telemetry Link Protectioncheckbox
☐ IPsec virtual private network
☐ Transport layer security
☐ DNP3 secure authentication
☐ Radio link encryption
☐ None on a private bearer
☐ Not applicable
12.3.4 Telemetry traffic that crosses a public carrier network shall be encrypted and authenticated end to end.
12.3.5 The polling interval and the exception deadbands shall be set so that the bearer is not saturated at the worst-case event rate.
NOTE Report by exception sends a value when it changes and a full refresh on a slow cycle, which fits the bandwidth of a narrowband bearer; fixed-interval polling sends everything every time, which is simple and predictable and saturates a slow bearer as the point count grows. DNP3 and IEC 60870-5-104 carry timestamped events and buffered reporting in the protocol itself, and Modbus carries neither, so a Modbus telemetry system reconstructs event time from the poll time. (12.3.8)

13 OT Cybersecurity Baseline

13.1 Security Program Basis

13.1.1 The hardening, account, patch, logging, and backup provisions of this section shall be implemented on every active network device and shall be recorded in the cybersecurity hardening plan.
NOTE The provisions of this section are the network baseline within the zone and conduit architecture; the Owner's security program under ISA/IEC 62443-2-1 governs above this baseline, and the integration-seam responsibilities of the system integrator are governed by Control Systems IntegrationControl Systems Integration and TestingResolves to the current adopted revision.sync/control-systems-integration. (13.1.2)

13.2 Device Hardening

13.2.1 Every active network device shall be hardened before it is placed in service by the measures indicated in the datasheet.
Device Hardening Measurescheckbox
☑ Default credentials removed
☑ Unused physical ports administratively disabled
☐ Port security on access ports
☑ Unused logical services disabled
☑ Unencrypted management protocols disabled
☑ Management access restricted to the management network
☑ Firmware at a version tested for the project
☑ Configuration backed up after commissioning
☐ Physical console port password protected
13.2.2 Where port security is selected, each access port shall be limited to the MAC address of the device scheduled for it, and the port shall shut down and raise an alarm on a violation.
13.2.3 Where disabling of unencrypted management protocols is selected, Telnet, unencrypted HTTP, and SNMP versions 1 and 2 shall be disabled on every device that supports an encrypted replacement, and management of that device shall be performed over the encrypted replacement.
NOTE A default credential on a switch is published in the manual, and an open management port on the control VLAN is reachable from every device on it, so an unhardened switch is a foothold that no firewall in front of the zone addresses. (13.2.4)

13.3 Account Management

13.3.1 The account model on active network devices shall be as indicated in the datasheet.
Account Model on Network Devicesradio
○ Individually named local accounts
○ Centrally authenticated named accounts with a local emergency account
○ Role-based shared local accounts
13.3.2 Each account shall carry the least privilege its role requires, and administrative privilege shall not be granted to an account used for routine monitoring.
13.3.3 Where restriction of management access is selected, the management interface of each network device shall be reachable only from the management VLAN and from the engineering hosts listed in the hardening plan.
13.3.4 Where a local emergency account is provided, its credential shall be sealed, stored under the Owner's control, and changed after each use.
NOTE A shared account produces a log that says an administrator did something and cannot say which one; a named account produces a log that can be acted on, and central authentication lets a departing employee's access be removed in one place rather than on every switch. Central authentication also depends on the authentication server being reachable, which is what the local emergency account is for. (13.3.5)

13.4 Patch Management

13.4.1 The qualification a firmware or software update shall pass before it is applied to a production device shall be as indicated in the datasheet.
Patch Qualification Required Before Applicationcheckbox
☑ Validated by the control system manufacturer for the installed platform
☐ Tested on a non-production replica of the network
☐ Tested on a spare device of the same model
13.4.2 The handling of an update that closes a vulnerability rated critical shall be as indicated in the datasheet.
Security-Critical Update Handlingradio
○ Applied at the next planned maintenance window
○ Applied in an expedited window after qualification
13.4.3 Updates other than security-critical updates shall be applied during planned maintenance windows agreed with the Owner's operations staff.
13.4.4 No update shall be applied to a production device that has not passed the selected qualification.
NOTE An untested firmware update on a ring switch can change the ring protocol's behavior and take the ring down, which is a process outage caused by a security measure; the qualification step is what keeps the cure from being the disease. (13.4.5)

13.5 Monitoring and Logging

13.5.1 Every active network device shall send its security and operational events to a central log collector using the transport indicated in the datasheet.
Network Device Log Transportcheckbox
☑ Syslog
☑ SNMP traps
☐ Flow records
13.5.2 The location of the central log collector shall be as indicated in the datasheet.
Central Log Collector Locationradio
○ Within the OT network
○ In the DMZ
13.5.3 The period for which network device logs shall be retained on the collector shall be as indicated in the datasheet.
Network Log Retention Periodrange
days
3090180365730
13.5.4 The network monitoring functions provided shall be as indicated in the datasheet.
Network Monitoring Functionscheckbox
☑ Link and port status to the supervisory system
☑ Redundancy state to the supervisory system
☐ Passive asset discovery
☐ Anomaly detection on inter-zone traffic
☐ Switch fault relay contact to the controller
13.5.5 Logged events shall carry the synchronized time of the OT network so that events from different devices can be placed in order.
NOTE A ring that has lost one segment is still running, and no one knows until the second segment fails and the plant stops; reporting the redundancy state to the operator is what turns a silent single failure into a work order. (13.5.6)

13.6 Configuration Backup and Recovery

13.6.1 The method by which device configurations are backed up shall be as indicated in the datasheet.
Configuration Backup Methodradio
○ Manual export after each configuration change
○ Automated scheduled export to a repository within the OT network
13.6.2 The as-commissioned configuration of every active network device shall be backed up, and the backup shall be updated whenever the configuration is changed.
13.6.3 A written restore procedure shall be provided for each device class, and it shall be demonstrated during commissioning by restoring one device of each class from its backup.
13.6.4 Backups shall be stored where a failure of the device, the network, or the host that holds them does not take the backup with it.

14 Testing and Commissioning

Copper Link Test Levelradio
○ Permanent link certification to the installed category
○ Channel certification to the installed category
○ Wire map and length verification
Optical Fiber Link Test Levelradio
○ Tier 1 insertion loss
○ Tier 2 insertion loss with OTDR trace
14.1.4 Cable test records shall be submitted and accepted before the network is energized for functional testing.

14.2 Network Functional Testing

14.2.1 The functional tests performed during commissioning shall be as indicated in the datasheet.
Network Commissioning Testscheckbox
☑ Addressing and VLAN membership of every device
☑ End-to-end communication between every controller and the supervisory layer
☑ Conduit rule set verified against the zone and conduit register
☑ Failover by opening each ring segment and each redundant link in turn
☑ Recovery time measured at each failover
☑ Time agreement measured between timestamping devices
☐ Utilization measured on each control segment under worst-case traffic
☐ Telemetry failover and store-and-forward at each remote site
☑ Restore of one device of each class from backup
14.2.2 Each failover test shall confirm that no controller lost communication with its I/O or with the supervisory layer for longer than the selected recovery time.
14.2.3 A test that fails shall be corrected and repeated, and the cost of the correction and of every repeated test shall be borne by the Contractor.

14.3 Security Acceptance

14.3.1 The method by which the as-built network is verified against the cybersecurity hardening plan shall be as indicated in the datasheet.
Security Acceptance Methodcheckbox
☑ Configuration review of every device against the hardening plan
☐ Authenticated vulnerability scan of every active network device
☐ Passive traffic capture reviewed against the conduit rule set
☐ Penetration test of the OT and enterprise boundary
14.3.2 Security acceptance shall confirm that no default credential remains on any device, that every hardening measure selected in the datasheet has been applied to every device, and that no path between zones exists outside the conduit register.
14.3.3 Where remote access is provided, the acceptance shall demonstrate that a session terminates on the DMZ host, that multi-factor authentication is enforced, and that no route from the DMZ host to a control device exists without the second authenticated hop.
NOTE An active scan sends traffic to every device it tests, and some OT devices fault when scanned, so an active scan on a live network is performed only during a planned outage and with the Owner's operations staff present. (14.3.4)

15 Installation

15.1 Device Mounting and Power Connection

15.1.1 Active network devices shall be mounted on DIN rail or in a rack within the panel or cabinet assigned to them, with the clearance the device manufacturer publishes for cooling and for cable bend radius.
15.1.2 Where redundant power inputs are furnished, each input shall be wired to its separate supply and each shall be individually fused or protected.
15.1.3 A network device shall not be mounted directly above a heat-producing component in the same enclosure unless the temperature at the device with that component operating remains within the device's operating temperature rating.

15.2 Shield Bonding and Grounding

15.2.1 The bonding of the shield on shielded copper network cable shall be as indicated in the datasheet.
Shielded Copper Cable Shield Bondingradio
○ Bonded at both ends
○ Bonded at one end at the panel
15.2.2 The selected shield bonding shall be applied consistently on every shielded segment, and the shield shall be bonded to the panel bonding point in accordance with Grounding And BondingGrounding and Bonding for Electrical SystemsResolves to the current adopted revision.sync/grounding-and-bonding.
15.2.3 Network equipment, racks, and cabinets shall be bonded in accordance with Grounding And BondingGrounding and Bonding for Electrical SystemsResolves to the current adopted revision.sync/grounding-and-bonding.
NOTE A shield bonded at both ends shunts high-frequency noise to ground at each end and is what an Ethernet cable's shield is designed for, and it carries circulating current where the two ends sit at different potentials; a shield bonded at one end carries no circulating current and shunts no noise at the far end. Where both ends are inside one bonded panel lineup the potentials match and both-end bonding costs nothing; where the ends are far apart on one structure the choice weighs the noise against the circulating current, and where they are on separate structures the media selection has already settled it. (15.2.4)

15.3 Identification

15.3.1 Every active network device, every port, and both ends of every network cable shall be labeled to match the as-built architecture drawings and the addressing plan.
15.3.2 The content of each device and cable label shall be as indicated in the datasheet.
Network Device and Cable Label Contentcheckbox
☑ Device or cable identifier
☑ Zone
☑ IP address
☐ VLAN
☑ Far-end device and port
15.3.3 Label materials and methods shall comply with Electrical IdentificationWiring System IdentificationResolves to the current adopted revision.sync/electrical-identification.

16 Delivery, Storage, and Handling

16.1 Active network devices shall be delivered in the manufacturer's packaging and protected from moisture, dust, electrostatic discharge, and impact until installed.
16.2 Optical fiber cable shall be delivered on reels with both ends sealed, and shall be stored and handled within the minimum bend radius and maximum pulling tension published for the cable.
16.3 Devices and cable stored on site before installation shall be kept in a dry, enclosed space within the storage temperature range published for the product.
16.4 Optical connectors shall be kept capped until the moment of connection, and a connector that has been exposed shall be cleaned and inspected before it is mated.

17 Warranty

17.1 The manufacturer shall warrant each active network device against defects in materials and workmanship for the period indicated in the datasheet, measured from the date of substantial completion.
Network Device Manufacturer Warranty Periodrange
years
1235
17.2 The integrator shall warrant the network configuration, including addressing, segmentation, redundancy, time distribution, telemetry, and hardening, for the period indicated in the datasheet, measured from the date of substantial completion.
Network Configuration Warranty Periodrange
years
123
17.3 Where the contract documents state a longer warranty period than the datasheet, the longer period shall govern.
17.4 A device that fails within its warranty period shall be replaced with the same model or a model the manufacturer designates as its successor, and the replacement shall be restored from the configuration backup by the integrator at no cost to the Owner.
17.5 Work performed under this warranty shall itself be warranted for a full new term equal to the original period measured from the date the correction is completed, or for the remainder of the original period, whichever ends later.
NOTE Manufacturers of industrial network hardware publish warranty terms from one year to five, and the term the Owner buys is a matter of the device count and the cost of a spare against the cost of the longer term, which is why this field asserts no norm. (17.6)

18 Spare Parts

18.1 The Contractor shall deliver the spare parts indicated in the datasheet to the Owner before the network is accepted, and shall obtain a signed receipt for them.
Spare Parts to Be Furnishedcheckbox
☑ One managed switch of each model and port configuration installed
☐ One media converter of each model installed
☑ Two transceivers of each type installed
☑ One power supply of each model serving network devices
☐ One protocol gateway of each model installed
☐ One telemetry radio or cellular gateway of each model installed
☑ Fiber and copper patch cords of each type and length installed
18.2 Spare devices shall be the same model as the installed devices, shall carry a firmware version compatible with the installed configuration, and shall be delivered in their original unopened packaging.
18.3 Spare devices shall be labeled with the model, the firmware version, and the installed device classes they are able to replace.