16 Attachment 01_Statement of Objective.pdf

Page | 1

AJW-L500, Product Services Group Federal Aviation Administration

Statement Of Objectives Date: 7.15.2024

ATLAS

AIT Tools for Logistics

Alignment at Scale Prepared By Megan Jones ATLAS Product Owner

Page | 2

Table of Contents

I. Background & Introduction

II. Problem(s) to be Solved

III. Product Vision

IV. Product Approach & Agile Methodology

A. Program Increments & Epics

B. Global Features

C. Activities, Intakes, Assets/Objects & Documents

1. Activities

2. Intakes

3. Assets and Objects

4. Documents

V. Anticipated Period of Performance

VI. Place of Performance

VII. Travel

VIII. System Environment

A. Environment

B. Tech Stack

1. Essential

2. Available

IX. Government Furnished Equipment & Network Access

X. Scope

A. Statement of Work

B. Discovery

C. Guidance

D. Configuration & Implementation

E. Data

F. Documentation

G. Training & Ongoing Support

H. Exclusions from Scope

XI. Deliverables

Page | 3

XII. Qualifications, Accreditation & Clearance

A. Atlassian Partnership, Specializations, and Accreditation

1. Atlassian Platinum Partnership

2. Atlassian Information Technology Service Management (ITSM) Specialization

3. Atlassian Agile At Scale Specialization

4. Atlassian Certified Associate (ACA) and Atlassian Certified Professional (ACP)

B. Security Clearance(s)

XIII. Key Personnel

A. Agency Team

1. Agency Product Owner (APO)

2. Agency Technical Lead (ATL)

3. Scrum Master (SM)

4. Development Team Members

B. Contractor Team

1. Product Owner (PO)

2. Technical Lead (TL)

3. Development Team Members

4. Contractor Team Approval

Page | 4

I. Background & Introduction The Federal Aviation Administration Product Services Group (AJW-L500) (hereinafter referred to as “the Agency” or “AJW-L500”) provides acquisition, logistics, preventative maintenance (PM), corrective maintenance (CM), installation and overhaul, systems engineering, and procurement services for multiple interagency FAA partners, including National Airspace Systems (NAS), National Airspace Defense (NDP), Department of Defense (DoD), Customs and Border Protection (CBP), United States Forest Service (USFS), and the United States Coast Guard (USCG).

Portfolio, Program, and Project management spans over thirty (30) discrete programs, accomplishing more than 450 projects per year, with more than 5000 supporting tasks and deliverables completed by over 300 group members organized into more than 25 sub-teams.

II. Problem(s) to be Solved Work is currently accomplished through multiple legacy systems of record, planning, and execution tools, many of which are desktop applications. Siloed teams experience gaps and overlaps in effort and perpetual lapses in data integrity due to disparate data sets. Consolidated planning, tracking, and forecasting require extensive efforts to collect and standardize data before it can be analyzed and rendered actionable.

III. Product Vision For FAA Logistics Center personnel

Who empower government missions through best-in-class Operations and Logistics services, AIT Tools for Logistics Alignment at Scale (ATLAS)

Is a web and mobile-accessible application suite

That consolidates all mission-critical activities and information into a single environment.

Unlike the current approach using multiple legacy systems of record, manual and paper processes, and disparate data sets, ATLAS utilizes standardized data collection and intake tools and customized automated workflows to plan, track, and manage the execution of Portfolio, Program, and Project financial and operational activities, provides near-real time metrics and dashboard visualization, and centralized knowledge and information management.

IV. Product Approach & Agile Methodology This solutions development project will use agile development principles, with robust documentation, human-centered design, and an extensible infrastructure via the Agency Horizon DevSecOps toolchain.

The Agency expects that the development process will be collaborative and iterative, with open, regular, and frequent communication between the Agency and the Contractor. The Agency expects that the development process will consist of 2-week sprint cycles.

Page | 5

The Agency expects that the initial phases of development will focus on user research and identity/access management.

A. Program Increments & Epics The Agency anticipates four (4) Program Increments under this statement of objectives. Targeted processes will be grouped into high-level Epics. The Epic backlog includes, but is not limited to:

PI 1 – Financial Planning and Tracking (Budget and Revenue)

PI 2 – Procurement Actions and Financial Registers

PI 3– Service Order Agreement Initiation, Project Planning, Estimating & Execution

