SF30_Amendment_0007.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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.

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The Purpose of Amendment 0007 is to revise RFP N00019-15-R-0081 as show n in Section I and as highlighted in yellow , to provide an updated SOW, to attach updated CDRLs, and to publish additional Questions and Answ ers.

1. CONTRACT ID CODE PAGE OF PAGES

1 27

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

16C. DATE SIGNED

BY 19-Nov-2015

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N00019-15-R-0081

X 9B. DATED (SEE ITEM 11)

18-Sep-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offer 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 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram 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 telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, 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)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

19-Nov-2015

CODE

NAVAL AIR SYSTEMS COMMAND

AIR-2.4.1.2 SUITE 256 BLDG 2272

47123 BUSE ROAD UNIT IPT

PATUXENT RIVER MD 20670

N00019 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00019-15-R-0081

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

DESCRIPTIONS AND SPECIFICATION

Items 0001 and 0002 –Engineering Development Model (EDM) #1 and the associated spares in the Pre-Critical

Design Review (CDR) configuration shall be manufactured and provided to the Government SATR Lab for testing and EDM #2 and the associated spares in the Pre-CDR configuration shall be manufactured and remain at the contractor’s plant for testing in accordance with paragraph 4.1 of Attachment 1, “Statement of Work for Shipboard

Air Traffic Radar (SATR) AN/SPN-50(V)(1)”, dated 16 November 2015.

Item 0003 – The Engineering and Manufacturing Development (EMD) non-recurring efforts are to develop, test and update the contractor design to a Post-CDR configuration in accordance with Attachment 1, “Statement of Work for

Shipboard Air Traffic Radar (SATR) AN/SPN-50(V)(1)”, dated 16 November 2015 and Attachment 2, “Systems

Requirements Document (System Specification) for Shipboard Air Traffic Radar AN/SPN-50(V)1”, dated 02

October 2015. EDM #3 and the associated spares in the Post-CDR configuration shall be manufactured, tested and delivered. EDMs #1 and #2 shall be updated to and tested in the Post-CDR configuration. Spares shall be provided for the Post-CDR EDMs #1 and #2.

Item 0004 – The technical and administrative data required hereunder shall be provided in accordance with Exhibit

A, Contract Data Requirements List, DD Form 1423.

SECTION D - PACKAGING AND MARKING

DELIVERIES AND PERFORMANCE

Items 0001 and 0002 –EDM #1 and associated spares in the Pre-CDR configuration shall be preserved, packed, and packaged in accordance with MIL-E-17555H, dated 15 November 1984, and Interim Amendment 2, dated 2

November 1992 and shipped to the SATR Lab in St. Inigoes, MD. EDM #2 and associated spares in the Post-CDR configuration shall be preserved, packed, and packaged in accordance with MIL-E-17555H, dated 15 November

1984, and Interim Amendment 2, dated 2 November 1992 and shipped to the SATR Lab in St. Inigoes, MD.

Preservation, packaging, and marking shall be at the following levels:

Preservation and Packaging Level A

Packing Level C

Item 0003 – EDM #3 and associated spares in the Post-CDR configuration shall be preserved, packed, and packaged in accordance with MIL-E-17555H, dated 15 November 1984, and Interim Amendment 2, dated 2 November 1992 and shipped to a Government Lab on the east coast of the United States. Preservation, packaging, and marking shall be at the following levels:

Preservation and Packaging Level A

Packing Level C

Item 0004 – The technical and administrative data to be furnished in accordance with Exhibit A, Contract Data

Requirements List, DD Form 1423, shall be adequately packaged and packed to ensure safe delivery at destination.

UNPACKING INSTRUCTION: COMPLEX OR DELICATE EQUIPMENT

(a) Location on Container. When practical, one set of the unpacking instructions will be placed in a heavy waterproof envelope prominently marked "UNPACKING INFORMATION" and firmly affixed to the outside of the shipping container in a protected location, preferably between the cleats on the end of the container adjacent to the identification marking. When the unpacking instructions are too voluminous to be affixed to the exterior of the container, they will be placed inside and directions for locating them will be provided in the envelope marked "UNPACKING INFORMATION.”

(b) Location on Container. When unpacking instructions are provided, shipping containers will be stenciled

"CAUTION-THIS EQUIPMENT MAY BE SERIOUSLY DAMAGED UNLESS UNPACKING

INSTRUCTIONS ARE CAREFULLY FOLLOWED. UNPACKING INSTRUCTIONS ARE LOCATED

(state where located)." When practical, this marking will be applied adjacent to the identification marking on the side of the container.

(c) Marking. All shipping containers will be marked in accordance with the Military Standard Marking for

Shipment and Storage, MIL-STD-129M, dated 15 June 1993.

SECTION E - INSPECTION AND ACCEPTANCE

ADDITIONAL ACCEPTANCE CRITERIA

Item 0001 – Inspection and Acceptance of EDM # 1 and associated spares in the Pre-CDR configuration shall occur upon successful completion of the factory performance testing in accordance with paragraph 4.1 of Attachment 1, “Statement of Work for Shipboard Air Traffic Radar (SATR) AN/SPN-50(V)(1)”, dated 16 November 2015.

Acceptance shall be made via a DD-250, “Material Inspection and Receiving Report”.

Item 0002 –Inspection and Acceptance of EDM # 2 and associated spares in the Pre-CDR configuration shall occur upon successful completion of the factory performance testing in accordance with paragraph 4.1of Attachment 1, “Statement of Work for Shipboard Air Traffic Radar (SATR) AN/SPN-50(V)(1)”, dated 16 November 2015.

Acceptance shall be made via a DD-250, “Material Inspection and Receiving Report”.

Item 0003 – Inspection and acceptance of the nonrecurring engineering & manufacturing development efforts to be provided hereunder shall be made by Government review and approval of data submittals under Exhibit A, Contract

Data Requirements List, DD Form 1423. Final acceptance of Item 0003 shall not occur until the Government has made final acceptance of all data submissions for which approval is required under Exhibit A, acceptance has been made of the upgrades of EDM # 1 and EDM # 2 to the Post CDR configuration, and acceptance has been made of

EDM # 3 in the Post-CDR configuration. Acceptance of the upgrades of EDM # 1 and EDM # 2 to the Post-CDR configuration shall occur upon successful completion of the Government approved Systems Operation and

Verification Test (SOVT) demonstrating compliance with Attachment 2, “Systems Requirements Document

(System Specification) for Shipboard Air Traffic Radar AN/SPN-50(V)1”, dated 02 October 2015. Acceptance of the upgrades of EDM # 1 and EDM # 2 shall be made via a DD-250, ‘Material Inspection and Receiving Report”.

Acceptance of EDM # 3 in the Post-CDR configuration shall occur upon successful completion of the Government approved Systems Operation and Verification Test (SOVT) demonstrating compliance with Attachment 2, “Systems

Requirements Document (System Specification) for Shipboard Air Traffic Radar AN/SPN-50(V)1”, dated 02

October 2015. Acceptance of EDM # 3 shall be made via a DD-250, “Material Inspection and Receiving Report”.

Item 0004 - The technical and administrative data required hereunder shall be inspected and accepted in accordance with Exhibit A, Contract Data Requirements List, DD Form 1423.

SECTION F - DELIVERIES OR PERFORMANCE

DELIVERIES OF PERFORMANCE

Accelerated delivery is acceptable predicated upon the written approval of the Contracting Officer, Naval Air

Systems Command, Attn: Mr. Dan Gentry , AIR-2.2.1.4, Bldg 2272, Suite 256, 47123 Buse Road, Unit IPT, Patuxent River, MD 20670-1547, Email: william.gentry@navy.mil

Item 0001 - The Contractor shall manufacture EDM #1 and associated spares in the Pre-CDR configuration and deliver EDM #1 and associated spares in the Pre-CDR configuration to Naval Air Warfare Center, Webster Field, no later than 16 months after contract award to the following address:

Receiving Officer

NAWC Patuxent River Webster Field Annex, Building 8008, Room 116

St. Inigoes, MD 20684

Phone: (301) 995-6071

F.O.B. Destination

Item 0002 – The Contractor shall deliver EDM #2 and associated spares in the Pre-CDR configuration and start testing at the Contractor’s facility no later than 19 months after contract award.

Item 0003 –The nonrecurring engineering and manufacturing development efforts to be provided hereunder shall be completed and delivered no later than 75 months after contract award. The Contractor shall complete the update of

EDM # 1 to the Post-CDR configuration at NAWC Patuxent River Webster Field Annex within 18 months after completion of CDR. The Contractor shall update EDM #2 to the Post-CDR configuration and deliver EDM #2 with

Spares to the Government no later than 18 months after completion of CDR to the following address:

Receiving Officer

NAWC Patuxent River Webster Field Annex, Building 8008, Room 116

St. Inigoes, MD 20684

Phone: (301) 995-6071

F.O.B. Destination

The Contractor shall deliver EDM Unit #3 with spares in the Post-CDR configuration to a Navy Lab in the eastern

United States no later than 12 months after completion of CDR. The address will be provided by the PCO 60 days prior to shipping.

mailto:william.gentry@navy.mil

Item 0004 - The technical and administrative data required hereunder shall be delivered in accordance with Exhibit

A, Contract Data Requirements List, DD Form 1423.

SECTION I - CONTRACT CLAUSES

The following have been added by reference:

52.219-9 (Dev) Small Business Subcontracting Plan (Deviation 2013-O0014) OCT 2015

52.219-16 Liquidated Damages-Subcontracting Plan JAN 1999

The following have been deleted:

52.219-9 Small Business Subcontracting Plan OCT 2014

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

SUBCONTRACTING PLAN

SUBCONTRACTING PLAN

Subcontracting Plan - at time of award

Attachment List

Attachment 1 –“Statement of Work for Shipboard Air Traffic Radar (SATR) AN/SPN-50(V)(1)”, dated 16

November 2015.

Attachment 2 - “Systems Requirements Document (System Specification) for Shipboard Air Traffic Radar AN/SPN-

50(V)1”, dated 02 October 2015 (provided under separate cover).

Exhibit List

Exhibit (A) – Contract Data Requirement List (CDRL), DD Form 1423

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

CONTENTS OF PROPOSAL

PART A - GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit a written proposal as part of this solicitation. Offerors shall respond to all requirements in Section L. Do not alter or rearrange the solicitation unless specifically requested. The Offerors are advised that the Government may incorporate into the final contract any part of the Offeror’s proposal deemed beneficial to the Government. No cost information shall be included in the Technical Volume.

Clarity, brevity and logical organization shall be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the areas of Section L to be meaningfully evaluated for compliance without discussions. Alternate proposals are not acceptable.

Failure to clearly address a specific factor may cause a proposal to be deemed unacceptable. There is no need to repeat information in more than one volume if an overlap exists. Unnecessarily elaborate brochures or other presentation beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

Offerors are expected to comply with all requirements of the Request for Proposal (RFP). The Government advises

Offerors that taking exception or deviating from any term or condition of the RFP shall make an offer Unacceptable and the Offeror ineligible for award.

Throughout these instructions, Offeror is defined as the prime contractor with its CAGE/NCAGE code identified in

Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. A “JV Team Member” is defined as one of the entities that make up a JV or any other partnership or teaming arrangement formed for the purpose of responding to this solicitation. The term

“entity” is used to mean any or all of the following: prime contractor, JV, critical team members, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different

