Exhibit A - BRAGG MTR 10-07 PWS.docx

FOUO Version 1.7 Maneuver Battle Lab 35 Ridgway Loop Fort Benning, GA 31905

Performance Work Statement: For Support Services for the Maneuver Battle Lab, Fort Benning, Georgia

1. GENERAL: The Maneuver Battle Lab’s (MBL) primary mission is to conduct experiments in support of the United States Army Training and Doctoring Command (TRADOC) Army Capabilities Integration Center (ARCIC) Campaign Plan (ArCP). They routinely support other experimentation in support of the Maneuver Center of Excellence (MCoE) interests with other organizations across DoD such as the Defense Advance Research Program Agency (DARPA) and the Research Development and Electronics Command (RDECOM). The MBL conducts experiments in live, virtual and constructive environments to support current and future force development by providing insight into Doctrine, Organization, Training, Leader Development, Materiel, Personnel and Facility (DOTLMPF). They are formational based and experiments are primarily conducted for Brigade Combat Team organizations which include the: Infantry Brigade Combat Team (IBCT), Heavy Brigade Combat Team (HBCT), Stryker Brigade Combat Team (SBCT), Armored Calvary Regiment (ACR), Modernized Brigade Combat Team (MBCT), and the Battlefield Surveillance Brigade (BfSB). Likewise the MCoE is the proponent for all Soldiers and the MBL conducts experiments at the small unit and Soldier level to inform Soldier development.

2. REFERENCES:

2.1 Army Regulation 5-11, Management of Army Models and Simulations, 1 February 2005.

2.2 Army Regulation 25-2. Information Assurance, 24 October 2007.

2.3 Army Regulation 71-9, Warfighting Capabilities Determination, 28 December 2009.

2.4 Department of the Army Pamphlet 5-11, Verification, Validation, and Accreditation of Army Models and Simulations, 30 September 1999.

2.5 TRADOC Regulation 5-14, Acquisition Management and Oversight, 5 January 2009.

2.6 TRADOC Regulation 10-5, U.S. Army Training and Doctrine Command, 22 December 2005.

2.7 TRADOC Regulation 10-5-2, Organization and Functions, U.S Army Training and Doctrine Command Futures Center, 20 January 2006.

2.8 TRADOC Regulation 71-20, Concept Development, Experimentation and Requirements Determination, Implementation, October 2009.

2.9 Code of Best Practices, Experimentation, Department of Defense Command and Control Research Program, July 2002.

2.10 The ArCP, FY 10-11, dated 12 August 2009.

2.11 Fort Benning Regulation 350-1, United States Army Infantry Center (USAIC) Training Directive, 25 June 2001.

2.12 Maneuver Battle Lab, Standard Operating Procedures, August 2009

2.13 Battle Lab Collaborative Simulation Environment, Standard Operating Procedures, May 2006.

2.14 Applicable DoD/Army/Local regulations for conducting experiments at DoD locations and OCONUS locations (i.e., Iraq and Afghanistan)

3. SCOPE: Provide comprehensive support services in the areas of planning, preparation, execution, documentation and analysis in support of MBL experimentation. The contractor shall be responsible for ensuring that the simulations, simulation facilities and simulation models are in a current and ready state. The contractor shall support the MBL in coordinating, integrating, conducting, and executing experiments in support of the MBL mission. The contractor will be required to simultaneously execute multiple experiments in various stages of completion. The contractor will be responsible for coordinating these experiments simultaneously in accordance with the applicable milestone schedules.

3.1 Place of Performance. Work shall be performed primarily at Fort Benning, Georgia, and may also require occasional support at other Department of Defense (DoD) locations throughout the Continental United States (CONUS), and Outside Continental United States (OCONUS) including Iraq, Afghanistan and other potential future Theater of Operations.

3.2 Period of Performance. The period of performance consists of an eleven (11) month basic ordering period with four additional one (1) year optional ordering periods. There will be a thirty (30) day phase-in period prior to the basic ordering period. Normal business hours are from 8:00am to 5:00pm, Monday through Friday. The hours of 8:00am to 5:00pm are the projected normal hours operating over a standard five-day period, excluding Federal holidays, however, these operating hours and days may vary based on mission requirements. Contractor personnel work schedules may be flexed five days a week to meet the manpower requirements for weekend and extended duty periods during regular training and exercises. The Contractor shall schedule personnel to preclude the need for overtime/Extended Work Week (EWW) to the maximum extent possible, and to fully maintain the experiment/activity required beyond the standard operating hours.

3.2.1 Overtime/EWW. Contractors shall perform all contracts, so far as practicable, without using overtime, particularly as a regular employment practice, except when lower overall costs to the Government will result or when it is necessary to meet urgent program needs. The Contracting Officer (KO) will address Overtime requirements at the Task Order level. Approval for the use of overtime may be granted after determining in writing that overtime is necessary in accordance with FAR 22.103-4. A copy of this approval must be included with the Monthly Task Summary Report (MSR).

