DRAFT_ARES Prototype Requirements.pdf

ARES Prototype Requirements

1.0 Purpose:

Prototyping is a means of testing assumptions about technologies and approaches before expending significant amounts of effort or money building something that may not address the organization’s problem. Prototyping is a low-cost, rapid risk mitigation approach. As such, we propose that the first Aerospace Readiness Enterprise System (ARES) use case be built as a prototype initially, with the following capability goals.

ARES is the Air Force’s enterprise solution for scheduling, standardization and evaluation (stan/eval) and training management which is intended to replace the Patriot Excalibur (PEX), Puckboard, and Graduate/Training Integration Management System (G/TIMS) legacy software programs.

Specifically, ARES will leverage commercial software to the greatest extent possible and be deployed, initially, within the Impact Level (IL) 4 partition with a path to IL-6 deployment thereafter. Further, the Air Force, in support of the DAF BATTLE NETWORK, has an enduring requirement to deploy a robust solution which provides enterprise capabilities for scheduling, stan/eval, and training for increased readiness and lethality.

Starting with the requirements of Air Education and Training Command (AETC) as the basis for this prototype, but not excluding requirements from other MAJCOMs, the prototype should meet as many of the following criteria as possible. Final acceptance of the prototype will be based on its ability to meet the threshold requirements outlined below. The final evaluation of the prototypes will also consider objective criteria as defined below. The prototype shall be completed and available for inspection and use no later than 90 calendar days after contract award.

1.1 Prototype Evaluation Methodology:

• Threshold represents the minimum acceptable value for the ARES requirement

• Threshold criteria will be evaluated on a Pass/Fail basis.

• Objective represents the ideal level of performance value for the ARES requirement

2.0 Threshold Requirements:

The following requirements outlined in the table below are threshold requirements and will be evaluated on a pass/fail basis.

ID # Type Description 1 Technical The prototype shall be hosted and developed on the Operations

Enterprise Architecture (OpsEA) platform.

2 Technical The prototype shall be built at the IL-4 level.

3 Technical The prototype shall not use any cloud services not forecast to be available at the IL-6 level.

4 Technical The prototype shall offer auditability, reporting, and platform ATO compliance as part of a CI/CD, DevSecOps hardened pipeline.

5 Technical The prototype shall integrate an Intrusion Detection System (IDS) and cyber security vulnerability to conform to OpsEA platform requirements.

6 Accessibility The prototype shall be designed for access control, to include defined user roles with associated permissions.

7 Accessibility The prototype shall enable systems/data access to be determined by user role.

8 Accessibility The prototype shall provide the ability for authorized users to assign or remove roles and permissions.

9 Syllabus Management

The prototype shall support building and managing formal training syllabi.

10 Scheduling The prototype shall support the following event scheduling capabilities:

Assigning an individual to a location/resource to accomplish an event.

11 Scheduling The prototype shall support verifying individual and resource availability and configuration.

12 Scheduling The prototype shall support allowing the ability to create, copy, and edit event details in calendar view.

13 Stan/Eval The prototype shall enable the capability to build, administer, and track routine qualification.

Extensibility & Scalability:

Although the ARES Prototype shall be developed with an initial focus on an AETC Undergraduate Pilot Training (UPT), the prototype shall be built for both extensibility and scalability such that the final solution will be capable of supporting the DAF-wide Enterprise with the potential to extend to support both Joint and Allied use cases.

Moreover, the design and architecture of the prototype must be flexible enough to eventually support a wide range of different air frames, scheduling frameworks, and user roles. The ARES Prototype Other Transaction (OT) contractor team shall demonstrate the potential for extensibility and scalability through development of the following artifacts to be delivered upon completion of the prototype:

• A roadmap (NTE 3 pages) outlining the plan to transition from IL-4 to IL-6. The roadmap shall demonstrate an understanding of the milestones and time required for this transition.

• Data Segregation Plan (NTE 5 pages) documenting the contractor’s approach to data segregation, to include defined data categories, proposed segregation mechanisms, data flow diagrams, access control policies. This Data Segregation Plan will enable access control to protect PII as well as the capability to scale to support Joint and Allied use cases.

• A whitepaper (NTE 3 pages) outlining a plan to scale to enable Denied, Degraded, Intermittent, and Limited (DDIL) and mobile access

• The contractor shall provide, with no page limit, release documentation for the prototype submittal.

3.0 Objective Criteria

The following items outlined in the table below are objective criteria.

ID # Type Description

1 Accessibility Ability to access scheduling and logging via mobile devices (i.e., Electronic Flight Bags (EFBs)).

2 Accessibility Ability to send notifications and alerts to users to indicate changes to scheduling, documentation, or personal information.

3 Syllabus Management

Assigning training syllabi to an individual and to classes.

4 Syllabus Management

Assigning syllabi versions and tracking version assignments to students.

5 Syllabus Management

