J11. 47QFHA24R0004_T10_09_DRRS Seed Attachment 1_PWS.docx

PERFORMANCE WORK STATEMENT (PWS)

DEFENSE READINESS REPORTING SYSTEM (DRRS) SUSTAINMENT

TASK ORDER

1. GENERAL: This is a Task Order (TO) under the Personnel and Readiness Infrastructure Support Management (PRISM) contract designed to support the DRRS Sustainment.

2. BACKGROUND: The Defense Authorization Act for Fiscal Year 1999 required the Secretary of Defense to implement a comprehensive readiness system capable of accurately and objectively measuring readiness to support execution of the National Security Strategy (NSS), National Military Strategy (NMS) and Title 10 responsibilities. This system must be able to measure readiness in a timely manner to ensure responsiveness to support National Command Authority (NCA) review of crucial national security issues.

Department of Defense Directive 7730.65, May 31, 2023, assigns the Under Secretary of Defense for Personnel and Readiness responsibility for managing the Defense Readiness Reporting System (DRRS), pursuant to Section 117 of Title 10, United States Code (U.S.C.). DRRS provides the Department a capabilities-based, adaptive, near real-time readiness reporting framework capable of using various data sources and inputs to support a resilient strategic readiness strategy, employing the tools, methods, and approaches necessary to effectively manage the data required to measure, report, and make decisions based on holistic strategic readiness information.

3. OBJECTIVE: The primary purpose of this contract is to provide the Office of the Secretary of Defense (OSD), Under Secretary of Defense (USD) for Personnel and Readiness (P&R), and the Deputy Assistant Secretary of Defense for Force Readiness (DASD-FR) with operation and sustainment support for DRRS and other related analytical services in achieving the Requiring Activity's (RA’s) mission requirements defined herein.

4. SCOPE: The scope of this TO includes all DoD components and efforts associated with all aspects of the operation and sustainment of the DRRS. This includes the day-to-day program operation, program monitoring, life cycle maintenance, training, help desk services, and management support associated with work performed under this effort. This includes work to maintain the program’s cybersecurity posture and modernization, systems engineering and integration, system testing, necessary to support the evolving and emergent needs of the DoD. This effort incudes all of the DRRS operating environments, in both the NIPR and SIPR domains, including DRRS Production, COOP, Pre-Production, Defense Readiness Unclassified Information & Data Site (DRUIDS) and the DRRS Virtualization Platform (DVP) environment with its DRRS test and training instances. The support under this effort covers both system operation and sustainment in the DRRS program’s legacy premise hosting construct and any cloud hosting environments to which the program expands or migrates.

The effort also includes the operation and sustainment of any Government owned development environment supporting the DRRS program and any systems being hosted in the JWICS domain.

Task 1 - Program Management

Task 2 - Contract Transition Support

Task 3 – DRRS Software and Systems Engineering Support

Task 4 – Life Cycle Support

Task 5 – DRRS Operations Support

Task 6 – JWICS Systems Engineering and Administration Support

5. PERIOD OF PERFORMANCE:

The period of performance for this TO is a 12-month base period followed by two, 12-month option periods.

Base Period:

First Option Period:

July 1, 2024 to June 30, 2025 July 1, 2025 to June 30, 2026

6. SPECIFIC TASKS:

6.1. TASK 1: Program Management:

6.1.1. Post-Award Orientation (PAO) The PAO shall be held within seven calendar days of the start of performance. This meeting shall be scheduled and conducted in coordination with the SME, Contracting Officer’s Representative (COR), and KO.

The purpose of the PAO is to: 1) discuss any unique characteristics of the requirement(s); 2) identify stakeholders' roles and responsibilities; and 3) establish a common understanding of cost, schedule, and performance expectations (Deliverable 3.1-1: Contract PAO Slides).

6.1.2. Program Management Plan (PMP) The PMP is a resource-loaded baseline that outlines the steps that will be taken, provides the timeline to completion (estimated project start and stop dates), provides an expenditure plan aligned to key milestones within the project (to include any anticipated Other Direct Costs (ODCs)), identifies and quantifies the deliverables associated with each project, and identifies any associated risks and appropriate mitigation needed for execution of the contract. The completion timeline(s) of any given project shall not extend beyond the overall Period of Performance (PoP) of the contract. The Contractor shall provide the initial PMP within 15 days after contract award and provide an updated PMP quarterly and within 15 days after each new project tasking. Upon acceptance and approval by the Government, the Contractor shall meet the cost, schedule, and forecasted delivery date of all deliverables by taking all reasonable measures to fulfill the requirement and report the project status in the Monthly Status Report (MSR). The deliverable quantities listed in each table from Task 4 and Task 5 are estimates provided for reference. The actual deliverable quantities will be reflected within the PMP upon assignment of the project(s) and the Final Technical Report (FTR) (Deliverable 3.1-2: PMP).

