Amendment_0004_Revised_SPEC_25_10_10.pdf

Building 81 Renovation JUNE 2016 Defense Distribution Center Susquehanna, New Cumberland, PA

AMENDMENT 004

AMENDMENT 004

DATE: September 2, 2016

RE: Building 81 Renovation Defense Distribution Center Susquehanna, New Cumberland, PA

FROM: CROMWELL ARCHITECT ENGINEERS, INC.

101 S. Spring Street Little Rock, Arkansas 72201

TO: BIDDERS OF RECORD

This Amendment forms a part of the Contract Documents and modifies the original Bidding Documents dated June 3, 2016, as noted below.

CHANGES TO SPECIFICATIONS:

1: Insert (this) Amendment 004 issued with this Amendment.

2: Replace the Project Table of Contents with revised Table of Contents issued with this Amendment

3: Replace Section 25 10 10 - UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END AND INTEGRATION issued with this Amendment.

CHANGES TO DRAWINGS:

4: Insert the attached revised and/or new Drawings issued with this Amendment:

Issue Revision Sheet Title/Description Date No.

MECHANICAL

M-103 FIRST LEVEL HVAC PLAN-AREA A 08/16/2016 1

M-104 FIRST LEVEL HVAC PLAN-AREA B 08/16/2016 1

M-105 SECOND LEVEL HVAC PLAN-AREA A 08/16/2016 1

M-106 SECOND LEVEL HVAC PLAN-AREA B 08/16/2016 1

M-604 HVAC SCHEDULES 08/16/2016 1

M-701 HVAC CONTROLS 08/16/2016 1

M-705 HVAC CONTROLS 08/16/2016 1

MD-103 FIRST LEVEL DEMOLITION PLAN - AREA A 08/16/2016 1

MD-104 FIRST LEVEL DEMOLITION PLAN - AREA B 08/16/2016 1

MD-105 SECOND LEVEL DEMOLITION PLAN - AREA A 08/16/2016 1

MD-106 SECOND LEVEL DEMOLITION PLAN - AREA B 08/16/2016 1

END OF SECTION

This page was intentionally left blank for duplex printing.

PROJECT TABLE OF CONTENTS

DIVISION 00 - PROCUREMENT AND CONTRACTING REQUIREMENTS

00 31 00 AVAILABLE PROJECT INFORMATION

00 31 02 LEED CHECKLIST

00 43 22 UNIT PRICES

DIVISION 01 - GENERAL REQUIREMENTS

01 11 00 SUMMARY OF WORK

01 14 00 WORK RESTRICTIONS

01 32 01.00 10 PROJECT SCHEDULE

01 33 00 SUBMITTAL PROCEDURES

01 35 26 GOVERNMENTAL SAFETY REQUIREMENTS

01 35 40.00 20 ENVIRONMENTAL MANAGEMENT

01 42 00 SOURCES FOR REFERENCE PUBLICATIONS

01 45 00.10 20 QUALITY CONTROL FOR MINOR CONSTRUCTION

01 50 00 TEMPORARY CONSTRUCTION FACILITIES AND CONTROLS

01 57 19.00 20 TEMPORARY ENVIRONMENTAL CONTROLS

01 57 20.00 10 ENVIRONMENTAL PROTECTION

01 62 35 RECYCLED / RECOVERED MATERIALS

01 74 19 CONSTRUCTION AND DEMOLITION WASTE MANAGEMENT

01 78 00 CLOSEOUT SUBMITTALS

01 78 23 OPERATION AND MAINTENANCE DATA

DIVISION 02 - EXISTING CONDITIONS

02 41 00 DEMOLITION

02 82 14.00 10 ASBESTOS HAZARD CONTROL ACTIVITIES

02 84 16 HANDLING OF LIGHTING BALLASTS AND LAMPS CONTAINING PCBs

AND MERCURY

02 85 00.00 20 MOLD REMEDIATION

DIVISION 03 - CONCRETE

03 30 53 MISCELLANEOUS CAST-IN-PLACE CONCRETE

03 45 00 PRECAST ARCHITECTURAL CONCRETE

DIVISION 05 - METALS

05 12 00 STRUCTURAL STEEL

05 30 00 STEEL DECKS

05 50 13 MISCELLANEOUS METAL FABRICATIONS

05 52 00 METAL RAILINGS

DIVISION 06 - WOOD, PLASTICS, AND COMPOSITES

06 10 00 ROUGH CARPENTRY

06 20 00 FINISH CARPENTRY

DIVISION 07 - THERMAL AND MOISTURE PROTECTION

07 13 53 ELASTOMERIC SHEET WATERPROOFING

07 21 16 MINERAL FIBER BLANKET INSULATION

07 22 00 ROOF AND DECK INSULATION

07 24 00 EXTERIOR INSULATION AND FINISH SYSTEMS

07 60 00 FLASHING AND SHEET METAL

07 61 14.00 20 STEEL STANDING SEAM ROOFING

PROJECT TABLE OF CONTENTS Page 1

07 84 00 FIRESTOPPING

07 92 00 JOINT SEALANTS

DIVISION 08 - OPENINGS

08 11 13 STEEL DOORS AND FRAMES

08 11 16 ALUMINUM DOORS AND FRAMES

08 14 00 WOOD DOORS

08 41 13 ALUMINUM-FRAMED ENTRANCES AND STOREFRONTS

08 71 00 DOOR HARDWARE

08 81 00 GLAZING

08 91 00 METAL WALL LOUVERS

DIVISION 09 - FINISHES

09 05 61 COMMON WORK RESULTS FOR FLOORING PREPARATION

09 22 00 SUPPORTS FOR GYPSUM BOARD

09 29 00 GYPSUM BOARD

09 51 00 ACOUSTICAL CEILINGS

09 65 00 RESILIENT FLOORING BASE AND TRANSITIONS

09 68 00 CARPETING

09 90 00 PAINTS AND COATINGS

DIVISION 10 - SPECIALTIES

10 14 10.00 10 MECHANICAL SIGNAGE

10 14 20.00 10 FIRE PROTECTION SYSTEM SIGNAGE

10 44 16 FIRE EXTINGUISHERS

DIVISION 12 - FURNISHINGS

12 21 00 WINDOW BLINDS

12 32 00 MANUFACTURED WOOD CASEWORK

12 59 00 SYSTEMS FURNITURE

DIVISION 21 - FIRE SUPPRESSION

