80AFRC18R0015P00003_-_SF30.pdf

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

000003

AFRC

Rosalia Toberman, Contracting Officer

The purpose of this amendment is to respond to questions received. Accordingly;

NASA/Armstrong Flight Research Center P.O. Box 273, M/S S323 Edwards, CA 93523-0273

80AFRC18R0015

1 4

09/27/2018

09/18/2018

Q & A FOR RFQ: 80AFRC18R0015 FBO.GOV POSTING

DATED: SEPTEMBER 18, 2018

Q1: In section 3.1 of the Statement of Work there are several items that are identified as *CS

(customer supplied); I would assume this is synonymous with Government Furnished Equipment.

Some of the sub‐items, for example 3.1(d)(i) list a requirement to “furnish and install” equipment and then show an equipment list that appears to be customer supplied.

A1: The wording “Furnish and” has been removed from section 3.1(d)(i) and it now reads as follows:

d. MFD‐640 – TYPICAL

i. Install a new Universal Avionics MFD‐640 Multifunction Display Unit in place of the existing Radar Indicator. The MFD may allow display of

Radar, TAWS, TCAS and FMS Nav information, if available.

Q2: There are items listed in various areas that are not identified as *CS (e.g. VHF antenna which do not list the required part number. Can a clarified list be released of what equipment is government supplied and what equipment (by part number and nomenclature) will need to be vendor provided?

A2: See Exhibit 4 of labeled “Attachment 1.1‐Exhibits 1‐4” on the base combined synopsis/solicitation for a detailed customer supplied parts list. VHF antenna are not going to be installed. We are utilizing currently installed UHV/VHF antenna on the aircraft.

- 3.1. a. iv. 8 is also *CS (customer supplied)

- 3.1. b. iii. 4. VHF Antenna is also *CS

- 3.1. e. may want to include *CS customer supplied parts from the following table

- 3.1. f. may want to include *CS customer supplied parts from

Q3: Will access to the tech data and “right to use” for existing STCs be government provided or does this cost need to be negotiated and provided by the vendor to be included in the quote?

A3: Tech Data will be government provided upon request from winning contractor of specific data requirements.

Q4: Is the government seeking STC certification for any portion of the upgrade which is not covered by an existing STC?

A4: NASA is not seeking any STC Certification. NASA is requesting a Form 337 using existing/applicable STC as a reference for the upgrades.

DATED: SEPTEMBER 18, 2018

Q5: In section 3.1 Avionics Upgrade, paragraph c. ADS‐B Proline TDR‐94D, v. Verify RVSM capability –

We are unsure if the aircraft has a current RVSM capability (equipment/approval), or if you wish the contractor to add this capability, or if you simply wish the contractor to verify that the ADS‐B out function remains compatible with the existing RVSM capability.

A5: NASA‐AFRC currently has RVSM.

Q6: Several annunciators are referred to in the section 3.1 Avionics Upgrade, paragraph a. IV. 9. Are these defined already by NASA or added WAAS annunciation that is required?

A6: Parts are undefined at this time but NASA‐AFRC will need annunciators that new FMS/GPS requires with WAAS/SBAS.

Q7: There are also two annunciators required in section 3.1 Avionics Upgrade, paragraph c. ADS‐B

Proline TDR‐94D, ii. 3. Are these the “ADS‐B FAIL” annunciators that are driven by the Skylight Digital

Discrete Adapter (DDA)?

A7: Annunciators may be required for ADS‐B capabilities using parts listed on Exhibit #4, if needed vendor will be required to procure.

Q8: In In section 3.1 Avionics Upgrade, paragraph d. MFD‐640 Typical, we don’t have any indication of the type of existing WX radar indicator that is to be replaced (although a Primus‐880 type can be assumed as that is the controller to be installed). This type of information, and photos of the instrument panel where the current weather radar indicator is located could help us refine this line‐ item cost for structures work that will be required.

A8: WX radar indicator with radar controller is going to be removed and replaced with P/N:

MFD‐640 and P/N: 7008471‐408 Radar Controller and has been provided by the NASA‐AFRC and is listed in Exhibit #4.

Q9: It’s unclear if the aircraft is in a Standard category, or experimental – Show Compliance category.

Without an N number registration, we assume it’s in Public Use category also.

This information will help determine the type of approvals to return the aircraft to service and the amount of FAA FSDO coordination required, along with DER type of approvals. (Public use or experimental does not allow our FAA DER’s to use FAA 8110‐3 forms for engineering data approval, only a letter‐in‐lieu of 8110‐3 that basically states if the aircraft were in a normal category, the data would be approvable).

A9: 30‐502AF is a public use aircraft under Governmental Function. Due to this reason a letter‐ in‐lieu of 8110‐3 that basically states if the aircraft were in a normal category, the data would be approvable is an acceptable alternative to the FAA 8110‐3 forms for engineering data approval.

Q10: In section 5.0 Deliverables, 5.5 – does this training have to be Universal Avionics classroom training for the UNS‐1Lw, UL‐801, ICS‐120 Satcom and MFD‐640, or on‐aircraft training in the cockpit and during flight evaluation?

DATED: SEPTEMBER 18, 2018

A10: The training will need to be on‐site training at the contractor’s location. This does not necessarily need to be Universal Avionics classroom.

Q11: Is it the intent of the solicitation to have non‐avionics related checks as defined below to be accomplished as part of the solicitation?

A. Operation No.1 (Exhibit 1), all codes except 237500 appear to be airframe related, not avionics related.

B. Operation No. 2 (Exhibit 2), all codes appear to be airframe related, not avionics C. Operation No. 3 (Exhibit 3), all codes except 253030, 223030, 223035, 340400, 340405, 340410, 341030, 341035, 346047, 346048, 346050, 346055, 346060, 346060, and 346070 appear to be airframe related, not avionics.

A11: Yes

Q12: Will NASA provide job cards for this effort?

A12: Yes

Q13: If Special Equipment (SE) is required for these maintenance checks, will NASA provide the SE?

A13: No

Q14: As the solicitation is to result in a Firm Fixed contract, how will labor and/or parts resulting for a failed test be compensated?

A14: A written request from the vendor with Justification will need to be submit for any over and above costs to include labor category with labor rates along with all material costs associated with the over and above.

Q15: Will the government accept that an FAA FAR 145 Certified Repair Station meets all Quality

Management compliance requirements for this effort? Ref: Attachment 2 of Q‐1, page 2(b).

A15: Offeror shall comply with all requirements of the solicitation.