Call for Solutions - Enterprise_25-01.pdf
PDF 276 KB Posted
- Attached to
- ARMY OPEN SOLICITATION (AOS) Federal contract opportunity
- Solicitation number
- W9128Z-25-S-A002
About this file
This document is a Call for Solution for the Army Training Management Capability (ATMC) project, issued by the Program Executive Office (PEO) Enterprise Army Training Information System (ATIS). The solicitation seeks innovative software solutions to address current Army training management challenges, including the lack of integrated, automated tools that burden company-level leaders and impact unit readiness. The prototype solution must provide collaborative training planning tools, training records management, data analysis capabilities, integration with existing software, identity and access management, and data migration services.
Key submission details include a solution brief due date of Friday, 16 May 2025 at 1200E, to be submitted to specific email addresses. The solicitation may result in a prototype Other Transaction (OT) award under 10 U.S.C. § 4022 and is not subject to Federal Acquisition Regulations. Evaluation criteria include feasibility, viability, desirability, technical merit, schedule, and price. Solution briefs must be no longer than four pages, with three pages of technical discussion and one page detailing the rough order of magnitude pricing for 40,000 annual users. The government reserves the right to award multiple contracts or make no award, with potential for a follow-on production contract without further competitive procedures.
View the file
Other files for this federal contract opportunity
Show all 24
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Call for Solution for Army Training Management Capability (ATMC)
Project Number ENTERPRISE_25-01 Open Solicitation Number
W9128Z-25-S-A002
Call for Solution Title Army Training Management Capability (ATMC)
Issued By Program Executive Office (PEO) Enterprise Army Training Information System (ATIS)
Submission Instructions
To respond to this Call for Solution, please refer to Sections 5 and 8 of this Call for Solution.
*Solution Briefs Due Date/Time (Suspense) Friday, 16 May 2025 at 1200E
Submit Solution Brief To Agreements Officer: leslie.m.dickson2.civ@army.mil Specialist: lindsey.j.arguello.civ@army.mil
Note: Please advise the cognizant Agreements Officer and Specialist as soon as possible via the email above if your organization intends to submit a Solution Brief to ATIS in response to this Call for Solution.
*Any submissions that are received by the Agreements Officer after the suspense date/time listed above will be deemed late and not evaluated. It is the sole responsibility of the company to ensure that its submission is received in the inbox listed above before the deadline specified.
This Call for Solution may result in the Government awarding a prototype OT in accordance with 10 U.S.C. § 4022. This Call for Solution, and any OT awarded from this Call for Solution, is not subject to the Federal Acquisition Regulations (FAR) or its supplements.
mailto:leslie.m.dickson2.civ@army.mil mailto:lindsey.j.arguello.civ@army.mil
1. BACKGROUND
ATIS will give time back to Soldiers and leaders via easy-to-use tools that leverage authoritative data while operationalizing training management processes described in Field Manual 7-0, Army Regulation 350-1, and TRADOC Regulation 350-70. ATIS will help the Army plan, prepare, execute, and assess training across the operational, institutional and self-development training domains for all COMPOs including Army Civilian Professionals. The ATIS effort is aligned to Army data goals and will provide authoritative data to the Army to support readiness reporting, TRADOC resourcing models, talent management and other key enterprise data goals.
2. PROBLEM STATEMENT
Current Army training management suffers from a lack of integrated, automated tools, creating significant burdens for company-level leaders and impacting unit readiness. Specifically, existing systems lack interoperability for both top-down guidance and bottom-up planning, resulting in unsynchronized scheduling and calendars across formations. This is compounded by the absence of a modern, automated method for assessing Mission Essential Task List (METL) proficiency, cross-walking those assessments to required tasks, and assigning tasks to personnel – a process currently reliant on manual effort that detracts from valuable training and leadership time and potentially leads to readiness gaps.
3. DESIRED SOLUTION ATTRIBUTES
A fully functional prototype must include the following unique or innovative capabilities, functions, and/or features:
a. Training Scheduling. The application shall provide collaborative training planning tools, with automated review/approval workflows, shareable training calendars with selectable data overlays for deconfliction or comparative analysis, and training schedule (T-week) production to assist commanders and leaders with training prioritization, planning, and preparation. Calendars and scheduling tools will provide visibility of available training resources; especially ranges, training areas, facilities and Training Aids, Devices, Simulators and Simulations (TADSS). Planning tools will allow commanders and subordinate leaders to identify and prioritize tasks to train based on training guidance and proponent approved training products. The planning tools will allow users to view doctrinal products and provide automation identifying specific events to create unit training calendars and schedules. The system will automate the production and viewing of training materials for company-level meetings and briefings, offering multiple viewing options based on planning horizons, echelons, unit adjacencies, and resource prioritization.
b. Training Records Management. The application shall provide a capability to record training outcomes in unit and individual training records including weapons qualifications, mission essential task (MET) assessments, task evaluations, Army Fitness Test (AFT) and body composition outcomes, completion of common mandatory training requirements, and other training topics, such as airborne jump logs and driver/operator training. The system shall facilitate conduct, storage and recall of after-action reviews (AAR) to include attachment of images and handwritten notes from evaluators. The application will allow users to manage unit quantities and types of weapons, then record qualification scores and outcomes. Task evaluations will reflect the overall “go/no-go” or
“Trained /Practiced/Untrained” (TPU) outcomes. The AFT and body composition data recording provides automated calculation using policy-based business rules.
c. Data Analysis. The application shall provide dashboards and reports focused on battalion-level and below training, while exporting data to external data analytic platforms for higher echelons. The dashboards will provide commanders, staff, and subordinate leaders with relevant information to monitor and assess training proficiency; view summary and aggregate training data with visualization tools that vary by echelon to inform training plans and talent management decisions; and facilitate basic analytic capabilities like predictive, trend, and comparative analysis capability. Leaders may drill down to view lower echelon and individual data, while also viewing peer or higher echelon dashboards.
The application will generate reports in varied, exportable formats to support external analysis or standard, recurring, and custom reporting requirements.
d. Integration with existing software. The application shall integrate with the Army Training Information System (ATIS) architecture which interfaces with multiple information systems and authoritative databases. The Army’s unified data reference architecture (UDRA) outlines data mesh principles to flatten and simplify the Army’s data architecture and streamline data product sharing across information systems to enable data-driven decision making at greater speed and scale.
e. Identity, Credential, and Access Management (ICAM). The solution must implement ICAM, to include authentication, authorization, and auditing capabilities, to ensure secure access to DoD resources. The solution must integrate with existing DoD identity management systems and provide user activity monitoring and regular access reviews to enhance security.
f. Data Migration from Legacy Systems. The solution must provide services to migrate data from legacy systems to the new, existing cloud-based infrastructure. The data migration must ensure data integrity and minimize downtime, and include a comprehensive migration plan, with data mapping, validation, testing, and rollback procedures to ensure a smooth transition.
In all cases, the appropriate safeguards must be in place to protect information to include guidelines and policies outlined in Appendix A.
4. AWARDING INSTRUMENT
This Call for Solution solicitation will be awarded in accordance with the Open Solicitation procedures detailed within Solicitation W9128Z-25-S-A002. The Open Solicitation outlines the guidelines for submitting Solution Briefs, pitches, and proposals and how the Government will evaluate responses to this Call for Solution.
5. SOLICITATION NOTES
In addition to the general guidelines included in the Open Solicitation, the following guidelines apply to this Call for Solution.
• The Government will give preference to submissions that demonstrate an innovative, existing, and reference-verifiable commercial ability to accomplish the desired solution attributes listed above.
• If the Government does not receive any Solution Briefs that demonstrate an innovative, existing, and reference-verifiable commercial ability to accomplish the desired solution attributes, preference will be given to submissions demonstrating existing and recent products that can be adapted for the solicited purpose with the least amount of non-recurrent-engineering effort.
• Resellers and academic research proposals are not desired.
• The period of performance / schedule for any Solution Brief or proposal submitted under this Call for Solution should generally be no greater than six (6) months.
• Submitted Solution Briefs shall be no longer than four (4) pages.
• The Solution Brief must identify any intellectual property involved in the effort and associated restrictions on the Government’s use of that intellectual property.
• The Government reserves the right to go directly from Solution Brief to award.
• The Government reserves the right to award more than one (1) award resulting from this
Call for Solution or to make no award.
6. NON-GOVERNMENT ADVISORS
As identified in Section I of the Open Solicitation, non-Government advisors may be used in the evaluation of Solution Briefs, Pitches, and during proposal development and negotiation. For this Call for Solution, the Government anticipates using non-Government advisors from the following contractors:
• LMI Consulting, LLC
• The MITRE Corporation
7. FOLLOW-ON PRODUCTION
Companies are advised that any prototype Other Transaction (OT) agreement awarded in response to this Call for Solution may result in the award of a follow-on production contract or transaction without the use of further competitive procedures. The follow-on production contract or transaction will be available for use by one or more organizations in the Department of Defense and, as a result, the magnitude of the follow-on production contract or agreement could be significantly larger than that of the prototype OT. ATIS requests a production Rough Order of Magnitude (ROM). As such, any prototype OT will include the following statement relative to the potential for follow-on production: "In accordance with 10 U.S.C. 4022(f), and upon a determination that the prototype project for this transaction has been successfully completed, this competitively awarded prototype OT may result in the award of a follow-on production contract or transaction without the use of competitive procedures.
8. EVALUATION CRITERIA
Solution Briefs and pitches will be evaluated based on the following evaluation criteria:
a. Feasibility – solution to problem statement is technically possible. This criterion measures whether the technology exists or is likely to be developed in the scope of this prototype effort.
b. Viability – solution to problem statement is compatible with DoD constraints, technical environments and other organizational requirements. This criterion measures whether DoD could easily adopt the prototype.
c. Desirability – solution is responsive to a problem statement. This criterion measures whether end users are likely to adopt the offeror’s prototype solution. An example of something which is not desirable is a SW solution that is not intuitive/easy to use and requires extensive training for use/operations.
d. Technical Merit: The Government will evaluate the Company’s Offeror’s proposed solution/concept relevance to the respective Topic; innovation or a potential capability;
solves a capability/gap/problem or provides potential innovative technological advancements; capabilities and scalability of the solution; benefits of the solution/concept;
and technical approach.
e. Schedule. The Government will evaluate the proposed solution/concept project schedule and maturity path.
f. Price. The Government will evaluate the proposed rough order of magnitude (ROM), to include the estimated out-the-door total cost/price.
Solution Briefs shall conform to the following. Should offerors submit anything longer, the Government will only evaluate the first four pages of a Solution Brief.
• Three (3) pages of technical discussion explicitly addressing the target problem statement and how the proposed solution meets the evaluation criteria.
• One (1) page ROM which includes the estimated out-the-door total price for 40,000 annual users.
The Government estimates that it will require two (2) weeks or less to review and respond to Solution Briefs. At that time, the Government will inform the offeror that:
a. The Government has not selected to move forward with the submitted Solution Brief;
b. The Government requests that the offeror participate in an in-person (or virtual) pitch; or
c. The Government will issue a Request for Prototype Proposal (RPP)
After pitches, the Government shall further down-select potential awardees and issue a request for prototype proposal (“RPP”) to the remaining candidate firm(s). The RPP will have specific guidelines. Chiefly, offerors must submit a statement of work and a detailed price breakdown as it relates to payment milestones. The Government shall use the same criteria to evaluate prototype proposals as described for Solution Briefs.
APPENDIX A: STANDARDS, REFERENCES & POLICIES
1) FIPS PUB 199 - Standards for Security Categorization of Federal Information and Information Systems - February 2004.
2) DoD Instruction 8510.01 DoD Risk Management Framework (RMF) for DoD Information Technology (IT)
3) NIST SP 800-30 Guide for Conducting Risk Assessments
4) NIST SP 800-37 Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy
5) NIST SP 800-39 Managing Information Security Risk: Organization, Mission, and Information System View
6) NIST SP 800-53 Security and Privacy Controls for Information Systems and Organizations
7) DoDI 5000.75, Business Systems Requirements and Acquisition, dated, 2 February 2017, with change 1, dated, 31 August 2018
8) DoDI 5000.87 Operation of the Software Development Pathway, dated, 2 October 2020
APPENDIX B: LIST OF ACRONYMS
AFT Army Fitness Test ATIS Army Training Information System ATMC Army Training Management Capability FFRDC Federally Funded Research and Development Center ICAM Identity Credential and Access Management MET Mission Essential Task OT Other Transaction PEO Program Executive Office RMF Risk Management Framework ROM Rough Order of Magnitude SETA Systems Engineering and Technical Assistance TADSS Training Aids, Devices, Simulators and Simulations TPU Trained, Proficient, Unsatisfactory TRADOC Training and Doctrine Command UDRA Unified Data Reference Architecture
| 1. BACKGROUND |
| 2. PROBLEM STATEMENT |
| 3. DESIRED SOLUTION ATTRIBUTES |
| 4. AWARDING INSTRUMENT |
| 5. SOLICITATION NOTES |
| 6. NON-GOVERNMENT ADVISORS |
| 7. FOLLOW-ON PRODUCTION |
| 8. EVALUATION CRITERIA |
| APPENDIX A: STANDARDS, REFERENCES & POLICIES |
| APPENDIX B: LIST OF ACRONYMS |
File details come from the government source that posted it. Updated .