SUAS_CDL_RFP.pdf

PDF 173 KB Posted

Attached to
Common Data Link (CDL) Communications for Small Unmanned Aircraft Systems (SUAS)
Solicitation number
14-0001
Issued by

About this file

SUAS CDL Request for Proposal

View the file

Other files

Show all 12

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

INL FORM

PROC-1811

08/30/2010

IDAHO NATIONAL LABORATORY

REQUEST FOR PROPOSAL NO. 14-0001

SUBJECT: Common Data Link (CDL) Communications for Small Unmanned Aircraft Systems (SUAS)

PRE-PROPOSAL TELECONFERENCE: November 19, 2013

RFP ISSUE DATE: November 8, 2013 INTENT TO BID AND FINAL QUESTIONS DUE: November 22, 2013 PROPOSAL DUE DATE: December 18, 2013

CONTRACT ADMINISTRATOR: Kort Bowman

TELEPHONE NO.: (208) 526-0154

E-MAIL: Kort.Bowman@inl.gov

08/30/2010

Idaho National Laboratory Request for Proposal No. 14-0001

1. INTRODUCTION

1.1. This is a Request for Proposal (RFP) in support of a Department of Defense initiative, prepared by The Department of Energy’s Idaho National Laboratory (INL) through Battelle Energy Alliance, LLC (BEA), the INL Management and Operating (M&O) contractor. Under no circumstances shall the recipient of this RFP contact any individual (excluding contact with INL Ombudsman, see RFP Special Considerations paragraph 4.6.1), other than the Contract Administrator named herein, regarding this RFP.

The RFP seeks proposals for Small Unmanned Aircraft System (SUAS) Common Data Link (CDL) terminals to be developed through an aggressive, competitive, two-phased acquisition effort. Phase One is Capability Development and Laboratory Demonstration. Phase Two is Terminal Development and Flight Demonstration.

This Request for Proposal is for Phase One work only (see Statement of Objectives (SOW- 11049)). As appropriated funding permits, Phase Two will be issued under a separate, competitively-awarded contract. However, a full set of Phase Two requirements are also provided at this time to guide Phase One development decisions and allow vendors to plan for the entire project.

The INL anticipates making multiple Phase One awards. The INL may down-select to one or more vendors to continue into Phase Two, but reserves the right to not make any Phase Two awards. The overall goal of this effort is to develop production-representative terminals. It is anticipated there will be some post-Phase Two activities required to fully certify the terminals with respect to environmental and information assurance requirements.

If the government decides to move forward with Phase Two, only vendors selected for an award under Phase One will be requested to provide a proposal for Phase Two.

It is expected that there will be two 12-month development phases (12 months for Phase One & 12 months for Phase Two). Accelerated vendor schedules are acceptable, although competition concerns and funding availability may limit flexibility in the timing of any Phase Two awards.

Phase One – Capability Development and Laboratory Demonstration

• Vendor demonstration of BE-CDL capabilities identified in Appendix A of the attached Statement of Objectives (SOW-11049) Phase Two – Prototype Development and Flight Demonstration

• Flight demonstration of capabilities identified in the Technical and Functional Requirements (TFR-861).

1.2. You are invited to submit your best estimated ceiling price proposal for performing in accordance with the requirements set forth in the Draft Contract No. 14-0001.

1.3. All vendors intending to respond to this RFP must declare their intention to bid by registering with the BEA Contracting Officer no later than 5:00 p.m. MST November 22, 2013. RFP Section 4.6.3 provides details for registering. Vendors not complying with this requirement will be considered nonresponsive.

1.4. Pre-proposal conference:

1.4.1. A pre-proposal conference (Industry Day) for prospective Offerors (lower-tiers are encouraged to attend) will be held via teleconference at 1 p.m. MST on Tuesday, November 19, 2013. All prospective Offerors must submit a written request to participate, no later than November 15, 2013, to the INL Contract Administrator via email (kort.bowman@inl.gov). The teleconference access information will be provided via email after the Contract Administrator has approved the

08/30/2010

Idaho National Laboratory