21 13 13.00 10 WET PIPE SPRINKLER SYSTEM, FIRE PROTECTION

DIVISION 22 - PLUMBING

22 00 00 PLUMBING, GENERAL PURPOSE

DIVISION 23 - HEATING, VENTILATING, AND AIR CONDITIONING (HVAC)

23 00 00 AIR SUPPLY, DISTRIBUTION, VENTILATION, AND EXHAUST SYSTEMS

23 05 93 TESTING, ADJUSTING, AND BALANCING FOR HVAC

23 07 00 THERMAL INSULATION FOR MECHANICAL SYSTEMS

23 08 00.00 10 COMMISSIONING OF HVAC SYSTEMS

23 09 00 INSTRUMENTATION AND CONTROL FOR HVAC

23 09 23.01 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER

BUILDING CONTROL SYSTEMS

23 11 25 FACILITY GAS PIPING

23 25 00 CHEMICAL TREATMENT OF WATER FOR MECHANICAL SYSTEMS

23 52 00 HEATING BOILERS

23 64 10 WATER CHILLERS, VAPOR COMPRESSION TYPE

23 64 26 CHILLED, CHILLED-HOT, AND CONDENSER WATER PIPING SYSTEMS

DIVISION 25 - INTEGRATED AUTOMATION

PROJECT TABLE OF CONTENTS Page 2

25 10 10 UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END

AND INTEGRATION

DIVISION 26 - ELECTRICAL

26 00 00.00 20 BASIC ELECTRICAL MATERIALS AND METHODS

26 08 00 APPARATUS INSPECTION AND TESTING

26 12 19.10 THREE-PHASE PAD-MOUNTED TRANSFORMERS

26 20 00 INTERIOR DISTRIBUTION SYSTEM

26 24 13 SWITCHBOARDS

26 28 01.00 10 COORDINATED POWER SYSTEM PROTECTION

26 29 23 VARIABLE FREQUENCY DRIVE SYSTEMS UNDER 600 VOLTS

26 36 00.00 10 AUTOMATIC TRANSFER SWITCH AND BY-PASS/ISOLATION SWITCH

26 51 00 INTERIOR LIGHTING

26 56 00 EXTERIOR LIGHTING

DIVISION 27 - COMMUNICATIONS

27 05 14.00 10 CABLE TELEVISION PREMISES DISTRIBUTION SYSTEM

27 05 29.00 10 PROTECTIVE DISTRIBUTION SYSTEM (PDS) FOR SIPRNET

COMMUNICATION SYSTEMS

27 10 00 BUILDING TELECOMMUNICATIONS CABLING SYSTEM

DIVISION 28 - ELECTRONIC SAFETY AND SECURITY

28 16 01.00 10 SMALL INTRUSION DETECTION SYSTEM

28 20 01.00 10 ELECTRONIC SECURITY SYSTEM

28 31 49 CARBON MONOXIDE DETECTORS

28 31 76 INTERIOR FIRE ALARM AND MASS NOTIFICATION SYSTEM

DIVISION 31 - EARTHWORK

31 00 00 EARTHWORK

31 11 00 CLEARING AND GRUBBING

31 31 16.13 CHEMICAL TERMITE CONTROL

DIVISION 32 - EXTERIOR IMPROVEMENTS

32 05 33 LANDSCAPE ESTABLISHMENT

32 10 00 BITUMINOUS CONCRETE PAVEMENT

32 11 23 AGGREGATE BASE COURSE

32 12 10 BITUMINOUS TACK AND PRIME COATS

32 16 13 CONCRETE SIDEWALKS AND CURBS

32 17 23.00 20 PAVEMENT MARKINGS

32 92 19 SEEDING

DIVISION 33 - UTILITIES

33 11 00 WATER DISTRIBUTION

33 40 00 STORM DRAINAGE UTILITIES

33 46 13 FOUNDATION DRAINAGE SYSTEM

33 71 02 UNDERGROUND ELECTRICAL DISTRIBUTION

-- End of Project Table of Contents --

PROJECT TABLE OF CONTENTS Page 3

AMENDMENT 004

cgtoney Text Box Revised Section 25 10 10 in Amendment 004

This page was intentionally left blank for duplex printing.

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 1 of 50

SECTION 25 10 10

UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END AND INTEGRATION

11/12

Table of Contents

PART 1 GENERAL

1.1 SUMMARY

1.1.1 System Requirements

1.1.2 Symbols, Definition and Abbreviations

1.1.3 System Units and Accuracy

1.1.4 Data Packages/Submittals Requirements

1.2 REFERENCES

1.3 DEFINITIONS

1.3.1 Alarm Generation

1.3.2 Alarm Handling

1.3.3 Alarm Routing

1.3.4 Application Generic Controller (AGC)(LonWorks)

1.3.5 Application Specific Controller (ASC)(LonWorks)

1.3.6 BACnet (BACnet)

1.3.7 BACnet Advanced Application Controller (B-AAC)(BACnet)

1.3.8 BACnet Advanced Operator Workstation (B-AWS)(BACnet)

1.3.9 BACnet Application Specific Controller (B-ASC)(BACnet)

1.3.10 BACnet Building Controller (B-BC)(BACnet)

1.3.11 BACnet Internetwork (BACnet)

1.3.12 BACnet Interoperability Building Blocks (BIBBs) (BACnet)

1.3.13 BACnet Operator Display (B-OD)(BACnet)

1.3.14 BACnet Operator Workstation (B-OWS)(BACnet)

1.3.15 BACnet Smart Actuator (B-SA)(BACnet)

1.3.16 BACnet Smart Sensor (B-SS)(BACnet)

1.3.17 BACnet Testing Laboratories (BTL)(BACnet)

1.3.18 BACnet Testing Laboratories (BTL) Listed (BACnet)

1.3.19 Binary

1.3.20 Binding (LonWorks)

1.3.21 Broadcast

1.3.22 Building Control Network (BCN)

1.3.23 Building Control System (BCS)

1.3.24 Building Point of Connection (BPOC)

1.3.25 Channel (LonWorks)

1.3.26 Commandable (BACnet)

1.3.27 Configuration Property (LonWorks)

1.3.28 Control Logic Diagram

1.3.29 Device Object (BACnet)

1.3.30 1.3.30 Explicit Messaging (LonWorks)

1.3.31 External Interface File (XIF) (LonWorks)

1.3.32 Facility Point Of Connection (FPOC)

1.3.33 Field Control Network

1.3.34 Field Control System (FCS)

1.3.35 Fox Protocol (Metasys Framework)

1.3.36 Functional Profile (LonWorks)

1.3.37 Gateway

1.3.38 General Purpose Programmable Controller (GPPC) (LonWorks)

1.3.39 Internetwork (BACnet)

1.3.40 JACE (Metasys Framework)

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 2 of 50

1.3.41 LonMark Object (LonWorks)

1.3.42 LNS Plug-in (LonWorks)

1.3.43 LonMark (LonWorks)

1.3.44 LonMark International (LonWorks)

1.3.45 LonWorks (LonWorks)

1.3.46 LonWorks Network Services (LNS) (LonWorks)

1.3.47 LonWorks Network Services (LNS) Database (LonWorks)

1.3.48 Modbus

1.3.49 Master-Slave/Token Passing (MS/TP)(BACnet)

1.3.50 Monitoring and Control (M&C) Software

1.3.51 Network (BACnet)

1.3.52 Network Variable (LonWorks)

1.3.53 Network Configuration Tool (LonWorks)

1.3.54 Metasys AX (Metasys Framework)

1.3.55 Metasys Framework (Metasys Framework)

1.3.56 Metasys Framework Supervisory Gateway (Metasys Framework)

1.3.57 Node (LonWorks)

1.3.58 Node Address (LonWorks)

1.3.59 Node ID (LonWorks)

1.3.60 Object (BACnet)

1.3.61 Override

1.3.62 Point, Calculated

1.3.63 Point, Network

1.3.64 Polling

1.3.65 Program ID (LonWorks)

1.3.66 Property (BACnet)

1.3.67 Protocol Implementation Conformance Statement (PICS)(BACnet) ...16

1.3.68 Repeater

1.3.69 Router(LonWorks)

1.3.70 Router (BACnet)

1.3.71 Segment

1.3.72 Service (BACnet)

1.3.73 Service Pin (LonWorks)

1.3.74 Standard BACnet Object/Property/Service (BACnet)

1.3.75 Standard Configuration Property Type (SCPT) (LonWorks)

1.3.76 Standard Network Variable Type (SNVT) (LonWorks)

1.3.77 Subnet (LonWorks)

1.3.78 Supervisory Controller

1.3.79 Supervisory Gateway

1.3.80 TP/FT-10 (LonWorks)

1.3.81 TP/XF-1250 (LonWorks)

1.3.82 UMCS Network

1.3.83 User-defined Configuration Property Type (UCPT) (LonWorks)

1.3.84 User-defined Network Variable Type (UNVT) (LonWorks)

1.3.85 Utility Control System (UCS)

1.4 SUBMITTALS

1.5 PROJECT SEQUENCING

1.6 QUALITY CONTROL (QC) CHECKLISTS

1.7 OPERATION AND MAINTENANCE (O&M) INSTRUCTIONS

PART 2 PRODUCTS

2.1 EQUIPMENT REQUIREMENTS

2.1.1 Product Certifications

2.1.2 Product Sourcing

2.1.3 General Requirements

2.1.4 Nameplates

2.1.5 Product Data Sheets

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 3 of 50

2.2 CONTROL HARDWARE

2.2.1 Control Protocol Routers

2.2.2 Monitoring and Control (M&C) Controller Hardware

2.2.3 BACnet Supervisory Controller Hardware

2.2.4 Control Protocol Gateways

2.3 COMPUTER SOFTWARE

2.3.1 Operating System (OS)

2.3.2 Office Automation Software

2.3.3 Virus Protection Software

2.3.4 Disk Imaging (Backup) Software

2.3.5 M&C Controller Hardware Configuration Software

2.3.6 CEA-852-B Configuration Server

2.3.7 CEA-709.1-C Network Configuration Tool

2.3.8 BACnet Network Browser

2.3.9 Monitoring and Control (M&C) Software

2.4 UNINTERRUPTIBLE POWER SUPPLY (UPS)

2.5 RACKS AND ENCLOSURES

2.5.1 Enclosures

2.5.2 Equipment Racks

PART 3 EXECUTION

3.1 EXISTING CONDITIONS SURVEY

3.2 DRAWINGS AND CALCULATIONS

3.2.1 Certificate of Networthiness Documentation

3.2.2 UMCS Contractor Design Drawings

3.2.3 As-Built Drawings

3.3 INSTALLATION REQUIREMENTS

3.3.1 General

3.3.2 Isolation, Building Penetrations and Equipment Clearance

3.3.3 Nameplates

3.4 INSTALLATION OF EQUIPMENT

3.4.1 Wire and Cable Installation

3.4.2 Grounding

3.4.3 Power-Line Surge Protection

3.4.4 IP Addresses

3.4.5 Computer Hardware and Software

3.5 INTEGRATION OF FIELD CONTROL SYSTEMS

3.5.1 Integration Step 1: Install Control Hardware

3.5.2 Integration Step 2: Add Field Control System to M&C Software

3.5.3 Integration Step 3: Configure M&C Software

3.6 START-UP AND START-UP TESTING

3.7 MAINTENANCE AND SERVICE

3.7.1 Work Coordination

3.7.2 Work Control

3.7.3 Working Hours

3.7.4 Replacement, Modernization, Renovation

3.7.5 Access To UMCS Equipment

3.7.6 Records, Logs, and Progress Reports

3.8 TRAINING

3.8.1 Training Documentation

3.8.2 Basic Training

3.8.3 Refresher Training

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 4 of 50

SECTION 25 10 10

UTILITY MONITORING AND CONTROL SYSTEM (UMCS) FRONT END AND INTEGRATION

PART 1 GENERAL

1.1 SUMMARY

The Defense Distribution Center, Susquehanna Post ( DDSP ) utilizes a Johnson Controls Metasys System for Utility Monitoring and Control System (UMCS) which performs supervisory monitoring and supervisory control of base-wide building control systems and utility control systems using one or more of: CEA-709.1-C (LonWorks) with LonWorks Network Services (LNS), ASHRAE 135 (BACnet), Modbus, as specified and shown. The existing, Base Wide UMCS shall be interfaced to local CEA-709.1-C building control systems installed per Section 23 09 23 LONWORKS DIRECT DIGITAL CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS, and maintain the LNS database(s) for the entire network.

1.1.1 System Requirements

Provide a connection to the existing UMCS as specified and shown, and in accordance with the following characteristics:

1.1.1.1 General System Requirements

a. The existing base wide UMCS is a Johnson Controls Metasys Extended Architecture system utilizing an Application Data Server Extended ( ADX server).

b. Integration of existing UMCS to the LON systems installed per section 23 09 23 shall be performed by Johnson Controls Inc and will utilize Johnson Controls Network Automation Engine (NAE-5520-3), provided in this section.

c. Integration of existing UMCS to ASHRAE 135 BACnet systems shall be performed by Johnson Controls Inc and may utilize Johnson Controls Network Automation Engine Network Automation Engine provided in this section.

d. The UMCS system interface shall perform supervisory monitoring and control functions including but not limited to Scheduling, Alarm Handling, Trending, Overrides, Report Generation, and Electrical Demand Limiting as specified.

e. The UMCS system interface shall include a Graphical User Interface which shall allow for graphical navigation between systems, graphical representations of systems, access to real-time data for systems, ability to override points in a system, and access to all supervisory monitoring and control functions.

f. All software used by the UMCS and all software used to install and configure the UMCS shall be licensed to and delivered to the installation.

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 5 of 50

g. All necessary documentation, configuration information, configuration tools, programs, drivers, and other software shall be licensed to and otherwise remain with the Government such that the Government or their agents are able to repair, replace, upgrade, and expand the system without subsequent or future dependence on the Contractor. Software licenses shall not require periodic fees and shall be valid in perpetuity.

h. Provide sufficient documentation and data, including rights to documentation and data, such that the Government or their agents can execute work to repair, replace, upgrade, and expand the system without subsequent or future dependence on the Contractor.

i. For UMCS systems with Monitoring and Control Software functionality implemented in Monitoring and Control (M&C) Controller Hardware, provide sufficient additional controller hardware to support the full capacity requirements as specified.

1.1.1.2 LonWorks Requirements

a. The UMCS may communicate using CEA-709.1-C over the Government furnished IP network in accordance with CEA-852-B as shown and specified and shall interface to CEA-709.1-C building control networks using LonWorks/IP Routers as specified.

b. All communication between the UMCS and LonWorks field control networks shall be via the CEA-709.1-C protocol over the Dedicated Base wide IP network in accordance with CEA-852-B.

c. Except for communication for device commissioning, configuration, and programming, all communication between the M&C Software and the field control system devices shall be via SNVT.

1.1.1.3 BACnet Requirements

a. The UMCS may communicate using ASHRAE 135 Annex J over the Government furnished IP network as shown and specified.

b. All communication between the UMCS and ASHRAE 135 field control networks shall be via the ASHRAE 135 protocol over the Dedicated Base wide IP network.

1.1.2 Symbols, Definition and Abbreviations

Symbols, definitions, and engineering unit abbreviations used in displays, submittals and reports shall be as shown in the contract drawings.

Symbols, definitions and abbreviations not in the contract drawings shall conform at a minimum to IEEE Stds Dictionary and the ASHRAE FUN IP, as applicable.

1.1.3 System Units and Accuracy

Displays, print-outs and calculations shall be performed in English (inch-pound) units. Calculations shall have accuracy equal to or exceeding sensor accuracy as specified in Section 23 09 23 LONWORKS DIRECT DIGITAL

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 6 of 50

CONTROL FOR HVAC AND OTHER BUILDING CONTROL SYSTEMS. Displays and printouts shall present values to at least three significant figures.

1.1.4 Data Packages/Submittals Requirements

Technical data packages consisting of computer software and technical data (meaning technical data which relates to computer software) which are specifically identified in this project and which may be defined/required in other specifications shall be delivered strictly in accordance with the CONTRACT CLAUSES and in accordance with the Contract Data Requirements List, DD Form 1423. Data delivered shall be identified by reference to the particular specification paragraph against which it is furnished. All submittals not specified as technical data packages are considered shop drawings under the Federal Acquisition Regulation Supplement (FARS) and shall contain no proprietary information and shall be delivered with unrestricted rights.

1.2 REFERENCES

The publications listed below form a part of this specification to the extent referenced. The publications are referred to within the text by the basic designation only.

AMERICAN NATIONAL STANDARDS INSTITUTE (ANSI)

ANSI INCITS 154 (1988; R 2004) Office Machines and Supplies - Alphanumeric Machines - Keyboard Arrangement

AMERICAN SOCIETY OF HEATING, REFRIGERATING AND AIR-CONDITIONING ENGINEERS

(ASHRAE)

ASHRAE 135 (2012; Errata 2013) BACnet—A Data Communication Protocol for Building Automation and Control Networks

ASHRAE FUN IP (2013) Fundamentals Handbook, I-P Edition

ASHRAE FUN SI (2013) Fundamentals Handbook, SI Edition

CONSUMER ELECTRONICS ASSOCIATION (CEA)

CEA-709.1-C (2010) Control Network Protocol Specification

CEA-709.3 (1999; R 2004) Free-Topology Twisted-Pair Channel Specification

CEA-852-B (2010) Tunneling Component Network Protocols Over Internet Protocol Channels

INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS (IEEE)

IEEE 1815 (2012) Electric Power Systems Communications- Distributed Network Protocol (DNP3)

IEEE 754 (2008) Floating-Point Arithmetic - IEEE Computer Society

IEEE 802.11 (2012; AA 2012; AE 2012; AD 2012) Information technology-Telecommunications and Information

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 7 of 50

Exchange Between Systems Local and Metropolitan Area Networks-Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications

IEEE C62.41 (1991; R 1995) Recommended Practice on Surge Voltages in Low-Voltage AC Power Circuits

IEEE Stds Dictionary (2009) IEEE Standards Dictionary: Glossary of Terms & Definitions

INTERNATIONAL ORGANIZATION FOR STANDARDIZATION (ISO)

ISO 8601 (2004) Data Elements and Interchange Formats - Information Interchange - Representation of Dates and Times

ISO 8859-1 (1998) Information Technology - 8-Bit Single-Byte Coded Graphic Character Sets - Part 1: Latin Alphabet No. 1

LONMARK INTERNATIONAL (LonMark)

LonMark Interoperability Guide (2005) LonMark Application-Layer Interoperability Guide and LonMark Layer 1-6 Interoperability Guide; Version 3.4

LonMark SNVT List (2003) LonMark SNVT Master List; Version 113

LonMark XIF Guide (2001) LonMark External Interface File Reference Guide; Revision 4.402

