W9124J22R0004 Atch F Task Order 1 PWS MED CDID CONSOLIDATED CONTRACT V 1.pdf

Performance Work Statement

Medical Capability Development Integration Directorate (CDID) Futures & Concepts Center

Proposed Consolidated Support Contract Task Order #1

PART 1

GENERAL INFORMATION

1. GENERAL: No change to base PWS.

1.1 Description of Services/Introduction: No change to base PWS.

1.2 Background: No change to base PWS.

1.2.1 The mission of the Medical CDID is to: No change to base PWS.

1.3 Objectives: No change to base PWS.

1.4 Scope: The Contractor shall provide:

Administrative, technical, and analytical support of Army concept development, experimentation, capability development and evaluation of materiel solution;

Modeling and simulation (M&S) support of Army Health System concepts, capabilities and organizations;

Input involving force modernization capability development actions across Doctrine Organization Training Materiel Leadership and Education Personnel, Facilities and Policy (DOTMLPF) domains;

1.5 Period of Performance: 15 Feb 2022 – 14 Feb 2023

1.6 General Information.

1.6.1 Federal Observed Holidays: No change to base PWS.

1.6.2 Hours of Operation: No change to base PWS.

1.6.3 Place of Performance: No change to base PWS.

1.6.3.1 No change to base PWS..

1.6.3.2 No change to base PWS.

1.6.4 Quality Control Program: No change to base PWS.

1.6.5 Quality Assurance: No change to base PWS.

1.6.6 Type of Contract: No change to base PWS.

1.6.7 Security Requirements: No change to base PWS.

1.6.7.1 Physical Security: No change to base PWS.

1.6.7.2 Key Control: NA

1.6.7.2.1. NA

1.6.7.2.2. NA

1.6.7.3 Lock Combinations: NA

1.6.8 Special Qualifications: Qualifications for contractor personnel are listed below:

1.6.8.1 General: No change to base PWS.

1.6.8.2 Requirements Core Competency:

I. Clinical Science and Technology SME with graduate level degree in a clinical field or biological science (MD, DO, DMD, MSN, PhD).

II. Joint Capabilities Integration and Development System SME with in-depth knowledge of the JCIDS process as it applies to the development of Information System (IS) requirements documents.

1.6.8.3 Experimentation Core Competency: No change to base PWS.

1.6.9 Post Award Conference/Periodic Progress Meetings: No change to base PWS.

1.6.10 Contracting Officer’s Representative (COR): No change to base PWS.

1.6.11 Key Personnel: No change to base PWS.

1.6.12 Identification of Contractor Employees: No change to base PWS.

1.6.13 Contractor Travel: No change to base PWS.

1.6.14 Contractor Personnel Conduct: No change to base PWS.

1.6.15 Other Direct Costs: NA

1.6.16 Data Rights: No change to base PWS.

1.6.17 Organizational Conflict of Interest: No change to base PWS.

1.6.18 Phase In/Phase Out: No change to base PWS.

1.6.19 Antiterrorism (AT) and Operations Security (OPSEC): No change to base PWS.

1.6.19.1 AT Level I Training: No change to base PWS.

1.6.19.2 Access and General Protection/Security Policy and Procedures: No change to base PWS.

1.6.19.3 AT Awareness Training for Contractor Personnel Traveling Overseas: No change to base PWS.

1.6.19.4 IWATCH Training: No change to base PWS.

1.6.19.5 Contractor Employees Who Require Access to Government Information Systems (IS): No change to base PWS.

1.6.19.6 For Contracts that Require an OPSEC Standing Operating Procedure (SOP)/Plan: No change to base PWS.

1.6.19.7 For Contracts that Require OPSEC Training: No change to base PWS.

1.6.19.8 For Information Assurance (IA)/Information Technology (IT) Training: No change to base

PWS.

1.6.19.9 For Information Assurance (IA)/Information Technology (IT) Certification: No change to base

PWS.

1.6.19.10 For Contractors Authorized to Accompany the Force: No change to base PWS.

1.6.19.11 For Contractors Requiring Performance or Delivery in a Foreign Country, DFARS Clause 252.225-7043, and Antiterrorism/Force Protection for Defense Contractors Outside the US: No change to base PWS.

