693KA9-26-R-00003

Part I – The Schedule

Section C – Statement of Work

PART I - SECTION B

SUPPLIES/SERVICES & PRICE/COST

B.1 GENERAL

This section contains the Schedule of Price for Services to be provided under the NISC Enterprise Support Tasking (NEST) contract as described in Section C, Statement of Work (SOW). The Federal Aviation Administration (FAA) Technical Operations ATC Facilities Directorate, Implementation Services Group (AJW-2131) has a requirement for technical support to Technical Operations programs. Technical support consists of Information Technology (IT) support, independent quality assurance, quality control, and application lifecycle operations and maintenance support for the NAS Implementation Support Contract (NISC) Information Management System (NIMS)/Contract Management Information System (CMIS). The FAA requires support throughout life cycle of contract management including, but are not limited to, task order management, financial transaction management, invoice life cycle management, reporting, award fee processing, and data integration with FAA and prime-contractor systems. 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.

This procurement is set-aside for Women Owned Small Business (WOSB) concerns with a single award envisioned.

B.2 BASE AND OPTION PERIODS

The term of this contract includes a 12-month Base Period and four (4) 12-month Option Periods for a total period of performance (POP) of up to five (5) years.

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

B.3 CONTRACT TYPE

Firm Fixed Price (FFP) Contract.

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.

CLIN 0001 Transition (See Subsection C.2.0 – Transition Plan) Description Quantity* Unit Unit Price Amount

FFP Transition Activities 3 Months $xx.xx $xx.xx CLIN 0001 Total $xx.xx

* Transition length to be proposed by Offeror but must not exceed 3 months (90 days)

Base Period CLIN 0002 FFP CMIS/NIMS Management (See C.3.1, C.3.2, C.3.3, and C.3.4)

Description Quantity Unit Unit Price Amount FFP NEST Services in accordance with SOW

12 Months $xx.xx $xx.xx

CLIN 0002 Total $xx.xx

CLIN 0003 FFP Travel (See C.3.1, C.3.2, C.3.3, and C.3.4)

Description Quantity* Unit Unit Price Amount FFP Travel 10,000 EA $1.00 $10,000.00

CLIN 0003 Total $10,000.00 *Travel requires pre-approval and must not exceed $10,000.00 annually

CLIN 0004 Other Direct Costs (See C.3.1, C.3.2, C3.3, and C.3.4)

Description Quantity Unit Unit Price Amount FFP Other Direct Costs 1 EA $xx.xx $xx.xx

CLIN 0004 Total $xx.xx

Option Period 1 CLIN 1001 FFP CMIS/NIMS Management (See C.3.1, C.3.2, C.3.3, and C.3.4)

Description Quantity Unit Unit Price Amount FFP NEST Services in accordance with SOW

12 Months $xx.xx $xx.xx

CLIN 1001 Total $xx.xx

CLIN 1002 FFP Travel (See C.3.1, C.3.2, C.3.3, and C.3.4)

FFP Travel 10,000 EA $1.00 $10,000.00 CLIN 1002 Total $10,000.00

*Travel requires pre-approval and must not exceed $10,000.00 annually

CLIN 1003 Other Direct Costs (See C.3.1, C.3.2, C3.3, and C.3.4)

Description Quantity Unit Unit Price Amount FFP Other Direct Costs 1 EA $xx.xx $xx.xx

CLIN 1003 Total $xx.xx

Option Period 2 CLIN 2001 FFP CMIS/NIMS Management (See C.3.1, C.3.2, C.3.3, and C.3.4)

Description Quantity Unit Unit Price Amount FFP NEST Services in accordance with SOW

CLIN 2001 Total $xx.xx

CLIN 2002 FFP Travel (See C.3.1, C.3.2, C.3.3, and C.3.4)

FFP Travel 10,000 EA $1.00 $10,000.00 CLIN 2002 Total $10,000.00

*Travel requires pre-approval and must not exceed $10,000.00 annually

CLIN 2003 Other Direct Costs (See C.3.1, C.3.2, C3.3, and C.3.4)

Description Quantity Unit Unit Price Amount FFP Other Direct Costs 1 EA $xx.xx $xx.xx

CLIN 2003 Total $xx.xx

Option Period 3 CLIN 3001 FFP CMIS/NIMS Management (See C.3.1, C.3.2, C.3.3, and C.3.4)

Description Quantity Unit Unit Price Amount FFP NEST Services in accordance with SOW

CLIN 3001 Total $xx.xx

CLIN 3002 FFP Travel (See C.3.1, C.3.2, C.3.3, and C.3.4)

FFP Travel 10,000 EA $1.00 $10,000.00 CLIN 3002 Total $10,000.00

*Travel requires pre-approval and must not exceed $10,000.00 annually

CLIN 3003 Other Direct Costs (See C.3.1, C.3.2, C3.3, and C.3.4)

Description Quantity Unit Unit Price Amount FFP Other Direct Costs 1 EA $xx.xx $xx.xx

CLIN 3003 Total $xx.xx

Option Period 4 CLIN 4001 FFP CMIS/NIMS Management (See C.3.1, C.3.2, C.3.3, and C.3.4)

Description Quantity Unit Unit Price Amount FFP NEST Services in accordance with SOW

CLIN 4001 Total $xx.xx

CLIN 4002 FFP Travel (See C.3.1, C.3.2, C.3.3, and C.3.4)

FFP Travel 10,000 EA $1.00 $10,000.00 CLIN 4002 Total $10,000.00

*Travel requires pre-approval and must not exceed $10,000.00 annually

CLIN 4003 Other Direct Costs (See C.3.1, C.3.2, C3.3, and C.3.4)

Description Quantity Unit Unit Price Amount

FFP Other Direct Costs 1 EA $xx.xx $xx.xx CLIN 4003 Total $xx.xx

B.5 CONTRACT PRICING

The following section describes pricing requirements FFP Contract Line Item Numbers (CLINs).

B.5.1 Firm Fixed Pricing

(a) Billing Rates

The tasks listed in C.3.1, C.3.2, and C.3.3 are Firm Fixed Priced at the rates specified in B.4 CLIN Structure, or as negotiated, if lower amounts are proposed. 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) Labor Hours

The Government estimates a total of 43,200 labor hours (8,640 annually) are required to perform the contract requirements. The labor categories and labor rates identified above are provided for use in the performance of work hereunder and the payment for such work. 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.

Unless authorized in writing by the Contracting Officer, all labor proposed under this contract must be in accordance with the applicable labor rates set forth in Section B above and labor categories described below. The labor rates set forth in Section B represent the maximum that the Government will pay for such labor during the life of this contract, including options years.

Throughout the term of this Contract, the Government will not accept other labor rates unless different rates are agreed upon by both parties or unless the parties negotiate additional labor categories and rates.

(c) 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.

(d) 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.

(e) Travel

If Contractor 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.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)

PART I - SECTION C

DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 STATEMENT OF WORK

C.1.1 Background

The AJW-2 Directorate, AJW-2131 Implementation Services Group, provides technical, engineering, financial, budget, and management support to Technical Operations programs using the NAS Integration Support Contract (NISC IV Contract) and Technical Support Services Contract (TSSC).These are task order contracts that present contract managers with the task of managing the entire Task Order Management lifecycle, the Financial Management lifecycle encompassing the obligation and de-obligation of funds by integrating with FAA’s financial systems, PRISM and Delphi and the Invoice/Payments lifecycle. The NISC IV contract will also be transitioned to NISC V contract during the award period, which will require a new system to support the NISC V contract, while maintaining the NIMS system to close out the NISC IV contract.

This work requires a support contractor that will provide Operations and Maintenance services for the NIMS systems that is used to manage the current NISC IV contract using the existing technology stack and will provide quality assurance and quality control to ensure uninterrupted system availability. In addition, the vendor should maintain and run reports if required from CMIS system that was used to support the NISC III contract and is currently not active. The work also requires the vendor to serve as a Subject Matter Expert (SME) capable of providing design, development, testing, deployment and documentation of the new software that will be required to support the NISC V contract when required. This includes, but is not limited to, making recommendations regarding the selection of software architecture and software development tools that will be required to develop the new system.

C.1.2 Scope of Work

The Contractor must provide operations and maintenance support for the NIMS/CMIS system, provide quality assurance and quality control, provide security compliance and ensure uninterrupted system availability. This effort also requires the vendor to serve as a SME and provide support with system architecture, software recommendations, system design, development, testing, deployment, and documentation for a new system to support NISC V contract requirements when required.

Contractor will maintain NIMS/CMIS security certifications required to operate the software and its associated server hardware. The Contractor must also provide transition support to any potential new vendor at the contract’s end.

C.1.3 Objectives

The objectives of the NEST’s Scope of Work are to provide the following support:

• Operation and Maintenance of the NIMS/CMIS System:

o Enhancement to NIMS systems, KITT Financial Database (KFDB) reporting database, and NISC Invoice Approval Tool (NIAT) using existing technology stack to support business process requirements as and when required by NISC PMO;

o Document NIMS (including test, development, production and mirror instances) code revisions, testing, software upgrades, and implementation activities;

o Operations support for NIMS for both NISC and TSSC by extracting and downloading Delphi and PRISM data into NIMS for use by NISC and TSSC customers;

o Maintain existing reports and create new integrated reports in KFDB to include funding and other pertinent information from FAA financial systems (PRISM/Delphi);

o Maintenance support for the NIMS application, i.e., troubleshooting, correcting data inaccuracies, responding to customer requests to make routine changes, and correcting defects as they are identified;

o Maintain CMIS, which is in-active. Vendor must be able to run and provide reports as requested by Project Management Office (PMO), Contracting Officer Representative (COR), and Contracting Officer (CO);

o System upgrades include developing and integrating financial dashboard (NED: NISC Enterprise Database) from the NISC IV Prime Contractor’s financial systems into NIMS based on requirements provided by the PMO to provide financial metrics such as Task Order EAC (Estimate at Completion), ETC (Estimate to Complete), Earned Value Measurement (EVM), and other financial metrics;

