CLIN 001 PWS.docx

ISC Contract #692M15-20-D-00004 Program Management Task Order #TBD

INTEGRATED SERVICE CENTER CONTRACT

PROGRAM MANAGEMENT SUPPORT TASK ORDER

PERFORMANCE WORK STATEMENT

in support of

FEDERAL AVIATION ADMINISTRATION OFFICE OF INFORMATION AND TECHNOLOGY

January 23, 2026

U.S. DOT Federal Aviation Administration

Table of Contents

Program Management Support Task Order PWS i

1 Introduction The Federal Aviation Administration (FAA) Office of Information and Technology (AIT) requires program management support for the FAA’s Integrated Service Center (ISC), which will provide enterprise-level information technology (IT) services, to include:

a. Service Center support,

b. Lifecycle asset management support for end-user devices and backend infrastructure,

c. IT customer training support, and

d. Special projects support.

1.1 Objective

The overarching business objective of the ISC Contract is to achieve and maintain a high level of customer satisfaction throughout performance of all ISC task orders, as described in Section C of the ISC 2.0 Contract.

The objective of this Program Management Task Order is to provide overarching program and project management support to enable the FAA to meet its mission needs through timely, effective, and integrated performance across all ISC task orders comprising the ISC Program.

1.2 Scope of Work

The scope of this Performance Work Statement (PWS) is defined in the following sections of the ISC 2.0 Contract PWS:

a. Section C.2 Scope

b. Section C.3.1 Task 1 – Program Management Support

This Program Management Task Order (herein referred to as the “Task Order”) PWS further defines the ISC 2.0 Contract PWS Task 1 requirements to provide program and project management, contract management, technical leadership and staffing, program planning, oversight, reporting and documentation, and financial and administrative management support for all task orders issued under the ISC Contract. The tasks described in this PWS are in addition to the management tasks described in other ISC task orders, thus providing a comprehensive and complementary management approach to integrated service delivery. This PWS aligns management activities to overarching ISC objectives, providing a framework for integrated management all of task order work and achievement of task order objectives from a holistic program perspective.

692M15-20-D-00004 - Program Management Support Task Order PWS

2 References The Contractor must adhere to the FAA Orders, standards, guidance, and reference materials specified herein, as applicable to this PWS, under the guidance of the Contracting Officer’s Representative (COR). These references may be updated or revised during the Task Order period of performance; the Contractor must adhere to the most current versions provided by the FAA.

a. Orders and Notices, Laws, Regulations, Policies, or Guidance:

(1) The FAA Orders and Notices applicable to performance of this Task Order are listed in ISC 2.0 Contract Exhibit C-012: Reference Information – Applicable Directives.

b. ID badge online application: https://my.faa.gov/org/linebusiness/ash/programs/id_badge.html

c. Forms: https://employees.faa.gov/tools_resources/forms/

d. ISC IDIQ 2.0 Contract Exhibits in Section C.6 are included by reference for additional information.

3 Task Requirements The Contractor must perform the tasks described in the following sections. All references to “days” throughout this PWS are business days unless otherwise specified.

Unless otherwise directed by the FAA, the Contractor must provide the facilities needed to perform all work under the ISC Contract and all task orders issued under the Contract. All Contractor facilities are subject to FAA inspection and approval.

3.1 Program, Project, and Contract Management

The Contractor must perform program management, project management, and contract management to ensure timely and effective performance across the ISC Contract, as follows:

a. Performing the necessary management and administration services and overseeing all activities performed by Contractor personnel (including subcontractors and teaming partners as applicable) to satisfy all requirements identified in the task orders issued under the Contract.

b. Effectively planning, managing, monitoring, controlling, and directing work activities and supervising Contractor personnel to support effective performance across all task orders and the achievement of ISC Contract objectives.

(1) Managing task orders issued under the ISC Contract and associated risks to ensure successful performance by continually tracking and managing the scope, schedule, budget, and quality of work performed and appropriately communicating status to the Government.

(2) Implementing the necessary processes and procedures to ensure quality, as documented in the Contractor’s Quality Management System (QMS) (required by Program Management PWS Section 3.1.2.3 and ISC Contract Section E).

c. Escalating problems with resolution recommendations to the Contracting Officer and COR in accordance with ISC Contract Section F and the Contractor’s approved Problem Escalation Process (see Program Management PWS Section 3.1.2.1).

3.1.1 Technical Leadership and Staffing

The Contractor must provide technical leadership and staffing that includes, but is not limited to:

a. Identifying, by name, a Program Manager who will provide management, direction, administration, quality assurance, and leadership for ISC task order performance.

b. Maintaining a current Contractor Key Personnel List identifying, by name, all key personnel performing work on the ISC task orders, and including contact information for all key personnel. The key personnel must work in concert with the Contractor’s Program Manager to provide day-to-day operational-level leadership and technical guidance to Contractor personnel performing work on the ISC task orders.

c. Providing the leadership, guidance, and oversight necessary to ensure work performed meets task order requirements, performance standards, and overarching ISC Contract objectives.

d. Managing the Contractor’s workforce to ensure flexibility in responding to changing requirements or priorities across the ISC Program in a timely and effective manner.

e. Implementing recruiting, hiring, and onboarding processes to staff task orders with appropriately-skilled personnel in a timely and effective manner.

f. Maintaining the technical currency of the Contractor’s IT capability, in accordance with ISC Contract Section H, to support current and future FAA requirements and special projects. This includes, but is not limited to:

(1) Maintaining a qualified and motivated workforce to support the FAA’s needs.

(2) Keeping pace with trends in technology and the marketplace.

(3) Collaborating with the FAA to identify emerging technologies and methodologies applicable to work performed under the ISC Contract.

g. Establishing and maintaining effective communication mechanisms to keep the FAA informed and to collaborate effectively with FAA representatives and other FAA support contractors performing on other related contracts.

3.1.2 Program-Level Plans

The Contractor must document its program management approach in program-level management plans. At a minimum, all program-level plans are to have at least an annual review to verify and validate that they are up-to-date. The Contractor must develop, implement, and maintain program-level management plans including, at a minimum:

a. Program Management Plan (PMP) in accordance with Program Management PWS Section 3.1.2.1.

b. QMS in accordance with Program Management PWS Section 3.1.2.3.

c. Recommended Improvement Plan in accordance with Section 4 of the ISC Contract PWS (Keeping Technology Current) and Program Management PWS Section 3.1.2.3.

d. Training Plan in accordance with Program Management PWS Section 3.1.2.4.

e. Subcontractor Management Plan in accordance with Program Management PWS Section 3.1.2.5.

f. IT Security Plan in accordance with Program Management PWS Section 3.1.2.6.

g. Continuity of Contract Performance Plan in accordance with ISC Contract Sections F and I.

3.1.2.1 Program Management Plan

The Contractor must update and maintain the PMP describing the Contractor’s management approach, operating procedures, staffing approach, and the overall Work Breakdown Structure (WBS). The PMP must contain an ISC Organizational Chart. Ancillary components of the PMP must include:

a. Risk Management Plan

b. Communications Plan

c. Change Management Plan

d. Problem Escalation Process in accordance with ISC Contract Section F

3.1.2.2 Program Initiatives Schedule

The Contractor must create, manage, and maintain a Schedule for Strategic Program Initiatives in a location that is shared with and accessible to the FAA. This schedule comprises multiple projects, spanning ISC task orders, providing an overall status of strategic initiatives across the program. Updates to be provided upon request of the COR. Performance of these duties includes such actions as:

a. Creating a Program Initiatives Schedule encompassing activities spanning ISC task orders.

b. Overall objectives with well-defined goals.

c. Steps and Milestones required to meet objectives.

d. Timeline and Progress of individual activities.

e. Assigned point of contact for tasks.

3.1.2.3 Quality Management System

The objective of the QMS is to establish performance monitoring and reporting processes and procedures which ensure the delivery of high-quality products and services. Such processes and procedures may include, but are not limited to, self-inspections, audits, tests, and program reviews to identify where Contractor performance is meeting quality standards versus where performance requires improvement or corrective action because quality standards or requirements are not being met.

In accordance with ISC Contract Section E, the Contractor must create, execute, and maintain a QMS for the ISC Program and its underlying task orders which will be reviewed and approved by the FAA. The Contractor’s QMS will be used to support any FAA Quality Assurance Surveillance Plans (QASPs) and quality requirements the FAA establishes to monitor Contractor performance on ISC task orders including, but not limited to, making any and all necessary updates to the QMS to reflect changes and/or updates to the QASPs. In addition, the Contractor must implement and perform the work under the Service Center Support Task Order using Information Technology Infrastructure Library (ITIL) methodologies. The Contractor’s QMS must sufficiently cover any task order-specific quality assurance requirements identified in other task order PWSs.

The Contractor must document, at a minimum, the following items in its QMS:

a. Quality assurance and quality control processes and procedures for complying with performance standards identified in each of the ISC task orders and any Award Fee Plan issued under the ISC Contract.

b. Techniques for measuring the quality of Contractor performance throughout the duration of the ISC Contract.

c. Communications protocols and reporting procedures to satisfy the FAA’s reporting needs.

d. Methods for preventing and eliminating the causes of unsatisfactory performance.

e. Procedures for reviewing and updating the approved QMS document on a regular basis, as directed by the COR, and as needed based on changes to ISC task orders.

f. A plan for conducting periodic QMS reviews which incorporate a “reset” process to accommodate anticipated program progress, ensure the program focuses on areas where support is needed as the program evolves over time, evaluate the effectiveness of ISC performance metrics, and make adjustments to align with the FAA’s current needs and objectives. Any significant changes that result from the “reset” process will be mutually agreed upon by the Contractor and the FAA.

As part of its QMS and in collaboration with FAA, the Contractor must develop and implement a Customer Satisfaction Measurement Plan defining effective and efficient processes and procedures for periodically assessing performance on the ISC Contract. It is anticipated that the performance evaluation process for measuring customer satisfaction will include conducting customer surveys (which are separate and distinct from the Service Center Satisfaction Surveys required by the Service Center PWS), and will take into account multiple data measures based on input from FAA lines of business/staff offices. The frequency of measurement may be based on monthly fiscal quarters or a rolling 90-day period.

Further, the Contractor must develop and implement a process to continually improve the effectiveness of its QMS, as well as its service delivery across all ISC task orders. This includes, but is not limited to:

a. Continually identifying, recommending, and implementing process improvements through the use of quality policy, quality objectives, audit results, data analysis, corrective and preventive actions, and management reviews.

b. Bringing innovation and industry best practices into the performance of ISC task orders to support operational maturity.

c. Providing suggestions to improve integration between the ISC Program and other support groups.

d. Applying lessons learned and supporting knowledge management to promote the implementation of improvements across the ISC Program.

As the Contractor identifies potential improvements, the recommendations for implementing those improvements must be proposed and documented as follows:

a. Short-term recommendations which can be implemented with minimal planning and coordination with other entities, and which do not require FAA executive approval, must be discussed during weekly Task Order Management Meetings held for each ISC task order. Such recommendations require COR approval before implementation.

b. Long-term recommendations or those requiring significant planning, coordination with other entities, or FAA executive approval must be documented in the Recommended Improvement Plan. The Recommended Improvement Plan must address ISC Program service delivery improvements, as well as technology improvements defined in ISC Contract Section C.4 – Keeping Technology Current. The Recommended Improvement Plan must be provided semi-annually, and must be discussed during quarterly Program Management Reviews (PMRs). At a minimum, long-term recommendations require COR approval before implementation, and may require approvals from FAA executives or other entities involved in or affected by the proposed improvement.

3.1.2.4 Training Plan

The Contractor must update and maintain the Training Plan describing how prime contractor and subcontractor employees will maintain required qualifications, certifications, and proficiencies, in accordance with the ISC Contract Section H (Contractor Training and Qualifications) and Exhibit C-007 (ISC Standard Labor Categories).

3.1.2.5 Subcontractor Management Plan

The Contractor must update and maintain the Subcontractor Management Plan that identifies each subcontractor (or teaming partner) and outlines the relationship between the prime and each subcontractor. (This plan is separate and distinct from the Subcontracting Plan specified in ISC Contract Sections F and I.) Items to address in the plan include, but are not limited to:

a. Describe each subcontractor’s roles and responsibilities (e.g., capabilities to be leveraged) and describe where and the extent to which each subcontractor will utilized in supporting the ISC task orders (i.e., level of subcontractor involvement and the areas of work the subcontractor will perform).

b. Describe how the prime contractor plans to manage the subcontractor resources. This must include a discussion of the integration and coordination of work activities among the prime and subcontractors, methods to be used to ensure the quality of the subcontractor’s services and deliverables, methods of reporting work progress/status, and the practices to be employed to prevent issues and enable timely, effective problem resolution.

3.1.2.6 IT Security Plan

