Attachment_6_Technical_Proposal_Instructions.docx

SOL-CI-15-00017 Technical Proposal Instructions Attachment 6

Attachment 6

Technical Proposal Instructions

Technical Proposal Instructions

1. One original electronic version of the Offeror’s technical proposal shall be submitted through FedConnect in accordance with EPA-L-15-104 and EPA-L-36-101(a)(3), and one hard copy volume shall be submitted in accordance with EPA-L-36-101(a)(4).

2. The Offeror’s technical proposal must be prepared as a separate part of the total proposal package, and it shall be specific and sufficiently detailed to allow a complete evaluation of the method for satisfying the requirements set forth in this solicitation. All cost or pricing details shall be omitted from the technical proposal.

3. The technical proposal shall comprehensively address each of the factors described in the provision at EPA-M-15-101, “Evaluation Factors for Contract Award,” and it shall be prepared in exactly the same order, using the same numbering system for all criteria and subcriteria. Include all material that is to be evaluated under each of the corresponding individual criterion and subcriterion.

4. Technical proposals shall be limited to a total of 150 numbered pages. Paper size shall be 8 ½” x 11”. A piece of paper that has printing on both sides (double-sided) counts as two pages. The type of font used shall be no less than 12 point character size, and pages shall have no less than 1” all around margins. Smaller font is acceptable for non-text items such as tables, graphics, and exhibits. Fonts for non-text items shall be no less than 9 point character size. Any information contained on pages that exceed the page limit shall not be evaluated. The following items are excluded from the page limitation: letters of transmittal, cover page, table of contents, dividers, letters of commitment, resumes, COI Plan, CBI plan, Quality Management Plan, Small Business Plan, and past performance information. All Representations and Certifications may be provided in the cost proposal and are not subject to the page limitation. The Offeror’s letters of commitment and resumes should be submitted as tabbed attachments to the technical proposal. The offeror is strongly urged to be as succinct, clear, and concise as possible in writing the technical submission and adhering to the page limitation.

5. In accordance with the Section L clause FAR 52.215-1, 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 should contain the offeror’s best terms from both a cost or price and technical standpoint. The Government reserves the right to conduct discussions if the Contracting Officer determines them to be necessary.

6. It should be noted that the following instructions are provided to supplement the technical evaluation criteria as set forth in the Section M provision EPA-M-15-101 (b) ‘Evaluation Factors for Contract Award.’ The Offeror bears the burden of providing and addressing all of the information indicated in the technical evaluation criteria. The instructions below in no way limit or eliminate this requirement. The term “Offeror” as used in the technical proposal instructions and technical evaluation criteria shall mean the prime contractor and any proposed subcontractors or consultants.

The following instructions apply to the evaluation factors as set forth in the Section M provision, EPA-M-15-101 Evaluation Factors for Contract Award:

Criterion I – Past Performance This criterion is established to evaluate the offeror’s past performance utilizing information which the Government will elicit from various sources regarding contractual experience with the offeror. The offeror shall provide a list of all or at least five (5) relevant contracts and subcontracts completed during the last three years which are similar in nature to this requirement in terms of size, type, technical scope, and complexity.

Size, or magnitude, is defined as dollar amount and duration. Type is defined as nature of the agreement (i.e. cost-reimbursement/cost-plus-fixed-fee) and offeror’s role (i.e. prime/subcontractor). Technical scope is defined as efforts relevant to the technical areas encompassed by the Performance Work Statement. Complexity is defined as performance challenges such as regulatory compliance, integration and coordination with team members and stakeholders, and handling multiple on-going tasks.

For each contract listed, the offeror shall provide the information as required under the Section L provision EPAAR 1552.215-75 ‘Past Performance Information’ as part of its proposal for both the offeror and for proposed subcontractors whose subcontracts are expected to exceed $500,000. The offeror bears the burden of demonstrating the relevancy of its past performance; therefore, the offeror is required to provide sufficient data for the government to properly evaluate past performance. The evaluation of relevance – size, type, technical scope, and complexity – will be evaluated in the context of the work or role that the entity is proposed to perform under the contract. The most recent and most relevant past performance information may receive greater consideration.

References may be contacted by the Government and used in the evaluation of the offeror’s past performance. The references contacted and used to evaluate past performance are not limited to those identified by the offeror.

Criterion II – Demonstrated Qualifications of Proposed Personnel This criterion is established to evaluate the qualifications and availability of the offeror’s proposed personnel to accomplish the work described in the solicitation.

Subcriterion I.a – Managerial Qualifications Offerors should provide documentation demonstrating the managerial qualifications (experience, expertise, and education) and availability of the proposed Program Manager in managing contracts of similar size (dollar value), type (cost-reimbursable), and management scope (including management of subcontractor effort, multiple activities, and changing priorities) to that specified in the Performance Work Statement.

The Program Manager position is considered important to the success of contract performance and, as such, it is designated as a key personnel position. The individual(s) proposed to perform under this position will be designated under the Section H clause EPAAR 1552.237-72, ‘Key Personnel.’

For the managerial qualifications of the Program Manager, please identify the following:

i. Name, professional level, and job title;

ii. Proposed role under the contract;

iii. Degree(s) held and corresponding field of study;

iv. Specific contract management experience which relates to the type of work specified in the Performance Work Statement;

v. Job responsibility for contract experience described in item iv (It is not sufficient to merely state that an individual managed a contract. WHAT DID THAT INDIVIDUAL DO?);

vi. Number of technical personnel supervised under the contracts managed;

vii. Time dedicated to each project in item iv;

viii. Beginning and ending date of each project in item iv; and

ix. Demonstration of how the Program Manager will remain available for this requirement while fulfilling his or her obligations to other contracts or clients. A commitment letter shall be provided for the Program Manager if not already employed by the prime contractor. If a percentage of availability is provided, please explain what the percentage is based on.

Subcriterion I.b – Technical Qualifications Offerors should provide documentation demonstrating the technical qualifications (experience, expertise, and education) and availability of the proposed Program Manager relative to the scientific, technical, and engineering requirements presented in the Performance Work Statement.

The Program Manager position is considered important to the success of contract performance and, as such, it is designated as a key personnel position. The individual(s) proposed to perform under this position will be designated under the Section H clause EPAAR 1552.237-72, ‘Key Personnel.’

For the technical qualifications of the Program Manager, please identify the following:

x. Name, professional level, and job title;

xi. Proposed role under the contract;

xii. Degree(s) held and corresponding field of study;

xiii. Specific related project experience that demonstrates the qualifications to perform and/or oversee technical tasks in accordance with the type of work specified in the Performance Work Statement (It is not sufficient to merely state that an individual worked on a project. WHAT DID THAT INDIVIDUAL DO?);

xiv. Demonstration of how the Program Manager will remain available for this requirement while fulfilling his or her obligations to other contracts or clients. A commitment letter shall be provided for the Program Manager if not already employed by the prime contractor. If a percentage of availability is provided, please explain what the percentage is based on

Criterion III – Demonstrated Effectiveness of Proposed QA/QC Measures This criterion evaluates the adequacy of the offeror’s Quality Management Plan (QMP) to effectively manage the quality assurance (QA) and quality control (QC) activities of the contract. The evaluation centers on the completeness and relevance of the offeror’s QMP for meeting the quality assurance requirements under the contract.

See the Section L provision EPA-L-46-101 ‘Instructions for the Preparation of a Quality Management Plan’ and the Section E clause FAR 52.246-11 ‘Higher-Level Contract Quality Requirement.’ Each offeror, as a separate and identifiable part of its technical proposal, shall submit a Quality Management Plan (QMP) setting forth the offeror’s capability for quality assurance. Additional information on EPA requirements for the Quality Management Plan can be accessed at the following: http://www.epa.gov/quality/qs-docs/r2-final.pdf.

It is the intent of the Government to incorporate the Quality Management Plan in its entirety into any resultant contract.

Criterion IV – Small Business Participation This criterion evaluates the proposed extent of participation by small business concerns in performance of the contract. The offeror shall submit a subcontracting plan in accordance with the Section I clauses FAR 52.219-8 ‘Utilization of Small Business Concerns’ and FAR 52.219-9 ‘Small Business Subcontracting Plan.’ The offeror’s subcontracting plans will be reviewed utilizing EPA’s goals for subcontracting with small business concerns as provided in Section L clause EPA-L-19-102 ‘EPA’s Goals for Subcontracting with Small Business.’

This criterion examines the extent to which small business concerns are specifically identified, the extent of commitment to use small business concerns, the complexity and variety of the work small business concerns are to perform, and the extent of participation of small business concerns in terms of total value.

Criterion V – Demonstrated Corporate Experience and Expertise This criterion is established to evaluate the offeror’s corporate experience and expertise in managing projects or contracts of similar size, type, and technical scope. This criterion differs from the past performance criterion in that past performance is an examination of what the contractor has done and how often, while this criterion is an examination of how well the offeror did it.

This criterion examines the offeror’s efforts in performing work relevant to providing economic, environmental, and financial analysis and support; providing technical and engineering analysis; providing communications, outreach, and regulatory program support; designing computer and web-based systems; providing database and technical support for these systems; providing support for compliance monitoring of air pollution regulations; and providing regulatory and compliance support for federal transportation fuels initiatives.

6-4