693KA9-24-R-00009 Amendment 0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

5. PROJECT NO. (If applicable)2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ.NO.

PAGE OF PAGES

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6)

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

CODE

9A. AMENDMENT OF SOLICITATION NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended , by one of the following methods: (a) By completing

Items 8 and 15, and returning is extended, is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required.)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(x) A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO THE AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation date, etc.) SET FORTH IN ITEM 14.

E. IMPORTANT: Contractor is not, X is required to sign this document and return

ORDER NO. IN ITEM 10A.

1 2

0001 03/20/2024

AAQ-420 EXECUTIVE OFFICE BRANCH A

Orville Wright Bldg. (FOB10A), Room 406 FAA National Headquarters 800 Independence Ave., SW

AAQ420-AFN

Washington DC 20591 x

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

separate letter or telegram which includes a reference to the solicitation and amendment number. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE RECEIVED AT

THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted , such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By ___________ 1 x x

693KA9-24-R-00009

1 copies to the issuing office.

01/10/2024

(x)

693KA9-24-R-00009 Amendment 0001

The purpose of this amendment is to revise SIR 693KA9-24-R-00009 with the following changes;

1. Section B and L002 – added the “Technical Specialist” labor category and administrative changes

2. Section C – added C.7.8 “Connect To Additional FAA Applications and Systems”

3. Section D – administrative changes

4. Section G – revised G.8 Billing Instructions

5. Section H – administrative changes

6. Sections I & K – updated clauses per AMS update no. 117 January 2024

Continued ...

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)15A. NAME AND TITLE OF SIGNER (Type or print)

15C. DATE SIGNED 16B. CONTRACT AUTHORITY 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED

(Signature of person authorized to sign) (Signature of Contracting Officer)

Francisco A. Felix

Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect .

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

NAME OF OFFEROR OR CONTRACTOR

2 2

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

(A) (B) (C) (D) (E) (F)

693KA9-24-R-00009/0001

7. Section L – added L.23 requirement for Volume

V – Small-Business Subcontracting Plan (Large

Business only)

8. Section M – added M.5.5 for Volume V –

Small-Business Subcontracting Plan (Large

Business only) evaluation

As a result of this action, SIR 693KA9-24-R-00009 is replace with the attached update and updated

L002 Pricing Worksheet.

The proposal due date changes from March 7, 2024 to April 18, 2024, 2:00PM EDT. No other changes are made.

Federal Aviation Administration (FAA) 800 Independence Avenue SW, Washington, DC 20591

See Section L.4

SOLICITATION, OFFER AND AWARD 1. THIS CONTRACT IS A RATED ORDER RATING

UNDER DPAS (15 CFR 7900)

PAGE OF PAGES

1 150

2. CONTRACT NUMBER

3. SOLICITATION NUMBER

693KA9-24-R-00009

4. RESERVED 5. DATE ISSUED

6. REQUISITION/PURCHASE NUMBER

N/A

7. ISSUED BY CODE AAQ420-AFN 8. ADDRESS OFFER TO (If other than item 7)

9. See Section L for proposal submittal instructions.

SOLICITATION

CAUTION - LATE Submissions, Modifications, and Withdrawals: See Section L of Submittals, AMS 3.2.2.3-14. All offers are subject to all terms and conditions contained in this solicitation.

10. FOR

INFORMATION

CALL:

A. NAME

Toloria J. Crawford

B. TELEPHONE (NO COLLECT CALLS) C. E-MAIL ADDRESS

Toloria.J.Crawford@faa.gov

AREA CODE

NUMBER

EXT.

11. TABLE OF CONTENTS

(X) SEC. DESCRIPTION PAGE(S) (X) SEC. DESCRIPTIO

N

PAGE(S)

PART I - THE SCHEDULE PART II - CONTRACT CLAUSES

A SOLICITATION/CONTRACT FORM 1

I CONTRACT CLAUSES 66-108

B SUPPLIES OR SERVICES AND PRICES/COSTS 2-12 PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

C DESCRIPTION/SPECS./WORK STATEMENT 13 -36

J LIST OF ATTACHMENTS 109

D PACKAGING AND MARKING 37 PART IV - REPRESENTATIONS AND INSTRUCTIONS

E INSPECTION AND ACCEPTANCE 38

K REPRESENTATIONS, CERTIFICATIONS AND

OTHER STATEMENTS OF OFFERORS 110-125

F DELIVERIES OR PERFORMANCE 39-41

G CONTRACT ADMINISTRATION DATA 42-48

L INSTRS., CONDS., AND NOTICES TO OFFERORS 126-141

H SPECIAL CONTRACT REQUIREMENTS 40-65

M EVALUATION FACTORS FOR AWARD 142-149

OFFER (Must be fully completed by offeror)

NOTE: Item 12 does not apply if the solicitation includes the provisions at AMS 3.2.2.3-2, Minimum Offer Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, AMS 3.3.1-6)

10 CALENDAR DAYS (%) 20 CALENDAR DAYS (%) 30 CALENDAR DAYS (%) CALENDAR DAYS(%)

14. ACKNOWLEDGMENT OF AMENDMENTS

