Attachment 1_(DRAFT) PWS_OE CORE_20240227.docx

PERFORMANCE WORK STATEMENT FOR

TRADOC Deputy Chief of Staff for Intelligence (G-2) Operational Environment (OE) and Core Functions

As of 27 February 2024

TABLE OF CONTENTS

SECTION C-1 GENERAL

SECTION C-2 ACRONYMS

SECTION C-3 GOVERNMENT FURNISHED PROPERTY AND

SERVICES

SECTION C-4 CONTRACTOR FURNISHED PROPERTY AND

SERVICES

SECTION C-5 SPECIFIC TASKS

SECTION C-6 PROGRAM MANAGEMENT SUPPORT

ENCLOSURE A CORPORATE NONDISCLOSURE AGREEMENT (NDA) FOR

CONTRACTORS

(PRS)

C-1 GENERAL

1.0 General Information Introduction. This Performance Work Statement (PWS) describes the performance requirements for the Operational Environment and Core (OE/Core) Functions at the United States Army’s Training and Doctrine Command (TRADOC) Deputy Chief of Staff for Intelligence (G-2). Section C-1, General Information, provides general information necessary to understand the requirements. Section C-2, Acronyms and Definitions, provides acronyms and definitions used throughout this document and in the performance of this effort. Sections C-3, Government-Furnished Property and Services, and C-4, Contractor-Furnished Property and Services, provide information on Government and Contractor furnished property and services, respectively. Section C-5, Specific Tasks, presents the specific tasks. Section C-6, Program Management Support, describes the program management support needed to efficiently monitor the performance requirements for OE/Core. Section C-7, Delivery, Inspection/Acceptance by the Government, and Invoicing, provides the guidance for delivery, inspection, and acceptance by the Government and for Contractor invoicing. Sections C-8, Deliverables Schedule, and C-9, Enclosures and Forms, outline technical exhibits and applicable documents that impact this work. Contractor products shall be submitted to the appointed COR/ACOR or designated TRADOC G-2 Government employees for review and approval, as appropriate.

1.1 Background. An operational environment (OE) is the aggregate of the conditions, circumstances, and influences that affect the employment of capabilities and bear on the decisions of the commander. For Army forces, an operational environment encompasses the air, land, maritime, space, and cyberspace domains; the information environment; the electromagnetic spectrum (EMS); and other factors. Commanders and staffs analyze an operational environment using the eight operational variables (PMESII-PT). Within an operational environment, it is difficult to discern how the many entities will behave and interact with each other, as well as the differing circumstances that will result from these actions. No two operational environments are the same. Additionally, an operational environment is not static; it continually transforms. This transformation results from opposing forces and actors interacting and their abilities to learn and adapt. The complex and dynamic nature of an operational environment makes determining the relationship between cause and effect difficult and contributes to the uncertain nature of military operations.

1.1.1 Agency Mission. TRADOC Deputy Chief of Staff for Intelligence (G-2)’s mission is to understand, visualize, describe, deliver & assess the OE in order to reduce risk and prevent surprise; today and over the next ten years. TRADOC G-2 is the designated Core Function Lead for the Operational Environment (OE) (TRADOC Reg. 10-5, Jul 2021). The OE is a composite of the conditions, circumstances, and influences that affect the employment of capabilities and bear on the decisions of the commander. The process of developing, verifying, validating, accrediting, and providing OE products and services represents an authoritative, validated OE contextual baseline for TRADOC users and operational forces in the areas of training and training development; education; leader development; doctrine development; and across DOTMLP-F integration.

TRADOC G-2 has the following responsibilities:

i. Study, develop, and maintain the OE; manage OE replication and design for Army Leader Development (LD), Army Training and provide validated OEs to support Capabilities Development including war-games and experiments. Describe how National Defense Strategy defined threats will fight the U.S. Army over the next ten years.

ii. Build and maintain an OE knowledge center as a flexible network of data, tools, relationships, processes, and systems capable of replicating the most complex and difficult circumstances expected in the OE.

iii. Manage the Army Operational Environment/Opposing Forces (OE/OPFOR) modernization program to support LD and training at Combat Training Centers (CTCs), home stations, and Centers of Excellence (CoEs).

iv. Collaborate with Deputy Director Joint Staff J-7, Joint and Coalition Warfighting (JCW) or equivalent Organization on the Joint Operational Environment (JOE) and threats to ensure consistency in the development of the OE benchmark for Joint LD, training, and experimentation.

v. Validate and assess OE and threats application across the TRADOC mission set.

vi. Provide Intelligence, Surveillance, and Reconnaissance (ISR) expertise in support of the command’s priorities.

Additionally, in support of the OE and TRADOC CORE functions, G-2 executes its mission and functions by:

i. Providing independent expert, critical reviews of plans, concepts, organizations, and programs.

ii. Exercising staff management of all intelligence, foreign disclosure, and security (personnel, technology, and communications) policy, products, and priorities.

iii. Representing TRADOC for intelligence resources and integration of ISR concepts and requirements with responsible agencies.

Lastly, G-2 executes special projects and missions assigned as short term, rapid acquisition needs for Subject Matter Experts (SMEs) and Consultants. Historical and current activity dictates G-2 establish and sustain an analytic enterprise to ensure TRADOC remains connected to ongoing OE activities in Joint and National Agencies as well as across TRADOC CoEs.

1.1.2 Current Environment. The TRADOC headquarters staff analyzes, assesses, provides staff-management oversight, and recommends for decision all activities affecting policy, command guidance, developmental processes, and implementation/execution processes to support the command in meeting its mission. The staff facilitates the coordination and dissemination of strategic operational concepts and plans, doctrine, and training to the Department of the Army (DA), Department of Defense (DoD), Congress, and external agencies and organizations. Also, the staff supports TRADOC subordinate organizations in executing command initiatives in recruiting, training, educating, designing, testing, and evaluating the force.

1.2 Scope. This PWS defines the requirements and acceptable performance levels for execution of this contract. The Contractor shall support TRADOC in a wide variety of efforts. The Contractor shall ensure all projects maintain consistency with each other and no duplication of effort exists within the program. The Contractor shall support the TRADOC G-2 to execute its mission as TRADOC’s designated Lead for its Core Function #13, the OE, and provide support and services to TRADOC in the following specific areas:

i. Identify, define, and predict the variables of the OE.

ii. Implement the analysis and supplant the traditional focus regarding LD and training (individual, unit, and collective training) as well as doctrine development (requirements determination, future doctrine, and joint doctrine).

iii. Provide Subject Matter Experts (SMEs) and Consultants to execute G-2 special projects and missions assigned as short term, rapid acquisition needs.

1.3 Objective. TRADOC has broadened its efforts to include supporting the Army in combat operations with enhanced, up-to-date training oriented on a current assessment of enemy capabilities as well as predictions for enemy reactions to a dynamic battlefield. TRADOC responsibilities regarding support to the Operating Force and the Generating Force have multiplied and increased. As a result, G-2 has been assigned a wide range of missions and projects that require expert analysis, planning, assessments, and execution from an increasing array of SMEs. The Army requires a flexible tool which brings these capabilities to bear on the challenges G-2 and TRADOC face today and will face in an ever-evolving and uncertain future.

1.4 General Information.

1.4.1 Period of Performance. The Period of Performance (POP) for the awarded contract includes an 8-month base period with a 30-day Phase-In. The awarded contract will include four one-year option periods.

1.4.1.1 Phase-in Period/Transition. The 30-day phase-in will commence on the period of performance start date, which will constitute the phase-in period. During the phase-in period, the Contractor shall prepare to assume full responsibility for all areas of operation in accordance with the terms and conditions of this contract. The Contractor shall take all actions necessary for a smooth transition of the contracted operations. This period will be up to a maximum of thirty (30) calendar days in duration. The Government will make all facilities and equipment accessible to the Contractor within the designated period prior to the performance start date. During the phase-in period, the Contractor shall, at a minimum:

i. Establish the Project Management Office,

ii. Recruit and hire necessary personnel,

iii. Obtain all required certifications and clearances, including personnel security clearances,

iv. Participate in joint inventories and sign for government-furnished property (GFP),

v. Develop and submit any required deliverables,

vi. Attend post-award meetings as required,

vii. Accomplish any necessary training to support the functions listed in the PWS.

1.4.1.2 Phase-Out Period/Transition. Thirty (30) calendar days prior to the completion of the Contract, an observation period shall occur at which time management personnel of the incoming workforce may observe operations and performance methods of the incumbent Contractor. This will allow for orderly turnover of facilities, equipment, and records and will help to ensure continuity of service. The Contractor shall not defer any requirements for the purpose of avoiding responsibility or of transferring such responsibility to the succeeding Contractor. The incumbent Contractor shall fully cooperate with the succeeding Contractor’s attempts to perform phase-in activities. During the phase-out period, the incumbent Contractor shall perform the following tasks:

i. Notify the incumbent contractor employees of the date when the contract will end, and the name and contact information for the successor contractor no later than five (5) days after award is announced by the contracting officer.

ii. Disclose necessary personnel records and allow the successor to conduct on- site interviews with incumbent contractor employees.

iii. If incumbent contractor personnel are agreeable to accepting employment with the successor contractor, release such personnel at a mutually agreeable date.

iv. Turn-over of work-in-progress to the successor contractor or Government personnel, as directed by the COR.

v. Perform inventories of Government property with Government personnel and/or the successor contractor, as directed by the COR.

vi. Remove contractor property from the Government workspace.

vii. Perform data and information transfer to the successor contractor and/or Government personnel, as directed by the COR; and,

viii. Perform any other actions required to ensure continuity of operations.

Full performance shall be maintained during the entire period. The rights and obligations in this provision are independent of those in FAR 52.237-3, Continuity of Services.

1.4.2 Statement of Non-Disclosure. All Contractor personnel shall comply with the non-disclosure requirements in the clause at Federal Acquisition Regulation (FAR) section 3.104-5(b) (or DFAR equivalent). All Contract Personnel must sign a non- disclosure agreement (NDA) prior to access to work-related materials as required.