6.1.3. Monthly Status Report (MSR) The MSR shall provide a detailed status for each project within the PMP as well as capture an overall status of the contract. The Contractor shall deliver the MSR on a date mutually agreed upon by the Contractor and the SME. Specific MSR format, and any additional content not specified in this section, shall be mutually agreed upon by the Contractor and SME; this format shall be established No Later Than (NLT) the PAO. The MSR reports cost, schedule, and performance against the PMP baseline and identifies planned versus actual expenditures per project; total monthly and cumulative ODC expenditures; status of known risks and risk mitigation efforts; deliverable(s) funded, technical progress made, and schedule status per deliverable(s); title, date, and number of deliverable(s) completed; and deliverable(s) scheduled to be delivered during the upcoming month. The MSR shall report all funding received and shall detail the projects supported by such funding, the date received, and the funding source (if known). If the MSR shows that a project is not meeting the performance standards set forth in the Service Summary found in Section 6.0, the Contractor shall provide the rationale and circumstances preventing the standards from being met (Deliverable 3.1-3: MSR).

6.1.4. Quarterly Project Management Reviews Conduct quarterly project management reviews and/or Contract Management Reviews (CMRs) with the Contract Administrator / SME to include detailed project information on cost, schedule, performance, risk assessment, and risk mitigation plans (Deliverable 3.1-4: Quarterly Project Management Review).

6.1.5. Contractor Acquired Property (CAP) Report Provide a monthly report for all CAP acquired via ODC charging to be included in the MSR, if applicable (Deliverable 3.1-3: MSR).

6.1.6. Task 1 Deliverables Table

Performance Deliverables

Submission confirmation shall be emailed to the SME, COR, and KO.

6.2. TASK 2: Contract Transition Support

6.2.1. Transition-Out Plan Develop and execute a Transition-Out Plan that shall facilitate the accomplishment of a seamless transition from the incumbent to incoming contractor or Government personnel at the expiration of the contract. Provide a Transition-Out Plan NLT 60 days prior to expiration of the contract. Identify how the incumbent will coordinate with the incoming contractor and Government personnel to provide a seamless transition and transfer knowledge regarding the following:

· Program and project management processes

· POCs

· Location of technical, program, and project management documentation

· Status of ongoing technical initiatives

· Transition of personnel

· Schedules and milestones

· Actions required of the Government

· Communication with the incoming contractor or Government personnel for the period of the transition via weekly status meetings

· Transition-Out Plan: The Contractor shall provide system life cycle and technical support for systems that are transitioned out from their area of responsibility to another organization or group. In support of this transfer, the Contractor shall provide documentation consistent with the system being transitioned to include analysis of the following:

· All current and historical documentation pertinent to the task under this PWS, including Cybersecurity Risk Management Framework and Authorities to Operate (ATO) documents

· Operations manuals and the roles of key personnel

· Continuity of Operations (COOP) plans and procedures

· Relationships and points of contact with other agencies, projects, and systems

· Passwords, access controls, and encryption keys as appropriate

6.2.2. Task 2 Deliverables Table

Performance Deliverables

6.3. TASK 3: DRRS Software and Systems Engineering Support

The Contractor shall provide maintenance and sustainment support for the all the DRRS operating environments, in both the NIPR and SIPR domains, including DRRS Production, COOP, Pre-Production, Defense Readiness Unclassified Information & Data Site (DRUIDS) and the DRRS Virtualization Platform (DVP) environment with its DRRS test and training instances. The support under these efforts cover both system operation and sustainment in the DRRS program’s legacy premise hosting construct and any cloud hosting environments to which the program expands or migrates. The support provided will include:

6.3.1. Systems Administration

6.3.1.1. The Contractor shall provide support to maintain a stable, efficient, and productive DRRS system and environment.

6.3.1.2. The Contractor shall perform software installation and updates, ensuring compliance with all DoD IT security requirements.

6.3.1.3. The Contractor shall support the maintenance of the operating systems and hardware, data access, data delivery, disaster recovery procedures (Deliverable 3.3-1: Disaster Recovery Plan) and disaster recovery backups.

6.3.1.4. The Contractor shall manage accounts, system configuration, and other system administrative duties as required.

6.3.1.5. The Contractor’s systems administration processes (Deliverable 3.3-2: System Administration Procedures) shall afford opportunities for input and oversight by the Government.

6.3.1.6. The Contractor’s periodic reports in this area should provide continuous monitoring of performance.

6.3.2. Database Maintenance

6.3.2.1. The Contractor shall provide technical and analytical services in support of database operations, maintenance and sustainment, and integration in an operational environment, including server production sites and any backup sites.

6.3.2.2. The Contractor shall provide system administration services on database structures, access to data, data replication support, system backup procedures (Deliverable 3.3-3: System Backup Procedures) and disaster recovery procedures.

6.3.2.3. The Contractor shall provide and maintain data concurrency and data consistency among server applications and sites.

6.3.2.4. The Contractor shall update, publish, and maintain schemas and database dictionaries for the systems.

6.3.2.5. The Contractor shall provide system design and systems engineering support to implement and maintain a framework for net-centric compliant interoperability between applications that collect, analyze, and report readiness information within the enterprise and between the enterprise and other segments of the DoD that need readiness data.

6.3.3. Business Intelligence (BI), System Administration and Database Maintenance

6.3.3.1. The Contractor shall provide database maintenance for DRRS resource functionality and integration with the program’s BI tool, IBM Cognos®.

6.3.3.2. The Contractor shall also provide system administration support to include maintenance on table structures, access to data, replication support, disaster recovery procedures and backups associated with the data structures integrated with and supporting the program’s BI tool.

6.3.4. Enterprise Messaging System

6.3.4.1. The Contractor shall configure, maintain, and when necessary, modify, the Enterprise Messaging (EM4) Data Exchange capability employed by DRRS.

6.3.4.2. The Contractor shall collect requirements, maintain, integrate, test, and support any changes necessary to the Data Exchange capability, which at a minimum includes the following:

· Provide a seamless data exchange service between DRRS and other relevant readiness systems (e.g., DRRS-A, JOPES / JPES, JTMIS / JTT, ADVANA)

· Monitor message transmission reliability

· Provide for dynamic routing between data sources and subscribers

· Provide for dynamic message building based on Government requirements

· Provide support for managed metadata for readiness community

· Provide transmission for a message in any Government-requested format

· Provide for security, and process classified data based on Government requirements

· Provide a scalable data exchange service

6.3.4.3. Data Exchange requirements shall be captured in a System Requirements Document (Deliverable 3.4-4: System Requirements Documentation) which must be approved by the Government prior to implementing any changes, upgrades, or improvements.

6.3.5. DRRS Product Installation

6.3.5.1. The Contractor shall provide installation plans using Government-approved configuration requirements.

6.3.5.2. The Contractor shall install and configure DRRS systems (hardware and software) as tested and having passed Certification and Accreditation (C&A) by the Government.

6.3.5.3. The Contractor shall participate in meetings with Government commands and activities to discuss development, T&E, C&A coordination, implementation policy, and schedule issues. Installation schedules are under the direction of the appropriate Program Office representative who will provide coordination.

6.3.5.4. The Contractor shall also be responsible for the installation of developed software or Government-approved Commercial off-the Shelf (COTS) purchased software under this contract necessary to support DRRS (e.g., METL Data, Resource Data Views and Associated Data and Functionality).

6.3.5.5. The Contractor shall also ensure all appropriate software is properly installed and configured to support DRRS.

6.3.6. Network Support

6.3.6.1. When required by the Government, the Contractor shall provide systems design and systems engineering support to implement and maintain a framework for net-centric compliant interoperability between applications that collect, analyze, and report readiness information within the enterprise and between the enterprise and other segments of the DoD that consume readiness data.

6.3.6.2. The Contractor shall provide telecommunications requirements analysis and network maintenance.

6.3.6.3. The Contractor shall provide networking, engineering, and installation services.

6.3.6.4. The Contractor shall provide network-cabling services, install necessary software and hardware (e.g., routers and servers), and troubleshoot network operations.

6.3.6.5. The Contractor shall participate in the installation of workstations and in the realignment of existing network capabilities.