Offeror’s request. Offerors are asked to limit their participation at the conference to no more than three dial-in lines. Please submit any questions/comments for the pre-proposal conference to the Contract Administrator via email (kort.bowman@inl.gov) by November 15, 2013. Offerors will also have the opportunity to ask questions at the conference in the general meeting. Responses to all generic questions will be furnished to all Offerors by the Contract Administrator through a posting on FEDBIZZOPPS. Questions concerning technical documentation will be answered via email only to registered vendors.

1.4.2. A Technology Day is tentatively scheduled to be held in the Baltimore, MD area in early December 2013 to provide information on recent CDL communications security developments.

Offerors not already registered to attend the Technology Day may do so by going to the website:

https://www.nsaarc.net and following the login instructions there to access registration information. Technology Day registration must be completed no later than November 15, 2013

1.4.3. The CDL Technical Working Group meets frequently to address CDL technical issues and proposed specification changes. Vendors are invited to participate in this forum. The next meeting will occur from November 19-21, 2013 in the Hanscom AFB, MA area. Offerors interested in attending this Technical Working Group meeting to participate in the BE-CDL specification development process may contact ESC.HNAB.CDL@hanscom.af.mil for details.

1.5. Any questions or comments relative to this RFP shall be submitted to the Contract Administrator via email (kort.bowman@inl.gov) in writing, no later than November 22, 2013. The responses (questions and answers) will be transmitted through a posting on FEDBIZZOPPS. Questions concerning technical documentation will be answered via email only to registered vendors.

1.6. Sensitive Unclassified Information: As described in Section 4.6.3 this RFP contains information that must not be accessible by any foreign national, i.e., non-U. S. Citizen, including employees. You are required to control the information in this RFP to ensure against access by any foreign national. If a recipient of this RFP is not awarded a contract, all (including any copies made) documents containing sensitive unclassified information must be returned to the Contract Administrator or be certified to the Contract Administrator, via INL Form Certification of Destroyed Sensitive Unclassified Information, as having been destroyed beyond reclamation.

2. SOCIOECONOMIC CLASSIFICATION

2.1. Classification Code: This procurement falls under North American Industry Classification System (NAICS) Code: 541712 (Description: Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology), Size Standard: 500 Employees). The stated size shall be the sole determining factor as to classification (small or large business) of an Offeror. It is the responsibility of the Offeror to certify its size on the enclosed INL Proposal Form, PROC-2120.

3. BASIS FOR AWARD

3.1. Selection Method: Awards will be made to the Offeror(s) whose proposal(s) are determined to provide the best value to INL, where both pricing and technical ability will be taken into consideration for award purposes. Multiple awards are anticipated as a function of federally appropriated and available funding. Awards will be made to the Offeror whose proposal provide the best value to INL, i.e., awards may be made to Offerors other than the one proposing the lowest price. The best value determination will follow the sequence presented herein.

3.1.1. After meeting the Mandatory Requirements, INL will evaluate and rank submitted proposals strictly in accordance with the evaluation criteria described in Section 3.5.

08/30/2010

Idaho National Laboratory

3.1.2. The price component of the proposal evaluation will not be scored but will be evaluated on reasonableness and the most advantageous probable cost to INL.

3.1.3. Upon completion of the technical proposal evaluation and the price offer evaluation, comparisons will be made, trading off the differences in capability and price. INL will continue to make comparisons until it is determined which proposals/offers represent the best value to INL.

3.2. Teaming Arrangements: Teaming arrangements are acceptable and shall be in the form of an Offeror/lower-tier relationship. The proposal shall be submitted to INL from one Offeror (the “prime” Offeror) with the responsibilities and capabilities of the lower-tier member(s) clearly stated in the proposal.

3.3. Mandatory Requirements: If an Offeror cannot meet, or does not address compliance with the following mandatory (go/no-go) requirements, its proposal will be considered nonresponsive and will not be evaluated further:

No. Mandatory Requirements

1 Offeror, or its lower-tier member(s) and or teaming partner(s) shall demonstrate applicable experience in the development of military and/or commercial radio terminals.