1.6.19.12 For Contracts That Require Handling or Access to Classified Information: No change to base

PWS.

1.6.20 Emergency Services: No change to base PWS.

1.6.20.1 No change to base PWS.

1.6.20.2 No change to base PWS..

PART 2

DEFINITIONS, ACRONYMS, AND ABBREVIATIONS

2. DEFINITIONS AND ACRONYMS: No change to base PWS.

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES: No change to base PWS.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES: No change to base PWS.

4.1 General: No change to base PWS.

4.2 Secret Facility Clearance: No change to base PWS.

PART 5

SPECIFIC TASKS

5. SPECIFIC TASKS:

5.1 Basic Services: The Contractor shall perform duties within the Medical Capability Development and Integration Directorate (MED CDID) in support of the organization’s four core competency missions: 1.

Concepts, 2. Requirements, 3. Experimentation and 4. Integration. The contractor will provide operational Army Health System (AHS) subject matter expertise to support the planning, synchronization, integration and development of Health Service Support and Force Health Projection capabilities in support of Multi-Domain Operations, AimPoint Forces of 2035 and the Army’s modernization strategy.

The contractor specific tasks are identified in Figure 1, and expressed in greater detail in paragraphs 5.2 through 5.6.

Figure 1

5.2.1 Concept of Operation (CONOP). No change to base PWS.

5.2.2 Operational and Organizational (O&O) Design. No change to base PWS.

5.2.3 Performance Standards No change to base PWS.

5.3 Requirements. Remove 5.3.1. Clinical Science and Technology SME

5.3.1 Clinical Science and Technology SME. Remove 5.3.1.

5.3.2 Operational SME. No change to base PWS.

MED CDID

Specified Tasks

5.2 Concepts

5.3 Requirements

5.4 Experimentation

5.6 Contractor Manpower

5.2.1 Concept of Operations

5.2.2 O&O Design

5.3.2 Operational SME

5.3.3 Analytical Support

5.3.4

JCIDS SME

5.4.1 System

Administrator

5.4.2 Model and

Simulation Support

5.3.54 Integration Activity

5.3.3 Analytical Support. No change to base PWS.

5.3.4 Joint Capabilities Integration and Development System SME. No change to base PWS.

5.3.5 Integration Activity. No change to base PWS.

5.3.6 Performance Standards: No change to base PWS Performance Standards as written.

5.4 Experimentation. The Army conducts conceptual experimentation planning, coordination and execution using a secret/FVEY enclave on the Defense Research and Engineering Network (DREN) called the Battle Lab Simulation Collaboration Environment (BLSCE). The DREN/BLSCE is a high capacity low latency network capability designed to support federated simulation events replicating Corps, Division and BCT operations. The DREN/BLSCE integrates / connects all Army warfighting functions CDIDs and enables distributed event planning and coordination, and participation. The Medical Battle Lab participates in Joint, Army, and interagency events and experiments to analyze medical concepts, operational and organizational concepts, and identify materiel, equipment, training, and personnel requirements. The contractor in coordination with the Medical Battle Lab shall identify experimentation venues across the warfighting functions and cross functional teams where medical equities are represented requiring either onsite or distributed participation. The contractor shall develop respective learning demands and essential elements of analysis to inform conceptual document information requirements, focus analysis and align with other experiments.

5.4.1 System Administration. The contractor shall perform system administration tasks to meet security compliance protocol, and maintain the functionally and connectivity of DREN/BLSCE. The contractor must have the requisite certifications to perform the necessary network operations and maintenance functions as stated in 1.6.8. The contractor will perform a range of system administration and customer service tasks to include:

5.4.1.1 Technical Support. The contractor shall assist with technical assistance to BLSCE users consisting of hardware troubleshooting, software troubleshooting, and the instruction of users on the proper use of systems. The contractor shall possess the required knowledge to diagnose and correct personal computer and network malfunctions (e.g. problems with registry settings, group policies, User Account Control settings, permissions, Client Server software, ports, protocols, etc.). The contractor must be technically knowledgeable with local area network hardware (e.g. switches, routers, etc.), and capable of providing support to the DREN in accordance with the MEDCoE/ARNORTH DREN service agreement.