6.3.6.6. Any proposed new system implementations, design changes, or design improvements in this section shall be documented in a System Requirements Analysis Document (Deliverable 3.4-5: System Requirements Analysis).

6.3.7. Task 3 Deliverables Table

Performance Deliverables

6.4. Task 4: Life Cycle Support

The Contractor shall provide maintenance and sustainment support for DRRS, including:

· Recommend software engineering approaches which describe program modules, classes, objects, databases, graphic user interface displays, and reports needed to successfully implement the application program functional requirements

· Provide asset management and procurement of COTS software

· Conduct analysis and prepare documentation of high-level design of application software, hardware, and data interfaces

· Participate in system requirements collection, analysis, and functional requirements definition

6.4.1. Asset Identification and Asset Management

6.4.1.1. The Contractor shall identify and track hardware and software assets and the state of their warranties and licenses.

6.4.1.2. The Contractor shall report the results of this asset management requirement in a technical report every quarter (Deliverable 3.4-1: Status of System Assets).

6.4.2. COTS Procurement

6.4.2.1. The Contractor shall procure the necessary maintenance and licenses required to maintain the Government-owned hardware and software required to support the DRRS Production, COOP, Pre-Production, DRRS Virtualization Platform (DVP) and Defense Readiness Unclassified Information & Data Site (DRUIDS) environments.

6.4.2.2. Examples of procurement include Cognos, InfoSphere DataStage and SolarWinds.

6.4.2.3. All maintenance, licenses, and data rights shall be held by the Government.

6.4.3. Government Registry

6.4.3.1. The Contractor shall ensure that all software, ports, protocols and services management (PPSM) are documented in the appropriate systems of record and assist in their updating when needed.

6.4.3.2. The Contractor shall assist the DIO as required with maintaining the DRRS related entries in the DoD Information Technology Portfolio Repository (DITPR) and with FISMA (Federal Information Security Management Act) accreditation information for the program.

6.4.4. DRRS Software Design Specification Compliance

6.4.4.1. The Contractor shall provide a web services-based system, exposing all data via Extensible Markup Language (XML), employing a DoD standards compliant XML schema and interfaces for DRRS. All software will be certified as fully compliant IAW the DISA NII Net Centric Warfare policy. The unclassified software and classified application software must meet all DoD policy requirements for operation on the Non-Secure IP Router Network (NIPRNET), the Secret IP Router Network (SIPRNET), and the Joint Worldwide Intelligence Communication System (JWICS).

6.4.5. Interoperability

6.4.5.1. The Contractor shall support requirements for interoperability as identified in CJCSI 6212.01 (series). This includes the requirement to support the DoD Architecture Framework (DODAF) requirements and processes, interoperability testing and certification, JCS-Interim Certificate to Operate (ICTO) and CTO briefings, reports and remediation, and coordination and support for Joint Interoperability Testing through approved forums.

6.4.5.2. The Contractor shall ensure that all Service-Oriented Architecture (SOA) applications will support integrated Identity Management, Permissions Management and Digital Rights Management ensuring that adequate confidentiality, availability, and integrity are provided.

6.4.6. Software Configuration and Repository

6.4.6.1. The Contractor shall document the production environment used to support DRRS (Deliverable 3.5-2: Engineering Analysis; Deliverable 3.4-3: System Design Plan).

6.4.6.2. The Contractor shall identify the hardware, software, and other resources needed for life cycle support of deliverable software and describe the developer's plans for transitioning deliverable items to the support agency.

6.4.6.3. The Contractor shall indicate how the end-product is compiled, tested, and distributed from the development environment to the production environment.

6.4.6.4. The Contractor shall indicate how databases are maintained and updated in both the development environment and production environment.

6.4.6.5. The Contractor shall assist the Government with upload and management of the source code along with the implementation and maintenance of source code management processes.

6.4.6.6. The Contractor shall provide technical support and quality assurance support with the Government repository for the DRRS software and artifacts repository.

6.4.7. Configuration Management (CM)

6.4.7.1. The Contractor shall establish a configuration management process for maintaining consistency of systems’ performance, functional and physical attributes, and hardware and software configuration parameters along with traceable requirements, design, and operational information. The CM process will include the ability for evaluation, coordination, approval or disapproval, and implementation of changes used to construct and maintain software systems (Deliverable 3.4-4: Configuration Management Plan).

