Atch 1 - DRAFT_ 2024.09.19 PWS.docx

PERFORMANCE WORK STATEMENT

FOR

ENTERPRISE ARCHITECTURE, DATA, AND ENGINEERING III

Se

19 September 2024 Prepared by

UNITED STATES TRANSPORTATION COMMAND

DIRECTORATE OF COMMAND, CONTROL, COMMUNICATIONS & CYBER SYSTEMS

1. DESCRIPTION OF SERVICES

1.1 Introduction

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 Transportation Component Command (TCC) includes the Air Mobility Command (AMC) supported by Headquarters Air Force Material Command’s (HQ AFMC) Air Force Life Cycle Management Center (AFLCMC), Military Sealift Command (MSC), and the Military Surface Deployment and Distribution Command (SDDC), as well as subordinate command, the Joint Enabling Capabilities Command (JECC).

The USTRANSCOM’s Directorate of Command, Control, Communications & Cyber 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 Acquisition (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 IT Programs and Support Services Division (TCAQ-D) provides responsive, flexible contracting support for USTRANSCOM Distribution Process Owner (DPO) initiatives and SDDC 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 (A&AS), management support services, ancillary support services, classified and unclassified network support, and Research and Development (R&D).

USTRANSCOM is co-located on Scott Air Force Base with two of the TCCs; AMC and SDDC. The architecture and engineering efforts jointly and collaboratively support the data requirements of USTRANSCOM, AMC, and SDDC missions.

The mission of the US Air Force Materiel Command Air Force Life Cycle Management Center Airspace Mission Planning Operating Location-2 (AFMC AFLCMC HBM OL-2) 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's mission is to provide rapid, global mobility and sustainment for America's armed forces. The AFLCMC/HBMMA Enterprise Architecture, Data, and Engineering Office resides within HBM OL-2 in support of AMC’s global air mobility mission. AFLCMC manages the integration of the communications-computer systems via enterprise-wide planning, systems engineering, architecture development, and interoperability processes. AFLCMC manages technical solutions for AMC C4I systems in compliance with DoD, US Air Force, USTRANSCOM, and joint architecture and integration goals. AFLCMC 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 and computer systems via enterprise-wide planning, deployable comms, systems engineering, architecture development, and interoperability processes. SDDC G6 Portfolio Management 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, US Army, USTRANSCOM, and joint architecture and integration strategies, policies, and objectives.

1.2 Background

In 2013, AMC, SDDC, and the USTRANSCOM consolidated contract requirements for enterprise architecture, data management, and enterprise engineering services to achieve architecture integration. This included the use of an integrated architecture tool suite to achieve greater efficiencies in architecture development while allowing for an enterprise view of the Transportation Enterprise. By consolidating contract requirements, the agencies were able to provide an enterprise view over three communities of interest (COI) providing analysis in support of the above commands and the Joint Deployment and Distribution Enterprise (JDDE). In 2022, the enterprise architecture, data management, and enterprise engineering services supporting AMC Command and Control (C2) systems transitioned to AFLCMC, Program Executive Office – Digital (PEO-D), and now falls under HBM Mission Planning Operating Location – 2, Scott AFB, and AMC Business System transitioned to Program Executive Office-USTRANSCOM (PEO-T), Scott AFB.

1.3 Objective

The objective of this contract is to achieve greater efficiencies and collaboration across the USTRANSCOM and its TCCs. The Government as the Transportation Enterprise expects to continue integration efforts to support and perform analysis across enterprise, systems of systems, and individual system levels and develops enterprise strategies, technical standards and services as the command transitions into commercial cloud services and future capabilities.

This includes development of enterprise architecture (EA) data in one integrated architecture tool suite identified in paragraph 6. The contractor shall provide enterprise data management, professional and engineering services, enterprise-wide support, and technical guidance related to mission needs and issues concerning the above commands and the JDDE.

1.4 Scope

The scope of this requirement is to acquire enterprise architecture, enterprise data management, and information technology engineering services for USTRANSCOM and its TCCs.

The scope of architecture, data management, and engineering services include operational and system perspectives of Command and Control (C2), planning, transportation, logistics, and business support system domains. Informed by strategic vision documentation, the contractor shall provide architecture, data management, and engineering support. Additionally, this contract will support prototyping, information support plan development, software development, and system administration that allows EA data to reside in all integrated architecture tool suites identified in paragraph 6. This PWS procures an integrated enterprise architecture from the enterprise level through the solution level and across architectures. Integration is achieved through an architecture tool suite, standardized templates and guidelines, training, and the architecture review process. The work effort will support engineering and analytical services required to support and implement USTRANSCOM and its TCCs operational and system requirement(s) solutions. The contractor shall possess an understanding of the DoD Architecture Framework (DoDAF), the Federal Enterprise Architecture Framework (FEAF), Unified Architecture Framework (UAF), the Business Process Model Notation (BPMN), Business Enterprise Architecture (BEA), and relationships/dependencies between architecture models to support assigned projects. This allows Government personnel to conduct impact analyses on the enterprise, systems of systems, and individual system levels.

Services and support anticipated under this contract exist within the scope of the following performance areas:

Performance Area 1 – Contract and Program Management Performance Area 2 – Enterprise Architecture Performance Area 3 – Enterprise Data Management Performance Area 4 – Enterprise Architecture, Data and/or Engineering Tools Performance Area 5 – Enterprise Engineering Performance Area 6 – Information Support Plan/Enhanced Information Support Plan Performance Area 7 – Agile Capability Development Performance Area 8 – Prototyping and Research, Development, Test, and Evaluation (RDT&E) Support

The services provided within the scope of this contract are considered Operationally Critical Support (OCS) and Covered Defense Information (CDI) as defined in Defense Federal Acquisition Regulation Supplement (DFARS) 252.204-7012, "Safeguarding Covered Defense Information and Cyber Incident Reporting.” Any CDI will be identified at the task order level.

2. CONTRACT REQUIREMENTS

2.1 Capability Maturity Model Integration (CMMI)

The contractor shall be CMMI Level III in the model for Development and/or Services. CMMI is a proven set of global best practices that drives business performance through building and benchmarking key capabilities and is endorsed by the CMMI Institute. The contractor is required to obtain and maintain a successful CMMI Level III Standard CMMI Appraisal Method for Process Improvement (SCAMPI) Class A appraisal throughout the contract lifecycle.

2.2 Quarterly In-Progress Reviews (IPR)

The contractor shall conduct quarterly IPRs for the life of this contract, unless otherwise notified by the Government. IPRs will address overall contract status and provide details regarding technical, programmatic, scheduling, operations, administration, project status, accomplishments, contract issues, and upcoming plans. Documentation and presentation materials shall be prepared and provided two business days in advance of the IPR. IPR dates and locations will be coordinated in advance by the designated Government Representative.

2.3 Information Sharing

The Government may use and disclose reported information (e.g., information regarding threats, vulnerabilities, incidents, or best practices) that does not include attribution information, at its discretion to assist entities in protecting information or information systems (e.g. threat information products, threat assessment reports); provided that such use or disclosure is otherwise authorized in accordance with applicable statutes, regulations, and policies.

2.4 Periodic Government Inspections

The contractor is subject to Government inspections and reviews to assure compliance with DoD Supply Chain Risk Management (SCRM) requirements throughout the contract performance period. The contractor shall be responsible for taking corrective action based upon the impact and severity of identified weaknesses.

2.5 Post Award Task Order Meetings/Conferences

Technical meetings and/or post award orientation conferences may be necessary to resolve problems and to facilitate understanding of the requirements of the contract and/or of each awarded task order. Participants at these meetings/conferences shall be members of the contractor’s technical staff and technical representatives of the Government. These meetings/conferences shall be scheduled by agreement of the parties and arrangements made between the Contracting Officer, his/her representative, and the contractor. Records of these meetings/conferences shall be made by the contractor and submitted to the Government within five business days after conclusion of the meetings/conferences. All costs associated with attendance at these meetings/conferences shall be at no direct charge to the contract.

3. PERFORMANCE AREA 1 – CONTRACT AND PROGRAM MANAGEMENT

The contractor shall provide all required materials, services, personnel, planning, direction, coordination, and control in support of this contract. The contractor must perform program management, project management, and contract management to ensure timely and effective performance.

3.1 Program Management

The contractor shall identify a Program Manager (PM), who is the authorized point of contact with the Government Contracting Officer’s Representative (COR). The PM responsibilities include, but are not limited to, interfacing with Government management personnel, staffing of all tasks, formulating, and enforcing work standards, creating personnel and project schedules, reviewing work discrepancies, and communicating Government policies, purposes, and goals to the contractor team.

3.2 Program Management Plan

The contractor shall develop a plan documenting the contractor’s management approach, operating procedures, staffing approach, and overall work breakdown structure. Staffing plans regarding resource assignments by task may be required at the task order level.

3.3 Documentation

The contractor shall provide support necessary to draft, review, revise, and deliver documents (e.g. reports, briefings, point papers, business case analysis, meeting minutes) required in conjunction with the contract. The contractor shall provide technical writing and document support to include all tasks identified in this PWS. The contractor shall provide support in separate and distinct deliverables and/or documentation will be identified at the task order level.

4. PERFORMANCE AREA 2 – ENTERPRISE ARCHITECTURE

The contractor shall provide all technical support services to include maintaining, documenting, and implementing fully integrated Enterprise Architecture that federates to other enterprise architectures. The contractor shall be required to support DoDAF and FEAF assigned projects; however, in the event other frameworks (e.g. UAF) are mandated and/or desired for use, the contractor shall support as necessary. The contractor shall use advanced digital engineering and model-based methods to support the design, analysis, verification, and validation associated with the development of USTRANSCOM and TCCs complex architectures.

4.1 Architecture Documentation

The contractor shall document enterprise, business, infrastructure, functional, and solution level architectures supporting USTRANSCOM and TCCs, to include reuse of existing architecture data/views to minimize development cost, schedule, and maintain configuration control of architectural artifacts and underlying models. Architectures will include the scope for C2, planning, transportation, logistics, and business systems domains (e.g., exercise, experiment, advanced technology demonstrations, and system-focused “as-is” and “to-be” architecture models), as well as ensuring documentation of critical links in DoDAF architecture model formats (in the event other frameworks (e.g. UAF) are mandated and/or desired for use, the contractor shall support as necessary including fit-for-purpose and tailored views within each framework), to include linkage between models and related architectures. Refer to Appendix B for additional references on architecture documentation.

The contractor shall be required to support development of artifacts, model “as-is” and “to-be” architectures and recommend operational business processes and/or use cases for architecture evolution.

The contractor shall adhere to Government-specified style guides, approved taxonomies, architecture implementation guides and element lists. The contractor shall capture and store USTRANSCOM and TCCs performers, activities (functions), business process rules, information exchanges, data exchanges, data elements, and Data Dictionaries in the tools identified in paragraph 6.

4.2 New and Existing Systems and Initiatives

The contractor shall review published guidance identified in paragraph 6 and conduct interviews with subject matter experts to gain an understanding of processes, systems, organizations, etc., to identify impacts to architecture development efforts. The contractor shall follow CMMI Level III SCAMPI Class A, or equivalent current CMMI level certification, and have quality gates built into their development process, a review processes and a documented resolution and adjudication of architecture discrepancies and deviations (with the expectation of 100% adjudication of the end product).

The contractor shall review existing reference models, recommend modifications, and implement changes as required by the COR. The contractor shall refine existing or develop new reference models, which may include development of ontologies and taxonomies and/or use of existing reference models, such as the Joint Capability Areas (JCAs), Plan-Order-Ship-Track-Pay (POST-P), or the Joint Common System Function List (JCSFL), and other publications as applicable.

4.3 Primitives for New and Existing Systems and Initiatives

The contractor shall be responsible for identifying, scoping and assembling primitives for new and existing systems and initiatives. The contractor shall review primitives (e.g., performers, systems, system functions, activities, information exchanges) identified while researching documentation and conducting interviews to determine whether these primitives exist within the Government designated enterprise architecture tool environment. The contractor shall ensure accuracy and currency during architecture development while coordinating any changes across task orders and ensuring minimal disruption across existing architectures. If the primitives do not exist, the contractor shall propose the primitives to the Government for approval.

The contractor shall collect, organize, correlate, and store architecture data required for architecture development and document architectural results in the Government designated enterprise architecture tool environment following Government approved procedures. The contractor shall perform primitive creation, architecture model construction, and architecture markup/coordination, using Government -provided tools in paragraph 6. 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, Systems Modeling Language (SysML), Unified Modeling Language (UML) techniques, etc.), and engineering techniques, such as use cases. The contractor shall mature architecture views throughout the review and approval process and ensure all architecture artifacts produced comply with DoDAF and Government approved templates and guidelines.

4.4 Architecture Configuration Management

The contractor shall provide administrative and analysis support to the Government configuration management process to include scheduling, arranging and facility set-up, preparing a draft agenda, completing preliminary analysis, updating Model Development Guides (MDG), and compiling presentation materials for the Configuration Control Boards (CCB).

4.5 Review Architectures

The contractor shall assist the Government in review of a variety of architectures from a technical, substantive, and administrative aspect. These architectures can range from certified to uncertified and may be internal and external to the contract in origin. The contractor shall record all concerns identified during the architecture review in a Government-provided comments matrix, to include a resolution to each comment or concern when delivered to the COR.

4.6 Enterprise Impact Analysis

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, to include 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 Government to include assessments and recommendations.

4.7 Enterprise Requirements and Review Analysis

The Government will identify enterprise information requirements for review and analysis. The contractor shall use a team approach, which uses the enterprise architecture to evaluate potential requirements for gaps and redundancies, by reviewing enterprise information requirements documents to evaluate the linkage to the existing architecture. The contractor shall assist the Government in developing courses of action and use cases, as well as provide recommendations for each enterprise information requirement.

4.8 Information Resource Catalogue (IRC)

The contractor shall collect and maintain information about systems used and/or of interest to the Government to conduct their respective missions. The contractor shall provide status updates and/or changes that have been incorporated into the IRC, which is the System Table of the Consolidated Architecture Tool Suite (CATS). At a minimum, the contractor shall collect and maintain information to include 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, other Government identified system information. This information shall be collected through surveys and correspondence with the various program management offices in control of the systems. Analysis will be conducted between multiple data environments to ensure that system data is synced and accurate to the greatest extent possible.