5.4.1.2 System Administrator/System Maintenance Support. No change to base PWS.

5.4.1.3 Operation and Equipment Support. The contractor shall be responsible for the setup, teardown, and operation of the BLSCE equipment to include VTCs and computer workstations to enable both onsite and distributive events in accordance with event specified requirements. The BLSCE facility and the contractor’s primary workstation may be in separate rooms or buildings, the contractor must be prepared to access and operate the network from multiple locations. A weekly facility usage and activity report will Medical Battle Lab.

5.4.2 Model and Simulation Support. The contractor shall provide operations research and system analysis support to enable qualitative and quantitative analysis and modeling of Army Health System concepts and capabilities. The contactor will also provide simulations technical, database and software subject matter expertise to support participation in federated or cloud based constructive simulation based experiments to replicate medical operations and formations at echelon. The contractor must possess an in-depth understanding and proficiency in using constructive force generation tools such as One Semi- Automated Forces (OneSAF) software.

5.4.2.1 Distributed Experimentation and Simulation Support. No change to base PWS.

5.4.3. Performance Standards: No change to base PWS Performance Standards as written.

5.5 Integration: Remove 5.5. Integration from PWS.

5.5.1 Operations Support: Remove 5.5.1. Operations Support from PWS.

5.5.2 Knowledge Management Support: Remove 5.5.2. Knowledge Management Support from PWS.

5.5.3 Performance Standards: Remove 5.5.3. Performance Standards from PWS

PART 6

APPLICABLE PUBLICATIONS

6. APPLICABLE PUBLICATIONS (CURRENT EDITIONS): No change to base PWS.

6.1 The Contractor must abide by all applicable regulations, publications, manuals, and local policies and procedures: No change to base PWS.

PART 7

ATTACHMENT/TECHNICAL EXHIBIT LISTING

7. Attachment / Technical Exhibit List:

7.1 Attachment 1/Technical Exhibit 1 – Performance Requirements Summary

7.2 Attachment 2/Technical Exhibit 2 – Deliverables Schedule

7.3 Attachment 3/Technical Exhibit 3 – Relative Importance

TECHNICAL EXHIBIT 1

Performance Requirements Summary

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Objectives (Tasks) Performance Standards

Performance Thresholds/Acceptable Quality Levels (This Is The Maximum

Error Rate. It Could Possibly Be “Zero Deviation From Standard)

Incentive/Remedy

5.2. Concepts. No change from

Base PWS.

Deliverables: No change from Base PWS

5.2. Concepts. No change from

Base PWS Performance Standards

5.2. Concepts. No change from

Base PWS on AQLs

No change from Base PWS on Incentives/Remedy

5.3. Requirements. 5.3.1.

Clinical S&T SME was removed from Base PWS. All other information is still valid.

Deliverables: No change to PWS deliverables

5.3. Requirements. 5.3.1. No

change from Base PWS Performance Standards

5.3. Requirements. No change

from Base PWS on AQLs

No change from Base PWS on Incentives/Remedy

5.4 Experimentation. Refer to

paragraph 5.4, 5.4.1, 5.4.1.1, 5.4.1.2, 5.4.1.3, 5.4.2, and

5.4.2.1 of PWS

Deliverables: No change to PWS Deliverables

5.4. Requirements. No change

from Base PWS Performance Standards

5.4. Requirements. No change

from Base PWS on AQLs

No change from Base PWS on Incentives/Remedy

5.5 Integration. 5.5., 5.5.1.,

5.5.2. were removed from Base

PWS

Deliverables: Deliverables were removed from Base PWS

5.5. Integration: Integration

Performance Standards were removed from Base PWS

5.5. Integration. Removed from

Base PWS

Incentives/Remedy for 5.5. and subordinate paragraphs were removed from Base PWS

TECHNICAL EXHIBIT 2

Deliverables Schedule

Number Deliverable Frequency Medium Submit To

A001 Medical Supporting Concept As Assigned Digital COR

A002 Operational and Organizational Concept Document

As Assigned Digital COR

A003 JCIDS Requirements Documentation As Assigned Digital COR

A004 White Paper As Assigned Digital COR

A005 Information Paper As Assigned Digital COR

