Tech_Recovery_III_Section_L.pdf

PDF 281 KB Posted

Attached to
Guardian Angel Tech Recovery Federal contract opportunity
Solicitation number
FA8629-17-R-5003
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Wright Patterson Air Force Base

About this file

Section L Instructions, Conditions, and Notices to Offerors or Respondents

View the file

Other files for this federal contract opportunity

Other files attached to Guardian Angel Tech Recovery, newest first.
File Type Posted
Summary_of_Changes_Amend_0003_-_3_Oct_17.pdf PDF
Tech_Recovery_III_Section_L_LPTA_-_Revision_2.pdf PDF
Responses_to_Industry_Questions_-_3_Oct_17.pdf PDF
FA8629-17-R-5300_0003.pdf PDF
Summary_of_Changes_Under_Amendment_-_FA8629-17-R-5003_0002_-_26_Sep_17.pdf PDF
Responses_to_Industry_Questions_26_Sep_17.pdf PDF
L-5_Tech_Recovery_III_SRD_-_26_Sep_17.pdf PDF
L-4_Technical_Recovery_III_Pricing_Matrix_Protected_26_Sep_17.xlsx XLSX spreadsheet
FA8629-17-R-5003_0002.pdf PDF
Summary_of_Changes_-_FA8629-17-R-5003;_Amend_0001_-_18_Sep_17.pdf PDF
Responses_to_Industry_Questions_-_18_Sep_2017.pdf PDF
L-4_Technical_Recovery_III_Pricing_Matrix_Protected_18_Sep_17.xlsx XLSX spreadsheet
Tech_Recovery_III_Section_L_LPTA_-_18_Sep_17.pdf PDF
L-2_Past_Performance_Questionnaire_-_18_Sep_17.pdf PDF
FA8629-17-R-5003_0001.pdf PDF
Tech_Recovery_III_Section_M_LPTA_-_18_Sep_17.pdf PDF
L-5_Tech_Recovery_III_SRD_-11_Sep_17_Signed.pdf PDF
Responses_to_Questions.pdf PDF
ppi_tool.accdb —
L-2_Past_Performance_QuestionnaireV2.pdf PDF
Questions.pdf PDF
Tech_Recovery_III_Section_L.pdf PDF
L-1_PPI_Tool_Instructions.pdf PDF
Model_Delivery_Order.pdf PDF
Cover_Letter.pdf PDF
L-5_Tech_Recovery_III_SRD.pdf PDF
L-4_Technical_Recovery_III_Pricing_Matrix_Protected_20170425.xlsx XLSX spreadsheet
L-6_Tech_Recovery_Proposal_Cross_Reference_Matrix_20170426.pdf PDF
Brand_Name_JA_.pdf PDF
L-2_Past_Performance_Questionnaire.pdf PDF
L-7_Technical_Recovery_Current_Kit_Count.pdf PDF
L-3_Pricing_Cross_Reference_Matrix.pdf PDF
Tech_Recovery_III_Section_M.pdf PDF
Model_Contract.pdf PDF
General_Notes_for_Technical_Recovery_III.pdf PDF
Show all 35

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

FA8629-17-R-5003

Section L

11 Aug 2017

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

1 PROGRAM INFORMATION

1.1 Program Structure and Objectives

The Guardian Angel (GA) Technical Recovery (TR) program objective is to provide specialized kits for extrication, confined space, and collapsed structure rescue while addressing the Personnel

Recovery (PR) equipment modernization and sustainment needs. This has been added to the program’s original plan of equipment standardization and weight reduction. The program shall be dedicated to continuing its mission of providing the most advanced technology, the best possible training through the use of the most realistic techniques based on operational scenarios, and a sustainment program to manage GA equipment assets in optimal condition.

1.2 USE OF NON-GOVERNMENT ADVISORS

(a) Offerors are advised that technical and cost/price data submitted to the government in response to this solicitation may be released to non-government advisors for review and analysis.

The non-government advisor support will be provided by:

Name(s) of firm(s)

Odyssey Systems

(b) Offerors shall complete paragraph (b)(2) or provide written objection to disclosure as indicated in paragraph (b)(1) if the offeror objects to disclosure of a portion of the proposal, the consent in (b)(2) should be provided for the remainder of the proposal.

(1) Any objection to disclosure:

(i) Shall be provided in writing to the contracting officer within 10 days of RFP issuance; and

(ii) Shall include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the offeror objects to disclosure to non-government advisors.

(2) I understand technical and cost/price data submitted to the government in response to this solicitation may be released to non-government advisors. I consent to release of any

(unless objection is provided in (b)(1) above) proprietary, confidential, or privileged commercial or financial data provided by the firm(s) named below in response to this solicitation, to non-government advisors for review and analysis:

11 Aug 2017

Firm:

Name (individual authorized to commit firm):

Title:

Date of Execution:

2 GENERAL INSTRUCTIONS

The offeror's proposal must include all data and information requested by this Instructions to Offerors

(ITO) and must be submitted in accordance with these instructions. The proposal shall be compliant with the requirements as stated in the Statement of Objectives (SOO), System Requirements Document (SRD), Contract Data Requirements List (CDRL), and Request for Proposal (RFP)/Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the

Government's requirements but, rather, shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities or experience and will base its evaluation on the information presented in the offeror's proposal.

Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

The proposal acceptance period is specified in Section A of the model contract/solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. The Government will destroy extra copies of such unsuccessful proposals.

2.1 Point of Contact

The Contracting Officer (CO), Lt Col John Wodochek, (937) 656-8271 (john.wodochek@us.af.mil) and the Contract Specialist, Mr. Branden Q. Jackson, (937) 656-8090, (branden.jackson.1@us.af.mil) are the sole points of contact for this acquisition. Address any questions or concerns you may have to the CO or

Specialist. Written requests for clarification may be sent to the CO at the address located in Section A of the model contract/solicitation. Any questions shall be submitted within (10) days of the RFP release date. Answers to any such questions/ clarifications will be provided on the Federal Business

Opportunities (FedBizOpps) website at https://www.fbo.gov/ and/or via RFP amendment. In the event of conflict between the answer to questions/clarifications and the RFP, the RFP shall take precedence.

http://farsite.hill.af.mil/vffara.htm

11 Aug 2017

2.2 Debriefings

The CO will promptly notify offerors of any decision to exclude them from the competitive range;

whereupon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing. The CO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

2.3 Discrepancies

If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the offeror is asking the CO to consider as related to the omission or error.

Electronic submittal of such notification is allowable.

2.4 Electronic Reference Documents

All referenced documents for this solicitation are available on FedBizOpps. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.5 Communications

Exchanges of source selection information between Government and offerors will be controlled by the

CO. Email may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the

Subject line. Otherwise, source selection information will be transmitted via the AMRDEC Safe file sharing website, <https://safe.amrdec.army.mil/safe/> or USPS, FedEx, UPS, or pick-up by local representative. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS

Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If you intend to submit source selection information via encrypted email, you will need to contact the Contracting Officer indicated on the face page of the solicitation prior to that first submittal in order to exchange Public PKI key credentials. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information).

http://farsite.hill.af.mil/vffara.htm

11 Aug 2017

3 PROPOSAL PREPARATION INSTRUCTIONS

3.1 Organization/Number of Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 below).

The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 1. The content identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table 1 - Proposal Organization

VOLUME

ITO

Paragraph

Number

VOLUME TITLE

COPIES

(Paper/

Electronic)

PAGE LIMIT

I 4.1 Executive Summary 3/2 5 Maximum

II 4.2 Technical Proposal 3/2

Subfactor 1:

50 Maximum

Subfactor 2:

30 Maximum

III 5 Past Performance Information 3/2

5 pages per Citation

5 Citations

Maximum

IV 6 Price Proposal 3/2 Unlimited

V 7 Model Contract Documentation 3/2 N/A

3.1.2 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal and excess paper copies will be returned to the offeror as soon as practicable. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors.

Each page shall be counted except the following: Cover Pages, table of contents, proposal cross reference matrix, System/Subsytem Specification (SSS), tabs, glossaries, transmittal letters, and resumes. If submitting an Indefinite Delivery/Indefinite Quantity (IDIQ) type contract as a Past

Performance reference, all Delivery Orders (DOs) will be considered as a single citation.

11 Aug 2017

3.1.3 Page Size and Format

(a) A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single spaced. Except for the reproduced sections of the solicitation document, the font shall be Times New Roman and the text size shall be no less than 12 - point.

Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1- inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs. These limitations shall apply to both electronic and hard copy proposals. For

Past Performance Information Tool printouts, use the default page size and format from the tool.

(b) Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics; not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than 10 - point. These limitations shall apply to both electronic and hard copy proposals.

3.2 Cross-Referencing

To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

The offeror shall fill out the Proposal Cross Reference Matrix at Attachment L-6 of this ITO indicating the proposal reference information as it relates to the ITO, SRD, SOO, CLIN numbers, and CDRL references found therein.

3.3 Indexing

11 Aug 2017

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections and will not be included in page limitations.

Index pages should be blank and not be used to convey any information.

3.4 Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

3.5 Binding and Labeling

Each volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. The same identifying data should be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 52.215-1(e), Restriction on disclosure and use of data, and FAR 3.104-4, Disclosure, Protection, and Marking of

Contractor Bid or Proposal Information and Source Selection Information.

All material shall include the following information located in the header and footer of each page:

SOURCE SELECTION INFORMATION FOR OFFICAL USE ONLY

See FAR 2.101 and FAR 3.104

3.6 Electronic Offers

The content and page size of electronic copies must be identical to the hard copies. For electronic copies, indicate on each Compact Disc (CD)/Digital Video Disc (DVD) the volume number and title.

Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The offeror shall submit volumes I through V in electronic format, using recordable

CDs/DVDs. Each volume shall be contained on a separate CD/DVD. If files are compressed, the necessary decompression program must be included. In the event that hard copies and electronic copies of a proposal are submitted and if there are any discrepancies between the hard copies and the electronic copies of the proposal, the hard copies will be used for evaluation. The electronic copies of the proposal shall be submitted IAW the following:

a. Electronic storage media shall be submitted in one of the following formats:

CD or DVD.

b. Submitting documents using MS Office 2010 or greater:

Word documents – Set "Save as type" to "Word Document (*.docx)"

Excel spreadsheets – Set "Save as type" to "Excel Workbook (*.xlsx)."

PowerPoint presentations – Set "Save as type" to "PowerPoint Presentation (*.pptx)."

c. Submitting documents using MS Office 2007:

11 Aug 2017

Word documents – Set "Save as type" to "Word Document (*.docx)"

Excel spreadsheets – Set "Save as type" to "Excel Workbook (*.xlsx)."

PowerPoint presentations – Set "Save as type" to "PowerPoint Presentation (*.pptx)."

d. Submitting documents using MS Office 2003:

Word documents – Install the Office Compatibility Pack from www.microsoft.com and

Save As "Word Document (*.docx) "

Excel spreadsheets – Install the Office Compatibility Pack from www.microsoft.com and

Save As "Microsoft Excel Workbook (*.xlsx) "

PowerPoint presentations – Install the Office Compatibility Pack from www.microsoft.com and Save As "Microsoft PowerPoint 2007 Presentation (*.pptx) "

e. Submit any MS Project files in MS Project 2007 or greater. There are no special “save” functions required for later versions of Project.

f. Submit PDF documents using only Adobe Acrobat X (10.0) or later. Do NOT submit any documents in PDF format that are copied as "images." When creating PDF files always create to enable textual search and copy functions.

g. Do NOT submit documents using file compression software (such as .zip format).

h. Past Performance Information: Offeror’s must use the past performance information tool for their electronic proposal submittal of relevant past performance contract information. This tool can be downloaded from the FBO site (https://www.fbo.gov/) as an attachment to the solicitation posting. Hard copies of the pages generated from this tool shall be used in the hard copy of the past performance volume subject to the limitations outlined in this RFP and should be Tab 1 of the past performance volume. If you are unable to download the past performance information tool, contact the CO for assistance. Save the PPI database file as prime contractor name + RFP number + .mdb (e.g., XYZCompanyFA862114R6318.mdb).

Provide the information requested in a separate completed form for each contract/program being submitted. Provide concise comments regarding your performance on the contracts you identify. Limit the number of past efforts submitted and the length of each submission to the limitations set forth in Section L 3.1.

3.7 Distribution

The "original" proposal shall be identified. The offeror’s proposal shall be prepared and submitted in five volumes: Executive Summary (Volume I), Technical Proposal (Volume II), Past Performance

Information (Volume III), Price Proposal (Volume IV), and Model Contract Documentation (Volume V).

All volumes must be received via two different media, electronic (CD or DVD) and paper. Proposals shall be addressed to the CO and mailed or hand carried to:

AFLCMC/WISK

ATTN: Lt Col John Wodochek (Tech Recovery Program)

1895 5th Street

Building 46, Room 210 http://www.microsoft.com/ http://www.microsoft.com/ http://www.microsoft.com/ https://www.fbo.gov/

11 Aug 2017

Wright-Patterson AFB OH 45433

Each volume will be labeled with a cover page containing (at a minimum) the program reference, solicitation number, volume title, and submission date. Be sure to advise the Administrative Contracting

Officer (ACO) and the Defense Contract Audit Agency (DCAA) for prime and subcontractors that the proposal is "For Official Use Only" and "Source Selection Information--See FAR 2.101 and FAR

3.104".

4 PROPOSAL ORGANIZATION

4.1 Volume I - Executive Summary

In the executive summary volume, the offeror shall provide the following information:

4.1.1 Narrative Summary

The narrative summary of the entire proposal should be concise and highlight any key or unique features, excluding price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

4.1.2 Proposal Cross Reference Matrix

Include a Proposal Cross Reference Matrix that provides traceability from RFP requirements to proposal volumes. Use Section L, Attachment L-6 to format the Cross Reference Matrix.

4.2 Volume II - Technical Volume

4.2.1 General

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation (except for the specific name brand required part numbers).

4.2.2 Format and Specific Content

Technical Capability shall be addressed in the Technical Proposal Volume. In this volume, address your proposed approach to meeting the requirements of each Technical subfactor.

http://farsite.hill.af.mil/vffara.htm

11 Aug 2017

4.2.3 Technical

In the technical volume, address your technical solution for meeting the Government’s minimum performance or capability requirements of each technical subfactor. (Section M 2.2)

4.2.4 Volume Organization

The Technical Proposal Volume shall be organized according to the following general outline:

(1) Table of Contents

(2) List of Table and Drawings

(3) Glossary

(4) Subfactor One: Training

(5) Subfactor Two: SRD Compliance

(6) SSS

4.2.5 Factor 1- Technical

4.2.5.1 Subfactor One: Training

Description: This Subfactor will evaluate the offeror’s proposed approach to provide training in accordance with SOO paragraph 9. The offeror shall provide:

A. A staffing plan including:

a. Sufficient minimum qualifications and experience for instructors IAW SOO 9.E.

b. Appropriate instructor to student ratios;

c. Maximum class size;

d. Plan to provide sufficient quantities of qualified instructors to conduct training courses

IAW SOO 9.A through 9.D.

B. A teaching syllabus and training plan for the Structural Collapse Kit portion of the Operator

Training course. (SOO 9.A / CLIN 0008) Assume 15 students.

C. A training facility plan (SOO 9.A through 9.D) including:

a. Processes for determining minimum facility requirements;

b. Process for identifying capable facilities at each training location;

c. Logical timeline for establishing facility use;

d. Post-course evaluation of facility adequacy

D. Develop a training scenario IAW SOO paragraph 9.F based on the given scenario and all of the following assumptions:

a. Scenario: After a Vehicle Borne Improvised Explosive Device blast at the U.S. Embassy in Kabul, Afghanistan, your team is alerted to respond. The scene has been cleared and is secured of any additional threats by American forces. The first story has pancaked down to the ground. The second floor appears to have open access on blast side and the

11 Aug 2017 basement is undefined. Three personnel are in the second floor, three are trapped in the first floor and two are in the basement.

i. Successfully recover eight personnel from a collapsed two-story building with a basement.

ii. Given a 15-person class utilize the Structural Collapse kit and other kits as required.

iii. Identify building approach and material construction considerations.

iv. Describe safe zones and means of communication.

v. Explain the consideration, construction, and placement of Shoring.

vi. Describe alternate considerations for identifying survivors.

vii. Covers all applicable tactics, techniques, and procedures taught in the Operator

Training course

viii. Details how student participation will be monitored and evaluated and given feedback.

4.2.5.2 Subfactor Two: SRD Compliance

Description: The offeror shall provide a SSS containing a complete components list of all technical recovery items organized into Confined Space, Structural Collapse, Heavy REDS, Light REDS, and

Mechanical Ascender Kits. (SRD Appendicies B, C, D, E, F, G, H, I, J)

A. For all items (Brand Name and Brand Name or Equal) listed in attachment L-5 SRD, the offeror shall provide brand and model number of proposed item. Additionally, for Brand Name or Equal items (SRD Appendicies C, E, F, G, I, J) that differ from the item listed, manufacturer’s specifications showing it meets the requirement for all items shall be included.

B. For items that are Brand Name or Equal (SRD Appendicies C, E, F, G, I, J), and differ from the items listed in the SRD, the offeror shall provide a narrative describing how a proposed item was selected. The narrative shall also demonstrate how the proposed item is in compliance with the

SRD performance requirements, specifications, and the Berry Ammendment (SOO paragraph

8A) as applicable.

5 Volume III - Past Performance

5.1 Past Performance Information (PPI) Tool

Each offeror shall submit a PPI Volume with its proposal, containing past performance information IAW the format contained in Attachment L-1.

5.2 Early Proposal Information

Offerors shall send Past Performance Questionnaire (PPQ) (Attachment L-2) directly to the points of contact for the past efforts identified. Offerors shall not fill out the PPQ prior to providing it to the points of contact mentioned above. All respondents shall be instructed that all responses are to be

11 Aug 2017 provided directly to the Government CO not later than dd mmm yyyy. Offerors shall provide a listing of the individuals to whom the questionnaires were sent, with contact information (name, phone, email, etc.). This is needed in case the Government has to follow-up with any POCs for questionnaires not received. This listing shall not be included in the volume page count.

Each offeror is requested to submit the information shown in Attachment L-2 for each relevant contract

15 calendar days prior to the date set for receipt of proposals. Failure to submit early proposal information will not result in offeror disqualification.

5.3 Recent and Relevant Contracts

Submit information IAW Attachment L-1: PPI on up to five recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort within the past 5 years from the date of issuance of this solicitation. Also include information on up to two of the five recent contracts performed by each of your teaming partners and significant subcontractors that you consider most relevant in deomonstrating their ability to perform the proposed effort. Each effort must have had at least six months of performance elapsed. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the Government will consider in determining recency and relevance, see Section M, paragraph 2.3.2.1 – Recency Assessment, paragraph 2.3.2.2 – Relevancy

Assessment.

5.3.1 Specific Content

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a no confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified. This may allow the offeror to be considered more favorably than without evidence of problem resolution. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required.

Categorize the relevant information into the specific Technical subfactors and Price factor used to evaluate the proposal.

5.3.2 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past

11 Aug 2017 performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the offeror(s), your

"roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the Government receives information from other sources.

6.0 Volume IV - Price

The pricing matrix, minus the TEP tab, will become an attachment to the contract at time of award.

6.1 General Instructions

This section is to assist you in submitting data other than certified cost and pricing data that is required to evaluate the reasonableness, completeness, and unbalanced pricing of your proposal. Compliance with these requirements is mandatory and failure to comply may result in rejection of the proposal.

Offers should be sufficiently detailed to demonstrate their reasonableness and balance. The burden of proof for credibility of proposed prices rests with the offeror.

6.1.1 Price Data

Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

6.1.2 Cost or Pricing Data Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit additional cost or pricing data.

6.1.3 Rounding

All dollar amounts provided shall be rounded to the nearest dollar.

6.2 Volume Organization

The Price volume shall consist of the following sections:

SECTION 1 - Table of Contents, Total Evaluated Price Matrix

SECTION 2 - Data other than certified cost or pricing data, to include estimating methodology.

http://farsite.hill.af.mil/vffara.htm

SECTION 3 - Other information such as inflation rate summary and explanation. List each exception to the ground rules and assumptions provided in the solicitation and each qualification of the Price volume, if any. Provide complete rationale for any exceptions.

6.3 Total Evaluated Price (TEP) Instructions

The Offeror shall complete the Guardian Angel Tech Recovery Price Matrix (RFP Section L –

Attachment L-4). Offerors will enter prices according to the following procedures.

a. CLIN 0001-Confined Space (CS) Kit - Enter the individual item price on the “Kit Pricing” tab of the Pricing Matrix.

b. CLIN 0002 - Structural Collapse (SC) Kit - Enter the individual item price on the “Kit Pricing” tab of the Pricing Matrix.

c. CLIN 0003 - Heavy Rapid Extrication Deployment System (REDS) Kit - Enter the individual item price on the “Kit Pricing” tab of the Pricing Matrix.

d. CLIN 0004 - Light Rapid Extrication Deployment System (REDS) Kit - Enter the individual item price on the “Kit Pricing” tab of the Pricing Matrix.

e. CLIN 0005 - Mechanical Ascender Kit - Enter the individual item price on the “Kit Pricing” tab of the Pricing Matrix.

f. CLIN 0006 – Replacement Parts – Enter the individual item prices on the “Required Brand Name

Items” and “Brand Name or Equal Items” tabs of the Pricing Matrix. If proposing “or Equal’ provide item description, manufacturer, and part number on the “Brand Name or Equal Items” tab of the Pricing Matrix

g. CLIN 0007 – Repair Parts – Enter the individual item prices on the “Repair Parts” tab of the

Pricing Matrix.

h. CLIN 0008 – Operator Training – Enter the per class price for CONUS traning in the “Training” tab of the Pricing Matrix.

i. CLIN 0009 – Operator Refresher Training – Enter the per class price for CONUS and OCONUS traning in the “Training” tab of the Pricing Matrix.

j. CLIN 0010 – Just-In-Time (JIT) Training – Enter the per class price for CONUS and OCONUS traning in the “Training” tab of the Pricing Matrix.

k. CLIN 0011 – Self-Contained Hybrid Integrated Evolution Life Support Device (SHIELD)

Training – Enter the per class price for CONUS and OCONUS training in the “Training” tab of the Pricing Matrix.

l. CLIN 0012 – Annual Maintenance Service Visit (AMSV) – Enter the per visit price for CONUS and OCONUS in the “AMSV” tab of the Pricing Matrix. The number of kits per unit is in attachment L-7.

m. CLIN 0013– System Engineering/Program Management – Enter the annual price for Program

Management in the “Project Management” tab of the Pricing Matrix.

Note: utilize Attachment L-3 Pricing Cross Reference Matrix as guidance for CLIN pricing

6.3.1 Proposal prices shall be based on the Government FY (October – September). Contract award is projected to be in FY18.

7.0 Volume V - Contract Documentation

7.1 Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The offeror's proposal shall include a signed copy of the Model Contract, and Sections A through K.

7.1.1 Section A - Solicitation/Contract Form

Completion of blocks 13 through 16, signature for block 17, and date for block 18 of the Standard

Form 33 (SF33), Solicitation Offer and Award. Completion of block 25 on the DD 1155 of the model

Delivery Order shall be consistent with prices proposed in the Pricing Matrix. Signature by the offeror on the SF33 and DD1155 constitutes an offer, which the Government may accept. The “original” copy should be clearly marked under separate cover and should be provided without any punched holes.

7.1.2 Section B - Supplies or Services and Prices

The offeror shall complete Section B of the Model Contract and Model Delivery Order. Please refer to

Section 6 above for instructions for completing the Pricing Matrix.

7.1.3 Section F - Deliveries or Performance

N/A

7.1.4 Section G - Contract Administrative Data

Upon award, Section G data will be provided by the Government.

7.1.5 Section H - Special Contract Requirements

N/A

7.1.6 Section I - Contract Clauses

The offeror shall complete all applicable fill-ins for Section I.

7.1.7 Section J - Attachments.

The offeror shall provide the following as attachments to the Model Contract (Section J):

Price Matrix (Attachment 1)*

Statement of Work (SOW) (Attachment 2)

Contract Data Requirements List (Attachment 3)

System Subsystem Specification (Attachment 4)*

Subcontracting Plan (Attachment 5)

*Note: The SSS and the Price Matrix shall only be placed in Volume II and IV, respectively, in accordance with paragraphs 4.2.4 and 6.2. The TEP will be modified in accordance with paragraph

11 Aug 2017

6.0 prior to incorporation into the contract. These two attachments will be incorporated into the contract at time of award.

a. Price Matrix. Price Matrices are provided in Attachment L-4. The matrices will provide a price summary for all CLINs.

b. Statement of Work (SOW). The SOO represents the Government's minimum objectives for the

Technical Recovery program. The offeror shall use the SOO to propose a SOW which expounds upon these minimum objectives to the extent necessary to conduct this acquisition. The proposed SOW shall define the tasks required for the Technical Recovery program ensuring all minimum requirements of the Government provided SOO have been addressed. The proposed

SOW shall consist of contractually binding tasking statements. Each tasking statement shall reference the CDRL items which will be delivered by that task if appropriate (data deliverables).

The proposed SOW, when accepted by the Government, will be put on contract at award.

c. Subcontracting Plan - Participation of Small Businesses (SB), Historically Black Colleges and

Universities, or Minority Institutions (HBCU/MI). Offerors shall submit a Small Business

Subcontracting Plan (SBSP) in accordance with FAR 52.219-9 that also identifies and specifies the extent of offeror's commitment to the participation of small businesses (SB), historically black colleges or universities (HBCU) and minority institutions (MI), whether as joint venture members, teaming arrangement partners, or subcontractors. If applicable, submit a copy of an approved Master Plan. In the event the offeror has negotiated a comprehensive subcontracting plan pursuant to DFARS 219.702, the offeror must submit the information that identifies and specifies the extent of its commitment to the participation of SB, HBCU and MI. Proposed subcontracting plans will be evaluated by the contracting officer prior to acceptance in accordance with FAR Part 19, as supplemented.

7.1.8 Section K - Representations, Certifications, and other Statements of Offerors

Completed representations, certifications, acknowledgments and statements must be provided by the offeror as detailed in the Model Contract.

7.2 Exceptions to Solicitation Requirements

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the format and content of

Table 7.2.

11 Aug 2017

Table 7.2 - Solicitation Exceptions

Solicitation

Document

Page/

Paragraph

Requirement/

Portion Rationale

SOO, SOW, SPEC,

Model Contract, ITO, etc.

Applicable

Page and

Paragraph

Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

7.3 Other Information Required

7.3.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government. As well as the name and title of the CEO, Division President, and/or Vice President.

7.3.2 Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

8.0 List of Attachments: Section L attachments listed below are provided as separate files.

L-1: Past Performance Information Tool Instructions

L-2: Past Performance Questionnaire

L-3: Pricing Cross Reference Matrix

L-4: Price Matrix

L-5: SRD

L-6: Proposal Cross Reference Matrix

L-7: Current Kit Count

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