1._b.__Amendment_2_RFP_Attachment_2_52.212-1.docx

ATTACHMENT 2

52.212-1 - Instructions, Conditions, and Notices to Offerors

1.0 Program Structure and Objectives

The Integrated Risk Information System (IRIS) develops and integrates mishap precursor detection and mitigation tools into AF and DoD aerial operations. The purpose of this contract is to maintain and sustain the IRIS data processing and analysis capability for the acquisition, aggregation, analysis, and visualization of flight and aviation hazard data to meet current and emerging USAF aviation safety requirements. This includes: flight data analysis manpower; flight data analysis software and analysis results data repository; a web-based capability; methods required to support military-specific flight phases, maneuvers, and measurements; mathematical models and language constructs to characterize textual, numerical, spatial, and temporal data to facilitate aggregation and correlation of data; maintenance and sustainment of existing IRIS analysis capabilities; and the fielding of IRIS capabilities for additional AF aircraft fleets.

DoD and AF operations and safety guidance requires ongoing sustainment of IRIS flight data analysis and mishap prevention activities; therefore, the requirement for analysis software maintenance and sustainment, as well as flight data analysis will continue. At this point the AF has not indicated it can provide organic software development and sustainment resources for this unique software need, nor will the pilots with the aviation expertise needed to accomplish the analysis be freed from flight duty. This assessment indicates the contract requirement will continue indefinitely.

2.0 General Instructions

(a) The offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

(b) 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 and experience and will base its evaluation on the information presented in the offeror's proposal.

(c) Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary or desired and will not be accepted.

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

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

2.1 General Information

2.1.1. Point of Contact

The Contracting Officer (CO) and the Contract Specialist (CS) are the sole points of contact for this acquisition. Address any questions or concerns you may have to the CO and CS. Written requests for clarification may be sent to the following:

Contracting Officer: Mr. Brian J Clark, email brian.clark.6@us.af.mil, phone 505-846-5703 Contract Specialist: Ms. Amber Doan, email amber.doan@us.af.mil, phone 505-846-6284

2.1.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 for each proposal. 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.1.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. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

2.1.4. Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.1.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.

2.2 Organization/Electronic Copies/Page Limits

The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.2 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 2.2. The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table 2.2 - Proposal Organization

Number

2.2.1 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. 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 title pages, the table of content for each volume, and glossary of abbreviations and acronyms.

2.2.1.1. 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. Except for the reproduced sections of the solicitation document, 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.

