NEXV3 SIR Sect C Amend 4.docx

693KA8-23-R-00005

Page C-1

PART I – SECTION C

STATEMENT OF WORK

TABLE OF CONTENTS

INTRODUCTION

Purpose This Statement of Work (SOW) defines the work required for the Contractor to deliver the NEXCOM Version 3 (V3) Radio equipment that meets the performance requirements specified in SIR Attachment J01 {FAA-E-37021, NEXCOM Version 3 (V3) Ultra High Frequency (UHF) / Very High Frequency (VHF) Radio Product Description (PD)}, hereafter referred to as the NEXCOM V3 Radio PD, and to deliver the Contract Data Requirement Lists (CDRLs) as defined in the Data Item Descriptions (DIDs) in SIR Attachment J02 and herein. The NEXCOM V3 Radio PD describes the functions and performance requirements necessary for the radio equipment to meet the NEXCOM V3 Radio deployment.

The Contractor must provide all necessary equipment; engineering; logistics support; maintenance/operator training; spares provisioning and maintenance program; and provide the documentation for implementation and operation for the receivers and transmitters.

Scope The NEXCOM V3 UHF/VHF Radio Contract scope encompasses all necessary equipment, software, documentation, and Contractor services required to replace existing legacy UHF and VHF radios, hereafter referred to as the NEXCOM V1 radio set. Contractor services include warranty and repair, contract and program management, configuration management, integrated logistics support, barcode and asset tracking, support of Government testing activities, development of maintenance/operator training, support of Government spares provisioning and maintenance program and other required services necessary for the implementation, maintenance, and operation of the UHF and VHF receiver and transmitter system.

The scope of this Indefinite Delivery/Indefinite Quantity (IDIQ) contract encompasses acquisition of any communications equipment and services necessary to address safety, security, supportability, and maintenance issues arising from the replacement of the NEXCOM V1 Radio equipment by NEXCOM V3 Radio equipment. NEXCOM V3 Radio equipment will replace the NEXCOM V1 Radio set at en route radio sites and at certain terminal and flight service radio sites as the FAA deems necessary. The NEXCOM V3 Radios must have Voice over Internet Protocol (VoIP) capability, which will harmonize a common standard equipment set throughout all environments in the National Airspace System (NAS).

APPLICABLE DOCUMENTS

The following documents are in effect on the date as stated and form a part of this SOW. Copies of these documents may be obtained from the links in Sections C.2.1 and C.2.2 or the Contracting Officer (CO).

Specifications

FAA:

https://www.tc.faa.gov/its/worldpac/Standards/ Standards and Orders Table 1: Standards and Orders

FAA

https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.list/documentType/order

https://www.tc.faa.gov/its/worldpac/Standards/dids/

Government Electronics Industry Association

SAE.org

Department of Defense http://quicksearch.dla.mil/

Precedence of Documents

a) In the event of conflict between the documents referenced herein and this SOW, the contents of this SOW take precedence.

b) In the event of a conflict between an FAA document and a non-FAA document, the FAA document takes precedence.

c) The Contractor must immediately notify the FAA Contracting Officer (CO) of any conflicts detected between any documentation used/referenced in this SOW.

REQUIREMENTS

The Contractor must fully manage all work to ensure its efficient and timely execution. The requirements include the specifications and standards set forth in Section C.2. The data to be delivered by the Contractor, as a result of performing the tasks prescribed by this SOW, are specified in the Contract Data Requirement Lists (CDRLs) and Data Item Descriptions (DIDs) in Attachment J02 of this contract.

Equipment & Associated Equipment/Documentation/Software The contractor must provide equipment that meets the requirements of the NEXCOM V3 Radio PD, and the Statement of Work (SOW) for the UHF and VHF Receivers and Transmitters as well as microphones. The equipment, firmware, and software provided under this contract must be supported by the Contractor for the life of this contract including exercised options and warranty period. The equipment includes the associated components, firmware, and software.

Documentation The Contractor must provide a list of the documentation for their comparable commercial-off-the-shelf (COTS) radio equipment, firmware, and software with their proposal. A final list and electronic copies (e.g., MS Word or PDF format) of this documentation, inclusive of any training documentation (if available), must be provided at the end of the Post Award Conference (PAC) as described in Section C.3.4.a.

Software The Contractor must provide and deliver to the Government all COTS executable (loadable) software in accordance with (IAW) Maintenance Data Terminal Software (MDTS) CDRL- S001 and UHF/VHF Receiver Transmitter Software/Firmware CDRL-S002, which are part of the equipment delivered by the Contractor. The Government’s requirement is to allow internal Government transfer, update, etc. of all associated software, without encumbrance, for the life of the system IAW SIR Section I, AMS Clauses 3.5-13, Rights in Data and 3.5-18 Commercial Computer Software License. The Contractor must:

a) Provide fully paid-up and transferable software licenses and the associated documents IAW Section C.3.3.1, Product Identification.

b) Provide the Government with the unrestricted authorization to prepare back-up copies without restriction of all software delivered with the equipment. Exceptions such as commercial software where the Contractor holds no license must be identified prior to Production Acceptance Test (PAT).

c) Provide the Government copies of all the Contractor’s validated software updates and modifications (e.g., routine updates to improve performance, enhance maintenance operations, correct system shortcomings) and the associated test procedures IAW CDRL-T001. Upon Government testing and approval, the software updates and modifications must be incorporated into the Configuration Status Accounting Reports (CSARs) IAW CDRL-A008 as specified by Section C.3.3.5. As the Government deems necessary in order to reflect current software releases, the contractor must also update the Product Baselines (Functional Configuration Audit (FCA) and Physical Configuration Audit (PCA).

d) Describe the process for accommodating software upgrades and future version changes IAW Section C.3.3, Configuration Management.

Maintenance Data Terminal Software (MDTS) Enterprise License Maintenance Data Terminals (MDTs) are Government laptop computers that provide the radio-equipment operator-interface. MDTs are issued to and used by FAA technicians to change parameter settings, observe readouts, and control various maintenance functions within the radio equipment.

If the Contractor’s NEXCOM V3 Radio equipment design necessitates a separate Maintenance Data Terminal Software (MDTS) executable to facilitate the MDT-to-radio equipment operator interface, then the Contractor must provide an Enterprise License for the MDTS IAW CDRL-S003. This Enterprise License must allow FAA personnel and FAA support contractors to distribute the MDTS freely, without restriction, IAW Section H.21.

CONTRACT MANAGEMENT

The Contractor must provide the required personnel and facilities to manage and administer the work required under this contract. This contract requires program management, planning, testing and testing management, configuration management, logistics planning and logistics management, quality assurance, scheduling, and coordination activities. These activities include the internal and external management activities necessary for basic contract performance, reporting progress, demonstrating results, and coordinating technical activities with the FAA.

Program Management The Contractor must maintain programmatic control over the work performed under this contract, including subcontractors and vendors. The Contractor must specify an individual who serves as the Program Manager and will manage this contract using the Program Management Plan (PMP). The Contractor must plan, schedule, budget, monitor, manage and report performance applicable to this contract. The PMP must describe the Contractor’s integrated formal reporting system and process to the Government. The Contractor’s reporting system and process must meet both the Contractor’s internal management requirements and the requirements of the FAA for timely, reliable performance reporting information. The Contractor must provide and maintain a PMP as specified by CDRL-A001 and manage the contract in compliance with the approved PMP.

Contract Work Breakdown Structure (CWBS) The Contractor must generate and maintain a CWBS to serve as a basis for contract and technical planning, scheduling, performance management, configuration management, and status reporting. The CWBS and CWBS Dictionary must be based upon the standard FAA Work Breakdown Structure (WBS) defined in the FAA Acquisition Standard Toolset (FAST – https://fast.faa.gov/docs/WBS.doc) and IAW CDRL-A002 and CDRL-A003. The CWBS must contain the data elements IAW the format in CDRL-A002.

The Contractor must extend the CWBS down to the appropriate level required to provide adequate internal management, surveillance, and performance measurement, regardless of the reporting level stipulated in this contract for FAA visibility.

Contract modifications that modify, add, or delete work scope under this contract must be incorporated into appropriate CWBS elements for work effort identification, definition, and procurement request relationships, as in the basic contract. The Contractor must not change the approved CWBS, associated definitions, or any of the reporting elements without prior written approval from the CO during the performance of this contract.

Integrated Master Schedule (IMS) The Contractor must provide an IMS IAW CDRL-A004 and must utilize it as the day to day planning and execution tool to both manage the execution of this contract and to assess program progress in meeting program requirements. The IMS must utilize the CWBS. The Contractor must report on program progress consistent with the IMS at each Program Management Review (PMR), at selected technical reviews, and at other times at the Government’s request. The Contractor must revise the IMS, when necessary, to reflect current and changing contract milestones and deliverables. The IMS must include all activities and dependencies of the Contractor, subcontractors, vendors and interrelated Government activities (e.g., Operational Test). All Contractor schedule information delivered to the Government or presented at program reviews must originate from the IMS. The Contractor must perform appropriate analyses of the IMS tasks and report potential or existing problem areas and recommend corrective actions to eliminate or reduce schedule impact to the program. The Contractor’s first submittal of the IMS must be attached to the PMP as an appendix IAW CDRL-A001.

Quality System Plan (QSP) The Contractor must have quality control over all aspects of this contract, including the production process. The Contractor must maintain and update a QSP IAW Section E, Inspection and Acceptance requirements, of this contract. The QSP CDRL-A005 that complies with Section E.2 of this contract must be attached to the PMP as an appendix IAW CDRL-A001 and integrated into the overall program. The Contractor must operate under the approved PMP and its integrated approved QSP. The Contractor must maintain quality control over work performed by subcontractors and vendors.

CONFIGURATION MANAGEMENT

The Contractor must have configuration management control over all contract deliverables including the production process. The Contractor must maintain and update a Configuration Management Plan (CMP) CDRL-A006, which is also integrated into the PMP as an appendix IAW CDRL-A001. The Contractor must maintain configuration management on all product identifiers and documentation, described in Sections C.3.3.1 and C.3.3.2 respectively, IAW the approved CMP. The Contractor must specify an individual who serves as a point of contact for all configuration management related issues. The Contractor must maintain configuration control over work performed by subcontractors and vendors to include, but not limited to, configuration identification (hardware, software, and documentation), establishment and control of configuration baselines (FCA and PCA), configuration status accounting, and audits.

Product Identification The Contractor must maintain a system to identify, barcode, label, serialize, and mark Hardware Configuration Items (HWCI), (also known as (aka) hardware identifiers), to provide traceability of all units from first delivery to final production delivery under this contract. The Contractor must maintain a system to identify, label and maintain version control of Computer Software Configuration Items (CSCI), (aka software identifiers), in order to provide traceability of delivery of all software releases under this contract. The identification processes for both HWCI and CSCI must be detailed in the CMP CDRL-A006.

Documentation Management The Contractor must deliver documents under this contract that adhere to configuration management practices as identified in Section C.3.3. The Contractor must identify by titling, labeling, numbering, identifying date of publication, identifying originator of the documentation, and cataloguing all documentation. The Contractor’s Document Management procedures must be detailed in the CMP CDRL-A006 and accomplish the following:

a) Identify specific versions of HWCI, and/or CSCI to which a document applies; and,

b) Uniquely identify the document number, edition, change status, and other identification details of each document.

Product Baseline The FAA will establish a Product Baseline after successful completion of the Factory Acceptance Test (FAT), described in Section C.3.8.3, the FCA, described in Section C.3.3.6.1, and the PCA, defined in Section C.3.3.6.2. The Product Baseline must occur prior to PAT, described in Section C.3.8.5. The software versions and components comprising the Lowest Replaceable Units (LRU) must form the basis of the Product Baseline identified in the Final Breakdown Structure (FBS), described in Section C.3.6.5. An LRU is the lowest level subassembly that can be replaced during site level maintenance activities. The Government will review for approval the results of FAT, FCA, and PCA for the establishment of the Product Baseline. The Product Baseline results in the identification of an established Government accepted baseline of hardware and software versions. The Configuration Status Accounting Report (CSAR) CDRL-A008, described in Section C.3.3.5, must be part of the Product Baseline documents submitted for review and is the mechanism for tracking changes to the Product Baseline.

Configuration Control The Contractor must extend configuration control to include hardware, software, and documentation. The Contractor must maintain a Configuration Control Board (CCB) to support baseline management of the Product Baseline. The Contractor must maintain traceability, currency of the baselines, and consistency among all project documentation, hardware, and software, as identified in Sections B1-B7 of this contract, as well as any test equipment, specialized test equipment (STE), manual and automated test plans, procedures and processes.

FAA configuration control over system functional performance will be in effect from formal approval of the FCA. FAA configuration control over the physical Form, Fit, Function or Interface (aka F3I) will be in effect from the formal PCA approval until the warranty expiration of the ultimate units delivered IAW this contract.

The terms “Form”, “Fit”, “Function” and “Deficiencies” are defined per MIL-HDBK-61B as follows:

1. Form - The shape, size, dimensions, mass, weight, and other physical parameters that uniquely characterize an item. For software, form denotes the language and media.

2. Fit - The ability of an item to physically interface or interconnect with or become an integral part of another item.

3. Function - The action or actions that an item is designed to perform; and

4. Deficiencies - Deficiencies consist of two types:

a. Conditions or characteristics in any item which are not in accordance with the item’s current approved configuration documentation.

b. Inadequate (or erroneous) configuration documentation which has resulted, or may result, in units of the item that do not meet the requirements for the item The Contractor must submit the proposed changes prior to implementing any changes into the system design. Engineering Changes and variances (formerly deviations and waivers) must be processed per Figure 1 below. The Contractor’s change notification processes must be detailed in the CMP CDRL-A006.

Figure 1: Change Notification Process Major Changes – Engineering Change Proposals (ECPSs) All Major Changes that propose changes to the Product Baseline and affect any HWCIs’ or CSCIs’ or Product Identifiers’ function, performance and/or interchangeability characteristics (i.e., formerly referred to as form, fit, function or interface (F3I) changes) will require Government approval. Any such changes, known as Major Changes as defined by EIA-649 (formerly known as Class I changes), must be submitted to the CO as ECPs IAW Figure 1 and CDRL-A007.

The Contractor is responsible for the development of ECPs and for all aspects of the implementation of the Major Change. Implementation must include, yet not be limited to, retrofit of all HWCIs or CSCIs or Product Identifiers and provision of support resources called for under the contract as updated by Major Changes per the ECP. The Contractor may also propose changes that are solely for the benefit of the Contractor; for example, where the Contractor wishes to change an approved process to increase its production capabilities without impacting the HWCIs’ or CSCIs’ or Product Identifiers’ contractual requirement.

Major Changes that are solely for the benefit of the contractor, if accepted by the CO, must be incorporated at no expense to the Government. Each proposed Major Change ECP must be limited to those changes required to accomplish the intent of the proposed change. Major Changes are defined as the following:

1) A change that affects specified and approved NEXCOM V3 Radio PD requirements for product attributes, including safety, reliability, and supportability.

2) A change, after the establishment of the Product Baseline, (i.e., the baseline for implementation of the product design, see Section C.3.3.3), that affects compatibility with interfacing products, including such products as test equipment, support equipment, software, and products furnished by a customer or that affects one or more of the following:

a. Delivered operation or servicing instructions (e.g., Technical Instruction Books (TIB), see Section C.3.6.8).

b. Required calibration to the extent that product identification, see Section C.3.3.1, should be changed.

c. Interchangeability or substitutability of replaceable products, assemblies, or components.

d. Change to add a previously non-qualified supplier, where supplier selection is specified.

e. User skills or user physical attributes.

f. Operator or maintenance training.

g. Requires retrofit of delivered products (e.g., by product recall, modification kit installation, attrition, replacement during maintenance using modified spares).

3) A change that does not impact the above criteria and would otherwise be classified as a Minor Change but does impact cost/price/delivery to customer(s), including warranties, contracted deliveries, or milestones.

4) A change that corrects a deficiency.

5) A change that impacts logistic documentation or support, and/or affects any Product Baseline documentation or the Logistics Management Information (LMI).

Major Change ECPs, approved by the CO, must be documented in the CSAR CDRL-A008. An approved Major Change ECP may require successful re-performance of FAT as described in Section C.3.8.3.

Minor Changes Minor Changes generated by the Contractor after the Product Baseline has been established, which have no impact to function, performance and/or interchangeability characteristics (i.e., provides the same F3I) will not require formal CO approval by the Government; however, this type of change, known as a Minor Change as defined by EIA-649 (formerly known as Class II change), must be determined in concert with the Government.

The QRO must notify the Contractor of a Minor Change classification concurrence or non-concurrence within five (5) business days after Government receipt. If the QRO does not notify the Contractor within five (5) business days, concurrence will be assumed.

In the event of QRO non-concurrence, the Contractor must hold further implementation of the proposed Minor Change within the Contractor’s own plant, at no cost to the Government. The Contractor may resubmit the change as a Major Change ECP or Request for Variance (RFV) within five (5) days following the QRO non-concurrence, and request review by the CO.

The Contractor must perform as directed by the CO; in the event that the Contractor disagrees, the Contractor may file an appeal under the AMS 3.9.1-1 Contract Disputes (January 2020) clause of this contract. Pending an appeal, however, the Contractor must continue to perform pursuant to the CO’s direction.

Minor Changes receiving classification concurrence from the Quality Reliability Officer (QRO), must be documented in the CSAR CDRL-A008.

Request for Variances (RFV) A variance requested during or after manufacture was formerly called a deviation or waiver. The Contractor’s change notification processes related to variances must also be detailed IAW Figure 1 and CMP CDRL-A006.

Configuration Status Accounting The Contractor must generate Configuration Status Accounting Reports (CSARs) CDRL-A008 to document changes to the Product Baseline. The CSAR identifies the HWCIs or CSCIs or Product Identifiers, status of changes, and provides the supporting documentation reflecting these changes. The CSAR must provide traceability of any change through the change control process. The first submission of the CSAR must be generated for the Product Baseline as part of establishing the baseline.

Configuration Audits The Contractor must host a Functional Configuration Audit and Physical Configuration Audit at the Contractor's facility. These audits must include all hardware, software, and documentation. The Government will disapprove the audit if identification of major discrepancies such as unbaselined (missed requirement traceability) specifications, invalid or unverified requirements and uncorrected test failures are found. The Government will indicate whether the audit is approved without conditions, approved with contingencies, or disapproved. Production orders will not be placed until all deficiencies are resolved and the audits are approved by the Government. The Government will not schedule audits until the prerequisite contract requirement is successfully completed.

Functional Configuration Audit (FCA) The purpose of the FCA is to ensure that the system meets the functional performance requirements defined in the NEXCOM V3 Radio PD. The Government will review the FAT results prior to conducting the FCA. FCA must be conducted within 60 calendar days after the successful completion of the FAT and acceptance of the FAT Report, described in Section C.3.8.3.4. The FCA is one of several meeting types outlined in Section C.3.4.c. Production orders will not be placed until the Government has approved the Contractor’s proposed corrective actions for any unresolved FCA deficiencies.

Physical Configuration Audit (PCA) The purpose of the PCA is: 1) to review top level design documentation for each LRU to validate that the Contractor has adequate engineering drawings to continue production of the hardware, software, and documentation; and 2) to identify the baselined physical characteristics of the various devices and control changes (for FAA support purposes). The PCA must be conducted no more than 60 days after the successful completion of FCA, described in Section C.3.3.6.1, on the equipment that passed the FAT. The Contractor must provide technically competent personnel to disassemble the equipment as necessary, and to respond to Government queries during the PCA.

Prior to conducting the PCA, the Contractor must resolve all action items assigned at FCA and provide documentary evidence of the resolution. The Government will not place production orders until all proposed corrective actions are approved.

The PCA is one of several meeting types outlined in Section C.3.4.d. The Contractor must describe the conduct and results of the PCA in meeting minutes (CDRL-A010). The PCA minutes must catalog any discovered deficiencies and provide conclusions and recommendations as well as planned corrective actions.

PCA Conduct The PCA baseline is established at the external perimeter of the primary LRUs, and includes all appurtenances, appliances, ancillary equipment, etc. that are part of the delivered device and/or that may be replaced for support purposes. The purpose of this baselining is to permit reliable configuration control by the FAA over the deployed equipment while avoiding unnecessary Government involvement in internal system design.

MEETINGS

The Contractor must prepare and deliver to the Government an agenda, as specified by CDRL-A009, prior to each conference and meeting. The Contractor must record and prepare minutes, as specified by CDRL-A010, for each scheduled conference and meeting. Contractor administrative support must be provided only when meetings or conferences are held at a contractor facility. Such support may consist of providing facilities, office equipment, and clerical support. The Contractor must provide facilities with adequate accommodation to house a Government team that will generally consist of no more than twenty-five (25) representatives.

The Government will not pay the direct costs for the meetings listed in a through g below, other than the price of the Contract Line Item Numbers (CLINs) associated with CDRLs A009 and A010. These meetings will be coordinated with the Contracting Officer’s Representative (COR) and approved by the CO (contractor’s facility agreed to by Contractor and FAA).

The Contractor must participate in the following meetings IAW contract requirements.

a) Post Award Conference (PAC). The Contractor must plan, host, provide administrative support, and participate in a PAC to be held at the Contractor’s facility, within the 48 contiguous states following contract award. The Government will determine the actual date of the PAC, which will occur no later than 60 calendar days after the contract award date. The PAC, which includes the Logistics Guidance Conference (LGC) and the Training Guidance Conference (TGC), is held to provide detailed clarifications of the Government’s expectations under the contract. The PAC agenda is set by the Contactor but approved by the FAA. During the PAC, the Contractor must brief the plans and schedule for satisfying each SOW requirement. The Contractor must include the finalized list of all their comparable COTS documentation and electronic copies of this documentation as part of the PAC meeting minutes IAW Section C.3.1.1.

b) Functional Configuration Audit (FCA). The Contractor must support and participate in an FCA, as described in Section C.3.3.6.1. The FCA must be at the Contractor's facility within the 48 contiguous states.

c) Physical Configuration Audit (PCA). The Contractor must support and participate in a PCA, as described in Section C.3.3.6.2. The PCA must be at the Contractor's facility within the 48 contiguous states.

d) Provisioning Conference (PC). The Contractor must support and participate in a PC, as described in Section C.3.6.4.1. The PC must be at the Contractor’s facility within the 48 contiguous states.

e) Program Management Reviews (PMRs). Four PMRs will be held annually through the first 24 months of this contract. Two PMRs will be held annually through the remaining term of this contract. The Government anticipates that all PMRs will be held at the Contractor's facility within the 48 contiguous states.

f) Technical Interchange Meetings (TIMs). The Contractor must support and participate in TIMs. The purpose of these meetings is to promote a free exchange of ideas between the Contractor and the Government in order to identify and resolve technical problems. The Contractor must provide the appropriate subject matter experts in order to respond to Government questions. The Contractor and FAA will coordinate the best location for the meetings. TIMs will be done via Task Orders utilizing the Technical Support Services CLIN(s).

g) Long Term Supportability Data Package (LTSDP) Inspections, described in Section C.3.6.10.2, must be at the Contractor's facility within the 48 contiguous states.

Teleconference meetings may be held in lieu of travel. The CO or COR will notify the Contractor of the Government's readiness at least fifteen (15) working days in advance of each teleconference.

Additionally, other technical meetings {e.g., Joint Technical Reviews (JTRs)}, logistical and/or training meetings {e.g., In-Process Reviews (IPRs)} will be held during the FAA review and approval of specific CLINs on this contract. These JTR and IPR meetings are not separately priced and are part of the Contract Data Requirements List (CDRL) for their respective CLIN.

PROGRAM REPORTING

Monthly Progress Status Report (MPSR) The Contractor must track and report the identification and status of new and existing risks, action items, problems as identified in the PMP, as well as Problem Trouble Reports (PTR) identified in the PTR process outlined in Section C.3.8.2.3. This data must be maintained for the life of this contract and no entry will be deleted without Government approval. The report must comply with CDRL-A011, the MPSR.

Monthly Financial Progress Status Report (MFPSR) The Contractor must furnish MFPSRs CDRL-A012 that state the planned and actual financial status of this contract.

The financial status information should be reported by CLIN and Task Order/modification. The reported budget and actual values and variances are FAA contract prices and not internal Contractor costs.

Monthly Delivery Performance Report (MDPR) The Contractor must submit a MDPR prepared IAW CDRL-A013. The Contractor must report summarized planned and actual performance information at each PMR, at selected technical reviews, and at other times at the Government's request.

Delivery performance information must be reported by CLIN and Task Order/Modification.

INTEGRATED LOGISTICS SUPPORT (ILS)

Point of Contact The Contractor must specify an individual who serves as a point of contact for all logistics issues.

Integrated Support Plan (ISP) The Contractor must deliver an ISP CDRL-L001. The ISP must detail the Contractor’s plan for managing the logistics requirements contained in Section C.3.6, and its subsections, for the program life cycle. The Contractor must ensure that all subcontractors and vendors comply with the ISP requirements.

Logistics Guidance Conference (LGC) As part of the PAC, described in Section C.3.4.a, the Contractor must host an LGC. The purpose of the LGC is to ensure the Contractor understands all Integrated Logistics Support tasks. Included in the LGC will be a Provisioning Guidance Conference (PGC). The purpose of the PGC is to ensure contractor’s understanding of the provisioning requirements. The Contractor must ensure the participation of appropriate Contractor/subcontractor personnel responsible for preparing the logistics deliverables specified in this contract.

Logistics Management Information (LMI) The Contractor must deliver to the Government the LMI Data Products CDRL-L002. The LMI data products must represent the physical top-down breakdown system design configuration including systems, subsystems, components, assemblies, subassemblies, cables and cable assemblies, support and test equipment, and training equipment required by the V3 radio types. Data submitted must be to the component level for all developmental items and to the LRU level for all COTS (e.g., receiver, transmitter, microphone), and non-developmental items. Any modification to a COTS item may disqualify it as COTS and may require LMI data to the component level. The Government will determine the level of LMI data required for COTS modified items. The Contractor must identify system LRUs during the LMI/Provisioning process. All items must be listed in the LMI submissions in the proper top down break down format. The Contractor must update the breakdown structure during the Government’s FCA/PCA and during the Provisioning Conference (PC) as required. After the PC the Contractor must deliver the final breakdown structure to the Government for approval IAW CDRL-L003. During the PC, the Government has the right to determine final system LRUs. Additionally, the Government reserves the right to add items it considers to be an LRU that are not considered an LRU by the Contractor. Data for temporary items is not required.

The Contractor must adhere to the data definitions, edits, and data formats as described in Appendix B of GEIA-STD-0007-C.

The Contractor must make maximum use of previously collected and analyzed data, as well as documentation prepared for COTS hardware and software components, whenever possible. Modified COTS items must be explicitly identified as modified COTS.

Provisioning Conference (PC) The Contractor must host and support PCs, as outlined in Section C.3.4.d. The Contractor must ensure the participation of contractor/subcontractor personnel knowledgeable of the V3 radio products. A PC must be held no later than 60 calendar days after Government receipt of the initial LMI data.

