W9126G18R0010-0002-DCF3_Cont_Sys_Inventory_sheet.xlsx

Read Me First

Purpose:

Scope:

Data Dictionary:

Inventory:

Per NNWC ltr dtd 14 DEC 2009, DESIGNATION AS PLATFORM INFORMATION TECHNOLOGY (PIT) FOR THE BUILDING AND UTILITIES INDUSTRIAL CONTROL SYSTEMS, the requirement to discover, document, and institute a configuration management program.

This data dictionary will assist in the data collection process. The most common terms and labels of anticipated equipments to be found are defined through graphic examples.

It is important to understand this data collection is the FECs responsibility to maintain and report on when changes toICS configuration occur affecting the Information Assurance (IA) controls of ICS. This data collection will serve to register all systems IAW DON CIO requirements and will be the authoritative information source for the regional CS Configuration Control Board (CCB) in the administration and the configuration management of all CS associated assets. It will be the source in providing the required reports in maintaining the PIT designation and continued operation of all CS.

This action encompasses all facilities constructed by or for Naval Facilities Engineering COmmand.

This tab is the detailed Inventory of CS devices. The content of this tab should be considered sensitive, and only shared with those having explicit need-to know. Each row in this tab must correspond to a single hardware device (or Virtual Machine).It is important that entire systems are broken out by component, and not simnply listed on one line as "the system".

Data Dictionary

Template Data Dictionary The following provides a detailed description of the fields used in the inventory spreadsheet

Options Include:

EU - COMMANDER NAVY REG EURAFSWA

FE - FAR EAST

HI - COMNAVREG PEARL HARBOR HI

JP - COMNAVREG JAPAN (Included in FE) KO - NAVY REGION KOREA (Included in FE)

MA - JTREG MARIANAS GUAM

ML - COMNAVREG MIDLANT

NW - COMNAVREG NW SEATTLE WA

SE - COMNAVREG SE JACKSONVILLE FL

SW - COMNAVREG SW SAN DIEGO CA

Options include:

CA - Compressed Air CW - Chilled Water DI - Deioninzed Water EL - Electric FO - Fuel Oil HW - Hot Water HVAC - HVAC and other building systems IR - Irrigation such as sprinklers LT - Lighting (Other than that associated with a single building) Multiple - More than one commodity is supported by this device. List the individual commodities in the Comments field.

NET - Network NG - Natural Gas OW - Oily Water PW - Pure Water SE - Sanitary Sewage ST - Steam SW - Salt Water WA - Potable Water

Locking Coabinet Non-Locking Cabinet Open, attached Open, loose Other (Write in) Extended Fac Info

UPS Is the component powered by a UPS?

Yes - Local Yes - Building No

Yes No

INF - Component is part of the CS Infrastrcuture

Infrastructure [Leave Blank] -Level 5 in Layer Cake Front End - Operational Servers, Workstations (Level 4 in Layer Cake) FPOC - Field Point of Connection (Level 3 in the layer Cake) Field Control System (Layers 0-2 in the Layer Cake) BCS - Building Control System UCS - Utility Control System BCS-UCS - part of both a BCS and UCS [other] - Use appropriate system desgination(ESS, FLSS, etc.) or just "Other" if unknown Accreditation Boundary See Enclosure (3) in CIO Bulletin "Sustain, Manage and Protect CS Inventory" and select from the following choices:

PE - Platform Enclave. This refers architecture, which may or may not be the "ICS-PE" OA - Operational Architecture Accreditation Component Based upon selection of PE or OA above, enter the appropriate choice below:

Platform Enclave CS-PE - Part of the ICS-PE authorization FACMCS - FEC NW Only [Leave Blank] - If not part of ICS-PE or FACMCS Operational Architecture NUMCS VHE - Hardware that is part of the NUMCS Virtual Hosting Environment NUMCS - If accredited under the NUMCS authorization, but not part of the VHE [Leave Blank] - If not part of NUMCS

Options Include:

Computer - Any laptop, desktop or server computer Supervisory Controller Equipment Controller Network

Example 1:

Device Type: IED Sub-Device Type: Protective Relay Device Function: Overcurrent Protection Example 2:

Device type: IED Sub-Device Type: Gateway (Protocol Converter)

Dell: "PowerEdge" Invensys: "I/A Series" Johnson Controls: "Metasys

Options Include:

None

DSL

Telephone Wired, Copper Wired, Fiber Wireless Wired (Copper) and Wireless

Ethernet Non-IP - The device utilizes Ethernet but is non-IP (non-Internet Protocol) Ethernet IP - The device utilizes an Ethernet IP protocol None - The device has no connected network Other - The device uses a protocol other than Ethernet Control Protocol Options Include:

Fox

DNP 3.0

IEC-61850

BACnet C37.118

COMTRADE

FTP

Modbus

MV-90

SEL

Telnet Other (Write in) Downstream Connectivity Network Media Type Options Include:

None Wired, Copper Wired, Fiber Wireless Transport Protocol Options Include:

None Other Ethernet Non-IP Ethernet IP Non-Ethernet

RS-485

RS-232

ARCNET

Control Protocol Options Include:

DNP

IEC-61850

BACnet Lon Modbus N1 N2 etc.

Yes - The device has an embedded Operating System (It is NOT a full-blown computer)

Invensys: "I/A Series" Johnson Controls: "Metasys

IMPORTANT:

a. Where data is not available because it simply does not exist, such as the IP address of an unmanaged Ethernet switch, note this in the Comment field.

b. Where data does exist, but has not yet been gathered in the inventory process, leave data fields BLANK.

** The Data Collection Form has fields for entering information specific to switch port usage. While not required for the inventory, this is valuable information to have in developing your IT/OT implementation, and takes little extra effort to capture during the inventory. It is highly recommended that each FEC capture this data for local use.

DATA DICTIONARY

Inventory

Control System Inventory TEMPLATE Version 10.6, for Contractor use only, in association with new contruction or repair projects that involve control systems.

ICS INVENTORY DATA

Page &P of &N ENCLOSURE (1) iNFADSLKUP