Creating dependencies among events in a syllabus.

6 Syllabus Management

View training progress in individual syllabi.

7 Scheduling Use of live data from Envision, specifically ARTEMIS currency data to be used to filter or highlight aircrew for applicable sorties.

8 Scheduling Provision of a user-defined and standard role-based calendar view, including views such as a 1-week, 2-week, and month views to accommodate a range of aircrew personas (i.e., Schedulers, SARM, Pilots, Loadmasters, etc.).

9 Scheduling Creation of event type templates that include location data, number of students, etc.

10 Scheduling Capability to schedule up to 160 sorties per day with a goal of accelerating the DAF’s pilot training pipeline.

11 Scheduling Enables definition of non-training days (holidays, down days, etc.).

12 Scheduling Requires acknowledgment when creating a conflict, highlights conflict on calendar views / reports.

13 Scheduling Provide “auto resolve” conflict ability that recommends ways to resolve conflicts.

14 Scheduling Ability to track attendance / report student attendance.

15 Scheduling Supports AI-enhanced scheduling that creates events and assigns individuals based on priorities.

16 Scheduling Allows students to export individual calendars in external file types, sanitize PII and CUI+ data.

17 Scheduling Integrates event location data with mapping programs (i.e., Google maps).

18 Scheduling Integrates instant messaging/ group chat for scheduling events (e.g.., Slack, Mattermost, etc.).

19 Stan/Eval Documents qualification statuses for selected individuals 20 Stan/Eval Assigns remedial training when required 21 Stan/Eval Indicates expiration date for accuracy of the data (earliest date a qual/cert expires for any individual) and highlights any expired qual/cert/currency or other limitation identified by associated Air Force Instruction.

22 Stan/Eval The ability to add and manage local qualifications, certifications, and syllabi at the individual squadron levels (i.e., Aircraft Commander Upgrade or Just-in-Time Training certification).

23 Waivers Requesting, submitting, and approval of waivers to specific requirements, 24 Waivers Defining routing chain by waiver type 25 Waivers Documenting and visibly displaying routing of waiver and final approval 26 Waivers The ability for certain users to review all waivers by status and level of approval.

27 Waivers Track waivers by data like individual, event, dates, or some combination 28 Waivers Waivers need to be signed off by higher echelons of command in order to bypass Air Force Instruction requirements levied on different flying communities.

29 Training Class Manager

Adding multiple students as a batch to classes and verifying prerequisites have been met

30 Training Class Manager

Management of training courses for various course types, locations, and forecasted variables

31 Training Class Manager

Incorporating existing AETC syllabi/ courses Building training classes to (structured series of classes) to include virtual, computer-based training (CBT), in-person, SIMs, etc.

32 Training Class Manager

Creating and modifying academic calendars (a calendar that encompasses all required training)

33 Training Class Manager

Forecasting class graduation dates based on start dates and syllabus length

34 Accessions/ Pipeline Management

Tracking the progress of assets (airframes or trainees) through various stages of the pipeline

35 Accessions/ Pipeline Management

Assigning tasks and responsibilities to team members involved in the assessment and onboarding process

36 Accessions/ Pipeline Management

Generating reports and analytics on the status and efficiency of the asset pipeline

37 Accessions/ Pipeline Management

Integrating with other systems or databases to gather necessary information for asset assessment and onboarding (e.g.,, ARTEMIS)

38 Accessions/ Pipeline Management

Ensuring compliance with regulations and standards throughout the assessment and onboarding process

39 Continuation Training

Creating and assigning local (base/unit specific) training requirements

40 Continuation Training

Developing and implementing a structured program to ensure personnel maintain proficiency and readiness in their assigned duties

41 Continuation Training

Monitoring and tracking training progress to ensure compliance with regulatory and organizational requirements with a dashboard display

42 Continuation Training

Provide a portal/host for training aids and instructions for personnel to complete continuation training activities efficiently and effectively

43 Training Documentation

Ensure training documentation is accurate, up-to-date, and accessible to relevant stakeholders

44 Training Documentation

Facilitate the creation and distribution of training materials, manuals, guides, and other resources

45 Reports and Analysis

Performing analysis on training data to identify trends, patterns, and areas for improvement

46 Reports and Analysis

Presenting findings and insights to users to inform decision-making and strategic planning

47 Reports and Analysis

Customizing reports to meet the specific needs and requirements of different suserss, such as management, instructors, and trainees

48 Reports and Analysis

Utilizing data visualization techniques, such as charts, graphs, and dashboards, to enhance the readability and comprehension of training reports

49 Reports and Analysis

Conducting comparative analysis to benchmark training performance against industry standards or organizational benchmarks

50 Reports and Analysis

Implementing feedback mechanisms to gather input from users and incorporate insights into training analysis and reporting

51 Documentation Create appropriate event authorizations, as required (i.e., flight authorizations)

52 Documentation Build Pre/Post event processes to meet requirements in AFIs 53 Safety Automation of risk calculation, customizable at the unit-level and based on factors defined by AFIs 54 Go/No-Go Verify an individual is qualified and certified to accomplish a specific event 55 Go/No-Go Identify specific event requirements not met by specific individuals 56 Go/No-Go Forecast when individuals will go overdue for a go/no-go requirement 57 Personnel

Manager Adding, editing, and storing comprehensive personnel training records

58 Personnel Manager

Data link to import/verify personnel data from external systems (i.e., MILPDS)

59 Personnel Manager

Minimize personnel data native to this system

60 Personnel Manager

Generating unique identifiers for aircrews and instructors

61 Personnel Manager

Detecting and merging duplicate records

62 Personnel Manager

Tracking employment details, history, and status as well as contact info, education, and emergency contacts

63 Personnel Manager

Managing all training and certifications

64 Personnel Manager

Ability to designate and assign roles (e.g.., instructor) to specific users

65 Personnel Manager

Importing/exporting personnel and reassigning to supervisors

66 Personnel Manager

Ability to search and filter via name, role, unit, etc.

67 Personnel Manager

Ability to on-board and off-board users between units

4.0 References:

• Invitation to ARES Lightning Networking Session, Statement of Need:

https://usaf.dps.mil/:w:/r/teams/FlightOpsAll- ARESMarketResearch/_layouts/15/Doc.aspx?sourcedoc=%7BE8D356F4-09CF-

4297-A6ED-

213B53CE25BE%7D&file=ARES%20Lightning%20Networking%20Session.docx &fromShare=true&action=default&mobileredirect=true

• AIR FORCE MANUAL 11-202, VOLUME 1 AIRCREW TRAINING: https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11-202v1/afman11- 202v1.pdf

• AIR FORCE MANUAL 11-202, VOLUME 2 AIRCREW STANDARDIZATION AND

EVALUATION PROGRAM: https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11-202v2/afman11- 202v2.pdf

• AIR FORCE MANUAL 11-202, VOLUME 3 FLIGHT OPERATIONS:

https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11- 202v2/afman11-202v3.pdf

• AIR FORCE INSTRUCTION 11-200, AIRCREW TRAINING,

STANDARDIZATION/EVALUATION, AND GENERAL OPERATIONS

STRUCTURE: https://static.e-publishing.af.mil/production/1/af_a3/publication/afi11-200/afi11-200.pdf https://usaf.dps.mil/:w:/r/teams/FlightOpsAll-ARESMarketResearch/_layouts/15/Doc.aspx?sourcedoc=%7BE8D356F4-09CF-4297-A6ED-213B53CE25BE%7D&file=ARES%20Lightning%20Networking%20Session.docx&fromShare=true&action=default&mobileredirect=true https://usaf.dps.mil/:w:/r/teams/FlightOpsAll-ARESMarketResearch/_layouts/15/Doc.aspx?sourcedoc=%7BE8D356F4-09CF-4297-A6ED-213B53CE25BE%7D&file=ARES%20Lightning%20Networking%20Session.docx&fromShare=true&action=default&mobileredirect=true https://usaf.dps.mil/:w:/r/teams/FlightOpsAll-ARESMarketResearch/_layouts/15/Doc.aspx?sourcedoc=%7BE8D356F4-09CF-4297-A6ED-213B53CE25BE%7D&file=ARES%20Lightning%20Networking%20Session.docx&fromShare=true&action=default&mobileredirect=true https://usaf.dps.mil/:w:/r/teams/FlightOpsAll-ARESMarketResearch/_layouts/15/Doc.aspx?sourcedoc=%7BE8D356F4-09CF-4297-A6ED-213B53CE25BE%7D&file=ARES%20Lightning%20Networking%20Session.docx&fromShare=true&action=default&mobileredirect=true https://usaf.dps.mil/:w:/r/teams/FlightOpsAll-ARESMarketResearch/_layouts/15/Doc.aspx?sourcedoc=%7BE8D356F4-09CF-4297-A6ED-213B53CE25BE%7D&file=ARES%20Lightning%20Networking%20Session.docx&fromShare=true&action=default&mobileredirect=true https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11-202v1/afman11-202v1.pdf https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11-202v1/afman11-202v1.pdf https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11-202v1/afman11-202v1.pdf https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11-202v2/afman11-202v2.pdf https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11-202v2/afman11-202v2.pdf https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11-202v2/afman11-202v2.pdf https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11-202v2/afman11-202v3.pdf https://static.e-publishing.af.mil/production/1/af_a3/publication/afman11-202v2/afman11-202v3.pdf https://static.e-publishing.af.mil/production/1/af_a3/publication/afi11-200/afi11-200.pdf https://static.e-publishing.af.mil/production/1/af_a3/publication/afi11-200/afi11-200.pdf