22R0040 Attachment II - IT Vendor Info for Water Jet.docx

UNCLASSIFIED

Information Needed From Vendors to Start the Acquisition Process All information from the Vendor is to be provided in either .docx (Word 2013 or higher), .xlsx (Excel 2013 or higher), or .pdf (Adobe Acrobat). The Vendor should note that these are minimum documentation requirements and more may be required as the acquisition process progresses. Alternate deliverable files and/or formats must be approved by the Vendor’s DoD POC, first. Files shall not be encrypted and shall not require a password to open. If the information contained within must be protected in transit to the DoD, the Vendor shall utilize the DoD SAFE at https://safe.apps.mil after their DoD POC initiates a Drop-Off Request for them.

Hardware Bill of Materials Itemized list of all major components and subcomponents, complete with the name of their original equipment manufacturer (OEM) and part numbers.

Software Bill of Materials Itemized list of all major components and subcomponents, complete with version numbers. This includes any and all libraries contained within, or external to, the final binaries, firmware, and/or container. Table 1 provides a short example of the type of information required, but is truncated for the sake of brevity. Actual submissions are expected to contain many more entries due to the complexity of modern software. Operating systems (OS) typically provide a method to export a list of installed software. The Vendor may contact their DoD POC, provide the version of the OS in use, and ask for instructions on how to generate this list.

Table 1: Example Software Bill of Materials

Connection Diagram/Details Breakout diagram showing both proposed and possible connections to and from the system/device as well as connections between components of the system/device. This includes not just physical, but wireless connection methods as well. At minimum, this must be an itemized list of all physically possible connection ports, what they connect to, or could be connected to, what the connection is used for, and the communication protocols utilized (e.g., TCP/IP, RS-232, etc.). This may also be a combination of the two where an overall system connection diagram contains lists of sub-connections beside each major component. See Figure 1 for an example of a suitable diagram/description.

Figure 2: Example Connection Diagram

List of Ports and Protocols Itemized list of all data ports and protocols supported by the system. This section is intended to capture any information missed by the Connection Diagram/Details section. If a port, protocol, and/or service is critical to the functionality of the system, but is provided by external means (e.g., NTP, DNS, etc.) via the Operating System, it must be noted here. Table 2 provides a short example of the type of information required.

Table 2: Example List of Ports and Protocols

UNCLASSIFIED

image1.emf

Microsoft_Visio_Drawing.vsdx