N2CS_PWS_04_MAR_16.docx

PERFORMANCE WORK STATEMENT (PWS)

For E-4B NATIONAL and NUCLEAR COMMUNICATION SUPPORT (N2CS) System Program Office (SPO) PWS control number: E4B-PWS-FY16-09

REVISION NUMBER: 0

DATE: 4 March 2016

SOLICITATION NUMBER: FA8106-16-R-0014

CONTRACT NUMBER FA8106-17-D-TBD

PREPARING ORGANIZATION: AFLCMC/WLVSA TINKER AFB OK 73145

DISCLAIMER: The requirements and structure as expressed in this document are subject to change based on market research, feedback, and further refinement of requirements

SECTION I -- DESCRIPTION OF SERVICES

SCOPE OF PERFORMANCE WORK STATEMENT (PWS)

This Performance Work Statement (PWS) defines the services the Contractor is required to perform to sustain and modernize critical capabilities on the E-4B aircraft in support of National and Nuclear Communication Systems (N2CS). This effort is comprised of:

· N2CS Software/Hardware Sustainment Support/Upgrade

· Mission Support Facilities (MSF)

· Support Management Field Service Representatives (FSR)

· N2CS systems sustainment support and modernization

· N2CS systems and sustainment modification engineering This scope applies to all systems identified in Addendum A. of this PWS. The objective and requirements identified within this PWS are described in general terms.

In addition to requirements identified within this PWS, a Support Task (ST) will address specific task requirements, scheduling, and other related performance criteria, as applicable. Details of a ST are found in paragraph 1.6.3.

The Contractor shall provide uninterrupted support between the normal hours of 7:30 AM to 4:00 PM, Monday - Friday, excluding federal holidays as observed by both the Contractor and the Government (New Year’s Day, Martin Luther King Day, President’s Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving, and Christmas), and excluding base closure dates, unless otherwise instructed. Base closure dates shall be documented in accordance with company policy.

BACKGROUND

The E-4B serves as the National Airborne Operations Center (NAOC) for the National Command Authority (NCA) and provides a worldwide-deployable, enduring node of the National Military Command System (NMCS) to fulfill national security requirements throughout the full spectrum of conflict. It is a modern, highly survivable, command, control and communications center to direct U.S. forces to execute emergency war orders and coordinate civil authorities' activities, including national contingency plans. The E-4B has a variety of communication and cryptographic equipment to provide connectivity within the radio spectrum from Very Low Frequency (VLF) to Extremely High Frequency (EHF).

There are four (4) E-4B’s in the Air Force’s inventory located at the Main Operating Base (MOB) Offutt AFB, NE.

PURPOSE

This contract will provide sustainment and modernization for the E-4B N2CS systems identified in Addendum A.

CONCEPT OF SUPPORT

The contract will provide the following support for N2CS systems:

· Message Processing System (MPS) software sustainment

· MSF management and sustainment

· Engineering Support

· Mission System Technology Refresh

· Mission System FSR support for those systems listed in Addendum A

· Modification/Support

· Program Scheduling/Planning

· Mission Support Other contracts will be utilized as determined appropriate for future mission system support and/or modifications. The SPO will remain as the E-4B platform integrator. However, the Contractor shall develop inclusive communication processes with other E-4B Contractors for successful, timely, and cost-effective outcomes.

CONTRACT PERFORMANCE OBJECTIVES

The SPO will issue an Indefinite Delivery Indefinite Quantity (IDIQ) contract and will issue STs for direct or indirect services that support N2CS on the E-4B. Contractor responsibilities include fulfilling the requirements of the basic contract and specific task assignment as designated by individual STs using an integrated approach in efficiently meeting all requirements of each ST. The Government will identify applicable Contract Data Requirements List (CDRL) in each ST (Table 5-2).

APPLICABLE DOCUMENTS

Compliance and reference documents related to specifications, standards, handbooks, regulations, instructions and tables applicable to the work required in the performance of this contract are listed in Addendum B: Applicable Publications and Documents.

The Contractor shall comply with the current versions of applicable regulatory and compliance documents at the time individual STs are issued.

REQUIREMENTS SUMMARY

The Contractor shall perform tasks in accordance with issued STs providing engineering, technical, and support services as specified therein.

PROGRAM MANAGEMENT SUPPORT

Program Manager The Contractor Program Manager (PM) shall be responsible for the performance of the work and shall have full authority to act for the contractor on programmatic matters relating to the performance of this contract.

Program Manager Qualifications The PM shall have a minimum of seven (7) years program management experience, of which, five (5) years shall be in communication systems management. The PM shall also have the following minimum experience qualifications:

· Knowledge and experience of Department of Defense and United States Air Force acquisition processes, policies, and requirements

· Experience in the implementation of time-phased earned value measurement and reporting systems in accordance with Defense Federal Acquisition Regulation (DFARS)

· Experience in airborne communication systems performance and interdependencies, and integrated weapons systems

· Large team leadership of engineering and financial analyses utilizing systematic, disciplined, quantifiable approaches to implement, develop, and document contractual requirement compliance

· Knowledge and experience in system design for environmental qualification, electromagnetic effects, nuclear survivability/vulnerability, configuration-control, modernization, and sustainment efforts Program Management Plan Program Management Plan The Contractor shall establish a management system and develop, maintain, and deliver an annual Program Management Plan (PMP) (CDRL: A001), for execution of the E-4B N2CS contract. The Program Management Plan shall be an integrated document showing technical, cost and schedule data to a common base, the Contract Work Breakdown Structure (CWBS) or its planning equivalent (CDRL: A002). It shall also provide information on the Contractor’s organization, practices, and techniques to be used in managing the program and, if applicable, subcontractors.

The PMP shall include the following:

1. Key Contact List, including: Contact Name, Organization, address, email address, and telephone number

2. Subcontracting Plan, including:

a. Monitoring subcontractor progress and performance (e.g., schedule, effort, cost, technical performance)

b. Monitoring, and analyzing subcontractor processes critical to the success of the project

c. Evaluating subcontractor products, product components, and work products critical to quality

d. Conducting technical reviews including: technical activities and verifying the supplier’s interpretation and implementation of the requirements are consistent with the project’s interpretation; technical commitments are being met and that technical issues are communicated and resolved in a timely manner; technical information about the supplier’s products; providing appropriate technical information and support to the supplier

e. Conducting management reviews including: critical dependencies, project risks, schedule and budget

f. Using review results to improve the supplier’s performance

g. Monitoring risks involving the supplier and taking corrective action as necessary

3. The Systems Engineering Management Plan (SEMP) Programmed Depot Maintenance Planning (PDM) The Contractor shall participate in PDM planning activities as identified in individual STs.

Funds Management The Contractor shall develop and maintain processes to identify and document contract funding requirements and changes, budget estimates and funds in excess of contract needs. The Contractor shall accomplish the following:

· Develop and implement a funds management system, which tracks, forecasts and monitors funding

· Develop, maintain and deliver a CFSR (CDRL: A004)

· Respond to SPO requests for funding data for fiscal year requirements and/or shortfall projections to include short notice requests from the Government

· Provide spend plans that reflect program costs and spend rates upon request

· Respond to SPO requests to identify, review, analyze and forecast financial impacts to program Risk Management The Contractor shall develop and maintain an integrated Risk Management Plan (RMP) (CDRL: A005), and continually update it throughout the life of the program. Risk Management shall include all aspects of the program including cost, schedule, performance, technical, product data access, technology protection, production, sustainment and logistics planning. The Contractor shall establish processes for risk planning, risk assessment (identification and analysis), risk handling and risk monitoring consistent with Air Force Instruction (AFI) 63-101 and AFPAM 63-128. The Contractor shall ensure its integrated RMP includes subcontractors, partners, and others involved in the E-4B program support. The Contractor shall analyze and mitigate risk on the program and comply with all schedule, concurrent depot maintenance/modifications, Original Equipment Manufacturer (OEM) data access, engineering support, and systems test and evaluation requirements. All identified risk items shall have mitigation plans within the RMP which form the baseline for event tracking. The Contractor shall brief risk management status during PMRs and other meetings.

Contractor Manpower Reporting The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the USAF via a secure data collection site. The Contractor is required to completely fill in all required data fields at http://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the CMRA help desk.

*Reporting Period: Contractors are required to input data by 31 October of each year.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and Contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the Contractor name and contract number associated with the data.

Meetings, Conferences and Reviews The Contractor shall support and participate in conferences, reviews, and meetings as identified in individual STs. Any travel for conferences, reviews, and meetings will be IAW JTR and approved by PM and CO. Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence.

Post Award Meeting The Contractor shall participate in a Post Award meeting in the Oklahoma City, OK area within 30 calendar days after Contract start date. The Contractor shall review with and demonstrate to the Government their management procedures, provide progress assessments, review of technical and other specialty area status, and to establish schedule dates for near term critical meetings/actions.

Integrated Product Team (IPT) The Contractor shall participate in Integrated Product Teams (IPTs) that provide functional support for the weapon system or its mission as requested by the Government. The Government will establish and coordinate various IPTs which are responsible for both sustainment and recommended improvement/modifications for their assigned functional systems. The focus of these IPTs is to provide recommendations. The following are examples of such recommendations and projected organizations involved in each:

· Aircraft Availability Improvement Team (Engineering Support Service (ESS), Contract Logistics Support (CLS), N2CS, SPO)

· Identify, monitor, and recommend courses of actions for obsolescent parts (ESS/N2CS, SPO, and CLS)

· Improve Reliability and Maintainability Components/Systems (N2CS, ESS, SPO, and CLS)

· Integrate modifications into the depot maintenance package (ESS/CLS/SPO/N2CS)

· Plan for USAF mandated modifications whether for safety, temporary, and enhancement purposes

· Plan for evolution of system technologies and standards NOTE: A Memorandum of Agreement (MOA) and appropriate Proprietary Information Agreements (PIA) for each IPT where data exchange is essential to the process shall be established during initial contract phase in. Each MOA and/or PIA shall specify objectives, roles and responsibilities of the IPT. IPTs meet quarterly (see also 1.6.1.3.5), but may be called to meet more frequently for discussion/resolution of time sensitive issues. IPT meetings may be attended either in person or via telephone call-in.

System Security Working Group Support The Contractor shall support the E-4B System Security Working Groups (SSWG) meetings as identified by individual STs in support of individual systems. The SSWG shall provide coordination and oversight for E-4B System Security Issues and shall meet regularly to address on-going system security issues (e.g. up-coming re-accreditations, changing requirements, and trends in industry) and modification driven activity. This Contractor representative shall be responsible for ensuring that appropriate representation from the Contractor, subcontractors, or vendors is available for SSWG meetings.

Recurring Meetings The Contractor shall host and/or support recurring meetings as required.

Hosted Meetings The Contractor shall host required meetings listed below on a recurring basis. The Contractor shall prepare and deliver a Meeting Agenda (CDRL: A006), and Meeting Minutes (CDRL: A007). A short description of each meeting and frequency is listed below.

IPT

Quarterly

Program Management Review (PMR) The Contractor shall host an annual PMR and associated side meetings in the fourth (4th) quarter (either July or August) of the FY. The Contractor shall host the annual PMR in Oklahoma City, OK unless directed otherwise by CO. The PMR duration shall be no more than 2 days with 150 participants. The Contractor shall brief overall program status, financial status, risk management, configuration management status, systems engineering status, and other assigned. The PMR agenda topics, presentations, and location will be approved by the Government 10 calendar days prior to the meeting (CDRLs: A006, A007, A008).

Monthly Customer Telecon The Contractor shall host a monthly teleconference unless otherwise directed by the CO. The monthly customer telecon is not required in the month of the annual PMR. The teleconference shall not exceed four (4) hours in duration. The Contractor shall cover program status, financial status, and other assigned topics. The Contractor shall provide the call in number. The Contractor shall record minutes from the teleconference (CDRL: A007).

Non-Recurring Meetings The Contractor shall support required meetings as required by individual STs.

Systems Engineering Meetings The Contractor shall support meetings required by the Systems Engineering Plan.

The Contractor shall provide agendas and minutes (CDRL: A006, A007).

MPS Software Working Group (SWG) The Contractor shall host the annual SWG. The Contractor shall deliver an agenda 10 calendar days prior to each meeting (CDRL: A006). The Contractor shall deliver minutes (CDRL: A007). The Contractor shall present all SWG write-ups in a Power Point Presentation (CDRL: A008). The Contractor with Government assistance shall prioritize the write-ups.

Phase-In Phase-In Plan The Contractor shall plan and execute an orderly transition from the incumbent Contractor. The Contractor shall provide a maximum of a 60 day phase-in plan (CDRL: A009). The Contractor shall hire and sustain a workforce to assure satisfactory performance beginning on the contract start date. The Contractor shall ensure that all training requirements for employee(s) are completed before full performance begins. The Contractor shall execute a transparent phase-in with no disruption to supply and maintenance support. The Contractor shall be fully responsible for work requirements and work in progress following the completion of the 60 calendar day phase-in period. The Contractor shall submit a detailed Phase-In plan for Government approval no later than 7 calendar days after contract award. The Contractor’s phase-in planning shall address, but is not limited to the following:

· A comprehensive list of milestones, tasks to be accomplished, entrance and exit criteria for each milestone, GFP which may include, but is not limited to: hardware, movement of MSF equipment, software, tools, data, documentation, and processes, and the responsible person(s) for those tasks

· Identify, score and rank risks for transitioning phase-in tasks and mitigation strategies for those risks

· Detailed plans to hire and sustain a workforce to assure satisfactory performance beginning full performance date (by the end of the 60 calendar day phase in period)

· Detailed plans to ensure all training requirements for employee(s) are completed before full performance begins

· Detailed schedule for transition of tasks and GFP (to include movement of MSF equipment if required) to complete transfer of responsibility Joint Phase-In Inventory The Contractor shall complete an inventory of N2CS GFP with the incumbent Contractor and Defense Contract Management Agency (DCMA)/COR within 20 calendar days of the beginning of Option One performance period. During the inventory, the Contractor shall determine the working order and condition of all GFP and obtain DCMA/COR concurrence. The Contractor shall document the condition of all GFP listed in the appendices of the contract and notify the CO in writing within five (5) days of completion of the inventory (CDRL: A010).

Phase-In Reporting Meeting During the phase-in, the Contractor shall conduct a weekly status review via teleconference (day of week to be directed by PM) with the SPO (CDRL: A011). As a minimum the status review shall address the following:

· Successful completion of, or failure to complete phase-in plan milestones of the previous week

· Where milestones have not been met measures taken to remedy the situation to ensure that the transition phase will not be delayed and start of contract full performance will not be affected

· Progress in obtaining personnel and management including current projections to the end of phase in period

· Status of efforts to ensure that all personnel have received requisite training by the end of the phase in period

· Status of efforts obtaining parts and material in support of this program and identification of problems Phase-Out Phase-Out Requirements The Contractor shall ensure the following phase-out requirements are accomplished within the 60 calendar days prior to contract end date. The Contractor shall cooperate with the Government and follow-on contractor to permit an orderly changeover of workload.

Access and Observation The Contractor shall allow all follow-on contractor and Government personnel access on a non-interference basis to observe equipment operation workflow to include: work in progress, reporting, priorities, forms, documents, scheduling, storage, safety, security, and quality control procedures.

Joint Ending Inventory The Contractor shall complete a joint inventory no earlier than 20 calendar days prior to the end of the last performance period. During the inventory, the Contractor shall determine the working order and condition of all GFP and obtain COR concurrence. The Contractor shall resolve discrepancies between the inventory and official Government records with the COR. The Contractor shall document the condition of all GFP listed in the appendices of the contract and notify the CO in writing within five (5) days of completion of the inventory (CDRL: A010).

Visits and Change-Over If there is a change in Contractor, the N2CS Contractor shall provide familiarization to the follow-on Contractor. During this familiarization period of up to 60 calendar days, the incumbent shall be fully responsible for continued operations IAW this PWS. The Government reserves the right to conduct site visits to all Contractor facilities in conjunction with the solicitation of offers for the follow-on to this contract. The Contractor shall cooperate to the extent required to permit an orderly change over to the follow-on Contractor and minimize disruption to mission activities.

ORIGINAL EQUIPMENT MANUFACTURER (OEM) DATA AND SUPPORT

During Phase-in period, the Contractor shall establish and maintain agreements with the appropriate OEMs that shall allow the Contractor to obtain and use the approved data and technical support necessary to maintain the military type certification of E-4B mission and communication systems. The Contractor shall ensure all agreements (PIAs, Associate Contractor Agreements (ACA) and/or Non-Disclosure Agreements (NDA) are in effect within 60 calendar days after contract award. The Contractor shall ensure maintenance flow, aircraft utilization, and mission reliability requirements are not adversely impacted as a result of obtaining data or support from OEMs (or lack thereof). The Contractor shall ensure that NDAs for employee are final prior to full performance.

Access and Use of Original Equipment Manufacturer (OEM) Data The Contractor shall obtain and maintain OEM Proprietary Data license agreement(s) for the access and use of OEM proprietary data necessary to execute this PWS and all STs herein. The use and access of data shall include sharing with Air Force maintenance technicians and flight/mission crews for operation and sustainment of the covered N2CS systems. The Contractor shall ensure that any subcontractors have required access and license for OEM data to support their activities under this PWS and all STs herein. Proof of such agreements shall be provided to the Government upon request by the CO.

Engineering Data Responsibilities All engineering data developed to support the requirements of this PWS shall be maintained by the Contractor and shall be submitted to the Government with “Unlimited Rights” at the end of the Period of Performance. All data shall comply with Federal Aviation Administration (FAA) accepted Air Transport Association (ATA) standards for identification of detail assembly, installation, specification, schematics, wiring diagrams, tooling drawings, test equipment drawings, company standards, referenced documents, associated lists, and other engineering data required to define the design and to fabricate, assemble, install, and support modification and general maintenance. The Contractor shall provide all records, files, and documents provided by the Government or generated by the Contractor in support of this contract to the Government (CDRL: A013).

NOTE: See Table 5-2 for deliverables that may be required as called out in the specific ST PWS.

Subscription Services The Contractor shall provide documentation and verification of all established subscription services required for the performance of this effort including, but not limited to commercial maintenance manuals, drawings, Service Bulletins, Service Instructions and Service Letters, prior to full scale performance (CDRL: A014).

SUPPORT TASKS

The Contractor shall comply with ST for liaison engineering, analysis, and general inquiries to support E-4B sustainment. Requests for ST services will be specifically detailed. The Contractor shall utilize operations, logistics, design, quality assurance system, planning, and program management to resolve properly channeled requests for support. This ST support shall consist of providing assistance to resolve issues associated with the following:

· Engineering Data –Vendors

· Logistics

· Certifications

· Test Support

· Maintenance

· Planning

· Aircraft Modifications

· Studies The Contractor shall provide the SPO online electronic access to STs and deliverables. The data shall be downloadable in format specified in the ST.

The Contractor shall establish and utilize a process to work and close STs agreed upon by the Government.

NOTE: See Table 5-2 for deliverables that may be required as called out in the specific ST PWS.

FIELD SERVICE REPRESENTATIVES

The Contractor shall provide FSRs on-site at the Main Operating Base (MOB) to provide technical guidance, training, hands-on troubleshooting, and repair assistance for all Addendum A. Systems in support of the E-4B maintenance functions. The Contractor FSRs shall provide technical guidance in the resolution of field problems related to installed equipment or systems.

FSR Qualifications and Expertise The Contractor shall ensure each FSR has a minimum of 5 years of relevant E-4B technical/operating/maintenance experience.

FSR Duties and Requirements The main objective of the FSR support shall be to provide enhanced technical support skills and abilities to Government personnel responsible for the operation and maintenance of E-4B equipment and systems. The specific requirements and duties include, but are not limited to, the following:

· Provide hands-on On the Job Training (OJT) and informal classroom instruction in operation, line maintenance, installation, removal, and system troubleshooting

· Provide training on the E-4B Technical Order (T.O.) or commercial manuals

· Provide hands-on troubleshooting and technical assistance to support organic aircraft field maintenance personnel as required

· Provide instruction on the use of the special tools, handling equipment, and unique Support Equipment/Special Test Equipment (SE/STE)

· Emphasize safety aspects to be observed on the E-4B aircraft

· Provide guidance and recommendations to support Time Compliance Technical Orders (TCTO) and Service Bulletins as required

· Participate in meetings with the Government and other Contractors as required

· Analyze maintenance difficulties and recommend changes to design, operation, maintenance, inspection, and training to improve the level of maintenance

· Assist the SPO in completing accident investigations and failure reports

· Provide technical support to include: analysis, investigation, content, and submission of material/quality deficiency reports (IAW USAF Deficiency Reporting, Investigation, and Resolution (T.O. 00-35D-54) and Technical Manual (TM) Change Recommendation and Reply (AFTO 22) IAW Technical Manual, AF Technical Order System (ATOS) (T.O. 00-5-1)

· Participate in technical reviews as requested by the PM

· FSRs shall be certified to drive on the flight line

· FSRs must be eligible for and be able to maintain a Top Secret/SCI security clearance Mission Support Contractor FSR personnel shall participate in E-4B flights. Flight participation shall support specific flight tests for new and/or modified systems, or troubleshooting specific problems that cannot be fully checked during ground operations. All mission support shall be coordinated from NAOC operations office to the PM and approved by CO. Contractor mission support personnel shall obtain a valid passport and shall possess a Top Secret security clearance with special access. Passports and security clearances shall be updated as required.

Mission Support other than Main Operating Base The Contractor FSR shall perform services at locations other than the Main Operating Base (MOB) at Offutt AFB, NE. When directed by the CO and coordinated with the Contractor PM, the Contractor shall work other than a normal or adjusted workweek. Travel expenses for duty at other than the MOB location shall be authorized by the CO. For E-4B international deployments, HQ MAJCOM Advanced Liaison (ADVON) representative or designee shall arrange for lodging and rental car transportation for support at overseas locations.

24 Hour Telephone Support The Contractor FSR shall maintain a 24 hour single point of contact via telephone seven days a week for hardware/software support after hours. All calls must be answered immediately or the call returned within 30 minutes. The Contractor shall maintain an event log, which shall be provided to the COR monthly (CDRL: A015).

Mission System Wake-up Support The Contractor shall support mission systems wake-up for the systems listed in Addendum A. IAW published Air Force Technical Orders. Support shall consist of FSR efforts required to facilitate the post-scheduled maintenance operational checks performed at the MOB or other locations designated by the SPO to bring the aircraft to an operational status.

FSR Training Duties The Contractor FSR shall provide on-the-job and informal classroom training (defined as follow-on training as opposed to initial training) instruction on N2CS SYSTEMS. Training shall normally be conducted during the FSRs normal work schedule, but adjusted times may be coordinated between the 55th Aircraft Maintenance Squadron/First Aircraft Maintenance Unit/ First Airborne Command and Control Squadron (55AMXS/1 AMU/1 ACCS), the PM, and the Contractor’s FSR (CDRL: A016).

FSR Training Requirements and Qualifications The Contractor FSR shall attend the same formal training afforded to the Air Force technicians as a result of system modifications during the performance of this contract. If multiple classes are provided as a result of a specific modification, the FSRs shall attend the first class in order to aid in follow-on training of Air Force technicians and system repair/troubleshooting.

Emergency Procedures Contractor employees shall follow the direction of Government employees in regards to emergency procedures; i.e. fire, tornado, active shooter, bomb threats. It is the responsibility of the contractor to provide guidance and establish procedures for responding to an emergency for their employees. It is the contractors' responsibility to account for their employees following an emergency evacuation. Contractor Personnel shall participate with government personnel in all fire and tornado drills at no additional cost to the Government.

AIRCRAFT / WEAPON SYSTEM MODIFICATIONS

The Contractor shall be responsible as identified in individual STs to design, develop and install modifications to the systems in Addendum A.

Aircraft Modifications Each ST shall define the extent of the effort and provide access to the requisite data needed for this support.

NOTE: See Table 5-2 for deliverables that may be required as called out in the specific modification ST PWS.

Scheduling The Contractor shall perform aircraft modification planning to aid the SPO in minimizing aircraft down time and cost as identified in individual STs. An Integrated Master Schedule (IMS) shall be developed for each modification program and shall include the time phased work breakdown structure down to two levels of detail below the critical path. The Contractor shall work with the SPO to incorporate other modifications into the installation plan as appropriate. The Contractor shall recommend action where synergies in the installation provide greater efficiencies. If a modification is to be accomplished during Programmed Depot Maintenance (PDM), as identified in individual STs, the contractor shall provide a draft IMS to the SPO no later than six months prior to the induction of a particular tail number for PDM. The Contractor shall provide the final IMS in Microsoft Project, no later than 30 calendar days prior to the start of the effort on a particular tail number.

NOTE: See Table 5-2 for deliverables that may be required as called out in the specific modification ST PWS.

Cost Estimates (In Support of System Modifications) The Contractor shall, as requested, develop and provide cost estimates to support the pricing of other contracting efforts. The Contractor shall also provide estimates in support of decision making and the planning, prioritization, identification and capture of funding for future efforts. The Contractor can receive requests for estimates from the CO (via Contracts Letter or Contract Modification). The Contractor shall prepare and provide the Program Engineer and/or CO, a work statement that describes the activity to be performed, the period of performance, labor, travel and material cost estimate. The Contractor shall submit all estimates to the CO (CDRL: A012).

Systems Engineering Approach The Contractor Systems Engineering Management Plan (SEMP) (CDRL: A003), shall include a disciplined engineering approach that ensures full spectrum integration and systems engineering principles are applied when performing all non-recurring and recurring tasks in this PWS. The Contractor shall develop, maintain and update the Contractor’s SEMP and provide it to the PM. The Contractor shall provide for technical planning, integrate Government and Contractor practices and processes and conduct continuous process improvement. The SEMP shall include a description of the key technical processes. The Contractor shall establish, in the SEMP, the metrics and measurements (the baseline) that will be used to monitor Contractor performance, including guidelines/standards for applicability. At a minimum, the SEMP shall address the metrics defined in the WLV Systems Engineering Plan (SEP). As a minimum the Contractors SEMP shall encompass:

· Affordability and cost effectiveness

· Requirements analysis and management

· Functional analysis and allocation

· Integrated planning and scheduling

· Risk management plan

· Technical Performance Measures (TPM)

· Interface control

· Baseline management

· Configuration Management

· Technology insertion

· System validation and verification Systems Engineering Modification Development Support The Contractor shall perform the following activities in support of E-4B modification development or in response to SPO requests for studies or investigations as identified in individual STs:

Requirements decomposition, traceability and management Coordinate Formal Program Technical Reviews Coordinate and lead informal technical reviews and SSWG which include: compatibility of mission equipment, safety, installation/integration, software, testing, certification, supportability, nuclear survivability/vulnerability, and reliability and maintainability Coordinate modification design development per the requirements of the program SEMP Identify and resolve technical problems that arise in the design and integration of current and new systems Perform detailed technical reviews of design and installation engineering Participate in SPO requested technical investigations Update system baselines

NOTE: See Table 5-2 for deliverables that may be required as called out in the specific modification ST PWS.

Aircraft Prototype Modifications The Contractor shall be requested to perform site surveys, engineering design, technical data development, TCTO preparation, fabrication, kit procurement, installation, test, certification, and delivery necessary to complete prototype modifications. Prototype modifications shall be defined as the first modification performed for a specified weapon system configuration. The Contractor shall plan for, and provision all equipment and materiel required to install, test, and sustain N2CS systems modification as identified in individual ST.

NOTE: See Table 5-2 for deliverables that may be required as called out in the specific modification ST PWS.

Engineering Studies The Contractor shall be required to conduct engineering studies to determine system definition and modification requirements for sustainment and enhancements of Addendum A. mission systems. The Contractor shall be required to coordinate with the Government to ensure possible solutions meet requirements and capabilities, or resolve performance issues.

Test Support The Contractor shall be required to provide test support to ensure successful integration, functionality, and operation of existing new and modified aircraft hardware and software. The Contractor shall be required to support by attending design reviews, technical demonstrations, Test Readiness Reviews (TRR), and SSWG.

NOTE: See Table 5-2 for deliverables that may be required as called out in the specific modification ST PWS.

Technical Data Technical Order Guidance Conference The Contractor shall conduct a Technical Order Guidance Conference (TOGC) within 60 business days of each relevant task order award. T.O. 00-5-3 provides guidance on what the conference will accomplish. The Contractor shall deliver a conference agenda in electronic format to the Government at least 10 business days prior to each meeting (CDRL: A007).

The Contractor shall deliver draft meeting minutes in electronic format to the Government within 10 business days after the meetings. The Contractor shall deliver the final package 5 business days after Government review. The final minute’s package shall include a copy of the agenda and presentation (CDRL: A006, A008).

Time Compliance Technical Order The Contractor shall develop a Time Compliance Technical Order (TCTO) formatted in accordance with T.O. 00-5-15 and MIL-PRF-38804D. TCTO priority, type, and level will be determined at CCB or Software Configuration Control Sub-Board approval. The Contractor shall provide one (1) electronic copy of the draft TCTO prior to start of installation via encrypted means. The Contractor shall provide the T.O. change page source data for incorporation into the final Technical Order rewrite. The Contractor shall provide one (1) electronic copy of the preliminary TCTO source data to the Government prior to the start of each In-Process Review, and Pre Publication Review, unless otherwise advised by the PCO. The Contractor shall provide the final TCTO source data to the Government NLT 60 calendar days after verification.

NOTE: See Table 5-2 for deliverables that may be required as called out in the specific modification ST PWS.

Contractor Source Data The Contractor shall provide Technical Order (T.O.) change page source data for the affected flight, wiring diagram, maintenance, Illustrated Parts Catalog (IPC), and support equipment manuals to the Government 10 calendar days prior to the start of each In-Process Review and Pre-Publication Review. Verification source data shall be provided at verification unless otherwise advised by the Government in the following quantities:

1. Four (4) paper copies and one (1) electronic copy of the flight manual

1. Four (4) paper copies and one (1) electronic copy of the wiring diagram, maintenance manuals, IPC manuals, and draft source data The source data shall be compatible with the existing style and format with the following exceptions:

1. Technical orders 1E-4B-2-110-1 and 1E-4B-2-110-91 may be provided in a list format rather than an affected page Technical Order Page Supplement (TOPS) format

2. Flight Manual source data will be provided in an operational supplement format

The baseline for development of T.O. changes shall be the published copies in existence when the T.O. Contractor Quality Assurance (CQA) is conducted. The Contractor shall provide the final Contractor source data NLT 60 calendar days after Verification.

NOTE: See Table 5-2 for deliverables that may be required as called out in the specific modification ST PWS.

In-Process Reviews The Contractor shall conduct a 35% and 75% In-Process Review (IPR) of the TCTO and the technical order source data. T.O. 00-5-3 provides guidance of what is expected at reviews. The Contractor shall provide meeting agenda and minutes for the In-Process Review (CDRL: A006, A007).

Contractor Quality Assurance & Verification Support The Contractor shall conduct Contractor Quality Assurance (CQA) prior to Technical Order Verification for the TCTO and source data (CDRL: A017). Upon completion of CQA activities and incorporation of markups, the Contractor shall notify the Government. The Government will schedule verification of the TCTO and source data. The Contractor shall provide on-site support during the verification of the TCTO and source data.

Marked-Up Source Data The Contractor shall deliver verified source data (fly-away data) for the prototype install 10 calendar days prior to aircraft Return to Service (RTS). The Contractor shall provide the following quantities:

1. Four (4) paper copies and one (1) electronic copy of the flight manual

2. Four (4) paper copies of maintenance manual draft source data and one (1) electronic copy

3. Four (4) CD copies of all data Pre-Publication Review The Contractor shall conduct a Pre-Publication Review for the TCTO and source data within 30 calendar days of completion of Verification to review incorporation of all the marked-up data from the verification master marked-up source data. The Contractor shall incorporate approved mark-ups from CQA and Verification into a final TCTO source data package prior to the Pre-Publication Review. The Contractor shall provide engineering and technical writer support during the Pre-Publication Review of the source data. The Contractor shall provide meeting agenda and minutes for the Pre-Publication Review (CDRL: A006, A007).

Final Source Data Delivery The Contractor shall incorporate approved changes from Pre-Publication Review into a final TCTO source data package. The Contractor shall deliver the following quantities:

1. One (1) electronic copy of all final source data in an unlocked PDF format

2. One (1) electronic copy of 1E-4B-2-110-1 and 1E-4B-2-110-91 final source data in an unlocked excel format

3. Four (4) CD copies of all the source data in a locked PDF format The Contactor shall provide final source data delivery NLT 60 calendar days after verification.

TECHNICAL DATA ASSISTANCE

The Contractor shall provide technical data/information reconciliation when the Government requires assistance incorporating data into existing technical orders, as identified in individual STs.

Aircraft Depot Maintenance- TCTO Contractor Quality Audit The Contractor shall provide support for TCTO validation and/or verification during third party installations at the PDM facility, as identified in individual STs.

N2CS SOFTWARE SUSTAINMENT

The Contractor shall provide software sustainment support for the systems identified in Addendum A.

Software Support The Contractor shall plan, support, and coordinate N2CS Software Working Group (SWG) meetings quarterly at the Contractor’s facility. The SWGs shall address planning, validation, review, prioritization, and resolution of software updates, deficiencies, enhancements, Time Compliance Network Orders (TCNOs), and integration of software applications for the MPS. The Contractor shall develop agendas and presentations, and provide minutes for these meetings (CDRL: A007). The Contractor, along with the SPO, shall identify a candidate set of software items to be implemented in a particular quarter based on the time required to implement the software items and the priorities of the items. This candidate list will be validated by the Government.

Software Configuration Management The Contractor shall maintain a Configuration Management (CM) system to manage software, documentation, configuration, test support, and other items ancillary to performing software sustainment, development, and test in support of the operational E4B systems identified in Addendum A, and development and integration environments (e.g. test equipment and software). The Contractor shall maintain a subscription for all software and monitor service literature, software revisions, software patches, TCNOs, and any other recommended changes to the configuration of the items listed in Addendum A.

The Contractor shall track E4B Mission Systems changes which are defined as deficiencies and enhancements. The changes shall consist of (at a minimum) a description of the issue, an estimate of the calendar time required to completely implement the change, a priority which shall be initially set by the Contractor, and validated by the SPO as part of the SWG. The calendar time estimate for each change shall consist of the times required to perform engineering analysis of the item, development time, time to develop and execute informal and formal testing of the change, and all other actions required to implement the software fix. These times shall be used to select the package of software changes to be implemented for each quarterly update cycle. Software changes shall be identified by the Contractor as part of software support by the users, or the SPO (CDRL: A018). All software changes will be validated by the Government as part of the SWG process.

Software Engineering Sustainment Support The Contractor shall maintain processes consistent with CMMI-DEV Level 3 (or equivalent) and DO-178C to address identified software deficiencies for the E-4B N2CS. The Contractor shall prepare and maintain a Software Development Plan (SDP) (CDRL: A019), to document the responsibilities, processes, and tools to perform software management on the systems identified in Addendum A.

Software Sustainment The Contractor shall sustain the MPS software by updating and deploying software releases quarterly, or as required in coordination with the Program Office. The Contractor shall maintain MSF/GSF software development hardware and software in operational configuration. The Contractor shall provide upgrades to the software development environment as necessary to improve efficiency or retain capability. The Contractor shall assess potential changes for schedule impact and a projected prioritization. Schedule impact shall be defined in terms of the total calendar time required to implement the change in the system. The Contractor shall support four (4) routine, and up to two (2) emergency software sustainment builds per FY.

1. Track Potential Software/Hardware Changes. Identify, collect, assess for schedule impact, and track proposed hardware or software changes. Potential software or hardware changes will be identified through user input, requirements documents (e.g. PWSs), changes to operational documents or requirements (e.g. Emergency Action Procedures (EAP)), TCNO, and similar sources (e.g. Interface Control Documents (ICD). This activity will be intermittent throughout the contract Period of Performance.

2. Recommend Software/Hardware Change Priority. Recommend a prioritization for potential software/hardware changes to be implemented.

3. Develop Software Changes. Develop software changes to fix anomalies and enhance system capabilities as directed by the SPO. Develop software for use in the MSF/GSF to enhance productivity and improve tracking of MSF/GSF efforts. Perform informal software testing and resolve issues identified in testing.

4. Test Software Changes. Perform formal testing, witnessed at the Governments discretion, using a…