PI 4 – Capacity Planning, Hiring Actions, and Field Visits (Preventative (PM) & Corrective Maintenance

(CM)

B. Global Features The Agency expects that all processes delivered within each Epic will include with the following global features:

• Process Metrics

• Process Dashboard(s)

• Scrum or Kanban Boards

• Task Management

• Automated Workflows

• Notifications & Alerts

• Authenticated Approvals and eSignature

• PDF Document Creation

• Document Repositories

• Knowledge Management & Information Sharing

• Single Occurrence Data Migration, when applicable

• Continuous Data Integration, when applicable

C. Activities, Intakes, Assets/Objects & Documents

1. Activities

Jira (and Atlassian Marketplace extensions, when applicable) will be used to manage Process activities and tasks.

Examples of activities and tasks include, but are not limited to:

• Assigned Trainings & Certifications

• Security Clearance management

• Contract purchases

• Credit Card purchases

Page | 6

• Engineering tasks (engineering change proposals, tech refresh planning, spares modeling, ATO data calls)

• Employee goal setting

• Funds approvals and certifications

• Hiring Actions

• Interagency Agreement (IAA) Initiation, Negotiation, and Approval

• Invoicing and Revenue Generation

• Joint Acceptance Inspections

• Meetings

• Part profile creation and maintenance

• Parts order, delivery, and return

• Performance Reviews

• Program Management Reviews

• Project estimating and resource planning

• Field Operations (maintenance, repair, overhaul, installation, and acquisition of fielded structures and technology)

• Reporting

• Resource and capacity management (both personnel and equipment)

• Scheduling

• Service Order Agreement (SOA) Initiation, Negotiation, and Approval

• Transportation of goods and materials

• Travel

2. Intakes Jira Service Management (and applicable Atlassian Marketplace extensions, when applicable) will be used as the primary gateway for intakes. Examples of intakes include but are not limited to:

• Data Calls

• Engineering and system changes

• Incident reporting and management

• Overtime/Comp Time Requests

• Procurement actions

• Service requests

• Site Surveys

• System Access Requests

• Time Off Requests

• Training requests

• Travel requests

3. Assets and Objects Assets and Objects (and Atlassian Marketplace extensions, when applicable) will be used manage a variety of resources. Examples of assets/objects include, but are not limited to:

Page | 7

• Fielded Structures

• Fielded Technology

• Fleet vehicles

• Hand Tools

• Heavy Equipment & Machinery

• Interagency Agreements (IAAs)

• Job Order Numbers (JONs)

• Lines of Accounting

• Personal Protective Equipment (PPE)

• Personnel and Teams

• Portfolios

• Programs

• Projects

• Schedules

• Service Order Agreements (SOAs)

• Service Areas, Regions, and Sites

• System Configurations

4. Documents Confluence (and applicable Atlassian Marketplace extensions) will be used for document creation and storage, as well as information management and knowledge-sharing. Examples of documents include, but are not limited to:

• Activity Reports

• Continuity Plans

• Deficiency Reports

• Desktop References

• Engineering Change Proposals (ECPs)

• Independent Government Cost Estimate (IGCE)

• Interagency Agreements (IAAs)

• Job Analysis Tools (JAT)

• Maintenance Action Reports

• Meeting Minutes & Summaries

• Micro-learning videos

• Permits

• Photos and images

• Portfolio Review slide decks

• Process Flow Charts

• Procurement Records

• Program Management Reviews (PMRs) slide decks

• Quotes & Rough Order Magnitude (ROMs)

• Statements of Work

Page | 8

• Service Order Agreements (SOAs)

• Site & System Diagrams

• Site Surveys

• Trip Reports

• Work Instructions

These preliminary examples provided above (Process Epics, Global Features, Activities, Intakes, Assets/Objects, and Documents) are provided only for illustrative purposes, and do not comprise the full scope or detail of the project. The Agency expects that the Contractor will work closely with the Agency Product Owner to perform regular user research and usability testing, and to develop and prioritize a full gamut of epics, features, and user stories as the period of performance progresses.

Individual epics, features, and user stories may be modified, added, retracted, or reprioritized by the Agency at any time, and the Agency expects that the user stories will be continuously refined during the development process.

V. Anticipated Period of Performance The period of performance shall be one year, with FAA options to extend for up to one additional year.

VI. Place of Performance The Contractor may choose the location(s) from which to perform the required services. AJW-L500 hours of operation are 7:00 a.m. to 3:30 p.m. Central Standard Time. The AJW-L500 Product Owner and any other necessary FAA representatives will be available to confer with Contractor representatives daily during the period of performance, either by telephone or by video connection.

VII. Travel Travel may be required to complete tasks assigned, particularly with respect to discovery and user research phases of implementation. When required, the travel destinations will primarily be (but are not limited to):

• FAA Logistics Center, Mike Moroney Aeronautical Center, Oklahoma City, OK

• FAA Headquarters in Washington, DC

VIII. System Environment A. Environment The AIT Horizon Toolchain is an existing DevSecOps toolchain owned and managed by the Agency.

Horizon is hosted on the Agency AWS Hybrid-Cloud infrastructure, in a FedRAMP authorized, FISMA-moderate environment.

Horizon is utilized by approximately 6000 users across the Federal Aviation Administration and is supported by the DevSecOps tools listed below under Tech Stack.

Page | 9

B. Tech Stack

1. Essential

The following DevSecOps tools are critical to the outcome of this project.

• Atlassian Data Center Marketplace Extensions, including but not limited to:

o ConfiForms o Draw.io o Jira Data Center o Jira Assets Data Center o Jira Service Management Data Center o Power BI Connector o Scriptrunner o Tempo Structure Bundle o Tempo Timesheets

• Confluence Data Center

• Ansible

• Ansible Tower

• Jenkins

• Jfrog Artifactory + Xray

• GitOps

2. Available The following DevSecOps tools are part of the toolchain and are available for project use but are not categorized as critical to the outcome of this project.

• BitBucket (ASP.net, Java, node.js)

• DataDog

• Docker

• MS Build

• SonarQube

• Terraform

• Tyrion

IX. Government Furnished Equipment & Network Access The government will furnish Contractor personnel with laptops appropriate for accomplishing project tasks, as well as PIV badge access to the FAA Mission Support Network.

X. Scope The scope of this effort is defined by the “Product Vision” section above. The contractor will develop and deliver solutions consistent with the Product Vision through the following service categories:

• Statement of Work

Page | 10

• Discovery

• Guidance

• Configuration & Implementation

• Data

• Documentation

• Training & Ongoing Support

A. Statement of Work The contractor will develop a Statement of Work (SOW) and incorporate the requirements of this Statement of Objective (SOO) into the contractors SOW.

B. Discovery The Contractor must begin this project by exploring and pinpointing the needs of AJW-L500 users, and the ways that the Atlassian-based solutions support their individual and organizational missions. The Contractor shall ensure holistic understanding of roles belonging to AJW-L500 and the ways in which individuals who fill those roles will interact with Atlassian solutions, including the actions they take online, through a mobile application if applicable, on a phone, or in person. Every encounter, whether online or offline, should move AJW-L500 users closer to their goal. The Contractor shall continually test configurations with real people to ensure delivery is focused on what is important.

C. Guidance The Contractor will conduct needs assessments to ensure holistic understanding of AJW-L500 goals, business model, user groups, existing workflow processes, deliverables, and reporting methods, tools, and systems of record.

The Contractor will provide guidance regarding Atlassian license requirements, as well as any third-party applications required to consolidate and migrate Program Management and Service Order Financial Operations into a single environment with the required Global Features ((see “Global Features,” Section IV.B, above). The Contractor will provide guidance regarding solution and data architecture for collected data, as well as dashboard design and data visualization strategies.

D. Configuration & Implementation The Contractor will provide configuration of Atlassian and, if indicated, third-party applications, following installation. The Agency expects that prioritized processes for workflow automation will be delivered with Global Features (see “Global Features,” Section IV.B, above) in no less than 8 weeks per process.

Configuration includes but is not limited to the following:

• Assets and object schemas

• Project schemas

• Issue schemas

• Screen schemas

• Field schemas

• Workflow schemas and automation

Page | 11

• AQL queries

• JQL queries

• Scrum/Kanban project board(s)

• Confluence space(s)

• JSM Intake forms

• GitOps deployment tools and methodologies

• Development, as needed and defined in collaboration with the Agency

The Implementation Window will include User Research, Solution Design/Configuration, User Testing, and Implementation, Technical Documentation, and Training (Atlassian Administration, Project & Space Administration, and End-User Training).

E. Data The Contractor will collaborate with the Agency’s internal scrum team to provide integration of existing data into ATLAS. Data Integration may include the following sub-tasks:

• Cleansing

• Normalization

• Adaptation

• Continuous Data Integration

• Single Occurrence Migration

Continuous Data Integration may be derived from the following sources, including but not limited to:

• PRISM

• Delphi

• UTBS (Microsoft Access financial database)

• Checkbook (Microsoft Access procurement database)

• LCSS (Logistics System)

• WMS (Warehouse System)

• DCRS (Attendance & Time-Keeping System)

• Miscellaneous Existing SQL server databases owned and maintained by the Agency

The Contractor will provide single-occurrence migration and incorporation of existing data from the following sources, including but not limited to:

• Smartsheet

• Excel

• Microsoft Project

• Other siloed data sources, as indicated

F. Documentation The Agency intends that all software configurations and documentation delivered by the Contractor will be owned by the Agency. This includes, but is not limited to, data, documents, graphics, code, plans, Page | 12 reports, schedules, schemas, metadata, architecture designs, and the like. Documentation will be created or upload daily and maintained in a GitOps environment provided by the Agency.

G. Training & Ongoing Support The Contractor will provide ongoing support for up to 60 hours per month for six (6) months following the implementation of epics and features. Ongoing support will include:

• Health Checks

• Coaching

• Add-On Reviews

• Script Reviews

• Automation Reviews

H. Exclusions from Scope Costs and activities associated with a hosting environment are excluded from scope. Licensing procurement and costs are excluded from scope.

XI. Deliverables The following chart sets forth the performance standards and quality levels the code and documentation provided by the Contractor must meet, and the methods the Agency will use to assess the standard and quality levels of that code and documentation.

Deliverable Due By Assessment Method Performance Standard(s) User Research End of

Sprint The Agency will manually evaluate the artifacts based on a research plan provided by the contractor at the end of the second sprint and every applicable sprint thereafter.

Research plans and artifacts from usability testing and/or other research methods with end users are available at the end of every applicable sprint, in accordance with the contractor’s research plan.

Usability testing and other user research methods must be conducted at regular intervals throughout the development process (not just at the beginning or end).

Product Backlog

End of Sprint

Manual review and refinement in collaboration with Agency PO

Epics, Features, User Stories, and Enablers will be created and managed in Jira and must be composed using Scaled Agile Framework (SAFe) best practices, including acceptance criteria.

Sprint Demos End of Sprint

Sprint goals and outcomes will be demoed live to Agency stakeholders upon the completion of each sprint.

Sprint demos will occur on the final day of each sprint and must include Agency PO, Agency Technical Lead, Contractor PO, Contractor Technical Lead, and any applicable and identified AJW-L500 process stakeholders.

Documentation End of Sprint

Combination of manual review and automated testing, if available

All dependencies are listed, and the licenses are documented. Major functionality in the software/source code is documented. Individual methods are documented inline in a format that permit the use of tools such as JSDoc. System diagram is provided.

Tested Code End of Sprint

Combination of manual review and automated testing

Code delivered under the order must have substantial test code coverage. Version-controlled

Page | 13

The Agency will have a period of one week within an iteration (“Evaluation Period”) after increments of a deliverable have been provided to verify that the Deliverable or part thereof is not deficient per acceptance criteria. The Agency should notify the Contractor prior to the expiration of the relevant Evaluation Period if the Deliverable or part thereof is deficient in any material respect (a “non-conformity” pursuant to the definition of done or acceptance criteria agreed upon by the parties). The Contractor will correct such Nonconformity as soon as reasonably practical but no longer than the length of one iteration, whereupon The Agency will receive an additional Iteration period (“Verification Period”) commencing upon its receipt of the corrected Deliverables or part thereof to verify that the specific non-conformity has been corrected.

XII. Qualifications, Accreditation & Clearance Worked performed and delivered under this Statement of Objectives will take place in the Horizon DevSecOps Toolchain, described above in “Environment”. Contractors will be working in the Agency’s Test and Staging environments with pre-existing tools. Staged and deployed changes delivered under this Statement of Objectives will impact Federal Aviation Administration users and missions outside of AJW-L500. Therefore, configuration changes made by the Contractor must be scanned, reviewed, and deployed via GitOps in collaboration and cadence with the Horizon SysAdmin team, using Scaled Agile Framework best practices.

A. Atlassian Partnership, Specializations, and Accreditation The Contractor must meet the following qualifications:

1. Atlassian Platinum Partnership

2. Atlassian Information Technology Service Management (ITSM) Specialization

3. Atlassian Agile At Scale Specialization

4. Atlassian Certified Associate (ACA) and Atlassian Certified Professional (ACP)

Scrum Team members assigned to tasks under this Statement of Objectives must hold the appropriate Atlassian Certified Associate (ACA) and Atlassian Certified Professional (ACP)

Horizon GitHub repository of code that comprises product that will remain in the government domain.

Minimum of 90% test coverage of all code. All areas of code are meaningfully tested.

Deployed Configurations & Code

End of Sprint

Combination of manual review and automated testing

Configurations and code must successfully build and deploy into Staging environment with a single command

User Accessibility

End of Sprint https://github.com/pa11y/pa11y

Web Content Accessibility Guidelines 2.1 AA standards; 0 errors reported using an automated scanner and 0 errors reported in manual testing

Security End of Sprint

Clean tests from a static testing through the Horizon Toolchain, along with documentation explaining any false positives

Meets or exceeds Agency quality gate standards

Page | 14 accreditations for the work products they are designing, configuring, implementing, and documenting, to include but not limited to:

a) Atlassian Certified Professional Certificates

• Jira Administration for Data Center (ACP-100)

• Managing Jira Projects for Data Center (ACP-610)

• Managing Jira Service Management Projects for Cloud (ACP-420)

b) Atlassian Certified Associate Certificates

• ITSM with Jira Service Management Foundations

• Jira Software Board Configuration

• Jira Software Essentials

• Confluence Essentials

B. Security Clearance(s) Configuration, implementation, and documentation will be conducted using the Horizon DevOps toolchain, which sits on the Federal Aviation Mission Support Network. Therefore, all contractor personnel participating with tasks covered in this SOW must apply for and obtain security clearances from both FAA (DOT) and CBP (DHS). The Contractor must ensure a Tier 1 NACI background investigation is completed for all contract employees. Contract employees must successfully pass the required security investigations to maintain assignment to the project.

When a contract employee receives BI beyond NACI there is a cost to the government. The contractor employee must remain in support of the activity for which the additional BI is obtained for the duration of period of performance, including through the option year, if elected by the Agency.

All Contractor personnel assigned to project tasks that require access to interagency partner facilities, information systems, security items, and products, sensitive unclassified, and/or classified information must be U.S. citizens.

XIII. Key Personnel The ATLAS Product Team will be comprised of the Agency Product Team and the Contractor’s Key Personnel and Development Team.

A. Agency Team The Agency will designate a Product Team comprised of the following roles:

1. Agency Product Owner (APO) The APO will be a direct liaison to the Contractor Team and to Agency Stakeholders. The APO will work collaboratively with the Contractor PO and Technical Leads to identify and document Epic and Feature backlogs. The APO will own prioritization responsibility for these backlogs.

Page | 15

2. Agency Technical Lead (ATL) The ATL will be a senior member of the Horizon DevSecOps team and will have a full understanding of the Horizon stack and DevSecOps policies and approaches.

3. Scrum Master (SM) The SM is a direct liaison to the APO and ATL. The SM will support the ATLAS Product Team to generate and manage ATLAS user and enabler stories in an Issue Backlog. The SM will own prioritization responsibilities for the Issue Backlog. The SM will set the cadence for Stand Ups, Backlog Refinements, Retrospectives, and Demos and will facilitate these ceremonies for the ATLAS Product Team.

4. Development Team Members The Agency will also provide a development team comprised of at least one (1) data engineer and three (3) software engineers. The development team will work collaboratively and in cadence with Horizon DevSecOps and the Contractor team.

B. Contractor Team The Contractor must designate both a Product Owner (PO) and a Technical Lead as Key Personnel for this effort.

1. Product Owner (PO) The PO will be a direct liaison to the Agency product team and will be responsible for the supervision and management of all of the contractor’s personnel.

2. Technical Lead (TL) The Technical Lead must have a full understanding of the technical approach to be used by the Contractor’s development team and will be responsible for ensuring that the Contractor’s development team follows that approach.

Key Personnel substitutions must be approved by the Agency in writing, and will only be justified by an Agency request, sudden illness, death, change of employment, or termination of employment for cause. Contractor requests for a substitution of Key Personnel must include a detailed explanation of the justifying circumstances, and a complete résumé for the proposed substitute or addition, including skills, experience, education, training, and security level. The Agency’s failure to approve a proposed substitution will not constitute grounds for non-performance by the Contractor or form a valid basis for any claim for money or any equitable adjustment.

3. Development Team Members The Contractor will provide development team members with requisite experience and Atlassian Accreditations and Certifications.

Page | 16

4. Contractor Team Approval Each member of the team proposed by the Contractor must be approved in advance by the Agency before starting work. The Agency may withhold approval, or at any time revoke a prior approval, for any reason. For each member of the development team proposed by the Contractor, the Contractor must provide the Agency with Atlassian Certified Associate and Atlassian Certified Professional accreditation identification number(s) and expiration date(s) for verification of accreditation. As mentioned in “Qualifications, Accreditation & Experience: Security Clearance,” all proposed Contractor team members must successfully complete a Public Trust and a High-Risk Law Enforcement Sensitive clearance to be approved by the Agency.

B. Security Clearance(s)