PWS -- CLMRS SCM-ERP Services Acqusition 2025 -- DRAFT.pdf

U.S. Department of Transportation Federal Aviation Administration

Configuration Logistics Maintenance Resource Solutions (CLMRS) Supply Chain Management- Enterprise Resource Planning (SCM-ERP) Solution Support

Performance Work Statement (PWS)

Prepared by:

FAA AJM-233

June 18, 2025

PWS – CLMRS SCM-ERP Solution Support

June 18, 2025 Page 2

Table of Contents

1.0 INTRODUCTION

1.1 FAA

1.2 CLMRS

1.3 IFS SOFTWARE

1.4 FAA LOGISTICS CENTER ................................................ ERROR! BOOKMARK NOT DEFINED.

1.5 CONFIGURATION MANAGEMENT AUTOMATION (CMA) ERROR! BOOKMARK NOT DEFINED.

1.6 REFERENCES

2.0 SCOPE OF WORK

3.0 TASKS

3.1 CLMRS SCM-ERP SOLUTION SUPPORT

3.1.1 Program Management

3.1.3 Program Management Support

3.1.4 Software Implementation Support

3.1.5 Financial Support

4.0 PERSONNEL QUALIFICATIONS

4.1 APPLICATION PROGRAM MANAGER

4.2 SENIOR PRODUCT SPECIALIST

4.3 SENIOR BUSINESS AND ARCHITECTURAL SPECIALIST

4.4 SENIOR ANALYST AND DESIGNER

4.5 DEVELOPER (POSITION SHOULD BE CONUS BASED)

4.6 SENIOR FINANCIAL ANALYST

4.7 OTHER PERSONNEL REQUIREMENTS

5.0 OTHER TASK REQUIREMENTS

5.1 PERIOD OF PERFORMANCE

5.2 PLACE OF PERFORMANCE

5.3 GOVERNMENT FURNISHED PROPERTY AND SERVICES

5.4 HOURS OF OPERATION

5.5 OBSERVANCE OF LEGAL HOLIDAYS AND FACILITY CLOSURES

5.6 TRAVEL

5.7 SECURITY

6.0 ACRONYMS

APPENDIX A - LCSS IFS APPLICATIONS SOFTWARE

June 18, 2025 Page 3

1.0 Introduction

1.1 FAA

The Federal Aviation Administration (FAA) mission is to provide a safe, secure, and efficient global aerospace system, contribution to United States (US) national security and promoting US aerospace safety. In support of this mission, FAA’s Logistics Center maintains, repairs, and overhauls equipment for the National Airspace System (NAS). The Logistics Center supports the National Airspace System (NAS) inventory valued at $735 million. Each year, it ships and receives approximately 200,000 parts to FAA field offices and other domestic and international customers. Therefore, financial transaction data availability and integrity are of the utmost importance.

1.2 CLMRS

Configuration Logistics Maintenance and Resource Solutions (CLMRS) manages a portfolio of programs within Agency Support Programs (AJM-2300). AJM-23’s vision is to be the leader in managing value-added support services facilitating the evolution of aviation safety and efficiency. AJM-2300 expects to achieve this by fostering excellence in leadership, teamwork, and through expert application of both innovative approaches and best practices for its stakeholders. The CLMRS Program Office is the organization and portfolio of programs and activities to sustain, enhance and develop new capabilities for Tech Ops’ maintenance and supply chain information systems. CLMRS’ vision is to revolutionize configuration management, logistics and maintenance for the FAA.

1.3 IFS Software

IFS Software is a Commercial of the Shelf (COTS) ERP Software that the FAA configures for supply chain operations purposes. IFS ERP combined with technical infrastructure and interfaces make up the FAA’s Supply Chain Management – Enterprise Resource Planning (SCM-ERP) system. The FAA refers to “IFS Cloud” as “IFS vCloud” in some contexts and is currently undergoing an upgrade from IFS Apps 10 to IFS vCloud. CLMRS programs leverage IFS Software and will continue seeking ways to optimize its use.

1.4 References

1) Contractor performance shall be in accordance with FAA 1370.121B - FAA Information Security and Privacy: Policy .

2) New vulnerabilities will be reviewed and assessed as required. The Department of Transportation (DOT) Cybersecurity Compendium requires the following remediation thresholds for a Moderate system.

• Critical severity within seven (7) days.

• High severity within sixty (60) days.

June 18, 2025 Page 4

• Medium severity within ninety (90) days.

• Low severity within technical capability and Authorizing Official’s (AO's) discretion.

For vulnerabilities not remediated within the prescribed thresholds, SCM-ERP Security will track and document the planned remediation actions by creating a Plan of Action and Milestone (POAM) and entering it into Cyber Security Assessment & Management (CSAM: “SMART”) within thirty (30) days for Critical, High and Medium vulnerabilities.

3) All products and services provided by the Contractor must meet the Electronic and

Information Technology Accessibility Standards (36 CFR Part 1194) to comply with Section 508 of the Rehabilitation Act of 1973. The Contractor must comply with the following standards:

• 1194.21 Software Applications and Operating Systems

• 1194.22 Web-Based Intranet and Internet Information and Applications

• 1194.26 Desktop and Portable Computers

• 1194.31 Functional Performance Criteria

• 1194.41 Information, Documentation and Support

2.0 Scope of Work

In support of the FAA mission of maximizing NAS capacity by:

1) the right parts

2) quality service

3) accurate data

4) effective costs

5) on time all the time

The Contractor must provide experienced expert services on the IFS ERP software in support of investment analysis, solution enhancement design, solution implementation, IFS ERP sustainment, and program management on an as-needed basis as defined by Task Orders issued by the FAA throughout the period of performance. The Contractor must have flexibility to deliver on each Task Order with one or more of the following, depending on FAA needs at that time: advisory services, training and enablement services, operational application management services, upgrade support services, and staff augmentation for the IFS platform to support enhancement and sustainment of existing IFS modules and applications within the SCM-ERP platform.

The Contractor must have flexibility and responsiveness to be able to deliver outcomes, as defined by Task Orders issued by FAA, to support FAA in its ongoing efforts to optimize its use of IFS Software without modification of source code (no customizations). While some of FAA’s needs can be determined months in advance, some high-priority needs may arise due to unforeseen circumstances that will require the Contractor to respond to a Task Order, provide necessary resources, and begin work quickly and provide fast turnaround.

June 18, 2025 Page 5

The Contractor must provide one or more key personnel who will be actively engaged with FAA to understand FAA’s implementation of IFS and make informed recommendations as needed.

The Contractor must ultimately provide experienced expert services on the IFS ERP and the FAA application of the IFS product within both Technical and Business Process contexts. As such, the Contractor must provide a continuity of knowledge and expertise gained and not to be lost due to fluctuations in work within the FAA or personnel changes made by the Contractor.

Both Technical and Business Process perspectives are imperative for the Contractor to ensure overall optimization of the Supply Chain.

3.0 Tasks

The services required by this contract must be performed in accordance with the requirements in this Performance Work Statement (PWS). Specific tasks will be defined via individual Task Orders issued on an as-needed basis as FAA’s needs arise throughout the period of performance.

The Contracting Officer’s Representative (COR) will direct these tasks to the Contractor using written and verbal descriptions.

The Contractor must provide deliverables that meet the requirements of the specific task. The Contractor must meet the task completion schedules and deliverable due dates required by FAA.

Contractor must submit deliverables to the COR and/or POCs designated by the COR.

Documentation deliverables must be submitted by email in editable format (i.e. not portable document format - PDF), unless the COR authorizes otherwise. Contractor must use Microsoft Office applications for documentation deliverables developed under this contract, unless the COR authorizes otherwise. All deliverables provided by the Contractor become the exclusive property of the FAA, unless existing intellectual property rights supersede that, such as for proprietary software.

3.1 CLMRS SCM-ERP Solution Support

The Contractor must provide experienced expert services on the IFS ERP software in support of investment analysis, solution enhancement design, solution implementation, IFS ERP sustainment, and program management on an as-needed basis as defined by Task Orders issued by the FAA throughout the period of performance. The Contractor must have flexibility to deliver on each Task Order with one or more of the following, depending on FAA needs at that time: advisory services, training and enablement services, operational application management services, upgrade support services, and staff augmentation for the IFS platform to support enhancement and sustainment of existing IFS modules and applications within the SCM-ERP platform. The Contractor must also support the working of FAA Service Orders with customer organizations who want to use IFS software.

3.1.1 Program Management

June 18, 2025 Page 6

The Contractor must plan, organize, direct, and control all the activities necessary to meet the requirements of this PWS. The Contractor must assign a Program Manager who has the resources and the authority to ensure efficient and timely program execution and must serve as the primary point of contact for all work performed under this contract to include directing project tasks, staffing, financial/budget tracking, and status reporting at a minimum. The Program Manager must be prepared at all times to discuss with the Government, the current status of all contract requirements.

The Contractor must describe their management approach to accomplish the required work efforts in a Program Management Plan (PMP).

The Contractor must work with FAA as a team and maintain open communications. Contractor communications with FAA must include means such as one-on-one discussions, meetings, teleconferences, electronic mail, telephone and facsimile. Contractor must use information and input provided by FAA as part of the Contractor’s completing tasks. Contractor must provide supervision of Contractor personnel.

Contractor must, as requested by FAA, deliver project management related documentation.

Contractor must promptly advise FAA of issues placing a task at risk of unsatisfactory completion in areas such as cost, schedule, and performance.

Deliverables:

1. Program Management Plan (PMP) due thirty (30) days after contract award (ACA).

2. Monthly Project Activity Report, starting thirty (30) days ACA and due monthly thereafter, for each project that includes the following:

a. Project status including costs (for the month and cumulative), schedule and performance

b. Activities completed that month

c. Activities expected to be completed next month

d. Project issues and risk mitigation

e. Project actions needed

f. Updated Microsoft Project Gantt Chart Work Plan - Must include project tasks, task durations, milestones, deliverables and travel. Must show projected completion schedules for each task, current progress for each task, and other relevant project planning and progress information.

g. Most recent copy of artifacts

h. Any additional information pertinent to the Government in administering the performance of this effort or when directed by the COR.

3.1.1.1 Program Management Reviews/Business Management Reviews

The Contractor must conduct Program Management Reviews (PMRs) and Business Management Reviews (BMRs) quarterly and present orally the program’s management, technical, schedule

June 18, 2025 Page 7 and cost status. PMRs/BMRs will be conducted in a location proposed by the Government. The date of the review will be proposed by the Government after the award; however, the Contracting Officer (CO) reserves the right to modify the meeting schedule to accommodate special program needs. The Contractor must provide briefing materials at least three (3) calendar days prior to the conduct of the review and ensure that the appropriate contractor personnel will be present. The Contractor must record and submit meeting minutes within seven (7) business days and track action items and report on them until they are closed. Topics to be addressed at the PMRs/BMRs include, but are not limited to:

• Major accomplishments since the last PMR/BMR;

• Expected major accomplishments prior to the next PMR/BMR;

• Review of action items from previous PMR/BMR;

• Status of software development, integration and /or configuration.

• Configuration Status Accounting Updates;

• Status of test and evaluation activities;

• Contractor deliverables to be delivered within the following ninety (90) calendar days, and status of changes from the previous PMR/BMR;

• Schedule status including identification of major drivers behind schedule variances and the action plans to resolve these variances, if applicable;

• Program risks or issues and status of risk mitigation activities;

• Cost/Funding status

• Current staffing roster and any changes since the last PMR/BMR or expected changes prior to the next PMR/BMR

Deliverable: Program Management Reviews/Business Management Reviews with briefing materials, minutes, and action items; PMR/BMR to be performed quarterly starting ninety (90) days ACA.

3.1.2 Quality Management

The Contractor must establish and maintain a quality management system in accordance with industry best practice as a means of assuring compliance with requirements of this contract. The Contractor must describe their quality management approach in the PMP. The FAA project managers will conduct frequent, informal, exploratory interviews with FAA stakeholders, team leads, subject matter experts, testers, and other team members to determine if the contractor’s services and deliverables are designed according to FAA standards and the scope of work.

Special attention will be given to the work documented in the quarterly PMRs and/or BMRs.

3.1.3 Program Management Support

The Contractor must provide IFS Services support for program management as requested by the CLMRS Program Office. Program Management support includes:

1. Actively participate in program meetings and teleconferences

2. Give briefings and presentations

3. Give project statuses verbally and in writing

June 18, 2025 Page 8

4. Provide program management support deliverables

1. Mentor Government personnel on IFS software as it pertains to the SCM-ERP and its applications

5. Provide knowledge transfer

6. Complete follow-on work associated with the Contractor’s tasks and deliverables

7. Complete other program management support tasks and provide associated deliverables that are within the scope of this contract

Deliverable:

1. Project Reports that include but are not limited to the following:

a. Analysis of project requirements such as technical, functional, operational, training and Business Process Re-engineering (BPR)

b. Solution alternatives analysis

c. Cost estimates

d. Risk analysis and risk mitigation recommendations

e. Resolution of issues

f. Completing actions generated from a project meeting

3.1.4 Software Implementation Support

The Contractor must provide IFS support as requested by FAA:

2. IFS software expertise both technical and functional

3. Specific IFS software expertise both technical and functional for the SCM-ERP and its applications

4. BPR expertise

5. Specific BPR expertise for the SCM-ERP and its applications

6. Advise on installation, setup and configuration of software modules performed by the

FAA

7. Training on software modules

8. Advise on Custom software development performed by the FAA

9. Implementation support in areas such as BPR, user acceptance prototypes, system testing activities, functional specifications including Reports, Interfaces, Conversions, Enhancements / Extensions (RICE) objects, proof of concept demonstrations, use of IFS software, RICE objects development, enterprise change management, end user training, pre-production pilots, system configuration, production releases, go live deployment, operations and sustainment

10. Provide software implementation support deliverables

11. Other software implementation related items that are within the scope of this contract including but not limited to: IFS platform optimization, IFS application development and optimization, IFS deliveries and updates, middleware evaluation and optimization, IFS Configurations, Reports, Integrations and Modifications (CRIMs) optimization.

Deliverable:

June 18, 2025 Page 9

1. Implementation support deliverables that include but are not limited to the following:

a. Software technical and functional documentation

b. BPR documentation

c. Installed, setup and configured software

d. Software training plan to include clear prerequisites, schedules and timing

e. Software training documentation

f. Software training

g. Software operations documentation

h. Custom software development documentation including but not limited to requirements document, design specification, test plan, test results, manuals and user guides

i. Software and source code for custom software

j. Software quality control documentation

k. Implementation deliverables in areas such as BPR, user acceptance prototypes, system testing activities, functional specifications including RICE objects, proof of concept demonstrations, use of IFS software, RICE objects development, enterprise change management, end user training, pre-production pilots, system configuration, production releases, go live deployment, operations and sustainment

l. Other software implementation related deliverables that are within the scope of this contract

3.1.5 Financial Support

The Contractor must provide IFS Systems financial support. The Contractor must support the financial automation and support the development of improved processes that will increase in detail, reduce human error, improve auditing capability, and provide for more timely reports. The Contractor must provide experienced expert assistance for understanding posting control capabilities and how to effectively capture the correct accounting on transactions as they occur.

The Contractor must provide support for bringing all financial activity inside IFS, which may include:

• Assistance with uniformity in Project/Task and remaining line of accounting (LOA), including standard general ledger (SGL)

• Posting controls customization

• Assistance with checking/validating full LOA / Project and Task prior to transmitting to

Delphi

• Development of exceptions/error queue of transactions not transmitted to Delphi

• Adding operational fields to financial reports within IFS before transferring to Delphi

4.0 Personnel Qualifications

Contractor must provide personnel with the appropriate skills to successfully complete all tasks.

Contractor must assure that persons employed on this contract possess the required skills and are assigned duties consistent with the job classifications for which they are employed. FAA expects

June 18, 2025 Page 10 the following labor categories or their equivalents may be required at some time under this contract. Those labor categories functional responsibilities, education and experience qualifications follow. FAA may waive some qualifications on a case by case basis. Other labor categories than the four described below may also be required of the Contractor depending on the specific task.

4.1 Application Program Manager

Functional Responsibilities - Serves as the contract project manager for task orders. Assists the Program Manager in interfacing with the Government CO, the task order level CORs for assigned task orders, Government management personnel, and customer agency representatives with respect to assigned task orders. Responsible for the day-to-day management (personnel, technical, and cost and schedule performance) of all work performed under assigned task order.

Allocates assigned resources for performance of task orders. Evaluates performance within assigned area of responsibility. Responsible for the complete satisfaction of all work defined by the PWS for assigned task order. May perform the functions of the Program Manager during brief absences.

Minimum Education - Master’s degree in related field.

Minimum Experience - Minimum of six (6) years’ experience in one or more of the following areas – manufacturing and planning, distribution, supply chain management, engineering and document management, maintenance management, service management, and/or finance (accounts payable, accounts receivable, general ledger).

4.2 Senior Product Specialist

Functional Responsibilities - Recognized for application implementation expertise, such as with specific products, across functional business areas within an organization. Utilizes technical area expertise to assess, select, manage, and implement application components, and to ensure that the technical solution solves the business problem as an organic part of the organization’s operational and functional baseline. Examples of the functional areas would include Distribution, Maintenance, Complex Repair, Human Resources, Finance, Supply, Service, etc. Focus is in a specific product or technology family of technologies on multiple platforms, which is supplemented with a clear understanding of the business requirements and related applications issues.

Works with product specialists to brief senior managers and end users on applications integration and functionality within the enterprise. Determines those technology inadequacies and/or deficiencies that affect the functional area’s ability to support and meet organizational goals.

Supports technical strategies that will improve productivity across functional areas within the organization. Educates others with regard to product specific best practices. Leads applications integration efforts and oversees the validation of associated work products. Provides work direction and guidance to other personnel, ensures accuracy of the work of other personnel, operates under deadlines, and is able to work on multiple tasks.

June 18, 2025 Page 11

Minimum Education - Bachelor’s degree in related field.

Minimum Experience - Minimum of six (6) years general information technology (IT) experience, including advanced training and experience in enterprise resource planning (ERP) with at least three years of this experience specifically in IFS.

4.3 Senior Business and Architectural Specialist

Functional Responsibilities - Recognized for business and/or architectural expertise with regard to ensuring functional business requirements and process issues are resolved using comprehensive applications solution sets. Works with senior managers to identify and solve functional area issues, designs business area solutions, develops conceptual business models, translates functional area business requirements into technical requirements, and supports the design and implementation of application solution sets. Plans or generates databases and/or data models that are the results of business systems planning and data requirements planning.

Provides the future business strategies as seen from a data point of view for the systems development and database administration groups.

Analyzes the information systems baseline and performs a gap analysis between the baseline, the user operational requirements, and the operating capability of application product sets.

Establishes requirements associated with the gap analysis to develop enterprise-wide systems that support organizational goals and missions. The design architecture includes the entire application, database, interface, and communications infrastructure necessary to provide for present and future operational needs. Generates business architecture alternatives that address the technology and industry trends affecting enterprise solution sets. Reviews all implementation and support activities and provides technical direction to the programming functions. Supports technical design reviews, enterprise approach validations, and work product assessments.

Provides work direction and guidance to other personnel, ensures accuracy of the work of other personnel, operates under deadlines, and is able to work on multiple tasks.

Minimum Education - Bachelor’s degree in related field.

Minimum Experience - Minimum of six (6) years general IT experience plus formal training and experience in BPR methods and in databases such as ORACLE. Minimum six years’ experience in enterprise resource planning (ERP) with at least three years of this experience specifically in IFS.

4.4 Senior Analyst and Designer

Functional Responsibilities - Performs enterprise application team lead responsibilities, including planning tasks, assigning resources to the task, monitoring and tracking progress, and informing project management on all project activities. Performs business and technical analyst functions, including workshop facilitation, business process data validation, enterprise application testing from a functional business area perspective, program development, unit testing of the application code from a technical perspective, work group and work session participation, and delivery of technical and business solutions. Implements databases that are the

June 18, 2025 Page 12 results of business systems planning and data requirements planning. Provides for systems development and database administration groups the future business strategies as seen from a data point of view.

Assists with the analysis of the information systems baseline and performs a gap analysis between the baseline, the user operational requirements, and the operating capability of application product sets. Also performs business and technical designer functions, including making contributions to both the business and technical architecture components of the solution;

supporting industry, functional area and business process specialists; supporting architecture, product, and technology specialists, and review and assess solution products for accuracy and consistency. Provides work direction and guidance to other personnel, ensures accuracy of the work of other personnel, operates under deadlines, and is able to work on multiple tasks.

Minimum Education - Bachelor’s degree in related field.

Minimum Experience - Minimum of six (6) years’ experience in enterprise applications and/or including formal training and experience in databases such as ORACLE. Minimum six years’ experience in enterprise resource planning (ERP) with at least three years of this experience specifically in IFS.

4.5 Developer (position should be CONUS based)

Functional Responsibilities - Performs development tasks in specific areas of the application such as development of Reporting and Analysis capabilities defined as Quick Report/Report Changes and/or Portals or Business Intelligence Reports. Performs core development tasks in the Base Layer of the ERP product such as Business logic changes. Provides graphical user interface (GUI) development in the core tools of IFS Applications. Assists in Configuration of the following tool sets such as IFS Admin & Security, Localization/Terms as well as Custom Events.

Minimum Education - Bachelor’s degree in related field.

Minimum Experience - Minimum of one (1) year experience in enterprise applications and/or including formal training and experience in databases such as ORACLE, M204, SYBASE, INFORMIX, DB2, etc. Minimum six years’ experience in enterprise resource planning (ERP) with at least three years of this experience specifically in IFS.

4.6 Senior Financial Analyst

Functional Responsibilities – Performs enterprise application team lead responsibilities, including planning tasks, assigning resources to the task, monitoring and tracking progress, and informing project management on all project activities. Performs business and financial analyst functions, including workshop facilitation, business process data validation, enterprise application testing from a functional business area perspective, program development, unit testing of the application code from a technical perspective, work group and work session participation, and delivery of technical and business solutions. Implements databases that are the results of business systems planning and data requirements planning. Provides for systems

June 18, 2025 Page 13 development and data base administration groups the future business strategies as seen from a data point of view.

Senior Financial Analyst will modify processes that are used in financial transactions. Senior level software developers in the financial environment will lead development teams and implement creative solutions to business needs throughout the software development lifecycle.

The developers need to understand end to end software development, testing, analytics, and coding.

Senior Financial Analyst must understand best practices of financial transactions and recommend improvements to the financial transaction process within the existing IFS software application.

Minimum Education – Bachelor’s degree in related field.

Minimum Experience – Minimum of six (6) years’ experience in enterprise applications and/or including formal training and experience in financial accounting and systematic transactions.

4.7 Other Personnel Requirements

Contractor must not employ any person who is or was an employee of the United States Government if the employment of that person would create a conflict of interest. Contract personnel must be issued a Contractor identification card identifying them as a Contractor employee, if they will work at a Government facility. The identification cards must be worn at all times while performing services under this contract when at a Government facility.

Contractor must conduct business in accordance with (IAW) the Code of Federal Regulations Title 5, Vol. 3 Employee Code of Conduct. Contractor must not employ persons on this contract if such employee is identified to the Contractor by the CO as a potential threat to the health, safety, security, and/or general well-being or operational mission of the installation and its population.

Contractor must provide FAA after contract award a list of Contractor employees working on this contract including names and position titles, with updates to this list as changes occur. All Contractor employees depending on particular condition, occasion or place, or job assignment must have professional, suitable attire.

The selection, assignment, reassignment, transfer, supervision, management and control of Contractor employees in performance of this PWS must be the responsibility of the Contractor.

The Contractor must comply with the requirements set forth in this PWS, and FAA and Mike Monroney Aeronautical Center MMAC regulations concerning conduct of employees.

5.0 Other Task Requirements

5.1 Period of Performance

June 18, 2025 Page 14

The contract has a one (1) base year period and four (4) option year periods for a total period of performance of five (5) years.

5.2 Place of Performance

The Contractor must perform work at the locations necessary to satisfactorily complete PWS tasks. FAALC expects the primary Government work location will be the MMAC in Oklahoma City, Oklahoma and may potentially transition to fully remote or hybrid (on-site and remote).

Other FAA departments may require some on-site work though remote work will generally be acceptable for most tasks.

5.3 Government Furnished Property and Services

FAA will provide office space for the Contractor when on-site at the MMAC. FAA will provide access to the FAALC Intranet and Internet to the extent considered necessary by the COR to meet program objectives. FAA will provide the Contractor with program information that FAA considers is needed to better enable the Contractor’s completing PWS tasks and providing deliverables.

5.4 Hours of Operation

Normal Contractor work hours when at MMAC are within the time period of 6:00 AM to 6:00 PM, Monday through Friday. Work on-site at MMAC outside the normal time period, including overtime (more than 40 hours per week), other than day shift, weekends and Federal holidays may sometimes be required to complete a particular task. Contractor support for times outside normal Contractor work hours and for overtime must be authorized by the COR in advance and not exceed the amount authorized in award documents issued by the CO.

Organizational hours of support may change over the course of the contract and the Contractor must support this dynamic environment. The Contractor must also support all PWS task requirements, which could result in different hours of operation being required. The Contractor must provide overtime, as required and authorized by the COR or CO to cover unforeseen workload increases or unanticipated workload surges.

5.5 Observance of Legal Holidays and Facility Closures

The Contractor must normally not be required or allowed to work when assigned to a work location at a Government facility that is on holiday or closed. During such periods, the Contractor will not be compensated for labor hours without 1) advanced direction by the CO or COR or 2) the work being a response to a Government emergency. Following is a list of United States Federal holidays and reasons for facility closures:

a. New Year’s Day, January 1

b. Martin Luther King’s birthday, the third Monday in January

c. President’s Day, the third Monday in February

d. Memorial Day, the last Monday in May

June 18, 2025 Page 15

e. Juneteenth National Independence Day, June 19

f. Independence Day, July 4

g. Labor Day, the first Monday in September

h. Columbus Day, the second Monday in October

i. Veteran’s Day, November 11

j. Thanksgiving Day, the fourth Thursday in November

k. Christmas Day, December 25

l. Any other day and time designated by Federal statute, executive order, or Presidential

Proclamation

m. Adverse weather conditions or national emergencies that require facility closure

5.6 Travel

The Contractor must travel as required to complete PWS tasks and as requested by FAA. The Contractor must not travel unless the COR or CO provides advanced authorization. Contractor must travel IAW General Services Administration (GSA) requirements and this contract.

Reimbursement for travel must not exceed the rates and expense types allowed by FAA Travel Policy and GSA Federal Travel Regulations for a Government employee traveling under similar circumstances. All travel must be authorized by the COR and CO in advance and not exceed amount authorized in award documents issued by the CO. FAA will reimburse travel IAW the Contract Travel Reimbursement Clause and Federal Travel Regulations

5.7 Security

The Contractor must comply with FAA security requirements as defined in this contract. This includes but is not limited to FAA facility access, Contractor personnel security screenings, and access to FAA information systems and data. Contractor personnel must sign a non-disclosure of information agreement in order to work on this contract, if requested by FAA.

Most Contractor work at Government locations will be performed within secure facilities. Some Contractor employees may be issued Government keys to facilitate contract performance.

Contractor must be responsible for safeguarding all Government property provided for Contractor use or under Contractor control. Whenever a work area is to be unattended for a period of time, Government facilities, equipment and materials must be secured. Contractor must provide the COR and CO a listing of Government provided property per employee and maintain that property list.

The Contractor must establish and implement methods of ensuring that all keys, identification cards and vehicle decals issued to the Contractor by the Government are not lost or misplaced and not used by unauthorized persons. No keys issued to the Contractor by the Government may be be duplicated. Issued keys must be turned in by personnel who no longer require access to locked areas. The Contractor must immediately report occurrences of lost or duplicate keys to the COR or CO. Contractor must prohibit use of Government issued keys by persons other than the Contractor’s employees. Contractor must prohibit the opening of locked areas by the Contractor’s employees to permit entrance of persons other than Contractor’s employees

June 18, 2025 Page 16 engaged in performance of assigned work in those areas, or personnel authorized entrance by the COR or CO.

June 18, 2025 Page 17

6.0 Acronyms

AJW-3 Aviation System Standards AML-40 Information Systems Group AML-90 FAA Logistics Center Logistics Transformation Office AP Accounts Payable AR Accounts Receivable AVN Aviation System Standards BPR Business Process Reengineering CBP Customs and Border Protection CM Configuration Management CO Contracting Officer (a FAA position) COR Contracting Officer’s Representative (a FAA position) COTS Commercial-off-the-Shelf ERP Enterprise Resource Planning FAA Federal Aviation Administration FAALC Federal Aviation Administration Logistics Center GL General Ledger GSA General Services Administration IAW In Accordance With IFS Industrial and Financial Systems ILM Inventory, Logistics and Maintenance IT Information Technology LCSS Logistics Center Support System LIS Logistics and Inventory System MMAC Mike Monroney Aeronautical Center NAS National Airspace System O&A Over and Above PDF Portable Document Format POC Point of Contact RICE Reports, Interfaces, Conversions and Extensions PWS Statement of Work SCM-ERP Supply Chain Management-Enterprise Resource Planning US United States

June 18, 2025 Page 18

Appendix A - LCSS IFS Applications Software

LCSS IFS Applications Software

All Access Functionality

Base Technology Licenses Foundation Runtime (includes IFS Enterprise Explorer) Application Extensibility

General Access Functionality General Document Management Quality Management Business Intelligence Base Package (includes Business Analytics) Financials General Ledger Accounts Receivable Fixed Assets Human Resources Employee Administration (HR Base Package) Strategic HR Expense Management Time and Attendance Management Payroll Administration (Payroll Transactions Interface) Engineering PDM Configuration Project Delivery Projects Sales Contract Management Project Management Project Reporting Manufacturing Costing Shop Floor Reporting with Shop Floor Workbench (Shop Floor Reporting includes Time Clock) Constraint Based Scheduling

June 18, 2025 Page 19

Shop Order Component MRO (MRO Component Repair) Repetitive Production Make and Assemble to Order Configure to Order Material Planning (Manufacturing Planning) Supply Chain Procurement (Purchasing) Customer Orders Distribution (includes Inventory) Inventory Replenishment (Inventory Planning and Replenishment) Multi-site Planning Demand Forecasting (Demand Planning) Sales and Service Field Service (Service Management) Call Center Component Repair (MRO Component Repair) Maintenance Equipment Work and Service Order Preventive Maintenance Fleet and Asset Management (Vehicle Information Management) Complex Assembly MRO (MRO Planning) Overall Equipment Effectiveness

Specific Access Functionality

CRM

Sales and Marketing Base Package Sales and Marketing Exchange Server Synchronizer Sales and Marketing Workshop Tool Sales and Marketing Import Toolkit Collaborative Solutions Collaborative Customer Quotation and Order Management Collaborative Procurement Management Collaborative Service Order Management Web Services, Instant Integrations and Tool Kits

June 18, 2025 Page 20

Strategic and Tactical Resource Planner (Rough-cut Capacity Planning and Simulation) Financial Connector Distribution: XML and EDI Messages for SCM/Distribution (IFS Webservices) Integration to Microsoft Project Integration to Primavera Project Planner P6 Industry Extensions Business Intelligence and Microsoft Reporting Package Financial KPI Functional Analysis Cube Sales Functional Analysis Cube Inventory Functional Analysis Cube Project Functional Analysis Cube Purchasing Functional Analysis Cube Maintenance Functional Analysis Cube Manufacturing Functional Analysis Cube Human Resources Functional Analysis Cube Project Reporting Functional Analysis Cube Limited Task Users (LTUs) Collaborative Procurement Management LTU

Tool Software Additional Modules as Purchased