Attachment 12 Sample TO 2.doc

Sample Tasks Order 2 - Training Developer Fort the procurement of

TRAINING, DOCTRINE, CAPABILITY DEVELOPMENT, ANALYSIS,

INSTRUCTION, ROLE PLAYERS AND SUPPORT SERVICES

AT FORT KNOX KY, AND FORT BENNING GA

MANEUVER CENTER OF EXCELLENCE

14 Dec 09 NOTE: MICC Center – Fort Bragg will be providing workload data to assist in the calculation of Sample Task Order 1 and Sample Task Order 2 total price at a later date. This data will be inclusive of class schedule, duration, size, and student/intructor ratio.

1. BACKGROUND: The objective of this Performance Work Statement (PWS) is to provide support in the development, coordination, and integration of training products for existing and emerging needs at the Maneuver Center of Excellence (MCOE), and enable accomplishment of high priority missions and developments within the Training and Doctrine Command (TRADOC) and the MCOE.

2. SCOPE OF WORK: The Contractor shall provide qualified personnel to support all stages of development and integration of training products into Institutional, unit, individual, pre-deployment, and other training. Training developers shall provide support in assigned programs to include: researching, developing, planning, coordinating, scheduling, testing, fielding recommending courses of action. This support can be for any or all of: updates, strategies, publications, courseware, programs of instruction, training aids, devices, simulations, simulators.

Work shall normally be performed at Fort Benning or Fort Knox, with travel to various sites for system/product coordination, testing, planning, symposiums, conferences, briefings, and/or feedback in support of soldiers and units worldwide. The Contractor shall provide a workforce with sufficient expertise, experience, skills, and other necessary credentials to accomplish the tasks described below. The Contractor is responsible for identifying personnel with the requisite technical expertise, experience, skills and for notifying the Contracting Officer’s Representative (COR) of any real or potential deficiencies in personnel availability. This does not, however, relieve the Contractor of any performance requirements.

2.1. Task Area 1: Prepare a Start of Work Briefing (SOWB). The Contractor shall develop a Start of Work Briefing (SOWB) in accordance with the contract.

2.1.1. The SOWB shall describe in detail the Contractor's approach to:

2.1.1.1. Provide qualified training developers to support the MCOE’s various current programs of record and emerging / developing programs, which include, but are not limited to: individual and collective tasks; weapons and ammunition; new equipment training; tactical training systems; and soldier systems.

2.1.1.2. Ensure general prerequisites applicable to all training developers are met, to include:

2.1.1.2.1. Expertise in English language, written and spoken, sufficient to: prepare briefing materials; write technical papers; participate in teleconferences and video teleconferences; prepare and deliver status briefings and updates; understand instructions and guidance as given by Government decision-makers.

2.1.1.2.2. Experience and expertise in the use of automated data processing (ADP) equipment and Microsoft products (Word, Excel, Access, PowerPoint, Outlook, etc) sufficient to produce documents, correspondence, and presentations as required.

2.1.1.2.3. Working knowledge of various applicable Army regulations, to include but not limited to:

· Army Regulation 350-1, Army Training and Leadership Development

· Army Regulation 350-38, Training Device Policies and Management

· DA Pamphlet 350-38, Standards in Weapons Training

· TRADOC Regulation 350-70 Systems Approach to Training Management, Processes, and Products.

· TRADOC Pamphlet 350-70-1 Guide for Developing Collective Training Products

· TRADOC Pamphlet 350-70-4, Systems Approach to Training: Evaluation

· TRADOC Pamphlet 350-70-5, Systems Approach to Training: Testing

· TRADOC Pamphlet 350-70-6, Systems Approach to Training: Analysis

· ARTEP publications, Field Manuals, Training Circulars, and other Infantry/Armor products specific to programs

2.1.1.2.4. Working knowledge and applicable experience in the development of Programs/Systems. As a Subject Matter Expert (SME), the Contractor shall, for each program assigned, provide comments, lessons learned, recommendations, input/develop training and integration strategies, modifications to training program, recommend improvements, transitions, growth, fielding, and Training Aids, Devices, Simulators and Simulations (TADSS), as appropriate. For each program, the Contractor shall provide personnel with background, experience, and expertise applicable or related to that program. In the case of new technology, a related field as appropriate may be substituted for the specific new program.

2.1.1.2.5. Working knowledge of the Army acquisition process. As a training developer, the Contractor shall coordinate with combat developers, program managers, program executive offices, and others as needed to research, develop, modify, and staff documents within the Joint Capabilities Integration Development System (JCIDS) process. At various times throughout the life cycle, the contractor will be involved in working groups and integrated process teams to: develop the F-series Analysis (Functional ); develop, update, or adjust the System Training Plan (STRAP) associated with the Initial Capabilities Document (ICD), the Capability Development Document (CDD), and the Capability Production Document (CPD); provide training input to the Basis of Issue Plan (BOIP), and insure the BOIP reflect the training requirements shown in the STRAP.

2.1.1.2.6. Military experience. The Contractor shall have military experience equivalent to four (4) years of more of active duty. While Combat Arms is preferred, both Unit and Staff positions, other experience in related areas is acceptable.

2.1.1.2.7. Working knowledge of Infantry (11 series) and Armor (19 series) Military Occupational Specialties (MOS). The Contractor shall have knowledge of MOS/Field structure, training requirements, capabilities, physical demands, and proponent systems.

2.1.1.2.8. Working knowledge of the programming and budget process. The Contractor shall have some experience in or knowledge of the acquisition process, and the timeline by which the Army determines its budget.

2.1.1.2.9. Critical thinking. The contractor must have the ability to: utilize analytical tools and technologies, such as war games, simulations, and scenario development; apply critical thinking skills to the development of strategies and integration plans; clearly express ideas in written or oral form; and understand and apply knowledge of secondary and tertiary consequences stemming from primary actions/decisions.

2.1.1.2.10. Clearance. Due to the nature of the work performed and network access requirements, all Contractor personnel shall have a current clearance, at or above “SECRET,” while under contract. For new clearance requests, the Contractor’s Facility Security Officer (FSO) shall: ensure that the employee completes an application, and submit an investigation request through the centralized database, Joint Personnel Adjudication System (JPAS). The Contractor shall ensure personnel are cleared through JPAS, with a valid clearance, prior to reporting for duty on site.

2.1.2. The management portion of the SOWB shall describe the Contractor's approach to staffing and managing project requirements.

2.1.2.1. The plan shall identify all Contractor and sub‑contractor key personnel, including the overall project manager, by name and qualifications (including experience with Army training in general, and task based training in particular).

2.1.2.2. The management portion of the SOWB shall specify the approach for recruiting and maintaining highly qualified personnel.

2.1.2.3. The plan shall include methods for managing the efforts of sub‑Contractors, procedures for coordination with proponent units and entities within the MCOE, which includes, but is not limited to: 192nd Infantry Brigade, 197th Infantry Brigade, 198th Infantry Brigade, 199th Infantry Brigade, 194th Armored Brigade, 16th Cavalry Regiment.

2.1.2.4. The plan shall include methods for managing communications and coordination within the MCOE. While most Contractors will be assigned to work within the Directorate of Training and Doctrine (DOTD), they must work in cooperation with Schools and Directorates, as illustrated in the Organizational Chart. Additionally, work space assignments are availability-based, and subject to change

2.1.3. The management portion of the SOWB shall describe the Contractor's plan and approach for quality assurance, surveillance, and in-place corrective procedures/plans for this project.

2.2. Task Area 2. The Contractor shall provide qualified training developers. Training developers are assigned in two distinct areas: (1) to support various programs/systems and related training efforts and (2) develop new and review current training materials and documents.

