PWS.docx

PERFORMANCE WORK STATEMENT (PWS)

2 March 2025 Army Training Models

1.0 Introduction

1.1 Description of Services/Introduction. The Headquarters, Department of the Army (HQDA) Deputy Chief of Staff Operations, Directorate for Training G-3/7, is the functional proponent for Army Training and for strategic resourcing within the framework of the Planning, Programming, Budgeting, and Execution (PPBE) process. The G-3/7 Training Directorate provides oversight and management for the training resource applications developed and supported outside HQDA. The Directorate for Training G-3/7 is the functional proponent for Regionally Aligned Readiness and Modernization Model (ReARMM), Munitions and Collective Training. In this capacity, the G-3/7 Training Directorate provides oversight and management for the training resource applications developed and supported outside HQDA. In this capacity, the G-3/7 has sponsored the development of a suite of software applications to find solutions associated with collective training, operational readiness, and institutional training.

1.2 Background. The training resource applications are collectively referred to as the Army Training Models (ATM). ATM provide analytical support to develop funding requirements for Army-wide collective and individual training and are used to support resource decision making within the PPBE at HQDA and in subordinate commands. This ATM contract supports critical training programs, as well as develops and defend training and operational readiness resource requirements and funding strategies for Army training programs consistent with Army Policies and Priorities in The Army Plan and to meet the timelines of the PPBE process.

1.3 Objectives. The Contractor shall provide subject matter experts with a focus on providing experience and continuity with the planning, programming, budgeting, and execution of the programs that support and resource a wide range of requirements for the Army and its modernization.

The Contractor shall provide technical and programmatic support for the Training Directorate, to include, the Programming & Resources Division (DAMO-TRP) development of Operational Tempo (OPTEMPO), Collective Training, Institutional Training, technical assistance, and subject matter expertise directly supporting the ReARMM, Munitions, Collective Training and Institutional Training divisions in support of the Director of Training and Chief of Staff Army (CSA).

1.4 Scope. The Contractor shall provide support services to various activities to ensure that Army Training requirements are adequately defined, resourced and managed. This effort incorporates requirements from the Director of Training, Army G-3/5/7 for programmatic and analytical support.

1.5 Period of Performance. The period of performance shall be for one (1) Base period of Seven and a half months.

Base period: 7 March 2025 – 22 October 2025

1.6 Quality Control. The Contractor must submit its quality control procedures for contracting officer acceptance with its proposal and maintain a quality program to ensure services are performed in accordance with this contract and established commercial and regulatory standards. The quality control plan must reflect the remedies offered by the contractor for non-performance. Government personnel will monitor the success of the quality program. The Contractor shall effectively retain personnel with the appropriate levels of education, experience and expertise to accomplish the range of tasks described in PART 5, Specific Tasks, in order to reduce the need for the government to expend time/money/effort to retrain and re-orient new contractor personnel.

1.6.1 Quality Assurance. The Government must rely on the Contractor to provide quality service by maintaining an effective quality control program. However, the Contracting Officer’s Representative (COR) will evaluate the Contractor’s performance through various methods of surveillance. Government personnel will record all surveillance observations. When an observation indicates defective performance, the quality assurance personnel will require the contract manager on site to initial address the observation and take corrective action. Government surveillance of tasks not listed in the PWS or by methods other than those listed in the PWS may occur during the performance period of this contract. Additionally, the Government will coordinate any necessary command clearances, approvals, and sponsorship for travel performed under this contract. The primary control mechanism for the work performed under this task order will be the COR. The contractor shall provide the COR with a monthly status report that covers what was accomplished over the last 30 days and work planned for the next 90 days for each employee. The status report is due by the 15th of the month following the month being reported.

1.7 Recognized Holidays. Unless otherwise directed by the customer, the Contractor is not required to work on the following Federal holidays.

Memorial Day Juneteenth Independence Day Labor Day Columbus Day

