DRAFT TECHNICAL EXHIBIT A-HISTORIAL EXAMPLES.pdf

Technical Exhibit A

Information being provided as historical data ONLY and SHOULD NOT be considered as absolute in terms of present or future requirements.

RESPONDERS ARE CAUTIONED TO USE AT OWN RISK.

Maneuver Center of Excellence

Historical Examples

The following examples are provided to augment the Performance Work Statement’s (PWS’s) task areas, citing recent (within the past 10 years) historic examples of contracted efforts, at least one example per task area. Each example presented contains the year(s) performed or completed, the name of the product or effort, and a short summary of the effort with respect to the task area. The examples are provided to give potential contractors additional insight into the type, complexity, and scope of work efforts that are envisioned for each of the PWS task areas. In some task areas, additional information is provided for background, definition, or greater understanding.

Task Area 1: General Technical and Analytical Support

EXAMPLE: 2006-2011 – Base Realignment and Closure (BRAC) Support Services – Based on the BRAC 2005

Recommendation, the BRAC 2005 Implementation Plan Guide, and other guidance and implementation instructions, this life-limited effort was to provide services to facilitate development and execution of a Campaign Plan for the establishment of the Maneuver Center of Excellence (MCoE) at Fort Benning, Georgia. The Contractor provided research, analysis, and recommendations in support of re-stationing actions, including a draft or recommended:

Operations Plan (OPLAN), Campaign Plan, terms of reference, Organizations and Functions manual, and an overall timeline of all actions required to move the Armor Center from Fort Knox to Fort Benning. The Contractor also provided support to the G-3: scheduled, coordinated, and facilitated weekly meetings of the realignment teams, addressing requirements, issues, and challenges; prepared information papers and decision briefings; presented results of analysis and research to the realignment teams; monitored and recorded communications and approvals;

and reviewed infrastructure and training requirements to provide recommendations to leadership.

EXAMPLE: 2006, Ground School XXI – Feasibility study completed to determine if further action should be taken, to develop a school for ground units patterned after the aviation branch’s Flight School XXI. The feasibility study included some preliminary analysis and recommended courses of action, which resulted in a “base plus four” contract action.

EXAMPLE: 2004, Parachute Ankle Brace (PAB) – Study and analysis in three parts: (1) to determine the impact of ankle injuries on Airborne Operations, (2) to analyze the effectiveness of the PAB, and (3) to recommend future direction, implementation, and evaluation of the PAB into training and operational units. The study was performed in cooperation with the Airborne School, medical personnel, and subject matter experts, and examined 18 years of data (1985-2002).

EXAMPLE: 1997-1999, Automated Systems Approach to Training (ASAT) Integration – When the ASAT database was in its infancy, the challenge was to populate the database with courses, resources, doctrine, and supporting information as quickly as possible, to make the database usable to all users. Multiple vendors were awarded contracts to meet the challenge of: (a) simultaneously inserting information into the database, course by course

(some of which were in the process of review and update), for all courses taught at Fort Benning, all Benning resources (ranges, classrooms, transportation, ammunition, instructors, audio/visual equipment, etc.), and all doctrine used by the courses; (b) connecting or linking the information to each other; (c) testing for accuracy and completeness; and, (d) assisting in setting up user accounts for instructors, course managers, and administrators.

(NOTE: This example includes effort described under Task Areas 1, 2, 3, and 7.)

ADDITIONAL INFORMATION: The type of support provided under this Task Area tends to be short-term in nature, and addresses immediate, less predictable, surge-type actions and needs.

Information being provided as historical data ONLY and SHOULD NOT be considered as absolute in terms of

Task Area 2: Training Development Support

EXAMPLE: 2008, Mine Resistant Ambush Protected (MRAP) Family of Vehicles Emergency Rollover/Egress

Procedures Graphic Training Aid (GTA) 07-09-001 – The development of this GTA addressed the specific changes of operation and incorporated approved rollover and egress procedures to supplement the New Equipment Training and unit sustainment training. (The MRAP Family of Vehicles was ramped up during 2007, as a vehicle unlike any other tactical vehicle, with different steering, handling, and maneuvering characteristics.)

EXAMPLE: 2001-2002, Basic Non-Commissioned Officers Course (BNCOC) Interactive Multimedia Instruction

