N00039-17-R-0005-02.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 this Amendment is to revise the Page Limit Table under Section 2.1.2 and language in Section M under CLIN 1001 (pg 24 denoted in BOLD).

Additionally, the Amendment deletes Section L Factor 3 Past Performance Section 3 language starting w ith "Large Business Offerors." For both large and small businesses, the Government w ill evaluate small business utilization and/or history of meeting goals as one aspect of past performance (among others) listed primarily through CPARS small business utilization category ratings as detailed in the evaluation criteria.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 27

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

16C. DATE SIGNED

BY 13-Nov-2017

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 N00039-17-R-0005

X 9B. DATED (SEE ITEM 11)

21-Sep-2017

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

13-Nov-2017

CODE

COMMANDER, SPACE AND NAVAL WARFARE

SYSTEMS COMMAND

02 CONTRACTS

4301 PACIFIC HIGHWAY

SAN DIEGO CA 92110-3127

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00039-17-R-0005

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

Submission of Proposals:

This solicitation is for development of an Optical Communications System (OCOMMS), including options for the demonstration support and a technical data package.

1.1 Questions: Offerors may request clarifications or submit questions concerning any aspect of this solicitation. All questions shall be submitted in writing by electronic means to Patricia Pacheco, at patricia.pacheco@navy.mil with a copy to the Contracting Officer at kate.mccoy@navy.mil not later than 15 calendar days after issuance of this solicitation. Offerors are advised that the Government will make available to the public any questions or comments and the Government’s associated responses; therefore offerors shall not provide questions or comments of a proprietary nature. The Government will use its best efforts to respond to offeror questions and comments; however, responses are not guaranteed.

1.2 Receipt of Offers: Proposals are due in 10:00AM PST on 15 Nov 2017.

1.3 Validity of Proposals: Proposals submitted in response to this solicitation shall be valid for 270 days from the solicitation closing date.

1.4 Certified Cost and Pricing Data: The offeror is not required to submit Certified Cost and Pricing Data unless the agency determines that DFAR 215.371 applies.

2.0 PROPOSAL REQUIREMENTS

2.1 Proposal Organization and Format

2.1.1 Proposal Organization

Proposals submitted in response to this solicitation shall be UNCLASSIFIED and shall consist of three (3) separately bound volumes identified as follows:

Volume 1: Contract

Volume 2: Technical Proposal

Volume 3: Cost/Price Proposal

2.1.2 Proposal Format

Offeror’s proposal Volumes shall include the following:

Item Page Limit

VOLUME I: CONTRACT

No page limit Section A: Cover Letter

Section B: Signed SF33 with completed Sections B through K mailto:Katie.melkun@navy.mil mailto:kate.mccoy@navy.mil

Section C: Response to Provision 252.227-7017, Identification and assertion of use, release, or disclosure restrictions

Section D: Systems and Compliances

Section E: Organizational Conflict of Interest:

(If Applicable)

Section F: Security Clearances

Section G: Small Business Subcontracting Plan

Section H: Financial Responsibility

No page limit Section I: Foreign Owned Subcontractors

VOLUME II: TECHNICAL

Section A: Technical Approach/Corporate

Experience (non-cost Factor 1 with subfactors 1a and

1b)

20 pages total

Subfactor 1a 15 pages total (Compliance

Matrix exempt)

Subfactor 1b 5 pages total

Section B: Integrated Master Schedule (IMS)(non-cost Factor 2)

2 pages total (for narrative regarding risks)

IMS exempt

Section C: Relevant Past Performance (non-cost

Factor 3)

3 pages total per reference, including the 2 page Relevant Experience Form (CPARs and

Past Performance Questionnaires (PPQs) if provided exempt)

Section D: Data Rights (non-cost Factor 4) 5 pages total

Data Rights Matrix, copies of Commercial

Licenses, and Specially Negotiated License

Right Agreements (SNLRAs) exempt

Section E: Small Business (non cost Factor 5) 2 pages total

VOLUME III: COST No page limit

Section A: Cost

Note: Failure to submit complete information in the manner above may be considered a “no response” and may result in the exclusion of the proposal from further consideration.

2.1.3 Proposal Content

An offeror’s proposal is presumed to represent the Offeror’s best efforts to respond to the solicitation. Proposals submitted for consideration for award must address the full scope of the solicitation. Proposals which address only part or portions of the solicitation will be considered unacceptable. Non-conformance may cause rejection of, or the down grading of, the proposal. Proposals should be clear, concise and complete. Organization, clarity, accuracy of information, relevance, and completeness are of prime importance.

Proposals shall correlate directly and sequentially with the following specific proposal preparation instructions.

Proposals shall be complete and self-sufficient, relate exactly to what is requested and proposed, and strictly adhere to the requirements of this solicitation. Use of documentation by reference, and not incorporated into the proposal, will not be allowed. Where cross-referencing is used, the volume, attachment, exhibit and paragraph numbers, as appropriate, shall be referenced.

