Attachment_1_-_Performance_Work_Statement.pdf

PERFORMANCE WORK STATEMENT

FOR

ENTERPRISE ARCHITECTURE, DATA, AND ENGINEERING

10 May 2019

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), Military Sealift Command (MSC), and the 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 Surface Deployment and Distribution Command (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 Air Mobility Command Directorate of Communications (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 and computer systems via enterprise-wide planning, deployable comms, 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, 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).

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 the development of the 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 the architecture, data management, and engineering services includes the operational and system perspectives of Command and Control (C2), planning, transportation, logistics, and business support system domains. Informed by strategic vision documentation, the contractor will 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 one integrated architecture tool suite 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, the use of 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 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. This allows Government personnel to conduct impact analysis 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 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 SCAMPI Class A appraisal throughout the contract lifecycle.

2.2 Quarterly in Progress Reviews (IPR)

The contractor will conduct quarterly IPRs for the life of this contract, unless otherwise notified by the Government. The 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 (2) 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 (5) business days after conclusion of the meetings/conferences. All costs associated with the 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 materials, services, personnel, planning, direction, coordination, and control necessary to provide the services required by 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 manage and oversee all activities performed by contractor personnel (including subcontractors and teaming partners, as applicable) to satisfy all performance requirements. The contractor shall effectively plan, manage, and monitor work activities and supervising contractor personnel to support effective performance and control risk, as well as escalate problems or concerns to the Contracting Officer and COR.

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 the tasks identified in this PWS. The contractor will 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 of fully integrated Enterprise Architecture that federates to other enterprise architectures.

The contractor will be required to support DODAF and FEAF assigned projects; however, in the event other frameworks (e.g. Unified Architecture Framework (UAF)) are mandated and/or desired for use, the contractor shall support as necessary.

4.1 Architecture Documentation

The contractor shall document enterprise and solution level architectures supporting USTRANSCOM, and TCCs, to include the reuse existing architecture data/views to minimize development cost and schedule, and maintain configuration control of architectural artifacts and the underlying models. 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), as well as ensuring the documentation of critical links in DODAF architecture model formats, to include the linkage between models and related architectures. Refer to Appendix B for additional references on architecture documentation.

The contractor may be required to support the 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, as well as conduct interviews with subject matter experts, to gain an understanding of processes, systems, organizations, etc. that will impact architectural development efforts and development of the architecture views. The contractor shall identify all architecture discrepancies during architecture model development and review processes, to include documenting resolution and adjudication of architect discrepancies.

The contractor shall review the 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 the development of ontology’s and taxonomies and/or the 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 others publications as applicable.

4.3 Primitives for New and Existing Systems and Initiatives

The contractor shall be responsible for identifying and 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 or not these primitives exist within the Government designated enterprise architecture tool environment. 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 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 perform primitive registration, 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 the 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 set-up a facility set-up, preparing a draft agenda, completing preliminary analysis and compiling presentation materials for the Configuration Control Boards (CCB).

4.5 Review Architectures

The contractor shall conduct architecture reviews for externally developed architectures. 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.

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 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 the systems used and/or of interest to the Government to conduct their respective missions. The contractor shall provide status identifying any 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

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 will be responsible for set 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.

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 the understanding of the design, development, categorization, and the use of data and metadata. The contractor shall also manage Master & Common Data for Enterprise use. The 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. Enterprise Data Management Working Group (EDMWG), 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 all Enterprise Data Management Office (EDMO) supported governing bodies (e.g. Defense Transportation Electronic Business (DTEB), EDMWG, 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 in order 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 the 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 EDMWG, 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 Storage & Operations

The contractor shall assist the Government in documentation development to design, implement, and support the 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 in managing the 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 support data and support 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, other contractors, and the Enterprise Data Environment team 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 and the Enterprise Data Environment team.

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 the data needs of the enterprise, and design and maintain the 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 the 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 the application known as Interface and Data Dictionary Repository (IDDR), identified in paragraph 6. 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 the verification and validation of the data currently in IDDR.

The contractor will develop lower level business process model to execute the 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 the systems transition to the prescribed standards. The contractor shall provide assistance as required for data enhancements and migrations. The contractor shall assist in developing implementation schedules, operating concepts, data requirements, and test plans in support of migration implementations, to include documentation revisions.

5.18 Data Exchange and Message Template Mining

The contractor shall document data exchanges, message templates, and supporting data element dictionaries with the 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.

5.19 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 identified in paragraph 6.

5.20 Data Support for Enterprise Initiatives

The contractor shall provide data support to developing enterprise initiatives (, Sprint to the Cloud, Big Data, and Transportation Management System (TMS)). The contractor shall use the Enterprise LDM 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, ANSI ASC X12 formats, enterprise terms, and enterprise reference data.

6. PERFORMANCE AREA 4 ENTERPRISE ARCHITECTURE, DATA AND ENGINEERING

TOOLS

USTRANSCOM and the TCC 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 includes the development of new functionality, as well as sustainment of CATS.

This includes 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 Oracle version 12c, or higher, MySql, Redhat Linux (RHEL7 or higher), RDS working in a Cloud environment and institute in a DM2 (DODAF Complaint) or Core Architecture Data Model (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 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 IA requirements and shall be scanned with the organization’s static code analysis tool (e.g. Fortify 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 the CATS tools current 3-Tier architecture consisting of a database tier, a presentation tier and an application tier, 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 will 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 will be responsible for future application development.

Contractor is required to:

- Assist with application instantiation in the DevOps 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 business 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 will maintain a development and testing environment within the Cloud environment using Government Furnished Equipment (GFE) identified in this PWS. The contractor shall develop and provide a software test plan.

The contractor shall provide a development environment allowing for the development and testing at the contractor’s site, and a Continuity of Operations (COOP) site, as determined by the COR, until CATS is determined System of Record in the Cloud and CATS development can be accomplished in the Cloud.

All development and testing will be accomplished without using live servers at the contractor’s site. The contractor shall develop 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, training, 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 will 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 ITSM 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.

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 one particular development priority.

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 will 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 base-lined 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 services, or system interface).

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 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 (at primary and alternate sites) 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, TCNOs 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 E. Data backups shall occur on a daily basis.

6.11 Database Availability

The contractor shall ensure databases are operational and available (on-line or batch) between the hours of 0600-1800, Monday through Friday excluding federally approved holidays. The contractor shall not be responsible for periods of unavailability controlled by the non- computer service providers (e.g., DISA).

The contractor shall coordinate with the respective customers, via E-mail, one workweek prior to scheduled maintenance. The contractor shall document and report to the COR controlled and non-controlled downtime to include: date and time, total downtime, problem, corrective actions, and preventative recommendations.

6.12 DBMS Access Rights

The contractor shall maintain access authorizations for DBMS objects and the underlying physical files (i.e., DBMS system files) IAW the USTRANSCOM DevOps CONOPS and applicable guidance.

6.13 Performance Optimization

The contractor shall ensure properly sized physical files underlying database objects per DBMS vendor specifications. The contractor shall ensure optimization of computer software and hardware utilization for command unique database structures and programs. The contractor shall perform routine physical structure analysis, transaction analysis, and on-line log analysis in an effort to pinpoint problem areas, optimize response time, and resize and optimize database structures due to growth trends.

6.14 Space and Space Performance Optimization

The contractor shall monitor and take necessary action to ensure that physical database page or table structure does not become inefficient per DBMS vendor specifications.

6.15 DBMS and Database Backups

The contractor shall ensure backup databases and Government Furnished Software DBMSs each business workday. The contractor shall rerun any failed jobs within one business day. The contractor shall retain backup data unless otherwise directed by the COR.

6.16 Software Testing

The contractor shall test the installation of updates and releases prior to implementation into a production environment IAW Government provided guidelines and time frames. 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.17 Remedial Maintenance

The contractor shall ensure DBMS maintenance and sustainment work orders (Help Desk or initiated) are documented in the existing work order system. The contractor shall complete work orders based on the following priority rating time frames: Priority 1 through 2 within one (1) business day of dispatch, and Priority 3 through 5 within four (4) business days of dispatch. Work order documentation shall be available upon request by the COR.

6.18 DBMS and Database Problem Resolution

The contractor shall complete work orders based on the following priority rating time frames: Priority 1 within one (1) work hour of dispatch, Priority 2 through 3 within two (2) work hours of dispatch, and Priority 4 through 5 within three work hours of dispatch. Work order documentation shall be available upon request by the COR. The DBMS and database problem resolution problems shall be synopsized in the Monthly Cost/Status and Resource Utilization Report.

6.19 Database and DBMS Restores and Recoveries

The contractor shall restore or recover files IAW DBMS specific backup capabilities including data and system files (dictionary and control files for example). The contractor shall recover files to within one workday prior to data corruption or customer-specified point-in-time. The contractor shall complete work orders based on the following priority rating time frames: Priority 1 within three work hours of dispatch, Priority 2 through 3 within one (1) business day of dispatch, and Priority 4 through 5 within one (1) workweek of dispatch. Work order documentation shall be available upon request by the COR.

6.20 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 complete work orders based on the following priority rating time frames: Priority 1 through 2 within four (4) work hours of dispatch and Priority 3 through 5 within one (1) workday of dispatch. The contractor shall provide customers consultation services, potentially including on-site meetings, as required. Consultation services include providing necessary on-site training to enable customers to effectively employ DBMS-related tools.

Work order documentation shall be available upon request by the COR.

6.21 Database Preservation

The contractor shall maintain a backup and restoration capability of the database of the entire CATS.

These will be maintained locally and at the COOP site. The contractor shall complete a database dump that captures all data, data structures, code, and web site code associated with CATS. This deliverable will provide the Government with the ability to completely recreate any tool/application/data should the need arise. This deliverable shall include the baseline databases and user interfaces. The contractor shall deliver the toolset to the COR in the applicable toolset format.

6.22 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 Global Technical GIG (GTG) 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.

The contractor shall maintain, modernize, and host the 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.).

6.23 Tool Software Releases

The contractor shall ensure that the delivered software/services operate according to DISA STIG 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, security test and evaluations, and Joint Interoperability Test Command (JITC) certification.

6.24 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.25 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.26 CATS Orientation

The contractor shall…