S5121A-15-R-0012-0002.pdf

S5121A-15-R-0012

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to:

(1) Update Addendum to 52.212-1

(2) Amend PWS to add minimum education and experience to all labor categories

(3) Update Attachment 5: Pricing Sheet

(4) Provide Attachment 8: DCMA MOCAS Support BPA Labor Categories

(5) Provide Vendors w ith MOCAS Brief

See Summary for Details

1. CONTRACT ID CODE PAGE OF PAGES

S 1 71

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 10-Dec-2015

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X S5121A-15-R-0012

X

9B. DATED (SEE ITEM 11)

26-Oct-2015

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

09-Dec-2015

CODE

DCMA PROCUREMENT CENTER IT S5121A

DCMA PROCUREMENT CENTER (IT S5121A)

3901 A AVE BLDG 10500

FORT LEE VA 23801-1809

S5121A 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been added by full text:

ATTACHMENT 10

DCMA MOCAS Support BPA Labor Categories Minimum Education & Experience

Labor Category Education

Minimum Work

Experience

Other

Requirement

Administration Specialist Associates * Minimum 3 years professional experience in

Administrative

Support directly related to work required in the PWS as identified in para

3.2.39 of the PWS.

Business Analyst Bachelors * Minimum 8 years professional experience.

* Minimum 5 years professional experience in

Business Analysis directly related to work required in the

PWS as identified in para 3.2.5 of the

PWS.

Business Process Reengineering Specialist Bachelors * Minimum 7 years

Business Process

Reengineering professional experience.

* Minimum 5 years professional experience in

Business Analysis directly related to work required in the

PWS as identified in para 3.2.31 of the

Capital Planning/Finance Analyst Bachelors * Minimum 5 years of professional experience in relevant capital planning.

* Minimum 3 years of proven experience in federal Capital

Planning and

Investment Control with understanding for CPIC process and

OMB reporting requirements for a program valued at

$15M or more.

Change Management Specialist Bachelors * Minimum 7 years experience in change management.

Chief Systems Engineer Bachelors * Minimum 10 years of engineering experience on IT

Projects, with at least

3 years in an engineering lead position on a program with a budget at or exceeding $15M.

* Minimum 5 years’ experience in

Systems Engineering and/or Program

Lifecycle

Development.

Certification in

Program/Project

Management and/or Enterprise

Architecture.

Client Data/Interface Analyst Bachelors * Minimum 6 years professional experience in directly related to work required in the

PWS as identified in para 3.2.30 of the

Communication Manager Bachelors * Minimum 7 years experience as a

Communications

Manager.

Cost Modeler Bachelors * Minimum 5 years experience

* Minimum 3 years experience in Capital

Planning and

Investment Control

Data Modeler Bachelors * Minimum 5 years professional experience directly related to work required in the PWS as identified in para

3.2.4 of the PWS.

* Minimum 3 years experience in

Information

Technology

Database Management Specialist Bachelors *Minimum 6 years experience in directly related to work required in the

PWS as identified in para 3.2.26 of the

Human Factors Analysis Bachelors * Minimum 6 years experience

* Minimum 3 years professional experience in directly related to work required in the

PWS as identified in para 3.2.10 of the

Incident/Problem Manager Bachelors * Minimum 6 years experience

* Minimum 3 years professional experience in directly related to work required in the

PWS as identified in para 3.2.22 of the

Information System Training Specialist Bachelors * Minimum 6 years experience directly related to work required in the PWS

3.2.29 of the PWS.

IT Security Specialist Bachelors * Minimum 5 years experience directly related to work required in the PWS

3.2.24 of the PWS.

MOCAS Database/Code Base SME Bachelors * Minimum 8 years professional experience directly related to work required in the PWS

3.2.16 of the PWS.

MOCAS Legacy Technology Programmer Bachelors * Minimum 8 years experience directly related to work required in the PWS

3.2.36 of the PWS.

MOCAS SME Bachelors * Minimum 8 years experience directly related to work required in the PWS

3.2.15 of the PWS.

Program Collaboration/SharePoint Content

Manager

Bachelors * Minimum 8 years professional experience directly related to work required in the PWS

3.2.33 of the PWS.

Program Manager Bachelors • Minimum 10 years of experience leading and managing programs and/or projects, including mission critical programs, IT systems implementation, solution development

• Minimum 5 years of proven experience in federal government program/project management

• Minimum 5 years of experience in

Information

Technology

• Experience managing a program with at least $10 million annual budget

Program

Management

Institute (PMI), Program

Management

Professional

(PMP) or

Program

Management

Professional

(PgMP) certification

Project Manager Bachelors * Minimum 7 years

Commercial/Federal

Project/Program

Management experience directly related to work required in the PWS as identified in para

3.2.14 of the PWS.

* Project/program with $5M annual budget

* Minimum 5 years in Information

Technology

(Required For IT

Projects Only)