(The offeror acknowledges receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

AMENDMENT NO. DATE AMENDMENT NO. DATE

0001 03/20/2024

15A. NAME AND

ADDRESS

OF OFFER-

OR

CODE FACILITY 16. NAME AND THE TITLE OF PERSON AUTHORIZED TO SIGN OFFER

(Type or print)

TBD

15B. TELEPHONE NUMBER 15C. CHECK IF REMITTANCE ADDRESS IS

DIFFERENT FROM ABOVE - ENTER SUCH

ADDRESS IN SCHEDULE.

17. SIGNATURE 18. OFFER DATE

AREA CODE NUMBER EXT.

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. RESERVED 23. SUBMIT INVOICES TO ADDRESS SHOWN IN ITEM

(4 copies unless otherwise specified)

24. ADMINISTERED BY (If other than Item 7) 25. PAYMENT WILL BE MADE BY CODE

26. NAME OF CONTRACTING OFFICER (Type or print) 27. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

28. AWARD DATE

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

OMB Control No. 2120-0595 (SF-33) FAA Template No. 2 (07/17 mailto:oloria.j.crawford@faa.gov

SIR No. 693KA9-24-R-00009 Section B - Supplies or Services and Price/Cost

PART I - SECTION B

SUPPLIES/SERVICES & PRICE/COST

B.1 GENERAL

The Federal Aviation Administration (FAA) has a requirement to provide a workforce scheduling system with the ability to manage the schedules of 20,000 employees with expansion capability to 40,000. This system will be implemented across multiple workforces, including but not limited to FAA Air Traffic Organizations’ air traffic controller and air traffic technician workforces, and the Air Traffic Academy. The Contractor must provide all management, supervision, labor, software, facilities, equipment, material supplies, and services (except as may be expressly set forth in this contract as furnished by the Government) and otherwise do all things necessary for, or incident to, the performance of the service solutions set forth under Section C, Statement of Work. The contractor will be subject to all terms and conditions of this contract.

This procurement will be a full and open competition with a single award envisioned.

B.2 BASE AND OPTION PERIODS

The term of this contract includes a two-year Base Period and five (5) one-year Option Periods for a total period of performance (POP) of up to seven (7) years.

Base Period: TBD Option Period 1: TBD Option Period 2: TBD Option Period 3: TBD Option Period 4: TBD Option Period 5: TBD

B.3 CONTRACT TYPE

Hybrid Firm Fixed Price (FFP) / Time and Materials (T&M)

B.4 PRICING / CLIN STRUCTURE

The following section provides the Pricing/CLIN structure for this contract. Services performed under all CLINs in this Section must be in accordance with Section C, Statement of Work.

Base Period: TBD

CLIN 0001 Workforce Scheduling Tool (T&M)

Consisting of Sub-CLINs 0001AA and 0001AB

Sub-CLIN 0001AA System Design, Test & Evaluation (SOW C.4, C.5 C.6 and C.7.1-3)

Labor Category Fixed

Hourly Rate

Estimated Hours*

Total Estimated Price

Project Manager $ xx $ xxx Software Engineer $ xx $ xxx Programmer $ xx $ xxx Tester $ xx $ xxx Technical Writer $ xx $ xxx Technical Specialist $ xx $ xxx Total $ xxx

* Yearly estimates proposed by Offeror

Sub-CLIN 0001AB Engineering Services (SOW C.7.7)

Labor Category Fixed Hourly Rate

Estimated Hours**

Total Estimated Price

Project Manager $ xx $ xxx Software Engineer $ xx $ xxx Programmer $ xx $ xxx Tester $ xx $ xxx Technical Writer $ xx $ xxx Technical Specialist $ xx $ xxx Total $ xxx

** Yearly estimates provided by FAA

CLIN 0002 Software Licenses (FFP)

Description Quantity Range Unit Price (each)

Software Licenses 01 - 49 xx Software Licenses 50 - 99 xx Software Licenses 100 - 249 xx Software Licenses 250 - 499 xx Software Licenses 500 - 999 xx Software Licenses 1,000 – 5,000 xx Software Licenses Enterprise wide xx

Note: The FAA plans to acquire a minimum of fifty (50) Software Licenses in the Base Year.

CLIN 0003 Software Maintenance (SOW C.7.4 - C.7.6) (FFP)

Software Maintenance 01 - 49 xx Software Maintenance 50 - 99 xx Software Maintenance 100 - 249 xx Software Maintenance 250 - 499 xx Software Maintenance 500 - 999 xx Software Maintenance 1000 – 5,000 xx Software Maintenance Enterprise

CLIN 0004 Travel

CLIN Estimated Travel

0004 xx

CLIN 0005 Materials / Other Direct Costs

CLIN Estimated Materials / ODC

0005 xx

Option One Period: TBD

CLIN 1001 Engineering Services (T&M)

Sub

CLIN

Labor Category Fixed Hourly Rate

Estimated Hours

Total Estimated Price

1001AA Project Manager $ xx $ 1001AB Software Engineer $ xx $ 1001AC Programmer $ xx $ 1001AD Tester $ xx $ 1001AE Technical Writer $ xx $ 1001AF Technical Specialist $ xx $

Total xxx $

CLIN 1002 Software Licenses (FFP)

Software Licenses 01 - 49 xx Software Licenses 50 - 99 xx Software Licenses 100 - 249 xx Software Licenses 250 - 499 xx Software Licenses 500 - 999 xx Software Licenses 1,000 – 5,000 xx Software Licenses Enterprise

CLIN 1003 Software Maintenance Pricing (FFP)

Software Maintenance 01 - 49 xx Software Maintenance 50- 99 xx Software Maintenance 100 - 249 xx Software Maintenance 250 - 499 xx Software Maintenance 500 - 999 xx Software Maintenance 1000 – 5,000 xx Software Maintenance Enterprise

CLIN 1004 Travel

1004 xx

CLIN 1005 Materials / Other Direct Costs

1005 xx

Option Two Period: TBD

CLIN 2001 Engineering Services (T&M)

Labor Category Fixed

Hourly Rate

Estimated Hours

Total Estimated Price

2001AA Project Manager $ xx $ 2001AB Software Engineer $ xx $ 2001AC Programmer $ xx $ 2001AD Tester $ xx $ 2001AE Technical Writer $ xx $ 2001AF Technical Specialist $ xx $

CLIN 2002 Software License Pricing (FFP)

Software Licenses 01 - 49 xx Software Licenses 50 - 99 xx Software Licenses 100 - 249 xx Software Licenses 250 - 499 xx Software Licenses 500 - 999 xx Software Licenses 1,000 – 5,000 xx Software Licenses Enterprise

CLIN 2003 Software Maintenance Pricing (FFP)

Software Maintenance 01 - 49 xx Software Maintenance 50 - 99 xx Software Maintenance 100 - 249 xx Software Maintenance 250 - 499 xx Software Maintenance 500 - 999 xx Software Maintenance 1000 – 5,000 xx Software Maintenance Enterprise

CLIN 2004 Travel

CLIN Estimated Travel Requirements

2004 xx

CLIN 2005 Materials / Other Direct Costs

2005 xx

Option Three Period: TBD

CLIN 3001 Engineering Services (T&M)

Labor Category Fixed Hourly Rate

Estimated Hours

Total Estimated Price

3001AA Project Manager $ xx $ 3001AB Software Engineer $ xx $ 3001AC Programmer $ xx $ 3001AD Tester $ xx $ 3001AE Technical Writer $ xx $ 3001AF Technical Specialist $ xx $

CLIN 3002 Software License Pricing (FFP)

Software Licenses 01 - 49 xx Software Licenses 50 - 99 xx Software Licenses 100 - 249 xx Software Licenses 250 - 499 xx Software Licenses 500 - 999 xx Software Licenses 1,000 – 5,000 xx Software Licenses Enterprise

CLIN 3003 Software Maintenance Pricing (FFP)

Software Maintenance 01 - 49 xx

Software Maintenance 50 - 99 xx Software Maintenance 100 - 249 xx Software Maintenance 250 - 499 xx Software Maintenance 500 - 999 xx Software Maintenance 1000 – 5,000 xx Software Maintenance Enterprise

CLIN 3004 Travel

3004 xx

CLIN 3005 Materials / Other Direct Costs

3005 xx

Option 4 Period: TBD

CLIN 4001 Engineering Services (T&M)

Labor Category Fixed Hourly Rate

Estimated Hours

Total Estimated Price

4001AA Project Manager $ xx $ 4001AB Software Engineer $ xx $ 4001AC Programmer $ xx $ 4001AD Tester $ xx $ 4001AE Technical Writer $ xx $ 4001AF Technical Specialist $ xx $

CLIN 4002 Software License Pricing (FFP)

Software Licenses 01 - 49 xx Software Licenses 50 - 99 xx Software Licenses 100 - 249 xx

Software Licenses 250 - 499 xx Software Licenses 500 - 999 xx Software Licenses 1,000 – 5,000 xx Software Licenses Enterprise

CLIN 4003 Software Maintenance Pricing (FFP)

Software Maintenance 01 - 49 xx Software Maintenance 50 - 99 xx Software Maintenance 100 - 249 xx Software Maintenance 250 - 499 xx Software Maintenance 500 - 999 xx Software Maintenance 1000 – 5,000 xx Software Maintenance Enterprise

CLIN 4004 Travel

4004 xx

CLIN 0005 Materials / Other Direct Costs

4005 xx

Option Five Period: TBD

CLIN 5001 Engineering Services (T&M)

Labor Category Fixed Hourly Rate

Estimated Hours

Total Estimated Price

5001AA Project Manager $ xx $ 5001AB Software Engineer $ xx $

5001AC Programmer $ xx $ 5001AD Tester $ xx $ 5001AE Technical Writer $ xx $ 5001AF Technical Specialist $ xx $

CLIN 5002 Software License Pricing (FFP)

Software Licenses 01 - 49 xx Software Licenses 50 - 99 xx Software Licenses 100 - 249 xx Software Licenses 250 - 499 xx Software Licenses 500 - 999 xx Software Licenses 1,000 – 5,000 xx Software Licenses Enterprise

CLIN 5003 Software Maintenance Pricing (FFP)

Software Maintenance 01 - 49 xx Software Maintenance 50 - 99 xx Software Maintenance 100 - 249 xx Software Maintenance 250 - 499 xx Software Maintenance 500 - 999 xx Software Maintenance 1000 – 5,000 xx Software Maintenance Enterprise

CLIN 5004 Travel

0004 xx

CLIN 5005 Materials / Other Direct Costs

0005 xx

B.5 CONTRACT PRICING

The following section describes pricing requirements for Time and Materials (T&M) and Fixed- Price (FP) CLINs.

B.5.1 Time-and-Materials (T&M) Pricing

(a) Billing Rates The labor rates in Section B.4 reflect fully burdened hourly rates for each labor category and will apply to all direct labor hours regardless of whether the labor hour is expended by the contractor or by one of its subcontractors. The labor rates include direct labor and all indirect costs applicable, including fringe benefits, overhead, G&A, and profit.

(b) Contractor Site Rates All labor billing rates are based on Contractor site locations. These fully-burdened labor rates must include applicable indirect costs for office space and all normal supplies and services required to support the work. This includes, but is not limited to, telephones, copiers, personal computers, postage, ordinary business software, such as word processing, spreadsheets, graphics, etc., normal copying and reproduction costs.

(c) Labor Hours The Contractor may deliver 70% to 130% of the hours specified for each labor category without a formal modification as long as the Contractor does not exceed the obligated funding.

(d) No Change to Rates if Subcontractors are Added or Deleted The fixed hourly labor rates represent the blended hourly rates of the Contractor and all of its subcontractors. The fixed hourly labor rates will not change after the contract award even if a subcontractor is removed by the Contractor or a new subcontractor is added by the Contractor to its team.

(e) Materials

1) Materials are defined as:

a) Direct materials;

b) Subcontracts for supplies and incidental services for which there is no labor category specified in the contract;

c) Other direct costs (e.g., incidental services for which there is no labor category specified in the contract, student transportation, printing, shipping, training facility

2) Indirect costs may be applied to materials in accordance with the Contractor’s established accounting practices.

3) The Government will not pay profit on materials.

(f) Travel (T&M) If instructor travel is authorized, travel will be reimbursed at actual direct costs in accordance with the limitations set forth in G.9 Travel Reimbursement. No profit is allowed for travel.

B.5.2 Fixed-Price CLINs

Software Licenses and Software Maintenance fees are Firm Fixed Price at the rates specified in B.4 CLIN Structure, or as negotiated, if lower amounts are proposed.

B.6 ADDITIONAL LABOR CATEGORIES

At any time and throughout the life of the contract, at the request of the Government, the Contractor may propose additional labor categories, rates and descriptions necessary to support training requirements of this contract. These additional labor categories, rates, and descriptions will be negotiated on a case-by-case basis. The additional categories, rates and descriptions proposed, upon determination by the Government that they are necessary for the scope of the effort and that the prices are fair and reasonable, may be incorporated into Section B.4.

(End of Section B)

SIR No. 693KA9-24-R-00009

Section C – Statement of Work

PART I - SECTION C

DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C. Introduction

This Statement of Work (SOW) establishes the performance, interface, test, quality assurance, and maintenance requirements for the Federal Aviation Administration’s (FAA) SCHEDULER TOOL (ST).

C.1 Background

The FAA currently uses a workforce scheduling system that is developed and maintained by the current contractor. The basis of the system is an underlying COTS workforce planning software tool. An attempt was made to implement management and front-line schedule and operations management features within Air Traffic Services including for schedule and operations management for air traffic controllers at FAA air traffic control facilities. However, due to myriad of reasons, the scheduler tool is only in use for limited management functions in approximately twenty air traffic facilities. The tool is currently being implemented in additional FAA lines of business including the Technical Operations technician workforce and for classroom and instructor resource scheduling at the FAA Air Traffic Academy.

The Agency desires to have a ST that is flexible enough to be implemented across multiple workforces, including but not limited to FAA Air Traffic Organizations’ air traffic controller and air traffic technician workforces, and the Air Traffic Academy. The Agency will consider any of the following options with evaluations made based on overall cost to government for development of the ST and ongoing support as well as the ability to meet the high-level requirements:

1. A Commercial Off-The-Shelf (COTS) product that can be customized to meet Agency needs

2. A software development solution

3. A solution that based on continued customization of the tool currently being used by the FAA

The ST is planned to integrate with the following systems during the performance period and these integration efforts will be implemented, as required, under the Engineering Services CLINs.

Key objectives for the ST include the following:

1. Automate workforce related tasks where possible

2. Decrease administrative overhead

3. Optimize resources deployment

4. Increase operational efficiency while adhering to all business and fatigue rules including those agreed to via collective bargaining agreement

5. Enhance management accountability

Legacy Systems Information/Data Elements Mandatory Timekeeping System Employee Information: name, operating initials, area, facility, org code, job title.

Overtime code, Other Duty codes, Leave types, Request types

Payroll / HR System Employee leave balance, Enter On Duty, Service Computation Date, Mandatory Retirement Date

6. Increase employee satisfaction by: improving and simplifying schedule bidding, notifications of changes to schedules and request responses, and remote access to schedule information through a mobile application

7. Improved workflows for items such as overtime and leave management

8. Provide robust, flexible reporting capability

C.2 Scope

This SOW defines the effort required to replace and/or to maintain and enhance scheduling software systems at the FAA. Specific tasks include:

1. Software Design, Development and/or Customization: Design, develop, and/or customize a scheduling system to meet FAA requirements.

2. Software Testing: Prepare test plans (for FAA approval) and perform systems testing.

3. Software Enhancements: Perform additional customization and configuration services as directed by the FAA. The FAA reserves the right to order additional customization and configuration services from the Contractor.

4. Interfaces: Develop interfaces as directed by the FAA.

5. Maintenance: Maintain FAA scheduling systems. Fix software bugs (i.e. software issues that are contained within the Software Requirements documents) within the agreed upon timeframes as identified in a maintenance agreement.

The ST Contractor must be responsible for ensuring that the scheduling systems fulfill the functional and performance requirements provided by the FAA.