CAGE/NCAGE code/DUNS than the Offeror). A “principal subcontractor” is defined as a subcontractor who provides at least 20% of the proposed total price (excluding the Offeror’s profit/fee) for the contract. “Critical team member” is defined as one of the entities of the Offeror that perform a critical technical function (i.e.

Security/Safeguarding, MAUS inspections and aircraft X-Rays) in the performance of the resulting contract.

The Offeror shall certify, in its proposal cover letter, that all electronic proposal information has been checked and is virus free, and specify the software, version, and virus definition used to check the data. With each subsequent submission of proposal information (e.g., responses to Evaluation Notices, Final Proposal Revisions, etc.), the

Offeror shall ensure and certify that its files are virus free.

The Offeror shall not embed sound or video (e.g., MPEG) files within the proposal submission.

The SPN-50 estimated funding profile by fiscal year is provided in the table below and is for informational purposes only. The offeror is not required to propose in accordance with the funding profile.

2.0 PROPOSAL FORMAT

1) Technical: Proposals must be formatted using a Times New Roman 12 point normal font (no reduction permitted), single-spaced with 1-inch margins all around and formatted for/printed on standard 8.5 x 11 inch paper.

All pages shall be numbered with section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. Tables must be formatted using a 10 point normal font (no reducton permitted). Drawings may be provided separately and may be any size but shall be folded to approximately 8.5 x

11 inch standard size and will count as 1 page. Graphs shall be presented in no smaller than a 10 point font and should contain a grid that allows values to be read directly from the graph to the same accuracy that a 10 x 10 to the

½ inch grid provides. Graphic resolution shall be consistent with the purpose of the data presented. Each Volume or Book shall be provided separately in a 3-ring binder. The binders shall be of an appropriate thickness for the number of pages it contains.

The Offeror will provide one complete copy of the proposal to the PCO as electronic files fully compatible with

Microsoft Office 2010 and/or Adobe Acrobat Reader 11.0.10 on a CD-ROM. The Offeror will ensure that the Price

Volume is provided on a separate CD-ROM. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy will take precedence. Instructions for the format and content of the Cost/Price

Volume are contained in Part B – Specific Instructions, paragraph 2.0 (Volume 2 – Price Proposal).

3.0 PROPOSAL CONTENT AND VOLUMES

General: The Offeror must present its proposal information in a manner that facilitates a one for one comparison between the information presented and this Proposal Instruction. Proposal information must be structured such that the paragraph number/letter is identical to the Proposal Instructions paragraph number to which it is responding, although the Offeror may add lower tier sub paragraphs. Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. Submission of all volumes of the Original proposal to the address provided in Part A, Section 4.0 (Proposal Submission) will determine timeliness of receipt. Not-to-exceed (NTE) page counts for each volume are specified in the table below as follows (title and table of contents pages do not count towards page limit).

Volume Number Volume Title Suggested Page

Count

Copies Required

Vol 1 TECHNICAL - Schedule (IMS), Key System Performance

Requirements, Small Business

Strategy

100 Pages

(Supporting data, such as test data, operating curves, tables, plots, or substantiating data for the

Performance model is not included in the

100 page count)

1 Original/7 Copies

Vol 2 Cost/Price No limit 1 Original/2 Copies

Vol 3 Executive Summary 11 Pages 1 Original/2 Copies

Each volume must contain the following information:

Cover and title page

Title of proposal and proposal number as applicable

Offeror’s name, address and POC

RFP number

Proposal volume/book number

Copy number

Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements)

Use tabs and dividers

The Cross Reference Matrix (CRM), required for the Technical volume and as needed for other volumes, is provided below as guidance to help ensure that all requirements are addressed, are easily accessible to the evaluators, and to facilitate the Offeror’s completion of the CRM of its proposal. The Offeror’s CRM shall provide a single integrated matrix. The Offeror’s CRM shall cross-reference its proposal volumes and paragraphs to specific

RFP requirements, as well as other parts of the proposal that contain relevant information. The CRM shall be provided, as a minimum, in the Technical proposal volume and is not included in the NTE page count. The

Offeror’s CRM may be identical to the one provided or revised to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. Areas indicated with shaded gray do not require separate write-up and are for identification of section only.

CROSS REFERENCE MATRIX (CRM) for Technical Volume 1

Volume Sect L

Para

Title of Annex Government

SOW

SATR System

Spec

Sec M

Criteria

Government

Referenced

Attachments

Technical

(Volume 1)

1.1 Integrated Master

Schedule

5.2 N/A IIA Section J, Attachment 1

1.2 Key System

Performance

Requirements

N/A .2.1, .2.2.1.1, .2.2.1.2, .2.2.1.3, .2.3.1, .2.3.2, .2.4, .2.4.1, .2.4.2, .2.5.4., .2.5.5, .2.5.6,.2.5.7, .2.8.1, .2.9.2, .2.9.2.1, .2.9.2.2, .2.9.2.3 .7.2, .7.2.1, .7.2.2, .7.2.3, 7.3, .7.4, .7.4.1, .7.4.2, .8.2, .8.2.1, .8.2.2, .8.2.3, .8.2.4, .8.2.5, and

.8.2.6

IA, IIA Section J, Attachment 2

4.0 PROPOSAL SUBMISSION

Clearly mark all packages with the solicitation number. The submission date for all Volumes shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP.

4.1 Unclassified Data

Method of delivery, such as by hand, United States Postal Service or commercial carrier, shall be coordinated with the Procuring Contracting Office (PCO) and/or contract specialist listed below. Proposals shall be submitted using the address provided below. Initial and Final Proposals shall not be submitted by facsimile or electronically via email.

Contract Specialist

AIR 2.2.4.1.5 Mrs. Virginia Perry-Aldridge

(301) 342-9920 virginia.perry-aldri@navy.mil

Contracting Officer

AIR-2.2.1.2 Mr. William D. Gentry

(301) 757-7069 william.gentry@navy.mil mailto:Benjamin.Washburn@navy.mil

Naval Air Systems Command

(ATTN: Mr. William D. Gentry / Mrs. Virginia Perry-Aldridge)

Solicitation Number: N00019-15-R-0081

Building 460

Floor 1

Room 107

Patuxent River, MD 20670

5.0 PROPOSAL PACKAGING

The Offerors shall package the proposal volumes in cartons or equivalent packaging containers in the most efficient manner possible grouping like volumes to the maximum extent possible. Also each carton shall be single person portable. However, the Master Set, as described below, shall be packaged separately and marked as the Master Set.

Each box shall identify its contents by including a packing slip detailing the requirement, each volume number and title and copy number. Also, each box shall be stamped or marked “For Official Use Only” and “Source Selection

Information – See FAR-2.101 and 3.104.”

The Master Set shall include all original proposal volumes, all proposal volumes on CD-ROM, a completed and original signed Standard Form 33; acknowledgement of all solicitation amendments, if applicable; and

Representations, Certifications and Other Statements of Offerors (Section K of this RFP) and other applicable fill-ins.

6.0 TECHNICAL LIBRARY/DATA

(1) Technical Library

A Technical Library of information directly related to the requirements of this contract will be provided in a

Compact Disc media format with the RFP (or emailed directly), upon request.

To request electronic copies of the solicitation materials, contact:

Mr. William D. Gentry, AIR- 2.2.1.2

Phone: (301) 757-7069.

Email: William.Gentry@navy.mil

For any changes and additional information to the solicitation please go to website:

http://www.fbo.gov

PART B - SPECIFIC INSTRUCTIONS

1.0 VOLUME 1: TECHNICAL – Integrated Master Schedule (IMS), Key System Performance

Requirements

This volume consists of the proposed schedule for meeting the delivery dates and key system performance requirements. The Offeror shall not contain any reference to price aspects of the offer in this volume. The Offeror shall address the following in the proposal:

1.1 Integrated Master Schedule (IMS)

The Offeror shall provide an Integrated Master Schedule (IMS) that delineates the planned activities/events listed below, along with contractor established activities deemed necessary for management of the program. The schedule shall cover the activities necessary to execute the program requirements outlined in Statement of Work (SOW) paragraph 5.2 (Contract Line Item Numbers (CLINs) 0001-0004) and achieve the delivery dates specified in Section

F. The IMS shall be submitted electronically in Microsoft Project 2010 version and in a written copy in the technical volume. Any additional schedule information can be submitted within a schedule narrative provided in hardcopy and electronic format. The IMS shall be based on the following:

mailto:William.Gentry@navy.mil http://www.fbo.gov/

Notes: Provide the number of hours required for system and subsystem development (for both hardware and software) and verification hours. The Offeror shall use a calendar consistent with the company’s work schedule. A listing of company holidays, for each year of the proposed plan, shall also be included in the schedule narrative.

1.2 Key System Performance Requirements

Offerors are advised that they must present proof in their proposal (e.g. test data, modeled data where applicable, analysis, and any required supporting data) showing how it meets the Shipboard Air Traffic Radar (SATR) performance requirements for SATR in a relevant environment based on actual testing or modeled analysis and any required supporting data; otherwise, the Offeror’s proposal will be deemed unacceptable and not be evaluated any further.

1.2.1 The Offeror’s demonstrated performance in a shipboard environment shall be supported by applicable test results to meet the System Specification requirements in the following section: REQ.2.8.1

1.2.2 The Offeror’s predicted performance and known limitations for the AN/SPN-50(V)1SATR in the post CDR configuration shall be supported by applicable test results or with the results of modeling and simulation or other predictive analysis tools A description of the tools, their validation with test and appropriateness to the proposed system should also be provided. The performance presented shall be in accordance with the external environmental conditions presented in the specification. The Offeror shall provide sufficient detail including actual radar test data, calculated data and performance curves to conclusively substantiate the ability of their proposed system to meet the following System Specification requirements:

a. Service Volume: Capable of meeting the requirements as specified in the system specification, REQ.2.2.1.1

b. Service Volume: Capable of meeting the requirements as specified in the system specification, REQ.2.2.1.2

c. Service Volume: Capable of meeting the requirements as specified in the system specification, REQ.2.2.1.3

d. Constraints: Capable of meeting the requirements as specified in the system specification, REQ.2.9.2, REQ.2.9.2.1, REQ.2.9.2.2, and REQ.2.9.2.3

e. Range and Azimuth Resolution: Capable of meeting the requirements as specified in the system specification, REQ.2.4, REQ.2.4.1, and REQ.2.4.2

f. Azimuth Accuracy: Capable of meeting the requirements as specified in the system specification, REQ.2.3.2.

g. Update Rate: Capable of meeting the requirements as specified in the system specification, REQ.2.1.

h. Reliability: Capable of meeting the requirements as specified in the system specification, REQ.8.2, REQ.8.2.1, REQ.8.2.2, REQ.8.2.3, REQ.8.2.4, REQ.8.2.5, and REQ.8.2.6 - Analysis shall be submitted in a format readable by Raptor or Windchill

i. Dimensions: Capable of meeting the requirements as specified in the system specification, REQ.7.2, REQ.7.2.1, REQ.7.2.2, REQ.7.2.3, REQ.7.3, REQ.7.4, REQ.7.4.1, and REQ.7.4.2

j. Range Accuracy: Capable of meeting the requirements as specified in the system specification, REQ.2.3.1.

k. Target Detection: Capable of meeting the requirements as specified in the system specification, REQ.2.5.4.

l. Target Detection: Capable of meeting the requirements as specified in the system specification, REQ.2.5.5, REQ.2.5.6, REQ.2.5.7.

If the Offeror’s proposed system does not currently meet all of the performance specifications, they shall identify where deficiencies exist, conclusively demonstrate how they will achieve the specification and reflect the cost in the

Cost Volume.

1.3 Small Business Subcontracting Plan

Large Business Offerors shall provide one of the following types of small business subcontracting plans: a

Comprehensive Subcontracting Plan approved in accordance with DFARS 252.219-7004; a Master Small Business

Subcontracting Plan with subcontracting goals applicable to the SPN-50 effort covered by this solicitation; OR an

Individual Small Business Subcontracting Plan for the SPN-50 effort covered by this solicitation. If the offeror provides either a Master Small Business Subcontracting Plan with subcontracting goals applicable to the SPN-50 effort covered by this solicitation or an Individual Small Business Subcontracting Plan for the SPN-50 effort covered by this solicitation, this plan shall be prepared in accordance with the provisions of FAR 19.704 and

DFARS 219.704. Please see FAR 19.702(a)(1) “Statutory requirements", regarding failure of the apparent successful Offeror to submit an approved Comprehensive Subcontracting Plan, a Master Small Business

Subcontracting Plan with subcontracting goals applicable to the SPN-50 effort covered by this solicitation, OR an

Individual Small Business Subcontracting Plan for the SPN-50 effort covered by this solicitation. The successful

Offeror’s approved Subcontracting Plan will be incorporated into the contract.

1.4 Use of Government Furnished Equipment

Offerors requiring any GFE other than EDM # 1 and EDM # 2 in the Pre-CDR configuration as described at

5252.245-9500, “Government Property for the Performance of this Contract (NAVAIR) (MAY 2104)” on page 15 of this RFP will not be deemed technically acceptable.

2.0 VOLUME 2 – COST/PRICE PROPOSAL

2.1 General Information

The following is a list of the Section L Cost Attachments that the Offeror shall utilize to provide cost information as required for this Volume:

Section L, and (10) Cost Attachments, which includes the following:

Cost Attachment 1 (CA-1) Program Work Breakdown Structure (PWBS) and PWBS Dictionary

Cost Attachment 2 (CA-2) Cost Cross Reference Matrix (CRM)

Cost Attachment 3 (CA-3) N0019-15-R-0081, DD Form 2794 CSDR Contract Plan

Cost Attachment 4 (CA-4) N0019-15-R-0081, Resource Distribution Table (RDT)

Cost Attachment 5 (CA-5) Modified DD Form 1921 Example

Cost Attachment 6 (CA-6) Modified DD Form 1921-1 Example

Cost Attachment 7 (CA-7) Cost Substantiation

Cost Attachment 8 (CA-8) Software

Cost Attachment 9 (CA-9) Systems Engineering/Program Management

Cost Attachment 10 (CA-10) Skill Mix/Composite Direct Labor Rate

All costs shall be contained in RFP Section B, and the cost/price proposal. The Government is required to evaluate each proposal relative to the cost/price criteria submitted in response to Section M. Proper presentation and adequate supporting documentation will ensure the cost/price proposal is efficiently evaluated and all assumptions are understood. The burden of proof for cost credibility rests with the Offeror.

The information required in this cost instruction applies to both the Offeror and to any Principal subcontractors, as defined in paragraph one (1) of the General Proposal Instruction, and is required to meet the requirements of this solicitation. Due to the proprietary nature of company rates, rate information may be presented separately for each

Offeror and principal subcontractor. Each principal subcontractor that provides a separate cost/price volume shall follow the same format as described in this instruction.

In developing the cost proposal, the Offeror shall develop a CLIN 0003 Cost Work Breakdown Structure (CWBS) and CWBS Dictionary that aligns to the Government provided CLIN 0003 Program Work Breakdown Structure

(PWBS) contained in Cost Attachment 1. Tailoring of the CWBS is encouraged and allowed at levels below the

PWBS to reflect the Offeror's specific design.

Any adjustments shall be clearly described in the Ground Rules and Assumptions portion of the Offeror’s Summary of Estimating Methodology (see paragraph 2.3.1.2). Any adjustments must be cross-referenced to the Offeror’s

CLIN 0003 CWBS, SOW, and CLIN 0003. The estimate must be easily traceable from the lowest level at which the

Offeror’s estimate was substantiated to CLIN 0003.

The proposal provided by the Offeror shall follow the format provided in paragraph 2.3, Cost/Price Proposal

Instructions.

2.2 Cost/Price Proposal Guidelines

Cost information shall be submitted in Then Year dollars (TY$) based on the Government’s fiscal year (1 October through 30 September) with the escalation formula provided for each year. The Offeror shall also provide a summary level of the Cost/Price Proposal in Constant Fiscal Year 2016 (FY16$) by Fiscal Year and CWBS using escalation/de-escalation factors supported by their rates and factors used in their cost/price proposal. Please provide this summary based on a Level 2 CWBS plus Level 3 and 4 for elements within CLIN 0003 of the AN/SPN-50(V)1

Program.

The Offeror shall prepare and submit the cost proposal narrative substantiation and rationale in Microsoft Word

2010 format and any numerical data in a Microsoft Excel 2010 format on CD-ROM. Files received in a format other than requested are unacceptable. Portable Document Format (PDF) is not acceptable, except when provided in addition to Microsoft Word or Excel formats. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using "value only" cells. If external links are utilized, supply those referenced files. The cost proposal shall be unprotected and unlocked, with formulas intact to show mathematical operations. Ensure that the electronically submitted filenames are directly traceable to the hard copy submittals.

2.3 Cost/Price Proposal Instructions

The proposal provided by the Offeror shall follow the format below:

Section 1 – Engineering Manufacturing Design NRE Cost for CLIN 0003

1.1 – Programmatic Information

1.1.1 – Post CDR System Description

1.1.2 – Ground Rules and Assumptions

1.1.3 – CLIN 0003 CWBS and CWBS Dictionary

Cost Attachment 1, CLIN 0003 Program Work Breakdown Structure (PWBS) and PWBS

Dictionary

1.1.4 – EMD Cost and Software Data Reporting (CSDR) Plan

Cost Attachment 3, N0019-15-R-0081, DD Form 2794 CSDR Contract Plan

1.1.5 – Level of Effort (LOE) Work Years (WYs) by Year

Cost Attachment 9, Systems Engineering/Program Management

1.1.6 – Subcontracts, Interdivisional transfers

Cost Attachment 4, N0019-15-R-0081, Resource Distribution Table (RDT)

1.1.7 – Special Tooling and Special Test Equipment (ST/STE)

1.2 – Summary of Estimating Methodology

Cost Attachment 2, Cost Cross Reference Matrix

1.3 – Cost Summaries

1.3.1 –DD Form 1921

Cost Attachment 5, Modified DD Form 1921 Example

1.3.2 –DD Form 1921-1

Cost Attachment 6, Modified DD Form 1921-1 Example

Cost Attachment 13, Summary of Cost and Hours by WBS

1.4 – Detailed Estimating Methodology

1.4.1 – Labor

Cost Attachment 7, Cost Substantiation

1.4.2 – Software Form

Cost Attachment 8, Software

1.4.3 – Material

Cost Attachment 7, Cost Substantiation

1.4.4 – Other Direct Charges/Travel

Cost Attachment 7, Cost Substantiation

1.5 – Fee

Section 2 – Contractor Rates

2.1 – Indirect rates

2.2 – Direct rates

2.2.1 – Direct Labor Rate

2.2.2 – Skill Mix

Cost Attachment 10, Skill Mix/Composite Direct Labor Rates

2.3 – Cost to Sell Equations

2.4 – Escalation

Section 3 – Other Cost/Price Impacts

Section 4 – Model Contract

2.3.1 SPECIFIC INSTRUCTIONS FOR SECTION 1 ENGINEERING & MANUFACTURING NRE COST

(CLIN 0003)

The following instructions apply to Section 1 costs. Offeror is expected to follow the instructions in each section and number according to the outline provided in Section 2.3 above.

The Government assessment will address the sum of the resources required to realistically conduct the program proposed by the Offeror. Of primary importance to this process are the Offeror’s actual expenditures for tasks comparable to those found in the CWBS and CWBS Dictionary and historical data from analogous efforts. Where this is not provided/available, the Government may consider historical data from previously executed programs as is deemed necessary in order to conduct the evaluation.

In all cases, documentation is required for each Offeror’s CWBS element priced out for the SOW contained in the solicitation, which shall provide the basis of estimate for labor, material, and purchased components. If there is any information requested that does not apply to the Offeror's proposal (e.g., non-recurring, manufacturing) then indicate with the letters ‘N/A’ (Not Applicable) on any forms where a space is provided.

The following guidelines and sample formats/attachments are provided to assist the Offeror in preparing clear, concise, comprehensive, and traceable proposals.

The Offeror shall cost the CWBS and ensure that it is cross-referenced to the SOW and CLINs. All totals shall agree. Substantiation shall be provided at the lowest level for which the Offeror developed estimates.

Ensure consistency between the information/data in this Volume and that provided in the Technical

Volume.

Historical data from comparable or analogous systems/subsystems shall be used to substantiate the

Offeror's estimate where possible. When using historical cost data from comparable systems/subsystems, all assumptions affecting the Offeror's cost proposal are to be fully documented (e.g., escalation methodology, make or buy decisions, etc.). A summary with a programmatic and technical description of the historical system shall be provided along with the actual cost data for the historical system, a comparison to the proposed system, and any adjustments made to derive the proposed estimate. The following shall be considered:

1) Programmatic description related to the acquisition aspects of any system identified by the Offeror as comparable/analogous. This includes, for example, the years the item was procured, production rates, quantities procured by year and definition of system composition, sole source or competitive procurement, and the development time period.

2) Technical description including the performance and physical aspects of the system. This describes the system in terms of the number of parts, physical configuration, type of material, technology, and physical/performance parameters.

3) Actual cost data including the cost account, narrative description of the effort, and the actual cost data (material and person-hours). The cost data shall be provided in terms of total dollars actually spent by fiscal year and by unit cost.

4) When using historical data, the Offeror should describe why the system is comparable to the proposed program. This includes a functional and technical comparison explaining the differences as well as similarities between the historical and the proposed system. Also include an explanation of the relationship between the analogous element cost and the total program cost.

5) The Offeror shall provide the basis and document any adjustments applied to the historical data

(e.g., complexity factors and normalization methods), which reflect the characteristics of the proposed system. This includes an audit trail sufficient for the Government to reconstruct the proposed estimate and judge its credibility.

a. General statements such as “estimates were derived from engineering analysis or engineering judgments” are unacceptable. If a level of effort task is the basis for projecting labor hour requirements, the data substantiation shall include task duration, man-loading, number of times the task is repeated (if applicable), time-phased hours and associated costs, and the relationship between the historical system and the system under review. If a "new or improved" engineering or manufacturing process is the basis for projecting labor hour requirements, the Offeror shall provide a description of the improvements, the relationship to the previous process, a summary of how these improvements will be achieved, and the cost impact of these improvements. General statements about process improvements, management by Integrated Product Team, the application of Acquisition Reform and Lean Six-Sigma/Airspeed, etc., will not be sufficient without substantiating data. Specific savings in person-hours and material must be documented with regard to the content and practicality of these improvements. Adjustments made to the historical data to normalize for changes in the accounting system, business base, or inflation rate shall be substantiated.

2.3.1.1 – Programmatic Information

2.3.1.1.1. Modified System Description

Provide the following technical information for the proposed system modifications and each proposed source data of each historical system used for analogy or parametric estimation.

a. Hardware Overview – An identification of the major hardware components within the proposed system modification. Also identify each component by material composition, prime/principal subcontractor, and make versus buy status.

b. Software Overview – An identification of the Computer Software Configuration Items (CSCIs), tracing the requirements allocated to the system specification for each CSCI and its associated Computer Software

Component(s) (CSCs).

c. System Test and Evaluation Overview – identify the purpose and function of each test, its SOW reference, and the source - prime or subcontractor - of the test component.

2.3.1.1.2. CLIN 0003 CWBS and CWBS Dictionary

The CLIN 0003 CWBS and CWBS dictionary shall be developed in accordance with the WBS structure found in

MIL-STD-881C, Appendix B, current edition. The CWBS is required to align with the Government provided CLIN

0003 Program WBS (PWBS) structure in Cost Attachment 1. The Offeror shall expand the CWBS as necessary and develop the CWBS Dictionary for its proposal to a minimum of the fourth level for all CWBS elements.

For Section 1 EMD Costs, the CWBS must agree with the EMD CSDR Contract Plan developed in Section

2.3.1.1.3, EMD Cost and Software Data Reporting (CSDR) Plan. Any expansions, element name updates, or element order changes to the CWBS elements from the developed contract CSDR plan shall be reflected in the

CWBS and CWBS Dictionary.

2.3.1.1.3. EMD Cost and Software Data Reporting (CSDR) Plan

The Offeror shall provide an EMD CSDR Contract Plan using the sample provided in Cost Attachment 3. The

Offeror shall mark any WBS elements that are not applicable “N/A”, and update the Software Resources Data

Reporting (SRDR) column to have an “X” in all WBS elements that have software. Additional instructions for updating CSDR Contact Plans may be found on the Defense Cost and Resource Center (DCARC) website http://dcarc.cape.osd.mil/.

2.3.1.1.4. Level of Effort (LOE) Work Years (WYs) by Year

Provide all Contractor and subcontractor WYs for Systems Engineering/Program Management (SEPM) in Cost

Attachment 9, SE/PM WY LOE Staffing Matrix.

2.3.1.1.5. Subcontracts, Interdivisional transfers

In order to show the prime Contractor’s analysis of subcontractors’ pricing, provide a list of anticipated subcontracts and interdivisional transfers. Identify the following by CLIN and by Government Fiscal Year (GFY).

a. The supplier

b. Description of the item, services, or quantity of hours

c. Type of contract

d. Subcontractor’s quoted and prime Contractor’s adjusted subcontract values. Explain any differences between the subcontractor's quoted cost and the subcontract cost proposed by the prime.

2.3.1.1.6. Special Tooling and Special Test Equipment (ST/STE) Modifications

Provide a list of all ST/STE modifications needed to fulfill the requirements and the proposed cost for each modification of ST/STE. Show the ST/STE modification costs including any set-up for the Offeror and principal subcontractors as applicable.

2.3.1.2 – Summary of the Estimating Methodology

In this section, the Offeror shall provide a detailed description of the process used to develop the cost/price proposal.

This will include, at the minimum, a summary of the approach used to estimate labor hours and a description of the process used to obtain vendor quotes for purchased equipment and/or material. It will also include a traceability matrix or table that shows the link between the labor hours and material costs included in the cost summaries and those in the detailed labor and material sections. Similar information shall be provided to show traceability between the prime and subcontractor sections.

To support the proposal, the Offeror shall provide discussion of the estimating methodology to address why the

Offeror’s proposed cost is realistic, including such factors as commonality with other programs, commercial sources, advantages of quantity buys, etc.

Provide a CWBS/CLIN/SOW Cross Reference Matrix. The Offeror shall populate its CWBS and ensure that it is cross-referenced to the CLIN, and Statement of Work (SOW). All information found in supporting documentation shall agree. The Cost Cross Reference Matrix (CRM) is shown here, and an electronic version is provided in Cost

Attachment 2, Cost CRM.

CLINs 0001 and 0002 are not included in the Cost Cross Reference Matrix, as these CLINs are firm fixed price, and will be evaluated for reasonableness only. Therefore, only the total price of CLINs 0001 and 0002 need to be http://dcarc.cape.osd.mil/ reported , including any associated spares, and do not need to be reported against the WBS structure enclosed below.

The Cost Cross Reference Matrix is intended to capture the costs associated with CLIN 0003 only.

Work Breakdown Structure CLIN SOW Paragraph

LEVEL 1 2 3 4

1.0 AN/SPN-50(V)1 Shipboard Air Traffic Radar

1.1 Prime Mission Product (PMP) 0003 4.2, 8.0, 8.1, 8.2, 8.3

1.1.1 PMP Above Deck 0003 4.2

1.1.1.1 Antenna Group 0003 4.2

1.1.1.2 Antenna 0003 4.2

1.1.1.3 Receiver 0003 4.2

1.1.1.4 Pedestal 0003 4.2

1.1.2 PMP Below Deck 0003 4.2

1.1.2.1 Radar Control Group 0003 4.2

1.1.2.2 Receiver 0003 4.2

1.1.2.3 Transmitter 0003 4.2

1.1.3 PMP Local Maintenance Set Control (LMSC) 0003 4.2

1.1.4 PMP Remote Radar Set Control (RRSC) 0003 4.2

1.1.5 PMP External Connections 0003 4.2

1.1.5.1 NAVSSI 0003 4.2

1.1.5.2 ECM Blanker System (AN/SLA-10) 0003 4.2

