AIE Functional RTM.xlsx
XLSX spreadsheet 651 KB Posted
- Attached to
- DRAFT REQUEST FOR PROPOSAL (RFP) - ARMY ACCESSIONS INFORMATION ENVIROMENT (AIE) Federal contract opportunity
- Solicitation number
- Not on record
About this file
This document is a draft Request for Proposal (RFP) for the Army Accessions Information Environment (AIE), released by the Army Contracting Command - Aberdeen Proving Grounds on behalf of the Program Executive Office Enterprise Information Systems (PEO EIS).
The RFP seeks to continue the development and expansion of AIE capabilities, which is currently leveraging the Salesforce IL 4 platform. The Government is requesting industry feedback on the technical approach, Agile performance metrics, incentives for innovation, CDRLs, and other areas requiring clarity. The anticipated contract award ceiling is $267 million over 10 years, with a 5-year base period and five 1-year option periods. The procurement will utilize a best value trade-off source selection approach under FAR 15.101-1 and 15.3. The RFP is anticipated to be posted to SAM.gov in late June 2024 with proposals due in late July 2024. The North American Industry Classification System (NAICS) code for this requirement is 541512.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| AIE Draft RFP Questions - Government Response.xlsx | XLSX spreadsheet | |
| AIE Draft RFP Questions Submission Form 05062024.xlsx | XLSX spreadsheet | |
| AIE CDRLs.zip | ZIP file | |
| AIE - Cost Price Sheet Task Order 1.xlsx | XLSX spreadsheet | |
| AIE L - M.pdf | ||
| AIE QASP Task Order 1.pdf | ||
| AIE Overview.pptx | PPTX presentation | |
| AIE PWS IDIQ Multiple Award.pdf | ||
| AIE Draft RFP Questions Submission Form.xlsx | XLSX spreadsheet | |
| AIE PWS Task Order 1.pdf | ||
| AIE Section G.pdf | ||
| AIE Section H.pdf |
Show all 12
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
Overview
| LEGEND | TABLE METRICS | |||||
| Item | Note | Metric | New Capability | Intiative | Epic | Feature |
| Green Items | Editable | # of Blanks | 0 | 0 | 0 | 0 |
| Blue of Grey Items | Do NOT Edit (These are Formulas or Pivot Tables) | # of TBDs | 0 | 0 | 0 | 0 |
| How to edit Pivot Tables | Make changes on green table on Table sheet and Refresh All the Data | # of Unique Items | 9 | 55 | 5 | 70 |
| How to Data Refresh | Data Tab > Refresh All |
Requirements Per Capability
Total CRM Foundation Intelligence Marketing Processing Sustain and Support Training and Leader Dev On-Boarding (Manage Reception Processing) UNAVAILABLE 106 162 68 20 194 27 101 85 14
Admin
ADMIN PAGE TO DRIVE METRICS ON THE WORKBOOK ELSEWHERE
Requirements Per Capability Pie Chart On Overview
| Capabilities | Count of Requirement |
| CRM | 106 |
| Foundation | 162 |
| Intelligence | 68 |
| Marketing | 20 |
| Processing | 194 |
| Sustain and Support | 27 |
| Training and Leader Dev | 101 |
| On-Boarding (Manage Reception Processing) | 85 |
| UNAVAILABLE | 14 |
Table
| KPP, KSA, APA | Old Reqt # | New Reqt # | Requirement | Capability | Intiative | Epic | Feature | SOR | Notes |
| 2.3 | 1.1 | The system shall provide the capability for live collaborative modification to records based on role. | Foundation | User Managment | Enlisted | User Management | |||
| KSA | 12.2 | 1.10 | The system shall provide the capability to interface with systems in accordance with the OV-3: Operational Resource Flow Matrix and Information Exchange Requirements. | Foundation | Integration | Enlisted | Integration | ||
| 1.0 | 1.11 | The system shall provide a multi-tenant environment from which continuous upgrades are issued based on best business practices or changes in law, policy, regulations, directives (LPRD). | Foundation | Technical/Non-Functional | Enlisted | Technical/Non-functional | |||
| 16.0 | 1.2 | The system shall provide the capability to perform document management. | Foundation | Technical/Non-Functional | Enlisted | Document Management | |||
| 3.21 | 1.4 | The system shall provide a single authoritative record for future applicants and current workforce that ensures data accuracy and data availability at a level that meets or exceed industry standards (e.g., 99,9% level of accuracy). | Foundation | Core Data | Enlisted | Core Data | |||
| 11.0 | 1.5 | The system shall provide the capability to perform data analytics. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 6.0 | 1.6 | The system shall enable a Common Operating Picture capability. | Foundation | Workspaces | Enlisted | Workspaces | Workspaces | ||
| 23.5 | 1.7 | The system shall provide a consistent user experience across all platforms commensurate with platform specifications, taking in to consideration a mobile-first design approach. | Foundation | Mobile | Enlisted | Mobile | |||
| 15.1 | 1.9 | The system shall provide the capability to create and maintain a command-approved content library to support planning and conduct of marketing activities and interviews. | Foundation | Content Library | Enlisted | UNAVAILABLE | |||
| 3.2 | 2.1 | The system shall provide the capability to perform near-real time leads creation, scoring, routing, assignment, tracking, and distribution. | CRM | Record Lifecycle Management | Enlisted | Lead Generation | |||
| 15.0 | 2.3 | The system shall provide the capability to implement a Digital Interview Platform. | CRM | Interviewing | Enlisted | Interviewing | |||
| 2.0 | 2.6 | The system shall provide the capability to perform record management. | CRM | Record Lifecycle Management | Enlisted | Record Lifecycle Management | |||
| 18.0 | 3.0 | The system shall provide the capability to digitally assemble pre-defined Accessions Packets for all defined Accessions Paths informed by the authoritative policy. | Processing | UNAVAILABLE | Enlisted | UNAVAILABLE | |||
| 18.1 | 3.1 | The system shall provide the capability to electronically complete the Accessions Packet. | Processing | Opportunity Management | Enlisted | UNAVAILABLE | |||
| 22.4 | 3.10 | The system shall provide the capability access and display cadet progress. | Processing | UNAVAILABLE | Enlisted | UNAVAILABLE | ROTC | ||
| 11.6 | 3.2 | The system shall provide the capability to create user-defined and configurable workflows (see Business Process Workflow definition). | Processing | Workflows | Enlisted | Workflows | |||
| 18.2 | 3.3 | The system shall provide the capability to distribute the completed Accessions Packet to the designated SORs. | Processing | Processing Integration | Enlisted | UNAVAILABLE | iPERMS/IPPS-A | ||
| New Requirement | 11.27 | 3.8 | The system shall provide the capability to perform processing automation in support of program business processes to reduce user workload. | Processing | RPA | Enlisted | UNAVAILABLE | ||
| NEW | 4.0 | The system shall allow for users to conduct on-boarding actions in accordance with current/developing LRPD. (NEW) | On-Boarding (Manage Reception Processing) | UNAVAILABLE | Enlisted | UNAVAILABLE | |||
| NEW | 4.1 | The system shall provide projected arrivals reports out to 18 months or in accordance with current LPRD. (NEW) | On-Boarding (Manage Reception Processing) | Conduct Arrival Actions | Enlisted | UNAVAILABLE | |||
| NEW | 4.2 | The system shall enable users to create, edit, modify and delete human resources financial, equipment, and medical information. (NEW) | On-Boarding (Manage Reception Processing) | Conduct Reception Processing | Enlisted | UNAVAILABLE | |||
| NEW | 4.3 | The system shall enable users to conduct processes and actions to transition Trainee to follow on assignment. (NEW) | On-Boarding (Manage Reception Processing) | Close-Out Reception Processing | Enlisted | UNAVAILABLE | |||
| NEW | 4.4 | Process Soldier Transition | On-Boarding (Manage Reception Processing) | Process Soldier Transition | Enlisted | UNAVAILABLE | |||
| NEW | 4.5 | The system shall integrate with different systems of record to provide data according to ingesting system requirements. (NEW) | On-Boarding (Manage Reception Processing) | On-Boarding Integration | Enlisted | UNAVAILABLE | |||
| 3.14 | 5.1 | The system shall provide the capability to automate mission management for the current workforce. | Intelligence | Manage Mission Planning | Enlisted | UNAVAILABLE | |||
| 3.19 | 5.2 | The system shall provide a secure capability to access, track, display, and store location of interest submissions within a territory for the current workforce. | Intelligence | Intel Capabilities | Enlisted | Intel Capabilities | |||
| 6.9 | 5.3 | The system shall enable the display of maps with real time, dynamic geographic mapping, and thematic overlays. | Intelligence | Geo-Maps | Enlisted | UNAVAILABLE | |||
| 3.19.5 | 5.4 | The system shall display live geo-tagging of influencers for future applicants. | Intelligence | Geo-Tagging | Enlisted | UNAVAILABLE | |||
| 7.0 | 7.0 | The system shall provide a publicly-accessible learning management capability. | Training and Leader Dev | UNAVAILABLE | Enlisted | UNAVAILABLE | |||
| 3.20.15 | 7.1 | The system shall provide the capability to access and display workforce management data from authoritative sources. | Training and Leader Dev | UNAVAILABLE | Enlisted | UNAVAILABLE | |||
| 21.0 | 8.0 | The system shall provide the capability for mission support. | Sustain and Support | UNAVAILABLE | Enlisted | UNAVAILABLE | Additional Initiatives may be required | ||
| 21.3.4 | 8.1 | The system shall analyze program effectiveness. | Sustain and Support | Sustain and Support | Enlisted | UNAVAILABLE | ROTC | ||
| New Requirement | 11.26 | 1.1.1 | The system shall provide the ability to designate/create specific sets or subsets of organizations or individuals with controlled access to specific features, data and capabilities for testing and comparative analysis of alternative treatments. | Foundation | User Managment | Enlisted | User Management | ||
| 3.20 | 1.1.1.1 | The system shall provide an adaptive personnel management capability for the current workforce. | Foundation | User Managment | Enlisted | UNAVAILABLE | |||
| 3.4 | 1.1.1.2 | The system shall provide a talent-aware personnel management capability for the current workforce. | Foundation | User Managment | Enlisted | UNAVAILABLE | |||
| 3.8 | 1.1.1.3 | The system shall provide the capability to access, display, and store knowledge, skills, abilities and other attributes (KSAOs) for the current workforce. | Foundation | User Managment | Enlisted | UNAVAILABLE | |||
| 3.9 | 1.1.1.4 | The system shall provide the capability to match current workforce KSAOs to authorized positions that require those KSAOs. | Foundation | User Managment | Enlisted | UNAVAILABLE | |||
| 12.20 | 1.10.1 | The system shall provide the capability to query Open Source Data Feeds. | Foundation | Integration | Enlisted | Integration | |||
| 30.1 | 1.11.1 | The system shall comply with all Information Assurance requirements as defined in the AIE program guidance for DoD, Army, and National Institute of Standards and Technology (NIST) Policy, Guidance, and Directives. | Foundation | Technical/Non-Functional | Enlisted | Technical/Non-functional | |||
| 3.20.5 | 1.11.1.1 | The system shall provide the capability to notify the person responsible for the lead and their supervisor when a lead's single source record is created or changed based on configurable parameters. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 6.7 | 1.11.1.10 | The system shall provide the capability to print locally and remotely. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 6.8 | 1.11.1.11 | The system shall provide the capability to perform a templated analysis to produce a standard report. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 8.9.3 | 1.11.1.12 | The system shall provide the capability to capture multiple email addresses in the single source record and distinguish by type (e.g., work, family). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 8.10.1 | 1.11.1.13 | The system shall provide the capability to scan government-issued user identification to identify the future applicant. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.0 | 1.11.1.14 | The system shall provide the capability to implement system changes based on changes to applicable laws, policies, regulations, and directives (LPRDs). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.1 | 1.11.1.15 | The system shall provide the capability to implement system changes in support of laws, policies, regulations, and directives (LPRDs). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.1.1 | 1.11.1.16 | The system shall provide the capability to implement system changes in support of directive changes. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.1.2 | 1.11.1.17 | The system shall provide the capability to implement system changes in support of statutory changes. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.1.3 | 1.11.1.18 | The system shall provide the capability to implement system changes in support of policy changes. Changes are timely, affordable, and enable continued mission accomplishment. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.1.4 | 1.11.1.19 | The system shall provide the capability to implement system changes in support of regulatory changes. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 3.20.6 | 1.11.1.2 | The system shall provide the capability to digitally capture an individual's identification data, within applicable laws, policies, regulations, and directives (LPRDs), and upload to the single source record. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.2 | 1.11.1.20 | The system shall provide the capability to rapidly implement system-configurable parameter changes in support of statutory changes. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.2.1 | 1.11.1.21 | The system shall provide the capability to rapidly implement system-configurable parameter changes in support of policy changes. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.2.2 | 1.11.1.22 | The system shall provide the capability to rapidly implement system-configurable parameter changes in support of regulatory changes. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.3 | 1.11.1.23 | The system shall provide the capability to track and report system changes. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.4 | 1.11.1.24 | The system shall have the capability to centrally deploy system changes and updates. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 10.5 | 1.11.1.25 | The system shall provide the capability to predict and assess the impacts of changes to doctrine, laws, policies, regulations, and directives (LPRDs). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 11.5 | 1.11.1.26 | The system shall provide the capability to create user-defined and configurable business rules (see Business Process Workflow definition). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 12.2.1 | 1.11.1.27 | All transactions within the AIE shall process within 10 seconds 95% of the time unless a different standard is established in a system interface agreement (SIA) identified as part of the system performance for all modes of access / availability (e.g., mobile use). | Foundation | Technical/Non-Functional | Enlisted | Technical/Non-functional | Unknown | ||
| KSA | 13.0 | 1.11.1.28 | The system shall provide the capability to automate business process workflows via a visual display in a low programming environment. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| 13.2 | 1.11.1.29 | The system shall capture the data entered in the application by the future applicant in the single source record. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 3.20.7 | 1.11.1.3 | The system shall provide the capability to identify how a lead was entered into the system. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 13.3 | 1.11.1.30 | The system shall provide the capability for the future applicant to stop and resume within the application process. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 13.4 | 1.11.1.31 | The system shall notify the workforce of the new future applicant single source record based on zip code / university. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 13.5 | 1.11.1.32 | The system shall provide a public-facing status view of the future applicant recruiting workflow. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 13.6 | 1.11.1.33 | The system shall provide the ability to input, track, and share Order of Merit List (OML) data between like OMLs based on role and echelon. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 13.7 | 1.11.1.34 | The system shall provide the capability to maintain accountability of Future Applicants and their data throughout the Accessions Enterprise. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 13.8 | 1.11.1.35 | AIE shall implement standardized workflow processes and procedures that are available for the next action by authorized users in near real time 99% of the time. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 13.9 | 1.11.1.36 | The system shall provide the capability to define workflow processes and procedures that allow parallel workflows and concurrent users. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 17.0 | 1.11.1.37 | The system shall provide the capability to send alerts and notifications. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 17.1 | 1.11.1.38 | The system shall provide the capability to send alerts and notifications in accordance with defined business rules. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 17.2 | 1.11.1.39 | The system shall provide the capability to send alerts and notifications in accordance with defined workflows. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 3.20.8 | 1.11.1.4 | The system shall provide the capability to capture and track lead transactions within the single source record. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 17.3 | 1.11.1.40 | The system shall provide the capability to send system-wide alerts and notifications. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 19.1 | 1.11.1.41 | The system shall provide an automated validation function. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 23.0 | 1.11.1.42 | The system shall provide an application-based, operating system-agnostic capability. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 23.1 | 1.11.1.43 | The system shall provide access to mission applications. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 23.2 | 1.11.1.44 | The system shall provide the capability to operate on approved accessions devices. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 23.3 | 1.11.1.45 | The system shall provide the capability to perform administrative functions by role by echelon. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 23.4 | 1.11.1.46 | The system shall provide a user-configurable, interactive, context-aware help capability within business process implementation. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 24.0 | 1.11.1.47 | The system shall provide access to multiple domains including NIPR, ARNET, GuardNet, .edu, .com, .gov, .org, and .net. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| KPP | 25.0 | 1.11.1.48 | The system shall comply with Interoperability of Information Technology (IT) IAW DoDI 8330.01. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| 25.1 | 1.11.1.49 | The system shall support the Key Management Interoperability Protocol (KMIP) standard. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 3.20.9 | 1.11.1.5 | The system shall provide the capability to sort on transactions within a lead single source record. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 25.2 | 1.11.1.50 | The system shall be compliant with Net-Centric Data Strategy and Net-Centric Services Strategy. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 25.3 | 1.11.1.51 | The system shall support contingency planning for a MAC level III systems as defined by AR 25-2. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 25.4 | 1.11.1.52 | The system shall comply with DoD IA requirements IAW DoD Instruction 8580.1. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 25.5 | 1.11.1.53 | The system shall effectively exchange information. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 25.6 | 1.11.1.54 | Architectural Products shall be produced IAW DoD Business Enterprise Architecture the most current DoD compliance requirements. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 25.7 | 1.11.1.55 | The system shall provide client-side security. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 25.8 | 1.11.1.56 | The system shall support soft certifications (software form of PKI credentials). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| KPP | 26.0 | 1.11.1.57 | The system shall support compliance with DA and DoD requirements in a commercial cloud configuration, and the National Institute of Standards and Technology Special Publication 800-145, September 2011. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| 26.1 | 1.11.1.58 | The system shall provide automatic virtual server provisioning to dynamically scale capacity during demand spikes to maintain performance and decrease capacity during lulls to reduce costs. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 26.2 | 1.11.1.59 | The system shall be compliant with FEDRAMP+ security controls and DoD Cloud Computing Security Requirements Guide (SRG) cloud security information impact level (IL) 4 security controls. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 6.1.1.2 | 1.11.1.6 | Data displayed shall have a level of accuracy that meets or exceeds industry standards (e.g., a 99.9% accuracy level). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 26.4 | 1.11.1.60 | The system shall provide capabilities that are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 26.5 | 1.11.1.61 | The system shall provide computing resources that are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| KSA | 26.6 | 1.11.1.62 | The system shall have the capability to automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service provided (e.g., storage, processing, bandwidth, and active user accounts) so that resource usage can be monitored, controlled, and reported. | Foundation | Technical/Non-Functional | Enlisted | Technical/Non-functional | ||
| 26.6.1 | 1.11.1.63 | The system shall have the ability to limit a user's access to data and reports at the organizational level required with a level of accuracy that meets or exceeds industry standards (e.g., a 99.9% level of accuracy). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 26.7 | 1.11.1.64 | The system shall provide the capability for off-line functionality. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 26.8 | 1.11.1.65 | The system shall provide a 508 compliant or certified exempt, client, or Web-based user interface. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 27.0 | 1.11.1.66 | The software vendor shall provide affordable and efficient system support. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 27.1 | 1.11.1.67 | The software vendor shall provide an Enterprise licensing agreement. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 27.2 | 1.11.1.68 | The software vendor shall provide maintenance support. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 27.3 | 1.11.1.69 | The software vendor shall provide training. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 6.2 | 1.11.1.7 | The system shall secure location tracking data and make available based on role and echelon. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 27.4 | 1.11.1.70 | The software vendor shall provide both an automated and manual processing option for 24/7 user and administrator application support and maintenance. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| APA | 28.0 | 1.11.1.71 | The system shall provide a mission availability rate of 98%. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| KSA | 29.0 | 1.11.1.72 | The system shall have at least a 98% probability of operating over a 72 hour period without an Essential Function Failure (EFF). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| 29.1 | 1.11.1.73 | The system shall ensure at least a mean time between failures (MTBF) of greater than 4 weeks, and a mean time to repair (MTTR) of less than 2 hours. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| APA | 30.0 | 1.11.1.74 | The system shall comply with Information Assurance Requirements IAW DoDD 8500.01E and Army Regulation 25-2. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| KPP | 31.0 | 1.11.1.75 | The system shall protect Personally Identifiable Information (PII ) and Protected Health Information (PHI) IAW DoDD 5400.11, DoD Privacy Program, and DoDI 8580.02 Security of Individually Identifiable Health Information in DoD Health Care Programs. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| 31.1 | 1.11.1.76 | The system shall provide sufficient safeguards to ensure PII and PHI data are protected from unauthorized release 99% of the time. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| KSA | 33.0 | 1.11.1.77 | The system shall provide a backup and disaster recovery capability. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| 33.1 | 1.11.1.78 | The system shall provide recovery of full capabilities within 24 hours of the official declaration of a disaster (e.g. loss of the primary data center), to include reestablishment of critical system interfaces, to a state not more than 4 hours prior to disaster Recovery Point Objective (RPO). | Foundation | Technical/Non-Functional | Enlisted | Technical/Non-functional | |||
| APA | 34.0 | 1.11.1.79 | The system shall record and maintain data, and present it in the form of reports in a timely manner. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| 6.5 | 1.11.1.8 | The system shall have the capability to perform automated report generation. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 34.1 | 1.11.1.80 | All transactions internal to AIE (which do not involve exchanging data with any partner system) shall be recorded and viewable for reporting in real time. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 34.2 | 1.11.1.81 | All transactions external to AIE (requiring data exchange with one or more partner systems) shall be recorded and will be viewable for reporting in near real time. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 3.18 | 1.11.1.82 | The system shall provide the capability to track and display center of gravity data relevant to subordinate unit(s). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 11.9 | 1.11.1.83 | The system shall provide the capability to perform automated configurable surveys and display results. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 11.9.1 | 1.11.1.84 | The system shall provide the capability to create configurable surveys by target audience. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 11.9.2 | 1.11.1.85 | The system shall provide the capability to aggregate survey results by configurable parameters. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 11.10 | 1.11.1.86 | The system shall provide an integrated capability to identify, categorize, assess, and display causes of attrition and retention across the Human Resources Enterprise to inform the Accessions Enterprise. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| New Requirement | 11.28 | 1.11.1.87 | The system shall have the capability to deploy available technological enhancements (SaaS, IaaS/iPaaS) as released and are viable to fulfill or enhance existing functional requirements. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| New Requirement | 11.29 | 1.11.1.88 | The system shall provide an AI assistant to guide individuals through the accession process. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ||
| 8.8 | 1.11.1.89 | The system shall provide a device-agnostic e-fax capability. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 6.6 | 1.11.1.9 | The system shall provide the capability to standardize data input and reduce the amount of free text. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 11.24 | 1.11.1.90 | The system shall provide the capability to identify potential opportunities for future applicants to join the Army based on information provided by future applicants. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | Temp Reservations | ||
| 14.0 | 1.11.1.91 | The system shall provide the capability to interface with public facing Web Portal(s). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 20.0 | 1.11.1.92 | The system shall provide the capability to manage force structure and request requirement and authorization changes (e.g., face, space, and location). | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 20.3 | 1.11.1.93 | The system shall provide the capability to provide workforce view of all human resources by interfaces with systems for civilian, military, active, reserve, contractors, temporary and borrowed manpower. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 21.3.8 | 1.11.1.94 | The system shall provide the capability to maintain local regulations and policy. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| 3.20.16 | 1.11.1.95 | The system shall provide an integrated communication tracking capability at echelon to record workforce transactions. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | |||
| KSA | 3.0 | 1.11.1.96 | The system shall provide an adaptive and talent-aware personnel management capability for future applicants and current workforce. | Foundation | Technical/Non-Functional | Enlisted | UNAVAILABLE | ROTC | |
| 16.2 | 1.2.1 | The system shall provide a secure device-agnostic source document capture and upload capability | Foundation | Document Management | Enlisted | Document Management | |||
| 16.3 | 1.2.1.1 | The system shall provide the capability to generate paperless documents complete with an authentication in accordance with laws, policies, regulations, and directives (LPRDs). | Foundation | Document Management | Enlisted | UNAVAILABLE | |||
| 16.5 | 1.2.1.2 | The system shall provide the capability to amend, append, or revoke a form subsequent to signing. | Foundation | Document Management | Enlisted | UNAVAILABLE | |||
| 15.8 | 1.2.1.3 | The system shall provide the capability to identify and display source document requirements based on Interview and Pre-Screen responses. | Foundation | Document Management | Enlisted | UNAVAILABLE | |||
| 18.6 | 1.2.1.4 | The system shall provide the capability to tag source document images in accordance with metadata requirements. | Foundation | Document Management | Enlisted | UNAVAILABLE | |||
| 18.1.1 | 1.3.1 | The system shall provide the capability to electronically sign products (e.g. documents, forms) in compliance with authentication laws, policies, regulations, and directives (LPRDs). | Foundation | Forms | Enlisted | Forms | |||
| 6.4 | 1.3.1.1 | The system shall provide the capability to create standardized templates. | Foundation | Forms | Enlisted | UNAVAILABLE | |||
| 16.4 | 1.3.1.2 | The system shall provide the capability to prompt the user to obtain a new signature if form data was changed subsequent to signing. | Foundation | Forms | Enlisted | UNAVAILABLE | |||
| 13.1 | 1.3.1.3 | The system shall provide the capability to develop and amend request for orders, and direct new member requirements in accordance with laws, policies, regulations, and directives (LPRDs) synchronized with eligibilities, gaining command requirements, personnel accountability requirements and supporting events. | Foundation | Forms | Enlisted | Forms | |||
| 16.1 | 1.3.1.4 | The system shall provide a single entry capability that populates required fields for specified all forms. | Foundation | Forms | Enlisted | UNAVAILABLE | |||
| 2.3.1 | 1.4.1 | The system shall provide the capability to archive records based on laws, policies, regulations, and directives (LPRDs). | Foundation | Core Data | Enlisted | Core Data | |||
| 2.3.2 | 1.4.1.1 | The system shall provide the capability to track collaborative modification actions to records. | Foundation | Core Data | Enlisted | UNAVAILABLE | |||
| 2.4 | 1.4.1.2 | The system shall provide the capability to merge data within an existing record. | Foundation | Core Data | Enlisted | UNAVAILABLE | |||
| 2.5 | 1.4.1.3 | The system shall provide the capability to identify record field conflicts for adjudication. | Foundation | Core Data | Enlisted | UNAVAILABLE | |||
| 19.0 | 1.4.1.4 | The system shall provide data validation. | Foundation | Core Data | Enlisted | UNAVAILABLE | |||
| 19.2 | 1.4.1.5 | The system shall provide the capability for real-time data validation during business process workflows. | Foundation | Core Data | Enlisted | UNAVAILABLE | Interface Dependency | ||
| 19.3 | 1.4.1.6 | The system shall have the capability to identify unvalidated data within the single source record. | Foundation | Core Data | Enlisted | UNAVAILABLE | |||
| 11.25 | 1.4.1.7 | The system shall provide the capability to identify and quantify the impact of competitors on the operational environment. | Foundation | Core Data | Enlisted | UNAVAILABLE | |||
| 3.6 | 1.4.1.8 | The system shall provide the capability to perform adhoc queries against data exposed to the network for the current workforce. | Foundation | Core Data | Enlisted | UNAVAILABLE | |||
| 3.5 | 1.4.1.9 | The system shall provide the capability to perform adhoc queries against data exposed to the network for future applicants. | Foundation | Core Data | Enlisted | UNAVAILABLE | |||
| 11.1 | 1.5.1.1 | The system shall provide the capability to perform predictive data analytics. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 20.4 | 1.5.1.10 | The systems shall provide the capability to access and display civilian force data and status. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 11.7 | 1.5.1.11 | The system shall provide the capability to perform data analytics by echelon. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 11.8 | 1.5.1.12 | The system shall provide the capability to perform data analytics by role. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 11.2 | 1.5.1.2 | The system shall provide the capability to perform descriptive data analytics. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 11.3 | 1.5.1.3 | The system shall provide the capability to perform prescriptive data analytics. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 11.16 | 1.5.1.4 | The system shall provide the capability to define the business rules to determine and assess mission and attrition risk. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 11.17 | 1.5.1.5 | The system shall provide the capability to determine, historical future applicant loss rate. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 11.18 | 1.5.1.6 | The system shall provide the capability to identify, future applicant losses associated with market attributes. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 11.19 | 1.5.1.7 | The system shall provide the capability to identify, display future applicant losses associated with non-market attributes. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 3.12 | 1.5.1.8 | The system shall provide the capability to determine individual productivity for the current workforce. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | |||
| 8.9 | 1.5.1.9 | The system shall provide a self-service information display showing information on upcoming events, and current and past future applicant profiles. | Foundation | Data Analytics | Enlisted | UNAVAILABLE | Self-serving Koski | ||
| 6.1 | 1.6.1 | The system shall provide a capability for the user to create and interact with configurable stories, dashboards, and reports in multiple formats based on user role and echelon. | Foundation | Workspaces | Enlisted | Workspaces | |||
| 9.2.3 | 1.6.1.1 | The system shall provide the capability to display a user-configured prospecting and enrollment plan assessment dashboard. | Foundation | Workspaces | Enlisted | Recruiter | |||
| 6.1.6 | 1.6.1.10 | The system shall provide a capability for the user to interact with the user reports in multiple formats based on user role and echelon. | Foundation | Workspaces | Enlisted | UNAVAILABLE | |||
| 6.3 | 1.6.1.11 | The system shall provide a capability to display the operational environment in multiple formats. | Foundation | Workspaces | Enlisted | UNAVAILABLE | |||
| 14.4 | 1.6.1.12 | The system shall provide a capability for each organization to configure a default homepage. | Foundation | Workspaces | Enlisted | UNAVAILABLE | |||
| KSA | 6.1.1 | 1.6.1.4 | The system shall provide a capability for the user to create a configurable story in multiple formats based on user role and echelon. | Foundation | Workspaces | Enlisted | UNAVAILABLE | ||
| 6.1.1.1 | 1.6.1.5 | The system shall provide standardized content for user defined displays that are configurable based upon role. | Foundation | Workspaces | Enlisted | UNAVAILABLE | |||
| 6.1.2 | 1.6.1.6 | The system shall provide a capability for the user to create a configurable dashboard in multiple format based on user role and echelon. | Foundation | Workspaces | Enlisted | UNAVAILABLE | Possible Duplicate | ||
| 6.1.3 | 1.6.1.7 | The system shall provide a capability for the user to create a configurable report in multiple formats based on user role and echelon. | Foundation | Workspaces | Enlisted | UNAVAILABLE | |||
| 6.1.4 | 1.6.1.8 | The system shall provide a capability for the user to interact with the user story in multiple formats based on user role and echelon. | Foundation | Workspaces | Enlisted | UNAVAILABLE | |||
| 6.1.5 | 1.6.1.9 | The system shall provide a capability for the user to interact with the user dashboard in multiple formats based on user role and echelon. | Foundation | Workspaces | Enlisted | UNAVAILABLE | |||
| 1.1 | 1.8.1.1 | The system shall provide a multi-tenant environment from which continuous security upgrades are issued based on best business practices. | Foundation | System Management | Enlisted | Security | |||
| 1.3 | 1.8.1.3 | The system shall provide a multi-tenant environment from which continuous innovation capability can be made available based on best business practices. | Foundation | System Management | Enlisted | Innovation | |||
| 15.2 | 1.9.1 | The system shall provide the capability to access content library products based on role. | Foundation | Content Library | Enlisted | Content Library | |||
| 15.3.1 | 1.9.1.1 | The system shall provide the capability for the content library content to be accessible on-line. | Foundation | Content Library | Enlisted | UNAVAILABLE | |||
| 15.3.2 | 1.9.1.2 | The system shall provide the capability to download selected library content for off-line usage. | Foundation | Content Library | Enlisted | UNAVAILABLE | |||
| 3.20.4 | 2.1.1.1 | The system shall provide the capability for lead data to be uploaded into the single source record from multiple sources and in multiple formats. | CRM | Lead Generation | Enlisted | Staging Leads | |||
| 3.20.13 | 2.1.1.2 | The system shall provide the capability to perform near-real time lead routing. | CRM | Lead Generation | Enlisted | UNAVAILABLE | |||
| 3.20.14 | 2.1.1.3 | The system shall provide the capability to perform near-real time lead assignment. | CRM | Lead Generation | Enlisted | UNAVAILABLE | |||
| 3.3 | 2.1.1.6 | The system shall provide a talent-aware personnel management capability for future applicants. | CRM | Lead Generation | Enlisted | UNAVAILABLE | |||
| 3.7 | 2.1.1.7 | The system shall provide the capability to access, display, and store knowledge, skills, abilities and other attributes (KSAOs) for future applicants. | CRM | Lead Generation | Enlisted | UNAVAILABLE | |||
| 3.20.12.3 | 2.1.1.8 | The system shall provide a lead source configurable digital acknowledgment when lead information is received. | CRM | Lead Generation | Enlisted | UNAVAILABLE | |||
| 4.0 | 2.2.1.1 | The system shall enable, track and report Prospecting Activities. | CRM | Community Portal | Enlisted | User Provisioning | |||
| 8.9.1 | 2.2.1.2 | The system shall provide the capability for the workforce to schedule appointments with a future applicant. | CRM | Prospecting | Enlisted | UNAVAILABLE | |||
| 8.2 | 2.2.1.3 | The system shall provide the capability to access Systems of Records (SORs) and review records to create email distribution lists for mass email to a selected group. | CRM | Prospecting | Enlisted | UNAVAILABLE | Some integration as well | ||
| 5.6 | 2.2.1.4 | The system shall provide the capability to initiate email campaigns. | CRM | Prospecting | Enlisted | ||||
| 5.6.1 | 2.2.1.5 | The system shall provide the capability to track and report email campaign data. | CRM | Prospecting | Enlisted | UNAVAILABLE | |||
| 4.1 | 2.2.1.7 | The system shall provide the capability to display prospecting measures of performance and measures of effectiveness related to all lead sources for prospecting. | CRM | Prospecting | Enlisted | Metrics | |||
| 15.4 | 2.3.1.10 | The system shall provide the capability to capture interview responses as the interview is being conducted. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 15.5 | 2.3.1.11 | The system shall provide the capability, based on the responses, automatically tailor follow-on questions so that non-applicable ones do not appear. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 15.9 | 2.3.1.12 | The system shall provide the capability to allow the workforce to incorporate any material from the content library to the interview process flow. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 15.1 | 2.3.1.13 | The system shall provide the capability to allow the workforce to incorporate command-approved personal material (videos, pictures, etc.) in to the interview process flow. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 15.11 | 2.3.1.14 | The system shall provide the capability to audio record and store the interview in accordance with laws, policies, regulations, and directives (LPRDs). | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 15.12 | 2.3.1.15 | The system shall provide the capability to produce a document for the Future Applicant that communicates the Army Value Proposition. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 8.0 | 2.3.1.16 | The system shall provide the capability to perform Future Applicant Management Support Services. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 8.4 | 2.3.1.2 | The system shall provide a centralized, automated, event-driven capability that supports the interview process. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 4.6.1 | 2.3.1.3 | The system shall provide the capability to match future applicant KSAOs with workforce KSAOs. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 8.1 | 2.3.1.4 | The system shall provide an integrated Multi-Point Video Conferencing capability that enables real-time communication, collaboration, recording, and storing through a single nexus. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 8.3 | 2.3.1.5 | The system shall provide an integrated multi-platform Immersive Virtual Reality and First Person Video capability that enables the recruiting subject to visualize, understand, and experience Army activities. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 8.5 | 2.3.1.6 | The system shall provide a centralized, automated, event-driven capability that supports the pre-screening process. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 8.6 | 2.3.1.7 | The system shall provide the capability for the workforce to tailor the pre-screen process for future applicant. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 8.7 | 2.3.1.8 | The system shall integrate the interview and pre-screening processes. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 15.3 | 2.3.1.9 | The system shall provide the capability for the workforce to tailor an interview from the content library. | CRM | Interviewing | Enlisted | UNAVAILABLE | |||
| 4.4 | 2.4.1.10 | The system shall provide the capability to manage referral information. | CRM | Recruiter Centric Network | Enlisted | UNAVAILABLE | |||
| 4.4.1 | 2.4.1.11 | The system shall provide the capability to input referral information from multiple sources in multiple formats and link. | CRM | Recruiter Centric Network | Enlisted | UNAVAILABLE | |||
| 4.4.2 | 2.4.1.12 | The system shall provide the capability to link referral information to a single source record. | CRM | Recruiter Centric Network | Enlisted | UNAVAILABLE | |||
| 4.4.3 | 2.4.1.13 | The system shall provide the capability to link referral information to an advocate record. | CRM | Recruiter Centric Network | Enlisted | UNAVAILABLE | |||
| 2.1 | 2.4.1.5 | The system shall be able to create an advocate record. | CRM | Recruiter Centric Network | Enlisted | Recruiter Centric Network | |||
| 2.1.1 | 2.4.1.6 | The system shall provide the capability to audit the advocate record. | CRM | Recruiter Centric Network | Enlisted | Recruiter Centric Network | |||
| 2.1.2 | 2.4.1.7 | The system shall provide the capability to capture changes to the advocate within the advocate record. | CRM | Recruiter Centric Network | Enlisted | Recruiter Centric Network | |||
| 5.9 | 2.4.1.8 | The system shall provide the capability to store marketing activity in the advocate record. | CRM | Recruiter Centric Network | Enlisted | UNAVAILABLE | |||
| 14.1 | 2.5.1.3 | The system shall provide the capability to ensure portal inputs are from a human (not a bot). | CRM | Community Portal | Enlisted | User Provisioning | |||
| 8.10.4 | 2.5.1.4.1 | The system shall provide the capability for future applicants to upload documents to the single source record. | CRM | Community Portal | Enlisted | Record Management | |||
| 19.4 | 2.5.1.5.1 | The system shall be able to use approved user authentication methods. | CRM | Community Portal | Enlisted | User Experience | |||
| 3.20.10.1 | 2.6.1.1 | The system shall provide the capability to modify lead prioritization business rules. | CRM | Record Lifecycle Management | Enlisted | Record Lifecycle Management | |||
| 15.6 | 2.6.1.10 | The system shall provide the capability to identify inconsistencies in responses with captured data. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 15.7 | 2.6.1.11 | The system shall provide the capability to reconcile inconsistencies when identified. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 3.20.1 | 2.6.1.12 | The system shall provide the capability to create a lead. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 3.20.2 | 2.6.1.13 | The system shall provide the capability to track a lead. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 3.20.3 | 2.6.1.14 | The system shall provide the capability to identify the source that created the lead. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 3.20.12 | 2.6.1.15 | The system shall provide the capability for lead distribution. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 3.20.12.2 | 2.6.1.16 | The system shall provide a notification to the workforce when a lead is generated. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 14.3 | 2.6.1.17 | The system shall provide the capability to capture certification of voluntary consent to contact. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 4.1.1 | 2.6.1.18 | The system shall have the capability to authoritatively classify lead sources. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 4.1.2 | 2.6.1.19 | The system shall have the capability to quantify lead source effectiveness. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 3.20.10.2 | 2.6.1.2 | The system shall provide the capability to define lead prioritization business rules configurable by role. | CRM | Record Lifecycle Management | Enlisted | Record Lifecycle Management | |||
| 4.1.3 | 2.6.1.20 | The system shall have the capability to capture multiple lead sources. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 4.1.4 | 2.6.1.21 | The system shall have the capability to provide feedback to lead source. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 4.2 | 2.6.1.22 | The system shall provide the capability to conduct Screening Activities. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 5.7 | 2.6.1.23 | The system shall provide the capability identify a person as a stale lead or stale prospect. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 5.7.1 | 2.6.1.24 | The system shall provide the capability to contact persons identified as stale lead or stale prospect using the specified modes of communication. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 5.7.2 | 2.6.1.25 | The system shall provide the capability to notify the workforce when a stale lead has been identified. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 5.7.3 | 2.6.1.26 | The system shall provide the capability to notify the workforce when a stale prospect has been identified. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 5.7.4 | 2.6.1.27 | The system shall provide the capability to define configurable stale lead criteria. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 5.7.5 | 2.6.1.28 | The system shall provide the capability to define configurable stale prospect criteria. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 5.7.6 | 2.6.1.29 | The system shall track stale lead follow-up mechanisms. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 3.20.12.1 | 2.6.1.3 | The system shall provide the capability for leads to be visible within the system as soon as the lead is generated. | CRM | Record Lifecycle Management | Enlisted | Record Lifecycle Management | |||
| 5.7.7 | 2.6.1.30 | The system shall track stale prospect follow-up mechanisms. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 14.2 | 2.6.1.32 | The system shall provide the capability to capture Privacy Act consent. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 3.1 | 2.6.1.33 | The system shall provide an adaptive personnel management capability for future applicants. | CRM | Record Lifecycle Management | Enlisted | Applicant Management | |||
| 2.2.3 | 2.6.1.34 | The system shall provide the capability to capture disqualifiers in an applicant's single source record. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 2.2.4 | 2.6.1.35 | The system shall provide the capability to allow the workforce to remove disqualifiers in an applicant's single source record. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 4.7 | 2.6.1.36 | The system shall provide the capability to record future applicant modes of communications preferences in the single source record. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 11.2 | 2.6.1.37 | The system shall provide the capability to match, current Future Soldier profiles with historical profiles. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 8.1 | 2.6.1.38 | The system shall provide an automated future applicant check-in capability. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 8.10.2 | 2.6.1.39 | The system shall provide the capability to upload future applicant check-in data from approved external and internal sources in to the single source record. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 2.2 | 2.6.1.4 | The system shall be able to create a single source record. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 8.10.3 | 2.6.1.40 | The system shall provide the capability to allow for workforce check-in assistance. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 8.10.5 | 2.6.1.41 | The system shall provide the capability to notify the workforce of future applicant self-certification completion based on check-in data. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 3.20.11 | 6.1.1.11 | The system shall provide the capability to perform near-real time leads scoring. | Marketing | Campaign | Enlisted | UNAVAILABLE | AEMO Discussion Needed | ||
| 3.20.11.1 | 6.1.1.12 | The system shall provide the capability to identify scoring criteria informed by business policy and industry standards. | Marketing | Campaign | Enlisted | UNAVAILABLE | AEMO Discussion Needed | ||
| 3.20.11.2 | 6.1.1.13 | The system shall provide the capability for leads to be scored in real-time based on established trends. | Marketing | Campaign | Enlisted | UNAVAILABLE | AEMO Discussion Needed | ||
| 3.20.11.3 | 6.1.1.14 | The system shall provide the capability for lead scoring criteria to be configurable by each user and organization. | Marketing | Campaign | Enlisted | UNAVAILABLE | AEMO Discussion Needed | ||
| 3.20.10 | 6.1.1.15 | The system shall provide the capability to prioritize leads. | Marketing | Campaign | Enlisted | UNAVAILABLE | AEMO Discussion Needed | ||
| 2.2.1 | 6.1.1.15 | The system shall provide the capability to audit the single source record. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 2.2.2 | 2.6.1.6 | The system shall provide the capability to capture changes to the single source record within the single source record. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 4.7.1 | 2.6.1.7 | The system shall provide the capability for future applicants to opt out of available modes of communication. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE | |||
| 4.8 | 2.6.1.8 | The system shall capture and maintain contact history from all communication methods in the single source record. | CRM | Record Lifecycle Management | Enlisted | UNAVAILABLE |
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 .