CPWSv3-12_-_Update_20_May_2013.pdf

PERFORMANCE WORK STATEMENT

FOR

ENTERPRISE ARCHITECTURE, DATA, AND ENGINEERING

Version 3.12, 27 Feb 13

Prepared by

UNITED STATES TRANSPORTATION COMMAND

DIRECTORATE OF COMMAND, CONTROL, COMMUNICATIONS & COMPUTER SYSTEMS

DRAFT

Table of Contents

1. DESCRIPTION OF SERVICES

1.1. Background

1.2. Scope

1.3. Requirements

1.3.1. Task 1 ‐ Contract Management

1.3.2. Task 2 ‐ Enterprise Architecture Development and Maintenance

1.3.3. Task 3 – Data Management

1.3.4. Task 4 ‐ Enterprise Architecture Tools

1.3.5. Task 5 ‐ Enterprise Engineering Support

1.3.6. Task 6 ‐ Alternate Functional Area Communications & Computer Systems Manager

(FACCSM) Duties

1.3.7. Task 7 ‐ Information Support Plan (ISP)/Tailored Information Support Plan (TISP)

1.3.8. Task 8 ‐ Agile Development (OPTIONAL)

1.3.9. Task 9 ‐ Prototyping (OPTIONAL)

1.3.10. Task 10 ‐ Economic Analysis ................................................... Error! Bookmark not defined.

1.3.11. Deliverable Schedule

2. SERVICE DELIVERY SUMMARY

3. GOVERNMENT FURNISHED EQUIPMENT (GFE)/GOVERNMENT FURNISHED

INFORMATION (GFI)

4. GENERAL INFORMATION

4.1. Handling of Non‐Public Information

4.2. Software and Data Rights

4.3. General Contractor Information

4.3.1. Contract Manager

4.3.2. Contractor Employees

4.3.3. Continuity of Operations (COOP)

4.3.4. Privacy Act

4.3.5. Quality Assurance

4.3.6. Place of Performance

4.3.7. Period of Performance

4.3.8. Travel

4.3.9. Inspection and Acceptance Criteria:

4.3.10. Packaging, Packing and Shipping Instructions

4.3.11. Contractor Proposed ODC

4.3.12. Government Proposed ODC

4.3.13. Conference ODC

4.3.14. Nondisclosure Agreement for Contractor Employees

4.3.15. Performance of Services during Crisis Declared by the President or Secretary of Defense up to and including War

4.3.16. Contractor Transition

4.3.17. Invoicing Procedures

4.3.18. Policy compliance

4.4. Security: Physical, Personnel, Information, Antiterrorism/Force Protection and Industrial

Security

4.4.2. IT‐II/ADP‐II/Non‐Critical Sensitive Positions

4.4.3. (IT‐II/ADP‐II/Non‐Critical Sensitive) Background Investigation Requirements

4.4.4. IT III/ADP III/Non‐Sensitive Positions

4.4.5. (IT‐III/ADP‐III/Non‐Sensitive) Background Investigation Requirements

4.5. Facilities Clearance Level

4.6. Personnel and Facilities Clearance Validation

4.7. Common Access Card Issuance Procedures

4.8. Scott Air Force Base/USTRANSCOM Physical Access

4.8.1. Restricted Area Badge

4.8.2. Facility Access Requirements

4.9. Visits to USTRANSCOM/SDDC Building

4.10. Additional Security Conditions

4.10.1. Security Training

4.10.2. Post Contract Security Actions

4.10.3. Derogatory Information

4.10.4. Accessing NATO Information

4.10.5. Security Debriefing

5. APPENDICES

5.1. A ‐ References

5.2. B ‐ Acronyms

5.3. C ‐ Applicable Documents

5.4. Nondisclosure Agreement

5.5. Operating Systems/Software/Applications Used

1. DESCRIPTION OF SERVICES

1.1. Background

The mission of the United States Transportation Command (USTRANSCOM) is to develop and direct the Joint Deployment and Distribution Enterprise to globally project strategic national security capabilities; accurately sense the operating environment; provide end-to-end distribution process visibility; and responsive support of joint, US government and Secretary of Defense-approved multinational and non-governmental logistical requirements.

The USTRANSCOM’s Directorate of Command, Control, Communications & Computer Systems (TCJ6) is responsible for long-range planning, policy guidance, direction, technical, control, and program management for projects involving the development and implementation of major transportation management systems Department of Defense (DOD)-wide.

The USTRANSCOM Directorate of Acquisitions (TCAQ) is responsible for partnering with industry and customers to develop and execute innovative acquisition solutions supporting the Command's full-spectrum, deployment and distribution mission. The Distribution Process Owner Division (TCAQ-D) provides responsive, flexible contracting support for USTRANSCOM DPO initiatives and Surface Deployment and Distribution Command National Level Transportation System requirements. Support includes, but is not limited to, commercial and non-commercial software development and related support services; Advisory and Assistance Services, management support services, ancillary support services; classified and unclassified network support, and Research and Development. Its major programs are: Agile Transportation for the 21st Century (AT21), Integrated Booking System (IBS), Global Freight Management (GFM), Defense Personal Property System (DPS), Enterprise Support Services (ESS), System Response Call Center, Total Supply Chain Process Improvement, Joint Distribution Process Analysis Center (JDPAC), Program Management Office (PMO) Support, Corporate Services Support (CSS), Integrated Computerized Deployment System (ICODES) and Automatic Identification Technology (AIT) Support.

The mission of the US Air Force Air Mobility Command Directorate of Command, Control, Communications, and Computer Information Systems (AMC/A6) is to provide integrated Command, Control, Communications, and Computer Information (C4I) systems and manage strategic C4I resources in support of AMC's global air mobility mission. AMC/A6CI manages the integration of the communications-computer systems via enterprise-wide planning, systems engineering, architecture development, and interoperability processes. AMC/A6CI ensures technical solutions for AMC C4I systems are in compliance with DOD, USTRANSCOM, US Air Force, and joint architecture and integration goals. AMC/A6CI is responsible for two separate interoperability roles: Air Force (appropriation funded) and Joint (Transportation Working Capital Funds).

The mission of the Military Surface Deployment and Distribution Command Communications Directorate (SDDC G6) is to manage the integration of the communications-computer systems via enterprise-wide planning, systems engineering, architecture development, and interoperability processes. SDDC G6/IMA Enterprise Services Branch provides the enterprise architecture, data integration, and engineering support which drives capability-based technical solutions within the command and ensures SDDC systems comply with DOD, USTRANSCOM, US Army, and joint architecture and integration strategies and objectives.

To achieve greater efficiencies and collaboration, the Government decided to combine the USTRANSCOM Enterprise Architecture (EA) (including data management and architecture tools), and enterprise engineering contracts with the equivalent AMC and SDDC contracts. The EA data currently resides in three independent repositories, managed by three independent tools.

With this consolidated contract, the Government expects an integrated architecture tool suite.

1.2. Scope

This Performance Work Statement (PWS) is to acquire EA and information technology engineering services for USTRANSCOM, AMC/A6, and SDDC’s Automated Transport Systems Division (AMSSD-IMA), all located at Scott AFB, IL.

This PWS procures an integrated enterprise architecture from the enterprise level down through the solution level and across solution level architectures. Integration is achieved through the architecture tool suite, the use of standardized templates and guidelines, training, and the architecture review process. The work effort will support analytical services required to support and implement USTRANSCOM, AMC and SDDC operational and system requirements solutions. The Contractor must possess a comprehensive understanding of the DOD Architecture Framework (DODAF), the Federal Enterprise Architecture Framework (FEAF) and the relationships/dependencies between architecture models to support assigned projects. The scope of the architecture and data management services contained in this PWS includes the operational and system perspectives of Command and Control (C2), planning, transportation, logistics, and business support system domains. Using established strategic vision documentation, the Contractor will provide architecture and data management support. This allows Government personnel to conduct impact analysis on the enterprise, systems of systems, and individual system levels. Systems administration of the tools that house the architecture and data artifacts is also required.

1.3. Requirements

1.3.1. Task 1 - Contract Management (FFP CLIN)

This task consists of functional activities relating to administration and management of this effort. The Contractor shall provide program management of Contractor personnel performing tasks in this order. The Contractor shall designate a principal point of contact for technical issues. The Contractor shall provide a centralized program management capability. This function shall encompass administrative, clerical, documentation and related functions that provide general support for the program. The Contractor shall provide support by preparing documents such as briefings, point papers, and meeting minutes related to the status of the performance of this task order. This task will span the entire duration of the contract.

1.3.1.1. Monthly Cost/Status and Resource Utilization Reports

The contractor shall provide a Monthly Status Report (MSR) to the Government no later than the 10th business day of the following month. The MSR shall list, by each active task/project area, the accomplishments of the reporting period. The MSR should outline a brief synopsis of the efforts completed, deliverables provided, and conferences and trips conducted/attended during the reporting period, and an overall evaluation of the PWS to date. The report shall list for each task any issues, problem areas, and items that require Government action. The final MSR shall be submitted no later than the last business day of the final period of performance

Deliverable: Monthly Cost/Status, Resource Utilization Report,

1.3.1.2. Weekly Activities Report (WAR)

The Contractor shall provide (2) separate (EA & Eng) WARs detailing significant events to the Contracting Officer Representative (COR).

The WAR shall be a Microsoft Office soft copy product covering project status, any risks and recommended solutions, status of previously identified issues, and any significant events for the previous week. The contractor shall provide the WAR to the Government no later than the second business day of the following week.

Deliverable: EA WAR, Enterprise Engineering WAR

1.3.1.3. Work Progress Review Meeting

The Contractor shall brief the COR on the status of ongoing and anticipated future projects weekly. As part of the status, the Contractor shall identify what Contractor personnel are assigned to specific projects and estimated completion dates.

Deliverable: Work progress review meeting

1.3.1.4. In-Progress Review (IPR)

The contractor shall conduct quarterly IPRs with the Functional Task Leads and COR during the contract meeting or as required by COR. The IPR shall summarize status, progress, recommendations, and concerns in the development of any tasks or documentation described within this PWS. Presentation materials shall be prepared and provided to the COR two (2) business days prior to the IPR. The presenting format shall be determined by the sponsoring (ordering) agencies. The IPR shall cover:

Current project status and/or development effort under this PWS

Summary of accomplishments to date

Risks and mitigation strategy for each risk

Schedule delays, cause and corrective actions

Current funds expended to date (chart with trend line-burn rate)

Unexecuted funds to date (chart with trend line-burn rate)

Plans for the next three (3) calendar months

Deliverable: IPR and presentation materials

1.3.1.5. Trip Reports

The contractor shall submit a trip report within five (5) business days of completion of any approved travel. The contractor shall submit the trip report to include the following details:

purpose, location, length of trip, travelers, and actual travel costs, individuals contacted during trip, synopsis of all discussions, future actions identified, decisions made, and issues of concern arising during the trip.

Deliverable: Trip Report

1.3.1.6. Meeting/Conference Minutes

The contractor shall attend meetings or conferences held at USTRANSCOM or other locations as identified by the Government. When directed by the Government, the contractor shall provide meeting/conference notes/minutes within two (2) days of attendance meeting/conference minutes that detail the results as well as the impact of the meetings/conferences. We estimate two (2) Chief Architect meeting forums per year. Meetings/Conferences shall generally take place during the normal duty hours but can extend beyond these core hours, e.g., information breach.

The Contractor shall attend and participate in Technical Exchange Meetings (TEMs) with the Government as well as various Government and private national forums to demonstrate and present enterprise architecture development challenges, lessons learned and ways-ahead. As required, the Contractor shall create demonstrations, presentations, and information exchange sessions. All materials produced by the Contractor shall be reviewed and pre-approved by the COR. This review includes the proper marking of briefing materials and appropriate disclosure.

Workload is estimated at one (1) TEM per month and one (1) conference or forum per quarter.

Deliverable: Presentation materials, meeting minutes

1.3.1.7 Enterprise-wide Contractor Manpower Reporting Application (eCMRA) Reporting

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for US Transportation Command via a secure data collection site. The contractor is required to completely fill-in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the CMRA help desk.

1.3.2. Task 2 - Enterprise Architecture Development and Maintenance (CLIN type designated at Sub-task Level)

1.3.2.1. Document Architectures (FFP Task)

1.3.2.1.1.1. The Contractor shall document enterprise and solution level architectures supporting USTRANSCOM, AMC, and SDDC missions. The architectures will include the scope for C2, planning, transportation, logistics, and business systems domains. (e.g., exercise, experiment, and advanced technology demonstrations, and system-focused “as-is” and “to-be” architecture models). The Contractor shall adhere to Government-specified style guides, approved taxonomies, architecture implementation guides and element lists. Within the architecture, the Contractor shall document the design of critical links in DODAF architecture model formats, to include the linkage between models and related architectures. The Contractor shall reuse existing architecture data/views to minimize development cost and schedule, and maintain configuration control of architectural artifacts and the underlying models. The Contractor shall capture and store USTRANSCOM, AMC, SDDC performers, activities (functions), business process rules, information exchanges, data exchanges, data elements, and Data Dictionaries in the tools identified in Section 3.

1.3.2.1.2. Research Documentation for Existing Architectures

The Contractor shall review published guidance identified in Section 3 as the initial source to gain an understanding of processes, systems, organizations, etc. that will influence architectural development efforts. The COR will identify other published guidance relevant to each architecture development effort.

Deliverable: DoDAF architecture views, overview and summary information

1.3.2.1.3. Conduct Interviews for Existing Architectures

The Contractor shall conduct interviews with subject matter experts, sponsors, and participating organizations prior to and during architecture development. This iterative process requires the

Contractor to obtain information from the business operations communities to develop the architecture views.

Deliverable: DoDAF architecture views

1.3.2.1.4. Identify Primitives for Existing Architectures

The Contractor will review primitives (e.g., performers, systems, system functions, activities, information exchanges, business rules, data exchanges and data elements) identified while researching documentation (Para 1.3.2.1.1) and conducting interviews (Para 1.3.2.1.2) to determine whether or not these primitives exist within the government designated enterprise architecture tool environment. If the primitives don’t exist, the Contractor shall propose the primitives to the COR for approval.

Deliverable: DoDAF architecture views, architecture primitives

1.3.2.1.5. Scope and Assemble Primitives into Architecture Views for Existing Architectures

The Contractor shall collect, organize, correlate, and store the architecture data required for architecture development and document the architectural results in the government designated enterprise architecture tool environment following government approved procedures. The Contractor shall support primitive registration, architecture model construction, and architecture markup/coordination, using government-provided tools in Section 3. This includes using multiple architecture modeling techniques (e.g., Entity Relationship Modeling, Swimlane Process Mapping, Functional Decomposition Tree Modeling, Business Process Modeling Notation (BPMN), Data Flow Modeling, Integrated Definition for Functional 0 (IDEF0) modeling, IDEF1X modeling, Event Trace Modeling, Dependency Analysis Modeling, Semantic Net Modeling, Unified Modeling Language (UML) techniques, etc.), and engineering techniques such as use cases. The Contractor shall mature the architecture views throughout the review and approval process and ensure all architecture artifacts produced comply with DODAF and Government approved templates and guidelines.

Deliverable: DoDAF architecture views

1.3.2.1.6. Resolve Discrepancies for Existing Architectures

The Contractor shall identify all architecture discrepancies during architecture model development and review processes. Obtaining Government approvals as necessary, the Contractor shall document the actions taken to resolve and adjudicate the discrepancies and provide a Monthly Discrepancy Report to the COR. The report may be in a format selected by the Contractor. The monthly report due date will be determined by the COR and may vary between one (1) to ten (10) business days.

Deliverable: Discrepancy and Resolution Report

1.3.2.1.7. Maintain Reference Models for Existing Architectures

The Contractor shall review the existing reference models and suggest modifications to the COR.

Upon approval of suggested changes by the COR, the Contractor shall implement changes. As required by the COR, the Contractor shall refine existing, or develop new, reference models which may include the development of ontology’s and taxonomies. Examples of reference models include, but are not limited to the the Joint Capability Areas (JCAs), Plan-Order-Ship- Track-Pay (POST-P), Joint Common System Function List (JCSFL), and Supply Chain Operations Reference (SCOR) Model. . Reference model modifications may occur as part of the architecture development process.

Deliverable: Suggested reference model changes

1.3.2.2. Develop New Architectures (LH Task)

1.3.2.2.1 Research Documentation for New Architectures

The Contractor shall review published guidance identified in Section 3 as the initial source to gain an understanding of processes, systems, organizations, etc. that will influence architectural development efforts. The COR will identify other published guidance relevant to each architecture development effort.

Deliverable: Architecture views, overview and summary information

1.3.2.2.2. Conduct Interviews for New Architectures

The Contractor shall conduct interviews with subject matter experts, sponsors, and participating organizations prior to and during architecture development. This iterative process requires the Contractor to obtain information from the business operations communities to develop the architecture views.

Deliverable: DoDAF architecture views

1.3.2.2.3. Identify Primitives for New Architectures

The Contractor will review primitives (e.g., performers, systems, system functions, activities, information exchanges) identified while researching documentation (Para 1.3.2.1.1) and conducting interviews (Para 1.3.2.1.2) to determine whether or not these primitives exist within the government designated enterprise architecture tool environment. If the primitives don’t exist, the Contractor shall propose the primitives to the COR for approval.

Deliverable: DoDAF architecture views, architecture primitives

1.3.2.2.4. Scope and Assemble Primitives into Architecture Views for New Architectures

The Contractor shall collect, organize, correlate, and store the architecture data required for architecture development and document the architectural results in the government designated enterprise architecture tool environment following government approved procedures. The Contractor shall support primitive registration, architecture model construction, and architecture markup/coordination, using government-provided tools in Section 3. This includes using multiple architecture modeling techniques (e.g., Entity Relationship Modeling, Swimlane Process Mapping, Functional Decomposition Tree Modeling, Business Process Modeling Notation (BPMN), Data Flow Modeling, Integrated Definition for Functional 0 (IDEF0) modeling, IDEF1X modeling, Event Trace Modeling, Dependency Analysis Modeling, Semantic Net Modeling, Unified Modeling Language (UML) techniques, etc.), and engineering techniques such as use cases. The Contractor shall mature the architecture views throughout the review and approval process and ensure all architecture artifacts produced comply with DODAF and Government approved templates and guidelines.

Deliverable: DoDAF architecture views

1.3.2.2.5. Resolve Discrepancies for New Architectures

The Contractor shall identify all architecture discrepancies during architecture model development and review processes. Obtaining Government approvals as necessary, the Contractor shall document the actions taken to resolve and adjudicate the discrepancies and provide a Monthly Discrepancy Report to the COR. The report may be in a format selected by the Contractor. The monthly report due date will be determined by the COR and may vary between one (1) to ten (10) business days.

Deliverable: Discrepancy and Resolution Report

1.3.2.2.6. Develop Reference Models for New Architectures

The Contractor shall review the existing reference models and suggest modifications to the COR.

Upon approval of suggested changes by the COR, the Contractor shall implement changes. As required by the COR, the Contractor shall refine existing, or develop new, reference models which may include the development of ontology’s and taxonomies. Examples of reference models include, but are not limited to the the Joint Capability Areas (JCAs), Plan-Order-Ship- Track-Pay (POST-P), Joint Common System Function List (JCSFL), and Supply Chain Operations Reference (SCOR) Model. . Reference model modifications may occur as part of the architecture development process.

Deliverable: Suggested reference model changes, new reference models

1.3.2.3. Architecture Configuration Management (FFP Task)

The Contractor shall provide administrative support to the Government configuration management process. The Contractor shall schedule, arrange and set-up a facility, prepare a draft agenda, and compile presentation materials for the Configuration Control Boards (CCB).

The Contractor shall provide draft agendas to the COR for approval no later than (5) business days prior to the CCB. The Contractor shall provide minutes of each CCB to the COR no later than five (5) business days after each meeting. Meetings shall be held on a quarterly basis or as required by the COR.

Deliverable: CCB agendas, presentation materials, minutes

1.3.2.4. Architecture Liaison (FFP Task)

