Attachment 1 Performance Work Statement 07.28.23.pdf

PDF 492 KB Posted

Attached to
Human Factors Flight Deck Research Simulator Maintenance Support Contract
Solicitation number
6973GH-23-R-00190
Issued by

About this file

This document outlines a performance work statement for a human factors flight deck research simulator maintenance support contract. The Federal Aviation Administration's Civil Aerospace Medical Institute requires technical support services for its flight simulator program, including on-demand simulator maintenance, software support, simulator upgrades and modifications, and technical support services. The contract would cover a five-year base period from October 2023 through September 2028 with labor categories including software engineers, systems technicians, and pilot subject matter experts. Work would be performed both on-site and off-site at the contractor's location. The document provides appendices describing the FAA's simulators and support equipment, as well as qualifications for contractor personnel.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Performance Work Statement

Office of Aviation Safety (AVS) Civil Aerospace Medical Institute (CAMI)

Aerospace Medical Human Factors Division

Human Factors Flight Deck

Research Simulator Maintenance Support Contract

July 28, 2023

1.0 BACKGROUND

2.0 SCOPE OF WORK

2.1 PERIOD OF PERFORMANCE

2.2 PLACE OF PERFORMANCE

3.0 REQUIREMENTS

3.1 PROGRAM MANAGEMENT

3.1.1 LABOR CATEGORIES AND SKILL SETS

3.1.2 RESPONSE TIMES

3.2 DOCUMENTATION

3.3 SIMULATOR MAINTENANCE AND SOFTWARE SUPPORT

3.3.1 ON-DEMAND SIMULATOR MAINTENANCE

3.3.2 SOFTWARE APPLICATIONS SUPPORT SERVICES

3.4 SIMULATOR UPGRADES AND MODIFICATIONS

3.5 TECHNICAL SUPPORT SERVICES

3.10 REPORTING REQUIREMENTS

4.0 SECURITY

4.2 BADGES

5.0 TRAVEL

6.0 FAA GENERAL REQUIREMENTS

6.1 SAFEGUARDING SENSITIVE BUT UNCLASSIFIED (SBU) INFORMATION

6.2 CONTRACTOR PROVIDED HARDWARE/SOFTWARE

6.3 SOFTWARE DATA RIGHTS

6.4 NORMAL WORKING HOURS

7.0 IMPLEMENTATION PLANS

8.0 DELIVERABLES/DELIVERY SCHEDULE

8.1 POST AWARD CONFERENCE

8.2 QUALITY CONTROL PLAN

8.3 TASK PROPOSALS

8.4 MONTHLY STATUS REPORTS

8.5 MONTHLY FINANCIAL REPORT

8.6 ORAL REPORTS

9.0 REFERENCES

APPENDIX A: SIMULATORS AND SUPPORT EQUIPMENT

TECHNICALLY ADVANCED GENERAL AVIATION RESEARCH SIMULATOR (TAGARS)

ADVANCED ROTORCRAFT SIMULATOR (ARS)

VERY LIGHT JET (VLJ) SIMULATOR

MULTI-MODAL LABORATORY (M&M LAB)

UNMANNED RESEARCH SIMULATOR (URS)

INSITU’S COMMON OPEN MISSION MANAGEMENT COMMAND AND CONTROL (ICOMC2)

HEADS-UPS DISPLAY (HUD)

HMD SYMBOLOGY GENERATION SYSTEM

HEAD TRACKING SYSTEM

MVRSIMULATION VIRTUAL REALITY SCENE GENERATION (VRSG) SOFTWARE

3D PERCEPTION DOME VISUAL SYSTEM

VIDEO/AUDIO STREAM AND DATA RECORDING FOR AFTER ACTION REVIEW (VADAAR)

URS (APPLIES TO ALL 3 CONFIGURATIONS)

ARS

TAGARS

HMD

COMMON EQUIPMENT CONSIDERED EITHER ANCILLARY OR AUXILIARY TO NAMED SIMULATORS:

FRASCA VLJ

DOME

MULTI-MODAL LAB

VRSG

HEAD TRACKING SYSTEM

HUD

APPENDIX B: QUALIFICATIONS OF PERSONNEL

APPENDIX C: SAMPLE TASK PROPOSAL TEMPLATE

1.0 Background

The Federal Aviation Administration (FAA) Civilian Aerospace Medical Institute (CAMI) requires technical support services for the continuing support of the Flight Deck Simulator Program. This Performance Work Statement (PWS) identifies services the Contractor will provide to the Human Factors Research Division (AAM-500). This includes, but is not limited to, the Flight Deck Research (AAM-510) simulators, associated equipment, and support of data integrations for human factors studies as required.

The AAM-510 lab consists of aviation flight simulators and associated advanced technology for research purposes. The lab has been in operation since 1993 and is a research asset to the FAA with the purpose of supporting human factors research to promote aviation safety in the National Airspace System (NAS). Two important priorities for the lab simulators are for them to be operationally relevant to aircraft flying in the NAS today and for them to be modifiable for research purposes.

2.0 Scope of Work

The contractor must provide the AAM-510 lab with on-demand support for the laboratory simulators and equipment. This support will include, but is not limited to, preventive and reactive maintenance activities, simulator modifications, upgrades, and material (hardware/software) replacement support for CAMI’s equipment, and related documentation, reporting, and training/demonstration by request. The Government will request support on a task-by-task basis and expect the Contractor to respond within 2 business days to initiate task coordination.

The Contractor must provide the appropriate resources to perform the following major services as requested by the Government:

• Provide Software Applications development and support using the latest technologies as appropriate and in accordance with the rational unified process

(RUP).

• Provide software engineering testing, and documentation support.

• Provide Configuration Management and software process improvement services in accordance with an Integrated Capability Maturity Model (ICMM) process.

• Conduct cable management on both existing systems and new systems. Cable management refers to the way cabling is routed, organized, and supported so that server rooms and work spaces are organized and cables are easy to identify.

• Maintain and upgrade existing software application systems.

• Maintain and upgrade existing operating systems.

• Maintain and implement operating system and application software backups;

including system images and incremental backups for the purpose of recovery to be included within the scope of configuration management and/or disaster recovery standard guidelines.

Configure, install and maintain the following database systems:

• GeoServer, a Java-based server that allows users to view and edit geospatial data

• MVRsimulation terrain database, proprietary terrain database used by MVRsimulation for out-the-window visualizations

• Recommend and/or implement new reporting solutions.

• Recommend and/or implement new software and hardware solutions.

• Configure and install hardware and software products, updates and upgrades on application and database servers.

• Respond to the Government’s requests to correct hardware and software problems on applications infrastructure.

• Provide engineering planning and design services for improvement of the application systems.

• Develop and maintain technical Standard Operating Procedures (SOPs) for Software Deployment and Implementation.

• Develop training materials and user manuals and conduct training and demonstration sessions for new/upgraded software applications that the contractor provides.

• Provide operational, planning and program support as requested by the Government customer.

• Procure equipment for the laboratory as requested.

2.1 Period of Performance

The Contract is anticipated to cover a five year period, (Basic 12-month year with four 12-month options). Note: Dates subject to change based on Contract Award date.

1 Base 12 Month Period October 1, 2023 through September 30, 2024 2 Option I October 1, 2024 through September 30, 2025 3 Option 2 October 1, 2025 through September 30, 2026 4 Option 3 October 1, 2026 through September 30, 2027 5 Option 4 October 1, 2027 through September 30, 2028

2.2 Place of Performance

The Contractor will perform the services for this Contract at either their business location or the FAA CAMI (Building 13) located on the Mike Monroney Aeronautical Center (MMAC) in

Oklahoma City, OK. The need for in-person access to the lab will be determined on a task-by-task basis.

The Contractor must submit to the COR a list of the Contractor’s employee and/or sub-vendor names no later than ten (10) business days prior to the scheduled visit to the CAMI site. If any of the employees and/or sub vendor employees are non-US citizens, the Contractor must submit to the COR a list of vendor names no later than fifteen (15) business days prior to the scheduled visit. Emergency on-demand support is exempt from this requirement.

If the Contractor is not local to the Oklahoma City area and an in-person visit to the lab requires travel expenses, a travel request must be approved by the COR in advance of the visit.

The Government may ship systems for repair to the Contractor facility. The Contractor will return the asset to serviceable condition or replace it in accordance with original equipment manufacturer (OEM) operation and maintenance manuals (OMM) and CO or COR instructions.

3.0 Requirements

The simulators and simulator support equipment are used for flight deck research operations of the Human Factors Research Laboratory. The AAM-510 simulators and support equipment are complex systems and subsystems designed to meet the requirements of changing mission needs of the research program as well as evolve with the technological advances in aircraft cockpits.

Unlike training simulators, in which modification of cockpit equipment requires recertification by the FAA, the AAM-510 simulators are designed to allow reconfiguration or modification as necessary for each research study. That makes the AAM-510 simulators unique because their purpose is to facilitate human factors research.

The many complicated computer systems of the simulators are frequently modified to be responsive to the changing requirements of agency sponsors (e.g., adding GPS capability to the simulator or adding a new display type). As the aerospace industry advances with digital computer technology, the simulator hardware and software require regular upgrades and modifications to continue to perform adequately for human factors flight deck studies with up-to-date flight deck equipment.

3.1 Program Management

The Contractor must:

A. Efficiently and effectively manage the performance under this contract to ensure all the necessary technical, business, and administrative planning; organizing; managing;

coordinating; and tracking (e.g., cost, schedule, deliverables), performance management, risk management, component procurement management, system engineering management, resource management, data management, and subcontract management required to perform all the activities successfully as required in the PWS. The project manager is the primary point of contact for work to be performed under the resultant contract. The program manager must keep the COR informed of any potential problems and make recommendations for solutions.

B. Ensure that assignments are completed in a thorough and timely manner and prepare written documentation of accomplishments. The FAA requirements in performing this contract demand that the Contractor's technical and administrative services support the level of expertise and experience required; demonstrated performance of contractor personnel providing the services must be at the highest level of providing quality support.

C. Provide sufficient personnel, both in number and qualification to perform work described herein.

D. Provide sufficient oversight and supervision of the contract in order to ensure all employees are functioning within their designated labor categories and at acceptable levels of performance and are performing their designated assignments in a timely manner and that all reporting requirements are honored. The Contractor must provide a quality assurance system to ensure the Government receives quality services as specified in the contract.