MODBUS ORGANIZATION, INC (MODBUS)

Modbus (2006) Modbus Application Protocol Specification;

Version 1.1b and Modbus Messaging on TCP/IP Implementation Guide; Version V1.0b

NATIONAL ELECTRICAL MANUFACTURERS ASSOCIATION (NEMA)

NEMA 250 (2008) Enclosures for Electrical Equipment (1000 Volts Maximum)

NATIONAL FIRE PROTECTION ASSOCIATION (NFPA)

NFPA 262 (2011) Standard method of Test for Flame Travel and Smoke of Wires and Cables for Use in Air-Handling Spaces

NFPA 70 (2014) National Electrical Code

OPC FOUNDATION (OPC)

OPC DA (2002) OPC Data Access (DA) Specification; Version 2.05a

TELECOMMUNICATIONS INDUSTRY ASSOCIATION (TIA)

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 8 of 50

TIA-568-C.1 (2009; Add 2 2011; Add 1 2012) Commercial Building Telecommunications Cabling Standard

TIA-607 (2011b) Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises

TIA/EIA-606 (2002a; Errata 2007; R 2007; Adm 1 2008) Administration Standard for the Telecommunications Infrastructure

THE INTERNET ENGINEERING TASK FORCE (IETF)

IETF RFC 4361 (2006) Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)

IETF RFC 5246 (2008) The Transport Layer Security (TLS) Protocol Version 1.2

IETF RFC 5545 (2009) Internet Calendaring and Scheduling Core Object Specification (iCalendar)

RFC 821 (2001) Simple Mail Transfer Protocol (SMTP)

U.S. AIR FORCE (USAF)

F ETL 11-1 (2011) Civil Engineer Industrial Control System Information Assurance Compliance

U.S. ARMY (DA)

DA AR 25-2 (2007; RAR 2009) Information Assurance

U.S. FEDERAL COMMUNICATIONS COMMISSION (FCC)

FCC EMC (2002) FCC Electromagnetic Compliance Requirements

FCC Part 15 Radio Frequency Devices (47 CFR 15)

UNDERWRITERS LABORATORIES (UL)

UL 1778 (2005; Reprint Oct 2011) Uninterruptible Power Systems

UL 60950 (2000; Reprint Oct 2007) Safety of Information Technology Equipment

1.3 DEFINITIONS

The following list of definitions may contain terms not found elsewhere in this Section but are included here for completeness. Some terms are followed with a protocol reference in parenthesis (for example: (BACnet)) indicating to which protocol the term and definition applies.

1.3.1 Alarm Generation

The process of comparing a point value (the point being alarmed) with a pre-defined alarm condition (e.g. a High Limit) and performing some action based on the result of the comparison.

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 9 of 50

1.3.2 Alarm Handling

See Alarm Routing.

1.3.3 Alarm Routing

Alarm routing is M&C software functionality that starts with a notification that an alarm exists (typically as the output of an Alarm Generation process) and sends a specific message to a specific alarm recipient or device.

1.3.4 Application Generic Controller (AGC)(LonWorks)

A device that is furnished with a (limited) pre-established application that also has the capability of being programmed. Further, the Program ID and XIF file of the device are fixed. The programming capability of an AGC may be less flexible than that of a General Purpose Programmable Controller (GPPC).

1.3.5 Application Specific Controller (ASC)(LonWorks)

A device that is furnished with a pre-established built in application that is configurable but not re-programmable. An ASC has a fixed factory-installed application program (i.e Program ID) with configurable settings.

1.3.6 BACnet (BACnet)

The term BACnet is used in two ways. First, meaning the BACnet Protocol Standard - the communication requirements as defined by ASHRAE 135, including all annexes and addenda. The second refers to the overall technology related to the ASHRAE 135 protocol.

1.3.7 BACnet Advanced Application Controller (B-AAC)(BACnet)

A hardware device BTL Listed as a B-AAC. A control device which contains BIBBs in support of scheduling and alarming but otherwise has limited resources relative to a B-BC. It may be intended for specific applications and supports some degree of programmability.

1.3.8 BACnet Advanced Operator Workstation (B-AWS)(BACnet)

Monitoring and Control (M&C) Software BTL Listed as an Advanced Operator Workstation and includes the ability to manage scheduling, alarming and trending in an open manner. The B-AWS is the advanced operator's window into a BACnet system. It is primarily used to monitor the performance of a system and to modify parameters that affect the operation of a system.

1.3.9 BACnet Application Specific Controller (B-ASC)(BACnet)

A hardware device BTL Listed as a B-ASC. A controller with limited resources relative to a B-AAC. It is intended for use in a specific application and supports limited programmability.

1.3.10 BACnet Building Controller (B-BC)(BACnet)

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 10 of 50

A hardware device BTL Listed as a B-BC. A general-purpose, field-programmable device capable of carrying out a variety of building automation and control tasks including control and monitoring via direct digital control (DDC) of specific systems and data storage for trend information, time schedules, and alarm data. Like the other BTL Listed controller types (B-AAC, B-ASC etc.) a B-BC device is required to support the server ("B") side of the ReadProperty and WriteProperty services, but unlike the other controller types it is also required to support the client ("A") side of these services. Communication between controllers requires that one of them support the client side and the other support the server side, so a B-BC is often used when communication between controllers is needed.

1.3.11 BACnet Internetwork (BACnet)

Two or more BACnet networks connected with BACnet routers. In a BACnet Internetwork, there exists only one message path between devices.

1.3.12 BACnet Interoperability Building Blocks (BIBBs) (BACnet)

A BIBB is a collection of one or more BACnet services intended to define a higher level of interoperability. BIBBs are combined to build the BACnet functional requirements for a device in a specification. Some BIBBs define additional requirements (beyond requiring support for specific services) in order to achieve a level of interoperability. For example, the BIBB DS-V-A (Data Sharing-View-A), which would typically be used by an M&C client, not only requires the client to support the ReadProperty Service, but also provides a list of data types (Object / Properties) which the client must be able to interpret and display for the user.

1.3.13 BACnet Operator Display (B-OD)(BACnet)

A hardware device BTL Listed as a B-OD. A basic operator interface with limited capabilities relative to a B-OWS. It is not intended to perform direct digital control. The B-OD profile could be used for wall-mounted LCD devices, displays affixed to BACnet devices; hand-held terminals or other very simple user interfaces.