Format: A page is defined as a sheet of paper that includes information. When information is contained on both sides of a single sheet of paper it will be counted as two pages and be numbered accordingly. The proposal shall be on 8-1/2" X 11" white bond paper with single-spaced typed lines, including figures, glossaries, table of contents and cover sheets. Type size shall be Times New Roman and no smaller than 12 point in the text, spreadsheets, drawings, figures, and tables. Foldouts may be used, but shall be no larger than 11” by 17”, shall be printed on one side only, and shall count as two pages. Standard margins shall be a minimum of one inch, excluding header and footer. The volumes shall contain a glossary of abbreviations and acronyms used and an explanation of each. No pen and ink changes are allowed.

Other Information: Information submitted in excess of the page limits established above will not be read or evaluated. Page limits do not include cover sheets, tables of contents, Subfactor 1a compliance matrix, Factor 2

IMS itself, CPARS and PPQs, Data Rights Matrix, Commercial Licenses, SNLRAs, lists of figures, lists of drawings, glossaries, tabs, dividers, or blank pages. All proposal material must be contained within the page limit(s) identified for each volume, unless otherwise specified. Partial pages count as a full page. All pages within a page limited volume shall be consecutively numbered, starting at page one, and shall not exceed the page limitation. Each page shall contain a footer that includes, as a minimum, the Offeror’s name, RFP number, volume number, section, page number and, if applicable, restrictive legend (see FAR 52.215-1(e)(2)). For example, Page 19 of Volume I, Section 3 would be numbered I-3-19. Do not include price information in any volume other than the Contract or

Cost/Price volumes.

Data Submission: The contractor shall submit copies of the proposal in three (3) different methods: 1) electronic proposal submittal via the SPAWAR E-Commerce Central website; 2) CD ROM electronic proposal copies and 3) paper proposals. The electronic submission governs for the purpose of the submission, modification and withdrawal of proposals.

Paper Proposal Format Requirements:

Binding and Labeling: Each volume of the proposal shall be separately bound in a 3-ring binder. A cover sheet shall be affixed to each volume, clearly marked as to the volume number, the copy number, the RFP identification and the Offeror's name. The volume and copy numbers shall appear on the spine of the volume binder to permit rapid accounting when the volume is placed in a vertical position in a storage cabinet.

Electronic Proposal Format Requirements

Each electronic proposal, to include submission to SPAWAR E-Commerce and the CD-ROM copies, shall include electronic copies of each Volume using Microsoft Office 2010 or compatible software suite including: Microsoft

Word 2010 for all files in original searchable text format; Microsoft Excel 2010 for all spreadsheets files [all excel files shall be operable versus value only spreadsheets (i.e. formulas shall be included in all applicable cells)]; and

Microsoft Project 2010 files shall be used for all schedules. All files shall use file formats compatible with and follow Windows / Office 2010 naming conventions. All signed documents shall be submitted as Adobe Acrobat

.pdf files (ex: signed SF33 with Sections B though K, Cover Letter, subcontractor agreements, etc.). Any graphics software compatible with Microsoft Office 2010 may be used to insert graphics within the Offeror’s proposal.

Tables, figures, and graphics that are inserted in Word documents or other Office 2010 compatible files must be legible. Embedded files that cause the proposal to exceed the page count limitations will not be accepted. No files shall be password protected. The Offeror shall not prepare any portion of its proposal using sound, animation, or video files.

Submission of Electronic Proposals via the SPAWAR E-Commerce Central Website

a) Offerors shall submit their proposals electronically to SPAWAR under the instructions contained in this provision. Electronic copies shall be submitted via the SPAWAR E-Commerce Central (SPAWAR E-CC).

Offerors submitting electronic proposals (e-Proposals) shall register in the SPAWAR E-CC and select their own password in order to submit a proposal. Offerors are required to read the “Submitting a Proposal?”

web page found in the SPAWAR E-CC. For information about “e-Proposal” submission, please visit the

SPAWAR E-CC. The URL for the SPAWAR E-Commerce Central is:

https://e-commerce.sscno.nmci.navy.mil

b) Each electronic file shall also be clearly marked to show the proposal volume number, solicitation number and offeror’s name. E-Proposal files shall not contain classified data. The offeror’s e-proposal shall be in accordance with the requirements set forth below:

(1) Adobe Acrobat version 4.01 or greater shall be used to create the “PDF” files.

(2) The proposal submission files may be compressed (zipped) into one, ZIP file entitled

“PROPOSAL.ZIP” using WinZip version 6.3 or greater.

(3) Cost or Pricing Type Data: All information relating to cost and pricing type data shall be included only in the section of the proposal designated by the Contracting Officer as the Cost Proposal. Under no circumstances shall cost and pricing type data be included elsewhere in the proposal. Paragraph cross-referencing between Cost Proposal paragraphs and technical/management proposal paragraphs is requested to provide clarity.

c) Bids and proposals submitted electronically will be considered “late” unless the bidder or offeror completes the entire transmission of the bid or proposal prior to the due date and time for receipt of bids or proposals.