During the PC, the Contractor:

a) Must make all V3 radio Government-approved drawings (e.g., approved during a PCA), proprietary and non-proprietary, available for Government to use as references. The Government will not copy or remove any proprietary data from the Contractor’s facility unless the Contractor is required to submit such data as part of other submissions.

b) Must have copies of the Government-approved FCA/PCA documentation available for use as a reference.

c) Must make samples of systems, assemblies, and parts listed in the approved Product Baseline available for examination for the duration of the conference.

d) Must furnish technically knowledgeable personnel and the tools required to disassemble the equipment, to the extent required by the Government.

e) Must provide facilities (e.g., office space, conference room, access to telephone/facsimile/internet), for the Government provisioning team and contractor personnel. The number of Government participants in the PC will be provided to the Contractor prior to the conference.

f) Must ensure the participation of contractor personnel with detailed knowledge of the subject matter they represent (e.g., provisioning, provisioning and technical documentation, hardware/software maintenance, engineering and system design).

At any time during the term of this contract or any extension thereof, the Government reserves the right to order additional Provisioning Conferences and updates to LMI data that may be required to support the PC.

Final Breakdown Structure (FBS) The Contractor must provide a top-down FBS to the LRU level on all hardware IAW CDRL-L003, after successful completion of FAT. The FBS is developed by sequencing all parts comprising the end item in a lateral and descending family tree/generation breakdown. This breakdown must consist of the end item, including all components, listing every assembly, subassembly, and parts, which can be disassembled, reassembled/replaced. All parts are listed in their relation to the end item, component, assembly, or installation system in which they are contained and to their own further sub-subassemblies and parts. This relationship is shown by means of an indenture code. The FBS shows the relationship of all items to one another. The Contractor must update the breakdown structure during the Government’s audits (FCA and combined PCA/PC). After the PCA, the Contractor must deliver the FBS CDRL-L003 to the Government for approval.

Tools and Test Equipment List (T&TEL) The Contractor must prepare and deliver to the Government a list of all the tools and test equipment CDRL-L004, both common and special, that are not an integral part of the V3 radios but are required to inspect, test, calibrate, service, and repair them. This list must identify only the tools and test equipment required to perform authorized site maintenance tasks (e.g., fault isolation and replacement to the LRU level). The Contractor must ensure that the T&TEL data on the list agrees with the T&TEL information contained in V3 radio technical documentation, e.g., the technical instruction book.

Repairs The Contractor must furnish Warranty and Non-Warranty repair services IAW the provisions of this section and its sub-sections, as well as Section H.3 of this contract, for all NEXCOM V3 Radio product repairable items and/or LRU(s). The Contractor must have the capability and expertise necessary to repair all repairable items and components. The contractor must have the capability and expertise necessary to repair all repairable items and components.

Under this concept, the FAA Logistics Center (FAALC) will manage and store exchange and repair (E&R) spares to support sites. The Contractor must furnish all qualified labor, supervision, materials, equipment, tools, appliances, and services to repair components of the equipment. The turn-around-time (TAT) for all repairs must be within 45 calendar days from the receipt of the item for repair unless otherwise specified by the CO.

Repairable items and components will be shipped at the Government’s expense directly from the FAALC to the Contractor’s repair facility. The FAALC Item Manager will furnish shipping instructions for repaired items. Unless otherwise directed by the Government, the Contractor must ship the repaired LRU to the FAALC in Oklahoma City, OK.

The Contractor must follow the repair requirements identified herein.

a) Contractor repair procedures must include the following:

1) Cleaning, visual inspection, bench tests, and fault isolation;

2) Disassembly as necessary to identify and accomplish required repairs or to establish the item as serviceable;

3) Reassembly, calibration, functionality testing, acceptance inspection, and preparation for shipment.

4) All repaired LRUs must successfully pass Production Unit Testing (PUT), as described in C.3.8.6, prior to being returned to the Government.

5) The Contractor must integrate repair process activity into the barcode scanning activities IAW C.3.7 and must include such data IAW the barcode scanning reporting requirements in C.3.7.4 for the life of this contract.

b) The Contractor must conduct all repairs IAW the Contractor’s established shop methods and procedures developed for the equipment.

c) When the Contractor determines that an item is beyond the Contractor’s ability to repair or the cost to replace the item is less than the repair cost, the Contractor must promptly notify the FAA CO and submit rationale for that determination. If the FAA CO in coordination with the COR, agrees that an item cannot be repaired, since the non-repairable item is Government Furnished Equipment (GFE), the FAA CO or COR will provide disposition instructions for the item to the Contractor and may request a replacement in lieu of repair.

d) At the time of repair the Contractor must complete any Government-approved modification to items required by this contract and not previously accomplished, inclusive of HWCIs or CSCIs, or Product Identifiers. Each modified item or LRU must meet form, fit, function or interface (F3I), of the item that it replaces and be two-way interchangeable, i.e., unmodified items must operate in place of modified items and modified items must operate in place of unmodified items.

e) The Contractor must be responsible for the initial lay-in of piece parts and for obtaining replenishment units and spare piece parts required for use in the repair of failed items. These parts must remain the property of the Contractor until incorporated into the repaired items at which time they become Government property. All parts removed as part of the repair become the property of the Contractor.

f) Upon receipt of a failed LRU from the Government, the Contractor must document the receipt and the initial determination of the LRU for warranty or non-warranty repair using the Monthly Repair Status Report (MRSR) (CDRL-L005) described in Section C.3.6.7.3.

g) The Contractor must maintain the Government-provided FAA Return Material Authorizations (RMAs), (formerly FAA 4650-12 form), that accompanies the failed LRU and report the information in the MRSR described in Section C.3.6.7.3.

h) The Contractor must prepare the Packing List/Shipping Report/Invoice to include the following information: Contract Number, Report Control Number, Part Number, Serial Number, Item Description, and National Stock Number for the FAALC receipt of a repaired LRU.

i) After inspection by the QRO, the Contractor must ship the repaired LRU to the FAALC with a completed copy of the FAA Return Material Authorizations (RMAs), (formerly FAA 4650-12 form), Fed Express shipping label, and instructions inside the container within this contractual TAT.

Cannot Duplicate/No Fault Found (CND/NFF) The Contractor must follow the repair requirements in Section C.3.6.7. If the Contractor’s repair procedures, as specified in Section C.3.6.7.a above, do not isolate any fault in the returned item/LRU, the return is a CND/NFF. If a CND/NFF returned LRU’s software is not at the current Government-approved version, then the LRU must be uploaded with the Government-approved software version. Any CND/NFF must be reported in the MRSR CDRL-L005.

Non-warranty Repair The Contractor must follow the repair requirements identified in Section C.3.6.7. Non-warranty repairs must apply to each unit that is determined not to be under warranty. This determination must be made IAW Section H.3.h of this contract.

a) The Contractor must electronically send a copy of the FAA Return Material Authorizations (RMAs), (formerly FAA 4650-12 form), and provide supporting information in sufficient detail to demonstrate that the cause of the failure was outside the warranty, to the FAA CO and COR, IAW Section H.3 of this contract.

b) For items determined to be non-warranty repairs by the Contracting Officer, the Contractor must cover the transportation costs and bear the risk of loss or damage from the Contractor's repair facility to the designated FAALC supply depot as part of the Non-warranty Repair CLIN.

c) The TAT for repair of the non-warranty repairs must be the same time as warranty repairs (refer to Section H.3) after receipt of a response from the FAA CO.

d) In the event a repair is required to return a defective LRU back into warranty status, the Contractor must bill the Non-warranty Repair CLIN for the repair costs.

Monthly Repair Status Reports (MRSRs) The Contractor must develop a MRSRs, as specified by CDRL-L005 and must contain the repair information for CND/NFF, warranty and non-warranty repair actions.

Technical Instruction Books (TIBs) The Contractor must develop and provide technical instruction books meeting the requirements of FAA-D-2494, Appendix I, as a minimum. The Contractor must deliver copies of the TIB CDRL-L008. There must be no restriction on reproduction or use of the TIB. The Contractor must specify an individual who will serve as a point of contact for all TIB issues.

The Contractor must grant the Government unlimited rights to the TIB data, which includes the right to use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly, in any manner and for any purpose, and to have or permit others to do so.

Training The Contractor must develop and deliver training materials for FAA personnel responsible for operating, maintaining, and performing second level engineering of the V3 Radio equipment. Training must be developed using Instructional System Design methodologies described in FAA Order 3000.22B. The Contractor must also ensure that web-based distance-learning training materials comply with the copyright and Section 508 of the Rehabilitation Act of 1973 as amended (29 U.S.C 794d) requirements of FAA Order 3000.22B.

Details for these requirements, as well as guidance IAW FAA Order 3000.57B related to the Air Traffic Organization Technical Operations Training and Personnel Certification procedures, will be provided during the Contractor hosted Training Guidance Conference (TGC).

Training Guidance Conference (TGC) As part of the PAC, described in Section C.3.4.a, the Contractor must host a TGC. The purpose of the TGC is to ensure the Contractor understands all training requirements.