2 Offeror, or its lower-tier member(s) and or teaming partners(s) shall demonstrate applicable experience in the integration of military encryption capabilities into military and or commercial radio terminals.

3.4. Evaluation Criteria: Offeror’s response to each of the stated evaluation criteria via its technical submission will be evaluated in terms of favorability against the Phase One requirements. (For the sake of consistency please structure your proposal to match the order of the evaluation criteria, no more than thirty (30) pages total).

3.5. Relative Weighing of the Criteria: The following criteria are listed in descending order of importance:

3.5.1. Technical Qualification Criteria (maximum of 25 pages):

3.5.1.1. Technical Approach – Provide a technical approach to safely meet the requirements of Statement of Work No. 11049 (SOW-11049), including descriptions of how proven and reliable processes and techniques will be utilized to complete the work.

3.5.1.2. Project Control Documentation – Provide a Work Breakdown Structure and 12 Month Project Schedule to be used as companion documents to validate proposed cost and schedule.

3.5.1.3. Technology Maximization – Describe Offeror’s ability to maximize performance parameters (range, data rates, environmental parameters, etc.).

3.5.1.4. Technical Risk – Describe any technology innovations required for the proposed technical approach and associated risk.

3.5.1.5. Resources & Availability –Offeror’s availability and access to research, test facilities, equipment and proposed staff. Also, address how key personnel will be retained for the duration of the project.

08/30/2010

Idaho National Laboratory

3.5.1.6. Personnel Experience – Identification of key personnel and their relevant experience working within the technology required to successfully complete the subject Statement of Work.

3.5.2. Company (including team members) Qualification Criteria (maximum of five pages):

3.5.2.1. Experience – Provide recent (i.e., within the last 5 years) experience of successfully completing relevant projects of similar technical complexity, cost and schedule. Offeror shall provide Contract Number, Organizational Name, Organizational Point of Contact (including phone number and email), and dollar value for each successfully completed contract with similar scope and tasking to the requirements of this RFP. Provided must be a minimum of two (2) examples demonstrating the following (maximum of five (5) pages):

3.5.2.1.1. Capability – Offeror’s ability to provide new and creative solutions that advance knowledge, understanding, technology, and state of the art solutions.

3.5.2.1.2. Capacity & Controls – Offeror’s ability to meet proposed cost and schedule requirements.

3.6. Price Proposal: Offeror must provide a realistic price proposal (ceiling). The proposal will be analyzed to assess the Offeror’s understanding of the requirements of this RFP. The price component will be evaluated on reasonableness and the most advantageous probable cost to INL. The price proposal must be summarized on Form PROC-2120 (Proposal Certification), and supported by a detailed cost breakdown. The price proposal shall include the following:

3.6.1. Labor Ceiling: Offeror shall provide the fully-burdened hourly labor rates and proposed hours for each proposed individual. The fully-burdened rates shall include all elements of direct cost, indirect cost, and profit. The profit component (percentage) of the fully-burdened rates shall be identified. The total of the fully-burdened rates times the hours for each person will constitute the “labor ceiling” for the contract. In the event that labor is required to complete the work scope in excess of this established labor ceiling, such additional labor, (if prior approved by INL), will be paid less the profit (the percentage identified in the proposal) of the fully-burdened hourly rates proposed.

3.6.2. Materials: Offeror shall provide the ceiling price for any materials required for the successful completion of this contract. Offerors may propose a reasonable “material handling fee” which may be added to material costs. The material handling fee is not G&A or profit. By application of the material handling charge, Offeror certifies that such costs are excluded from the indirect rates it applies to labor. No other adders besides the material-handling fee may be applied to material costs. Reimbursable costs of materials shall be limited to the amounts actually paid by the Offeror.

3.6.3. Travel: Offeror shall provide the ceiling price for any travel expense required under this contract.

(Please note that travel must be billed according to Federal Travel Regulation limits and guidelines). No adders may be applied to travel expense.

3.7. Right to Reject: The right is reserved by INL to reject any and all proposals and to disregard minor irregularities in proposals received. Offerors are advised that, although negotiations and a request for best and final offers may follow receipt of proposals, award may be made without discussions on proposals received. Thus, proposals should be submitted initially on the most favorable terms of price, technical compliance, and completeness.

08/30/2010

Idaho National Laboratory

3.8. Competitive Range: If INL determines that revised proposals or best and final offers are necessary, INL may solicit them from only those Offerors deemed by INL (based upon evaluation of the current proposals) to have a reasonable chance to be selected for award, i.e., the competitive range.

4. PROPOSAL SUBMITTAL REQUIREMENTS

4.1. Proposal Due Date: The proposals are due by 4:00 p.m. MST on December 18, 2013. The proposals shall be mailed to: Kort Bowman at 1765 N. Yellowstone Hwy, Idaho Falls, ID 83415-3725. The Technical and Price Proposal shall be separate volumes. The Technical Proposal will contain items 4.5.1 below. The Price Proposal will contain items 4.5.2, 4.5.3, and 4.5.4, below.

4.2. Late Proposals: Proposals received after the designated date and time, i.e., late, will be returned without opening.

4.3. Proposal Packaging: Responses shall be submitted in hard copy form. Responses shall be submitted in two separate, sealed envelopes (a price proposal and a technical proposal), to allow technical evaluation of proposals without access to price information. These envelopes shall be clearly marked as follows:

“Price Proposal, RFP No. 14-0001” and “Technical Proposal, RFP No. 14-0001”. The price proposal envelope shall include six (6) bound priced copies; the technical proposal envelope shall include six (6) bound unpriced copies. The separately sealed price proposal and technical proposal shall both be placed in another sealed envelope/package.

4.4. Format Requirements: Proposals shall be submitted in strict compliance with the following requirements:

4.4.1. A concise proposal consisting of the Technical Approach limited to twenty-five (25) pages (8 ½

in. by 11 in. paper) inclusive of cover pages, figures, charts, etc. and documentation of Experience limited to five (5) pages (8 ½ in. by 11 in. paper).

4.4.2. All pages will contain no less than 1 inch margins on top, bottom and sides of the page in which no proposal specific information is allowed. Company identification, distribution markings and page numbers are allowed in the margins.

4.4.3. Document text will be limited to Arial font, no smaller than 12 point. This text restriction does not apply to any figures, charts, tables, schedules, graphs, etc., but graphics may not be evaluated if they cannot be clearly interpreted.

4.5. The following must be completed and submitted to INL (Note: Specified forms are provided with this

RFP):

4.5.1. Technical Proposal: Technical proposal as described in Section 3.5.1 & 3.5.2.

4.5.2. Price Proposal: Price proposal as described in Section 3.6.

4.5.3. Form PROC-2120, Proposal Certification: (In accordance with the requirements of the draft Contract, Offeror's price proposal shall include Idaho sales tax for any materials specified under this RFP, if any.)

4.5.4. Certificate of Current Cost or Pricing Data Form PROC-1814 and Form PROC-1810, Contract Pricing Proposal Sheet, which incorporates all data submittal requirements.

4.5.5. The following additional documents will be required of the successful Offeror(s) prior to contract award:

08/30/2010

Idaho National Laboratory

4.5.5.1. Form PROC-1860, Small Business and Small Disadvantaged Business Subcontracting Plan. Large businesses only must submit this plan. For this solicitation, a large business is defined as more than 500 employees.

4.5.5.2. IRS Form W-9.

4.5.6. Failure to submit any of the foregoing, at INL's discretion, could result in the Offeror being determined non-responsive.

4.6. SPECIAL CONSIDERATIONS

4.6.1. Ombudsman Program: Offeror is hereby notified that issues/concerns relative to this solicitation and/or any resulting contract award that are not resolved by the Procurement Agent identified herein shall be resolved through INL's Ombudsman Program (Phone: (208) 526-7711). Any issue/concern shall be submitted, in writing, no later than 30 calendar days after contract award to be considered for review.

4.6.2. Voluntary Protection Program (VPP): The INL Voluntary Protection Program (VPP) has been established to promote and ensure a safe and healthful work site that is free of injury and illness.

The INL is a VPP Star Site and is committed to maintaining that designation. Offerors desiring to perform work at the INL must commit to participate in INL's VPP. This commitment will ensure a safer environment for everyone working at the INL. Questions pertaining to the VPP should be directed to the Procurement Agent named herein.

4.6.3. Registration and Request Procedure for RFP Technical Data: This solicitation is restricted to U.S.

companies. A significant amount of additional technical documentation will be necessary to respond to this RFP. This documentation is available through the INL Contracts Office Point of Contact, kort.bowman@inl.gov. To request the additional technical documentation, the following information must be provided in the requesting email:

Company Name

Physical and Mailing Address

Company Point of Contact (Name/email/telephone)

CAGE Code

Prior to release of additional technical information, vendors will be validated by CAGE Code via the Joint Certification Program (JCP) website at http://www.dlis.dla.mil/JCP/. Vendors not currently registered in the JCP may follow the instructions on the website to become certified, if they meet the eligibility requirements. All requests for technical documentation must be made to the Contract Administrator no later than November 22, 2013. Technical documentation will not be sent out in response to late requests.

4.7. PROPOSAL INSTRUCTIONS

4.7.1. Interpretations and Exceptions:

4.7.1.1. Offeror shall submit its proposal on the basis of compliance with the RFP requirements.

Any interpretation of the requirements by the Offeror may be considered an exception and treated accordingly, i.e., establish the offer as non-responsive. Offeror must obtain, from INL, concurrence/clarification regarding its interpretation to classify it (them) as compliant with, or exception to, the RFP requirement(s). Any exception must be documented as part of the proposal and priced as an alternative.

08/30/2010

Idaho National Laboratory

4.7.1.2. If Offeror takes exception to any RFP requirement(s), either technical or administrative, it shall be so stated in the proposal and formatted as follows:

4.7.1.2.1. Technical exceptions shall be numbered and attached to the technical proposal in a single document;

4.7.1.2.2. Administrative exceptions shall be numbered and attached to the price proposal;

and

4.7.1.2.3. Each exception shall be clearly and completely defined.

4.7.2. Rights Reserved by INL:

4.7.2.1. INL reserves the right to procure all or any part of the work specified from any Offeror and reserves the right to accept or reject any proposal with or without prior discussion with the Offeror.

4.7.2.2. INL reserves the right to conduct any necessary pre-award survey and analysis to evaluate an Offeror's capabilities to comply with the requirements of this RFP.

4.7.2.3. INL reserves the right to conduct a pricing audit to facilitate a determination of the reasonableness of proposed pricing.

4.7.3. Proposal Validity Period: A proposal shall remain firm for 90 days after the proposal due date, unless otherwise specified by the Offeror.

4.7.4. Proprietary Information:

4.7.4.1. If you can provide a proposal without proprietary information, INL prefers this approach.

If proprietary data/information is essential to an effective presentation of your proposal, please adhere to the following:

4.7.4.1.1. If it is possible to do so without destroying the effectiveness of your presentation, place all proprietary data in a separate document as an attachment or appendix to the appropriate proposal volume.

4.7.4.1.2. Each page containing proprietary data must be marked with the following legend, an alternative legend that INL specifically agrees to accept, or a statement that the documents are submitted pursuant to a specifically identified written agreement between you and INL defining the duties and obligations of the parties relative to the proprietary data: "This contains 'proprietary data', furnished under this Request for Proposal No. 14-0001 which may be duplicated and used by the U.S.

Government or its agents with the express limitations that the "proprietary data" may not be disclosed outside the U. S. Government and it’s designated agents."

Contact the Contract Administrator if the legend furnished by INL is not considered appropriate, must be revised, or should be replaced by a written agreement controlling submittal of proprietary data.

4.7.5. Discrepancies in the Request for Proposal: Should an Offeror find discrepancies in, or omissions from, the RFP, its attachments or related documents, or should Offeror be in doubt as to the meaning of any requirements, Offeror shall notify INL and obtain correction or clarification prior to submitting its proposal.

4.7.6. Proposals that fail to provide ALL items and quantities specified in this RFP may be deemed non-responsive in their entirety, and may not be considered for award.

File details come from the government source that posted it. Updated .