This paragraph (d) supplements the submission, modification and withdrawal of bids and proposals coverage in the FAR 52.212-1 “Instructions to Offerors--Commercial Items”, FAR 52.214-7 “Late

Submissions, Modifications, and Withdrawals of Bids”, FAR 52.214-23 “Late Submissions, Modifications, Revisions, and Withdrawals of Technical Proposals under Two-Step Sealed Bidding”, or the FAR 52.215-1

“Instructions to Offerors--Competitive Acquisition” provision contained in the solicitation.

Submission of CD ROM Electronic Proposal Copies and Paper Proposal Copies

The Offeror shall provide two (2) copies of each electronic proposal Volume on separate CD-ROMs. Offerors shall also submit an original signed paper copy of their proposal, and five (5) additional paper copies of the technical volume and two (2) additional copies of the cost/contracts volumes of the proposal as specified below to the following address:

CD-ROM Copy Submittal Address:

Space and Naval Warfare Systems Command (SPAWAR)

2.0 Contracts Directorate

Attn: Kate McCoy, Code 2.1B7

4301 Pacific Highway, Building OT-4, Room 1038

San Diego, CA 92110-3127

(A) VOLUME I – CONTRACT. The contract volume shall be organized as follows:

The required content of each contract volume section is described below. The completion and submission to the

Government of the items in Volume I will constitute the offer. The Government’s acceptance of the offer will create a binding contract between the Government and the Offeror. The Offeror’s failure or refusal to assent to any of the terms and conditions of this RFP or its imposition of additional conditions or any material omission in its offer may constitute a deficiency which may make the offer unacceptable to the Government.

(i) Section A: Cover Letter

The Offeror’s proposal shall include a cover letter on the Offeror’s letterhead stationary and signed by an executive of the company who possesses authority to contractually bind the Offeror. Cover letter shall acknowledge receipt of all amendments (if any are issued) to the RFP. The submittal letter shall identify all enclosures being transmitted as part of the response to the RFP. The letter shall reference the RFP number and acknowledge that it transmits an offer in response to the RFP. It shall state: (1) Commercial and Government

Entity (CAGE) number, (2) DUNs Number, (3) address(es) of the location(s) at which the Offeror intends to perform the proposed effort, (4) state the name, address and telephone number of the cognizant DCAA audit office, (5) the name, address and telephone number of the cognizant DCMA office, and (6) a statement that the https://e-commerce.sscno.nmci.navy.mil/ proposal is valid for 270 days after the RFP closing date. The above listed information (items 1-6) shall also be provided for all proposed subcontractors.

(ii) Section B: Signed SF33 with completed Sections B through K

The Offeror’s proposal shall provide a completed RFP to include completed and signed SF33 acknowledging all amendments and completed Sections B through K. The Offeror’s proposal shall include any exceptions to the provisions of the solicitation. The Offeror shall clearly state the exceptions and provide references to the applicable RFP page, paragraph or exhibit line item number. The Offeror shall provide a full explanation for all exceptions taken to the solicitation. Any material exceptions to the RFP may render the proposal unacceptable and ineligible for award on initial proposals. If the Offeror takes no exceptions to the provisions of the solicitation, the Offeror shall state “No exceptions.”

(iii) Section C: Response to Provision 252.227-7017

The Offeror shall submit intellectual property rights information pertaining to technical data or computer software to be delivered under a contract resulting from this solicitation in accordance with DFARS 252.227-

7017.

(iv) Section D: Systems and Compliances

The Offeror shall provide documentation demonstrating that the Government has determined that the Offeror currently has an adequate Accounting System, Estimating System, Purchasing System and Disclosure

Statement. Cover letters shall include the report number and date of the cognizant DCAA office’s determination stating that the prime contractor’s and subcontractor’s accounting systems are adequate for the accumulation, reporting, and billing of costs under a cost reimbursement contract (attach a copy of the report).

In the event that a subcontractor does not have an adequate accounting system, the prime contractor shall administer FAR compliant contracts (T&M or FFP) with their subcontractor and are responsible for determining the responsibility of their prospective subcontractors per FAR 9.104.

(v) Section E: Organizational Conflict of Interest (OCI) Mitigation Plan(s).

The Offeror’s attention is directed to FAR Subpart 9.5 relating to organizational conflicts of interest. It is the

Government’s intent to avoid, neutralize, or mitigate potential conflicts as early in the acquisition process as possible. The Offeror shall submit draft versions of any required OCI Mitigation Plans, consistent with the guidance contained in FAR Subpart 9.5.

(vi) Section F: Security Clearances.

Offerors shall also document that all facilities and personnel proposed to perform this contract possess at a minimum the security clearance levels required by the RFP (DD Form 254).

(vii) Section G: Small Business Subcontracting Plan.

Offerors, unless otherwise exempt, due to being small business concern or a company performing outside of any

State, territory, or possession of the United States, the District of Columbia, and the Commonwealth of Puerto

Rico, shall, in accordance with FAR 19.7 and FAR 52.219-9, submit a Small Business Subcontracting Plan, as part of Volume I. Failure to submit and negotiate a subcontracting plan acceptable to the Contracting Officer shall make the offer ineligible for award of a contract.