3.3 Contractor responsibilities include planning, coordinating, preparing, executing, and documenting experiments in support of Joint Concept Technology Demonstrations (JCTD), Advanced Technology Demonstrations (ATD), Army Technology Objectives (ATO), ArCP experiments and experiments in support of the MCoE and other DoD organizations as required.

3.4 The contractor must plan each experiment to meet experimental objectives and identify appropriate resources. The process is documented in the MBL Standard Operating Procedures (SOP).

3.5 Each experiment requires a comprehensive report with briefing requirements throughout the DoD.

3.6 DoD experiments to be supported by the contractor include, but are not limited to:

· Army Expeditionary Warrior Experiment (AEWE) Campaign

· Talon Strike Omni Fusion FY10

· Battlefield Extraction Assist Robot (BEAR)

· Gunshot Detection System (GDS) Capabilities and Limitations

· Sniper Detection/Defeat with Systems Experiment

· Measurement and Signature Intelligence Tactical Information Fusion (MASTIF) Advance Concept Technology Demonstrations (ACTD)

· Enhanced 50 Caliber Machine Gun M2E2

· Land Warrior Experimentation In-Theater Assessment

· Ground Soldier System (GSS) Assessments

· M240 Machinegun Studies

· XM1037 Subcaliber Device

· Ammunition Bandoleers

· Call for Fire with Unmanned Aerial System

· Consolidated Interim Single Channel Handheld Radio

· Networked Brigade Combat Team Simulation Exercise (SIMEX) Campaign

· Squad Mission Support System

· Microclimatic Cooling for Soldiers

· Wireless Network after Next (WNaN)

· 84mm Carl Gustaf Sub-Caliber Training Round

· M240/M249 Collapsible Buttstock

· M240 Bipod

· Other experiments as required in support of Operational Needs Statements (ONSs), various Program of Record (POR) Program Managers, or MCoE directed. The MBL historically conducts between 45 – 60 experiments per year.

4. OPERATIONAL SUPPORT: The task areas associated with Operational Support are as follows:

· Task Area: Plan, Prepare, Execute operations to support and conduct experimentation.

· Task Area: Simulation Environment.

· Task Area: Network Services.

· Task Area: Information Assurance and Physical Security

· Task Area: Government Furnished Property (GFP).

· Training/Certification.

4.1 Task Area: Plan, Prepare, Execute operations to support and conduct experimentation. The Contractor shall execute experimentation in support of the ArCP which supports: concept and capability developments; Concept Capability Plans (CCPs); concept-based capabilities from the Capability Needs Analysis (CNA); and doctrine-based capabilities from the Capabilities Gap Analysis (CGA); Learning Demands (LDs) and Venue Analysis. Typical experiments conducted for the MBL Experiments Environment Branch (EEB) range from a squad-sized event with a four-to-six week planning and execution cycle to a brigade combat team-sized event with a six-to-twelve month planning and execution cycle. Experimentation forces are represented by any combination of instrumented live, constructive simulation, and virtual simulators. Tactical representation of units includes organic equipment, personnel and equipment with higher echelon and joint enablers. Forces will replicate current organizational structure and capability or proposed capability of twenty years in the future. Historically, there has been an average of four to six major simulation experimentation efforts annually with most at the brigade down to platoon and individual soldier level. These requirements take approximately 220 days including development, execution, and completion of the final report. There has also been an average of 40-50 live prototype experiments per calendar year in addition to the simulation events. This historical data is for informational purposes only and may not fully capture the actual workload to be incurred in performance of this requirement; therefore, it shall not be a limiting factor on the Contractor's obligation to perform all services within scope of the contract to the required level of performance.

4.1.1 Task: Simulation Environment Planning. The Contractor shall execute planning and preparation activities for simulation events, develop simulation environments, and develop planning and preparation products for experiments, demonstrations, studies, and/or tests that support experimentation events in support of Government personnel. Planning and preparation for follow-on experiments may occur simultaneously with an ongoing experiment.

4.1.1.1 For each experiment, demonstration, study, or test, the Contractor shall develop required experimentation products that include, but are not limited to the following:

· The Model and Simulation Support Plan (including Simulation Architecture and operational views (OVs), system views (SVs), experiment Interface Control Documents, and a task organization and entity reference).

· Technical and Modeling and Simulation Milestones and schedule.

· The experiment Integration Plan.

· The experiment Validation Plan.

· The experimentation Training Plan.

· The Communications Architecture.

· The experiment Weapon, Sensor, Munition List (WSML) Data Request, and coordinate with Army Materiel Systems Analysis Activity (AMSAA) for required data products.

4.1.1.2 For each experiment, demonstration, study, or test, the Contractor shall develop required simulation environment products and provide input to the Experiment Project Lead for the following:

· The Experiment Directive. The Analysis Plan including the Data Collection Management Plan (DCMP).

· The manning requirements to include personnel budget estimates to support the requirement.

· The Event Design Document.

· The operational scenario for the experiment, including tactical orders and planning products that may be provided to military role players for implementation IAW current or future doctrine, tactics and procedures.

· Surveys to be administered during the conduct of the experiment.

