Section L Amendment 2 - 14 Oct 11.docx

SECTION L INSTRUCTIONS TO OFFERORS

L1.0 INFORMATION TO OFFERORS (ITO) and INSTRUCTIONS FOR PROPOSAL PREPARATION

1.1 General Instructions

(a) This section provides general guidance, as well as specific instructions on format and content, for preparing proposals. The offeror’s proposal must include all information requested and must be submitted in accordance with these instructions. Compliance with these instructions is mandatory and failure to furnish a complete proposal, at the time of proposal submission, may result in the proposal being unacceptable to the Government and may eliminate the offeror from further consideration for award. It is the offeror’s responsibility to ensure the completeness of the proposal submitted. With respect to cost/price proposals, the burden of proof for credibility rests with each offeror. Evaluation of a proposal will be conducted solely on the basis of the information contained within it and the Government will not assume that an offeror possesses any capabilities not specified. Inconsistencies among the parts of each proposal shall be explained. Any unexplained inconsistency may raise a fundamental question of the offeror’s understanding of the requirement and/or ability to perform. Offerors are advised that their proposals are presumed to represent their best efforts and most complete responses to this solicitation. Proposals that simply reiterate the contents of this solicitation, or contain only superficial responses, may be considered unacceptable. Evidence of experience, capability, and qualifications that clearly demonstrate and support the offeror’s claims are essential. The absence of such evidence will adversely influence the evaluation of the offeror’s proposal. Once an offeror is selected for award of a task order, that offeror may be excluded for all other task order selections until all awardees have received at least one task order award and met the minimum guaranteed amount specified in FAR 52.216-19 Order Limitations. Initial task orders may be of similar size, scope, and value. No initial task orders will be sole sourced. OFFERORS SHALL NOT SUBMIT NAMES OF PROPOSED PERSONNEL IN ANY VOLUME OF THE PROPOSAL.

(b) The proposal shall be clear, concise, and 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 rather shall provide convincing rationale to address how the offeror intends to meet the requirements. The offeror shall assume that the Government has no prior knowledge of the Contractor’s capabilities or experience; and as such, the Government will base its evaluation on the information presented in its proposal. The offeror is reminded that the Government intends to award this effort based on the initial proposal, as received, without discussion.

(c) A proposal may include data, such as technical designs or concepts, financial data, or management plans that the offeror does not want disclosed to the public for any reason, or used by the Government for any purpose other than proposal evaluation and contract award. If the offeror wishes to restrict the proposal, the offeror shall mark it in accordance with FAR 52.215-1(e).

(d) In accordance with FAR Subpart 4.8, Government Contract Files, the Government will retain the “original” copy of all proposals and supplemental documents provided. Unless the offeror requests otherwise, at the completion of this acquisition the Government will destroy all extra copies of proposals and additional documents submitted.

1.1.1 General Information

1.1.1.2 Point of Contacts

All questions, concerns, or clarifications shall be addressed to the Procuring Contracting Officer (PCO) listed below as the sole point of contact for this acquisition. All inquiries must be made in writing and submitted electronically to the Contract Specialist with a copy to the PCO. Offerors will receive a notice of receipt, but if they do not, it is their responsibility to follow-up by contacting the addressees listed below.

Contract Specialists: Leah Ransom and/or Garrentt Baca

AFOTEC/A-7K

8500 Gibson Blvd SE Kirtland AFB, NM 87117-5558 Phone—(505) 846-1393/ (505) 846-2242 Email: leah.ransom@kirtland.af.mil/garrentt.baca@kirtland.af.mil Fax: (505) 846-2414

PCO: Paulette S. L. Windley

AFOTEC/A-7K

8500 Gibson Blvd SE Kirtland AFB, NM 87117-5558 Phone—(505) 846-1955 Email: paulette.windley@kirtland.af.mil Fax: (505) 846-2414

Concurrent with the release of this Request For Proposal (RFP), appropriate offices will be advised that a source selection action is in progress for the proposed effort and that contact by participating offerors on the subject of this RFP is inappropriate. Recipients of this RFP shall not attempt such contacts during this period.

1.1.1.3 Debriefings

If a competitive range is established, the PCO will promptly notify offerors of any decision to exclude them, whereupon they may request a debriefing in accordance with FAR 15.505, Pre-Award Debriefing of Offerors. The PCO will also notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.503, Notification to Unsuccessful Offerors. 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.506, Post Award Debriefing of Offerors, as applicable.

1.1.1.4 Security Classification

A DoD Contract Security Classification Specification, DD Form 254, will be incorporated as part of the contract. An offeror must be able to perform requirements at the highest level (TS/SCI/SAP) to be eligible for award.

1.1.1.5 Pre-Award Survey

A pre-award survey may be accomplished on all offerors submitting proposals to supplement the determination of contractor responsibility as defined in FAR 9.1. The offeror shall be required to participate in a pre-award survey for the purpose of determining its financial and technical ability to perform. The pre-award survey is conducted with the assistance of the offeror’s cognizant Government Contract Administration Office to determine its eligibility and ability to perform. Refusal to participate in a pre-award survey and failure to provide all requested information may be cause for rejection of the offer.

The pre-award survey may include performance of a formal financial capability risk assessment or an audit by the Defense Contract Audit Agency (DCAA) or other personnel assigned by the PCO to perform the task. This effort would be performed in accordance with DFARS 232.072-1 and the information required for an audit would include, but not be limited to, the information identified in DFARS 232.072-2. The contractor agrees to provide the financial information for such financial capability effort in a timely manner. Failure to provide the requested data could cause the offeror to be determined financially irresponsible as discussed in FAR 9.103(b).

1.1.1.6 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. The offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of additional or substitute pages of the initial proposal.

1.1.1.7 Evaluation Notices (ENs)

If any additional exchanges are required, written ENs will be sent to the offeror. Offerors will be allowed sufficient time to submit written responses.

1.1.1.8 Contract Limitations

The shared contract ceiling is $77 million.

1.1.1.9 Evaluation

Offers will be evaluated using the factors and subfactors found in Section M, Evaluation Factors for Award. The offeror’s responses to task orders will be used as a validation tool for the offeror’s capabilities in reference to, and understanding of, the technical subfactors. Failure to comply with the RFP will render the proposal non-responsive, and may eliminate the proposal from consideration for contract award.

L2.0 PROPOSAL FORMAT AND PREPARATION INSTRUCTIONS

2.1 Proposal Format

In order to maximize efficiency and minimize the time for proposal evaluation, the paper proposal (and electronic proposal if printed) shall meet format requirements. The proposal shall be limited to the submission of the volumes specified in Table L3.1.1 below. Proposals shall not contain any classified information.

2.1.1 Text

Text type shall be Times New Roman. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12-point with normal proportional spacing. Text lines to include all tables, charts, graphs, and figures, shall have 1.5-line spacing. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software.

2.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 (for paper copies) will not be returned to the offeror. For electronic CD-ROM submission, no hidden fields, macros, comments, etc., will be read. All information shall be written clearly and be easily accessible. Page limitations may also be placed on ENs, if required. The page limitations for ENs, if any, will be identified in the correspondence forwarding the ENs to the offerors. When both sides of a sheet of paper display printed material, it shall be counted as two pages. Each volume shall contain a detailed table of contents to delineate what is in the respective volume, which will not be counted in the page limits. In addition, the following will also not be counted in the maximum page limits: cover pages, tabs, cross-reference matrix, glossaries, and any position descriptions.

2.1.3 Page Size

A page is defined as each face of a 8 ½ x 11-inch sheet of paper containing information (excludes such things as blank pages, title pages, table of contents, tabs, dividers, glossaries, and indices). Page margins shall be a minimum of 1-inch each for the top, bottom and sides. All material must be contained within the page limit identified for each volume or appendix. The page limitations specified in Table L3.1.1 shall be treated as maximum limits to assist in the evaluation of each proposal. Total page count will be based on the printed proposal submission. The background color of each page of the proposal submission shall be white or ivory paper only. If Final Proposal Revisions (FPR) are required, the same initial proposal page limitations apply for each volume or appendix. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to ENs, and to both electronic and hard copy proposals.

2.1.4 Tables, Charts, Graphs, And Figures

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and/or task layout, schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size when printed. Foldout pages shall fold entirely within the volume and count as two pages. Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics, and not for pages of text. For tables, charts, graphs and figures, the text shall be no smaller than Times New Roman 10 point. All tables, charts, graphs and figures will be included in the page count. Any tables, charts, graphs and/or figures containing smaller than Times New Roman 10 point font will be disregarded. This restriction applies to both electronic and hard copy proposals. Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

2.1.5 Cross-Reference Matrix

To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with minimal 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 and/or improve clarity. The cross-reference matrix will not count against the page limitations for their respective volumes.

2.1.6 Tab 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. Tabs/indexes will not count against the page limitations for the respective volume.

2.1.7 Glossary Of Terms

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

2.1.8 Binding And Labeling

Each volume shall be separately bound and labeled in a D-ring, loose leaf binder, and clearly identified on the front and side. The binders should permit the volume to lie flat when open, and allow for easy removal and replacement of pages. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation number and the offeror’s name and CAGE code. The same identifying data should be placed on the spine of each binder. 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 on both the hard copy and CD-ROM.

2.1.9 Electronic Media Offers And Submission

On each CD-ROM indicate the offeror’s name, CAGE code, solicitation number, volume, and title and any appropriate markings identified in L2.1.8. The electronic copies of the proposal shall be submitted in a format readable and usable by Microsoft (MS) Office 2007® (MS Word®, MS Excel®, and MS PowerPoint®) or in PDF format viewable with the standard Adobe Acrobat Reader 9 . All files shall not be compressed. Hidden fields, comments, macros, etc., shall be omitted. The files shall be consistent and uniformly named to allow for easy distinction by Volume, Tab, etc. Inclusion of company name is preferred. An example of this would be: V-IV Cost/Price XYZ Company, or V-IV Cost/Price XYZ Co. Table 1 or XYZ Co. Vol-IV, Tab A. The documents submitted in electronic format, if printed, should match the original paper copy. In the event there is a discrepancy between the content found in a paper copy and an electronic copy, the paper copy shall take precedence. The receipt of the paper copies shall constitute the timely receipt of the formal proposal.

2.1.9.1 Electronic Media Offers And Submission for the PPI Tool When submitting electronic versions in the PPI Tool, offerors shall follow these instructions:

1. Electronic storage media shall be submitted in one of the following format: prerecorded (pressed) CD-ROM or CD-R.

1. Submitting documents using Microsoft Office 2007:

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

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

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

1. Submit any Microsoft Project files in Microsoft Project 2007. There are no special “save” functions required for later versions of Project.

1. Submit PDF documents using only Adobe Acrobat 9.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 function

2.1.10 Electronic Reference Documents

All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at https://www.fbo.gov or the AF e-publishing website at www.e-publishing.af.mil. Potential offerors are encouraged to subscribe for FedBizOpps real-time e-mail notifications when information has been posted to the website for this solicitation.

2.1.11 Cost Or Pricing Information

All cost or pricing information shall be addressed ONLY in the Cost/Price Proposal Volume. Cost trade off information and work hour estimates may be used in other volumes only as appropriate for presenting rationale for alternatives or trade off decisions.

L3.0 PROPOSAL VOLUME INSTRUCTIONS AND OTHER REQUIRED DOCUMENTATION

3.1 Volumes

Offers will consist of four (4) separate proposal volumes: Executive Summary & Contract Documentation, Technical, Past Performance, and Cost/Price.

3.1.1 Proposal Volumes Organization, Number Of Copies, And Page Limits The offeror shall prepare the proposal as set forth in Table L3.1.1 and Section L.

Table L3.1.1. Proposal Organization

Including OCI mitigation plan, if applicable Original + 4

+ 1 CD-ROM

10 pages for Executive Summary/No Limit for Contract Documentation

+ 1 CD-ROM

120 pages total

+ 1 CD-ROM

+ 1 CD-ROM with PPI Tool See Para L8.0 No hard copies of Business Relationships or PPI report are required.

+ 1 CD-ROM

No Limit

3.2 Volume II Cross-Reference Matrix

Offerors shall complete the cross-reference matrix provided at Attachment L1 indicating the proposal reference information as it relates to the RFP. The cross-reference matrix does not count in the total page count. The purpose of the cross-reference matrix is to show critical relationships and dependencies as it applies to the RFP, and the location in the offeror’s proposal. As appropriate, format will be “Volume(s) X; Page(s) X; Para. (s) X”.

