Atch_4_TO_Ordering_and_Admin_25Jun19.pdf

PDF 1 MB Posted

Attached to
MEUAS IV Draft RFP Federal contract opportunity
Solicitation number
H9240819R0001
Issued by
United States Special Operations Command

About this file

This document outlines task ordering procedures and contract administration for the Mid-Endurance Unmanned Aircraft Systems IV (MEUAS IV) indefinite-delivery/indefinite-quantity (IDIQ) contract. Key details include:

Task orders will be competed among all MEUAS IV contract holders using lowest price technically acceptable or other evaluation criteria specified in each task order request for proposal. One initial task order will be issued to meet the minimum guarantee. Task orders will be for unmanned aircraft systems and payloads to support intelligence, surveillance and reconnaissance requirements at various operational sites for periods including pre-deployment, integration, operations and post-deployment. Evaluation criteria for task order proposals include technical approach, past performance, price and compliance with requirements. Pricing shall be fixed-price to the maximum extent possible.

MEUAS IV Draft TO Ordering Guide and Administration

View the file

Other files for this federal contract opportunity

Other files attached to MEUAS IV Draft RFP, newest first.
File Type Posted
20190925_MEUAS_IV_DRFP_Q&As_Correction.pdf PDF
20190830_DRFP_QnA.pdf PDF
Atch_1_MEUAS_IV_PWS_18Jul19.pdf PDF
Atch_IV_PP_Questionaire_18Jul19.pdf PDF
Atch_2_MEAUS_IV_Draft_DD_Form_254.pdf PDF
Atch_V_TO_Notional_CLIN_30Jul19.pdf PDF
Atch_I_MEUAS_IV_Experience_Survey_30Jul19.pdf PDF
Atch_3_UCC__23Apr_2019.pdf PDF
Exbt_A_MEUAS_IV_CDRLs_17Jul19.pdf PDF
Atch_II_MEUAS_IV_CDP_18Jul19.pdf PDF
H9240819R0001_DRFP_30Jul19.pdf PDF
Atch_III_WSMR_Info.pdf PDF
Atch_5_MEUAS_IV_Acronym_List_17Jul19.pdf PDF
Show all 13

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

H9240819R0001 Attachment 4 25Jun19

MID-ENDURANCE UNMANNED AIRCRAFT SYSTEMS IV (MEUAS IV)

Task Ordering Procedures and Contract Administration

Table of Contents

1. General Task Order Award Procedures

2. TO-RFP

3. Task Order Proposal Submissions

4. Evaluation of Task Order Proposals

5. Authorization to Proceed on Orders

6. Task Order Options

7. Exercise of “Off Ramp” Procedures

8. Fair Opportunity

9. Order Ombudsman

10. Order Completion

11. Protecting and Handling Proprietary Information

12. Appendix

1. General Task Order Award Procedures

a. An initial task order (TO) to attend the initial Kick Off Meeting will be issued concurrently with the execution of the IDIQ contract, which will meet the Government’s minimum guaranteed purchase amount. Unless an exception to the fair opportunity requirement is approved, all MEUAS IV IDIQ contract holders will compete for subsequent new task orders, which may include one or more new or established sites. As requirements are identified, the Government will issue a TO Request for Proposal (TO-RFP) to all MEUAS IV IDIQ contract holders unless an exception to the fair opportunity requirement is approved. All task orders issued are subject to the terms and conditions of the basic contract. No work may be performed or any costs incurred until authorized by the Contracting Officer (KO) via a signed Task Order.

b. The following will apply without exception:

(1) Orders shall be made under the provisions of FAR 16.505 and these Task Ordering Procedures. References to FAR part 15 or any other policies, provisions, or procedures of the FAR are for clarity only, unless explicitly required to be followed by FAR 16.505 (e.g., FAR subpart 15.4).

(2) Contract holders are not guaranteed award of any task order beyond the initial task order.

(3) The Government intends to award primarily utilizing a Lowest Price Technically Acceptable (LPTA) process as set forth in these Task Order Award Procedures and each TO- RFP, but the Government reserves the right to utilize any evaluation scheme, advantageous to the Government, that would result in fair consideration being given to all contract holders in placing each order.

c. Above Threshold Technical Requirements: The Government may issue a TO-RFP with minimum technical requirements that are above thresholds, which may preclude some contract holders from being able to participate in the task order competition. Such contract holders shall submit a waiver in paragraph 2.d below.

d. Ordering Authority: TOs under this IDIQ contract will be issued only by SOF AT&L-KR

Division. The Contracting Officer (KO) administering the IDIQ contract is responsible for both the IDIQ contract and all TOs. Ordering Authority has not been granted to any other office in USSOCOM, DoD, or any other Government Agency.

2. TO-RFP

a. General: Unless otherwise specified in the TO-RFP, each contract holder shall have 10 business days to submit its proposal. A business day is defined as Monday through Friday, with the exception of federal holidays. The amount and detail of information required in the proposal may vary depending upon the evaluation criteria, which will be set forth in the TO-RFP (see sample in Appendix A).

b. TO-RFP Issuance: Unless an exception to the fair opportunity requirement is approved, the KO will issue a TO-RFP to all contract holders when the Government has a requirement established for a new task order. The TO-RFP will contain:

(1) Instructions to Offerors (ITO), which will provide the evaluation criteria being utilized, all information needed for the contract holder to scope its task order proposal, and instructions for proposal submissions. The Government’s operational requirements set forth in the ITO will be within the scope of the IDIQ contract PWS (Section J, Attachment 1).

(2) As necessary, other documents that further describe the Government’s operational requirements, which will also be within the scope of the IDIQ contract PWS (Section J, Attachment 1) requirements.

(3) Acceptable transmittal methods.

(4) A Total Evaluated Price workbook.

(5) Any other information considered to be of assistance to the contract holders in preparing a proposal.

c. Issuance of a TO-RFP will not obligate the Government to issue a TO, nor will it authorize the contract holder to perform any work pursuant to such TO-RFP prior to the execution of a TO or the contract holder’s receipt of an authorized Notice to Proceed by a warranted KO.

d. Proposal Waivers: Contract holders are required to submit a proposal for every requirement solicited unless granted a waiver in advance by the KO. The contract holder can request a waiver by submitting a detailed statement supporting the request to the KO. All statements shall be submitted to the KO prior to the required proposal submission deadline.

Submission timelines do not constitute a valid reason for not providing a detailed statement of reason(s) in requesting a waiver.

e. Non-Responsiveness: Contract holders that fail to submit a proposal for more than three

TO competitions in a fiscal year may be considered for Off-Ramping or Dormant status (described below), and the lack of participation may be used in any subsequent evaluation of past performance.

f. Urgent Requirement: In the event of an urgent requirement, each interested contract holder shall provide a written proposal within the timeframe specified by the KO (generally 1-5 business days) in the specified format. If an exception to fair opportunity is not approved and the urgent requirement is competed, a contract holder may provide written notice to the KO within 24-hours of its inability to participate and withdraw from that specific TO competition. This will not be included in the number of non-participations described in subparagraph e, but may be used in subsequent past performance evaluations.

g. Mission Capability Gaps: The Government may authorize one or more below threshold requirements at the TO level in order to facilitate an above-threshold capability in one or more technical requirements, and to address mission capability gaps while achieving specific capability objectives. For example, the Government may reduce the endurance requirement below threshold in order to meet a higher payload weight requirement. The acceptability of below threshold requirement(s) will be on a case by case basis and will be clearly identified within the TO-RFP.

3. Task Order Proposal Submissions

a. Alternate proposals will not be accepted.

b. File Naming Conventions: A standard naming convention for all files submitted shall be utilized. The convention is as follows: YYYYMMDD COMPANY (Abbreviated) Doc Name. For instance, a proposal submitted for operational site “SCAR 8” from the Acme Unmanned Aircraft Services Inc. on March 17, 2017 would be named: “20170317 KPR AUAS SCAR 8”. A support file would be named: “20170317 KPR AUAS SCAR 8 Prop Supp. The goal of the naming convention is to keep the name as short as possible while maintaining clarity of the document.

c. The proposal format for all task order proposals are:

(1) Text size shall be no smaller than what is equivalent to Times New Roman, 11 point, uncompressed font.

(2) Pages shall be single sided, lines shall be one and one half spaced, and margins shall be at least one inch on all sides.

(3) Pages shall be dated and numbered sequentially starting with page 1 per document.

The page count will be specified in the TO-RFP.

(4) Limit displays (tables, charts, graphs and figures) to only those not previously provided in the final proposal for the IDIQ contract; otherwise include a matrix for reference. If used, these displays shall be uncomplicated, legible and shall not exceed 11 by 17 inches in size. Foldout pages shall count as two pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for text. For displays, any accompanying text shall be related solely to the subject of the displays and no smaller than 8 point Arial font.

(5) Both an Adobe PDF and a Microsoft Office 2013 compatible version of all proposal documents shall be submitted. This includes an Adobe PDF of the TEP worksheet.

Compatibility to Microsoft Office 2013 is the offeror’s responsibility.

d. The standard requirements for all task order proposals are:

(1) All proposals shall have a validity period stated on the proposal. A validity period of at least 60 days after proposal submission is required, unless otherwise stated on the TO-RFP.

(2) Unless the ITO indicates otherwise, proposals shall include a Task Order Total

Evaluated Price (TO-TEP). In those circumstances where a tradeoff competition is utilized, the offeror will provide a TO-TEP and a price volume narrative for any COST CLINs proposed. A contract holder may be required to provide additional data in the event a cost realism evaluation of one or more fixed-price CLINs is deemed to be necessary.

(3) Once the maximum amount of pages has been reached, all remaining pages (not including a cover page) will be deleted/removed and the Government will not evaluate them.

Page removal may cause a proposal to be evaluated unfavorably.

(4) Each task order proposal will be evaluated without reference to any outside material.

A submission of “please refer to the prior proposal” or simply asserting the ability to meet a requirement without adequate explanation is unacceptable and will result in a determination of Technically Unacceptable for LPTA or as a Deficiency for Trade Off competitions.

(5) For firm-fixed-price (FFP) proposals (which may include certain standard Cost

CLINs for travel and ODCs), prices shall be inclusive of all related direct and indirect costs, plus profit. When other than certified cost or pricing data is required to evaluate prices, it shall be submitted within a timeframe sufficient to ensure complete analysis and effect award prior to the established beginning of the period of performance for the TO.

(6) For CPFF proposals, the offeror shall submit a cost proposal in accordance with

FAR 15.403, the TO-RFP, and this guide. The proposal will include the estimated cost and fee for each CLIN as well as a total estimated cost and fee. Costs will be submitted in the workbook shown in Appendix B of this guide. Offerors shall not re-format or remove cells from the required format. All cells containing costs shall be rounded to two decimal places. An approved accounting system is required for CPFF TOs in accordance with limits detailed in FAR 215-21.

(7) A task order may include a COST CLIN for meal reimbursement for sites that do not have a Government-provided dining facility. A daily rate will be negotiated and approved by the KO for each site, as needed.

(8) The Contract Data Requirements List (CDRL) at the task order level shall be the same as the MEUAS IV IDIQ contract CDRL, unless otherwise stated.

(9) Defense Priorities and Allocation Systems rating for all orders shall be DO-A1.

(10) Government Furnished Property, if required, will be stated in the TO-RFP

Instructions to Offerors. Each contract holder shall comply with FAR 52.245-1 and applicable supplements as stated in the MEUAS IV IDIQ contract.

(11) Task Order Options: Options may be included in a TO-RFP that are governed by the contract clause at FAR 52-217-9.

4. Evaluation of Task Order Proposals

a. The KO will lead the evaluation of each proposal and issue a TO based on the evaluation criteria set forth in each TO-RFP. The standard evaluation of orders will be an evaluation of the proposed technical approach to meet PWS requirements (technical proposal), past performance (which may be pulled from CPARS and other sources), and proposed costs and/or prices, as well as any other criteria stated in the ITO. Other specific procedures may be set forth in each TORFP. Such procedures may be similar to those found in FAR part 15; however, these fair opportunity competitions are solely governed by FAR 16.505, with the exception of price evaluation under FAR subpart 15.4.

b. The KO may:

(1) After review of TO proposals, communicate with contract holders whose proposals appear to have ambiguities; vagaries; inconsistencies; missing data; unreasonable, unrealistic, and/or unbalance costs or prices, and/or apparent mistakes. These contract holders may be allowed to modify their proposals without similar communications being held with all other contract holders. No communications will be undertaken with contract holders whose proposals are found not to have any ambiguities; vagaries; inconsistencies; missing data; unreasonable, unrealistic, and/or unbalance costs or prices, and/or apparent mistakes, or

(2) Reject one or more of the proposals, or

(3) Cancel the requirement and notify all contract holders of the cancellation, or

(4) Price will be evaluated in accordance with FAR subpart 15.4, as required by FAR 16.505.

5. Authorization to Proceed on Orders

In time-critical situations, after TO award decision, but prior to the contract holder’s receipt of the TO, the KO may direct the contract holder in writing (including email) to commence performance of the TO. The contract holder is not authorized to commence performance prior to the issuance of the TO or other written (including email) notice provided by the KO. In no case shall the contract holder commence work without explicit written (including email) approval from the KO.

6. Task Order Options

If options are utilized at the task order level, the exercise of any option will be accomplished in accordance with FAR 17.207. TO option periods will be outlined in each TO-RFP.

7. Exercise of “Off Ramp” Procedures

a. To ensure success of the MEUAS IV, each MEUAS IV contract holder is expected to: (i) participate in the ordering process by submitting proposals in response to all TO-RFPs; (ii) successfully perform their TOs, and (iii) promptly improve performance when it does not meet the requirements of the TO or IDIQ contract. In order to achieve the Government's goal of maximum competition under this IDIQ for all TOs, the annual assessment of performance will also take into consideration the number, value, and complexity of work assigned to each holder and amount of competition achieved.

b. The Government will review each contract holder's performance annually based upon information obtained from all evaluation areas in the contract holder Performance Assessment Reporting System (CPARS). The Government may also review a contract holder’s performance at any time whenever such review is deemed necessary in the sole discretion of the KO. If a prime contract holder receives "marginal" or "unsatisfactory" CPAR ratings in any assessment area, the Government may “off-ramp” the contract holder by:

(1) Prohibiting the contract holder from competing on future delivery/task orders under this IDIQ;

(2) Implementing a termination for convenience (if applicable and only if such action is in the Government’s best interest); or

(3) Taking any other action which may be permitted under the MEUAS IV IDIQ contract’s terms and conditions, for example (but not limited to) a contract holder being placed in a “Dormant” status.

8. Fair Opportunity

a. IAW FAR 16.505, the KO must provide each MEUAS IV contract holder a fair opportunity to be considered for each order exceeding $3,500 issued under multiple delivery-order contracts or multiple task-order contracts, except as provided for in paragraph (b)(2) of the reference.

b. It is the Government’s intent to ensure Fair Opportunity by focusing on TO level competition to the fullest extent possible in order to accomplish the USSOCOM Commander’s goals to provide the highest quality goods and services at the most fair and reasonable prices throughout the entire contract performance.

9. Order Ombudsman

The Task and Delivery Order Ombudsman is responsible for reviewing complaints regarding this IDIQ. The Ombudsman shall review complaints from any contract holder and ensure all contract holders are afforded a fair opportunity to be considered for award of TOs, consistent with the procedures of the contract. The SOCOM Ombudsman is assigned in accordance with

SOFARS 5616.506.

10. Order Completion

Within 90 days after the completion of FFP TOs, an authorized representative of the contract holder shall certify in writing to the KO that the TO is completely billed, remaining dollars of said amount can be de-obligated (if applicable), and all deliverables have been received and accepted by the Government. This information will be used as part of the final required documentation for contract closeout. The final closeout proposal shall include itemized Accounting Classification Reference Number (ACRN) de-obligations at the CLIN level per TO.

CPFF TOs will be closed out in accordance with DCAA procedures.

11. Protecting and Handling Proprietary Information

a. During contract performance each contract holder may, either directly or through the Government, receive proprietary technical data and/or payloads (hereafter “proprietary information"). The contract holder shall protect such proprietary information with the same caution that a reasonably prudent contract holder would use to safeguard highly valuable property. Proprietary information shall not be duplicated, used or disclosed in whole or in part, without prior written permission of the owner of the proprietary information and the Government, for any purpose other than to perform this contract. This restriction does not limit the contract holder's right to use, duplicate or disclose such information if such information was lawfully obtained by the contract holder from other sources.

b. The contract holder shall enter into written agreements with all companies whose proprietary information it receives to safeguard such information. In addition, the contract holder shall obtain individual non-disclosure agreements (NDA) from all employees who have access to such data. The contract holder shall furnish to the Contracting Officer Representative (COR) copies of these agreements and NDAs. The Government may reject and demand modification of any NDA the Government finds to be materially ineffective to protect the relevant data.

However, it is not the responsibility of the Government to draft any such NDA.

c. The contract holder shall include this provision, including this paragraph, in subcontracts of any tier which involves access to information covered in paragraph (a) above. The use of this clause in such subcontracts shall be read by substituting the word "subcontractor" for the word "contract holder" wherever the latter appears.

12. Appendix A

Appendix A is an example of a TO-RFP letter with attachments. This is an example only and the Government reserves the right to utilize any evaluation scheme, advantageous to the

Government, that would result in fair consideration being given to all contract holders in placing each order.

(END)

APPENDIX A

UNITED STATES SPECIAL OPERATIONS COMMAND

7701 TAMPA POINT BOULEVARD

MACDILL AIR FORCE BASE, FLORIDA 33621-5323

November 9, 2000

Directorate of Procurement

TO ALL MEAUS IV CONTRACT HOLDERS

You are invited to submit a proposal to U.S. Special Operations Command (USSOCOM) for Task Order (TO) Request for Proposal (RFP) “TORFP00XX-TITAN 9” per the enclosed RFP package. Your proposal must meet all requirements within the RFP Package and its attachment(s) in order to be considered for award.

This TO-RFP consists of one 6-month base period and two 12-month options. Only one

TO will be awarded based on a Lowest Price Technically Acceptable process decision. The Total Evaluated Price (TEP) workbook (Attachment 3 of this letter) indicates the Contract Line Item Numbers (CLIN) required to fulfill the PWS requirements. All items must be completed in order to be considered for award.

This RFP does not commit the Government to pay any cost for the preparation and submission of a proposal. Your System for Award Management registration must be current and no terminations listed in order to receive an award. Please submit your proposals via AMRDEC or your company’s FTP site (with access granted to the Contracting Officers).

The undersigned must provide approval to use any other method of delivery. Proposals shall be signed and dated by a person within your organization with the authority to bind your company.

Please be advised that SOFARS 5652.204-9003, Disclosure of Unclassified Information and Notification Requirements for Cyber Security Breaches (2013), in the IDIQ contract, applies to both successful and unsuccessful offerors and their subcontractors.

Consequently, submission of a proposal shall constitute your unequivocally agreement that you shall not release to anyone outside your organization any unclassified information, regardless of medium, pertaining to any part of this contract unless the Contracting Officer has given prior written approval. Should the Government be made aware of such disclosures of unclassified information, administrative action will be taken including, but not limited to, documenting the occurrence in any contract holder’s past performance rating.

Please be advised that the following FAR clause may be utilized in this task order:

FAR 52.217-9 – Option to Extend the Term of the Contract (a) The Government may extend the term of this contract by written notice to the Contractor within 45 days provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least 60 days before the contract expires. The preliminary notice does not commit the Government to an extension.

(b) If the Government exercises this option, the extended contract shall be considered to include this option clause.

(c) The total duration of this contract, including the exercise of any options under this clause, shall not exceed 3 years.

(End of Clause)

All submission items must reach the contracting officers, Jennifer.Metty@socom.mil and Christine.Johnson@socom.mil by the date and time stated the Instructions to Offerors (Attachment 1) of this letter in order to be considered. You may submit general questions for clarification of documents by email within two days of this letter.

We appreciate your support of the Special Operations Forces warfighter.

Sincerely, Jennifer A. Metty Contracting Officer

Enclosures:

1. Instructions to Offerors (ITO)

2. Payload Data Sheet (PDS)

3. Total Evaluated Price (TEP)

4. Payload Acceptance Checklist (PAC)

5. Cost Proposal Workbook (CPW)

INSTRUCTIONS TO OFFERORS (ITO)

Proposal #: MEUAS TO-RFP000X – TITAN 9

INSTRUCTIONS TO OFFEROR (ITO) and PERFORMANCE REQUIREMENTS

1.0 Background: The USSOCOM Fixed Wing Program Office for Airborne ISR has established a requirement for a new MEUAS-IV operational site. This requirement will be referred to as TITAN 9 and will replace the existing MEUAS site currently known as “ROMAN-11.” One spoke is required at this site. The ability to operate multiple Government Furnished Property (GFP) payloads simultaneously is required. Proposal contents should present a solution that clearly identifies technical, schedule, and price associated with providing a complete capability on day one of ISR. Only an MEUAS IV approved system will be acceptable. An MEUAS IV approved system is defined as the system(s) proposed, evaluated and incorporated into the MEUAS IV IDIQ contract.

2.0 Environmental Conditions (Estimated for the Site’s Region):

Field

Elevation

[ft]

Max

Density

Altitude

[ft]

Average of Density

Altitude

[ft]

Min of

Density

Altitude

[ft]

Max of

Outside Air

Temperature

[°C]

Average of

Outside Air

Temperature

[°C]

Min of

Outside Air

Temperature

[°C]

Max of

Barometric

Altitude [ft]

Average of

Barometric

Altitude [ft]

Min of

Barometric

Altitude [ft]

2250 6390 4700 3340 44 26 19 N/A N/A N/A

3.0 Period of Performance: The anticipated periods of performance for Pre- Deployment, Integration, ISR, and Post Deployment are noted below. Please note the Pre-Deployment requirements in PWS 3.5.1.

3.1 ISR: 900 Hours Per Month will be ordered

3.2 Pre-Deployment: Date of Task Order through 3 months

3.3 Integration: Concurrent with Pre-Deployment

3.4 ISR: Month 4 through Month 11

3.5 Post Deployment: Month 12

Options are included in this TO-RFP. If the first option is exercised, ISR will continue through Month 12 at the hourly rate for Month 5. Post Deployment will be de-scoped from the base period, and the funds de-obligated. Post Deployment will be ordered and funded for the last month of the option period. Subsequent options, if exercised, will follow the same general schema set forth in this paragraph.

4.0 General Information:

4.1 Submit your proposal IAW TO Ordering Procedures and information contained herein.

4.2 Due Date of Proposal: A complete proposal is due to the KO no later than Monday, June 11, 2021 at 4:00 p.m., Eastern Standard Time.

4.3 Proposal Validity: 60 days minimum from proposal submission deadline unless

Offeror provides another date.

4.4 Estimated Date of Award: June 20, 2021.

5.0 Evaluation Criteria: The award will be made on the basis of two factors: Price (Factor 1) and Technical (Factor 2).

5.1 Factor 1, Price: You shall complete and submit a Total Evaluated Price (TEP) worksheet. All numbers shall be rounded to two decimal places before being input into the TEP. Numbers rounded by MS Excel will not be accepted.

5.1.1 The TEP will be the price used in the Government’s evaluation of price reasonableness.

5.1.2 Integration is a cost-plus-fixed-fee CLIN and is included in the TEP.

Please note the fee shall not exceed 10% of your estimated cost (excluding the fee) (FAR 15.404-4(c)(4)(i)(C)). The offeror shall also complete a cost proposal support workbook. All numbers shall be rounded to two decimal places before being input into the workbook. Numbers rounded by MS Excel will not be accepted. Technical review of the proposal support workbook is detailed below under Factor 2, Technical.

5.1.3 If price reasonableness cannot be determined using price analysis of

Government-obtained information, additional information may be required of you to support the proposed price (FAR 15.403-3(a)(i)(2)).

5.2 Factor 2, Technical: A 20-page technical volume will be allowed for the technical volume submitted. The evaluation will determine if the offeror provides a sound, compliant approach that meets the requirements of the MEUAS IV IDIQ contract and this document. You shall demonstrate a thorough knowledge and understanding of those requirements. An evaluation rating of Technically Acceptable / Unacceptable will be assigned upon completion of the technical evaluation.

5.2.1 Past and Present Performance: Past and Present Performance will only include information on the MEUAS III & IV contract and its task orders. The performance rating definitions are as follows:

Performance Rating Definitions

Rating Description

Acceptable Based on the offeror’s performance record, the Government has a reasonable expectation that the offeror will successfully perform the required effort, or the offeror’s performance record is unknown. (See note below.)

Unacceptable Based on the offeror’s performance record, the Government has no reasonable expectation that the offeror will be able to successfully perform the required effort.

Note: In the case of an offeror without a record of relevant past performance or for whom information on past performance is not available or so sparse that no meaningful past performance rating can be reasonably assigned, the offeror may not be evaluated favorably or unfavorably on past performance (see FAR 15.305 (a)(2)(iv)).

Therefore, the offeror shall be determined to have unknown past performance. In the context of acceptability/unacceptability, “unknown” shall be considered “acceptable.”

5.2.2 Government Furnished Property (GFP) Payload Integration: If payloads have been successfully integrated on previous task orders, referencing the prior integration efforts is sufficient to determine technical acceptability. For all new payloads, demonstrate the ability to integrate the following payload(s) while maintaining PWS requirements. The Government will only provide support as stated in the attached Performance Data Sheet (PDS). Any other support (to include Government Furnished Property, Equipment, Information, or Manpower) proposed may result in a technically unacceptable proposal. To be considered technically acceptable, your proposal must include the following for each GFP payload: (i) a detailed integration plan to include tasks down to Work Breakdown Structure Level 3; (ii) power and weight budgets; (iii) component listings with source of supply; and (iv) images of CAD or fit testing showing consideration of preliminary integration. For integration details see the PDS. To be considered technically acceptable, your solution must demonstrate the ability to integrate and operate the following payload(s), while maintaining PWS requirements:

5.2.1.1 Dell 3C and STATAN 4 payload combinations

simultaneously.

5.2.1.2 DELL-3C and STATAN 4 and Gateway EW payloads

simultaneously.

5.2.1.3 DELL 8A and STATAN 24 and Gateway EW payloads

simultaneously.

5.2.1.4 DELL 8A and STATAN 4 and STATAN 24 and Gateway EW

payloads simultaneously.

5.2.2 MULTINT Endurance: In your proposal, demonstrate the ability to meet endurance requirements while maintaining PWS requirements. To be considered technically acceptable, all solutions must meet these uninterrupted on-station endurance requirements, while maintaining PWS requirements. For details see the

PDS.

5.2.2.1 DELL 3C and STATAN 4 payload, the UAS shall achieve

uninterrupted on-station endurance of 6 hours for UAS in a Multiple Intelligence (MULTINT) payload configuration and recover with at least 30 minutes of reserve fuel.

5.2.2.2 DELL-3C and STATAN 4 and Gateway EW payloads, the

UAS shall achieve uninterrupted on-station endurance of 6 hours for UAS in a MULTINT payload configuration and recover with at least 30 minutes of reserve fuel.

5.2.2.3 DELL 8A and STATAN 24 and Gateway EW payloads, the

UAS shall achieve uninterrupted on-station endurance of 6 hours for UAS in a MULTINT payload configuration and recover with at least 30 minutes of reserve fuel.

5.2.2.4 DELL 8A and STATAN 4 and STATAN 24 and Gateway EW

payloads simultaneously, the UAS shall achieve uninterrupted on-station endurance of 6 hours for UAS in a MULTINT payload configuration and recover with at least 30 minutes of reserve fuel.

5.2.3 PDS: All PDS questions must be addressed in the technical volume of the proposal response. In your proposal clearly identify the PDS question number to which you are responding. To be considered technically acceptable the answers provided on the PDS must validate compliance in achieving and maintaining the technical requirements of the IDIQ contract and this document.

5.2.4 Key Personnel: Identify by name your proposed key personnel for this site, reference SOFARS 5652.237-9001 in MEUAS IV IDIQ contract. To be considered technically acceptable your proposal must include names for all key personnel and his/her experience level.

5.2.5 Pre-Deployment Plan: Provide a timeline of actions planned for

Pre-Deployment (or Pre-Deployment Existing Site). This timeline shall detail all actions required in Pre-Deployment to achieve Initial Operating Capability (IOC). A technically acceptable timeline will include complete explanations of the processes and the establishment of target dates for: (i) shipment of material to site; (ii) onboarding of employees; (iii) training of employees (including security clearance and LOA/CAC issuance); (iv) field personnel deployment; (v) site set-up; (vi) preparations for first operational flight hours; (vii) IOC; and (viii) Full Operational Capability (FOC). Ideally the IOC and FOC will be the same date; however, if two different dates are submitted, a valid explanation shall be included. Without a valid explanation, the offeror’s timeline will not be found technically acceptable. To be considered technically acceptable, the pre-deployment timeline must demonstrate the knowledge and capability to accomplish all of the above in the period of performance given for pre-deployment. The information in this paragraph does not count against the proposal page limit.

5.2.6 Technical Evaluation of Cost Support Workbook (CLIN 0004 Only):

The workbook data will be analyzed to determine whether the labor, materials, and other direct costs are sufficient to successfully execute the proposed technical solution.

5.3. Factor 3, Price: Each contract holder shall submit a Total Evaluated Price Worksheet and a pricing workbook (if proposing a cost reimbursable CLIN.)

(END)

APPENDIX B

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