Privacy Act. All contractor personnel assigned to this task shall have access to information that may be subject to the Privacy Act of 1974. The contractor shall brief its personnel on compliance with Privacy Act requirements with-in 30-days employment.

1.4.3 Personnel. The Contractor shall provide all necessary personnel and managerial resources for execution of this contract.

1.4.3.1 Supervision. Contractor personnel are employees of the Contractor and under the administrative control and supervision of the Contractor. The Contractor shall select, supervise, and exercise control and direction over its employees; however, the Contractor shall not supervise, direct, or control activities of Government personnel or the employees of other Contractors. The Contractor shall be responsible for the actions of its personnel and shall follow installation and Army regulations.

1.4.3.2 Hours of Operation. Government facilities will be available from 0630 through 1830 hours, five days per week, Monday through Friday, excluding federal holidays, holidays declared by Executive Orders, and emergencies. Federal Government holidays are as follows:

1.4.3.3 Privacy Requirements/Security. Work on this contract will require that Contractor personnel have access to sensitive, privileged, or Privacy Act information. Personnel shall adhere to the Privacy Act, (5 U.S.C. § 552a) and applicable Agency rules and regulations. Contractor personnel shall not divulge, or release privacy data or information developed or obtained in the performance of this contract award, until made public or specifically authorized by the Government. The Contractor shall not use, disclose, or reproduce a third-party company’s proprietary data, other than as authorized and required in the performance of this contract award. The Contractor shall notify the Primary COR within 24 hours, identifying personnel that no longer require access to Government information systems.

Contractor personnel working on this contract may be required to have access to classified materials or work in classified spaces. Clearances, work location, and travel requirements for every task in this PWS are identified at the end of each section of the PWS. The majority of positions require SECRET level clearances, and some amount of the work requires TOP SECRET clearances, as identified in the PWS and the DD 254. The Government will identify all classified material at the appropriate level. A background investigation is required for SECRET level access. Contractor personnel shall adhere to the following regulations:

i. Army Regulation (AR) 25-1, paragraph 5-3c, the Army Knowledge Management and Information Technology.

ii. Use of Government Property, 5 CFR 2635.704.

Security clearance requirements for every PWS Functional Area are also identified in the Work Breakdown Structure (WBS) for proposals.

1.4.3.4 Email Services. It is required for all contractors to conduct Government business and communications on Gov provided capabilities only (Army email, Army Teams, SPO, and transition to Army ADO). The CTR provided Dev Environment is an exception to this policy, until the time an appropriate Dev environment exists in cARMY. This policy is outlined in AR 25-1.

1.4.3.4.1 Use of official Government email service. Army personnel will use only Government-provided email services to conduct official business unless otherwise authorized (AR 25-1, para 4–8b). Email services provided by a commercial service provider are prohibited for Army business communications containing sensitive information. Automatically forwarding from an official Government account to an unofficial (commercial service) is prohibited. “Auto-forward” default settings on email will restrict individuals from automatically forwarding their email messages to commercial (private) addresses. There is no prohibition for manually forwarding email messages, one at a time, after opening and reading the content to ensure that the information is not sensitive or classified.

1.4.3.4.2 Use of unofficial Government email service. Law and DOD policy are clear: "non-official electronic messaging accounts," including personal email accounts, must not be used to conduct official DOD communications, with very few exceptions, and intentional violations of this may be the basis for disciplinary action. Personal or other non-official email accounts may be used for official business only in those rare and extraordinary situations where an official email capability is not available. When this happens, the CTR shall copy his/her official email account at the time of sending or forward the message to his/her official account within 20 days of sending the email. In doing so, the sender shall mitigate against transmitting non-public or controlled unclassified information. Classified information may never be transmitted over any unclassified networks, whether DOD or commercial.”

1.4.3.5 Contractor Identification. The Contractor’s personnel performing work shall conspicuously display on their person a Contractor-furnished photo identification badge while on duty, as well as a Government-issued photo identification badge. The badge shall display, at a minimum, the employee’s full name and legal name under which the Contractor is doing business. Contractor personnel shall wear badges at all times and shall identify themselves as Contractors at meetings, emails, telephone conversations, etc.

1.4.3.6 Security Requirements. The contractor shall comply with all appropriate Government security directives and regulations. In accordance with (IAW) Army Regulation and Air Force Instructions, all prospective contractors shall undergo a verification process to determine the trustworthiness and suitability prior to being granted access to federal property. Contract Company Security Managers shall submit all background investigations on prospective contractors requiring CAC and/or network access.

i. Contractors shall establish an owning relationship in Defense Information Security System DISS for each individual performing duties in support of this performance work statement. Facility Security Officers (FSO) will send a Visit request (VR) using DISS or for all contractors requiring access to facilities, classified information, access to information systems and/or if required to maintain a clearance IAW the presiding contract. This will help ensure that employees are not denied entry to the installation. No access will be given until the verification can be completed in DISS. Visit request is only valid for one year. The contractor shall be vetted on a reoccurring basis. For contractors, the minimum requirement for access to classified federal information systems is as follows: IT- II access, a T5, T5R, SBPR, PPR, IT-II access, T3, T3R,); and IT- III access, a T1.

ii. IAW Army Regulation and Air Force Instructions, all prospective contractors shall undergo a verification process to determine trustworthiness and suitability prior to being granted access to government networks and federal property. Limited access with escort may be granted (at the installation's discretion) for an interim period while investigations are being conducted.

iii. The common access card (CAC) is the DOD personal identity verification credential. In order to receive a CAC, every employee must be investigated as part of the HSPD-12 process. The type of investigation used in compliance with HSPD-12 adjudications is the T1. The T1 serves as the minimum type of investigation required to be issued a CAC and installation access. It consists of several elements, including database and local agency checks as well as written inquiries. CACs will not be issued before the fingerprint check results have been completed and the investigation has been submitted. All fingerprints and the appropriated investigation will be submitted by the government.

The Contractor shall be responsible for notifying the Government when an employee departs so the CAC card access can be inactivated. The security manager and or trusted agent shall be responsible for retrieving the CAC from a departing contractor.

iv. The awarding contracting company must have a valid facility clearance at the time of award.

v. Anti-Terrorism (AT) Level I Training. All contractor employees, to include subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete AT Level I Awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 30 calendar days after completion of training by all employees and subcontractor personnel. AT level I Awareness training is available at the following website: http://jko.jten.mil.

vi. AT Awareness Training for Contractor Personnel Traveling Overseas. This standard language requires U.S.-based contractor employees and associated subcontractor employees to make available and to receive government-provided AT awareness training specific to the area of responsibility (AOR) as directed by AR 525-13. Specific AOR training content is directed by the combatant commander, with the unit Anti-Terrorism Officer (ATO) being the local point of contact.

vii. Access and General Protection/Security Policy and Procedures. The contractor and all associated subcontractors' employees shall comply with applicable installation, facility, and area commander installation and facility access and local security policies and procedures (provided by the Government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services, or Security Office. The contractor workforce must comply with all personal identity verification requirements as directed by DoD, HQDA, and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

viii. iWATCH Training. The contractor and all associated sub‐contractors shall brief all employees on the local iWATCH Army program (training standards provided by the requiring activity ATO). This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 10 calendar days after contract award.

ix. Threat Awareness Reporting Program (TARP). The Government shall provide all contractor employees, to include subcontractor employees, annual TARP training by a Counter-Intelligence agent or other trainer. Contractors may be tasked for the Opening and Closing of collateral Open Storage Areas and Sensitive Compartmented Information (SCI) Open Storage Areas, within TRADOC G-2 facilities. The contractors shall have the appropriate clearance, access, and need-to-know when accessing and handling classified materials.

x. Contractor Employees Who Require Access to Government Information Systems. All contractor employees with access to government information system must be registered in the Army Training Certification Tracking System (ATCTS) at commencement of services and must successfully complete the DoD Information Assurance Awareness training prior to access to the information system and then annually thereafter.

xi. The contractor shall adhere to the TRADOC operational security (OPSEC) Plan, including OPSEC Training. Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within 30 calendar days of reporting for duty. All contractor employees must complete annual OPSEC awareness training. This training is mandatory.

xii. For Information Assurance (IA)/Information Technology (IT) Training. All contractor employees and associated subcontractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working in IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M, and AR 25-2 within six months of employment.

xiii. For Information Assurance (IA)/Information Technology (IT) Certification. Per DoD 8570.01-M, DFARS 252.239.7001, and AR 25-2, the contractor employees' supporting IA/IT functions shall be appropriately certified within 6 months of assignment to a position. Personnel who are not appropriately qualified within 6 months of assignment to a position or who fail to maintain their certification status shall not be permitted privileged access.

xiv. Physical Security. The contractor shall be responsible for safeguarding all Government equipment, information and property provided for Contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

xv. Intelligence Oversight. All contractor employees, including subcontractor employees, conducting intelligence or intelligence-related activities or supporting those efforts under SECARMY authority will ensure the contract requires contractor personnel to complete Intelligence Oversight training within the first 30 days on contract and refresher training annually. All G2 CORE Contractors are to report any QIA or S/HSM to the TRADOC Intelligence Oversight Officer. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee to the COR within 30 calendar days after completion of training by all employees and subcontractor personnel.

1.4.3.7 Key Personnel. Certain experienced professional and/or technical personnel are essential for successful accomplishment of the work to be performed under this contract. The following two (2) positions are identified as Key Personnel for the performance of this contract:

1.4.3.7.1 Contract Program Manager (PM). The Contractor PM shall provide complete program management support that fully integrate, manage, control, and document all phases of the PWS requirements. The Contractor PM shall be the focal point for all issues for this effort and shall keep the Government fully informed on OE CORE status and events both verbally and in writing. The PM shall have:

1.4.3.7.1.1 Demonstrated successful prior experience managing a Government contract similar in size and nature to this requirement over a 3–5-year period or a minimum of 3-5 years managing a military organization similar in size and nature to this requirement, with demonstrated ability to resolve performance, cost, and schedule problems quickly.

1.4.3.7.1.2 3-5 years of technical program management experience.

1.4.3.7.1.3 Minimum 8-10 years military experience, and knowledgeable about TRADOC and its missions.

1.4.3.7.1.4 Strong personal, oral, and written communications skills appropriate for senior level audiences.

1.4.3.7.1.5 TS/SCI clearance required.

1.4.3.7.2 Senior Systems Architect (reference para 5.3.4 of the PWS). The Contractor shall provide an experienced Senior Systems Architect to support the TRADOC G2 OEE transformation into a Data Centric Organization by acquiring, transforming, transferring, and maintaining data and information to replicate the OE for Leader Development, Training, Education, Capability and Concept Development, Experimentation, and Home Station Training across the Army. The Senior Systems Architect shall have:

1.4.3.7.2.1 3 -5 years' experience designing IT architecture and systems integration at the enterprise level that fits within the Department of Defense Architecture Framework (DoDAF) - DoD's framework that provides visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views.

1.4.3.7.2.2 Experience resolving problems integrating existing systems and application architectures.

1.4.3.7.2.3 Experience with Security and compliance activities necessary to maintain system accreditation (to include documentation and mitigation).

1.4.3.7.2.4 Skills in executing the following tasks: requirements analysis, risk management, configuration management and verification, backup architecture management, infrastructure maintenance, and process documentation.

1.4.3.7.2.5 Must be eligible to obtain and maintain a Secret Clearance.

1.4.4 Travel. Guidance for Contractor travel can be found in FAR 31.205-46, the General Services Administration Federal Travel Regulations (FTR), DoD Joint Travel Regulations (JTR) and Department of State Standardized Regulations (DSSR).

1.4.4.5 Travel Requests. All requests for travel shall be submitted for review and approval by the COR prior to incurring cost, as travel will be reimbursed IAW the FTR, JTR, and/or DSSR. Contractors shall minimize the number of travelers and rental cars, and travel shall be scheduled during normal duty hours whenever possible. Requests for travel approval shall be prepared and processed through the COR, including a description of proposed travel, a list of travelers, the contract number, Contract Line-Item Number (CLIN), and be submitted at least 48 hours prior to travel for approval (see PWS para 6.1.8 and PWS Attachment C).

1.4.5 Data Rights. “Data rights” refer to the Government’s nonexclusive license rights in two categories of valuable intellectual property, “technical data” and “computer software” delivered by the contractor under task orders issued under this contract. Data Rights shall be governed by the applicable FAR and DFARS clauses incorporated in this contract. The Data Rights clauses incorporated in this contract are: FAR Clauses 52.227- 1, 52.227-2, 52.227-17, 52.227-18, 52.227-19, 52.227-20, and DFARS Clauses 252.227- 7013, 252.227-7014, 252.227-7015, 252.227-7016, 252.227-7017, 252.227-7019, 252.227-7025, 252.227-7027, 252.227-7028, 252.227-7030, 252.227-7037, 252.246- 7001.

1.5 Export Requirement. Contractor may be required to travel outside the United States and to be responsible, as authorized under the International Traffic in Arms Regulations (ITAR) (22 CFR §§ 120-130), specifically, ITAR § 125.4(b) (3) and § 126.4(a), for exporting and temporarily importing defense articles including technical data presentations, manuals, training materials, (loaded via hard drive, CD-ROM), and for performing defense services in support of the this requirement. When requested, the contractor shall provide proof of compliance with DFARS 252.204-7008 to the KO and/or COR.

1.6 Special Contract Requirements. This PWS contains optional support tasks, and two different types of requirements (firm-fixed-price and time-and-materials). These special requirements impose unique processes in order to properly execute and administer.

1.6.3 Optional Support Tasks. There are six (6) specific tasks that are strictly optional; meaning, these tasks will require performance only when exercised via contract modification issued by the KO. These tasks are: (i) 5.3.2, OE Support Division; (ii) 5.3.4, Intelligence Surveillance and Reconnaissance Integration, (iii) 5.3.5, Joint Intelligence Surveillance and Reconnaissance Support; (iv) 5.3.7, Threat Emulation Force, (vi) 5.3.8, Network Engagement Training, and (vi) 5.4.1, Red Team Support. These tasks will be priced separately, based upon competed, firm- fixed-price amounts, and have its own contract line item in Section B of the awarded contract. When the TRADOC G-2 has a need for any of these optional support tasks as defined in its corresponding PWS paragraph, the Contracting Officer will issue a modification to add appropriate funds to exercise those CLINs for the required amount of time. There is no guarantee that optional support tasks will be exercised.

1.6.4 Time-and-Material (T&M) Requirements. This PWS primarily consists of firm- fixed-price requirements; however, there are some areas that will require T&M support due to the nature of the requirement. PWS paragraph 5.3.7 is primarily T&M type requirements, with the exception of its corresponding ‘Key’ personnel. There are also ad hoc requirements that will arise in other functional areas contained in the PWS that will be related/in-scope. The contractor shall not incur T&M costs unless and until they receive written direction from either the COR or the Contracting office. Both areas will follow the process below.

1.6.4.5 T&M Administration Process. TRADOC G-2 Directors develop Technical Letters of Instruction (Tech LOIs) for COR approval which will clearly identify which existing contract tasks the work to be performed fits within, the appropriate labor category that will be listed on the contract after award, and an estimated number of hours. The COR will prioritize the Tech LOIs for internal TRADOC G-2 Technical Review Board approval. Once approved, the COR will pass the Tech LOIs to the KO and Contractor; the Contractor will then propose the labor category(ies) with rate(s) as stated in the awarded contract (applying any discounts if desired), number of estimated labor hours, estimated material and travel needed to perform, and will provide a total estimated cost (referred to herein as a ‘rough order magnitude’ (ROM)) which the KO and COR will review and approve if appropriate. The COR will assign a ROM approval number and will track each event to include the approved estimated values, time sheets, and actual expended amounts. THE CONTRACT WILL INCLUDE A CEILING PRICE THAT THE CONTRACTOR EXCEEDS AT ITS OWN RISK.

1.6.4.6 T&M Deliverables. T&M deliverables are defined in PWS para 6.1.7 and in Section C-8.

SECTION C-2 ACRONYMS

2.0 Acronyms and Definitions. The following terms, as used throughout this Operational Environment/Core Functions Performance Work Statement, have the meaning set forth below.

SECTION C-3 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.0 Government-Furnished Property (GFP) and Services. The Government will provide workspaces/desks (not standing desks), chairs, and office automation to include computer(s), telephones, printers, etc. as necessary by the work performed for each contractor personnel. TRADOC G-2 Government personnel will determine property disposition, acquisitions, and final acceptance of deliveries of services/supplies. The Contractor shall not engage in inherently governmental functions associated with service/supply acquisition management (see FAR Subpart 7.5).

SECTION C- 4 CONTRACTOR-FURNISHED PROPERTY AND SERVICES

4.0 Contractor-Furnished Property and Services. The Contractor shall be responsible for providing vehicles, simulated weapons, and equipment necessary for the OPFOR to employ capabilities IAW threat doctrine to meet OT&E requirements at wargames, experiments, tests, and evaluations. Contractor must have the ability to produce or procure threat systems as they emerge in the OE. Costs for all Contractor-furnished vehicles, simulated weapons, and equipment to replicate threats in support of the Threat Emulation Force (TEFOR) task 5.3.7 will be billed to the Government as material rental charges. Vehicles, simulated weapons, and equipment must arrive on-site at each event in CONUS at least one day before the start of each event. Items the Government will rent as materials to replicate the OPFOR include (but are not limited to):

· 6-8 Threat technical vehicles per event, 2-3 times per year, at various locations including Fort Benning, Fort Bliss, Fort Stewart, Fort Hood, and White Sands Missile Range.

· Simulated weapons (examples: RPK, AK47, UZI, MAC 10, SKS, DSHK, 20mm, KORNET and RPG-29 simulators, RPG 7, and simulated side arms to replicate criminal, non-state, and foreign governments. Enough simulated weapons are needed to outfit 20-40 role players per event.

· MILES systems for Threat crew served weapons that are compatible with TRADOC MILES inventories. One MILES transmitter is needed on each simulated weapons system per event.

· Aerial reconnaissance support for security, offense, and defense missions with Threat sUAS to support OPFOR actions in the live OT&E environment. sUAS systems must comply with all Federal, State, and local regulations. They must include video downlinks provided at the proper frequencies and power settings. An estimated 1-2 events per year will require sUAS support.

· Aerial reconnaissance support includes a DJI Phantom 4 RW sUAS team, a Turbo Ace Matrix-I RW sUAS team, and a MTD FW sUAS team with equipment.

The rental costs for contractor-furnished vehicles, simulated weapons, and equipment necessary to replicate the OE in support of TEFOR must be included in the contractor’s quoted proposal.

SECTION C-5 SPECIFIC TASKS

5.0 Specific Functional Areas. The following figure depicts the organization of specific tasks within this PWS.

NOTE: There are six (6) specific tasks that are strictly optional; meaning, these tasks will require performance only when exercised via contract modification issued by the KO. There is no guarantee that optional support tasks will be exercised.

5.1 Mission Support. The Contractor shall provide support in the following areas.

5.1.1 Information and Data Management (Information Technology (IT) and Knowledge Management (KM)) support to TRADOC G-2. Information and Data Management (IDM) includes the functions of Enterprise Architecture, IT Service Support (ITSS), Digital Systems (DS) Development and Sustainment, Cyber Security (CS), and Data and Knowledge Management (DKM).

5.1.1.1 Provide Enterprise Architecture Support. The Contractor Shall:

5.1.1.1.1 Provide architecture development and analysis for the OEE. For example: update architecture documentation (DoDAF), conduct architecture-based analysis of enterprise capabilities, recommend solutions to OEE information/data exchange issues, administration of an OEE Architecture Working Group, and ensure compliance with the Army Common Operating Environment (COE) requirements.

5.1.1.1.2 Conduct feasibility studies of computer and networking technology to facilitate a wide range of general and special purpose systems in support of the TRADOC G-2. These duties include developing concepts and strategies for the integration and interoperability of numerous components that structure and support major networks.

5.1.1.1.3 Provide technical guidance and analysis on existing, new, and emerging automation technologies for TRADOC G-2 customers.

5.1.1.1.4 Perform ongoing technical analysis of network design characteristics to determine the need for suitable equipment, system component interfaces, expansion capabilities, and specific operational features. The TRADOC G2 currently has equities in local NIPR, SIPR, and JWICS, and Cloud resources in TRADOC G6 Azure Cloud IL2/4, cARMY Azure Cloud IL2/4/6.

5.1.1.1.5 Support TRADOC G2 IT and KM governance. Specifically provide ITIL functions of Change, Configuration, and Release Management, and a Configuration Management Database (CMDB). Assist TRADOC G2 CIM to develop TRADOC G2 enterprise governance policies and processes.

5.1.1.2 Provide IT Service Support (ITSS) including: Help-desk request ticket response, communication support, and network support in non-secure, secure open storage and SCIF environments as appropriate. The Contractor shall:

5.1.1.2.1 Provide help desk support for all G-2 personnel at Fort Eustis, Virginia and Fort Leavenworth, Kansas on JWICS, SIPRnet, and NIPRnet PC and network support, In Coordination with (ICW) the Regional or Local Network Enterprise Center (RNEC/LNEC). The Government estimates 400 helpdesk tickets will need to be resolved per annual period of performance at Fort Eustis, Virginia and Fort Leavenworth, Kansas, combined.

5.1.1.2.2 Ensure all ITSS personnel are credentialed, ICW DoDI 8140, with an operating system and Security certifications (i.e. Microsoft and COMPTIA Security +) for ITSS and Help Desk Tasks.

5.1.1.2.3 Provide installation, configuration, and set-up of computer support for TRADOC G-2 end users at Ft Leavenworth, KS and Fort Eustis, VA, ICW RNEC/LNEC. The Contractor is required to support approximately 262 customers on NIPRnet; 210 customers on SIPRnet and 58 customers on the JWICS network (including the TRADOC Command Group personnel). Leavenworth: 70+/- customers on NIPRnet; 48 on SIPRnet; and 30 +/- on JWICS. Additional special purpose networks include: : Commercial, Battle Lab Collaborative Simulation Environment (BLCSE), and Battlefield Information Collection and Exploitation System (BICES).

5.1.1.2.3.1 Standard imaging over network connection, PXE boot, or “iso” are used. Individual setup for users takes approximately 1 hour and then standard imaging takes approximately 1 additional hour.

5.1.1.2.3.2 Standard imaging comprises 70% of the overall system builds.

5.1.1.2.3.3 30% of systems/users require unique setup requiring additional time and third-party applications.

5.1.1.2.3.4 Approximately 15% of TRADOC G-2 users require non-domain “stand-alone” systems for conferences, travel, and telecommuting; these non-standard systems are primarily laptops fitted with specific classification requirements.

5.1.1.2.4 Serve as a Telephone Maintenance Officer (TMO) for TRADOC G-2 LAN connect phones and mobile devices. Respond to all telephone and mobile device issues for 262 personnel for both analog and digital equipment, unclassified and classified. There are 350 phone systems for these personnel (including desk telephones, secure telephones, and mobile devices).

5.1.1.2.5 Provide technical and professional support to VTC operations, applications, and administration to JWICS , other special mission networks and, as required, NIPR and SIPR. TRADOC G-6 currently provides generic VTC support (NIPR & SIPR). TRADOC G-6 does not provide support to JWICS and other special mission networks.

5.1.1.2.6 Serve as an Alternate communications security (COMSEC) custodian.

5.1.1.2.7 Evaluate, design, implement, and sustain all data communication operations and networking infrastructure within the TRADOC G-2.

5.1.1.2.8 Install, maintain, and upgrade network interfaces and monitor the interaction of network hardware and software.

5.1.1.2.9 Asset Management. In support of TRADOC G-2’s asset manager, assist to perform asset management and equipment lifecycle functions supporting the addition, tracking, removal, and disposition of Information Technology equipment for TRADOC G- 2. Maintain database for tracking TRADOC G-2 Information Technology (IT) equipment located at Fort Eustis and Fort Leavenworth. The Contractor shall:

5.1.1.2.9.1 Prepare Hand-Receipt and Non-Hand-Receipt equipment for turn-in to the Property Book Office (PBO) and for issue to TRADOC personnel. Maintain signed copies of Hand Receipts on file for IPBO, FMO, real property and durable property/5K and below in accordance with AR 710-2, para 2-10g. Ensure all required DA Form 1687 signature cards are current and complete with received dates and signatures in accordance with AR 710-2 and ALARACT 025/2012. Ensure sub hand receipts are on file and filled out properly in accordance with DA PAM 710-2-1, para 5-3a and 5-3c, Figure 5-1.

5.1.1.2.9.2 Generate DA Form 3161 Turn-In documents for Hand Receipt and Non-Hand Receipt equipment being turned into the Installation Property Book Office and DA Form 2062 Hand Receipts for equipment being issued to TRADOC personnel. Remove, document, and prepare labels, degauss and destroy Hard Drives from computer systems in preparation for equipment Turn-In to the Property Book Office (PBO).

5.1.1.2.9.3 Assist TRADOC G-2 with conducting annual inventories of durable property in accordance with AR 735-5.

5.1.1.3 Digital Systems Support. The Contractor shall provide personnel to perform the functions of Senior Systems Architect, Senior Software Engineer, Enterprise Manager, and Software Developers to support the TRADOC G2 OEE as a DevSecOps (Development Security Operations) Software Development Organization; for the purpose of developing, maintaining, and sustaining web applications and software tools to support the OE for Leader Development, Training, Education, Capability and Concept Development, Experimentation, and Home Station Training across the Army.

5.1.1.3.1 Digital System Enterprise Support. The Contractor shall design, develop, and maintain a suite of core software capabilities to support the DevSecOps execution to include, but not limited to, a policy library, build server, logging server, static code scanner, container repository, container scanner, and other supporting architecture. The Contractor Shall:

5.1.1.3.1.1 Develop data analytic and machine learning tools and applications to transform, exploit, and visual OE data and information.

5.1.1.3.1.2 Provide matrixed (from existing resources) capability development teams to work closely with OEE customers (units/organizations requiring support) in order to develop capabilities that match the needs.

5.1.1.3.1.3 Create project plans for each initiative, data ingest, or data application/tool creation to ensure delivery of a timely and high-quality solution.

5.1.1.3.1.4 Use Open-Source software whenever and wherever possible.

5.1.1.3.1.5 Support and implement the architectural design for the Digital Systems Capability.

5.1.1.3.1.6 Perform enterprise-level administration and management of the Digital Systems Capability.

5.1.1.3.1.7 Modify both the design and the implementation as necessary in order to maintain a state-of-the-art capability reflective of both industry and DoD changing best practices; e.g. ‘cloud’, ‘big data’, etc.

5.1.1.3.2 OE Mission Systems, development, maintenance, sustainment, and support . The Contractor shall:

5.1.1.3.2.1 Maintain the suite of TRADOC G2 Tools (Information Operations Network (ION), Exercise Support Application (ESA), Traffic Integration and Messaging System – Live (TiMS Live), Operational Environment (OE) Data Integration Network (ODIN), Virtual OPFOR Academy, and OE-Visualization on testing, staging, and production environments (NIPR/SIPR) within Army Cloud environments.

5.1.1.3.2.2 Prepare to rapidly move user-defined requirements into production to support soldier usability and adoption.

5.1.1.3.2.3 Maintain the current Agile DevSecOps development methods and structures and processes for requirement approval and prioritization. This will include moving individual capability enhancements to production in an accelerated manner.

5.1.1.3.2.4 Provide enterprise-level capabilities, processes, and support (e.g. training, documentation, data, or Program of Record communities).

5.1.1.3.2.5 Provide best practice capability development activities; e.g., requirements review, work task management, testing, and release management.

5.1.1.3.2.6 Provide planning support to expand capabilities into Joint environment, other Services or Allied partner environments as necessary.

5.1.1.3.3 System Administration and Configuration Support. Support and system administration shall be provided for all TRADOC G2 mission systems and web applications hosted on-premises and Cloud. The Contractor shall:

5.1.1.3.3.1 Monitor open problem reports, verifying problem resolution with clients and escalating unresolved problem reports to next support level or appropriate outside vendor support.

5.1.1.3.3.2 Assist in instructing staff in the use of standard operating systems, business and administrative software, including word processing, spreadsheets, database management, email, and internet browser, providing instructions or written documentation when needed.

5.1.1.3.3.3 Develop a library of standard operating procedures dealing with installation and support of common computer hardware and software.

5.1.1.3.3.4 Perform daily, weekly, monthly, quarterly and annual systems maintenance tasks.

5.1.1.3.3.5 Help develop and implement IT standards and best practices to ensure a high-degree of user satisfaction.

5.1.1.3.3.6 Create and maintain comprehensive documentation for all computer systems, and documenting system and procedural changes as needed.

5.1.1.3.3.7 Configure and maintain remote access solutions such as Remote Desktops Services, VPN, SSL, etc.

5.1.1.3.3.8 Set up, install, configure, administer, maintain, monitor, and support physical, virtual, and cloud servers including Windows , Linux, Virtualization Software (VMware ESX/vSphere, Virtual Box, Hyper-V) and other Server Applications products to include federal cloud. (These tasks are not applicable to G-2 Leavenworth activities at this time)

5.1.1.3.3.9 Manage, administer, and maintain Backup Systems and storage technologies.

5.1.1.3.3.10 Administer of server applications such as Apache, IIS, Active Directory, Virtualization Software, SQL, and others.

5.1.1.3.3.11 Analyze and plan for changes in data requirements and interfacing between different but interdependent data systems.

5.1.1.3.3.12 Ensure the rigorous application of information security/information assurance policies, principles, and practices in accomplishing the data management functions of this job.

5.1.1.3.3.13 Apply revisions to host system firmware and software.

5.1.1.3.3.14 Setup and operate security scanning tools such as ACAS, Burp Suite, TRVY, and SonarCube.

5.1.1.3.3.15 Utilize AESMP or the standard government…