N68335-17-R-0010-0001.docx
DOCX document 51 KB Posted
- Attached to
- Heat Gun Tool Set
- Solicitation number
- N68335-16-R-0356
About this file
Amendment 0001 to N68335-17-R-0010
View the file
Other files
| File | Type | Posted |
|---|---|---|
| N68335-17-R-0010-0002.docx | DOCX document | |
| PMA275_CMP_2014_09_01.pdf | ||
| CDRL_Email_Address_List_26_Oct_16.doc | DOC document | |
| A001_ECP_Heat_Gun_SERD_2522_(1).docx | DOCX document | |
| A002_RFV_Heat_Gun_SERD_2522_(1).docx | DOCX document | |
| ATTACHMENT_10_Past_Performance_Questionnaire.docx | DOCX document | |
| N68335-17-R-0010.docx | DOCX document | |
| ATTACHMENT_9_CPARS_Update_Questionnaire.docx | DOCX document |
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
N68335-17-R-0010
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION A - SOLICITATION/CONTRACT FORM
The following have been added by full text:
AMENDMENT 0001
The purpose of this amendment is to change the due date for receipt of proposals from 10 May 2017 to 3 April 2017; to remove Attachment 1 SERD 2522 Performance and Acceptance Test Plan; renumber the Attachments in Section J and provide Attachment 1 V-22 Program Configuration Management Plan; and to change references for drawing attachments to “Attachments 2 through 6” and for the CPARS Update Questionnaire and Past Performance Questionnaire to “Attachment 8” and “Attachment 9”, respectively, in Section L. All other terms and conditions remain unchanged.
The point of contact for this amendment is Alice Tornquist, at alice.tornquist@navy.mil or 732-323-4316.
SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS
The following have been modified:
TABLE OF CONTENTS
Exhibit/Attachment Table of Contents
| DOCUMENT TYPE |
| DESCRIPTION |
| PAGES |
| DATE |
| Exhibit A |
| CDRL Data Item No. A002 |
| 1 |
| 16-JUN-2016 |
| Exhibit A |
| CDRL Data Item No. A001 |
| 1 |
| 06-JUN-2016 |
| Attachment 1 |
| V-22 Program Configuration Management Plan |
| 52 |
| 01-SEP-2014 |
| Attachment 2 |
| Parts List PL901-220-971-103 |
| 2 |
| Attachment 3 |
| Drawing 901-220-971 Sheet 1 of 3 Rev G |
| 1 |
| Attachment 4 |
| Drawing 901-220-971 Sheet 2 of 3 Rev G |
| 1 |
| Attachment 5 |
| Drawing 901-220-971 Sheet 3 of 3 Rev E |
| 1 |
| Attachment 6 |
| Drawing 3909AS9999 Rev B Sheets 1-2 |
| 2 |
| Attachment 7 |
| Email Address List for |
CDRLs
| 1 |
| 26-OCT-2016 |
| Attachment 8 |
| CPARS Update Questionnaire |
| 1 |
| Attachment 9 |
| Past Performance Questionnaire |
| 2 |
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been modified:
DD2345 REQUIREMENT
Digital copies of Attachments 2 through 6 will be sent to qualified offerors who have provided a valid DD2345 Militarily Critical Technical Data Agreement to Alice Tornquist via email at alice.tornquist@navy.mil.
SECTION L - (1)
CONTENT OF PROPOSALS (SUPPLIES)
PART A GENERAL INSTRUCTIONS
1.0 GENERAL
The Offeror is required to submit sufficient information concerning the following areas to enable Government personnel to fully ascertain capabilities of the Offeror to perform the requirements. The proposal must be sufficient in detail and scope to permit evaluation and provide the evaluators a clear understanding of the Offeror’s capability to meet or exceed the defined elements as required by the solicitation. All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the requirements, associated risks and is able, willing and competent to devote the resources necessary to meet the requirements, and that the Offeror has valid and practical solutions for all requirements and potential risk areas. Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The Offeror has the burden of proof to demonstrate compliance with all the evaluation factors and or sub factors identified in this solicitation. With the exception of the Price/Cost volume, no cost or pricing information should appear in any volume. Alternate proposals are not acceptable.
In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. The Offeror is responsible to present enough information to allow the Government to evaluate the proposed work effort, support, and approach, as well as the price/cost proposal without opening discussions. Statements that the prospective Offeror understands, or can and/or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may render a rating of unacceptable.
The Offeror must include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. Since proposals will be evaluated on a lowest priced, technically acceptable (LPTA) basis, failure to address a specific factor or sub factor clearly will render the proposal as unacceptable. There is no need to repeat information in more than one volume if an overlap exists; the detailed information must be included in the most logical place and summarized and referenced in other areas. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.
The Offeror is expected to comply with all requirements of the RFP. The Government advises the Offeror that taking exception or deviating from any term or condition of the RFP may make an offer unacceptable, and the proposal un-awardable, unless the RFP expressly authorizes such an exception or deviation with regard to that specific term or condition. Since this is an LPTA evaluation, the government expects to make an award without discussions. The government reserves the right to award a single contract.
Throughout these instructions, a “principal subcontractor” is defined as a subcontractor who provides at least 25% of the proposed total price/cost (excluding the Offeror’s profit/fee), for the contract. “Team member” is defined as those entities that make up a joint venture or any other partnership or teaming arrangement formed for the purpose of responding to this solicitation. “Critical team member” is defined as those entities of the Offeror that perform a critical function in the performance of the resulting contract, whether it is technical or financial, and/or that have important roles in any high or medium risk areas identified in the Offeror’s proposal.
2.0 PROPOSAL FORMAT
Written proposals must be formatted for standard 8.5 x 11 inch paper. All pages should be numbered with section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to approximately 8.5 x 11 inch standard size and will count as 1 page. Graphs shall be presented in no smaller than a 10 pt font and should contain a grid, which allows values to be read directly from the graph to the same accuracy that a 10 x 10 to the ½ inch grid provides. Graphic resolution should be consistent with the purpose of the data presented. Due to shelving limitations at the NAVAIR filing facility, submission of proposals in three-ring binders is not desired.
The Offeror will provide one complete copy of the written proposal to the Procuring Contracting Officer PCO as electronic files fully compatible with Microsoft Office 2000 and for information not supported by MS Office products, with the latest Adobe Acrobat reader on a CD-ROM. The Offeror will ensure that the Price/Cost Volume is provided on a separate CD-ROM. Each CD-ROM is to be labeled for content and the Offeror’s name. If a discrepancy exists between the original paper copy of the proposal and the disk copy, the paper copy will take precedence.
The Offeror must present proposal information in a manner that facilitates a one-to-one comparison between the information presented and this Proposal Instruction. Proposal information must be structured such that its paragraph number/letter is identical to the Proposal Instructions paragraph number to which it is responding, although the Offeror may add lower tier subparagraphs. The Offeror must provide reasons it will not provide information for a particular paragraph. The proposal information instructions are structured by paragraph numbers where first, second, third, and fourth parts correspond to the volume, book, section, and element, etc., in Offeror’s proposal.
3.0 PROPOSAL CONTENT AND VOLUMES
The Peculiar Support Equipment (PSE) end item of this procurement relates to the following item and drawing number:
Part #: 901-220-971-101 Dwg # 901-220-971
Each volume of the proposal shall be submitted as one original and additional copies as specified in the table below. All volumes of the original proposal shall be delivered to the address provided in Section 4.0 prior to the closing date/time stated in this solicitation. Page limitations for each volume if any, are also specified in the table below; title and table of contents pages do not count towards page limit. Proposal pages beyond the specified maximum limit will not be reviewed as part of the evaluation.
Information submitted as an Annex to the proposal includes manuals, specifications, plans, procedures, and policies that exist as an official document of the company or facility, as well as other information requested in Part B Specific Instructions. Annexes do not have page limitations.
| Volume Number |
| Volume Title |
| Maximum Page Limit |
| Copies Required |
| 1 |
| TECHNICAL |
| 30 |
| 1 Original/3 Copies/1 CD |
| 2 |
| PAST PERFORMANCE |
| 10 |
| 1 Original/1 CD |
| 3 |
| PRICE/COST |
| No page limit |
| 1 Original/1 CD |
Each volume shall contain the following information:
| Cover and title page |
| Title of proposal and proposal number as applicable |
| Offeror’s name, address and POC |
| RFP number |
| Proposal volume/book number |
| Copy number |
| Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements) |
Identify lot(s) proposed to Use tabs and dividers
The Offeror shall submit a Cross Reference Matrix (CRM) for the Technical Volume, similar to the example below, to help ensure that all solicitation requirements are addressed and to facilitate the evaluators’ review of the Offeror’s proposal. The CRM should be a single integrated matrix and cross-reference the proposal volumes and paragraphs to specific RFP requirements, as well as other parts of the proposal that contain relevant information. The Offeror’s CRM may be identical to the example below or revised such as to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. The CRM does not count against any of the proposal page limitations.
EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)
| Section L – Proposal Instructions |
| Government PWS/SOW |
| Section M – Evaluation Factor |
| Offeror’s Proposal Reference |
| CLIN Reference |
Volume 1 Technical Example: Para 3.1 Note: This column shall address all paragraphs in Sections xx and xy of the Performance Specification
| 2.A |
| Provide reference to Offeror’s Proposal Volume I – Technical. Example: Refer to appropriate page number in Offeror’s written proposal |
Volume 1 Technical
Volume 1 Technical
4.0 PROPOSAL SUBMISSION:
Clearly mark all packages with the solicitation number. The submission date for the original proposal shall be no later than the date and time specified in Block 9 of Standard Form 33 of the RFP. Volumes one (1), two (2) and three (3) must be submitted simultaneously by the closing date for receipt of offers, specified in Block 9 of Standard Form 33 of the RFP.
Offeror shall submit proposals via United States Postal Service or through a commercial carrier using the address provided below. Offeror shall not submit proposals by facsimile or electronically via email.
Naval Air Systems Command Code: AIR-2.5.2.2.2 Alice Tornquist Bldg 562-3 Hwy 547 Joint Base MDL, NJ 08733-5082 Solicitation Number: N68335-17-R-0010
5.0 CLASSIFIED DATA
All proposals must be UNCLASSIFIED
PART B SPECIFIC INSTRUCTIONS
1.0 VOLUME 1: TECHNICAL
Note: This volume shall not contain any reference to cost or price aspects of the offer.
1.1 The Offeror shall provide all information and data required to conduct a thorough and complete technical evaluation. The Offeror shall address the following in the proposal:
The Offeror shall provide a complete schedule illustrating the proposed approach to completing the work described in the O&I Level PSE Tool Set, Heat Gun Statement of Work (SOW) (Section C of this solicitation) and drawings (Attachments 2 through 6). The Offeror shall include all subcontracted work and show all processes in order to ensure it demonstrates a thorough understanding of how it will produce the requirements within the required delivery schedule. The Offeror shall also provide accompanying narrative to describe its production approach, production capacity, facilities, equipment, personnel qualifications, and internal processes that demonstrate its ability to meet the Government requirements set forth in the SOW and drawings.
More specifically, the Offeror shall discuss:
1. How it intends to meet the technical specifications set forth in the drawings.
2. Manufacturing approach (planning/implementation/sustainment of production/ management of resources to meet delivery schedules). This should include the capacity of the production facility- the offeror shall demonstrate to the Government that their production facility will be able to accommodate the quality fabrication and timely delivery of the Heat Gun in addition to their current and anticipated workload. The Offeror shall also identify potential manufacturing risks and corresponding mitigation plans to be implemented in order to maintain the schedule. Finally, the Offeror shall demonstrate experience in timely manufacturing items of similar complexity.
3. Personnel and other resources needed to support the fabrication and production for the proposed effort. Identify whether those resources are presently available for allocation in support of this requirement. If the resources are not currently available, the Offeror shall detail their plan to obtain those resources and/or train the necessary personnel to meet the contractual requirements. Personnel skill, qualifications & certifications – this will include qualifications, certifications, experience and numbers of personnel that will be dedicated to this effort.
4. Quality Assurance – The Offeror shall describe any quality control or other quality-related processes that will demonstrate its ability to produce and deliver consistently conforming products. The offeror shall demonstrate compliance with ISO 9000 or ANSI/Q9001/Q9003 or equivalent.
5. Subcontractor management plan – Offeror shall provide their protocol of their oversight of their subcontractors to insure delivery of a quality product on schedule.
2.0 VOLUME 2: PAST PERFORMANCE
2.1 General
The Offeror shall identify any contracts performed within five years of this proposal submission date which contain efforts similar to those performed by Offeror, Offeror’s principal subcontractors, and critical team members in solicitation. e.g., tasks, complexity, contract type, contract dollar value, etc. Commercial contracts may be included. List the contracts from the most relevant to the least relevant. In general, recent performance will be considered more relevant than older performance. When possible, these contracts should include at least five of the most relevant contracts for the prime contractor, five of the most relevant contracts for each critical team member, and two of the most relevant contracts for each principal subcontractor (as defined in Paragraph I, General Instructions). If proposing as joint venture/single legal entity (JV/SLE), the Offeror should provide the five past performance references for the JV/SLE. If less than the five past performance references are available for the JV/SLE, each member of the JV/SLE should individually submit the five references in addition to their JV/SLE references.
For each contract identified, provide contract data, relevancy, past performance, and systemic improvement information as described below. Demonstrate the relevancy of the Offeror’s, and if applicable, the Offeror’s principal subcontractors’ or critical team members’ past performance and systemic improvements with respect to the solicitation requirements. For each past performance problem identified, describe the status of the systemic improvement efforts and, where applicable, demonstrate the impact that the systemic improvement effort had on resolving the problem such that it would not reoccur.
For contracts that have CPARS Reports that are more than six months old, e.g., the completion date is more than six months before the due date for this Past Performance Volume; the Offeror will forward a copy of the CPARS Update Questionnaire (Attachment 8) to that contract customer’s Program Manager. For all contracts identified which do not have CPARS Reports, the Offeror will forward a copy of the Past Performance Questionnaire (Attachment 9) to that contract customer’s PCO, Administrative Contracting Officer, and Program Manager.
The Offeror shall provide written consent from their principal subcontractors and critical team members that will allow the Government to coordinate their Past Performance issue(s) with the Offeror. If the Offeror does not submit such written consent, then the Government will address any past performance issues directly with the principal subcontractor or critical team member and the Offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any principal subcontractors and critical team members that do not provide such written consent, provide a point of contact (name, address, phone number, and email address) with which the Government may coordinate these issues and obtain any responses as needed.
The Government may use information other than that provided by the Offeror in their proposals to evaluate past performance. The Government may use Past Performance information obtained from sources other than those identified by the Offeror. The Past Performance Information Reporting System (PPIRS) will be the primary method used to evaluate Past Performance. It is incumbent upon the Offeror to explain the relevance of the data provided. The Government has no duty to search for data to cure the problems it finds in the information provided by the Offeror. The Offeror has the burden of providing thorough and complete past performance information.
(a) Contract Data Provide the information identified below separately for each relevant contract:
1. Description of item(s) provided
2. Contract number/type
3. Procuring agency (include POC contact information)
4. Description of product
5. Date of Contract award and delivery schedule
6. Dollar value of contract
7. Place of Performance (with explanation if different than for this contract)
8. CPARs (yes/no) - CPARS completion date - on DOD PPIRS (yes/no) 9/ Relevancy (see below)*
*- Relevancy – Provide a concise assessment of the degree of relevancy that each contract identified has to the solicitation; identifying tasks and/or aspects of the effort undertaken on the contract that are relevant to the program. Also provide the Offeror’s assessment of the relevancy of the contract in terms of one of the following ratings: Very Relevant (V), Relevant (R), Somewhat Relevant (S), or Not Relevant (N) where:
Past Performance Relevancy Ratings
| Rating |
| Definition |
| Very Relevant |
| Present/past performance effort involved essentially the same scope and magnitude of effort and complexities this solicitation requires. |
| Relevant |
| Present/past performance effort involved much of the magnitude of effort and complexities this solicitation requires. |
| Somewhat Relevant |
| Present/past performance effort involved some of the scope and magnitude of effort and complexities this solicitation requires. |
| Not Relevant |
| Present/past performance effort involved little or none of the scope and magnitude of effort and complexities this solicitation requires. |
(b) Relevancy -The Offeror shall explain what aspects of the contract are deemed relevant to the proposed contract. At a minimum, identify key or critical tasks of the solicitation and indicate the relevancy of the “past performance” contract to these tasks. Also identify where contract performance took place and provide rationale why it is relevant to the solicitation if the location is different from where the related effort is proposed to take place.
(c) Past Performance Information-The Offeror shall provide a brief description of performance in delivering quality products in each of the following areas: 1) meeting technical requirements, i.e., the quality of technical performance, e.g., performing analysis, design, testing, etc., 2) meeting schedule requirements, i.e., schedule performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc., 3) controlling contract cost, i.e., cost performance, e.g., on time or late delivery, modification of original schedules and reasons for any changes, etc., and 4) managing the contracted effort, i.e., program management, e.g., cooperation with customer, subcontract management.
(d) Systemic improvement Information-Identify those systemic improvement actions taken to resolve past problems. Describe the techniques, elements, and tools used to correct problems and, if applicable, how these techniques, elements, and tools will be used during this contract.
For the purpose of this solicitation, relevance is defined as something that has a logical connection with the matter under consideration. Such aspects of relevance include the type of effort (e.g., development, production, repair), the type of requirements (e.g., weapon systems, information systems, engineering services, scheduled depot maintenance), service similarity, service complexity, contract type, contract dollar value, the division of the company that will perform the work, and degree of participation by principal subcontractors, team members, or critical team members. Recency is defined as performance within 5 years of the date of this proposal submission.
3.0 VOLUME 3: PRICE/COST PROPOSAL
3.1 Volume Content:
(a) This Volume shall contain the information requested in RFP Section B below and shall include a copy of Section B with the Contract Line Item (CLIN) and Sub-CLIN Unit Prices and for evaluation purposes, the Total Prices filled in (Supplies and/or Services and Prices and/or Costs) using the estimated quantities value in the solicitation.
(b) All price/cost and price/cost supporting information shall be contained in section B and the price/cost proposal. No price or pricing information shall be included in any other technical volume including cover letters. Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate their price/cost proposal.
3.2 Ground Rules and Assumptions:
(a) In the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors and may conduct negotiations with the Offeror, pursuant to FAR Part 15.403-4, in order to ensure a reasonable and realistic price/cost. Further, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2. Offeror shall acknowledge the requirement to provide additional cost or pricing information and certify the data prior to award if/when requested by the Government.
(End of Summary of Changes) image1.wmf
File details come from the government source that posted it. Updated .