(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. For tables, charts, graphs and figures, the text shall be no smaller than 12 pointclearly legible.

2.2.2 Pricing Related Data

All pricing data shall be addressed ONLY in the Price Proposal and Contract Documentation Volumes.

2.2.3 Cross-Referencing

To the greatest extent possible, each volume shall be written on a standalone 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.

2.2.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.

2.3 Electronic Labeling of Offers

Each volume must be identified by volume number and title. A cover sheet shall be included for each volume and clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. The offeror shall submit volumes I (insert volume number) through V in electronic format, using email. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2010, MS Office Excel 2010, MS Office Project 2010, and MS Office Power Point 2010, or Adobe Acrobat Pro XI as applicable. Be sure to apply all appropriate markings including those prescribed in accordance with FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

2.4 Distribution

All proposals shall be sent to the Contracting Officer at email address: brian.clark.6@us.af.mil.

The proposal shall be sent in an encrypted email and shall include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line as well as the RFP number.

3.0 Volume I Executive Summary

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

3.1 Narrative Summary

The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding price. The salient features should tie in with the 52.212-2 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.

3.2 Table of Contents

Include a master table of contents of the entire proposal.

3.3 All the solicitation documents obtained from the 10 March 2017 RFP will need to be destroyed. Offerors need to certify (in their Executive Summary) to the Air Force that they have destroyed these documents and will not contact UTRS employees on the IRIS team by using any employee information obtained through the 10 March posting.

*Note new documents were uploaded to RFP FA9401-17-R-0002 on 13 March 2017 and are to be used moving forward.

4.0 Volume II - Technical Volume

4.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 52.212-2, 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.

4.2 Format and Specific Content

4.2.1 Technical

In the technical volume, address your technical solution for meeting or exceeding the Government’s minimum performance or capability requirements of each technical subfactor.

4.2.1.1 Technical Risk

Address Technical Risk associated with those aspects of your proposed technical approach you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased Government oversight, or the likelihood of unsuccessful contract performance. Classify each risk in accordance with DoD Source Selection Procedures Table 3, Technical Risk Rating. Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements in the PWS and whether or not those requirements are identified as subfactors. Propose a realistic "workaround" or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation.

4.2.2 Volume Organization

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

Table of Contents

(1) List of Table

(2) Glossary

(3) Subfactor 1: Software

(4) Subfactor 2: Sustainment and Maintenance

(5) Subfactor 3: Compenation Plan for Professional Employees

(6) Subfactor 4: Extent of Participation of Small Business Concerns

4.2.3. Offerors shall address the following technical subfactors:

4.2.3(1) Subfactor 1: Software. The contractor shall provide a written description of how the proposed approach to flight data analysis, the proposed software tool set, and proposed analysts will continue current MFOQA analytical services by addressing the following elements: describe the capabilities of the proposed flight data analyses software tool set and how the capabilities meet the hazard identification and analysis requirements IAW PWS Paragraph 4.1.1.1; how flight data files from multiple recorder types and in various formats will be integrated in the analysis process as required in PWS Paragraph 4.1.1.4; and how the proposed software GUI facilitates the use and functionality of the query tools and the analyst’s ability to derive and communicate analysis results meeting the requirements of PWS Paragraph 4.2.6 and 4.1.1.3. **Note - Though the Air Force currently uses a Government-off-the-Shelf system the Air Force is open to offerors providing other systems that meet the parameters/capabilities of the current GOTS system in place. However, use of the GOTS is mandatory during the transition period and until testing is completed and ATO documents are prepared for the potential COTS solution, if proposed. Offerors providing COTS shall still be required to address the use of GOTS during the transition/testing period.

4.2.3(2) Subfactor 2: Sustainment and Maintenance. The contractor shall provide a written description of how the contractor will sustain and maintain the IRIS data analysis software and capabilities by describing the following: a process for expanding MFOQA analysis capability, including processing flight data files from multiple recorder types, the additional aircraft fleets identified in Appendix 5, and meeting PWS Paragraphs 4.1.1.5 and 4.2.3 requirements; a process for the development and deployment of upgrades to fix software discrepancies and improve analysis capabilities meeting PWS Paragraph 4.2.10.2; sustainment of web access to IRIS capabilities meeting PWS Paragraphs 2.2, 2.4, and 5.1.4; and activities required to maintain and renew the ISIS Authority to Operate, meeting PWS Paragraphs 2.4 and 4.2.5

4.2.3(3) Subfactor 3: Total Compensation Plan for Professional Employees. The total compensation plan required by FAR 52.222-46 shall be submitted as part of Volume II and shall be no more than twenty-five (25) pages which is counted in the 70 page limit outlined in Table 2.2. The plan shall set forth salaries and fringe benefits proposed for professional employees and include supporting information to enable the Government to review the proposed salaries and fringe benefits in accordance with FAR 52.222-46. Note: The compensation plan must address the compensation for professional employees of the offeror and all critical subcontractor(s). However, for an offeror or a critical subcontractor that is a populated joint venture (a joint venture in which the employees are employed by the joint venture itself and not by any individual joint venture partner), the joint venture must submit the total compensation plan for the joint venture. For each unpopulated joint venture, each individual joint venture partner must submit its own total compensation plan.

4.2.3(4) Subfactor 4: Extent to which offerors identify and commit to small business performance of the contract. Pursuant to the requirements of FAR 52.219-8, each offeror must provide, with its offer, targets, expressed as dollars and percentages of total contract value, the North American Industry Classification System (NAICS) code 541511 Custom Computer Programming Services, Industry Subsectors as determined by the Department of Commerce. NAICS code 541511 Custom Computer Programming Services is posted at: http://www.census.gov/eos/www/naics/. The targets may provide for participation by a prime contractor, joint venture partner, teaming arrangement member, or subcontractor; however, the targets for subcontractors must be listed separately. Targets are those to whom the offeror has committed work to should the offeror win the contract.

Each offeror, including small business concerns, shall submit a narrative that contains the following:

(1) Identification of one or more companies in at least one of the following categories to which the offeror has committed work to be performed under the IRIS contract if the offeror receives the award.

Small Business Concerns, Veteran-Owned Small Business Concerns, Service-Disabled Veteran-Owned Small Business Concerns, HUBZone Small Business Concerns, Small Disadvantaged Business Concerns, and/or Woman Owned Small Business Concerns

An identified company may be a joint venture partner and/or a subcontractor. A prime offeror that is a small business may identify in its Small Business Participation Plan work that the prime offeror itself is committed to perform.

(2) For each identified company, provide the full name of the company, a description of the applicable small business category, a description of the committed work, and a description of the extent of the commitment (e.g. dollar value, percentage, work type, etc.).

5.0 Volume III - Past Performance

5.1 General

Each offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 3. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are critical to the overall successful performance of the contract. Offerors are cautioned that the Government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

Along with the information required in this paragraph, the offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information (sample letter provided at attachment 4 of this RFP). For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the offeror's performance.

5.2 Relevant Contracts

Submit information in accordance with Attachment 3: Past Performance Information on five (5) recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort. Also include information on two (2) recent contracts performed by each of your teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. 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 52.212-2 - Evaluation Factors, paragraph c. - Past Performance Factor.

5.3 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 limited or 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 a higher confidence candidate. 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.1 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 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.

**Past Performance Information is strongly requested to be submitted no later than 10 days prior to the closing date of the solicitation in the interest of facilitating a thorough past performance evaluation, but in no event shall be submitted later than the date and time for receipt of proposals. Provide PPI for this volume in the format of attachment 3 PPI Request Form.

6.0 Volume IV - Price

6.1 General Instructions

6.1.1 Price Reasonableness and Realism

This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness of your proposed price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Reasonableness and unbalanced pricing applies to all CLINs. Unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed prices rests with the offeror.

6.1.2 Estimating Techniques and Methods

When responding to the Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating techniques to develop their estimates.

6.1.3 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.4 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.5 Rounding

All dollar amounts provided shall be rounded to the nearest dollar. All loaded labor rates shall be rounded to the nearest penny.

6.1.6 Option to Extend Services

This evaluation shall include all options plus the amount calculated for option(s) under 52.217-8 addressed below.

The government has included FAR clause 52.217-8, Option to Extend Services. Offerors are not required to provide additional pricing for these 6 months. For evaluation purposes only, the option under 52.217-8 will be evaluated by dividing the total proposed price for Option Year IV by two (2) to represent the six (6) months additional performance under the clause upon execution of 52.217-8 if needed.

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 the schedule.

7.1.1 Solicitation/Contract Form

Completion, signature, and date for blocks 30a, 30b, and 30c of the model contract. Signature by the offeror on the model contract constitutes an offer, which the Government may accept.

7.1.2 Services and Prices

Completed pricing information in the line item/pricing schedule of the model contract.

7.1.3 Representations, Certifications, and other Statements of Offerors

Completed representations, certifications, acknowledgments and statements.

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, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 7.2.

Table 7.2 - Solicitation Exceptions

Solicitation Document Page/ Paragraph Requirement/ Portion Rationale

Page and Paragraph Numbers

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.

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.

7.3.3 Subcontracting Plans.

IAW FAR 19.705-2, large business prime Offerors shall provide a clear, detailed and realistic plan that complies with FAR 52.219-9 and DFARS 252.219-7003 and satisfies all of the requirements of FAR 19.704, DFARS 219.704, and AFFARS 5319.704(a)(1) in order to be determined acceptable by the PCO prior to contract award. The Offeror’s submission must provide sufficient information to support the PCO's review of the subcontracting plan to determine acceptability. If small business subcontract possibilities do not exist or are limited, the Offeror’s plan must state such and provide rationale supporting the assertion. An approved Subcontracting Plan is required for any contract awarded to a large business Offeror.