C.3 Applicable Documents

The following specifications, orders, and standards form a part of this SOW and are applicable to the extent specified herein. Note – these documents are expected to evolve over the life of this contract and will require periodic updates and additions.

Table 1: Applicable Documents Document Number Title FAA Standards:

Section 508 Rehabilitation Act of 1973, as amended (29CFR 794d) Federal Documents FED-STD-795 Uniform Federal Accessibility Standards Other FAA Documents Order 1375.1E Information/Data Management Order FAA HDBK 007 FAA Data Standardization Handbook FAA Order 1370.121A Information Security and Privacy Policy DOT/FAA/CT-96/1 Human Factors Design Guide (HFDG) FAA Order 8040.4B Safety Risk Management FAA Order 1600.75 Protecting Sensitive Unclassified Information FAA Order 1600.1E Personnel Security Program FAA Order 1600.72A Contractor and Industrial Security Program

FAA Personnel Management Directive (FAPM) 410

Training and Development

FAA Specific National and Local Labor Agreements

C.3.1 Obtaining Copies of Documents

1. Copies of FAA specifications and interface documents may be obtained from the Federal Aviation Administration, Headquarters Public Inquiry Center APA-230, 800 Independence Avenue SW, Washington, DC 20591, 202-267-3484. Requests must fully identify material desired and cite the solicitation or contract number.

2. Requests for copies of documents not covered in the preceding paragraph must be addressed to the Contracting Officer. Requests must fully identify material desired and cite the solicitation or contract number.

3. Electronic requests for number one and two above may be made at:

http://www.faa.gov/foia/email_foia/index.cfm?region=hq

4. Copies of the Acquisition Management System Test and Evaluation Process Guidelines are available in the FAA Acquisition System Toolset (FAST). The on-line internet address of FAST is:

http://fast.faa.gov/.

C.4 ST Application Requirements

C.4.1 Project Management and Reporting

C.4.1.1 Project Manager (PM)

The Contractor must assign a designated Program Manager (PM) to manage this effort. The PM must be the point of contact (POC) between the FAA and the Contractor in the execution of this program and must be prepared at all times to present and discuss with the FAA the status of contract activities, given reasonable notice.

The PM must meet the criteria put forth in Section H.6 of this SIR package. Additionally, the PM must continuously monitor the performance of this contract and of all subcontracts, provide the Government with a timely assessment of program progress or problems, and to control the contract activities as well as subcontractor and Contractor activities.

C.4.1.2 Program Management Plan

The Contractor must prepare, submit and utilize the approved program management plan. The plan states the Contractor’s overall strategy and approach to managing the ST development, testing, monitoring and control, and implementation activities under this contract. It also provides details on management processes, organization design, and roles and responsibilities of key personnel and teammates.

In addition, the program management plan includes the communication channels used internally and externally and approaches for general program management, software development, test and evaluation processes, and risk management. Additionally this document must include in the body or as an appendix a section regarding Risk.

Applicable CDRLs CDRL PM01 Program Management Plan

C.4.1.3 Project Status Reports

The Contractor must provide Monthly Status Reports (MSRs). The MSR must document the activities of the previous month and identify planned activities for the following month. The reports must include, at a minimum, the following information:

http://fast.faa.gov/

• Overview of work completed, work in progress, and work planned for each task.

• Status of funds.

• Status of individual deliverables.

• Identification of risk areas with recommended remedial actions.

• Status of all outstanding identified risks.

• Summary of expenditures by resource and labor category for the monthly reporting period, as well as cumulative year-to-date totals for the performance.

• Any additional information pertinent to the Government in administering the performance of this effort when directed by the TC.

Applicable CDRLs CDRL PM02 Project Status Report

C.4.2 Management & Technical Reviews

C.4.2.1 Project Reviews

The Government may elect to waive or tailor the scope of project reviews specified under the following Sections C.5.3.5.2, C.5.3.5.3 and C.5.3.5.4 if it determines the Contractor’s ST has previously completed these reviews or is a proven Commercial-Off-The-Shelf (COTS) system.

C.4.2.2 Program Management Reviews (PMR)

The Contractor must convene PMRs at least quarterly to demonstrate the successful completion, or progress toward completion, of project milestones. The PMRs will normally be conducted at the Government’s facility; however, other sites may be selected by mutual agreement between the Government and Contractor.

During the PMRs, the PM must present, to the CO, COR or appropriate designee, and review each part of the Project Management Plan. Other participants may be required to attend, as deemed necessary by the CO.

C.4.2.3 System Requirements Review

The Contractor must conduct a System Requirements Review (SRR). The objective of this review is to ascertain the adequacy of the Contractor’s efforts in defining system design requirements and to initiate the functional system requirements baseline. These meetings will occur as required and may be held in conjunction with the PMR meeting as required by the CO or COR.

The Contractor must demonstrate that they reviewed and are in compliance with the latest TRM as part of the SRR. Furthermore, the Contractor must present and review the following documents with the Government:

1. Plans for key activities such as Testing or Site visits

2. Program risk analysis, including assumptions, trade-offs, and alternative approaches

C.4.2.4 SRR Acceptance Criteria

The SRR acceptance criteria are as follows:

1. Demonstration of analysis and a thorough understanding of the requirements in the ST SOW and associated documents.

2. Resolution of all action items.

C.4.2.5 Preliminary Design Review