L4.0 RECEIPT OF PROPOSALS

Proposals are due on the date and time specified on the Standard Form 33, Block 9, and shall be submitted in accordance with the instructions herein. Late proposals may be rejected from consideration. If any proposal is received late, the PCO will promptly notify the offeror that its proposal was received late and whether the proposal will still be considered. It is the offeror’s responsibility to confirm the Government has received the proposal.

Early submission of the past performance volume before the required submission date for the rest of the proposal is desirable. The questionnaire should be sent directly to the Government Contracting Officer identified in L.1.1.1.2. Mailing the questionnaire(s) is an acceptable alternative method of transmission. If mailing, the outside envelope must be marked with: “NOTE: TO BE OPENED BY ADDRESSEE ONLY”. Each offeror is requested to submit Volume III, Past Performance 10 days prior to the date set for receipt of proposals. Failure to submit early proposal information will not result in offeror disqualification.

All proposals delivered in response to this solicitation shall reflect the following in the address label:

(1) Solicitation Number: FA7046-11-R-0003

(2) The Legend. “TO BE DELIVERED UNOPENED TO THE CONTRACTING OFFICER,” and

(3) The volume copy numbers contained in each box.

L5.0 BIDDER’S LIBRARY

There will not be a physical Bidder’s Library. All unclassified Bidder documents including PWS exhibits are available on the FedBizOpps website.

L6.0 VOLUME I – EXECUTIVE SUMMARY & CONTRACT DOCUMENTATION

6.1 Executive Summary

The purpose of this portion of this volume is to provide the Government evaluators with a clear and concise introduction to the content and structure of the offeror’s entire proposal, including significant risks, and highlight any key or unique features, excluding cost/price. This should be a "big picture" explanation and provide the offeror’s overall approach and supporting rationale for the performance/management of the OTES requirements. Offerors shall provide an Organizational Chart. The format of the Executive Summary is at the discretion of the offeror. Material presented in the Executive Summary will not be considered toward meeting the requirements for any portions of other volumes of the proposal.

6.2 Contract Documentation

The purpose of this portion of this volume is to provide information to the Government for preparing the contract document and supporting file(s). This portion shall include the following sections completed by the offeror:

6.2.1 The offeror shall provide the company/division's street address, county and facility code; CAGE code; DUNS code; size of business (large or small); and labor surplus area (i.e. HUBZone) designation. This same information must be provided if the work for this contract will be performed at any other location(s). Provide the same information for your major subcontractors.

6.2.2 Signature by the offeror on the Standard Form (SF) 33 constitutes an offer the Government may accept. The “original” copy shall be clearly marked under a separate cover and shall be provided without any punched holes. Section A shall also include the acceptance period of no less than 180 days during which the Government may accept the offer to create a binding contract.

6.2.3 Section G - Contract Administrative Data. Complete the “fill-in” required in Contractor’s Contract Administration in Section G. If not applicable, state so.

6.2.4 Section I – Complete fill-ins as applicable.

6.2.5 Section K - Representations and Certifications or a copy of the notice that these are available electronically via the Online Representations and Certifications Application (ORCA) website.

6.2.6 Acknowledgement of all amendments issued (if applicable).

6.2.7 The date of the offeror’s Affirmative Action Plan, expiration date, and the name and address of the cognizant U.S. Department of Labor, Office of Federal Compliance Programs Office.

6.2.8 Department of Labor Equal Employment Opportunity Clearance (EEOC) Information (Section L Attachment). In accordance with FAR Subpart 22.805, Pre-award clearances for contracts and subcontracts of $10million or more are required unless the contractor is listed in Office of Federal Contract Compliance Programs (OFCCP) National Pre-award Registry (http://www.dol-esa.gov/preaward/). In order for the PCO to request clearance from the appropriate OFCCP regional office, the Attachment in Section L shall be completed and submitted with the Contract Documentation Package. If an offeror is already listed in OFCCP’s National Pre-award Registry (http://www.dol-esa.gov/preaward/), submit verification of the registry entry in place of the completed Section L Attachment.

6.2.9 The date of the offeror’s most recent Federal Contractor Veterans Employment Report VETS-100 Report (Reference FAR 22.1304).

6.2.10 Identification of any actual or potential Organizational Conflict of Interest and associated mitigation plan IAW Section L 5352.209-9001, Potential Organizational Conflict of Interest.

6.2.11 Government Offices. Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO). Provide the same information for your major subcontractors.

6.2.12 Offeror’s Terms & Conditions and/or Statement of Exceptions to the Solicitation. Offerors must clearly identify any exception to the solicitation Terms & Conditions and provide complete accompanying rationale. Any non-compliance with Terms & Conditions of the RFP may cause the proposal to be unacceptable. See L.10 for format.

6.2.13 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. Finally, please provide the name, title, and telephone number of the CEO, Division President, or Vice President of the offeror.

6.2.14 Organizational Financial Information. Submit copies of the prime contractor's latest available financial statement covering the organization(s), which will perform the contract. Include any information, which may have a bearing on your ability to handle the financial management of the contract per FAR 9.104-1(a). If you are proposing a joint venture, describe how you will handle financial matters.

6.2.15 Any other data the offeror chooses to bring to the attention of the PCO.

L7.0 VOLUME II – TECHNICAL

7.1 General

The purpose of the Technical Volume is to provide the Government the ability to evaluate the management and technical approach of the offeror to perform the OTES requirements. The offeror’s technical proposal shall be specific and complete. Legibility, clarity, and coherence are very important. The offeror’s technical proposal shall provide as specifically as possible the actual methodologies and system that will be used to accomplish/satisfy the OTES requirements. All the requirements specified in the solicitation are mandatory. Offerors shall not merely reiterate the objectives or reformulate the requirements specified in the solicitation but shall demonstrate a clear and concise approach to meet the requirements. The technical proposal shall not include price information, classified information, or "For Official Use Only" information. Evaluation will be against the technical subfactors as specified in Section M of this RFP. For each planned subcontractor/teaming member, provide a brief description of the capability the subcontractor/teaming member will provide and/or work they will perform and the basis for selecting them. The Government shall not assume that the offeror possesses any capability unless identified in the proposal.

7.2 Volume Organization

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

Table of Contents List of Table and Drawings Glossary Cross Reference Matrix Subfactor One: Knowledge of Technical Capabilities Subfactor Two: Management Approach

7.2.1 Subfactor One: Knowledge Of Technical Capabilities

In the technical volume, offerors shall address their proposed approach to meeting the requirements of each technical subfactor, as well as the risks in their proposed approach in terms of technical capability/performance, cost, and/or schedule. The offeror’s proposal shall address the overall RFP requirements unless specifically instructed to address at the task order level. The technical volume will provide basis for evaluating the offeror’s ability to comply with the specific performance requirements of the PWS and the task orders. The task orders are:

Task Order 0001, Nuclear Weapons, Directed Energy Weapons, and Natural Space Environment Survivability Services. This task order will be awarded.

Task Order 0002, Operational Test & Evaluation (OT&E) Test Program Technical & Scientific Services for the Bomber Test Division. This task order will be awarded.

Sample Task Order 0003, Joint Service Personnel Skin Decontamination System (JSPDS). This sample task order will not be awarded and will be used to evaluate the offeror’s ability to meet CBRN requirements.

Areas to be addressed are as follows:

0. Provide an adequate approach to satisfying PWS 3.2, 3.3, 3.4, 3.5, and 3.6 requirements as applicable for each individual task order

0. Use the Integrated Life Cycle Chart attachment to explain how a program office performs an acquisition to include:

a) List methods to influence early processes.

b) List key documents AFOTEC requires to understand and/or provide input to the acquisition process.

0. Describe the processes AFOTEC uses to create an Initial Test Design and list the process steps leading to finalize the test design.

0. List and describe all the major components required in a test plan. Explain how data is collected to write each of these components.

a) Explain what a Data Management and Analysis Plan (DMAP) is and its purpose and provide a sample of a DMAP (1 page)

b) Explain what Detailed Test Plans (DTPs) are used for and provide a sample page of a DTP.

0. Provide the following related to operational test execution; including test range infrastructure, test instrumentation, and data collection

a) Explain the use of hypothesis testing processes.

b) Explain Design of Experiment (DoE) as used in operational test design.

c) Explain statistical processes for Reliability, Maintainability & Availability (RMA).

d) Explain how and why AFOTEC uses Modeling and Simulation (M&S).

e) Explain Verification, Validation, and Accreditation (VV&A) process and AFOTEC’s role in this process.

0. Explain the resources necessary and instrumentation required to execute:

a) munitions test

b) space test

c) aircraft test

d) cyber test

0. Explain the AFOTEC processes timelines to gather data and publish a report. Specifically describe:

a) Joint Reliability and Maintainability Evaluation Team (JRMET) process

b) Deficiency Review Board

c) Deficiency Reporting

d) Data Analysis

7.2.2 Subfactor Two: Management Approach

Offeror shall submit a written proposal explaining how your company shall meet the government’s overall management requirements by providing the following. Government assumes that the management approach will apply to Task Orders 0001 through 0003 and all subsequent task orders issued.

7.2.2.1 Management Plan. Plan must demonstrate to the Government, the offeror’s ability to develop an effective Management Plan by addressing:

a) Organizational Chart or the offeror’s proposed performance/management structure that defines the functional relationships, areas of responsibility, and lines of control/authority among the organizational elements, including proposed subcontractors and/or teaming members IAW PWS Paragraph 3.1.

b) Relationship of the management of this contract with the corporate organization and the management of subcontractors.

c) Position descriptions for all direct technical personnel performing technical requirements (no résumés with names).

7.2.2.2 Initial Staffing. Present the plan for selecting/retaining personnel with sufficient breadth and currency of experience/expertise across the core competencies. The plan must address:

7.2.2.3 Personnel End Strength. Present the plan for staffing the required personnel for the life of the contract and task orders. The plan must address:

7.2.2.4 Staffing Vacancy-Filling. Discuss how management plans to provide an active, responsive staffing vacancy-filling system to ensure adequate manning throughout the contract’s life to include SAP personnel. The plan must address:

7.2.2.5 Phase-In Transition Plan. A transition plan is required by all offerors. The plan should address the following: 1) Include a schedule for meeting all objectives within the 30-day transition period. Include security clearance processing. In addition, establish incremental milestones that will be used to measure the progress of the transition; 2) Describe how operations, management, and certification training (if applicable) shall be accomplished; 3) Describe how personnel will be apportioned to ensure a sufficient breath of experience; 4) Describe the offeror’s approach to development and dissemination of policies, procedures, and control in preparation to assume control of all responsibilities from the incumbent; 5) Identify the level in the corporation at which responsibility for the phase in plan is located, the structure of the organization for accomplishing phase in activates and corporate specialists; 6) identify the offeror’s approach to establishing controls to ensure the operations, management, training schedules are accomplished; 7) Convey the offeror’s understanding of the importance of not having deterioration of service during the transition from one contractor to another. The government realizes that there is inherent risk in the transition effort. Offerors are encouraged to identify such risk and explain how they propose to minimize it. Discuss the offeror’s intent to retain incumbent personnel and how the offeror will transition the subject personnel to his/her organization. Discuss any special techniques that will be used to maintain a strong working relationship with the incumbent. Proposed cost for the task order transition efforts are not separately priced. All costing data shall be included in the task order proposals, to be provided in Vol IV. There will be no Phase-In if the successor contractor subcontracts to an ETS incumbent (prime or subcontractor) and they are performing the same or similar work. The offeror must provide an orderly transition of work acceptance and accomplishment such that any impact to a program is minimized. The Phase-In time period is 30 days and is the first month of the 12-month period of performance for the basic effort.

L8.0 VOLUME III – PAST PERFORMANCE

8.1 General

The offeror shall submit a past performance volume containing past performance information. Failure to provide the information may result in the offeror being removed from consideration for award. Past Performance Information submitted, either Government or commercial, must be for the same business unit proposing to perform the OTES requirements. A business unit (also called a department, division, or functional area) is defined to be a distinct operating unit within the overall corporate entity distinguishable from other units based on a mission, objectives, and defined set of products or services different from other company business. This rule applies to the proposed prime Contractor as well as proposed subcontractors/teaming members.

8.2 Content Of Past Performance Volume

The offeror’s Past Performance Volume shall contain the following and be within the specified page constraints.

Table of Contents Glossary

Business Relationships (PPI Tool) Describe the role of the offeror and each subcontractor, teaming partner, and/or joint venture partner.

8.2.1 Table Of Contents

The Table of Contents shall list all documents contained in the Past Performance Volume.

8.2.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 performance evaluation. Since the Government intends to consider past performance information provided by other sources as well as that provided by the offeror(s), the "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. This information is required on the offeror and major subcontractors/teaming members. A major subcontractor is defined as one that will perform 20% or more of the technical work for Task Orders 0001 and 0002.

8.2.3 Business Relationships Report

This report shall describe the role and efforts to be performed by the prime offeror and each subcontractor/ teaming member for which past performance information is provided. The offeror shall submit the Business Relationships Report in accordance with the format contained in Section L Attachment L2.

8.2.3.1 Determination Of Responsibility

Even though the assessment of Past Performance as a specific evaluation factor is separate and distinct from the Determination of Responsibility required by FAR 9.1, Responsible Prospective Contractors, information obtained as part of the proposal evaluation process will be used to support the Determination of Responsibility for the successful offeror(s).

8.2.4 Past Performance Information Report

A Past Performance Information Report is required on the prime offeror and each major subcontractor/teaming member defined above. Offerors shall submit information on contracts they consider most relevant in demonstrating their ability to perform the proposed effort. Past performance on IDIQ type contracts shall be submitted according to the manner in which performance is formally assessed (e.g. per specific delivery/task order or for the IDIQ contract as a whole). For instances where performance is formally assessed for the IDIQ contract as a whole, the offeror shall identify the single point of contact that can verify the offeror’s performance record under that IDIQ type contract. In instances where performance is not formally assessed at either level, offerors shall submit past performance information at the delivery/task order level. Each delivery/task order submitted will be counted as one contract. Clearly link the past performance information to the relevancy information in the past performance area of Section M. Offerors are required to explain what aspects of the contracts submitted for review are deemed relevant to the OTES effort.

The offeror shall submit the Performance Information Report in accordance with the format contained in Section L Attachment L2. The offeror shall submit no more than a total of seven (7) Performance Information Reports identifying active or completed contracts, either Government or commercial. Limits on Performance Information Reports are as follows:

If subcontractors are to be used:

1. Three (3) reports identifying active or completed contracts, either Government or commercial, for the prime, team, and/or joint venture (within the same division or cost center).

1. Two (2) reports from each subcontractor who will be completing 20% or more of the technical work.

8.2.4.1 Alternate Past Performance Assessment Forms

If an evaluation method other than a PPIRS has been used in conducting performance assessments (e.g. an Award Fee notification letter, a subcontractor’s prime Contractor performance evaluation, etc.), this should be noted on the Past Performance Information Sheet submitted with the contract number, phone number and email address of the individual that can be contacted to obtain this past performance information.

8.2.5 Consent And Client Authorization Letters

Past performance information concerning subcontractors/teaming members cannot be disclosed to a private party without the subcontractor’s or teaming member’s consent. Because the offeror is a private party, the Government will need consent from the appropriate subcontractor/teaming member before disclosing subcontractor/teaming member past performance information to the offeror during any exchanges. In an effort to assist the Government in assessing the offeror’s past performance record, a consent letter, similar to that included at Attachment L5, should be completed by each major subcontractor/teaming member identified in the offeror’s proposal. The completed consent letter(s) submitted as part of the Past Performance Information Volume will not be considered in the page count of that Volume. Should the offeror not submit a completed consent letter for a major subcontractor/teaming member the Government will not disclose/discuss the applicable past performance information other than with that prospective subcontractor or teaming member being reviewed. If there is a concern with the proposed subcontractor’s/teaming member’s past performance, the offeror can be notified, but no details may be discussed without the subcontractor’s or teaming member’s consent. For each identified effort for a commercial customer, the offeror shall also submit a Client Authorization (Consent) Letter, Attachment L5 in Section L, authorizing release to the Government the requested information on the offeror’s performance.

8.2.6 Recency And Relevancy Of Past Performance Volume

The Government will consider recency and relevancy of past performance. See Section M, Table 3, “Past Performance Relevancy Ratings”. Offerors shall include their rationale why the contract, or a specific portion of the contract submitted, is relevant for consideration in demonstrating their ability to perform the OTES requirements. The Government is not bound by the offeror’s opinion of relevancy. The Government may contact references other than those identified by the offeror, and use the information received, to evaluate the offeror’s past performance. The offeror shall complete the relevancy matrix similar to that included as Attachment L6.

8.2.7 Past Performance Questionnaire

The Past Performance Questionnaire is included at Attachment L4. Although it will become part of the Past Performance content, the completed questionnaires shall not be submitted with the rest of the Past Performance Volume. The offeror shall distribute the questionnaire to each POC listed on the Past Performance Information Sheets. A cover letter for transmitting the questionnaire to each POC is provided at Attachment L3. The offeror shall exert its best efforts to ensure that there are at least two (2) points of contact (PCO, Program/Project Manager, ACO, or equivalent) per relevant contract. Each of the POCs shall e-mail, fax or mail the completed Present and Past Performance Questionnaire directly to the PCO’s attention (see paragraph 1.1.2). Responses routed through the offeror will not be accepted. Mailing the questionnaire(s) is an acceptable alternative method of transmission. If mailing, the outside envelope must be marked with: “NOTE: TO BE OPENED BY ADDRESSEE ONLY”.

8.2.7.1 Questionnaire Recipients

Offerors shall provide a summary list of questionnaire recipients to include POCs and phone numbers.

8.2.8 Specific Content

Offerors may include a discussion of efforts accomplished by them to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. 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. Categorize the relevance information into the specific Technical subfactors and Cost/Price factor used to evaluate the proposal.

8.2.9 AFOTEC Safety Requirements Compliance.

Contractor must provide OSHA citations for the last 3 years. Information must include willful, serious and other-than serious violations for NAICS code 541712. “Violations” is defined in OSHA standards.

L9.0 VOLUME IV – COST/PRICE

9.1 General

Separate cost proposals, including options, must be submitted for each task order performance work statement using cost summary format provided. The basic year and each option year shall be segregated. A cost proposal for transition phase-in and phase-out and travel are not required. Transition Phase-in costs are effective with the start date of each task order and are not to be segregated on each task order. Do not propose travel costs. The Government has stated the ceiling cost for travel in each task order, to include all applicable indirect costs and tax (if applicable), fee will not be paid on travel; funding and ceiling amount will be included on each task order when awarded. A cost proposal is not required for the basic performance work statement. Corresponding workload estimates are provided in each task order performance work statement that provides the current manning. This data is provided as information only. See Paragraph 9.2.7.1.4 for additional information.

9.1.1 Cost/Price Reasonableness And Realism

These instructions provide the offeror guidance in submitting informational other than cost or pricing data that is required to evaluate the reasonableness and realism of their proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note, that unrealistically low or high-proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has made an unrealistic proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers shall be sufficiently detailed to demonstrate their reasonableness and realism. The burden of proof for credibility of proposed costs/prices rests with the offeror.

9.1.2 Cost/Price Information

Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All information 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 information and documentation be included elsewhere in the proposal.

9.1.3 Cost or Pricing Information Requirements

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

9.2 Cost/Pricing Volume Content

The format of the Cost/Price volume shall be as follows:

9.2.1 Tab 1 – Table Of Contents, Glossary, And Definitions

Provide a detailed table of contents for this volume. Provide a glossary of all abbreviations and acronyms used, with an explanation for each. However, use of abbreviations and acronyms should be limited. Provide definitions as necessary.

9.2.2 Tab 2 – Estimating System/Methodology

Provide a summary description of your standard estimating system or methods, current policies, and/or new policies. State whether you have Government approval of your estimating system and if so, provide evidence of such approval. The summary description shall cover separately each major cost element (e.g., Direct Labor by major labor category, Indirect Costs, Other Direct Costs, Overhead, G&A, etc.) Provide any known/cited estimating system deficiencies. Also, identify any deviations from the offeror’s established/standard estimating procedures used in preparing this proposal. See paragraph 9.2.7.2 regarding requirements for detailed basis of estimate narratives.

9.2.3 Tab 3 – Purchasing System

Provide a summary description of your purchasing system or methods. State whether you have Government approval of your purchasing system and if so, provide evidence of such approval. Provide any known/cited purchasing system deficiencies.