CLIN 003 PWS.docx

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

INTEGRATED SERVICE CENTER CONTRACT

LIFECYCLE ASSET MANAGEMENT – END-USER DEVICE 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

692M15-20-D-00004 - LCAM End-User Device Support Task Order PWS Page i

1 Background The FAA provides all infrastructure, hardware, and software needed to support the FAA workforce and its mission in a consistent, cost-effective, and manageable manner. The FAA Office of Information and Technology (AIT) is responsible for agency-wide Lifecycle Asset Management (LCAM)—defined as the planned technology refreshment (tech refresh) of end-user devices—to meet the FAA’s need to support the workforce while achieving the following goals:

a. Compliance with United States Code and Department of Transportation (DOT) Mandates: 49 U.S.C. 106(f)(s)(D) and DOT Orders 4357 and 435M require a sustainable electronic stewardship plan and policy for the maintenance, procurement, and replacement of computing devices.

b. Prevention of data loss and reduced work productivity: Computing hardware is a mechanical item that will eventually fail. LCAM strives to proactively replace equipment prior to data loss and work stoppage.

c. End-User Device Lifecycle: Consists of the following:

1. Technical Currency: Regular replacement and updating keeps employees using current technology to gain efficiencies in work production.

2. Repair/Replace: When remote troubleshooting fails, permanent replacements will be fulfilled to keep down time to a minimum.

3. No Longer Meets Needs: As job duties change, a swap may be required to a device with more power, or alternatively to a more mobile platform.

4. New Requirement: New requirements include new hires, or a project requiring a new hardware device (not replacing an existing device).

5. Asset Retrieval with Data Preservation: Preservation of required data (e.g. legal or manager holds), wiping, and dispositioning end-user devices.

d. Security: Regular asset tracking and hardware and software reviews keep the enterprise secure and allow non-secure items to be removed during LCAM processes.

e. Alignment with Industry Standards: The industry standard for replacement of computing devices is 20-30% per year. Proactive LCAM brings the FAA closer to the industry standard, thus improving the Agency’s ability to easily receive support from industry partners and vendors.

f. Control of Software Licensing Costs: Software licensing can be very expensive, and has been a large, uncontrolled expense for the FAA in the past. The FAA receives limited funding to procure operating system and other software licenses. Regular disposal of legacy equipment in a planned manner enables the FAA to ensure compliance with licensing, and to control the costs of unapproved licenses in use which could be discovered via scanning and may result in additional unplanned licensing costs via a process to “true up”, i.e., pay for additional licenses in use that are identified via discovery tools.

Based on these goals, the FAA LCAM Team (within the AIT Strategy and Performance Service (ASP) organization that is dedicated to the planned tech refresh of end-user devices) is responsible for replacing 25% of all personal computing devices annually based on the device purchase date and manufacturer support for the device. For fiscal year 2025, approximately 12,500 to 15,000 devices will be replaced.

The FAA selects computing device models based on the computing needs of the agency. The computing equipment is purchased via mandatory-use procurement contracts. Due to funding requirements, purchased devices to be used for LCAM replacement are typically delivered to the FAA over the course of approximately 3 months. The FAA configures devices with Standard Client baseline images. using various imaging methods in accordance with standard deployment and configuration guides (see Section 2: References below). In the future, the FAA may opt to have imaging on some or all devices completed at the manufacturer facility within the scope of the IT equipment procurement contracts. The FAA allows for post-configuration installation of FAA-approved, non-baseline software in accordance with AIT software approval processes, which may require manual installation or the use of automated installation packages over the network.

The FAA provisions devices on an ad-hoc basis in response to Helpdesk incidents and service requests and performs remote installation to deploy the computing devices. The FAA has transitioned to a user- driven model for provisioning end-user devices where deployment technicians support user-driven deployments remotely.

Core Hours FAA regular/core business hours are 0600 – 1800 local time, Monday through Friday.

1.1 Scope of Work

The scope of this PWS is defined in the following sections of the ISC 2.0 Contract PWS:

a. Section C.2 Scope

b. Section C.3.3 Task 3 – Lifecycle Asset Management – End-User Device Support To support achievement of the goals outlined above, the FAA requires qualified contractor services to assume and transform the method and quality of the FAA’s LCAM, end-user device provisioning, and asset management processes. The scope of this Lifecycle Asset Management (LCAM) End-User Device Support Task Order (herein referred to as the “Task Order”) includes, but is not limited to:

· Performing asset management activities (see Exhibit C-026), to include accurately accounting for, tracking, and managing assets across their lifecycle, and documenting, maintaining, and tracking asset information in FAA-designated inventory control systems (assets include laptops, tablets, desktops, and peripheral devices).

· Implementing and managing repeatable processes to support tech refresh activities for at least 25% of the end-user clients on an annual basis.

· Scheduling, managing, and performing computer deployments for the LCAM, break/fix or other required replacement of end-user computing devices and associated peripherals.

· Provisioning devices on an ad-hoc basis in response to Helpdesk incidents, onboarding requests and other service requests and provisioning devices for lifecycle replacement. Shipment of assets for incidents must be shipped within 24 hours of determining a replacement is required. New hire hardware should be shipped and received by the user on or before the new hire start date.

· Following naming standards to ensure assets are provisioned with the correct Active Directory attributes and all records and reports contain accurate data.

· Facilitate the repair of computers and peripherals by either coordinating with the vendor or performing the repair, ensuring systems with hardware issues are not redeployed, receiving, documenting, shipping, imaging, configuring, performing data recovery, wiping, and dispositioning end-user devices. ISC 2.0 Contract Exhibit C-005: Background Information - Standard Client Images provides information on the FAA’s current Standard Client images and associated baseline software.

· Managing, tracking and maintaining inventory of end-user devices and associated peripherals for use in resolving Helpdesk incidents to ensure re-use of in-warranty systems based on first in, first out methodologies.

· Performing intake of received shipments within one week of receipt. The documentation should include the tracking number, ticket number (if applicable), list of devices received including barcode and serial number of accountable assets and the disposition of the assets.

· Packaging and disposing of excess equipment in accordance with FAA personal property policy and guidance and ensuring assets are archived in the FAA designated inventory control system.

· Performing data recovery and other data copy activities as required by the FAA chief counsel or in the event of a hardware failure.

The Contractor must provide, via the Program Management Support Task Order, the facilities needed to perform all work under this Task Order. Contractor facilities are subject to FAA inspection in accordance with the ISC 2.0 Contract clause E.3 entitled, “Inspection of Contractor-Provided Facilities”.

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 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 that are applicable to performance of this Task Order are listed in ISC Contract Exhibit C-012: Reference Information – Applicable Directives

(2) Windows FRESH Installation Deployment and Configuration Guide, KBA00048704

(3) Commercial-off-the-Shelf (COTS) and custom software installation guides

(4) Worldwide Web Consortium, Web Content Accessibility Guidelines (WCAG): https://www.w3.org/WAI/intro/wcag.php

(5) 49 CFR Part 172 – Hazardous Materials Table, Special Provisions, Hazardous Materials Communications, Emergency Response Information, Training Requirements, And Security Plans

(6) 49 CFR Part 173 - Shippers - General Requirements For Shipments and Packagings

(7) AIT Processes contained in the AIT Process Repository: https://my.faa.gov/org/staffoffices/afn/information/processes

(8) FAA Personal Property Policy & Guidance https://my.faa.gov/org/staffoffices/afn/acq_business/aviation_property_management/property_operations/asset_management/pol_guidance

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 provide a qualified workforce to perform the tasks described in the following sections. All references to “days” throughout this PWS are business days unless otherwise specified.

The Contractor must provide the facilities needed to perform all work under this Task Order. Contractor facilities are subject to FAA inspection in accordance with the ISC 2.0 Contract clause E.3 entitled, “Inspection of Contractor-Provided Facilities.” All FAA-furnished assets managed under this Task Order will be procured and owned by the FAA.

3.1 Task Order Management Support

The Contractor must administer and manage the work performed under this Task Order to ensure timely and effective performance. The Contractor must organize, plan, schedule, implement, control, analyze, and report on all elements of the Task Order. The Contractor must participate as a member of a government-led team as requested by the COR.

3.1.1 Meetings

The Contractor must attend and participate in meetings as required by the COR to ensure the success of this Task Order. In addition, the Contractor must:

a. Participate in regular Task Order Management Meetings with and scheduled by the FAA to:

(1) Review performance, identify and determine courses of action for issues, and plan for future changes.

(2) Proactively provide actionable recommendations for improvements or changes.

When requested by the COR, the Contractor will provide meeting minutes within 5 days.

3.1.2 Quality Control Plan

The Contractor must maintain a Quality Management System (QMS), in accordance with the QMS requirements described in the Program Management Support (PM) PWS section 3.1.2.3 and additional activities specified below. The approach for quality control, includes, but is not limited to the following:

(1) Approach for meeting performance requirements specified in Attachment A of this PWS.

(2) Metrics and techniques for measuring quality and performance.

(3) Approach for eliminating the causes of unsatisfactory performance.

3.2 Lifecycle Management Process Improvement

The FAA currently uses a variety of tools to accurately track and manage end-user hardware assets throughout their lifecycle. The FAA seeks to increase LCAM efficiencies through process optimization and data/tool aggregation. The Contractor must assess the FAA’s current environment to identify areas for improvement, which includes, but is not limited to:

a. Baselining and reviewing current operating processes and procedures to identify opportunities to streamline LCAM activities and automate them where feasible and cost effective.

b. Baselining and reviewing current tools used for tracking, managing, and controlling assets, inventory, and deployment activities to identify opportunities for streamlining data management and reporting through tool enhancement, integration, and/or replacement.

c. As potential improvements are identified, recommending repeatable processes and supporting tools to implement those improvements. Such recommendations must be proposed in accordance with the ISC Program Management PWS, as follows:

(1) 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 Operational Meetings. Such recommendations require COR approval before implementation.

(2) Long-term recommendations or those requiring significant planning, coordination with other entities, or FAA executive approval must be documented in the Recommended Improvement Plan (in accordance with the Program Management PWS). The Contractor must explain how the recommended approach and tools will improve LCAM operations and data management, meet FAA operational and technical requirements, and adhere to FAA policies and guidance. The recommendations must include technical specifications for proposed tools, as well as implementation timelines and estimated costs. 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.

d. Implementing and testing the Contractor’s recommendations upon FAA approval. This includes, but is not limited to, updating and/or developing new process and procedure documentation to reflect the approved approach, enhancing or implementing approved tools, and migrating FAA asset data to the approved tools. The Contractor must coordinate with the FAA as appropriate to implement the approved recommendations and to obtain FAA confirmation of readiness to transition to the new processes and tools, ensuring no detrimental impact to the FAA at any time during or after implementation and transition. The Contractor must use current FAA processes and tools until the new processes and tools have been fully implemented and tested, and until the implementation has been approved by the FAA. Non-acceptance of the tools by the FAA must not impact performance.

e. Refining, maintaining, and managing the new processes, procedures, and environment.

These process improvement activities apply to all tasks described in this PWS and must be performed on an ongoing basis throughout the Task Order period of performance to continually improve and maintain operational currency as LCAM activities evolve over time.

3.3 Configuration Management

692M15-20-D-00004 - LCAM End-User Device Support Task Order PWS

The Contractor must perform configuration management tasks which include, but are not limited to:

a. Performing large-scale device imaging. The Contractor must provide the imaging facilities and equipment (except for Government furnished equipment which will physically connect to the FAA infrastructure). The Contractor facilities are subject to FAA inspection.

b. Imaging computing devices with the appropriate Standard Client image (see Exhibit C-005) in accordance with the FAA’s configuration, deployment, and installation guides (see PWS Section 2: References) and the checklists within these guides.

(1) The FAA may, at its convenience, reallocate some imaging responsibilities to the manufacturer(s)/vendor(s) from whom the FAA purchases computing devices. The ISC Contractor must still perform post-imaging responsibilities, such as reimaging devices, adding software components, or implementing other configuration changes, in accordance with FAA guidance and direction.

c. Testing and verifying that the images function properly and performing a quality check to confirm the completeness of the imaged device before shipment.

3.4 End-User Device Provisioning

End-user device provisioning includes providing end users with IT PC devices in response to Helpdesk incidents, onboarding requests and service requests (ad-hoc provisioning), the planned lifecycle replacement of end-user devices, and the disposition of devices in accordance with FAA policy. These tasks are detailed in the sub-sections below and require the Contractor to perform ancillary activities related to the physical movement of the devices, as well as inventory tracking and positive asset control.