The Contractor must conduct a Preliminary Design Review (PDR). This review must evaluate software requirements definitions. The objective of this review is to establish the software requirements baseline, and to approve the high-level design of each configuration item. The SRR must be approved by the Government before a PDR may be conducted, and all SRR action items must be closed prior to conducting the PDR, unless the Government has given permission to proceed. These meetings will occur as required and may be held in conjunction with the PMR meeting as required by the CO or COR.

For all non-proprietary software used by the Contractor in its solution, the Contractor must provide a functional/physical description and define technical requirements and interfaces with other system components. For these non-proprietary items, the Contractor must provide the results of the analysis that verifies the item will meet the associated technical requirements and the methods used to ensure that each requirement has been met. Overall technical program risks must be reviewed on a technical, cost, and schedule basis.

As part of the PDR, where customized coding is required, the Contractor must present and review the following documents, or commercial equivalents, with the Government:

1. Deliverables, with overview of the following documents:

2. Draft Software Requirements Specification (SRS) (CDRL SW01)

3. Master Test Plan (MTP) (CDRL TE01)

4. System overview and software requirements definitions.

5. Basic design approach for each configuration item, including CI to CI interfaces and CI to external system interfaces.

6. Functional flow, requirements allocation, and schematic diagrams.

7. CI development schedule.

8. Security considerations including how interfaces will be protected, how system access will be controlled, availability, and integrity of data.

9. Security Assessment.

10. Program and technical risks.

11. Documentation status and availability.

12. PDRs will be held in conjunction with the PMRs.\

C.4.2.6 PDR Acceptance

The Contractor must provide the PDR to the Government for review, comment, and approval.

C.4.2.7 Critical Design Review

The Contractor must conduct a Critical Design Review (CDR). This review must be conducted for each configuration item when detailed design is essentially complete. The PDR must be reviewed and approved by the Government before a CDR may be conducted, and all PDR action items must be closed prior to conducting the CDR, unless the Government has given permission to proceed. These meetings will occur along the same schedule as the PMR schedule and may be held in conjunction with that meeting as required by the CO or COR.

The CDR is intended to ensure that detailed design solutions satisfy performance requirements established by the baselined requirements documents and do not compromise the Government security standards. The Government must approve all customizations to design solutions. The objective of this review is to establish an allocated baseline of low–level design requirements, which becomes an input to the coding process.

The purpose of this review will be to:

1. Ensure that technical, performance, security, and user interface requirements are correctly reflected in design.

2. Ensure that architectural means in software design are correctly identified as derived requirements.

3. Confirm that all derived requirements are defined and have undergone the system security assessment process.

4. Review all change requests generated by the software design process.

5. Ensure that the computer software interfaces are documented and are congruent with high-level interfaces.

6. Ensure that test plans and test procedures provide complete coverage of software requirements.

7. Assess configuration item risk areas (on a technical, cost, and schedule basis).

The CDR must cover the detailed design of all Contractor-developed hardware and computer software configuration items. For all non-proprietary software (e.g., iLog, Crystal Reports, Documentum) used by the Contractor in its solution, the Contractor must provide a detailed functional/physical description of the item, any additional results since the PDR of the analysis that verifies the item will meet the associated technical requirements, and a detailed description of the interfaces with other configuration items.

The Contractor must provide further details than were presented at PDR of its plans for acquiring and developing the required hardware and software to meet contract requirements. Overall technical program risks must be reviewed on a technical, cost, and schedule basis.

As part of the CDR, the Contractor must present and review in detail the following documents with the Government:

1. Deliverables, with overview of the Final SRS.

2. Program and technical risks.

3. Development and test schedule.

4. CDRs will be held in conjunction with the PMRs.

C.4.2.8 CDR Acceptance

1. The Contractor must provide the CDR to the Government for review, comment, and approval.

Contractor is not authorized to begin coding until the CDR has been accepted, unless otherwise authorized by the Contracting Officer (CO) or the COR.

2. Deliverables, with overview of the following documents (CDRL SW01):

a. Final Software Product Specifications (SPS),

b. Updated Software Version Description (SVD), and

c. Software User Manual (SUM).

3. List of open ST Problem Reports (APR) and closure plans.

C.4.2.9 Configuration Management Program

The Contractor must use an internal Configuration Management (CM) system for the control of all elements of the ST including software, documentation, and test equipment. The detailed requirements are included in the subparagraphs below.

C.4.2.10 Contractor's Configuration Management Plan

The Contractor must use the agreed upon Configuration Management Plan (CMP). Any changes to the CMP must be approved by the FAA.

C.4.2.11 Project Configuration Management (CM)

The Contractor must establish an internal CM environment for the development and build of the ST, which must be made available to the Government. The Contractor must produce and provide a map of the ST in a system level Product Directory Structure that contains the hierarchical directory and subdirectories of folders and files used to store the ST. The Contractor must create an initial baseline for the ST work products and define baseline promotion levels.

C.4.2.12 Change and Delivery Configuration The Contractor must utilize separate development, test, and production environments in order limit impact to production use of the software. The Contractor must deploy their software solution in the FAA development environment prior to test environment and test environment prior to the production environment in order to limit impact to the FAA enterprise data center or other systems.

C.4.2.13 ST Problem Reporting (APR)

The Contractor must use an APR system as part of the Contractor's CM program. The Contractor must identify all ST discrepancies or problems identified during development, testing, production, or installation and must submit an APR along with corrective action plans. The Contractor must provide the Government with a complete listing of all APRs pertaining to the product. During each PMR, the Contractor must report on all outstanding discrepancies or problems relating to the product and document the planned resolution.

The Government will have the right to witness or review the documentation regarding the closure of any discrepancy item. In addition, all APRs identified must be documented, along with correction plans and status in the Test Reports submitted to the Government. The Contractor must document and maintain traceability of all changes to the product.

C.4.2.14 Report Findings

The Contactor must report any discrepancies found during the FCA to the Government in the Audit Findings. In addition, the Contractor must identify corrective actions per below:

1. For discrepancies relating to missing work products, the Contractor must place the work product under configuration control or create a CR to create the missing work product.

2. For discrepancies relating to untested or failed requirements, the Contractor may target a later baseline or negotiate for removal from the set of requirements.

3. For discrepancies relating to un-closed CRs, the Contractor may simply need to close the CR; or it may need further testing; or it may need to be deferred to a later baseline.

4. The Contractor must assign responsibility and determine a completion date for those discrepancies that require corrective action.

The Contractor must provide the Government with a complete listing of all ST problems pertaining to the product, including those identified by other customers.

C.4.2.15 Quality Management

The Contractor must maintain the agreed upon and documented quality system as a means of assuring compliance with the software requirements of the contract.

C.4.2.16 Systems Engineering and Design Development

Any Contractor Furnished Software (CFS) must comply with all requirements contained in this SOW. for individual system performance. CFS must be subjected to the provisions described in Section C.4 of this specification.

C.4.2.17 Systems Platforms

ST solution must work with at least one of the following Operating Systems as listed in the current ATO Technical Reference Model (TRM)

C.4.2.18 Hardware

ST solution must work with at least one of the hardware as listed in the current ATO Technical Reference Model (TRM)

C.4.2.19 Application Server

ST solution must work with at least one of the following Application Servers as listed in the current ATO Technical Reference Model (TRM)

C.4.2.20 Authentication, Access & Delivery

ST solution must work with at least one of the following authentications, access, & delivery mechanism as listed in the current ATO Technical Reference Model (TRM)

C.4.2.21 Operation

1. ST solution must be able to work within a three-tiered environment: Development, Test, and

Production Environment.

2. ST solution must be available to users 24/7.

3. Clients (if any) must be designed and built for remote deployment via Tanium toolset in accordance with ATO release management practices.

4. System documentation must include scripts, knowledge base, etc. for National Service Center (NSC) use for known minor problems and general Tier 1 support, as well as role based access allowing for Tier 1 Password resets.

5. ST hardware, COTS application software, operating system software, and other third party application components must be independently replaceable.

C.4.2.22 Technical Reference Model (TRM) requirements

The ST must comply with current Technical Reference Model (TRM) in use by the FAA and be fully functional within such model.

C.5 Software Development

The ST must provide the scheduling functions that the FAA users rely upon while delivering new capabilities needed to advance agency practices and processes. The ST must incorporate the business and fatigue rules per the current Collective Bargaining Agreements and other key documents as provided by the

FAA.

C.5.1 Basic ST Requirements

The ST must be able to perform the following administrative, general, and functional requirements.

C.5.2 Administrative Requirements

The ST must meet the following system administration requirements:

1. 24x7 Access for both administrators and end-users.

2. FAA local and national business rules.

3. Uninstall capabilities for the client (if applicable).

4. Graphical user interface (GUI) management tools.

C.5.3 General Requirements

In addition to the above administrative functions, the ST must meet the following general requirements.

These requirements are based on existing development of ST within the Agency. Contractor should expect that additional work is required for each workforce with the intent to further define detailed requirements for design and/or customization of existing solution. The Agency will collaborate with applicable bargaining units to verify/refine detailed requirements.

1. The ST must provide the capability to schedule up to 1,000 employees in one facility or other work entity sharing different activities/tasks/sectors.

2. The ST must provide the capability to provide schedules for all FAA terminal, en route, maintenance, and other facilities or offices as desired, with expansion capability.

3. The ST must support both local and global (centralized) management. Local personnel will manage schedule creation, optimization, and local business rules. At the same time the ST must support centralized management of the databases, as well as the ability to configure global, or static national business rules.

4. The ST must be able to have flexible work demand as its core input. Demand unit will differ by FAA workforce such as 15 minute on-position requirements for air traffic controllers, course demand for Academy resources, and equipment maintenance and repair demand for technicians.

5. The ST must be able to provide schedules based on multiple shifts throughout a twenty-four (24) hour day, including full-time, part-time, split shifts, and other variations.

6. The ST must be able to create and publish two-week schedules for each scheduling entity (e.g.

facility, area, etc.). The published schedule must have the ability to graphically show the schedule’s ability to meet work demand.

7. Published schedule should display the start time and duration of shifts for each employee,

8. The ST must have the ability to manage leave and schedule change workflows such as leave requests, shift swaps, RDO swaps, shift changes, overtime requests, etc. In order to provide decision support assistance for management, the ST must have the ability to show the impact of these actions on the schedule’s ability to meet the work demand.

9. All schedule change workflows must be evaluated against applicable business rules and impact on ability to meet business rules must be presented to decision-maker via the ST interface.

10. The ST must provide an administrative/management interface that acts as an analysis “sandbox” for users to review scheduling decisions. Actions performed in this interface do not impact published or future schedules and are for reference or reporting only.

11. The ST administrative/management interface must provide modeling capabilities for the FAA to consider alternative scheduling options.

12. The ST must be able to determine optimal schedules including shift definitions, shift start times, shift rotation, and shift staffing requirements. This should be based on input work demand and results should be available in the administrative/management interface for comparison to published schedules and schedules from the analysis sandbox.

13. The ST administrative/management interface must provide the ability to run scenarios at various levels, such as facility, region, or headquarters. This means that given work-area specific daily demands, the optimization can take place at any of these levels. For example, headquarters can run a scenario that includes all facilities.

14. The ST must be capable of functioning within the current FAA network architecture, both within the Local Area Network (LAN) at field facilities, and within the Wide Area Network (WAN) using conventional Internet Protocols (IP). Authenticated users must be able to access the ST from remote places, outside of FAA facilities, via Internet and with a mobile application.

15. The ST must function and present accurate data even in the event of WAN outages, including facilities with intermittent connectivity (remote facilities in AK for instance). Upon restoration of connectivity all data must be synchronized to ensure data integrity for external users.

16. The ST must provide a schedule and leave bidding module. This module will allow authenticated users to generate shift lines and leave slots and configure various bid options including start and end times for bidding, bid rosters, etc. At the conclusion of bidding all results should seamlessly migrate into the normal workflow for creating schedules and acknowledging requests.

17. The ST must integrate with certain FAA systems such as payroll and time and leave tracking systems (ie. Air Traffic Operations Management System, ATOMS). Where permitted and required, the ST must have bi-directional communication with other systems to read and update personnel information such as basic employee information, employee qualifications, leave balances, shift start times, etc.

18. The ST must provide multiple roles so that users can have appropriate permissions based on their responsibilities.

19. The ST must provide robust activity logging and ability for certain users to review activities of all users in the system, especially related to request responses and schedule changes. The ST must provide audit trails.

C.5.4 Advanced Functional Requirements

More detailed functional requirements specific to the ST requirements for air traffic controllers are provided in Appendix C.A. These are presented herein as an example of requirements for an air traffic ST and to ensure Contractor has a sense for the complexity of the FAA’s ST needs. Contractor should expect that further work is required along with FAA management in collaboration with collective bargaining unit(s) to verify and refine the detail requirements for ST systems. Contractor should also expect that ST system requirements for air traffic technicians, Academy staff, and other desired workforces will approach similar complexity.

C.5.5 Additional Requirements

The FAA reserves the right to purchase, as options, additional functionality, software maintenance, and associated technical support and services.

C.5.6 Capacity Requirements

The ST capacity must be scalable, with the ability to manage the schedules of 20,000 employees with expansion capability to 40,000.

C.5.7 Connections To Additional FAA Applications and Systems

The FAA reserves the right to purchase the capability to connect to other FAA applications/systems.

C.5.8 ST Software Design and Documentation

The Contractor must submit software documentation to the Government for review and approval. The following sections describe the required software documentation to be provided by the Contractor.

C.6 Software Development Plan (SP)

Several documents make up the SDP; these documents must address software requirements specification (SRS), interface design document (IDD) software change proposals (SCP), software user manuals (SUM) software development tool manuals and a software version description (SVD).

The overall SDP is a tool for documenting the management processes for software development, the methods to be used, the approach to be followed for each activity, and project schedules, organization, and resources. The SDP describes how to conduct the ST software development effort.

The Contractor must prepare, use, maintain, and update the SDP throughout the performance of the contract.

The SDP must be developed in accordance with CDRL SW01 and is subject to Government approval.

The SDP must not relieve the Contractor from complying with all other requirements of the ST specifications within this SOW. The Contractor must ensure that software products developed by subcontractors are in accordance with all prime contract requirements. The Contractor must specify the means by which this is to be accomplished in the SDP.

C.6.1 System Requirements Specification

The SRS must address the requirements for the software system and the methods to be used to ensure that each requirement has been met. The SRS is used as the basis for design and qualification testing of the software system.

C.6.2 Interface Design Document

The IDD describes the interface characteristics of one or more systems, subsystems, Hardware Configuration Items (HWCIs), Software Configuration Items (SCIs), manual operations, or other system components. The IDD may describe any number of interfaces. The IDD can be used to supplement the Software Design Description. The Government anticipates that the IDD will be developed using Web Services Definition Language (WSDL), the Offeror is encouraged to offer other alternatives in their proposals.

C.6.3 Software Change Proposals

The Contractor must provide the design, development, installation, checkout, test, and validation of specific ST enhancements as requested by the Government. The CO may require the Contractor to submit an SCP for Government identified ST enhancements.

C.6.4 Security Program

The ST must not interfere with FAA Information System Security. The ST must provide confidentiality, integrity, and availability commensurate with the sensitivity level of information.

The Contractor must establish and implement a security program in accordance with FAA Order 1370.82A, FAA Order 1600.72A, FAA Order 1600.75. The Contractor must prepare a ST Security Plan documenting the applicable security features and their proposed implementation for the ST. The Security Plan must describe the information necessary to support the FAA Security Certification and Authorization Package (SCAP) process.

C.6.5 Personnel Security

The Contractor must comply with the requirements of FAA Order 1600.1E in all personnel security matters.

The Contractor must submit the security forms for all personnel so identified to the Government for processing in accordance with FAA Order 1600.1E.

C.6.6 Information Security

The Contractor must comply with…