Project Scheduler Bachelors * Minimum 5 years

Program Scheduler experience directly related to work required in the PWS

3.2.37 of the PWS.

Quality Management Analyst, Software Bachelors * Minimum 8 years experience

* Minimum 4 years professional experience directly related to work required in the PWS

3.2.19 of the PWS.

Requirement Analyst Bachelors * Minimum 6 years experience

* Minimum 3 years professional experience directly related to work required in the PWS

3.2.8 of the PWS.

Risk Management Specialist Bachelors * Minimum of 3 years experience in risk management directly related to work required in the

PWS as identified in para 3.2.20 of the

Senior Business Process Analyst Bachelors * Minimum 12 years professional experience

* Minimum 8 years experience in

Business Analysis directly related to work required in the

PWS as identified in para 3.2.9 of the

Service Assets & Configuration Mgmt. Specialist Bachelors * Minimum 8 years experience.

* Minimum 4 years professional experience directly related to work required in the PWS

3.2.8 of the PWS.

Service Orientated Architecture (SOA) Engineer Bachelors * Minimum of 5 years experience in

SOA. *

Minimum 4 years professional experience directly related to work required in the PWS

3.2.34 of the PWS.

SME Acquisition Systems Bachelors *Minimum 8 years experience directly related to work required in the PWS

3.2.17 of the PWS.

Software Architect Bachelors * Minimum 8 years experience

* Minimum of 5 years professional experience directly related to work required in the PWS

3.2.13 of the PWS.

System Architect Bachelors * Minimum 10 years experience

* Minimum 5 years experience in System

Architect directly related to work required in the PWS

3.2.3 of the PWS.

Systems Engineer Bachelors * Minimum of 5 years of engineering experience on IT

Projects directly related to work required in the PWS as identified in para

3.2.6 of the PWS.

* Minimum of 2 years experience in

The Department of

Defense Architecture

Framework (DoDAF) modeling with

Business Process

Model and Notation

(BPMN), Unified

Modeling Language

(UML) and

Extensible Markup

Language (XML) notations.

Systems Programmer Bachelors Minimum of 5 years experience in language/technology specified in task order(s).

Technical Editor Bachelors * Minimum of 5 years professional experience directly related to work required in the PWS

3.2.23 of the PWS.

* Minimum 1 years

Information

Technology experience (Required

For IT Projects

Only).

Test Engineer Bachelors * Minimum of 5 years of Software or

IT Systems test experience as a Test

Engineer.

* Minimum of 5 years professional experience directly related to work required in the PWS

3.2.11 of the PWS.

Test/Release Manager Bachelors * Minimum of 7 years of Software or

IT Systems test experience.

Minimum of 5 years professional experience directly related to work required in the PWS

3.2.12 of the PWS.

Training Manager Bachelors * Minimum of 8 experience directly related to work required in the PWS

3.2.27 of the PWS.

Training Specialist Bachelors * Minimum of 5 experience directly related to work required in the PWS

3.2.28 of the PWS.

Web/User Interface Developer Bachelors * Minimum of 7 years Web/User

Interface Developer professional experience.

* Minimum of 5 years professional experience directly related to work required in the PWS

3.2.32 of the PWS.

The following have been modified:

ADDENDUM 52.212-1

A. ADDENDUM 52.212-1: INSTRUCTIONS TO OFFERORS

(1) Submission of Proposals: The competition for DCMA MOCAS IDIQ contracts is being executed as 25% small business set aside. The Government contemplates award of multiple IDIQ contracts resulting from this solicitation.

This multiple award IDIQ effort may result in up to four awards. The Government reserves the right to award to any size business if it’s determined to be in the best interests of the Government. The number of IDIQ awards may be limited for efficiency purposes, but it is anticipated IDIQ contracts will be awarded to at least one small business interest, with equal preference given to 8(a), Service Disabled Veteran Owned Small Business (SDVOSB), Woman

Owned Small Business (WOSB), and/or Historically Underutilized Business Zones (HUBZone) during the evaluation process. However, if no acceptable proposals are received from a small business at a fair market price, the 25% small business set aside will be automatically dissolved.

The Government contemplates that the majority of future DOs awarded will be Lowest Price Technically

Acceptable (LPTA) but reserves the right to issue DOs on a best value basis. Task Orders may be awarded on a

Firm Fixed-Price (FFP) or Time & Materials/Labor Hour (T&M/LH) basis. The collective ceiling for all contracts awarded as a result of the RFP will be $142M.

Offerors are responsible for submitting Proposals so as to reach the Government office designated below by 21 Dec

2015, 12:00 PM (EST). Proposals shall be submitted prior to the closing date and time identified to the following address.

Attn: Brian Gillead (S5121A-15-R-0012)

Room 1069.07

Defense Contract Management Agency (DCMA)

3901 A. Ave, Fort Lee, VA 23801

