Amd_0001.pdf

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 extend the closing date from 30 December 2016 to 30 January 2017 by 1:00 pm local Quantico, Virginia time.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 17

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

16C. DATE SIGNED

BY 07-Dec-2016

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 M67854-17-R-2602

X 9B. DATED (SEE ITEM 11)

16-Nov-2016

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 X is extended, 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 1 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

07-Dec-2016

CODE

COMMANDER, MARCORSYSCOM

ATTN: PATRICIA PETERSON

2200 LESTER STREET

QUANTICO VA 22134

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

M67854-17-R-2602

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

SECTION L: Instructions, Conditions, and Notices to Offerors Section L-1 – Proposal Submission

I. Introduction The Government intends to meet its requirements by selecting a single contractor for award of an Indefinite Delivery Indefinite Quantity (ID/IQ) contract consisting of a 5 year ordering period, utilizing a firm-fixed-price and a cost-plus-fixed-fee type CLIN structure.

II. General This section contains general instructions for submitting proposals for this effort as defined below:

A. The proposal shall be complete and clear in all respects without the need for additional explanation or information. The proposal shall be in sufficient detail and scope to permit the Government to evaluate it with respect to the technical and cost/price factors specified under Section M of this solicitation.

B. It is the Offeror’s responsibility to submit a well-written proposal, with adequately detailed information which demonstrates its clear understanding of, and compliance with, the solicitation requirements. Offerors are cautioned against general, vague or unsubstantiated statements which prevent or render difficult the Government’s evaluation of the proposal. Statements such as “will comply,” or “noted and understood,” without a supporting narrative to define compliance, are rarely acceptable. Further, a proposal that merely “parrots back” the requirements of the solicitation, but fails to provide the required approach to meeting the solicitations requirements, is generally unacceptable.

C. Data, even though previously submitted or presumed known by the Government, cannot be considered as part of the Offeror’s proposal unless submitted with, and incorporated into, the proposal.

D. Any inconsistency, whether real or apparent, between projected performance and cost/price, should be explained in detail by the Offeror. The burden of demonstrating technical merit and adequate approach at a realistic cost/price rests with the Offeror.

E. As prescribed by 52.215-1, the Government may award on the basis of initial offers received, without discussion. Therefore, each initial offer should contain the Offeror’s best terms from a cost or price and technical standpoint. However, the Government reserves the right to conduct discussions and award on the basis of proposal revisions.

F. Offerors are expected to submit sufficient information in the format specified in this section.

Section L-2 – Offeror’s Proposal Requirements

1. Contract Award

Any Offeror that is rated “Marginal” or below in any evaluation criteria may not be considered for contract award.

Award will be to the responsive and responsible Offeror whose proposal (conforming to the solicitation) represents the best value to the Government considering the areas of Technical Approach, Management Approach, Subcontracting and Small Business Participation, Past Performance, and Price. The Government may award to other than the lowest-priced Offeror or to other than the Offeror with the highest technical rating if the Contracting Officer determines that to do so would result in the best value to the Government. The Government may reject any or all proposals if such action is in the Government’s interest.

NOTE: All or part of the successful Offeror’s technical proposal may be incorporated into the contract resulting from this solicitation. Nothing contained in the successful Offeror’s technical proposal shall constitute a waiver to any requirement of the contract. In the event of any conflict between the successful Offeror’s technical proposal and any portion of the resulting task order, the conflict shall be resolved in favor of the task order.

2. Proposal Submission

THE GOVERNMENT RESERVES THE RIGHT TO REJECT ANY PROPOSAL THAT DOES NOT

SUBSTANTIALLY COMPLY WITH THESE PROPOSAL PREPARATION INSTRUCTIONS. THIS

INCLUDES, BUT IS NOT LIMITED TO, PROVIDING COMPLETE AND COMPREHENSIVE SECTIONS

IN ALL VOLUMES.

Proposals shall be valid for a period of 180 days from date of submission.

A. Requests for Clarification (RFCs) and Intents to Propose

1) All Offeror RFCs are due by 10:00 A.M. (local time, Quantico, VA) on 30 November 2016.. Please use a table format, similar to Table 1 below, for your comments.

Table 1. Example RFC Format

Current Numbe r

Solicitation Section

Document Page / Paragra ph / Line Number

Comment/Questions

2) Information shall be sent via email (Microsoft (MS) Office Word format) to Patricia Peterson at:

mcsc_mc3_contracts@usmc.mil with a subject line of MC2S SM Support and ST/DT Support

M67854-17-R-2602-RFC.

3) Electronic submission of requests is the only acceptable method of submitting RFCs. The Government will not provide any information concerning requests for clarifications in response to telephone calls, written, or faxed copies from offerors.

4) The Government intends to publish written responses to questions via FEDBIZOPS. Should any RFC’s be received after the date stated above, the Government reserves the right not to provide an answer. If, however, in the Government’s opinion, a late RFC cites an issue of significant importance, the Government may publish as response.

B. Intent to Submit Proposal Notification

1) Please provide by 10:00 A.M. (local time, Quantico, VA) on the next business day following the