1.3.2.4.1. The Contractor shall review architectures from a process or operations perspective.

The Contractor shall facilitate the modification, update, documentation, and coordination of architecture views and artifacts within the operations communities for existing systems. The Contractor shall assist the Government in assessing deployment and distribution challenges, recommending new business rules, and enabling better resource allocation decisions while improving delivery of forces and sustainment to desired points of effect. The Contractor shall provide analyses and recommendation reports by Government directed topic on business process improvement proposals and new business operations requirements documents involving materiel and personnel deployment, distribution, and sustainment operations. The format for analyses and recommendations will be determined by the Government and may include, but is not limited to point papers, white papers, and briefing slides. The Contractor shall also provide operational architecture artifacts to support requirements proposals. The Contractor shall provide analyses and recommendations and operational architecture artifacts quarterly or as required by the COR.

Deliverable: Analyses and recommendation reports, DoDAF architecture artifacts

1.3.2.4.2. The Contractor shall review architectures from a process or operations perspective.

The Contractor shall facilitate the modification, update, documentation, and coordination of architecture views and artifacts within the operations communities for new systems and initiatives. The Contractor shall assist the Government in assessing deployment and distribution challenges, recommending new business rules, and enabling better resource allocation decisions while improving delivery of forces and sustainment to desired points of effect. The Contractor shall provide analyses and recommendation reports by Government directed topic on business process improvement proposals and new business operations requirements documents involving materiel and personnel deployment, distribution, and sustainment operations. The format for analyses and recommendations will be determined by the Government and may include, but is not limited to point papers, white papers, and briefing slides. The Contractor shall also provide operational architecture artifacts to support requirements proposals. The Contractor shall provide analyses and recommendations and operational architecture artifacts quarterly or as required by the COR.

Deliverable: Analyses and recommendation reports, architecture artifacts

1.3.2.5. Review Architectures (LH Task)

1.3.2.5.1. The Contractor shall conduct architecture reviews for externally developed (non- USTRANSCOM/AMC/SDDC) architectures as required by the COR. The Contractor shall record all concerns identified during the architecture review in a comments matrix, in the format provided by the Government, and provide the completed comments matrix to the COR. External architecture reviews are estimated at ten (10) per fiscal year for USTRANSCOM. External architecture reviews are estimated at two (2) for AMC. The due dates for the comments matrices will be determined by the COR and may vary between one (1) to ten (10) business days.

Deliverable: Comments matrices

1.3.2.6. Conduct Architecture Analysis (LH Task)

1.3.2.6.1. The Contactor shall perform analysis of architecture projects by using graphical, statistical, and document-based techniques. The Contractor shall perform enterprise impact analysis of operational, system, and programmatic changes as required by the COR. The analysis consists of reviewing internally/externally developed architectures for potential linkage and/or integration with DOD, USTRANSCOM, Component, Army, or Air Force architectures.

For example, the analysis includes activities such as comparing performers, need lines, resource flows, activities, system interfaces/exchanges, and technical standards in the parent architecture and/or system-focused/program architectures to the architecture being reviewed. Analysis may also include assessments and roadmap/migration planning documentation to provide users with accurate, complete, and concise architecture information. After the conclusion of each analysis project, the Contractor shall provide the enterprise impact analysis to the COR. Assessments and recommendations may be in the format of comment matrix, reports, point papers, talking papers, emails, or presentations. Requests for architecture analysis are estimated at four (4) per fiscal year. The due dates for the analysis documentation will be determined by the COR and may vary between one (1) and ten (10) business days.

Deliverable: Enterprise Architecture impact analysis documentation

1.3.2.6.2. Enterprise Requirements and Review Analysis. The Government will identify enterprise information requirements for review and analysis. The Contractor shall support a team approach which uses the enterprise architecture to evaluate potential requirements for gaps and redundancies. The Contractor shall support this approach by reviewing enterprise information requirements documents to evaluate the linkage to the existing architecture. As the needs are (re-)defined, the Contractor shall use the architecture views as developed in Task 2 (Para 1.3.2.1) to model/illustrate the requirement. Additionally the Contractor shall assist the Government in developing Courses of Action and use cases. Requests for architecture analysis of enterprise information requirements are estimated at twenty (20) per fiscal year. Upon completion of the analysis for each enterprise information requirement, the Contractor shall provide inputs to the COR. The suspense for inputs will be determined by the COR. The due dates will be relayed to the Contractor by the COR and can vary between two (2) and twenty (20) business days depending on the urgency and complexity of the requirement.

Deliverable: Architecture Analysis

1.3.2.6.3. Enterprise Architecture Support for Existing System Business Case Analysis (BCA).

The Contractor shall provide architecture support for USTRANSCOM business case analysis efforts for existing systems. Requests for government approved BCA support is estimated at three (3) per fiscal year. For each Government approved BCA, the Contractor shall provide a Rough Order of Magnitude (ROM) on manpower resources required prior to perform the architecture analysis. When developing the BCA, the Contractor shall use the existing architecture to perform the analysis. Once complete, the deliverable will be submitted to the COR. The due dates for the analysis will be determined by the COR and can vary between five

(5) and fifteen (15) business days.

Deliverable: Architecture analysis

1.3.2.6.4. Enterprise Architecture Support for New System Business Case Analysis (BCA).

The Contractor shall provide architecture support for USTRANSCOM business case analysis efforts for new systems and initiatives. Requests for government approved BCA support is estimated at three (3) per fiscal year. For each Government approved BCA, the Contractor shall provide a Rough Order of Magnitude (ROM) on manpower resources required prior to perform the architecture analysis. When developing the BCA, the Contractor shall use the existing architecture to perform the analysis. Once complete, the deliverable will be submitted to the COR. The due dates for the analysis will be determined by the COR and can vary between five

(5) and fifteen (15) business days.

Deliverable: Architecture analysis

1.3.2.7. Information Resource Catalogue (IRC). The Contractor shall collect and maintain information about the automated information systems used by USTRANSCOM/AMC/SDDC to conduct their respective missions. The Contractor shall provide monthly status as part of the Monthly Cost/Status and Resource Utilization Report to the COR identifying any updates and/or changes that have been incorporated into the IRC. Contractor shall collect and maintain the information below:

Application type

Functional area

Security level

Initial operational capability date and full operational capability date, if available

Data system designator and system identifier as applicable

Description

Migration information

Planned upgrades

Technology/platforms

Interfaces with other systems

1.3.3. Task 3 – Data Management (LH Tasks)

1.3.3.1. USTRANSCOM Enterprise Data Quality (DQ)

The Contractor shall provide data quality support. The Contractor shall identify Enterprise DQ issues that are reported by programs or business operations customers. The Contractor shall assist programs/services to resolve data quality problems with external legacy databases, multiple systems or services. The Contractor shall elevate issues through the COR to the DQ Working Group (DQWG), if needed. The Contractor shall identify proactive DQ issues through the active monitoring and problem resolution of non-compliant data. In the current environment this monitoring will be accomplished using multiple software tools identified in Section 3, Paragraph 1.

1.3.3.1.1. Operational Data Transaction Assessments

The Contractor shall develop for COR approval DQ business rules and procedures ensuring timely and accurate transmission of data using the six characteristics of DQ (Accuracy, Completeness, Consistency, Timeliness, Uniqueness, and Validity). The DQ business rules shall be delivered to the COR and will be stored in a common tool(s), using a methodology consistent with the published USTRANSCOM Data Strategy. For environments where the Contractor can monitor online transactions, the Contractor shall develop and receive automated alerts via dashboards to the Enterprise DQ Office. The alerts will identify errors during data transmission or errors detected in critical data. The Contractor shall prepare draft Memorandums of Agreement (MOAs) between the DQ Office and the programs that describe their agreement on how to identify and resolve data quality issues. The Contractor shall baseline the data and identify potential business process improvements, system changes, or process workarounds to achieve and improve data quality. The due dates for the draft MOAs will be determined by the COR and can vary between five (5) and fifteen (15) business days. DQ business rules shall be delivered to the COR for approval within 30 days after contract start and updated as required.

Deliverable: DQ Business Rules, Draft MOAs

1.3.3.1.2. Operational Metrics

The Contractor shall interact with the various business operations organizations or systems to identify, capture, and analyze/monitor data to improve data across the USTRANSCOM enterprise. The Contractor shall baseline current data assessment statistics based on the existing architecture, identify any shortfalls, and provide recommended courses of action. The Contractor shall provide suggested metrics using the six DQ characteristics in paragraph

1.3.3.1.1 to the COR. The DQ metrics and courses of action shall be delivered monthly to the

COR.

Deliverable: DQ metrics, courses of action

1.3.3.1.3. Data Quality Working Group (DQWG)

The Contractor shall schedule, arrange and set-up a facility, and assist in leading the monthly DQWG meetings. The Contractor shall prepare draft agendas and presentation materials for the meetings and provide them to the COR for approval within five (5) business days prior to the meeting. Upon the COR’s approval, the Contractor shall provide presentation materials to participants. The Contractor shall prepare minutes and provide them to the COR within five (5) business days after the DQWG meetings and ten (10) business days after the annual DQ Summit.

The Contractor shall post the approved minutes and presentation materials on designated USTRANSCOM portals and send an email to the participants informing them that the minutes have been posted. The Contractor shall maintain the DQWG Charter and provide updates as required by the COR.

Deliverable: DQWG presentation materials, minutes, and DQWG Charter

1.3.3.2. AMC Data Quality Support. For AMC only, the Contractor shall monitor, evaluate, and test data integration efforts for new AMC systems (C2, planning, transportation, logistics, and financial system functions) and prototyping initiatives, regardless of data exchange methods, to ensure the data is consistent, certified and reconcilable using criteria such as timeliness, accuracy, completeness, validity, consistency, and uniqueness. This task shall be accomplished by looking at specific instances of data at the database level. The Contractor shall provide a report on the results of the evaluation to the business operations community through the COR.

This task will be ongoing and the COR will identify the specific databases for evaluation and set due dates for data quality reports.

Deliverable: Data quality report

1.3.3.3. Interface Management.

