N6133115R0009-0001.pdf
PDF 99 KB Posted
- Solicitation number
- N61331-15-R-0009
About this file
N61331-15-R-0009-0001
View the file
Other files
| File | Type | Posted |
|---|---|---|
| N6133115R0009-0004.pdf | ||
| N6133115R0009-0003.pdf | ||
| J.1_Exhibit_A.pdf | ||
| N6133115R0009-0002.pdf | ||
| CDRLs.pdf | ||
| Section_J_Cost.xlsx | XLSX spreadsheet | |
| personnel_qualifications.pdf | ||
| N6133114R0009_RFP.pdf |
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
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
See page 2 herein for changes.
1. CONTRACT ID CODE PAGE OF PAGES
S 1 17
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 06-Feb-2015
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N61331-15-R-0009
X 9B. DATED (SEE ITEM 11)
28-Jan-2015
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning 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
06-Feb-2015
CODE
NSWC PANAMA CITY (M. DAVIDSON)
MARLENE.DAVIDSON1@NAVY.MIL
850-230-7084
110 VERNON AVE.
PANAMA CITY FL 32407-7001
N61331 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
N61331-15-R-0009
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION SF 30 - BLOCK 14 CONTINUATION PAGE
The following have been added by full text:
SUMMARY OF CHANGES
The purpose of this amendment to Solicitation N61331-15-R-0009 is to effect the following changes:
1. SECTION B - SUPPLIES OR SERVICES AND PRICES
a) Change the deliverable of CLIN 0003 Travel, from the delivery to period of performance.
b) Renumber Contract Data Requirement List CLIN 0004 to CLIN 0005 and add the verbiage “Not
Separately Priced” in the line item description
c) Incorporate CLIN 0004, Mission Planning and Object Database Software- Firm Fixed-Price
2. SECTION C - DESCRIPTIONS AND SPECIFICATIONS
a) Statement of Work, new point of contact for this effort is Luis Gely, luis.gely@navy.mil.
3. SECTION E - INSPECTION AND ACCEPTANCE
a) Add FAR clauses as follows:
a. 52.246-2 Inspection Of Supplies--Fixed Price
b. 52.246-3 Inspection Of Supplies Cost-Reimbursement
c. 52.246-5 Inspection Of Services Cost-Reimbursement
4. SECTION F - DELIVERIES OR PERFORMANCE
a) Establish the delivery date of CLIN 0004 at 24 months.
5. SECTION I - CONTRACT CLAUSES
a) Add FAR and DFARS clauses as follows:
a. 52.217-7 Option For Increased Quantity-Separately Priced Line Item
b. 252.225-7015 Restriction on Acquisition of Hand or Measuring Tools
c. 252.225-7016 Restriction on Acquisition of Ball and Roller Bearings
d. 252.227-7017 Identification and Assertion of Use, Release, Or Disclosure Restrictions
e. 252.225-7019 Restriction on Acquisition of Anchor and Mooring Chain
f. 252.225-7025 Restriction on Acquisition of Forgings
g. 252.225-7027 Restrictions on Contingent Fees for Foreign Military Sales
h. 252.227-7028 Technical Data or Computer Software Previously Delivered to the Government
i. 252.225-7037 Evaluation of Offers for Air Circuit Breakers
b) Delete previously incorporated FAR and DFARS clauses as follows:
a. 52.227-14Rights in Data—General
b. 252.227-7013Rights in Technical Data – Noncommercial Items
6.Section J- List of Documents, Exhibits, and other Attachments
a. J.5 is replaced with a new attachment.
6. SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
a) Change title of the proposal’s Volume III from price proposal to cost proposal.
b) Instructions of new point of contact for this effort’s General Information and Statement of Work, Proposal
Classifications and Distribution sections, is Luis Gely, luis.gely@navy.mil.
c) Update the CLIN structure on paragraph 3.0 Volume III to reflect the changes under Section B of this amendment.
SECTION B - SUPPLIES OR SERVICES AND PRICES
CLIN 0004
This CLIN has been renumbered to CLIN 0005.
The CLIN extended description NOT SEPARATELY PRICED. Technical Data in accordance with the SOW and Section J, Exhibit A. has been added.
CLIN 0004 is added as follows:
ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT
0004 1 Each
OPTION MISSION PLANNING AND OBJECT DATA BASE
FFP
SOFTWARE. The offeror shall proposed Mission Planning and Execution Software (MPE) in accordance with the SOW par. 3.12 FOB: Destination
NET AMT
SECTION C - DESCRIPTIONS AND SPECIFICATIONS
STATEMENT OF WORK
Offerors requesting a copy of the SOW shall contract the POC:
Contract Specialist: Luis Gely Email: Luis.Gely@navy.mil
SECTION E - INSPECTION AND ACCEPTANCE
The following Acceptance/Inspection Schedule was added for CLIN 0004:
INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY
N/A N/A N/A Government
The following have been added by reference:
52.246-2 Inspection Of Supplies--Fixed Price AUG 1996 52.246-3 Inspection Of Supplies Cost-Reimbursement MAY 2001 52.246-5 Inspection Of Services Cost-Reimbursement APR 1984
SECTION F - DELIVERIES OR PERFORMANCE
The following Delivery Schedule Item has been deleted from CLIN 0004:
DELIVERY DATE QUANTITY SHIP TO ADDRESS UIC
2 yrs. ADC N61331
NSWC PANAMA CITY
C/O NSA PC - N61008
101 VERNON AVENUE
PANAMA CITY BEACH FL 32407-7001
N61331
The following Delivery Schedule item has been added to CLIN 0004:
DELIVERY DATE QUANTITY SHIP TO ADDRESS UIC
24 mths. ADC 1 N61331
NSWC PANAMA CITY
C/O NSA PC - N61008
101 VERNON AVENUE
PANAMA CITY BEACH FL 32407-7001
N61331
SECTION I - CONTRACT CLAUSES
The following have been added by reference:
52.217-7 Option For Increased Quantity-Separately Priced Line Item MAR 1989 252.225-7015 Restriction on Acquisition of Hand Or Measuring Tools JUN 2005 252.225-7016 Restriction On Acquisition Of Ball and Roller Bearings JUN 2011 252.225-7019 Restriction on Acquisition of Anchor and Mooring Chain DEC 2009 252.225-7025 Restriction on Acquisition of Forgings DEC 2009 252.225-7027 Restrictions on Contingent Fees for Foreign Military Sales APR 2003 252.225-7037 Evaluation of Offers for Air Circuit Breakers JUN 2005
252.227-7017 IDENTIFICATION AND ASSERTION OF USE, RELEASE, OR DISCLOSURE
RESTRICTIONS. (JAN 2011)
(a) The terms used in this provision are defined in following clause or clauses contained in this solicitation--
(1) If a successful offeror will be required to deliver technical data, the Rights in Technical Data--Noncommercial Items clause, or, if this solicitation contemplates a contract under the Small Business Innovation Research Program, the Rights in Noncommercial Technical Data and Computer Software--Small Business Innovation Research (SBIR) Program clause.
(2) If a successful offeror will not be required to deliver technical data, the Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation clause, or, if this solicitation contemplates a contract under the Small Business Innovation Research Program, the Rights in Noncommercial Technical Data and Computer Software--Small Business Innovation Research (SBIR) Program clause.
(b) The identification and assertion requirements in this provision apply only to technical data, including computer software documents, or computer software to be delivered with other than unlimited rights. For contracts to be awarded under the Small Business Innovation Research Program, the notification requirements do not apply to technical data or computer software that will be generated under the resulting contract. Notification and identification is not required for restrictions based solely on copyright.
(c) Offers submitted in response to this solicitation shall identify, to the extent known at the time an offer is submitted to the Government, the technical data or computer software that the Offeror, its subcontractors or suppliers, or potential subcontractors or suppliers, assert should be furnished to the Government with restrictions on use, release, or disclosure.
(d) The Offeror's assertions, including the assertions of its subcontractors or suppliers or potential subcontractors or suppliers shall be submitted as an attachment to its offer in the following format, dated and signed by an official authorized to contractually obligate the Offeror:
Identification and Assertion of Restrictions on the Government's Use, Release, or Disclosure of Technical Data or Computer Software.
The Offeror asserts for itself, or the persons identified below, that the Government's rights to use, release, or disclose the following technical data or computer software should be restricted:
Technical Data or Computer Name of Person Software to be Furnished Asserting With Restrictions * Basis for Assertion ** Asserted Rights Category *** Restrictions ****
(LIST) ***** (LIST) (LIST) (LIST)
*For technical data (other than computer software documentation) pertaining to items, components, or processes developed at private expense, identify both the deliverable technical data and each such items, component, or process. For computer software or computer software documentation identify the software or documentation.
**Generally, development at private expense, either exclusively or partially, is the only basis for asserting restrictions. For technical data, other than computer software documentation, development refers to development of the item, component, or process to which the data pertain. The Government's rights in computer software documentation generally may not be restricted. For computer software, development refers to the software. Indicate whether development was accomplished exclusively or partially at private expense. If development was not accomplished at private expense, or for computer software documentation, enter the specific basis for asserting restrictions.
***Enter asserted rights category (e.g., government purpose license rights from a prior contract, rights in SBIR data generated under another contract, limited, restricted, or government purpose rights under this or a prior contract, or specially negotiated licenses).
****Corporation, individual, or other person, as appropriate.
*****Enter "none" when all data or software will be submitted without restrictions.
Date __________________________________________________
Printed Name and Title ________________________________
Signature _____________________________________________
(End of identification and assertion)
(e) An offeror's failure to submit, complete, or sign the notification and identification required by paragraph (d) of this provision with its offer may render the offer ineligible for award.
(f) If the Offeror is awarded a contract, the assertions identified in paragraph (d) of this provision shall be listed in an attachment to that contract. Upon request by the Contracting Officer, the Offeror shall provide sufficient information to enable the Contracting Officer to evaluate any listed assertion.
(End of provision)
252.227-7028 TECHNICAL DATA OR COMPUTER SOFTWARE PREVIOUSLY DELIVERED TO THE
GOVERNMENT (JUN 1995)
The Offeror shall attach to its offer an identification of all documents or other media incorporating technical data or computer software it intends to deliver under this contract with other than unlimited rights that are identical or substantially similar to documents or other media that the Offeror has produced for, delivered to, or is obligated to deliver to the Government under any contract or subcontract. The attachment shall identify--
(a) The contract number under which the data or software were produced;
(b) The contract number under which, and the name and address of the organization to whom, the data or software were most recently delivered or will be delivered; and
(c) Any limitations on the Government's rights to use or disclose the data or software, including, when applicable, identification of the earliest date the limitations expire.
(End of clause)
The following have been deleted:
52.227-14 Rights in Data--General MAY 2014 252.227-7013 Rights in Technical Data--Noncommercial Items FEB 2014
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been modified:
INSTRUCTIONS
I. NOTIFICATION OF POTENTIAL ORGANIZATIONAL CONFLICT(S) OF INTEREST (NAVSEA)
(JUN 1994)
(a) Offerors are reminded that certain existing contractual arrangements may preclude, restrict or limit participation, in whole or in part, as either a SubContractor or as a prime Contractor under this competitive procurement. Of primary concern are those contractual arrangements in which the Offeror provides support to NSWC PCD or related laboratories (if applicable), in support of operation of the office or any of its programs. General guidance may be found in FAR 9.505; however, this guidance is not all inclusive. The Offeror's attention is directed to the "Organizational Conflict of Interest" (or similar) requirement which may be contained in current or completed contract(s) which prohibits the prime or SubContractor from providing certain supplies or services to the Government as described above during the period of the current "support" contract(s) or for a period after completion of the "support" contract(s). Notwithstanding the existence or non-existence of an Organizational Conflict of Interest (OCI) clause or similar requirement in current or completed contract(s), the Offeror shall comply with FAR 9.5 and identify whether an OCI exists and not rely solely on the presence of an OCI requirement.
(b) If a potential conflict of interest exists at any tier, each potential prime Offeror is requested to notify the Contracting Officer within 14 days of the date of this solicitation. The Offeror shall provide: (1) the contract number and name and phone number of the Contracting Officer for the contract which gives rise to a potential organizational conflict of interest; (2) a copy of the requirement; (3) the statement of work (or technical instruction) from the existing contract; (4) a brief description of the type of work to be performed by each SubContractor under the competitive procurement; and (5) any additional information the Contracting Officer should consider in making a determination of whether a conflict of interest exists. The Government may independently verify the information received from the Offeror. Notwithstanding the above, the Government reserves the right to determine whether a conflict of interest exists based on any information received from any source.
(c) The Government will notify an Offeror of any conflict of interest within 14 days of receipt of all required information. Those Offerors deemed to have a conflict of interest may be ineligible for award. Failure to provide the information in a timely manner does not waive the Government's rights to make a conflict of interest determination.
The Offeror is notified that if it expends time and money on proposal preparation, such expenditure is at its own risk that the Government will not determine that an organizational conflict of interest exists.
(d) Any potential prime Contractor which proposes a SubContractor later determined to have a conflict of interest and deemed ineligible to participate in the current competition, may not be granted the opportunity to revise its proposal to remove the ineligible SubContractor. The Government reserves the right to determine which Offerors remain in the competitive range through the normal source selection process.
(e) If the Offeror determines that a potential organizational conflict of interest does not exist at any tier, the Offeror shall include a statement to that effect in its response to this solicitation.
II. NOTICE TO OFFERORS
Your proposal shall be prepared and submitted as follows:
Submit volumes as indicated below:
VOLUME VOLUME TITLE QUANTITY CD-ROM ADD’L COPIES
I Solicitation, Offer, and Award 1 1 1 II Technical Proposal 1 1 6 III Cost Proposal 1 1 1
Each volume must be separately bound and contain sufficient information to permit a detailed evaluation. Previously submitted data, if any, will not be used in the evaluation of your response to the Request For Proposal (RFP).
Previously submitted data should not therefore be included in your proposal “by reference”.
1. General Information
The Offeror’s proposal shall be based on the technical and contractual requirements contained in this RFP (including those documents, exhibits, and other attachments to the RFP identified in Section J). Offerors are required to submit a price proposal encompassing all items listed in Section B herein. Proposals submitted on any other basis may be rejected. The Offeror shall submit all information required by this RFP including the required Certifications addressed in Section K. Each Offeror shall submit only one fully compliant offer.
Offerors may submit written questions requesting clarification of solicitation requirements. It is requested that all questions be received within ten (10) days after release of the RFP to allow the Navy adequate time to prepare and issue responses to all Offerors prior to the date and time set for receipt of proposals. The Navy will continue to accept questions up to the closing date and time of the solicitation; however, time may not permit responses to be issued prior to proposal receipt for questions received after the time set forth above. Only questions transmitted electronically will receive a response. It is the Government’s intention that questions and responses will be distributed electronically to all Offerors. Information provided with each question should include the document name, document date, specific page, paragraph, clause or other definitive citation requiring clarification. All questions shall be directed to:
Luis Gely NSWC PC, Code 022 110 Vernon Ave Panama City, FL 32407 Telephone No. (850) 234-4296 Email: Luis.Gely@navy.mil
2. Statemet of Work (Attachment J.2.) and Specifications (Attachment J.3)
Potential Offerors shall submit a request for the Statement of Work and Specifications to the POC: Luis Gely, Code: 022, 110 Vernon Avenue, Panama City, FL 32407 or by email:Luis.Gely@navy.mil.. Requests must be received within ten (10) days after release of the RFP to allow the Navy adequate time to confirm security clearance and delivery. In the request, the Offeror shall provide their physical address, classified address, cage code, and a point of contact for the requested documents. Potential Offerors will receive the documents in electronic format via mail. All documents and/or drawing(s) received by potential Offerors shall be returned to address listed below within 10 days of the solicitation closing date.
Naval Surface Warfare Center Panama City Division (NSWC PCD) Attention: William Divine, Code X24
110 Vernon Avenue, Building 110 Panama City, FL 32407
The Documents should be marked:
RFP N61331-15-R-0009
DO NOT OPEN IN MAIL ROOM
ATTN: William Divine Code X24, Building 110
Reproduction or destruction of the documents provided by the Government is not authorized without written authorization from the Procurement Contracting Officer.
3. Proposal Format
The proposal shall be submitted in Three (3) volumes as indicated below.
Volume Title Elec. Copies Page Limit I Solicitation, Offer, and Award 1 None II Technical Proposal 1 75 III Cost Proposal 1 None
* If any amendments to the solicitation are issued the Offeror must ensure that such amendment(s) are signed, dated, returned and acknowledged in Block 14 of the SF 33 (Section A).
The proposal shall be in Microsoft Office 2007 compatible files or Adobe pdf files for documentation where Microsoft Office file formats are incompatible.
A date shall be placed on each page of the proposal corresponding to the date of the initial proposal. Any pages that may be revised as a result of discussions (if required) shall contain revision numbers and dates.
For the purposes of compliance with the page limitation, classified information (if applicable) shall be supplied separately as a supplement and added at the end of the technical volume. The page count shall include all material with printed matter and figures unless otherwise noted herein. Those pages excluded from the page count must contain only material pertinent to the page heading. The Cost Volume shall contain only information relative to the cost. The page count shall not include:
a. Cover Page
b. Executive Summary (limited to 5 pages)
c. Title Pages
d. Table of Contents
e. Lists of Figures, Tables, Illustrations and Appendices
f. Tab Pages
g. Matrices
h. Other material specifically cited as excluded
i. Key Personal Resume
The narrative material in the proposal shall be in Times New Roman font with the type no smaller than 12 point. A page is defined as one side of a sheet 8 ½ inches by 11 inches. Oversize pages are to be fold out format, with each fold out counted as a single page. Fold out pages may be used for diagrams, charts or graphic material only and may not exceed 11 inches by 34 inches. Fold out pages may only include narrative sufficient to describe the diagram, chart or graphic material. Fold out pages are limited to 20 pages. Pages in excess of the maximum page count will be removed prior to the evaluation. Proposal material shall be in a single column on each page and shall print double-sided pages. (Refer to Section I, FAR 52.204-4).
The text shall be double-spaced with minimum margins as follows:
Left Hand 1.0 inch Right Hand 1.0 inch Top 0.5 inch Bottom 0.5 inch
Each volume of the proposal shall be bound in three ring binders to permit removal of sections with each major part tabbed. The Offeror’s company name shall appear at the top of each page and all pages shall be numbered.
The cover page of each volume shall contain:
a) The document number and title (Vol. I – Solicitation, Offer, and Award, Vol. II – Technical Proposal, or Vol. III – Price Proposal);
b) The solicitation number of the Request For Proposal (RFP);
c) The full company name of the Offeror;
d) The address, point of contact and phone number for the Offeror;
e) The Offeror’s position regarding disclosure of proposed data in accordance with the provision entitled
“Restrictions on Disclosure and Use in Proposals”.
No cost/price information shall be submitted in the Technical Volume or in the forwarding letter for the proposal. All price information shall be submitted in the Price Volume only, in a separate file.
4. Proposal Classifications and Distribution
The classification of this proposal shall not be higher than SECRET, with Volumes I and III being unclassifed.
The classification of the TDD hardware and Technical Data is SECRET. If the Offeror needs to provide SECRET material, it shall be submitted as a supplement to the Technical Volume, included in the page count, and handled in accordance with appropriate security procedures.
The Offeror shall separately package and mark each volume and any supplements thereto with the solicitation number.
All originals and copies of the Solicitation, Offer, and Award (Volume I) and the Price Proposal (Volume III), including all amendments, shall be sent at the same time to:
Attention: Luis Gely, Code 022 110 Vernon Avenue, Building 372
The Vol I. and Vol. III proposal packages should be marked:
RFP N61331-15-R-0009
DO NOT OPEN IN MAIL ROOM
ATTN: Luis Gely Code CDC1, Building 372
All originals and copies of the Technical Proposal (Volume II) shall be sent at the same time to:
Attention: William Divine, Code X24 110 Vernon Avenue, Building 110
The Technical Proposal packages should be marked:
RFP N61331-15-R-0009
DO NOT OPEN IN MAIL ROOM
ATTN: William Divine Code X24, Building 110
III. GENERAL CONTENT REQUIREMENTS
This section delineates general information and requirements to be followed in the preparation of the proposal.
If the requirements of proposal content, general or specific are not met, an Offeror’s proposal may be determined ineligible for further consideration in the competition.
Proposals submitted shall be sufficiently detailed to enable project management, engineering, logistics and contracting personnel to make a thorough evaluation of the proposal by factor, and to arrive at a sound determination as to whether and how well the Offeror will be able to perform in accordance with the requirements of the RFP.
The proposal must be sufficiently complete to demonstrate how the Offeror proposes to comply with the requirements of the RFP. Legibility, clarity, and compliance to the requirements of the RFP are essential.
Failure to provide the requested information will adversely affect proposal evaluation. “Brochuremanship” is not desired. Clarity, completeness and conciseness are essential and the overall quality of the proposal will be evaluated in the context of being representative of the Offeror’s capabilities. Data previously submitted, or presumed to be known (i.e., previous projects performed for NAVSEA) may not be considered as part of the proposal unless physically incorporated therein.
In the event that someone who is not a bona fide employee of the Offeror who is submitting the proposal writes a portion of the technical proposal, a responsible officer of the Offeror shall sign a certificate to this effect. The certificate shall show the person’s name, employment capacity, the name of his firm, the relationship of that firm to the Offeror’s, and the portion of the technical proposal written by that person.
Proposals submitted in response to this RFP must contain a precise description of all terms and conditions of the services to be offered by the Offeror. The format and content of the proposal shall contain a response to the topics of discussion noted below. Information presented shall appear in the same order as outlined below.
IV. PROPOSAL CONTENT
(1) Volume I – Solicitation, Offer, and Award Documents (SF 33 – RFP)
(a) This document, which may be used as part of the contract award document, shall be fully executed and returned as a separate document from the technical/management and price proposal. Special attention should be taken to accurately enter the prices required in Section B, complete all RFP fill-ins by Section, complete all Representations and Certifications in Section K and ensure that an authorized person signs the offer in Block 17 of Page 1. If any amendments to the solicitation are issued the Offeror must ensure that such amendment(s) are signed, dated, returned and acknowledged in Block 14 of the SF 33 (Section A). This document shall not be embellished with any covers or binding.
(b) This volume must contain a certification that it contains all exceptions, deviations, and waivers that the Offeror takes from the provisions of the RFP and its applicable documents. An exception is where an Offeror states it will not comply with a requirement, usually involving contract terms and conditions. A deviation is where an Offeror states it will not comply with a requirement, usually involving a specification. A waiver is where an Offeror requires authorization for the government to accept an item, which will depart from specified requirements but would nevertheless be considered suitable. Exceptions, deviations or request for waivers may cause proposals to be considered unacceptable.
Provide a detailed description for each exception, deviation, or waiver. Indicate the Offeror’s difficulty with the applicable requirements and the Offeror’s proposed solution. Specifically, identify the portion of the RFP and the Offeror’s proposal, which are affected.
(2) Volume II - Technical Proposal
The Technical Proposal shall be specific and complete so as to clearly demonstrate to the Government that the Offeror has a thorough comprehension of and capabilities to perform all aspects of the solicitation requirements including technical, product assurance, fabrication, management, availability and reliability objectives, and resource requirements as well as all other provisions of this solicitation. Statements that the Offeror understands the problem and can or will comply with the requirements will be considered inadequate, as will statements such as “straight-forward development/fabrication techniques” or “the highest quality control procedures.” It is required that all pertinent factors be detailed. Clarity and completeness are essential. The proposal shall not simply rephrase or restate the Government’s requirements but shall provide convincing rationale to address how the Offeror intends to meet these requirements. Specifically, the proposal shall discuss in detail the Offeror’s technical superiority in accomplishing the requirements of this solicitation, and shall detail its proposed approach for meeting those requirements. This volume should also identify areas of potential risk to the achievement of the solicitation requirements. The Offeror shall identify the degree of risk involved in each area and describe a plan to mitigate the risk.
2.1 Executive Summary
This section shall highlight the Offeror’s approach to this acquisition, its key capabilities, and the general features of the Offeror’s resources. Experience and understanding of the technical efforts required by this solicitation should also be summarized herein. In addition, the Offeror should clearly indicate the technical reasons why the contract should be awarded to the Offeror. The Executive Summary shall be limited to five pages and is not included in the Technical proposal page limitation. The Executive Summary will not be evaluated.
2.2 Reserved
2.3 VOLUME II - TECHNICAL PROPOSAL REQUIREMENTS
The Technical Proposal shall consist of the sections as detailed below. The Offeror must use the same numbering scheme for the sections as the ones used below.
FACTOR 1 – DESIGN MATURITY
Design maturity is a continuum ranging between the extremes of concept formulation (immature) and multiple end items in current operation (mature). As defined above, a Bathymetric Measuring System Sensor (BMSS) existing only on paper is immature. A BMSS, exactly as proposed, having had multiple operational end items produced is considered fully mature.
Discuss where the proposed BMSS and support systems and equipment fall on the continuum of design maturity. If a derivative of a parent system, also discuss where the parent system falls on the continuum of design maturity. Quantify maturity determinations by providing evidence. Key elements of the BMSS are the swath bathymetry/imagery sonar, gap filler bathymetry/imagery sonar, if applicable, and the integrated navigation system. Evidence pertinent to the key elements should consist of:
Fielded systems performance data, Full scale performance data, Scale-model performance data, or
Calculation/analysis data.
The preceding data is listed in order of significance (i.e. Fielded systems performance data is more significant than full scale performance data, which is more significant than scale-model performance data, which is more significant than calculation/analysis data). Include all end items claimed to substantiate design maturity for the proposed BMSS as a whole or for any of its components or systems.
System performance data is defined as:
Collected data sets that demonstrate the proposed system’s (or derivative parent system’s) ability to meet the bathymetry/imagery resolution and integrated navigation accuracy requirements.
The ability to process and display the swath bathymetry/imagery sonar, gap filler bathymetry/imagery sonar, if applicable, and the integrated navigation system information in real time.
The ability to process and display the ancillary functions as defined in the performance specification.
If the proposed BMSSS solution is a derivative of a parent system, provide a complete set of drawings, data, calculations, and schematics which clearly demonstrate the design, construction, and performance of the parent system.
FACTOR 2 - TECHNICAL COMPETENCE AND UNDERSTANDING
The Offeror shall provide a clear and concise technical approach to meeting each of the requirements contained in the performance specification. Each offer shall demonstrate an understanding of the requirements and state how the work will be accomplished. The Offeror shall describe the buildings, equipment, software and communications facilities and resources which will be applied to performance of the order and describe how the proposed facilities/resources support the requirements specified in the performance specification. A schedule shall be included that shows key milestones.
FACTOR 3 – STAFFING AND KEY PERSONNEL
(a) Key Personnel Resumes Resumes are required for Key Personnel. Resumes shall not exceed 2 pages in length. Offerors may supplement each 2-page resume with information that sets forth work experience and qualifications that are directly related to this requirement. Key Personnel for this effort include:
Program Manager
Systems Engineer
Sonar Engineer
Navigation Engineer
It is the Offeror’s responsibility to provide information and evidence that clearly demonstrates the ability of proposed personnel to satisfactorily fulfill the contract requirements. Do not provide any information that would violate the Privacy Act. If the employee is not a current employee of the Offeror (or a proposed subcontractor), a copy of the accepted offer letter shall be provided. An additional copy of this letter shall be provided in the Cost Proposal which identifies a projected start date and the agreed to annual salary.
Resumes shall contain the following information:
1. Years of Experience
2. Name/Current Position/Title/Company
3. Educational and professional development history
4. Chronology of professional experience with emphasis on performance specification related experience
(b) Staffing Plan
The Offeror shall provide a matrix (key and non-key personnel) demonstrating how the proposed personnel shall support task areas described in the performance specification with their man-year allocation. Include name, company name, years with the company, primary work location, contract labor category, years of applicable professional experience, percent of time proposed, proposed task area assignments, level of security clearance, resume page number (if applicable). It is not necessary to duplicate information for Key Personnel in the matrix that was provided in a resume. The Offeror shall describe their proposed organizational structure and the responsibilities of proposed individuals. The Offeror shall describe the breadth and depth of its corporate knowledge base as it applies to this requirement and the ability to bring this corporate knowledge to bear on the tasks covered by the performance specification. Do not provide any information that would violate the Privacy Act.
(c) Subcontracting/Teaming/Consulting Agreements A copy of any subcontracting/teaming/consulting agreements proposed to fulfill any direct charged part of the contract shall be provided. It shall be signed by both the Offeror and the proposed subcontractor/team member/consultant and shall show agreement as to the specific technical work areas to be subcontracted, the projected labor categories (key/non-key/support) to be provided, and the level of effort to be provided. It shall be fully consistent with other portions of the proposal to include resumes submitted and the Cost Proposal.
Agreements shall be submitted only for those subcontractors or consultants who are priced in the Cost Proposal.
This documentation is not to be included in the technical proposal page limitation.
FACTOR 4 - PAST PERFORMANCE
The Offeror shall complete Table L-1 below, and submit the information as part of the proposal in Volume 2. Please note that this form is a summary of the Prime’s relevant contract data. Contracts detailed in this volume should be consistent with the contracts identified.
1 Contractor Name:
2 Cage Code:
3 Contract Number:
4 Contract Type:
5 Dollar Amount:
6 Period of Performance:
7 Procuring Agency:
8 Brief Description of Work or Responsibility:
9 Points of Contact
Name:
Phone:
Email:
10 Contracting Officer (PCO/ACO)
Name:
Phone:
Email:
The Offeror shall provide up to three past performance references that reflect recent, relevant experience within the last five years that demonstrate the Offeror’s ability to handle the scope and breadth of the performance specifications for this contract. Include the following information for each past performance reference: contract/Contract number, contract type, program name, total contract cost, short description of work performed, description of how the work performed is relevant to the requirements, names and valid phone number, e-mail address, and mailing address for the Procuring Contracting Officer (PCO) (or equivalent), Contracting Officer’s Representative (COR) (or equivalent) and Program Manager (PM) (or equivalent). Other development activities such as Independent Research and Development (IRAD), cooperative agreements and no cost contracts or the like could be provided as past performance if they demonstrate relevant experience of the magnitude required for this contract. If the Offeror does not provide three past performances during the last five years, the Offeror shall address this and provide a written narrative detailing the reasons for not providing three references.
The relevancy of Offeror’s past work and how this experience will assist in performing under this contract shall be explained in detail. Offerors are advised that:
(1) The Government may contact any or all references in the proposal and third parties (such as other customers, the DoD Past Performance Information Retrieval System (PPIRS), Contractor Performance Assessment Reporting System (CPARS), other Government contractors, the Environmental Protection Agency, the Department of Labor, consumer protection organizations, etc.) for performance information
(2) The Government reserves the right to use any such information received as part of its evaluation of the Offeror’s past performance
(3) The Government reserves the right to directly solicit input on the Offeror’s past performance from any other sources and the Government may use any other data available to its evaluators, including the personal knowledge of those individuals
(4) If the Offeror omits projects of which the Government evaluation team is aware or becomes aware, customer assessments may be sought from the relevant organization.
The Government reserves the right to limit or expand the number of references it contacts and to contact references other than those provided by the Offeror. If subcontracting is proposed for the requirement, past performance references where the Offeror has served as a prime Contractor with Subcontractors would be of interest.
3.0 Volume III – Cost Proposal (FACTOR 6 – Cost)
Proposals submitted on the basis other than the cost types listed below would be considered ineligible for award.
The price proposal includes the signed SF 33 with the pricing of all CLINs provided in Section B. Any inconsistencies between the proposed amount in Section B and Section J- Cost Summary Section, the Government shall use the total price proposed in Section B in arriving to the total evaluated price.
1. CLIN 0001- The Offeror shall provide a Cost-Plus-Fixed-Fee for the “Manpower, materials, and facilities to develop, fabricate, and integrate the Bathymetric Measuring System Sensor (BMSS) for the production representative EDM for Fleet evaluation as described in the Statement of Work and Specifications.” The projected start date is July 2015 for a period performance of two (2) years.
2. CLIN 0002- Engineering Services- Cost Plus-Fixed Fee for the 2,000 hours estimated. The Offeror is reponsible for proposing the hours per labor mix.
3. CLIN 0003- Travel (Cost Only). The Offeror shall propose $100,000 as a Not to Exceed (NTE) unburdened amount for travel support of CLIN 0001. Travel will be negotiated in accordance with the Department of Defense’s Joint Travel Regulations on a cost only basis as needed during the contract period of performance.
4. CLIN 0004- MPE- Firm Fixed-Price. The Offeror shall proposed in accordance with the SOW para. 3.12
5. CLIN 0005- Contract Data Requirement List (CDRL) – Not Separately Priced (NSP)
Price proposals shall be effective for one hundred-eighty (180) days from the closing date for receipt of offer.
NOTE: Offerors are reminded that Offeror’s signed copies of Volume I - Solicitation, Offer, and Award, and all amendments thereto, Volume III – Price Proposal are to be submitted separate from the Technical Proposal.
No price information is to be presented in the Volume II – Technical Proposal.
Cost Summary. Provide cost summary in the format of Attachment J.2, “Cost Summary Format”, showing cost elements AND functioning formulas in a Microsoft Excel Format. This spreadsheet shall be divided into separate pages with Times New Roman 10 font.
Offers submitted in response to this solicitation shall be in terms of U.S. Dollars. Offers received in other than U.S. Dollars shall be rejected. The cost data shall be organized as follows. These instructions apply equally to the prime Contractor as well as proposed subcontractors/consultants.
Section B Supplies or Services and Prices. Offeror shall complete the Estimated Cost, Fixed Fee and Estimated Cost-Plus-Fixed-Fee columns for CLIN 0001. The prime Offeror’s fee includes all fee associated in calculating the Total Cost including fee charged on the subcontractor’s Total Price.
Offerors cost proposals shall include a proposed fixed fee that is representative of business and technical risks associated with this effort and are substantiated in the proposal.
Provide supporting cost data as required in the format of solicitation Attachment J.3, “Supporting Cost Data.”
For each cost element (labor hours, direct rates and indirect rates) the Offeror must address the following three questions:
1) What is the estimate based on?
2) How was the estimate derived?
3) Why is it reasonable?
When the Offeror elects to claim FCCOM as an allowable cost, the Offeror must include DD Form 1861, Contract Facilities Capital Cost of Money. Offeror shall provide a narrative of the cost elements for the two years to describe the derivation of labor rates and application of escalation, use of uncompensated overtime, pools to which indirect rates are applied, and historically proposed, DCAA recommended and ACTUAL (audited and unaudited) direct and indirect rates experienced by the Offeror within the past three years. Additional narrative, if necessary, may also be attached. If a formal Forward Pricing Rate Agreement has been negotiated, provide a copy.
Provide copies of any DCAA correspondence that approves proposed indirect rates. Identify the planned subcontract type for each Subcontractor/consultant.
Provide historical data to reflect actual escalation rates realized for the past three years.
3.3.3 Direct Labor
Offerors shall base the hours of their Cost Proposals as permitted in accordance with the requirement outlined in the Performance Work Statement. The Fair Labor Standards Act (FLSA) establishes the national minimum wage and maximum hour requirements that apply to firms involved in interstate commerce.
Support functions include but not limited to word processing, reproduction, library, financial, contract administration (to include support of progress report preparation and invoicing), security administration, contract quality assurance, deliverable review and approval necessary to support technical effort. The Offeror shall indicate the hours/amounts proposed for each of these proposed administrative functions, and any deviations to the proposed man-year allocation.
Uncompensated Time (UT)
In compliance with FAR 31.201-4, Determining Allocability; CAS 401, Consistency in Estimating, Accumulating and Reporting Costs; and CAS 418, Allocation, the contractor shall proposed based on total time accounting of direct and indirect labor costs. The Contractors shall propose based on the following methods of accounting for uncompensated overtime acceptable to DCAA:
Calculating a separate average labor rate for each labor period, based on the salary paid divided by the total hours worked, and distributing the salary costs to all cost objectives based on that rate.
Determining the percentage of total hours worked on each cost objective during the labor period and distributing salary cost based on the percentage allocation. For example, if an employee was paid on a weekly basis and worked 20 hours on one project and 30 hours on another, 40 percent of the employee's salary would be charged to the first cost objective and 60 percent to the other.
Computing an estimated hourly rate for each employee for the entire year based on the total hours the employee is expected to work during the year and distributing the salary costs using the estimated hourly rates. Any variance between the actual salary costs and the amount distributed is charged or credited to overhead.
FAR 52.237-10 in Section I of the Basic Contract defines Uncompensated Time (UT) as any hours worked in excess of 40 hours per week without additional compensation. Offerors and its proposed subcontractors shall:
(a) Identify whether the proposed labor categories will be supported by a full time employee and the number of full time employees per labor category
(b) Provide the method use in deriving to the uncompensated overtime. If proposing based on DCMA forward pricing rate recommendations (FPRR) or proposal, the contractor shall provide basis in arriving to the proposed FPRR.
(c) Offerors shall provide a copy of its policy on the use of uncompensated overtime, and as well as for each Subcontractor which has uncompensated overtime included in their proposed LOE.
(d) The Offeror and its subcontractor(s) shall i identify uncompensated overtime hours and the uncompensated overtime rate for direct-charge FLSA-exempt personnel included in the prime and subcontract proposals. This includes uncompensated overtime hours that are in indirect cost pools for personnel whose regular hours are normally charged as a direct cost.
(End of Summary of Changes)
File details come from the government source that posted it. Updated .