o Support and maintain the current level of security certification by interfacing with the FAA Cyber security organization and conducting the necessary security threat detection and system scans, resolution of cyber security issues and the associated updates to documentation such as System Characterization Document (SCD), System Security Plan (SSP), and Plan of Action & Milestones (POAM) fixes, and any other documents required by FAA’s cybersecurity team;

o Comply with FAA IT policies and guidelines to include PIV/My Access security authentication layer integrated into NIMS/CMIS;

o Provide data extracts and reports from NIMS/CMIS to meet data call requirements o Transition-out NIMS/CMIS support to a potential new vendor over three – six months upon contract termination;

o Training NIMS users and developing/updating User Guides as requested by PMO;

• Implementation of new systems to support NISC V in Option Period 2 onward:

o Provide system architecture, software recommendations, design, development, testing, deployment and maintenance support for future NISC V contract, while complying with all requirements from FAA Cyber Security organization.

C.2 TRANSITION PLAN – PRIOR TO CONTRACT START

The Contractor must submit a Transition-In Plan for execution during the transition period. The Plan must not be materially altered without the Government’s consent. The transition period will begin upon execution of contract award unless a later date is specified. The Contractor must propose the length of the transition period, which must not exceed 90 days.

The transition period is intended to provide the Contractor with time to perform due diligence functions associated with NIMS Capabilities. This includes the inventory of all systems, software, and third-party components that make up NIMS, as well as those systems and software that interface or integrate with it.

Contractor will be paid for transition costs in accordance with its pricing proposal. Transition costs are defined as all costs expended during the transition period that are necessary and reasonable to assume operation, maintenance, and responsibility for the system.

The Contractor’s transition plan must permit sufficient time for a deliberate and orderly turnover of the NIMS system but must not exceed 90 days. The Contractor must participate in technical discussions with the outgoing contractor for the purpose of ensuring a smooth transfer.

If the Contractor does not initiate and comply in accordance with transition activities as outlined in its transition plan, any extra costs arising from the delay in meeting the timeline will be the Contractor's responsibility.

The Contractor will only be compensated by the Government when the failure is not attributable in any way to the acts or omissions of the incoming Contractor.

C.3 ACTIVITIES

The Contractor must conduct the following tasks as outlined here and within the following subsections in support of systems documented within subsection C.1.3:

• Operations and Maintenance of the current NIMS software and hardware

• Ensure quality assurance and quality control of current NIMS application

• Data collection and analytical support

• Ensure compliance with FAA’s security policies and control

• Maintaining current integration with FAA’s systems (Delphi/Prism) and enhancing integrations with these systems as and when required; and

• Recommend and Implement systems for supporting the upcoming NISC V contract.

C.3.1 Task 1 – Task Management

Task management involves the activities listed below which are in direct support of the Statement of Work. The program management functions associated with specific tasks will be found in subsections C.3.1 through C.3.4. The Contractor must provide program/project management support for NIMS/CMIS as required below upon direction from PMO:

• Conduct and coordinate tasks assigned to manage the project effectively, including developing and maintaining project schedules for implementation;

• Provide comprehensive documentation such as briefings, reports, business process models, workflow diagrams, analyses, plans, schedules, and other documents necessary for supporting NIMS project functions;

• Develop work breakdown structures to manage project scope, ensuring coordination and information exchange with stakeholders through meetings and project status updates;

• Provide support to the FAA’s Project Manager in the development, coordination, and review of plans and documentation necessary for the development, integration, and enhancements of NIMS and its associated system applications. This includes staffing plans, change proposals, implementation plans, documentation, analyses, and training plans, drafting notices/policies/directives for system operation, solution assessment, and validation results as required;

• Develop and implement NIMS Plans to include software development and/or upgrade as well as any necessary hardware upgrade or modification;

• Track costs and budgets, providing financial control reports and variance analysis to the PMO;

• Develop project management plans and documentation consistent with Project Management

Lifecycles (PMLC) and Software Development Lifecycles (SDLC) methods (e.g., waterfall, agile, iterative development);

• Ensure requisite standards and metrics are applied for quality product delivery;

• Develop and maintain a detailed plan to manage risks;

• Provide details on the methodology and purpose of tools that will be used to manage the project;

• Coordinate with the PMO and NISC Prime Contractor for managing any data related issues;

• Support the NIMS/CMIS projects by participating in meetings as required and providing requisite action item tracking, meeting notes and consolidated monthly activity reports;

• Assist with managing all the deliverables listed in the SIR and any others are required by PMO;

• Assist with procurement of software licenses and SSL certificates, planning and coordination of funding requirements for the NIMS/CMIS instances that are in the cloud environment

• Develop and execute a plan to transition NIMS/CMIS support from the current vendor to any potential future vendor over a three to six-month period without operational impact on the systems;

• Adhere to proven and repeatable software development practices that are approved and recognized in the industry as well as recommended by FAA IT standards.

• Provide asset management support which involves the management of current NIMS/CMIS systems and design and installation of new systems to support the NISC V contract, connectivity and installation support, relocation or consolidation of applications in the FAA’s cloud environment, systematic tracking of hardware (H/W) and software (S/W) assets, managing H/W specifications, maintenance and upgrading of requisite hardware and software, S/W end-user license agreement (EULA) acquisition and management, S/W and H/W Maintenance Agreement, and asset reports; and

• Assist with the identification of business needs and scope, research and evaluate potential options and present recommendations with rationale for implementing a system to support the upcoming NISC V Contract

C.3.2 Task 2 – NIMS/CMIS Operations and Maintenance, User Training, Helpdesk and Security Management Support

The current application stack for NIMS/CMIS includes the following:

Adobe ColdFusion (2018/2023 version), Fusion Charts used as charting engine, SQL*Plus, Toad, Oracle Database 19c Enterprise Edition, Oracle Enterprise Manager (OEM) Cloud Control, Oracle RMAN (Recovery Manager) and Oracle Data Pump. The NIMS application is hosted in FAA’s AWS Cloud Environment.

NIMS/CMIS Operations and Maintenance consist of those activities required to manage the task order management lifecycle, the financial management lifecycle for obligation and de-obligation of funds, which includes extraction and downloading of contract specific data from PRISM and Delphi and making it available to financial personnel managing the finances on participating NIMS and TSSC contracts and the Invoice/Payment lifecycle. The financial management data must be presented in a format that is readable by the established user interfaces. The Contractor must undertake all activities required to manage and enhance the NIMS system and associated interfaces, track and resolve helpdesk tickets and provide required user training. The Contractor is responsible for responding to all the data calls, performing requisite system changes and submitting compliant documents to ensure compliance with FAA’s Cyber Security organization, conduct and attend presentations, briefings and any other meetings that are required to obtain the Authority To Operate (ATO) status for the NIMS/CMIS systems as directed by the FAA IT and associated Cyber Security related policies and personnel in support of the AJW-2131 management.

The Contractor must:

• Support the day-to-day operations of NIMS, ensuring contract-specific data is accessible only to authorized personnel, while adhering to FAA IT recommended frameworks encompassing but not limited to, Enterprise Risk Management (ERM) framework, Enterprise Architecture Framework, Data Governance (DG), Architecture Governance Board, IT Service Management (ITSM) and FAA Technology Roadmaps. This support broadly includes, without limitation, the following:

o Software architecture and design for any system enhancements of the current NIMS system;

o Solution development and bug fixes using the existing technology stack;

o System enhancements and maintenance using the existing technology stack;

o Disaster recovery, archiving and backups;

o Assist with any system decommissioning requirements;

o Patching and updating applications, software upgrades;

o System/Platform administration support, including operating system and database management and upgrades;

o Cloud management support;

o Management of Plan of Action and Milestones (POAM) and security vulnerabilities remediation;

o Managing the NIMS database, its interfaces, and associated financial data access tools, including related software upgrades;

o Producing financial data reports and maintaining requisite database and access tools;

o Reviewing current business processes, and recommending and implementing AI solutions to assist with process improvements and/or to assist with meeting task order or financial reporting requirements for all users o Performing frequent data refreshes and downloading information from FAA's Delphi and PRISM financial systems into NIMS for both NISC and TSSC contracts;

o Resolving invoice and payment processing issues in NIMS and coordinating with the NISC Prime Contractor to resolve any invoice data related issues; Analyzing the downloaded information from Delphi and PRISM to identify and correct errors in the data;

o Running scripts and refreshing the KFDB database and adjusting KFDB reports if required to meet business requirements, o Coordinating and testing the financial interfaces to comply with any PRISM and Delphi upgrades and making changes to ensure the interfaces provide requisite data o Enhancing System and reports to comply with policies as required;

o Running reports and extracting data when required from CMIS, which is currently not active o Responding to data calls from the security team in a timely manner;

o Coordinating yearly scanning of the systems with the cybersecurity personnel;

o Addressing and correcting application issues pertaining to scan results and ensuring compliance with FAA’s cybersecurity team;

o Coordinating with FAA IT personnel to resolve scan issues pertaining to the Windows and Database environments;

o Managing POAM in ATOM systems or any other FAA systems to ensure compliance;

o Procuring and installing SSL certs and licenses as required;

o Drafting and submitting documentation such as SCD, SSP, etc. and participating in meetings required to maintain CMIS/NIMS ATO status to comply with Cyber Security Assessments and Accreditation that are required to be performed year-round and to reply to information requests from FAA Security Offices based on deadlines established by AJW-213 Program Office and FAA IT. This support includes, but is not limited to:

Cloud security assessments;

Code auditing to comply with cybersecurity requirements;

Cyber security and information assurance;

Intrusion detection;

Event detection and monitoring;

Virus detection; Inspections and associated assessment corrections or remediations or justifications;

Security integrated with development (DevSecOps);

FAA PIV security authentication integration.

• Provide 1st and 2nd level helpdesk technical support to End Users, Key User, PMO and

Financial Analysts on NIMS applications and associated interfaces. Support would typically involve user activation/de-activation, resolving production issues, financial data validation, etc.

There may be exceptions, however, historically, the number of support requests has varied and typically remained at or below 10 calls per month. Provide assessment of the impact of FAA Security Policies, design and provide remediation strategies and integration solutions to ensure compliance.

C.3.3 Task 3 –Systems Support for NISC Contract Transition

• Please submit a detailed proposal describing your firm’s methodology and overall approach for gathering requirements, architecting, designing, developing, building, testing, and deploying a new software solution that has similar functionality like NIMS along with its integration to FAA’s backend systems Prism and Delphi. The proposal should clearly explain how your team will plan, execute, and manage the work throughout the full software development lifecycle. At a minimum, please address the following:

• Your overall delivery methodology and framework (e.g., Agile, hybrid Agile/Waterfall, DevSecOps, or other approaches) and how it will be applied to this project.

• Your approach to adherence to FAA’s Technology and Security framework, including procuring requisite authorization to operate the new system within FAA’s environment.

• Your approach to sizing and acquisition of hardware and software to meet new system requirements.

• The proposed project phases, key activities, milestones, and deliverables associated with each phase.

• Your approach to requirements discovery, analysis, and validation with stakeholders.

• The process your team uses for solution architecture, technical design, and technology selection.

• Development practices, including coding standards, version control, collaboration practices, and integration methods.

• Your approach to testing and quality assurance, including unit testing, system testing, integration testing, performance testing, and user acceptance testing.

• Security practices and how security will be incorporated throughout the development lifecycle.

• Deployment strategy, release management, and environment management (e.g., development, testing, staging, and production).

• DevOps or CI/CD practices used to support automated builds, testing, and deployments.

• Project governance, communication, and reporting processes, including how progress, risks, issues, and changes will be managed.

• The roles and responsibilities of the proposed team and how collaboration with project stakeholders will occur.

• Your approach to documentation, knowledge transfer, and post-deployment support or maintenance.

• In addition, please provide at least one example of a comparable project of similar size, scope, and complexity in which your organization successfully architected, designed, developed, built, and deployed a similar Contract Management solution encompassing a complete Task Order Management Lifecycle, Financial Management Life Cycle (Obligations, De-Obligations, etc.) Invoice and Payment management Lifecycle. For each example, please include:

• A brief description of the client, project objectives, and overall scope.

• The scale and complexity of the project (e.g., number of users, integrations, data volume, system components, or geographic reach).

• Your organization’s specific role and responsibilities in the project.

• The architecture and technology stack used.

• The methodology and development approach applied.

• Key challenges encountered and how they were addressed.

• The implementation timeline and major milestones.

• The outcomes achieved, including measurable results where available (e.g., performance improvements, operational efficiencies, user adoption, cost savings, or other business impacts).

• This information will help evaluate your team’s technical capabilities, delivery approach, and demonstrated experience in successfully delivering solutions of similar scale and complexity.

C.3.4 Task 4 – Transition Plan Transition-IN Plan As referenced in Section C.2, Contractor must provide a Transition Plan that describes in detail its approach, process, resourcing, any anticipated risks and responsive risk mitigation strategies, and schedule for providing a structured, thoughtful, effective, and orderly transition from the outgoing NEST contractor.

The transition plan at a minimum must address the following areas:

• Transition Plan Contractor Assumptions

• Contractor’s Proposed Team Structure

• Contractor’s understanding of the Transition Plan Scope

• Proposed approach to business process and technology knowledge transfer

• Proposed Transition Plan Schedule

• Proposed Risk Mitigation Strategies in support of Transition

• Proposed Transition Staffing and Resourcing

• Proposed Change Management

Transition-OUT Plan Contractor must provide an approach for a plan to transition system support to any potential future vendor without operational impact on the systems.

C.4. END RESULTS/DELIVERABLES

C.4.1 Acceptance and List of Deliverables by Task

The following table provides a list of the required deliverables by task. All deliverables under this contract will be subject to review and inspection by the CO or COR. Inspection, review or approval of deliverables or associated services prior to final acceptance must not be construed as assurance of acceptance of the finished product. Final inspection and acceptance of deliverables or services will be performed by the CO or COR.

Task Deliverable Due Date Acceptance Criteria

1 Reports As required Government Approval

1 Financial Reports and Analysis As required Government Approval

1 Program Management Reviews, Plans, Schedules

As required Government Approval

1,2,3 Test plans and associated documentation

As required Government Approval

1 Project Schedules As required Government Approval

1 Meeting notes As required Government Approval

2,3 Updated code As required Government Approval

2,3 Database Feeds for both NISC and TSSC Contracts

Each agency systems’ operational workday, as required

Government Approval

1,2,3 NIMS Upgrades As required Government Approval

4 Transition Plans As required Government Approval

1 Monthly Status Report Monthly Government Approval

1,2,3

Updated System Design and Architecture documentation, Database Management documentation and Data Dictionary, Requirements Document, Test Plans, Operations manuals and any relevant transition related documents

Baseline documents within 90 days of contract award and periodic updates thereafter.

All final documents must be submitted before transition.

Government Approval

1,2,3 All security related documents As required Government Approval

C.4.2 Transmittal/Delivery

The Contractor must provide electronic copies of files, reports, and deliverables. Acceptable electronic formats are Microsoft Word, Microsoft Excel, Microsoft PowerPoint, Microsoft Project, and other formats agreed to by the FAA. Hard copies may be delivered if approved by the FAA. The Contractor, as needed, by the government must also follow the Knowledge Service Network (KSN) site protocol to deposit the electronic documents as part of deliverables.

C.5 PLACE OF PERFORMANCE

The principal place of performance will be at FAA’s or Contractor’s facilities. For requirements to be performed at the Contractor’s facility, the facility must be conveniently located to ensure timely access to FAA Headquarters, 800 Independence Avenue SW, Washington, DC 20591.

C.6 TRANSITION/CLOSEOUT PLAN – PRIOR TO CONTRACT END

In addition to the requirements of AMS Clause 3.8.2-11, approximately three (3) months prior to this effort’s end date, the Contractor must provide the following:

• All documentation, as of the most recent revision;

• A transition status report to include a projection for the next 90 days of the program; and

• A close out meeting (to include all key personnel) with the FAA (details to be determined by the

FAA)

C.7 OTHER DIRECT COSTS (ODCs)

C.7.1 Travel

Travel will be required for the annual NISC off-site training.

C.7.2 Material Costs

Purchase of materials is authorized for this effort. When items are to be purchased, the material must be determined to be in direct support of administration or performance or accomplishment of tasks under the Contract by the COR in advance of purchase. Any items purchased under the Contract as a direct cost become the property of the government. Disposal of obsolete equipment must be in accordance with FAA procedures. The Contractor must keep a record of all the approved purchase requests.

C.8 OTHER REQUIREMENTS

C.8.1 Office Space

The Contractor must provide adequate space and communication tools necessary for its personnel to work effectively under this contract. The Contractor must maintain a modern office environment located within the United States with amenities such as standard office furniture, telephone equipment, copying equipment, conference or workroom facilities, file storage facilities, and operating supplies.

C.8.2 Telework

Contractor employees may work remotely (Telework) with prior approval from the FAA management. The FAA may revoke this approval at any time; if it does, performance may no longer occur remotely. Telework costs (space, phones, internet, travel, etc.) will not be allowed as direct costs under this contract.

(End of Section C)

Section D – Packaging and Marking 693KA9-26-R-00003

PART I - SECTION D

PACKAGING AND MARKING

D.1 PACKING AND PACKAGING

All deliverables under this contract must be preserved and packaged in accordance with the most economical and best commercial practices to ensure delivery at the destination and to prevent deterioration and damage due to shipping, handling, and storage hazards.

D.2 GENERAL MARKING

In addition to information provided with shipping instructions, all deliverables must be marked on the outside of the packaging with the following:

1. FAA contract number;

2. Contractor's name and address;

3. List of contents

4. Contract Data Requirements List (CDRL) number; and

5. Applicable Data Rights Notices

D.3 MARKING OF REPORTS

The Contractor must mark all data deliverables as follows:

1. Report Title;

2. Contract number;

3. Date; and

4. Distribution

D.4 TRANSMISSION OF DELIVERABLES

All deliverable items required by this contract will be shipped F.O.B. destination, within the consignee’s premises, with all mailing and transport expenses prepaid by the Contractor.

(End of Section D)

Section E – Inspection and Acceptance 693KA9-26-R-00003

PART I - SECTION E

INSPECTION AND ACCEPTANCE

E.1 FAA AMS 3.1-1 CLAUSES AND PROVISIONS INCORPORATED BY

REFERENCE (JULY 2019)

This Screening Information Request (SIR) or contract, as applicable, incorporates by reference the provisions or clauses listed below with the same force and effect as if they were given in full text. Upon request, the Contracting Officer (CO) will make the full text available, or Offerors and Contractors may obtain the full text via Internet at https://fast.faa.gov/contractclauses.cfm

The following contract clause or clauses pertinent to this section are hereby incorporated by reference:

Clause Title

3.10.4-4 Inspection of Services - Both Fixed-Price & Cost Reimbursement (April 1996)

E.2 INSPECTION AND ACCEPTANCE

(a) The Contracting Officer, or their duly authorized representative, is authorized to perform inspection on behalf of the Government for the purpose of acceptance of all materials, data, or services to be provided. In this regard, the Contracting Officer’s Representative (COR) is an authorized representative of the Contracting Officer. Final acceptance of all deliverables under this contract must be made by the Contracting Officer or designee, in writing.

(b) Inspection, review or the anticipation of acceptance/approval of a deliverable item during the course of its preparation must not be construed as assurance of acceptance of the finished product.

(End of Section E) https://fast.faa.gov/contractclauses.cfm

Section F – Deliverables or Performance 693KA9-26-R-00003

PART I - SECTION F

DELIVERIES OR PERFORMANCE

F.1 FAA AMS 3.1-1 CLAUSES AND PROVISIONS INCORPORATED BY

REFERENCE (JULY 2019)

This Screening Information Request (SIR) or contract, as applicable, incorporates by reference the provisions or clauses listed below with the same force and effect as if they were given in full text. Upon request, the Contracting Officer (CO) will make the full text available, or Offerors and Contractors may obtain the full text via Internet at: https://fast.faa.gov/contractclauses.cfm

The following contract clause or clauses pertinent to this section are hereby incorporated by reference:

3.10.1-9 Stop-Work Order (April 2025) 3.10.1-11 Government Delay of Work (April 1996) 3.10.1-24 Notice of Delay (March 2009) 3.11-34 F.O.B. Destination (April 1999)

F.2 AMS CLAUSE 3.8.2-22 SUBSTITUTION OR ADDITION OF PERSONNEL (October 2006)

(1) The Contractor must assign only those individuals whose resumes, personnel data, or personnel qualification statements have been submitted and determined by the Contracting Officer to meet the minimum requirements of the contract. The Contractor must not substitute or add personnel except in accordance with this clause.

(2) Substitution of Personnel.

(a) For the first 30 days of contract performance, the Contractor must not substitute personnel for the individuals whose resumes or other personal qualifications were submitted with its offer and that were determined by the Contracting Officer to be acceptable at the time of contract award, unless such substitutions are because of an individual's sudden illness, death, or termination of employment.

In any of these events, the Contractor must promptly notify the Contracting Officer and propose substitute personnel as required by paragraph (4) below.

(b) If an individual becomes, for whatever reason, unavailable for work under the contract for a continuous period exceeding thirty (30) working days or is expected to devote substantially less effort to the planned work, the Contractor must propose a substitute personnel as required by paragraph (4) below.

(3) Addition of Personnel. If an FAA requirement will increase the specified level of effort for a designated labor category, but not the overall level of effort of the contract, then the Contractor must notify the Contracting Officer to add personnel to the designated labor category. The Contractor must request added personnel as required by paragraph (4) below.

