Attachment 3 Section L.docx

Section L – 29 June 2011 – Rev 8

Clear/Cod Radar Section L:

Instructions, Conditions, and Notices to Offerors for

HQ0147-11-R-0002

Table of Contents

L-07.4

L-01 POINT OF CONTACT

Point of Contact The PCO is the sole point of contact for this acquisition. Address any questions or concerns to the PCO. Written requests for clarification shall be sent to the PCO via an e-mail. E-mail is the preferred method of communication. The PCO for this acquisition is as follows:

Ms. Carol C. Rivard Missile Defense Agency (MDA) Contracts Directorate – MDA/DACX Building 5222, Martin Road Redstone Arsenal, AL

(256) 450-1474 E-mail: carol.rivard@MDA.MIL

USE OF CONTRACTOR SUPPORT SERVICES

Non-Government Advisors MDA may release proposal data submitted to non-Government advisors for review, analysis, and evaluation. The non-Government advisors are:

CACI Dynamic Systems, Inc.

6700 Odyssey Dr. NW Huntsville, AL 35806 Kepler Research Inc.

1530 Wilson Blvd, Suite 600 Arlington, VA 22209

The MITRE Corp.

202 Burlington Road Bedford, MA 01730 Defense Acquisition, Inc.

658-B Discovery Drive Huntsville, AL 35806

These support Contractor advisors are expressly prohibited from competing on this acquisition in any fashion, i.e., being a prime, subcontractor, or teaming partner. Contractor personnel supporting this acquisition have signed Non-Disclosure Agreements (NDAs) and are subject to Organizational Conflict of Issue (OCI) restrictions. Individuals will be authorized access only to those portions of the proposal data and discussions that are necessary for them to perform their respective duties.

Submission of your proposal to this solicitation is considered consent to the government’s use of non-government advisors

Objections to disclosure of proposals, or specific portions, to the non-Government advisors listed above must be provided in writing to the PCO within five (5) business days of solicitation issuance. If no objections are submitted, the Government will consider this as Offeror concurrence with the Government’s use of non-Government advisors.

Your written objections must include a detailed statement of the basis for your objection and identify specific portions of the proposal you object to disclose to non-Government, Contractor advisors.

SOURCE SELECTION METHODOLOGY

Competitive, Best Value Source Selection The Government contemplates the competitive award of contract with options resulting from this solicitation. The proposal instructions in this section are designed to assist Offerors in preparing a complete response that reflects a full understanding of the proposed approach to accomplish all contractual requirements. Section M provides further detail as to how the proposals will be evaluated.

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 factors or subfactors to be eligible for award. By submission of its offer, the Offeror accedes to all solicitation requirements and identified constraints.

Offeror’s Best Terms The Offeror’s initial proposal shall contain the Offeror’s best terms for technical, management, past performance, and cost/price. The Government may conduct discussions with Offerors in the competitive range in accordance with (IAW) FAR 15.306(c). If the Government contemplates award without discussions, the Offerors may be given the opportunity IAW FAR 15.306, to clarify certain aspects of their proposals (e.g., the relevance of an Offeror’s past performance information and adverse past performance information to which the Offeror has not previously had an opportunity to respond) or to resolve minor or clerical errors.

The Government reserves the right to consider as acceptable, only those proposals submitted in accordance with all instructions set forth or referenced in this solicitation. A proposal that omits material elements required of the solicitation may be omitted from further consideration. Failure to comply with the requirements of laws and regulations set forth or referenced in the solicitation may affect eligibility for award.

Final Proposal Revisions Once discussions have been concluded with Offeror(s) determined to be in the competitive range, if conducted, the PCO will request that the Offeror provide a Final Proposal Revision (FPR). The Offeror is advised that any changes to the proposal in the FPR must be fully addressed and/or explained and reflected in the proposed cost/price. Failure to comply with this requirement can adversely influence the evaluation of the proposal. The PCO will establish a common due date and time for submission of the FPR.

When final proposal revisions are requested, any revisions or non-concurrence with contract terms and conditions submitted in the final proposal revision may not be subject to further discussion or negotiation and may render the offer unacceptable to the Government. This provision is not intended to restrict the Offeror’s opportunity to revise figures, e.g., prices, discounts, or percentage rates. Rather, it is intended to preclude any misunderstandings by the Government, which could result if new or revised terms and conditions are submitted in the final proposal revision that have not been fully disclosed, discussed, and understood during discussions or negotiations. Hence, such new or revised terms and conditions are not solicited and, if submitted in the final proposal revision, may render the offer unacceptable to the Government.

Post Award Debriefing An unsuccessful Offeror will have three (3) business days from the date of Government notice of contract award to submit a written request for a post-award debriefing IAW FAR 15.506. An unsuccessful Offeror who fails to submit a timely request will not be entitled to a debriefing. IAW FAR 15.506, the PCO may elect to conduct the debriefing orally, in writing, or any other acceptable method. An Offeror will receive no more than one (1) debriefing.

Errors/Omissions 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 no later than five (5) business days after release of this solicitation. Also, the Offeror shall give written notification to the PCO of ambiguities in the solicitation no later than five (5) business days after the release of this solicitation.

Mistakes Mistakes in an Offeror’s proposal shall be handled IAW FAR 14.407-4 as referenced in FAR 15.508.

Request for Proposal (RFP) Revisions/Amendments The Government reserves the right to revise or amend any portion of this solicitation. Such revisions or amendments will be available on the FedBizOpps website at https://www.fbo.gov/ using Standard Form (SF) 33. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the websites for this solicitation. The Government, while trying to ensure document applicability and currency, does not warrant the accuracy or compliance of the information contained in the library’s documents. All documents are subject to revision and changes without further notice. If such amendments require material changes, the proposal due date may be extended at the discretion of the CO and by enough days to enable an Offeror to revise its proposal. In such cases, the amendment will include an announcement of the new proposal due date and time. The Offeror shall provide acknowledgement in Block 14 of the SF 33 of any solicitation amendments issued by the Government.

Offeror’s Library All regulations, manuals, or other publications, referenced in the RFP are either publicly accessible or available via the offeror’s library. Companies requesting access to the Offeror’s Library must comply with the handling and destruction requirements documented on the request form. No pick-up service or physical location is available to review the documents contained in the Offeror's Library.

PROPOSAL PREPARATION INSTRUCTIONS

Classification and Presentation Each proposal volume shall be unclassified. Each volume shall be written in Standard English and be complete in itself (e.g. the Government will evaluate technical capabilities IAW Section M based solely on information in the Technical Volume. Do not include Technical information in other volumes unless they are required to support evaluation of the relevant Section M factor/subfactor for that volume).

Legible tables, charts, graphs, and figures should be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. Large drawings, tables, or charts shall be separately provided and will not be included in the overall page count. Large drawings, tables, or charts shall be used only if necessary for clarity or legibility. For tables, charts, graphs and figures, the text shall be no smaller than 10 point. These limitations shall apply to both electronic and paper proposals.

Completeness The Offeror's proposal shall include all data and information requested and shall be submitted IAW these instructions. Non-conformance with the instructions provided may result in an unfavorable proposal evaluation, or rejection of an Offeror’s proposal, rendering it ineligible for award.

The Offeror’s proposal shall be clear, concise, and include sufficient detail for effective evaluation by the Government and for substantiation 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 areas to be evaluated. Offerors shall assume that the Government has no prior knowledge of their experience and will base its evaluation on the information presented in the Offeror's proposal. The Offeror’s proposal shall respond to all factors and subfactors. The Offeror’s proposal shall demonstrate that the Offeror possesses the technical expertise, experience, and program management capability to plan, organize, and deliver the Clear/Cod Upgrade in a coordinated, technically competent fashion that is timely and cost efficient. Innovative management, technical, and business approaches to improve efficiencies and reduce costs are encouraged; but will not constitute an alternate proposal. An alternate proposal is when a proposal provided departs or deviates from the stated requirements and/or the terms and conditions of the solicitation. Contingent or alternate proposals are not allowed, nor will they be accepted, considered or evaluated by the Government. The Offeror’s proposal shall include all of the information requested and must comply fully with these Section L instructions. Failure to do so may cause the Offeror’s proposal to be eliminated from consideration for award. Offerors are reminded to properly mark their proposal documents which contain proprietary or restricted information.

Due Date Proposals are due at the location specified in _______(TBD)__________ on ______(TBD)___________, by 1600 hours (Eastern Standard Time). It is anticipated that the proposals will be delivered to Hanscom Air Force Base.

All Offerors’ proposal(s) shall be valid at least 240 days after the due date. The Offeror shall make a clear statement in Volume I, Tab 1: Cover Letter (ref. L-07.1) that its proposal is valid until the applicable date as referenced above.

NOTE IF A PROPOSAL IS NOT RECEIVED BY THE DUE DATE/TIME SPECIFIED, THE OFFEROR’S PROPOSAL IS CONSIDERED LATE IN ACCORDANCE WITH FAR 52.215-1.

Organization Page Limits Proposal page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. When both sides of a sheet display printed material, it shall be counted as two pages. These limitations shall apply to both electronic and hardcopy proposals. Hardcopy proposals shall be separately bound in three-ring, loose-leaf binders.

Page size shall be 8.5 x 11 inches, not including foldouts. Pages shall be single-spaced and use at least 1-inch margins on all sides of each page. Pages shall be numbered sequentially by volume. Page limitations apply to electronic proposals, as well. If there are discrepancies in page counts and/or content between hard copy and electronic volumes, the hardcopy version shall be used for evaluation (e.g., if the hard copy version of a volume is 51 pages, and the electronic version of the same volume is 48 pages, the Government will treat the volume as having 51 pages). Special considerations will not be given for colors, pictures, or unnecessary graphics. Other than the electronic media solicited, audio and video recordings, or any other electronic media will not be accepted.

Page Limit Exemptions Each page shall be counted except the following:

Volume Cover Pages Table of Contents List of Tables and Figures Glossaries (Definitions, Abbreviations, and Acronyms) Tabs Dividers Blank Pages Online Representations and Certifications Applications (ORCA) information Proposal Matrix Consent Letters Subcontracting Reports for Individual Contracts in the Past Performance Volume DD Form 1423-1 Contract Data Requirements List (CDRL) OCI Disclosure Forms Page Size Page size shall be 8.5 x 11 inches, not including foldouts. Except for the reproduced sections of the solicitation document, the text size shall be no less than Microsoft Word (2007 or compatible format) Times New Roman 12 point font.

Hardcopy foldout pages may be used for diagrams or illustrations; paper size shall not exceed 11 x 17 inches, and; font size for diagrams or illustrations shall be no smaller than 10 point using Microsoft Word Times New Roman. Each printed side of a foldout will count as two pages. Exhibits shall be legible; font shall be no smaller than 10 point using Microsoft Word (2007 or compatible format) Times New Roman. All information (except documentation numbers, classification markings, and page numbers) shall be contained within an image area of 9 x 15 inches. Foldout pages shall fold so that the Government can read and evaluate them without removal from the proposal binder. Foldout pages shall fold entirely within the volume.

Volume Organization and Structure The Offeror shall prepare the proposal as set forth in Table L-05-1, Volume Organization, below. The title and contents of the volumes are defined in this table, all of which shall be within the required page limits, and with the specified number and type of copies. The volumes identified in the table should be separately bound in three-ring, loose-leaf binders. The contents of each proposal volume are described in the proposal organization paragraphs as noted in the table below. The table below (Table L-05-1) shall serve as the Offeror’s guide for proposal organization and content by volume.

Signed

DVD

Due Date

VOLUME I EXECUTIVE SUMMARY

Tab 7: Reserved

VOLUME II TECHNICAL/MANAGEMENT

VOLUME III PAST PERFORMANCE

VOLUME IV COST/PRICE

Table L-04 Volume Organization *Each volume shall be submitted on a separate CD/DVD.

Evaluation Notice The Government may need to conduct exchanges with Offerors which will be in the form of an Evaluation Notice (EN) issued by the PCO. Page limits, format limitations, and submittal timelines will be levied on responses to ENs in the event ENs are issued. ENs may be sent electronically via email at the discretion of the Government. The ENs typically will request an email or a paper response; but may request both and/or CD/DVD responses.

Glossary Each volume shall contain a glossary of all specialized terms, abbreviations, and acronyms used for the entire proposal, with an explanation for each.

Table of Contents Each volume shall contain a detailed table of contents (with hyperlinks in the electronic version) to delineate the subparagraphs within that volume.

The table of contents shall contain a detailed List of Tables, Figures, and/or Exhibits (with hyperlinks in the electronic version) to identify Tables, Figures, and/or Exhibits within that volume.

The Master Table of Contents contained in Volume I shall be a consolidation of the individual table of contents for all Volumes (I through IV).

Volume Segregation Cross-referencing between Volumes is not allowed. Each Volume shall be written on a standalone basis so that its contents may be evaluated without cross-referencing to other Volumes of the proposal.

Indexing/Tabs Tab indexing shall be used to identify sections within each Volume. The Offeror shall index the sections as identified in Table L-05-1, Volume Organization, outlined in each Volume. Tabs do not count against the page limitations for their respective Volumes.

PROPOSAL COPIES & ADDRESSES

Proposal Package Requirements All copies (hardcopy and electronic copy) of an Offeror’s proposal shall be submitted together IAW the scheduled submission date. All Prime and teammate/subcontractor information shall be incorporated into one (1) coherent submittal at the location specified in ________(TBD)_________ on _______(TBD)___________, by 1600 hours (Eastern Standard Time). Ensure appropriate markings such as the legend at FAR 52.215-1(e), Restriction on disclosure and use of data.

Hardcopy One hardcopy of each volume shall be clearly identified as original. The original shall be formatted as follows:

Each volume shall have a cover sheet, clearly marked as volume number, “ORIGINAL”, Offeror’s name, solicitation title, and solicitation number.

The original shall be unbound and contain original signatures.

Proposals shall be addressed to the PCO.

Each hardcopy volume of the proposal, with the exception of the original, should be separately bound in a three-ring loose-leaf binder, which shall permit the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked to indicate volume number, copy number, Offeror’s name, solicitation title, and solicitation number [reference FAR 52.215-1(c)(2)].

The front cover of each binder shall clearly identify volume number, copy number, Offeror’s name, Offeror’s address, solicitation title, and solicitation number. The spine of each binder shall clearly identify volume number, copy number, Offeror’s name, solicitation title, and solicitation number.

Electronic Copies Complete electronic volumes shall be submitted in Microsoft Office 2007 format, readable by Microsoft (MS) Word, MS Excel, MS Power Point, MS Project and/or Adobe Acrobat (.pdf). Offerors shall not use pivot tables. Electronic files contained on the CD/DVD shall not be read/write/password protected. Regarding the use of MS Excel, all formulas and hidden columns shall be viewable by the Government. All electronic copies shall be submitted on a read-only CD/DVD in a protector (sleeve or jewel box). Place as much documentation onto one CD/DVD as possible to limit the number of disks received. Each CD/DVD and protector shall be clearly marked as to volume number, Offeror’s name, solicitation title, and solicitation number. Electronic file directory titles and organization shall reflect the titles and organization of these instructions. Each directory (with hyperlinks in the electronic version) shall contain a Master Table of Contents for that Volume. Offerors shall ensure electronic copies on CD/DVD are virus free. Electronic versions of the proposal shall be an exact duplicate of the original hardcopy proposal. Page format restrictions and limitations apply. Sound or video (e.g., MPEG) files shall not be embedded into the proposal files. The Government requests the Past Performance Volume be submitted to the PCO fifteen (15) days prior to the date set for receipt of proposals. Failure to submit the Past Performance Volume early will not result in Offeror receiving an unfavorable evaluation.

If discrepancies are identified between the electronic proposal and the original hardcopy proposal, the original hardcopy proposal shall prevail.

Cost/Price CD/DVD requirements: Files contained on the Volume IV Cost/Price CD/DVD shall not be password protected. Electronic links are only permissible within the Cost/Price Volume. If files contain links, the links shall be intact and maintained through all revisions.

Proposal Delivery Address Proposals shall be submitted to the following address:

Missile Defense Agency ATTN: Ms. Carol Rivard/MDA/DACX MDA Source Selection Facility (TBD in the Hanscom AFB local area) c/o MDA Source Selection Support Team, RFP HQ0147-11-R-0002

All hand carried proposals shall be coordinated with the PCO no later than 24 hours in advance of the proposal due date.

VOLUME I - EXECUTIVE SUMMARY

TAB 1: Cover Letter The Executive Summary volume shall contain a cover letter that includes, but is not limited to proposal validity period (reference L-05.3) and all information referenced in FAR 52.215-1(c)(2).

The Offeror is required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. By submission of its offer, the Offeror accedes to all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements.

The Offeror shall provide a statement in the cover letter specifying the extent of agreement with all terms, conditions and provisions included in the solicitation and shall state all exceptions taken or asserted.

TAB 2: POC List For the prime Offeror and each teammate/subcontractor, a two-page summary shall be provided that identifies the following:

Company/Division Mailing Address Commercial and Government Entity (CAGE) code Data Universal Numbering System (DUNS) code Tax Identification Number (TIN) Size of business (large or small) and NAICS Labor surplus area designation Congressional district of parent company Primary and alternate point of contact for all matters concerning their proposal (i.e. including name, position title, address, phone, and e-mail address) Cognizant Defense Contract Management Agency (DCMA), Defense Contract Audit Agency (DCAA), and Government Paying Office points of contact (i.e. including name, facility code, position title, mailing address, telephone number, and e-mail address).

Cognizant Security Office TAB 3: Summary Information The Offeror shall provide a concise narrative of the entire proposal, including significant risks, and a highlight of any key or unique features, excluding cost/price. The content of Volume I is for information only and will not be evaluated for the purpose of contract award. The format of this volume is at the discretion of the Offeror, but should specifically indicate where material may be found for each major element of the evaluation as defined in Section M of this Request For Proposal (RFP). The salient features should tie in with Section M evaluation factors/sub-factors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal. Within this volume, the Offeror shall state that its proposal is valid for 240 days. The Executive Summary shall also identify all subcontractors and joint venture partners. A brief description of their planned roles in the effort shall be included. A list of all participating divisions and locations (prime, subcontractors, and joint venture partners) shall be furnished indicating whether teaming agreements have been executed or not. An organization chart of the proposed UEWR team shall be provided to show all key personnel (Offeror, subcontractors, joint venture partners, etc.) and depict how the Offeror’s team fits within the company. The organization chart shall start at the level of the Offeror’s Chief Executive Officer and clearly identify the entire chain of command specifying the name, title, and division name and location. The reporting lines and names, title, and division name and location of personnel responsible for quality assurance shall also be included. Phone numbers for points of contact including the Division’s Vice President, program manager, program manager alternate, and contracting officer shall be provided. The contact list should also identify those personnel authorized to negotiate on behalf of their company. Furthermore, the list should indicate the person to contact in the event the Offeror is awarded a contract (provide, at a minimum, contact’s title, phone number, fax number, and mailing address). Material presented here shall not be considered as meeting the requirements for any portion of other volumes of the proposal.

TAB 4: Master Table of Contents This tab shall contain a master table of contents (with hyperlinks in the electronic version) of the entire proposal.

TAB 5: Proposal Cross Reference Matrix The Offeror shall provide a Proposal Cross Reference Matrix as set forth in Table L-07.1, Proposal Master Cross Reference Matrix, to cross reference the proposal to, at a minimum, the Contract Statement of Work (SOW), the Contract Work Breakdown Structure (CWBS); and Sections L & M. Offerors may amend the proposal matrix provided. This proposal matrix is only a tool to assist in the proposal evaluation process. The Offeror is ultimately responsible for ensuring all areas are addressed fully and all requested information is completed and turned in appropriately IAW the solicitation.

Table L-07.1 Proposal Master Cross Reference Matrix

TAB 6: Solicitation/Contract Form (SF33) Sections A-K, DD 254 The Offeror shall complete and provide within this tab Section A- Solicitation/Contract Form blocks 13, 14, 15A, 15B, 15C, 16, 17, 18, and schedule B. The facilities capital cost of money shall not include an allocation of fee. Signature by the Offeror on the Standard Form 33 constitutes an offer, which the Government may accept. The "original" copy should be clearly marked under separate cover.

The Offeror shall also complete and provide within this tab all other Request for Proposal (RFP) sections and documents requiring fill-ins not identified to be provided in other tabs to include: Section K, Representations, Certifications, and Other Statements of Offerors; RFP Amendment(s); Contract Security Classification Specification DD Form 254, and; any and all exceptions to or deviations from the terms and conditions of the RFP from either the prime or the subcontractors.

TAB 7: Reserved TAB 8: ORCA Information Offerors shall complete representations, certifications, acknowledgements and statements via the Online Representations and Certifications Application (ORCA) (http://orca.bpn.gov). A copy of the Offeror’s ORCA data sheet print-out shall be provided in this tab.

TAB 9: Organizational Conflict of Interest (OCI) Plan NOTICE REGARDING ORGANIZATIONAL CONFLICT OF INTEREST (OCI) AGREEMENT(S) (Federal Acquisition Regulation [FAR] 9.5)

Responsibility lies with the prime contract Offerors to ensure that both the prime and its proposed subcontractors are not restricted from participating in this proposed acquisition due to an OCI clause in any Federal Government contract, including, but not limited to, MDA contracts.

An Offeror who has signed, as well as proposed subcontractors who have signed, a contract with an OCI agreement, as either a prime Contractor or subcontractor under any such contract, shall submit a written application to obtain approval to participate in this acquisition to the MDA Directorate of Contracting, Sensors, via e-mail to the PCO at CLEARCompetition@MDA.MIL.

Further, if either the prime Offeror (or any of its proposed subcontractors) is currently performing (or in the process of proposing on) an effort that appears to have a potential conflict with the upcoming Clear/Cod UEWR, regardless of whether there is an OCI clause or not, the prospective prime Contractor shall submit a written application to the MDA Director of Contracting, Sensors, via e-mail to the PCO at CLEARCompetition@MDA.MIL, to obtain approval to participate in this acquisition.

The Offeror(s) with either of the potential OCI restrictions, described in the paragraphs above, shall provide the following Plan:

Offerors shall submit an OCI Plan that addresses, at a minimum, internal processes and procedures for identification, disclosure, evaluation and resolution of potential, real and apparent, OCI and Personal Conflicts of Interest (PCI); provides a plan to track actual and potential OCIs, and; protects non-public information and proprietary data, including that to which the Government will have access to during operations. Offerors shall describe their OCI training and oversight programs, and the Offeror’s procedures for complying with FAR 9.5, DFAR 209.5, and the OCI clause at Section H-09 of this solicitation. The plan shall also address mitigation efforts to include firewalls, separate corporate divisions, separate reporting chains and similar measures to ensure proprietary and nonpublic information is properly used and safeguarded consistent with the OCI clause at Section H-09 of this solicitation.

If an Offeror determines that an actual or potential OCI does not exist, it shall include a statement to that effect as part of its OCI Plan. The OCI Plan shall specifically address the OCI Disclosures required in this Section (L-07.9.2) and explain how the prime is in full compliance with the agency's OCI policy. As part of its OCI Plan, the Offeror shall identify which contracts, subcontracts, or task orders it will continue to support and those it intends to terminate or allow to lapse to eliminate any conflicts. The plan shall also address other OCI resolution and mitigation measures to include the divestment of business units.

An Offeror’s failure to provide adequate information to avoid or mitigate an OCI may cause its proposal to be rejected by the PCO and relieves the Government of any further responsibility to resolve OCI issues. See FAR 9.504(e). Notices to Offerors of OCIs and their responses thereto are not negotiations or discussions as those terms are used in FAR 15.306(d). The PCO also reserves the right to obtain an OCI waiver and make an award when in the best interests of the Government.

This Tab of the Offeror’s proposal shall also include OCI Disclosure Forms (see Section L, Attachment L-1). The submission shall identify all of its team's MDA-funded contracts or subcontracts; BMDS-related contracts or subcontracts; and any significant, non-BMDS related business relationships with firms doing business with or in support of MDA. For each identified contract, the Offeror shall disclose the contract number; name, and telephone number of the CO; a description of the work performed or being performed; and such additional information as the PCO may request to assist in the identification of actual or potential OCIs. OCI Disclosure Forms shall not be counted against page limitations.

The Offeror shall ensure that it complies with paragraph d(1), Representations and Disclosures, of the OCI clause in Section H-09 of this solicitation, and provides the required disclosures in this tab.

The successful Offeror’s OCI Plan will be incorporated into the contract at contract award.

TAB 10: Small Business Subcontracting Plan

The Offeror shall submit a Small Business Subcontracting Plan IAW FAR 52.219-9 including information required in paragraphs (d) (1) through (d) (11) of that clause. The Small Business Subcontracting Plan must be determined to be acceptable by the PCO in order for the Offeror to be eligible for contract award.

MDA Supplemental Subcontracting Reporting Requirements (Oct 2009) In addition to the content requirements specified in 52.219-9, plans shall include the following:

a. Percentage goals expressed in terms of total contract value.

b. Individual descriptions and dollar amounts of the planned use of Alaska Native Corporations, Indian tribes, Historically Black Colleges and Universities/Minority Institutes, and Ability One (formerly Javits-Wagner-O‘Day) organizations that are included in the small disadvantaged business and small business goals/dollars proposed.

c. A statement that block 15 of the Individual Subcontract Report and Summary Subcontract Report will contain the email addresses of both the CO and the Missile Defense Agency Office of Small Business Programs (subcontracting-oversight@mda.mil).

d. A description of the process the prime Offeror will use to ensure timely and accurate small business subcontract reporting in the Electronic Subcontracting Reporting System (eSRS) for all tiers of subcontracting.

e. A description of the specific initiatives and tools (e.g. mentor protégé program) that will be employed under the contract to enhance small business utilization and capabilities both in the instant acquisition and to meet future requirements to be supported by the BMDS small business industrial base. Some areas of importance to MDA include:

(1) Expanding the pool of qualified small businesses to reap the benefits of increased competition for production of components and piece parts in MDA acquired systems.

(2) Engaging small businesses to serve as second sources in order to mitigate the risks of single point failures in the supply chain and increase the quality of supplies or services.

(3) Leveraging investments in the MDA SBIR/Small Business Technology Transfer programs to transition appropriate technologies into operational or planned systems.

The successful Offeror’s Small Business Subcontracting Plan will be incorporated into the contract at contract award.

Note: The Government's assessment of small business participation under the management factor is separate from the Federal Acquisition Regulation (FAR) requirement for PCO review and acceptance of an Offeror's Small Business Subcontracting Plan.

VOLUME II - TECHNICAL/MANAGEMENT VOLUME (Factor 2/3) General The Technical Approach and Management Approach factors will be addressed in Volume II. This should address the Offeror’s proposed approach to meeting the requirements of each factor and sub-factor, as well as risk mitigation in the Offeror’s proposed approach in terms of technical capability, cost trade-offs and/or schedule. This volume should be specific and complete. Legibility, clarity and coherence are very important. The Offeror’s responses will be evaluated against the factors and sub-factors defined in the Evaluation Factors for Award. Using the instructions provided below, provide, as specifically as possible, the actual methodology the Offeror will use to accomplish/satisfy these factors and sub-factors. All the requirements specified in the RFP are mandatory. By the Offeror’s proposal submission, the Offeror is representing that the Offeror will perform all the requirements specified in the RFP. It is not necessary or desirable for the Offeror to tell the Government so in the proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the RFP.

Technical (Factor) Technical Sub-factor 1: Signal Processor and Data Processor (SPDP) Describe your proposed design approach highlighting any differences from the Government provided design and describe the rationale that supports your proposed design changes. Describe the technical benefits of the proposed design along with an assessment of the sustainability of that design. Describe your plan to meet the UEWR requirements. Provide a cross reference from the UEWR system requirements to applicable paragraphs of your proposed design approach using the Cross-Reference Matrix. Describe your approach for providing the required scalability in your design, and your ability to accelerate the design and implementation schedule.

Technical Sub-factor: Radar Software Describe your software development approach and provide insight into what software development will be required for the Upgraded Early Warning Radar. Describe your software quality and Management processes and any certifications you have achieved (e.g., ISO 9001, CMMI Maturity or Capability ratings). Describe your Integrated Development Environment approach and processes. Explain how the processes will be structured and implemented to develop, integrate, and sustain UEWR software capabilities under this contract. Describe how flexible these processes are to evolving operational needs, differences between particular site baselines, and inevitable technical changes.

Technical Sub-factor 3: Information Assurance (IA) Describe your approach for meeting all requirements of the DoD Information Assurance Certification and Accreditation Process (DIACAP) and how you will ensure success in obtaining an Authority to Operate/Authority to Connect (ATO/ATC) from the AF Designated Approval Authority (DAA) (AFSPC/A6) and MDA/DOC for the UEWR. Also, discuss your approach for maintaining and sustaining the IA posture for hardware, software and firmware changes in accordance with DIACAP 8510.01 for a classified system. Describe your corporate depth and breadth of experience, as well as, that of your personnel who will be involved in the DIACAP Process.

Describe the major test challenges specific to your design and how your test strategies (technical and organizational) will accelerate successful testing. Specifically address any foreseen Information Assurance (IA) or EWR/UEWR test challenges. Describe any relevant documented lessons learned, best practices or creative strategies that are planned to be applied to this program.

Technical Sub-factor 4: Hardware Obsolescence Redesign Describe your design approach for hardware and obsolescence redesign highlighting technical maturity of the proposed design along with an assessment of the sustainability of that design. Describe your plan to meet the UEWR requirements and your strategy to reduce the impact and frequency of performing COTS obsolescence upgrades. Describe the ability of the hardware solutions to be form/fit/function replacements allowing for retrofit of their design into the Beale/Fylingdales/Thule UEWRs without the need for significant re-engineering or sustaining engineering costs.

Technical Sub-factor 5: Scalability and Growth Capacity Describe how your overall technical approach (hardware and software) is scalable and flexible to accommodate future growth but also remain consistent with the architecture currently in place at the Beale, Fylingdales, and Thule UEWRs. The scalability and flexibility of the design should allow for the future addition of new mission requirements without the need for a substantive redesign or re-architecting effort.

MANAGEMENT (Factor 2) General The Offeror shall describe the maturity and integration of their proposed processes. Where standard processes are proposed, the Offeror shall clearly indicate any process tailoring that has been performed for the Clear/Cod UEWR program. The Offeror’s description shall pay particular attention to how the proposed processes will support Government review and configuration processes and milestones. The Offeror shall clearly describe how their processes will ensure that the design and development efforts maximize coordination with the Government.

Management Sub-factor 1: Systems Engineering Describe your Systems Engineering processes and any certifications you have achieved (e.g., ISO 9001, CMMI Maturity or Capability ratings). Explain how the processes will be implemented to develop, integrate, and sustain UEWR capabilities under this contract. Describe how flexible the processes are to evolving operational needs, differences between particular site baselines, and inevitable technical changes. Describe how any subcontractors performing on this contract will provide consistent process application and performance.

Management Sub-factor 2: Program Management Describe your Program management Process. Explain how the process will be implemented to manage the development, integration, and sustainment of the UEWR capabilities under this contract. Describe how flexible the processes are to evolving operational needs, differences between particular site baselines, and inevitable technical changes. Describe how any subcontractors performing on this contract will provide consistent process application and performance.

Provide a staffing plan that identifies the specific personnel needs for the program in each of the categories of engineering, test, program management, support, and the staffing profile that illustrates when the staffing positions must be filled. Identify all clearance levels required for the positions. Describe the approach to ensure that these positions are appropriately filled with qualified staff in time in order to support all UEWR program requirements and schedules. Specifically address how the Offeror will quickly ramp up with highly qualified staff. Identify areas where teaming is required to bring the right skills to the UEWR effort.

Management Sub-factor 3: Integrated Master Schedule (IMS) Provide an Integrated Master Schedule (IMS) and accompanying narrative that describes all significant program activities that are aligned with the proposed program level staffing profile. Include a time line for completion, in a timely manner, of each activity identified in the proposed program. Provide details that clearly describe the purpose for and importance of key activities. Identify all critical path elements and key dependencies.

Management Sub-factor 4: Sub-Contractor and Associated Contractor Management

Describe your Sub-contractor approach. Explain how you will ensure the flow down of requirements to the various sub-contractors. Describe how you will manage the sub-contracting effort to ensure quality products and timely delivery. Describe your approach at resolving potential schedule conflicts associated with multiple independent contractors engaged in work at CLEAR and COD to include associated contractor agreements coordination/de-confliction capable of avoiding program delays and cost overruns.

Management Sub-factor 5: Small Business Participation & Commitment The Government‘s assessment of small business participation and commitment as measured against the total contract value which is separate from the FAR requirement for PCO review and acceptance of an Offeror‘s Small Business Subcontracting Plan. Large business Offerors shall ensure that individual subcontracting plan submissions are consistent with proposal information associated with this subfactor. All Offerors shall provide the Proposed Participation Dollars and Percent of Estimated Contract Value for the period of performance. Small business participation is small business contributions to contract performance at the prime contract through second tier subcontract levels. Offers shall include a narrative explanation regarding the basis for and efforts associated with establishing proposed participation dollars and percentages including a breakout of prime, first tier, and second tier small business participation.

Small Business Participation Dollars and Percent

Large Business

Total

100%

Note: The above small business participation UEWR targets represent the PCO’s assessment of appropriate minimum participation (prime through the 2nd tier) expressed as a percentage of total contract value. Offerors are encouraged to propose values greater than the targets listed.

Offerors shall identify by name, type of business, product/service, dollar value, timeframe, and nature of commitment the small business participation planned for this acquisition. Offerors shall clearly describe the nature of commitment (e.g., fully executed teaming agreement, planned purchase order). Offers shall describe new, contract specific initiatives and tools (e.g., mentor protégé agreements, developing second sources focused on improving readiness or reducing cost, and leveraging Small Business Innovation Research [SBIR] investments) that will be employed under the contract to enhance small business utilization and capabilities both in the instant acquisition and to meet future BMDS requirements. Offerors shall describe the process they will use to ensure proper flow-down of requirements, process management, and performance assessments of small business utilization at lower tiers.

VOLUME III – PAST PERFORMANCE (Factor 3)

The Offeror shall provide past performance information for evaluation, including metrics on past software development experience (e.g., new software lines of code [SLOC], re-used SLOC, commercial off-the-shelf [COTS] SLOC, EVM, etc.). An Offeror with no past performance experience should submit the appropriate explanation; failure to provide this information may result in the Offeror being removed from consideration for award. In evaluating the Offeror’s past performance record, the Government will use past performance information obtained from various sources known or identified by the Government. The Government reserves the right to contact sources other than those provided by the Offeror to assess past performance. Offerors shall consider recency and relevancy (Section M-05.3) when preparing the Past Performance Volume.

Tab 1: Organizational 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 present or past efforts or between conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult for evaluators to determine what past performance is relevant to the acquisition being evaluated.

The Offeror shall therefore include a roadmap describing changes in the organization of the Offeror and any teaming partners, which includes proposed subcontractors, and/or joint venture partners. As part of this explanation, show how these changes impact the relevance of any efforts identified for past performance evaluation/performance assessment. The roadmap shall be both specifically applicable to the efforts identified and general enough to apply to efforts on which the Government receives information from other sources.