The Technical Proposal and the Price Proposal shall be separate and complete so that evaluation of one may be accomplished independently of the other. DO NOT INCLUDE price information in the technical proposal."

Technical and Price Proposals received after the deadline will be considered “late” and will not be accepted.

Minimum Guarantee: The minimum guarantee for each ID/IQ contract is $2500.00.

(2) Request for Proposal Questions: All questions concerning this RFP shall be submitted in writing to the POC:

Brian Gillead via email larry.gillead@dcma.mil no later than 10 November 2015, 12:00 PM (EST).

When submitting questions and comments, please refer to the specific text of the RFP in the following format:

Subject: RFP No. S5121A-15-R-0012

Reference: Section ___, Paragraph(s) ____, Page(s) ____.

All questions will be kept anonymous. Answers will be issued via amendment and provided to all Offerors on the

Internet via www.fbo.gov.

Noncompliance with the RFP requirements will raise serious questions regarding an offeror’s technical ability to perform the services and may be grounds to eliminate the proposal from further consideration for contract award.

The submission of the documentation specified below will constitute the offeror's acceptance of the terms and conditions of the RFP, concurrence with the Performance Work Statement, and the proposed contract type.

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

If an offeror believes that the requirements in these instructions contain an error, an ambiguity, omission, or are otherwise unsound, the offeror shall immediately notify the KO in writing with supporting rationale. The offeror is mailto:larry.gillead@dcma.mil reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion.

(2.1) North American Industry Classification System (NAICS) Code applicable to this solicitation is 541611 and the

Size Standard is $15 million. Per FAR 4.1201(a): Prospective contractors SHALL complete electronic annual representations and certifications (Reps & Certs) at https://www.acquisition.gov database. Your Reps and Certs must include the NAICS applicable to this solicitation document and indicate your organization’s business size status.