The Contractor must package, ship (using FAA’s shipping services, currently GSA Advantage Delivery Services, paid for by the FAA outside the ISC Contract), receive, and store small and large quantities of devices (which includes the safe and protected movement of devices) within the Contractor’s facility. This includes, but is not limited to:

a. Packaging devices correctly for shipment in a manner that protects Government property and ensures its arrival in a new, working, and undamaged condition. The Contractor may be liable to reimburse the FAA if devices arrive damaged due to improper packaging.

b. Labeling packages to enable tracking of equipment movement and receipt.

c. Labeling packages according CFR Part 172 & 173.

d. Coordinating shipping pickup to ensure timely arrival and availability of devices for deployment.

Store devices in an organized and inventoried manner.

The Contractor must perform inventory tracking and positive asset control of end-user devices, which includes, but is not limited to:

a. Maintaining asset data in the FAA’s designated inventory tracking systems and configuration management tools for all devices deployed and replaced, in accordance with FAA guidance (personal property bulletins) and Orders (currently FAA Order 4600.27C - Personal Property Management). This includes, but is not limited to:

(1) Performing asset management/scanning of computing devices within designated timeframes to account for all movement of devices, in accordance with FAA guidance

(2) Entering all hardware asset data in the appropriate systems within designated timeframes.

(3) Capturing, storing, and reporting shipping information, to include shipping date, shipped-to location, addressee, date of receipt, name of receiver, and courier tracking number.

(4) Capturing, storing and reporting receiving information, to include courier tracking number, date of receipt, and asset information.

(5) Performing asset transfers, which includes transferring new devices to end users and accepting transfers of legacy devices from end users via entry into the proper disposition account, within designated timeframes.

(6) Updating Active Directory to accurately reflect the status of each device throughout the asset lifecycle.

(7) Applying FAA bar codes to assets in accordance with the Property Operations Division, APM-400’s Personal Property Desk Guide for Custodians and Delegates.

b. Resolving any issues with inventory lost in transit.

3.4.1 Ad-Hoc End-User Device Provisioning

The Contractor must perform all tasks required to provide end users with new and replacement devices to resolve Helpdesk incidents and service requests, in accordance with the FAA’s configuration, deployment, and installation guides (see PWS Section 2: References). These tasks include, but are not limited to:

a. Configuring, receiving, and shipping devices and peripherals using FAA’s shipping services (currently GSA Advantage Delivery Services, paid for by the FAA outside this ISC Contract) in response to Helpdesk incidents related to:

(1) Break/fix hardware.

(2) New hire hardware.

(3) Requests for hardware and peripherals.

b. Assuming responsibility for configuring and maintaining the stock of IT PCs at the Contractor’s facilities, shipping IT PCs to end users, and reconfiguring IT PCs to original configurations upon return by end users. Contractor must monitor IT PC usage and notify the FAA when inventory is low to ensure that a sufficient stock of laptops is available to meet end-user needs.

(1) For end users within the continental United States (CONUS), the Contractor must prepare an IT PC for pickup by the FAA’s selected shipper from the depot no later than 24 hours after the technician makes a determination that shipment of an IT PC is necessary, utilizing priority overnight or equivalent shipping.

The Contractor must document the following in the ITSM tool:

i. The date and time the IT PC was shipped i.e. when the shipping record was created in the shipping service’s system.

ii. The date and time the IT PC was received at the end-user’s location i.e. when the shipping receipt was recorded in the shipping service’s system.

(2) For end users outside the continental United States (OCONUS), the Contractor must ship an IT PC to arrive as quickly as possible given OCONUS shipping requirements and constraints. The Contractor must document the shipping information as defined in the prior paragraph.

(3) The Contractor must coordinate with the end user to ship the IT PC back to the Contractor for reconfiguration.

c. Maintaining a stock of peripherals such as monitors, keyboards, and mice to ship to end users for Helpdesk incident resolution. The Contractor must monitor peripheral needs/usage to ensure a stock of peripherals is available to fulfill break/fix and new hire requests:

(1) Monitors – approximately 5,000.

(2) Keyboards / Mice - approximately 1,000.

(3) Cables / cable adapters (e.g. video) – approximately 50 each of various types e.g. HDMI, DVI, and DP.

(4) Encrypted flash drives - approximately 50.

(5) Laptop bags – approximately 1,000.

(6) Batteries – approximately 500.

(7) Power adapters – approximately 1,000.

d. Preparing devices for disposition in accordance with FAA guidance. Activities may include, but are not limited to:

(1) Performing end-user data backup and storage in accordance with AIT data retention requirements.

(2) Wiping internal hard drives (e.g. account, data, and software) using approved methods after a 2-week holding period.

(3) Archiving data in accordance with FAA records management regulations and protocols.

(4) Performing disposition activities as directed by the FAA and in accordance with FAA guidelines and policies related to the security and disposition of accountable assets, as well as any applicable Standard Operating Procedures (SOPs).

(5) Performing the steps necessary to ensure assets are properly archived in FAA- designated inventory tracking systems.

(6) Travel to FAA facilities to support disposition activities as directed by the FAA.

e. Tracking and reporting on all asset inventory used to support Helpdesk incident resolution. Inventory reports related to ad-hoc end-user device provisioning must include the following elements, at a minimum:

(1) Stock of new/used computing devices and monitors on a weekly basis. Report must include make, model, count of devices, and identification of deployable devices.

(2) Stock of peripherals on a quarterly basis.

3.4.2 Lifecycle Replacement and Deployment of FAA End-User Devices The Contractor must perform all tasks required to complete lifecycle replacements (tech refreshes) of FAA end-user devices, as described in the following sub-sections and in accordance with the FAA’s configuration, deployment, and installation guides (see PWS Section 2: References).

3.4.2.1 Tech Refresh Planning

The FAA’s current goal is to replace 25% of its end-user devices annually based on device age and eligibility (using FAA-determined parameters). Currently, a combination of AIT and contractor personnel perform tech refresh planning using various tools (e.g., Belarc, BigFix, SharePoint lists and workflows, Microsoft Access) to produce the list of devices to be replaced, manage and maintain the list on an ongoing basis, and coordinate device selection with end users via the ITSM solution.

Under this Task Order, the Contractor must assume responsibility for developing, managing, and maintaining the list/schedule of devices to be replaced based on FAA rules and guidelines. On an annual basis and in coordination with the FAA, the Contractor must develop the list of devices to be replaced and must update the list quarterly to reflect changes in end-user needs since the annual list was created (both the annual lists and quarterly updates must be approved by the FAA). The due date for the first Contractor-developed list will be determined in coordination with the FAA based on the award date of this Task Order and the timing of tech refresh cycles in progress. The Contractor must recommend an approach (tools, processes, and resources) to tech refresh planning which will meet all task objectives and FAA requirements. The Contractor must use the FAA’s current tools and processes to perform this task until the Contractor’s proposed approach has been approved and its implementation has been accepted by the FAA. The FAA’s non-acceptance of Contractor- proposed tools and processes does not excuse the Contractor from meeting all performance requirements.

3.4.2.2 LCAM Deployment

The Contractor must support LCAM deployment activities that include, but are not limited to:

a. Developing and implementing an LCAM Deployment SOP (and supporting tools and templates as appropriate) for FAA review and approval. The SOP must describe the process for completing hardware replacements using pre-imaged computing devices in accordance with current FAA configuration, deployment, and installation guides (see PWS Section 2: References). The SOP must describe, at a minimum, how the Contractor will:

(1) Identify and record all non-baseline software and local applications/configurations prior to deployment of an end user’s device using GFE electronic discovery tools, currently Belarc.

(2) Communicate with the end user to validate the accuracy of discovery results.

(3) Perform any local configuration and data migration tasks needed to restore the end user to full service. Data migration must be performed using GFE equipage kits which currently consist of, depending on deployment methodology (remote installation vs. on site deployment), PC-Mover software, a USB transfer cable, and OneDrive.

(4) Provide the end user with replacement peripherals.

(5) Coordinate with the FAA to remediate any partially complete or unsuccessful deployments.

(6) Document deployment completion in an FAA-approved deployment tracking tool.

(7) Provide shipping label to return LCAM computers to the Depot and track the ticket until return of the LCAM computers are validated as received by the Depot.

(8) Perform asset transfers in the FAA property system of record.

b. Informing end users on the proper process to request installation of non-standard software in accordance with AIT policy, or the process to request like-function software to replace prohibited versions that may have resided on legacy devices.

c. Dispositioning non-accountable, used peripherals in accordance with FAA policy.

d. Preparing devices for disposition in accordance with FAA guidance. Activities may include, but are not limited to:

(1) Performing end user data backup and storage in accordance with AIT data retention requirements.

(2) Wiping internal hard drives (e.g., account, data, software) using approved methods after a 2-week holding period.

(3) Archiving data in accordance with FAA records management regulations and protocols.

(4) Performing disposition activities in accordance with FAA guidelines and policies related to the security and disposition of accountable assets, as well as any applicable Standard Operating Procedures (SOPs).

(5) Performing the steps necessary to ensure assets are properly archived in FAA- designated inventory tracking systems.

e. Coordinating with the COR and TOR regarding any end-user feedback which may require action to improve end-user satisfaction with devices or deployment services provided.

f. In the case of an end user’s refusal to accept a device, providing information to the TOR regarding the reason for refusal.

(1) In the case of an end user requesting a different device type the Contractor will get approved by the TOR.

3.4.3 Deployment Reporting

All deployments (ad-hoc or LCAM) require daily and weekly deployment status reporting. The Contractor must provide the following reports, at a minimum:

a. Daily status reports by deployment type which include, but are not limited to:

(1) Deployment type, LCAM, break/fix, new hire, hardware request, etc.

(2) Devices deployed, including date deployed, end user profile, and device name, model, and bar code.

(3) Devices refused, including date refused, reason for refusal, end user profile, and device name, model, and bar code.

(4) Devices replaced, including end user profile and device name, model, bar code, and serial number.

b. Weekly mass asset transfer reports for submission to APM for processing 4 Deliverables Schedule 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, and in accordance with Section F of the ISC 2.0 Contract.

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 2.0 Contract or as specified in this Task Order.

PWS

Section No.

Deliverable Title

Due Date/Frequency

Format Applicable Data Rights

User Device Support PWS Section 3.2.

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

User Device Support PWS Section 3.4.1.e 3.5-13 Rights in Data – General (October 2014)

User Device Support PWS Section 3.4.1.e 3.5-13 Rights in Data – General (October 2014)

User Device Support PWS Section 3.4.3.

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

PWS

Section No.

Deliverable Title

Due Date/Frequency

Format Applicable Data Rights

User Device Support PWS Section 3.4.2.2.

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

4.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. Inspection may include validation through the use of automated tools or testing. 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

c. Adhere to applicable formats, templates, style guides, and standards; and

d. Satisfy the applicable deliverable requirements.

If the FAA finds that a deliverable contains excessive typographical errors or otherwise does not conform to the required format, templates, 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.

5 Performance Standards and Evaluation The performance standards and methods that will be used to monitor and evaluate the Contractor’s performance are defined in LCAM End-User Device Support PWS Attachment A - Performance Requirements Summary.

6 Period of Performance The period of performance for this Task Order begins on April 15, 2025, and extends through April 14, 2026.

7 Places of Performance The place of performance for this Task Order is at both Contractor site(s) and the FAA facilities listed in ISC 2.0 Contract Exhibit C-001 - Background Information: Worldwide FAA Facilities, or other FAA facilities as requested by the FAA.

8 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.

8.1 Other Direct Costs

It is anticipated that the FAA may require the Contractor to purchase equipment, materials, ancillary supplies, or other items necessary and incidental to performance of this Task Order. Such purchases must be made in accordance with ISC 2.0 Contract Section H.*

*After Task Order award, the FAA Contracting Officer, at his/her discretion, may delegate limited approval authority to the FAA COR with specific limitations of such authority prescribed in writing, such as the dollar thresholds or types of procurement that the COR would be authorized to approve.

9 Government Furnished Facilities The FAA will provide access to its facilities for Contractor employees who are cleared for such access. Space provided in FAA facilities will be limited, and may range from a secure, temporary work area for on-site device storage and staging to an office work area that may include cubicles and desk space as determined necessary by the FAA COR, site manager.

The Contractor must maintain all work and storage areas in a clean and uncluttered condition for the safety and health of all personnel co-located in the same area. This includes the Occupational Safety and Health Administration mandates to maintain 36” walkways in all spaces occupied by the Contractor.

Attachment A: Performance Requirements Summary LCAM End-User Device Support Task Order The Government will use the table below to monitor the Contractor’s performance on this Task Order. The Contactor must report on the performance standards pertaining to each measurement area within the Monthly Status Report (as required by the ISC Program Management PWS).

Tasks

Tasks

image1.png image2.jpeg