Government’s issuance of the RFC responses, an email notification of your intent to submit a proposal.

Additionally, please provide your Commercial and Government Entity (CAGE) code, Data Universal Numbering System (DUNS) number, Tax Identification Number (TIN), and information and point of contact (POC) information including name, phone number, street address, and email address. Notice of Intent to Propose should be sent via email to Patricia Peterson at mcsc_mc3_contracts@usmc.mil with a subject line of: SM Support and ST/DT Support M67854-17-R-2602 Intent to Bid.

C. Content and Organization of Proposals

1) To assure timely and equitable evaluation of proposals, Offerors must follow the instructions contained herein. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical/management requirements, and must thoroughly mailto:mcsc_mc3_contracts@usmc.mil address all evaluation factors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale in VOL II – Exceptions, Deviations, and Waivers.

a. Margins and Fonts: Proposals shall be prepared using “Arial” or “Times New Roman” 12 point font. Tables and illustrations may use a reduced font style not less than 8 point. Foldouts are not allowed, except for the Contractor Work Breakdown Structure (CWBS) (where applicable), and technical diagrams and shall be no larger than 11 inches x17 inches. Margins shall be 1 inch on all four sides. All materials submitted may be single-spaced. Offerors shall ensure that each page provides identification of the submitting Offeror in the header or footer.

b. Pages: The definition of a page is a single side of paper with text, drawings, data, or similar content. Pages shall be 8.5 x 11 inches in size.

c. Page Limitations: Page limitations are identified for each Volume/Section of the proposal, as described in Tables 2 and 3 below, and will be treated as maximums. Excess pages that exceed stated page limitations will not be read or considered in evaluation of the proposal. Included in the page count are separate pages for providing graphics, charts, illustrations, and pictures.

d. Format: The proposal must be submitted in MS Office 2010 format and/or Adobe PDF format.

Price breakdown will include MS Excel spreadsheets with formulas intact. In the event that there is a conflict between the printed copy of the proposal and the electronic copy of the proposal, the printed copy will take precedence.

e. Binding: Bind each printed proposal volume in three-ring binders. Individual sections should be removable and replaceable to the volumes. Each volume shall contain a title page, table of contents, and list of tables and figures for that volume. Include a Cross Reference Matrix showing the location where the evaluator should look in that volume for a discussion of a particular requirement (excluding price information). Pages for this information will not count against volume page limitations. Use tab separators to separate required sections within a volume. Tab separators do not count against page count. Number all pages sequentially. Only material allocated to a specific section shall be in that section.

f. Software: In accordance with DFARS 252.227-7019 (Validation of Asserted Restrictions-

Computer Software – Sep 2011), the Offeror shall identify in its proposal, to the extent feasible, any computer software that was developed at private expense, or that is anticipated for future development at private expense, and upon the use of which the Offeror desires to negotiate restrictions; for such items, the Offeror shall state the nature of the proposed restrictions. Any restrictions on the Government’s use or disclosure of computer software developed at private expense, and to be delivered under the contract shall be set forth in an agreement made part of the contract before delivery. If no such computer software is identified, all deliverable computer software will be subject to unlimited rights.

g. Copies: The Offeror shall submit one original and six printed copies of all Volumes except for Price (comprised of Volumes I - VII, as listed below in Table 2) and one original and one printed copy of the Price Volume (comprised of Volumes VIII and IX, as listed below in Table 3), each in a separate, appropriately sized, three-ring binder. The Offeror shall also submit one original and six electronic copies of the all Volumes except for the Price Volumn on CD-ROM and it shall be a searchable MS Office 2010 format. Offerors shall submit one (1) original printed copy and one (1) original on CD-ROM of the Price Volume. Price breakdown will include MS Excel spreadsheets with formulas intact.

2. Electronic file naming convention. Please name all files submitted on CD in this manner: companyname-titleofdocument-dateofdocument.xxx; where xxx is the file type (i.e. .xls or doc).

This space intentionally left blank.

Table 2: Proposal Volumns

Volume Title Max Pages

I EXECUTIVE SUMMARY Two (2); N/A for Financial Statement

II EXCEPTIONS, DEVIATIONS AND

WAIVERS One (1)

Matrix PWS Cross Reference Matrix No limit

III TECHNICAL APPROACH Forty (40)

Section 3.1 Software Maintenance and Development Approach Included in 40 page limit

Section 3.2 Sample Task Order Development Approach Included in 40 page limit

Section 3.3 Cybersecurity Posture Included in 40 page limit

Section 3.4 Software Trouble Reports (STR) Included in 40 page limit

IV MANAGEMENT APPROACH Fifty (50)

Section 4.1 Software Engineering Processes Included in 50 page limit

Section 4.1.1 Software Engineering Processes for Sample Task Orders 1 through 3 Included in 50 page limit

Section 4.2 Integrated Master Plan Separate Document in MS Project or MS Excel- No page limit

Section 4.2.1 Integrated Master Plan for Sample Task Orders 1 through 3

Separate Document in MS project or MS Excel- No page limit

Section 4.3 Organizational Structure and Staffing Plan Included in 50 page limit

Section 4.3.1 Organizational Structure and Staffing Plan for Sample Task Orders 1 through 3 Included in 50 page limit

Section 4.4 Key Personnel Included in 50 page limit

Section 4.4.1 Key Personnel for Sample Task Orders 1 through 3 Included in 50 page limit

Volume Title Max Pages

V SUBCONTRACTING & SMALL

BUSINESS PARTICIPATION

Section 5.1 Small Business Participation Plan no page limit

Section 5.2 Small Business Subcontracting Plan – LARGE BUSINESSES no page limit

VI PAST PERFORMANCE As Defined below

Section 6.1 Recent and Relevant Past Performance Information (3) page limit per each.

Section 6.2 Past Performance Questionnaire Five (5) Page Limit for each of the three questionnaires

VII GATE 1 PASS/FAIL CRITERIA As Defined below

Section 7.1 Capability Maturity Model Integration (CMMI) Maturity Level III (DEV) Appraisal Disclosure Statement (ADS)

3 Pages

Section 7.2 DCMA or DCAA Accounting System Certification to include SF 1408 2 Pages

Section 7.3 Secret Facility Clearance executed DD Form 441 Completion of Block 7 on

DD254.

2 Pages

Table 3: Cost/Price Volume Volume Title Max Pages

Volume VIII

PRICE

Section 8.1

Pricing Workbook

N/A Worksheet Provided

Section 8.2

Basis of Estimate (BOE)

No Limit

Volume IX

CONTRACT INFORMATION

Section 9.1

Model Contract

No Limit

Section 9.2

Compensation Plan

15 pages

Section 9.3

EEO/VETS 100 Pre-Award Clearance Information

1 page

3. Offerors are responsible for addressing all solicitation requirements and adequately addressing all evaluation criteria. Ensure each section adequately contains all the information necessary for evaluation.

D. Proposal Submission Location, Time, and Date

1. Proposals for the supplies/services to be provided shall be hand delivered to the address below by 1300

(1:00 P.M. local time, Quantico, VA) on 30 January 2017. Offerors shall prominently mark all containers used for delivery of proposals with the following statement:

“REQUEST FOR PROPOSAL – SOLICITATION M67854-17-R-2602

PROPOSALS SHALL BE HAND CARRIED TO:

Marine Corps Systems Command – M67854

105 Tech Parkway, 2nd Floor Stafford, VA Attn: Patricia Peterson/Jodie Shifflett, PM MC3, Code 2.2

(703) 432-9896

a. Additional Instructions: Prior to delivery please notify the Contract Specialist by email the date and approximate time for delivery to ensure someone is available to receive it. Upon arrival at 105 Tech Parkway, please call Patricia Peterson at (703) 432-9896 or Jodie Shifflett at (703) 432-9908. The Contracting Officer or representative will arrive in the lobby to receive the proposal and issue a receipt. Electronic, fax, or other forms of submission are not authorized and will not be considered.

E. Instruction for Preparation of Proposal Content

VOLUME I. EXECUTIVE SUMMARY

1. Volume I shall include the following information:

a. Confirmation: Confirmation that representations, certifications, acknowledgments, and statements have been completed electronically. (Note: Offerors must also comply with the System for Award Management (SAM) requirements of FAR 52.204-7).

b. Valid Period: Statement of the period for which the proposal is valid (not less than 180 calendar days).

c. Authorized Offeror Personnel: 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.

d. Company and Codes: Company/Division Address, Identifying Codes, and Applicable Designations.

Provide company/division's street address, county and facility code; Commercial Activity and Government Entity (CAGE) code; Data Universal Numbering System (DUNS) code; and size of business (large or small). Company POC to include Principal(s) name, position title and contact details. Provide the same information for your major subcontractors (over a 5-year ordering period).

e. Organizational Financial Information. Submit a copy of the latest available financial statement covering each company which will perform the contract. Multiple years of financial statements are not required or requested. Include any information which may have a bearing on your ability to handle the financial management of the contract. If you are proposing a joint venture, describe how you will handle financial matters. The financial statement should be included in the Executive Summary section of the proposal.

VOLUME II. EXCEPTIONS, DEVIATIONS, AND WAIVERS

1. Volume II must include a certification that it contains all exceptions, deviations, and waivers that the

Offeror takes from the provisions of the RFP and its applicable documents. An exception is where an Offeror states it will not comply with a requirement, usually involving contract terms and conditions. A deviation is where an Offeror states it will not comply with a requirement, but proposes an alternative to meet the intent of the requirement, usually involving a specification. A waiver is where an Offeror requests authorization for the Government to accept an item that will depart from specified requirements, but would nevertheless be considered suitable.

Note: Exceptions, deviations, and requests for waivers may cause proposals to be considered unacceptable.

2. The Offeror shall provide a detailed description of each exception, deviation, or request for waiver. Indicate the Offeror's difficulty with the applicable requirement and the Offeror's proposed solution. Specifically identify the portion of the RFP and the Offeror's proposal that are affected.

VOLUME III. TECHNICAL APPROACH (GATE 2)

