HSCG38-11-R-H00002 EFDS RFP W Clauses

HSCG38-11-R-H00002

A1U EFDS

NOTICE FOR FILING AGENCY PROTESTS

It is the policy of the Coast Guard to issue solicitations and make contract awards in a fair and timely manner. The Ombudsman Program for Agency Protests (OPAP) was established to investigate agency protest issues and resolve them without expensive and time-consuming litigation. OPAP is an independent reviewing authority that is empowered to grant a prevailing protester essentially the same relief as the General Accounting Office (GAO).

Interested parties are encouraged to seek resolution of their concerns within the Coast Guard as an Alternative Dispute Resolution (ADR) forum, rather than filing a protest with the GAO or some external forum. Interested parties may seek resolution of their concerns informally or opt to file a formal agency protest with the contracting officer or Ombudsman.

Informal forum with the Ombudsman. Interested parties who believe that a specific USCG procurement is unfair or otherwise defective should first direct their concerns to the cognizant contracting officer. If the contracting officer is unable to satisfy the concerns, the interested party is encouraged to contact the USCG Ombudsman for Agency Protests. Under this informal process, the agency is not required to suspend contract award performance. Use of an informal forum does not suspend any time requirement for filing a protest with the agency or other forum.

In order to ensure a timely response, interested parties should provide the following information to the Ombudsman: solicitation/contract number, contracting office, contracting officer, and solicitation closing date (if applicable).

Formal Agency Protest with the Ombudsman. Prior to submitting a formal agency protest, protesters must first use their best efforts to resolve their concerns with the contracting officer through open and frank discussions. If the protester’s concerns are unresolved, an independent review is available by the Ombudsman. The protester may file a formal agency protest to either the contracting officer or as an alternative to that, the Ombudsman under the OPAP program.

Contract award or performance will be suspended during the protest period unless contract award or performance is justified, in writing, for urgent and compelling reasons or is determined in writing to be in the best interest of the Government. The agency’s goal is to resolve protests in less than 35 calendar days from the date of filing. Protests shall include the information set forth at FAR 33.103. If the protester fails to submit the required information, resolution of the protest may be delayed or the protest may be dismissed. This will not preclude re-filing of the protest to meet the requirement. To be timely, protests must be filed within the period specified in FAR 33.103(e). Formal protests filed under the OPAP program should be submitted to:

Department of Homeland Security United States Coast Guard (CG-9131) Ombudsman Program for Agency Protests 1900 Half Street, SW, Room 11-0602 Washington, D.C. 20593-0001

FAX: 202.475.3904

The Ombudsman Hotline telephone number is 202.372.3695

SF1449 to be inserted here

CONTINUATION OF SF 1449 – BLOCKS 17B - 25

Block 17B: REMITTANCE ADDRESS: Payment will be made to the Financial Institution listed in Central Contractor Registration (CCR). To receive award contractor must be registered in Central Contractor Registration (CCR) http://www.ccr.com.

Blocks 19 through 24: The following pages contain the Schedule of Supplies/Services and Statement of Work (SOW).

This Request for Proposal is issued, in accordance with FAR Part 12, Commercial Items in conjunction with FAR Part 15, Contract Negotiations. For questions concerning this solicitation contact Mr. Danny R. Sawyer, Contract Specialist at 252-335-6291 or via email at Danny.R.Sawyer@uscg.mil.

Questions regarding this solicitation must be in writing and sent via email to Danny.R.Sawyer@uscg.mil. The questions and answers will be posted on FedBizOpps via an Amendment to the solicitation. Questions will not be accepted after APRIL 21, 2011, 4:00pm EST.

COTS Displays have a volumetric pass/fail evaluation criteria. Any proposal which offers a COTS Display that does not meet the volumetric requirements (placement and location) identified in the SSS will be excluded from further consideration for award and the Contracting Officer will notify any affected offeror in writing not later than 30 days after the proposal due date.

Anticipated Award Date: The contract is expected to be awarded on or about July 31, 2011.

ATTACHMENTS:

(1) System/Subsystem Specifications (SSS) dated 03/23/2011

(2) Contract Data Requirements List (CDRL)

(3) Compliance Matrix http://www.ccr.com/

The US Coast Guard (USCG) seeks to award one firm fixed price requirements contract for the procurement of a commercially off the shelf (COTS), suitable and proven

Electronic Flight Display System (EFDS) for the USCG HC-130H Avionics I Upgrade

(A1U) Project. This contract will consist of a two-year base and three (3) one-year option periods, not to exceed a total of five years. The base period will consist of a firm fixed price Non-Recurring Engineering (NRE) effort and the purchase of approximately 3 ship sets to be installed in prototype aircraft and as a part of the System Integration Lab (SIL).

The option periods will be for EFDS ship sets for approximately 15 fleet aircraft plus approximately 2 ship sets for USCG initial sparing. The exact numbers of ship sets ordered during each option period will be estimates contingent on funding. Select

Engineering and Technical Support Services during the base and each option period may be ordered by labor hour. This requirement will be satisfied by using commercial acquisition procedures specified in FAR Part 12 and negotiated procedures specified in

FAR Part 15. This solicitation incorporates provisions and clauses in effect through

Federal Acquisition Circular 2005-51. Delivery of COTS ship sets that meet the physical dimensions and will perform to the EFDS System/Subsystem Specifications (SSS) for the modification efforts to the prototype aircraft NLT-120 days after contract award is required. Within 30 days after contract award, the awardee shall participate and support a Subsystem Technical Review to ensure the proposed EFDS can proceed into detailed design, and can meet the stated performance requirements within cost, schedule, risk and other system constraints. A Critical Design Review (CDR) will be convened 90 days after contract award, followed shortly thereafter by an

