Atch6_522121_SectionLInstructions.pdf

A-10 Teamcenter Professional Engineering Services

FA8202-16-R-1003

16 June 2016

ATTACHMENT 6

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

(SECTION L)

ADDENDUM to FAR 52.212-1: L - I - INFORMATION TO OFFERORS (ITO) AND

INSTRUCTIONS FOR PROPOSAL PREPARATION

1.0 Program Structure and Objectives

The purpose of this effort is for the contractor to provide technical support services to sustain, change and implement Teamcenter functionality into the A-10 SPO Teamcenter PLM environment to support all users and programs associated with the A-10 to use engineering data to support the A-10 aircraft. It includes all the management, labor, materials, and necessary Teamcenter Professional Services to satisfy the mission support requirements of the A-10 Product Lifecycle Management (PLM) environment.

The technical support services required for this effort include Teamcenter Professional Engineering

Services to support the A-10 SPO Engineering staff. Highly skilled, experienced Teamcenter engineering services are paramount to application administration. This effort requires working in a leading edge CAD environment with a mix of 2D and 3D data; some with drawings and some without.

All of the engineering data created exists in CAD models and a Teamcenter database. As a consequence of this approach, interface of this data to other sustainment systems and interfaces must be developed.

These interfaces and data include:

• Provisioning and spare part procurement using D220

• S/N control tracking using REMIS

• Change control of engineering data using JEDMICS

• Analysis and airworthiness data using WSMT

• Tooling/manufacturing support data using Teamcenter

• Systems engineering and engineering processes

• Maintenance and repair sustainment WSMT

• Technical order relationships to engineering data and change control using ETIMS/CITOMS

• Modifications of existing configuration and data access using WSMT

• Requirements management using DOORS and Teamcenter

• Conversion of WSMT data to Teamcenter

• Manage the conversion of data to AFMC A4 PLM Initiatives (PLMi) systems

• Development of A-10 personnel Teamcenter administration skills

1.1 Budget/Funding Information

For consideration in developing your proposal, the program/budget funding is as follows:

Base and all options total (including the six-month extension of services):

$3,759,965.00

2.0 General Instructions

(a) This section of the instructions provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with (IAW) these instructions.

The proposal must be complete, self-sufficient, and respond directly to the requirements of this solicitation. The proposal shall be compliant with and meet the entire RFP requirements. Offerors are advised that submissions that DO NOT conform to the instructions provided herein may result in an unacceptable proposal evaluation, and/or exclusion from further consideration.

(b) Include Sufficient Detail: The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal shall not simply rephrase or restate the Government's requirements, but 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, capabilities, and experience and will base its evaluation on the information presented in the offeror's proposal.

(c) Embellishments Not Desired: Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

(d) Proposal Acceptance and Validity Dates: 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 for a minimum of 90 days from the solicitation closing date.

(e) Disposition of Proposals: IAW FAR 4.8, the Government will retain one copy of all proposals.

Unless the offeror requests otherwise (in their proposal), the Government will destroy extra copies of the successful and unsuccessful proposals.

(f) Past Performance: For each contract identified, the offeror shall complete a Past Performance

Information Sheet (PPIS), Attachment 8, in response to this RFP. The PCO will make a determination of acceptable past and current performance (defined in Section M) IAW FAR part 15.101-2 and FAR part

15.305(a)(2).

2.1 General Information

2.1.1 Point of Contact: The Procuring Contracting Officer (PCO) and the Contract Specialist are the sole points of contact for this acquisition. Written requests for clarification may be sent by mail or email

(preferred) to the PCO, with a copy to the Contract Specialist. All questions and answers shall be submitted to the Government through the prime offeror no later than 18 July 2016, 10 AM MT. The

Government cannot guarantee that questions submitted after this date will be answered.

AFLCMC/WWAK

ATTN: Mr. Ian Sanders

Contract Specialist

6072 Fir Avenue Building 1233

Hill AFB UT, 84056-5820 ian.sanders@us.af.mil

(801) 777-6041

ATTN: Ms. Stephanie Rearick, Procurement Contracting Officer

6072 Fir Avenue Building 1233

Hill AFB UT, 84056-5820 stephanie.rearick@us.af.mil

(801) 777-4207

2.1.2 Debriefings: The PCO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon, they may request and receive a debriefing IAW FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or, at the offeror’s request, this debriefing may be delayed until after award. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. After award, the PCO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, successful/unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW 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 PCO in writing with supporting rationale as well as the remedies the offeror is asking the PCO to consider as related to the omission or error. Government responses will be published on the Federal Business Opportunities

(FedBizOpps) website for access by all offerors. 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 FedBizOpps website at http://www.fedbizopps.gov or through the “Bidder’s Library” if established by the A-10 Contracting Office. 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 Oral Presentations: Oral presentation shall not be permitted.

2.1.6 Communications: Exchanges of source selection information between Government and offerors will be controlled by the PCO. 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 other means as appropriate. See Attachment 17, Email Encryption Instructions.

mailto:ian.sanders@us.af.mil mailto:stephanie.rearick@us.af.mil http://www.fedbizopps.gov/

2.1.7 Amendments to the Solicitation: If this Request for Proposal (RFP) is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this RFP by the date and time specified in the amendment(s) by signing and returning the front page of each.

2.1.8 Alternate Proposals: Proposals that do not address requirements within the ITO or meet program objectives will be deemed alternate proposals. Alternate proposals will not be considered.

2.2 Organization/Number of 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 the table below. The technical proposal, performance confidence and price proposal volumes identified in the table shall be separately bound in a three-ring, loose-leaf binders; the remaining volumes can be in one binder with a distinct tab for each volume.

The contents of each proposal volume are described in this section and summarized in the table below.

Offerors shall include a Table of Contents in the proposal. In addition to the “Hard Copies” requested in

Table 2.2 below, please submit on CD-R for each volume of the offeror’s proposal (not on CD-RW).

Table 2.2 - Proposal Organization Table

Volume ITO

Paragraph

Number

Volume Title CDs/

DVDs

Hard

Copies

Page Limit

I 3.0 Executive Summary 2 2 5

II 4.0 Technical Volume 2 2 45

*Includes 5 page max per Sample

Task

III 5.0 Performance Confidence 2 2 15

IV 6.0 Cost/Price Proposal 2 2 Unlimited

V 7.0 Contract Documentation 2 2 Unlimited

2.2.1 Page Limitations: Page limitations are identified in Table 2.2 – Proposal Organization, and explained below. Offerors are advised that the limitations shall be treated as maximums. If exceeded, the excess pages will not be evaluated or considered for award purposes; rather, they will be returned to the offeror, or destroyed as soon as practical. Additionally, information provided outside of the appropriate volume will not be evaluated. For example; additional technical information found within Volume V would not be evaluated. Page limitations may be placed on responses to Evaluation Notices (ENs) if applicable. The specified page limits for EN responses will be identified in the letters forwarding the

ENs to the offerors if discussions are entered into. Each page shall be counted except cover/title pages, tables of contents, tabbed dividers, acronym lists, and glossaries.

2.2.2.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 by 11 inches, not including foldouts. Pages shall be typed using single spacing, except for the reproduced sections of the solicitation document and contractor deliverable plans, for which the CDRL Data Item Descriptions state shall be prepared in contractor formatting. The text shall be Times New Roman and no less than

12-point font. Use at least 1 inch margins on the top and bottom, and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to

ENs. These limitations shall apply to both electronic and hard copy proposals.

(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 8-point. These limitations shall apply to both electronic and hard copy proposals.

(c) All portions in the electronic version of the proposal shall be searchable for text in the host program.

This includes narratives as well as all tables, foldouts, graphics, and figures

2.2.2 Cost or Pricing Related Data: All cost or pricing data shall be addressed only in the Cost/Price and Contract Documentation Volumes. Cost trade-off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions.

2.2.3 Classified Information: Classified information shall not be submitted in the proposal.

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

2.2.5 Indexing: 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.

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

2.2.7 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. Since classified information shall not be provided in the proposal, all 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 IAW 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. Each page that contains proprietary information shall be marked inside the header and footer of each page with the following statement “SOURCE SELECTION

INFORMATION (FAR 3.104) FOR OFFICIAL USE ONLY.”

2.3 Electronic Offers: The content and page size of electronic copies must be identical to the hard copies. In the event there is a discrepancy between the hard copy and the electronic copy, the hard copy will take precedence and will be used for evaluation. The offeror shall submit Volumes I through V in electronic format, using virus-free CD-R or DVD-R. In no cases shall the offeror use CD-RW or DVD-

RW. Each disk shall be properly labeled. For electronic copies, indicate on each CD/DVD the volume number and title. Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. When naming files, use titles to describe the content of the file rather than using numbers alone to more easily navigate and identify specific data. Each volume shall be in a different directory on a separate CD/DVD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable and searchable by Adobe XI, Microsoft (MS) Office Word 2007-2013, MS Office Excel

2007-2013, MS Office Project 2007-2013, and MS Office Power Point 2007-2013, as applicable.

Ensure all graphics (to include tables, charts, and foldouts) in the electronic version of the proposal are pasted into the proposal (do not paste as picture only).

2.4 Proposal Delivery: The original proposal shall be identified “Original” and signed by the offeror’s authorized representative, and the copies should be identified appropriately. All requested copies must be received by the due date identified on the front page of the RFP. Proposals shall be addressed to the

PCO and mailed or hand carried to:

Attn: Ms. Stephanie Rearick, PCO c/o Mr. Ian Sanders, Contract Specialist

6072 Fir Avenue, Building 1233

Hill AFB, UT 84056-5820 stephanie.rearick@us.af.mil

Include Solicitation Number FA8202-16-R-1003 on the address label.

Hand carried delivery of proposals shall be coordinated at least 48 hours in advance of the due date/time with the PCO. Proposal delivery cannot occur after 1400 MT. Electronic and paper copies of proposals must be received IAW the hour and date specified in the solicitation. Proposals received after the due date and time (1400 MT) specified herein shall be treated IAW FAR 15.208, Submission, Modification, Revision, and Withdrawal of Proposals.

3.0 Volume I - Executive Summary

The Executive Summary Volume is not evaluated, scored, or used to clarify other discrepant information in other volumes. Do not include cost information in 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 cost/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.

3.2 Table of Contents: Provide a master table of contents for the entire proposal, by SECTION L and

Government PWS paragraph number and the corresponding paragraph that addresses the referenced item. The table of contents will not count against the page limitation for this volume.

3.3 Other Information Required

3.3.1 Authorized Offeror Personnel: Provide the name, title, telephone number, and email address of the company/division point of contact regarding decisions made with respect to the offeror’s proposal and who can obligate (as to this proposal) the offeror’s company/firm contractually. Also identify those individuals authorized to negotiate with the Government.

3.3.2 Government Offices: Provide the mailing address, telephone number, email address, and facility code for the cognizant Contract Administration Office, Defense Contract Audit Agency (DCAA), and

Government Paying Office for the offeror’s company/firm. Also provide this information for the

Administrative Contracting Officer (ACO).

3.3.3 Company/Division Address, Identifying Codes, and Applicable Designations; and verifications:

• Offeror shall provide company/division's street address, county and facility code; CAGE code;

DUNS code; and labor surplus area designation. This same information must be provided if the work (for completing what is proposed) 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.

• Offeror shall provide verification that unlimited/unrestricted rights IAW DFARS 252.227-7013 or 252.227-7015 apply for all required technical data deliveries, since such deliveries are either

(1) necessary for operation, maintenance, installation, or training (other than detailed manufacturing or process data) and/or (2) funded completely by the Government under this contract.

3.4 Volume Organization: The Executive Summary shall be organized according to the following general outline:

1. Table of Contents

2. Authorized Offeror Personnel POCs

3. Government Offices POCs

4. Company Address, Cage Codes and Applicable Designations

5. Partnership/Joint Venture Agreement(s)

4.0 Volume II – Factor 1: Technical Volume

4.1 General: The technical proposal shall be clear, concise, and complete and include sufficient detail for effective evaluation. Legibility, clarity, and coherence are very important. The proposal shall not simply rephrase or restated the Government’s requirements, but rather shall provide convincing documentation to address how the offeror will meet these requirements. There will be no reference to rates or price in this volume. Offerors shall assume that the Government has no prior facilities, capabilities, and experience. The Government will base its evaluation on the information presented in the offeror’s proposal. Using the instructions provided below, provide as specifically as possible the actual methodology the offeror would use for accomplishing/satisfying these sub-factors. All the requirements specified in the solicitation are mandatory. By the offeror’s proposal submission, the offeror is representing that the company/firm will perform ALL the requirements specified in the solicitation (including the PWS); it is not necessary or desirable to tell us so in the proposal. Do not merely reiterate the objectives or reformulate the requirements specified in this RFP.

Responses will be evaluated against the Technical sub-factors defined in Section M, Evaluation Factors for Award.

4.1.1 Adequate Responses: Cursory responses or content which merely reiterates or reformulates section L, section M, or the PWS will not be considered as being responsive to the requirements of the solicitation. Evidence, which clearly demonstrates and supports the offeror’s claims is essential. The absence of such evidence may result in a technically unacceptable proposal.

4.2 Volume Organization: The proposal shall be organized according to the following general outline

Section Title

1 Table of Contents

2 List of Tables and Drawings

3 Glossary

4 Sample Task Responses (Sub-Factor A, B, & C)

5 Task Requirements (Sub-Factor D)

6 Management Approach (Sub-Factor E)

4.2.2 Technical Content: Using the instructions provided below, provide as specifically as possible the actual approaches (processes/methodologies) and capabilities proposed for use in accomplishing/ meeting or exceeding the minimum performance or capability requirements of each technical subfactor, as well as the risks in the proposed capabilities in terms of technical performance, cost, and schedule.

4.2.2.1 Technical Risk: Address Technical Risk associated with the aspects of the 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 IAW DoD Source Selection Procedures Table 2B, Technical Risk

Ratings. 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, whether or not those requirements are identified as subfactors. Propose realistic risk mitigation for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such risk mitigation. The Government will not be bound by the offeror’s proposed risks, risk ratings, or risk mitigations; the Government will make the final determination of the technical risk rating assigned in the evaluation.

4.3 Technical Volume Subfactors – Content

4.3.1 Subfactor A: Sample Task #1 – Data Architecture and Interface Plan, See Attachment 13

The proposal and response to this task shall clearly demonstrate that the offeror has sufficient familiarity, experience, technical expertise and competence to accurately, correctly, effectively and efficiently understand, interpret, correct, complete, and update existing and new Teamcenter data architectures and system-to-system interfaces.

4.3.2 Subfactor B: Sample Task #2 – Data Import and Validation Plan, See Attachment 14

The proposal and response to this sample task shall clearly demonstrate that the offeror has sufficient familiarity, experience, technical expertise and competence to accurately, correctly, effectively and efficiently maintain the A-10 Data Exchange Specification (ADES) with additional data mapping, importing, and validation requirements.

4.3.3 Subfactor C: Sample Task #3 – Serial Number and Unit Configuration Tracking Plan, See

Attachment 15

The proposal and response to this sample task shall clearly demonstrate that the offeror has sufficient familiarity, experience, technical expertise and competence to accurately, correctly, effectively and efficiently research and implement new capability in Teamcenter to define, build, and maintain serial number tracking of aircraft configurations.

4.3.4 Subfactor D: Task Requirements

The offeror shall provide a technical solution. The proposal shall describe in detail the offeror’s technical approach for meeting the PWS sections identified in the following paragraph(s). For those requirements, the proposal shall mirror the outline of the PWS. If the technical approach uses subcontractor(s), identify how the prime contractor will be responsible for performing the primary and vital requirements.

Specifically, the offeror shall provide detailed strategies of how they will accomplish and satisfy these key requirements IAW the PWS:

4.3.4.1 The technical solution shall address each subparagraph of PWS paragraph 3.1 as listed below:

(a) Describe how you will develop, manage, and maintain the functionalities in Teamcenter IAW each

PWS para 3.1.a; 3.1.b; 3.1.g; 3.1.h; 3.1.i; 3.1.j; 3.1.l; 3.1.m; 3.1.n.

(b) Describe how you will provide the necessary Teamcenter administrative support and interface to a data center within a DoD/AFNET type of environment IAW each PWS para 3.1.d; 3.1.e.

(c) Describe how you will provide the necessary Teamcenter administrative support to address client issues with Teamcenter and related interfacing software products on A-10/USAF client computers on the AF/AFNET network IAW PWS para 3.1.f.

(d) Describe how you will provide the necessary Teamcenter consulting and implementation support to ensure present business practice operating instructions are valid and congruent AF, A-10 and industry standard policies as implemented within a Teamcenter environment IAW each PWS para 3.1.c and

3.1.k.

(e) Describe how you will provide the necessary Teamcenter operational support to the A-10 SPO IAW

PWS para 3.1.o; 3.1.p; 3.1.q.

4.3.4.2 The task requirements solutions shall address technical risk IAW 4.2.2.1 of this document.

4.3.2 Subfactor E: Management Approach

The proposal shall describe the offeror’s program management approach toward accomplishing the requirements of the PWS. The offeror shall describe their approach that outlines all processes and programs by which the offeror will use to effectively execute the requirements of the PWS. The proposal shall include an organizational chart of all key contractor employees, consultants and subcontractors that contains the appropriate level of expertise and skill mix for the successful performance of this requirement. The offeror shall outline how they will provide personnel with the necessary skill sets to successfully execute the tasks of this requirement. The proposal shall also describe their approach that outlines all task performance, schedule, travel requirements, and reports.

4.3.2.1 The offeror shall describe how they will fulfill each of the skill sets requirements outlined IAW

PWS Paragraphs 3.2.a-o and 6.4.

4.3.2.2 The offeror will describe how they will maintain and augment the skill sets necessary to meet the contract requirements IAW PWS Paragraph 3.2.1 and 6.4.

4.3.2.3 The technical skills proposal shall address technical risk IAW 4.2.2.1 of this document.

4.3.2.3 The offeror shall describe their method for planning & scheduling the back-fill of required hours due to contractor time off for TDY and personal issues IAW PWS 3.3 and 6.4.

4.3.2.4 The offeror shall describe how they will determine and track the monthly administration training requirements IAW PWS Paragraph 3.1.t.

4.3.2.5 The offer shall explain, in detail, how they intend to meet the transition period IAW PWS 3.6.

4.3.2.6 The technical skills proposal shall address technical risk IAW 4.2.2.1 of this document.

4.3.2.7 The offeror shall describe how required travel plans and costs will be tracked IAW PWS 7 and

6.4.

5.0 Volume III – Factor 2: Performance Confidence

5.1 General: Each offeror shall submit a Performance Confidence Volume containing past performance information IAW the formats described below. Each offeror’s responses will be evaluated as defined in paragraph 5.0 of Section M, Evaluation Factors for Award. 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.

5.1.1 Past Performance Information Sheet (PPI): The offeror shall submit PPI sheets using

Attachment 8, Past Performance Information Sheet, for up to three (3) recent and relevant contracts for the prime offeror and up to three (3) recent and relevant contracts for each subcontractor, teaming partner, and/or joint venture partner considered most relevant in demonstrating an ability to perform the proposed effort. This information is required for the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 20 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance. For a description of the characteristics or aspects the Government will consider in determining whether the submitted Past Performance is recent and relevant, see Section M, paragraph

5.0, Factor 2: Performance Confidence.

5.1.1.1 PPI Content: Offerors are required to explain what aspects of the past performance 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. For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required.

5.1.2 Consent and Client Authorization Letters

The offeror shall submit Attachment 10, Subcontractor/Teaming Partner Consent Letter, signed and executed by the subcontractors, teaming partners, and/or joint venture partners, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall submit Attachment 11, Commercial

Client Authorization Letter, authorizing release to the Government of requested information on the offeror's, subcontractor’s, teaming partner’s, and/or joint venture partner’s performance.

5.1.3 Past Performance Questionnaires

Offerors shall complete Section 1 of Attachment 09, Past Performance Questionnaire and e-mail it along with Attachment 12, Past Performance Questionnaire Cover Letter to all POCs the offeror has listed in the PPI Sheets (see paragraph 5.1.1 above). The POCs will complete the questionnaires and forward them by e-mail directly to Ms. Stephanie Rearick at stephanie.rearick@us.af.mil. Respondents to the questionnaires shall not send the completed information sheets back to the offeror. Offerors shall not follow-up with respondents to ensure they have completed the questionnaires. The Past Performance

Evaluation Team will conduct such follow-up with any POC as necessary.

5.2 Performance Confidence Volume Submission: It is requested that the offeror submit its

Performance Confidence Volume ten (10) calendar days prior to the date set forth in block 9 of the

SF1449; however, offerors shall not submit it later than the proposal deadline.

5.3 Relevant Contracts: Relevance does not mean same or identical. Relevant means significantly similar to this acquisition to provide indicators of performance. Consider such things as product or service similarity, complexity, contract type, contract dollar value/size, program phase, division of company, major or critical subcontractors, teaming partners and joint ventures. Submit information IAW

Attachment 5, PPI. The offeror shall submit past performance information for work efforts identified in para 5.1.2; maximum of five (3) recent work efforts that are most relevant in demonstrating the offeror’s ability to perform the proposed effort. The offeror shall also include information for a maximum of three

(3) recent work efforts performed by each of the teaming partners and significant subcontractors that are considered most relevant in demonstrating their ability to perform the proposed effort. Offeror shall include rationale support its assertion of relevance.

5.4 Organizational Structure Change History: If your company has been acquired or

Acquired/Merged with another company, provide a roadmap explaining transitions as it relates to past performance for your company.

5.5 Contractor Relationships: If any of the offerors’ subcontractor identified on the PPIS are also potential offerors for this solicitation, the offeror may provide the POCs for the next higher level customer.

Provide information regarding predecessor companies, key personnel who have relevant experience of subcontractors that will perform major or critical aspects of the requirement when such information is relevant to the acquisition and will be considered in the evaluation. If a teaming arrangement is contemplated, provide complete information as to the arrangement, including any relevant and recent past performance information on previous teaming arrangement with same partner. As with all past work efforts identified in the proposal, use the PPIS (Attachment 1).

5.6 Clarifying Submitted Past Performance: The Government may contact the points of contact provided by the offeror for the purpose of ascertaining and/or clarifying past performance information.

5.7 Other Performance Confidence Considerations: It is not presumed that the offeror’s past performance has been perfect. Rather, the proposal should contain evidence of the offeror’s ability to correct past problems if applicable. Problems not addressed by the offeror, but found by the Government during the evaluation of the information in this volume, will be assumed to still exist. Note: In the case of CPARS, if the offeror’s input has already been provided and the rationale/circumstances have not changed, DO NOT repeat them here. The Government may use data provided by each offeror in this volume and may use data obtained from other sources in the development of the confidence assessment.

5.8 Volume Organization: The Performance Confidence volume shall be organized according to the following general outline:

2 Glossary

3 Past Performance Information Sheets (PPISs)

4 Consent Letters

6.0 Volume IV – Factor 3: Cost/Price

6.1 General Instructions

6.1.1 Cost/Price Reasonableness: The purpose of this volume is to provide the Government contracting office and cost team evaluators with an understanding of how the price proposal was developed. Your responses will be evaluated as defined in paragraph 6.0, Section M, Evaluation Factors for Award. Note that proposals which do not meet required tests of reasonableness, initially or subsequently, may be eliminated from competition either on the basis that the offeror does not understand the requirement or has submitted an inadequate proposal. Additionally, 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 costs/prices rests with the offeror.

6.1.1.1 Total Evaluated Price (TEP):

(a) Insert proposed unit and extended prices in the pricing attachment of the RFP for each Contract

Line Item Number (CLIN) and all option CLINs, including the six-month extension of services.

The extended amount must equal the whole dollar unit price multiplied by the provided quantity unit of issue.

(b) The total TEP will be the price factor in determining which offeror’s proposal represents the best value to the Government. Consequently, the offeror submitting the “best value” proposal will be the successful contract awardee. The TEP is for award determination purposes only and will be a consideration in the best value award decision.

6.1.1.2 Cost Summary by Cost Elements: Provide a cost summary by major cost elements by CLIN.

Major cost elements may include: Prime Hours, Subcontractor hours, Direct Labor, Overhead, Material, Subcontracts, Other Direct Costs, G&A, Facility Capital Cost of Money, Profit/Fee.

6.1.2 Estimating Techniques and Methods: When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique.

6.1.3 Cost/Price Data: Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/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 Cost/Price volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

6.1.4 Cost or Pricing Data Requirements: IAW 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 IAW FAR 15.403-5. If, after receipt of proposals, the PCO 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. If only one offer is received, the Government will follow procedures found in DFARS 215.371-3.

The PCO has made a preliminary determination of “Adequate Price Competition” IAW FAR 15.403-1

(c)(1). Therefore, a Certificate of Current Cost or Pricing Data per FAR 15.403-4 will not be required. In the event that adequate competition does not emerge in response to the solicitation, the PCO may require submission of certified cost and pricing data, and a Certificate of Current Cost or Pricing Data (IAW

FAR 15.403-4).

6.1.5 Rounding: All dollar amounts provided shall be rounded to the nearest dollar.

6.2 Volume Organization: The Cost/Price volume shall consist of the following sections:

2 Glossary

Pricing information and supporting data, to include cost summary by cost elements, estimating methodology and additional cost justifications/support. The offeror shall complete the pricing attachment by inserting proposed prices for each CLIN.

4 Data other than certified cost or pricing data, to include estimating methodology. List any exception to ground rules and assumptions provided in the solicitation and each qualification of the Cost/Price volume, if any. Provide complete rationale for any exceptions. Provide other information such as Government Furnished Property/Government Furnished

Equipment (GFP/GFE), base support, etc.

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: Complete Blocks 13-27 of the Standard Form (SF)

1449. Signature by the offeror on the SF1449 constitutes an offer, which the Government may accept.

In signing the SF1449, the offeror accedes to the contract terms and conditions as written in the RFP

Sections A through K. 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 Costs/Prices: Insert proposed unit an extended prices in the pricing attachment for each Contract Line Item Number (CLIN), including all option periods. The extended amount must equal the whole dollar unit price multiplied by the number of units.

7.1.3 Section G - Contract Administrative Data: Section G of the Model Contract will include all fund cites and dollar amounts for the contract. The offeror is not required to fill in this information.

7.1.4 Section I - Contract Clauses: The offeror shall complete necessary fill-ins in Section I and submit only pages that require a fill-in. The offeror shall comply with the clauses specified within Section I of the Model Contract. Furthermore, any inference of a clause and/or provision will be adhered to. All laws, regulations, and statutory authorities will also be applied within the model contract.

7.1.5 Section K - Representations, Certifications, and other Statements of Offerors: The offeror shall provide 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 below.

Table 7.2 - Solicitation Exceptions

Solicitation

Document

Page/

Paragraph

Requirement/

Portion Rationale

PWS, SPS, 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 Attachments to the Model Contract: The offeror shall provide the following, and when accepted by the Government, will be incorporated on contract as attachments or by reference upon contract award:

7.4 Technical Volume: The proposed Technical Volume, Volume II, when accepted by the

Government, will be incorporated into the contract upon award.