m2P1_Section_L_for_Amend_0002.pdf

Revised per Amendment 0002 dated July 29, 2016

Section L – Instructions to Offerors

L.1.0 Program Title and Objectives

The purpose of this contract is to obtain cloud infrastructure services in DISA data center facilities. These commercially-developed infrastructure services are to be available within DoD networks, implemented as a “private cloud” service deployment, with the single tenant being the DoD community and DoD partners.

This effort is being undertaken to leverage the substantial ongoing and persistent commercial investment into high density multi-tenant computing environments at significantly lower total cost of ownership than traditional DoD efforts. The goal is to improve the on boarding efficiencies for DoD consumers, reduce cost, increase efficiency of computing platforms and increase the IT security posture of the U.S. Government.

The DoD has applications and data distributed across the United States. This deployment will exist within the DoD Wide Area Network (WAN) and will directly connect to the Department of Defense Information Network (DoDIN) Non-Secure

Internet Protocol Router Network (NIPRnet).

The government intends to award a single, firm fixed price ID/IQ contract. Award will be made to the offeror whose proposal represents the best value in accordance with the evaluation criteria defined in Section M, Evaluation Factors for Award. The government reserves the right to make no award at all.

For consideration in developing your proposal, funding will be provided via the issuance of task order. It is anticipated that incremental funding will be utilized in accordance with (IAW) DFARS Clause 252.232-7007. The contract ceiling for the overall contract lifecycle is $498500M.

L.2.0 General Instructions

For the purpose of this solicitation, an offeror is defined as a prime contractor. Only one reference regarding subcontractor experience or past performance will be recognized.

Each offeror, identified by a distinct Commercial and Government Entity (CAGE) code, may submit only one proposal for this RFP.

L.2.1 Use of Non-Government Evaluators. Non-government personnel will not be utilized in the evaluation of proposals, however, an automated source selection software tool (FedSelect), licensed from a non-government source (CACI International Inc.), will be used during the proposal evaluation process. Non-Disclosure Agreements will be furnished for the administration of the software.

L.2.2 Government Furnished Information (GFI). There may be Government

Furnished Information (GFI) at the contract level. There will be no physical library or reading room for this solicitation.

L.2.3 General Proposal Guidance

a. This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The offeror's proposal must include all data and information requested by the RFP and must be submitted in accordance with these instructions. Non-conformance with the instructions provided in this section may result in removal from competition.

b. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of the offeror’s facilities and experience and will base the Government’s evaluation only on the information presented in the offeror's proposal.

c. Elaborate brochures or documentation, detailed art work, or other embellishments are unnecessary and will not be considered part of the proposal, but will be considered part of the page count.

d. The offeror shall make a clear statement in its Volume I cover page that the proposal is valid for a minimum of 365 days from the proposal due date.

e. In accordance with FAR Subpart 4.8 (Government Contract Files), the

Government will retain one digital copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of unsuccessful proposals.

L.2.4 General Information

L.2.4.1 Point of Contact. The Contracting Officer (KO) and the Contract Specialist

(CS) are the only points of contact for this procurement. Address any questions or concerns you may have to the KO and CS. Written requests for clarification must be sent to the KO and CS at the email address located in DARS Clause 52.204-9000, Points of

Contact, of the solicitation.

L.2.4.2 Debriefings. The KO will notify unsuccessful offerors of the source selection decision in accordance with FAR 15.503. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

Excluded offerors are entitled to no more than one debriefing.

L.2.4.3 Discrepancies. If an offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the KO or CS in writing with supporting rationale.

L.2.4.4. Electronic Reference Documents. All referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) web site at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

L.2.4.5 Exchanges of Information

a. Exchanges of source selection information between government and offerors will be controlled by the KO or CS. Evaluation notices and responses will be transmitted as e-mails and will be treated and marked as Source Selection

Sensitive Information. Questions/comments will only be entertained if received in email and only when submitted on Attachment L-1 Questions and Answer

Template in Section L. Questions/comments are due 9:00 am. (CST) on July

18, 2016. Questions submitted after the deadline may not be answered. The email is to be addressed to the KO and CS at the to the following email addresses:

Email Address: debra.l.powell-schaffer.civ@mail.mil

Attn: Debra L. Powell-Schaffer

Contracting Officer

Email Address: lisa.a.odonnell4.civ@mail.mil

Attn: Lisa A. O’Donnell

Contract Specialist

PL8322 (Hardware Section)

2300 East Drive

Scott AFB, IL 62225-5406

Subject Line Reference: RFP HC1028-16-R-0020, Contractor Name, Source

Selection Information See FAR 2.101 and 3.104

b. No information concerning this solicitation or requests for clarification will be provided in response to offeror-initiated telephone calls. All such requests must be made in writing and submitted to the above email address. Written inquiries will be answered in writing and provided to all offerors. However, because of administrative time, written inquiries may not be answered when requests are received by the above addressee after the original due date for receipt of questions as specified in this solicitation. The timeframe for submitting inquiries will not be extended as a result of an extension to the due date for the receipt of offers, unless authorized by the KO.

c. The Government intends to award without discussions. Therefore, the offeror’s initial proposal should contain the offeror’s best approach/terms for technical, http://www.fedbizopps.gov/ management, past performance, and price; however, despite this intent, the government reserves the right to conduct discussions if the Source Selection

Authority (SSA) determines they are necessary. If the SSA determines discussions are necessary, a competitive range will be established. Based on the ratings of each proposal against all evaluation criteria, the contracting officer shall establish a competitive range comprised of all of the most highly rated proposals, unless the range is further reduced for purposes of efficiency pursuant to FAR 15.306(c)(2).

In the event issues pertaining to a proposed contract cannot be resolved to the

SSA's satisfaction, the government reserves the right to withdraw and cancel the solicitation. In such event, offerors will be notified in writing.

L.2.5 Organization/Page Limits

L.2.5.1 Proposal Organization. The offeror shall prepare the proposal as set forth in the

Proposal Organization Table (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 as specified in Table L.1. The contents of each proposal volume are described in applicable paragraphs of Section L as noted in the table below.

Table L.1 Proposal Organization.

VOL.

RFP

PARA #

VOL. TITLE PAGE LIMIT

I L.3 Executive Summary N/A

Cover Page 1 Page

Readme File 1 Page

Table of Contents No Limit

Glossary of Abbreviations and Acronyms No Limit

II L.4 Technical/Management Approach (Factor 1)

Qualifying Criteria 5 pages

Technical/Management Approach (Factor 1)

(to include all subfactors) 45pages

III L.5 Past Performance (Factor 2)

Offeror’s Past Performance Information

Sheets

30 pages (10 pages per past performance effort

(Summary Page not included in page count))

List of Past Performance Questionnaires sent to customers 1 Page

VOL.

RFP

PARA #

VOL. TITLE PAGE LIMIT

IV L.7 Cost/Price (Factor 3)

Price Narrative No Limit

Pricing Spreadsheet; Pricing Proposal No Limit

V L.8 Additional Requirements

Contract Information No Limit

Small Business Participation Commitment

Document (all offerors)/Subcontracting Plan

(Large businesses only)

No Limit

Organizational and Consultant Conflict of

Interest Mitigation Plan No limit

SCRM Plan No limit

DD254, DoD Contract Security Classification

Specification No Limit

Cross Reference Matrix No Limit

L.2.5.2 Page Limitations. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations shall not be circumvented by including inserted text boxes/pop-ups or internet links to additional information; such inclusions are not acceptable and may be cause for elimination of the proposal from consideration. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. The government reserves the right not to consider for award any proposal that does not adhere to the administrative requirements of this solicitation. Each page shall be counted except the following: table of contents, glossaries and blank pages shall not be counted and no information on those pages will be evaluated.

L.2.5.3 Page Size and Format.

a. A page is defined as the material that fits between page breaks in a Microsoft

Office Word document. Pages shall be 8.5 x 11 inches in format size. The font type/text size shall be no smaller than 12-point Times New Roman (no other font variations are acceptable) font for all text. For all tables, charts, graphs and figures included in the proposal, the text shall be no smaller than 10-point Times New

Roman font.

b. The Technical/Management Volume of the proposal is to be submitted as an

Adobe Acrobat, Portable Document Format (PDF) document. The document may not be protected to prevent copying of text. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1 inch margins on the top and bottom and 1-inch side margins. The pages of individual files within each volume shall be numbered sequentially.

c. Legible charts, graphs and figures may be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed a single page in size.

Tables whose total length (number of rows) exceed a single page may be continued by the use of repeating headers. For tables, charts, graphs and figures, the text shall be no smaller than 10-point Times New Roman font.

L2.6 Cost or Pricing Information. All cost or pricing information shall be addressed

ONLY in the Cost/Price Proposal Volume. The KO will review each proposal to ensure cost/price information is not mentioned outside of the Cost/Price Volume.

L2.7 Table of Contents. Each volume, except the Cost/Price Volume IV, shall contain a more detailed table of contents to delineate the subparagraphs within that volume.

L2.8 Glossary of Abbreviations and Acronyms. Volume I shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. Glossaries of

Abbreviations and Acronyms do not count against the page limitations for that volume.

Each Abbreviation and Acronym shall be spelled out in its entirety the first time used.

L.2.9 Proposal Submission

a. To respond to this solicitation, the offeror shall deliver an electronic proposal to https://www.ditco.disa.mil/vendors/ in accordance with the following instructions:

Submitting proposals via the worldwide web: Prior to submitting proposals, the offerors shall be registered in System for Award Management (http://www.sam.gov).

The offeror must also have an External Certification Authority (ECA), located at:

http://iase.disa.mil/pki/eca/. This webpage provides links to approved ECA. To apply for your certificate, select one of the approved ECA vendors and complete the registration. When applying, personnel will be required to verify their identity. If a new

ECA is required, please contact the ECA vendor as soon as possible. The length of acquiring an ECA depends on the vendor approval. **NOTE: A Medium Assurance certificate is the type of certificate required.**

The offeror must also be registered on the DITCO Solicitations and Uploads (formerly

DCOP) web site, at https://www.ditco.disa.mil/vendors/. If the offeror has an existing account (i.e., registered with DITCO for a prior solicitation) it is not necessary to re-register. The offeror may use that existing account to upload this proposal. If the offeror is required to register on the DITCO web site, choose the option for "The solicitation requires vendor registrations for eligibility" during the registration process. The offeror will then be prompted to enter the solicitation number. The solicitation number entered at this point is only used to help DITCO prioritize the order in which to review and https://www.ditco.disa.mil/vendors/ http://www.sam.gov/ http://iase.disa.mil/pki/eca/ approve the registration requests. Upon completion of the on-line registration process, a

DITCO representative will review and approve the registration request before the offeror will be given access to the protected areas of the web site. As soon as the registration has been approved, an email will be sent to the email address of the person who registered.

The email will contain a user id and password that will be needed when uploading proposals. The approval of the registration request usually takes one business day. This registration process allows DITCO to precisely track when proposals are uploaded (or attempted to be uploaded). Offerors are strongly encouraged to register a minimum of two weeks prior to uploading a proposal. Offerors should also attempt to upload their proposal as early as possible to ensure no problems arise at the last minute. A link to the detailed guide for utilizing the website is located on the login pagealso being posted on FedBizOpps with the solicitation package, titled “DITCO Solicitations and

Uploads Reference Document– Vendors.” If you have any problems, contact the DITCO

Customer Service Center at (618) 229-9333.

b. All proposal volumes shall be submitted in Adobe Acrobat, Portable Document

Format (PDF), Version 11.0.16 (or previous versions that are completely compatible); except the Pricing Template, which shall be submitted in MS Excel

2010. Note: There shall be no page markings with restrictive legend prohibiting the copying and pasting of text for government use specific to this acquisition.

Also, no scanned images are permitted with the exception of the signed SF33 cover page (Section A), Sections I and K of the solicitation, and other documents originating from third parties as verification or certification required by the RFP

(e.g. acceptable accounting system verification). The government must be able to copy text.

c. Submit each volume as a separate electronic .zip file with the volume number and the name of the volume from Table L.1. Each individual file within the zip file must be autonomous and complete. Then zip all volumes into a single zip file using the offeror’s legal business name and CAGE code as the file name.

d. Virus Check. Offerors shall perform a virus check prior to proposal submittal and certify they have done so in the proposal’s Cover Page.

e. Use of the software and procedures described in this part will reduce the amount of time and effort needed by the government to receive and install proposals into an electronic evaluation system and will help to ensure that proposals are suitable for reading electronically. Information regarding electronic products listed herein should not be construed as government endorsement for such products.

f. Due Date/Time. The time specified on the SF-33, Block 9, is in Central Standard

Time (CST). Any proposal, modification, or revision that is received at the

DITCO Solicitations and Uploads web site specified in Section L2.9 after the exact time specified for receipt of proposals in Block 9 is “late” and will be handled in accordance with FAR 15.208(b) and subparagraphs thereto.

g. The offeror’s proposal submission will be considered complete when all volumes have been received. Partial proposals will be considered late.

h. The offeror shall prepare a “readme” file, included in Volume I, which describes the organization and layout of the files in its electronic submission. The file shall describe the names of the .zip files and the names of each file included therein.

i. Efforts by the government to clarify or expedite installation of electronic proposal submissions, in accordance with FAR 15.207(c), will not be considered discussions.

L.2.10 Use of Software Tool. The government will access the softcopy versions of the offeror’s proposal using an automated source selection documentation tool.

L.2.11 Classified Information. Offerors shall not submit classified information.

L.2.12 Acceptance of Proposals. The government reserves the following rights:

a. To consider as acceptable only those proposals that are submitted in accordance with all technical requirements stated or referenced in the solicitation, and that demonstrate an understanding of and the ability to perform the government’s requirements.

b. To reject as unacceptable those proposals that delete or alter technical requirements of the solicitation or include terms, conditions, or assumptions that caveat or limit performance.

L.3.0 Volume I – Executive Summary.

a. In the Cover Page, the offeror shall provide the following information:

i. The offeror’s firm name

ii. The solicitation name and number

iii. The name, address, electronic address and telephone and facsimile numbers of the offeror

iv. A statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation and agreement to furnish any or all items upon which prices are offered at the price set forth in the schedule

v. Names, titles, electronic addresses and telephone and facsimile numbers of persons authorized to negotiate on the offeror’s behalf with the government in connection with this solicitation

vi. Name, title, and signature of person authorized to sign the proposal

vii. Proposals signed by an agent shall be accompanied by evidence of that agent’s authority, unless that evidence has been previously furnished to the issuing office

viii. A generic company email address shall be provided for this solicitation and all correspondence or the email addresses of a maximum of two points of contact.

ix. Provide the offeror’s CAGE code; DUNS code; TIN; and business size (large or small) and type(s) of small business, if applicable

x. Confirmation offeror’s proposal is valid for a minimum of 365 days from the proposal due date

xi. Confirmation of virus check

b. Readme file as described in Section L2.9.h.

c. Table of Contents of the entire proposal to include Lists of Tables, Figures, and/or

Drawings.

d. Glossary of Abbreviations and Acronyms

L.4.0 Volume II - Technical/Management Approach (Evaluation Factor 1).

The PWS provides the government’s overall requirements for the duration of the m2P1 contract. Offerors shall submit their Technical/Management Approach as Volume II of the proposal in response to the Technical/Management Factor found in Sections M.2.1, as applicable.

L.4.1 General. The Technical/Management Volume should be specific and complete.

Your responses will be evaluated against the technical/management subfactors defined in

Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation.

It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

L.4.1.1 Qualifying Criteria

All proposals will initially be evaluated to determine whether their proposal is acceptable in meeting the following qualifying criteria requirement. Acceptable/unacceptable criteria are provided in Table M.1.

Include the following table (Table L.2) in the Technical/Management Approach to acknowledge that the proposal meets the qualifying criteria and indicate the section of the proposal where the requirement is addressed and meets the requirement.

Table L.2 Qualifying Criteria

Qualifying Criteria Volume, Section and Page Reference

Offeror to provide certification of a Federal Risk and Authorization Management Program

(FedRAMP) Joint Authorization Board (JAB)

Provisional Authorization (PA) at either the High or

Moderate Systems level. Certification must be current (offeror’s company name is listed on the

FedRAMP website having a JAB PA in IaaS or

PaaS) and in effect at the time of initial Request For

Proposal (RFP) submission.

L.4.2 Content and Organization (Volume II). Please construct and present your responses according to the Proposal Organization discussed above. Ensure your responses address the following:

Volume II - Technical/Management - Factor 1

Subfactor 1: Authority to Operate (ATO)

Subfactor 2: Scalability to Full Operation Capability (FOC)

Subfactor 3: Business Management

L.4.2.1 Technical/Management

In the technical/management volume, address your proposed approach to meeting or exceeding the minimum performance or capability requirements of each technical/management subfactor, as well as, the risks in your proposed approach in terms of technical/performance, cost, and/or schedule. Offerors should discuss how their solution will introduce new technology during the life of the contract. In order to facilitate evaluation, proposals should provide sufficient details as outlined below:

Factor 1, Technical Management

Subfactor 1: The offeror will provide an implementation plan with initial Work

Breakdown Structure (WBS) showcasing the optimal methodology to operationalize the capability. The plan should document timeframes for vendor work to be performed in order to achieve Authority to Operate (ATO) according to PWS section 6.1.14 within 9 months. For example, equipment delivery, configurations, management hardware delivery timeframes, infrastructure software implementation, etc. The offeror will also annotate all known DISA constraints/dependencies.

Highlight how your technical architecture meets or exceeds the key performance parameters (KPPs) and Service Level Agreements (SLAs) outlined in PWS section

6.1.10.1 sub elements 1, 2, 3, and 4:

(1) Identify how your infrastructure will maintain an overall availability for the consumers to a target of 99.500%, expressed as a percentage to 5 significant digits.

(2) Identify how each infrastructure service component will maintain target availability to the Consumers of 99.500%. At a minimum the Contractor will monitor and report on the Compute services, the Object and Block Storage services, the infrastructure service portal, and the provisioning capabilities.

(3) Describe how your solution will provide a Guaranteed IOPS or throughput levels for each tier of storage offered including a minimum 500 IOPS for Tier

1 and 40 sustained IOPS for Tier 2.

(4) Describe how your solution will provide vCPUs with a minimum of 2.0 GHz as the standard performance level

Subfactor 2: The offeror will highlight how their technical architecture supports maintaining KPPs and SLAs, outlined in PWS section 6.1.10.1 sub elements 1, 2, 3 and

4, while the system reaches Final Operational Capability (FOC) within 24 months after

IOC and scales up to and beyond 5,000 workloads.

Subfactor 3: Business Management

The Offeror will highlight how their performance and resource usage tools meets or exceeds the minimum requirement, outlined in PWS section 6.1.11.3 sub elements 1-7:

(1) Describe your role filtered self-management tools to support billing, monitoring, and reporting on service management functions. At a minimum each category must support defined roles limited to specific authorized areas and supporting levels of authority including Read/Write, Read Only, and

Audit functions as appropriate.

(2) Describe how your solution will provide visibility into usage metering using metrics and granularity appropriate to the type of service. At a minimum all billable elements must be individually tracked and reported. Metrics must be current within 24 hours, and must be reported in the same time increments as the metering units.

(3) Describe your solution to provide a suite of reports, dashboards, and alarms to monitor and track operational and infrastructure performance (included but not limited to incidents, service usage, capacity, SLA adherence, etc. . .). At a minimum reports must address the noted areas listed in the previous sentence. Reports must be tailored and access limited to the level or role of the authorized user, including PMO access to all records, and Consumer access limited to the consumer’s area of interest.

(4) Describe your solution to automatic monitoring of resource utilization and other events such as failure of service, degraded service, via service dashboard or other electronic means. The output of this must be near real time and available to the Consumer, PMO, and DISA management based on role and authorization.

(5) Describe how your solution provides Consumers the ability to filter and view usage and invoicing by: DoD organization, DoD program, IT System, IT

System type, and Security Level. At a minimum, these reports must be granular enough to report on all billing elements, and reportable by each bill-payer or consumer, and must be current within 24 hours.

(6) Describe how your solution provides online reporting metrics interface for all resource utilization including metrics such as: current utilization, historical average and peak for a user defined window of time. At a minimum metrics must provide near real-time visibility, and address the performance of virtual servers, and both virtual and physical CPU, Memory and Storage, and be visible to the user based on authorized role.

(7) Describe your life-cycle development and configuration management methodology and timeline for releasing changes to the self-management tools. At a minimum, the methodology must document the response time to emergency changes and bug fixes aligned with the severity levels identified in

PWS section 6.1.10.7. Program changes and updates related to change requests from the government must be addressed within a timeframe based on the size of the change, typically 30 business days for a minor change and 60 business days for a major change.

L.4.2.1.1. Technical/Management Risk

Address technical/management risk by identifying those aspects of the PWS requirements you consider to have the potential for disruption of schedule, increased cost, poor performance, the need for increased government oversight, and/or the likelihood of unsuccessful contract performance. Classify each risk in accordance with the table below.

TABLE L.3 – TECHNICAL RISK RATINGS

Rating Description

Low

Has little potential to cause disruption of schedule, increased cost or degradation of performance. Normal Offeror effort and normal government monitoring will likely be able to overcome any difficulties.

Moderate

Can potentially cause disruption of schedule, increased cost or degradation of performance. Special Offeror emphasis and close government monitoring will likely be able to overcome difficulties.

High

Likely to cause significant disruption of schedule, increased cost or degradation of performance. Extraordinary Offeror emphasis and rigorous government monitoring may be able to overcome difficulties.

Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent the successful accomplishment of other contract requirements (e.g., PWS or specification requirements), whether or not those requirements are identified as subfactors. Propose a realistic “workaround” or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level.

Identify and classify any new risks introduced by such risk mitigation.

L.4.2.2 Volume II Organization

The Technical/Management volume II must be organized according to the following general outline:

(1) Table of Contents

(2) Proposal Format

L.5.0 Volume III – Past Performance (Evaluation Factor 2).

Each offeror shall submit a Past Performance Volume containing past performance information. Offerors are cautioned that the government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

L.5.1 Content and Organization (Volume III). The Past Performance Volume shall be organized as shown in Table L.1. according to the following general outline:

a. Summary Page describing the role of the offeror and/or significant subcontractor that the offeror is require to provide Past Performance

Information Sheets (Ref. Attachment L-2)

a. Subcontracting Consent Letters executed by each significant subcontractor authorizing the release of past performance information so the offeror can respond to such information. A sample consent letter is provided as

Attachment L-5.

b. Client Authorization Letters for each identified effort for a commercial customer authorizing release to the government of requested information on the offeror’s performance. See Attachment L-6.

c.a. Past Performance Information Sheets. See Attachment L-2. (Refer to Table

L.1 for page limitations on past performance information sheets.)

L.5.2 General

Each Offeror must submit a past performance volume with its proposal, containing past performance information (see format in Attachment L-2) in accordance with this section.

This information is required for the offeror and subcontractors who are proposed to perform at least 40% of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance.

Offerors are cautioned that the government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance including government knowledge of the offeror past performance with the agency.

Along with the information required in this paragraph, the offeror must submit a consent letter executed by each subcontractor authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. Consent letters cannot exceed two pages. For each identified effort for a commercial customer, the offeror should also submit a client authorization letter, authorizing release to the government of requested information on the offeror's performance. Client authorization letters cannot exceed more than one page. See Attachments L-5 and L-6 for sample consent and client authorization letters.

L.5.3 Relevant Contracts

Submit information on contracts you consider most relevant in demonstrating your ability to perform the proposed effort using the format contained in Attachment L-2, Past

Performance Information on no more than three (3) recent contracts, including significant subcontractor’s past performance information submissions, that you consider most relevant in demonstrating you and your significant subcontractor’s ability to perform the proposed effort. Include rational supporting your assertion of relevance. See Section M.2.2 for a description of the characteristics or aspects the government will consider in determining recency and relevance. See Table M.5 for the definitions of relevancy and recency.

a. In addition, the prime offeror shall include information on a minimum of one (1) recent contract performed by the prime offeror that you consider most relevant in demonstrating your ability to perform the proposed effort.

b.a. The offeror shall submit past performance information on no more than a total of three (3) contracts/task orders (including past performance information submitted for significant subcontractors). If an offeror submits past performance information for an indefinite delivery contract for any significant subcontractor, then the offeror must identify a specific task order under the indefinite delivery contract.

c.b. Recent contracts are considered to be efforts that the prime offeror and its significant subcontractors have performed with the past three (3) years prior to issuance of this solicitation, or for ongoing efforts, must have been in place at least nine months before the proposal due date.

L.5.3.1 Specific Content

Offerors are required to explain what aspects of the contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This may include a discussion of efforts accomplished by the offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to an unacceptable assessment, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified.

L.5.3.2 Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between conclusion of recent past efforts and this source selection.

As a result, it is sometimes difficult to determine what past performance is relevant to this procurement. To facilitate this relevancy determination, include in this proposal volume a "roadmap" describing all such changes in the organization of your company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the government intends to consider past performance information provided by other sources, as well as that provided by the Offerors, your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the government receives information from other sources.

L.5.4 Questionnaires

The offeror shall provide the Past Performance Questionnaire and Cover Letter, found at

Attachments L-3 and L-4, to each of the customer Points of Contact (POC) identified for each of the relevant past performance efforts. In order to expedite the assessment process, the offeror shall complete Sections 1 and 2 of the Past Performance

Questionnaire for the convenience of the POC. The offeror shall not, however, complete any other section of the Past Performance Questionnaire. Once the questionnaires are completed by the POCs, the information contained therein shall be considered sensitive and shall not be released to the offeror. Early submission of questionnaires is encouraged. Questionnaires shall be sent directly to DITCO to lisa.a.odonnell4.civ@mail.mil and nicole.thomas28.civ@mail.mil no later than the due date stated in the RFP. Electronic submission is required.

L.6.0 Small Business Participation (Evaluation Factor 3). Offerors will address this factor in Volume V, Additional Requirements. Refer to paragraph L.8.4 for details.

L.7.0 Volume IV Cost/Price (Evaluation Factor 4)

L.7.1 General Instructions

L.7.1.1 Cost/Price Information

This section is to assist you in submitting information other than pricing data that is required to evaluate the reasonableness and completeness of your proposed price.

Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your Cost/Price position. All information relating to the proposed price, including all required supporting documentation must be included in the section of the proposal designated as the Cost/Price Volume. Under no mailto:lisa.a.odonnell4.civ@mail.mil mailto:nicole.thomas28.civ@mail.mil circumstances shall this information and documentation be included elsewhere in the proposal.

Pricing submitted for the base period and all option periods, including option pricing for an additional six-month period that may be authorized IAW FAR 52.217-8 "Option to Extend

Services" will be evaluated. See FAR 52.217-8 which authorizes the government to require continued performance of any services within the limits and at the rates specified in the contract. The pricing proposal should include separate line items by CLIN for the additional six-month period IAW FAR 52.217-8. These prices shall be identical to the proposed pricing in the six months prior to expiration of the base period, or the final option period, if option periods are present. The total evaluated price will consist of the proposed price for the base period, all option periods, and the option pricing for the additional six-month period. Pricing will be incorporated upon contract award and used for all orders placed post-contract award.

L.7.1.2 Cost or Pricing Information Requirements

In accordance with FAR 15.403-1(b) and 15.403-3(a), information other than cost or pricing data may be required to support price reasonableness. Information shall be provided in accordance with FAR 15.403-5.

L.7.1.3 Schedule of Pricing

Offeror should stringently follow the government’s Schedule of Supplies or Services

(Attachment J-3 Exhibit B-1 m2P1 Cost Model) construct.

The offeror must complete the cost model Workload table with the propsed configurationclosest configuration that meets or exceeds the required of the PWSworkload.

The offeror shall provide a description of each solution proposed along with the basis of the proposed pricing in enough detail to allow evaluation using one or more techniques defined in FAR 15.404. Supporting pricing data shall be made available to the government upon request. Any added SLINs and corresponding unit prices in the cost model will be included in the contract award.

L.7.1.3.1 Schedule of Pricing for Government Provided CLIN/SLIN Structure

The Offeror shall provide pricing for all requirements identified in Attachment J-3. The proposed pricing for each requirement shall be considered negotiated ceiling rates.

L.7.1.3.2 Pricing for Requirements beyond Government provided CLIN/SLIN

Structure:

Offerors may propose additional SLINs in the Attachment J-3, Exhibit B-1 m2P1 Cost

Model to supplement their proposed technical solution. However, none of the additional vendor-proposed SLINs should be required to meet the standard solution requirements in the PWS and Proposal Format. SLINs shall not be added within the existing SLIN groupings. SLINs should be added in the provided space below the existing SLIN groupings and reference the existing SLIN headings. Any added SLINs should follow the same numbering and description name formats as what is provided in the cost model. The

Offeror shall follow the current government provided format for the base and all option periods when proposing additional SLINs, if applicable.

https://workspaces.disa.mil/Documents%20and%20Settings/Deborah.Wellen/Local%20Settings/Temporary%20Internet%20Files/Content.IE5/far/FAR15.DOC#b154031 https://workspaces.disa.mil/Documents%20and%20Settings/Deborah.Wellen/Local%20Settings/Temporary%20Internet%20Files/Content.IE5/far/FAR15.DOC#b154033 https://workspaces.disa.mil/Documents%20and%20Settings/Deborah.Wellen/Local%20Settings/Temporary%20Internet%20Files/Content.IE5/far/FAR15.DOC#b154035

If the Offeror chooses to propose additional SLINs, the government requires the Offeror to provide additional information to support price reasonableness. The Offeror is instructed to provide backup information such as and not limited to: Current published price lists;

historical prices paid by the government; sales data; any information reasonably required to explain the offeror’s estimating process to include judgmental factors applied and the mathematical or other methods used in the estimate, including those used in projecting from known data.

L.7.1.3.3 FFP Labor Rate Schedule

The labor rate schedule proposed in the Attachment J-3, tab ‘Labor Support’ will be used as the ceiling labor rates for pricing of all FFP task orders issued under this IDIQ contract.

The FFP rate ceiling will be based on the “composite” fully burdened labor rates proposed for each labor category, and be considered negotiated ceiling labor rates.

L.7.1.3.4 Transition Support Tasks

The Offeror shall submit pricing for the Transition Support Tasks 3, 4, 5, and 6 identified in Attachment J-106, Transition Support Tasks, in a MS excel to include formulas.

Proposed pricing for each Transition Support Task shall be clearly separated within MS

Excel. Multiple MS Excel Spreadsheets are permissible or the use of multiple worksheets within a workbook are acceptable.

L.7.1.3.4 Plug Number for Travel Associated with Transition Support. Due to the likely inability of any offeror to accurately estimate travel associated with this requirement, the government is providing plug numbers for SLINs 003TAT through 803TAT are to be used by all offerors when proposing travel. These cells are locked in the cost model and should not be changed. Actual travel shall be authorized by the Contracting Officer’s

Representative (COR) in writing prior to performance and will be paid IAW FAR Part

31.205-46.

L.7.2 Cost Model

Offerors should stringently follow the government’s Schedule of Supplies or Services

(Section J, Exhibit J-3, m2P1 Cost Model) construct and calculations and should not deviate from this format.

L.7.3 Volume Organization

The Cost/Price volume shall consist of a price/cost proposal outlining the proposed prices for each of the Contract Line Item Number (CLIN)/Sub-Contract Line Item Number

(SLIN). The government has provided a baseline ‘Exhibit B-1 m2P1 Cost Model’ MS

Excel workbook that the Offerors shall utilize in pricing their proposal. Within the

Exhibit B-1 Cost Model, offerors are required to provide monthly unit prices for all contract years for all CLINs/SLINs, on the worksheet tab entitled “B-Table.” If the price for a SLIN is “not separately priced (NSP)”, Offerors shall indicate the SLIN where the price is included and provide detailed supporting rationale in the column allotted for

Offeror’s Pricing Notes in the “B-Table” tab. The provided “B-Table” unit prices will be multiplied by the government provided evaluation quantities (as detailed in the

Evaluation Quantities tab of Exhibit B-1 Cost Model) to calculate the Total Evaluated

Price.

Offerors should only provide monthly unit pricing, unless otherwise noted, in the B-Table tab of Exhibit B-1 Cost Model for all of the government provided SLINs. Unit pricing provided in the B-Table tab will populate into the Evaluation Quantities. Unit pricing for all government provided SLINs will be included in the contract award. With the exception of selected cells within the “B-Table” tab of Attachment B-1 Cost Model, the

Cost Model is protected by the government and offerors shall not unprotect, alter or add to the Cost Model in any manner not directed in the instructions.

For all m2P1 resolutions, a complete standard solution to meet the minimum requirements of the PWS must be demonstrated using the government provided SLINs.

SLINs should not be added within the existing SLIN groupings. SLINs should be added in the provided space below the existing SLIN groupings and reference the existing SLIN headings. The offeror shall provide a description of each solution proposed along with the basis of the proposed pricing in enough detail to allow evaluation using one or more techniques defined in FAR 15.404. Supporting pricing data shall be made available to the government upon request. Any added SLINs and corresponding unit prices in the B-

Table tab will be included in the contract award.

Offerors should not include additional technical data in Volume IV – Cost/Price to include Exhibit B-1 Cost Model and any supplemental summaries. Technical data should only be included in Volume II of the offeror’s proposal.

L.7.4 Cost/Price Proposal To enable the government to evaluate pricing information as Factor 3 of the solicitation, the offeror shall provide unit prices for all CLINs/SLINs in the cost/price spreadsheet in

Section B.

L.8.0 Volume V – Additional Requirements.

The purpose of this volume is for offerors to provide information to the government for preparing the contract document and supporting file. Required information includes:

a. Table of Contents

b. Contract Information

c. Small Business Subcontracting Plan and Small Business Participation Plan

d. Organizational and Consultant Conflict of Interest (OCCI) Mitigation Plan

e. DD254, DoD Contract Security Classification Specification

f. Cross Reference Matrix

g. Glossary of Abbreviations and Acronyms

L.8.1 Contract Information. The offeror's proposal must include a scanned copy of the signed cover page (Section A) and of Sections I and K of the solicitation (as described in

L2.9.b). The RFP Section B will not contain pricing. Completed pricing information will be in Section J’s Exhibit J-3 m2P1 Cost Model of the solicitation.

L.8.1.1 Solicitation/Contract Form. Completion of Section A, blocks 30a-31c of the

Standard Form (SF) 1449 is required. Signature by the offeror on the SF1449 constitutes an offer, which the government may accept. By signing block 31b of the solicitation, the offeror acknowledges compliance with all sections in this RFP, HC1028-16-R-0020.

Offerors are reminded that many clauses require the prime contractor to include the same or similar clause(s) in contracts with subcontractors. Note: The offeror must comply with the FAR provision 52.204-7 entitled “System for Award Management.” The KO will validate offerors’ qualifications for award in SAM for those offerors who have been determined to be eligible for award. An offeror may be determined ineligible for contract award if not registered within SAM at time of award. Offerors are also required to complete and submit fill-ins, representations, certifications, acknowledgments, and statements reflected in this solicitation that are not already completed in SAM.

L.8.2 Assumptions to Solicitation Requirements

No assumptions or exceptions will be entertained.

L.8.3 Other Information Required

L.8.3.1 Authorized Offeror Personnel

Provide the name, title, and telephone number of the company/division point of contact and an alternate who can make decisions with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the government.

L.8.3.2 Company/Division Address, Identifying Codes, and Applicable Designations

Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other locations. List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or sub-offeror, and the percentage of work to be performed at each location.

L.8.4 Small Business Participation

All offerors, including small business, submitting a proposal as a prime contractor are required to meet or exceed the minimum quantitative requirement (MQR) of 25% or better of the offeror’s proposed pricing in awards to small businesses. For purposes of this acquisition, the offeror’s proposed pricing will be different than the total evaluated price. The basis for the total evaluated price of the contract will not be released prior to contract award.

L.8.4.1 Small Business Participation Commitment

The government’s assessment of small business participation and commitment will be measured to determine if small business participation is maximized where applicable.

Small business participation is separate from the FAR requirement for Contracting

Officer review and acceptance of an Offeror‘s Small Business Subcontracting Plan.

“Small business participation” means small…