E. Participate in a Contract kick-off meeting no later than five (5) days after Contract award. The Contracting Officer will schedule and lead this Kickoff Meeting. The FAA will capture minutes and forward to all parties no later than 5 days after meeting.

F. Prepare written documentation of accomplishments for inclusion in the Monthly Status and Financial Report (MSFR) (see Section 3.10);

3.1.1 Labor Categories and Skill Sets

The Contractor must provide and maintain support personnel with appropriate and relevant skills, including ongoing requisite training, to successfully complete all tasks applicable to this PWS. Personnel may be located remotely and labor categories must be flexible enough to support a variety of ranges from junior to senior level personnel. (See: Appendix B)

3.1.2 Response Times

When the Government communicates a question or a need to the contractor via email or phone, the contract must be able to acknowledge receipt of the communication within 1 business day.

For normal on-site support requests the contractor must be able to have appropriate personnel at the Government site within 10 business days. For emergency on-site support requests the contractor must be able to have appropriate personnel at the Government site within 2 business days. For support requests that do not require the contractor to be on-site, the timeframe will be situationally flexible.

3.2 Documentation

The Contractor must update and maintain all pertinent documentation for each functional area and facility as described herein, including but not limited to the following: vendor commercial off-the-shelf (COTS) documentation, product specifications, site plans/topologies, system manuals, desktop application manuals, vendor application documentation, testing, quality assurance, contingency operations, backup, recovery, restart procedures, configuration management related documentation, and all other documentation required by FAA government personnel. Documentation should be made available in hard copy or electronic format, when required.

3.3 Simulator Maintenance and Software Support

3.3.1 On-Demand Simulator Maintenance

The Contractor must provide preventive and/or reactive maintenance as requested. The Contractor technical team must excel at the following:

A. Provide all labor with appropriate skill sets to efficiently execute tasks requested and approved by the FAA.

B. Sourcing and providing parts, and consumables required to perform the tasks requested and approved by the FAA.

C. Diagnose out-of-service equipment and then propose and execute solutions approved by the

FAA.

D. Deploy personnel with the appropriate skillsets to the equipment site within the appropriate response time (see Section 3.1.2).

E. Provide highly organized cable management any time cables are touched.

F. Participate in customer meetings as requested to provide technical input.

3.3.2 Software Applications Support Services

The Contractor must provide planning, analysis, troubleshooting, integration, installation, operations, maintenance, training, documentation, and administrative services for the AAM-510 simulator systems, hardware, and applications:

1. Applications Support: The Contractor must provide applications installation, deployment, configuration management, and troubleshooting support to the end user of the applications.

2. Telecommunications Administration, Support and Maintenance: Provide support for telecommunications requirements to include cable installations, testing of fault isolation circuits to perform problem diagnostics and analysis.

3. Communications and Connectivity Maintenance and Support: Perform communications and connectivity maintenance, including coordination with agency groups, and maintenance vendors to acquire, install, integrate, coordinate, and resolve data communication and connectivity issues and problems.

4. Network Operations: Maintain and support the computer network operations including system backups, environmental monitoring, connectivity, Uninterruptible Power Supply, communications equipment including hubs, routers, switches and all other equipment related communication software.

5. ID Administration and Management: Define, develop, manage and administer User ID, passwords and security keys (public/private, unique).

6. Address Administration: Administer and maintain network and server configurations utilizing COTS applications if necessary.

7. Inventory and Configuration Management: Maintain inventory for hardware and software according to AAM-510 policy. Maintain configuration management standards, as established by AAM-510.

8. Applications Support and Maintenance: Provide testing, installation, maintenance, management of configuration control, and administration services for applications software.

9. Performance Monitoring: Analyze and assess equipment for performance degradation, including determination of hardware, software, networking, and/or technical changes to meet operating requirements as necessary.

10. Documentation: Maintain documentation on how software/hardware is installed.

Document standard operating procedures and backup procedures. Maintain updates as changes occur within operating network environment.

11. Recommend Emerging Technologies: As directed, evaluate hardware, firmware, peripherals, and software packages for potential use by the Flight Deck Human Factors Research Laboratory, and provide recommendations for their integration into the environment.

12. Specific/Special Tasking: Specific tasking support for AAM-510 includes, but is not limited to, configuring and deploying new hardware and software for the laboratory, and physical relocation of equipment.

3.4 Simulator Upgrades and Modifications

The Contractor must provide simulator upgrades and modifications as requested. The Contractor technical team must excel at the following:

A. Provide all labor with appropriate skill sets to efficiently execute the simulator upgrade and/or modifications requested by the FAA.

B. Sourcing and providing parts, and consumables required to perform the upgrade/modification requested by the FAA.

C. Deploy personnel with the appropriate skillsets to the equipment site within the appropriate response time (see Section 3.1.2).

D. Knowledgeable about the kind of upgrades and modifications possible for various simulator types to support FAA planning for upcoming research studies.

E. Provide highly organized cable management any time cables are touched.

F. Participate in customer meetings as requested to provide technical input.

3.5 Technical Support Services

AAM-510 requires technical support of ongoing maintenance, modification, and upgrades of its Aviation Research Simulators to facilitate research necessary to meet mission requirements.

The technical support may consist of database maintenance, migrations & integration, and/or preventative maintenance, modifications, and upgrades to AAM-510 simulators. Technical support may be required when new avionics symbology or technology is designed, or as other sponsored research drives it. The Contractor must provide skilled staff that understands aerospace human factors research simulation and requirements to support a thriving research program and the tasks required. The Contractor must ensure that candidates have sufficient knowledge, experience, and technical skills to be recognized as having the required expertise and possess the qualifications in the general and specific areas outlined below.

3.5.1 Software Engineer/Programmer

A. Provide on-demand software configuration and programming for AAM-510 simulators.

B. Experience with JAVA, C, and C++ software languages C. Experience with Operator CNTOS version O and higher D. Develop and maintain software programs for AAM-510, as requested, in accordance with approved system/subsystem design requirements and specifications.

E. Must be able to perform complex analytical projects as part of the AAM-510 Simulator Team throughout the life cycle of the simulators.

F. Must be able to analyze processes and procedures and create program design modifications to support research of emerging technologies across the NAS.

G. Must be able to implement and utilize unit testing frameworks when appropriate.

H. Must provide documentation to support analysis, design, and development activities.

I. Must have the ability to work with OEM frameworks, and experience with ZedaSoft’s Container

Based Architecture (CBA) is preferred.

3.5.2 Sr. Software Architect

A. Must be able to define requirements, conceptualize simulator hardware and software, develop system designs, present alternative designs and make recommendations for possible system enhancements.

B. Experience with JAVA, C, and C++ software languages C. Experience with Operator CNTOS version O and higher D. Experience working with Container Based Architectures (CBAs) E. Must be able to direct the efforts of programmers.

3.5.3 Programming Analyst

A. Responsibilities include applying specialized technical and analytical skills and techniques in the support of the AAM-510 Simulator Program.

B. Must be able to assist in the definition of program requirements, assessment of required resources, identification of processes and procedures, addressing of outstanding issues for resolution and description of alternative approaches.

C. Must be able to propose and/or develop methodologies for the conversion of AAM-510 Simulator Program operation/program data into appropriate electronic format.

3.5.4 Systems Technician

A. Must be able to perform tasks related to electrical and computer fabrication

B. Must be able to work directly in the wiring and fabrication of simulator systems and subsystems.

C. Must have basic understanding of wiring and fabrication of electrical and mechanical panels, switches and related electrical and mechanical equipment.

3.5.5 Pilot: Subject Matter Experts

A. Must be a Certified Commercial Pilot with an Instrument Rating B. Must have professional experience with aircraft simulators

3.5.6 Project Manager

A. Must provide the following:

• Managing a project’s timeline, cost, and quality to meet customer expectations

• Preparing project proposals with realistic timeline and cost projections

• Preparing post-task summaries with actual timeline and cost information

• Professional communication with Government customers

• Proactive communication and planning for anticipated customer needs and/or foreseen issues

• Timely submission of monthly reporting and invoicing

• Organized invoicing that provides transparency of cost per task

• Quality control checking during project execution

• Participation in recurring Status Update Meetings with customer, and other meetings as needed.

3.6 General Qualifications

A. All labor categories require the best combination of expertise and competence available to perform the duties described in the Service Contract Act Directory of Occupations issued by the Department of Labor and have the work/skills defined in this PWS that are obtainable at prevailing or negotiated wage rates. The scope of this PWS is not meant to exclude administrative tasks or specific efforts under a task that may require unique/temporary combinations of expertise, competence and/or responsibility.

B. The Contractor must provide capable employees trained and qualified as outlined below.

All employees must be able to speak, read, write, and understand English fluently. All employees must be competent using email and Microsoft Office products (Word, PowerPoint, and Excel).

C. The Contractor must provide support services including administration, management, and performance of the tasks outlined in this PWS. The Contractor must be able to perform to Federal Aviation Regulation (FAR) Part 67, ISO-9001 certified FAA AVS QMS procedures and written policies.

D. The Contractor must be able to hire and maintain key personnel and keep its staff current and be capable of providing the necessary services in the fulfillment of the Aerospace Human Factors Research mission.

E. The Contractor is solely responsible for hiring, selecting/non-selecting, upgrading/promoting, making work assignments, providing work-related awards or discipline, approving work schedules/absences, handling labor-management issues, career planning, and compensation for all employees working under this PWS. Any suspected or actual incident of FAA personnel being involved in these processes must be reported to the CO.

F. The FAA reserves the right to direct the Contractor to remove any employee who does not comply with the provisions of the contract.

3.7 Technical Support Over and Above

The acquisition may necessitate additional support services deemed necessary to the Aerospace Human Factor Research Division. The Contracting Officer will request a proposal from the Contractor as the necessity for additional support is required (i.e. Technical Writer, General Clerk, Subject Matter Experts (SME), Simulation Specialist, Configuration Management Specialist, Computer Graphics Specialist, or other). These changes shall be incorporated into the Contract through bilateral modification.

3.8 Reporting Requirements

The Contractor will provide the following reports to the COR and Contracting Officer in Contractor format:

• Monthly Invoices within 10 days from the end of the previous month for hours incurred by contract employees itemized by position/employee.

• Document monthly reports by employee and task within 10 days from the end of previous month itemized by team.

• The Contractor must provide Monthly Status and Financial Reports (MSFRs), and any other required reports, based on the deliverables identified in this PWS. The Contractor must provide an MSFR that documents the activities of the previous month and identifies planned activities for the following month. The Contractor must deliver the reports for COR approval and must include:

Written synopsis of work completed, work in progress, and work planned for each task;

Hours expended by task, labor category, and personnel;

Status of individual deliverables;

Identification of risk areas with recommended remedial actions;

Status of all outstanding risks identified in previous MSFRs;

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

Projected date when 75% of funds are spent;

Projected date when funds are exhausted;

Other direct costs (ODCs) estimated, used, and remaining by month;

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

Individual contributions, including all activities supporting the PMO and stakeholders;

Updated Master Program Schedule; and Updated Activity Calendar

All days are business days unless otherwise specified.

Task End Result/Deliverable

Due Date Acceptance Criteria

3.1F Monthly Status and Financial Reports

10th day of the following month

The MSFRs are accurate, complete, submitted on time in the COR approved format and is prepared in accordance with PWS Section 3.

3.1D Quality Control Plan 30 days after Contract award;

updates within 15 days of COR request or change to the Contract

The QCP is accurate, complete, submitted on time in the COR approved format and is prepared in accordance with PWS Section 3

3.7.6 Program Management

Reports

Quarterly The Reports are accurate, complete, submitted on time in the COR approved format and is prepared in accordance with PWS Section 3

4.0 Security

The Contractor shall ensure that employees observe and comply with all FAA/CAMI policies, regulations and procedures concerning COVID-19, fire, safety, environmental protection, sanitation, identification, security, traffic, parking, limited access areas, gratuities, and conduct.

Contract employees working in government facilities shall be responsible for compliance with applicable building and physical security requirements. These requirements include, but are not limited to, the use of authorized entrance and exit points, responsibility for securing doors, protecting government property from loss theft abuse or damage, and the use of telephones and computers for only mission related activities. The Contractor shall be responsible for safeguarding all Government property issued for Contractor use. Specific security requirements for tasked projects shall be identified in the Task Order.

4.1 Clearances

All Contractor personnel are required to submit to a FAA Background Investigation (BI).

Contractor personnel are required to complete the security forms and forward them to the Investigations Division, prior to assignment to work location and performing work.

Contractor employees may not perform work under this task, or any subsequent sub-tasks, until they submit the security forms and FAA gives preliminary approval for assignment.

Should the FAA determine that a Contractor employee is unsuitable for a position, the Contractor employee will be denied access to FAA facilities, sensitive information, and will not be eligible for assignment to this task.

4.2 Badges

The Contractor shall be responsible for transitioning employees if required and obtaining an FAA issued visitor’s badge and car parking pass for each employee upon initial entry to the work site.

While on FAA premises, each Contractor shall wear their FAA visitor’s badge at all times in accordance with FAA/MMAC current policies and directives.

5.0 Travel

The Contractor may need to travel, as tasked, to support the program. If the Contractor must travel to provide on-site personnel, the FAA COR must approve all travel in advance of its occurrence. The Contractor will not be reimbursed for any unauthorized travel.

The Government will reimburse the Contractor for travel and per diem costs incurred only in the performance of this contract. Reimbursement will be at cost only and in accordance with Joint Travel Regulations of the Federal Government. The Government will not reimburse the Contractor for travel costs incurred in the replacement of personnel when such replacement is accomplished for the Contractor’s or employee’s convenience.

6.0 FAA General Requirements

6.1 Safeguarding Sensitive but Unclassified (SBU) Information

The Contractor must have established procedures for securing materials and data upon contract award that must include:

A. Procedures for safeguarding "Confidential" and "Sensitive" materials B. Procedures for assurance that all documents are secured at all times and are never left unattended C. Procedures to prevent discussion outside the immediate work area of information contained on any medical or other document containing personally identifiable information (PII)

D. Procedures to prevent addresses or information from being disseminated to anyone regarding a specific individual, e.g., celebrities or dignitaries

6.2 Contractor provided Hardware/Software

The Contractor may be required to provide material support for replacement, or upgrade of both hardware and software components. The cost of these supplies and materials shall be reimbursed to the Contractor as a direct cost in accordance with acceptable accounting principles and if deemed necessary by the Government in performance of work. The business practices that apply to the Contractor’s purchases should reflect a similar degree of rigor as applied to acquisitions made by the FAA. At a minimum, competition is required to be the basis for vendor selection, prices to be reasonable, and all costs to be allocated to the contract. Documentation must be present to show the competitive process that was used or the rationale for not using competition.

All purchasing documentation shall be recorded in the Government’s database of choice and shall remain the property of the FAA.

In addition, the following shall apply:

A. The Contractor shall negotiate sales tax exemptions with vendors to the maximum extent possible.

B. Purchase of supplies/tools/equipment in excess of $100.00 per purchase requires advanced approval by the Contracting Officer or designated Contracting Officer Representative.

C. Reimbursement of supplies and equipment, utilized in the performance of this PWS, will be submitted through the standard voucher method if appropriate approvals were received prior to purchase. Backup documentation regarding competitive quotes and proof of pricing that is fair and reasonable to the Government must immediately be provided for review and approval as requested by the Contracting Officer or COR.

6.3 Software Data Rights

All data produced or software developed under this contract is the property of the Government unless expressly written otherwise. The Contractor must obtain and convey appropriate warranties and data rights on the acquired COTS products to be delivered to the Government.

Data rights must permit the Government to make unlimited copies of all documentation. The Contractor must ensure such documents are free of encumbrances that would prohibit their reproduction or use by the Government for training and site operational purposes. The Contractor must identify and report all license, copyright, and proprietary restrictions that affect the Government’s ability to maintain the COTS products.

6.4 Normal Working Hours

The Contractor must be available to provide services during the Government's primary operations of 6am – 6pm Central Standard Time, Monday through Friday, except Federal Holidays or any other day(s) designated by Federal Statute, Executive Order, or Presidential Proclamation. The Eleven federal holidays include New Year's Day; Martin Luther King, Jr.

Day; Presidents' Day; Memorial Day; Juneteenth, Independence Day; Labor Day; Columbus Day; Veterans Day; Thanksgiving Day; and Christmas Day.

7.0 Implementation Plans

7.1 Management Plan

The Contractor must develop a Management Plan that details how they will manage the contract.

The Plan should detail project management practices as well as task management practices that are technically sound to support the staffing and types of tasks required under this PWS. The plan should demonstrate an understanding of the Government’s need and show an organizational chart of how personnel will be organized and managed.

7.2 Transition Plan

The Contractor must produce a Transition Plan, which provides an approach to a seamless and effective transition to full performance. An initial plan must be included in the contract proposal, with a more detailed plan submitted no later than 45 days after contract award. The plan must contain each transition action/event necessary to achieve successful transition to full performance capability, a schedule of critical milestones, and titles of Contractor personnel required to participate in each transition action/event. This plan should include a list of qualified personnel.

7.3 Close-out Plan

Approximately four weeks prior to this Task Order’s end date, the FAA will require the Contractor to provide the following:

A. All documentation as of the most recent version B. A final financial report C. A final status report that includes a projection of activities for the remainder of the Task

Order D. A closeout meeting with the FAA (details and participants to be determined by the FAA)

All FAA security badges, if issued, must be turned in to the COR by closeout of the Task/Project.

8.0 Deliverables/Delivery Schedule

8.1 Post Award Conference

The Contractor will attend a Post Award Conference to be held at the Contractor facility, FAA facility, or virtually within seven (7)-days after contract award. The Contractor must notify the Government of their preferred conference date(s) at least five (5)-days prior to the conference. At this conference, the Contractor must address the plans and schedules for the Flight Deck Research Simulator Program laboratory work efforts, and any clarification of administrative/business requirements must also be discussed.

8.2 Quality Control Plan

The QCP must describe how the Contractor plans to ensure the work meets the FAA’s expectations. The QCP may include: Proposed documentation templates, methods for monitoring progression of work, post-task simulator testing, spend down tracking, and more.

8.3 Task Proposals

The Contractor must produce a proposal for each task requested by the FAA. The proposal will include a project management sheet identifying related tasks, critical path/milestones, proposed start and completion timeframes, and estimated cost and hours. The Contractor must get the approval from COR before starting the work on the tasking.

8.4 Monthly Status Reports

The Contractor must submit monthly status reports. The status reports will be submitted to the COR, or the appointed FAA Project Manager by the 10th day of each month. The reports highlight the work performance and related activities accomplished during the prior month and the planned/expected activities for the following month. The report must clearly organize activities reported by task and be directly traceable to the invoice for the corresponding time period. The report should also include any exceptions or deviations from the planned activities.

8.5 Monthly Financial Report

A monthly financial report will be submitted no later than the 10th of each month. The report should include the following information elements at minimum:

• Financial spend-down by task (budget authorized compared to amount invoiced to date)

• Identification of which contract CLIN each task will be invoiced against

8.6 Oral Reports

The Contractor must deliver oral progress reports as requested by the COR or the assigned FAA project managers. These reports must include, but are not limited to, all of the elements listed under the monthly status reports.

8.7 Delivery Schedule

This section describes 1) the products and tangible end results that are expected from each task contained in the previous section, 2) the date each deliverable is due, and 3) the government acceptance criteria.

Task End Result/Deliverable Due Date Acceptance Criteria

1 Post Award Conference Within 7 days from contract award.

May be scheduled virtually or on-site.

2 Transitional Implementation Plan

45 days after contract award.

Plan must be delivered in MS Word, Excel, or PowerPoint and must be briefed at a meeting with the FAA.

3 Task Proposals 3 business days from receipt of Task Request.

Task Proposals must be delivered in MS Word or Excel and they must include the Contractor’s proposed milestones, timeline, and cost estimate for the tasking requested (at minimum).

4 Post-Task Summaries 5 business days from task completion.

Post-Task Summaries must be delivered in MS Word or Excel and they must directly correlate with the Project Proposal and document the actual timeline and cost used for the tasking compared to what was proposed.

5 Monthly Status Reports 10th day of each month The MSRs must provide a description of work completed per approved task. The MSR should clearly justify the number of hours invoiced for the corresponding month.

6 Quality Control Plan 30 days after Task Order award; updates within 15 days of COR request or change to the Task Order

The QCP must describe how the Contractor plans to ensure the work meets the FAA’s expectations. The QCP may include:

Proposed documentation templates, methods for monitoring progression of work, post-task simulator testing, spend down tracking, and more.

7 Monthly Financial Reports

10th day of each month The Monthly Financial Reports must break out spending by approved task and directly correspond with the Monthly Status Report and Invoice for that month.

8 Status Update Meetings

Once per month or as scheduled by FAA

The Contractor should come to the scheduled meetings prepared to discuss ongoing tasking and provide up-to-date information regarding timeline, cost, and technical details.

9 On-demand simulator maintenance, upgrades, and modifications

As requested by the FAA team and approved by the

COR

The on-demand work should only be completed after a project proposal is approved by the COR.

10 Software Data Rights As software is purchased or renewed

All software acquired through this contract must be fully available to the FAA independent of this contract.

9.0 References

All applicable FAA Orders and FAA Acquisition Management System (AMS) policies, guidelines and processes must be used. The Contractor must research and employ appropriate FAA Orders, where necessary, under the guidance of the Contracting Officer’s Representative (COR). The Contractor must ensure all work is in full compliance with:

• FAA standards and guidelines

• CAMI policies, regulations, directives and procedures

• FAA AMS guidelines

• Current International Organization of Standardization (ISO) 9000 standards

9.1 Websites:

• ID badge online application:

https://employees.faa.gov/org/staffoffices/ash/id_badge/ https://employees.faa.gov/org/staffoffices/ash/id_badge/

• Contractor & Industrial Security Program:

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.informatio n/documentid/15573

• Orders and Notices:

http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parent TopicID/184

• Forms:

http://www.faa.gov/library/forms/

• Standard Operating Procedures:

https://my.faa.gov/org/staffoffices/ang.html

• Acquisition Management System http://fast.faa.gov/

• Civil Aerospace Medical Institute https://www.faa.gov/about/office_org/headquarters_offices/avs/offices/aam/cami/

9.2 Conflict of Interest

Due to the nature of the work required by this PWS, AMS Clause 3.1.7-1, Exclusion from Future Agency Contracts, is applicable to this Task Order.

9.3 Definitions/Acronyms

As used throughout this contract, the following terms shall have the meaning set forth below and specified as applicable:

9.3.1 General Definitions

• Acceptable Quality Level (AQL) - The standard at which service is considered satisfactory as agreed upon by the Contractor and the Government.

• Compatible: The quality of handling data and programs devised from one type of computer system to another

• Computer Security-The Safeguarding of computing resources against unauthorized use, especially the protection of data from deliberate or accidental damage, unauthorized change, or disclosure of controlled or Privacy Act material.

• Contractor- The term Contractor as used herein refers to both the prime Contractor and any subcontractor. The prime Contractor shall provide a single point of contact (an employee of the prime) to coordinate all tasking, schedules, and requirements.

The Contractor shall ensure that his/her subcontracts (if any) comply with the provisions of this contract. The onsite supervisor must be an employee of the Prime Contractor.

• Contracting Officer (CO) - One with authority to enter into, administer, and/or terminate contracts and make related determinations.

• Contracting Officer’s Representative (COR) - One who is designated and authorized in writing by the CO to be responsible for surveillance/monitoring of http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentid/15573 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentid/15573 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentid/15573 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.information/documentid/15573 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/184 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/184 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/184 http://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/parentTopicID/184 http://www.faa.gov/library/forms/ https://my.faa.gov/org/staffoffices/ang.html http://fast.faa.gov/ https://www.faa.gov/about/office_org/headquarters_offices/avs/offices/aam/cami/ the Contractor's performance.

• Contractor-Owned Property- All property used on this contract that is owned or furnished by the Contractor.

• Data Integration- Combining data residing in different sources and providing users with a unified view of these bioinformatics data.

• Government Supplied Equipment- All equipment owned by or leased to the

Government or acquired by the Government under the terms of the contract.

Government supplied equipment includes equipment provided by both the Government and the Contract as defined in AMS Guidance T3.10.3.

• Quality Assurance (QA) - Those actions taken by the Government to assure services meet the acceptable quality level established by the contract between the Contractor and Government.

• Quality Control (QC) - Those actions taken by the Contractor to ensure Contractor performance meets the requirements of the contract.

• Study Ready – the state of a simulator or system that has been maintained per approved procedures and is available for use in a study without modifications.

9.3.2 Acronyms

(AAM) Office of Aviation Medicine (AGARS) Advanced General Aviation Research Simulator (AMS) Acquisition Management System (AQL) Acceptable Quality Level (AVS) Office of Aviation Safety (CAMI) Civil Aerospace Medical Institute (CBA) Container-Based Architecture (CLIN) Contract Line Item Number (CO) Contracting Officer (COR) Contracting Officer’s Representative (EA) Enterprise Architecture (FAA) Federal Aviation Administration (FAR) Federal Aviation Regulation (HF) Human Factors (HMD) Head Mounted Display (ISO) International Organization for Standardization (IT) Information Technology (MMAC) Mike Monroney Aeronautical Center

(NAS) National Airspace System (NTSB) National Transportation Safety Board (ODC) Other Direct Costs (OSHA) Occupational Safety and Health (PII) Personally Identifiable Information (PMs) Program Managers (PMO) Program Management Office (PMR) Program Management Review (PWS) Performance Work Statement (QC) Quality Control (QA) Quality Assurance

Appendix A: Simulators and Support Equipment

