PWS draft.docx

PERFORMANCE WORK STATEMENT (PWS)

FORMATION BASED LAYERED PROTECTION FUTURE CAPABILITY DIRECTORATE

(FBLP FCD) EXPERIMENTATION DIVISON (ExDIV)

INFORMATION TECHNOLOGY (IT) & SIMULATION SUPPORT

PART 1

GENERAL INFORMATION

1. General: This is a non-personal service(s) requirement under which the personnel rendering the service(s) are not subject, either by the contract’s terms or by the manner of its administration, to the supervision and control usually prevailing in relationships between the Government and its employees.

1.1. Description of Services: This is a non-personal service(s) requirement to provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform simulation support, as defined in this Performance Work Statement (PWS) except for those items specified as government furnished property and services.

1.2. Background: The U.S. Army Formation Based Layered Protection Experimentation Division (FBLP ExDIV) is a critical asset in the Army and the Department of Defense for simulations and analysis in support of U.S. Army Maneuver Support Center of Excellence and Chemical, Engineer, and Military Police Corps issues. The FBLP ExDIV supports the Army Vision, the Army Modeling and Simulation Master Plan, and Army Transformation efforts by conducting experimentation and analysis to assess warfighting concepts, design forces, determine requirements, and evaluate Doctrine, Organizations, Training, Materiel, Leadership and Education, Personnel, and Facilities (DOTMLPF) concepts and programs for the Maneuver Support Center of Excellence (MSCoE). Gathering data to underpin analysis to inform decision makers at all levels is the primary task of the FBLP ExDIV and the primary avenue for generating that data for analysis is through computer-based experimentation and studies.

1.3. Scope: The Contractor shall provide non-personal service(s) pertaining to IT administration and simulation support functions.

1.4. Objectives: The objective of this requirement is to enable and provide system administration, IT support, and complete simulation execution/support tasks for studies and events led by/with contributions from the FBLP ExDIV.

1.5. General Information:

1.5.1 Quality Control Plan (QCP): The Contractor shall develop and maintain a QCP to ensure services are performed in accordance with (IAW) this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractor's QCP is the means by which it assures that the work provided complies with the requirements of the contract.

1.5.1.1 The Contractor’s Proposed QCP shall be submitted to the Contracting Officer (KO) through the Contracting Officer’s Representative (COR) for review within ten days after contract start date.

1.5.1.2 The Government will review and either notify the Contractor in writing of acceptance of the plan or return their comments to the Contractor within 15 workdays. If the Government has provided comments, the Contractor shall then have 10 workdays to submit a Final QCP. After receipt of the Final QCP, the Contractor may receive the Contracting Officer’s acceptance in writing. Any proposed changes to the accepted QCP are required to be resubmitted for acceptance by the Contracting Officer no later than 30 workdays prior to the anticipated change and before implementation by the Contractor. The timeline noted above will apply for review and acceptance for proposed changes. At a minimum, the QCP must include and answer the following to be acceptable:

1.5.1.2.1 A chart showing the organizational structure and lines of authority, the names, qualifications, duties, responsibilities, and classification of each member of the Contractor's Quality Control Team;

1.5.1.2.2 How the Contractor will monitor work to ensure performance complies with all deliverables (etc. timelines, deadlines, and goals);

1.5.1.2.3 How the Contractor will monitor work to ensure performance complies with all specifications and requirements of the contract, including the contract’s clauses;

1.5.1.2.4 How the Contractor will monitor and ensure staff qualifications remain current and valid including Department of War (DoW) Contractor Personnel Office (DOCPER) processes/approvals throughout contract performance;

1.5.1.2.5 How the Contractor will inventory, and track maintenance of all Government Provided Equipment / Materials;

1.5.1.2.6 How the Contractor will identify, investigate, and correct any non-conforming performance and prevent similar deficiencies in the future; and

1.5.1.2.7 How the Contractor will file and save all Quality Control related documents for the life of the contract plus five years.

1.5.1.2.8 The Contractor shall inform the COR of issues or potential issues that might affect the performance within one workday of identifying those issues. Verbal reports shall be followed by written reports within three workdays.

1.5.2 Quality Assurance: The Government will evaluate the Contractor’s performance under this requirement.

1.5.3 Recognized Holidays: The following provides information on recognized holidays for the purpose of the PWS. If submittal of any documentation (e.g. deliverables, submittals, etc.) deadlines fall on a holiday, the closest workday prior to the holiday will apply as the deadline for submittal.

1.5.3.1 U.S. Holidays: Work shall not be performed on U.S. federally recognized holidays occurring during the normal workweek unless otherwise directed by the Contracting Officer. When a U.S. holiday occurs on a Saturday or a Sunday, the holiday is observed on the preceding Friday or following Monday, respectively.

1.5.4 Hours of Operation: The Government facility office hours, facility operating hours, and the Contractor support hour requirements often coincide, however, they may differ. Please refer to the following:

1.5.4.1 Government Facility Operating Hours: The Contractor is responsible for conducting business, between the hours of 0730 and 1630 central time, Monday through Friday except U.S. Holidays identified in paragraph 1.5.3.1 above or when the Government facility is closed due to local or national emergencies, administrative closings, executive orders, or similar Government directed facility closings.

1.5.4.2. Weekends and After-Hours Support: On occasion, the Government anticipates the needs for Contractor support at times other than the normal Government operation hours noted above. In such situations, the Contracting Officer’s Representative (COR) will provide at least three working days in advance notice of the reasons and the anticipated dates and times for such support. The Government estimates approximately 80 man-hours of weekend and after-hours support shall be required during the period of performance (PoP). In each such situation, Government will provide facility access and escort. Contractor shall provide the weekend and after hour support at no additional cost to Government.

1.5.4.3 Contractor Support Hours: The Contractor shall provide support between the hours of 0730 and 1630 central time. The Contractor shall maintain an adequate workforce at all times, for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce is essential.

1.5.5 Place of Performance: The work to be performed under this contract will be performed at FBLP ExDIV facilities at FLW, Missouri.

1.6 Security Requirements: The following information is provided on security related matters.

1.6.1 Security Program: Contractor personnel performing work under this contract must have a Tier 3 Security Clearance at time of the proposal submission and must maintain the level of security required for the life of the contract. The security requirements are IAW with the DOW Contract Security Classification Specification (DD Form 254), which is currently accessible at the following link: http://www.dtic.mil/whs/directives/forms/eforms/dd0254.pdf

1.6.2 Personnel Security Clearance Requirements: Contractor personnel performing work under this contract must have an active personnel security clearance at the Tier 3 Level in the Defense Information System for Security (DISS) at time of the proposal submission and must maintain the level of security required for the life of the contract. The security requirements are IAW the DoD Contract Security Classification Specification DD Form 254. The Contractor shall ensure that Contractor employees and subcontractor employees performing services under this contract comply with FAR 52.204-2 Security Requirements when the employee has access to information classified “Confidential,” “Secret,” or “Top Secret.” The Contractor shall ensure the employee complies with the DoD Security Agreement (DD Form 441), and the NISPOM rule at 32 Code of Federal Regulation (CFR) Part 117, effective 24 Feb 2021. The NISPOM is the National Industrial Security Program Operating Manual to which contractors must implement and comply. The Contractor shall ensure that all assigned personnel understand applicable security policies and directives. Personnel who knowingly violate security policies or directives are subject to immediate removal from any compensated work relating to this requirement.

1.6.3 Installation Access: Access to U.S. installations, buildings and controlled areas is limited to personnel who meet security criteria and are authorized. Failure to submit required information/data and obtain required documentation or clearances will be grounds for denying access to U.S. installations, buildings and controlled areas. The Contractor shall ensure that any subcontractors used in performance of this contract complies with these requirements and that all employees, of both the Contractor and any subcontractor utilized by the Contractor, are made aware of and comply with these requirements.

1.6.3.1 The Contractor shall be aware of and comply with the requirements associated with Installation Access Control. The Government is not liable for any costs associated with performance delays due solely to a firm’s failure to comply with Installation Access Control System (IACS) processing requirements.

1.6.3.2 The Contractor shall return installation passes to the issuing IACS office when the contract is completed or when a Contractor employee no longer requires access.

1.6.3.3 Common Access Cards (CAC) and CAC Log: The Government will provide each Contractor with a civilian identification card, i.e., CAC. The Contractor shall provide the following information: Last, First and Middle Names, government issued personal identifier (e.g. Social Security Number, Federal Identification Number, or Tax Identification Number), date of birth, primary email address (this email address will be used to contact the individual) and any other necessary information required to obtain a CAC or installation access card, to the COR with five days after the contract start date. The Contractor shall ensure safeguarding of Personally Identifiable Information (PII)

1.6.3.3.1. Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05.

1.6.3.4 The Contractor employee will be issued a CAC only if duties involve one of the following:

1.6.3.5 Both physical access to a DOW facility and access, via logon, to DOW networks on-site or remotely.

1.6.3.6 Remote access, via logon, to a DOW network using DOW-approved remote access procedures.

1.6.3.7 Physical access to multiple DOW facilities or multiple non-DOW federally controlled facilities on behalf of the DOW on a recurring basis for a period of 6 months or more.

1.6.3.8 The Contractor shall obtain a CAC through the Mission Partner ICAM portal. https://mpartnerspnrweb.dmdc.osd.mil/mpartnerspnrweb/app/

1.6.3.9 Notify the Government Mission Partner Affiliation Sponsor (MPAS) (i.e., COR) of new Contractor employee CAC requirements.

1.6.3.10 The Contractor company representative must provide all personnel data required to process the MP ICAM application with the MPAS, including security investigation requirements.

1.6.3.11 Obtain the CAC at a Defense Enrollment Eligibility Reporting System/Real Time Automated Personnel Identification System terminal when the MP ICAM application is approved.

1.6.3.12 Contractor employees will inform the Corporate Facility Security Officer/Security Manager of approval/denial of CAC application.

1.6.3.13 The Contractor shall return the employee’s CAC to the MPAS upon departure or dismissal.

1.6.3.14 Failure, inability, or delay in obtaining the CAC does not relieve the Contractor from performing under the terms of the contract

1.6.4 Background Checks: The Contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services, or Security Office. The Contractor workforce shall comply with all personal identity verification requirements as directed by DOW, HQDA and/or local policy.

1.6.5 Physical Security: The Contractor shall safeguard 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 IAW the Army Physical Security Program (AR 190-13).

1.6.6 Operations Security (OPSEC) Requirements: Contractor personnel shall adhere to facility security policies and restrictions. The Contractor shall immediately report suspicious activities to security personnel. Government issued access badges shall not be worn outside designated facilities where visible to the general public.

1.7 Post Award Conference/Periodic Progress Meetings: The Contractor shall attend any post award conference convened by the contracting activity or contract administration office in accordance with FAR Subpart 42.5. The Contracting Officer, COR, and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings the Contracting Officer will apprise the Contractor of how the Government views the Contractor's performance and the Contractor shall apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government.

1.7.1 The Contractor shall attend, participate in, and furnish input to scheduled and unscheduled meetings, conferences, and briefings that relate to the functions and services herein as required by the Government to provide effective communication and impart necessary information. The Contract Manager or designated representative shall attend meetings as requested by the Government. Meeting attendees shall at times include Contractor managerial, supervisory, and other personnel knowledgeable of the subject matter. Meetings may start or end outside of regular duty hours.

1.8 Contracting Officer’s Representative (COR): Refer to Part 2 of this PWS for the definition of a COR. As determined by the Contracting Officer, a COR will be appointed and identified by letter of designation, a copy of which will be provided to the Contractor by the Contracting Officer. The designation letter states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates, or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is not authorized to obligate the Government. If the work is not written in the contract, the COR is not authorized to request new work. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract, perform inspections necessary in connection with contract performance, maintain written and oral communications with the Contractor concerning technical aspects of the contract, issue written interpretations of technical requirements, including Government drawings, designs, specifications, monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies, coordinate availability of Government property, and coordinate site entry of Contractor personnel.

1.9 Key Personnel: The following personnel are considered key personnel by the Government: System Administrator, Network Administrator, and Simulation Engineer. The Contract Manager and Alternate Contract Manager shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The Contract Manager or Alternate Contract Manager shall be available between

1.9.1 Qualifications for all key personnel are listed below:

1.9.2 Personnel Qualifications. Contractor shall provide personnel to perform the required services that meet the following qualifications:

1.9.3 Contractor personnel shall meet the following knowledge and experience qualifications: Be able to setup, operate, administer, maintain and repair IT hardware and software (described below) that are located in the FBLP EXDIV SIMNET facilities. This includes network attached storage devices, servers, CISCO routers and switches, projectors, Crestron touch panels, audio visual racks and related software packages (Microsoft and Linux operating system software, Microsoft server software (Server 2019), Microsoft Office, Ghost, Hyper-V, and Cisco IOS).

1.9.4 Contractors shall meet the following knowledge and experience qualifications of IAT - II: Shall have seven years prior experience in network administration and computer system hardware repair and maintenance per Information Assurance Training and Certification Best Business Practice dated March 2012, appendix E https://cs.signal.army.mil/default.asp?title=reflib. Contract personnel performing the System and Networking Administration duties must have the following baseline certifications: CompTIA Security+, Sever, Linux, and Networking.

1.10 Identification of Contractor Employees: All Contractor personnel attending meetings, answering Government telephones, and working in other situations where their Contractor status is not obvious to third parties must identify themselves, to include proper marking of signature blocks in correspondence, to avoid creating an impression in the minds of members of the public that they are Government officials. The Contractor shall ensure that all documents or reports, produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed.

1.10.1 Contractor workspace: Shall contain a sign signifying the space is occupied by Contractor employee(s) to ensure that Government employees and the public know that they are not Government employees. Workspace sign location shall be coordinated with the COR. Contractor employees shall identify themselves by name and company affiliation when answering the telephone, presenting briefings, conducting or attending meetings, and seminars. All Contractor correspondence (written, facsimile, and email display) shall include their company name.

1.10.2 Contractor Identification Badges: Contractor personnel shall be easily identifiable through the display of badges IAW Contractor Identification (AE Reg. 27-715). (For services at Child, Youth, and School Services where children are present, recommend personnel wear identification when children are present.)

1.11 Contractor Travel: The Contractor may be authorized travel expenses at rates no higher than the substantive provisions of the Joint Travel Regulation (JTR), IAW FAR Part 31.205-46, and the limitation of funds specified in this contract. All travel requires Government approval and authorization five days prior to scheduled travel.

1.12 Other Direct Costs (ODCs): The need for computer peripherals and services or other materials at additional cost to the Government will be determined if necessary for the performance of specified PWS tasks or deliverables by the COR and approved by the KO.

1.13 Data Rights: The Government has unlimited rights to all documents and materials produced under this contract. All documents and materials, to include the source codes of software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership and copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the Contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.14 Non-Disclosure Requirements: Performance under this contract may require the Contractor to access data and information proprietary to a Government agency, another Government Contractor, or of such nature that its dissemination or use other than as specified in this work statement would be adverse to the interests of the Government or others. The Contractor and Contractor personnel, shall not divulge or release data or information developed, or obtained under performance of this PWS, except to authorized Government personnel or upon written approval of the Contracting Officer. The Contractor shall not use, disclose, or reproduce proprietary data, which bears a restrictive legend, other than as specified in this PWS. All documentation showing individual names or other personal information shall be controlled and protected under the provisions of the Privacy Act of 1974, Public Law 93-579, 5 United States Code (U.S.C.) Section 552a.

1.14.1 Non-Disclosure Agreements: Contractor employees assigned to this project will be required, prior to working, to sign a non-disclosure agreement for the Government agreeing not to share any information or data with other contractor personnel not assigned to the project or, if assigned to the project, which has not signed a non-disclosure agreement.

1.14.1.1The signed nondisclosure statements will be furnished to the contracting officer prior to contract performance. The company will include, with its submission of the RFQ, its plan to “firewall” these employees and enforce this provision (i.e., internal controls, training, etc.).

1.14.1.2 Failure to adhere to these non-disclosure safeguards may result in termination of this task. Final authorship and copyright (if required) of any deliverable will be with the Government. The Contractor cannot gain any unfair advantage.

1.15 Protection of Government and Contract Information: Per Public Use Notice of Limitations stated by Defense imagery Management operations Center and contained at https://www.dma.mil/Services/Visual-Information/References/Limitations/, the Contractor shall not cite any information (e.g., contract information, pictures, locations, etc.) obtained through this contract on any hard copy or digital marketing tools to include its company website.

1.16 Organizational Conflict of Interest (OCI): Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent OCI as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s OCI Mitigation Plan will be determined to be acceptable solely at the discretion of the Contracting Officer. In the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.17 Phase In /Phase Out Period: To minimize decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the 30 days phase in/ phase out periods. During the phase in period, the Contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date.

1.18 Required Training: The following provides information on training requirements. Contractors shall comply with and participate in these pertinent training programs (when performance or services will occur on an Army installation).

1.18.1 Anti-Terrorism (AT) Level I Training: All Contractor employees, including subcontractor employees, who are employed under the contract, shall complete AT Level I Training within 30 workdays after contract start date, or 30 workdays after employment of new personnel. Contractor personnel travelling overseas shall complete area of responsibility (AOR) specific AT awareness training for U.S. based Contractor employees and associated subcontractor employees. 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 five workdays after completion of this training by all employees and subcontractor personnel. AT Level I awareness training is available at https://jkodirect.jten.mil. Contractor personnel shall complete refresher training within 30 workdays of an exercised option year, except AOR specific AT Level I Training which shall be completed as required by local AT policies.

1.18.1.1 If training cannot be conducted on the website, the Contractor shall coordinate with the COR who will contact the local AT Officer at their assigned location for classroom training.

1.18.1.1.2 Contractor personnel completing training in the classroom will receive a certificate or the training attendance roster signed by the AT Officer. Verification of the training shall be provided to the COR within five workdays after completion of the training.

1.18.2 OPSEC Training: All Contractor employees, including subcontractors, shall complete Level I OPSEC training within 30 workdays of employment under this contract. Verification of the training shall be provided to the COR within five workdays after completion of the training. OPSEC Level I training is available at http://www.cdse.edu/catalog/elearning/GS130.html.

1.18.2.1 If training cannot be conducted on the website, the Contractor shall coordinate with the COR, who will contact the local OPSEC Officer at their assigned location for classroom training.

1.18.3 iWATCH Training: The Contractor and all associated subcontractors shall brief all employees on the local iWATCH 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 workdays after the contract is awarded and within five after new employees commence contract performance, with the results reported to the COR within five workdays after the contract is awarded and within five workdays after new employees commence contract performance. Verification of the training shall be provided to the COR within five workdays after completion of the training.

1.18.4 Information Assurance (IA) Training: All Contractor employees, including subcontractors, requiring access to Government information systems shall complete the DoW IA Cyber Awareness Training within 30 workdays after contract start date or effective date of incorporation of this requirement into the contract, whichever applies, or 30 workdays after employment of new personnel. Verification of the training shall be provided to the COR within five workdays after completion of the training.

1.18.4.1 All Contractor employees, including subcontractors, working information technology (IT)/IA functions shall comply with DOW and Army training requirements per Information Assurance Training Certification and Workforce Management DoD Directive (DoDD) 8570.01, Information Assurance Workforce Improvement Program DoD 8570.01-M, and Information Assurance AR 25-2 within thirty (30) calendar days of employment.

1.18.5 Physical Security: 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 IAW the Army Physical Security Program (AR 190-13).

PART 2

DEFINITIONS, ACRONYMS, AND REVELANT PUBLICATIONS

2. Definitions, Acronyms, and Publications:

2.1. Definitions: Although not inclusive of every term used within this PWS, the following provides a list of definitions used throughout this PWS and commonly used in the acquisition field.

Contracting Officer – means a person with the authority to enter into, administer, and/or terminate contracts and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the Government.

Contracting Officer's Representative (COR) – As defined in DFARS 202.101, means an individual designated and authorized in writing by the Contracting Officer to perform specific technical or administrative functions. DoD Instruction (DoDI) 5000.72, Part II Definitions states the following when defining a COR: “Defined in subpart 202.101 of Reference (f). Any individual delegated responsibilities pursuant to subpart 1.602-2 of Reference (e), regardless of local terminology, must be certified in accordance with this instruction. For example, local terminology can be COR, Contracting Officer’s technical representative, technical point of contact, technical representative, alternate COR, administrative COR, assistant COR, line item manager, task order manager, quality assurance personnel, quality assurance evaluator, or COR management.” In addition, Army Regulation 70-13, Chapter 2, paragraph 2-2g, states, in part, the following when providing other surveillance support personnel to assist the COR when needed, “…These other surveillance support personnel may serve as on-site representatives of the COR in performance of actual contract surveillance if they meet all COR requirements and have been appointed by the Contracting Officer as alternate CORs.”