(2.1.2) Per 13 CFR 121.104 - If the size determination is based on average annual gross revenue, the method for determining business size status is based on the company’s average annual gross revenues for the last three fiscal years. Organizations whose average annual gross revenues exceed the size standard of this solicitation are considered large businesses. [Additional definition is available by searching 13CFR121 at http://www.gpoaccess.gov/cfr/index.html]

(2.1.3) PERIOD FOR ACCEPTANCE OF OFFERS: Reference 52.212-1 Paragraph(c)

The Government requires a minimum acceptance period of 90 calendar days in lieu of the 30 calendar days as specified in FAR 52.212-1(c), Period of Acceptance of Offers. The Government will not award a contract to an offeror allowing less than the Government’s minimum acceptance period.

(2.1.4) COLLECTIVE BARGAINING AGREEMENTS (CBAs):

The contractor is required to submit all CBAs applicable to the facility providing service to the requirement location(s). The CBA must be signed and final. If the CBA is currently in negotiation, submit an unsigned copy with the offer; however, the final CBA must be submitted as soon as signed.

(2.1.5) ADDITIONAL CLASSES OF SERVICE EMPLOYEES: Reference 52.222-41(c):

The Contracting Officer has identified the classes of service employees anticipated to be employed under the resultant contract in FAR Clause 52.222-42. If the Offeror anticipates employing classes of employees not identified under Clause 52.222-42, or listed under the applicable wage determination, the offeror shall classify the unlisted employee labor categories so as to provide a reasonable relationship between the unlisted labor categories and the listed labor categories in the wage determination, per paragraph (c) of clause 52.222-41. Full definitions of the labor categories are available on the Department of Labor site at http://www.dol.gov/whd/govcontracts/sca.htm, under Guidance, Service Contract Act Directory, 5th Edition.

(3) Solicitation Posting: The solicitation will be 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.

(4) Debriefings: The KO will promptly notify offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with FAR 15.505. The KO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506.

Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

(5) Oral Presentations: The Government reserves the right to require oral presentations by the offerors. The offerors will receive a minimum of seven (7) calendar day notice prior to the requested time for presentation and details describing the requirements for oral presentations.

(6) Proposal Preparation Instructions: These instructions prescribe the format for the proposal and describe the approach for the development and presentation of proposal data. These instructions are designed to ensure the submission of necessary information to provide for the understanding and comprehensive evaluation of proposals.

http://www.gpoaccess.gov/cfr/index.html http://www.dol.gov/whd/govcontracts/sca.htm http://www.fedbizopps.gov/

(7) Proposal Format: Offerors shall submit an original and the number of copies listed in the below table of their proposal. Each volume of the proposal should be separately bound in a three-ring loose leaf binder which shall permit the volume to lie flat when open. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification and the offeror's name. The same identifying data should be placed on the spine of each binder. All text shall be single spaced and printed black on white paper (black and white requirement does not apply to graphics, photos, etc., Company stationary and logos are acceptable). Printing shall be easily readable (12 point font or 10 point font proportional spacing.) Cross-references should be utilized to preclude unnecessary duplication of data between sections. Page limitations are as follows:

VOLUME TITLE HARD

COPIES

DIGITAL

COPIES

PAGE LIMITS

I Contract/Price Original 1 N/A

II Technical Capability Original + 5 1 45 Pages

III Past Performance Original + 5 1 12 Pages

(8) Proposal Limitation: The proposal shall not exceed the limits stated above. If the page limits are exceeded, the pages in excess of the limit shall be removed and returned, unread, to the offeror. The Government will not accept any changes to the contractor’s proposal after the closing date of the solicitation (See FAR 15.208 for further information regarding late proposals). If discussions become necessary, page limitations may be placed on responses to Items For Negotiation (IFN). The specified page limits for IFN responses will be identified in the letters forwarding the IFN to the offerors.

(8.1) Page Limit Includes: All appendices, charts, graphs, diagrams, tables, photographs, drawings, etc.

(8.2) Page Limit does not include covers for volumes, tables of contents, executive summary, resumes, glossary of abbreviations and acronyms, indexes, title pages, cross reference indexes, and section dividers/tables if they are inserted solely to provide ease to the reader in locating parts/sections of the proposal. They will be counted if they contain any other information, i.e., diagrams, extraneous data, etc. Pages marked “This page intentionally left blank” will not be counted.

(8.3) What Counts As A Page? A page shall be an “8 ½ X 11” sheet of paper. When both sides of a sheet display printed material, it shall be counted as two pages. Letter size and spacing requirements for illustrations and tables can be at the discretion of the offeror but must be easily readable. Fold-outs will be counted as the appropriate number of pages based on an “8 ½ X 11” sheet of paper. Use at least 1 inch margins on the top and bottom and 3/4 inch side margins. The Contractor shall number each page in order to eliminate any confusion. In the event the contractor creates an ambiguity in their numbering of pages, the Government may exercise its own discretion in counting pages.

(9) Exceptions: 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 “Instructions” and

“Evaluation factors” (Addendum 52.212-1 and 52.212-2). Failure to meet a requirement may result in an offer being ineligible for award. If the offeror finds it necessary to take exception to any of the requirements specified in this solicitation, clearly indicate in the applicable Volume each such exception with a complete explanation of why the exception was taken, what benefit accrues to the Government (if any), and its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. This information shall be provided in the format below.

Solicitation

Document

Page/

Paragraph

Requirement/

Portion

Rationale &

Impact

PWS Section and Para

# etc.

Applicable

Page and

Paragraph

Numbers

Identify the requirement or portion to which exception is taken

Describe

The rationale and impact of the exception

(10) Volume I – Contract/Price: Section A: Offerors are required to submit a completed SF 1449 (including acknowledgment of Amendments), completed Pricing Worksheets. All final monetary extensions shall be in whole dollars only. Failure to follow the below Contract Proposal preparation instructions may cause your proposal to be deemed unacceptable by the Government. The price proposal must be aligned with the Offeror’s technical proposal to permit the Government to perform a complete evaluation of the proposed prices. The offeror shall provide the name, title and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

(10.1) Pricing Worksheets: The offeror shall complete the Pricing Worksheet incorporated into this solicitation. The offeror shall indicate the unit price for each labor category listed on the Pricing Worksheet. The labor category rates provided are to be fully burdened rates that includes labor categories and rates (off-site) for the entire ten year ordering period. For evaluation purposes only, off-site Hourly Rates should be based on a Full-Time Equivalent

(FTE) with 1,920 hours and Place of Performance to be DCMA Fort Lee, VA. Offerors must submit pricing by completing Attachment 5 Pricing Sheet of the solicitation. Failure to complete the Pricing Sheet will result in exclusion of Offeror for consideration of award. Should a contract be issued to the offeror, the proposed labor rates provided on the pricing worksheet shall become the maximum rate allowable for that labor category when pricing

Delivery Orders issued against the resultant contract.

(10.2) The Contract Price Volume shall be organized as follows and contain the identified information.

i. A completed and signed Page 1 of the SF 1449 with the Contractor’s Tax Payer Identification number

(TIN) and DUNS number typed.

ii. Completed Pricing Sheet (Attachment 5). A statement explaining how the price was derived.

iii. Information regarding the financial ability of the Offeror and its subcontractor(s) to fulfill the requirements of the contract (such as a current financial statement or a D&B report, etc.) shall be submitted. This section shall not exceed 5 pages per contractor (i.e. a prime with 2 subcontractors will be allowed 15 pages). The Offeror must meet all requirements as listed in the solicitation and be registered in System for Award Management (SAM), www.sam.gov, to be eligible for award. No proof is required other than a statement that the Offeror is registered in SAM.

iv. Small Buisnees Sub-Contracting Plan (As Applicable)

(11) Volume II - Technical Capability: The Technical Capability Volume shall, at a minimum, be prepared in a form consistent with the Performance Work Statement (PWS), and the evaluation criteria for award set forth in the solicitation. The section shall be prepared in an orderly format and in sufficient detail to enable the Government to make a thorough evaluation of the contractor’s technical competence and ability to comply with the contract task requirements specified in the PWS. The offeror shall address as specifically as possible the actual methodology you would use for accomplishing the tasks. The volume shall be organized according to the following general outline:

Tab A: Table of Contents (Not included in “Tab G” 45 page limitation)

Tab B: List of Table and Drawings (Not included in “Tab G” 45 page limitation)

Tab C: RFP Compliance Matrix (Attachment 6) (Page Limitation N/A)

Tab D: Exceptions/Assumptions (Identification and explanation of any exceptions or deviations).

Additionally, identify any assumptions used in preparing the proposal (Page Limitation N/A)

Tab E: Executive Summary (Recommended not Mandatory) (3 Page Limitation)

Tab F: Experience (6 Page Limitation) Organizational Conflict of Interest

Tab G: Technical Capability (45 Page Limitation)

Tab H: Security Qualification (Page Limitation 2)

Tab I: Proof of Capability Maturity Model Integration (CMMI) Level 3 (Page Limitation N/A)

Tab J: Organizational Conflict of Interest (Page Limitation N/A) http://www.sam.gov/

(11.1) For Tab E, Executive Summary (NOT INCLUDED IN THE 45 PAGE LIMITATION) is limited to (3) pages pages. The offeror shall provide an executive summary of the entire proposal, including significant approach tradeoffs and risks, and highlight any key or unique features, excluding cost. The offeror shall include a list, including addresses, of all companies participating on the offeror’s team, including the prime contractor, any partners, subcontractors, etc. Any material presented in this summary shall not be considered as meeting the requirements for any other parts of the proposal.

(11.2) Offerors shall also provide a completed RFP Compliance Matrix (Attachment 6) in their technical proposal to clearly indicate where in the response each of the RFP requirements is addressed. Incomplete RFP compliance matrix may result being deemed unresponsive.

(11.3) Offeror shall provide a technical proposal to address the requirements of the RFP and the evaluation factors presented in this RFP in a straightforward, complete, and concise manner. The Offeror shall demonstrate its ability to comply with each requirement and explain how such compliance is achieved. Statements such as, “the Offeror understands,” or “the Offeror will comply” and statements that paraphrase the Statement of Work or other contract requirements are inadequate. The technical proposal shall not refer to price. However, resource information such as data concerning labor hours and category, materials, subcontracts, etc. shall be included in the technical proposals, if applicable, so that the Government can evaluate the Offeror’s understanding of the scope of the required work.

(11.5) TAB F: Factor 1: Experience (NOT INCLUDED IN THE 45 PAGE LIMITATION)

Go/No-Go Factors represent minimum qualifications, experience, and/or capabilities that Offerors should possess in order to successfully carry out contractual requirements. Proposals will first be reviewed to confirm the Offeror’s ability to meet the Go/No-Go factors provided in this solicitation (reference 52.212-1) para (7). If a proposal fails to meet any of the Go/No-Go factors provided herein, the proposal will not be evaluated further, and the

Offeror will not be given further consideration for a contract award.

(11.5.1) For the purposes of satisfying Go/No-Go requirements, the Government will consider the ability of the proposed team to meet these criteria, whether by the prime contractor alone or together with its subcontractors.

Offerors should be aware that if awarded a contract under this solicitation, the Offeror is expected to produce and maintain throughout performance of the contract the level of quality that was initially proposed. The following matrix is provided to clarify how potential offerors may satisfy the Go/No-Go Factors:

Sub-Factor Description Responsible Team Member

1 Contract Experience Prime Only

2 Prime Experience Prime Only

3 Project Experience Prime or Team

Note: Offerors shall clearly identify what information provided in its proposal satisfies the Go/No-Go factors identified in the technical evaluation factors(shall not exceed 6 pages) of the technical proposal. Offerors shall not rely on the Government to make assumptions about its ability to satisfy the Go/No-Go factors.

(11.5.2) Offerors shall submit the following information in response to the Go/No-Go factors:

Question PAST PERFORMANCE

A Name of Contracting Agency:

B Contracting Officer’s or Similar Representative Name:

Telephone:

Email:

C Contract/Task Order Number:

D Contract Type: (T&M, FFP, CPFF, IDIQ)

E Total Contract Value:

F Total value of Task Orders Awarded:

G Contract Period of Performance:

H Offeror’s Role: (Prime or Subcontractor)

I Description of contract work:

(11.6) TAB G: Factor 2: Technical Capability

(11.6.1) Sub-factor 1: Technical Approach (ability to satisfy requirements in PWS Technical Capability)

(11.6.2) The Offeror shall describe in detail its technical capabilities on how it will meet the criteria in the statement of work. The Offeror shall describe in detail its technical approach. The Offeror’s technical approach shall clearly describe and address the Offeror’s understanding of the desired outcomes contained in the PWS. The Offeror shall also explain how its technical approach would benefit the government.

(11.6.3) The technical capability shall clearly cite discrete examples of successful performance and tangible results similar to the specific tasks contained in the PWS. Statements such as “the Offeror understands” or “the Offeror will comply” and statements that paraphrase the PWS or other contract requirements are inadequate. Statements alone without substantiation are not enough to demonstrate Offeror’s technical capabilities.

(11.7) Sub-factor 2: Management Approach (quality oversight).

(11.7.1) The offeror shall submit an organization chart with a detailed explanation of their organization structure, including what the key positions are, the qualifications of the position(s), and what authority the individuals possess;

what parts of the organization are responsible for managing and accomplishing what work (identify each organizational element, i.e., Division/Branch/Team); where decision making authority lies within the organization; explain how will you simultaneously manage multiple delivery orders; and identify what specific work the prime, subcontractors or teaming partners are performing.

(11.7.2) The Offeror shall describe in detail its management approach. The Offeror’s management approach shall demonstrate the Offeror’s ability to manage and successfully execute a contract this size. The management approach shall also explain the Offeror’s staffing approach (including the ability to quickly provide all necessary labor categories and continuity in any DCMA location), subcontracting plan and the overall contract and Delivery

Order management process.

(11.7.3) The offeror shall describe the ability to manage and integrate teaming partners/subcontractors into their organization. The offeror shall describe the working relationship between the prime and their teaming partners/subcontractors at the corporate level and employee level and when teaming partners/subcontractors are performing the work how will they ensure adequate oversight of teaming partners/subcontractors to include performance monitoring and timely resolution of any issues that may arise. Additionally, identify what specific corporate reach-back capability they will possess and identify the benefits the government will receive as a result of this capability.

(11.7.4) The offeror shall identify, consider, and address any Organizational Conflict of Interest (OCI) concerns. If required, the offeror shall present a written mitigation plan which details how they will ensure compliance with OCI clauses in the solicitation. The mitigation plan shall clearly identify a credible and concrete mechanism for identifying, avoiding, neutralizing, or mitigating actual or potential conflicts. The offeror’s proposed mitigation plan shall flow down to the subcontractor level as required.

(11.8) Sub-factor 3: Staffing & Key Personnel (meeting required specialized experience).

(11.8.1) The Offeror’s proposal shall include a resume for all key personnel. These qualifications will be evaluated on how well they meet or exceed the functional, educational, and experience requirements of each prospective

Offeror’s Labor Categories and demonstrate an ability to successfully implement the Offeror’s proposed solution.

The personnel portion of the proposal shall include:

(a) The Offeror shall identify its key personnel and describe their ability to satisfy the requirements of the

PWS. The Offeror must submit the qualification documentation for the key personnel positions to include all security requirements. (see Section 3.0 of the PWS – Key Personnel) which demonstrate the qualifications of the individual and their ability to meet the required specialized experience. Each resume is limited to three (3) pages. Only one (1) resume is required for each key personnel labor category.

(b) In performing some of the primary tasks in the PWS, locating and retaining personnel in positions that require extremely unique skill sets and have a finite pool of qualified candidates has been identified as a high risk. With this in mind, the offeror shall specifically identify all of the labor classifications they deem to be uniquely skilled and/or hard to find skill sets, explain why they choose these skill sets, describe whether they already possess individuals with these skill sets, and describe how they will recruit and retain for these positions.

(12) Volume III: Factor 3: Past Performance

(12.1) Past Performance information described herein is required on the offeror and all subcontractors, teaming partners, and/or joint venture partners proposed to perform the PWS primary tasks and subtasks. The offeror shall submit, along with the information required in this paragraph, a consent letter, executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the offeror's performance.

Note: The consent and client authorization letter is not included in the 12 page count limitation for Volume III.

(12.2) In conducting the Past Performance evaluation, the Government reserves the right to use both the information provided in the offeror’s Past Performance Volume and information obtained from other sources, such as the Past

Performance Information Retrieval System (PPIRS) or similar systems, Defense Contract Management Agency

(DCMA) and commercial sources.

(12.3) The offeror shall include documentation regarding their relevant past performance as it directly relates to the work being procured under this solicitation. The offeror SHALL ONLY submit past performance data on contracts that have been active within the last 36 months from solicitation issuance. The past performance data shall document a successful history of past contract performance. To illustrate the offeror’s past performance, the following documentation shall be submitted:

(12.4) The offeror shall provide documentation outlining the offeror’s past performance in contracts, as a prime or major subcontractor, that they deem is the same or similar in nature, size, magnitude, and complexity to the services being procured under this Solicitation (no more than 3 contracts shall be provided). The submittal shall include rationale on how it was determined that the work performed previously was the same or similar in nature, size, and complexity to the work specified by this solicitation. Non-Government contracts may be used if Government contracts are not available. The documentation shall be submitted in the following format:

Question PAST PERFORMANCE

A Name of Contracting Agency:

B Contracting Officer’s or Similar Representative Name:

Telephone:

Email:

C Contract/Task Order Number:

D Contract Type: (T&M, FFP, CPFF, IDIQ)

E Total Contract Value:

F Total value of Task Orders Awarded:

G Contract Period of Performance:

H Offeror’s Role: (Prime or Subcontractor)

I Description of contract work:

J List of all disputes associated with the contract:

K List of options that were not exercised and reason(s) why they were not exercised:

L Problems encountered and how they were resolved:

K Achieved benefits to the customer:

(12.5) Subcontractors’ past performances are allowed but at least one past performance must be from the prime contractor. In demonstrating past performance, the Offeror must describe the relevance of the work experience listed above to the requirements contained in the PWS, and shall provide any other information that will serve to establish the Offeror’s proven corporate technical and managerial experience in fulfilling the requirements contained in the scope of this PWS.

(12.6) For the contracts identified for past performance evaluation, the offeror shall forward a copy of the Past

Performance Questionnaire (Attachment 7: Past Performance Questionnaire) to the points of contact responsible for monitoring performance under such contracts. Each past performance submittal is limited to four (4) pages for maximum of (12) pages. DCMA reserves the right to contact any and all past performance references submitted in response to this RFP. The Offeror must follow the submission instructions in (Attachment 7) to complete the Past

Performance Questionnaires.

(12.7) These questionnaires shall be returned directly to Brian Gillead, contract specialist, at larry.gillead@dcma.mil. Any questionnaires not returned directly to the contract specialist will not be reviewed and evaluated. The information contained in the questionnaires will be used to evaluate the offeror’s past performance.

If any negative past performance information is received, the contractor may be given an opportunity to provide rebuttal, unless the contractor was previously afforded an opportunity to do so. A maximum of three (3)

Questionnaires should be received by the contract specialist prior to the date and time established for the RFP closing. New entities that have no past customers shall notify the contract specialist, prior to the date and time established for the RFP closing, that they have had no previous clients and that the minimum number of questionnaires cannot be provided. Offerors without past performance history will be rated as “Neutral”.

(12.8) Offerors are reminded that both independent Government/Commercial data and data provided by offerors in their proposals may be used by the Government to evaluate offeror past performance. However, the burden of providing thorough, complete, and current past performance information as requested in this paragraph remains with the offerors. Proposals that do not contain the information requested by this paragraph risk rejection or a less than acceptable performance rating by the Government. In the case of an offeror without any relevant past performance history, past performance will be evaluated as “neutral.”

ADDENDUM 52.212-2

B. ADDENDUM 52.212-2: EVALUATION CRITERIA

(1) Evaluation of Proposals

(1.1) Basis for Contract Award: Full Tradeoff Source Selection Process utilizing streamlined procedures for evaluation of commercials items IAW FAR 12.602. This best-value decision shall be based on a comparative assessment of proposals against all source selection criteria in the solicitation, considering recommendations and minority opinions presented to the SSA. While the Source Selection Authority (SSA) may use reports and analyses prepared by others, the source selection decision shall represent the SSA's independent judgment.

(1.2) Contract(s) may be awarded to the offeror(s) who are deemed responsible in accordance with the FAR, as supplemented, whose proposal(s) conform to the solicitation’s requirements (to include all stated terms, conditions, representations, certifications, and all other information required by Addendum 52.212-1 & Addendum 52.212-2) of the solicitation and is judged by an overall assessment of the evaluation factors to represent the most advantageous offer(s) to the Government. As part of making the assessment, a best value analysis will be performed utilizing trade-offs between price and non-price factors.

(1.3) As a basis for award, trade-offs between price and non-price factors are permitted. THEREFORE, THE

GOVERNMENT RESERVES THE RIGHT TO AWARD TO OTHER THAN THE LOWEST PROPOSED PRICE.

However, the degree of importance of price as a factor in determining award could become greater depending upon mailto:larry.gillead@dcma.mil the equality of the proposals evaluated in the non-price factors. The greater the equality of proposals within the non-price factors, the more important price becomes in selecting the best value to the Government. Unreasonably proposed prices may be grounds for eliminating a proposal from competition.

(1.4) Award for All of the Work: The Government contemplates making four (4) awards as a result of this solicitation. The Government intends to evaluate proposals and award contracts without discussions with offerors

(except clarifications as described in FAR 15.306(a), Clarifications and award without discussions). Therefore, the offeror’s initial proposal should contain the offeror’s best terms from a cost or price and technical standpoint. In the event that discussions are held, a competitive range determination will be made.

(1.5) Relative Importance of Factors: DCMA anticipates awarding a contract(s) to the Offeror whose proposal is the best value to DCMA based upon an analysis of the factors below. Proposals will first be reviewed to confirm the

Offeror’s ability to meet the Go/No-Go factors provided in this solicitation (reference 52.212-1) para (7). If a proposal fails to meet any of the Go/No-Go factors provided herein, the proposal will not be evaluated further, and the Offeror will not be given further consideration for a contract award. Offerors that meet the

Go/No-Go factors will then be evaluated on all remaining factors and no one factor is determinative. For instance, DCMA may award to an Offeror based on past performance or an offeror that does not offer the lowest price or to an Offeror that is not the highest technically rated proposal. DCMA reserves the right to make no award pursuant to this solicitation.

(1.6) The Government will complete the evaluation on all proposals IAW Addendum 52.212-2. Technical Factors are listed in descending order of importance. Non-price Factors when combined are significantly more important than price. Pricing will be evaluated, but not be assigned a rating. The evaluation of the price proposal will include accuracy to the instructions as identified in Addendum to 52.212-1, completeness, and reasonableness.

(1.7) The Government will evaluate the degree to which the Offeror’s proposed technical approach demonstrates an understanding of the objectives/principles and functional and technical requirements of this solicitation and is likely to result in successful completion of the PWS and other requirements, in accordance with the PWS.

(1.8) Technical and management approaches that decrease risk to the government or exceed stated requirements may be viewed as strengths or advantages that result in higher evaluation.

(2) Technical Evaluation Factors for Award: DCMA will evaluate the Offeror’s proposed solution for the following factors:

(2.1) FACTOR 1: EXPERIENCE:

(2.1.1) Evaluation Method: GO/NO-GO FACTORS

(2.1.2) Sub-factor 1 – Contract Experience - Prime must have successfully completed at least one (1) contract in the IT Program Management Office (PMO), IT Portfolio management, IT Project or Program management support services areas within the past five (5) years with a total awarded amount (PER CONTRACT) GREATER THAN $4 million.

***Completed is defined as the base period of performance that has been performed and completed as well as, all deliverables in the base period having been accepted by the Government. The total awarded amount for the base period and any option periods shall be greater than $4 million.

(2.1.3) Sub-factor 2: Prime Experience – The Prime must have completed at least three (3) years of experience that meets all of the following:

1. Experience must be as the Prime Contractor of a federal/commercial contract similar in scope.

2. Experience can be from one or multiple contracts as the Prime.

3. Experience must be obtained prior to the proposal due date.

4. Experience from multiple concurrent contracts during the same year only count as one year.

5. Offerors shall be Capability Maturity Model Integration (CMMI) Level 3 rated and have experience as a Prime Contractor for one successful period of performance Minimum (12 Months) on any Federal/DoD or commercial contract by the close of the RFP date to be qualified to provide support for MOCAS Lifecycle Investment Management (LIM), Defense Contract Management Agency (DCMA) Office of the Chief Technology Officer, and other DoD eCommerce Project/Programs with the referenced task areas and labor categories.

(2.1.4) Sub-factor 3 – Project Experience – The Offeror must have successfully completed contracts in each of the following service areas (IT Program Management office (PMO), CPIC/Portfolio Management, IT Project AND

Program management support) within the past five (5) years (BY THE PROPOSAL DUE DATE).

1. Experience, successfully migrating persistent data storage and providing migration solutions for

Legacy or other commercially similar software.

2. Experience and how to modernize access/data for Legacy or other commercially similar software.

3. Experience in successful development and implementation of user interface of major Government or commercial systems for modernization and migration to modern web based technologies.

4. Experience in the development and implementation of various architectural approaches supporting transactional environment i.e. various architectural approaches supporting transactional versus batch processing and successful development of developing/implementing system state recovery for major systems.

5. Experience, successfully developing and implementing security solution for a “Cloud” solution (access controls, Auditability, Federal and DoD compliance, etc.).

(3) FACTOR 2: - TECHNICAL CAPABILITY/APPROACH

(3.1) The Technical Capability evaluation provides an assessment of the offeror’s capability to satisfy the

Government’s requirements. The evaluation will focus on the significant strengths, strengths, significant weaknesses, weaknesses and deficiencies of the offeror's proposal for each subfactor. The below subfactors will be evaluated together for assessment of the overall Technical Capability.

(3.2) The Technical Capability Factor/Subfactor will receive one of the combined technical/risk rating defined below. The rating includes risk associated with the technical approach. Proposal risk is used to portray the evaluation of weaknesses in the offerors’ proposals.

Rating Description

Outstanding

Proposal meets requirements and indicates an exceptional approach and understanding of the requirements. Strengths far outweigh any weaknesses. Risk of unsuccessful performance is very low.

Good

Proposal meets requirements and indicates a thorough approach and understanding of the requirements. Proposal contains strengths which outweigh any weaknesses. Risk of unsuccessful performance is low.

Satisfactory

Proposal meets requirements and indicates an adequate…