1. PWS Cross Reference Matrix - The PWS Cross Reference Matrix maps each requirement from the PWS to the appropriate place in the proposal (Vol, Sect, Page and Paragraph) addressing the requirement.

2. Volume III shall include the Offeror’s Technical Approach for the work effort defined by the PWS and Sample Task Orders.

This section shall be limited to 40 pages, unless otherwise defined elsewhere in this solicitation, and shall consist of the technical approach to perfoming the work described in the PWS, to include the specific work efforts described in the Sample Task Orders. This part shall concisely demonstrate the Offeror’s ability to comply with the PWS.

3. Volume III, Elements: The following elements are required in the Offeror’s response to the RFP.

a. Section 3.1, Software Maintenance and Development Approach: The Offeror shall provide a detailed approach that demonstrates an in-depth and comprehensive understanding of the work to be performed based on the requirements stated in the PWS at Attachment 1.

b. Section 3.2, Sample Task Order Development Approach: The Offeror shall provide a detailed approach that demonstrates in detail the Offeror’s design approach to fulfill the requirements addressed in the Sample Task Orders identified in Exhibits E-2, E-3, and E-4 of the solicitation.

(1) Sample Task Order 1 - 64 Bit Conversion: Approach to updating the C2PC software to a 64-bit computing architecture from its current 32-bit structure.

(2) Sample Task Order 2 - MILSTD 2525D: Approach to designing a new Symbology Service build that is compliant with MIL-STD-2525D Symbology.

(3) Sample Task Order 3 - Core Connector: Approach to developing a TSOA common connector pattern which will be reusable to connect with multiple tactical data systems.

c. Section 3.3, Cyber Security Approach: The Offeror shall provide a detailed approach that demonstrates the Offeror understands Cybersecurity requirements, and has the ability to maintain the appropriate Cybersecurity posture for C2PC and TSOA.

d. Section 3.4, Software Trouble Reports: The Offeror shall provide a detailed approach that demonstrates the Offeror’s ability for diagnosing and resolving Software Trouble Reports (STR).

VOLUME IV. MANAGEMENT APPROACH

1. Volume IV shall include the Offeror’s Management Approach for the work effort defined by the PWS and

Sample Task Orders. The Offeror’s proposal shall contain the information identified in the sections below.

2. This section shall be limited to fifty 50 pages, except as specifically stated otherwise in Section L, and shall consist of the management approach for the work defined in the PWS, to include the specific work efforts defined in Exhibits E-2, E-3, and E-4 – Sample Task Orders. This part shall concisely but thoroughly demonstrate the Offeror’s ability to comply with and perform the PWS requirements and provide convincing proof that its firm has, or, has the ability to obtain personnel with relevant experience in the technical areas described in the PWS.

3. Volume IV Elements: The following elements are required in the Offeror’s response to the RFP.

a. Section 4.1, Software Engineering Processes: The Offeror shall provide a detailed approach that describes the Offeror’s Software Engineering Management processes that will be used to accomplish the work effort identified in the PWS. The proposal shall address, with specificity, the Offeror’s approach to Requirements Management, Configuration Management, Technical Data Management, Risk Management, Technical Assessments, and Decision Analyses, and shall provide sufficient detail to demonstrate an understanding of what is required in a Software Development Plan.

b. Section 4.1.1, Software Engineering Process for Sample Task Orders 1 through 3: The Offeror shall provide a detailed approach that demonstrates the Offeror’s Software Engineering Management processes that will be utilized and applied through the execution of the work effort identified in Sample Task Orders 1 through 3. The proposal shall address, with specificity, the Offeror’s approach to Requirements Management, Configuration Management, Technical Data Management, Risk Management, Technical Assessments, and Decision Analyses, and shall provide sufficient detail to demonstrate an understanding of what is required in a Software Development Plan.

c. Section 4.2, Integrated Master Plan: The Offeror shall provide an IMP in MS Project 2010 or MS

Excel 2010.

(1) The IMP should clearly and concisely describe the Offeror’s plans for producing software components, controlling, and accomplishing the work described in the PWS. The IMP should define and describe the integration of the events, accomplishments, and criteria required.

(2) The IMP shall include a draft Integrated Master Schedule (IMS) that supports the tasks defined in the PWS.

(3) The IMP shall also include a Work Breakdown Structure (WBS) to at least a Level 3 that effectively defines the scope of the work in this PWS.

d. Section 4.2.1, Integrated Master Plan for Sample Task Orders 1 through 3: The Offeror shall provide an IMP in MS Project 2010 or MS Excel 2010. The IMP should clearly and concisely describe the Offeror’s plans for producing software components, controlling, and accomplishing the work described in each Sample Task Order PWS. In addition, the IMP should define and describe the integration of the events, accomplishments, and criteria required. The IMP shall include a draft Integrated Master Schedule (IMS) that supports the task defined in the Sample Task Orders and shall include a Level 3 Work Breakdown Structure (WMS) that effectively defines the scope of the work in each Sample Task Order PWS.

e. Section 4.3, Organizational Structure and Staffing Plan: The Offeror shall provide a detailed approach that describes its proposed organizational structure and proposed staffing plan and define how this structure will support the MC2SA team. The Offeror must clearly define the relationship between the program and the overall corporate structure, reporting responsibilities, and lines of authority.

f. Section 4.3.1, Organizational Structure and Staffing Plan Sample Task Orders 1 through 3: The Offeror shall provide a detailed approach that describes its proposed organizational structure and proposed staffing plan for Sample Task Orders 1 through 3.

g. Section 4.4, Key Personnel: For the Key Personnel required in PWS 4.1.3, the Offeror shall identify and describe the proposed qualifications, certifications, education, and experience for those positions.

Additionally, the Offeror shall identify their proposed key personnel and demonstrate how their qualifications and relevant experience relates to the requirements of the PWS.

h. Section 4.4.1, Key Personnel for Sample Task Orders 1 through 3: The Offeror shall identify the Key Personnel proposed for each Sample Task Order effort. The Offeror shall describe the qualifications, certifications, education, and experience of each position and identify the proposed personnel, explaining how their qualifications and relevant experience relate to the requirements of the Sample Task Order PWS. Offerors shall also identify and describe the qualifications of other Key Personnel proposed if applicable.

VOLUME V: SUBCONTRACT & SMALL BUSINESS (SB) PARTICIPATION

Section 5.1, SB Participation Plan: The cover page for the Offeror’s Small Business Participation section shall summarize the Offeror’s SB Participation goals and SB Subcontracting percentage goals for the total requirement as follows in Table 4 below:

Table 4: Template for the Small Business Summary Table

SB Participation Plan SB Subcontracting Plan

Total Total

SB % %

SDB % %

WOSB % %

HUBZone SB % %

SDVOSB % %

a. The SB Participation Plan is plan is required from all Offerors. The Offeror’s SB Participation

Plan percentages are to be presented in terms of total dollars of work performed by each SB category, divided by the total contract value.

b. The Offeror shall identify the extent and nature of participation of SB, WOSBs, HUBZone SBs, and SDVOSBs in the performance of the proposed contract. Participation includes subcontractors or material suppliers to the prime contractor or subcontractors. Offerors shall include in the percentages their own participation as an SB, WOSB, HUBZone SB or SDVOSB.

The plan shall include, at a minimum:

The name and DUNS number (or CAGE code) of each of the firm(s) included in the plan:

A copy of the System for Award Management (SAM) profile for each of the firm(s) included in the plan;

Discussion of the specific services to be performed by each firm;

Identification of the North American Industry Classification System (NAICS) code

(appropriate to the principal nature of the planned subcontract) supporting each firm’s size status;

The estimated total dollar value subcontracted to each firm;

The estimated total dollar value subcontracted to each SB category;

The percentage of total contract value subcontracted to each firm; and The percentage of total contract value subcontracted to each SB category;

The Offeror shall provide evidence of any enforceable commitments in place between itself and the participating small businesses. Each participation percentage shall be accompanied by detailed supporting documentation regarding the individual commitments;

If applicable, for each category in which the Offeror’s SB Participation Plan contains goals below those described below, a detailed explanation as to why.

The Offeror shall include evidence of compliance with the requirements of FAR 52.219-8, “Utilization of Small Business Concerns,” and 52.219-9, “Small Business Subcontracting Plan,” in prior contracts containing the clause. This information shall be provided, at minimum, for each of the contracts discussed in the Offeror’s Past Performance volume.

a. SB Participation Plan Objectives.

The Government’s Participation objectives for this acquisition are as follows:

Small Business 16% Small Disadvantaged Business: 5% Women-Owned Small Business 5% HUBZone Small Business: 3% Service-Disabled Veteran-Owned Small Business 3%

Section 5.2, Small Business Subcontracting Plan: The SB Subcontracting Plan is a requirement for award to a large business and will be incorporated into any resultant contract. This plan is only required from an Offeror which is itself other than a SB, SDB, WOSB, HUBZone SB or SDVOSB. The SB Subcontracting Plan describes the Offeror’s approach to maximizing opportunities for small businesses in this effort, based on the subcontracted portion’s value. The Offeror’s SB Subcontracting Plan percentages are to be presented in terms of total dollars of work each SB category, divided by the total value of subcontracts.

The required elements of the SB Subcontracting Plan are set forth in FAR 52.219-9 and DFARS 252.219- 7003 and should be organized to address these elements in similar order to clearly demonstrate that each element has met the SB Subcontracting Plan objectives. All small businesses and historically black colleges or universities and minority institutions included in the SB Subcontracting Plan shall be specifically identified to facilitate compliance with DFARS 252.219-7003(g). The Offeror shall provide the CAGE code or DUNS number for each proposed subcontractor, and include identification of the NAICS code (appropriate to the principal nature of the planned subcontract) supporting each proposed subcontractor’s size status. The information in the SB Subcontracting Plan must properly correlate with that of the Offeror’s SB Participation Plan.

The Government’s subcontracting objectives for this acquisition, as follows:

Small Business 36.7% Small Disadvantaged Business 5% Women-Owned Small Business 5% HUBZone Small Business: 3% Service-Disabled Veteran-Owned Small Business 3%

Offerors proposing a SB Subcontracting Plan with percentages below the Government’s subcontracting objectives shall, for each category below the objective, explain in detal why they are unable to meet the objectives and what measures, if any, they will take to meet the objectives.

VOLUME VI: PAST PERFORMANCE

1. Volume VI shall include the Offerors Past Performance Information.

2. This section has a twenty four (24) page limit as defined.

3. Volume VI Elements: The following elements are required in the Offeror’s response to the RFP.

a. Section 6.1, Recent and Relevant Past Performance. The Offeror shall submit a minimum of three recent and relevant efforts of the prime or a proposed major subcontractor (meaning one who will perform 35% of the solicited effort), preferrably with the Department of Defense or another federal agency, and prefereably developing software of the same nature as is required by this solicitation. As a part of the past performance description, the Offeror shall explain the extent to which personnel who contributed to these previous efforts will be supporting the solicitated effort. The Offeror shall identify any corporate subsidiaries or other divisions who were involved in performing the reported effort, as well as any other major subcontractors. Offerors with no relevant past performance on federal contracts may submit for efforts performed for other entities instead.

(1) “Recent” is defined as contracts, whether ongoing or completed, with at least 12 months of performance occurring during the 3 years preceding the proposal submission date.

(2) Past Performance efforts shall be described in sufficient detail to allow for comparison of the prior performance to the solicitation’s PWS. As a result, it will be important to identify what portion of the solicited effort will be performed by each entity for whom past performance information is submitted.

(3) Offerors shall submit this information in the following format:

Identify, by name, which company (prime or major subcontractor) the past performance is for and whether the past performance was as a prime or subcontractor. Provide the CAGE code for the referenced company.

Customer Name, address, and telephone number.

Customer’s Procuring Contacting Officer’s name, telephone number, and FAX number.

Contracting activity’s technical representative or contracting officer representative

(COR), telephone number, and FAX number.

Customer Program Manager, telephone number and FAX number.

Government contract administration activity and the name, telephone number, and FAX number of the administrative contracting officer (ACO) and the Chief of Program and Technical support.

Contract number.

Customer Program title.

Contractor/subcontractor place of performance.

Contract type.

Period of performance.

Total contract amount and price per year obligated.

Final or projected price or cost.

Offeror’s description of the effort, highlighting similarities and differences between the size, scope and complexity of that experience and that of the solicited effort.

Offerors should pay particular attention to the solicited effort’s PWS and provide sufficient detail in the description to readily allow for a relevance comparison.

Schedule and Cost Performance. Provide a narrative of the objectives achieved and any cost growth or schedule delays encountered. For any Government contracts that did not meet original requirements with regard to schedule and cost performance, provide a brief explanation for such shortcomings and any demonstrated corrective actions taken to avoid recurrence. Explain those processes now in place to prevent past problems and ensure such problems do not affect performance on this proposed contract. Identify, provide and explain any cure notices received.

Provide the above required information for any and all of the Offeror’s Government contracts, whether or not similar to the proposed effort, that were terminated, in whole or in part, for any reason during the past three years. Include those efforts currently in the process of such termination.

Offerors shall include in their proposal the written consent of their proposed significant subcontractors to allow the Government to discuss that subcontractor’s past performance evaluation with their respective Offeror during negotiations (Note: Written permission from subcontractors is excluded from the page count).

Section 6.2, Past Performance Questionnaire (PPQ). The Offeror shall provide the Past Performance Questionnaire, Exhibit E-1, to each of the customer POCs for their respective identified past performance efforts. In order to expedite the assessment process, the Offeror may complete Section II, General Information, of the Past Performance Questionnaire for the convenience of the customer POC. The Offeror shall not, however, complete any other section of the Past Performance Questionnaire. The questionnaire shall be provided to the customer POC with instructions to complete and submit the completed form directly to the MCSC Contracting Office no later than the proposal due date. Electronic submission to mcsc_mc3_contracts@usmc.mil is preferred; however, hardcopy mail or fax will be accepted. If by mail or fax, the submission should be received by the proposal due date and the Contracting Officer shall be notified in advance that the PPQ will be mailed or faxed. The Offeror shall submit with its proposal a list of the customer POCs that were provided a Past Performance Questionnaire. The Offeror shall provide the performing contractor name (prime/subcontractor), DUNS Number, and Contract Number in their email.

VOLUME VII: MANDATORY REQUIREMENTS–PASS/FAIL CRITERIA (GATE 1)

1. As stated above, the Government will evaluate proposals using an evaluation process that consists of two

Gates, as described in Section M.

2. This section has page limits, as defined.

3. Volume VII Elements: The following documents shall be provided with the Offeror’s proposal for evaluation under the Gate 1 process:

mailto:mcsc_mc3_contracts@usmc.mil

a. Section 7.1, CMMI Maturity Level III (DEV): Offerors shall provide a copy of its Capability Maturity Model Integration (CMMI®) Maturity Level III (DEV) CMMI Institute Appraisal Disclosure Statement (ADS) confirming the Level III certification. The ADS must be for the Offeror (rather than a subcontractor) and be for the specific division/location of the company that will be performing the contract. An ADS from a subcontractor or team member is unacceptable.

Section 7.2, Accounting System Certification: The proposal shall include valid documentation from DCMA or DCAA, or another Federal audit agency evidencing that the Offeror has an adequate accounting system for performing Government cost type contracts. The Offeror shall complete Attachment 8 –SF 1408 Pre-award Survey of Prospective Accounting System Checklist with supporting documentation. If the Offeror is proposing subcontractor(s), and a cost-reimbursement subcontract type will be used, the proposal shall include that documentation for the subcontractor(s).

Offerors are cautioned that determination of the adequacy of the accounting system must be accomplished to be eligible for contract award. Therefore, Offerors shall be prepared to support DCAA audits upon the initiation of the audit.

c. Section 7.3, Secret Facility Clearance: The proposal shall include the Offeror’s current Secret Facility Clearance. The submission shall include a fully executed DD Form 441 issued by the Defense Security Services (DSS). Offerors shall complete block 7 of the DD Form 254, (Attachment 2). In addition, Offerors shall provide, if applicable, an SF328.

VOLUME VIII: PRICE PROPOSAL

1. Volume VIII shall include the Offeror’s Price Proposal.

2. The purpose of this section is to provide offerors with Ground Rules and Assumptions and instructions on preparing price proposals.

a. Section 8.1, Ground Rules & Assumptions:

(1) The Offeror’s price proposal shall be submitted both in the Model Contract and Attachment 5, Pricing Workbook, as instructed below. The Offeror shall submit pricing for every FFP CLIN with the exception of CLINs 1014 through 1020, in the Model Contract; failure to do so may result in the proposal being ineligible for award.

(2) As this is a competitive acquisition with adequate price competition anticipated, any cost/price documentation requested need not be certified cost or pricing data, as described in FAR 15.406-2 for CLINs 1001 through 1013 and the corresponding ordering period CLINs. In the event that adequate price competition does not exist for the FFP CLINs under this effort, after receipt of proposals, the Government may request additional cost or pricing data as necessary from the Offeror, subcontractors and team members, pursuant to FAR 15.403-4.

(3) If subcontractors are proposed, subcontractors shall provide all of the same information and rates required of the prime, as instructed below, in Attachment 5, Pricing Workbook Subcontractor and Sample Task Order Pricing. Subcontractors may submit Attachment 5, Pricing Workbook, directly to the Government if data is determined to be proprietary to the company. Subcontractors shall indicate who their prime contractor is within their submittal and the Workbook shall be submitted on or before the Proposal Due Date and Time specified above to: mcsc_mc3_contracts with a subject line of “MC2S SM Support and ST/DT Support M67854-17-R-2602-Subcontractor Pricing.” NOTE: It is the Prime Offeror’s RESPONSIBLITY to ensure all proposed Subcontractors who choose to submit a Pricing Workbook separately follow these instructions and SUBMIT their Pricing Workbook on or before the Proposal Due Date and Time.

(4) The Offeror shall ensure the submitted files are accessible and legible for the Government. In the event a file cannot be opened or read, the Government reserves the right to find the submission non-compliant and ineligible for evaluation and award.

(5) No cost or pricing information shall appear in any volume other than the Price Volume.

(6) Pre-contract costs are not authorized.

b. Section 8.2, Pricing Workbook: Attachment 5 to the Solicitation, entitled “Pricing Workbook,” is an

Excel workbook consisting of 4 worksheets. Tab 1 – Instructions, Tab 2 –Contract FFP CLINS PRIME Tab 3 –Contract FFP CLINS SUB and Tab 4 Labor Rates and Categories.

(1) Prime Contractor Contract FFP CLINs Worksheet: Offerors shall submit pricing for FFP CLINs

1001 through 1013 for all ordering periods. Pricing under this worksheet shall match pricing provided in the Model Contract, Schedule B, CLINs 1001 through 1013 and the corresponding ordering period CLINs. CLIN 1020, within this worksheet, provides the Government’s NTE ODC/Travel estimate.

• Offerors shall provide backup documentation in a separate spreadsheet format consisting of its Basis of Estimate (BOE) supporting the costs/prices provided in the Contract FFP CLINs.

Any additional supporting documentation may be provided at the Offeror's discretion. (There is no page limit for the Pricing Proposal). The BOE shall include all cost elements. Labor Rates and Categories for the FFP CLINs shall align to the Offeror’s Proposed Contract Labor Rates and Categories Worksheet.

(2) Contract Labor Rates/Categories Worksheet: Under this Worksheet offerors shall submit the following:

• Labor Categories

• Roles and Responsibilities

• Education

• Years of Experience

• 2016 hourly Compensation Rate

• 2016 hourly Fringe

• Years 1 through 5 Fully Burdened Rates

(3) The Government intends to utilize the proposed fixed hourly burdened rates and individual labor categories for all task orders awarded under the contract. While the Offeror will be limited, in its task order proposals, by those proposed rates, the Government does intend to seek discounts on those rates, as appropriate. Therefore, the Offeror shall provide, in Attachment 5 – Pricing Workbook, ALL labor categories and fully burdened rates necessary to complete the requirements identified in the PWS for each CLIN, whether or not every category will be proposed for one of the three Sample Task Orders. Labor rates are fixed for all contract ordering periods, and are NOT subject to any escalation through the course of the ordering periods. The Government intends on incorporating the Labor Rates/Categories as an attachment to the awarded contract.

(4) The Offeror shall provide separate spreadsheets consisting of its BOE supporting the Labor Rates.

The BOE shall include all cost elements included in the fully burdened labor rate.

Section 8.3 Sample Task Orders 1 through 3 Pricing: Offerors shall provide, in a separate Excel spreadsheet, pricing information for EACH Sample Task Order (64 Bit Conversion, MILSTD 2525D, and Core Connector).

Offerors should undertand that the Government may award any or all of the Sample Task Orders (1-3) as proposed.

The period of performance for each Sample Task is 1 year. The Offeror shall provide sufficient information to support its Sample Task cost/price for each Sample Task, as well as an explanation of all ground rules and assumptions that impact the cost/price estimates. Offerors are hereby notified that pricing for the Sample Task Orders need not be certified but the Offerors cost proposal shall include supporting information for each cost element consistent with offeror's cost accounting system. The supporting breakdown should include such elements as materials, direct labor, indirect cost, and other costs such as travel. The Offeror shall provide exhibits as necessary to substantiate each cost element. Should rates be used in the proposal which are not DCAA approved, the Offeror shall provide complete documentation and the rationale for their use at time of proposal submission. In addition, the Offeror’s cost proposal shall include:

(1) Offeror’s spreadsheet shall identify each Sample Task Order separately and provide the following information for itself as the PRIME and all proposed SUBCONTRACTOR(s):

• The Offeror shall fully disclose the build-up of cost/price proposed for each Sample Task. The

Sample Task Order is Cost Plus Fixed Fee (CPFF) and cost (unburdened) for any proposed Travel or Material.

• The Offeror shall identify a fixed hourly burdened rate for each individual labor category necessary to complete the requirements identified for each Sample Task Order PWS.

• The Offeror shall identify the hours to be performed by each identified labor category in performance of the requirements.

• The Offeror shall identify the overall price per labor category.

VOLUME IX: CONTRACT INFORMATION

1. The purpose of this section is to provide information to the Government for preparing the contract document and supporting file. Failure to provide all portions may result in rejection of the proposal without evaluation.

2. Page limits are as defined.

3. Information required includes:

a. Section 9.1, Model Contract. The Offeror's proposal shall include a signed copy of the Base Contract’s SF33, with blocks 12 through 17 completed and with all Amendments acknowledged.

(1) Each page of the Offeror’s proposal shall contain the following legend at the bottom: Source

Selection Information - See FAR 2.101 and 3.104.

b. Section 9.2, Compensation Plan: The Offeror shall submit a total compensation plan setting forth:

(1) Proposed salaries (i.e. non burdened hourly rates) for each of the labor categories proposed within the pricing volume;

(2) Fringe benefits provided in both an hourly rate as well as an itemized list of benefits;

(3) Fully burdened hourly rates;

(4) Supporting documentation of sufficient compensation. Documentation to include data (such as recognized national and regional compensation surveys and studies of professional, public, and private organizations) used in establishing the total compensation structure.

c. Section 9.3 Equal Employment Opportunity (EEO) and VETS 100 Pre-award Clearance

Information: To expedite the Government’s EEO pre-award clearance request process, the prime contractor shall include a list of all proposed subcontractors with a proposed subcontract value estimated at $10 million or more, to include the following information: Name, address, individual’s name/point of contact, and telephone number, and DUNS Number. The Government plans to request

EEO clearances early in the evaluation process to avoid possible delays in making contract awards (page limit not applicable).

(1) In addition, Offerors shall submit a copy of the confirmation of receipt notification (e-mail) for verification of successful submission of VETS 100 report for the prime contractor and any subcontractor with a proposed subcontract value estimated at $100,000 or more. If a contractor, for any reason, cannot produce a confirmation notification, then they may contact the VETS 100 Service Center to request a verification search to be performed.

Phone: (866) 237-0275 Email: VETS100-customersupport@dol.gov

(2) Please note that to perform a verification search, the VETS 100 Service Center will need one, or a combination of, the following information. Having all of the requested data elements will provide for a more detailed search.

• Company Name

• Company Address

• Employer Identification Number (EIN)

• DUNS Number

Section L-3 – INTENT TO INCORPORATE CONTRACTOR’S TECHNICAL PROPOSAL

1. All or part of the successful Offeror’s technical proposal may be incorporated in any contract or task order resulting from this solicitation. Nothing contained in the successful Offeror’s technical proposal shall constitute a waiver to any requirement of the contract or task order. In the event of any conflict between the successful Offeror’s technical proposal and any portion of the contract or task order, the conflict shall be resolved in favor of the contract or task order.

(End of Summary of Changes)