The Contractor must identify an IT Security point of contact and must submit verification of the IT Security Plan validity annually describing the processes and procedures the Contractor will follow to ensure the appropriate security of IT resources that are developed, processed, or used under the ISC Contract. The Contractor must comply with the most recent version of all applicable Federal, Department of Transportation (DOT), and FAA guidance documents, including, but not limited to, the following: (Please note if a newer version of a document/reference exists than what has been used before, the Contractor must notify the AIT PMO (SSMO) who will make a determination as to which version applies): 40 U.S.C. § 11331, the Federal Information Security Management Act (FISMA) (https://www.cisa.gov/federal-information-security-modernization-act), and the E-Government Act of 2002. The IT Security Plan must also meet IT security requirements in accordance with Federal, Department of Transportation (DOT), and FAA policies and procedures, as may be amended from time to time during the term of the ISC Contract and which include, but are not limited to:

a. Office of Management and Budget Circular A-130 Appendix III, Security of Federal Automated Information Resources.

b. National Institute of Standards and Technology Guidelines.

c. DOT Order 1350.2.

d. FAA Security Orders, including Order 1600.1E: FAA Personnel Security Program, and Order 1370B.121: FAA Information Security and Privacy Program & Policy.

3.1.2.7 Service Center Reporting Tool

The Contractor must provide an online Service Center reporting tool to be in accordance with the Service Center Support PWS Section 3.2.5 a.

The Contractor must submit its reporting tool recommendation in writing, with sufficient detail to support the FAA’s thorough review. The Contractor’s recommendation must be approved by the FAA in writing before implementation.

3.2 Program Oversight, Reporting, and Documentation

The Contractor must support and participate in program oversight meetings and prepare a variety of program reports and other documentation necessary to review and discuss the status of program tasks, problems, risks, and other pertinent matters, and to assess performance across the ISC Program.

3.2.1 Program Oversight

3.2.1.1 Program Status and Performance Meetings

The Contractor must:

a. Participate in regularly scheduled (At least Monthly) program status and performance meetings.

b. Participate in these meetings to discuss ISC Program status.

c. Record and submit meeting minutes for COR approval no later than 5 days after each meeting.

3.2.1.2 Quarterly Program Management Reviews

The Contractor must meet quarterly with the ISC Program Management Office and COR to participate in a PMR at FAA Headquarters in Washington, DC, (or other FAA location specified in advance) to discuss, from a program perspective, the following:

a. State of ISC task orders and summary of performance by task order.

b. Overview of ISC staffing and status of subcontractors/team members.

c. Financial overview.

d. Overview of problems and corrective actions identified in Problem Notification Reports.

e. Program risks and mitigation plans.

f. Significant accomplishments since the previous review.

g. Action items from the previous review.

h. Recommendations for improvement, including recommendations concerning business management decisions and issues pertaining to task order functional requirements, as well as recommendations in the Contractor’s Recommended Improvement Plan.

The Contractor must develop and submit a PMR briefing (which includes, but is not limited to the topics outlined above) for COR review no later than 3 days prior to each PMR.

3.2.2 Program Reporting and Documentation

The Contractor must provide documentation services, which are the activities associated with developing, revising, maintaining, managing, reproducing, distributing, and archiving all reports and documentation in printable and electronic formats. Such documentation includes, but is not limited to, required and ad-hoc reports, briefings, presentations, deliverables, and information related to Contractor performance and services provided under the ISC Contract. Such documentation also includes IT service area information (e.g., project planning materials, system design specifications, procedures manuals, operation guides, performance metrics), as well as all incident data and/or any other structured data, which must be provided in an easily-portable format to maintain any relational information, as directed by the COR.

To prepare required documentation, the Contractor must perform complete, thorough, and accurate data collection, compilation, analysis, and interpretation using software, automated tools, and/or manual processes. The Contractor must provide advice and make recommendations based on the data collected and analyzed. The Contractor must also collaborate and support all regular and unplanned AIT audits of data.

For all specified meetings, the Contractor must provide meeting minutes for COR review within 5 days after each meeting, and upon COR request, the Contractor must develop and submit meeting agendas no later than 3 calendar days prior to each meeting. The Contractor must retain, file, and organize such documentation in a repository for the FAA’s efficient and effective retrieval at all times, as described in Program Management PWS Section 3.2.2.4.

3.2.2.1 Monthly Status Reports

The Contractor must provide Monthly Status Reports (MSRs) documenting the activities and progress of the previous month and identifying planned activities for the following month. MSRs must include, at a minimum:

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

b. Program Initiatives Schedule showing completion progress of milestones and activities.

c. Status of individual deliverables, including planned submission dates, actual delivery dates, acceptance dates, and corrective action(s) being taken, if any, to address rejected deliverables.

d. Identification of risk areas with recommended mitigation strategies for managing risk.

e. Status of all outstanding risks identified in previous MSRs.

f. Performance metrics by month, as defined for each task order.

g. Key personnel leave schedule for the subsequent month.

h. Confirmation that all required professional certifications are current for Contractor personnel whose positions require certification (in accordance with Exhibit C-007: ISC Standard Labor Categories). Such confirmation must include evidence of renewal or recertification for expiring/expired certifications.

i. Staffing Roster in contractor format to include current staff on all ISC task orders, and to include the following information; CLIN number, Name (Last, First), Company, Labor Category (for T&M orders as applicable), Employee Status (Active, Onboarding, Terminated, Etc), AFN Region, Work Site (FAA, SAIC, Telecommute), City, and State.

j. Any additional information pertinent to the Government in administering the performance of this effort or as requested by the COR.

3.2.2.2 Monthly Financial Overview Reports

The Contractor must prepare monthly Financial Overview Reports that include:

a. Contract Line Item Numbers (CLINs) used during month.

b. Funding by type of funding and apportioned by CLIN.

c. Funds remaining by CLIN.

d. Monthly burn by CLIN.

e. Projected date when 75% of funds will be spent by CLIN for each Task Order.

f. Projected date when funds will be exhausted by CLIN for each Task Order.

g. Travel completed for the month, including each traveler’s name, purpose of travel, and travel cost; and projected/planned travel for the subsequent month.

h. Other direct costs (ODCs) estimated, used, and remaining for the reporting period.

i. Summary of expenditures (as invoiced to date) by CLIN for the monthly reporting period, as well as cumulative year-to-date totals.

3.2.2.3 Inventory Reports

The Contractor must prepare and maintain a Government Furnished Facilities and Property Report. At a minimum, this report must contain the following:

a. Report of Supplies and Repair Parts for Replenishment, in accordance with ISC Contract Section H.

b. Report detailing the current inventory of facilities and property furnished by the Government to the Contractor.

3.2.2.4 Documentation Library

The Contractor must maintain, secure, back-up, and update the program and contract management documentation library using storage and access methodologies and technology which are appropriate for the document types being stored, and which support the agreed-upon documentation requirements and formats.

3.3 Financial and Administrative Management

The Contractor must provide all financial and administrative management support required to successfully manage the ISC Contract and meet all task order requirements. These services include, but are not limited to, travel management, personnel security, clerical, logistics, and asset management functions.

As applicable for given task orders, the Contractor must provide IT security and administrative support essential to meeting requirements and ensuring compliance with Federal policies, including but not limited to the Federal Desktop Core Configuration, FISMA, the Chief Information Officer’s Policies, and the FAA’s IT policies.

4 Transition The integrated nature of ISC Program tasks requires seamless hand-offs and uninterrupted support across the enterprise. As such, it is envisioned that, in addition to the transition requirements in each task order PWS, task order transitions will be managed and supported from a program perspective.

Each of the ISC task orders includes transition-related requirements for the discrete work to be performed under the scope of a given PWS. The incoming and outgoing contractors must work together, in collaboration with the FAA, to rationalize Transition-In and Transition-Out Plans which provide for smooth operational turnovers and minimize the impact on supported organizations across the FAA.

4.1 Kick-Off Meeting

The Contractor must participate in Task Order Kick-Off Meetings, as required in ISC Task Orders, scheduled by the Contracting Officer and attended by FAA and Contractor representatives. The purpose of this meeting is to establish the foundation, from both FAA and Contractor perspectives, for effectively managing performance across the ISC Contract and task orders.

4.2 Contract Transition-In Plan

The Contractor must support the transition of services provided under the contract when the Task Order performance period begins. The Contractor must support the orderly change from a predecessor contractor that ensures a high level of quality of work and security is maintained, are not degraded, and to exercise its best efforts and cooperate to implement an orderly and efficient transition. The Contractor must draft a comprehensive Transition-in Plan, when required by a Task Order, and updated upon the Contracting Officer’s written notice. The Transition-in Plan must, at a minimum, address the following:

1. A transition staffing plan that includes:

a. A labor category matrix reflecting resource assignments.

b. The Contractor’s plan to recruit and hire following Contract award throughout each task order transition period.

c. The strategy to train and seamlessly transition staff into each task order without impacting service delivery.

2. A plan to execute a smooth transition-in and provide service continuity.

3. Transition risks, contingencies, and the steps the Contractor will take to mitigate risks.

4. A schedule depicting the transition activities and milestones for accomplishing the ISC task order transitions. The Contractor must perform, at a minimum, the following activities during the transition-in period:

a. Perform joint inventories and inspections with the FAA and outgoing contractor(s) of all Government furnished facilities and property to establish a baseline which accounts for and ensures that proper accountability and chain of custody is maintained for any Government furnished items.

b. Develop and validate a comprehensive listing of supported IT equipment, if any, with the FAA and outgoing contractor(s).

c. Coordinate with the FAA to validate or establish priorities for supported equipment and services.

The Transition-In Plan must address any task order-specific transition-in requirements identified in the respective task order PWSs.

4.3 Contract Transition-Out Plan

Upon Contracting Officer’s direction, the Contractor must develop, document, and provide a Transition-Out Plan no later than 180 calendar days prior to the Contract end date, or earlier if directed. The Contractor’s Transition-Out Plan must facilitate the accomplishment of a seamless transition from the incumbent to the incoming contractor(s) and/or FAA personnel. The Contractor must identify transition activities, schedules, and milestones for the turnover of work centers/functions (e.g., Service Center operations, maintenance, engineering, training, asset management, and logistics functions) and identify how it will coordinate with the incoming contractor(s) and FAA personnel to transfer knowledge regarding, at a minimum:

a. Program/project management processes.

b. Points of contact.

c. Location of program/project management documentation.

d. Location of technical documentation, artifacts, and configuration data.

e. Status of ongoing technical initiatives.

f. Transition of personnel.

g. Elevated system privileges, accounts, and access in accordance with technical direction issued by the COR.

h. Inventory, inspection, and transfer of applicable software, hardware, licenses, and warranties, and the return of all Government furnished items and Contractor-maintained data and equipment, ensuring that positive control, accountability, and chain of custody are maintained through the point of turnover.

To affect a seamless transition, it is anticipated that status meetings will be conducted with pertinent stakeholders at a mutually-agreeable day and time, and that communication protocols will be established with incoming contractor(s)/FAA personnel for the duration of the transition.

5 Deliverables Schedule The Contractor is responsible for all deliverables listed in Section F of the ISC Contract.

The table below describes the deliverables required for performance of this Task Order. Unless otherwise specified, all deliverables in the following Deliverables Schedule must be submitted with a transmittal letter to the attention of the Contracting Officer and COR.

The following abbreviations are used in this schedule:

· NLT = Not Later Than

· TOA = Task Order Award

· IAW = In Accordance With All days are business days unless otherwise specified. If a deliverable submittal falls on a Federal holiday or weekend, the deliverable will be due on the next Government workday.

Deliverables must not contain proprietary markings inconsistent with the Government’s data rights set forth in the ISC Contract or as specified in this Task Order.

PWS

Section No.

Deliverable Title

Due Date/Frequency

Format Applicable Data Rights

3.5-13 Rights in Data – General (October 2014)

3.2.1.1, 3.2.2

5.1 General Acceptance Criteria

Deliverables will be inspected for content, completeness, accuracy, and conformance to applicable standards and guidelines to confirm that they meet the FAA’s needs and requirements. The general criteria for acceptance are that deliverables must:

a. Be complete and accurate in presentation and technical content;

b. Be legible and free of spelling, grammar, and typographical errors; and

c. Adhere to applicable formats, templates, and standards.

If the FAA finds that a deliverable contains excessive typographical errors or otherwise does not conform to the required format, template, or standards, the deliverable may be immediately rejected without further review and returned to the Contractor for correction and resubmission.

Final acceptance will occur when all discrepancies, errors, or other deficiencies identified in writing by the FAA have been resolved, either through correction, document updates, or other mutually-agreeable methods. If formal deliverable acceptance or rejection by the FAA is not provided to the contractor in writing within fourteen (14) calendar days, deliverables will be deemed accepted.

6 Performance Standards and Evaluation The Award Fee Plan and task order-specific Performance Requirements Summaries will be used to monitor performance at the program level.

7 Period of Performance The period of performance for this Task Order with a projected start date upon award on or around April 15, 2030 for a period of ten years.

8 Places of Performance The place of performance for this Task Order is at both Contractor site(s) and the FAA facilities listed in Exhibit C-001: Background Information – Worldwide FAA Facilities.

9 Travel and Other Direct Costs The Contractor may be required to travel during the performance of this Task Order. All travel must be in accordance with the conditions described in the ISC 2.0 Contract.

692M15-20-D-00004 - Program Management Support Task Order PWS image1.jpeg image2.jpeg