6.4.7.2. The Contractor shall address all new and/or modified hardware, firmware, software, and documentation resulting from work in support of this effort. The configuration management process shall provide configuration identification, configuration control, configuration status accounting for the duration of the contract.

6.4.7.3. The Contractor shall account for changes in the baseline configuration and track changes to the baseline, including traceability of requirements, throughout the program life cycle.

6.4.7.4. The Contractor shall provide the Subject Matter Expert (SME) with reports on engineering change proposals (ECPs) (Deliverable 3.4-5: Engineering Change Proposal), baseline configuration and changes to the baseline configuration (Deliverable 3.4-6: System Baseline Documentation). The configuration management system and access to all associated work products, requirements, work items, will be readily accessible to all members of the DRRS Program, including Government and other contractors.

6.4.8. Requirements Management

6.4.8.1. The Contractor shall analyze current business processes and document potential improvements.

6.4.8.2. The Contractor shall collect, manage, and report to the SME requirements to code functionality in order to establish a common understanding among the stakeholders.

6.4.8.3. The Contractor shall coordinate recommendations and requirements with the SME.

6.4.8.4. The Contractor shall provide data on feedback from users, requirements, and requirements traceability (Deliverable 3.4-7: Requirements Management Plan).

6.4.9. Engineering Changes

6.4.9.1. The Contractor shall provide input and recommendations to the SME on defect corrections, enhancements, and new requirements, including those changes proposed by system users.

6.4.9.2. The Contractor shall analyze the proposed changes to baseline requirements and provide detailed descriptions of implementation requirements and impacts to the Government.

6.4.9.3. The Contractor shall have a formal process to accept and track engineering change proposals, including changes to scope, requirements, defect reports and work items.

6.4.9.4. The Contractor shall capture data on priority of change, level-of-effort cost estimate, and completion status.

6.4.9.5. The Contractor’s configuration management process shall afford opportunities for input and oversight by the Government (Deliverable 3.4-5: Engineering Change Proposal; Deliverable 3.5-3: Configuration Management Plan).

6.4.10. DRRS Cloud Environment

6.4.10.1. The Contractor will support the Government migration and transition to a hybrid architecture with a heavy emphasis on virtual and cloud environments. The Contractor shall provide support for the legacy and virtual IT environments. The Contractor shall provide Infrastructure as a Service (IaaS), Platform as a Service (PaaS), Software as a Service (SaaS) capabilities and expertise to develop applications to run on a cloud infrastructure in accordance with Government defined standards and within Government defined frameworks. The Contractor shall provide Enterprise Computing, Storage, and Cloud Service Delivery Life-cycle support for the DRRS global enterprise architecture at designated Government locations. Enterprise Computing, Storage, and Cloud services require a wide range of technical, functional, and program management services to support full engineering, the design, integration, installation operations, and maintenance activities of all classified and unclassified, compute, storage, cloud, physical and virtual infrastructure components.

6.4.11. Enterprise Computing and Storage Service

6.4.11.1. The Contractor shall provide Enterprise Computing and Storage services to include but not limited to, creating, accrediting, and maintaining server and workstation baselines for all supported operating systems on all networks, standardizing , deploying, and patching for all systems in operations, repairing and maintaining hardware and software, administering and managing server and storage, providing data services, data administration, and database management, providing infrastructure system services, administration, and management support for traditional systems and systems that use virtual and cloud services hosted by other agencies or external cloud service; operating, maintaining, and sustaining enterprise shared applications and infrastructure services (e.g., Identity Management, Directory Services, Public Key Infrastructure (PKI), Global Load balancing Traffic Management), providing event monitoring and management, performance monitoring, capacity planning, and analysis; and providing incident response, tracking, and resolution.

6.4.12. Cybersecurity

6.4.12.1. The Contractor shall provide certified cybersecurity expertise (i.e., Information System Security Engineers (ISSE) or Information Systems Security Officers (ISSO), as appropriate) throughout the design, engineering, and installation processes to ensure proper security controls are in place and validated. The Contractor shall ensure IT architecture and networks are interoperable with computer network defense (CND) capabilities. The Government will identify specific Enterprise Computing, Storage, and Cloud requirements and services in the individual task orders.

6.4.13. Documentation

6.4.13.1. The Contractor shall maintain an up-to-date library that contains the complete set of documentation for the DRRS system.

