Army HR Intelligent Engagement Platform Industry Q_A 11 AUG 2025.xlsx
XLSX spreadsheet 43 KB Posted
- Attached to
- Army HR Intelligent Engagement Platform
- Solicitation number
- W519TC25R2HRP
About this file
This document is a comprehensive Questions and Answers (Q&A) spreadsheet for the Army HR Intelligent Engagement Platform, a pre-solicitation opportunity seeking innovative solutions to modernize the Army's HR service delivery. The solicitation aims to develop an intelligent engagement platform that provides a unified, secure interface for accessing HR systems, with the goal of improving service delivery, reducing costs, and enhancing user experience for Soldiers and civilian personnel. Key technical requirements include integrating with authoritative systems like IPPS-A, ATIS, and Vantage, implementing single sign-on capabilities, supporting 1.1 million users, and achieving IL5+ security compliance.
The procurement will occur in multiple phases, with the current Phase 1 Solution Brief submission deadline extended to 15 August 2025. Vendors are expected to propose solutions that leverage AI, large language models, and advanced integration techniques, with a focus on automating Tier 0 (self-service) HR interactions. The platform must support various user personas including Soldiers, HR professionals, and commanders, and provide capabilities such as workflow automation, knowledge base management, and seamless system integrations. Evaluation criteria will emphasize technical merit, innovation, security compliance, and the solution's potential to transform HR service delivery across the Army enterprise.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| No. | Solicitation Reference | Comment/Question | Government Response |
| 1 | CFS, Section 2, Problem Statement | How are IPPS-A and other HR systems providing Tier 0 support today? | IPPS-A and other HR systems currently provide Tier 0 support through fragmented self-service portals and manual processes, which lack integration and unified access. This results in inefficiencies and delays in service delivery. |
| 2 | SOO, Section 5.0 Solution Objectives | Can the Government please provide an example Permanent Change of Station (PCS) flow for the priority use cases? | PCS flows typically involve initiating orders, updating records, and coordinating logistics. The proposed solution should streamline these processes by automating workflows and integrating authoritative systems like IPPS-A and Vantage. |
| 3 | General | What foundational large language models (LLMs) does IPPS-A have access to today? | The Government does not currently utilize foundational LLMs within IPPS-A. Vendors are encouraged to propose solutions leveraging commercially available or proprietary LLMs that meet security and compliance requirements. |
| 4 | SOO, Section 5.0 Solution Objectives | Is there a requirement to pursue a separate PIA/SORN for the proposed solution? | The Government will follow appropriate regulatory policies. Vendors must ensure all data is protected and adheres to PII utilization standards. |
| 5 | SOO, Section 5.0 Solution Objectives | Is there an existing API deployment mechanism in place that should be used? | Existing API mechanisms vary by system. Vendors should propose solutions that integrate seamlessly with current systems using open APIs or other approved protocols. |
| 6 | SOO, Section 5.0 Solution Objectives | How many different user personas will need to access the proposed solution? Can the Government please provide the personas and definitions? | User personas include Soldiers, HR Professionals, Commanders, and Civilians. Each persona will have tailored access and functionality based on their roles. |
| 7 | SOO, Section 5.0 Solution Objectives | Are attribute-based access controls (ABAC) required? | Vendor shall implement robust security measures to protect sensitive data and enable secure user authentication and role awareness. |
| 8 | CFS, Section 3, High-level Solution/Concept | Items B and D of the Solution Concepts appear to be duplicative. Will the Government please update the Call for Solutions document to remove the duplication or clarify what is desired? | 3.b and 3.d were duplicatives and in the amended CFS 3 D. has been removed. Vendors should address both general innovated and specific technological innovations in their solutions. |
| 9 | 3. Desired Solution Objective | Do all of the Authoritative Data Systems that would require integration into the future state solution have API capability? Are there any systems requiring integration that lack open APIs or direct integration capability? | Most authoritative systems have API capabilities, but some may require custom connectors or data feeds. Vendors should work to ensure solution is interoperable to the maximum extent possible vendor should also account for potential integration challenges. |
| 10 | 3. Desired Solution Objective | Is there an existing IDP that should be leveraged for SSO? Should RBAC groups be managed through that IDP or within the provided solution? | Existing Army identity management systems (e.g., CAC integration, DS LOGON) should be leveraged for SSO. RBAC groups should align with these systems. |
| 11 | 3. Desired Solution Objective | Will the system be required to store and manage the knowledge base documents? | Yes, the system should store and manage knowledge base documents securely, ensuring accessibility and compliance. |
| 12 | 3. Desired Solution Objective | Is there a need for mobile offline capabilities? | Mobile offline capabilities are not explicitly required but may be beneficial for certain use cases. Vendors will not be discouraged from proposing innovative solutions. |
| 13 | 3. Desired Solution Objective | Is there an estimated number and complexity of workflows that are expected to be automated? | The initial phase will focus on 5–10 high-impact workflows, such as PCS processing and benefits elections. Complexity will vary based on the use case. |
| 14 | Reference Section 7.2.g | What is meant by the last bullet “Gate Criteria” in the Company Description section? | Gate Criteria has been removed. Solution Briefs will be judged against the evaluation factors outlined in 10 and the response to the SOO for the solutions. The offeror may also submit a cover page, 1 page company information, and table of contents that will not count towards the 5 page limit. |
| 15 | Reference—Section 3, first bullet | Are there MOUs or other related paperwork in place that allow us to immediately connect the AI to these systems (IPPS-A, Army Service Center, ATIS, Vantage, etc.)? | MOUs and agreements for system integration are in place for existing systems. Vendors will need to coordinate with the Government to ensure compliance and access. |
| 16 | CFS Section 7 - Solution Submission Requirements | Graphics containing 12pt font are cumbersome and provide little room for quality information. Will the government consider adjusting the definition of “Readable” to include a 9pt font minimum for tables and graphics? | The Government will allow smaller font sizes for tables and graphics, provided they remain legible and accessible. To be evaluated the vendor shall comply with identified font size as stated. |
| 17 | CFS Section 7.3 - High Level Solution/Concept | Will the government please confirm that offerors need only to cover 3.a, 3.b, and 3.c to satisfy the submission requirements in their High Level Solution/Concept submission? | 3.b and 3.d were duplicatives and in the amended CFS 3 D. has been removed. |
| 18 | General | Does the Army have any preference of AI / ML platforms? Can we recommend a platform leveraging Oracle’s relevant SKUs? | The Goverment will not restrict innovation vendors may recommend platforms, including Oracle, provided they meet security and compliance requirements. |
| 19 | General | Does the Army use CTI / IVR telephony integrations for case management? | The Army does not currently use CTI/IVR telephony integrations for HR case management. Vendors may propose solutions that include these capabilities. |
| 20 | General | Is there any component of Business Process redesign in this initiative, that is expected to be fulfilled by the SI? | Yes, business process redesign is expected to align with the implementation of the HR Intelligent Engagement Platform. Vendors should address this in their proposals. |
| 21 | General | Can you please provide some volumetric ranges for Calls, Emails and Cases / month? | The Government does not have specific volumetric ranges available at this time. Vendors should propose scalable solutions to accommodate high volumes of interactions. |
| 22 | Section 7 Solution Submission Requirements | I do not understand what “To Gate Criteria” means in reference to items a and b. | Gate Criteria has been removed. Solution Briefs will be judged against the evaluation factors outlined in 10 and the response to the SOO for the solutions. |
| 23 | Item 2 | Item 2 mentions Gate Criteria. It is unclear what content we are supposed to provide. Are we to respond to each of the items below? | Gate Criteria has been removed. Section 10 provides a list of items that the Government will be specifically evaluating within the submitted solution briefs. The Phase 1 solution brief cannot exceed 5 pages. The Offeror may also submit a cover page, 1 page of company information, and a table of contents.The cover page, company information, and table of contents will not count toward the 5 page solution. |
| 24 | Item 2 | Are all of the below Gate Criteria items expected to be included in the 2 Pages before the 5-Page High-level Solution/Concept? | Gate Criteria has been removed. Section 10 provides a list of items that the Government will be specifically evaluating within the submitted solution briefs. Note, the submitted solution briefs should cover at a minimum these topics within the 5 pages. It is imperative that Contractors address the all areas within the SOO to express how industry intends to solve the HR problem provided. |
| 25 | CFS | Can you elaborate on the specific authoritative data systems and HR applications that must be integrated at launch and in future phases? | Authoritative systems include IPPS-A, Army Service Center, ATIS, and Vantage. Future integrations may include additional HR systems as identified during implementation. |
| 26 | CFS | Are there preferred integration standards or protocols beyond open APIs (e.g., SCIM, SAML, REST, SOAP)? | Preferred protocols include REST, SOAP, and SAML. Vendors should propose solutions that align with these standards and ensure interoperability. |
| 27 | CFS | Is there an existing enterprise content management system (ECM) or document repository in use across Army HR today? | The Army uses various ECMs and repositories. Vendors should propose solutions that integrate with or migrate from these platforms as needed. |
| 28 | CFS | How does the Army envision managing unstructured HR content (e.g., forms, supporting documents, policy memos) within the engagement platform? | The platform should provide secure, centralized storage and collaboration capabilities for unstructured HR content. |
| 29 | CFS | What platform is currently being used to host the HR knowledge base? | The Army does not have a centralized HR knowledge base platform. Vendors should propose solutions to create or integrate one. |
| 30 | CFS | Are there any workflow tools currently leveraged in the HR process flows today and if so, what are they? | Workflow tools vary by system. Vendors should propose solutions that integrate with existing tools or introduce new ones. |
| 31 | CFS | Does the Army have a preference for commercial off-the-shelf (COTS) conversational AI engines versus custom/NLP models trained on Army-specific data? | The Army is open to both COTS and custom solutions, provided they meet security, scalability, and compliance requirements. The solution shall favor COTS products. However, the goverment will not limit innovation and vendor shall provide the best solution to address the call for solutions. |
| 32 | CFS | Will the Government share evaluation rubrics or weighting for technical merit, innovation, past performance, and other criteria? | Evaluation rubrics and weighting will not be shared. Vendors should address all criteria outlined in the solicitation. |
| 33 | CFS | Is there flexibility in the demonstration/prototype phases to showcase differentiated capabilities not explicitly listed in the SOO? | Yes, vendors may showcase additional capabilities during the demonstration/prototype phases, provided they align with the overall objectives. |
| 34 | General | Will preference be given to modular architectures that allow discrete capabilities to be iteratively improved or replaced without vendor lock-in? | Yes, modular architectures that promote flexibility and avoid vendor lock-in are preferred. |
| 35 | General | Should the solution architecture support open standards (e.g., OpenAPI, MCP, A2A) to ensure future extensibility and integration with emerging platforms? | Yes, the solution architecture should support open standards to ensure extensibility and interoperability. |
| 36 | General | Does the government have a preference for solutions that avoid proprietary data structures or codebases that limit government ownership and sustainment? | Yes, solutions that avoid proprietary limitations and promote long-term government ownership are preferred. |
| 37 | General | Does the government expect the platform to natively support Section 508 compliance from initial deployment, or can that be remediated post-award? | Section 508 compliance is expected from initial deployment. Vendors should ensure accessibility standards are met. |
| 38 | CFS | How many HR transactional systems are in use today? Are there different versions or instances of HR systems? | The Army uses multiple HR systems, including IPPS-A, ATIS, and Vantage. Versions and instances vary by system. |
| 39 | CFS | IPPS-A is built using the Oracle Peoplesoft HR suite — what version are they at today? | IPPS-A is currently using Oracle PeopleSoft version 9.2. |
| 40 | CFS | Is the current IPPS-A environment hosted in Oracle cloud or in AWS/Azure? | IPPS-A is hosted in a secure, Army-authorized environment. Specific cloud providers are not disclosed. |
| 41 | CFS | Is IPPS-A currently leveraging Oracle’s ODA/PICASO for process automation and chatbot? | No, IPPS-A is not currently leveraging Oracle’s ODA/PICASO. Vendors may propose solutions that include these capabilities. |
| 42 | CFS | Is there an Army IDAM/ICAM solution that we will need to tap into for SSO and CAC Card access? | Yes, vendors must integrate with existing Army IDAM/ICAM solutions for SSO and CAC access. |
| 43 | CFS | Does Army HR have a Data Governance program that has already established enterprise-wide data management, ontology, taxonomy, master data management, data quality management, metadata management in place? | The Army has a Data Governance program in place. Vendors should align their solutions with existing frameworks. |
| 44 | CFS | Are there other critical datasets for the prototype in addition to IPPS-A? If so, what are they and where do they reside? | Additional datasets may include ATIS, Vantage, and Army Service Center data. Locations vary by system. |
| 45 | CFS | Will the USG clarify what information is required within the 2-page limitation for Company Information, specifically for (g): Gate Criteria? | The references and requirement for "gate criteria" have been removed from the call. Solution briefs will be evaluated against the evaluation criteria listed in section 10. The phase 1 solution brief cannot exceed 5 pages. The offeror may also submit a cover page, 1 page of company information, and a table of contents. The cover page, company information, and table of contents will not count toward the 5 page solution brief limit. |
| 46 | General | Can you share details on your current HCM system of record? | The Army’s current HCM system of record is IPPS-A, which integrates personnel and pay functions. |
| 47 | General | Is there a current or planned enterprise identity provider that should be used for SSO (e.g., Army ICAM, Azure AD, Ping)? | Vendors should integrate with the Army’s existing ICAM solution for SSO and CAC authentication. |
| 48 | General | Can the Government confirm the hosting and networking requirements (e.g., NIPRNet, GovCloud IL5) for development and deployment environments? | Hosting and networking must comply with IL5 requirements and operate within Army-authorized environments such as NIPRNet or GovCloud. |
| 49 | General | Does the Government anticipate integration with any existing chatbot frameworks, or should the vendor propose a net-new conversational AI solution? | Vendors may propose net-new conversational AI solutions or integrate with existing frameworks, provided they meet the requirements outlined in the SOO. |
| 50 | General | Is natural language understanding (NLU) for military terminology and acronyms expected to be pre-trained or developed as part of this engagement? | NLU for military terminology and acronyms should be developed as part of this engagement, leveraging Army-specific data. |
| 51 | General | Will the Army provide authoritative HR knowledge bases (e.g., policies, MILPER/ALARACTs) to pre-load into the virtual assistant during development? | Yes, the Army will provide authoritative HR knowledge to be interoperaable with the solution provided. The vendor shall not isolate solution or innovations based only focused on a virtual assistance. |
| 52 | General | Can you clarify which user roles/personas will be in-scope for tailored experiences at launch (e.g., Soldiers, HR professionals, Commanders, Civilians)? | User roles include Soldiers, HR Professionals, Commanders, and Civilians, with tailored experiences based on their roles. |
| 53 | General | Is there an existing Army governance body for digital HR platforms that this solution must align with (e.g., architecture, accessibility, user testing)? | Yes, the solution must align with the Army’s governance body for digital HR platforms, including architecture and accessibility standards. |
| 54 | General | What level of user feedback or usability testing is expected during development phases (e.g., Soldier focus groups, HR SMEs)? | Periodic user testing with Soldiers and HR professionals is expected during development to validate and refine the solution. |
| 55 | General | Is there a baseline dataset for Tier 0 HR service metrics (e.g., volume of common questions, call center usage) that vendors can use to project ROI? | The Army does not currently have a baseline dataset for Tier 0 HR service metrics. Vendors should propose methods to capture and analyze these metrics. |
| 56 | Section 5.5 Concurrent users | Does the 1.1 million user count refer to total licensed users or anticipated concurrent users? | The 1.1 million user count refers to total licensed users across the Army enterprise. |
| 57 | Section 5.0 Integrations | Are there specific APIs or existing integration standards for IPPS-A, ATIS, Vantage, and Army Service Center that bidders should be aware of? | Vendors should leverage open APIs and integration standards such as REST and SOAP for these systems. Specific documentation will be provided during later phases. |
| 58 | Section 7 | Does the government have a target award date for phase 2 or final? | The Government anticipates notifying selected vendors for Phase 2 shortly after the Phase 1 submission deadline. It is conditions based. |
| 59 | General | Can the Government clarify the minimum security and compliance requirements for platform(s) involved in the proposed solution (e.g., DoD Impact Level or FedRAMP baseline, CMMC requirements, etc.)? | Platforms must meet IL5 requirements, comply with DoD RMF standards, and adhere to FedRAMP High or equivalent baselines. |
| 60 | General | Will the prototypes (Phases 3 and 4) require operation within an environment that already possesses an ATO, and will Government-furnished environments be provided, or must offerors provision their own compliant environments? | Prototypes must operate within environments that possess an ATO. Government-furnished environments may be provided, but vendors should be prepared to provision compliant environments if necessary. |
| 61 | General | Is it permissible to leverage existing commercial or DoD cloud environments for Phase 3/4 prototyping, or must all capabilities be instantiated in a Government-provided, isolated, or new environment? | Vendors may leverage existing commercial or DoD cloud environments, provided they meet IL5 requirements and are approved by the Government. |
| 62 | General | Will integration points with IPPS-A and other HR systems be available during prototyping, or will simulated/mock interfaces be required for earlier phases? | Simulated/mock interfaces may be required during earlier phases. Integration points will be made available during later phases. |
| 63 | General | Are there any restrictions or required standards for Single Sign-On (SSO) integration (e.g., specific identity providers or protocols required/approved by Army PEO Enterprise)? | Vendors must integrate with Army-approved identity providers and protocols, such as CAC and DS LOGON. |
| 64 | General | Given the technical complexity of the solution space, would the Government consider extending the Phase 1 Solution Brief page limit to allow for more detailed narratives, architectural diagrams, or risk/mitigation discussions? | The Government will not extend the page limit for Phase 1 Solution Briefs. Vendors should provide concise and impactful responses within the existing limit. |
| 65 | General | In the event that responses to questions or amendments are issued close to the submission deadline, will the Government consider extending the submission deadline to allow all offerors sufficient time for adjustment? | The Government is extending the submission deadline to 15 AUG 2025. |
| 66 | General | Are there any technical, security, or operational criteria that will be weighted more heavily than others in Phase 1? If so, can the Government clarify their relative importance? | Technical merit, security compliance, and innovation will be weighted heavily in Phase 1 evaluations. Vendors should address all criteria comprehensively. |
| 67 | General | Will the Government require any specific rights or access to proprietary or commercial software/IP as part of the prototype demonstration, or can solutions be delivered as a service with appropriate access controls? | Solutions may be delivered as a service with appropriate access controls. Vendors must disclose any proprietary IP and associated restrictions. |
| 68 | General | Can the Government provide estimates or ranges for expected user concurrency, transaction volume, and/or peak load to guide performance and scalability planning for the intelligent engagement platform prototype? | The platform should support up to 1.1 million users, with scalability to handle high transaction volumes and peak loads. Specific metrics will be provided during later phases. |
| 69 | General | What measures will be in place to ensure the protection of offerors’ proprietary information given the involvement of non-Government advisors in the evaluation process? | Non-Government advisors will adhere to strict confidentiality agreements to protect proprietary information. |
| 70 | General | Is the Government solution and platform agnostic for this requirement, or are there any pre-existing preferences, constraints, or limitations on the technology stack, cloud provider, or software approach that offerors should be aware of? | The Government is solution-agnostic but requires compliance with IL5 standards and integration with existing Army systems. Vendors should avoid proprietary limitations. |
| 71 | General | Could you clarify whether an enterprise AI/data strategy and governance framework already exists or whether the selected vendor is expected to help develop one as part of this effort? | The Army has an existing data governance framework. Vendors may propose enhancements or align their solutions with the framework. |
| 72 | Call for Solutions, Page 4 | Are bidders permitted to use smaller than size 12 font for tables and graphics? | Yes, smaller font sizes (minimum 9pt) are permitted for tables and graphics, provided they remain legible. |
| 73 | Call for Solutions, Page 5 | Can the government please rewrite a-d to eliminate redundancies in what the government has requested? | Gate Criteria has been removed. Solution Briefs will be judged against the evaluation factors outlined in 10 and the response to the SOO for the solutions. The phase 1 solution brief cannot exceed 5 pages. The offeror may also submit a cover page, 1 page company information, and table of contents that will not count toward the 5 page solution brief limit. |
| 74 | Call for Solutions, Page 5 | Is the government's intention for bidders to respond to a-d (linking that to the SOO), as well as the additional requirements introduced in the Evaluation Criteria? | 3.b and 3.d were duplicatives and in the amended CFS 3 D. has been removed. Bidders should respond to a-c and address the additional requirements in the Evaluation Criteria, ensuring alignment with the SOO. |
| 75 | Call for Solutions, Page 5 | Can the government please confirm the gate criteria? There is not a clear distinction in the documents that have been provided what the gate criteria is. | The references and requirement for "gate criteria" have been removed from the call. Solution briefs will be evaluated against the evaluation criteria listed in section 10. The phase 1 solution brief cannot exceed 5 pages. The offeror may also submit a cover page, 1 page of company information, and a table of contents. The cover page, company information, and table of contents will not count toward the 5 page solution brief limit. |
| 76 | Call for Solutions, Page 1 | Would the government please provide an extension to August 19, 2025, to allow bidders time to incorporate answers to questions into their response? | The Government is extending the submission deadline to 15 AUG 2025. |
| 77 | Call for Solutions, Page 6 | In section 10, the government refers to this as a closed call." Please clarify the difference between an open call and closed call." | A closed call" refers to a solicitation limited to specific requirements and timelines |
| 78 | General | What enterprise HR system(s) are in place that this solution will be asked to integrate with? | Enterprise HR systems include IPPS-A, Army Service Center, ATIS, and Vantage. Additional systems may be identified during implementation. |
| 79 | Call for Solutions, Page 6 | In section 10, evaluation criteria, the government states four bullets for evaluation, but doesn’t provide any distinction on what defines these four bullets. For example, technical merit, how is the government determining? | Technical merit will be evaluated based on relevance to the problem statement, innovation, scalability, and compliance with the SOO. |
| 80 | Call for Solutions, Page 6 | In section 10, evaluation criteria, the government states that records of solution …" Is the government seeking offerors' past performance in implementing the proposed solution?" | Yes, the Government seeks evidence of past performance in implementing similar solutions in commercial or Government environments. |
| 81 | Call for Solutions, Page 6 | In section 10, evaluation criteria, the government states the offerors qualification …" | what are the preferred qualifications |
| 82 | Company information | Please clarify the page limitations for Company Information versus Specific Company Information. | shall not exceed two (2) pages. Company information for submissions shall include the Program/Project Name" (pg. 4)" |
| 83 | Company information | Part (g) of the Specific Company Information covers the Gate Criteria. Is this in the two (2) page limit or part of the excluded information that does not count towards any page limit? | The references and requirement for "gate criteria" have been removed from the call. Solution briefs will be evaluated against the evaluation criteria listed in section 10. The phase 1 solution brief cannot exceed 5 pages. The offeror may also submit a cover page, 1 page of company information, and a table of contents. The cover page, company information, and table of contents will not count toward the 5 page solution brief limit. |
| 84 | High-level Solution/Concept (5 Page Limit)" (pg. 5)" | We respectfully request increasing the Solution Brief to ten (10) pages for a more comprehensive solution description. | The Government will not increase the page limit for the Solution Brief. Vendors should provide concise and impactful responses within the 5-page limit. It should be noted that the cover page, company information, graphics, and table of contents will not count toward the 5 page solution brief limit. |
| 85 | SOO | Are there preferences for the Army HR Intelligent Engagement platform to support specific LLMs (e.g., open-source vs. proprietary)? | The Army is open to both open-source and proprietary LLMs, provided they meet security, scalability, and compliance requirements. |
| 86 | SOO | What is the scope of Army-authorized environments" mentioned in section 3.0?" | Army-authorized environments" refer to secure hosting environments that comply with IL5 requirements and are approved by the Army for operational use." |
| 87 | Success Criteria | Does the Government have defined goals or success metrics for this initiative? (e.g., HR time saved, employee experience improvements, call deflection rates, case volume reduction) | Success metrics include HR time saved, improved employee experience, increased call deflection rates, and reduced case volumes. Vendors should propose methods to measure and achieve these goals. |
| 88 | HR System Landscape | Can the Government provide additional context about the existing HR technology landscape (IPPS-A, Army Service Center, ATIS, Vantage), specifically: What platforms or technology are these systems built on? Which systems currently integrate with each other? | IPPS-A is built on Oracle PeopleSoft, while other systems use varied platforms. Integration capabilities vary, and vendors should propose solutions that enhance interoperability. |
| 89 | Knowledge Base | Does Army HR have a centralized knowledge base? If so: What technology is it built on? Is it accessible to both employees and HR professionals? | The Army does not currently have a centralized HR knowledge base. Vendors should propose solutions to create or integrate one. |
| 90 | Governance | Is there a central governing body that will help coordinate this initiative across different HR systems, particularly those with separate owners? | Yes, the Army’s governance body will coordinate this initiative to ensure alignment across HR systems and stakeholders. |
| 91 | Conversational AI Capabilities | Are there any conversational AI or chatbot capabilities already in use within Army HR today? | The Army does not currently use conversational AI or chatbot capabilities for HR. Vendors may propose solutions to introduce these capabilities. |
| 92 | User Satisfaction Tracking | How does the Army currently capture: User satisfaction with existing HR technologies? Overall employee satisfaction with HR services? | User satisfaction is captured through surveys and feedback mechanisms. Vendors should propose methods to enhance satisfaction tracking. |
| 93 | Preferred Technologies | Are there any commercial platforms, frameworks, or tools the Government prefers vendors to consider or avoid? | The Government is platform-agnostic but prefers solutions that align with existing systems and DoD standards. Vendors should avoid proprietary limitations. |
| 94 | Hosting Environment | Does the Army have a preferred IL5-compliant cloud environment? | The Army does not specify a preferred IL5-compliant cloud provider. Vendors may propose solutions using AWS, Azure, or other approved providers. |
| 95 | ATO Responsibility | Will the contractor be responsible for obtaining an ATO, or will this solution operate under an existing enclave or ATO? | Contractors may need to obtain an ATO for their solution unless it operates under an existing Army-authorized enclave. |
| 96 | Analytics Integration | Does Army HR have an existing analytics platform this solution should integrate with? | The Army uses various analytics platforms. Vendors should propose solutions that integrate with or enhance these platforms. |
| 97 | User Research | Will vendors have access to Soldiers, civilian employees, and/or HR personnel to conduct user interviews and usability testing? | Yes, vendors will have access to Soldiers, civilian employees, and HR personnel for user interviews and usability testing during development phases. |
| 98 | Priority Use Cases | Have the 5–10 high-impact use cases been selected for the initial launch phase? If so, can the Government share them? | High-impact use cases include PCS processing, benefits elections, and NCOER/OER timelines. Additional use cases may be identified during implementation. |
| 99 | Test Environments | Will the Government provide access to test environments for existing HR systems and test data to support development and demonstration? | Yes, the Government will provide access to test environments and data during development and demonstration phases. |
| 100 | Call For Solutions, Page 2, Section 3, first bullet | Is integration into Army E-ICAM a requirement for SSO? | Yes, integration into Army E-ICAM is required for SSO. Vendors must ensure compatibility with this system. |
| 101 | SOO, page 2, Section 4, third bullet | Does IL5+ include FISCAM/FISMA control overlays? | Yes, IL5+ environments must comply with FISCAM/FISMA control overlays and other DoD cybersecurity standards. |
| 102 | SOO, Page 3, Section 4, data systems | Can the Gov't provide information on the location of the authoritative data systems? On Premises? In which CSP? | Authoritative data systems are hosted in secure, Army-authorized environments. Specific CSPs are not disclosed. |
| 103 | SOO, Page 3, Section 4, data systems | Will the Gov't consider private cloud environments for hosting? | Yes, private cloud environments may be considered, provided they meet IL5 requirements and are approved by the Government. |
| 104 | SOO, Page 3, Section 4, Security Measures | Will the program support work with Army E-ICAM on IGA integration for roles? | Yes, the program will support integration with Army E-ICAM for role-based access control (RBAC) and identity governance. |
| 105 | SOO, Page 3, Section 4 Security Measures | Is Army E-ICAM PAM integration required? | Yes, integration with Army E-ICAM for Privileged Access Management (PAM) is required to ensure secure access control. |
| 106 | CFS | What types of artifacts or documentation does the government expect to see regarding a certification" of meeting the requirements of the SOO?" | Vendors should provide documentation such as compliance certifications, technical specifications, and evidence of prior successful implementations that align with the SOO requirements. |
| 107 | CFS | What types of artifacts or documentation does the government expect to see regarding records of the solution integrated in the commercial and/or Government marketplace"?" | Vendors should provide case studies, references, or performance metrics demonstrating successful integration of their solution in commercial or Government environments. |
| 108 | CFS | Can you confirm user roles, for example are general users envisioned to develop their own agents or will this be more of an administrative function? | Developing agents will primarily be an administrative function. General users will interact with pre-configured agents tailored to their roles. |
| 109 | CFS | We understand the overall impact level requirement is IL5. Will there be the opportunity to develop/prototype on the low side and move code up-domain? | Yes, vendors may develop and prototype on lower domains initially, provided the solution is capable of transitioning to IL5 environments. |
| 110 | CFS | Is the Army open to a hybrid deployment model where certain public-facing functions (e.g., general HR FAQs) can reside in IL2/IL4 environments, while sensitive HR workflows remain in IL5 zones? | Yes, the Army is open to hybrid deployment models, provided sensitive workflows remain in IL5-compliant environments. |
| 111 | CFS | Can you provide more detail on the authoritative HR systems and APIs (e.g., IPPS-A, ATIS, Vantage) we will be expected to integrate with at launch? Are API specs or credentials available? | Vendors will be expected to integrate with IPPS-A, ATIS, Vantage, and other systems. API specifications and credentials will be provided during later phases. |
| 112 | CFS 5.0 Solicitation Notes Pg. 3 | Please clarify what constitutes “reference-viable commercial ability” and the specific types of evidence or documentation preferred to demonstrate this. | “Reference-viable commercial ability” refers to solutions that have been successfully deployed in commercial or Government environments. Evidence may include case studies, performance metrics, and customer references. |
| 113 | CFS 5.0 Solicitation Notes Pg. 3 | Please provide guidance on the preferred format or level of detail for identifying intellectual property and any associated restrictions within the 5-page Solution Brief. | Vendors should clearly identify intellectual property, including patents, trademarks, or proprietary algorithms, and specify any restrictions on Government use. This can be included as a separate section within the Solution Brief. |
| 114 | CFS 5.0 Solicitation Notes Pg. 3 | If the Government exercises its right to go directly from Solution Brief to award, what additional information (e.g., pricing, detailed schedule) would be required from the selected offeror beyond the Phase 1 Solution Brief? | Additional information may include detailed pricing, implementation schedules, and technical documentation to support contract negotiations. |
| 115 | CFS 9. Organizational Conflict of Interest (OCI) Pg. 6 | Is there a template or specific format preferred by the Government for the OCI analysis and any associated mitigation plan? | The Government does not provide a specific template. Vendors should submit a detailed analysis and mitigation plan consistent with FAR 9.5 and industry best practices. |
| 116 | CFS 10. Evaluation Criteria Pg. 7 | What is the anticipated timeframe for notification regarding selection for Phase 2 (Pitch or Proposal) after the Phase 1 Solution Brief submission deadline of August 12, 2025? | Notifications for Phase 2 selection are anticipated within 2–3 weeks after the Phase 1 submission deadline. |
| 117 | SOO 3.0 Scope / Mission / 5.0 Solution Objectives Pg. 3 | What are the specific authoritative data systems beyond IPPS-A, Army Service Center, ATIS, and Vantage that are considered critical for integration at launch or within the initial 12-month period? | The initial focus will be on IPPS-A, Army Service Center, ATIS, and Vantage. Additional systems may be identified during implementation based on mission needs. |
| 118 | SOO 5.0 Solution Objectives Pg. 4 | Please define the specific performance metrics or Service Level Agreements (SLA) expected for the AI engagement layer regarding response times, uptime, and concurrent user support for 1.1 million users. | Performance metrics include 99.9% uptime, sub-second response times for queries, and scalability to support 1.1 million users concurrently. Vendors should propose SLAs aligned with these metrics. |
| 119 | SOO 5.0 Solution Objectives Pg. 4 | Beyond the examples provided, does the Army have a prioritized list of the top 5–10 high-impact use cases it wishes to support at launch, or will the offeror propose these based on analysis? | Vendors may propose high-impact use cases based on their analysis, but examples include PCS processing, benefits elections, and NCOER/OER timelines. |
| 120 | SOO 4.0 Delivery Schedule Pg. 4 | Given the ambitious 12-month timeline for all four phases (Solution Brief, Demonstration, Phase 3 Prototype, Phase 4 Prototype), can the Government provide a more detailed estimated timeline for each phase’s duration and expected start/end dates? | Phase 1 (Solution Brief): 1 month; Phase 2 (Demonstration): 2 months; Phase 3 (Prototype): 4 months; Phase 4 (Final Prototype): 5 months. Adjustments may be made based on progress. |
| 121 | SOO 4.0 Delivery Schedule / 5.0 Solution Objectives Pg. 4 | Please clarify if “IL5+” refers to Impact Level 5 or higher. Please specify the Army-authorized IL5+ cloud environments that must be used for hosting. | “IL5+” refers to Impact Level 5 or higher. Vendors may propose solutions hosted in Army-authorized environments such as AWS GovCloud or Azure Government. |
| 122 | SOO 5.0 Solution Objectives Pg. 5 | What is the preferred commercial cloud provider (e.g., AWS, Azure, GCP) for the IL5 environment, or is the choice left to the offeror? | The choice of cloud provider is left to the offeror, provided the environment meets IL5 requirements and is Army-authorized. |
| 123 | SOO 5.0 Solution Objectives Pg. 5 | Please provide the specific technical documentation available for the existing Army identity management systems (CAC integration, DS LOGON) to facilitate integration planning. | Technical documentation for CAC integration and DS LOGON will be provided during later phases to selected vendors. solutions will be favored which are in compliance and interoperaable with current authentication/authorization solutions approved by the goverment. |
| 124 | SOO 5.0 Solution Objectives Pg. 6 | What level of detail is expected for the sustainability and transition plan in Phase 1? What are the Army’s expectations regarding the transfer of intellectual property rights or software licenses for long-term ownership? | Vendors should provide a high-level sustainability and transition plan in Phase 1, including licensing terms and intellectual property transfer options for long-term Army ownership. |
| 125 | General | Can the Army confirm that a cover letter does not count as part of the 5-page limit? | Yes, a cover letter does not count toward the 5-page limit for the Solution Brief. |
| 126 | CFS Page 5 | Can the Army specify whether Gate Criteria is the same as Section 10 Evaluation Criteria, and if so, how should we respond to the following request? | Gate Criteria has been removed. Solution Briefs will be judged against the evaluation factors outlined in 10 and the response to the SOO for the solutions. |
| 127 | Question 2 | Is it safe to assume that as long as our response covers each gate criteria throughout the response we are good to go? Or do you need a dedicated section of multiple bullets for each criteria? | Gate Criteria has been removed. Solution Briefs will be judged against the evaluation factors outlined in 10 and the response to the SOO for the solutions. |
| 128 | CFS | Did the government intend to include a different fourth gate criteria for Phase 1 Solution Briefs? Section 3b and 3d seem very similar with 3b asking about innovative advancement" and 3d asking about "innovative technological advancements." Is there supposed to be a different 3d?" | 3.b and 3.d were duplicatives and in the amended CFS 3 D. has been removed and Gate Criteria has been removed. Solution Briefs will be judged against the evaluation factors outlined in 10 and the response to the SOO for the solutions. The phase 1 solution brief cannot exceed 5 pages. The offeror may also submit a cover page, 1 page company information, and table of contents that will not count toward the 5 page solution brief limit. |
| 129 | CFS | If 3b and 3d are correct, how does the government differentiate between innovative advancement" and "innovative technological advancements"?" | 3.b and 3.d were duplicatives and in the amended CFS 3 D. has been removed and Gate Criteria has been removed. Solution Briefs will be judged against the evaluation factors outlined in 10 and the response to the SOO for the solutions. The phase 1 solution brief cannot exceed 5 pages. The offeror may also submit a cover page, 1 page company information, and table of contents that will not count toward the 5 page solution brief limit. |
| 130 | Technical Integration & Data Access | Which HR systems (e.g., IPPS-A, Army Service Center, ATIS, Vantage, iPERMS, etc.) must be integrated and operational at initial launch, and which are considered future integrations? | Initial integrations include IPPS-A, Army Service Center, ATIS, and Vantage. Future integrations may include iPERMS and other systems as identified during implementation. |
| 131 | Technical Integration & Data Access | Will the Government provide technical documentation (APIs, data schemas, test environments) for required system integrations and support for onboarding? | Yes, technical documentation and test environments will be provided during later phases to support system integrations. |
| 132 | Technical Integration & Data Access | Are there data residency/location requirements for any integrated systems or for the platform itself beyond IL5 hosting? | Data residency must comply with IL5 requirements and reside within Army-authorized environments. Vendors should ensure compliance with DoD standards. |
| 133 | Use Cases, Content, and User Experience | Will the Government provide a prioritized list of the 5–10 “high-impact” use cases to be supported at launch, or should offerors propose this based on their domain expertise? | Vendors may propose high-impact use cases based on their expertise, but examples include PCS processing, benefits elections, and NCOER/OER timelines. |
| 134 | Use Cases, Content, and User Experience | Are there requirements or preferences for supported user personas (Soldier, HR Pro, Commander, Family Member, etc.), languages, or accessibility standards beyond Section 508? | Supported personas include Soldiers, HR Professionals, Commanders, and Civilians. Accessibility standards must comply with Section 508, and additional language support may be proposed. |
| 135 | Use Cases, Content, and User Experience | Will the Government provide existing Army HR knowledge base content for ingestion, or is content development/curation expected as part of the proposal? | The Government will provide existing HR knowledge base content for ingestion. Vendors may also propose content development/curation to enhance the knowledge base. |
| 136 | Security, Compliance, and Access | What is the expected timeline and process for obtaining Authorization to Operate (ATO) and meeting cybersecurity requirements (DoD RMF, PII handling, etc.)? | Vendors should plan to obtain ATO within the prototype phases. Compliance with DoD RMF and PII handling standards must be demonstrated during development. |
| 137 | Security, Compliance, and Access | Are there specific Army identity management systems for SSO/CAC/DS Logon integration that should be supported from Day 1? | Yes, vendors must integrate with Army identity management systems such as CAC and DS Logon from Day 1. |
| 138 | Security, Compliance, and Access | Will the Government provide access to existing identity management or role mapping data for user context and tailored experiences? | Yes, the Government will provide access to identity management and role mapping data to support tailored user experiences. |
| 139 | Analytics, Feedback, and Reporting | What are the Government’s expectations for usage analytics, reporting cadence, and format? | Vendors should provide real-time usage analytics dashboards and periodic reports (e.g., monthly or quarterly) in formats compatible with Army systems. |
| 140 | Analytics, Feedback, and Reporting | Will benchmarks or baseline call/task volumes be provided for measuring call deflection and ROI? | The Government does not currently have benchmarks or baseline data. Vendors should propose methods to capture and analyze these metrics. |
| 141 | Evaluation & Selection Process | Will feedback be provided to non-selected offerors after Phase 1 or subsequent phases? | Yes, feedback will be provided to non-selected offerors after Phase 1 and subsequent phases to improve future submissions. |
| 142 | Evaluation & Selection Process | Can the Government clarify the format and scope of the technical challenge for Phase 2 (e.g., live demo, scenario-based, scripted use cases)? | The technical challenge for Phase 2 will include a live demo and scenario-based use cases. Detailed instructions will be provided to selected vendors. |
| 143 | Intellectual Property & Data Rights | What are the Government’s expectations regarding intellectual property, open source, and Government Purpose Rights for solutions and data generated under this program? | The Government expects vendors to grant Government Purpose Rights for solutions and data generated under this program. Open-source solutions are encouraged where feasible. |
| 144 | Intellectual Property & Data Rights | When and how should offerors disclose any proprietary IP included in the proposed solution? | Proprietary IP should be disclosed in the Solution Brief, including restrictions on Government use. Vendors may include this information as a separate section. |
| 145 | Organizational Conflict of Interest (OCI) | Is there a preferred template or format for the OCI analysis submission? | The Government does not provide a specific template. Vendors should submit a detailed OCI analysis consistent with FAR 9.5 and industry best practices. |
| 146 | Process & Administration | Will the identity of question submitters be anonymized when Q&A responses are published on SAM.gov? | Yes, the identity of question submitters will be anonymized when Q&A responses are published on SAM.gov. |
| 147 | Process & Administration | Are additional Q&A sessions anticipated beyond the 5 August 2025 deadline for questions? | No additional Q&A sessions are anticipated beyond the 5 August 2025 deadline. Vendors should submit all questions by this date. |
| 148 | Statement of Objectives - 2.0 Background | The Statement of Objectives mentions that Soldiers and civilian personnel are the users of the HR Engagement Platform. Are these two groups the entire user base or could there be others (e.g., contractors or reservists)? | The primary user base includes Soldiers (Active/Guard/Reserve) and civilian personnel. Additional users, such as contractors and reservists, may be included based on mission needs. |
| 149 | SOO - 3.0 Scope/Mission | The Statement of Objectives mentions integrations and interfaces with existing data and HR processes (other systems) and section 5.0 lists IPPS-A, ATIS, and Vantage as such systems. Are there any other likely systems industry should consider when estimating scope of integration work? | Vendors should focus on IPPS-A, ATIS, Vantage, and the Army Service Center for initial integration. Additional systems may be identified during implementation. |
| 150 | SOO Pg. 8 – 4.0 Delivery Schedule | The Statement of Objectives refers to an agile delivery schedule in 4 phases. Do agile phases begin with submission phases 3 and 4 (the prototypes)? Or do the agile delivery phases begin after prototype selection? | Agile delivery phases begin after prototype selection and will focus on iterative development and refinement of the solution. |
| 151 | CFS - #7 Pg. 4 | What is the anticipated budget for the Prototype Phase? | The Government has not disclosed the budget for the Prototype Phase. Vendors should propose cost-effective solutions aligned with the scope and objectives. |
| 152 | CFS - #7 Pg. 4 | What is the intention for the Government to bypass a specific phase? | The Government may bypass specific phases if a solution demonstrates readiness for direct implementation or award. |
| 153 | CFS - #7 Pg. 4 | Will there be two separate budgets for the two Prototype Phases? | Budget allocations for the two Prototype Phases will be determined based on the scope and complexity of each phase. Vendors should propose detailed cost estimates. |
| 154 | CFS - #2 Pg. 5 | The Instructions and Evaluation Criteria mentions Gate Criteria" on multiple instances for both administrative company information and the technical components. Can the Government explain what they are looking for when answering Phase 1 Solutions Brief | Gate Criteria has been removed. Solution Briefs will be judged against the evaluation factors outlined in 10 and the response to the SOO for the solutions |
| 155 | #1 & #3 Pg. 4 & 5 | Does the Government have a maximum page limit of 5 pages total or 7? (2 for questions 1-2, and 5 for question 3)? | The phase 1 solution brief cannot exceed 5 pages. The offeror may also submit a cover page, graphics, 1 page company information, and table of contents that will not count toward the 5 page solution. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .