2a_-_Final_Draft_Section_L_-Draft_27_Aug_15_.doc

PART IV - REPRESENTATIONS AND INSTRUCTIONS

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS

SECTION L

Instructions, Conditions, and Notices to Offerors or Respondents

“Notice to Offeror(s)/Supplier(s): Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse any offeror for any costs.”

SOLICITATION PROVISIONS INCORPORATED BY REFERENCE

NOTICE: The following provisions are incorporated herein by reference:

A. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) SOLICITATION PROVISIONS

52.204-7

SYSTEM FOR AWARD MANAGEMENT (JUL 2013)

52.207-1

NOTICE OF STANDARD COMPETITION (MAY 2006)

52.211-14

NOTICE OF PRIORITY RATING FOR NATIONAL DEFENSE,

EMERGENCY PREPAREDNESS, AND ENERGY PROGRAM USE

(APR 2008)

Contracting Officer indicates DX or DO Rated Order: 'DO'

52.215-01

INSTRUCTIONS TO OFFERORS--COMPETITIVE ACQUISITION (JAN 2004)

52.215-16

FACILITIES CAPITAL COST OF MONEY (JUN 2003)

52.215-20 REQUIREMENTS FOR CERTIFIED COST OR PRICING DATA AND DATA OTHER THAN CERTIFIED COST OR PRICING DATA (OCT 2010)

52.215-20 REQUIREMENTS FOR CERTIFIED COST OR PRICING DATA AND DATA OTHER THAN CERTIFIED COST OR PRICING DATA (OCT 2010)

ALTERNATE IV (OCT 2010)

52.215-22 LIMITATIONS ON PASS-THROUGH CHARGES – IDENTIFICATION OF SUBCONTRACT EFFORT (OCT 2009)

52.216-01

TYPE OF CONTRACT (APR 1984)

Type of contract is 'Firm Fixed Price, Cost-Plus-Fixed-Fee, and Cost-Reimbursement'

52.216-27

SINGLE OR MULTIPLE AWARDS (OCT 1995)

52.233-02

SERVICE OF PROTEST (SEP 2006)

Para (a) Official or location is ATTN: Erik Urban, '205 West D Avenue

Ste. 425 Eglin AFB, FL 32542-6808'

B. DEPARTMENT OF DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENT (48 CFR CHAPTER 2) SOLICITATION PROVISIONS

252.204-7004

ALTERNATE A. SYSTEM FOR AWARD MANAGEMENT (FEB 2014)

252.227-7028 TECHNICAL DATA OR COMPUTER SOFTWARE PREVIOUSLY DELIVERED TO THE GOVERNMENT (JUN 1995)

252.242-7006 ACCOUNTING SYSTEM ADMINISTRATION (FEB 2012)

C. AIR FORCE FEDERAL ACQUISITION REGULATION SUPPLEMENT SOLICITATION PROVISIONS

5352.215-9000 FACILITY CLEARANCE (MAY 1996)

SOLICITATION PROVISIONS IN FULL TEXT

NOTICE: The following provisions are hereby incorporated in full text:

A. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) SOLICITATION PROVISIONS

52.252-01 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this address: http://farsite.hill.af.mil/

52.252-05 AUTHORIZED DEVIATIONS IN PROVISIONS (APR 1984)

(a) The use in this solicitation of any Federal Acquisition Regulation (48 CFR Chapter 1) provision with an authorized deviation is indicated by the addition of "(DEVIATION)" after the date of the provision.

(b) The use in this solicitation of any Defense Federal Acquisition Regulation Supplement (48 CFR Chapter 2) provision with an authorized deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation.

B. DEPARTMENT OF DEFENSE FEDERAL ACQUISITION REGULATION SUPPLEMENT (48 CFR CHAPTER 2) SOLICITATION PROVISIONS:

None.

C. AIR FORCE FEDERAL ACQUISITION REGULATIONS SUPPLEMENT SOLICITATION PROVISION

5352.201.9101 Ombudsman

(a) An ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition. When requested, the ombudsman will maintain strict confidentiality as to the source of the concern. The existence of the ombudsman does not affect the authority of the program manager, contracting officer, or source selection official. Further, the ombudsman does not participate in the evaluation of proposals, the source selection process, or the adjudication of protests or formal contract disputes. The ombudsman may refer the interested party to another official who can resolve the concern.

(b) Before consulting with an ombudsman, interested parties shall first address their concerns, issues, disagreements, and/or recommendations to the contracting officer for resolution. Consulting an ombudsman does not alter or postpone the timelines for any other processes (e.g., agency level bid protests, GAO bid protests, requests for debriefings, employee-employer actions, contests of OMB Circular A-76 competition performance decisions).

(c) If resolution cannot be made by the contracting officer, the interested party may contact the ombudsman Colonel Todd M. Copeland, todd.copeland@us.af.mil; Fair Opportunity Ombudsman: Audrea Feist, (850) 882-7284, audrea.feist@us.af.mil. Concerns, issues, disagreements, and recommendations that cannot be resolved at the Center/ombudsman level, may be brought by the interested party for further consideration to the Air Force ombudsman, Associate Deputy Assistant Secretary (ADAS) (Contracting), SAF/AQC, 1060 Air Force Pentagon, Washington DC 20330-1060, phone number (571) 256-2395, facsimile number (571) 256-2431.

APPLICABLE CLAUSES (MAY 2009)

The appropriate clauses to be included in the contract will be determined based on Offeror's response to the Section K representations.

(a) Patent Rights. If the Offeror is a small business firm or nonprofit organization, then FAR

52.227-11, PATENT RIGHTS -- OWNERSHIP BY THE CONTRACTOR, and DFARS 252.227-7039, PATENTS - REPORTING OF SUBJECT INVENTIONS will be used in Section I. Otherwise, DFARS 252.227-7038, PATENT RIGHTS - OWNERSHIP BY THE CONTRACTOR (LARGE BUSINESS), will be included in Section I consistent with FAR Part 27.

(b) Cost Accounting Standards. Section I of this solicitation may contain the three Cost Accounting Standards clauses at FAR 52.230-3, 52.230-4, 52.230-5, and/or 52.230-6. The resultant contract will contain only those clauses required based on the Offeror's response to the Section K certification titled Cost Accounting Standards Notices and Certification (National Defense).

(c) State of New Mexico. Section I of this solicitation may contain the clause at FAR 52.229-10, STATE OF NEW MEXICO GROSS RECEIPTS AND COMPENSATING TAX. The resultant contract will contain this clause only if performance is in whole or in part within the State of New Mexico and the contract directs or authorizes the contractor to acquire property as a direct cost under the contract.

(d) Educational institutions and nonprofit organizations. If a cost-reimbursement type contract is contemplated and the offeror is an educational institution, paragraph (a) of the clause at FAR 52.216-7, Allowable Cost and Payment shall be altered in the resultant contract to refer to FAR Subpart 31.3 for determining allowable costs. Similarly, if the offeror is a nonprofit organization (other than an educational institution, a State or local government, or a nonprofit organization exempted under OMB Circular No. A-122), paragraph (a) of the clause at FAR 52.216-7 shall be altered to refer to FAR Subpart 31.7. In addition, if the offeror is an educational institution, DFARS 252.209-7005, MILITARY RECRUITING ON CAMPUS, will be added to Section I of the resultant contract.

(e) Subcontracting Plan. If the offeror has a comprehensive subcontracting plan under the test program described in 219.702(a), DFARS 252.219-7004, SMALL BUSINESS SUBCONTRACTING PLAN (TEST PROGRAM) will be used in lieu of FAR 52.219-9, FAR 52.219-10, FAR 52.219-16, AND DFARS 252.219-7003.

(f) Access to Air Force Computer Systems (May 2004). If performance under this contract will require access to Air Force computer systems (stand alone or networked), compliance with Air Force Instruction (AFI) 33-119 and Air Force Instruction (AFI) 33-202V1 is mandatory. It should be noted that such access requires, at a minimum, a National Agency Check or Entrance National Agency Check in accordance with DoD 5200.2-R, Personal Security Program. Offerors should make themselves familiar with local procedures for processing such requirements, and be prepared to be in compliance on the first day of contract performance. Failure to comply with this requirement may be considered a failure to perform.

INSTRUCTIONS, CONDITIONS, AND NOTICE TO OFFERORS

L-1.0 SUBMISSIONS OF PROPOSALS

a. Offeror's shall submit proposals no later than 9:00 AM CST on 9 Sep 2015 and shall be addressed to the CO, in accordance with Table 2.1, and mailed or hand carried to:

AFTC/PZIE

Erik Urban, Contracting Officer

205 West D Ave, Source Selection Facility (Bldg 373)

Eglin AFB, FL 32542-6864

b. Be sure to advise the Administrative Contracting Officer (ACO) and the Defense Contract Audit Agency (DCAA) for prime and subcontractors that the proposal is “For Official Use Only” and “Source Selection Information – See FAR 2.101 and FAR 3.104”

L-2.0 GENERAL INFORMATION

a. Offerors must include a valid and current DD 2345 “Military Critical Technology Data Agreement.” The proposal must include; the company name, mailing address, email address, point of contact, phone number, current CAGE number and System for Award Management (SAM) registration. The written request must include acknowledgement of the Responder's responsibility under the U.S. export contract laws and regulations. Upon verification of status and acknowledgement of responsibilities under U.S. export control laws and regulations

b. The offeror's proposal shall include all data and information requested by this Request for Proposal (RFP) and shall be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the SOW, Contract Data Requirements List (CDRL), and Model Contract. Non-conformance with the instructions provided in this RFP may result in the proposal being ineligible for award.

c. 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 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 shall base its evaluation on the information presented in the offeror's proposal.

d. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired. Similarly, for oral presentations, elaborate productions are unnecessary and not desired.

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

f. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all proposals.

g. Government Point of Contact: The CO is the sole point of contact for this acquisition. Address any questions or concerns you may have to the CO. Written requests for clarification shall be sent to the CO at the address located in Section A of the model contract/solicitation.

h. Offeror’s Point of Contact: The offeror shall notify the CO in writing of the name, phone, email, and FAX number of the individual to whom the Government shall give notice with the submission of the offeror’s proposal.

i. Security: The majority of Delivery Order (DO) requirements on this contract will be at a minimum at the SECRET level. Security requirements shall be addressed at the DO level. However, not having a security clearance will not exclude offerors from award on the basic contract.

j. The Government intends to award approximately 5 contracts under this solicitation. A parallel small business set aside competition is being conducted concurrently. An offeror awarded a prime contract under one of these two solicitations shall not receive a prime contract award under the other solicitation.

L- 2.1 Proposal Organization

a. The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 2.1 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 2.1. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. The contents of each proposal volume are described in the Instructions to Offerors (ITO) paragraph as noted in the table below:

Table 2.1 - Proposal Organization

Paper/

Electronic * Page Limit

SOW Capabilities

Subcontracts Utilization and Management/Small Business Participation with Small Business Plan*

SBP Only 10

Delivery Order Management Process/Sample Delivery Order*

SDO Response Only 10

OCI Mitigation Plan*

1 (This table is a sample. Include volumes and limits appropriate to your acquisition to include instructions on submittal of electronic versions of the proposal.)

For oral presentations no presentation shall exceed 60 minutes and any/all presentation materials not presented within the time limit will be excluded from evaluation.

* Written requirements are specified.

*** For a firm fixed price proposal where no pricing information other than CLIN prices is solicited, the Cost/Price volume may be eliminated and the proposed CLIN prices included in the Contract Documentation volume.)

b. If Evaluation Notices (ENs) are required, page limits shall be placed on any responses. The specific page limits for responses to ENs shall be identified in the letter forwarding ENs to the offeror. Excess pages submitted in response to these shall be removed and disposed of by the CO. Other deviations from the instructions shall be reviewed by the CO to ensure that no contractor receives a competitive advantage. Deviations resulting in a competitive advantage for an offeror shall result in the proposal being determined to be noncompliant with the RFP requirements.

c. To the greatest extent possible, each written volume shall be 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 shall be assumed to have been omitted from the proposal.

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

e. Each written volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections.

L- 2.2 Page Size/Presentation slide Format

a. A page is defined as a 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 1/2 x 11 paper.

b. Font shall be Times New Roman. Line spacing shall be set at 1.15 or greater. Text size for oral presentation materials (slides) shall be 14-point or larger with proportional spacing permitted. Text size for written proposal materials shall be 10-point or larger with proportional spacing permitted.

c. Margins on all four (4) edges of each page shall be at least 1 inch. In header on upper right of all pages, include: RFP number, part and/or subdirectory title and page number. Company name and proprietary information notices shall be placed in top and bottom margins. Pages in each volume shall be numbered sequentially and consecutively. The cover page, table of contents, list(s) of tables and drawings, blank pages, and cross-reference matrix are excluded from the page count.

d. Additional briefing format for Volume I: slides shall be legible and details concerning slide format are left up to the offeror.

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

f. The printed Small Business Plan, Sample Delivery Order proposal, and OCI Mitigation Plan (Volume I), relevant Past Performance Volume (Volume II), and Cost/Price Volume (Volume II) shall be bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet shall be used to clearly mark the volume number, title, solicitation identification, and the offeror's name. The same identifying data shall 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.

g. Electronic proposal materials: Do not submit on flash drive media; all content shall be READ ONLY. The offeror shall submit Volumes I, II and III on three separate labeled virus-free CD-ROMs/DVD. Identify the following data on both the disc and the disc jacket cover: RFP # (FA2487-15-R-0121), Government Address, disclosure statement, and company name. Do not compress the files. AFTC uses Microsoft Office 2010 for all data access.

L- 2.3 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 shall make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

L-2.4 DISCREPENCIES

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.

L- 2.5 Electronic Reference Documents

Most 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. The Statement of Work shall be forwarded to U.S. owned vendors only via secure email.

L- 3.0 Program Structure and Objectives The primary purpose of this CIMTIC IV Indefinite Delivery, Indefinite Quantity (IDIQ) contract is to meet Defense Guidance and Joint Chiefs of Staff objectives for the test and evaluation of Command, Control, Communications, Computers (C4) Information systems and munitions systems. The C4 Information & Munitions Test Improvement Contract IV (CIMTIC IV) will provide for the development and modification of Eglin Range systems, facilities, and test infrastructure required to test and evaluate C4I and munitions systems. This work includes development and modification of unique hardware and software. CIMTIC IV's primary purpose is to respond to urgent test range user's needs and prevent work stops for C4I and munitions test programs. This capability to provide rapid response, surge capacity, and flexibility for unforeseen events is critical to meet the short lead times and dynamic test requirements inherent in the testing of modern weapon systems and rapidly changing defense technologies.

This contract shall fill agency needs by placing DOs when short notice or unique requirements and products are identified. This contract vehicle does not have specific funding tied to it but rather will depend on inter-agency and outside agency (through the primary customers) funding and other program funding as provided. Each request for use of this contract vehicle shall be evaluated for appropriateness. This vehicle shall not be used for any Advisory and Assistance (A&AS) work nor shall it be used for full production requirements.

L- 4.0 Oral Presentations (FAR 15.102)

a. Each offeror is requested to notify the Government via email (erik.urban@us.af.mil) of their desire to provide an oral presentation two weeks after the release of the request for proposal. No oral presentation may exceed 60 minutes. One paper copy and two electronic copies (via CD-ROM/DVD) of all materials shall be submitted on the due date identified in block 9 of the RFP as amended. Briefing charts are to provide structure to the oral presentation. It is recommended that offerors structure their oral presentations to follow the order of items in Attachment M-1. The oral presentation shall be the basis for evaluation of Factor I as defined in Table 2.1. Any and all information contained in the slides not orally presented will not be considered as part of the offeror’s oral evaluation.

b. Offerors may not present any classified information either in their proposals or during oral presentations.

c. The location of the face-to-face oral presentations shall be in the Eglin AFB area. Presentations shall tentatively begin within one (1) week after the proposal due date. The offeror shall notify the CO in writing of the name, phone, email, and FAX number of the individual to whom the Government shall give notice with the submission of the offeror’s proposal.

d. The order of oral presentations shall be randomly generated. The Contracting Officer will notify offerors within one (1) week prior to the proposal close date by phone, email, or FAX of the offeror’s date, location and time of presentation. Offeror’s shall provide the Government with a primary and alternate point of contact to which the Contracting Officer should contact for scheduling purposes.

e. All oral presentation will be video/audio recorded

Note: The Government reserves the right to ask clarification questions after the 60 minute presentation following a short break for consultation. The Q&A session will be considered in the offeror’s oral evaluation. Q&A does not constitute formal discussions. Any and all information contained in the slides not orally presented will not be considered as part of the offeror’s oral evaluation.

L- 4.1 Communications Exchanges of source selection information between Government and offerors shall 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.

L- 5.0 Cost or Pricing Related Data

All cost or pricing data shall be addressed ONLY in the Cost/Price Proposal and Contract Documentation Volumes. Cost/Price Proposal and Contract documentation will NOT be included in the oral presentations.

L- 6.0 Volume I – Technical: SUBFACTORS A, B, C, D AND E

a. Subfactor A, B, C and D slide deck shall be provided in accordance with Table 2.1.

b. Subfactor A and B shall be presented via oral presentations.

c. Subfactor C Subcontracts Utilization and Management shall be presented via oral presentations. The proposed Small Business Plan shall be submitted in writing on the specified submittal date within the RFP.

d. Subfactor D Delivery Order Process shall be presented via oral presentations. The proposed Sample Delivery Order shall be submitted in writing on the specified submittal date within the RFP.

e. Subfactor E Organizational Conflict of Interest (OCI) Mitigation Plan shall be submitted in writing on the specified submittal date within the RFP.

L-6.1 SUBFACTOR A: STATEMENT OF WORK CAPABILITIES

Program Management and Technical Requirements shall be specific and demonstrate a complete understanding of SOW paragraph 3.0 through 3.14 and 3.16 through 3.32. Legibility, clarity, and coherence are very important. Responses shall be evaluated against M-3.1 Subfactor A: Statement of Work Capabilities. Provide as specifically as possible the actual methodology you would use for performing Program Management and the five technical requirements in Subfactor A. The technical criteria requirements are reflected in Section M.

L-6.1.1 DESIGN/REDESIGN

Offeror shall demonstrate the ability to perform Design and Engineering Development functions. The following are examples:

· defining the problem

· developing the analysis plan

· gathering & reviewing data

· constructing/populating models

· hypothesis testing

· running models

· analyzing results

· developing insights

· documenting/briefing results and soliciting feedback

· design approaches for initial designs and redesigns

· validate analytical models

· quantify contract technical performance and manufacturing quality

· measure progress in a system engineering design and development

· minimize technical risks

· predict integrated system operational performance (effectiveness and suitability) in the intended environment

· identify system problems (or deficiencies) to allow for early and timely resolution

L-6.1.2 HARDWARE

Offeror shall demonstrate the ability to execute hardware development, integration, modification, and manufacturing. The following are examples

· Compatibility, interoperability, and integration of all interfaces between the system and its operating environment, including electrical/electronic and mechanical hardware, firmware and software.

· Fabricate complex systems and ensure proper manufacturing planning

· Ensure system design and manufacturing processes are efficient and economical

· Track and assess the status of the program to determine if schedule, cost, and quality standards are being met

· Conduct quality and production assessments and reviews of the manufacturing effort

L-6.1.3 SOFTWARE

Offeror shall demonstrate the ability to execute software development, modification, and integration. The following are examples

· Compatibility, interoperability, and integration of all interfaces between the system and its operating environment, including electrical/electronic and mechanical hardware, firmware and software.

· Use of Computer Aided Software Engineering (CASE) methods and tools, inspections, and peer reviews.

· Standards and procedures for planning, estimating, coding, and recording software development efforts

· Data collection, storage, manipulation, filtering, feature extraction, control systems, data processing, data display, data archiving, scientific/engineering/technical analysis, and formatting and conversion

· Modifying software used to integrate, test and evaluate C4I systems or systems of C4I systems including scenario test scripting and simulated data streams

· Identification and management of Hardware Configuration Items (HWCI) and Computer Software Configuration Items (CSCI)

· Support of Government accreditation and/or firmware verification processes

L-6.1.4 TESTING

Offeror shall demonstrate the ability to perform testing at the breadboard, component, end item, and system levels. The following are examples:

· Conduct test planning, prepare and support test events, analyze and document test results.

· Conduct system performance validations and verifications to include high dynamic environments, EMI/EMC and complete all failure and hazards analysis.

· Provide essential information to decision-makers, assess attainment of technical performance parameters, and determine whether or not systems are operationally effective, suitable, survivable, and safe for intended use.

L-6.1.5 PROGRAM MANAGEMENT

Offeror shall demonstrate the ability to perform Program Management. The following are examples:

· Plan, estimate, budget, finance, manage cost, allocate resources, meet timelines, make trade-offs, implement subcontract management and a quality management system, and conduct risk management for individual projects to be complete within established schedule and budget for multiple projects.

· Management of special handling items (HAZMAT, Explosives, STINFO, Classified)

L- 6.2 SUBFACTOR B: STAFFING, QUALIFICATIONS AND EXPERIENCE

The offeror shall be specific and demonstrate a complete understanding of SOW paragraph 3.15 and shall provide recent/relevant experience in performing Program Management, and each of the Technical Requirements under paragraph M-3.1. Experience shall meet a recency period of within the past five years from the proposal due date. Each experience example shall relate to an entity (e.g. prime, subcontractor, etc.) that the contractor proposes to perform the particular type of effort under this contract. This information shall be reflected in the oral presentation.

L-6.3 SUBFACTOR C: SUBCONTRACTS UTILIZATION AND MANAGEMENT AND SMALL BUSINESS PARTICIPATION WITH SMALL BUSINESS PLAN

The offeror will describe his proposed subcontracts utilization and management approach including his proposed use of subcontractors to meet knowledge and technical criteria, processes for oversight of subcontractors, and organization and staffing necessities to meet subcontracts management requirements.

The Small Business Subcontracting Plan is a requirement for award and shall be incorporated into any resultant contract. The offeror shall present a small business subcontracting plan that complies with FAR 52.219-8.

Table L-6.3 below depicts the breakdown of the Small Business Subcontracting Plan goals. Offerors shall submit, in writing, a Small Business Subcontracting Plan addressing each of the categories listed in the table. Offeror’s goals shall meet or exceed the DoD goals shown in Table L-6.3 and the offeror shall present a methodology for meeting or exceeding such goals. For small business categories where the offeror’s goal is less than the DoD goal shown in Table L-6.3, the offeror shall provide a substantiated rationale for not meeting the suggested goal.

Table L- 6.3

Type of Small Business

(Reference DFARS 215.304(c)(ii). If this is a Major Defense Acquisition Program, as defined in 10 U.S.C. 2430, and the purchase and use of capital assets (including machine tools) manufactured in the U.S. is pertinent to the best value determination, include language substantially as follows, under one of the subfactors: “Submit a list of capital assets manufactured in the United States that will be purchased and/or used on this program. Include for each capital asset a brief description, date of purchase, or planned purchase, purchase price, manufacturer’s name and address, and location of asset manufacture.”)

(For all ACAT source selections and all other source selections where systems engineering effort is required consider Systems Engineering effort as a subfactor. Tailor paragraph accordingly. Specific guidance on how to tailor the evaluation criteria on Systems Engineering can be found at the Air Force Center for Systems Engineering, in their “Reference Library” under “DoD Policies and Guidance.” Look for the Guide for Integrating Systems Engineering into DoD Acquisitions and Contracts.)

L-6.4 SUBFACTOR D: DELIVERY ORDER MANAGEMENT PROCESS/SAMPLE DELIVERY ORDER

The offeror will describe his proposed delivery order management approach including his proposed delivery order process from RFP receipt, to proposal, followed by the delivery order execution process and closeout. The offeror will describe his corporate commitment and methodology to manage immediate tasking, and respond to changing delivery order requirements, including availability of resources to meet changing capacity requirements, and reporting of contractually required documentation.

In the evaluation of the sample delivery order, the Government will evaluate the offeror’s understanding of the requirement, technical approach, schedule/labor realism, and overall cost/price reasonableness. The offeror's proposal shall describe the technical approach and solution, perceived teaming arrangements/subcontractor involvement, technical risk, and data deliveries.

L-6.5 SUBFACTOR E: ORGANIZATIONAL CONFLICT OF INTEREST MITIGATION PLAN

It is a significant objective of this acquisition to promote customer confidence that Government activities are unencumbered by potential OCI in the use of customers’ competition-sensitive or proprietary information. That confidence among industry customers is vital to CIMTIC IV contractor access to sensitive and proprietary customer information that in turn is vital to the effective fulfillment of CIMTIC IV program requirements. Describe how your company will comply with the requirements of the OCI clause.

The offeror shall disclose business activities of itself, its affiliates, its team members, and affiliates of its team members which may create at least the appearance that any element of the offeror’s team might be motivated to use the Government customer’s information improperly.

The offeror may provide evidence of facts and circumstances which it believes ameliorates concerns related to the appearance and/or presence of such motive. The offeror may submit proposed approaches to mitigating the effects of any apparent or actual conflicts of interest arising out of the business activities disclosed.

L-7.0. VOLUME II – PAST PERFORMANCE INFORMATION

L-7.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 1. This information is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners who are proposed to perform 20(insert percentage) percent or more of the proposed effort based on the total proposed price (or cost, as applicable) or perform aspects of the effort the offeror considers critical to overall successful performance. 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. 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. The completed consent forms should be submitted as part of your Volume II, Past Performance Information, and will NOT be counted towards the 30-page limitation.

L-7.2 EARLY PROPOSAL INFORMATION

Each offeror is requested to submit the information shown in Attachment 1 (Attachment 2 to this template) for each relevant contract 7(insert number) days prior to the date set for receipt of proposals. Failure to submit early proposal information will not result in offeror disqualification. (The team needs to decide whether late submittal of the past performance volume will or will not result in offeror disqualification. If it will result in disqualification, clearly state in any cover letter that submission of the past performance volume will be subject to the late proposal rule. See Zebra Technologies International, LLC, B-296158, Jun 24, 2005.)

L-7.3 RELEVANT CONTRACTS

Submit information in accordance with Attachment 1: Past Performance Information on five (5) recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort. To be recent, the effort must either be ongoing on or any part of the contract performance must have been performed during the past five (5) years from the date of issuance of this solicitation. Also include information on five (5) 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 Section M, provision M-2.02 - Evaluation Factors, paragraph M-4.0 - Past Performance Factor.

L-7.3.1 SPECIFIC CONTENT

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a 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 sub-factors and Cost/Price factor used to evaluate the proposal.

L-7.3.2 ORGANIZATIONAL STRUCTURE CHANGE HISTORY

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

L-8.0 Volume III – cost/price

Offerors shall complete the Total Evaluated Price (TEP), identified in Attachment 2 Template L-1. Offeror shall use Attachment 2 Template L-2 to show how Burdened Labor Rates (BLR) are calculated.

Cost/Price data shall not be presented in the oral presentations.

Although this IDIQ is not considered an A&AS or a services contract, labor is anticipated on future DOs to provide a final product. The labor categories and hours provided in Attachment 2 Template L-1 represent several of the anticipated labor categories/needs that shall commonly be required under this IDIQ.

Burdened rates for their respective labor categories, identified in Attachment 2 Template L-1, shall be considered the ceiling rates for performance during the first 12 months of the IDIQ.

Attachment 2 Template L-1 reflects potential representative list of labor categories that may apply to future DOs.

L-8.1 Cost/Price Reasonableness

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. Offers shall be sufficiently detailed to demonstrate their reasonableness.

L-8.1.1 Price Data Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All data relating to the proposed price, including all required supporting documentation, shall 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.

L-8.1.2 Cost or Pricing Data Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. If required, 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.

All dollar amounts provided shall be rounded to the nearest dollar. All burdened labor rates shall be rounded to the nearest penny. (This is requested as a separate attachment so that it can be provided to the technical team for cost realism and technical evaluation purposes.)

L-9.0 Model Contract/Representations and Certifications

This contract is an Indefinite Delivery, Indefinite Quantity contract with baseline clauses/stipulations. The specific prices, contract type(s), delivery and performance shall be determined at the DO level. As such, certain areas within the model contract shall not reflect initial data.

L- 9.1 SOLICITATION/Contract format

Table L-9.1, shown below, reflects the Uniform Contract Format.

Table L- 9.1

No notes.

L- 9.2 Exceptions to OFFEROR 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 shall 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 L-9.2.

L- 9.3 Other Information Required

a. 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. (Additionally, you may want to ask for the name, title, and telephone number of the CEO, Division President, and/or Vice President, etc. The SSA may request these in order to contact his/her counterparts when notifying the successful and unsuccessful offerors of the award decision.)

b. Government Offices: Provide the name, mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, DCMA Administrating Contracting Officer, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

c. 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 shall 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.

L- 10.0 Minimum Delivery Order

The Government minimum order value for each award contract is $1,000.

Attachment 1 Past Performance

A2.1. General.

Each Offeror will submit present and past performance information for itself and for each proposed subcontractor, teaming contractor, and/or joint venture partner. Offerors are notified that the Government will use the data provided, that is determined to be recent and relevant to the effort at hand and data obtained from other sources, in the development of performance confidence assessments. The Government will evaluate the quality and extent of each offeror's performance deemed relevant to the requirements of this RFP. The evaluation of past performance information will take into account past performance information regarding predecessor companies, key personnel who have relevant experience, or subcontractors that will perform major or critical aspects of the requirement when such information is relevant to the instant acquisition. The following subparagraphs identify page counts, where applicable, toward the 30-page limit for the offeror‘s past performance proposal.

A2.2. Administrative Data Sheet (Section L, Attachment 1, Template L-1) for Offeror’s Relevant Past Performance for CIMTIC IV for Each Contract or Delivery Order

Offerors should complete Section L, Attachment 1, Template L-1, not to exceed one page for each recent and relevant contract or task order submitted for evaluation in determining the Performance Confidence Assessment.

Provide at least one (1) recent and relevant, but no more than ten (10) contracts or delivery orders of the offeror and at least one (1), but no more than five (5), relevant contracts or delivery orders from subcontractors or teaming partners performed for Federal agencies and commercial customers (for each Attachment 1, Template L-1 submission there should be a corresponding Attachment 1, Template L-2 submission).

Note: For the purposes of evaluation, delivery orders belonging to one contract shall not be counted in the aggregate, but shall stand alone and each contract and each delivery order shall be counted as “one” submission.

A2.3. Offeror’s Relevant Past Performance for CIMTIC IV for Each Contract or Delivery Order

Offeror should complete Section L, Attachment 1, Template L-2, not to exceed two pages, for each recent and relevant contract or delivery order submitted for evaluation in determining the Performance Confidence Assessment. Explain how and why you consider the examples provided are recent and relevant. Offerors should include a discussion of any significant achievements and explain any past performance problems that they consider relevant to the proposed efforts. Offerors should also discuss past and present efforts to identify and manage program risk. Categorize this information into the specific Technical Proposal Subfactors as it applies to recent and relevant past performance. The Technical Proposal Subfactors are defined in (TA-1) and (TA-2). This information should include data on efforts performed by other divisions, corporate management, subcontractors, or teaming contractors, only if such resources will be brought to bear or significantly influence the performance of the proposed effort. The Government will utilize the information in Attachment 1, Template L-2 to determine which of the contract or delivery orders will be considered in making the past performance evaluation.

A2.4. Summary of Offeror’s Relevant Past Performance for CIMTIC IV Offeror should complete a single Summary of the offeror’s relevant past performance for the CIMTIC IV (Section L, Attachment 1 Template L-3), not to exceed two pages, that rolls up and summarizes all Attachment 1,…