A006 Briefing Document As Assigned Digital COR

A007 Executive Summary As Assigned Digital COR

A008 Activity / Significant Event Report for Each Core Competency Task

Weekly Digital COR

TECHNICAL EXHIBIT 3

ESTIMATED WORKLOAD DATA TABLE

This technical exhibit lists:

1. The Historical Workload Data by Labor Category Table. This is provided for informational purposes only. The contractor shall propose its staffing plan with labor mix and hours to accomplish all task in the PWS.

2. The Relative Importance Data Table illustrates the percentage of importance each requirement has in relation to 100% of the contracted requirements in the PWS.

HISTORICAL ESTIMATED WORKLOAD DATA BY LABOR CATEGORY TABLE

ITEM NAME ESTIMATED QUANTITY and Annual Hours

2 Modeling and Simulations Specialist I 2 3840

5 Requirements Analyst 6 11520

RELATIVE IMPORTANCE TABLE

Statement % of Relative Importance

5.2 Concepts. The contractor shall develop and brief the Medical Supporting Concept using the Army Concept Framework (ACF). The Medical Supporting Concept will describe how Army forces conduct medical operations (Health Service Support and Force Health Protection) during Multi-Domain Operations (MDO), at echelon, and integrated across all Army functional concepts. The Medical Supporting Concept will address challenges of the future force with new operational approaches, capabilities, and emerging technologies. The Medical Supporting Concept will be updated continuously, describe the capabilities required to conduct operations in the future and serve as the basis for experimentation throughout the requirements determination process. The contractor shall develop knowledge needs and learning demands to examine elements of the Medical Supporting Concept through a series of Quicklook, Limited Objective Experiments (LOE) designed to analyze specific functions and capabilities required to support revisions to the concept, O&O or required capabilities. Date, time, location and venue for LOEs will be determined as needed by the CRD leadership. The contractor shall write as directed information papers to underpin and inform senior leaders on conceptual documents.

25%

5.3 Requirements. The contractor shall use the Top Down Future Development Process (TDFDP), knowledge needs, robust conceptual and constructive experimentation participation, and detailed research and analysis planning to inform how AHS capability and capacity will be organized, command and controlled, and arrayed throughout the operational framework. The contractor will apply elements of the requirements determination process to collectively support the identification of required capabilities (clinical and non-clinical) that are expressed in the Medical Supporting Concept and aligned with the AOC and functional concepts.

25%

5.4 Experimentation. The Army conducts conceptual experimentation planning, coordination and execution using a secret/FVEY enclave on the Defense Research and Engineering Network (DREN) called the Battle Lab Simulation Collaboration Environment (BLCSE). The DREN/BLCSE is a high capacity low latency network capability designed to support federated simulation events replicating Corps, Division and BCT operations.

25%

The DREN/BLCSE integrates / connects all Army warfighting functions CDIDs and enables distributed event planning and coordination, and participation. The Medical Battle Lab participates in Joint, Army, and interagency events and experiments to analyze medical concepts, operational and organizational concepts, and identify materiel, equipment, training, and personnel requirements. The contractor in coordination with the Medical Battle Lab shall identify experimentation venues across the warfighting functions and cross functional teams where medical equities are represented requiring either onsite or distributed participation. The contractor shall develop respective learning demands and essential elements of analysis to inform conceptual document information requirements, focus analysis and align with other experiments.

5.5 Integration. The contractor will provide support for integration requirements across DOTMLPF-p domain, strategic investment portfolios, and program resourcing and force structure determination activities. The Med CDID performs and supports three levels of integration: a. Level 1 integration includes activities within the CDID(s) which include policy, guidance, and event support necessary to develop and synchronize modernization efforts, b. Level II integration include activities between CAC, FCC, CCDC, CoE, CFT, and external stakeholders, and c. Level III integration includes activities typically between the ACOMs and DA. MED CDID in coordination with the medical force modernization proponent participates in SPAR and POM planning and preparation activities and validates as the capability developer strategic investment and funding priorities are nested with and support Army medicine modernization requirements. The contractor will support the MED CDID during the development of annual AHS science and technology, product development and modernization priorities in support of the Medical Requirements Oversight Council engagements.

25%