Inventory_Spreadsheet_2017-12-07.xlsx
XLSX spreadsheet 42 KB Posted
- Attached to
- MATOC Federal contract opportunity
- Solicitation number
- W911S7-19-R-0008
About this file
This document contains an inventory spreadsheet for tracking networked devices and a federal contract opportunity notice. The inventory spreadsheet provides instructions for cataloging details of each networked device such as location, hardware specifications, operating systems, network connectivity information, and security posture. Fields are required to identify the device, installation, facility, room and specific location within the room. Additionally, details must be provided regarding hardware type, manufacturer, model, serial number, operating system, network protocols and addresses used, upstream and downstream connectivity, and security guidelines applied.
The related federal contract opportunity is a notice for a Multiple Award Task Order Contract for construction services. The North American Industry Classification System code is 236220 with a small business size standard of $36.5 million. The Product Supply Code is Y1AA for construction of office buildings. The place of performance is Fort Leonard Wood, Missouri and Lake of the Ozarks Recreational Area. This will be a total small business set-aside. A request for proposal will be issued on January 3, 2019 under solicitation number W911S7-19-R-0008 with quotes due February 4, 2019 for an indefinite delivery, indefinite quantity contract with firm fixed prices.
Inventory spreadsheet
View the file
Other files for this federal contract opportunity
Show all 38
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions
| Instructions: | |
| 1. | Complete all fields for each device that is connected to a network. |
| 2. | Do not leave blank cells: Provide the indicated information; Enter "N/A" or "NONE" if an entry is not applicable or not required; or Enter "<UNKNOWN>" if the information is required but not known. |
| Data Field | Required/Optional/If Applicable | Instructions/Description | Details | HQ/FEC Required | Optional | Restricted to FEC and select HQ/Ech III FTEs | FEC only | Partial FEC, partial HQ/Ech III FTEs | ||
| Identifier | Required | Device identifier used throughout the project documentation. | X | |||||||
| Device Location | Installation | Required | The name of the Installation | IA Required | X | |||||
| Special Area | Optional | Special area of the installation. | Helps Identify location | X | ||||||
| Facility Number or Identifier | Required | The facility number or identifier where the device is located. Typically a building number | IA Required | X | ||||||
| Facility Name or Description | Required | The facility name or description where the device is located. | IA Required | X | ||||||
| Floor | If Applicable | Floor in facility where device is located if applicable | IA Required | X | ||||||
| Room | Required | Room number, name or both where device is located. Example: "Mechanical Room 123", "Room 123", "Electrical Room" | IA Required | X | ||||||
| Location In Room | Required | Specific location of device in identified room. Examples: | ||||||||
| "Cabinet", "Brown Cabinet", "Back of Room", "On transformer" | X | |||||||||
| Enclosure / Mount Type | Required (for IP connected devices) | For devices connected to an IP network, indicate how the device is mounted. As one of the following: |
Locking Cabinet Non-Locking Cabinet Open, attached Open, loose Other (specify) UPS Power Required Indicate if the component is powered by a UPS using one of the following entries:
Yes - Local Yes - Building No
| Control System Info | Architecture Level | Required | Architecture level the device resides in based on the "5-LEVEL CONTROL SYSTEM ARCHITECTURE" described in UFC 4-010-06 (available at http://www.wbdg.org/ffc/dod/unified-facilities-criteria-ufc) | Used for prioritization during the approval process | X |
| Control System Type | Required | The control system type . Use the system types and abbreviations from the Facility Related Control System Master List (available at [_____]). If the system type is not included on that list, enter the system type. |
Note that control system network hardware should indicate the control system type that is it used for.
| Part of which UMCS | If Applicable (if known) | The name of the UMCS to which this component belongs to, or will belong to after future integration. | Used for prioritization during the approval process | X |
| Electrical/Mechanical system or equipment Controlled | If Applicable | For controllers, identify the specific real-world system, equipment or component which the listed device controls or monitors . Use the system, equipment or component identifier established by the control system drawings when applicable. | Required as other fields do not easily identify what the device does. | X |
HARDWARE DETAILS* Device Type Required Indicate the type of device as one of:
Controller Network Hardware Computer
| Other | Required as other fields do not easily identify what the device does. | X | |||||
| Device Sub-Type | Required | The specific device type as defined by the control system specification. Indicate the specification number, paragraph number and paragraph title where the product requirements for the device are specified. Use the specification paragraph that most specifically identifies the device. For example: "Section 23 09 23.02, Para 2.3, DDC Hardware" or "Section 23 09 23.01, Para 2.3.3, Application Specific Controller (ASC)" | Clarification for Device | X | |||
| Device Function | Optional | Provide further information for Device Type of "OTHER" when the Device Sub-Type or function of the device is unclear. | IA Required | X | |||
| Manufacturer | Required | Device Manufacturer | I/A Required. Part of model designation. | X | |||
| Product Line | If Applicable | Many inventory entries are part of a product line. Examples: |
Dell: "PowerEdge" Invensys: "I/A Series"
| Johnson Controls: "Metasys" | IA Required | X | |||||
| Model # | Required | Device Model Number | IA Required | X | |||
| Serial # | Required (for Computer and Other) | Device Serial Number. Required only for Device Types of Computer or Other | IA Required | X | |||
| OPERATING SYSTEM & PLATFORM | Type of Operating System (OS) | Required | Indicate the type of OS as one of: |
Normal - The device is a "full-blown" computer Embedded - The device is NOT a "full-blown" computer, but has an OS distinguishable from the application None - The device lacks an OS distinguishable from the application.
| For NONE, the Following 3 questions are all N/A | I/A Required | X | |||||
| OS Vendor | If Applicable | Provide the O/S Vendor Name, such as "Microsoft" or "Red Hat" | IA Required | X | |||
| OS Name | If Applicable | Provide the underlying operating system for the device. In the case of embedded controllers this will not always be known. For servers it is the flavor of Windows or Linux, etc. For embedded controllers it is the base O/S, such a QNX or Windows XP | IA Required | X | |||
| OS Version | If Applicable | Provide the version of the O/S | I/A Required | X | |||
| Platform | Platform Vendor | If Applicable | If the application (platform) is distinct from the hardware or OS, then provide platform information even if the same as other answers. If the application is NOT distinct from the hardware or OS, then enter "N/A" for the "Platform" fields. | I/A Required (Part of Platform designation) | X | ||
| Platform Product Line | If Applicable | Many inventory platform entries are part of a product line. Examples: |
Invensys: "I/A Series"
| Johnson Controls: "Metasys" | IA Required | X | |||||
| Platform | If Applicable | Provide the name of the platform(s) running on top of the O/S. This will not always be known, and would include the application(s) being run on a server or embedded device such as Niagara, Metasys, Telvent, etc. | IA Required | ||||
| Platform Version | If Applicable | Provide the platform version | Needed for active Enclave management, full MAC retained by FEC. Minimum of first three octets will be submitted to HQ for verification against manufacturer. | X |
Sole or Upstream Network Connectivity Control Protocol Required Indicate the control protocol used for upstream connectivity or the control protocol used by a device having only a single network connection. Specify the protocol using the following list:
LonWorks (CEA 709.1) BACnet Fox
DNP 3.0
IEC-61850
C37.118
COMTRADE
Modbus
MV-90
SEL
Other (describe) MAC Address(es) Required Indicate the MAC address (or equivalent) for the Sole or Upstream connection. There will be one unique MAC address for each connected network port. Protocol specific guidance:
LonWorks: Provide Node ID BACnet MS/TP: RS-485 address BACnet/IP: <IP address>:<UDP Port>
| Ethernet: MAC address | IA Required | X | |||
| Network Address | Required | For IP connected devices, indicate the IP address. For other devices, indicate the protocol-specific network address. | |||
| Network Media Type | Required | Indicate the network media type. |
Examples:
For IP connected devices :
Ethernet For non-IP devices:
RS-485
BACnet MS/TP LonWorks TP/FT-10 LonWorks TP/XF-1250 Second or Downstream Connectivity Control Protocol If Applicable Indicate the control protocol used for doiwnstream connectivity or the control protocol used by a device having only a second network connection. Specify the protocol using the following list:
LonWorks (CEA 709.1) BACnet Fox
DNP 3.0
IEC-61850
C37.118
COMTRADE
Modbus
MV-90
SEL
Other (describe) MAC Address(es) If Applicable Indicate the MAC address (or equivalent) for the Second or Downstream connection. There will be one unique MAC address for each connected network port. Protocol specific guidance:
LonWorks: Provide Node ID BACnet MS/TP: RS-485 address BACnet/IP: <IP address>:<UDP Port> Ethernet: MAC address
| Network Address | If Applicable | For IP connected devices, indicate the IP address. For other devices, indicate the protocol-specific network address. |
| Network Media Type | If Applicable | Indicate the network media type. |
Examples:
For IP connected devices :
Ethernet For non-IP devices:
RS-485
BACnet MS/TP LonWorks TP/FT-10
| LonWorks TP/XF-1250 | Required to manage Enterprise IP ranges and VLANs. | X | ||
| Upstream Device | If Applcable | Indicate the upstream device this device communicates with or through to communicate with the next higher architecture level. |
| Note that for devices communciating through a control protocol gateway, the control protocol gateway is the upstream device. Otherise the upstream device with typicall be the device at the next higher architecture level which connects to this device's network. | I/A Required | X | |||||
| Hostname | If Applicable | Provide the hostname of the device, if known. | |||||
| Ethernet LAN Type | Required (For IP Devices) | For IP devices only, indicate whether the Ethernet network is a VLAN on another network or a dedicated LAN by entering the VLAN identifier or the word "Dedicated". (For all other devices enter N/A) | |||||
| I/A Required | X | ||||||
| Device Hardening | Network or security scan information | Required | Indicate date and type of scan performed on the device, or indicate "NONE" if the device has not been scanned. | IA Required | X | ||
| Apoplicable STIGs/SRGs | Required | Indicate the Security Technical Implementation Guidance (STIGs) and the Security Requirements Guides (SRGs) which are APPLICABLE to the device (regardless of whether or not they were implemented for the device). If there are no applicable STIGs/SRGs, indicate "NONE". | I/A Required | X | |||
| STIGs/SRGs NOT Applied | Required | Indicate the STIGs/SRGs which are applicable to the device but which have NOT been implemented. If there are no applicable STIGs/SRGs or all applicable STIGs/SRGs have been applied, indicate "NONE ". | X | ||||
| Comments on STIG/SRG | Optional | Provide any comments or additional details regarding application of STIGs/SRGs to the device. |
Comments Provide any comments or additional details regarding the device.
DATA DICTIONARY
Data Sheet
| Device Location | Control System Info | HARDWARE DETAILS | OPERATING SYSTEM & PLATFORM | Platform | Sole or Upstream Network Connectivity | Second or Downstream Connectivity | Device Hardening | |||||||||||||||||||||||||||||||||||||
| Identifier | Installation | Special Area | Facility Number or Identifier | Facility Name or Description | Floor | Room | Location In Room | Enclosure or Mount Type | UPS Power | Architecture Level | Control System Type | Part of which UMCS | Electrical/Mechanical System or Equipment Controlled | Device Type | Device Sub-Type | Device Function | Manufacturer | Product Line | Model # | Serial # | Type of Operating System (OS) | OS Vendor | OS Name | OS Version | Platform Vendor | Platform Product Line | Platform | Platform Version | Control Protocol | MAC Address(es) | Network Address | Network Media Type | Control Protocol | MAC Address(es) | Network Address | Network Media Type | Upstream Device | Hostname | Ethernet LAN Type | Network or security scan information | Applicable STIGs/SRGs | STIGs/SRGs NOT Applied | Comments on STIG/SRG | Comments |
File details come from the government source that posted it. Updated .