1.8 Hours of Operation/Place of Performance. Core hours of operation are from 0800 - 1700 Monday through Friday, except federal holidays and non-work hours due to closure or inclement weather. The COR must approve work in excess of eight hours per day or 40 hours per week prior to performance. Work in support of Software Development will be performed at the contractor’s facility. Work in support of Functional Analysis will be performed at the contractor’s facility and the government sites. However, much of the work that will be done on this contact will require considerable interaction (Face-to-Face, Video Teleconference (VTC), Teleconference, and email) with staffs: Army G-3/5/7 (Training Directorate), Army National Guard, the Office of the Chief of Army Reserves, Training and Doctrine Command (TRADOC), Centers of Excellence and other locations as stated in the Technical Exhibit 3. The Contractor must at all times maintain an adequate work force for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the work force are essential. The government will provide workspace, office furniture, computer resources, telephones, offices supplies and tools necessary to perform duties at government locations. The vendor will provide workspace, office furniture, computer resources, telephones, offices supplies and tools necessary to perform duties at the vendor’s location. The contractor shall have access to government regulations and technical manuals. Government furnished items shall not be used for any project other than these tasks.

1.9 Type of Contract. The Government anticipates award of a Firm Fixed Price contract.

1.10 Privacy Requirements. Contractor personnel performing work under this contract may have access to information, which may be subject to the Privacy Act of 1974. The Contractor shall ensure that personnel agree to adhere to the Privacy Act of 1974, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations. All personnel shall hold and maintain a secret level clearance. See attached DD Form 254 (Department of Defense Contract Security Classification Specification).

1.11 Security Requirements

1.11.1 Personnel Clearance. In accordance with (IAW) DD Form 254 Classification Specification: All personnel shall hold or be eligible to receive and maintain a SECRET level clearance. At least one individual on this contract requires a TOP SECRET (TS) level clearance. The user agency will identify classified information and provide specific direction and guidance concerning the safeguarding of such information. The contractor staff shall be required to read and adhere to the appropriate nondisclosure requirements and shall be required to sign appropriate nondisclosure requirements. In addition to a SECRET clearance, one individual assigned to Department of the Army Management Office, Regionally Aligned Army Readiness & Modernization Model (ReARMM) Division (DAMO-TRR) and United States Army Special Operations Command (USASOC) require a top secret clearance, and one requires a TS Sensitive Compartmented Information (SCI) clearance, at each location. Additionally, both individuals supporting USASOC require access to Alternate Compensatory Control Measures (ACCM) / Focal Point information. See attached DD Form 254 (Department of Defense Contractor Security Classification Specification). The contractor staff shall be required to read and adhere to the appropriate nondisclosure requirements and shall be required to sign appropriate nondisclosure requirements. Contractor personnel will be required to complete associated security paperwork and comply with associated policies. Contractor personnel may be required to access data and information proprietary to the Government while performing on this contract. Contractor personnel may also have information of such a nature that its dissemination or use, other than in performance of this contract would be averse to the interest of the Government or others.

The Contractor shall not divulge, or release data or information developed or obtained in performance of this contract except to authorize Government personnel or upon written approval of the (COR). The Contractor shall not use, disclose, or reproduce proprietary data, other than as required in the performance of this contract. The limitations above do not apply to data or information that has been made public by the Government. Further, this provision does not preclude the use of any data independently acquired by the Contractor without such limitations or prohibit an agreement at no cost to the Government between the Contractor and the data owner, which provides for greater rights to the Contractor. All products produced and their associated work papers are to be considered the property of the Government. Contractor will be responsible for completing a DD Form 254.

Contractor shall be responsible for safeguarding all Government property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured.

1.11.2 AT OPSEC Requirements

i. AT Level I training. This standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area. All contractor employees, to include subcontractor employees, requiring access Army installations, facilities and controlled access areas shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The Contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer, if a COR is not assigned, within 30 calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: http://jko.jten.mil

ii. Access and general protection/security policy and procedures. This standard language is for contractor employees with an area of performance within Army controlled installation, facility, or area. Contractor and all associated sub-contractors’ employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

iii. For contractors requiring Common Access Card (CAC). Before CAC issuance, the contractor employee requires a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

iv. For contractors that do not require CAC but require access to a DoD facility or installation. Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

v. iWATCH Training. This standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area. The Contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 45 calendar days after contract award.

vi. Army Training Certification Tracking System (ATCTS) registration for contractor employees who require access to government information systems. All contractor employees with access to a government info system must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services and must successfully complete the DOD Information Assurance Awareness prior to access to the IS and then annually thereafter.

vii. For contracts that require a formal OPSEC program. The Contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer. This plan will include a process to identify critical information, where it is located, who is responsible for it, how to protect it and why it needs to be protected. The contractor shall implement OPSEC measures as ordered by the commander. In addition, the contractor shall have an identified certified Level II OPSEC coordinator per AR 530-1.

viii. For contracts that require OPSEC Training. Per AR 530-1 Operations Security, the contractor employees must complete Level I OPSEC Awareness training. New employees must be trained within 30 calendar days of their reporting for duty and annually thereafter.

ix. For information assurance (IA)/information technology (IT) training. All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of appointment to IA/IT functions.

x. For information assurance (IA)/information technology (IT) certification. Per DoD 8570.01-M, DFARS 252.239.7001 and AR 25-2, the Contractor’s employees supporting IA/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

xi. For contracts that require handling or access to classified information. Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); (2) any revisions to DOD 5220.22-M, notice of which has been furnished to the contractor.

xii. Threat Awareness Reporting Program. For all contractors with security clearances. Per AR 381-12 Threat Awareness and Reporting Program (TARP), contractor employees must receive annual TARP training by a CI agent or other trainer as specified in 2-4b.

xiii. Controlled Unclassified Information (CUI). Include DFARS clause 252.204-7012, which requires the contractor to comply with NIST 800-171. Also include DFARS provision 252.204-2019 into solicitations.

Acquisition officials should follow procedures outlined in DFARS 204.73 and verify vendors have an adequate NIST SP 800-171 summary assessment score within the Supplier Performance Risk System (within PIEE). If the score doesn't show a medium- or high-level assessment with a score of 110 or better (as described in the "NIST SP 800-171 DoD Assessment Methodology"), include clause 252.204-7020 and obtain the vendor's "system security plan" and "plan of action" for NIST SP 800-171 verification and assurance by Army security officials.

1.11.4 Physical Security. The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the COR. Also, contractor personnel assigned to this contract on a full-time or close to full-time basis will be expected to acquire a Pentagon badge for access to the building and must be able to obtain a badge allowing unescorted access.

1.11.4.1 In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the COR, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

1.11.4.2. The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the COR.

1.11.4.3 Lock Combinations. The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s Quality Control Plan.

1.12 Key Personnel; Program Manager: The Contractor shall provide a Program Manager who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the Contractor when the Program Manager is absent shall be designated in writing to the contracting officer and the COR. The Program Manager is considered a key personnel under this contract and must comply with security requirements.

The Program Manager or alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The Program Manager or alternate shall be available between the hours of 0800 to 1700, Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons.

1.13 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. Contractor personnel are required to display distinguishing badges or other visible identification at all times. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that Contractor participation is appropriately disclosed.

1.14 Contractor personnel shall comply with DOD 8570.01.

1.15 Travel. Contractor personnel may be required to travel within CONUS and/or OCONUS to accomplish tasks in this PWS. The COR’s advance concurrence to planned travel is required. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. Local travel shall include destinations within the greater National Capital Region (NCR). Travel may also be required in support of related conferences and forums. All travel requires Government approval/authorization and notification to the COR.

1.16 Transition Plan. The Contractor shall submit a transition plan with its proposal. The transition plan must include a Phase-In plan and a Phase-Out Plan.:

1.16.1 The Phase-In Plan must:

· Demonstrate clearly a reasonable, realistic approach for assuming full contractual responsibility without disruption or degradation of performance during the transition period;

· Identify risk and propose appropriate mitigation strategies;

· Propose a realistic, achievable, and affordable transition schedule and staffing plan; and,

· Ensure sufficient resources are on hand and available to begin work on the effort; and

· Detail an approach to ensure the availability of trained and qualified personnel.

1.16.2 The Phase-Out Plan must:

· enable transition to replacement services and ensures no disruption in service when the existing contract performance period ends.

· provide for phase-in support for up to 45 working days to the selected contractor if the incumbent contractor is not selected herein.

· describe the transfer of knowledge, experience and lessons learned to the new contractor; and,

· Includes a process to appropriately transfer all property, documentation, digital and hard copies of all in-progress working files, historical files, briefings for incoming personnel, timelines and standards for completion.

1.17 Data Rights

The Government’s rights in non-commercial technical data and software deliverables shall be governed by DFARS 252.227-7013 and DFARS 252.227-7014, respectively. The Government's rights in commercial technical data deliverables shall be governed by DFARS 252.227-7015. All technical data (e.g. documents, drawings, computer aided design models, simulation and modeling) and software deliverables shall be properly marked in accordance with the marking requirements set forth in DFARS 252.227-7013(f) and DFARS 252.227-7014(f). Technical data and software deliverables with non-conforming restrictive markings shall be rejected and corrected by the Contractor at the Contractor's expense, in accordance with DFARS 252.227-7013(h)(2) and DFARS 252.227-7014(h)(2) respectively. A current version of the Data Rights Assertion List governing all Prime and sub-Contractors (including sub-contractors from previous Task Orders) shall be included in the Proposal.

Note that no other marking regarding the license rights is allowed in the data deliverables. For example, Notice or Disclaimer to the Third party, Proprietary markings, and any other related statements regarding the rights are strictly prohibited.

The Contractor shall submit the corresponding commercial software license agreements which will be reviewed and approved by the Contracting Officer for the Government. The Contractor shall not submit any commercial software license terms that conflict with federal procurement law or do not satisfy user needs. Commercial Software License terms that are unacceptable to the Government include (but are not limited to) indemnification provisions (and other types of provisions that include unauthorized or unbudgeted funding obligations), attorney's fees provision, state or foreign choice of law/jurisdiction provisions, binding arbitration provisions, and injunctive relief provisions.

In order to assert that the Government will only have limited rights to non-commercial technical data and restricted rights to non-commercial computer software, the Contractor must be prepared to show evidence that (1) all components/parts of the product was developed exclusively with private fund; and (2) the Government is not entitled to Government Purpose Rights or Unlimited Rights IAW DFARS 252.227-7013 or DFARS 252.227-7014.

The Government will have ownership of all non-technical data deliverables (including but not limited to business data, administrative data, management data, and financial data) generated/developed by the contractor under this contract.

The Government has unlimited rights to all documents/material produced under this contract. 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/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.

1.18 Manpower Reporting. The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall 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 required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer’s 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) Actual direct labor hours (including sub-contractors); (6) Actual 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); (11) 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 standardized nomenclature provided on website); (12) Presence of deployment or contingency contract language; and (13) Number of contractor and sub-contractor employees deployed in theater this reporting period (by country). As part of its submission, the Contractor shall 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 September 30 of each Government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct Extensible Markup Language (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.

1.19 Access to Protected Information. If during the performance of this procurement contractor personnel obtain access by any means to protected information, including, but not limited to, trade secrets or proprietary information of other contractors, Government source selection information, Privacy Act information, or any other information with distribution limited by the Government, contractor personnel shall in no way divulge any such information except as it relates to the performance of this procurement within the Army, or shall not otherwise use or disclose this information for their personnel gain, the gain of their employer, or the gain of anyone else. The Contractor shall notify the COR of any potential organizational conflicts of interest created by any such access. However, a nondisclosure agreement will not overcome an Organizational Conflict of Interest (OCI) as defined in FAR part 9.5. Compliance with the Trade Secrets Act requires the consent of the owner of the proprietary information before another non-federal entity may be allowed access to such information. Accordingly, all Government contractors are required to mark their proprietary information and any time the Contractor is given access to such marked information it is incumbent upon the Contractor to inform the COR cor COR of the access. Contractor personnel will ordinarily be required to sign a nondisclosure agreement before starting work under the contract. Failure to comply with this clause shall be deemed adequate cause for the removal of a contractor employee from employment with the Contractor. The Contractor’s employment contracts with their employees shall include a provision to provide for the removal under these conditions.

2.0 ATM: Purpose, Description, and Operating Environment

2.1 Purpose. The overarching objective of the ATM are to provide a common understanding of training resource requirements and funding across the Army by formalizing the HQDA standard methodology for training resource management. The ATM enable HQDA to synchronize training and operational readiness resource management across the Army and ensure that the training management community applies a consistent training resource management methodology. The ATM are used to provide input to internal applications by Forces Command (FORSCOM), TRADOC, and US Army Special Operations Command (USASOC). The ATM also support and receive input from the Army Centers of Excellence (CoEs), Deputy Assistant Secretary of the Army for Cost & Economics (DASA-CE), and HQDA. The Army National Guard and the Office of the Chief, Army Reserve, along with their subordinate commands, use the ATM for decision support analysis and to make recommendations across all phases of Planning, Programming, Budgeting, and Execution.

Due to the broad usage of ATM, the Contractor will frequently interact with these stakeholders, receive data and feedback from them, and (when approved) make improvements to the software applications to support them. Any proposed modifications to the ATM that emanate from stakeholder feedback must be coordinated with the COR in HQDA, Office of the Deputy Chief of Staff, G3/5/7, Training Directorate (DAMO-TR), prior to formal inclusion in the model. The Contractor shall ensure no development work duplicates or is incompatible with other ATM features.

2.2 ATM Descriptions. The ATM consist of an information management system known as the Training Resource Model Information System, and three models: (1) Training Resource Model, (2) Aviation Training Resource Model, and (3) Institutional Training Resource Model, as well a collection of enabling sub-applications.

2.2.1 The Training Resource Model Information System (TRMIS) is the user interface by which stakeholders access information produced by the ATM, planning factors, ATM inputs, and training execution data used to validate the models. TRMIS facilitates information sharing between HQDA and TRADOC and provides the ability to calculate per capita rates. Data displays and calculations are generated based upon user-defined requirements. TRMIS generates ATM reports to support stakeholder analyses required during Budget and Program Development/Execution.

2.2.1.1 The Contractor provides stakeholders with ATM reports and analyses to support the annual development of POM and PBR submission via TRMIS. The Contractor also provides stakeholders with ATM reports to support publication of budget guidance via TRMIS.

2.2.1.2 Additionally, the Contractor converts model data into the proper format to support data reporting to Army and Office of the Secretary of Defense systems, to include Resource Finance Systems (RFS),Cloud Programming Budgeting Execution (cPROBE), and Select and Native Programming (SNaP) Data. Future training resource requirements will be based upon the needs of units to meet the training requirements outlined within Army approved Combined Arms Training Strategies (CATS). The TRMIS serves as a data warehouse of key program data, functions as an Executive Information System (EIS), and, to some extent, functions as a Decision Support System (DSS). TRMIS will provide an intuitive user interface which allows stakeholders at all levels to access data using customizable, ad hoc queries.

2.2.1.3 Typical reports generated through TRMIS include, but are not limited to, the following:

· Training strategy analysis

· Collective Training Analysis

· Historic Cost Factor reports

· Financial/Logistical policy analysis

· Weapon System Review analysis

· Capability Portfolio Review analysis

· Army Working Capital Fund analysis

· Military force structure analysis

· MTOE analysis and change impacts

· Civilian force structure and pricing analysis

· Analysis of supply and equipment cost factors

· Training resource management policies and practices

· Program of Instruction analysis

· Training Resource Integration Initiatives

· CONOPS impact analysis

· Training Resource Business Rule Development/Execution Reporting Policies

· Budget/Program Justification and Analysis

· PPBE support and analysis

· Institutional Training Policies and Analysis

· Analyze and vet new requirements

· Student Travel Analysis

· Individual Training Program Analysis

· Individual Equipment and Clothing Analysis

2.2.2. The Training Resource Model (cTRM) determines the funding resource requirements needed for Army-wide operational units to perform their collective training and operations.

2.2.2.1 The cTRM is designed to meet the following sub-objectives:

· Compute the cost of alternative training strategies and associated training events.

· Articulate the level of training readiness supported by a specified budget by providing a readiness-based benchmark for defining requirements.

· Provide an authoritative, analytical, readiness-based, trainer-driven methodology for determining the OPTEMPO and cost in dollars required to support readiness objectives.

· Provide a uniform methodology for defining training resource requirements from HQDA to the unit/organizational level that is based upon an approved force structure and an approved training strategy.

2.2.2.2 cTRM contains costs for Air and Ground OPTEMPO, civilians supporting unit training, contractor logistics support, and HQDA approved training or operational readiness requirements. These groupings are primarily designed to group resources according to their variability based upon either structure or training activity changes.

2.2.2.3 cTRM has two sub-applications called the Battalion Level Training Model and the Man-Day Resource Model.

2.2.3. The Battalion Level Training Model (BLTM), which is a sub-application of cTRM, is the basic building block for defining activity unique to a type of organization or entity. The BLTM contains multiple sustainment-training strategies that are expressed in terms of the frequency, duration of training events and miles per weapon system required for the training event. BLTM resource requirements are generally measured in terms of equipment operating tempo, or cycle rate (required miles, hours, or rounds). The degree of specificity in the BLTM strategy is directly related to the echelon level of the BLTM.

2.2.3.1 At the Army level, the BLTM strategy is a metric that represents an average of the estimated amount of training activity required for that type of unit to achieve the desired level of training readiness or training objective. Not all units require this level of activity, but on average, the specified level of activity is necessary to provide a reasonable degree of assurance that those type units can meet established training standards.

2.2.3.2 The activity levels contained in the BLTM serve two primary functions in the training resource management process. First, they represent the HQDA assessment of time and activity necessary to meet HQDA established training readiness objectives. Second, they provide a consistent reference point from which units may articulate the need for additional training requirements that exceed the base BLTM strategy metric.

2.2.4 Man-Day Resource Model (cMRM), which is also a sub-application of cTRM, provides for the additional man-days needed over and above the required 39 statutory days provided each year for the Operational Reserve (Compo 2 & 3). Those additional man-days are defined by Training Strategies. Reserve Component (RC) (Compo 2 & 3) training strategies are broken down into 4 or 5 years depending on type of unit (i.e: an ABCT is on a 4-year cycle and IBCT is on a 5-year cycle). Rule of thumb, it takes the RC 5 years what the Active Component does in 1 year due to the constraint of available training days. The cMRM calculates reserve component additional flight training periods required for Readiness Level (RL) progression and sustainment.

2.2.5. The Aviation Training Resource Model (cATRM) provides estimates of funding requirements for Army-wide aviation training and is used to support resource decision making within the Planning, Programming, Budgeting and Execution System (PPBES) at HQDA. The cATRM (previously known as the Flying Hour Management System) supports the HQDA flying hour program manager. Flying hours are arrayed by Army Command (ACOM) and Type-Model-Series for each of the activities that contain flying hour costs. These hours are displayed in either the Program or Execution Module depending upon the point in the PPBE cycle being reviewed.

2.2.5.1 Key inputs for the cATRM include but are not limited to:

· aircraft inventory (both manned and unmanned) by ACOM and Type-Model-Series aircraft

· OPTEMPO for tactical aviation

· total hours for non-tactical requirements

· cost per hour for each Type-Model-Series aircraft.

· parts, fuel, and maintenance needs

· projected number of pilots available to fly the Flying Hour Program

· projected amount of equipment in the units to support the Flying Hour Program

· number of units projected to be deployed

Based upon the above-referenced inputs and considerations concerning pilots per crew ratios, the cATRM computes the dollars required to support the total flying hour program.

2.2.6 The Institutional Training Resource Model (cITRM) provides estimates of funding requirements for Army-wide individual training and is used to support resource decision making within the PPBES at HQDA. cITRM produces estimates at course level of detail broken out into a variety of categories (such as by type of training, by performing organization, and by budget account) with multiple levels of aggregation within each category. The cITRM process has three applications that support cost factor analysis, military/civilian work-year data, training products, workload vs. manpower analysis, and POI integration into the resource requirement generation process. These software tools are the Per Capita Model, the Training and Doctrine Development Management System (TD2), and the Course Level Training Model (CLTM).

2.2.6.1 cITRM uses Program of Instruction (POI) Based Pricing to capture the critical tasks, Terminal Learning Objectives, and standards established by the branch proponents for each course. POI-based pricing under cITRM allows the Army to directly establish the training requirements and generate a consistent resource package of ammunition, equipment, facilities, instructors, military and civilian personnel, training aids and devices, cost factors, and dollars needed to support the institutional training base. It includes expanding the cITRM resource package to include more finite estimates of civilian pay, non-OPTEMPO equipment, contracts, training developments, distance learning initiatives, and individual training readiness while meeting the objectives of the Total Army School System (TASS). As POIs are developed or revised, especially those that incorporate distance learning, revised workload drivers must be developed and integrated into cITRM.

2.2.6.2 The Contractor will modify the TRMIS software to generate weighted average per capita factors developed off of the latest FY with the per capita factors developed off of the two and three previous FYs. Weighting will be based on each year’s respective workload (i.e., student load, civilian and military manpower).

2.2.6.3 The components of cITRM are:

· Detailed data organized by institutional training course.

· Information Management and Decision Support Software.

· OPTEMPO Tracking and Analysis.

· SII database to ensure accurate identification of SIIs and the courses they support.

· Per Capita Validation Software

2.2.7 The Course Level Training Module (CLTM) is a sub-application of cITRM that documents POI data;

2.2.8 Resource Prioritization Database (1-n) is a sub-application of cITRM that functions as a resource module for the management of Operations and Maintenance, Army (OMA), and Reserve Personnel, Army (RPA) requirements; and,

2.2.9 Monthly Army Performance Review (MAPR) is a sub-application of cITRM, which provides Official Army equipment air and ground mileage and hourly execution.

2.3 Extension of these applications and methodologies to subordinate commands provides a consistent, credible methodology for calculating and presenting training resource requirements. These utilities support cost factor processing, force structure processing, modernization plans, and other key input data sources.

2.4 Operating Environment.

2.4.1 The operating environment that this ATM contract supports is complex and dynamic. Analysis supported under this contract is time-sensitive and may require rapid adjustments based upon changing user inputs or output needs. The Army continually adapts to meet changing conditions. To remain relevant, the ATM must adapt accordingly. Sources of change may include, but are not limited to, changes to force structure (both operational and generating force), training strategies, authorized equipment, deployment strategies, and cost factors.

2.4.2 Doctrinal shifts changing the size, composition, stationing, and readiness standards of Army units, coupled with deployment of integrated, virtual training simulations will continue to dictate changes to the training resource requirements. The software must be capable of supporting revision to training strategies such as ReARMM or any other emerging Army strategy. Changes to Army budget data elements such as Management Decision Execution Package (MDEP), Army Management Structure Code (AMSCO), Dollar Type, Object Classes, and training readiness definitions will require the ATM to adapt accordingly. This will require the Contractor to adapt these software programs and models to changing Army data structures and environments

2.4.3 Reports will continue to evolve to meet changing needs for data to articulate training resource requirements to agencies outside the Department of the Army, within the Army Staff, and to disseminate guidance to subordinate Army Commands. These revisions will cause the Army to reassess the outputs of the ATM to ensure they are responsive to Senior Leader needs.

2.4.4 As a result, the Contractor must have expertise in training resource requirements development, training, force management, logistics and financial policy and systems analysis as well as fluency in the development of appropriate software tools to facilitate data analysis and training resource management. These skills are necessary to anticipate, conceptualize, and implement changes to the ATM rapidly and effectively.

3.0 Tasks

3.1 This PWS covers the full spectrum of software support and maintenance within the full suite of ATM, and establishes the baseline for any major software modifications, as well as full spectrum of analysis and support required to support HQDA G3 and DAMO-TR. The Contractor shall provide technical and programmatic support for the Training Directorate. Support includes but is not limited to program management, technical assistance, and subject matter expertise directly supporting the ReARMM, Munitions and Collective Training in support of the Chief of Staff, Army (CSA), as well as Operational Analysis for the G3-5/7 Training Directorate. The Contractor shall furnish the necessary personnel, functional support, software, materials, facilities and other services as may be required to perform the work contained in this PWS.

3.1.1 Tasks performed on this contract generally fall within one of five categories. These categories are (1) Software maintenance, (2) Software development, (3) Training, (4) Custom Analysis (5) Staff Support.

3.2 Software Maintenance. The Contractor will maintain all software necessary to accomplish the objectives of this contract. Software maintenance includes routine enhancements to existing applications.

As technology advances, the Contractor will migrate the software applications as directed by the COR. The Contractor is responsible for maintaining DoD/Army Risk Management Framework (RMF) and ensuring that all delivered application or modifications to software complies with RMF requirements; and also documenting all ATM models and utilities for end users.

3.3 Software Support. In addition to existing applications, other applications are emerging to capture information, introduce new technologies, and to better disseminate and share sensitive Operational Tempo (OPTEMPO) resource decisions. Though they perform many different functions, these ATM applications are structured to operate within a common technical architecture where software code is a shared resource among multiple applications.

Shared code is efficient by design; the successful Contractor must ensure that this approach is also effective in meeting the needs of the diverse client community supported by this project.

A key feature of this requirement’s definition process is the establishment of a linkage between the force structure contained in the cTRM and the force being supported within the cITRM. This linkage is critical to ensuring that all training resource requirements are based upon common force structure decisions. Outputs of the cITRM include a projection of anticipated student workload based upon a given force structure and the costs associated with the courses anticipated to be required to support that force.

3.3.1 Development Objectives: Per Contract Data Requirements List (CDRL) A002, consistent with available time and resources, the COR will prioritize development projects which may include the following:

· Continue any work associated with migration to the cloud. (as required by the government)

· Linking ATM reports to Program Optimization and Budget Evaluation (c-PROBE) to load change packages directly from TRMIS.

· Automating the reconciliation process

· Developing a user interface to resolve “Z-lines” collaboratively between HQDA and other stakeholders

· Developing a user interface to conduct cut drills and excursions (either funding based, or end strength based)

· Developing and updating as appropriate an application that tracks OPTEMPO and other training or operational readiness resources.

· Developing a user interface which allows the comparison of two non-sequential ATM positions.

· Developing a capability to produce POM and budget reports, and produce historical program reports across 15 or more years for Army Senior Leaders (ASL), HQDA, and Army Materiel Command (AMC), Assistant Secretary of the Army (Acquisition, Logistics, & Technology (ASA (ALT)), and others

· Developing a user interface which allows users at all levels to drill down into the drivers and factors underpinning specific data.