(4) Request and Review. The Contractor must submit the request for substitute or added personnel in writing to the Contracting Officer at least thirty (30) days (if a security clearance must be obtained, at least sixty (60) days before the proposed date of substitution or addition. The Contractor's request must provide a detailed explanation of the circumstances causing the proposed substitution or addition, a complete resume for the proposed substitute or added personnel, and any additional information required by the Contracting Officer. Proposed substitutes and added personnel must have qualifications equal to or higher than those stated in the contract for the labor category. The Contracting Officer will evaluate the Contractor's request and promptly notify the Contractor of the decision to accept or reject the qualifications of the substitute or added personnel.

(5) The Contracting Officer may terminate the contract if the Contractor has not made suitable, timely, and reasonably forthcoming replacement of personnel who have been reassigned or terminated or otherwise become unavailable to work under the contract or the resulting loss of productive effort would impair the successful completion of the contract. Alternatively, if the Contracting Officer finds the Contractor to be at fault for the condition, then the Contracting Officer may equitably adjust (downward) the contract price or fixed fee to compensate the Government for any delay, loss or damage as a result of the Contractor's action.

(End of clause)

F.3 PERIOD OF PERFORMANCE

The period of performance of this contract is one (1) year base period and four (4) one-year option periods, for a maximum total period of performance of five (5) years.

F.4 PLACE OF PERFORMANCE

The principal place of performance will be at FAA’s or contractor’s facilities. For requirements to be performed at the contractor’s facility, the facility must be conveniently located to FAA Headquarters to ensure timely access.

F.5 DELIVERABLES

All applicable deliverables, their required delivery dates, destination of delivery, and schedule for completion of work to be performed are specified in Section C.

For purposes of delivery, all deliverables must be made by 4:30 P.M, local time (Eastern Time) at destination, Monday through Friday.

All deliverables submitted in electronic format must be free of any known computer viruses or defects. If a virus or defect is found, the initial deliverable will not be accepted. The replacement file must be provided within two (2) business days after notification of the presence of a virus.

Each deliverable must be accompanied by a cover letter from the Contractor on Company letterhead.

Multiple deliverables may be delivered with a single cover letter describing the contents of the complete package. All deliverables are to be submitted in electronic format.

In the event the Contractor anticipates difficulty in complying with any delivery schedule, the Contractor must immediately provide written notice to the CO, COR, and the Program Manager (PM). Each notification must give pertinent details, including the date by which the Contractor expects to make delivery; provided that this data must be informational only in character and that receipt thereof must not be construed as a waiver by the Government of any contract delivery schedule, or any rights or remedies provided by law or under this contract.

(End of Section F)

Section G - Contract Administrative Data 693KA9-26-R-00003

PART I - SECTION G

CONTRACT ADMINISTRATION DATA

G.1 FAA AMS 3.1-1 CLAUSES AND PROVISIONS INCORPORATED BY

REFERENCE (JULY 2019)

This Screening Information Request (SIR) or contract, as applicable, incorporates by reference the provisions or clauses listed below with the same force and effect as if they were given in full text. Upon request, the Contracting Officer (CO) will make the full text available, or Offerors and Contractors may obtain the full text via Internet at: https://fast.faa.gov/contractclauses.cfm The following contract clause or clauses pertinent to this section are hereby incorporated by reference:

3.10.1-22 Contracting Officer’s Representative (April 2012)

G.2 CONTRACT ADMINISTRATION POINTS OF CONTACT

Contracting Officer Federal Aviation Administration

Jose A. Duran 800 Independence Avenue SW Washington, D.C. 20591 Phone:

202–267–7374 Email: 9-AWA-AAQ410-Contracting- Team@faa.gov

Contracting Officer’s Representative

(COR)

TBD

mailto:9-AWA-AAQ410-Contracting-Team@faa.gov

G.3 CONTRACTING OFFICER’S AUTHORITY

The Contracting Officer assigned to this contract has responsibility for ensuring the performance of all necessary actions for effective contracting, ensuring compliance with the terms of the contract, and safeguarding the interests of the United States in its contractual relationships. In this regard, the Contracting Officer is the only individual who has the authority to enter into, administer, or terminate this contract. In addition, the Contracting Officer is the only person authorized to approve changes to any of the requirements under this contract, and notwithstanding any provision contained elsewhere in this contract, the said authority remains solely with the Contracting Officer.

The Contractor must immediately notify the Contracting Officer for clarification when a question arises regarding the authority of any person to act for the Contracting Officer under the contract or when the Contractor receives direction that appears outside contract scope.

It is the responsibility of the Contractor to contact the Contracting Officer immediately if there is even the appearance of any technical direction that is or may be outside the scope of the contract. Costs incurred that were not authorized by the Contracting Officer and/or work outside the scope of the contract must be considered unallowable costs and will not be reimbursed by the Government.

G.4 CONTRACTING OFFICER’S REPRESENTATIVE

The COR is responsible for the technical administration of the contract and the technical liaison with the Contractor. The COR is not authorized to change the scope of work or specifications in the contract, to make any commitments or otherwise obligate the Government or authorize any changes which affect the contract price, delivery schedule, period of performance, or other terms and conditions of the contract.

The COR is responsible for monitoring progress and overall technical management of the work hereunder and will be contacted regarding questions or problems of a technical nature.

In no event, however, will any understanding or agreement, modification, change order, or other matter deviating from the terms of the contract between the Contractor and any person other than the Contracting Officer be effective or binding upon the Government, unless a contract modification or letter of direction is executed by the Contracting Officer prior to completion of this contract.

On all matters that pertain to contract terms, the Contractor will contact the Contracting Officer. When, in the opinion of the Contractor, the COR requests effort outside the existing scope of the contract, the Contractor will promptly notify the Contracting Officer. The Contractor, under such request, will take no action unless and until the Contracting Officer has issued a letter of direction or a contract modification.

G.5 CORRESPONDENCE PROCEDURES

To promote timely and effective contract administration, correspondence submitted under this contract (except invoices and deliverable items) must be subject to the following procedures:

• Technical correspondence of a routine nature must be addressed to the designated COR with an information copy of the correspondence to the Contracting Officer listed in G.2.

• Other considerations including technical correspondence involving technical issues and correspondence proposing or otherwise involving waivers, deviations, or modifications to the contract, must be addressed to the Contracting Officer listed in G.2, with information copies to the COR.

All correspondence must include the contract number.

G.6 ELECTRONIC COMMUNICATIONS

The Contractor must ensure an electronic means for communicating with FAA personnel. The Contractor must ensure that the communications are compatible with the FAA’s electronic mail system which is currently MS Outlook. The Contractor must also ensure that the Contractor’s electronic mail has the capability to receive and retrieve attachments.

All contract reports/deliverables, including invoices, must be made in electronic format with all links and interdependencies readily traceable.

G.7 BILLING INSTRUCTIONS

Invoices must be submitted monthly in accordance with AMS 3.2.4-5, Allowable Cost and Payment (October 2019). Payment is subject to review, approval and certification by the CO and COR. In the event of questioned costs, the CO may withhold any or all invoice amounts until the Contractor provides all required data to the satisfaction of the CO. The payment will be made pursuant to FAA AMS 3.3.1- 34 Payment by Electronic Funds Transfer/System for Award Management.

Compliance with these instructions will reduce correspondence and other causes for delay to a minimum and will thus promote prompt payments to the Contractor. Invoices must be submitted no more frequently than once per month unless prior written consent is obtained from the CO, and supporting cost documentation is as described in this section.

Invoices must be submitted in soft copy as established below:

Accounts Payable Email copy to:

9-AMC-AMZ-FAA-

APInvoices@faa.gov

Monthly

Contracting Officer and COR Email copy to:

9-AWA-AAQ410-Contracting- Team@faa.gov

Concurrently with submittal to Accounts Payable, submit one signed copy in PDF format

Upon completion, termination, or expiration of the contract, the Contractor must submit a final voucher clearly marked “FINAL.” The final voucher must contain an itemized accounting of total contract costs that includes:

• Certification that all contractual requirements have been satisfied; and

Certification…