If the Offeror is a participant in the Department of Defense (DoD) Comprehensive Subcontracting Test Program specified in DFARS 219.7, the Offeror shall provide a copy of the approved comprehensive plan and describe how small business participation on this contract will contribute to its overall Comprehensive Subcontracting

Plan goals. The description must provide the extent of small business participation for this procurement with percentage and dollar amounts for specific small business categories.

Plans shall be in compliance with the Subcontracting Goals stated in Section L, Factor 5 of the solicitation.

(viii) Section H: Financial Responsibility

To aid in the determination of contractor responsibility, the following information is required:

(a) Information regarding the general financial condition of your firm and specific plans for financing the proposed contract, including the latest available financial statements. If you are currently being audited, or have been audited by the Defense Contract Audit Agency (DCAA), provide the address, current telephone number, and current point of contact for the cognizant DCAA and the cognizant Defense Contract Management Area Office (DCMAO). Also include the latest approval date of your Disclosure Statement (not applicable to Small Businesses) and most recent audit status, i.e., when was the last one performed, what were the findings, etc.

(b) A listing of previous and/or ongoing experience in related areas. Include the contracting activity, program or item produced, contract number, current point of contact, current telephone number, duration of contract, type of contract and total dollar amount of contract. Please ensure information provided is current and up-to-date. If the Offeror believes that the information provided under “Past Performance Information – FACTOR 4” adequately addresses the requirements of this provision, please so state here. Repetition of the same information is not necessary.

(c) A summary of your:

(1) accounting procedures and controls.

(2) organization.

(3) production control procedures.

(4) property control system

(5) quality assurance programs

(6) equipment and facilities relative to this effort.

(d) If any subcontracting, provide the following information:

(e) Methodology for the selection of proposed subcontractors, if any, and the benefit they would bring to the arrangement

(ix) Section I: Foreign Owned Subcontractors. The proposed Offeror shall identify any and all potential foreign-owned subcontractors they intend to team with for the procurement in the following format:

Name of Subcontractor:

Country of Origin:

Date of executed Technical

Assistance Agreement (TAA):

The Offeror shall provide a copy of the executed TAA within the Contracts Volume. In the event that a TAA is not in place at the time of proposal submission, the Offeror shall provide a copy of a draft TAA for Government review.

The Offeror shall ensure that the TAA will be in place prior to the award of the contract. The Offeror shall ensure all applicable subcontractor flow down clauses are complied with by the all subcontractors, including foreign-owned.

2.2 VOLUME II - TECHNICAL PROPOSAL. The technical proposal shall be organized as follows:

2.2.1 TECHNICAL PROPOSAL CONTENT.

The technical proposal shall cover the Offeror’s understanding of the work and the Offeror’s method(s) to attain contract objectives. The technical proposal shall enable technical personnel to make a thorough evaluation and a determination as to whether the proposal will satisfy the requirements of the Government. The technical proposal shall be specific, detailed, complete, and fully demonstrate that the prospective Offeror has a thorough understanding of the Government’s requirements. The technical proposal shall also address technical risks, the achievement of the specification requirements and the approach to execute the work required by the RFP. Data previously submitted will not be considered; therefore such data shall not be incorporated in the technical proposal by reference. No cost or price information shall be included in the technical proposal. Statements that the prospective Offeror understands, can or will comply with all specifications, statements paraphrasing the specifications or parts thereof, and phrases such as “standard procedures will be employed” or “well known techniques will be used,” etc., will be considered insufficient. Offerors shall provide separate responses to each technical evaluation factor within the identified page limitations. Offerors shall not exceed the page limitation by cross referencing other sections of their proposals.

Offerors shall provide the following information to support the Government’s evaluation of the Offeror’s technical proposal.

The technical evaluation factors are:

Factor 1 – Technical Approach/Corporate Experience

Subfactor 1a Technical Approach

Subfactor 1b Corporate Experience

Factor 2 –Integrated Master Schedule (IMS)

Factor 3 – Relevant Past Performance

Factor 4 – Data Rights

Factor 5 – Small Business Utilization

Cost/price

The proposal shall address the following technical evaluation factors:

Technical Approach/Corporate Experience (Factor 1)

Technical Approach (Subfactor 1a)

The Offeror shall provide a clear description of how the proposed design and development approach meets the requirements of the solicitation’s Performance Specification SPAWAR-S-OCOMMS001 and Statement of Work

(SOW) in the areas detailed below:

Airborne System Design and Development

The Offeror shall describe how the proposed design/development approach meets the requirement to operate in an airborne platform environment while meeting the search, acquisition, and optical tracking requirements in the

OCOMMS Performance Specification (SPAWAR-S-OCOMMS001 Section 3.2.1, 3.3.1, 3.3.2.4, 3.4.1) and minimizing the Size, Weight, Power and Cooling. Additionally, the offeror shall include an assessment of the