1.3.3.3.1. The Contractor shall review interface documentation and inventory existing information exchanges for the USTRANSCOM Portfolio programs of record. The Contractor shall store interface management information in the tools identified in Section 3. The Contractor shall compile industry standards for data exchanges, investigate core technologies, and develop and integrate standard data exchange practices with existing USTRANSCOM data governance.

1.3.3.3.2. Defense Transportation Electronic Business (DTEB) Support. Recommend, Maintain, and Publish Extensible Markup Language (XML), Electronic Data Interchange (EDI) Implementation Convention (IC), and other Technical Guidance and Standards. In support of the migration from Military Standard (MILS) to Defense Logistics Management Standard (DLMS), the Contractor shall recommend and maintain XML schemas, EDI ICs, EDI IC Data Maintenance (DM) actions and other technical guidance and standards on behalf of the defense transportation, supply maintenance, and the acquisition communities of interest. To ensure the defense transportation community adheres to consistent format standards, the Contractor shall validate XML schemas and EDI ICs in compliance with the USTRANSCOM and X12 standards.

The Contractor shall store the ICs on the DTEB secure and public websites to make them available to the DTEB Community (DTEBC).

The Contractor shall create and support the standardization (to include use of enterprise terms) of XML documents to include XML schemas, document-type definitions (DTDs) and style sheets for submission to the DOD Metadata Registry (MDR). In addition to posting the XML to the DOD MDR, the Contractor shall also package the IC DM and XML schemas for posting on the DTEBC website for community voting.

The Contractor shall provide support at the Accredited Standards Committee (ASC) X12, and the Automated Carrier Interface (ACI) meetings. The ASC meets approximately three (3) times per fiscal year. The Contractor shall provide a trip report to the COR within ten (10) business days of the meeting. The due dates for the IC documentation will be determined by the COR and can vary between five (5) and thirty (30) business days.

Deliverable: IC documentation, Trip report

1.3.3.3.3. DTEB Support. The Contractor shall identify key operating issues; assess alternative solutions, and present recommendations. The Contractor shall arrange and set up facilities for the meetings, and develop draft agendas and briefings to be approved by the COR a minimum of five (5) business days prior to the meeting. The DTEBC is estimated to meet three

(3) times per fiscal year. The Contractor shall provide meeting minutes to the COR within five

(5) business days after the meetings. Upon approval by the COR, the Contractor shall post meeting minutes and presentation materials used and/or created during the meetings to the websites within ten (10) business days after the conclusion of the meeting three (3) times per fiscal year.

Deliverable: Draft agendas, presentation materials, minutes

1.3.3.3.4. Data Exchange Migration. USTRANSCOM has legacy and non-standardized systems. Therefore translation (or mediations) will occur until the systems transition to the prescribed standards. The Contractor shall provide assistance as USTRANSCOM and, Transportation Component Commands (TCCs) systems to perform required enhancements and migrations. The Contractor shall work with the programs of record to develop implementation schedules, operating concepts, data requirements, and test plans in support of migration implementations, and update the IT Data Strategy and revise documentation. The Contractor shall provide specific technical and administrative support which includes arranging trading partner communications (meetings, teleconferences, etc.) and tracking the progress of the various programs in their migration efforts.

1.3.3.3.5. Data Exchange and Message Template Mining. The Contractor shall document data exchanges, message templates, and supporting data element dictionaries in the tool(s) in Section 3, Paragraph 1 based on the priorities established by the COR. The Contractor shall perform data mining down to the data element level, including collection of required metadata. The Contractor shall also map interfaces to the Enterprise Logical Data Model.

Deliverable: Report of volume of data exchanges, message templates, and supporting data element dictionaries documented and of interfaces mapped.

1.3.3.3.6. Enterprise Terms. The Contractor shall manage the enterprise terms to include identifying all required metadata and authoritative sources. The Contractor shall map the terms to the Enterprise Logical Data Model and include the terms in the tool identified in Section 3, paragraph 1.

Deliverable: Report of terms mapped to Enterprise Logical Data Model

1.3.3.4. Enterprise Logical Data Modeling. The Contractor shall maintain the Enterprise Logical Data Model(s) (LDM(s)). The Contractor shall document the data requirements and business rules identified by USTRANSCOM and the TCCs. The Contractor shall develop the LDM(s) based on data requirements obtained from distribution and deployment system interfaces, reference data requirements, and other sources, as required by the COR. The Contractor shall document all modifications and/or updates to the Enterprise LDM(s) as required.

Deliverable: Enterprise LDM(s)

1.3.3.5. Data Support for Enterprise Initiatives. The Contractor shall provide data support to developing enterprise initiatives, e.g., AT21 and CSV initiatives, as required by the COR. The Contractor shall provide support to include using the Enterprise LDM to define and scope requirements, development of business rules, using test scripts to ensure the quality of data, and promoting the use of enterprise reference data and enterprise terms. This support may include the development of XML schemas, ANSI ASC X12 formats, enterprise terms, and enterprise reference data.

Deliverable: XML Schemas, enterprise terms

1.3.3.6. Update and maintain designated USTRANSCOM Data Web Capability and Web Site content. The Contractor shall update and maintain the USTRANSCOM data web content as required by the COR. The Contractor shall ensure links to other websites required by the Government remain active and up-to-date. The Contractor shall confer with the COR and respond to any posted comments/ questions in accordance with the COR’s direction, in not later than five (5) business days.

