N0002423R5202 Amendment 0001.pdf
PDF 1 MB Posted
- Attached to
- Surface Ship Undersea Warfare (USW) Combat System Production Federal contract opportunity
- Solicitation number
- N0002423R5202
About this file
This is a solicitation for the production of the Surface Ship Undersea Warfare (USW) Combat System. The Navy seeks to procure this system with an Open System Architecture including Infrastructure as a Service using hypervisor technologies. The solicitation involves the production of two configurations: Initial Installs for new ship construction and Build in Place systems for upgrades. It requires the planning, procurement, manufacture, assembly, integration, testing and evaluation of Technical Refresh upgrades to the AN/SQQ-89 system hardware. The contractor must perform systems engineering, facilities management, program management, deliver key personnel, and meet small business participation requirements. The contractor will also need to address rights in technical data and past performance. Proposals are due by a specified date and award is estimated for April 2024. The solicitation involves both cost-reimbursement and fixed-price CLINs over an 8-year period of performance.
View the file
Other files for this federal contract opportunity
Show all 18
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
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 update Sections J and L.
1. CONTRACT ID CODE PAGE OF PAGES
L 1 29
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 07-Sep-2023
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 N0002423R5202
X 9B. DATED (SEE ITEM 11)
04-Aug-2023
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 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
07-Sep-2023
CODE
NAVAL SEA SYSTEMS COMMAND (HQ)
1333 ISAAC HULL AVE SE
WASHINGTON NAVY YARD, DC 20376-2030
N00024 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
N0002423R5202
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS
The following have been modified:
LIST OF ATTACHMENTS/EXHIBITS
The following document(s), exhibit(s), and other attachment(s) form a part of this contract:
Exhibits
Exhibit A – Contract Data Requirements List (CDRL), DD Form 1423, 62 Pages
Exhibit A1 – CDRL Addressee List (incorporated upon award)
Attachments
Attachment J-1 – DoD Contract Security Classification Specification, DD Form 254, 6 Pages
Attachment J-2 – Government Furnished Property (GFP) List, Amendment 0001
Attachment J-3 – Government Furnished Information (GFI) List
Attachment J-4 – Small Business Subcontracting Plan, incorporated upon award
Attachment J-5 – CDRL Cross Reference Matrix
Attachment J-6A – DFARS 252.227-7017 Data Rights List, incorporated upon award
Attachment J-6B – Enhanced Data Rights Option for DFARS 252.227-7017 Data Rights List, incorporated upon award
Attachment J-7A – DFARS 252.227-7028 Data Rights List, incorporated upon award
Attachment J-7B – Enhanced Data Rights Option for DFARS 252.227-7028 Data Rights List, incorporated upon award
Attachment J-8A – Supplemental Information Statement, incorporated upon award
Attachment J-8B – Enhanced Data Rights Option for Supplemental Information Statement, incorporated upon award
Attachment J-9 – Commercial Technical Data (CTD), Commercial Computer Software (CS), or Commercial
Computer Software Documentation (CSD) Rights Assertion List
Attachment J-10 – Key Personnel Resumes
The following document(s), exhibit(s), and other attachment(s) form a part of this solicitation:
Attachments Attachment JS-1 – Bidder’s Question Submittal Form
Attachment JS-2 – Staffing Plan, Amendment 0001
Attachment JS-3 – Total Cost/Price Buildup Spreadsheet, Amendment 0001
Attachment JS-4 – Contractor Award Information
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been modified:
1.0 GENERAL INFORMATION
IMPORTANT: In order to be considered for contract award under this procurement, the Offeror shall possess a
Defense Security Service SECRET facility clearance with SECRET personnel clearances and SECRET safeguarding capability, all issued by the United States Government, by the closing of the solicitation. SECRET facility physical construction must meet the requirements as defined in DoD 5205.07-M Vol 3. The Offeror (and any subcontractors performing SECRET-level work) shall not be:
Under foreign ownership or control
Under a special security agreement
Restricted in access to Compartmented Information, Cryptographic Materials or Systems, Restricted Data, or Formerly Restricted Data.
The Government will not entertain any proposed revisions to the terms and conditions contained in this solicitation submitted as part of Offeror’s proposals, including any attachment or exhibit referenced therein. Therefore, any offer that includes “redlines,” condition(s) of offer, or any other deviation from the requirements of the solicitation may be rejected by the Government.
For proposal purposes, the estimated date of Award is April 2024. The Government reserves the right to award sooner or later if necessary. The start and end dates will be updated accordingly upon Award.
Each Offeror is required to submit a proposal that is sufficiently detailed and complete to fully demonstrate an understanding of, and compliance with, all of the requirements of the solicitation. Proposals shall contain only material directly related to this acquisition. Offerors shall submit all information required by this solicitation.
Offerors’ proposals shall be based on the requirements contained in this solicitation (including those documents, exhibits, and other attachments to the solicitation identified in Section J). Offerors shall submit a proposal encompassing all of the line items listed in Section B of this solicitation. FAILURE TO FOLLOW THE
INSTRUCTIONS OR CONFORM TO ALL REQUIREMENTS OUTLINED IN THIS SOLICITATION
MAY RESULT IN REJECTION OF THE OFFEROR’S PROPOSAL.
Proposals submitted in response to the solicitation must contain a complete description of all pertinent aspects of the effort proposed by the Offeror. Offerors shall not assume that previously submitted data or prior experience presumed to be known to the Government (e.g., previous projects performed for the Government) will be considered as part of the proposal.
General statements such as, “the Offeror understands,” “the Offeror can or will comply with the requirements,”
“standard procedures will be used,” “well-known techniques will be used,” or statements which merely paraphrase the solicitation in whole or in part do not constitute compliance with the requirements for proposal content. Data previously submitted, or presumed to be known (e.g., data or services previously submitted or performed for the
Government) cannot be considered as part of the proposal unless explicitly incorporated into the proposal.
Discussions of each topic in the proposal shall exhibit continuity and logical progression.
1.1 GOVERNMENT-WIDE POINT OF ENTRY (GPE)
This solicitation will be made available only through the Internet on the SAM website (https://sam.gov). From time to time, the Government may post additional information to the SAM website relating to this solicitation (e.g.
responses to questions, solicitation amendments, etc.). It is the responsibility of prospective Offerors to monitor the
SAM website for any such information.
1.2 COMMUNICATIONS WITH THE GOVERNMENT
Unless otherwise specified, the Naval Sea Systems Command Procuring Contracting Officer (PCO) and Contract
Specialist are the sole Government points of contact for this acquisition.
Ms. Tiffany Wulfsohn
Procuring Contracting Officer / Branch Head tiffany.k.wulfsohn.civ@us.navy.mil
(202) 781-5135
Ms. Stephanie Little
Contract Specialist stephanie.m.little6.civ@us.navy.mil
(202) 781-1370
1.3 AVAILABILITY OF ATTACHMENTS AND BIDDER’S LIBRARY
The Government will make available to Offerors a Bidder’s Library containing information to assist in the preparation of a proposal. The Bidder’s Library will also contain certain solicitation attachments that cannot be posted to the GPE. Documents in the Bidder’s Library may contain classified data and/or technical data whose export is restricted by the Arms Export Control Act (Title, U.S.C. Section 2751 et seq. or Executive Order 12470).
To request access to the Bidder’s Library, please submit a completed copy of the DD Form 254, a signed Terms of
Use Agreement (TOUA), and a current copy of your company’s approved DD Form 2345, Military Critical
Technical Data Agreement (verifying eligibility and authority to receive export-controlled information) via email to the PCO and Contract Specialist identified in L.1.2 above. Please reference the name of your company and
“N00024-23-R-5202 Bidder’s Library Access Request” (without quotes) in the subject line of the message. In the body of the email, provide the name and email address of a company individual who will receive a secure download link for the Bidder’s Library materials. If the Government has already granted your company access to the Bidder’s
Library for this procurement, please indicate this also in the body of the email. Offerors that previously executed a
TOUA during the pre-solicitation phase for this solicitation must still submit a request via email to the Contracting
Officer and Contract Specialist for access to the controlled solicitation and Bidder’s Library, but need not resubmit the TOUA or DD Form 254.
The Government will verify the DD Form 254 and DD Form 2345 submission. Upon successful verification and receipt of a duly executed TOUA, the Government will provide via email to the designated company representative a secure download link for the Bidder’s Library. Over the course of the procurement, the Government may provide
Bidder’s Library updates or additional materials to the same designated company representative.
The deadline to request access to the controlled solicitation documents and Bidder’s Library shall be the same as the deadline to submit bidder’s questions regarding this solicitation.
1.4 SUBMISSION OF QUESTIONS AND COMMENTS
Offerors shall submit written questions and comments related to this solicitation using the Bidder’s Question
Submittal Form (Attachment JS-1) for this solicitation. For ease of Government review and to minimize response time, Offerors shall submit this form in the original file format. Do not convert the form to Portable Document
Format (PDF). To ensure the Government understands the context of the question, Offerors shall detail the applicable document name, document date or version, page, paragraph, clause or other specific citation to which the question applies. Information contained in the Government’s responses to bidder’s question shall not supersede any information contained in the solicitation (including amendments). In the event of a discrepancy between a response to a bidder’s question and the content of the solicitation, the solicitation shall take precedence.
Offerors shall not submit comments, questions, or inquiries to any Government representative other than the
Contracting Officer and Contract Specialist identified herein.
The Government intends to distribute bidder’s questions and associated responses via public posting to the SAM website. However, any question or response that contains classified or controlled unclassified information will not be posted publicly, but rather will be posted in the bidder’s library or sent directly to those Offerors who have an executed TOUA and meet the security requirements detailed herein.
In the event that a prospective Offeror wishes to submit a comment or question that the prospective Offeror believes addresses a subject that is specific or proprietary to the Offeror, then the Offeror shall mark the question accordingly on the submission form and provide justification to support its claim. If the Government concurs with this identification, the Government will respond only to that potential Offeror. If the Government does not concur with this identification, it will inform the submitting Offeror and will not provide any further response. The Offeror may resubmit the question without the proprietary marking.
Offerors shall submit in accordance with this section any questions or suggestions related to the terms and conditions of this solicitation prior to the deadline for questions.
The deadline for receipt of questions is 20 calendar days after the date the original solicitation was issued (See Block
5 of the Standard Form 33). Any questions received after this date may not be answered prior to receipt of proposals.
1.4.1 UNCLASSIFIED QUESTIONS
Submit written unclassified questions related to this solicitation via email to the PCO and Contract Specialist identified in Section L 1.2 above. Reference “N00024-23-R-5202 Question from [name of Offeror]” (without quotes or brackets) in the subject line of the message.
1.5 SOLICITATION SECURITY CLASSIFICATION
This solicitation is unclassified, although some information provided in conjunction with this solicitation may be classified. All employees of the Offeror working on the classified portion of its proposal shall have active security clearances at the appropriate classification level. Offerors must provide a completed DD Form 254 in order to gain access to and handle classified materials. Offerors must meet all clearance requirements detailed in the DD Form
254 by the time of contract award.
The Government does not anticipate a need for Offerors to submit classified material in any proposal volume.
OFFERORS SHALL NOT PLACE ANY CLASSIFIED INFORMATION IN ANY PORTION OF ITS
PROPOSAL.
1.6 AWARD WITHOUT DISCUSSIONS
Pursuant to the provision under this section entitled FAR 52.215-1, “Instructions to Offerors – Competitive
Acquisition,” the Government intends to award a single contract on the basis of a proposal submission without conducting discussions with Offerors, but reserves the right to conduct discussions per FAR 15.306 “Exchanges with Offerors After Receipt of Proposals” if determined by the Contracting Officer to be necessary. Each Offeror shall submit only one proposal. No alternate proposals will be accepted, and the submission of multiple proposals will result in rejection of the proposal. Therefore, each Offeror’s proposal submission shall contain the
Offeror’s best terms from a price and technical standpoint. However, the Government may contact any, all, or a limited number of Offerors with questions concerning their proposals as permitted under FAR Part 15. Upon the conclusion of discussions, if they occur, the Government will request Final Proposal Revisions (FPRs) from all
Offerors still within the competitive range.
1.7 PROTECTING CONTROLLED UNCLASSIFIED INFORMATION
Pursuant to DFARS 252.204-7008(c)(1), prospective Offerors are advised proper safeguarding of Controlled
Unclassified Information (CUI) is considered a special standard of responsibility for this solicitation. See FAR subpart 9.1. Failure to properly safeguard and mark Controlled Unclassified Information in a prospective Offeror’s proposal in accordance with applicable regulation and policy (to include Executive Order 13556, the Defense
Acquisition Regulations Supplement and DoD Instruction 5200.48) may preclude the Contracting Officer from being able to provide the required affirmative determination of responsibility. If the Contracting Officer is unable to affirmatively determine the prospective Offeror to be responsible, the prospective Offeror will be ineligible for award.
2.0 GENERAL PROPOSAL INSTRUCTIONS
The completion and submission to the Government of an offer shall indicate the Offeror’s unconditional acceptance of the terms and conditions in the solicitation.
The Government encourages Offerors to contact the PCO and Contract Specialist via the Bidder’s Question Process as outlined in Section L.1.4 above.
Offerors shall take care to submit a legible, neat, orderly, concise and comprehensive proposal. Elaborate brochures or artwork, expensive paper or bindings, or expensive visual or presentation aids beyond those sufficient to present a complete and comprehensive proposal are unnecessary. Clarity is essential. The use of brochures shall be minimized and if used will count against page limits.
2.1 PROPOSAL STRUCTURE, FORMAT, AND PAGE COUNTS
Offerors shall structure proposal submittals such that the required content is organized as follows:
VOLUME
TITLE
PAGE LIMIT
ELECTRONIC COPIES
I Technical/Management Approach
150 1
II Cost/Price Proposal None 1
III Standard Form (SF)
33/Completed Contract
None 1
Note 1: The total page limit for Volume I will vary depending on the number of subcontractors for which the
Offeror must provide past performance information. The past performance narrative for the Offeror shall not exceed five (5) pages in length. The past performance narrative for applicable subcontractors (see Section L.3.1.4) shall not exceed two (2) pages in length for each subcontractor, and there shall be no more than two (2) subcontractors.
Therefore, the page limit for this volume shall be (5 + 2x), where x represents the number of applicable subcontractors. For further details, see the instructions for Volume I.
See Section L.3 and subparagraphs for instructions regarding proposal content. Proposal content designated by this solicitation for electronic submission (e.g., Integrated Master Schedule, Contract-wide
Staffing Plan, etc.) does not count against the solicitation page limits.
Offerors are advised that the quality of information contained in a proposal is significantly more important than quantity. In this respect, Offerors shall strictly observe the page count limitations for each volume. Pages in excess of the applicable page count limit will be removed by the PCO from the back of the respective volume prior to evaluation and shall not be read or evaluated by the Government. It is not necessary to supply the maximum number of pages allowed for each volume; fewer pages may be submitted. Offerors shall organize proposal content sections using index pages or tabbed index divider pages with clear cross-referencing to the table of contents. All pages shall be consecutively numbered within each volume (e.g., 1, 2, 3, …), with the exception of the Cost/Price Volume. For the Cost/Price Volume only, pages must be numbered consecutively within each section, but page numbering may restart at the beginning of each section.
Section L.3 identifies specific items that will be exempt from the page count limitations set forth above. In addition, the following proposal content will be exempt from the page count limitations:
Cover letter
Table of contents
Title pages
Annex pages
Index pages
Tabs
Glossary
Basis of Estimate
Bill of Material Attachment J-4 – Small Business Subcontracting Plan (incorporated upon award)
Attachment J-6A – DFARS 252.227.7017 Data Rights List (incorporated upon award)
Attachment J-6B – Enhanced Data Rights Option for DFARS 252.227.7017 Data Rights List (incorporated upon award)
Attachment J-7A – DFARS 252.227.7028 Data Right List (incorporated upon award)
Attachment J-7B – Enhanced Data Rights Option for DFARS 252.227.7028 Data Right List (incorporated upon award
Attachment J-8A – Supplemental Information Statement
Attachment J-8B – Enhanced Data Rights Option for Supplemental Information Statement (incorporated upon award)
Attachment 9 – Commercial technical data (TD), Commercial computer software (CS), or Commercial computer software documentation (CSD) rights assertion list
Attachment J-10 – Key Personnel Resumes
Attachment JS-1 – Interested Offeror Questions Form
Attachment JS-2 – Staffing Plan
Attachment JS-3 – Total Cost/Price Build Up Spreadsheet
Attachment JS-4 – Contractor Award Information
The Government may consider any failure on the part of an Offeror to comply with these instructions to be an indication of how the Contractor will comply with contract requirements during contract performance. Therefore, the Government encourages Offerors to contact the PCO and Contract Specialist via the Bidder’s Question Process outlined in Section L.1.4.
2.2 LABELING AND PACKING
Each proposal section shall start on a new page. Each volume shall contain a table of contents that lists the sections, subsections, and page numbers. Each volume shall also include a glossary explaining all abbreviations and acronyms used.
The first page of each proposal volume shall display the information required by FAR 52.215-1(c)(2) and shall also contain the volume number, volume title, security classification level of the volume and serial/copy number. If an
Offeror wishes to restrict the disclosure or use of its proposals, the Offeror shall use the legend permitted by FAR
52.215-1(e) and prominently indicate the specific pages and paragraphs that contain proprietary information. Each page of an Offeror’s proposal shall be labeled with the Offeror’s name, solicitation number and date corresponding to the date of the proposal, and CUI designation.
All information relating to contract cost or pricing data shall be included only in the section of the proposal designated as the Cost/Price Proposal Volume. UNDER NO CIRCUMSTANCES SHALL OFFERORS
INCLUDE CONTRACT COST AND PRICING DATA IN VOLUME I. In the event that cost and pricing data are included in Volume I, that data will be excluded from the evaluation.
Electronic proposal submissions and supporting information shall be submitted via the Procurement Integrated
Enterprise Environment (PIEE) website (https://piee.eb.mil) and shall be sent to both the PCO and Contract
Specialist listed in L.1.2 above. If files are password protected, passwords shall also be provided to the PCO and
Contract Specialist listed in L.1.2 above. The Government will not accept submissions on any other electronic media, such as flash memory cards or USB flash drives. All files submitted to the Government shall be compatible with Microsoft Office 2016. All viewgraphs shall be submitted in Microsoft PowerPoint format. All spreadsheets shall be submitted in Microsoft Excel format with all mathematical equations used for calculations visible and traceable. All text and proposal narrative shall be submitted in Microsoft Word format. All schedules shall be submitted in Microsoft Project format. No fields or documents may be password protected. Offerors shall not embed sound or video files into the electronic files. All Microsoft Excel files shall be completely readable and editable such that the Government may readily ascertain the validity of the pricing or other data contained therein. All data and tables shall be submitted in a printable format.
2.3 PAGE SIZE AND FORMAT
The narrative material in each proposal shall be single-spaced, typed, or printed in 12-point Times New Roman font.
Text within tables, diagrams, pictorial charts, or graphic material may use no smaller than 8-point font in Times
New Roman or Arial typeface.
Every section, figure, and table shall be numbered; paragraphs within sections do not need to be numbered.
2.4 PROPOSAL SUBMISSION
Proposals in response to this solicitation shall be submitted to the Government no later than the time specified in Block 9 of the SF 33. “Local time” shall refer to the time zone for Washington, DC.
Telegraphic offers, facsimile offers, or offers submitted by electronic commerce will not be considered. Any proposals received through these means will be deleted or destroyed. Furthermore, the Government will not consider telegraphic, facsimile, or electronic commerce modifications of offers, or withdrawals of offers.
Each Offeror shall submit electronic copies using the method and quantities specified above. Electronic copies delivered via the Procurement Integrated Enterprise Environment (PIEE) website (https://piee.eb.mil), Solicitation
Module, shall be sent to both the PCO and Contract Specialist identified in L.1.2 above. If files are password protected, passwords shall also be provided to the PCO and Contract Specialist identified in L.1.2 above.
2.5 MAJOR SUBCONTRACTOR PROPOSALS
For the purposes of this proposal, a significant subcontractor is defined as a subcontractor or supplier whose effort is proposed to be 10 percent (10%) or greater of the total proposed cost to the Government of CLINs x002, x004, x008, and x009 inclusive of prime burdens and fee on the subcontractor proposed cost. However, where otherwise minor subcontractors cumulatively perform more than 20% or greater of the total proposed cost to the Government of CLINs x002, x004, and x008 inclusive of prime burdens and fee on the subcontractor proposed cost, in Section B, all subcontractors performing under cost-reimbursable arrangements are considered major subcontractors and must propose as such.
Major subcontractors may submit proposals or supporting information directly to the Government. The prime
Offeror shall be responsible for the timeliness of any major subcontractor submissions. Failure to submit major subcontractor proposals by the proposal due date may render the entire proposal, including the prime Offeror's proposal unacceptable. All subcontractors that do not meet the definition of major subcontractor are minor subcontractors.
3.0 PROPOSAL CONTENT REQUIREMENTS
Offerors shall provide the information requested in the following paragraphs in the volumes indicated. If additional information is provided in other volumes or sections, Offerors shall provide clear references to the location in the proposal where the information may be found.
An Offeror’s proposal shall be sufficiently detailed to enable Government evaluation members to make a thorough evaluation against specific factors established in Section M, and to arrive at a sound determination as to whether or not the prospective Offeror will be able to perform in accordance with the stated requirements. Discussions of each topic in the proposal shall exhibit continuity and logical progression. Data shall be organized to enable Government personnel to thoroughly evaluate the proposal. A concise, legible, neat, orderly and comprehensive proposal is required. The Government does not assume the duty to search for data to cure problems it finds in proposals.
Failure to conform to all requirements of this solicitation may form the basis for rejection of the proposal.
3.1 VOLUME I: TECHNICAL
Do not include cost or price information in this volume. The information contained in this volume shall enable
Government personnel to thoroughly evaluate and arrive at a sound determination of whether or not the proposal meets the requirements of the solicitation. To this end, this volume shall be specific, detailed, and complete enough to demonstrate clearly and fully that the Offeror understands the objectives and has a thorough understanding of the solicitation requirements for accomplishing the efforts under this solicitation and the technologies involved.
Proposals may include block diagrams, flow diagrams, sketches, drawings, schematics, and interface descriptions required to describe the Offeror's proposed concept. The technical section must be sufficient to show how the
Offeror proposes to comply with the Government's requirements and must include a full explanation of the methodology and procedures to be followed. The Offeror must also identify and evaluate any risks associated with the Offeror’s proposed approach and propose mitigation steps to minimize the Government’s risk in accepting the
Offeror’s proposed solution.
The Offeror must clearly state any and all assumptions made in developing the proposed solution. Attachments J-2 and J-3 provide a complete list of all Government Furnished Property (GFP) and Government Furnished Information
(GFI) that the Government intends to provide under this contract. The Offeror shall not assume the use of any GFP or GFI not listed in Attachments J-2 and J-3. Volume I shall address the following factors:
TITLE FACTORS/ELEMENTS
Technical Volume Factor (1): Technical Approach
Element 1: Systems Engineering
Element 2: Facilities
Factor (2): Management Approach
Element 1: Program Management
Element 2: Key Personnel
Element 3: Personnel Resources
Element 4: Small Business Subcontracting
Plan and Participation
Factor (3): Rights in Technical Data
Factor (4): Past Performance
Background: The AN/SQQ-89 Undersea Warfare (USW) program implements sensors and weapon support control systems with advanced acoustic data processing and displays in order to provide battlespace dominance operations in open-ocean and littoral environments for the Aegis Destroyers, Cruisers, and Frigates. These capabilities are sustained by periodically delivering tech refresh upgrades to the fleet based on the latest Commercial Off-the-Shelf
(COTS) hardware. These upgrades also address concerns of hardware obsolescence, capacity and capability expansion, resolution to observed fleet issues, and cost-trade analyses. As part of this approach, the Government intends to procure these system(s) with an Open System Architecture (OSA), which includes support for
Infrastructure as a Service (IaaS) via the use of hypervisor technologies.
Production and assembly of Hypervisor Technology 0 (HT0) will occur primarily in two configurations: Initial
Installs (e.g., New Ship Construction) and Build in Place (BIP). Initial Install systems are herein defined as full production unit assemblies in support of newly built ships, such as the DDG-51 and FFG-62 New Construction
Programs. All computer processing and structural cabinet hardware is required for such a delivery. Build in Place systems are herein defined as a combination of full production assemblies and unit modification kit (modkit) assemblies. The Build in Place approach avoids unnecessary removal of AN/SQQ-89 cabinet structures and subassemblies on board ship while ensuring the upgraded system configuration matches the current hardware baseline (e.g., HT0). Additionally, reclaimed fleet hardware components may be supplied to the contractor as GFE in order to integrate with future system deliveries. The Build in Place approach requires less hardware to be procured and assembled thus potentially reducing production lead times for this configuration type.
3.1.1 VOLUME I: FACTOR 1 – Technical Approach
The Offeror’s proposed Technical Approach shall demonstrate adequate knowledge, understanding, capability, and experience to perform all areas of the AN/SQQ-89 Statement of Work (SOW) in accordance with hardware (HW) requirements and specifications.
The elements included in this factor are Systems Engineering and Facilities.
3.1.1.1 Systems Engineering
i. The Offeror shall describe its System Engineering (SE) process and how it allocates and manages performance and interface requirements, communicate with multiple platform/sensor organizations, and affects multiple warfare areas. The Offeror shall describe how it will flow the requirements across the AN/SQQ-89 system hardware and software engineering efforts to produce a balanced system design as described in Section C. The Offeror shall discuss the processes, tools
(such as Computer-Aided Systems Engineering (CASE) and automated tools), and any virtualization to be used to optimize and standardize development and what access will be provided to Government personnel.
ii. The Offeror shall provide a narrative for designing and developing a follow-on notional hardware set based on HT0, in order to develop the next iteration which is going to be HT1. The narrative must address specific efforts required for performance of trade studies, design reviews, program reviews, and development of the Technical Data Package (TDP) required to support hardware architecture design and integration activities. The narrative must account for Environmental
Qualification Testing (EQT) requirements outlined in IWS5-95-Q89-EPQS-037 REV 8.1.
Historically, subsequent baseline deltas may include, but are not be limited to, technological improvements, new capabilities, obsolescence solutions, and modified interfaces. The Offeror shall describe its Obsolescence Management process in accordance with Section C, Paragraph
3.2.2.2.
iii. As described in the SOW, the AN/SQQ-89 HT0 baseline enables Infrastructure as a Service (IaaS) within its footprint. IaaS enables software to be developed independent of the details of the computing infrastructure, effectively abstracting the hardware to an extent. As long as the IaaS solution is a known constant to the software developers, hardware design activities have a higher degree of freedom to vary the computing infrastructure without significant adverse effects to the software developers. The Offeror’s proposal shall describe two approaches to accomplish the IaaS scope of the contract.
Approach A: Government furnished IaaS solution
Under this approach, the Offeror’s proposal shall describe its method to integrate the GFE with the
AN/SQQ-89 system. The HT0 TDP describes a potential solution, where Data Processing
Cabinets and Workstations house the servers where the IaaS solution executes.
Approach B: Contractor furnished IaaS solution
Under this approach, the Offeror’s proposal shall describe its method to design an IaaS solution in accordance with Statement of Work section 3.2.1.9 to support integration with the rest of the
AN/SQQ-89 system.
iv. The Offeror shall describe their process to plan, procure, manufacture, assemble, integrate, test, and evaluate Initial Install and Build in Place Technical Refresh AN/SQQ-89 HT0 systems in accordance with Table L-1. This description shall include the process to plan for Critical Item
Testing (CIT). This description shall include the plan and procedures for Critical Item Testing
(CIT). These processes shall address expected interactions with the Government and include what role GFI and GFP/E/M play. The Offeror shall describe the approach to integration of third party vendor infrastructure services, enclosures (i.e. cabinets), and network processing components including Government Furnished Equipment (GFE) required to produce the AN/SQQ-89(V) hardware Product Baseline. The Offeror shall supply Basis of Estimates (BOEs) for each applicable Contract Work Breakdown Structure (CWBS) element for the production support activities and a representative Bills of Materials (BOMs) for all Production efforts. BOEs shall be organized sequentially by CWBS element and contain sufficient substantiating information to demonstrate the authenticity of the Offeror’s proposed hours. The Offeror shall specifically answer the following questions in every submitted BOE:
i. What is the estimate for the proposed hours? The Offeror shall provide a direct calculation of the estimate.
ii. What is it based on? The Offeror shall include a description of the estimating methodology for the proposed hours (analogy, actual performance, parametric estimating, cost estimating relationship, standard commercial available cost models, etc.) with detail of the program, pools, or historical data and accompanying rationale as to why the BOE is appropriate.
iii. How is it derived? The Offeror shall provide for all referenced programs, derivations of data, historical data reflecting actual performance incurred, and any and all calculations to arrive at the BOE for the proposed hours.
iv. Why is it reasonable? The Offeror shall include an in-depth description of why the
BOE for the proposed hours is fair and reasonable, citing regency and relevancy to the scope of work being estimated.
v. What assumptions were made in deriving the BOE for the proposed hours?
Table L-1 exhibits the procurement profile of each configuration, where each row equates to a
Sub-system or Part/Unit (e.g., Unit 139) that is part of the system identified in either the Initial
Install or Build in Place columns to the right of the table. Top Level Part Numbers for each unit can be referenced against the Production Drawings provided by Attachment J-3. The Initial Install and Build in Place columns define the quantity of units needed to produce Qty 1 of that system configuration.
Table L-1: Sub-system or Part/Unit Required per Configuration
Unit Nomenclature/Name Top Level Part Number Initial Install Build in Place
139 TOWED ARRAY POWER SUPPLY (TAPS) 77C728051G4 1
606 RADIO FREQUENCY TRANSMITTER LN606/R S140217AJ-01 1
607 RADIO FREQUENCY ANTENNA, AS-2809/SRC 6983667-1 1
608 LAMPS HELICOPTER INTERFACE G302319-1 1
608A RF ANTTENUATOR G378976-1 1
703 POWER DISTRIBUTION UNIT (PDU) 7348609G1 1
705-710 TRANSMITTER CABINET 7344064G10 6
711 SWITCH TRANSMIT/RECEIVE (T/R SWITCH) 7344062G1 1
735 POWER DISTRIBUTION UNIT (PDU) W/ 35A BREAKER 7348604G2 1
740 MAMS CABINETS (SER1) 11200000481 1
741 MAMS CABINETS (SER3) (SMP DESIGN) 11200000281 1
760 POWER DISTRIBUTION UNIT (PDU) W/ 35A BREAKER 7348605G3 1
761 POWER DISTRIBUTION UNIT (PDU) W/ 35A BREAKER 7348606G4 1
762 POWER DISTRIBUTION UNIT (PDU) W/ 35A BREAKER 77C739789G1 1
818 SYSTEM CONTROL PANEL - CG VERSION (DECK MOUNTED) 77C740676G2 1
819 SOFTWARE DEFINED SONOBUOY RECEIVER (SDSR) 2517-050-001 1
830-835 CONSOLE, COMPUTER DISPLAY (CMT VERSION) N168636-2 6
837 CONSOLE, COMPUTER DISPLAY (837) 77C740681G1 1
838 AI&R DEDICATED DISPLAY N168580-1 1
839 E-STATUS BOARD (SCR) N168579-4 1
840 E-STATUS BOARD (CIC)(DDG-127 AND BEFORE) N168579-5 1
840 E-STATUS BOARD (CIC) (I/O BOX/SPEAKER ASM ONLY)(DDG-128AF) N168579-3 1
845 DATA PROCESSOR CABINET (SIM TO) 77C740677G3 1
845MK DATA PROCESSOR CABINET 77C740677G3001 1
846 DATA PROCESSOR CABINET (SIM TO) 77C740677G3 1
846MK DATA PROCESSOR CABINET 77C740677G3001 1
847 DATA PROCESSOR CABINET (SIM TO) 77C740677G3 1
847MK DATA PROCESSOR CABINET 77C740677G3001 1
858 RECEIVE I/O CABINET (7.2A, 7.2B, 9.X, 10.X) (SIM TO) 77C740678G1 1
858MK3 RECEIVE I/O CABINET (5.3.9, 5.4, 6.3) FOR TI-14/16 77C740678G2001 1
859 TRANSMIT I/O CABINET (7.2A, 7.2B, 9.X, 10.X) (SIM TO) 77C740679G1 1
859MK2 TRANSMIT I/O CABINET (5.3.9, 5.4, 6.3) 77C740679G2001 1
870 NOISE MONITORING HYDROPHONE (NMH) 8359869-1 1
870 NOISE MONITORING HYDROPHONE (NMH) MOD KIT 77C739794G1 1
871 EQUIPMENT RACK (SIM TO) 77C740680G1 1
871MK EQUIPMENT RACK 77C740680G1001 1
MCE MCE CABINETS N000520-2 5
6KVA KITS MCE 6KVA MODIFICATION KITS N000520-2001 5
v. The Offeror shall describe the use of its system security engineering (SSE) process in specifying and designing a system that is protected against external threats and hardware/software vulnerabilities as described in Section C, Paragraph 3.2.1.7. The Offeror shall also describe the approach for information security engineering compliance with Cybersecurity requirements in accordance with DoDI 8500.01 and PEO IWS INST 5239.1.
vi. The Offeror shall describe the application of its Configuration Management (CM) responsibilities in support of the Systems and Subsystems and the processes used to manage the many variants and baselines of hardware, firmware and IaaS under this contract. The Offeror shall describe its processes for configuration identification of as-delivered items and the configuration status accounting for delivered Hypervisor Technology hardware products.
vii. The Offeror shall provide and describe an Integrated Master Schedule (IMS) at the lowest
Contract Work Breakdown Structure (CWBS) level that shows how it will be ready to start full-rate production of AN/SQQ-89 systems in Year 3 of the contract, and deliver the first system in
Year 5 of the contract with a delivery cadence of at least one (1) system per month. The IMS shall include:
Tasks on the critical path and methodology for managing these tasks to achieve proposed milestones and required delivery dates.
The allocation of these tasks between prime and significant subcontractors.
Adequate detail regarding technology trade studies, requirements verification, obsolescence mitigation, test plans, test procedures, TDP and Installation Control Drawings (ICD) deliveries, SETR reviews, CIT’s and EQT events in order to meet a Production Readiness
Review (PRR) milestone prior to commencing production.
3.1.1.2 Facilities
The proposal shall demonstrate that the Offeror has adequate design, development, testing, and manufacturing capability and capacity for successful performance of all described requirements, including system and engineering support facilities and manufacturing facilities, to include Build in Place systems, in accordance with the SOW, RFP, DD254 (Attachment J-1), and all GFI (Attachment J-3). This description shall address the following:
i. The Offeror shall describe how its facilities meet the IMS provided in response to Section L 3.1.1.1.vii.
Additionally, the Offeror shall describe the facility capacity in terms of the maximum production delivery cadence of systems per month.
ii. Describe its facilities for the physical inspection and storage of incoming materials and vendor supplied items; production, fabrication, and assembly; performing critical processes and procedures; and development, production test, and inspection. The facilities involved in this effort should include sites used for fabrication, assembly, Incoming Inspection Tests, Functional Configuration Audits (FCA), Physical
Configuration Audits (PCA), Production Inspection Test (PIT) and Production Reliability Acceptance Test
(PRAT). PIT and PRAT requires use of classified software and therefore the Offeror shall provide appropriate classified test facilities.
iii. The Offeror shall describe the simulations and stimulations to be incorporated into the test facility and the method of accreditation of each.
iv. The Offeror shall describe the layout of space, provide a diagram of its facilities for this specific program, and assure the availability of the facilities to meet the Government’s requirements.
v. The Offeror shall state whether the facilities are leased or owned. If leased, the Offeror must provide copies of all pertinent lease(s).
3.1.2 VOLUME I: FACTOR 2 – MANAGEMENT APPROACH
The Offeror shall propose a Management Approach that describes its understanding, capability, and experience to perform all areas of the AN/SQQ-89 SOW in accordance with HW requirements and specifications.
The elements included in this factor are Program Management, Key Personnel, Personnel Resources and Small
Business Subcontracting Plan and Participation.
3.1.2.1 Program Management
The Offeror’s proposal shall:
i. Describe the organization structure it will create to accomplish the scope of the SOW, how that organization will distribute workload among its workforce and subcontractors, and how it will interact with the Navy, indicating lines of authority and communication within the Offerer’s organizational structure in terms of effective integration of AN/SQQ-89 system design, development, testing, and integration support tasks.
ii. A description of the program organization and management capabilities to accomplish the contractual obligations, and provide scheduling and planning for the development, fabrication, test, subcontracting, purchasing and manufacturing. If teaming is applicable, expand the management organizational chart and discussion requested above to illustrate the working levels of internal and external interfaces among subcontractors and team members.
iii. Describe the alignment of Cost, Performance, and Schedule metrics with Contract Data Requirement List
(CDRL) A001 and A003 requirements. This description shall include the Offeror’s proposed
Cost/Schedule/Control System and Earned Value Management System (EVMS), the method to be used in providing cost control, and linkage to contract performance reporting.
iv. Describe the Offeror’s plan to leverage personnel across the various functional areas including system design, development, testing, production, remote and on-site support of fielded systems (at land-based test site and surface ships) to efficiently move people onto and off tasks, and between tasks as tasks start and stop over time.
v. Provide a risk mitigation plan that describes areas of the SOW that the Offeror assesses as containing technical, schedule and cost risks. Addresses in detail how the plan will offset potential cost variance, schedule delay, and technical performance risk associated with delivery or integration for all deliverables, including GFE/P/M issues, and mitigation activities.
3.1.2.2 Key Personnel
The Offeror shall propose the below listed personnel as mandatory key personnel possessing the experience and education specified below. The Offeror shall submit detailed resumes for proposed key personnel that include the following information:
Name
Years of experience
Training
Unique or special qualification
Positions held
Tenure with the firm
Degrees received from and dates of attendance at accredited colleges or universities
Work history (including dates) of each individual as it relates to the anticipated statement of work task(s) to be assigned to that individual
Security Clearance Level, including date and time of last investigation
U.S. Citizenship
Resumes shall have a page limit of two (2) pages each, but will not count towards the overall page count limit for
Volume I. Resumes are to be submitted as part of the Appendix to Volume I and do not count against the page limit.
Key Personnel resumes will be incorporated into the contract at award as Attachment J-10. The resumes shall demonstrate the qualifications possessed by the proposed key personnel to complete the functions of which the
Offeror has proposed that person.
The qualifications listed in each individual proposed key personnel resume, not the specific individual, are the materially relevant aspects of the proposed key personnel partially forming the basis of award under the clause entitled C-237-H002, Substitution of Key Personnel. Therefore, even if a proposed key individual becomes unavailable to the Offeror between proposal submission and award, the Government will evaluate and make its award decision based on the qualifications listed on the proposed resume(s). When the Government awards a contract under those circumstances, the Government will require the awardee to use the qualifications listed on the relevant proposed key personnel resume as the basis for replacing that individual during contract performance. The
Offeror shall make no substitution of key personnel without prior notification to and concurrence of the Contracting
Officer.
Minimum requirements and desired qualifications for each of the key personnel identified below are as follows:
a. Program Manager
Minimum Requirements:
o 15 years of experience in Industry or Government technical or business management o Active Secret (S) Security Clearance at the closing of the solicitation o U.S. Citizenship
Desired Qualification:
o 15 years of experience with DoD acquisition processes in Navy program management and
Field Site Operations o Bachelor degree (BS/BA) in related technical field
b. Chief Engineer:
Minimum Requirement:
o 10 years of experience with systems engineering o Bachelor degree (BS/BA) in related technical field o Active Secret (S) Security Clearance at the closing of the solicitation o U.S. Citizenship
Desired Qualification:
o 10 years of experience with system engineering of Undersea Warfare systems used in a Navy environment
c. Lead for Test and Integration
Minimum Requirement:
o 10 years of experience working with Navy or Department of Defense organizations working on hardware qualification and integration tests and associated mechanical and electrical testing o Active Secret (S) Security Clearance at the closing of the solicitation.
o U.S. Citizenship
Desired Qualification:
o 6 years of technical experience with Undersea Warfare Systems.
o Bachelor degree (BS/BA) in related field.
3.1.2.3 Personnel Resources
The Offeror shall provide a Staffing Plan (excel file – without rate information), which shall include all proposed labor category personnel (by name – both prime and subcontractors) known at the time of proposal submission to support performance of CLINs x002 and x008. The format for the Staffing Plan without cost is provided as
Attachment JS-2. The Offeror shall complete the Staffing Plan columns regarding Years of Applicable Experience, Highest Degree Achieved, Degree Area, place of performance, and may provide additional information to support the level of experience and/or education requirements listed below. The Offeror shall complete all columns in the
Staffing Plan. Offeror may use “TBD” for non-key positions that do not have identified personnel. All Key
Personnel shall be identified. The Staffing Plan shall be provided as a separate file and include all of the information requested using the provided template. Offerors shall highlight any key positions. Offerors are cautioned that the staffing plan provided in the technical volume, including the names of all individuals and all proposed efforts, must be the same mix and amount of hours as that of the cost proposal.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .