Attach_13_FAR_52.212-1_18JUN19.docx

HQ0147-19-R-0006

Attachment 13 – FAR 52.212-1 Instructions to Offerors, Commercial Items

HQ0147-19-R-0006

Instructions to Offerors, Commercial Items

TEAMS

Visual Information and Production Center

18 June 2019

Table of Contents

FAR 52.212-1: Instructions to Offerors – Commercial Items (Oct 2018) (Tailored)

1.0 GENERAL INSTRUCTIONS TO OFFERORS

1.1 The proposal instructions in this section are designed to assist offerors in preparing a complete response that reflects a full understanding of the approach proposed to accomplish all contractual requirements. Attachment 14, FAR 52.212-2 details how proposals will be evaluated.

1.2 Offerors are expected to comply with all requirements of the Request for Proposal (RFP). The term “Subcontractor” is defined as any tier subcontractor or Inter-Company Work Transfer Agreements (IWTAs). Team Members are the entities that make up a joint venture or any other partnership or teaming arrangement that is formed for the purpose of responding to this solicitation. All forms of joint ventures are acceptable for TEAMS. Industry should review FAR subpart 9.6, FAR part 19, and 13 CFR part 121 for information on joint ventures. The responsibility for ensuring that any joint venture meets the Small Business Administration (SBA) requirements to be classified as a Small Business rests with the offeror. Teaming agreements should be provided with a joint venture’s proposal.

1.3 The Procuring Contracting Officer (PCO) is the primary point of contact for this acquisition. Address any questions or concerns you may have to the PCO. The Contract Specialist is the secondary point of contact. Written requests for exchanges of information may be sent to the PCO via email. Email is the preferred method for exchanges of information. The PCO for this acquisition is as follows:

Joshua B. Kachelman

MISSILE DEFENSE AGENCY (MDA)

CONTRACTS DIRECTORATE - MDA/CTS

5222 Martin Road Redstone Arsenal, AL 35898-0001

(256) 450-0343 Email: joshua.kachelman@mda.mil

The secondary point of contact is as follows:

Jonathan Wood

MISSILE DEFENSE AGENCY (MDA)

CONTRACTS DIRECTORATE - MDA/CTS

5222 Martin Road Redstone Arsenal, AL 35898-0001

(256) 450-0458 Email: jonathan.wood@mda.mil

1.4 Non-Governmental personnel from the contractors identified below:

The Government may release submitted proposal data to non-Government advisors for review, analysis, and evaluation. The following firms may assist in the proposal evaluation process in an advisory capacity. The Government may also employ administrative and engineering support services contractors in the handling of solicitation documentation for purposes of security and document control. All such personnel will be required to execute a statement to preserve and protect from disclosure any source selection and contractor proprietary information disclosed to them during the course of these evaluations. It is anticipated that the following firms will be involved in the source selection process:

Manage the Isolated Local Area Network (ISOLAN) during source selection.

LinTech Global, Inc.

31600 W 13 Mile Rd, Ste 122 Farmington Hills, MI 48334-1407 Attn: Michael Linn

(248) 553-8033 mlin@lintechglobal.com

Manage FEDSELECT© source selection evaluation database:

CACI, Inc.

14370 Newbrook Drive Chantilly, VA 20151-4206 Attn: Jim King

(703) 434-5193 jtking@caci.com

Provide Source Selection Advisory Assistance:

Kepler Research 13663 Office Place Suite 202 Woodbridge, VA 22192 Attn: Dudley Wireman 703-465-4035 dudley.wireman@keplerreserach.com

These support Contractor advisors are subject to contractual OCI restrictions and 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 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.

Objections to disclosure of proposals, or specific portions, to the non-Government advisors listed above must be provided in writing to the Contracting Officer within five (5) business days of solicitation issuance. If no objections are submitted, the offeror(s) must enter into a non-disclosure agreement with the non-government advisor(s), or with the company employing the non-government advisor before the non-government advisor(s) are given access to the offeror(s) proprietary or source selection information. The fully executed NDAs must be submitted NLT 10 days prior to the proposal submission. They can be sent to joshua.kachelman@mda.mil and jonathan.wood@mda.mil.

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.

1.5 Notice Regarding Organizational Conflict of Interest (OCI) – Determination to Participate in This Acquisition

a. The acquisition of advisory and assistance services under this solicitation may create actual or potential conflicts of interest for offerors and their prospective subcontractors. In assessing and addressing conflicts of interest, MDA will follow the guidance in FAR subpart 9.5. Offerors are responsible for ensuring that both they and their proposed subcontractors are not restricted from participating in any acquisition under the TEAMS areas due to an OCI caused by any MDA-funded contract or subcontract; Ballistic Missile Defense System (BMDS)-related contract or subcontract; or, other significant, non-BMDS related business relationships with firms doing business with or in support of MDA.

b. MDA has developed an OCI memorandum with respect to the acquisition of advisory and assistance services (52.212-1, TAB 13j – TEAMS OCI Memorandum).

c. Certain capability areas under TEAMS contracts present heightened concern to the Government with respect to OCI. These contracts are outlined in the TEAMS OCI Memorandum at TAB 13j. Offerors shall consider these areas carefully and fully evaluate potential OCIs. The Government will analyze potential OCIs within these and other areas of concern on a case-by-case basis.

d. Procedures to follow before submission of proposals:

1) Offerors should carefully review the TEAMS OCI Memorandum and OCI clause to ensure their proposals and teaming arrangements are consistent with the TEAMS OCI Memorandum. Questions and clarifications regarding the policy should be provided to the Contracting Officer. The Contracting Officer will meet with offerors on a one-on-one basis, if requested and as necessary, to discuss individual offeror or team arrangements concerning the OCI policy.

2) Offerors will submit the completed OCI Disclosure Form and supporting documentation before the proposal due dates as PDF documents via electronic mail to joshua.kachelman@mda.mil and jonathan.wood@mda.mil. This submission will not count against any proposal page limitation. Based on MDA’s review of the submitted documentation, the Contracting Officer will provide preliminary, written advisory approval to participate in this acquisition. This advisory approval will not be binding on MDA. If the form and supporting documentation are not submitted earlier, they must be included as part of the offeror’s proposal submission.

3) The submission shall also identify all actual or potential conflicts of interest that might occur under the TEAMS areas, and shall specify in adequate detail for the Government’s evaluation, the nature of the conflict and the measures the contractor has taken or proposes to take to avoid, mitigate, or neutralize (hereafter referred to as “mitigate”) such conflicts.

e. Procedures to Follow With Proposal Submission:

1) Each offeror must submit, for itself and its subcontractors, an "OCI Disclosure Form" (dated Jan 2015), Tab 13E, and applicable supporting documents. The submission shall identify all of the 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 Contracting Officer; a description of the work performed or being performed; and, such additional information as the Contracting Officer may request to assist in the identification of actual or potential OCIs. An offeror that has already submitted the OCI Disclosure Form(s) to the Contracting Officer and received an OCI advisory letter does not have to re-submit the forms with its proposal. If changes have been made, the offeror must submit the changes with its proposal.

2) An offeror’s failure to provide adequate information to avoid or mitigate an OCI may cause its proposal to be rejected 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).

3) The offeror must submit a Mitigation Plan, as part of Volume I Tab 5, which addresses all conflicts in adequate detail for the PCO to determine whether an OCI exists or has been mitigated. 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 proposal, and does not need to submit an OCI Mitigation Plan with its proposal. However, to facilitate resolution of OCIs during contract evaluations, offerors are encouraged to submit an OCI Mitigation Plan with their proposals. The OCI Mitigation Plan shall specifically address the OCI disclosures required in this section and explain how the prime is in full compliance with the TEAMS OCI policy. As part of its Mitigation Plan, the offeror must identify which contracts or subcontracts 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. The OCI Mitigation Plan will be reviewed in conjunction with the PCO’s Responsibility Determination prior to award and will be a Section J attachment at award.

f. MDA Engineering Team – Industry (MET-I) (formerly MDA National Team (MDNT)) Participation: Based on the relevant MET-I confidentiality documents and FAR subpart 9.5:

1) MET-I Participants will be restricted from all TEAMS pre-contract award activity, including, but not limited to, marketing activities, IR&D planning in support of TEAMS, bid/no-bid decisions, and proposal preparation activities - including Red-Team participation.

2) After award of a TEAMS contract, MET-I Participants may work for a TEAMS contract awardee, including direct or indirect involvement with any subsequently competed TEAMS contracts, so long as they are not continuing to also work as a MET-I Participant. Former MET-I Participants have a continuing duty to protect proprietary information acquired under the MET-I program and to refrain from any non-MET-I use of such information without permission of the owner.

3) The term "MET-I Participant" means those individuals who are assigned by their MET-I employer to work on the MET-I and, by reason of this assignment, will have access to the proprietary information of others or information that could provide its employer an unfair competitive advantage.

g. The Contracting Officer shall review and determine whether each offeror selected for award has addressed and resolved all OCIs in its OCI Mitigation Plans before making an award. If an OCI is not adequately addressed or mitigated, the Contracting Officer reserves the right to notify the contractor, as is, and allow the contractor a reasonable opportunity to respond before making an award decision. The Contracting Officer reserves the right to reject offers from contractors which do not adequately resolve all OCIs or are inconsistent with the Agency’s OCI policy. The Contracting Officer also reserves the right to obtain an OCI waiver and make an award when in the best interests of the United States.

h. The Government has determined that this acquisition may give rise to a potential organizational conflict of interest. Accordingly, the attention of prospective offerors is invited to FAR subpart 9.5 —Organizational Conflicts of Interest. The nature of this conflict is contractor access to nonpublic information as part of its performance of a Government contract, which may provide the successful offeror (or an affiliate) with an unfair competitive advantage in future procurements. The successful offeror, through performance of the resulting contract, will have access to information not available to other contractors (source selection information or other non-public Government information). This information includes such things as government estimates, government schedules, technical data and other forms of internal government data. Therefore, the successful offeror and its subcontractors shall be ineligible to perform future work for the Missile Defense Agency as a prime or subcontractor (any tier) under any MDA contract other than advisory and assistance services (A&AS). This restriction shall remain in effect until expiration of the resulting contract to avoid unfair competitive advantage or potential bias.

2.0 SOURCE SELECTION METHODOLOGY

2.1 Competitive, Best Value Source Selection

The Government intends to award a full and open, competitive hybrid FFP and cost reimbursement contract under FAR Part 12 using FAR Part 15 procedures. The contract will consist of FFP Labor, Cost ODC, and an option FFP/LOE CLIN; and will have a base period of three years with two, one-year options.

2.2 MDA Intent to Award without Discussions - Offeror’s Best Terms

The Government intends to evaluate proposals and award a contract without discussions with offerors (except clarifications as described in FAR 15.306(a)). Therefore, the offeror’s initial proposal shall contain the offeror’s best terms for Mission Capability, Past Performance, Small Business, and Cost and Price. The Government reserves the right to conduct discussions if the Contracting Officer later determines them to be necessary.

2.3 Competitive Range

If the Contracting Officer determines that discussions are necessary, the PCO will establish a competitive range (as set forth in FAR 15.306(c)) based on the ratings of each proposal against all evaluation criteria. If the PCO determines that an offeror’s proposal should not be included in the competitive range, the proposal will be eliminated from consideration for award and written notice of the decision will be provided to the unsuccessful offeror in accordance with FAR 15.503.

Discussions (if required) may be conducted either orally or in writing. The scope and extent of the discussions are a matter of PCO judgment as set forth in FAR 15.306. Responses from offerors may be required within two business days.

If the PCO determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the PCO may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

2.4 Final Proposal Revisions (FPR)

If discussions are deemed necessary with offeror(s), upon completion of those discussions, the PCO will request that the offeror provide a FPR.

The offeror is advised that any changes to the proposal in the FPR shall be fully addressed and/or explained and reflected in the proposed price. Failure to comply with this requirement can adversely influence the evaluation of the proposal. The PCO will establish a common due date, time, and instructions for submission of the FPR.

If FPRs are requested, any revisions or non-compliance with contract terms and conditions submitted in the FPR 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) but is intended to preclude any misunderstandings by the Government (that could result if new or revised terms and conditions submitted in the FPR have not been fully disclosed, discussed, and understood during discussions or negotiations). Thus, such new or revised terms and conditions are not solicited and, if submitted in the FPR, may render the offer unacceptable to the Government.

2.5 Pre/Post Award Debriefing

Pre/Post award debriefings will be conducted IAW FAR 15.505 and 15.506, respectively.

2.6 Errors/Omissions

If an offeror believes that the requirements in these instructions contain an error, omission, ambiguities, or are otherwise unsound, the offeror shall immediately notify the PCO in writing with supporting rationale no later than five business days after release of this solicitation.

2.7 Mistakes

Mistakes in an offeror’s proposal discovered after award shall be handled IAW FAR 14.407-4 as referenced in FAR 15.508.

2.8 Evaluation Notices (ENs)

Should the Government need to conduct written exchanges with offerors, they will be in the form of an evaluation notice (EN). Page format and limitations will be placed on responses to ENs in the event they are issued. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. The ENs may be sent electronically (i.e., via e-mail) at the discretion of the contracting officer. Offerors must submit their responses by the time and date specified in the letter.

2.9 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) 1449. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to FedBizOpps. If such amendments require material changes, the proposal due date may be extended at the discretion of the PCO 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 written acknowledgement of any solicitation amendments issued by the Government.

2.10 Offerors’ Documents

The Offerors’ Library contains representative products and reference documents provided to assist in the development of offerors’ proposals. Access to the documents will be provided through FBO.gov. Offerors will need to request access the Offeror's Library by submitting an email request to joshua.kachelman@mda.mil. The subject line of the email shall state: "VIPC HQ014719R0006 Offeror's Library," and the emails must include the following information:

Company Name:

Company/Division Address:

CAGE Code:

DUNS Number:

Defense Security Service (DSS) Industrial Security Representative:

Company Point of Contact: (name and phone number)

The Government will verify the company information identified above in the System for Award Management website (www.sam.gov). Firms without a CAGE Code and DUNS number will not be provided access to the Offeror's Library (Attachment 13L).

The Government, while trying to ensure document applicability and currency, does not warrant the accuracy or compliance of the information contained in the Offerors’ Library. All documents are subject to revision and changes without further notice.

All documents will be unclassified/For Official Use Only (FOUO). A table identifying annual historical hours by stakeholder for the VIPC requirement is provided at Tab 13G. This information was compiled based on historical contract performance for work similar in scope to that contained in this Request for Proposal. Offerors are cautioned that this information is historical in nature and should not be used as the sole basis for proposing the effort required to accomplish the requirements of this solicitation. Product tables for the VIPC requirement are provided at Attachment 1a.

3.0 PROPOSAL CONTENT

3.1 Proposal Acceptability

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 consents and agrees to all solicitation requirements and identified constraints. 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. Non-conformance includes, but not limited to, failure to submit all volumes described in Table L-1 in electronic format including all the information requested for each volume by these instructions.

3.2 The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation by the Government and for substantiating the validity of stated claims. The proposal shall provide convincing rationale to address how the offeror intends to meet the areas to be evaluated. Proposals shall not simply rephrase or restate the Government's performance work statement requirements nor restate applicable laws, policy, or regulations.

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 demonstrate that the offeror possesses the technical expertise and management experience to perform all requirements of the PWS. Alternate proposals – defined herein as proposals that deviate in any way from the solicitation terms and conditions and/or the stated performance requirement – will not be considered.

Contingent proposals are not allowed, nor will they be accepted, considered or evaluated by the Government. Contingent proposals are defined herein as proposals that include terms or conditions that imply that performance is contingent upon any sort of provisioning from the Government that is not set forth in the RFP.

The offeror’s proposal shall include all of the information requested and shall comply fully with these Attachment 13, FAR 52.212-1 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.

3.3 Offerors are advised that the Government may incorporate into the final contract enhancing features included in the offeror’s proposal deemed beneficial to the Government. With the exception of the Cost and Price Volume and the Small Business Volume, no cost or pricing information should appear in any other volume. The Government advises offerors that taking exception to or deviating from any term or condition of the RFP may make an offer unacceptable and the offeror ineligible for award.

3.4 All offerors’ proposals shall be valid at least 180 days after the RFP closing date. The offeror shall make a clear statement in the Executive Summary that the proposal is valid at least 180 days from the proposal due date. NOTE: IF THE PROPOSAL IS NOT RECEIVED BY THE DUE DATE/TIME SPECIFIED, THE OFFEROR’S PROPOSAL IS CONSIDERED LATE IN ACCORDANCE WITH FAR 52.215-1.

4.0 PROPOSAL ORGANIZATION

4.1 In presenting material in the proposal, the offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the offeror to present enough information to allow the various technical and management approaches, as well as price, to be meaningfully evaluated without discussions. The offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

4.2 The offeror shall prepare the proposal as set forth in the Proposal Organization Table L-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 L-1. The hard copy 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 Proposal Organization paragraphs as noted in the table below.

4.3 Each proposal volume shall be unclassified. Each volume shall be written in Standard English and be complete in and of itself.

The offeror shall provide a Proposal Cross Reference Matrix as set forth in Table L-2. This proposal matrix is only a tool to assist in the proposal evaluation process.

4.4 Table L-1 shall serve as the offeror’s guide for proposal organization and content by volume.

Table L-1: Proposal Organization and Content

Tab 1: Master Table of Contents

Tab 2: Model Contract

Tab 3: Solicitation Exceptions Matrix

Tab 4: Ground Rules and Assumptions

Tab 5: OCI Mitigation Plan

Tab 1: Executive Summary Content

Tab 2: Proposal Cross Reference Matrix unlimited

Tab 1: Technical Approach

Tab 2: Program Management

Tab 3: Graphic Product Samples***

N/A

Tab 4: Sample Motion Media/Video***

N/A

Tab 1: List of Subs and Joint Ventures (JVs)

Tab 2: Past Performance Information (PPI)

Tab 3: Past Performance Questionnaire

Tab 4: Consent Letter unlimited

Tab 5: Client Authorization Letter unlimited

* SUBMIT EACH VOLUME ON A SEPARATE DVD-R.

** Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. These limitations shall apply to both electronic and hard copy proposals. Each page shall be counted except the following:

1. Volume Cover Pages

2. Table of Contents

3. List of Tables and Figures

4. Glossaries / Acronym List

5. Tabs/ Dividers

6. Blank pages

***This is not required in the hard copy proposal, but is required in the electronic copies of the proposal.

4.5 Page size shall be 8.5 x 11 inches, not including foldouts. Except for the reproduced sections of the solicitation document and any non-narrative sections (e.g., tables, graphs, charts, figures, etc.), the text size shall be no less than Microsoft Word Times New Roman 12 point font, single-spaced. Use at least 1-inch margins on the top and bottom and 1-inch side margins. Pages shall be numbered sequentially by volume. In the event the offeror creates an ambiguity, the Government may exercise its own discretion in counting pages. If the page count is exceeded, the excess pages will not be read or considered in the evaluation of the proposal. 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 (i.e., CD & tape) will not be accepted.

4.6 The Government may need to conduct exchanges with offerors which will be in the form of an EN. Page format and specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. ENs may be sent electronically (i.e., via email) at the discretion of the Government. The EN will request an email response, and offerors must submit their responses by the time and date specified in the letter.

4.7 Foldout pages may only be used for large tables, charts, graphs, diagrams and schematics. Foldout pages may not be used for pages of text. Legible tables, charts, graphs, diagrams, schematics and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and shall not exceed 11 x 17 inches in size. Each printed side of a foldout will count as two pages. For tables, charts, graphs and figures, the font shall be no smaller than 10 point. 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.

4.8 Each volume shall contain a glossary of all abbreviations and acronyms used for the entire proposal, with an explanation for each. Glossaries do not count against the page limitations for their respective volumes.

4.9 Each volume shall contain detailed table of contents to delineate the subparagraphs within that volume. A Master Table of Contents, contained in Volume I, shall contain a consolidation of the individual Table of Contents for all Volumes (I through VI) - See Section 5.1.

4.10 Tab indexing shall be used to identify sections within each volume. The offeror shall index the sections identified in the volume organization outlined in each volume. Tabs do not count against the page limitations for these respective volumes.

4.11 Tables and figures can be used to illustrate quantitative or qualitative data. Tables and figures are not required. If provided, each volume shall contain a list of all tables and figures within that volume. The List of Tables and Figures will not count against the page limitations for their respective volumes. Tables, graphs, charts, and figures are considered non-narrative sections of the proposal and are only to be provided to enhance the proposal narrative. If, at the PCO’s discretion, an excessive amount of narrative is included in a table, chart, graphic, or illustration in an effort to subvert the proposal’s page limitations, the text may be severed from the non-narrative section and included in the page count of the narrative section of the proposal.

4.12 Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Each response to each subfactor shall be self-contained.

4.13 All copies (hard copy and electronic copies) of an offeror’s proposal must be submitted together in accordance with the scheduled submission date for the particular volumes. All prime and team member information must be incorporated into one coherent submittal. Be sure to identify appropriate markings such as the legend at FAR 52.215-1(e), Restriction on disclosure and use of data.

4.14 The hard copy of each volume shall be formatted as follows:

4.15 A cover sheet shall be inserted on the front of each Volume, clearly marked with volume number, offeror’s name, solicitation title, and solicitation number.

4.16 A label should be placed in the spine of each binder clearly identifying the solicitation number, volume number and name, and offeror’s name.

4.17 Complete electronic volumes shall be submitted in Microsoft Office 2010 or compatible format. Offerors are permitted to submit documents such as signed letters (i.e., OCI, Consent and Client Authorization Letters), ORCA and embedded graphics (if applicable) in .pdf format, with the exception of pricing. Pricing spreadsheets (Excel Price Workbook (EPW)) should be submitted using MS Excel 2007 or compatible. If files contain links, the links must be intact and maintained through all revisions. Electronic copies shall not be password protected. All electronic copies shall be submitted on DVD-R in a protective sleeve. The DVD-R and protective sleeve 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 shall contain a Microsoft Word file with the Master Table of Contents for that directory. Offerors shall ensure electronic copies on DVD-R are virus free. If there are disagreements between the paper copy and the electronic copy, the electronic copy shall take precedence.

4.18 Sound or video files shall not be embedded into the proposal files.

4.19 All proposals shall be submitted to the following address:

MISSILE DEFENSE AGENCY (MDA)

ATTN: Joshua Kachelman, MDA/CTS MDA Source Selection Facility 5222 Martin Road Redstone Arsenal, AL 35898-0001

If hand delivering proposals, call Joshua Kachelman, PCO, at (256) 450-0343 to schedule a date and time.

5.0 VOLUME I: CONTRACT DOCUMENTATION

5.1 The offeror shall include a master table of contents of the entire proposal (include in Contract Documentation only). See Section 4.9 and Table L-1: Proposal Organization and Content.

5.2 Model Contract (SF-1449)

The offeror shall provide a complete copy of this RFP (including Attachment 13, FAR 52.212-1 and Attachment 14, FAR 52.212-2, less other attachments, with any amendments) with the original signature of an official authorized to contractually bind the offeror in Block 30 of the SF-1449. The offeror must complete the following sections within the RFP:

· SF-1449, Block 17 Offerors shall populate the price for FFP CLINs on the SF-1449 Continuation Sheet. Offerors shall complete representations, certifications, acknowledgments and statements via the System for Award Management (SAM) at https://www.sam.gov.

NOTE: Offerors shall verify that “reps and certs” are also contained in SAM to ensure that all “reps and certs” completed and submitted via SAM correspond with those included in the solicitation. For example, the solicitation may contain new cybersecurity clauses that are not available in SAM. In such cases, offerors shall complete the applicable “reps and certs” included in the solicitation and submit with their proposal.

5.3 Solicitation Exceptions Matrix

The offeror is required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements. The offeror must clearly identify any exceptions to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall refer to a 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 to document any exceptions to, or deviations from, any of the clauses or special contract requirements along with justification. However, any exceptions which fail to comply with the terms and conditions of the solicitation may result in the offeror being removed from consideration for award.

5.4 Ground Rules and Assumptions

The offeror must clearly identify any ground rules and assumptions made in preparing the proposal.

5.5 OCI Mitigation Plan

The offeror must submit an OCI Mitigation Plan, unless one is not required, as detailed in paragraph 1.5 (e).

6.0 VOLUME II: EXECUTIVE SUMMARY

6.1 The Executive Summary shall include company information and a summary of the offeror’s proposal. This portion may be utilized by the evaluation team to support its evaluation of each factor. However, any summary material presented here shall not be considered as meeting the solicitation requirements for any portions of other volumes of the proposal.

Company Information: The offeror shall provide the Company/Division Address, Identifying Codes, and Applicable Designations, company/division's street address, county and facility code, CAGE code, DUNS code, and size of business (large or small). The offeror shall also provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, Defense Contract Audit Agency (DCAA), and Government Paying Office including the name, telephone and fax number for the Administrative Contracting Officer (ACO). The offeror shall provide a single point of contact and one alternate for all matters dealing with their proposal including name, position title, address, phone, fax number and email address. In addition, the offeror shall provide the name and contact information for their Facility Security Officer that is responsible for managing the offeror’s facility and personnel clearance actions.

Proposal Summary: The offeror shall provide a top-level summary of its proposal suitable for describing its approach to Agency senior leadership.

6.2 Proposal Cross Reference Matrix: The offeror shall provide a matrix using the format below (Table L-2) to cross reference its proposal to, at a minimum, the PWS; Attachment 13, FAR 52.212-1; and Attachment 14, FAR 52.212-2. The offeror’s proposal paragraph number and format shall mirror Attachment 13, FAR 52.212-1 and Attachment 14, FAR 52.212-2 paragraph numbering to the maximum extent practicable. The offeror shall populate and include additional columns as it sees fit to accommodate a more efficient evaluation.

TABLE L-2: Proposal Cross Reference Matrix Format

PO #2 (Paragraph 3.2) PO #3 (Paragraph 3.3) PO #4 (Paragraph 3.4) Paragraph 7.1 Technical Approach (Subfactor 1) Paragraph 4.1 Technical Approach (Subfactor 1)

PO #1 (Paragraph 3.1) PO #5 (Paragraph 3.5)

Paragraph 7.2 Program Mgmt (Subfactor 2)

Paragraph 4.2 Program Mgmt (Subfactor 2)

Paragraph 8.0 Factor 2:

Paragraph 5.0

Paragraph 9.0 Factor 3:

Paragraph 6.0

Paragraph 10.0 Factor 4:

Paragraph 7.0

7.0 VOLUME III: FACTOR 1 MISSION CAPABILITY

The Offeror’s Mission Capability volume will consist of the following subfactor sections.

Mission Capability Subfactor 1 (MCS1): Technical Approach Mission Capability Subfactor 2 (MCS2): Program Management

MCS1: Technical Approach

· Vision Information, Design & Production: Performance Objective #2

· Motion Media Services: Performance Objective #3

· Documentary Flight Test Support: Performance Objective #4

MCS2: Program Management

· Delivery of Support services for MDA: Performance Objective #1

· VIPC Operations Administration: Performance Objective #5

7.1 Subfactor MCS1: Technical Approach

The offeror will be required to perform all PWS requirements. However, for proposal evaluation purposes, the offeror (inclusive of team members such as prime/subcontractor, joint venture, etc.) shall propose its approach to the following three Performance Objectives to include skill mix as set forth in Tab13M; specifically Tab 13M shall summarize proposed staffing for a 12-month period by inputting proposed labor hours by labor category for each of the PWS paragraphs (not just the PWS paragraphs for the three Performance Objectives below). There is a separate tab for each of the three regional locations. Attachment 1c Labor Competencies is provided to describe the labor categories present in the Tab 13M Staffing Approach to assist in its completion:

Performance Objective #2: Visual Information Design and Production

The offeror’s proposal shall demonstrate an approach to, and understanding of, providing graphic design services as described in PWS 3.2.1.

The offeror’s proposal shall demonstrate an approach to, and understanding of, management of high speed digital print services and production, as identified in PWS 3.2.2, utilizing the hardware listed in PWS 3.1.5.c., including:

· High speed print coordination/scheduling/job cueing

· Quality control checking

· Efficient production steps utilizing digital color press printing methodology

· File preparation

· Efficient use of dedicated front-end raster image processors (RIPs)

· Document finishing configuration (automatic punching, binding, folding, etc.).

The offeror’s proposal shall include 5-10 digital product samples for each of the graphic products identified below (total not greater than 10 per product type for a grand total not greater than 40 total samples), originally created by the offeror (labeled as Volume III Tab 3), to demonstrate its technical capability:

· Logos

· Posters

· Large format graphics (display or wall graphics)

· Program/booklet or brochures

The offeror’s product sample submissions should demonstrate its technical capability to provide the following:

· Highly refined finished products;

· Original artwork;

· Inventive/imaginative ideas and concepts;

· Use of color, creative typography, and layout balance.

The sample content can be based on any subject matter relative to the offeror's experience/business area. The samples must be submitted under Tab 3 of Volume III. The digital copies shall not exceed 30MB per sample. Any sample that exceeds the limitations will not be evaluated.

See additional details provided in the historical hours and information located in 52.212-1, TAB 13G, as well as the VIPC Product Sample Book in the Offerors’ Library.

Performance Objective #3: Motion Media Services: Video Support, Design and Production, Photography; Animation and Modeling; Audio Visual Support

The offeror’s proposal shall demonstrate an approach to, and understanding of, providing motion media services as described in PWS 3.3.1, paragraphs a through g.

The offeror’s proposal shall demonstrate an approach to, and understanding of, providing dedicated A/V support (Unclassified and Classified) to execute requirements as described in PWS 3.3.4.

The offeror’s proposal shall include a product sample Motion Media/Video product originally created by the offeror (labeled as Volume III, Tab 4). The demonstration video may focus on any topic or subject matter the offeror chooses. The product shall be a short demonstration reel, as follows:

· High definition video in MOV or MP4 format;

· 3-5 minutes in length;

· Incorporating elements of live video, graphical elements, animation of models and elements in a 3-D environment with audio and narration.

The offeror’s sample motion media/video product submission should show the extent to which proposed product sample demonstrates the offeror’s technical ability to provide:

· High production value;

· Professional creative editing and transitions;

· Shot composition and subject lighting;

· Attention to high resolution layout and design;

· Detail/fidelity in 3-D models with texturing and/or articulation, animated with realistic lighting/shadowing, high quality effects, accurate background topology and environmental effects;

· Effective use of audio/effects, music selection, quality of sound editing

· Professional voice quality and integration with video elements.

The Motion Media/Video product sample content can be based on any subject matter relative to the offeror's experience/business area and must be submitted as Tab 4 to Volume III. However, the content shall only be provided as part of the two electronic copies. Any portion of a sample that exceeds the limitations will not be evaluated.

Performance Objective #4: Documentary Flight Test Support

The offeror’s proposal shall demonstrate an approach and understanding of coordinating and executing ancillary photo and video support for a documentary flight test as described in PWS 3.4.

7.2 Subfactor MCS2: Program Management

The offeror will be required to perform all PWS requirements. However, for proposal evaluation purposes, the offeror (inclusive of team members such as prime/subcontractor, joint venture, etc.) shall propose its approach to the following two Performance Objectives:

Performance Objective #1: Delivery of Support Services for MDA

The offeror shall submit a Program Management Plan (CDRL A007) detailing its approach and understanding for Delivery of Support Services for MDA as described in PWS 3.1.6 (paragraphs b-f) and CDRL A007.

The offeror shall complete Tab 13M Staffing Approach summarizing the proposed staffing for a 12-month period. Attachment 1c Labor Competencies is provided to describe the labor categories present in the Tab 13M Staffing Approach to assist in its completion.

Performance Objective #5: VIPC Operations Administration

The offeror’s proposal shall demonstrate an approach to, and understanding of, oversight and management of the high-speed digital video editing systems and SAN storage system as described in PWS 3.5.4.

8.0 VOLUME IV: FACTOR 2 PAST PERFORMANCE

8.1 The offeror shall submit a complete list of all subcontractors and joint ventures with this volume. Past Performance Information (PPI) (52.212-1, Tab 13A) should be submitted only for the prime contractor and major subcontractors expected to perform aspects of the effort the offeror considers critical to the overall successful performance. As stated in 1.2, “Subcontractor” is defined as any tier subcontractor or Inter-Company Work Transfer Agreement (IWTA). Team Members are the entities that make up a joint venture or any other partnership or teaming arrangement that is formed for the purpose of responding to this solicitation. PPI can reflect experience at either the Prime contractor or subcontractor level. Offerors must demonstrate how the offeror’s and subcontractors’ past performance meets the relevancy definition in Attachment 14 52.212-2 Table M-7. This information is to assist the evaluators in determining relevancy of past performance submitted for the evaluation by confirming the roles of the team members compared to the scope of the contract(s) submitted for evaluation. In demonstrating relevancy, the offeror’s PPI submissions should focus on the following:

· Relevant experience in management of personnel and resources in geographically dispersed locations;

· Relevant experience in visual information production and professional quality graphic design requirements;

· Relevant experience in Motion Media (MM) requirements;

· Relevant experience in providing ancillary professional-quality documentary (photography and HD video) support

· Relevant experience in providing enterprise-wide operations administration for requirements similar to VIPC.

8.2 Past Performance Information (PPI), (52.212-1, TAB 13A): A maximum of five PPIs may be submitted for the entire team. The team consists of the Prime offeror, its proposed subcontractors and/or joint ventures.

8.3 Past Performance Questionnaire (PPQ) (52.212-1, TAB 13B): The offeror is responsible for, not later than 10 days prior to proposal due date, sending 52.212-1, TAB 13B to respondents of its choice who will subsequently submit information to the Government to be received by the proposal due date. The offeror shall provide a list of the proposed respondents with two points of contact, current e-mail address and phone numbers, in its Past Performance Volume. The Government reserves the right to contact these sources if they do not submit responses by the RFP closing date and consider them in making a past performance assessment.

8.4 Even though the evaluation of acceptability of Past Performance is separate and distinct from Determination of Responsibility required by FAR subpart 9.1, past performance information contained herein may be used to support the Determination of Responsibility for the successful offeror. Information provided on the PPQs assists the evaluation team in determining the past performance confidence assessment.

8.5 Consent Letters (52.212-1, TAB 13C): Past performance information concerning subcontractors will not be disclosed to a private party without the subcontractor's consent. Because a Prime offeror is a private party, the Government will need that consent before disclosing subcontractor past performance information to the prime during exchanges. The offeror shall provide a consent letter for each proposed subcontractor using the format provided at 52.212-1, TAB 13C, Consent Letter. This letter allows the release of adverse past performance information on a subcontractor to the offeror so the offeror can respond to such information. The offeror shall provide original consent letters for each subcontractor and/or joint venture partner. Once the consent letter is received, the Government will discuss past performance only with the offeror under review. If the offeror fails to submit consent letters with the proposal, the Government will only be able to notify the offeror that it has discovered adverse past performance information for one of its subcontractors, but that it cannot disclose or discuss the adverse past performance.

8.6 Client Authorization Letters (52.212-1, TAB 13D): Each offeror, subcontractor, and/or joint venture shall execute a Client Authorization Letter for commercial customers authorizing release to the Government of requested information on their respective performance using the format provided at 52.212-1, TAB 13D, Client Authorization Letter. The offeror shall provide original client authorization letters for the offeror and each subcontractor and/or joint venture.