4.9 Enterprise Architecture Instructional Services/Seminar

The contractor shall provide instructional and training solutions in support of business processes and supporting technology principles for COR review. These services/seminars will be for the purpose of educating Government personnel and their support staff on how to use and read architectures. The contractor shall be responsible for setting up the facility with necessary equipment and supplies to facilitate the training, recording student’s contact information, capture course comments, issue a student survey, and consolidate survey results.

4.10 Government Reference Architecture (GRA)

The contractor shall assist the Government in managing and updating GRAs to support modernization of the transportation portfolio. The contractor shall engage with SMEs to update the GRA so that it aligns with the Command’s goals and objectives for technology replacement and maturation.

5. PERFORMANCE AREA 3 – ENTERPRISE DATA MANAGEMENT

The contractor shall provide all technical support services to include advising on Enterprise Data (i.e. JDDE) governance, data management, establishing guidelines, maintaining and documenting data interoperability issues, interface management, system resources, and service while assisting in understanding of the design, development, categorization, and use of data and metadata. The contractor shall also manage Master & Common Data for Enterprise use. The Data Management Association (DAMA) Data Management Framework, known as the DAMA Wheel and its 11 Knowledge Area Framework, shall be utilized in this effort.

5.1 Enterprise Data Governance

The contractor shall assist the Government in delivering documentation that enables the Data governing entities (e.g. Data Stewardship Working Group (DSWG), Chief Data Officer, etc.) to exercise authority, control, and shared decision making to include planning, monitoring, and enforcement over the management of data assets. The contractor shall provide technical, subject matter expertise, and administrative support to the Data Division supported governing bodies (e.g. Defense Transportation Electronic Business (DTEB), DSWG, etc.).

5.2 Enterprise Data Quality

The contractor shall assist the Government in the planning, implementation, and control of activities that apply data quality management techniques to enterprise data to assure it is fit for consumption. The contractor shall provide data quality support, as well as identify enterprise data quality issues 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, and elevate issues as needed. The contractor shall identify proactive data quality issues through active monitoring, which uses multiple software tools, and problem resolution of non-compliant data.

The contractor shall monitor, evaluate, and test data integration efforts for existing and new systems (i.e. 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.

5.3 Data Project Portfolio Management

The contractor shall provide project portfolio management support to identify, capture, document, and recommend data-oriented mission improvement opportunities and data issues for the DSWG, utilizing Government supplied tools. The contractor shall provide subject matter expertise in data management and data use to properly align enterprise data resources.

5.4 Data Operations

The contractor shall assist the Government in documentation development to design, implement, and support stored enterprise data to maximize its value to the JDDE. The contractor shall collaborate, as necessary, to align data stewardship efforts, manage database technology, and manage database operations.

5.5 Data Security

The contractor shall assist the Government in defining, planning, and developing, data security standard-to provide proper authentication, authorization, access and auditing of data and information assets.

5.6 Data Integration and Interoperability

The contractor shall ensure organizational vision and defined to-be standards are being utilized across the JDDE. The contractor shall assist the Government with review of newly received requests for data to determine availability of requested data. The contractor shall assist the Government in managing movement and consolidation of data within and between data stores, applications, and organizations, as appropriate.

5.7 Document and Content Management

The contractor shall assist the Government in the planning, implementation, and control of activities for life cycle of management of data and information through lifecycle management of an Enterprise Document and Content Management (EDCM) standard supporting the JDDE COI.

5.8 Reference and Master Data

The contractor shall assist the Government in identifying, capturing, and managing of JDDE shared/common data to meet goals, reduce risks associated with redundancy, ensure higher quality, and reduce the costs of data integration. The contractor shall assist in establishing guidelines and operational management of JDDE Data Services.

5.9 Warehousing and Business Intelligence

The contractor shall assist the Government in the strategic planning, implementation, and control processes to provide decision-making support to knowledge workers engaged in reporting, query, and analysis.

5.10 Metadata

The contractor shall assist the Government in the planning, implementation, and control of activities to enable access to high quality integrated metadata. This corresponds to the metadata lifecycle: create, source, store, integrate, delivery, usage, control and maintain processes.

5.11 Data Solutions - Convergence

The contactor shall work with the Government and contractors to source, select, converge, and make available structured data and data set solutions, to be maintained as trusted data sets within Data Services, which may be applied to business intelligence (BI) outputs or developed as software solutions.

The contractor shall assist in the development and maintenance of operational processes to select, source, and converge data from across the JDDE to provide additional structured data sets for common use within and in conjunction with JDDE Data Services.

5.12 Data Solutions -Visualization

The contractor shall develop user solutions for visualization and end-user use of data. These solutions may be business intelligence-based outputs using BI tools or in many cases custom applications as user interfaces for execution of decision-support and decision-making data-enabled mission activities.

5.13 Data Architecture

The contractor shall capture data needs of the enterprise, and design and maintain master blueprints which guide data integration, control data assets, and align data investments with the business strategy supporting the JDDE.

5.14 Data Modeling and Design

The Contractor shall discover, analyze, and scope data requirements. Represent and communicate data requirements in a conceptual, logical, and/or physical data model that support the JDDE.

5.15 Enterprise Logical Data Modeling

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

5.16 Interface Management

The contractor shall review interface documentation and inventory existing information exchanges for the USTRANSCOM Portfolio Programs of Record. The contractor shall mine and store interface management information in CATS applications known as Interface and Data Dictionary Repository (IDDR) and Service Documentation Repository (SDR). 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. This effort will include verification and validation of data currently in IDDR and SDR. The contractor shall develop a lower-level business process model to execute development of new services and create conceptual models of data objects and how the data objects associate with each other.

5.17 Data Exchange Migration

The Government has legacy and non-standardized systems. Therefore translation (or mediations) will occur until systems transition to the prescribed standards. The contractor shall assist as required for data enhancements and migrations, to include, but not limited to, developing implementation schedules, operating concepts, data requirements, and test plans in support of migration implementations, and documentation revisions.

5.18 Data Exchange and Message Template Mining

The contractor shall document data exchanges, message templates, and supporting data element dictionaries with tools provided in the tool(s) in paragraph 6. 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 (ELDM).

5.19 Enterprise Terms

The contractor shall manage enterprise terms to include identifying all required metadata and authoritative sources. The contractor shall map terms to the ELDM, and message elements exchanged between system.

5.20 Data Support for Enterprise Initiatives

The contractor shall provide data support to developing enterprise initiatives. The contractor shall use the ELDM to define and scope requirements, develop business rules, use test scripts to ensure the quality of data, and promote the use of enterprise reference data and enterprise terms. The contractor shall develop XML schemas, American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12 formats, enterprise terms, and enterprise reference data.

6. PERFORMANCE AREA 4 – ENTERPRISE ARCHITECTURE, DATA AND/OR ENGINEERING TOOLS

USTRANSCOM and the TCCs use a variety of Commercial Off-The-Shelf (COTS) and Government Off-The-Shelf (GOTS) products to support architecture, data, and engineering. All products comply with DoD Standards and guidelines and are approved by USTRANSCOM and/or TCC governance processes.

6.1 Consolidated Architecture Tool Suite (CATS) Development and Sustainment The contractor shall develop and sustain the Government architecture and metadata tool and associated environment based on a consolidated and prioritized list of requirements.

The contractor’s efforts shall include the development of new functionality, as well as sustainment of CATS. This includes, but is not limited to, system/software engineering, integration activities, system security, configuration management 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 the use of current database and containerization implementation and practices (e.g. PostgreSQL, MySql, Redhat Linux (RHEL) containers, and Windows containers). The contractor shall also be proficient in AWS support and nomenclature including working in a Cloud environment and instituting a DoDAF Meta Model (DM2) (DoDAF Complaint), DoDAF+, UAF, or CADM compliant framework supporting DoD Architecture Framework version 2.02. This shall integrate with the CATS suite of web tools based on .NET and Angular DevSecOps pipelines. CATS functionality includes, but is not limited to, an Architecture Builder Tool (ABT), a Primitive Manager (Prim Mgr), an Architecture Viewer (ARV), an Interface and Data Dictionary Repository (IDDR), an Information Resource Catalog (IRC), and a Services Documentation Repository (SDR).

All code shall comply with current cloud architecture (e.g. TCODE and Platform (P1) One Certificate to Field (CTF)) and shall be scanned with the organization’s proscribed analysis tools (e.g. Fortify, SonarQube, or other prescribed tool). The contractor shall provide and/or store base-lined code within a Government designated code repository for versioning control.

The contractor shall maintain/enhance the CATS applications current architecture consisting of a database tier, a presentation tier, and an application tier; modernize CATS architecture to leverage cloud services/cloud architecture; and the development of system interfaces to support a Government designated Cloud environment.

CATS development, staging, training, production, and/or disaster recovery environments will reside in the Cloud environment. The contractor shall provide operational System Administrator and/or Database Administrator support within commercial Cloud environment. The contractor shall support the Cloud support team with any application-specific COTS, configuration, and/or application software requirements within these environments.

The Government will provide an environment that supports application development that meets all applicable standards and requirements in the Cloud. The contractor shall be responsible for future application development.

Contractor is required to:

· Assist with application instantiation in the DevSecOps environment.

· Support application throughout integration and deployment process.

· Deliver scripts to fully test and deploy application functionality in an automated fashion.

· Deliver code and artifacts via the appropriate repositories within commercial Cloud environment.

· Utilize developed blueprints and pipelines to meet USTRANSCOM standards (i.e. infrastructure and operating systems).

· The Government may, directly or through a third party, modify code base maintained by the application developer. The application developer has 30 calendar days from Government code acceptance to dispute responsibility of code changes on redeveloped applications. Developer will have an opportunity to test application before deployment into Production.

6.2 CATS Development and Testing

The contractor shall maintain a development and testing environment within the on premises and/or Cloud environment using Government Furnished Equipment (GFE) identified in this PWS. The contractor shall provide a development environment allowing for the development and testing at the contractor’s site, and Cloud environments, as determined by the COR. All development and testing at the contractor’s site shall be accomplished in a secure Government approved solution. The contractor shall develop and provide a software test plan in accordance with (IAW) DI-IPSC-81438 Rev A to identify aspects of testing.

The contractor shall implement future application development, and assist in the advancement of the development, staging, and production environments towards Continuous Integration/Continuous Deployment (CI/CD).

6.3 CATS Maintenance

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 user community and the CATS Information Technology Sustainment Management Office (ITSMO).

The contractor shall apply agile and iterative development methodologies 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 designed IAM, program lifecycle documentation, application documentation, and database documentation required for continued software support and requirements management.

The contractor shall maintain the CATS database(s) including any required updates for security and improved functionality. The contractor shall assist the Government in the effort to ensure database backups and restorations are performed by Cloud environment team.

The contractor shall maintain user web front ends (applications) for CATS, as needed, in the application/version/format required by the COR. The front end shall allow queries (e.g., Ad Hoc, etc.) for architecture and engineering developmental efforts. The contractor shall propose changes to the Government to include modifications to the database structure, performance tuning, load balancing, performance of backup and restoration of data, replication services, and manipulation of data.

6.4 CATS Configuration Management

The contractor shall provide Configuration Management (CM) support for the application in coordination with a Government CM (GCM).

The contractor’s Configuration Manager (CCM) shall provide input to CATS’s Configuration Management Plan (CMP) and processes that are consistent with and complement the GCM processes. The contractor shall provide updates to the document to include their developmental CM processes.

6.5 Change Control

The contractor shall provide change control for all baselines and configuration items to include documentation, COTS software, application, database, source, and executable code. The Government will provide the contractor with web access to a designated change control tool (CCT). The CCT will be a shared tool by the CATS Program Office and the contractor staff. The CCT is programmed to support the CATS configuration management process. The contractor shall be responsible for updating the CATS CM processes within the tool, as required.

The contractor shall evaluate all Change Requests. Evaluations include but shall not be limited to requirement clarification; requirements analysis; determination if the requirement is feasible; cost (labor hours) estimation; adherence to standards; and the consequences of the proposed change. This information shall be provided to the Government for evaluation via the CCT and/or as a separate document depending upon the amount of information required or provided. The evaluation shall assist the Government and the contractor to determine how many, and which change requests shall be rolled into each release.

The contractor shall conduct a physical and functional configuration audit of each code baseline/release delivered to the Government.

6.6 Configuration Control Board (CCB)

The contractor’s Configuration Manager (CCM) shall participate in and document the Government’s CCB, to include meetings. The contractor’s CM shall act as the liaison between the Government and contractor to provide any additional information that the CCB requires. Participation ensures contractor activities are focused in the areas the Government deems important, and changes within the Government’s hosting environment(s) are properly vetted across all affected programs. The Government will provide tools to track the CM process, add prioritization, and level of effort, i.e. Gitlab.

Multiple capabilities may be addressed in any one development cycle, but periodic, agile, releases may encompass several similar capabilities while working to the final stage of any development priorities.

6.7 Base-lined Source Code

The contractor shall provide installation guidance (guide(s)) to the Government representative for installing base-lined source code in the Government environment. The contractor shall use applicable installation guidance to deploy CATS development, staging, training, and production environments. The contractor shall use the DevOps/automation pipeline(s) or assist other personnel designated by the COR in the installation and is responsible for successful installation of the software. The contractor shall store baselined code within a designated source code repository for versioning control prior to release to Production. The method to identify software versions is documented in the CMP; all versioning shall be coordinated with the GCM.

6.8 Data Sharing

The contractor shall make available portions of CATS’s information with other users/systems as required by the COR. The contractor shall ensure data is DoDAF Meta Model (DM2) compliant to facilitate sharing of data. The contractor may be required to expose the data using a variety of methods (e.g., Representational State Transfer (REST) services, or application programming interface (API)).

6.9 Database and Application Support

The contractor shall perform database and application administration and integration support for tools and software applications (e.g., CATS and all subsystems/applications). The contractor shall provide database administration support to include but not limited to upgrades, allocation and management of database space, development and maintenance of backup and recovery routines, database security administration (including data backup), consultation, production problem resolution, and coordination. The contractor shall perform upgrades to the database and applications as required including but not limited to:

· The development of policy and procedures as they relate to maintenance, security and archiving

· Installing and upgrading servers and clients

· Performs security patches, Time Compliance Network Order (TCNO) and other upgrades

· Allocating system storage and planning future storage requirements for all database systems

· Creating primary database storage structures (table spaces)

· Creating primary objects (tables, views, indexes)

· Modifying the database structure, as necessary

· Creating and maintaining users and maintaining system security

· Controlling and monitoring user access to the database

· Monitoring and optimizing performance

· Planning for backup and recovery of database information

· Maintaining archived data

· Backing up and restoration services for the database

· Contacting vendors for technical support

· Compliance with Defense Information Systems Agency (DISA) Security Technical -Implementation Guides (STIGs), and any other upgrades/modifications

6.10 Database Administration

The contractor shall provide database administration support to include allocation and management of database space, development and maintenance of backup and recovery routines, database security administration (including data backup), consultation, production problem resolution, and coordination with vendors and other agencies. Database Management Systems (DBMS) currently supported are identified in Appendix D. Data backups shall occur daily.

6.11 Software Testing

The contractor shall test the installation of updates and releases prior to release into the DevSecOps pipeline. The contractor shall identify software “bugs” with software vendor, DoD Software Engineering Centers (SECs), and Government and non-Government network entities. The Government shall monitor, review, and approve the distribution of software licenses and the contractor. The contractor shall maintain the distribution of software licenses. Some release administration requires support during non-duty hours. The contractor shall report test findings, identifying deficiencies, corrective actions, and milestones.

6.12 DBMS Resolution Documentation

The contractor shall ensure DBMS resolution documentation is recorded in the work order system and shall be completed IAW the work order priority ratings. The contractor shall provide customers consultation services, potentially including on-site meetings, as required. Consultation services include providing necessary Platform-as-a-Service (PaaS) support and requests to for DBMS-related issues. Work order documentation shall be available upon request by the COR.

6.13 Web-based Information/Applications

The contractor shall modernize and/or maintain web-based sources of information and applications for CATS and DTEB websites in a format defined by the COR (e.g., CATS web pages on the .mil domain). Modernization includes the development of new functionality. The web pages shall follow the Joint Assessments and Standards Management (JASM), Defense Information Systems Repository (DISR) standards, and applicable network policies/mandates using Common Access Card (CAC) authentication process and logon. Support includes, but is not limited to, posting data coordination, modifying out-of-date information, and recording feedback and suggestions.

6.14 Tool Software Releases

The contractor shall ensure that the delivered software/services operate according to Defense Information Systems Agency Security Technical Implementation Guide (DISA STIG) specifications, Cloud Service Provider (CSP) specifications, and meets the exit criteria (pass/fail criteria) to include any modifications identified in the Validated Requirements List for each requirement.

The contractor shall ensure that the delivered software does not break/interfere with currently fielded Government software or meets backwards capability requirements.

The contractor shall ensure the developed capability is suitable for delivery to the COR at the test baseline. Testing will include unit, system, regression, security, and performance testing in a Government-designated environment.

The contractor shall ensure and document certification or accreditation testing for all security classification domains. This includes, but is not limited to, the existing requirements for Government acceptance testing, system integration testing, Risk Management Framework (RMF) accreditation, Certificate to Field (CtF), security test and evaluations, and Joint Interoperability Test Command (JITC) certification.

6.15 Data Call Support

The contractor shall support requests for data from CATS. The COR will identify the content, format, and suspense for the data calls.

6.16 Software/Development Tool Evaluations

The contractor shall evaluate software and development tools. The COR will inform the contractor of which tools are to be evaluated and what criteria will be used to perform the evaluation.

6.17 CATS Orientation

The contractor shall provide up to a two-hour orientation on any of the enterprise architecture suite of tools/applications when requested. The orientation will provide background on how the data analysts/users can enter and extract data from the enterprise architecture suite of tools. The Government anticipates four (4) orientations annually with up to ten (10) participants.

6.18 Help Desk

The contractor shall receive, document, and resolve trouble tickets from customers via the Government -provided tool. The contractor shall troubleshoot production incidents including determining root causes identifying and implementing corrective actions, and documenting in the Government provided tool (i.e., CATS & GIT).

6.19 System Security

The contractor shall comply with and assist with Information Assurance (IA) Program and RMF guidance as it applies to the environment. The contractor shall review DoD-level IA documents and assess impact to the environment, review systems requirements documentation, develop security accreditation documentation (RMF or CtF Artifacts), and support required e-Government reporting (i.e. Federal Information Security Modernization Act (FISMA), etc.). The contractor shall obtain and maintain a current Authority-to-Operate (ATO) security accreditation and required network security authorizations. The contractor shall maintain a system security documentation record set for hardware and software on the network and, at a minimum it shall consist of the following: submitted and approved IA controls, test plans and results, Certification and Accreditation (C&A), and ATO documents upon managing system updates. The contractor shall assist in system security engineering and incident analysis.

The contractor shall ensure equipment and applications on the network comply with all applicable CtF or RMF guidance. The contractor shall prepare the required documentation to obtain and maintain required network certifications and shall provide the documentation to the COR for coordination. The contractor shall follow the standards for database security established for USTRANSCOM and Platform One (P1) / Cloud One (C1).