1.1.5.3 RADDS (AN/SPQ-12) 0003 4.2

1.1.5.4 Identify Friend or Foe (IFF) 0003 4.2

1.1.5.5 Display System (TPX-42) 0003 4.2

1.1.5.6 CTCC/AATCC 0003 4.2

1.1.6 PMP Miscellaneous Components...n 0003 4.2

1.1.6.1 Component 1 0003 4.2

1.1.6.2 Component 2 0003 4.2

1.1.6.3 Component 3 0003 4.2

1.1.6.4 Component 4…n 0003 4.2

1.1.7 PMP Software Release…n 0003 8.0, 8.1, 8.2, 8.3

1.1.7.1 SW Release 1 0003 8.0, 8.1, 8.2, 8.3

1.1.7.2 SW Release 2 0003 8.0, 8.1, 8.2, 8.3

1.1.7.3 SW Release 3 0003 8.0, 8.1, 8.2, 8.3

1.1.7.4 SW Release 4…n 0003 8.0, 8.1, 8.2, 8.3

1.1.8 PMP Integration, Assembly, Test and Checkout 0003 4.2

1.2 Platform Integration, Assembly, Test and Checkout 0003 4.2

1.2.1 Installation 0003 4.2

1.2.2 Drawings 0003 4.2

1.2.3 Test & Checkout 0003 4.2

1.3 Systems Engineering 0003 7.0, 7.1, 7.2, 7.3, 7.5, 7.7, 10, 10.1, 10.7, 11.1, 11.2, 13, 13.1, 13.1.5, 14.4, 14.14,

1.4 Program Management 0003 5.0, 5.1, 5.2, 5.3, 5.4, 5.5, 5.6, 5.7, 5.8, 5.9, 5.10, 5.10.1, 5.11, 5.12, 5.13, 5.13.1, 5.14, 11, 12, 12.1, 12.2, 13.1.6, 14, 14.5, 14.12, 17, 17.1, 17.2, 17.3, 17.4, 17.5

1.5 System, Test, and Evaluation 0003 10.11.1, 10.11.2, 16.1, 16.2, 16.3, 16.4, 16.5, 16.6

1.5.1 Development Test and Evaluation 0003 10.11, 10.11.1, 10.11.2

1.5.2 Operational Test and Evaluation N/A

1.5.3 Mock-ups / System Integration Labs (SILs) N/A

1.5.4 Test and Evaluation Support 0003 16, 16.1, 16.2, 16.3, 16.4, 16.5, 16.6

1.5.5 Test Facilities N/A

1.6 Training 0003 13.2

1.6.1 N/A N/A N/A

1.6.2 Services 0003 13.2.1, 13.2.2, 13.2.3, 13.2.4, 13.2.5

1.6.3 Facilities N/A

1.7 Data 0003 6.0

1.7.1 Technical Publications 0003 14.10

1.7.2 Engineering Data 0003 6.2, 6.3, 6.4, 6.8, 10.2, 10.3, 10.6, 10.8, 10.9, 10.10, 11.3, 11.4, 13.1.1, 13.1.2, 13.1.3, 13.1.4, 14.1, 14.1.1, 14.2

1.7.3 Management Data 0003 6.8, 6.9, 12.2.1, 12.2.2, 14.11, 14.2, 14.13, 18

1.7.4 Support Data 0003 6.5, 6.6, 6.7, 9.0, 9.1, 9.2, 9.3, 10.5, 10.11.3, 10.11.4, 14.3, 14.6, 14.7, 14.8, 15, 15.1, 15.2

1.7.5 Data Depository 0003 6.1, 14.9, 14.9.1

1.8 Peculiar Support Equipment 0003 14.11

1.8.1 Test and Measurement Equipment 0003 14.11

1.8.2 Support and Handling Equipment 0003 14.11

1.9 Common Support Equipment 0003 14.11

1.9.1 Test and Measurement Equipment 0003 14.11

1.9.2 Support and Handling Equipment 0003 14.11

1.10 Operational/Site Activation N/A

1.10.1 System Assembly, Installation and Checkout on Site N/A

1.10.2 Contractor Technical Support N/A

1.10.3 Site Construction N/A

1.10.4 Site/Ship Conversion N/A

1.10.5 Sustainment/Interim Contractor Support N/A

1.11 Industrial Facilities N/A

1.11.1 Construction/Conversion/Expansion N/A

1.11.2 Equipment Acquisition or Modernization N/A

1.11.3 Maintenance (Industrial Facilities) N/A

1.12 Initial Spares and Repair Parts 0003 4.2, 15.3, 15.4

1.12.1 INCO-I N/A

1.12.2 INCO-R N/A

1.12.3 Repair of Repairables 0003 14.9.2, 15.3, 15.4

1.12.4 Ship Spares 0003 4.2

1.12.5 Depot Spares N/A

2.3.1.3 – Cost Summaries

For guidance on populating DD Form 1921 and 1921-1, refer to DoDM 5000.04-M-1, Cost & Software Data

Reporting (CSDR) Manual dated November 4, 2011. The CSDR Manual may be found on the DCARC website http://dcarc.cape.osd.mil/.

2.3.1.3.1 – Cost Summary Reports

The Offeror shall provide a DD Form 1921, Cost Summary Report, or comparable format to a minimum of Level 2 for the proposed CWBS elements for the EMD contract plus to a minimum of Level 4 for elements under Prime

Mission Product. An example of a modified DD Form 1921 has been provided in Cost Attachment 5. The sum of the CWBS elements shall correspond to the Offeror's total proposed cost with subtotals provided at each higher level of the CWBS. Information required in this section includes total program costs, separately identified as nonrecurring and recurring costs, for both the prime and principal sub-contractors. The Offeror’s General and

Admi…