Amendment_0001.docx
DOCX document 60 KB Posted
- Attached to
- MK 5 Velocimeter
- Solicitation number
- N00024-16-R-5369
About this file
Amendment 0001
View the file
Other files
Show 40 more
50 files listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
N00024-17-R-5369
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION E - INSPECTION AND ACCEPTANCE
The following have been added by full text:
HQ E-2-0015 QUALITY MANAGEMENT SYSTEM REQUIREMENTS (NAVSEA) (APR 2017)
Quality Management System Requirements. The Contractor shall provide and maintain a quality management system that, as a minimum, adheres to the requirements of ANSI/ISO/ASQ 9001-2015 Quality Management Systems and supplemental requirements imposed by this contract. The quality management system procedures, planning, and all other documentation and data that comprise the quality management system shall be made available to the Government for review. Existing quality documents that meet the requirements of this contract may continue to be used. The Government may perform any necessary inspections, verifications, and evaluations to ascertain conformance to requirements and the adequacy of the implementing procedures. The Contractor shall require of subcontractors a quality management system achieving control of the quality of the services and/or supplies provided. The Government reserves the right to disapprove the quality management system or portions thereof when it fails to meet the contractual requirements.
The following have been deleted:
HQ E-2-0015
SECTION G - CONTRACT ADMINISTRATION DATA
The following have been modified:
| PURCHASING OFFICE |
| COMMANDER |
| REPRESENTATIVE: |
| ATTN: Rufus Brown |
NAVAL SEA SYSTEMS COMMAND
1333 ISAAC HULL AVENUE SE STOP 2040
WASHINGTON NAVY YARD DC 20376
Telephone No. 202/781-1451
Fax No.
Email Address: rufus.brown@navy.mil
SECTION I - CONTRACT CLAUSES
52.209-4 FIRST ARTICLE APPROVAL--GOVERNMENT TESTING (SEP 1989)
(Contracting Officer shall insert details)
(a) The Contractor shall deliver the 3 FAU MK 5 Velocimeters within 12 months from the date of this contract to the Government at the address identified in Section F for first article tests. The shipping documentation shall contain this contract number and the Lot/Item identification. The characteristics that the first article must meet and the testing requirements are specified elsewhere in this contract.
(b) Within 90 calendar days after the Government receives the first article, the Contracting Officer shall notify the Contractor, in writing, of the conditional approval, approval, or disapproval of the first article. The notice of conditional approval or approval shall not relieve the Contractor from complying with all requirements of the specifications and all other terms and conditions of this contract. A notice of conditional approval shall state any further action required of the Contractor. A notice of disapproval shall cite reasons for the disapproval.
(c) If the first article is disapproved, the Contractor, upon Government request, shall submit an additional first article for testing. After each request, the Contractor shall make any necessary changes, modifications, or repairs to the first article or select another first article for testing. All costs related to these tests are to be borne by the Contractor, including any and all costs for additional tests following a disapproval. The Contractor shall furnish any additional first article to the Government under the terms and conditions and within the time specified by the Government. The Government shall act on this first article within the time limit specified in paragraph (b) of this clause. The Government reserves the right to require an equitable adjustment of the contract price for any extension of the delivery schedule or for any additional costs to the Government related to these tests.
(d) If the Contractor fails to deliver any first article on time, or the Contracting Officer disapproves any first article, the Contractor shall be deemed to have failed to make delivery within the meaning of the Default clause of this contract.
(e) Unless otherwise provided in the contract, the Contractor--
(1) May deliver the approved first article as a part of the contract quantity, provided it meets all contract requirements for acceptance and was not consumed or destroyed in testing; and
(2) Shall remove and dispose of any first article from the Government test facility at the Contractor's expense.
(f) If the Government does not act within the time specified in paragraphs (b) or (c) of this clause, the Contracting Officer shall, upon timely written request from the Contractor, equitably adjust under the Changes clause of this contract the delivery or performance dates and/or the contract price, and any other contractual term affected by the delay.
(g) The Contractor is responsible for providing operating and maintenance instructions, spare parts support, and repair of the first article during any first article test.
(h) Before first article approval, the acquisition of materials or components for, or the commencement of production of, the balance of the contract quantity is at the sole risk of the Contractor. Before first article approval, the costs thereof shall not be allocable to this contract for (1) progress payments, or (2) termination settlements if the contract is terminated for the convenience of the Government.
(i) The Government may waive the requirement for first article approval test where supplies identical or similar to those called for in the schedule have been previously furnished by the Offeror/Contractor and have been accepted by the Government. The Offeror/Contractor may request a waiver.
(End of clause)
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been added by full text:
HQ L-2-0013 SPECIAL PROPOSAL RECEIPT REQUIREMENTS (NAVSEA) (APR 2015)
(a) NAVSEA HQ is located at the Washington Navy Yard (WNY) where access is strictly limited in accordance with Naval District Washington (NDW) security regulations. It is recommended that proposals be mailed in accordance with RFP instructions. In the event you prefer to hand carry your proposal, ensure adequate time has been allowed by your representative to accommodate the additional security procedures. Detention at a NDW gate or failure to adhere to the procedures provided herein will not be considered an exception to timely proposal delivery as addressed in FAR 52.215-1, Instructions to Offerors – Competitive Acquisitions.
(b) Offerors hand carrying proposals shall call the contracting officer or contract specialist at least 48 hours prior to arriving at the WNY to make arrangements. Offerors with proper credentials (CAC) can enter the WNY via the Isaac Hull Gate off M Street SE; other offerors must go to the O Street Gate, WNY Pass Office, where they will need to be sponsored onto the installation by a Government representative of the contracting officer. Vehicles entering NDW are subject to random searches. Packages should not be sealed as they are subject to inspection. Classified material shall be prepared in accordance with current security requirements. The contracting officer or contract specialist may receive the proposal and provide the offeror a receipt with the time and date of delivery.
(c) All offerors shall mark each RFP package with the name of the contracting officer and the contract specialist, their codes and phone numbers. In the event you have not been provided with this information contact the person listed in block 5 of the SF 26 or block 7 of the SF 33.
SECTION L
INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS
PERIOD FOR ACCEPTANCE OF OFFERS
(a) The Offeror agrees, if this offer is accepted by the Government within 120 calendar days from the date for receipt of offers specified in Block 12 of Standard Form 33 to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.
(b) A written notice of award or acceptance of an offer; mailed or otherwise furnished to the successful Offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party.
PRE-AWARD SURVEY
The Government reserves the right to conduct a pre-award survey or to require other evidence of technical, production, managerial, financial, and similar abilities to perform the required work prior to the award of a contract in either Phase I or Phase II.
L.1: PROPOSAL PREPARATION INSTRUCTIONS
1. General The MK 5 Velocimeter Acquisition consists of two phases. Phase I First Article Units and Phase II Production. It is the intention of the Government to award up to two contracts pursuant to this solicitation for the Phase I Velocimeter First Article Units. Following completion of Phase I, the Government will down-select to one of the successful Phase I Contractors for the performance of the Phase II Velocimeter Production, using the evaluation factors listed in Attachment 5.
Multiple proposals are not acceptable. Each Offeror shall submit only one proposal which represents their best approach to meeting the requirements of the solicitation.
Offerors shall respond to the full solicitation (not just Phase I). Phase II, will utilize Phase I FAUs to test against requirements and pricing provided as part of the Phase I solicitation, so pricing must be provided for all phases to be fully evaluated.
Evaluation of the proposals will be in accordance with Section M of the Request for Proposal (RFP). Phase I award will be made to the responsible Offeror(s) whose proposal for First Article Units for Phase I is determined by the Government to offer the Best Value to the Government, price and non-price factors considered. Phase II award will be made to the responsible Offeror whose First Article Units meet the requirements specified in Section C of this solicitation, and therefore is deemed technically acceptable, and offers the lowest price for the production units.
SECTION L 1.0
General
1.1 The Contracting Officer is the sole point of contact for this solicitation; however, the designated Contract Specialist may communicate with industry on the Contracting Officer’s behalf.
The Contracting Officer for this solicitation is:
Mr. Brian H. Kimm, SEA 02533
(202) 781-3027 brian.kimm@navy.mil
The designated Contract Specialist is:
Mr. Rufus Brown
(202) 781-1451 rufus.brown@navy.mil
1.2 The Government intends to evaluate proposals and may award up to two contracts for First Article Units of MK 5 Velocimeter systems under Phase I (CLIN 0001). The estimated award date is September 29, 2017.
1.3 No classified data shall be included within proposals. Appropriate security classification markings shall be included, and handling instructions followed, for all submitted data. Strict compliance with applicable law; regulation; and DoD directives, instructions, and manuals is required.
1.4 “Pricing information,” is defined as facts, statistics, or data describing the consideration an offeror will receive in exchange for furnishing the supplies and services described in this solicitation. Pricing information may only be included within Volume I: Price Proposal. Inclusion of pricing information within any other Volume will likely result in rejection of the Offeror’s proposal, as well as the Offeror being determined ineligible for award. If doubt exists as to what constitutes pricing information, Offeror’s are strongly encouraged to submit a question in accordance with paragraph 2.8 of this section.
1.5 Offerors shall refer to FAR 52.215-1, Instructions to Offerors -- Competitive Acquisition. The information below is provided to supplement and implement FAR 52.215-1. Please note that pursuant to FAR 52.215-1, the Government intends to award a contract on the basis of a proposal submission without conducting discussions with Offerors, but reserves the right to conduct discussions in accordance with FAR 15.306 if determined by the Contracting Officer to be necessary.
1.6 Each Offeror shall submit only one proposal. No alternate proposals will be accepted, and submission of multiple proposals will result in disqualification of the submitting Offeror. The Offeror’s proposal submission should contain the Offeror’s best terms from a price and technical standpoint.
1.7 Offerors are reminded past performance information is proprietary source selection information. The Government will only discuss past performance information directly with the prospective prime or sub-contractor that is being reviewed. If there is a problem with a proposed subcontractor’s past performance the prime may be notified of a problem, but no details will be discussed without the subcontractor’s permission.
1.8 At the end of discussions, if they occur, the Government will request Final Proposal Revisions (FPRs) from all Offerors still within the competitive range.
1.9 Each Offeror must submit all information required by this solicitation. The Offeror’s proposal shall be based on the requirements contained in this solicitation (including those documents, exhibits, and other attachments to the solicitation identified in Section J). Failure to comply with the terms and conditions of the solicitation and/or failure to provide all of the requested information may result in the Offeror’s proposal being rejected, and may result in the Offeror being determined ineligible for award.
1.10 The solicitation will be announced through the Governmentwide point of entry (GPE) at: https://www.fbo.gov/.
1.11 The Government may post additional information to the GPE relating to this solicitation (e.g. a solicitation amendment responding to submitted Offeror questions). It is the Offeror’s responsibility to check the GPE for any such information.
1.12 All questions shall be submitted to the Contracting Officer and Contract Specialist in accordance with paragraph 2.8 of this section.
1.13 The Government may schedule a pre-award site survey at facilities identified in any or all or a limited number of Offeror proposals following the proposal submission date.
1.14 All notional dates included within this solicitation (e.g. 12 months after contract award) shall be unilaterally changed by the Government to actual calendar dates (e.g. January 31, 2018) at contract award.
SECTION L 2.0
INSTRUCTIONS FOR SUBMISSION OF OFFERS
The solicitation response shall be contained in two (2) separate volumes:
| Volume I: | Price Proposal |
| Volume II: | Technical Proposal |
SECTION L 2.1
Proposal format and delivery
The contents of the proposal (with page limitations, copy requirements, and references to explanatory paragraphs in this section) are summarized in the table below:
| Section 2.1, Table 1: Proposal Summary |
| Copies Required |
| Volume |
| Title |
| Reference |
| Page Limit |
| Paper |
| Electronic |
| I |
| Letter of Transmittal |
| ¶ 2.2.1 / 2.6.1.1 |
| 2 |
| 1 |
| 2 |
| I |
| Standard Form 33 (completed) |
| ¶ 2.6.1.2 |
| None |
| 1 |
| 2 |
| II |
| Executive Summary |
| ¶ 2.6.2.5 |
| 10 |
| 1 |
| 2 |
| II |
| Technical Approach |
| ¶ 2.6.2.5.1 |
| 75 |
| 1 |
| 2 |
| II |
| Integrated Master Schedule |
| ¶ 2.6.2.5.1 (Subfactor 1.3) |
| None |
| 1 |
| 2 |
| II |
| Management Approach |
| ¶ 2.7.2.5.2 |
| 15 |
| 1 |
| 2 |
| II |
| Past Performance |
| ¶ 2.7.2.5.3 |
| 10 |
| 1 |
| 2 |
2.1.1 Instructions for paper and electronic proposal submissions are detailed below in sections 2.3 and 2.4, respectively. The content of paper and electronic proposals shall be identical in form and content. In the event of discrepancies between paper and electronic copies, the content of the paper copy will prevail.
2.1.2 In order to maximize efficiency and minimize the effort involved in the proposal evaluation process, proposals must comply with the instructions for the format and content herein. Proposals which do not comply may be rejected, and the submitting Offeror may be determined ineligible for award.
SECTION L 2.2
General submission requirements
2.2.1 The Letter of Transmittal submitted with Volume I shall be considered the “first page of the proposal” (see FAR 52.215-1) and shall include the elements required by FAR 52.215-1(c)(2).
The elements required by FAR 52.215-1(c)(2) are:
| i. |
| the solicitation number; |
| ii. |
| the name, address, and telephone and facsimile numbers of the offeror (and electronic address if available); |
| iii. |
| a statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation and agreement to furnish any or all items upon which prices are offered at the price set opposite each item (to facilitate evaluation and direct comparison of received proposals, submitted proposals which do not unconditionally agree with all terms, conditions, and provisions included in the solicitation may be rejected and the Offeror may not be considered further for award); |
| iv. |
| names, titles, and telephone and facsimile numbers (and electronic addresses if available) of persons authorized to negotiate on the offeror’s behalf with the Government in connection with this solicitation; and |
| v. |
| name, title, and signature of person authorized to sign the proposal. Proposals signed by an agent shall be accompanied by evidence of that agent’s authority, unless that evidence has been previously furnished to the issuing office |
The Letter of Transmittal shall also include:
| i. |
| the name, telephone number, and electronic mail address of the Offeror’s assigned DCAA Auditor; |
| ii. |
| the name, telephone number, and electronic mail address of the Offeror’s assigned DCMA Administrative Contracting Officer; |
| iii. |
| the Offeror’s Dunn and Bradstreet (DUNS) number; |
| iv. |
| the Offeror’s Commercial and Government Entity (CAGE) code; |
| v. |
| a statement certifying electronic data submitted is free of computer viruses and other malware; |
| vi. |
| a statement certifying the proposal is valid for 180 days from the closing date of the solicitation; |
| vii. |
| a statement providing unconditional agreement with all terms, conditions, and provisions included in the solicitation; |
| viii. |
| any statement required by solicitation provision HQ L-2-0005 Notification of Potential Organizational Conflict(s) of Interest (NAVSEA) (JUN 1994); and |
| ix. |
| volume number and title (“Volume I – Pricing Proposal (Part 1 of X)”). |
The Letter of Transmittal shall serve as the cover letter for Volume I and a separate cover letter is neither required, nor desired.
2.2.2 Volume II shall each contain a cover letter containing:
| i. |
| Offeror name, address, and point of contact |
| ii. |
| Offeror point of contact phone number and electronic mail address |
| ii. |
| Offeror CAGE code and DUNS number |
| iii. |
| Title of proposal, proposal number, and RFP number (N00024-17-R-5369) |
| iv. |
| Volume number and title (e.g. “Volume II – Technical Proposal (Part 1 of X)”) |
2.2.3 To facilitate evaluation of each received proposal, Volume II should also include the following:
i. Table of Contents, Tables, and Figures. The Table of Contents should include the first through third level section titles. A separate list of tables and figures utilized in the proposal volume should be appended at the end of the Table of Contents.
ii. Glossary of Terms, Abbreviations, and Acronyms. The Glossary of Terms, Abbreviations, and Acronyms should include all utilized abbreviations, acronyms, and all terms which are either newly introduced, uncommon, or specialized.
2.2.4 Duplicated information within a given factor may be included in full once and referenced thereafter, as long as there is a clear reference to the duplicated information. If duplicated information is included for more than one evaluation factor, it must be included in full text the first time it is discussed under each factor.
2.2.5 A concise, legible, neat, orderly and comprehensive proposal is required. Brochuremanship is not desired. Elaborate brochures, artwork, expensive paper and bindings, or expensive visual or other presentation aids beyond those sufficient to present a complete and comprehensive written proposal are unnecessary. Elaborate brochures, artwork, expensive paper and bindings, or expensive visual or other presentation aids beyond those sufficient to present a complete and comprehensive written proposal will be included in enforcement of page count requirements. Clarity is essential.
2.2.6 Proposals must present information in sufficient depth for the Government to make a comprehensive evaluation of the Offeror’s understanding of, and capability to, meet the requirements of this solicitation. Offerors bear the burden of submitting a clear and unambiguous proposal that is fit for evaluation. Offerors shall provide all information necessary to demonstrate their ability to meet the requirements of the solicitation. Discussion of each factor in the proposal shall be self-contained (i.e., data shall be organized to enable Government personnel to thoroughly evaluate the proposal against specific factors established in Section M), and must be separated within each volume by a side tab file divider.
SECTION L 2.3
Paper submission
2.3.1 Each volume shall be bound separately in three ring binders and shall not exceed the page limitations cited above. Volumes I and II shall each be presented separate from the remainder of the proposal (i.e. each Volume shall be submitted in a single or multiple binders separately and discretely from all other volumes; no binder should contain material from more than one Volume). Discussion of each factor and subfactor within a binder shall also be separate and discrete, and shall be separated by a side tab file divider.
2.3.2 The Offeror’s company name, proposal number, and RFP number (N00024-17-R-5369) shall appear at the top of each page in the header section (from left to right). The date of submittal, page numbers and the corresponding electronic file name shall be placed on each page of the proposal in the footer section (from left to right).
2.3.3 Revisions (including but not limited to FPRs) will only be received and considered at the specific request of the Contracting Officer. Any pages revised must include the date of revision in the place of the date of submittal, and shall also contain a revision number (e.g. 12 Dec 2017 - Revision 1). Revisions shall be submitted in the form of change pages (allowing for substitution of the entire page—front and back if used—where the revision is located).
2.3.4 The narrative material in each proposal shall be single spaced, typed or printed in Times New Roman font with type no smaller than 12-point font. Paper, excluding foldout pages (see paragraph 2.3.5, below), shall be 8 1/2 x 11 inches with a minimum margin of 1 inch around the page. Any type contained within tables, graphs, etc. shall not be smaller than 8-point Times New Roman font.
2.3.5 Foldout pages (Foldouts) may be used for charts and graphs where necessary to depict organization, layout or implementation schedules. Foldouts shall be uncomplicated to preserve clarity. Written text or tabular data, beyond that which is reasonably required for clarity should not be included in the material presented on the foldout sheet. Foldouts shall fold entirely within the volume and shall be limited in size to no more than 11 x 17 inches. Each foldout shall contain printed material on only one side of the foldout. Each foldout page will be regarded as two pages for page count purposes.
2.3.6 The following items will not be considered pages for the purposes of page count limitations (but still shall conform to formatting requirements detailed herein):
| i. |
| Blank pages |
| ii. |
| Cover letters |
| iii. |
| Table of Contents, Tables, and Figures |
| iv. |
| Glossary of Terms, Abbreviations, and Acronyms |
| v. |
| Index of Terms |
| vi. |
| Integrated Master Schedule |
| vii. |
| Technical Proposal Cross-reference Matrix |
2.3.7 Only pages which count against page count limitations shall be numbered. Pages excluded from page count limitations (i.e. items in paragraph 2.3.6, above) must contain only material pertinent to the page heading and the page heading must clearly indicate the name of the item. Blank pages should be marked "Intentionally Left Blank." Pages submitted which are not excluded from page count limitations (i.e. items in paragraph 2.3.6, above), and which exceed the page count limitations provided in Section 2.1--Table 1 (e.g. any pages following the 10th page of the past performance section), will be removed and will not be evaluated.
2.3.8 Each submitted paper proposal page shall also include standard 2-3/4" center-to-center holes positioned symmetrically at the top of each page (i.e. 2-hole filebinder punch on top edge).
SECTION L 2.4
Electronic submission
2.4.1 Submitted electronic files shall not be compressed. Each Volume shall be submitted on a separate DVD, and a set of two DVDs (one for each Volume) constitutes an electronic copy of the proposal. Submission of two copies of the electronic proposal is required.
2.4.2 Included files shall be created/prepared using Microsoft Office 2010 compatible applications. Spreadsheets, worksheets, and workbooks shall be prepared using Microsoft Excel compatible applications. Schedules shall be created and submitted using Microsoft Project compatible applications. Graphics, photographs, and other data beyond the capability of Microsoft Office 2010 compatible applications may be submitted in Adobe Acrobat format. Submitted electronic files shall be limited to the following extensions:
| .docx |
| Microsoft Word |
| .xlsx |
| Microsoft Excel |
| .pptx |
| Microsoft PowerPoint |
| Adobe Acrobat |
| .mmpx |
| Microsoft Project |
2.4.3 Pricing information for the supplies and services solicited here shall only be included within the DVD containing Volume I: Price Proposal. Inclusion of pricing information on any other DVD may result in the Offeror’s proposal being rejected, and the Offeror being determined ineligible for award. If doubt exists as to what constitutes pricing information, Offeror’s are strongly encouraged to submit a question in accordance with paragraph 2.8 of this section.
2.4.4 Each submitted disc shall be labeled with the following:
| i. |
| “RFP N00024-17-R-5369” |
| ii. |
| Date of submittal |
| iii. |
| Volume number |
| iv. |
| Offeror name, address, and point of contact |
| v. |
| Offeror point of contact phone number and electronic mail address |
2.4.5 Audio or video shall not be included on any submitted DVDs. Inclusion of audio or video on any submitted DVD may result in the Offeror’s proposal being rejected, and may result in the Offeror being determined ineligible for award.
2.4.6 Electronic spreadsheets shall not be compiled or password protected; and all cells and formulas shall be visible, editable, and unprotected. Formulas shall be maintained in each Excel sheet to permit verification of calculations, and revision of output(s) through variation of inputs(s).
2.4.7 Any tables contained within submitted narrative must be capable of being edited (i.e. not embedded pictures or screenshots).
2.4.8 Submitted files shall not reference external data.
SECTION L 2.5
Proposal submission
2.5.1 Proposal submissions not conforming to submission requirements may not be evaluated, and the Offeror may be determined ineligible for award.
2.5.2 All copies of all proposal volumes shall be submitted at the place and on or before the date and time in Block 9 of the SF 33. All offerors shall mark each RFP package in accordance with Section L 2.5.3 (see below).
2.5.3 All proposals shall be marked as follows:
Commander
ATTN: RUFUS BROWN
NAVAL SEA SYSTEMS COMMAND
WASHINGTON NAVY YARD
1333 ISAAC HULL AVENUE S.E.
WASHINGTON, D.C. 20376
RFP: N00024-17-R-5369
DO NOT OPEN IN THE MAILROOM; CONTACT MR. RUFUS BROWN (202) 781-1451
SECTION L 2.6
Solicitation Package Proposal Content
SECTION L 2.6.1
Volume I (Pricing Volume) content Volume I of the proposal is the only volume which may include pricing information, and shall be used to evaluate Factor 4 – Total Price. Offered pricing shall be entered on Section B of the submitted Standard Form (SF) 33. Only pricing entered on Section B of the SF 33 will be considered when determining the Total price.
Volume I of submitted proposals shall include:
2.6.1.1 Letter of Transmittal. See paragraph 2.2.1, above, for a discussion of the content requirements for the Letter of Transmittal.
2.6.1.2 Standard Form 33, “Solicitation, Offer, and Award” (SF 33). The SF 33 must be completed entirely by the Offeror. Common mistakes include: (1) failing to complete all of blocks 12-18 on the first page, (2) failing to list pricing for all Contract Line Items (CLINs) in Section B, and (3) failing to fully complete SF 33, Section K.
i. To be considered for award, the Offeror must insert 120 days in Block 12 of the SF 33 to ensure adequate time for proposal evaluation and contract award.
ii. If the Offeror’s Representations, Certifications, and Other Statements of Offerors are available, active, and valid in the System for Award Management (SAM) (https://www.sam.gov); the Offeror may reference them in the Letter of Transmittal and decline to complete the portions of Section K of the SF 33 which are already present in SAM. The Offeror bears the burden of: (1) ensuring all information referenced in SAM is current accurate, and complete; and (2) ensuring any necessary information not present in SAM is provided within the Offeror’s proposal.
iii. Changes to any portion of the SF 33 not specifically requiring the input of information by the Offeror are prohibited. Red-lines, strikethroughs, additions, deletions, or any other changes not specifically required will be considered conditional agreement with solicitation terms, conditions, and provisions. An Offeror’s proposal which changes any portion of the SF 33 not specifically requiring the input of information by the Offeror may be rejected, and the Offeror furnishing the proposal may be determined ineligible for award.
SECTION L 2.6.2
Volume II (Technical Volume) content
Volume II shall not include pricing information. Volume II of the submitted proposal shall include:
2.6.2.1 Cover Letter. See paragraph 2.2.2, above, for a discussion of the content requirements for the Cover Letter.
2.6.2.2 Table of Contents, Tables, and Figures. See paragraph 2.2.3(i), above, for a discussion of the content requirements for the Table of Contents, Tables, and Figures.
2.6.2.3 Glossary of Terms, Abbreviations, and Acronyms. See paragraph 2.2.3(ii), above, for a discussion of the content requirements for the Glossary of Terms, Abbreviations, and Acronyms.
2.6.2.4 Executive Summary. The Executive Summary shall summarize the Offeror’s planned approach to satisfy the Government’s requirements. Key elements of the proposal shall be highlighted from both technical and management perspectives.
2.6.2.5 Technical Phase I Proposal. The Technical Phase I Proposal shall enable technical/engineering personnel to make a thorough evaluation and arrive at a sound determination of whether or not the proposal is technically acceptable. To this end, the Technical Phase I Proposal Volume shall be specific, detailed, and complete. Proposals shall include any block diagrams, flow diagrams, sketches, drawings, schematics, and interface descriptions required to describe the Offeror's proposed approach. The technical proposal must be sufficient to show how the Offeror proposes to comply with the Government's requirements and include a full explanation of the methodology and procedures to be followed. The technical Phase I proposal shall discretely address each of the following factors and subfactors (separated by side tab file dividers):
Factor 1 – Technical Approach
| Subfactor 1.1: Proposed Design and Manufacturing Plan |
| Subfactor 1.2: Data Rights Assertion |
| Subfactor 1.3: Integrated Master Schedule (IMS) |
Factor 2 – Management Approach Factor 3 – Past Performance
An extended description of desired proposal content is included below:
2.6.2.5.1 Technical Approach Proposal
Subfactor 1.1: Proposed Design and Manufacturing Plan
A. The Offeror shall provide a clear description of its proposed design for the FAUs, including a component list. The Offeror’s discussion of its design should be sufficient to demonstrate that the proposed design has a high likelihood of passing the acceptance testing described in the SOW upon initial delivery. The Offeror shall also describe its approach to performing factory test prior to delivery to the Government.
B. The Offeror shall provide a manufacturing plan, work breakdown structure (WBS), and work flowchart, based upon the requirements defined in Section C. The offeror’s manufacturing plan, WBS, and work flowchart shall demonstrate the offeror’s understanding of the requirements and ability to produce systems in accordance with the specifications and data contained in this solicitation. Specifically, the offeror shall include major process activities—beginning at contract award and continuing through acceptance of the final system—in the manufacturing plan and work flowchart to meet production requirements. The WBS should clearly and traceably provide an hours estimate of the design and manufacturing efforts the Offeror anticipates to perform the effort. The Offeror’s proposed design discussion should identify components or technologies the Offeror proposes to be leveraged from existing systems to meet the schedule.
C. The Offeror shall provide demonstration of experience as a prime contractor or subcontractor producing a system of similar size and complexity. The Offeror shall address the required technologies, equipment, and/or specialized skills proposed to build the MK 5 Velocimeter system configurations in accordance with the requirements. This should include—at a minimum—discussion of the following technologies used within the current velocimeter:
| • | Production assembly of a unit with external mounting, all-weather, and waterproof design consisting of an antenna, RF transmitter, receiver, and electronics required to measure and provide muzzle Initial Velocities (IVs) via a bi-directional RS-232 serial link |
| • | Ability to produce and utilize both Active and Passive Trigger Modes |
| • | Ability to monitor five operating RF channels and automatically select the frequency with the least noise |
D. The Offeror shall provide description of the Offeror’s system(s) for acquisition of material, material control, and monitoring delivery status of material previously ordered. The Offeror should also include a Bill of Materials (BOM) to include any Commercial-Off-The-Shelf (COTS) items that they will be starting from and also include, if applicable, a list of any hazardous material planned to be used within the system design. The Offeror shall describe their plans and processes to ensure complete compliance prior to acquiring material and prior to release of material for manufacturing. The Offeror shall address manufacturing processes, inspection, component level testing, and production acceptance testing.
E. The Offeror shall discuss the Offeror’s proposed configuration management and quality management of their proposed design. The Offeror shall provide specific examples supporting any claims made. Examples cited should include: a description of specific actions undertaken (e.g. production line and process updates, coordination with vendors, etc.), impact(s) on production, and outcomes.
F. The Offeror’s proposal shall describe the facilities, including the relevant tooling and equipment, the Offeror proposes to use to manufacture the delivered systems within the delivery schedule required.
Subfactor 1.2: Data Rights Assertion
The Data Rights Volume shall define how the Offeror will offer data rights for the work required by this solicitation. It shall describe in detail the proposed rights for hardware, software, and interfaces to be developed as required by this solicitation. The Data Rights Volume shall be limited to five (5) pages. Price information shall be completely omitted from the Data Rights in the Technical Proposal Volume.
It is the Government’s intent and goal that all non-commercial technical data (TD) and computer software/computer software documentation (CS/CSD), other than TD, CS, and CSD developed at Government expense, be delivered with Government Purpose Rights. If such non-commercial TD/CS/CSD contains elements generated previously with Offeror’s own capital, it is the Government’s intent that non-commercial TD/CS/CSD be delivered with a minimum of Government Purpose Rights (as defined in DFARS 252.227-7013 (MAR 2011) and DFARS 252.227-7014 (MAR 2011)). If the Offeror proposes to deliver commercial TD/CS/CSD, it is the Government’s desire to obtain a license to the commercial TD/CS/CSD that would grant the Government the equivalent of Government Purpose Rights. In the event an Offeror proposes to deliver any commercial or non-commercial TD/CS/CSD with less than such rights, the Government will evaluate the adverse impact on the Government’s ability to use, modify, release, or disclose such TD, CS, or CSD. The Data Rights offered (7017 list, 7028 list, and/or Supplemental Information—Noncommercial Technical Data, Noncommercial Computer Software, Noncommercial Computer Software Documentation) shall be provided as attachments to Volume II and will become Attachments to the Contract.
The Government will evaluate the degree to which the proposal meets the Government’s desired level of rights in TD, CS and CSD and enables the Government to adequately sustain the end item deliverables over their lifecycle including for maintenance, repair and upgrade. The Offeror shall describe how they will support the Government’s desire with respect to noncommercial Technical Data (TD) and Computer Software / Computer Software Documentation (CS/CSD).
Further, the Government will consider the adverse impact of less than Unlimited Rights/Government Purpose Rights in its best value determination. The Data Rights offered shall be incorporated into the successful Offeror’s contract upon award. The Offeror’s shall provide the following information as attachments to its offer:
| a. | Rights in Noncommercial TD, Noncommercial CS, and Noncommercial CSD. |
| i. | The 7017 List. The Offeror shall list all noncommercial TD, CS, and CSD that it asserts will be delivered with other than unlimited rights. Specific instructions and requirements concerning this list are set forth in the DFARS 252.227-7017 “Identification and Assertion of Use, Release, or Disclosure Restrictions” (Jun 1995) provision incorporated at Section K of this solicitation. If the Offeror does provide assertions, this paragraph shall also serve as the Contracting Officers request for Offeror submission of evidence and information to evaluate and validate listed assertions. Additionally, if there is no data or software to be identified in the 7017 list, the Offeror shall submit the list and enter "None" in the body of the list. If the Offeror is awarded a contract, the 7017 List shall be incorporated into the contract as an Attachment. |
| ii. | The 7028 List. The Offeror shall list all noncommercial TD, CS, and CSD that it intends to deliver with other than unlimited rights and that are identical or substantially similar to noncommercial TD, CS, or CSD that the Offeror has delivered to, or is obligated to deliver to, the Government under any contract or subcontract. Specific instructions and requirements concerning this list are set forth in the DFARS 252.227-7028 “Technical Data or Computer Software Previously Delivered to the Government” (Jun 1995) provision incorporated at Section K of this solicitation. Additionally, if there is no data or software to be identified in the 7028 list, the Offeror shall submit the list and enter "None" in the body of the list. If the Offeror is awarded a contract, the 7028 List shall be incorporated into the contract as an Attachment. |
| iii. | Supplemental Information. The Offeror shall include in its offer a statement, entitled “Supplemental Information—Noncommercial Technical Data, Noncommercial Computer Software, Noncommercial Computer Software Documentation” (the statement) that, for each item of noncommercial TD, CS, or CSD that the Offeror asserts should be delivered with specifically-negotiated license rights (as discussed at DFARS 252.227-7013 “Rights in Technical Data – Noncommercial Items” (NOV 1995) and/or DFARS 252.227- 7014 “Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation” (JUN 1995), sets forth a complete description of all such proposed restrictions on the Government’s ability to use, modify, release, perform, display, or disclose such TD, CS, or CSD. This information shall be provided by referencing and delivering any and all proposed license agreements that are attached to the statement. The Offeror shall submit the statement dated and signed by an official authorized to contractually obligate the Offeror. If there is no information to be included in the statement, the Offeror need not submit the statement. If the Offeror is awarded a contract, any statement provided will be incorporated into the contract as an Attachment. |
| b. | Rights in Commercial TD, Commercial CS, and Commercial CSD. |
| i. | The Offeror shall attach to its offer a list, entitled “Commercial Technical Data, Commercial Computer Software, and Commercial Computer Software Documentation-Government Use Restrictions” (the Commercial Restrictions List (CRL)), that the Offeror (including its sub-Offerors or suppliers, or potential sub-Offerors or suppliers, at any tier) intends to deliver with other than unlimited rights: (1) identification of the data or software; (2) basis for asserting restrictions; (3) asserted rights category; and (4) name of the person asserting restrictions. For any item designated as NDI, the Offeror is requested to provide details of the Agency and level therein that paid for development and the contract number(s) and dates wherein payments were received. For each entry in the list citing an asserted rights category other than the standard license rights applicable to commercial TD as set forth in the DFARS 252.227-7015 “Technical Data – Commercial Items” (Nov 1995) clause, the Offeror shall provide a complete description of the asserted rights (e.g., a specially negotiated license, or the license customarily offered to the public); this information may be provided by referencing any proposed nonstandard or commercial license agreement that is attached to the list, but in all cases, the non-standard or commercial license will be attached for Government review. The Offeror shall submit the Commercial Restrictions List as an attachment to its offer, dated and signed by an official authorized to contractually obligate the Offeror. If there is no information to be included in the Commercial Restrictions List, the Offeror shall submit the list and enter "None" as the body of the list. If the Offeror is awarded a contract, the Commercial Restrictions List shall be attached to the contract as an Attachment. |
| c. | Rights in Background Inventions. |
| i. | The Offeror shall provide a list, entitled "Background Inventions--Identification and Licensing" (the BIIL List), identifying all inventions described in and covered by any patents or pending patent applications in which the Offeror (1) has any right, title, or interest; and (2) intends to include in any items, components, or processes (ICP) to be developed or delivered under the resulting contract, or that are described or disclosed in any technical data (TD), computer software (CS), or computer software documentation (CSD) to be developed or delivered under the resulting contract. Such inventions are hereafter referred to as "background inventions." The BIIL List shall be made an attachment to the resulting contract, and shall be updated by the Offeror as necessary to identify all background inventions. |
For each background invention, the BIIL List shall identify (1) the invention, by (i) patent or application number, (ii) title of the patent or application, and (iii) issue date of the patent, or filing date of the pending application; (2) the ICP, TD, CS, and CSD that will include or disclose the invention; (3) the nature of the Offeror's right, title, or interest in the invention; (4) whether the Government, or any third party, has any right, title, or interest in the invention, and if so, the nature of such right, title, or interest; and (5) whether the Offeror is willing to sell to the Government a license to practice the invention, and if so, the precise terms of such license. To be of any interest or value to the Government, any such license should grant the Government the right to practice, or to have practiced on its behalf, the background invention(s) at least for Government purposes.
The BIIL List does not apply to, and shall not include, any "subject inventions," as that term is defined in the patent rights clauses of the contract (FAR 52.227-11, 52.227-12, and 52.227-13). Disclosure of, and rights in, subject inventions are governed by the appropriate patent rights clause.
If there are no background inventions to be identified in the BIIL List, the Offeror shall submit the list and enter "None" as the body of the list. However, the BIIL List may be updated after contract award by mutual agreement based on new information or inadvertent omissions, unless the inadvertent omission would have materially affected the source selection decision.
The Offeror's failure to identify a background invention in the BIIL List, as set forth above, shall constitute a grant to the Government of a nonexclusive, nontransferable, irrevocable, worldwide, paid-up license to practice, and to have practiced for or on its behalf, such invention for Government purposes.
As used in this section, the terms "Offeror" and "Offeror" include the Offeror's or Offeror's subcontractors, suppliers, and potential subcontractors or suppliers, at any tier; and "Government purposes" include any activity in which the United States Government is a party, including cooperative agreements with international or multi-national defense organizations, sales or transfers by the United States Government to foreign Governments or international organizations, and competitive procurement, but do not include commercial purposes.
Subfactor 1.3: Integrated Master Schedule (IMS)
The Offeror shall describe within an Integrated Master Schedule (IMS) its approach to ensure satisfaction of the delivery requirements of Section F, as well as First Article Test requirements. The Offeror shall provide an IMS demonstrating its ability to meet schedule, management activities, and delivery requirements. A direct and traceable correlation should exist between events in the IMS and SOW.
2.6.2.5.2 Management Approach Proposal
The Offeror shall demonstrate its ability to successfully manage a production program of similar scope and complexity. The Offeror shall describe within a Project Management Plan its approach to: maintaining project schedule, operating within approved budgets, meeting project milestones, early notification of potential problems, utilizing management metrics to track progress and trends, providing deliverables on-time, and maintaining ongoing operations in an effective manner.
2.6.2.5.3 Past Performance Proposal.
Recent and Relevant Performance Offerors shall provide at least three (3) recent and relevant contract efforts with their proposal using the format provided as Attachment 6 (Previous Contracting Efforts) with this solicitation. All contract efforts shall have been performed within the last three Government fiscal years (1 October 2014 – present). Offerors must also submit at least one (1) recent and relevant contract effort for each proposed subcontractor that performs more than ten percent (10%) of the total contract efforts. The contracts identified should demonstrate in-depth knowledge and successful performance of contracts, of similar size, scope and complexity to this solicitation. For each contract, the Offeror shall identify at least one of the following customer Points of Contact (POCs): Program Manager (PM), Procuring Contracting Officer (PCO), Administrative Contracting Officer (ACO), Contracting Officer’ s Technical Representative (COTR) or Contracting Officer’ s Representative (COR), Task Monitor. The Offeror shall provide the current address, phone number, FAX number, and email address for each POC.
Customer Assessments Offerors shall submit the Past Performance Questionnaire provided as Attachment 7 with this solicitation to each of their customer POCs identified in Attachment 6. In order to expedite the assessment process, the Offeror may complete the “Contract Information” portion of the Past Performance Questionnaire for the convenience of the customer POC. The Offeror shall not, however, complete any other section of the Past Performance Questionnaire. The questionnaire shall be provided to the customer POC with instructions to complete and submit it directly to the Contracting Officer on or before the proposal due date. Electronic submission by the customer is preferred; however, hardcopy mail or FAX will be accepted. The Government reserves the right to limit or expand the number of references it decides to contact and to contact other references than those provided by the Offeror.
Previous Contract Effort Narratives:
For each of the Past Performance Efforts submitted, the Offeror shall also provide a Previous Contracting Effort Narrative detailing the following information:
(a) Description of how the scope for the contract/task order relates to this effort in scope and complexity.
(b) Description of the significant achievements, challenges or obstacles that were encountered during contract performance and the measures taken to overcome them.
(c) Description of achievements for the most recent period for which performance measures have been applied to each contract. The performance measures should be specific and show the target performance levels that are set forth under the applicable contracts as well as the level of performance achieved. The Offeror shall describe the tools and/or methods used to collect metrics data and the frequency of data collection and reporting.
NOTE: The Government reserves the right to use contract performance data provided in the Offeror’s proposal and contract performance data obtained from other sources, such as the Contractor Performance Assessment Reporting System (CPARS) data base and from the points of contact identified by the Offeror in its proposal.
SECTION L 2.7
Offeror questions
2.7.1 Communications regarding this solicitation with any Government personnel other than the point of…
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 .