· The experiment schedule, milestones, and event Battle Rhythm.

4.1.1.3 For each experiment, demonstration, study, or test, the Contractor shall prepare, coordinate, facilitate, and execute technical and Modeling and Simulation, and Planning Conferences (Initial, Mid, and Final), working groups, Video Teleconferences, or Telephone Conferences as required. All conference preparations and expenditures shall be approved by the Contracting Officer prior to execution.

4.1.1.4 For each experiment, demonstration, study, or test, the Contractor shall conduct technical and Modeling and Simulation In-Process Reviews (IPRs) to the community of practice, Director MBL, Concept Development Integration Directorate (CDID), and Commanding General (CG) as required.

4.1.2 Task: Simulation Environment Preparation. The Contractor shall develop and publish preparation products for simulation events and execute preparation activities for simulation events. Preparation for follow-on experiments may occur simultaneously with an ongoing experiment.

4.1.2.1 The Contractor shall conduct verification and validation operations for all models and simulations required for each event, verify data collection and analysis tools output, and prepare documentation for accreditation of the event.

4.1.2.2. The Contractor shall train and certify Simulation Inter-actors/ operators (SI) in operation of respective simulations and battle command systems, basic military doctrine, and relevant experimentation technologies as required. A training plan is developed for each experiment and tailored to the specific requirements of the experiment; SIs shall be trained and tested on the pertinent information in accordance with the requirements of the applicable training plan. Personnel who successfully complete the training plan requirements will receive a certificate of completion. The contractor shall maintain a copy of the personnel testing results and certification. Each time an individual is utilized in support of an experiment, they will be retested to ensure their skills have not atrophied before they are given a duty position as part of the experiment.

4.1.2.3 The Contractor shall train and certify Military Role Players in operation of respective simulations and battle command systems, basic military doctrine, and relevant experimentation technologies as required. A training plan is developed for each experiment and tailored to the specific requirements of the experiment; Military Role Players shall be trained and tested on the pertinent information in accordance with the requirements of the applicable training plan. Personnel who successful complete the training plan requirements will receive a certificate of completion. The contractor shall maintain a copy of the personnel testing results and certification. Each time an individual is utilized in support of an experiment, they will be retested to ensure their skills have not atrophied before they are given a duty position as part of the experiment.

4.1.3 Task: Simulation Environment Execution. The Contractor shall execute simulation events in accordance with planning and preparation guidance. Typically, experiments run sequentially, but may occur simultaneously.

4.1.3.1 For each experiment, demonstration, study, or test, the Contractor shall conduct the following:

· Experimentation Training Plan complete and executed.

· Execute the Experiment Battle Rhythm.

· Execute Pilot Runs and Record Runs.

· Enable and assist the Project Lead in conducting experiment surveys.

· Enable and assist the experiment Project Lead in conducting After Action Reviews (AAR) /Hot Washes.

· Provide daily event summary reports.

· Execute Experimentation In-processing activities as required for visiting personnel.

4.1.3.2 Simulation Inter-actors / Operators (SI).

4.1.3.2.1 Qualified and certified personnel for simulation control and technical control are required to conduct man-machine interface for the various simulations in support of experimentation as defined in paragraph 4.1.

4.1.3.2.2 A full time group of qualified and certified personnel are required as simulation operators to conduct man-machine interface for the various simulations to conduct platoon-sized simulation events, testing, and preparation of experimentation as defined in paragraph 4.1.

4.1.3.3 Simulation Data Collection and support to Analysis and Assessment.

4.1.3.3.1 The Contractor shall configure, maintain, develop, and prepare data collection products derived from simulation events in support of Government personnel and in support of the MBL Analysis Division. Data Collection personnel shall be able to script, develop, compile, and produce standard and event-specific quantifiable data products from the simulation environment and tools.

4.1.3.3.2 The Contractor shall gather and compile data; modify and create data collection means; copy and place the data on media; and refine and compile collected data into appropriate formats for analysis from the simulations, simulation federation, and network.

4.2 Task Area: Simulation Environment. Implement Live, Virtual, Constructive, or mixed simulation architectures for experimentation to address gaps and deficiencies across all DOTMLPF areas.

4.2.1 The Contractor shall demonstrate the appropriate engineering and technical skills to perform simulation systems integration, development, and engineering services to enable MBL experimentation.

4.2.2 The Contractor shall provide support to integrate and establish the following:

· Federation of simulations and simulators using the Distributed Interactive Simulation (DIS) protocol.

· Federation of simulations and simulators using High Level Architecture (HLA) federations; implement, modify, or create Simulation Object Models; implement, modify, or create Federation Object Models; and install, configure, and operate HLA Run Time Integrator (RTI) systems.

· Battle command architecture stimulated by a federation of simulations and simulators.

4.2.3 The Contractor shall trouble-shoot simulation software and hardware for the virtual and constructive simulations and simulators used by the MBL.

4.2.4 The Contractor shall assess the impact and associated requirements related to the addition and integration of a simulation or simulator not previously used by the MBL and its associated modeling and simulation tools.