Technically Advanced General Aviation Research Simulator (TAGARS) Make, Year, and Airframe TAGARS uses the Piper Malibu Meridian as its aero model. The simulator was delivered by Zedasoft Inc. in 2020. The Piper Meridian model is favored for the general aviation human factors research because it is a high performance pressurized single engine aircraft capable of flying cruising above 20,000 ft. TAGARS cockpit display is fully functional with today’s typical single engine aircraft cockpits and it is easily reconfigurable to customize for individual studies.

Computers Systems TAGARS has 7 Dell 7920s, which use Linux CentOS as an operating system, and 1 Dell 7920, which uses Windows 10 as an operating system.

Avionics and Controls TAGARS uses a BRUNNER Elektronik CLS-B NG Yoke to drive the yoke of the aircraft, and a BRUNNER Elektronik Rudder with Toe Brakes to drive the rudder pedals.

The BRUNNER Elektronic systems are controlled by the Flight Model Computer using BRUNNER CLS2Sim software. The cockpit user interface is a simulated Garmin G1000, in addition to several monitor-displayed steam gauges, and physical toggle switches and buttons.

Out-the-Window (OTW) Imagery TAGARS uses the 3D Perception Dome Visual System detailed below.

Software Languages and Special Requirements TAGARS primarily uses Java built atop the ZedaSoft Java Container Based Architecture (CBA) framework. CBA is designed for rapid development of custom solutions for easy integration of new hardware/software for simulator research applications. TAGARS uses C and C++ for the hardware drivers to communicate with components in the TAGARS cockpit. Additionally, some of the applications used in TAGARS use JOGAmp OpenGL bindings for Java, Distributed Interactive Simulation (DIS) protocol, and DISTI GLStudio for Java.

Advanced Rotorcraft Simulator (ARS)

Make, Year, and Airframe The ARS is a rotorcraft simulator that has two flight models: the Bell 206 and Bell 407.

The Bell 206 was originally delivered by Southern California Electronics (SCE) in 2015.

The Bell 407 flight model was added and delivered by ZedaSoft Inc in 2022 along with an upgraded digital electric motor feedback control loading system by Simulation and Controls Technologies, Inc.

Computer Systems

The ARS uses 3 Dell 7920s running Linux CentOS, 1 Dell 7920 running Windows 10, 1 SCT Control Loading Systems (CLS) computer running Linux CentOS, and 1 custom built PC running Windows 7. The custom built PC is used only in the Bell 206 configuration to run the flight model.

Avionics and Controls The ARS cockpit can be swapped between the Bell 407 and Bell 206 configurations. The Bell 407 cockpit uses a simulated Garmin G1000 display, as well as several physical steam gauges. The Bell 206 flight model uses an actual Garmin GTN 750 navigation system.

OTW Imagery The ARS uses the 3D Perception Dome Visual System detailed below.

Software Languages and Special Requirements The ARS primarily uses Java atop the ZedaSoft CBA framework. ZedaSoft simulator software generally uses a mix of Java, C, and C++ languages in its current software baseline as well as some applications using JOGAmp OpenGL bindings for Java, Distributed Interactive Simulation (DIS) protocol, and DISTI GLStudio for Java.

The Bell 407 has Java based software built atop ZedaSoft CBA. The Bell 206 real-time software is Java, and the real-time 206 aero model flight software comes from Presagis Helisim flight model development and real-time aero model integration software delivered by SCT in 2015.

Very Light Jet (VLJ) Simulator

Make, Year, and Airframe The Very Light Jet (VLJ) is a COTS Frasca International training simulator which simulates a Cessna Citation Mustang. The FAA uses it for Very Light Jet research studies. The VLJ was not designed for modification, so changes to the hardware are generally very limited, or will involve add on technologies not directly integrated into the

VLJ.

Computer Systems The VLJ computers operate using Windows 10.

Avionics and Controls The VLJ two seat cockpit is fitted with Garmin G1000 avionics and jet aircraft controls.

The VLJ uses a Garmin flight model and supporting electrical and environmental simulation models.

OTW Imagery MVRSimulation Virtual Reality Scene Generator (VRSG) drives the OTW graphics system. The OTW visual is projected on a 4 m diameter dome using Immersive Display Solutions blending software to warp and blend the OTW visual into a dome shape.

Software Languages and Special Requirements All Frasca software is proprietary. While the Contractor is not expected to perform any modifications to the simulator, the Contractor must be familiar with the functionality of the simulator computer hardware, cockpit controls and Garmin 1000 system to assess and report repairs and support upgrades to the FAA.

Multi-Modal Laboratory (M&M Lab)

The M&M Lab is a simulator built on X-Plane 11 and Air Traffic Control in a Box (ATCiB).

The M&M Lab will be primarily maintained and modified by FAA personnel, with Contractor support only required on occasion.

Unmanned Research Simulator (URS)

Make, Year, and Airframe The Unmanned Research Simulator is one research simulator with multiple configurations (specified below).

Operating System The URS uses 4 Xi MTower PCIe Rack Mounted Computers running Linux CentOS, and 1 Dell 7910 running Windows 10.

Avionics and Controls Four computers drive various monitors that are configured for avionics viewing and out-the-window visual scene viewing. User input can be accomplished through the use of a digital control stick and/or keyboard/mouse control input.

OTW Imagery MVRsimulation VRSG drives for the OTW graphics system, which displays as a camera mounted on the belly of the aircraft.

Software Languages and Special Requirements Contractor personnel will be required to maintain and/or modify the hardware for the URS to accommodate research…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .