Amendment_1.docx
DOCX document 98 KB Posted
- Solicitation number
- N00024-17-R-6405
About this file
Amendment 0001 of the RFP N00024-17-R-6405.
View the file
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
N0002417R6405
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION B - SUPPLIES OR SERVICES AND PRICES
CLIN 0002
The contract type has changed from COST to CPFF.
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
CLIN Number 0002
| 1 |
| Lot |
Material Material in Support of CLIN 0001 (See Note E) FOB: Origin (Shipping Point)
PURCHASE REQUEST NUMBER: N0002417NR92954
CPFF
ESTIMATED COST
FIXED FEE
TOTAL EST COST + FEE
CLIN 1002
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
CLIN Number 1002
| 1 |
| Lot |
| OPTION |
| Material |
Material in Support of CLIN 1001 (See Notes B and E) FOB: Origin (Shipping Point)
ESTIMATED COST
FIXED FEE
TOTAL EST COST + FEE
CLIN 1008
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
CLIN Number 1008
| 1 |
| Lot |
| OPTION |
| Material |
Material in support of CLIN 1007 (See Notes B and E) FOB: Origin (Shipping Point)
ESTIMATED COST
FIXED FEE
TOTAL EST COST + FEE
CLIN 2008
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
CLIN Number 2008
| 1 |
| Lot |
| OPTION |
| Material |
Material in support of CLIN 2007 (See Notes B and E)
ESTIMATED COST
FIXED FEE
TOTAL EST COST + FEE
CLIN 3002
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
CLIN Number 3002
| 1 |
| Lot |
| OPTION |
| Material |
Material in Support of CLIN 3001 (See Notes B and E) FOB: Origin (Shipping Point)
ESTIMATED COST
FIXED FEE
TOTAL EST COST + FEE
CLIN 3008
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
CLIN Number 3008
| 1 |
| Lot |
| OPTION |
| Material |
Material in support of CLIN 3007 (See Notes B and E)
ESTIMATED COST
FIXED FEE
TOTAL EST COST + FEE
CLIN 4008
| ITEM NO |
| SUPPLIES/SERVICES |
| QUANTITY |
| UNIT |
| UNIT PRICE |
| AMOUNT |
CLIN Number 4008
| 1 |
| Lot |
| OPTION |
| Material |
Material in support of CLIN 4007 (See Notes B and E)
ESTIMATED COST
FIXED FEE
TOTAL EST COST + FEE
The following have been modified:
NOTE A
Note A: The Government will issue Technical Instructions in accordance with the Section H clause of this contract entitled “TECHNICAL INSTRUCTIONS”. The engineering and technical services will be defined within the Technical Instruction. The Contractor shall not perform any efforts under these items until and unless tasked by the Government.
SECTION D - PACKAGING AND MARKING
PACKAGING AND MARKING
Items - 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008, 0009, 0010, 0011, 0012, (and Option Items 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1009, 1010, 1011, 1012, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 3001, 3002, 3003, 3004, 3005, 3006, 3007, 3008, 3009, 3010, 3011, 3012, 4001, 4002, 4003, 4004, 4005, 4006, 4007, 4008, 4009,4010, 4011, 4012, 4013 and 4014, if exercised) – The supplies furnished hereunder shall be packaged in accordance with best commercial practice.
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
SECTION L
INSTRUCTIONS TO OFFEROR(S)
1.0 INSTRUCTIONS TO OFFEROR(S)
1.1 AMENDMENTS TO THE SOLICITATION
If this solicitation is amended all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this solicitation by the date and time specified in the amendment(s) and sign the applicable SF-30.
1.2 GENERAL
This RFP is for a competitively awarded contract in support of technical engineering services for maintenance, modernization, product improvement, and design services including the DDS units, HOSUBs, transporter, Training Closure and Hatch Assemblies (TC&HA), and the DDS Rotatable Pool. The award will be made to the responsible offeror whose proposal represents the best overall value to the Government.
The Offeror’s proposal shall be based on requirements contained in this RFP (including those documents, exhibits, and other attachments to the RFP identified in Section (J)). Offerors are advised that the Government seeks proposals that demonstrate the greatest technical merit at a reasonable cost. Accordingly, Offerors are advised that award may not be made to the Offeror with the lowest evaluated cost to the Government if award to an Offeror with a higher cost proposal affords the Government a greater overall benefit. Award will be made to the Offeror who meets the requirements of FAR subpart 9.1, “Responsible Prospective Contractors,” whose proposal conforms to the requirements of the solicitation and has been determined to be technically acceptable, and whose proposal is determined to offer the best value to the Government in accordance with the evaluation criteria and factors set forth in Section M. In this competition, overall technical merit, including past performance, is considered significantly more important than evaluated cost; however, the importance of cost will increase as the difference in overall technical merit among competing proposals decreases.
Upon request, and once the appropriate terms of use agreement is in place, the Government will make available to Offerors additional unclassified references, information and data for information purposes only via http://safe.amrdec.army.mil. The Government does not warrant the content and performance of data contained therein and, if provided, such data is intended as information only. Offerors must ensure proposals address all Contract Line Items (CLINs) and that all CLINs meet the Government’s requirements as outlined in this solicitation and the cited applicable documents and specifications. Upon request and once the appropriate terms of use agreement is in place, Classified references can be made available. For access to both Classified and Unclassified information, please contact the Purchasing Office Representative identified in Section G.
Comprehensive responses to the requirements of this solicitation are required to enable the Government to evaluate the Offeror’s understanding of and capability and approaches to accomplish the stated requirements. Proposals shall be submitted in accordance with the instructions in this solicitation and non-conformance with the specified required content may be cause for rejection of the proposal. Offerors are advised that material submitted in excess of that required herein will not be evaluated. The proposal shall be valid for no less than 365 days from the date of solicitation closing. Proposals shall not contain any classified data. Offerors are required to submit a proposal encompassing all items listed in Section B. The proposal shall provide comprehensive responses to the insrtuctions provided under Section L. The proposal shall be a complete response to the Statement of Work (SOW) and the requirements of this Solicitation including those documents, exhibits, and other attachments to the Solicitation identified in Section J, taking into consideration required delivery schedules specified elsewhere in this solicitation.
Any Offeror lacking the requisite facilities security clearance and intending to respond to this procurement shall, within ten (10) days of issuance of this solicitation, request initiation of such clearance action in email to Attention: Ms. Tchwan Slye, at Tchwan.slye@navy.mil. Appropriate clearance action in accordance with established procedures will be initiated by the Naval Sea Systems Command, but the Naval Sea Systems Command does not represent that such action can be completed and clearance granted prior to expiration of offers. In no event are Offerors to submit a proposal that is not in accordance with the solicitation. Offers which are found to deviate from the RFP may be rejected as unacceptable.
Offerors are hereby notified that from time to time the Government may post additional information via the internet site Federal Business Opportunities (FBO) or URL:https://www.fbo.gov/ , relating to this solicitation (e.g., responses to questions, amendments, etc.). It is the Offeror’s responsibility to check the website for such information.
If Offerors have any questions to any specific technical requirement of the SOW, specifications or any other terms and conditions of the solicitation which, in the Offeror’s opinion, prevents it from responding fully to the RFP, the Offeror shall notify the Government in writing via E-mail. Offeror’s questions shall identify each specific area of concern. The Government requests Offerors submit questions via e-mail within 21 days after issuance of this RFP to allow the Navy adequate time to prepare and issue responses to all Offeror’s questions prior to the date and time set for receipt of proposals. Offerors may submit questions at any time prior to the date set for receipt of proposals. However, questions received after 21 days after issuance of the RFP may not provide the Government adequate time to respond in a manner that may affect an Offeror’s proposal. If the Government determines that a specific change is in fact required, then an amendment to the RFP will be issued.
Each question shall be submitted using the MS Excel file template. All unclassified questions shall be sent directed to the Contract Specialist, Ms. Tchwan Slye with copy to the PCO, Mr. Peter Agyei-Sarpong. The preferred method of correspondence is via email. If an Offeror needs to ask a question of classified nature, it shall express its desire to do so. An appropriate channel for classified questions will be established at which point the Offeror may pose its classified question.
1.3 SOLICITATION RESPONSE REQUIREMENTS
Each Offeror shall submit a proposal in response to this solicitation subject to the following requirements.
| Volume # | Volume | Title | Pages | Copies | ||
| I | Technical Proposal | 150 Maximum | 3 paper copies with 6 CDs | |||
| II | Cost/Price Proposal | No Limit | 3 paper copies with 3 CDs | |||
| III | Contract Information | No Limit | 1 paper copies with 3 CDs |
In addition, the Offeror shall submit a cover letter with its Proposal that identifies all amendments to the RFP that the Offeror has included with his proposal. However, the cover letter will not be evaluated and will not count towards the page limits. No price information shall be on the Cover Letter. One of the submitted copies of Volumes I, II, and III shall be marked as “original.” and shall have two holes punched at the top of each page.
The narrative material in the proposal for both Volumes I and II shall be single spaced, typed on both sides of the page with type no smaller than Times New Roman 12 point size characters. A page is defined as one side of a sheet 8 1/2 inches by 11 inches, Header/Footer = 1.0 inch, Right/Left Margins = 1.0 inches. Each double-sided sheet counts as two (2) pages.
Each volume shall be bound separately and shall not exceed the page limitation cited above. The page count shall include all printed matter and figures, except cover pages, title pages, Table of Contents (TOC), lists of illustrations, tab pages, appendices, index and lists of tables. Pages excluded from the page count must contain only material pertinent to the page heading or be blank and marked "Intentionally Left Blank." Index pages and Tabs are required and shall be cross-referenced to the TOC. Every page, except those marked as blank, shall be numbered. If the proposal exceeds the page limit identified above in either the paper copy or the electronic CD-ROM copy, the Government will remove all pages exceeding the specified page count from the back of the proposal prior to the evaluation. These pages will not be removed from the index or appendices provided at the back of the proposal. The CD-ROM should reflect the exact contents of the paper copy and should not contain any additional content not existing in the paper copy. 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 and dated. In the event of any discrepancies between the electronic and hard copy of a proposal, the hard copy proposal will take precedence.
The Offeror shall provide each Volume on separate CD-ROMs. Each disk shall be labeled as follows:
N00024-17-R-6405 Volume # Offeror Company Name, City, State Offeror POC Offeror POC Phone #
The cover page of each Proposal Volume shall contain:
· Volume Number and Title (e.g., Volume I - Technical Proposal)
· Item Nomenclature and RFP Number
· Company Name of the Offeror
· Offerors Position on Disclosure of Proposal Data
THE OFFEROR IS REQUIRED TO SUBMIT THE REQUIRED NUMBER OF COPIES OF VOLUME II (COST/PRICE PROPOSAL) SEPARATE FROM THE TECHNICAL VOLUME.
Offeror’s proposal submission shall be as follows:
All required copies shall be submitted at the place specified below and at or before the time and date specified in block 9 of the SF 33:
Commander Naval Sea Systems Command Attn: Tchwan Slye, SEA 02642 1333 Isaac Hull Ave. SE Stop 2050 Washington Navy Yard, DC 20376-2050 Tchwan.Slye@navy.mil Telephone Number: (202) 781-3972
Although legible, neat, orderly, and comprehensive proposal(s) are required, elaborate brochures or other presentations beyond that sufficient to present a complete and effective explanation are not desired. Elaborate artwork, expensive visual or other presentation aids are neither necessary nor desired. Offeror shall not embed sound or video files into the electronic files. Graphics, tables, photographs, and other data beyond the capability of Microsoft Office Suite 2007 may be submitted in Adobe Acrobat format.
Volume I shall be compatible with Microsoft Office 2007 or greater, or be readable as a .pdf and stored on a compact disk (CD-ROM). Volume I of the proposal should not contain more than ten (10) foldouts. A foldout is defined as any document larger than a standard 8 1/2 by 11 inch sized page. Fold out pages may be used for diagrams, charts or graphic material only and may not exceed 11 inches by 17 inches. Foldout pages count as one (1) page. Each double-sided foldout counts as two (2) pages.
Volume II (Cost/Price Proposal) financial data (e.g. Elemental Cost Summaries by CLIN for each CLIN and Consolidated Total) shall be provided using the Excel software application and shall have all formulas traceable to all cells, and no password protection applied. The Excel workbook(s) shall be provided on a compact disk (CD-ROM). The pricing spreadsheets generated must present all cells containing derived data with the formulas used to derive the data. Hard coded numbers, without the use of formulas, are unacceptable. This is only for evaluation purposes. Any narrative shall be compatible with Microsoft Office 2007 or greater, or be readable as a .pdf and stored on a compact disk (CD-ROM).
No cost or pricing information shall be included in the Offeror's cover letter or in any part of its submitted volumes, except for Volume II and Volume III. Forwarding letters are merely instruments for transmitting the submitted proposals; they are not part of the page count.
1.4 CONDITIONS AND NOTICES TO OFFERORS
The Government will evaluate each Offeror’s understanding of the Government’s requirements and ability to perform the work on the basis of its proposal. It is the Offeror’s responsibility to provide information and evidence that clearly demonstrates its ability to satisfactorily respond to the solicitation requirements.
The solicitation will be issued through the internet at: https://www.fbo.gov/. Offerors shall submit all information required by this RFP. Failure to comply with the terms and conditions of the RFP may result in the Offeror being removed from consideration for award. The performance of this contract requires that the Offeror have a SECRET facility clearance granted by a Military Department prior to award.
Solicitation Responsiveness. Offerors are advised to submit proposals that are complete, clear, and consistent in all respects without the need for additional explanation or information. Offerors are cautioned against the use of general, vague, or unsubstantiated statements, which prevent concise proposal evaluation. Each factor will be evaluated on how well the response meets the requirements of the solicitation. A response that completely addresses all of the solicitation requirements may be judged superior to a response that minimally addresses solicitation requirements under evaluation factors. The Offeror’s submission is not to be a restatement of information in Section C (Statement of Work (SOW)) of the RFP. The Offeror shall include cross-referencing for traceability.
Due to the nature and scope of the work encompassed by this solicitation, the Government requires that there be no conflict which would preclude the prime contractor and/or subcontractors from performing any portion of the SOW, regardless of whether it intends to subcontract that portion. Due to the nature of the work outlined in Section C, the Government anticipates that organizational conflicts of interest (OCIs), including impaired objectivity OCIs, may arise for Offerors that perform under other contracts within the cognizance of PMS399 (Special Operations Forces (SOF) Undersea Mobility Office) as prime contractor or subcontractor for the efforts that will be covered by this solicitation.
The Government is most concerned about potential OCIs in the following scenarios: (1) when a contractor’s work under one Government contract could entail its evaluating itself or a related entity, either through an assessment of performance under another contract or an evaluation of proposals (impaired objectivity OCIs); (2) when performance of the work under this solicitation would place an Offeror in a position to make technical, design, or programmatic recommendations that would include hardware, software, system design, integration, or production of systems provided by the Offeror’s organization; or (3) when the provision of the engineering and technical direction described in Sections C and L of the RFP would create the situation prohibited by FAR 9.505-1 because the Offeror is currently a prime contractor, subcontractor, or consultant on a contract for services or the supply of a system covered by this solicitation or any of its major components.
Therefore, if any Offeror may have an OCI, or if any Offeror has taken any steps to eliminate an OCI and the Offeror believes that the conflict no longer exists, the Offeror must notify the Government and must submit an OCI mitigation plan with its proposal in Volume III. Failure by an Offeror that has identified a potential OCI to submit an OCI mitigation plan with its proposal shall be considered grounds for disqualification from award. The Government will not accept mitigation measures for impaired objectivity OCIs.
For any OCI, the Government will not accept mitigation or elimination measures: (1) that create an additional burden on the government to implement; (2) that involve directed subcontractors or creating separate lines of reporting or any modification to the Government/prime contractor relationship; or (3) that are deemed in the sole discretion of the contracting officer to provide insufficient organizational independence between the prime contractor or a subcontractor under this contract and a prime contractor or subcontractor for hardware, software, system design, integration, or production of the systems that will be covered by this solicitation. This is not an exhaustive list of measures that will be considered inadequate to protect the Government. It is an illustrative list provided in an effort to ensure that all Offerors understand the Government’s expectations and intent to avoid OCIs.
The Government reserves the right to determine whether or not any mitigation plan provided by an Offeror is sufficient to protect the Government. The Government also does not intend to accept any mitigation measures that involve additional oversight or commitment of resources by the Government, such as agency review of contractor deliverables, internal review of task assignments for OCI before issuance, or formalized monthly reviews of work performed and projected. All Offerors are directed to review and comply fully with the OCI clauses included in Sections C and L of this solicitation (ORGANIZATIONAL CONFLICT OF INTEREST (NAVSEA) (JUL 2000) and NOTIFICATION OF POTENTIAL ORGANIZATIONAL CONFLICT(S) OF INTEREST (NAVSEA) (JUN 1994) respectively).
2.0 GENERAL CONTENTS OF THE PROPOSAL
The Offeror's proposal must include the following:
a. Standard Form 33: Solicitation, Offer and Award, with blocks 13 through 18 completed by the Offeror.
b. Solicitation with all Offeror fill-ins completed as well as Section K: "Representation, Certification and Other Statements of Offerors," completed by Offeror.
c. Small Business Subcontracting Plan: The Offeror’s attention is directed to Section I clauses FAR 52.219-9 entitled “Small Business Subcontracting Plan” and DFARS 252.219-7003 entitled "Small Business Subcontracting Plan (DOD Contracts)": and FAR 52.219-16 entitled "Liquidated Damages - Subcontracting Plan." As prescribed in FAR 19.708, Offerors other than small business concerns shall submit a subcontracting plan and that plan, once approved shall be made part of any contract resulting from this solicitation.
d. Technical and Management Approach: Offerors shall submit electronic and hard copies of their Technical and Management proposal.
e. Past Performance Information: Offerors shall submit the past performance information in the format specified.
f. Cost/Price Proposal: Offerors shall submit cost/price and other information required.
g. The Offeror shall not submit the Security Classification Specification as part of the proposal. The DD Form 254 will, however, become a material part of any resultant contract.
h. OCI Mitigation Plan, as applicable.
The Offeror's proposal is the sole basis for evaluating the merits of what is offered, the degree to which the Offeror's claims of performance capacity are supported and the ability of the Offeror to perform in accordance with the requirements. Failure of the Offeror to comply with all aspects of the solicitation requirements may, at the Government’s discretion, render the proposal unacceptable, and the Offeror may be eliminated from the competition for award. The factors to be considered are discussed herein. Proposals submitted shall be sufficiently detailed to enable Government personnel to make a thorough evaluation of the proposal by factor/sub-factor, and to arrive at a sound determination as to whether the prospective Offeror will be able to perform in accordance with the requirements of the solicitation. .
The Offeror need not repeat information within the same volume required in the response to two or more proposal requirements. Such information shall be presented in detail in one area of the volume where it contributes most critically to the discussion. In other areas where discussion of the same information is necessary, the Offeror shall refer to the initial discussion and identify its location within the proposal volume.
Each volume shall be written to the greatest extent possible on a standalone basis so that its content may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal. Each volume shall contain a glossary of all abbreviations and acronyms used, with a definition for each. Glossaries do not count against the page limitations for their respective volumes.
In the event that any portion of the technical proposal is written by someone who is not a bonafide employee of the offeror who is submitting the proposal, a certificate to this effect shall be signed by a responsible officer of the Offeror and 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.
3.0 PROPOSAL ORGANIZATION/OUTLINE
The format and content of the proposal must contain a response to each of the topics of discussion noted below. Information presented shall appear in the same order as outlined. A master index identifying major subsections by number, title, page number and volume shall be provided in each volume. A separate index or matrix which correlates proposal information to the solicitation elements shall be provided. Proposal information shall be referenced to the proposal’s outlines and page numbers, and solicitation elements shall be cited by section and page numbers.
Documents, exhibits, and other attachments that form a part of this solicitation, that will become part of any resultant contract are identified in Section J. Section K will be incorporated by reference, while Sections L and M will not become a part of any resultant contract. The Offeror must also address the clauses that require a response.
Pursuant to FAR 52.215-1(f), Instructions to Offerors-Competitive Acquisition (JAN 2004), the Government may evaluate offers and award the contract without discussions with offerors. The Government reserves the right to conduct discussions if the PCO determines them to be necessary or in the best interest of the Government. However the Contracting Officer reserves the right to enter into discussions.
Proposals shall be organized as follows:
| FACTORS |
| SUB-FACTORS |
| Attachment |
| Page Limit |
Volume I – Technical Proposal
| 1. Technical Approach |
| A. Technical Capabilities |
150* Pages (Total)
B. Corporate Experience
C. Software Development
D. Personnel Staffing and Key Personnel
| 2. Management Approach |
| A. Organization Management & Integration of Effort |
B. Facilities, Tools, and Production Processes
| 3. Past Performance |
| (None) |
None
Volume II – Cost/Price Proposal
| 4 Total Evaluated Cost |
| (None) |
No Limit
Volume III – Contract Information**
| (None) |
| (None) |
No Limit
* IAW paragraph 4.2.1.3 (a), the initial Software Development Plan (SDP) is not subject to the technical proposal page limitation ** Contract Information required under Volume III including Solicitation Fill-ins, Small Business Subcontracting Plan, and OCI Mitigation Plan, if applicable, has no page limit.
The evaluation factors are divided into two categories: Non-Cost Factors (Factors 1, 2 and 3) and Cost Factors (Factor 4). Factor 1 (Technical Approach) is significantly more important than Factor 3 (Past Performance). Factor 2 will be evaluated as acceptable/unacceptable. Factors 1 and 3, collectively, are significantly more important than Factor 4 (Total Evaluated Cost); however, as competing proposals approach non-cost (Factor 1 and 3) equality, Factor 4 will increase in importance. Within Factors 1, sub-factors are of equal importance. There are no Sub-factors for Factor 3 or Factor 4.
4.0 PROPOSAL CONTENT
4.1 OFFER
The completion and submission to the Government of an offer shall indicate the Offerors unconditional agreement to the terms and conditions to this solicitation.
4.2 VOLUME I – Technical Proposal
This volume shall be as specific, detailed and complete as to clearly demonstrate the Offerors understanding of, and the ability to meet, the requirements of the solicitation, SOW, specifications, and various exhibits. By addressing the Factors and sub-factors below, the Offeror shall present, in detail, the proposed efforts to be performed. The SOW, the cited applicable documents, and the specification establishes the detailed minimum requirements that the Offeror is required to meet. The following information shall be included in Volume I and shall be organized as outlined below.
Factors 1, 2, and 3 shall be constrained by the 150-page limitation unless otherwise specified.
i Title Page ii Table Of Contents iii List Of Figures iv List Of Tables v List Of Appendices vi Glossary Of Abbreviations And Acronyms
4.2.1 FACTOR 1 – Technical Approach
The Offeror shall describe its technical approach by addressing the following four (4) Sub-factors: (A) Technical Capabilities; (B) Corporate Experience; (C) Software Development; and (D) personnel Staffing and Key personnel at performing similar or equivalent work. The requirements of the following sections shall be addressed in their entirety.
4.2.1.1 FACTOR 1 Technical Capabilities (Sub-factor A)
Offerors shall demonstrate comprehensive technical knowledge , capabilities and understanding of the requirements/tasks contained in the SOW. This section shall discuss, in detail, the Offeror’s technical knowledge, capabilities and understanding of the Navy’s requirements and how to meet technical complexities of the effort required.
Offeror’s proposal shall demonstrate the following:
(1) Understanding of the work, including technical knowledge and understanding of (1) designing, fabricating, installing and certifying configuration changes, (2) the Restricted Availabilities/Technical Availabilities (RAV/TAVs) at the Government’s DDS Maintenance and Offeror’s facilities, (3) emergent and emergency repairs and (4) maintaining the Rotatable Pool related to fielding configuration changes to the DDS, transporters, Host Submarines (HOSUBs), DDS training facilities, and Training Closure and Hatch Assemblies (TC&HA) or DOD shelter systems of a similar nature to that which would be performed under this contract. The technical capabilities approach shall address the following in details:
(a) Designing a Temporary Modification (TM), Temporary Alteration (TA), Field Change (FC)/Ship Alteration (SA) including the following for each:
i. Initial investigation and requirement setting
ii. Establishment of TM, TA, FC, or SA concept and schedule development
iii. Rapid development
iv. Adhering to cost and schedule requirement as well as real-time tracking/reporting cost and schedule execution
v. Design for manufacture/Proofing the design/Adherence to Deep Submergence System – Scope of Certification (DSS-SOC) and/or Submarine Safety (SUBSAFE) design and manufacturing & testing requirements, as applicable
vi. Addressing configuration differences between Dry Deck Shelter units and ship interfaces
vii. Modeling, prototyping, early testing and evaluation
viii. Development of logistics support changes including Planned Maintenance System (PMS) and Maintenance Requirement Card (MRC) changes, technical manual, supply support, and training
(b) Producing the TM, TA, FC, SA, addressing for each:
i. Material ordering and handling
ii. DSS-SOC and SUBSAFE compliance
iii. Fabrication
iv. Factory testing
v. Quality Control
(c) Kitting the TM, TA, FC, or SA, addressing for each:
i. Installation procedures and instructions
ii. Part inventory and kitting for efficient installation
iii. Packaging
iv. Consumables
v. Shipment
vi. Receipt inspection/storage
(d) Installing the TM, TA, FC, or SA, addressing for each:
i. Work permit process/Work Authorization process
ii. Integration with lead maintenance activity
iii. Hotel/Support Services
iv. Adherence to procedures/standards
v. Quality Control and handling of Deviations and Waivers/Adherence to DSS-SOC and/or SUBSAFE installation & testing requirements, as applicable
vi. Plan and generating DSS-SOC and SUBSAFE records
(e) Installation testing and certifying the installed TM, TA, FC, or SA, addressing for each:
i. Test plan/procedure development
ii. Conduct of In-unit/On-Host testing
iii. Test result analysis and acceptance
iv. Tests data recording/reporting
v. Support of system certification to DSS-SOC and/or SUBSAFE requirements, as applicable
(f) The Offeror shall describe its approach to supporting and conducting RAV/TAVs at the Government’s DDS Maintenance facilities identified in the Government Furnished Property list, Attachment 3 of Section J, which is the DDS unit ‘homeport’. The technical approach will address the following details:
i. Supporting the planning process, addressing
ii. Work package development, including meeting DSS-SOC requirements as applicable
iii. Development of the RAV/TAV work plan
iv. Conduct of RAV/TAV addressing:
1. Ability and means to handle surge workload to support notional RAV/TAV availabilities.
2. Planned work site tooling
3. Establishing and maintaining organizational interfaces
4. Establishment of agreements (e.g. Lead activity/support activity, hotel services)
5. Means of providing contractor supplied hotel services
6. Utilization of tiger teams
7. Early identification/accommodation of new work/work growth within/understanding the impact to schedule and cost
8. Process and oversight to ensure adherence to schedule and cost including real-time tracking reporting of cost and schedule performance
(g) In addition to the elements listed in paragraph (f) above, the Offeror shall describe its approach to supporting and conducting the RAV/TAVs at the Offeror’s facility. The technical approach will address the following details:
i. Machine shops
ii. Main overhaul/production floor
iii. Test bay/fixtures
iv. Handling capability
v. Air and Roadway accessibility to plant facility
(h) Supporting and conducting the emergent and emergency repairs.
i. Use of rapid response teams addressing:
1. Evaluation of failures
2. Conduct of repairs made on an embarked or deployed asset, including meeting DSS-SOC and SUBSAFE requirements as applicable
ii. Rapid correction of repairs at a shore side repair facility
iii. Root cause investigation/determining appropriate immediate, short-term, and long-term corrective action
iv. Timely determination/reporting of costs
(i) Approach to maintaining the Rotatable Pool
i. Receipt inspection and overhauling of returned items
ii. Stocking/shipping/asset tracking
iii. Maintenance/failure analysis
iv. Facilities to be used for the maintenance of rotatable pool items
v. Adherence to Ready-For-Issue (RFI) objectives, including meeting DSS-SOC requirements as applicable
vi. Adherence to cost objectives
(j) The Offeror shall describe its technical approach of work package development and long lead time material procurement in support of an ROH at the Offeror’s facility utilizing the Baseline Overhaul Work Package (Section J, Attachment 4) as the basis. The technical approach will address the following details supporting the planning process:
i. Work package development, including meeting DSS-SOC requirements as applicable
ii. Development of an ROH work plan
iii. Procurement of long lead time material utilizing both the Naval Stock System and Industry, as necessary
iv. Early identification/accommodation of new work/work growth within/understanding the impact to schedule and cost
v. Process and oversight to ensure adherence to schedule and cost including real-time tracking reporting of cost and schedule performance
4.2.1.2 FACTOR 1 Corporate Experience (Sub-factor B)
The Offeror shall provide evidence of corporate experience related to DDS, or Deep Submergence Systems (DSS), or submarines to include DSS-SOC or SUBSAFE systems. The Offeror shall be concise and specific in detailing past experience in design, development, modification, testing, maintenance, and certification of similar systems. Offerors are to show specific related experience in one or more of the following areas of consideration. The following considerations are in descending order of importance.
a. Experience over the last ten years with design development, modification, testing, maintenance, and certification of manned DSS built and maintained to DSS-SOC requirements
b. Experience within the last five years with the design development, modification, testing, maintenance, and certification of Diver Life Support Systems with characteristics similar to the DDS and designed for limited depth manned diving and hyperbaric operations
c. Experience within the last five years in the design and production of Navy Special Emphasis Program (NSEP) material such as piece-parts, components, subassemblies procured in accordance with the Level I or DSS-SOC requirements. Include experience in providing Level I and/or DSS-SOC material through other (e.g. non-NSEP) channels or procurement processes.
d. Other relevant and related DoD experience
4.2.1.3 FACTOR 1 – Software Development (Sub-factor C)
The Offeror shall submit a Software Development Plan and detail their Software Development and CMMI or Equivalent Experience in accordance with the following clauses;
SOFTWARE DEVELOPMENT PLAN (NAVSEA) (DEC 2006)
(a) As part of the proposal, offerors shall submit an initial Software Development Plan (SDP) that at a minimum addresses the requirements of Section C paragraph 3.1.4 and 3.2.1. The initial SDP shall not be subject to the technical proposal page limitation of the solicitation. Offerors are advised however, that initial SDPs, which are concise and well-written, may receive more favorable consideration than those that contain extraneous material and/or brochuremanship.
(b) Offerors shall also submit an SDP rationale which describes why their specific approach is appropriate for the system to be procured, developed or maintained and how their proposed processes are equivalent to those articulated by CMMI® capability level 3. The SDP rationale is subject to the technical proposal page limitation of the solicitation and shall not exceed 3 pages.
The SDP shall be submitted as part of of Volume I : Factor 1 - Technical Approach, Part C – Software Development.
The Offeror shall submit a summary of software development and CMMI or equivalent experience in accordance with the following:
SOFTWARE DEVELOPMENT AND CMMI OR EQUIVALENT EXPERIENCE (NAVSEA) (DEC 2006)
(a) Offerors shall submit a description of previous relevant experience, within the past 24 months in developing software of the similar size and complexity as that required under the statement of work. As a part of this description, the offerors shall describe the extent to which personnel who contributed to these previous efforts will be supporting any resultant contract.
(b) Offerors shall also describe any previous relevant CMMI® or equivalent model-based process maturity appraisals performed within the past 24 months. As a part of this description, offerors shall identify the organizational entity and location where the appraisal was performed, the type of evaluation, the organization performing the evaluation, and the level earned. This description shall not exceed 5 pages.
The descriptions called for under paragraphs (a) and (b) above are subject to the technical proposal page limitation of the solicitation.
4.2.1.4 FACTOR 1 – Personnel Staffing and Key Personnel (Sub-factor D)
(1) The Offeror shall describe its personnel capabilities as well as its ability and approach to hiring and maintaining sufficient and proficient staff to conduct the work identified in this solicitation throughout the life of the contract.
(2) The Offeror shall provide resumes for the following Key personnel. Individuals that support multiple roles shall reflect the expected time for each work area proposed. Resumes shall be appended as supplemental information and are excluded from the page limitation requirements. The resumes shall contain the following information, at a minimum, and be no greater than two (2) pages in length per individual:
· The individual’s current title, position, and, length of time with the organization.
· The individual’s proposed title/job position and level of participation the individual will devote to this contract.
· A brief description of specific duties and responsibilities to be performed by the individual.
· A description of all relevant positions held (title, dates of employment, employee’s major duties, responsibilities, and accomplishments).
· The individual’s education, training, licenses, certifications, and any other relevant information.
· The Offeror’s narratives shall demonstrate the individuals depth of experience and qualification to perform the scope of work required.
Key Personnel shall meet or exceed the qualifications for the position they are expected to fill as defined in the solicitation. Key Personnel shall be identified as either present employees (PE), or contingent hires (CH). Any contingent hire shall have a signed letter of intent to include the planned start date.
The data contained in the Key personnel resumes shall be consistent with the information provided in the staffing plan. The data contained in the Technical proposal shall be consistent with the data provided in the Cost/Price proposal.
(a) Overall Program Management/Key Personnel:
i DDS Program Manager (Key Personnel) ii Chief Engineer (Key Personnel) iii Waterfront Engineer/Design Manager (Key Personnel) iv Production Manager (Key Personnel) v Quality/Certification Director (Key Personnel)
All key personnel must have a minimum of ten (10) years of experience in their proposed functional competency demonstrating specific capability, knowledge, and relevant experience of similar scope and complexity for assigned functions. In addition to the above, the DDS Program Manager shall have a Project Management Professional (PMP), Defense Acquisition University Program Management Level III, or equivalent and have an additional 5 years of experience in managing a cost type contract for a US DOD component. For the Chief Engineer and Waterfront Engineer, a Bachelor of Science Engineering degree from an accredited college or university is required.
Although Section M provides for Key Personnel becoming unavailable prior to contract award, Offerors shall only propose Key Personnel resumes for individuals that, at the time of proposal submission, the offeror has a good faith expectation of providing at award. Failure to provide the specific individuals proposed as Key Personnel without reasonable rationale may result in negative CPARS findings during contract performance. Additionally, the Government considers the submission of Letters of Intent for proposed contingent Key Personnel to be material to the proposal since these Letters of Intent demonstrate the offeror's ability to hire personnel with the qualifications bid at the salary proposed.
(3) The Offeror shall identify Lead personnel by name and their associated position description. Resumes are not required to be submitted for lead personnel. Individuals that support multiple roles shall reflect the expected time for each work area proposed. If the Offeror determines that such a position is neither appropriate nor required, then an explanation and basis for that determination shall be provided.
(a) Lead/Manager for Configuration Changes (e.g. TM, FC, TA, or SA):
i Configuration Change lead/manager ii Hull/structural lead iii Piping/fluids lead iv Diving Systems support/atmospheric control lead v Electrical/electronic lead vi Production lead vii Quality/Certification specialty lead viii Test lead
(b) RAV/TAV/ROH:
i Management lead ii Planning Lead iii Production lead iv Engineering liaison/support lead v Test lead vi Quality/Certification specialty lead
(c) Emergent/Emergency Repairs:
i Engineering Lead ii Production Lead iii Test lead iv Quality/Certification specialty lead
(d) Rotatable Pool:
i Rotatable pool lead
All lead personnel must have a minimum of five (5) years of experience in their proposed functional competency demonstrating specific capability, knowledge, and relevant experience for contract(s) of similar scope and complexity. The Offeror may utilize the same person for more than one lead position identified above.
Personnel Staffing Plan Using Microsoft Excel, Offerors shall provide a Personnel Staffing Plan by task area, of all proposed labor category personnel supporting each of the task areas specified in the statement of work. The Offeror shall provide their Personnel Staffing Plan in the format consists of the following information set:
· Labor Category/level
· Whether the individual is a key or non-key personnel
· Employer (employee's company name)
· The functional area of the Statement of Work, target Work-Center and sub-Work-Area
· Whether the individual is employed by a sub-contractor who will be performing on this contract
· Number of labor hours proposed for each base and option year
· Employees shall be identified as either present employees (PE), or contingent hires (CH) or unidentified ‘to be hired’ (TBH). Key and Lead personnel shall only be designated as PE or CH.
· Idenify all contingent hires and planned start date for base year of the contract
Note 1: The data contained in the Personnel Staffing Plan shall not conflict with the data provided in the Key Personnel List.
Note 2: A copy of a signed offer letter indicating acceptance by the individual shall be provided for each Key or Lead contingent hire.
Note 3: In the event that Offeror has not identified a firm candidate for proposed non-key personnel positions, the Offeror’s Staffing Plan submittal shall:
(1) Include the word, “Pending” in lieu of an individual’s name, and the designation TBH
(2) Identify the applicable Labor category/level
(3) Identify the number of hours that position is expected to contribute to the effort.
Offerors should attempt to minimize the number of proposed unidentified candidates. Technical level of risk should be expected to increase with a greater number of unidentified candidates.
Labor Category Description The Offeror shall provide the description of each labor category proposed under this soliciation.
Labor Mix Discussion The staffing plan shall also describe the Offeror’s proposed labor mix (e.g. Program Management, Engineering, Production), labor grade/level (e.g. Senior, Mid, Junior), the rationale used in selecting the mix and should explain any difference between the Offeror’s proposed labor mix and the following historical labor mix. Staffing plans for all proposed tasks must propose the same mix and amount of hours as that of the cost proposal. Any discrepancies are subject to technical and/or cost realism adjustments.
Average DDS RAV, Rotatable Pool, Field Change Installation, and Emergent Repair Labor Mix:
Level of Effort/Management: 25% Engineering: 5%
Production: 70%
Average Engineering Support Services Labor Mix Level of Effort/Management: 45%
Engineering: 45%
Production: 10%
Average Configuration Change Design/Development Labor Mix Level of Effort/Management: 20%
Engineering: 70%
Production: 10%
4.2.2 FACTOR 2 – MANAGEMENT APPROACH
Offerors shall describe their corporate structure and ability to manage resources in relation to the following two Sub-factors: (A) Organization Management and Integration of Effort; and (B) Facilities, Tools and Production processes. The requirements of the following sections shall be addressed in their entirety.
4.2.2.1 FACTOR 2 Organization Management and Integration of Effort (Sub-factor A) Offeror shall describe its organization management and integration approach in relation to this effort. The proposal shall clearly describe the Offeror's management and integration approach (clear chain-of-command or responsible individual) to controlling and integrating the diverse efforts required by the SOW. Offeror shall describe its corporate structure and ability to manage resources. Offerors shall describe procedures in place for providing quality assurance of work products. Offeror’s management and integration approach shall address the following:
· Overall management experience and approach
· Offerors shall address in sufficient detail the adequacy of corporate management and corporate resources to support the technical requirements of the solicitation and ability to function as a viable and productive partner with the Government.
· Quality contract execution and compliance
· Offerors shall describe the management approach to quality and how it will be accommodated in the contract execution. Additionally, the Offeror shall provide information on its corporate experience in quality management systems such as ANSI Z540.3 Requirements for the Calibration of Measuring and Test Equipment, ISO 17025:2005 General Requirements for the Competence of testing and calibration and ISO 9000:2015 International Standards on Quality Management and Quality Assurance, including the Offeror’s plan for early identification and resolution of problems. The Offeror shall describe how management, quality and engineering services teams are integrated to overcome risks from scheduled, programmatic and operational requirements changes.
· Resolution of contractual and technical problems
· Offerors shall describe their experience performing similar work within the structure, systems, and legal/regulatory requirements of DoD and DoN. This can be demonstrated by the Offeror’s own experience or proposed subcontractor’s experience in providing similar contractor support as required to meet the tasks outlined in the SOW.
· The Offeror shall address how their management approach will meet the cost, schedule, and performance requirements of this solicitation. Finally, Offerors shall identify and address performance and schedule risk that may occur under the resultant Contract and discuss its approach for managing and mitigating the identified risks.
· Subcontracting approach
· The Offeror’s management and integration approach shall include the prime and subcontractors (if any)(sub-contractor level of effort greater than 5% of total contract hours) organizational structure, functional relationships, responsibilities and coordination among the prime team members.
· Offerors shall define/describe/explain the usage of Teaming, Personnel, and Subcontractors including:
· Offerors shall present their knowledge of the personnel and subcontractor qualifications necessary to perform the work
· Offerors shall address any teaming arrangements for accomplishing the proposed work.
· Offerors shall reveal the extent of involvement in the performance of their subcontractors (if applicable); including Subcontract Management detailing how each subcontractor will be managed to ensure cohesive integration into the overall management approach that all contract objectives are met.
· Offerors shall describe how their team will integrate the teaming partners into their management approach in the following areas and how the Offeror will leverage their strengths to bring value to the Navy: Technical Leadership, Quality Assurance, and Process Improvement.
· The Offeror shall specifically address in the Subcontracting Plan, how and why selected subcontractor(s) were chosen, which knowledge and skills they will be acquiring through…
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.