Technology and Software Readiness Levels (TRL/SRL) of the Pointing System and Tracking System, and technical risk and mitigation approaches pertaining to the airborne design and development.

Optical Transmitter and Receiver Design and Development

The Offeror shall describe how the proposed design/development approach meets the transmitter and receiver optical performance requirements over the full range of airborne engagements (altitude, elevation angles, and spot sizes) in the OCOMMS Performance Specification (SPAWAR-S-OCOMMS001 Section 3.3.2). Additionally, the

Offeror shall include an assessment of the TRL/SRL of the EO Imaging System, Receiver System, Laser subsystem, and Transmit Optical Subsystem, and technical risk and mitigation approaches pertaining to the optical transmitter and receiver design and development.

Test and Evaluation

The Offeror shall describe their approach and capability to conduct all testing of the OCOMMS Demonstration

System in accordance with SOW Section 3.1.11 and OCOMMS Performance Specification Section 4. The Offeror shall identify the specific facilities, whether in-house or subcontracted, and equipment that will be used to perform all testing.

Compliance Matrix

The Offeror shall complete a compliance traceability matrix (attachment 6) indicating whether the proposed design meets performance specifications per requirement as identified in the OCOMMS Performance Specification

(SPAWAR-S-OCOMMS001) Section 6, Table 2. For any requirement not met, the Offeror shall provide their expected performance and an explanation for the non-compliance. Additionally, the Offeror shall address on an individual and cumulative basis, if applicable, non-compliance impacts to the overall system design, performance, Airborne System size, weight and power (SWAP), and/or risk. The Compliance traceability

Matrix is exempt from the page count.

Corporate Experience (Subfactor 1b)

The Offeror shall describe the corporate experience of its team, including the prime and any subcontractors, in the below areas (a-c), and how the prime will organize the team for this effort. As part of this description, the Offeror shall identify which subcontractor is performing what portion of the effort with cross-reference to the applicable

OCOMMS Performance Specification sections. Such information shall correlate with each proposed subcontractor and its portion of work as proposed. For example, if the prime proposes subcontractor A to provide the Laser subsystem, the Offeror should provide relevant experience of subcontractor A developing similar systems. The

Offeror shall provide specific examples of prior experience and capability from the prime and/or appropriate team members, including contract numbers for U.S. Federal Government customers. Simply restating excerpts from the

Performance Specification or affirmative statements of having performed certain tasks without support or details will not be sufficient.

a) Development of optical systems, electronic systems, and components capable of operating in an outdoor environment as described in OCOMMS Performance Specification (SPAWAR-S-OCOMMS001) Sections

3.4 and 3.5, including environments experienced on rotary wing and fixed wing aircraft.

b) Development of pointing and tracking and stabilized systems capable of operating on a rotary wing and fixed wing aircraft as described in OCOMMS Performance Specification (SPAWAR-S-OCOMMS001)

Section 3.3.1.

c) Development of Optical Communications Payload systems or subsystems, including compact pulsed lasers operating in the 450 – 550 nanometer (nm) region, large aperture narrow bandwidth and wide field of view optical filters, and sensitive large aperture optical detectors as described in OCOMMS Performance

Specification (SPAWAR-S-OCOMMS001) Section 3.3.2.

Integrated Master Schedule (IMS) (Factor 2)

The Offeror shall submit a draft IMS that identifies major program milestones, tasks, task interrelationships and dependencies, and task durations to meet requirements, including cross-references to applicable SOW sections.

The IMS shall include no schedule constraint dates and shall be developed, wherever possible, in a finish to start relationship. The critical path shall be indicated in the Gantt Chart based upon the most likely duration. As a general rule, level of effort task activities that do not directly affect the critical path need only be presented at the summary task level

The IMS shall contain all the task activities required to furnish and deliver the services and supplies necessary to accomplish the program, satisfy the entrance and exit criteria for each program milestone, and correlate with the

WBS and WBS dictionary provided as Attachments L-1 and L-2. The IMS shall include task activities down to a

WBS level sufficient to provide insight into the proposed program with sufficient detail to explain risk mitigation efforts. The duration(s) proposed for each task activity and the milestone events shall be those the Offeror identifies as the most likely to occur. The IMS shall include the Task ID, the Task Name, the Task Duration in days, the task

Start Date, the Task Finish Date, and the Task Predecessor ID(s) on each printed page. Landscape page layout is highly recommended.

Additionally, in narrative separate from the IMS itself, the Offeror shall identify the most significant risk areas, and for these risk areas, shall discuss the risk mitigation activities the Offeror proposes to undertake.

Relevant Past Performance (Factor 3)

The Offeror shall provide past performance information on a maximum of four (4) previous Government contracts/orders. The Government desires at least one (1) past performance submission for the prime contractor on this effort and at least one (1) past performance submission for any subcontractor performing 25% or more of the total proposed contract amount (CLINs 0001, 1001, 1003, 2001).

The Offeror shall provide Past Performance information as follows:

1. Complete and submit, ensuring provision of all information requested, the Relevant Experience Form

(Attachment 7). The Offeror shall address only one contract/order per form. The Offeror shall list and provide contact information for the PCO and Contracting Officer Representative (COR) for each relevant contract/order.

The Offeror shall ensure that the above-requested Government points of contact (POCs) are current, accurate, and complete. The Offeror shall describe how each reference meets the below definition of relevancy.

2. Submit CPARS evaluations, if available, for each relevant contract/order. If CPARS evaluations are unavailable for a particular Relevant Experience Form, the Offeror shall request a Past Performance Questionnaire (PPQ)

(Attachment 8), per past experience from the Technical Point of Contact (TPOC) listed in Block 9a/9b of the

Relevant Experience Form. Offerors should request that TPOCs send the completed PPQ, prior to the solicitation closing date, directly to SPAWAR Contracts via e-mail to INSERT 2.0 POC, Contract Specialist, SPAWAR

2.1B26 at: Patricia.Pacheco@navy.mil and kate.mccoy@navy.mil . However, the Government may consider past performance information received after this date and time. The Government reserves the right to communicate with individuals listed as POCs on past performance forms and to use past performance information obtained from sources other than those identified by the offeror in the evaluation of past performance.

Note, (1) the Government may (but is not required to) solicit information relating to contracts cited in subfactor 1b for use in the Factor 3 Past Performance evaluation; and (2) the Government will not evaluate magnitude or contract type as part of relevancy.

Data Rights (Factor 4)

The Offeror shall submit a data rights proposal addressing: (1) non-commercial Technical Data (TD)/Computer

Software (CS)/Computer Software Documentation (CSD), and (2) commercial TD/CS/CSD in consideration of the below Government’s objectives.

(1) For non-commercial TD/CS/CSD, the Government has three (3) objectives, in descending order of preference, with the last objective being a material requirement for evaluation purposes:

a. For all OCOMMS Demonstration System designs and deliverables under this contract, including items, components, or processes developed with mixed funding, the Government desires that all non-commercial TD as defined at DFARS 252.227-7013, and CS (including source code) and

CSD both as defined at DFARS 252.227-7013 and 252.227-7014 be delivered with Unlimited

Rights (defined at DFARS 252.227-7013 and 252.227-7014).

b. If such non-commercial TD/CS/CSD pertains to items, components, or processes developed exclusively at the Offeror’s own expense, the Government desires rights no more restrictive than

Government Purpose Rights (GPR) (defined at DFARS 252.227-7013 and 252.227-7014) for potential future competitive procurements, installation, maintenance, and/or repair related to the

OCOMMS System.

c. For CDRLs A014, A015, A016, A017, and A024, the Government requires a license agreement for Specifically Negotiated License Rights (SNLR) (SNLR is set forth in DFARS 252.227-7013 and 252.227-7014) that addresses the Government’s material requirement for disclosure of information to the United Kingdom and Northern Ireland Ministry of Defense (UK MOD)

Government and UK MOD Contractor(s), as part of the OCOMMS PA. At a minimum, the license agreement shall provide the US Government with the following rights:

i. The US Government may release or disclose technical data, computer software, and/or computer software documentation (TD/CS/CSD) contained in CDRLs A014, A015, A016, A017, and A024, outside the US Government to the UK MOD, and UK mailto:Patricia.Pacheco@navy.mil mailto:kate.mccoy@navy.mil contractors, to reproduce, use, display, release or disclose the TD/CS/CSD within their respective entities and wholly-owned subsidiaries, if applicable, only for the exclusive purpose of performing under their respective contract supporting the UK COMMS PA.

The “UK Contractor” may include any prime contractor or subcontractor currently or in the future performing work under a contract or subcontract for the UK portion of the

OCOMMS PA.

(2) For any commercial TD/CS/CSD that the Offeror proposes to utilize or deliver commercial TD/CS/CSD, the Government has two objectives, with the second objective being a material requirement for evaluation.

a. The Government desires to obtain a license to the commercial TD/CS/CSD that grants the

Government the equivalent of GPR in all of the commercial TD/CS/CSD.

b. The Government requires a SNLR with equivalent rights as detailed above in (1)c.i. for CDRLs

A014, A015, A016, A017, and A024.

The Offeror shall complete and submit the table as contained in the Section K provision(s) entitled "Identification, and Assertion of Use, Release, or Disclosure Restrictions" (DFARS 252.227-7017) and, if applicable “Technical

Data or Computer Software Previously Delivered to the Government” (DFARS 252.227-7028), to identify both the commercial and non-commercial TD/CS/CSD to be delivered with other than unlimited rights, the asserted rights category, the basis for the assertion, and the name of the corporation, individual, or other person asserting restrictions. The Offeror shall use separate tables for commercial and non-commercial items; for the commercial list, the Offeror shall follow the DFARS 252.227-7017 format as closely as possible. The Offeror shall ensure that the

TD/CS/CSD are identified by specific reference to the requirement to deliver or provide that TD/CS/CSD in the contract, for example, by referencing the associated CLINs, CDRLs, or paragraphs in the SOW. Additionally, the

Offeror shall complete the data rights matrix identifying proposed data rights on a CDRL basis, Attachment 10.

If commercial computer software (including open source software) is proposed for delivery as part of the Offeror’s solution, the Offeror shall include, as part of the proposal, any and all commercial or open source license agreements applicable to CDRLs or other deliverables under this contract, including those applicable to the Offeror’s sub-contractors. The Government reserves the right to negotiate any terms of use and conditions of the commercial licenses that are inconsistent with federal procurement law, that do not meet the Government’s needs (as stated above), and/or that conflict with the Section I Clause “Technical Data – Commercial Items” (DFARS 252.227-

7015). The resulting license agreements will be attached to the executed contract. If the Offeror intends to use computer software development tools to develop its computer software deliverables, but not deliver the development tools, it must do so in a manner that does not impose licensing burdens on the Government with respect to the computer software deliverables.

Additionally, if the Offeror is proposing delivery of TD/CS/CSD associated with a license agreement for SNLR, it shall include as part of the proposal any and all such license agreements applicable to CDRLs or other deliverables under this contract, including those applicable to the Offeror’s subcontractors. Merely referencing or describing a license agreement for SNLR is not sufficient.

The Offeror shall ensure consistency between the technical data rights assertion tables, data rights matrix, and information provided in the data rights proposal.

The technical data rights assertion tables, data rights matrix, copies of commercial licenses and/or license agreements for SNLR are exempt from the page count.

Factor 5: Small Business Utilization

The Offeror (including small businesses) shall describe its proposed approach to utilizing to small business concerns for this effort. Offerors shall include vendors who are providing material on the Bill of Materials

(BOM) as part of the Small Business Commitment Sheet. Small Businesses include Small Disadvantaged

Businesses, Women-Owned Small Businesses, Veteran- Owned Small Businesses, Service-Disabled Veteran-

Owned Small Businesses, HUBZone Small Businesses and Historically Black Colleges or Universities and

Minority Institutions (See 13 CFR 121.105, 13 CFR 410 and 13 CFR 121.411). Small business offerors

(assuming a valid small business in accordance with 13 CFR 121.105) should include their own participation in the proposed participation percentage.

The Offeror shall provide the cage code and proposed North American Industry Classification Standard (NAICS) code for each proposed small business subcontractor for verification of size status. The Offeror shall list all applicable business types for which each subcontractor qualifies. For each small business subcontractor or vendor proposed, Offerors must ensure that the subcontractor/vendor names and values listed in the Small Business

Commitment Sheet (Attachment l-7) match the subcontractor/vendor names and values listed in Volume II of the proposal. The inclusion of each subcontractor/vendor in the cost proposal shall serve as evidence that the prime contractor and subcontractor/vendor have entered into a business agreement; no further evidence of a business agreement is required. Only the portion of small business participation that is both listed in the matrix and substantiated by the cost proposal will be considered in the evaluation.

Note: Large business concerns are required to submit a separate Small Business Subcontracting Plan under other provisions of this solicitation; namely, FAR 52.219-9 Alternate II. The requirement for the Small Business

Subcontracting Plan is in addition to the information required by this provision.

COST / PRICE PROPOSAL ORGANIZATION

The Offeror’s Volume III: Cost / Price Proposal shall consist of the following:

1. CLIN 0001, Design of OCOMMS Demonstration System (CPFF)

2. CLIN 1001 OCOMMS Demonstration Support (CPFF)

3. CLIN 1003 Other Direct Costs (ODCs) (Cost – Non Fee Bearing)

4. CLIN 2001 Data Rights (FFP)

Cost Offerors shall submit a separate Cost Proposal as described in the solicitation.

The information required in this section will be used by the Government to evaluate the Offeror’s (and each major subcontractor’s) cost/price proposal for realism and reasonableness as stated in Section M of the RFP. This volume should contain cost information only. The guidelines and requirements in this section are provided to (1) aid

Offerors in preparing their cost/price volume, and (2) aid the Government in reviewing and evaluating the Offeror’s cost/price volume. The Government’s intent is to provide instructions that will allow the Offerors to develop clear, concise and comprehensible proposals and to minimize data requests by the Government during the evaluation process.

Throughout these instructions, formats are provided to assist the Offeror/major subcontractor in providing adequate substantiation and ensuring traceability throughout the cost/price proposal. Blank versions of each attachment are provided in a Microsoft Excel file on the SPAWAR e-commerce website. Each spreadsheet shall be structured so as to show separate totals per CLIN. There are no specific font-size requirements for the information provided in the cost/price proposal, but all information provided in hard copy shall be easily legible. All cost/price information shall be submitted in Then Year dollars (TY$) unless otherwise noted.

All data provided by the Offeror/major subcontractor shall be traceable throughout the proposal. For example, all data provided at lower levels in the Cost Volume shall add up to the totals on the Cost Volume’s summary formats as well as the costs/prices in Section B; the information shall also be traceable to that provided in the Technical and other volumes (where applicable). Where the trace is not direct it shall be explained with detailed narrative addressing all pertinent sections. If costs are not traceable throughout the proposal, the proposal may be rendered unacceptable and ineligible for an award on initial proposals.

For purposes of the Cost/Price Volume, “major subcontractor” is defined as any subcontractor performing more than

3% of the work (in dollars) based on the total proposed contract amount (CLINs 0001, 1001, 1003, 2001). As stated in Section M, the Government reserves the right, but is not required, to incorporate proposed subcontractor costs 3% or below of the total proposed cost without evaluation.

CLIN 0001 (OCOMMS Development)

The offeror shall submit BOE, other direct charges, and BOM substantiation as detailed below.

Basis of Estimates (BOE)

The proposed cost estimates shall be supported with the Offeror’s historical costs and historical experience with similar programs, including actual resources expenditures for comparable tasks and historical data on previous programs. Simply stating that the proposed costs are based on these similar programs is not adequate substantiation.

The Offeror is required to provide data for the historical program and demonstrate the relationship between the historical program, the proposed effort, and explain how and why the data was used. The Offeror shall describe the basis for any parametric factors. When adequate substantiation is not provided in the proposal, the Government may opt to utilize historical data and its experience with other programs. The burden of cost credibility rests entirely with the Offeror. Substantiation of each portion of the proposal and a clear trace to the lowest level for which estimates were developed is required for the Offeror and each major subcontractor. As defined above, major subcontractors are subcontractors that represent 3% or more of the total contract. The Offeror shall furnish the procedures and methodology used in compiling the proposed cost.

When using historical cost data from comparable, analogous systems/subsystems, all assumptions affecting the

Offeror’s proposal are to be fully documented (e.g. inflation, methodology, make or buy decisions, etc.).

Additionally, the Offeror shall present information that clarifies the complexity of the analogous system relative to that of the proposed system. The Offeror must establish that the historical system is in fact similar enough to the proposed system to constitute a valid analogy. When using historical or analogous systems as substantiation, the

Offeror shall describe why the system is comparable to the proposed system.

Substantiation of each portion of the proposal and a clear trace to the lowest level for which estimates were developed is required for any major subcontractor as well as for the Offeror. This information shall be consistent with the information provided in the technical proposal.

General statements such as “estimates were derived from engineering analysis or judgment” are unacceptable.

Statements that simply describe a historical program and the associated labor hours and material costs do not substantiate a cost estimate. The relationship of that program to the proposed system must be demonstrated and justified as outlined in this section.

Cost data shall include the narrative description of the effort and the actual cost data (including material, man-hours and total dollars). Actual cost data does not qualify as adequate substantiation when the Offeror/major subcontractor simply refers to a cost account and provides the labor/material resource for the cost account (example: the XYZ program with the cost account 12345 containing 450 man-months). The Offeror/major subcontractor shall properly cite, clarify, and establish the proper context of all historical actuals used to substantiate their offer and submit to the

Government any relevant documentation needed to support the Offeror’s/major subcontractor’s claims.

A Work Breakdown Structure (WBS) (Attachment L-1) is provided to enable the Offeror to propose the costs associated with CLIN 0001 in a common format for evaluation purposes. For each WBS, the Offeror shall propose labor hours and material estimates as well as rationale and supporting data on separate BOEs. The BOE shall be in accordance with attachment L-8 which is provided as a template. The BOE shall include reasons and justification for any adjustments made to programmatic, technical and actual cost data for the historical system. The Offeror shall provide the basis and document any adjustments applied to the historical data, such as complexity factors and normalization methods, to reflect the characteristics of the proposed system. The BOE shall also include an audit trail "sufficient" for the Government to reconstruct the proposed estimate and judge the credibility of data application. The WBS dictionary (Attachment L-2) is also provided to describe the content of each WBS element for the contract cost effort in greater detail.

Other Direct Charges

Other direct charges are defined as costs not previously identified as a direct material cost, direct labor cost, or indirect cost. In other words, this is a cost that can be identified specifically with a final cost objective that the

Offeror does not treat as a direct material cost or a direct labor cost. Examples of the types of cost commonly included as other direct charges include: Special tooling, test equipment, and facilities, Computer services, Consultant services, Travel, Federal excise taxes, Royalties, Preservation, packaging, packing costs, and

Preproduction costs.

Include the following for support for other direct charge items:

a. Dollars .

b. A narrative summary that gives the approach for the estimate.

c. How the Offeror estimated the cost (i.e., analogy, Rough Order of Magnitude (ROM), model, Cost

Estimating Relationship (CER), etc.). If a cost or price model was used, provide all information (i.e., all assumptions, inputs, etc.) necessary to duplicate the estimate and determine its reasonableness.

d. The Offeror’s or major subcontractor’s evaluation of any quote estimates (i.e., rationale used to determine the reasonableness)

e. Explain any factors applied. Examples of these factors include panstock, scrap, rework, yields, escalation, learning curves, freight, quantity adjustments, and negotiation decrements. Substantiation, including the historical data to support these factors, shall also be provided.