Installation Readiness Review (IRR) and then the initiation of the A1U modification efforts to the prototype aircraft. Inspection and acceptance will be by the Contracting

Officer’s Technical Representative (COTR) for all items except production ship sets that will be inspected and accepted by Certificate of Conformance (COC).

Schedule of Supplies/Services

BASE PERIOD

From Contract Award thru the Following Two-Year Period

(Contract Years One and Two)

CLIN Description Est Qty

Unit of

Issue

Unit Price Extended Price

All efforts leading to successful completion of the Subsystem Technical Review as summarized in SOW paragraphs 3.4.1.4, 3.4.1.4.1 and 3.4.1.4.2

JB

completion of the Critical Design Review as summarized in SOW paragraphs 3.4.1.5, 3.4.1.5.1, 3.4.1.5.2, 3.4.1.5.3 and 3.4.1.5.4 completion of the Installation Readiness Review (IRR) as summarized in SOW paragraphs 3.4.1.6, 3.4.1.6.1, 3.4.1.6.2 and 3.4.1.6.3 completion of the Flight Readiness Review as summarized in SOW paragraphs 3.4.1.7, 3.4.1.7.1, 3.4.1.7.2 and 3.4.1.7.3 completion of the Aircraft Integration Testing as summarized in SOW paragraph 3.4.2.19 completion of the Production Decision (Production Approval) as summarized in SOW paragraph 3.7

Engineering and Technical Support to support EFDS Integration & Installation efforts as summarized in SOW paragraph 3.9

HR

Schedule of Supplies/Services BASE PERIOD (Continued)

From Contract Award thru the Following Two-Year Period (Contract Years One and Two)

Unit of

Travel Expenses for Government Directed Travel IAW SOW par 5

– Reimbursable IAW FAR 31

Not Separately Priced

0009A 0009B 0009C 0009D

EFDS Ship Sets (for Prototype and System Integration Lab

SIL)

Quantity Price Discount

4-6 7-9

10-12 13-17

SE

Base Period Estimated Total $________________________

The base period estimated total is a summation of the extended price for CLIN’S 0001, 0002, 0003, 0004, 0005, 0006, 0007 and 0009.

Inspection and acceptance for CLIN’S 0001, 0002, 0003, 0004, 0005, 0006, 0007 and 0009 shall be by the Contracting Officer’s Technical Representative (COTR) (to be assigned at contract award). Travel will be directed by the Contracting Officer or the

COTR.

CLIN 0009 - If testing and evaluation is ahead of schedule and funds are available to purchase ship sets for the production aircraft during the base period CLIN’S 0009A, 0009B, 0009C and 0009D are included should quantity discounts be offered. The total estimated quantities during the 5 years of this contract is 20 ship sets: 2 ship sets for the prototype aircraft, 15 ship sets for production aircraft and 1 ship set for System Integration Lab (SIL) and 2 ship sets for initial sparing. This is a Firm Fixed Price requirements contract and quantities are estimates only; there is no obligation for the government to purchase a minimum or maximum quantity. Quotes for EFDS ship set CLIN’s 0009 and 0009A-0009D shall be FOB Destination. FOB destination point:

Aviation Logistics Center, Receiving Building 63, Elizabeth City, NC 27909.

Delivery ship set for SIL is NLT 60 days after contract award. Delivery of ship sets for the modification efforts to the prototype aircraft is NLT 120 days after contract award.

Option Period One One-Year following the Base Period

(Contract Year Three) CLIN Description Est

Qty Unit of

1001A 1001B 1001C

EFDS Ship Sets (for Production Acft and initial Sparing)

Quantity Price Discount

Engineering Sustainment and Technical Support (Composite Hourly Labor Rate) as

3.9

Directed Travel IAW SOW para 5-Reimbursable IAW FAR 31

Not Separately

Option Period One Estimated Total $________________________

The Option Period One estimated total is a summation of the extended price for CLIN’S 1001 and 1002.

CLIN 1001- If funds are available to purchase more than 6 estimated ship sets during this period CLIN’S 1001A, 1001B and 1001C are included should quantity discounts be offered. Inspection and Acceptance for production and initial sparing shall be by Certificate of Conformance (COC) in accordance with FAR 52.246-15 at FOB destination point: Aviation Logistics Center, Receiving Building 63, Elizabeth City, NC 27909. Delivery Schedule for production EFDS ship sets is desired 60 days after receipt of delivery order NLT 120 days after receipt of order.

CLIN 1002 and 1003- Inspection and Acceptance shall be by the Contracting Officer’s Technical Representative (COTR) (to be assigned at contract award).

Option Period Two One-Year following the Option Period One

(Contract Year Four)

Unit of

2001A 2001B 2001C

Acft and Sparing)

Quantity Price Breaks

Hourly Labor Rate) as

Not Separately

Option Period Two Estimated Total $________________________

The Option Period Two estimated total is a summation of the extended price for CLIN’S 2001 and 2002.

CLIN 2001- If funds are available to purchase more than 6 estimated ship sets during this period CLIN’S 2001A, 2001B and 2001C are included should quantity discounts be offered. Inspection and Acceptance for production and initial sparing shall be by Certificate of Conformance (COC) in accordance with FAR 52.246-15 at FOB destination point: Aviation Logistics Center, Receiving Building 63, Elizabeth City, NC 27909. Delivery Schedule for production EFDS ship sets is desired 60 days after receipt of delivery order NLT 120 days after receipt of order.

CLIN 2002 and 2003- Inspection and Acceptance shall be by the Contracting Officer’s

Option Period Three One-Year following Option Period Two

(Contract Year Five)

Uni t of Issu e

3001A 3001B 3001C

Acft and Sparing)

Quantity Price Breaks

13-15

Hourly Labor Rate) as

Option Period Three Estimated Total $________________________

Estimated Contract Total $__________________________

The Option Period Three estimated total is a summation of the extended price for CLIN’S 3001 and 3002. The estimated contract total is the summation of the Base Period, Option Period One, Option Period Two and Option Period Three estimated totals.

CLIN 3001- If funds are available to purchase more than 6 estimated ship sets during this period CLIN’S 3001A, 3001B and 3001C are included should quantity discounts be offered. Inspection and Acceptance for production and initial sparing shall be by Certificate of Conformance (COC) in accordance with FAR 52.246-15 at FOB destination point: Aviation Logistics Center, Receiving Building 63, Elizabeth City, NC 27909. Delivery Schedule for production EFDS ship sets is desired 60 days after receipt of delivery order NLT 120 days after receipt of order.

CLIN 3002 and 3003- Inspection and Acceptance shall be by the Contracting Officer’s

HC-130H EFDS Statement of Work

Date: 28 March 2010

WARNING

This document (software) contains technical data which may be Restricted for export under the International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR). Violations of these export laws may be subject to fines and penalties under the Arms Export Control Act (22 U.S.C. 2778).

WARNING

Contents 1 Scope

1.1 Identification

1.2 System Overview

1.3 Terminology

1.4 Contract Pricing

1.5 Data Deliverables

2 References

2.1 Source of Documents

3 Requirements

3.1 Electronic Flight Display System (EFDS)

3.2 Flight Management System (FMS) Interface

3.2.1 Final Design Configuration

3.3 Program Management (PM)

3.3.1 Monthly Status Report

3.3.2 Integrated Master Schedule (IMS)

3.3.3 Risk Management Plan

3.4 Systems Engineering

3.4.1 Meetings and Reviews

3.4.2 Data and Documentation

3.4.3 Aircraft Qualification and Compatibility

3.4.4 Test and Evaluation

3.4.5 Installation Support

3.5 Human Engineering

3.5.1 Design for Operator

3.5.2 Design for Maintainer

3.6 Logistics

3.6.1 Integrated Logistics Support Plan (ILSP)

3.6.2 Support and Test Equipment (SE)

3.6.3 Maintenance Planning

3.6.4 Computer Resource Support

3.6.5 Supply Support

3.6.6 Facilities

3.6.7 Training

3.6.8 Computer Based Training (CBT)

3.6.9 Training In-Process Reviews (IPR)

3.6.10 Instructor Led Training (ILT)

3.6.11 Publications and Source Data

3.6.12 Government Furnished Equipment (GFE)/ Government Furnished Information (GFI)

3.6.13 Item Unique Identification and Valuation

3.6.14 Request for Nomenclature

3.6.15 HAZMAT Management Program (HMMP) Report

3.6.16 Operations Security (OPSEC) Plan

3.7 EFDS Prototype Evaluation

3.8 Production Approval

3.9 Engineering and Technical Support

4 Administrative Information

4.1 Packaging, Packing and Marking

4.1.1 Shipping Destinations

4.1.2 Shipping Documents

4.2 Inspection and Acceptance

4.3 Delivery Schedule for Production Items

4.4 Period of Performance

4.5 Address of Correspondence

4.6 Invoicing

4.6.1 Invoice Procedures

4.7 Ordering Office

4.8 Exercise of Option

5 Government Directed Travel 6 Proposal Evaluation & Contract Award 7 Rights in Data

Rest of page intentionally blank

1 Scope

1.1 Identification

This document applies to the US Coast Guard (USCG) HC-130H Avionics I Upgrade Project. The HC-130H requires avionics improvements to support Department of Homeland Security (DHS)/USCG strategy and operations and service life through 2027.

Specifically obsolescence, supportability, mission effectiveness, Communication, Navigation, Surveillance/Air Traffic Management (CNS/ATM) functionality, legacy system situational awareness and satellite communications will be addressed via the upgrade, hereafter referred to as the Avionics I Upgrade or A1U.

The Naval Air Systems Command (NAVAIR), Program Manager Air (PMA209), Air Combat Electronics oversees all A1U integration efforts for the USCG, including the project’s non-recurring engineering (NRE). For the purposes of this requirement, the US Government is defined as Naval Air Systems Command, Program Manager Air (PMA209), US Coast Guard Program Office, CG-931, and US Coast Guard Aviation Logistics Center (ALC), Elizabeth City, NC. ALC is responsible for the award and administration of the contract.

The COTS Electronic Flight Control System (EFDS) hardware ship sets are defined in the schedules. The total estimated quantities during the 5 years of this contract is 20 ship sets: 2 ship sets for the prototype aircraft, 15 ship sets for production aircraft, 1 ship set for a System Integration Lab (SIL) and 2 ship sets for initial sparing. The System/Subsystem Specifications (SSS) takes precedence over the SOW in any disagreement between the SSS and the SOW. The Statement of Work (SOW) defines the NRE work to be accomplished by the Contractor, as required by the Government, to complete the design integration efforts through aircraft verification for hardware and software within the firm fixed pricing established in the schedules. The tasks to be accomplished within the scope of this SOW include supporting US government requirements studies, requirements definition, cost-benefit analysis, budgetary planning and technical reviews. Additional tasks performed as labor hour established rates in the schedules include Engineering and Technical support from the EFDS contractor during prototype development, installation and test phase of the A1U Project. Engineering and Technical support may also be called upon to support the Validation and Verification Phase and initial system deployment.

This effort will leverage from other NAVAIR CNS/ATM efforts (P-3C, C-2A, E-2C, and CH/MH-53E), Army CAAS platforms, as well as other previous and ongoing efforts in order to minimize cost and effort while maximizing functionality provided to the Coast Guard fleet.