4.2.5 The Contractor shall create or modify capabilities and parameters of simulators and simulations, including performance, environment, visual, sensor, and other characteristics as required to demonstrate and assess experiment related capability for the virtual and constructive simulations used by the MBL.

4.2.6 The Contractor shall develop new simulation models, compositions, entities, and force structure data-bases for the virtual and constructive simulations used by the MBL.

4.2.7 The Contractor shall 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 MBL.

4.2.8 The Contractor shall be responsible for configuration control, configuration management, database management, and tasks required to maintain software source code version control and properly document all software and database changes made to the virtual and constructive simulations used by the MBL. The Contractor shall perform the following:

· Maintain and provide an integrated software development environment for the Government Furnished Property (GFP) simulations and simulators.

· Produce documentation and inventory of changes to existing software source code or functionality as part of the software development. The software inventory shall include an inventory of changes made and shall provide an annual detailed Version Description Document.

· Maintain a system to capture metrics on software development and to report troubles and problems pertaining thereto.

4.2.9 The Contractor shall provide and maintain simulation data bases consisting of current and directed future task organizations including the following maneuver brigade formations: IBCT, HBCT, SBCT, ACR, BfSB, and in coordination with the Future Force Integration Directorate (FFID), the Brigade Combat Team Modernization Program.

4.2.10 The Contractor shall support development, modification, and management of simulation terrain databases and virtual models for the virtual and constructive simulations and simulators used by the MBL utilizing hardware and software terrain development tools provided by the Government.

· The Contractor shall be knowledgeable in Geospatial Information tools that can enable the creation, conversion, and modification of new or existing simulation terrain databases including the accompanying visual files for three-dimensional representations.

· The Contractor shall develop, store, create, modify, do configuration management, and maintain the simulation terrain databases and information used to support the MBL experiments.

· The Contractor shall manage and coordinate electronic mapping products required for use on battle command systems used during experimentation, and produce digital mapping products to support battle command systems or modify existing mapping products to match simulation terrain developed for experimentation.

4.3 Task Area: Network Services. The Contractor shall provide network services support of various Local Area Networks (LANs) and Wide Area Networks (WANs).

4.3.1 The Contractor shall provide technical support and execute LAN/WAN installation, configuration, operation, troubleshooting, monitoring, and maintenance within MBL facilities.

4.3.2 The Contractor shall provide technical support to maintain network connectivity required to conduct live, virtual and constructive experimentation between MBL simulation facilities, the McKenna Urban Operations Facility, and any other range complexes that are used in experimentation.

4.3.3 The Contractor shall provide technical support for connectivity using the Defense Research and Engineering Network (DREN), Battle Lab Collaborative Simulation Environment (BLCSE) Network, and any required project related installed LAN/WAN networks.

4.3.4 The Contractor shall relocate LAN/WAN equipment in order to provide any temporary network services and equipment to support the MBL efforts locally or off site as required by specific events or demonstrations.

4.3.5 The Contractor shall provide network design engineering services, development support, node operations support, acquisition recommendations, and system qualification requirements in support of simulation experimentation, demonstrations, and tests. At a minimum, this task shall include the following:

· Connections between existing MBL facilities, the McKenna Urban Experimentation Facility, and other range complexes that are used in any experimentation.

· Connection of additional facilities and locations to the LAN/WAN as required supporting the MBL mission.

· Utilization of the following in support of systems and hardware currently owned by the government: Cisco Certified Entry Networking Technician (CCENT), Cisco Certified Network Associate (CCNA) Routing & Switching , CompTIA Network+, Red Hat Certified Engineer (RHCE), Microsoft Certified Systems Engineer (MCSE), and Microsoft Certified Systems Administrator (MCSA) certified and trained technical support.

4.4 Task Area: Information Assurance and Physical Security

4.4.1 The Contractor shall ensure that the experimentation network complies with the requirements of AR 25-2 (Information Assurance) and remains accredited in accordance with DoD Information Assurance Certification and Accreditation Process (DIACAP) so that it supports MBL events and there is no interruption of experimentation.

4.4.2 Provide a subject matter expert trained IAW AR 25-2 to assist the MBL Information Assurance Security Officer (IASO). Tasks shall include the following: coordinate and ensure that all MBL computers, routers, and other digital equipment, as well as procedures and documentation meet the necessary requirements and specifications for accreditation of the experimentation network with both the classified and unclassified domains; coordinate efforts with the MBL IASO to ensure AR 25-2 and DIACAP compliance and the security of the experimentation network; and work in conjunction with the MBL IASO in the performance of duties pertaining to Information Assurance and Security as specified in AR 25-2.

4.4.3 The Contractor shall ensure that its performance is in compliance with the requirements of facility physical security so that there is no interruption of experimentation.

4.5 Task Area: Government Furnished Property (GFP). The Contractor shall install, operate, configure, maintain, inventory, and account for GFP.

4.5.1 The Contractor shall provide an efficient process to manage equipment lifecycle utilization, and recommend new equipment and software version updates for lifecycle replacement.

4.5.2 Equipment may include, but are not limited to:

4.5.3 Operating Systems licensed by the Government may include, but are not limited to:

Linux (Red Hat and others) Windows (multiple versions) Windows Server (multiple versions) MS DOS (multiple versions)

4.5.4 Software licensed by the Government may include, but are not limited to:

Soldier Virtual Simulations (SVS) Squad Synthetic Environment (SSE) Virtual Battle Space 2 (VBS2) LVC Game Web3D Simulations SIM Storm ASTi Radio DAC C4I Terrex Solar Winds Cisco Call Manager Voice Over Internet Protocol Phones Statistical Programming for Social Science (SPSS) Virtual Soldier Skills Assessment (VISSA)

4.5.5 Government-owned simulations may include, but are not limited to:

OneSAF (Objective One-SAF) Joint Semi-Automated Forces (JSAF) Infantry Warrior Simulation (IWARS) Joint Virtual Tactical Radio (JVTR) Universal Controller 3d Vis Snap Server Comprehensive Mine and Sensor Simulation (CMS2) Counter Mine Server (CMS) Advanced Concept Research Tool-Ground Variant (ACRT-GV) Advanced Concept Research Tool-Command and Control Vehicle Variant (ACRT-C2V) Advanced Concept Research Tool-Desktop Variant (ACRT-DT) Role Player Workstation (RPWS) Remote Reconfigurable Intelligent Instrumentation to Control, Collect, Stimulate, and Simulate [(RICS)2] Stargen Starship Simulation Test Operations Rehearsal Model (STORM)

4.5.6 Government-owned software may include, but are not limited to:

Data Collection and Analysis Tool (DCATS) Digital Collection, Analysis and Review System (DCARS) Joint Digital Collection, Analysis and Review System (J/DCARS) Force XXI Battle Command, Brigade-and-Below (FBCB2) Command Post of the Future (CPOF) CPOF Repository CPOF Data Bridge Army Battle Command System (ABCS) Publish and Subscribe Server (PASS) Maneuver Control System (MCS) -Light Battle Command Server (BCS)

4.5.7 The Contractor shall conduct 100% GFP inventories twice per calendar year.

4.5.8 The Contractor shall pick-up, receive, and inventory equipment furnished by the Government.

4.5.9 The Contractor shall pack, label, and coordinate for shipment of equipment as required by the government.

4.5.10 The Contractor shall turn-in unserviceable, excess, or unneeded equipment to the Defense Reutilization Management Office (DRMO) as directed by the Government.

4.5.11 The Contractor shall ensure the MBL facilities remain clean in between scheduled cleanings provided by the installation janitorial staff.

· The Contractor shall keep contracted personnel offices and workspaces clean.

· The Contractor shall empty contracted personnel office and workspace trash cans.

· The Contractor shall escort installation janitorial or maintenance staff as required to clean and maintain common use areas.

4.5.12 The Government will provide office space, office supplies, telephone service, workstations, computers, system access, and storage space at Fort Benning. All Government-furnished property will be provided in accordance with FAR 52.245-1. The Government property shall be used only in performance of this contract. The Contractor shall be responsible for accountability of GFP provided for individual offices and workspaces.

4.5.13 The Government will be responsible for the following during the on-site activities:

4.5.13.1 Verifying accessibility of key Contractor personnel that will be participating in projects. Providing access to the network system assets, including wiring closets, raceways, computer rooms, and network devices (modems, routers, bridges, hubs, and storage rooms).

4.5.13.2 The Government will provide manuals, tests, briefs, and other materials associated with the hardware/software. The Government will provide initial familiarization/orientation of the MBL. Contractors will be provided access to Army Knowledge Online, Army email systems, and such other information systems as the various Government site managers may find appropriate and necessary for the conduct of specified contract activities. The MBL Standard Operating Procedures (SOP) will be available to the Contractor at the place of performance. The Contractor shall comply with the procedures described in the MBL SOP.

4.6 Training/Certification. Locations and duration of training cannot be established at this time. Specific training as directed by the Government may be required.

4.6.1 The Contractor will be responsible for the training of contractor personnel. Such training shall not be chargeable as part of the contract direct labor costs.

4.6.2 The Government will reimburse the Contractor for the initial training of contractor personnel as required when the MBL implements a new simulation, simulator, battle command system, or other software or hardware required by the Government.

4.6.3 The Government will reimburse the Contractor for the training of SIs as required to support specific experimentation efforts.

4.6.4 The Contractor is responsible for sustainment training/certification for contract personnel.

4.6.5 The KO must approve required training that the Contractor justifies to be chargeable to the contract in advance.

5. EXPERIMENTATION SUPPORT: The task areas associated with Experimentation Support are as follows:

· Task Area: Plan, coordinate, synchronize, identify resources for, execute, and document experiments in support of prototype experimentation.

· Task Area: Perform operational analyses utilizing Government-approved models, threat characteristics, and deployment and employment protocols in accordance with appropriate doctrine.

· Task Area: Manage McKenna Urban Site for training and experimentation.

· Task Area: Support Experimentation in current and future operations, and provide information and logistics management.

5.1 Task Area: Plan, coordinate, synchronize, identify resources for, execute, and document experiments in support of prototype experimentation. Experiments are executed in maneuver areas, training areas, ranges, the simulation center at Fort Benning, and other DoD installations or OCONUS locations.

5.1.1 Experiments may include a wide array of DoD experimentation activities including JCTDs and Army Technology Objectives (ATOs).

5.1.2 Experiments shall be conducted in accordance with terms and conditions of the associated Task Order in conjunction with the ID/IQ contract and incorporated documents.

5.1.3 The Contractor shall participate in various official forums such as Integrated Product Teams (IPTs), Integrated Concept Teams (ICTs) working groups, technology assessments, seminars and other similar forums.

5.1.4 The Contractor shall document reports with findings and recommendations that fully support the experimentation objectives.

5.1.5 The Contractor shall conduct New Equipment Training (NET) for all experiment participants where prototype equipment and new operational concepts are involved. Additionally, the Contractor shall provide input, advice, and recommendations to the Government for development of handbooks, manuals, and training courses. The Contractor shall be prepared to assist the Government with MBL NET of operationally suitable and ready prototypes (emerging technologies) to the Current Force.

5.1.6 Expertise is required in the areas of future concepts, operations, analysis, data collection, training, and modeling/simulation/wargaming as a non-personal service. The Contractor shall be capable of supporting experimentation that is focused on the individual soldier up to and including the Brigade Combat Team (BCT). The Contractor shall be knowledgeable in current Army doctrine and Joint/Army Warfighting concepts.

5.1.7 The Contractor shall be required to work with a variety of DoD commands and Government agencies, including but not limited to: TRADOC G-2, Army Test and Evaluation Command (ATEC), United States Special Operations Command (USSOCOM), FFID, RDECOM, and the Defense Advanced Research Projects Agency (DARPA).

5.1.8 The Contractor shall replicate selected higher headquarters role players and exercise controllers for the AEWE experiment and other experiments as required. The Contractor shall operate an experiment control cell ensuring execution of the experimental design and analysis plan. The Contractor shall facilitate After Action Reviews (AARs) and conduct hot washes. Additionally, the Contractor shall provide an intelligence fusion and effects cell along with other key staff, as determined by the experiment design plan.

5.1.9 The Contractor shall support technical integration of associated experimental technologies, to include development of integration plans, supporting architectures, and execution of physical/systems integration in support of annual experimentation.

5.1.10 The Contractor shall be capable of evaluating industry and Government documentation related to Army requirements, capability generation, and developing recommended MCoE positions to the Government.

5.1.11 The Contractor shall develop the scenarios, road-to-war, operations orders, event list, and other necessary documents in preparation for experiments including the AEWE campaign of experiments.

5.1.12 The Contractor shall be capable of meeting additional experimentation support requirements once they are identified and experimentation support requirements for new experiments that cannot be met with existing resources. To include, but not limited to the following:

· Satisfying additional requirements for simulation operators to conduct man-machine interface for the various simulations in support of experimentation as defined in paragraph 5.1.

· Experiment Role Players. Satisfying additional requirements for qualified and certified personnel to act as experiment role players, and man leadership and staff positions for experimentation forces.

· Utilization of the following in support of systems and hardware currently owned by the government: Cisco Certified Design Associate (CCDA), Cisco Certified Design Expert (CCDE), and Cisco Certified Network Professional (CCNP) certified and trained technical support. The Contractor must demonstrate these capabilities or maintain the ability to reach out for required support.

The annual expectation for additional personnel from past years is a major event requiring approximately 67 personnel for three months and four to five experiments requiring from 5 – 10 personnel for one month. New major programs have been added that required a project officer and an assistant for one year.

5.1.13 The contractor shall perform all range support operations functions required in support of Live Experimentation. Contractor personnel in support of range operations must be certified to run ranges on Ft. Benning (and other posts as required). Ft. Benning Range operations shall be performed in accordance with the U.S. Army Infantry Center Regulation 350-19, Installation Range and Terrain Regulation. The contractor shall perform the following range functions: Range Officer in Charge (ROIC), Range Safety Officer (RSO), Ammunition Handler, Combat Life Saver (CLS), Range Safeties, Tower Operator, demolition training and range Support Personnel. These personnel are mandated by United States Army Regulation 350-19, The Army Sustainable Range Program. The majority of range operations will be conducted at Fort Benning, GA. Any range operations required to be executed outside of Fort Benning will be identified and coordinated as part of experimental planning.

5.2 Task Area: Perform operational analyses utilizing Government-approved models, threat characteristics, and deployment and employment protocols in accordance with appropriate doctrine. The Contractor shall:

· Develop an analytically sound experimentation evaluation plan for experiments. The plan must capture all Critical Operational Issues and Criteria (COICs), including Measures of Performance (MOPs) and Measures of Effectiveness (MOEs).

· Develop a data collection plan for all experiments. Data must be compiled such that it can be sorted and archived for presentation and later data-mining.

· Maintain a database of the experimentation data that is collected. The Contractor is responsible for data reduction and formatting, to include graphics that substantiate findings and recommendations.

· Recommend to the Government the data collection instruments necessary for data gathering, storage, and display.

· Design experiment data collection plans; sort, archive, and process raw data; and subsequently package and present findings for inclusion in the experimentation report.

· Interface and coordinate with test agencies such as Army Research Institute (ARI), the Army Test and Evaluation Command (ATEC), Army Research Lab (ARL) Human Research and Engineering Directorate (HRED), and other analytical organizations as required.

5.3 Task Area: Manage McKenna Urban Site for training and experimentation. The Contractor shall:

· Be responsible for operating the audio-visual system provided by the Program Executive Officer for Simulation, Training and Instrumentation (PEO-STRI) and for operating the Soldier tracking system at McKenna Urban Site and throughout the Fort Benning maneuver space. The Contractor is responsible for the instrumentation connectivity to the Simulation Lab located on Main Post to ensure live, virtual, and constructive training and experimentation capability. The Contractor shall ensure its operations are consistent with all Fort Benning, TRADOC, Army, and DoD information assurance and security policies and regulations. The Contractor shall ensure the instrumented operations are consistent with the Department of Defense Information Assurance Certification and Accreditation Process (DIACAP) accreditation procedures.

· Be responsible for all on-site management of the McKenna Urban Site to include supervision of on-site contractor personnel and day-to-day operations of the facility, self-help maintenance, infrastructure upgrades, equipment maintenance, and environmental compliance of McKenna Urban Site. Tower climber capabilities are required to service instrumentation towers. Maintenance of the facility includes but is not limited to the following: conducting routine and periodic operator maintenance on all support equipment managed and stored by MBL to ensure equipment readiness and availability to include vehicles, generators, and heavy equipment/systems; replacing antennas on towers; minor structural repair; servicing equipment required to maintain capability (e.g., generators); and grass cutting. Infrastructure upgrades are minor and include but are not limited to painting and replacing network computers and other components. In reference to environmental compliance, McKenna, and all other facilities on Ft Benning, must operate IAW AR 200-1, Environmental Protection and Enhancement. The impact is mainly in the proper storage of what the regulation classifies as a “hazardous substance”. All parts and equipment will be Government Furnished Equipment (GFE).

· Provide the logistical, operational, and network support for experimentation that is conducted at McKenna Urban Site and the instrumented maneuver space on Fort Benning.

· Integrate various simulation/stimulation systems used to create the training and experimentation federation for McKenna Urban Experimentation Facility. The Contractor shall interface directly with Government and Contractor personnel.

· Provide expert simulation technical system engineering to integrate projects and programs within the McKenna Urban Experimentation Facility. Tasks shall be performed on-site at Fort Benning. The technical requirements shall include configuring and maintaining simulation hardware and software.

· Provide the capability to create and modify 2D/3D models for a battlefield visualization product. The software to create this visualization will be provided by the Government.

· Provide configuration management of both hardware and software utilized in experiments. This includes instrumentation development and integration/installation; automation data processing; and network assurance and system administration support. Instrumentation is defined as all the technical devices and ancillary systems and equipment used to collect, sort, archive, process, present, and deliver/export experimentation data.

· Operate and train experiment participants and soldiers on the operation of instrumented systems or instrumentable manworn engagement systems and the data radio tracking system.

· Participate in all specialized projects and programs as subject matter experts (SMEs).

· Configure instrumentation to provide evaluations in compliance with network security requirements and regulations specified by the Experiment Designated Approval Authority (DAA) and the Network Enterprise Center (NEC) Benning.

· Adhere to Fort Benning, TRADOC, Army, and DoD information assurance and security policies and regulations. This includes the DIACAP.

· Plan and coordinate site occupation and ensure that the experimentation site is prepared and ready to execute upon the arrival of the organization conducting the experiment or training. Plan, coordinate, prepare, and organize the site set-up and clear participating units, physically and administratively, from MBL facilities.

· The McKenna Urban site serves as the central node for the MBL's instrumentation capability which covers the entire Ft Benning maneuver area and includes position location, shot-pairing and health status. This capability is enabled by individual soldier harnesses with the Multiple Individual Laser Engagement System (MILES) Laser system, Ground Positioning System (GPS) and data radio; 7 permanent and 2 portable towers which relay the data from the individual radios to the Control Room at McKenna where the data is captured and displayed for analysis. The Urban Site is fully instrumented with audio/visual capture, battlefield effects and targetry. The site is used extensively for both training and experimentation. Historically, the following positions have been utilized at the McKenna Urban site: Supervisor, Operations, Maintenance, Instrumentation, and Network Administrator.

5.4 Task Area: Support Experimentation in current and future operations, and provide information and logistics management. The Contractor shall provide overall operational and resource support planning, coordination, and synchronization of external support requirements for all MBL experiments.

5.4.1 Task: Information Management. The Contractor shall provide information management in support of MBL experimentation. The Contractor shall:

5.4.1.1 Perform network management, to include the McKenna and the Way Street simulation networks, including systems and applications management, fault configuration, accounting, performance, and security management. Network management incorporates all support functions associated with providing customer access to the installation of classified and unclassified data, voice, and video network(s) and connection to remote sites, DoD enterprise networks (SIPRNET and NIPRNET), and the Internet. This includes planning for appropriate network hardware and software technology upgrades and replacements to ensure customer and information assurance demands are met.

5.4.1.2 Develop recommendations, establish, maintain, and recommend compliance procedures for ADP/Network security.

5.4.1.3 Configure instrumentation to provide evaluations that are compliant with network security policies as specified by the DAA and the Network Enterprise Center (NEC) Benning.

5.4.1.4 Comply with Fort Benning, TRADOC, Army, and DoD information assurance policies, guidance, and training requirements.

5.4.1.5 Provide the MBL interface with the Network Enterprise Technology Command (NETCOM) Benning for accreditation and automation matters. Ensure the MBL is compliant with Fort Benning, TRADOC, Army, and DoD information assurance and security policies and regulations. This includes the DIACAP.

5.4.2 Task: Operations. The Contractor is responsible for operations management (planning, coordination, and execution) in support of MBL experimentation. The Contractor shall provide oversight of overall operational and resource planning, coordination, and synchronization of all resources for experiments. The Contractor shall:

· Serve as the experiment operational support liaison between MBL and all Government and non-Governmental agencies for experimentation.

· Develop and sustain the automation tools to synchronize MBL experimentation.

· Coordinate operational functions for the MBL, such as support personnel, ammunition, training area, ranges, operational briefings, and visitors.

· Operate the Range Facilities Management Scheduling System (RFMSS) to schedule ranges and terrain for experiments.

· Plan, coordinate, and handle ammunition and pyrotechnics for experimentation support.

· Maintain the MBL activities calendar.

5.4.3 Task: Logistics. The Contractor shall provide logistics management in support of all MBL experimentation. The Contractor shall provide logistics planning, execution, and support for all MBL experiments. To this end, the Contractor shall:

· Serve as the experiment technical logistical liaison between MBL and all Government and non-Government agencies requiring experimentation support.

· Serve as the MBL technical logistics SME for the MBL.

· Monitor current and project future MBL experiment technical logistical support requirements.

· Provide the technical logistical support required to execute MBL experiments and demonstrations.

· Maintain property accountability, storage, and disposal of all Maneuver Battle Lab property as directed by the MBL.

· Coordinate the shipping and receiving of all material and equipment for the MBL.

· Implement and maintain equipment maintenance plans and procedures, operator qualifications, and dispatching procedures for the safe operation of all MBL equipment.

5.5. Experimentation Workload Assignment Procedures. The services required by the Government will be requested by the Contracting Officer and reviewed by the Contracting Officer’s Representative (COR). This will be accomplished through the issuance of a Task Order (TO) by the Contracting Officer, with the applicable terms and conditions. The procedure below outlines the basic procedure for experimentation workload assignment.

5.5.1 Experimentation services are provided to outside agencies (e.g. DARPA, RDECOM, OSD, PMs etc) that approach the MBL for an experiment or assessment. If the request for services is accepted, the requirement is assigned to a Government branch chief (government personnel) who works with the government agency to define exactly what is to be done and for what purpose.

5.5.2 The primary objectives are determined by the government and the requirement is then provided to the Contracting Officer in the form of a Statement of Objectives (SOO). The Contracting Officer will then prepare and issue a Request for Task Order Response (RTOR) to the Contractor for the required services.

5.5.3 Upon the receipt of a RTOR from the Government, the Contractor shall prepare a price proposal utilizing the appropriate labor categories and hourly labor rates incorporated into the contract. The price proposal and any supporting information/documentation shall be submitted to the Contracting Officer within three (3) working days of receipt of the RTOR, unless otherwise stated. The contractor is responsible for developing the concepts needed to complete the requirement and identifying the required resources, key milestones and deliverables, and the estimated costs for completion.

5.5.4 Upon receipt of the Contractor’s Task Order Price Proposal, the Government will review the proposal for completeness, use of the proper labor categories and accuracy of the estimated labor hours proposed. The Government will negotiate with the Contractor when the proposed quality or level of work varies from what the Government estimates. Any required deliverables or technical submittals will be approved by the COR with input from the MBL Director. The Contracting Officer will issue a task order for performance of work After negotiations have concluded and all documents are approved.

5.5.5 The Contractor shall provide services in accordance with the executed task order. Task Order progress will be monitored by the COR through periodic formal and informal In-progress reviews. All reports are signed by the Director, MBL after inspection and acceptance by the COR.

5.5.6 The MBL will complete a Quality Questionnaire with the customer for adequacy of work. This data will be taken into consideration when completing the contractor’s performance assessments. A Contractor Performance Assessment Reporting System (CPARS) report will be prepared for Task Orders valued at or above $1,000,000.

6. Schedule and Reporting Requirements. The Contractor shall provide a complete historical archive of work performed and items produced (briefings, charts, papers, memos, and reports). The archive shall be electronic computer files to the greatest extent possible.