1.3.14 BACnet Operator Workstation (B-OWS)(BACnet)

Monitoring and Control (M&C) Software BTL Listed as a B-OWS. An operator interface with limited capabilities relative to a B-AWS. The B-OWS is used for monitoring and basic control of a system, but differs from a B- AWS in that it does not support configuration activities, nor does it provide advanced troubleshooting capabilities.

1.3.15 BACnet Smart Actuator (B-SA)(BACnet)

A hardware device BTL Listed as a B-SA. A simple control output device with limited resources; it is intended for specific applications.

1.3.16 BACnet Smart Sensor (B-SS)(BACnet)

A hardware device BTL Listed as a B-SS. A simple sensing device with very limited resources.

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 11 of 50

1.3.17 BACnet Testing Laboratories (BTL)(BACnet)

Established by BACnet International to support compliance testing and interoperability testing activities and consists of BTL Manager and the BTL Working Group (BTL-WG). BTL also publishes Implementation Guidelines.

1.3.18 BACnet Testing Laboratories (BTL) Listed (BACnet)

A device that has been certified by BACnet® Testing Laboratory. Devices may be certified to a specific device profile, in which case the certification indicates that the device supports the required capabilities for that profile, or may be certified as "other".

1.3.19 Binary

A two-state system or signal; for example one where an "ON" condition is represented by a high signal level and an "OFF" condition is represented by a low signal level. 'Digital' is sometimes used interchangeably with 'binary'.

1.3.20 Binding (LonWorks)

The act of establishing communications between CEA-709.1-C devices by associating the output of a device, to the input of another, so that information is automatically (and regularly) sent without being requested by the recipient.

1.3.21 Broadcast

Unlike most messages, which are intended for a specific recipient device, a broadcast message is intended for all devices on the network.

1.3.22 Building Control Network (BCN)

The network used by the Building Control System. Typically the BCN is a BACnet ASHRAE 135 or LonWorks CEA-709.1-C network installed by the building control system contractor.

1.3.23 Building Control System (BCS)

One type of Field Control System. A control system for building electrical and mechanical systems, typically HVAC (including central plants) and lighting. A BCS generally uses Direct Digital Control (DDC) Hardware and generally does NOT include its own local front end.

1.3.24 Building Point of Connection (BPOC)

A FPOC for a Building Control System. (This term is being phased out of use in preference for FPOC but is still used in some specifications and criteria.)

1.3.25 Channel (LonWorks)

A portion of the control network consisting of one or more segments connected by repeaters. Channels are separated by routers. The device quantity limitation is dependent on the topology/media and device type.

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 12 of 50

For example, a TP/FT-10 network with locally powered devices is limited to 128 devices per channel.

1.3.26 Commandable (BACnet)

A point (Object) is commandable if its Present_Value Property is writable and it supports the optional Priority_Array Property. This functionality is useful for Overrides.

1.3.27 Configuration Property (LonWorks)

Controller parameter used by the application which is usually set during installation/testing and seldom changed. For example, the P and I settings of a P-I control loop. Also see 'Standard Configuration Property Type (SCPT)'

1.3.28 Control Logic Diagram

A graphical representation of control logic for multiple processes that make up a system.

1.3.29 Device Object (BACnet)

Every BACnet device requires one Device Object, whose properties represent the network visible properties of that device. Every Device Object requires a unique Object_Identifier number on the BACnet internetwork.

This number is often referred to as the device instance or device ID.

1.3.30 1.3.30 Explicit Messaging (LonWorks)

A non-standard and often vendor (application) specific method of communication between devices.

1.3.31 External Interface File (XIF) (LonWorks)

A file which documents a device's external interface, specifically the number and types of LonMark objects, the number, types, directions, and connection attributes of network variables, and the number of message tags.

1.3.32 Facility Point Of Connection (FPOC)

The FPOC is the point of connection between the UMCS IP Network and the field control network (either an IP network, a non-IP network, or both).

The hardware at this location which provides the connection is generally one of a control protocol router, a control protocol gateway, or an IT device such as a switch, IP router, or firewall.

In general, the term "FPOC Location" means the place where this connection occurs, and "FPOC Hardware" means the device that provides the connection.

Sometimes the term "FPOC" is used to mean either and its actual meaning (i.e. location or hardware) is determined by the context in which it is used.

1.3.33 Field Control Network

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 13 of 50

The network used by a field control system.

1.3.34 Field Control System (FCS)

A building control system or utility control system.

1.3.35 Fox Protocol (Metasys Framework)

The protocol used for communication between components in the Metasys Framework. By default, Fox uses TCP port 1911

1.3.36 Functional Profile (LonWorks)

A standard description, defined by LonMark International, of a LonMark Object used to classify and certify devices.

1.3.37 Gateway

A device that translates from one protocol to another. Devices that change only the transport mechanism of the protocol - "translating" from LonWorks over TP/FT-10 to LonWorks over IP for example - are not gateways as the underlying protocol (data format) does not change. Gateways are also called Communications Bridges or Protocol Translators.

1.3.38 General Purpose Programmable Controller (GPPC) (LonWorks)

Unlike an ASC or AGC, a GPPC is not furnished with a fixed application program and does not have a fixed ProgramID or XIF file. A GPPC can be (re-)programmed, usually using vendor-supplied software. When a change to the program affects the external interface (and the XIF file) the ProgramID will change.

1.3.39 Internetwork (BACnet)

See BACnet Internetwork.

1.3.40 JACE (Metasys Framework)

Java Application Control Engine. See Metasys Framework Supervisory Gateway

1.3.41 LonMark Object (LonWorks)

A collection of network variables, configuration properties, and associated behavior defined by LonMark International and described by a Functional Profile. It defines how information is exchanged between devices on a network (inputs from and outputs to the network).

1.3.42 LNS Plug-in (LonWorks)

Software which runs in an LNS compatible software tool, typically a network configuration tool. Device configuration plug-ins provide a 'user friendly' method to edit a device's configuration properties.

1.3.43 LonMark (LonWorks)

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 14 of 50

See LonMark International. Also, a certification issued by LonMark International to CEA-709.1-C devices.

1.3.44 LonMark International (LonWorks)

Standards committee consisting of independent product developers, system integrators and end users dedicated to determining and maintaining the interoperability guidelines for LonWorks. Maintains guidelines for the interoperability of CEA-709.1-C devices and issues the LonMark Certification for CEA-709.1-C devices.

1.3.45 LonWorks (LonWorks)

The term used to refer to the overall technology related to the CEA-709.1- C protocol (sometimes called "LonTalk"), including the protocol itself, network management, interoperability guidelines and products.

1.3.46 LonWorks Network Services (LNS) (LonWorks)

A network management and database standard for CEA-709.1-C devices.

1.3.47 LonWorks Network Services (LNS) Database (LonWorks)

The standard database created and used by LonWorks Network Services (LNS) compatible tools, such as LNS Network Configuration tools.

1.3.48 Modbus

A basic protocol for control network communications generally used in utility control systems. The Modbus protocol standard is maintained by The Modbus Organization.

1.3.49 Master-Slave/Token Passing (MS/TP)(BACnet)

Data link protocol as defined by the BACnet standard. Multiple speeds (data rates) are permitted by the BACnet MS/TP standard.

1.3.50 Monitoring and Control (M&C) Software

The UMCS 'front end' software which performs supervisory functions such as alarm handling, scheduling and data logging and provides a user interface for monitoring the system and configuring these functions.

1.3.51 Network (BACnet)

In BACnet, a portion of the control internetwork consisting of one or more segments of the same media connected by repeaters. Networks are separated by routers.

1.3.52 Network Variable (LonWorks)

See 'Standard Network Variable Type (SNVT)'.

1.3.53 Network Configuration Tool (LonWorks)

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 15 of 50

The software used to configure the control network and set device configuration properties. This software creates and modifies the control network database (LNS Database).

1.3.54 Metasys AX (Metasys Framework)

The current version (release) of the Metasys Framework. While it is often used to refer to just the front end, it includes all components of the Metasys Framework. (Note: The previous version of the Metasys Framework is "R2".)

1.3.55 Metasys Framework (Metasys Framework)

A set of hardware and software specifications for building and utility control owned by Tridium Inc. and licensed to multiple vendors. The Framework consists of front end (M&C) software, web based clients, field level control hardware, and engineering tools. While the Metasys Framework is not adopted by a recognized standards body and does not use an open licensing model, it is sufficiently well-supported by multiple HVAC vendors to be considered a de-facto Open Standard.

1.3.56 Metasys Framework Supervisory Gateway (Metasys Framework)

DDC Hardware component of the Metasys Framework. A typical Metasys architecture has Metasys specific supervisory gateways at the IP level and other (non-Metasys specific) controllers on field networks (TP/FT-10, MS/TP, etc.) beneath the Metasys supervisory gateways. The Metasys specific controllers function as a gateway between the Metasys framework protocol (Fox) and the field network beneath. These supervisory gateways may also be used as general purpose controllers and also have the capability to provide a web-based user interface.

Note that different vendors refer to this component by different names.

The most common name is "JACE"; other names include "EC-BOS", "FX-40", and

"UNC".

1.3.57 Node (LonWorks)

A device that communicates using the CEA-709.1-C protocol and is connected to a CEA-709.1-C network.

1.3.58 Node Address (LonWorks)

The logical address of a node on the network, consisting of a Domain number, Subnet number and Node number. Note that the "Node number" portion of the address is the number assigned to the device during installation and is unique within a subnet. This is not the factory-set unique Node ID (see Node ID).

1.3.59 Node ID (LonWorks)

A unique 48-bit identifier assigned (at the factory) to each CEA-709.1-C device. Sometimes called the Neuron ID.

1.3.60 Object (BACnet)

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 16 of 50

A BACnet Object. The concept of organizing BACnet information into standard components with various associated Properties. Examples include Analog Input objects and Binary Output objects.

1.3.61 Override

To change the value of a point outside of the normal sequence of operation where this change has priority over the sequence. An override can be accomplished in one of two ways: the point itself may be Commandable and written to with a priority or there may be a separate point on the controller for the express purpose of implementing the override.

Typically this override is from the Utility Monitoring and Control System (UMCS) Monitoring and Control (M&C) Software. Note that this definition is not standard throughout industry.

1.3.62 Point, Calculated

A value within the M&C Software that is not a network point but has been calculated by logic within the software based on the value of network points or other calculated points. Calculated points are sometimes called virtual points or internal points.

1.3.63 Point, Network

A value that the M&C Software reads from or writes to a field control network.

1.3.64 Polling

A requested transmission of data between devices, rather than an unrequested transmission such as Change-Of-Value (COV) or Binding where data is automatically transmitted under certain conditions.

1.3.65 Program ID (LonWorks)

An identifier (number) stored in the device (usually EEPROM) that identifies the node manufacturer, functionality of device (application & sequence), transceiver used, and intended device usage.

1.3.66 Property (BACnet)

A BACnet Property - a data element associated with an Object. Different Objects have different Properties, for example an Analog Input Object has a Present_Value Property (which provides the value of the underlying hardware analog input), a High_Limit Property (which contains a high limit for alarming), as well as other properties.

1.3.67 Protocol Implementation Conformance Statement (PICS)(BACnet)

A document, created by the manufacturer of a device, which describes which potions of the BACnet standard, are implemented by a given device.

1.3.68 Repeater

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 17 of 50

A device that connects two control network segments and retransmits all information received on one side onto the other.

1.3.69 Router(LonWorks)

A device that connects two channels and controls traffic between the channels by retransmitting signals received from one subnet onto the other based on the signal destination. Routers are used to subdivide a control network and to control bandwidth usage.

1.3.70 Router (BACnet)

A device that connects two or more BACnet networks and controls traffic between the networks by retransmitting signals received from one network onto another based on the signal destination. Routers are used to subdivide an internetwork and to control bandwidth usage.

1.3.71 Segment

A 'single' section of a control network that contains no repeaters or routers. There is generally a limit on the number of devices on a segment, and this limit is dependent on the topology/media and device type. For example, a TP/FT-10 segment with locally powered devices is limited to 64 devices, and a BACnet MS/TP segment is limited to 32 devices.

1.3.72 Service (BACnet)

A BACnet Service. A defined method for sending a specific type of data between devices. Services are always defined in a Client-Server manner, with a Client initiating a Service request and a Server Executing the Service. Some examples are ReadProperty (a client requests a data value from a server), WriteProperty (a client writes a data value to a server), and CreateObject (a client requests that a server create a new object within the server device).

1.3.73 Service Pin (LonWorks)

A hardware push-button on a device which causes the device to broadcast a message containing its Node ID and Program ID. This broadcast can also be initiated via software.

1.3.74 Standard BACnet Object/Property/Service (BACnet)

BACnet Objects, Properties, or Services that are standard Objects, Properties, or Services enumerated and defined in ASHRAE 135. Clause 23 of ASHRAE 135 defines methods to extend ASHRAE 135 to non-standard or proprietary information. Standard BACnet Objects/Properties/Services specifically exclude any vendor specific extensions.

1.3.75 Standard Configuration Property Type (SCPT) (LonWorks)

Pronounced 'skip-it'. A standard format type (maintained by LonMark International) for Configuration Properties.

1.3.76 Standard Network Variable Type (SNVT) (LonWorks)

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 18 of 50

Pronounced 'snivet'. A standard format type (maintained by LonMark International) used to define data information transmitted and received by the individual nodes. The term SNVT is used in two ways. Technically it is the acronym for Standard Network Variable Type, and is sometimes used in this manner. However, it is often used to indicate the network variable itself (i.e. it can mean "a network variable of a standard network variable type"). In general, the intended meaning should be clear from the context.

1.3.77 Subnet (LonWorks)

Consists of a logical grouping of up to 127 nodes, where the logical grouping is defined by node addressing. Each subnet is assigned a number which is unique within the Domain. See also Node Address.

1.3.78 Supervisory Controller

A controller implementing a combination of supervisory logic (global control strategies or optimization strategies), scheduling, alarming, event management, trending, web services or network management. Note this is defined by use; many supervisory controllers have the capability to also directly control equipment.

1.3.79 Supervisory Gateway

A device that is both a supervisory controller and a gateway, such as a Metasys Framework Supervisory Gateway.

1.3.80 TP/FT-10 (LonWorks)

A Free Topology Twisted Pair network (at 78 kbps) defined by CEA-709.3.

This is the most common media type for a CEA-709.1-C control network.

1.3.81 TP/XF-1250 (LonWorks)

A high speed (1.25 Mbps) twisted pair, doubly-terminated bus network defined by the LonMark Interoperability Guidelines. This media is typically used only as a backbone media to connect multiple TP/FT-10 networks.

1.3.82 UMCS Network

An IP network connecting multiple field control systems to the Monitoring and Control Software using one or more of: LonWorks (CEA-709.1-C and CEA- 852-B), BACnet (ASHRAE 135 Annex J), Modbus or OPC DA.

1.3.83 User-defined Configuration Property Type (UCPT) (LonWorks)

Pronounced 'u-keep-it'. A Configuration Property format type that is defined by the device manufacturer.

1.3.84 User-defined Network Variable Type (UNVT) (LonWorks)

A network variable format defined by the device manufacturer. Note that UNVTs create non-standard communications (other vendor's devices may not

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 19 of 50 correctly interpret it) and may close the system and therefore are not permitted by this specification.

1.3.85 Utility Control System (UCS)

One type of field control system. Used for control of utility systems such as an electrical substation, sanitary sewer lift station, water pump station, etc. Building controls are excluded from a UCS, however it is possible to have a Utility Control System and a Building Control System in the same facility, and for those systems to share components such as the FPOC. A UCS may include its own local front-end.

1.4 SUBMITTALS

Government approval is required for submittals with a "G" designation;

submittals not having a "G" designation are for information only. When used, a designation following the "G" designation identifies the office that will review the submittal for the Government. Submit the following in accordance with Section 01 33 00 SUBMITTAL PROCEDURES and TABLE 1:

PROJECT SEQUENCING

SD-02 Shop Drawings

UMCS Contractor Design Drawings; G UMCS Contractor Design Drawings in hard copy and on optical disk in PDF.

Final As-Built Drawings; G Final As-Built Drawings in hard copy and on optical disk in PDF.

SD-03 Product Data

Product Data Sheets; G Copies of all manufacturer catalog cuts and specification sheets for all products (equipment) specified in PART 2 and supplied under this contract.

Computer Software; G The most recent versions of all computer software provided under this specification delivered as a Technical Data Package. The user manuals for all software delivered for this project shall be submitted with the software.

Certificate of Networthiness Documentation; G Documentation of existing Certificates of Networthiness or completed [via email and ]on optical disk.

SD-06 Test Reports

Start-Up and Start-Up Testing Report; G Four copies of the Start-Up and Start-Up Testing Report. The Start-Up and Testing report may be submitted as a Technical Data Package.

PVT Phase I Procedures; G

SD-10 Operation and Maintenance Data

Preventive Maintenance Work Plan; G Four copies of the Preventive Maintenance Work Plan. The Preventive Maintenance Work Plan may be submitted as a Technical Data Package.

Basic Training Documentation; G

Section 25 10 10 Utility Monitoring and Control System (UMCS) Front End and Integration Page 20 of 50

Training manuals for Basic Training delivered for each trainee on the Course Attendance List with two additional copies delivered for archival at the project site. Two copies of the Course Attendance List shall be delivered with the archival copies. The Basic Training Documentation may be submitted as a Technical Data Package.

One set of training manuals delivered for each trainee on the Course Attendance List with two additional copies delivered for archival at the project site. Two copies of the Course Attendance List shall be delivered with the archival copies.

The Advanced Training Documentation may be submitted as a Technical Data Package.

One set of training manuals delivered for each trainee on the Course Attendance List with two additional copies delivered for archival at the project site. Two copies of the Course Attendance List shall be delivered with the archival copies.

The Refresher Training Documentation may be submitted as a Technical Data Package.

Operation and Maintenance (O&M) Instructions; G Four bound O&M Instructions and copies of the Instructions in PDF format on optical disk. Bound Instructions shall be indexed and tabbed. Instructions in PDF form shall be a single PDF file, or multiple PDF files with a PDF file table of contents containing links to the other files. O&M Instructions may be submitted as a Technical Data Package.

SD-11 Closeout Submittals

Closeout QC Checklist; G Four copies of the Closeout QC Checklist.

1.5 PROJECT SEQUENCING

TABLE I: PROJECT SEQUENCING specifies the sequencing of submittals as specified in paragraph SUBMITTALS (denoted by an 'S' in the 'TYPE' column) and activities as specified in PART 3: EXECUTION (denoted by an 'E' in the 'TYPE' column).

a. Sequencing for submittals: The sequencing specified for submittals is the deadline by which the submittal must be initially submitted to the Government. Following submission there will be a Government review period as specified in Section 01 33 00 SUBMITTAL PROCEDURES.