There will be significant modifications to the HC-130H’s Flight Deck as a result of the A1U requirement. The Pilot and Co-Pilot stations will be modified with a new instrument panel including changes to the center console. Where appropriate, other Pilot/Co-Pilot equipment will be relocated to improve the Human Machine Interface

(HMI). The existing Navigator and Radio Operator’s stations will both undergo significant modifications to allow for improved crew coordination and distribution of crew responsibilities. The existing avionics bay under the flight deck will undergo rework to allow for the new avionics equipment to be installed. Where appropriate on the aircraft, other equipment and antennas will be installed to support the A1U.

The A1U provides for a CNS/ATM upgrade, a complete display system upgrade, and the incorporation of HMI design considerations for the HC-130H aircraft. The major components comprising the A1U are the CDU-7000 based common cockpit Flight Management System (FMS) and the Electronic Flight Display System (EFDS).

1.2 System Overview

The HC-130H aircraft must operate worldwide and operate in civil airspace. In order to ensure safe separation of military and civil air traffic and adherence to air traffic control clearances, the HC-130H aircraft must be capable of performing the following functions:

Required Navigation Performance for Area Navigation (RNP RNAV).

Barometric Vertical Navigation (Baro VNAV).

Mode Select (Mode S) – elementary and enhanced surveillance.

Mode 5 Level 2.

8.33 kHz VHF Channel Spacing.

Traffic Collision Avoidance System (TCAS).

Terrain Avoidance & Warning System (TAWS).

Automatic Dependent Surveillance – Broadcast (ADS-B).

The system must also have growth capability to meet the following future requirements:

Joint Precision Approach Landing System (JPALS).

Mobile User Objective System (MUOS).

Display of flight director data.

1.3 Terminology

This document uses the following terms and definitions:

SHALL: Indicates a requirement. An approved design shall comply with every requirement, which can be assured by inspection, test, analysis or demonstration

Will: Denotes a capability that is a surety or fact.

Should: Denotes a recommendation that would improve the equipment, but does not constitute a requirement.

May: Denotes a recommendation that is optional.

1.4 Contract Pricing

Firm-fixed prices are required for each Contract Line Item Number (CLIN) shown in the Schedule of Supplies/Services for the Base Period and all Option Periods. This includes products and services to support development, integration, installation, test and evaluation of the A1U system on the prototype aircraft (#1/1504) and validation/verification aircraft (#2/TBD) in accordance with the Statement of Work and CDRL A002 Integrated Master Schedule.

CLIN’S 0001, 0002, 0003, 0004, 0005, and 0006 are established as a Firm Fixed Price for completion of Non-recurring Engineering (NRE) services required to integrate the EFDS into the Coast Guard A1U cockpit for the HC-130H aircraft, associated Hardware and Software design and development, Hardware and Software required for Qualification Testing, Qualification Tests, Data Deliverables described in the Contract Data Requirements List (CDRL) (Attachment 2). Authorization to begin Performance under CLIN 0001, 0002, 0003, 0004, 0005 and 0006 will be authorized by issuance of Individual Delivery Orders. Payment for services will be initiated when the assigned Contracting Officer’s Technical Representative (COTR) (TBD) acknowledges final acceptance.

CLIN’S 0009, 1001, 2001 and 3001 are firm-fixed price for an estimated quantity of ship sets to be quoted F.O.B. destination. Each ship set shall be priced as a complete set.

Each set shall be identified by individual components and priced individually to allow component purchasing for initial sharing.

CLIN’S 0007, 1002, 2002 and 3002 are for Engineering and Technical Support services at a fully burdened Hourly Labor Rate inclusive of all applicable cost factors, such as overhead, general and administrative and profit for additional Engineering and Technical support from the EFDS contractor during prototype development, installation and test phase of the A1U Project. Engineering and Technical support may also be called upon to support the Validation and Verification Phase and initial system deployment. Funding for Engineering and Technical Support will be provided by issuance of individual Delivery Orders as a Not-to-Exceed amount, based on the number of estimated hours proposed and agreed upon.

CLIN’S 0008, 1003, 2003 and 3003 are for Government Directed Travel in the event the Government determines a need for on-site Engineering and Technical Support. This reimbursement applies to travel identified in section 5 of the SOW and does not apply to travel to meetings, reviews, conferences, etc., required by Section 3 of the SOW. All Government Directed Travel costs SHALL be reimbursed in accordance with FAR Part

31. The contractor SHALL submit invoices only for Government Directed Travel with supporting documentation in the form of receipts for actual costs. Travel costs outside the specific allowable costs detailed by FAR 31.205-46 shall be borne by the contractor.

1.5 Data Deliverables

The Contract Data Requirements List (CDRL) provided as Attachment 2, discussed in more detail in Section 3.4, comprise the final deliverables relative to the firm fixed priced CLIN’S 0001, 0002, 0003, 0004, and 0005. Government data rights vary and are expressed in Block 4 of each CDRL. All CDRLS shall be submitted to the Government via Email as follows:

Contracting Officer’s Technical Representative (COTR) Email: to be assigned at contract award.

One (1) copy to Naval Air Systems Command, PMA209, Pautuxent River, MD Email: navair.uscg.ISSCDRLSs@eroom.navair.navy.mil

One (1) copy to USCG Program Office, CG-931 Email:

Eric.W.Gerlacher@uscg.mil

One (1) copy to USCG ALC Contracting Officer via the Contract Specialist (Administrator) Email: to be assigned at contract award.

Rest of page intentionally blank mailto:navair.uscg.ISSCDRLSs@eroom.navair.navy.mil mailto:Eric.W.Gerlacher@uscg.mil

2 References

The following references form a part of this SOW to the extent specified. In the event a conflict exists between this SOW and any of the listed references, the SOW SHALL be considered the superseding document.

2.1 Source of Documents

CNO FRD for RNP RNAV Rev.A, 17 Apr 2006

Chief of Naval Operations (CNO) Functional Requirements Document for Required Navigation Performance Area Navigation

Required

MIL-HDBK-454A

03 November 2000

Department of Defense Handbook General Guidelines for Electronic Equipment Guidance

MIL-HDBK-61A(SE) Functional Configuration Audit Guidance Guidance

COMDTINST

M13020.1F

USCG Aeronautical Engineering Maintenance Management Manual Required

Training Center Instruction M1 550.1

USCG Human Performance Technology/Instructional Systems Design Handbook

Guidance

MIL-STD-704A

09 August 1967

Electric Power, Aircraft, Characteristics and Utilization of Guidance

MIL-STD-810G

31 October 2008

Environmental Engineering Considerations and Laboratory Tests Guidance

MIL-STD-882D

10 February 2000 Standard Practice for System Safety Guidance

MIL-STD-1472F

23 August 1999

Department of Defense Design Criteria Standard:

Human Engineering Guidance

JSSG-2000A

8 Oct 2002 Joint Service Specification Guide Air System Guidance

MIL-HDBK-217F

28 Feb 1995

Reliability Prediction of Electronic Equipment Guidance

MIL-PRF-49506

18 Jan 2005

Logistics Management Information Guidance

NAVARINST 5234.5

20 July 2005

Naval Air Systems Command Metrics for Software Intensive Programs Guidance

NAVARINST 4355.19C

10 April 2006

Naval Air Systems Command Engineering Technical Review Process Guidance

JSSG-2010

30 Oct 1998

Department of Defense Joint Service Specification Guide, Crew Systems Engineering Handbook Guidance

JPL-D-10058 Software System Safety Handbook Guidance

STANAG 4404 Software Safety Guidance Guidance

MIL-PRF-29612B Instructional Systems Development Guidance Guidance

MIL-85762A

26 Aug 1988

Lighting, Aircraft, Interior, Night Vision Imaging System (NVIS) Compatible Required

MIL-STD-461F

10 Dec 2007

Requirements for the Control of Electromagnetic Interference Characteristics of Subsystems & Equipment.

Guidance

MIL-STD-464A

19 Dec 2002

Department of Defense Interface Standard;

Electromagnetic Environmental Effects Guidance

S1000D 24 Jan 2005

International Specification for Technical Publications Utilizing a Common Source Data Base Guidance

CGTO PG-85-00-150 Support Equipment Process Guide Required

MIL-DTL 7700G

13 May 2002

Detailed Specifications Flight Manuals, Air Refueling Procedures, and Abbreviated Checklists Guidance

MIL-STD-130N

17 Dec 2007

Military Standard, Identification Marking of US Military Property Guidance

3 Requirements

The overall objective of this SOW is for the contractor to design, modify and integrate hardware and software to meet the requirements delineated in the HC-130H EFDS System/Subsystem Specification, (SSS) provided as Attachment 1 and shall provide all Data identified in the Critical Data Requirements List provided as Attachment 2.

3.1 Electronic Flight Display System (EFDS)

The Contractor SHALL identify all ship set hardware, software or architecture modifications needed to meet the performance requirements of the EFDS SSS such as:

- Display of Required Navigation Performance for Area Navigation (RNP RNAV) data.

- Display of required Barometric Vertical Navigation (Baro VNAV) data.

- Display of communication radio data.

- Display of dual Embedded GPS/INS (EGI) data.

- Display of dual ARN-118 TACAN, dual ARN-123 VOR, ARN-149, and DF-430 data.

- Display of Digital Video/Imagery.

- Control and display of digital map Control and display of electronic chart data.

- Display of Terrain Avoidance & Warning System (TAWS) data.

- Display of Traffic Collision Avoidance System (TCAS) data.

The system must also have growth capability to meet the following future requirements:

-Joint Precision Approach Landing System (JPALS).

-Mobile User Objective System (MUOS).

-Display of flight director data.

3.2 Flight Management System (FMS) Interface

The Contractor SHALL recommend ship set hardware, software or architecture modifications needed to integrate EFDS functionality with the FMS such as data required or data bus requirements identified in paragraph 3.1 and modifications needed to meet the performance requirements of the FMS SSS such as:

RNP RNAV operations (with VNAV) down to and including RNP 0.3.

Control and display of APX-119 Common Digital Transponder modes, 1, 2 3/A, C, 4, 5, (level 2).

Control and display of Mode S ELS and EHS.

Control and display of dual ARC-190 RT-1341(V)8 radios, three ARC-210 RT-

1851A radios, 618M-3A VHF radio.

Control and display of dual Embedded GPS-INS units (EGI) equipped with GEM

V SAASM GPS receiver.

Control and display of dual ARN-118 TACAN, dual ARN-123 VOR, ARN-149

ADF, and DF-430.

3.2.1 Final Design Configuration

Final design configuration, which identifies system display components, SHALL be provided, by part number to the USCG Contracting Officer, inclusive of firm-fixed component pricing. The components will be incorporated by modification for production acquisition purposes.

3.3 Program Management (PM)

The contractor SHALL establish an HC-130H System/Subsystem Integrated Product Team (IPT). The contractor SHALL identify and maintain a single point of contact

(Program Manager-PM) for all non-technical tasks required and a single point of contact for all technical tasks for the program.

The contractor will be responsible for planning and implementing sound project management processes. The contractor planning SHALL include identification of all work to be accomplished, schedules for the work, and identification of the organization charged with the responsibility for performance of the work.

3.3.1 Monthly Status Report

The contractor SHALL report, on a monthly basis, the status of the program. This includes tasks completed, issues, the risk mitigation plan, software metrics (as described in NAVAIR INSTRUCTION 5234.5), logistics, training, as well as plans for the next period. As part of this report, the contractor SHALL provide funding and man-hour expenditures inclusive of past and current reporting period compared to planned, baseline values. The contractor SHALL provide explanation for cost/schedule variances greater than 5% from planned values (CDRL A001 – Monthly Status Report).

3.3.2 Integrated Master Schedule (IMS)

The contractor SHALL prepare an Integrated Master Schedule for input to the Master IMS that is managed by the Government. For the basis of program performance and schedule assessment, program and technical reviews will be addressed during each NRE Job completions. The IMS SHALL include formal and informal engineering software builds, functionality for each software build, and test and release dates. The contractor SHALL plan efforts through Verification (including A-Kit design, development, install, check-out and final testing), as well as clearly delineate the program critical path. The IMS will be updated and submitted on a monthly basis (CDRL A002 – Integrated Master Schedule).

3.3.3 Risk Management Plan.

The contractor SHALL employ the Risk Management Plan for identifying, mitigating and managing program risks. The contractor SHALL participate in and support the Government’s overall risk management efforts as part of the HC-130H A1U System/Subsystem (CDRL A003 – Risk Management Plan).

3.4 Systems Engineering

The contractor SHALL conduct development efforts that ensure end-to-end FMS/EFDS System/Subsystems requirements traceability from the system level down to test and evaluation plans and procedures. This traceability will be demonstrated throughout the systems engineering effort as part of design reviews and as a final deliverable product.

3.4.1 Meetings and Reviews

3.4.1.1 Meetings and Reviews

The contractor SHALL host and participate in periodic program meetings and reviews for the duration of the contract. These reviews will be conducted at the contractor’s facility, Patuxent Naval Air Station, or USCG Headquarters Washington, DC or USCG Aviation Logistics Command (ALC), Elizabeth City, NC. NAVARINST 4355.19 Series will be used as a guide in the conduct of various reviews. The contractor SHALL provide meeting agenda and presentation material (CDRL A004 – Meeting Agenda, CDRL A005 – Presentation Material). The contractor will be responsible for publishing minutes of all meetings and reviews. Meeting minutes SHALL be distributed for the Government’s approval NLT 10 days after any meeting (CDRL A006 – Meeting Minutes). Travel costs for meetings, regardless of location SHALL be borne by the traveling party.

3.4.1.2 Program Management Reviews (PMRs)

The contractor and the Government SHALL collaboratively support a Program Management Review (PMR) with FMS contractor every quarter. PMRs will cover, at a minimum, program status, updated software/system metrics, relevant program issues, and updated IMS. PMRs may be combined with other reviews or meetings as appropriate.

PMRs may be conducted via teleconference or Web Based with Government concurrence. The location for PMRs, as separate meetings, will be evenly divided between FMS contractor, USCG and Navy (Patuxent River) facilities.

3.4.1.3 Technical Interchange Meetings (TIMs)

The contractor and the Government SHALL collaboratively participate in three (3) Technical Interchange Meetings (TIM’s) with FMS contractor, to facilitate the exchange of technical information necessary to resolve system/subsystem issues. TIMs may be combined with other reviews and meetings as appropriate. TIMs may be conducted via teleconference as separate meetings with Government concurrence. The location for the TIMs, as separate meetings, will be evenly divided between contractor, USCG and Navy (Patuxent River) facilities.

3.4.1.4 Subsystem Technical Review

The contractor SHALL participate and support a Subsystem Technical Review for the HC-130H A1U system, subsystem, and software designs 30 calendar days after contract award. The primary purpose of the review is to ensure the system can proceed into detailed design, and can meet the stated performance requirements within cost, schedule, risk and other system constraints.

Completion of this review should provide:

An established system allocated baseline.

Risk assessment.

Program schedule including system and software critical path drivers.

This review determines whether the hardware, human and software preliminary designs are complete, and whether the contractor is prepared to start detailed design and test procedure development. The subsystem requirements are evaluated to determine whether they correctly and completely implement all system requirements allocated to the subsystem, and whether traceability of subsystem requirements to system design is maintained. The contractor brief shall demonstrate completion of required accomplishments and readiness to proceed to Critical Design Review (CDR).

3.4.1.4.1 Subsystem Technical Review Deliverables:

Presentation Material (CDRL A005 – Presentation Material).

Integrated Master Schedule (CDRL A002 – Integrated Master Schedule).

Final HC-130H EFDS System/Subsystem Specification (SSS) (CDRL A007 –

System/Subsystem Specification).

Complete RVM with a preliminary allocation of system requirements to hardware, human and software subsystems (CDRL A008 – Requirements Verification Matrix).

Updates to the FMS contractor for the System/Subsystem Requirements Document (SRD) (Support FMS contractor SRD CDRL)(DAL).

Updates to the FMS contractor Interface Control Document (Support FMS contractor ICD CDRL) (DAL).

Preliminary System Safety Hazard Analysis (CDRL A009 – System Safety Hazard Analysis).

Software Development Plan (CDRL A010 – Software Development Plan) Risk Plan (CDRL A003 – Risk Management Plan).

3.4.1.4.2 Data To Be Presented

The contractor SHALL present a vendor briefing with the following, at a minimum:

System design.

Program Organization and Staffing status.

System Architecture (hardware, software, human) complete with details regarding partitioning rationale and approach to architecture development.

Updated program schedule, work breakdown, and resource allocations.

Estimates of allocated Hardware Configuration Items (HWCI)/Computer

Software Configuration Items (CSCI) performance requirements, including those for execution time, storage requirements, and similar constraints.

Software Lines of Code (SLOC) estimates (new, reused, modified) for all CSCI’s.

Requirements Traceability/Verification Matrix.

Identification of program risks and mitigation plans.

Updated cost and schedule data.

Logistics documentation status.

Software plans and tracking metrics.

Subcontract/Supplier Status.

Software Integration effort with FMS.

Facilities.

Training design and status.

3.4.1.5 Critical Design Review (CDR)

The CDR is a multi-disciplined product and process assessment to ensure the system under review can proceed into system fabrication, demonstration, and test, and can meet the state performance requirements within cost, schedule and risk and other system constraints. Generally this review assesses the system final design as captured in product specifications for each configuration item in the system (product baseline), and ensure that each product in the product baseline has been captured in the detail design documentation.

The contractor SHALL participate in and support a CDR for the final system, subsystem and software designs. This review will be held at a facility to be jointly determined when the entry criteria listed below are met. As the primary purpose of the CDR is to evaluate the completeness of the software design, its interfaces, and its suitability to start initial coding, the contractor brief must demonstrate completion of required accomplishments and readiness to process to the next key milestones.

3.4.1.5.1 CDR Entry Criteria

The contractor SHALL participate in a CDR 90 calendar days after contract award. The contractor SHALL provide the following items as per the DD 1423-1 CDRL form:

Inputs requested by the FMS contractor to support the RNP analysis are provided.

Inputs requested by the FMS contractor to support Final System Requirements

Document (SRD) are provided.

The updated System Requirements Verification Matrix (only depicting delta and derived requirements) (CDRL A008 – Requirements Verification Matrix).

Final Page Layouts contained in the SRD – presented at CDR.

Updated data required for Government to obtain a flight clearance – present at

CDR:

o Mass properties of all CFE/Contractor modified GFE.

o Electrical Characteristics (load requirements) for all CFE/Contractor modified GFE.

o Cooling requirements for all CFE/Contractor modified GFE.

o CFE Environmental Qualification data.

o CFE Electromagnetic Environmental Effects (E3) Qualification data.

o CFE interface control documentation sufficient to support installation of the LRU/WRA into the aircraft.

o Final Subsystem Hardware Requirements Documents (SHRD) (CDRL

A011 – Subsystem Hardware Requirements Document).

o Inputs requested by the FMS contractor to support Final Interface Control

Document (ICD) are provided.

o Final HIDD (CDRL A012 – Hardware Interface Design Document) completed.

o Final System Safety Hazard Analysis (CDRL A009 -- System Safety

Hazard Analysis).

o Final Integrated Master Plan (IMTP) (DAL).

o Inputs requested by the FMS contractor to support final Integrated

Logistics Support Plan (ILSP) are provided.

o Preliminary Software Design Description (CDRL A013 – Software Design

Description).

o Preliminary Software Test Descriptions (DAL).

o Preliminary System Users Source Data (CDRL A014 – System Users

Source Data).

3.4.1.5.2 Data to be presented at CDR:

At a minimum, the contractor SHALL present the following at CDR:

The system design, including traceability of design characteristics to the SSS.

The identified risks and risk mitigation plans.

System Safety and Software hazards including use of hazardous materials.

The test program including an updated Integrated Master Test Plan.

Updated Requirements Verification Matrix (only depicting delta and derived requirements).

Software metrics, test and release dates.

Status of subcontract efforts.

System Integration Lab (SIL) support status.

Integrated Master Schedule.

Page trees and page layouts.

Display page layouts.

Updated subsystem functional flows, requirements allocation data, and schematic diagrams.

A functional review of each EFDS-based application (Computer Software

Configuration Item), including inputs, processing, and outputs to provide an understanding of application dependencies and relationships.

All interface requirements for each EFDS-based application both internal and external to the system.

Updated EFDS-based storage allocation data, timing and sizing.

EFDS-based application component functionality and application internal data flows.

Updated EFDS-based application control function descriptions.

Integrated Logistics support and planning status.

3.4.1.5.3 CDR Exit Criteria:

The CDR SHALL be considered complete when the requirements of paragraphs

3.4.1.5.1 and 3.4.1.5.2 are met, the meeting minutes are approved, all Requests for Actions (RFAs) are signed off, and an acceptable level of program risk is ascertained.

3.4.1.5.4 CDR Approval Process

Upon successful submission of and/or evidence of meeting the criteria listed above, approval will be accomplished by US Government Engineering Personnel. Formal written notification to proceed beyond CDR will be provided by the USCG Contracting Officer.

3.4.1.6 Installation Readiness Review (IRR)

The IRR is an examination of a program to determine if the “A-Kit” design is ready for production and installation and the installer has accomplished adequate planning without incurring unacceptable risks that will breach thresholds of schedule, performance, cost or other established criteria. The full, production configured system is evaluated to determine that it correctly and completely implements all system requirements, and whether the traceability of final system requirements to the final installed system is maintained.

The contractor SHALL support an IRR, 60-90 days after CDR, for the final system, subsystem, and software designs. This review will be held at a government facility, either NAVAIR, Patuxent River, MD, or the SELEX facility in Kiln, MS (installation facility) or USCG HQ Washington DC, when the entry criteria listed below are met:

3.4.1.6.1 IRR Entry Criteria

IRR technical products have been made available to the cognizant IRR participants prior to this review.

Change control process has been established and the customer has approved the installation configuration baseline.

A-Kit manufacturing, production and quality requirements have been addressed during the design/development phase.

Current risk assessment.

The CDR has been successfully completed and closed out.

All system performance specification qualification test requirements have been successfully met.

3.4.1.6.2 IRR Exit Criteria

The IRR will be considered complete when all Requests for Actions (RFAs) are closed by CG-931.

3.4.1.6.3 IRR Approval Process

Upon successful submission of and/or evidence of meeting the criteria listed above, IRR approval will be accomplished US Government Engineering personnel. Formal written notification to proceed beyond IRR will be provided by the USCG Contracting Officer.

3.4.1.7 Flight Readiness Review (FRR)

The FRR is a multi-disciplined product and process assessment to ensure the system under review can proceed into flight test with NAVAIR and USCG airworthiness standards met, objectives clearly stated, flight test data requirements clearly identified and an acceptable risk management plan defined and approved. Generally, this review ensures that proper coordination has occurred between engineering and flight test and that all applicable disciplines understand and concur with the scope of effort that has been identified and how this effort will be executed to derive the data necessary (to satisfy airworthiness and test and evaluation requirements) to ensure the system evaluated is ready to proceed to flight test.

The contractor SHALL support an FRR for the final system, subsystem, and software designs. This review will be held at a government facility, either NAVAIR, Patuxent River, MD, or the SELEX facility in Kiln, MS (installation facility) or USCG HQ Washington DC, when the entry criteria listed below are met:

3.4.1.7.1 FRR Entry Criteria

The CDR has been successfully completed and closed out.

CDR technical products (all elements of the product baseline to be reviewed and approved at the FRR, including final specifications, analyses, and data) have been made available to the cognizant FRR participants prior to the review. This SHALL include open and closed action items from the CDR and any subsequent technical review.

Final detail hardware and software designs have been implemented in all configuration items and have been placed under configuration management control. All integrated system testing will be completed by FRR.

A flight clearance pre-planning meeting has been convened and an Engineering Data Requirements Agreement Plan (EDRAP) has been signed between the APMSE/IPT (or applicable Senior Engineer), Air 4.x Engineering and USCG Engineering personnel (CG-41).

Applicable PMs have been briefed to ensure FRR is consistent with program objectives (cost, schedule and performance) and priorities are understood.

A flight clearance has been issued (or a defined flight clearance process, with plans to get an initial flight clearance at FRR exists).

Critical flight test support efforts have been identified and are under review and/or completed.

3.4.1.7.2 FRR Exit Criteria

The FRR will be considered complete when all Requests for Actions (RFAs) are closed by CG-931.

3.4.1.7.3 FRR Approval Process

Upon successful submission of and/or evidence of meeting the criteria listed above, FRR approval will be accomplished jointly by US Government Engineering personnel.

Formal written notification to proceed beyond FRR will be provided by the USCG Contracting Officer.

3.4.2 Data and Documentation

3.4.2.1 Systems Engineering Plan

The Contractor SHALL deliver a Systems Engineering Plan. The SEP shall detail the Contractors robust systems engineering approach that balances total system performance and total ownership costs within the family-of-systems, system-of-systems context. The details are described in NAVAIR 4355.19 series document titled “Systems Engineering Technical Review Process” (CDRL A015 - Systems Engineering Plan).

3.4.2.2 System/Subsystem Specification (SSS)

The contractor SHALL maintain and update the EFDS SSS provided as an attachment to this Request for Proposal (RFP) based on changes and approvals adopted during preceding system reviews. This requirements document is derived from the government furnished FRDs, ORD and other USCG requirements documents (CDRL A007 – System/Subsystem Specification).

3.4.2.3 Requirements Verification Matrix (RVM)

The contractor SHALL generate, update and maintain the Requirements Verification Matrix and provide to the FMS contractor. The RVM SHALL ensure end-to-end requirements traceability from the system level down to test and evaluation plans and procedures. This traceability SHALL be demonstrated throughout the systems’ engineering effort as part of design reviews and made available on the Data Accession List (DAL) in Microsoft Excel format. The contractor SHALL provide an RVM that depicts delta and derived requirements (CDRL A008 – Requirements Verification Matrix)

3.4.2.4 Required Navigation Performance (RNP) Analysis

Report

The contractor SHALL support the FMS contractor in developing and maintaining an RNP Analysis Report that presents a detailed analysis of the HC-130H CNS/ATM system in terms of its compliance to RNP RNAV standards. This report will present the methods and assumptions used in the analysis. The RNP RNAV FRD defines the standards used for the analysis.

3.4.2.5 System/Subsystem Requirements Document (SRD)

The contractor SHALL support the FMS contractor in updating and maintaining the SRD. The SRD SHALL determine and document the system requirements for the Top Level SRD and HC-130H FMS System components with assistance from other program contractors.

3.4.2.6 Interface Control Document (ICD)

The contractor SHALL support the FMS contractor in updating and maintaining the system-level Interface Control Document (ICD). This ICD SHALL describe all digital interfaces including bit definition, order of transmission, transmission rates, frame rates, destination, source and bus loading. The ICD SHALL provide sufficient tracking back to the HIDD to permit systems engineers to determine if filters and/or cable impedance could compromise data transmission rate.

3.4.2.7 Subsystem Hardware Requirements Document

(SHRD)

The contractor SHALL provide a detailed Specification Document for vendor hardware as well as specification drawings for other subcontractor equipment delivered as components of the A1U (CDRL A011 – Subsystem Hardware Requirements Document).

3.4.2.8 Subsystem Interface Control Documents (SICD)

The contractor SHALL provide interface control documents for the CFE/Contractor modified GFE (CDRL A016 – Subsystem Interface Control Documents). The documents SHALL include as a minimum:

Outline and Installation drawings.

Electrical and pneumatic (as applicable) connector descriptions.

Connector pin signal listings with function and electrical descriptions.

Digital signal protocol definitions.

Identification of any configuration pin settings (aircraft ID tables).

3.4.2.9 Hardware Interface Design Document (HIDD)

The contractor SHALL generate, update and maintain the Hardware Interface Design Document (HIDD). This HIDD SHALL describe the point-to-point wiring requirements amongst the system LRU’s. This document SHALL include cable/harness lists that describe individual point-to-point signal or power carrying requirements. Data rate and nominal current and voltage SHALL be described.