MBL_Requirement_ver_1.6_(04-16-10).docx

Maneuver Battle Lab 35 Ridgway Loop Forty 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 TRADOC’s ARCIC Campaign Plan (ArCP). The MBL routinely supports 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). The MBL is formational based and primarily experiments 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, 30 April 1997.

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, 6 Oct 09.

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

2.10 The Army Capabilities Integration Center (ARCIC) Campaign Plan (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: The Contractor shall provide program management, technical, and analytic skills in support of the MBL experimentation plan. The Contractor shall provide a skilled workforce to conduct all tasks related to experimentation: planning, preparing, executing, analyzing, and documentation. The contractor shall provide the skilled work force to meet experimentation requirements typically found in the ArCP Campaign plan which have a long lead time as well as short term requirements that are measurable in months or less. The contractor shall provide a sustainable integrated simulation capability that is DIACAP compliant with the ability to surge technical capability as required to meet experimentation requirements.

3.1 Place of Performance. This contract is 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 and Afghanistan and other potential future Theater of Operations.

3.2 Period of Performance. The intended period of performance is 30 August 2010 through 29 August 2011 with four additional one (1) year option periods. The hours of 0800 to 1700 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. Overtime may be required as an integral part of this labor contract. Overtime requirement for this contract is estimated to be 5% percent of the total hours performed. All written requests for overtime/EWW must be approved by COR in writing prior to execution. A copy of this approval must be included with the Monthly Task Service 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), Army Capabilities Integration Center (ARCIC) Campaign Plan (ArCP) experiments and experiments in support of the Maneuver Center of Excellence (MCOE) and other Department of Defense (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 Department of Defense.

3.6 Examples of 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:

4.1 Task Area: Plan, Prepare, Execute operations to support and conduct experimentation. Execute experimentation in support of The Army Capabilities Integration Center (ARCIC) Campaign Plan (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 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. The norm is four to six experimentation efforts annually with most at the brigade down to platoon and individual Soldier level. 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.

4.1.1 Task: Simulation Environment Planning. The Contractor shall provide personnel who 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 coordination with 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.

4.1.1.4 For each experiment, demonstration, study, or test, the Contractor shall conduct technical and Modeling and Simulation 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.

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.

4.1.3 Task: Simulation Environment Execution. The Contractor shall provide personnel who can 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 conduct experiment surveys.

· Enable and assist the experiment Project Lead conduct 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 The contractor shall provide a group of qualified and certified personnel for simulation control and technical control to conduct man machine interface for the various simulations in support of experimentation as defined in paragraph 4.1.

4.1.3.2.2 The contractor shall provide a full time group of qualified and certified personnel for 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 provide personnel who shall configure, maintain, develop, and prepare data collection products derived from simulation events in coordination with 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 Doctrine, Organization, Training, Materiel, Leadership, Personnel, and Facilities (DOTMLPF) areas.

4.2.1 The Contractor shall provide personnel with 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 provide the capability to trouble-shoot simulation software and hardware for the virtual and constructive simulations and simulators used by the MBL.

4.2.4 The Contractor shall provide the capability to 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 provide the capability to 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 provide the capability to 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 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 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 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: Infantry Brigade Combat Team (IBCT), Heavy Brigade Combat Team (HBCT), Stryker Brigade Combat Team (SBCT), Armored Calvary Regiment (ACR), Battlefield Surveillance Brigade (BfSB), and in coordination with the Future Force Integration Directorate (FFID), the Brigade Combat Team Modernization Program.

4.2.10 The Contractor shall provide the capability to 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. To include the following:

· The Contractor shall provide personnel knowledgeable in Geospatial Information tools who 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 provide the capability to: 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 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.

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 WAN and LAN networks.

4.3.4 The Contractor shall relocate WAN and LAN 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.

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

· Cisco Certified Entry Networking Technician (CCENT), Cisco Certified Network Associate Routing & Switching (CCNA), CompTIA Network+, Red Hat Certified Engineer (RHCE), Microsoft Certified Systems Engineer (MCSE), and Microsoft Certified Systems Administrator (MCSA) Certified and trained technical support must be available within the current workforce.

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 IAW 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 by name to assist the MBL Information Assurance Security Officer (IASO). Duties shall include: 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 assist the MBL IASO in the performance of his duties as specified in AR 25-2.

4.4.3 The Contractor shall ensure that the MBL facilities comply with the requirements of facility physical security so that there is no interruption of experimentation.

4.5 Government Furnished Property (GFP). The Contractor shall Install, operate, configure, maintain, inventory, and account for Government Furnished Property.

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 SPSS (Statistical Programming for Social Science) VISSA (Virtual Soldier Skills Assessment)

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

OneSAF (Objective One-SAF) JSAF (Joint Semi-Automated Forces) IWARS (Infantry Warrior Simulation) 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:

DCATS (Data Collection and Analysis Tool) DCARS (Digital Collection, Analysis and Review System) J/DCARS (Joint Digital Collection, Analysis and Review System) 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 directed by the government.

4.5.10 The Contractor shall Turn-in unserviceable, excess, or unneeded equipment to DRMO as directed by the Government.

4.5.11 The Contractor shall maintain MBL facilities.

· 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 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 the place of performance. 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 task. 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 shall fund training of Core task personnel. Such training shall not be chargeable as part of the contract direct labor costs.

4.6.2 The Government shall fund the initial training of personnel 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 shall fund training of simulation Interactors/Operators (SI) as required to support specific experimentation efforts.

4.6.4 The Contractor shall fund sustainment training/certification for existing personnel.

4.6.5 The COR or his/her delegated representative must approve required training that the Contractor justifies to be chargeable to the task in advance.

5. EXPERIMENTATION SUPPORT

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 are conducted in accordance with memorandums of agreement and associated milestones between the customer and the Director, MBL.

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 new MBL equipment training (NET) of operationally suitable and ready prototypes (emerging technologies) to the Current Force.

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

5.1.7 The Contractor shall have a demonstrated ability 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), Future Force Integration Directorate (FFID), Research and Development Engineering Command (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 Army Expeditionary Warrior Experience (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 provide additional surge personnel to meet experimentation support requirements once they are identified and to meet experimentation support requirements for new experiments that cannot be met with incumbent personnel. To include:

· The contractor shall provide required additional qualified and certified personnel 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. As required the contractor shall provide qualified and certified personnel for experiment role players to man leadership and staff positions for experimentation forces.

· Cisco Certified Network Professional (CCNP), Cisco Certified Design Associate (CCDA), Cisco Certified Design Expert (CCDE), and Cisco Certified Network Professional (CCNP) Certified and trained technical support must be available either within the current workforce or contractor must maintain ability to reach out for required support.

The annual expectation for additional surge 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 require a project officer and assistant for one year.

5.1.13 The contractor shall perform all range support operations functions in order to operate a range as outlined in U.S. Army Infantry Center Regulation 210-4 (Range and Terrain Regulation). The contractor shall provide personnel to 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. The majority of range operations will be conducted at Fort Benning, Ga. Range operations off Fort Benning will be identified and coordinated when required.

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 MBL on-site contract management and self-help maintenance, infrastructure upgrades, equipment maintenance, and environment compliance of McKenna Urban Site. Conduct 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. The Contractor shall provide tower climbers to service instrumentation towers. 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 experimenters 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 DoD Information Assurance Certification Accreditation Process (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.

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 is compliant with network security policies as specified by the Designated Approval Authority (DAA) and the Network Enterprise Center (NEC) Benning.

5.4.1.4 Disseminate and implement Fort Benning, TRADOC, Army, and DoD information assurance policies, guidance, and training requirements.

5.4.1.5 Provide the MBL interface with the 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 Department of Defense Information Assurance Certification and Accreditation Process (DIACAP).

5.4.2 Task: Operations. The Contractor is responsible for operations management (planning, coordination, and execution) of all 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 synchronized 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 MBL property on-hand and property provided to MBL in support of a variety of experiments.

· 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.

6. Contract Transition. The transition period shall begin immediately after the post award conference and must be completed in no later than 30 days following immediately the post award conference.

6.1 The Contractor shall begin transition activities with the existing Contractor providing MBL support immediately after the post-award conference.

6.2 The Contractor shall conduct a thorough transition inventory of all equipment, software, and infrastructure.

6.3 Transition will occur without any interruption of ongoing experiments. Experiment planning and preparation currently underway will be handed off to new contractor with Government oversight. All reports will be completed before completion of transition but no more than 60 days post award of new contract.

7. Facilities Transition

7.1 The Contractor shall be required to support actions necessary to implement transition planning, preparation, and execution of the move of the MBL-Virtual Constructive Simulation Division – Fort Knox (VCSD-K) from Fort Knox, KY to Fort Benning, GA and its integration with the MBL.

7.2 The Contractor shall be required to support actions necessary to implement transition planning, preparation, and execution in support a move of the MBL from current facilities into new facilities. These actions include: conduct an inventory; identify packing materials and shipping requirements; pack equipment and items; move sensitive computers and equipment; unpack at new facility; confirm inventory; and install, setup, and configure items. This may involve an interim building leading up to final MBL facilities.

8. 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. The files/archive shall be made available for review upon request of the Government.

8.1 The services required by the Government will be requested by the Contracting Officer and reviewed by the Contracting Officer’s Representative (COR). This shall be accomplished by means of the Contracting Officer issuing a Technical Letter of Direction (TLD) with a Government sample of process. The Contractor shall deliver all end items specified in the TLDs as well as the work control documentation to the COR. The COR will review the Contractor’s deliverables in accordance with all specifications stated in the TLD. Only the COR will have the authority to inspect and accept or reject deliverables. The acceptance of deliverables and satisfactory work performance required herein shall be based on the timeliness and accuracy of the service requested by the COR. Deliverables shall be itemized and explained in individual TLDs. See below for detailed breakout of additional deliverables. A hardcopy of all invoices and Monthly Status Reports shall be given to the COR for review. Invoices will be entered into the Wide Area WorkFlow (WAWF) system for DFAS payment.

8.2 The Monthly Narrative Report and the Monthly Task Summary Report (MSR) and a copy of the invoice shall be submitted to the COR by the 10th.of each month. The specific deliverables and schedule for deliverables shall be documented in the TLDs.

8.3 Schedule. Specific delivery schedule will be identified in individual TLDs.

8.4 Acceptance Criteria – Each TLD will be evaluated by the completion of each expected objective and achievement of the proposed schedule.

8.5 Inherent to the services described herein is the Contractor's ability to provide successful completion of all TLDs. The Contractor will immediately inform the COR or his/her Government representative (as designated in writing) when a problem is beyond its expertise. A description of the problem and the implemented resolution shall be provided to the COR or his/her Government designated representative, within five days of problem recognition. The Contractor shall submit a Problem Resolution Report to the COR, monthly.

8.6 The Contractor shall submit a Monthly Narrative Report to the COR containing the following information:

· Brief description of current requirements

· Brief summary of accomplishments during the reporting period

· Significant events regarding the TLD

· Progress on deliverable products

· Current or anticipated problems

· Summary of activity planned for the next reporting period.

· Formal review meetings will be held between the Contractor and the COR on a monthly basis. The exact date of these meetings will be determined by task demands and objectives, and will be set at the discretion of the Government.

8.7 The Contractor shall submit a Monthly Task Summary Report. The report shall include labor charges for actual hours worked and other costs which may be authorized in the task (e.g., travel and training). Original receipts, and travel vouchers completed in accordance with (IAW) and required by Government Travel Regulations shall be maintained by the Contractor to define charges other than labor hours and made available to Government auditors upon request.

Note: Travel charges must include the traveler’s name and dates of travel. Reports must be generated from the first calendar day of each month to the last calendar day of each month. (i.e., January 1st through 31st, etc.). All travel will be conducted and reimbursed IAW FAR 31.205-46.

8.8 The Contractor shall submit monthly invoices to the COR for review. The invoices shall include all information required by FAR clause 52.232-25, Prompt payment. Hours and rates incurred by individual skills and a summary page of all skills shall be attached. Invoices shall also include all travel, training, and additional costs incurred and previously approved by the COR. A Contractor official with authority to bind the company contractually shall certify all invoices.

8.9 Formal performance review meetings shall be held between the Contractor and the MBL COR and MBL Leadership on a periodic basis.

8.10 The Contractor shall submit invoices for work performed.

9. Travel. Travel may be required to fulfill the requirements of this task. Locations and duration of travel cannot be established at this time; therefore a travel budget is estimated at $500,000 per year. All travel must be approved in advance. The Contractor is required to submit a trip report to the Branch Chief and COR 24 hours or the next business day after completion of the trip (IAW MBL SOP). The Contractor shall ensure that the requested travel costs shall not exceed what is authorized and approved by the COR for each trip. Travel shall be in accordance with FAR 31.205-46.

10. Expertise and education. The Contractor is required to provide personnel with technical, educational, and functional expertise for execution of the MBL experimentation support mission. The Contractor shall have knowledge and experience in Army requirements generation processes and a detailed knowledge of the MCOE MBL and its associated projects. Contractor personnel shall be required to work outdoors and be thoroughly familiar with the development of experimentation sets and their implementation. Strong interpersonal skills are necessary to perform in this vital capacity. Contractor personnel shall have the ability to collaborate and coordinate at the highest levels within the Infantry Center and at TRADOC, Department of the Army, and other agencies, to include the military and the civilian sectors. Contractor personnel shall have strong communications skills (oral and writing skills) and a working knowledge of computers and associated software, to include but not limited to Microsoft Word, Excel, Access and Power Point.

10.1 Contractor ADP personnel shall have the ability to perform operations, test, and maintain computer systems, including all servers and…