(IMI) – The Contractor was required to review and redesign selected Programs of Instruction (POI) of BNCOC, converting it from classroom instruction to independent computer-based study. Included were the basic principles of map-reading and land navigation, tactics, forward observer procedures, and call for fire procedures, each of which included a pre-test, periodic checks on learning, and a post-test. The product also included an interface which allowed the student to ask questions, up-load test scores, and gain a certificate of completion. The finished product was designed to act as a prerequisite to the resident course, eliminating approximately one-third of the cost and time of sending a Soldier to the course. (Within a couple years, however, the changes to the course were sufficient to render the IMI obsolete. That stated, MCoE anticipates that review and redesign work of a similar nature may be required for other POIs.)

Task Area 3: Doctrine Development Support

EXAMPLE: 2004-2006, Lessons Learned Integration – Observations and lessons learned from theater-specific operations were analyzed and integrated into doctrine. Support in this contract included the integration of updated

Tactics, Techniques, and Procedures (TTPs) into the Field Manuals and other doctrinal publications.

EXAMPLE: 1999-2001, Combined Arms MOUT Task Force (CAMTF) – Fueled in part by the conflict in Kosovo, this contracted effort to develop an overarching urban operations training strategy for the Army included updates to training, recommendations to improve training and training facilities, and the updating of all Urban Operations doctrinal publications. In the doctrinal area, the effort updated and linked Field Manual (FM) 3-06 Urban

Operations (formerly 90-10 Military Operations on Urbanized Terrain) to FM 3-0 (100-5) Operations, and Joint

Publication (JP) 3-06 Doctrine for Joint Urban Operations, and linked FM 3-06.11 Combined Arms Operations in

Urban Terrain (formerly 90-10-1 An Infantryman's Guide to Combat in Built-Up Areas) and 7/71 Series FM updates to FM 3-06 (90-10) for brigade-sized organizations and below.

Task Area 4: Capability Development Support

EXAMPLE: 2005 - 2007, Project Sheriff / Full Spectrum Effects Platform (FSEP) – Now classified as a variant of the Stryker vehicle, the initial concept development (Project Sheriff) and subsequent experiments/testing stemmed from Operational Needs Statements (ONS) that outlined the need for a capability to escalate force as needed when operating in an urban environment. The concept was for a suite of scalable non-lethal devices/weapons, combined with lethal weapons onto a single existing military vehicle, which would provide a full spectrum of components in conducting force protection missions, route reconnaissance, crowd control, raids, and point defense – all in the effort to save lives and reduce collateral damage. Contracted efforts under the initial project included: review of combat tasks for essential/critical tasks; cross reference of critical tasks to problem / solution in areas which needed improvement; research of current technologies for specific performance capabilities; identification of potential vehicle candidates from current inventory.

Information being provided as historical data ONLY and SHOULD NOT be considered as absolute in terms of

ADDITIONAL INFORMATION:

Capability Development hinges on the JCIDS process (see also TRADOC Regulation 71-20):

a) Concepts feed the JCIDS. Concepts illustrate how forces will operate, describe the capabilities required to carry out a range of military operations against adversaries in the expected joint operational environment (JOE), and how a commander, using military art and science, might employ these capabilities to achieve desired effects and objectives. They are the foundation for future requirements determination efforts. Concepts consist of future capabilities descriptions within a proposed structure of military operations for a period of 10-20 years in the future.

Each concept describes problems to solve, the components of potential solutions, and how those components work together to solve the problems.

b) Experiments explore innovative methods of operating to assess their feasibility, evaluate their utility, or determine their limits to reduce risk in current operations and future development efforts. Experimentation identifies and verifies acceptable solutions for required changes in DOTMLPF to achieve significant advances in force capabilities. Experiments aid in validating the feasibility and utility of future requirements determination efforts. Concept development and prototype experiments help refine capabilities development and reduce risk to warfighters by providing credible analytical underpinnings to support decision making for force development.

Experimentation applies structured assessment procedures to substantiate the effects of proposed warfighting capabilities using discovery, hypothesis-testing, and demonstration approaches as appropriate.

c) Requirements determination assesses required capabilities to identify gaps and develop DOTMLPF RIO solutions to resolve or mitigate gaps with unacceptable risk. It consists of determining, prioritizing, and documenting changes in DOTMLPF, as well as supporting analysis. These new requirements are the result of JCIDS capabilities-based assessments (CBAs), operational needs statements (ONS), operational lessons learned, and senior leader decisions to accelerate the fielding of future capabilities to the force. Initial capabilities documents (ICDs);

capability development documents (CDDs); capability production documents (CPDs); joint DOTMLPF change recommendations (DCRs); and Army DOTMLPF integrated capabilities recommendations (DICRs) formally document these new requirements.

Task Area 5: Training Instruction Support

EXAMPLE: 2008-present, NCO Academy Instructors – In response to losses in Active Duty personnel caused by unit rotation and operational units’ shortages, contracted personnel augmented the Academy personnel, presenting nearly the entire course’s Programs of Instruction for enlisted professional development.

EXAMPLE: 2003 – 2010, Javelin Training Instructors – Contracted personnel augmented the active-duty military, and presented information and instruction on the safe operation of the Javelin weapon system, a shoulder-launched, anti-tank weapon. The approved Program of Instruction was an 80-hour course, delivered approximately 18 times per year. Target audience was E-1 through E-5, for Infantry, Armor Scout, and Combat Engineers. The requirement for this instruction was discontinued by TRADOC, based on manpower reductions.

Task Area 6: Simulations and Analysis Support

EXAMPLE: 2005 - 2007, Project Sheriff / Full Spectrum Effects Platform (FSEP) – (See TE 4 discussion for additional description.) Contracted efforts under the maturing project included: virtual simulation of patrol scenarios, with variables (i.e., crowd control, sniper attack, IED detonation, and cordon and search), and the analysis

Information being provided as historical data ONLY and SHOULD NOT be considered as absolute in terms of of action / outcomes. Simulations and varied scenarios showed areas which needed improvement, and allowed for refinement of specific capabilities.

EXAMPLE: 1998 - 2004 New Generation Army Targetry System (NGATS) – Hardware and software replacement and enhancement of targets, which replicate battlefield visual and audio events on military training ranges, as part of the immersive technology replacing live fire exercises with constructive simulations. Simulation proved to save on resources, including ammunition, target repair, manpower, and availability of ranges.

ADDITIONAL INFORMATION: Since 2002, the Army has been working to establish the ITE to enable more effective, efficient training in the resource-constrained Army Force Generation (ARFORGEN) process. The ITE gained traction in October 2009, when the Live, Virtual, Constructive Integrating Architecture (LVC-IA) became a funded program of record (POR). Viewed as the "engine" of the ITE, the Integrating Architecture is the standards, protocols and design criteria that enable systems to communicate without excessive numbers of operators (low overhead), workarounds or specially designed computers. The Army plans to match LVC-IA with training infrastructure such as TADSS, land, ranges, Battle Command Training Capabilities and the Framework for Army

Training and Education (training support packages, databases and common scenarios) to provide ITE core capabilities to 12 FORSCOM installations by fiscal year (FY) 16.

Task Area 7: Support Services

EXAMPLE (Stand-alone Requirement): 1999-present, CONUS Replacement Center (CRC) - The mission of CRC is to receive and process individual non-unit related personnel (NRPs) of all branches and components, civilians, employees, contractors and units for deployment to and re-deployment from theaters of operations in various locations across the globe. Contractors now provide the majority of the work force for this effort. The Contractor is required to: process military personnel action requests; monitor military awards programs and decorations packages;

prepare and coordinate Evaluation Reports for Officers and NCOs; prepare official correspondence in draft and final copies. The Contractor is further required to maintain accurate records in: tracking system and historical records;

battalion records for Drug and Alcohol, Safety, Weight Control, and MWR programs; duty rosters, personnel rosters, and emergency contact information; personnel accountability and tracking - via the Worldwide Individual

Augmentation System (WIAS) and the Replacement Operations Augmentation Management System (ROAMS) - to include arrival and departure reports; and to prepare in the Defense Travel System (DTS), travel vouchers and per diem requests for personnel processing through CRC.

EXAMPLE (Support of Other Work): 1998-2010, Editorial Support – A small pool of editors and illustrators:

reviewed doctrine and training products for grammatical and style errors; added graphics (charts, graphs, pictures, sketches, etc.) with captions; inserted reference and cross-reference items (index, table of contents, table of illustrations, annexes, and appendices); paginated documents; and prepared products for mass printing.