1.3.3.6.1. The Contractor shall maintain the Defense Transportation Electronic Business (DTEB) web homepage. The DTEB website shall provide for the collaboration and configuration management of DTEB actions to keep commercial and Government trading partners abreast of current developments. The DTEB website shall provide for the creation and maintenance of user accounts (password-protected) that shall have levels of access based upon substantiated user needs. The DTEB website shall have the capability to send e-mail notifications to the user community about updates to Implementation Conventions (ICs), Data Maintenance (DM) actions, and other important DTEBC activities (meeting minutes, calendar changes, etc.).

Deliverable: Configuration management change request

1.3.4. Task 4 - Enterprise Architecture Tools (CLIN Broken out by subtasks)

1.3.4.1. Consolidated Architecture Tool Suite (CATS) (formally known as AMCADRE) Modernization and Development (LH Task)

The Contractor shall modernize the architecture tool environment based on a consolidated and prioritized list of requirements provided by the USTRANSCOM and TCC CORs.

Modernization includes the development of new functionality, for example the capability to support new DODAF architecture models and views. This includes system/software engineering, integration activities, system security, and program documentation required for continued software support and requirements management. The Contractor shall ensure compliance with policy identified in this PWS. The Contractor shall be proficient in Oracle version 11g or higher and institute in a DM2 (DODAF Complaint) or CADM compliant framework supporting DOD Architecture Framework 2.02. This shall integrate with the CATS suite of web tools based on the .net environment. CATS functionality includes, but is not limited to, an architecture builder, a primitive manager, an architecture viewer, an enterprise data repository, an information systems catalog, and a services repository.

All code shall comply with current IA requirements and shall be scanned with the organization’s Fortify or other prescribed tool. The contractor shall provide and/or store base-lined code within the SDDC’s enterprise software (Dimensions) for versioning control

The CATS tools currently reside within a 2-Tier architecture consisting of a web tier and database tier. Future modernization plans could include breaking the web tier into a presentation tier and an application tier to create a 3-tier architecture, and the development of system interfaces..

CATS production, staging, and disaster recovery environments are part of the SDDC CCE.

Therefore, CATS will receive operational System Administrator and Database Administrator support from the Enterprise Integration Program (EIP), the CCE’s support team. The contractor shall support the EIP team with any application-specific COTS, configuration, and/or application software requirements within these three (3) environments.

Deliverable: Source Code and Fortify scan results

1.3.4.1.1. CATS Development and Testing. The Contractor will maintain a development and testing environment using Government Furnished Equipment (GFE) identified in this PWS. This will allow development and testing to be done at the Contractor’s site, and a Continuity of Operations (COOP) site, as determined by the COR. All development and testing will be accomplished without using live servers. The Contractor shall develop a software test plan In Accordance With (IAW) DI-IPSC-81438 Rev A to identify aspects of testing and provide it the COR fifteen (15) business days prior to testing.

The contractor shall utilize the SDDC SDE and Test environments for CATS development and testing and shall be perform, but not limited to, the following: tuning and performing backups, database tuning, and system patching. The contractor shall work with the G6 Information Assurance (IA) staff (including third party contractors) to ensure compliance with current IA guidance. The contractor shall be responsible for loading all application and COTS software within the test and development environments, and assists the EIP team in loading application and COTS software within the Staging, Production, and DRE servers

Deliverable: Software test plan

1.3.4.2. CATS Maintenance (FFP Task)

1.3.4.2.1. The Contractor shall maintain the CATS, to include ‘fixing defects’, application software, tools, capabilities, and databases, for the CATS applications, and related functionality in support of the USTRANSCOM and TCC user community and the CATS Program Management Office (PMO). Contractor shall apply agile and iterative development methodologies in order to provide timely capabilities to the user community. The CATS maintenance tasks also include maintaining system/software engineering, integration activities, system security in coordination with SDDC IAM, program lifecycle documentation, application documentation, and database documentation required for continued software support and requirements management. The maintenance tasks shall be synopsized in the Monthly Cost/Status and Resource Utilization Report.

All code shall comply with current IA requirements and shall be scanned with the organization’s Fortify or other prescribed tool. The contractor shall provide and/or store base-lined code within the SDDC’s enterprise software (Dimensions) for versioning control

CATS production, staging, and disaster recovery environments are part of the SDDC CCE.

Therefore, CATS will receive operational System Administrator and Database Administrator support from the Enterprise Integration Program (EIP), the CCE’s support team. The contractor shall support the EIP team with any application-specific COTS, configuration, and/or application software requirements within these three (3) environments.

Deliverable: Source code and Fortify scan results

1.3.4.2.2. The Contractor shall evaluate the performance of CATS. Based on the evaluations, the Contractor shall propose changes to the Government. Examples of changes include modifications to the database structure, performance tuning, load balancing, performance of backup and restoration of data, replication services, and manipulation of data.

Deliverable: Evaluation results, change proposals, configuration management change requests

1.3.4.2.3. CATS Database. The Contractor shall maintain the CATS database(s) including any required updates for security and…