5.1. The PM will establish a project plans for the data dictionary and Proposed High-Level UAM and UBA Enterprise Solution Technical Requirements within 30 days of onboarding. The PM will work with the Government to establish key milestones and deadlines.
5.2. Data Dictionary
5.2.1. Data Dictionary. At the direction of government, the team will define a data dictionary for each of the items described in the DHS Insider Threat Sharing Guide 262-05-002-01. The Contractor shall deliver documentation of its process for this task to the Government within 21 days after contract award.
5.2.2. The Contractor shall identify all databases, at each DHS component, that are described in the DHS Insider Threat Sharing Guide 262-05-002-01
5.2.3. Develop a data dictionary that will contain but is not limited to; type and variation of field format from defined data specification, type and variation of valid values from data specification, number of rows submitted by data element/layer/table/text file.
5.2.4. A Data Dictionary is typically organized in a spreadsheet format. Each attribute is listed as a row in the spreadsheet and each column labels an element of information that is useful to know about the attribute. The Contractor will provide a common data format that will be easy to review and implement.
5.2.5. No proprietary tools, software, or applications shall be used unless approved by the COR.
5.2.6. Determine the network route from each component to the DHS ITP to ensure proper delivery of data sets.
5.2.7. The deliverable will be a network diagram accompanied by an associated white paper for each component to explain movement of the data.
5.2.8. The Contractor shall deliver proposed common data dictionary format; once the proposed format has been approved the Contractor will provide a common data dictionary format for all items related to the DHS Insider Threat Sharing Guide 262- 05-002-01 which will be easy to review and implement.
5.3. Current Architecture
5.3.1. At the direction of the government the team will review the current ITP technical architecture. This will help ensure a foundation of the current architecture to better help define gaps and vulnerabilities.
5.4. Proposed High-Level UAM and UBA Enterprise Solution Technical Requirements
5.4.1. Prepare and present formal design documentation, including drawings, plans, spreadsheets, and specifications that address the future needs and support the approved design objectives. Provide draft copies for review and comment.
22.214.171.124. Make recommendations on design objectives for the ITP network architecture.
126.96.36.199. At the direction of the government provide an OV1 overview
188.8.131.52. Objectives must support reliability of business operations and data storage, increased protection against cyber security threats, and increased accessibility, flexibility, and expansion.
184.108.40.206. This includes but is not limited to; proposed local network topologies, physical network topologies, security architecture, VLAN segmentation, OnPremise storage, and Cloud-based storage
220.127.116.11. At the direction of government, the team will provide an architectural solution for a data repository to hold data while following the NARA guidelines.
18.104.22.168. The contractor shall design and present a plan for an integrated data storage solution that will work in conjunction with all of DHS’s UAM/UBA databases
22.214.171.124. The Contractor shall design and present a plan for an integrated enterprise disaster recovery/backup solution
“7 Period of Performance
7.1. The contract period of performance is a twelve (12) month base period with four (4) 12-month option periods from September 20, 2021 to September 19, 2026…”
XFactor Members access the complete set of documents here.
To register for a free XFactor trial, read more here.