Contractor – means a supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

Contractor-acquired Property - means property acquired, fabricated, or otherwise provided by the Contractor for performing a contract and to which the Government has title.

Day – means, unless otherwise specified, a calendar day.

Defective Service – means a service output that does not meet the standard of performance associated with the Performance Work Statement.

Deliverable – means anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

Government-furnished Property – As reflected in FAR 52.245-1, Government-furnished Property “means property in the possession of, or directly acquired by, the Government and subsequently furnished to the Contractor for performance of a contract. Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes contractor-acquired property if the contractor-acquired property is a deliverable under a cost contract when accepted by the Government for continued use under the contract

Government Property - means all property owned or leased by the Government. Government property includes both Government-furnished and Contractor-acquired property. Government property includes material, equipment, special tooling, special test equipment, and real property. Government property does not include intellectual property and software.

Property Administrator - means an authorized representative of the Contracting Officer appointed in accordance with agency procedures, responsible for administering the contract requirements and obligations relating to Government property in the possession of a Contractor.

High Level Objective (HLO) – means a key overarching result-based objective for a project necessary to achieve the project’s vision. HLOs are similar to Level 2 in a Work Breakdown Structure. Each HLO may contain several statements to flesh out the areas necessary to meet the objective.

Physical Security – means that part of security concerned with physical measures designed to safeguard personnel; to prevent unauthorized access to equipment, installations, material, and documents; and to safeguard against espionage, sabotage, damage, and theft.

Quality Assurance – (or Government contract quality assurance) means the various functions, including, inspection, performed by the Government to determine whether a Contractor has fulfilled the contract obligations pertaining to quality and quantity.

Quality Control – means all necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

Statement – means the specific results-based activities required to satisfy HLOs. A statement contains a result, the context of the statement, and the required action(s). Statements focus on “what” is to be accomplished; however they are not prescriptive in describing “how” the outcome is to be achieved. Each HLO may have several statements to flesh out the areas necessary to meet the objective. Statements are similar to Level 3 in a Work Breakdown Structure.

Subcontractor – means one that enters into a contract with a prime Contractor. The Government does not have privity of contract with the subcontractor.

Work Day - The number of hours per day the Contractor provides services in accordance with the contract.

Work Week - Monday through Friday, unless otherwise specified.

2.2 Acronyms: Although not inclusive of every term used within this PWS, or that may be included in an acquisition, the following provides a list of acronyms commonly used in the acquisition field.

2.3. Applicable Publications (Current Editions) The following publications, manuals, regulations, etc. are mentioned in the PWS and are listed below. These will be made available for inspection.

2.3.12 DoDAF Architecture Framework Verison 2.02, 10 August 2010

2.3.13 OneSAF Users Manual

2.3.14 DoD STIGs

2.3.16 DoD Manuals Cyberspace Workforce Qualifications and Management Program (DoD 8140.3), 15 February 2023

PART 3

GOVERNMENT PROPERTY (GP) AND SERVICES

3. Government Property and Services

3.1 Services: The Government will provide adequate working conditions to complete the duties required in this requirement. User workstations and network access will be supplied as necessary to the on-site contractors.

3.2 Facilities: The Government will provide the necessary workspace for the Contractor staff to perform the contract, to include desk space, telephones, computers, and other items necessary to maintain an office environment. These Government-furnished facilities shall be determined at the task order level. Government-furnished facilities may include: office/work space, office supplies, telephone service, computer access, and storage space. The Government will provide network services (Non-secure Internet Protocol Router Network (NIPRNET), Secret Internet Protocol Router Network (SIPRNET), Defense Switched Network (DSN), Joint Worldwide Intelligence Communications System (JWICS) and other data collection/production/reproduction equipment/software for tasks to be accomplished at Fort Eustis.

3.3. Utilities: Utilities will be provided for the Contractor’s use in performance of this contract. Government-furnished utilities will be determined at the task order level. If utilities are furnished, the Contractor shall instruct employees in utilities conservation practices. The Contractor shall be responsible for operating under conditions that preclude the waste of utilities, which include turning off the water faucets or valves after using the required amount to accomplish cleaning vehicles and equipment.

3.4 Equipment: The Government will provide the contract with adequate working conditions to complete the duties required in this contract. User workstations and network access will be supplied as necessary to the on-site contractors. In order to gain required administrative capabilities on DoD networks, contractors are required to be 8140 compliant.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4. Contractor Furnished Property and Services

4.1. General: The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.

PART 5

SPECIFIC TASKS

5. Specific Deliverables: Contractor shall provide services for IT and for simulation operations (planning, preparing, and executing). Execute experimentation in support of FCC FBLP FCD and FCC G3/5/7 which supports concept and capability developments; Concept Capability Plans; concept-based capabilities from the Capability Needs Analysis; and doctrine-based capabilities from the Capabilities Gap Analysis; Learning Demands and Venue Analysis. Typical tasks for the experiments conducted for the FBLP ExDIV are conducting Simulation events, maintain event scenarios, support simulation data collection, and update the simulation software. Perform the tasks that are laid out in the following paragraphs. Historic simulation workload data is depicted in the table below. General specifics of the events will be provided at the time of the award. Provided are the type of events with total weeks for each event. Historically the integrating events that are directed by FCC G3/5/7 there will be approximately a six-month notice before the event start date. For the local events there will be approximately a 30-day notice for the event start date. The time between events is when additional updates to the simulation software and maintenance to the scenario/task structure will occur.

event

Maintain Scenario/Task Structure

Update Simulation Software

5.1. Simulation Environment Preparation. Shall perform the following tasks to prepare for each simulation event once they have received the simulation plan. Generally, for the large-distributed events the plan will be known a year in advance. For the smaller scale events the plan will be known 90-120 days in advance of the simulation event.

5.1.1 Responsible for the setup, configuration, and testing the simulation federation environment, either Bifrost, HLA or DIS. This will include the installation, configuration, and testing of simulation software on workstations. Once set up, shall update and maintain the simulation environment so it is ready to support simulation events. This must be completed to meet the deadlines prescribed in the simulation plan.

5.1.2 Conduct verification and validation operations for all models and simulations required for each event. Verify data collection and analysis tools output. Prepare the simulation accreditation documentation for the event. This shall be completed within the timelines prescribed in the simulation plan.

5.1.3 Develop the experimentation Simulation Training Plan. Have it reviewed and approved 30 days prior to the start of the event.

5.1.4 Responsible for development of the required WMSL Data Request, and coordinate with FCC G3/5/7 for required data products, by the deadline prescribed in the simulation plan.

5.1.5 Responsible for development of the experiment’s appropriate entities and force structure. For the large-scale distributed event, enter that data into simulation to meet the deadlines prescribed in the simulation plan.

5.1.6 Within 30 days from the date the contractor is given the experiment design documents, develop and test the simulation scenario(s) to ensure it meets that experiment design for the simulation event. The scenario needs to be 100% accurate in regard to entities correctly modeled, and behaviors properly configured.

5.1.7 Develop or modify simulation behaviors and/or entities as needed, in order to properly execute the simulation that supports experimentation and monthly technical integration events.

5.1.8 Participate in Technical, Modeling and Simulation working groups. Also participate in Planning Conferences/Meetings (Initial, Mid, and Final).

5.2 Simulation Environment Execution. Execute simulation events in accordance with planning and the M&SSP. Typically experiments run sequentially. Shall perform the following tasks for simulation event execution:

5.2.1 Perform constructive simulations, as needed (see above Workload Table).

5.2.2 Federate all the simulations, using either Bifrost, HLA or DIS simulation architecture.

5.2.3 Perform Battle-master duties; to include daily start up, mission save and shut down procedures as required by the experiment’s battle rhythm. Maintain a daily log of simulation issues that occurred during the event. Update graphics, experiment entities, force structure, and scenarios as required. Ensure the applicable scenarios, graphics, entities, and force structure are correct. Maintain constant communication with the Experiment Lead during experimentation. Assist the simulation interactors in performing their intended duties and resolving simulation issues.

5.2.4 Execute Monthly Technical Integration Events, Spiral Testing Events, Pilot Runs and Record Runs.

5.2.5 Train simulation interactors/ operators in the operation of respective simulations, basic military doctrine, and relevant experimentation technologies as required.

5.3 IT Support Tasks. Administration, Maintenance and Repair. The Contractor shall perform the following tasks.

5.3.1 Contractor personnel shall administer, maintain, and repair the FBLP ExDIV systems and network IAW AR 25-2, Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGS), the National Institute of Standards and Technology (NIST) Risk Management Framework (RMF) standards or current DoD certification and accreditation; Army approved operational security image and policy. Install, upgrade (version change or patches) and configure Microsoft and Linux commercial off-the-shelf workstation and server operating systems, commercial application software (Microsoft Office Professional, Microsoft Structured Query Language database, Microsoft SharePoint) and Army developed computer software and other associated FBLP ExDIV SIMNET software see Appendix A for software list, to operate with the various computing systems described herein and their peripheral devices and software components.

5.3.2 Administer the FBLP ExDIV SIMNET Closed Network devices and cabling. This includes installation, configuration and updating of Government provided network devices such as switches and routers and the installation and upgrades of network cabling. Network devices shall be configured IAW AR 25-2 and applicable STIGS provided by the COR.

5.3.3 Daily, ensure all computer hardware and software components are compatible, operational and ready for training to interface with users, currently installed software and hardware products to preclude system conflicts and malfunctions.

5.3.4 Repairs. The Contractor shall troubleshoot and repair the FBLP ExDIV SIMNET, peripheral equipment and network; analyze and troubleshoot computer software products, computer systems, peripheral devices and network connectivity; determine if problems are related to hardware, software, connectivity or combination of both; coordinate with co-workers, system developers, vendors and functional users to effect successful problem resolution ( the Contractor shall not contact developers or vendors in situations when the Government may be charged for the consultation); make recommendations to the COR suggesting system modifications to preclude problem recurrence (actions taken on all Contractor recommendations are within the sole discretion of the Government and the Government’s failure to act on any such recommendation shall not support a claim for breach or equitable adjustment). All systems shall remain operational during normal Government operation hours. Issues reported for systems within the FBLP EXDIV SIMNET shall be initially responded to within 15 minutes of reporting during planned experiment or study events and within 24 hours during non-event time periods. Problems shall be identified and corrected, or equipment shall be replaced, if required, with available Government provided spares within two hours of reporting during any experiment or study events and within 48 hours, dependent on available spares, during non-event time periods

5.3.5 To resolve unique problems or to gather additional installation or usage information. The Contractor shall not contact developers or vendors without first receiving written permission from the COR in situations when the Government may be charged for the consultation.

5.3.6 Exchange or replace components with Government provided replacement parts. Based on historical evidence, the Government estimates that 25% of hardware components shall require replacement over the PoP. This estimate is provided in order for Contractor to prepare a proposal and is not intended to be considered a cap on the amount of work to be performed. In no event shall the Contractor purchase replacement parts or obligate the Government for purchase of the same.

5.3.7 Government Parts Ordering. All non-functioning equipment shall be repaired or required repair part reported to the Government within one business day. Ordering of equipment shall be executed and funded by Government.

5.3.8 The Contractor shall maintain and update the system documentation required for the system accreditation. These documents include but not limited to network diagrams, hardware/software lists, system configurations and engineering change proposals (ECPs).

5.3.9 Contractor shall conduct vulnerability scans and run intrusion detection software, apply security patches to safeguard the system from intrusion and provide virus detection and removal services IAW AR 25-2 on a weekly basis utilizing the current approved Government provided security scanning software. Electronic copies of vulnerability scans provided to the FBLP EXDIV SIMNET IASO weekly.

5.3.10 Identify and notify the FBLP EXDIV SIMNET Information Assurance Support Officer (IASO) of software that appears to violate applicable licensing agreements, and copyright laws within one week, IAW RMF or current DoD certification and accreditation.

5.3.11 The Contractor shall provide the capability to conduct technical research, make recommendations and, with Government approval, implement improvement, enhancement, or replacement of constructive, virtual, and instrumented live simulations and simulators used by the FBLP EXDIV.

5.3.12 Kick Off Meeting. Contractor shall attend at the Maneuver Support Battle Lab, via teleconference or face to face a kick-off meeting with Government to discuss the scope of work and receive GFI. The meeting date shall occur not later than five days after Contract start, and shall be scheduled by the COR.

PART 6

APPLICABLE PUBLICATIONS

The DoDAF…