6.4.13.2. The Contractor shall update existing documentation or create new documentation as required by the SME. Format and content of the changes shall not deviate significantly from that of the existing documentation.

6.4.14. Task 4 Deliverables Table

Performance Deliverables

6.5. TASK 5 DRRS Operations Support

The Contractor shall provide support to all the functions required of the DIO to normally operate DRRS. This includes all forms of customer and management support as well as domain operational experts to support the design and analysis of DRRS data runs. In addition, the Contractor shall support special global or regional events and exercises. The Contractor will be required to provide cleared staff at the SECRET level, or the TOP SECRET/Sensitive Compartmented Information (SCI) level as required, capable of supporting these events, around-the-clock, at any DOD facility (Deliverable 3.5-1: Contractor Personnel Roster).

6.5.1. Help Desk and Customer Support

6.5.1.1. The Contractor shall provide help desk support at the Tier-1, Tier-2, and Tier-3 levels. The contractor will provide on-site support during the week (Monday through Friday,) for 20 hours each day. The gap in daily coverage will be at a time approved by the Government. On the weekends, (Saturday and Sunday,) the contractor will provide eight hours of coverage each day, with the hours of covered to be approved by the Government. Response to trouble calls after hours (including holidays) shall be provided in accordance with the program’s applicable response plans.

6.5.1.2. The manpower level during the periods of support will be sufficient to ensure all trouble calls are responded to in a timely manner. For the purposes of this task, a timely manner is within 24 hours, preferably the same working day, unless a federal holiday falls within the 24-hour period, in which case 48 hours is the upper threshold.

6.5.1.3. The support provided will include responding to account and permissions issues, application performance issues, providing technical and administrative information regarding the DRRS system. Responses will be provided via any means available, but the Contractor shall provide a response record logged via the Government email system. The help desk/customer support team shall aid in upload, generating queries, and downloading information. (Deliverable 3.3-2: System Administration Procedures).

6.5.2. Training

6.5.2.1. The Contractor shall provide training to users of fielded DRRS functionality. The trainers shall have knowledge and experience with DRRS and be able to understand and relate to the users’ operational environment and culture.

6.5.2.2. For each user training event identified by the Government, the Contractor shall prepare training materials, make arrangements for training delivery (time, location, etc.), and conduct the training. Training may be self-study, one-on-one, instructor-led, hands-on and/or computer-based training (CBT), as agreed upon by the Government. Training material products shall be delivered on electronic media (Deliverable 3.5-2: Training Materials).

6.5.2.3. The Contractor shall assist the Government with the development of training plans, training schedules, and shall participate in administrative tasks such as scheduling classes, tracking student loading and instructor assignments, and processing payments, receipts, and invoices.

6.5.2.4. The Contractor should plan to conduct a ninety minute training session three times a month.

6.5.3. Business Intelligence and Data Mining

6.5.3.1. The Contractor shall collect, analyze, and display DoD readiness information in support of recurring and ad hoc projects.

6.5.3.2. The Contractor will support the collection and manipulation of data from across the DoD into DRRS, analytical products, reports and models.

6.5.3.3. The Contractor shall provide the capability to extract data from DRRS and other legacy enterprise sources to support analytical products, reports, models, and decision-making at the enterprise level.

6.5.3.4. The Contractor shall develop methods to improve decision-making and capability assessment by retrieving and revealing information from DRRS and enterprise data sources, when requested by the Government. This will include the use of Online Analytical Processing (OLAP) tools to effectively query the DRRS databases and building a performance oriented data warehouse and OLAP engine supportable information cubes.

6.5.4. Subject Matter Expertise

6.5.4.1. The Contractor is responsible for providing personnel capable of working independently and with demonstrated working knowledge of the DRRS effort. Because of the nature of the support required by USD P&R, it is highly desirable for the long-term success of DRRS and to the continuity of operations that all personnel have related operational experience, and 3 or more years DoD or equivalent experience working with or in development of the following:

· Operational Readiness Concepts

· Joint and Service Planning and Operational Concepts

· Mission Capability Package (MCP), Operations Plans (OPLANS), Contingency Plans (CONPLANS), DoD-approved Scenarios and Joint Combat Operations

· Training Requirements and Objectives

· Mission Essential Task Construct

· Global Forces Management and Force Structure Construct

· Joint Planning Guidance

· National Security Strategy and National Military Strategy

· Personnel with experience in software-intensive data systems, data mining, data quality assurance, and SOAs

6.5.5. Test and Evaluation

6.5.5.1. DRRS is a web-based enterprise application sharing data with numerous other Government systems. The DRRS program has a continuous need to perform internal and external testing with other systems in the readiness enterprise. This requires that the Contractor support testing and evaluation activities at the direction of the DIO.

6.5.5.2. The Contractor shall support testing on all products planned for delivery to the DIO providing independent Government testing for developmental testing (DT), operational testing (OT), user acceptance testing (UAT), Sustainment, and other Test & Evaluation activities.

6.5.5.3. The Contractor shall develop and deliver all required testing documentation to the DIO (Deliverable 3.5-3: Test Planning Documentation; Deliverable 3.5-4: Test Analysis and Reporting).

6.5.6. Information Assurance (IA) Support

6.5.6.1. The Contractor shall work with the DIO to ensure DRRS operations meet the security requirements defined in the DoD Risk Management Framework (RMF) process. These tasks may include, but not be limited to assign IA controls, develop, and implement RMF strategy, initiate and execute IA Implementation Plans, define, and execute the DIO IA Vulnerability Alert Management Plan, conduct validation activities and compile results, initiate and update lifecycle validation plans, coordinate with Certification Authorities (CA) and Decision Accreditation Authorities (DAA).

6.5.6.2. When performing requirements identified by the DIO IA team, the contractor shall follow all procedures identified in the DIO IA Vulnerability Management Plan to acquire, install, and test all software to mitigate identified security vulnerabilities.

6.5.6.3. The Contractor shall develop and deliver the required installation and test documentation with every software update required to be applied to the production system. The delivered documentation will be approved by the Government (Deliverable 3.5-4: Test Analysis and Reporting; Deliverable 3.4-6: System Baseline Documentation).

6.5.6.4. The Contractor shall aid the DIO in maintaining the DRRS System Security Authorization Agreement, (SSAA,) Information Support Plan (ISP) and other documentation associated with the RMF approval process, Interoperability Certification and testing processes.

6.5.7. Management Support

6.5.7.1. The Contractor shall develop presentations, reports, point papers and other documentation in support of the tasks described in this PWS.

6.5.7.2. The Contractor shall use email for administrative coordination issues. Classified (up to SECRET) information may be transmitted via SIPRNET e-mail. TOP SECRET and TOP SECRET/SCI information may be transmitted via JWICS email.

6.5.8. Reports, Papers and Presentations

6.5.8.1. The contactor shall develop presentations, reports, point papers, and other documents in support of the DIO.

6.5.8.2. The Contractor shall participate in the performance of all technical analysis, assessments, research, special studies and monitoring.

6.5.8.3. The Contractor shall participate in technical and status review meetings.

6.5.8.4. The Contractor shall submit project review reports. (Deliverable 3.5-5: Report, Record of Meeting / Minutes).

6.5.9. Meetings

6.5.9.1. The Contractor shall participate in working group meetings with managers and users to: help determine requirements, discuss implementation issues, conduct reviews, and other project related purposes when required by Government.

6.5.9.2. The Contractor shall submit meeting minutes documenting the results of these meetings and trip reports.

6.5.9.3. The Contractor shall participate in project reviews and submit project review reports when required by the Government.

6.5.9.4. Contractor shall conduct and/or attend Technical Interchange Meetings (TIMs) to facilitate the exchange of technical information and enhance effective communication among the interested parties authorized by the Government. (Deliverable 3.5-5: Report, Record of Meeting / Minutes).

6.5.10. Task 5 Deliverables Table

Performance Deliverables

6.6. TASK 6: JWICS Systems Engineering and Administration Support

The Contractor shall provide maintenance and sustainment support for the all the DRRS operating environments in the JWICS domain when requested by the Government. The support provided will include:

6.6.1. Systems Administration

6.6.1.1. The Contractor shall provide support to maintain a stable, efficient, and productive DRRS system and environment.

6.6.1.2. The Contractor shall perform software installation and updates, ensuring compliance with all DoD IT security requirements.

6.6.1.3. The Contractor shall support the maintenance of the operating systems and hardware, data access, data delivery, disaster recovery procedures (Deliverable 3.6-1: Disaster Recovery Plan) and disaster recovery backups.

6.6.1.4. The Contractor shall manage accounts, system configuration, and other system administrative duties as required.

6.6.1.5. The Contractor’s systems administration processes (Deliverable 3.6-2: System Administration Procedures) shall afford opportunities for input and oversight by the Government.

6.6.1.6. The Contractor’s periodic reports in this area should provide continuous monitoring of performance.

6.6.2. Database Maintenance

6.6.2.1. The Contractor shall provide technical and analytical services in support of database operations, maintenance and sustainment, and integration in an operational environment, including server production sites and any backup sites.

6.6.2.2. The Contractor shall provide system administration services on database structures, access to data, data replication support, system backup procedures (Deliverable 3.6-3: System Backup Procedures) and disaster recovery procedures.

6.6.2.3. The Contractor shall provide and maintain data concurrency and data consistency among server applications and sites.

6.6.2.4. The Contractor shall update, publish, and maintain schemas and database dictionaries for the systems.

6.6.2.5. The Contractor shall provide system design and systems engineering support to implement and maintain a framework for net-centric compliant interoperability between applications that collect, analyze, and report readiness information within the enterprise and between the enterprise and other segments of the DoD that need readiness data.

6.6.3. Business Intelligence (BI), System Administration and Database Maintenance

6.6.3.1. The Contractor shall provide database maintenance for DRRS resource functionality and integration with the program’s BI tool, IBM Cognos®.

6.6.3.2. The Contractor shall also provide system administration support to include maintenance on table structures, access to data, replication support, disaster recovery procedures and backups associated with the data structures integrated with and supporting the program’s BI tool.

6.6.4. DRRS Product Installation

6.6.4.1. The Contractor shall provide installation plans using Government-approved configuration requirements.

6.6.4.2. The Contractor shall install and configure DRRS systems (hardware and software) as tested and having passed Certification and Accreditation (C&A) by the Government.

6.6.4.3. The Contractor shall participate in meetings with Government commands and activities to discuss development, T&E, C&A coordination, implementation policy, and schedule issues. Installation schedules are under the direction of the appropriate Program Office representative who will provide coordination.

6.6.4.4. The Contractor shall also be responsible for the installation of developed software or Government-approved Commercial off-the Shelf (COTS) purchased software under this contract necessary to support DRRS (e.g., METL Data, Resource Data Views and Associated Data and Functionality).

6.6.4.5. The Contractor shall also ensure all appropriate software is properly installed and configured to support DRRS.

6.6.5. Task 6 Deliverables Table

Performance Deliverables

7. GOVERNMENT PROPERTY

7.1. Access to Government Property

7.1.1. The Government will provide the Contractor with access to facilities on an as-needed basis, inclusive of items incidental to the place of performance as necessary to complete this tasking under this contract. The Government will arrange for the Contractor to have access to all necessary military installations including training sites, installation sites, and test facilities necessary to complete all aspects of the tasks.

7.2. Government Furnished Information (GFI)

7.2.1. The Government will provide the Contractor with access to information on an as-needed basis to complete the tasking under this contract. Any GFI such as federal policies, directives, instructions, or documents provided during performance of this contract shall be provided with a Distribution Statement setting forth the disclosure limitations with which the Contractor must comply. In the event that GFI is provided without a Distribution Statement, any disclosure shall be IAW DFARS 252.204-7000, Disclosure of Information, and the IAC MAC Basic Contract. The Contractor shall treat technical data in its possession as Government sensitive information that is not to be released outside of the originating organization.

8. SECURITY REQUIREMENTS

The work performed by the Contractor shall include access to Unclassified and up to TOP SECRET/SCI data, information, and spaces in accordance with the DD 254 attached to the order. The Contractor shall follow mandated procedures to ensure information access is limited to individual classification level (e.g., no individual may gain access to information at a higher level than their clearance and granted access allows). The Contractor will require access to SIPRNET and JWICS. The Contractor shall be North Atlantic Treaty Organization (NATO) briefed and complete derivative classification training prior to being granted access to SIPRNET; training is provided by the facility security officer. The Contractor shall be briefed on Special Intelligence (SI) handling requirements, as well as individual briefings applicable to any compartmented information required, and complete derivative classification training prior to being granted access to JWICS.

As required by National Industrial Security Program Operating Manual (NISPOM) Chapter 1, Section 3, Contractors are required to report certain events that have an impact on: 1) the status of the facility clearance (FCL); 2) the status of an employee's personnel clearance (PCL); 3) the proper safeguarding of classified information; 4) or an indication that classified information has been lost or compromised.