2.2.1. The Contractor shall provide training developers to serve as Subject Matter Experts and Action Officers for programs or systems. Programs vary in maturity from concepts and spin-out developments to near-retirement; therefore, the specific needs of each program will be different. Due to the dynamic nature of some programs, the nomenclature may change, or one program may be absorbed into another, or split into multiple programs. The Contractor must be flexible in responding to these changes; program changes do not absolve the Contractor from meeting any requirements agreed upon, except as listed in contract modifications.

2.2.1.1. The Contractor shall provide at least one qualified person to each of the programs listed in this paragraph. A “qualified person” (in addition to requirements listed in paragraph 2.1.1.2. and its sub-paragraphs) is defined as one with “hands-on experience or equivalent education” in the program field or a closely-related field.

· Combat ID/Vehicle Recognition

· Personnel Recovery

· Robotics

· Close Combat Missile Systems (Javelin, TOW)

· Battle Command System Concepts

· Instructional Systems Design

· Military Education System

· Bradley Fighting Vehicle

2.2.1.2. The Contractor shall provide at least two qualified persons to each of the programs listed in this paragraph. A “qualified person” (in addition to requirements listed in paragraph 2.1.1.2. and its sub-paragraphs) is defined as one with hands-on experience or equivalent education in the field or related field.

· STRAP Manager/Coordinator

· Sniper/Counter-Sniper

· Escalation of Force/Nonlethal systems

· Live, Virtual, and Constructive (LVS) Simulations

2.2.1.3. Action officer activities and duties include: develop/maintain a continuity book, which contains pertinent information such as points of contact, quad charts, goals, projected requirements; update status of program and related documents, and location information of electronic files; attend meetings and briefings, and provide minutes or summary; develop briefings, provide updates, track milestones, and report to/through COR and other Government personnel as required on program progress/status; develop and staff program-related documents, training requirements, and graphic training aids; observe training events, drills, tests, simulations, symposiums, and other activities for insights, results, information, and new developments within the program; review and recommend revisions for Technical Manuals within program area; maintain communication with COR and assigned Government personnel.

2.2.2. The Contractor shall provide qualified training developers to conduct research and develop training documents and materials, to include: Programs of Instruction (POIs); Training Support Packages (TSPs); task analysis (individual and collective); lesson plans (LP); training materials to be integrated into a Combined Arms Training Strategy (CATS); analysis of Training Aids, Devices, Simulators, and Simulations (TADSS); Situational or Field Training Exercises (STX/FTX).

2.2.2.1. The Contractor shall provide qualified training developers who have the ability to understand and apply training development principles, concepts, practices and standards. Personnel must have demonstrated experience developing technical or procedural documentation (training manuals, technical manuals, quick reference guides, user manuals), and experience in preparing for or participating in Validation and Verification (V&V) reviews.

2.2.2.2. Training developers assigned to this task use training applications to create, edit, and retrieve task, LP, and POI information. The current application, the Automated Systems Approach to Training (ASAT), is an installation-independent database, scheduled to be phased out and replaced with the Training Development Capability (TDC), a Web-based program consolidating the TRADOC training products into a single database. Personnel assigned to this task must be available for developmental training, teleconferences, and progressive updates.

2.2.2.3. Training developers shall develop new training products as needed, to reflect the changes in the Army’s individual and collective tasks, training priorities, institutional and unit training, and

2.3. Task Area 3. The Contractor shall adhere to all administrative requirements and guidance.

2.3.1. Identification of Contractor personnel. The Contractor shall endure proper identification of all Contractor employees.

2.3.1.1. Prior to the contractor reporting for duty, the FSO shall send the COR a Visit Authorization Letter (VAL) of verification. The purpose of the VAL is twofold: (1) to inform the Government that an individual has been hired onto a contract, and (2) to provide a source document for facility and network access. Contractors must submit the Visit Authorization Letter must submit them through their responsible Facility Security Officer (FSO) IAW DoD 5220.22-M (28 Feb 06), Chapter 6. All requests must be submitted on company letterhead, signed by the company FSO, and faxed or encrypted e-mailed to the MCOE Point of Contact (COR or designated Government representative). The VAL must have the following information:

· Name

· SSN

· Citizenship

· Eligibility level and date (Example: SECRET granted 03 Jul 08)

· Type of investigation and date (Example: SSBI dated 14 Jun 08)

· Purpose of visit (Example: For work on Contract # XXXX00-00-X-0000)

· Date of birth

· Place of birth

· MCOE POC (if not the COR, both COR and POC must be listed)

· Length of visit (maximum 1 year)

· Signature block of FSO

2.3.1.2. The Contractor shall provide each employee an identification (ID) card/badge. The ID badge shall be made of nonmetallic material, easily readable, and include mandatory elements of employee's name, Contractor's name (logo optional), and color photograph. Optional elements may include contract/employment start date, functional area of assignment, employee number, or other information at the Company’s discretion, but may not interfere with the legibility of the required elements.

2.3.1.3. Contractor personnel shall wear the ID badge at all times when performing work under this contract to include attending Government meetings and conferences. Unless otherwise specified in the contract, each Contractor employee shall wear the ID badge in a conspicuous place on the front of exterior clothing and above the waist, except when safety or health reasons prohibit such placement.

2.3.1.4. Contractor personnel shall identify themselves as Contractor employees when answering Government telephones.

2.3.1.5. When prime Contractor or Sub-Contractor personnel send E-mail messages as a part of contract performance (or otherwise relating to contract matters), each sender shall include his/her name (both first and last names), E-mail address and the name of the individual's employer.

2.3.1.6. Contractor personnel shall identify themselves as Contractor employees in any case or circumstance where the possibility exists that said employee could be mistaken for a Government representative. Contractor employees are responsible to avoid the impression or appearance of mistaken identity. For those employees who are retired military, the display name used in Outlook or other global e-mail media shall indicate their contractor status, not their retiree status, while performing work on or for the contract.

2.3.2. Travel. Travel is sometimes required to fulfill the requirements of this task. The Contractor shall ensure that the requested travel costs will not exceed what has been authorized in the task order. If performed, travel shall be in accordance with the Joint Travel Regulations (http://www.dtic.mil/perdiem/jtr.html). The Contracting Officer or his/her delegated representative must approve all travel in advance. The Contractor personnel shall be required to perform travel to various locations within, and possibly outside, the continental U.S. Specific locations and duration of travel will be established and funded during performance of contract.

2.3.3. Working hours. The hours of 0800 to 1700, Monday through Friday, are the projected normal working time, operating over a standard five day period (40 hours per week), excluding Government holidays. However, these operating hours and days may vary, based on the requirements of the Government. Contractor Personnel work schedules may be flexed to meet the manpower requirements for weekend and extended duty periods during regular training and exercises. Contractor Personnel work schedules shall NOT be flexed for either the convenience of the Contractor or Contractor personnel without the expressed written consent of the COR on a case by case / individual basis.

2.3.4. Security and Privacy. All Contract personnel assigned by the Contractor to perform under this SOW shall possess a security clearance at or above the security level of “SECRET.”

2.3.4.1. Privacy Act. All Contractor personnel assigned may have access to information subject to the Privacy Act of 1974. The Contractor is responsible for ensuring all assigned Contractor personnel are briefed on Privacy Act requirements.

2.3.4.2 The Contractor shall ensure that all assigned personnel understand applicable Security policies and directives. Personnel who knowingly violate security policies or directives shall be dismissed.

3. GOVERNMENT FURNISHED DATA, PROPERTY, AND EQUIPMENT. The Government will provide office/work space at the MCOE, and appropriate equipment as best suits the needs of the tasks, as follows.

3.1 Common Access Card (CAC). The Government will issue a Common Access Card (CAC) for those employees whose functions require access to systems or facilities controlled by the Common Access Card. Paragraphs 2.1.1.2.10. and 2.3.1.1. apply as a precursors to CAC issuance.

3.1.1. The CAC is used for access to MCOE e-mail accounts and computer systems. Contractor employee shall obtain CAC at the local DEERS/RAPIDS terminal when application is approved. Contractor employee shall inform Corporate Facility Security Officer (FSO)/Security Manager of approval/denial of CAC application. The Contractor shall be responsible for implementation and follow-up. Failure, inability, or delay in obtaining the CAC does not relieve the Contractor from performing under the terms of the contract.

3.1.2. The Contractor shall be responsible for notifying the Government when an employee departs, and returning the CAC to the issuing facility or designated representative, i.e., the COR.

3.1.3. In the event of a loss/stolen card, the Contractor shall provide a letter explaining the circumstances surrounded the loss of the CAC. In addition, the Contractor shall obtain documentation, preferably in the form of a memorandum, from the Provost Marshall or the Security Office as proof that the CAC loss was reported.

3.2. Office/work space at MCOE. The Government will provide reasonable working accommodations as needed to support this Task Order. All Government-furnished property shall be provided in accordance with FAR 52.245-1.

3.2.1. Tangible accommodations may include: office space, office supplies, telephone service, workstations, computers, system access, and storage space at the place of performance. The Government property shall be used only in performance of services related to this PWS.

3.2.2. Information specific to a program will be provided as Government Furnished Information (GFI) as needed and as available. Previously work performed may include studies, analyses, JCIDS documents, reports, white papers, or other paper or electronic products.

3.2.3. The Government retains ownership of all property and information furnished to the Contractor as a part of this Task Order. The Government has unlimited rights to all documents and material produced under this requirement. All documents and materials, to include the source codes of any software, produced under this contract shall be Government owned and are the property of the Government with all rights and privileges of ownership and copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the Contractor without written permission from the Contracting Officer. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights under the applicable Data Rights clause(s).

4. PERIOD OF PERFORMANCE: This is a one-year base (to inlcude phase in) and two (2) one-year options.

5. DELIVERABLE PRODUCTS AND SCHEDULE

5.2. Contractor activity report to COR

Weekly

5.3. Contractor Technical Summary (MTS)

Monthly

6. SECTION 508 REQUIREMENTS:

6.1. All electronic and information technology (EIT) procured through this task order must meet the applicable accessibility standards at 36 CFR 1194, unless an agency exception to this requirement exists. 36 CFR 1194 implements Section 508 of the Rehabilitation Act of 1973, as amended, and is viewable at http://www.section508.gov/aCFessible.html- Part 1194." (FAR 39.2).

6.2. The Contractor shall indicate for each line item in the schedule whether each product or service is compliant or noncompliant with the accessibility standards at 36 CFR 1194. Further, the proposal must indicate where full details of compliance can be found (e.g., vendor's website or other exact location).

7. Accounting for Contractor Services:

The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor will report ALL contractor manpower (including subcontractor manpower) required for performance of this contract. The contractor is required to completely fill in all the information in the format using the following web address: https://contractormanpower.army.pentagon.mil. The information to be reported is as follows:

(1) Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative;

(2) Contract number, including task and delivery order number;

(3) Beginning and ending dates covered by reporting period;

(4) Contractor name, address, phone number, e-mail address, identity of contractor employee entering data;

(5) Estimated direct labor hours (including sub-contractors);

(6) Estimated direct labor dollars paid this reporting period (including sub-contractors);

(7) Total payments (including sub-contractors);

(8) Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different);

(9) Estimated data collection cost;

(10)Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information);

(10) Locations where contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardization nomenclature provided on website);

(11) Presence of deployment or contingency contract language; and

(12) Number of contractor and sub-contractor employees deployed in theater this reporting period (by country).

As part of its submission, the contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending 30 September of each government fiscal year and must be reported by 31 October of each calendar year. If contract performance is completed before 30 September, the data can be entered upon contract completion rather than waiting for the end of the fiscal year. Contractors may use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractor’s systems to the secure web site without the need for separate data entries for each required data element at the web site. The specific formats for the XML direct transfer may be downloaded from the web site.*

*For in-theater contracts, requiring activities have the option of requiring more frequent reporting.

Attachment 12, Sample TO 2 1

PAGE

Attachment 12, Sample Task Order 2