M67854-17-R-7832-0004_(Mod_Proper)_-_FINAL_issued_20OCT2017.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

This Amendment 0004 is issued to provide answ ers to questions from industry regarding this Combat Convoy Simulator Request for Proposal (see Attachment J36). In addition, this Amendment slightly modif ies Sections J, L, and M (w ith changes annoted therein). This Amendment also reissues revised Section J Attachments J1, J2, J3, J4 (w ith changes annotated therein), and J32. Furthermore, this Amendment issues new Section J Attachments J34, J35, and J36. Finally, this Amendment modif ies line items 2100AA, 2100AB, 2300AA, 2300AB, 2400AA, and 2400AB to better harmonize w ith Attachment J32.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 28

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

16C. DATE SIGNED

BY 20-Oct-2017

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 M6785417R7832

X 9B. DATED (SEE ITEM 11)

21-Aug-2017

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

20-Oct-2017

CODE

MARCORSYSCOM

ATTN:EDWARD MCGRAIL/

CT 2.7

12211 SCIENCE DRIVE

ORLANDO FL 32826

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

M6785417R7832

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

SUBCLIN 2100AA

The CLIN extended description has changed from:

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- Option Year 2. USMC Funding Sponsor (approximately 75 percent).

To:

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- Option Year 2. "1 Lot" is unit of issue due to multiple funding sponsors tied to this line item (vice, for example, having Quantity of "12" and Unit of Issue of "Month").. Billing should be in even monthly increments on a monthly basis. Reason for "1 Lot" designation has to do with dynamics of multiple funding sponsors tied to a single line item and interaction with DFAS payment office.

The pricing detail quantity has decreased by 8.00 from 9.00 to 1.00.

The unit of issue has changed from Months to Lot.

SUBCLIN 2100AB

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- Option Year 2. Navy is anticipated Funding Sponsor (approximately 25 percent).

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- Option Year 2. "1 Lot" is unit of issue due to multiple funding sponsors tied to this line item (vice, for example, having Quantity of "12" and Unit of Issue of "Month").. Billing should be in even monthly increments on a monthly basis. Reason for "1 Lot" designation has to do with dynamics of multiple funding sponsors tied to a single line item and interaction with DFAS payment office.

The pricing detail quantity has decreased by 2.00 from 3.00 to 1.00.

SUBCLIN 2300AA

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- Option Year 3. USMC Funding Sponsor (approximately 75 percent).

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- Option Year 3. "1 Lot" is unit of issue due to multiple funding sponsors tied to this line item (vice, for example, having Quantity of "12" and Unit of Issue of "Month").. Billing should be in even monthly increments on a monthly basis. Reason for "1 Lot" designation has to do with dynamics of multiple funding sponsors tied to a single line item and interaction with DFAS payment office.

The pricing detail quantity has decreased by 8.00 from 9.00 to 1.00.

SUBCLIN 2300AB

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- Option Year 2. Navy is anticipated Funding Sponsor (approximately 25 percent).

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- Option Year 2. "1 Lot" is unit of issue due to multiple funding sponsors tied to this line item (vice, for example, having Quantity of "12" and Unit of Issue of "Month").. Billing should be in even monthly increments on a monthly basis. Reason for "1 Lot" designation has to do with dynamics of multiple funding sponsors tied to a single line item and interaction with DFAS payment office.

The pricing detail quantity has decreased by 2.00 from 3.00 to 1.00.

SUBCLIN 2400AA

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- 6 Month Option to Extend Services per FAR 52.217-8. USMC Funding Sponsor (approximately 75 percent).

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- 6 Month Option to Extend Services per FAR 52.217-8. "1 Lot" is unit of issue due to multiple funding sponsors tied to this line item (vice, for example, having Quantity of "12" and Unit of Issue of "Month").. Billing should be in even monthly increments on a monthly basis. Reason for "1 Lot" designation has to do with dynamics of multiple funding sponsors tied to a single line item and interaction with DFAS payment office.

The pricing detail quantity has decreased by 3.00 from 4.00 to 1.00.

SUBCLIN 2400AB

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- 6 Month Option to Extend Services per FAR 52.217-8. Navy is anticipated Funding Sponsor (approximately 25 percent).

Combat Convoy Simulator (CCS) System Post Deployment Software Support (PDSS) in support of all systems- 6 Month Option to Extend Services per FAR 52.217-8. "1 Lot" is unit of issue due to multiple funding sponsors tied to this line item (vice, for example, having Quantity of "12" and Unit of Issue of "Month").. Billing should be in even monthly increments on a monthly basis. Reason for "1 Lot" designation has to do with dynamics of multiple funding sponsors tied to a single line item and interaction with DFAS payment office.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

SECTION J

Section J and Attachments List

J1 Statement of Work - CCS Modification (Public Release) – Revised and Reissued per RFP Amendment

J2 Performance Work Statement - CLS and PDSS (Public Release) – Revised and Reissued per RFP Amendment 0004

J3 Exhibit A - CDRLs (Public Release) – Revised and Reissued per RFP Amendment 0004 J4 CDRL Instructions (Public Release) – Revised and Reissued per RFP Amendment 0004 J5 DID List (Public Release) J6 QASP - (Public Release) J7 MCSCO 4160, Marine Corps Systems Command Disposal Planning Process - (Public Release) J8 Controlled Unclassified Information (CUI) Description, Marking, and Handling Guidance - (Public

Release) J9 TDP Option Selection Worksheet - (Public Release) J10 CDRL A00G Safety Assessment Report (SAR) Attachment - (Public Release) J11 Rights in Data (Including Technical Data, Computer Software, and Computer Software

Documentation) - (Public Release) J12 Technical Data Certification - (Public Release)* J13 CCS Scenario Description Outline - (Public Release) J14 SL-3 Template (CDRL E003) - (Public Release) J15 CCS System Performance Specification - (Public Release) J16 CDRL A00L Site Specific Health and Safety Plan (SSHSP) Attachment - (Public Release) J17 Non-Disclosure Agreement Form for Joint Battle Command - Platform (JBC-P) Software &

Instructions - (Controlled distribution) J18 MCSCO 5400.5, Naval Systems Engineering Policy and the Marine Corps Systems Command Systems

Engineering Technical Review (SETR) Handbook - (Controlled distribution)

J19 CCS Systems Engineering Plan (SEP) - (Controlled distribution)

J20 CCS Test and Evaluation Master Plan (TEMP) - (Controlled distribution) J21 Legacy CCS Drawings - (Controlled distribution) J22 Legacy CCS Operations and Maintenance Manual - (Controlled distribution) J23 Legacy CCS Safety Assessment Report (SAR) - (Controlled distribution) J24 Legacy CCS Prime Item Development Specification (PIDS) - (Controlled distribution) J25 P1346 Camp Lejeune Design Documents - (Controlled distribution) J26 Government Furnished Property (GFP) Process Flowchart - (Public Release) J27 Wage Determinations - WD 15-4389 (Rev 05) Onslow County NC; WD 15-5147 (Rev 03) Harrison

County, MS; WD 15-5625 (Rev 04) Ventura County, CA; WD 15-5629 (Rev 05) San Bernardino County, CA; WD 15-5635 (Rev 06) San Diego County, CA; WD 15-5689 (Rev 03) Honolulu County, HI

J28 Travel Template J29 Government Responses to Industry RFI (FEDBIZOPS Presolicitation M67854-17-R-7832) - (Public

Release) J30 Performance Specification and SOW elements for Evaluation J31 Past Performance Quetionnaire

J32 Pricing Template – Revised and Reissued per RFP Amendment 0004

J33 Small Business Participation Goals

J34 Affidavit of Compliance – Issued per RFP Amendment 0004

J35 Bureau of Alcohol, Tobacco, Firearms, and Explosives Letter to Marine Corps Systems Command dtd 06OCT2015 – Issued per RFP Amendment 0004

J36 Questions and Answers to Industry regarding CCS RFP M67854-17-R-7832 – Issued per RFP Amendment 0004

*Attachment J.12 “Technical Data Certification – (Public Release)” is to be competed, signed, and provided by the respective offeror to the Government for adjudication prior to Government delivery or distribution or any documentation marked “Controlled Distribution” in the above table. See also paragraph L.11 of this Request for Proposal for further details.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

SECTION L

Section L - Instructions, Conditions, and Notices to Offerors

L.1 OVERVIEW

The proposal process will be a single phase effort consisting of a written proposal leading to the award of a base period of performance to upgrade the Existing Combat Convoy Simulators (CCS) with four Post Deployment Software Support annual options. The Government intends to conduct a source selection in accordance with the competitive source selection procedures contained in Federal Acquisition Regulation (FAR) Part 15.

The Product Manager, Training Systems (PM TRASYS) is seeking potential Offerors with the capability to provide the services described in the Performance Sepcifications (PSpec), Statement of work (SOW), and Performance Work Statement (PWS).

Note: Any reference to “solicitation” or “this solicitation” shall be deemed to include all exhibits and attachments thereto.

L.2 INSTRUCTIONS FOR PREPARATION OF OFFERS

A. General Instructions.

These instructions prescribe the requirements for proposals and describe the approach for the development and presentation of proposal data. They are designed to ensure the submission of information essential to the understanding and comprehensive validation of proposals. Offerors are cautioned to follow the instructions carefully. It is an 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. The Offeror is responsible for including sufficient details to permit a complete and accurate evaluation of the proposal. Offerors shall confine their submission to essential matters, sufficient to define their offer, and provide an adequate basis for evaluation. Likewise, 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 supporting narrative to define compliance are not acceptable. Further, a proposal that merely “parrots back” the requirements of the solicitation, but fails to provide the required approach to meeting the solicitation’s requirements, is not acceptable. Finally, the Government will not assume that an Offeror possesses any capability unless identified in the proposal. An offeror who was or is an incumbent for any of the contracts being consolidated in this effort is still required to, in its proposal, meet the requirements stated in this solicitation. An Offeror shall not, based upon the Offeror’s incumbency, presume the Government’s knowledge regarding its performance, capabilities, skills, etc.

B. Proposal Format.

1. The definition of a page is a single side of paper with text, drawings, data, or similar content. Pages shall be 8.5 by 11 inches in size except for foldouts.

2. Page and Line Numbering. The Offeror shall use a standard page and line numbering system to facilitate proposal references. Number consecutive pages within each section of each volume. Charts, graphs and other insert materials shall be page-numbered as part of the page numbering system. All lines of text shall be consecutively numbered within Volumes.

3. Page Limitations. Page limitations are identified for each Volume/Section of the proposal in Table 1, above, and will be treated as maximums. If exceeded, excess pages will not be read or considered in evaluation of the proposal. Included in the page count are separate pages providing graphics, charts, illustrations and pictures. Page limitations will be checked utilizing the hard copies provided. Any Volume/Section violating limitations will be removed and any corresponding information within the CD ROM and any such information will not be considered in the evaluation. Foldouts count as two pages. Limit use of foldout pages to non-textual matter.

4. Margins and Fonts. The text margins shall be no less than one inch on all sides. Text font shall be in Times New Roman or Arial Narrow, no smaller than 12point. Font for tables, figures, embedded graphics (tables and illustrations) and other graphics shall be no smaller than 9 point Times New Roman or Arial Narrow. It is imperative that all text be legible on the original submission as well as any revised proposal submissions. Line spacing shall be no less than 1.5 lines with 6 point spacing before and after paragraphs.

5. Volumes and Binding. Bind each 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. Should the Offeror need, each section may also contain a title page/cover, table of contents, table of figures, and list of figures. Pages only used specifically for title page, table of contents, list of tables and figures information, and glossaries of acronyms and abbreviations 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 and lines sequentially. Only material required for a specific section shall be in that section.

6. Electronic Proposals. Electronic proposal volumes (except for Volume III) shall be submitted in Adobe Acrobat, Portable Document Format (PDF), Version 10.0. Volumes I and II can be submitted on the same CD-ROM, Volumes III and IV can be submitted on the same CD-ROM.

7. Attachments. Any other attached documents requested herein shall be compatible with Microsoft (MS) Office 2007 format and/or PDF. Any graphics files embedded within the MS documents shall be provided in *.jpg or *.png in order to minimize memory storage requirements for electronic files. Landscape pages shall face right. All Attachments will be counted against page limitations when applicable.

8. Compliance: Attempts to circumvent the intent of these limitations (condensed printing, oversize paper, extensive or unnecessary use of large foldouts, utilizing the incorrect volume and / or section to submit additional information, or other similar actions) may result in removal of such material from the proposal and its exclusion from the evaluation.

9. Number and Form of Copies. The Offeror shall submit its proposal in hard copy and electronic format (CD-ROMs), in accordance with the following instructions. One of the hard copy shall be designated as “Original”. Should a conflict arise between the material presented in any volumes and the CD ROMs submitted, the precedent for consideration of the proposal shall be within the written word contained in the original hard copy of the proposal. Proposals not following this format may be considered unacceptable. Offerors shall insert their company’s name in the filename. Examples below are for the ABC Company. The maximum number of pages for each volume shall be limited in accordance with the following table:

Table 1: Proposal Page Limits and Number of Copies Vol Title Max. Pages Hard Copy CD-ROM File Naming Structure

I Technical Approach Proposal See below See below See below

Sect. 1 System Performance Specification and SOW Elements

30 pages 5 copies 2 copies

ABC-Vol1-Sect1. pdf

Vol Title Max. Pages Hard Copy CD-ROM File Naming Structure

Sect. 2 Hardware Virtualization

5 pages 5 copies 2 copies ABC-Vol1-Sect2. pdf

Sect. 3 SEMP and TEPP 20 pages each 5 copies 2 copies ABC-Vol1-Sect3. pdf

Sect. 4 OSA 5 pages 5 copies 2 copies ABC-Vol1-Sect4.pdf Sect. 5 PDSS and CM 3 pages 5 copies 2 copies ABC-Vol1-Sect5. pdf Sect. 6 Cybersecurity 3 pages 5 copies 2 copies ABC-Vol1-Sect6. pdf Sect. 7 IMP and IMS No Limit 2 copies ABC-Vol1-Sect7. mpp

Sect.8 Small Business Participation

10 Pages 5 copies 2 copies ABC-Vol1-Sect8.pdf

II Past Performance Proposal

20 pages 5 copies 2 copies

Sect. 1 Recent and Relevant Past Performance ABC-Vol2-Sect1.pdf

Sect. 2 Customer Assessment List ABC-Vol2-Sec2.pdf

Sect. 3 Other Past Performance No limit ABC-Vol2-Sec3.pdf III Price Proposal No Limit 2 copies 2 copies IV Contract Information No Limit 2 copies 2 copies Sect. 1 Model Contract 2 copies 3 copies ABC-Vol4-Sect1.pdf

Sect. 2 EEO and VETS 4212 Pre-Award Clearance Information

2 copies 2 copies ABC-Vol4-Sect2.pdf

Sect. 3 Non-Disclosure Agreement for JBC-P Software

2 copies 2 copies ABC-Vol4-Sect3.pdf

Sect. 4 OCI 2 copies 2 copies ABC-Vol4-Sect4.pdf

Sect. 5

Contractor Accountability Management System Administration

2 copies 2 copies ABC-Vol4-Sect5.pdf

Sect. 6 Federal Firearms License – Attachment J34

2 copies 2 copies ABC-Vol4-Sect6.pdf

Sect.7 Small Business Participation

10 Pages 5 copies 2 copies ABC-Vol4-Sect7.pdf

L. 3 PROPOSAL CONTENT

The proposal must be prepared in 4 parts: Volume I: Technical Approach, Volume II: Past Performance, Volume III: Price, Volume IV: Contract Information. Confine all information pertaining to each indicated topic to the appropriate volume and section. Each of these volumes shall be separate and complete in itself so that evaluation of one may be accomplished independently of evaluation of the other.

L.4 VOLUME 1 - Technical Approach Proposal Instructions

The Technical Approach Proposal should reflect a clear understanding of the nature of the work being undertaken. Proposals should clearly demonstrate the Offeror’s competence and technical understanding to successfully accomplish the requirements set forth in the SOW (Attachment J1)

PWS (Attachment J2), and Performance Specification (Attachment J15). The Technical Proposal shall be divided into nine sections:

A. Section 1 System Performance Specification and SOW Elements: The Offeror shall provide their approach to satisfying the System Performance Specifications and Statement of Work (SOW) Requirements provided in Attachment J30. Please note, there are two tabs with the Attachment. Offerors shall address each “Indent 3”, “Indent 4”, and “Indent 5” provided under Attachment J30 separately, except as otherwise noted on the Attachment.

B. Section 2 Hardware Virtualization: The Offeror shall describe the approach to hardware virtualization including the impact on:

• a reduction in the number of physical servers,

• improved hardware utilization,

• performance of systems administration functions and software updates, and

• recovery from system failure.

C. Section 3 SEMP and TEPP: Utilizing the Government’s Systems Engineering Plan (SEP) (Attachment J19) and Test and Evaluation Master Plan (TEMP) (Attachment J20), the Offeror shall provide a CCS Modification Program Systems Engineering Management Plan (SEMP) and Test and Evaluation Program Plan (TEPP) per the requirements described in CDRL A003X and A004Y.

D. Section 4 OSA: The Offeror shall describe their modular open systems architecture (OSA) approach as it applies to the following key CCS architectural components:

• Image Generation System,

• Semi-Automated Force System,

• Weapons System,

• Host System

E. Section 5 PDSS and CM: The Offeror shall describe their approach to performing post-deployment software support (PDSS) and configuration management of the software product baseline.

F. Section 6 Cybersecurity: The Offeror shall describe their approach to performing Cybersecurity for the CCS Modification Program.

G. Section 7 IMP and IMS: The Offeror shall submit an Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) with their proposal.

• The Offeror shall provide an IMP as part of their proposal submittal. Note: The IMP shall be event-based, containing the events, significant accomplishments, and accomplishment criteria needed to successfully complete the CCS modification and installation. The following major events shall be the minimum provided in the IMP:

(1) PAC, SRR/SFR, CDR, SIQT, TRR, FCA, PCA, SVR, Site Installations, PAT&E, RMF Pre-SCV Validation and SCV Validation, and Component Removal and Relocation to Camp Lejeune P-1346 Simulation/Simulator Facility. Other events may be included as necessary at the discretion of the Offeror. The IMP Shall contain the following:

a. Events – logical points to assess the CCS Modification program’s progress.

b. Significant Accomplishments – two or more for each event that define the desired results prior to, or at the completion of, each event.

c. Criteria – two or more for each significant accomplishment defined as measurable information that will provide definitive evidence that a specific accomplishment has been completed. Completion of all the criteria constitutes completion of the significant accomplishment.

Each event, significant accomplishment, and criteria shall be given a unique Activity Identifier (e.g., Event A, Significant Accomplishment 01, Criteria “a” would be given the Activity Identifier “A01a”; Event B, Significant Accomplishment 03 would be given the Activity Identifier “B03”, etc.).

• The IMS shall be an integrated, logically driven network-based schedule that is vertically and horizontally traceable to the execution IMP and shall: (1) identify the activities/tasks necessary to support the events, significant accomplishments, and criteria of the IMP, with predecessor and successor activity/task relationships defined (e.g., Finish-to-Start (FS) relationship, etc.); (2) logically sequences the activities/tasks necessary to support the events, significant accomplishments, and criteria of the IMP; (3) estimates the type, quantity, and characteristics of the (a) workforce (labor categories), (b) equipment, and/or (b) raw material/supplies necessary to accomplish the activities/tasks identified in their IMS; and (4) estimates the activity/task durations associated with each activity/task identified in the IMS.

Note: Offerors shall disclose whether the durations included with their proposal are the most likely, best (optimistic), or worst (pessimistic) duration estimates. The selected method for estimating activity/task duration shall be applied consistently across the entire schedule for all activities/tasks included within the IMS.

The IMS need not cover every conceivable activity/task, but should describe a realistic and supportable schedule, illustrating the plan to meet all CCS Modification Program requirements.

The IMS shall identify significant external dependencies that involve a relationship or interface with external organizations, including Government-furnished items (e.g., decisions, facilities, equipment, information, data). The required or expected decision/delivery dates shall also be identified in the IMS. External dependencies shall be logically linked in the schedule to the appropriate IMS tasks.

The IMS shall contain all calendars that define working and non-working time periods, or other information that may impact the schedule.

If Level-of-Effort (LOE) activities/tasks are included in the IMS, they shall be clearly identified as such. LOE activities/tasks shall not impact, or be impacted by, discrete activities/tasks.

Any contingency reserve established by the Offeror within their IMS shall be explicitly identified to the Government within their proposal to include the basis of the reserve identified (i.e., percentage of time of the duration of an activity/task), and the analytical foundation for establishing the contingency reserve (e.g. Program Evaluation and Review Technique (PERT), Monte Carlo Simulation, etc.).

H. Section 8 Small Business Participation: A Small Business Subcontracting Plan must be submitted in accordance with clauses FAR 52.219-9 with Alternate II by all Large Business Offerors. No Commercial Plans (as defined by FAR 19.701) shall be accepted. Failure to submit an Individual Small Business Contract Plan shall result in the Offeror’s proposal being UNACCEPTABLE.

The Offeror shall also submit with their Individual Contract Plan:

• Percentages associated with dollar amounts provided under 52.219-9(D)(2) with Alternate II. Percentages shall be calculated by dividing the total dollars to be contracted per category by the total overall proposed price of the solicitation. If proposed percentages do not meet the goals delineated in Attachment J33, the Offer shall include an explanation describing why, and what actions are being taken to increase percentage participation to meet the goals.

• Assurances that the offeror will submit the Individual Subcontracting Reports (ISR) and Summary Subcontracting Reports (SSR) under the eSRS

• Assurances that its subcontractors agree to submit ISRs and SSRs

L.5 VOLUME II - Past Performance Proposal

A. Section 1: Recent and Relevant Past Performance.

The offeror shall identify up to three (3) of the Offeror’s most relevant Government past performance contracts and may identify up to an additional two (2) of the most relevant Government past performance contracts for each principle subcontractor. (Principal subcontractors are defined as any entity performing 15 percent or more of the identified contract Total Evaluated Price (TEP).) Past Performance contracts submitted for non-principle subcontractor WILL NOT be reviewed.

To be considered for purposes of past performance recency or relevance, a contract must have been performed in part within five (5) years of this proposal submission date as specified in Block 9 of Standard Form 33 of the RFP (i.e., any active portion of performance within five years). Preference will be given to contracts or orders with a period of performance greater than six months and within the past five years. Offerors may submit past performance contracts on which they were the prime contractor or a subcontractor, although for subcontracts there should be a demonstrated defined scope of work for which the Offeror was responsible.

For purposes of this solicitation, relevance is defined as contract performance and responsibility similar to this solicitation performed by the Offeror and the Offeror’s principle subcontractors.

Aspects of relevance include:

-the contract type,

- total dollar amount,

- dollar amount of the effort actually performed by the company for which the past performance effort is being submitted, -the location and division of the company that performed the effort, the length of the period of performance of the past performance effort, -the scope and complexity of the past performance effort to the effort proposed to be performed under this solicitation. The scope and complexity of the effort under this solicitation should address experience in integration of simulated weapon systems, vehicle host systems, semi-automated forces systems, image generation systems, exercise control/scenario generation systems, sound generation systems, communication systems, military command and control systems, or external gateways.

The Offeror must include all requested data that illustrates the adequacy of the Offeror’s (or principle subcontractor’s) various contracts selected to convey recent and relevant past performance. For each contract identified the Offeror shall provide the following information:

1. Name, title, email address, phone number and any additional information for the point of contact.

2. A description of the contract effort, relative to this solicitation, that the Offeror performed or was responsible for.

3. The relevancy of the Offeror’s, and if applicable, the Offeror’s principal subcontractors’ past performance.

4. The Offeror’s past performance in the delivery of quality supplies/services, which includes meeting technical requirements.

5. The Offeror’s past performance in meeting schedule requirements, to include on-time or late deliveries, and modifications of original schedules.

6. The Offeror’s past performance in managing the contracted effort, to include program management, subcontract management, and cooperation with the customer.

7. The Offeror’s past performance in meeting any identified Acceptable Quality Levels or minimum thresholds of performance.

8. If applicable, any improvements made during performance to resolve problems with respect to the problems or issues related to performance requirements. For each past performance problem identified, describe the status of the improvement efforts and, where applicable, demonstrate the impact that the improvement effort had on resolving the systemic problem such that it would not recur.

The offeror has the burden of providing thorough and complete past performance information. It is incumbent upon the Offeror to explain the relevance of data provided in its proposal. The Government has no duty to search for additional data to cure problems the government finds in the information provided by the offeror.

Task or delivery orders awarded under single-award indefinite delivery/indefinite delivery (ID/IQ) or Multiple-Award Contracts (MACs) will be considered standalone “contracts” for purposes of past performance evaluation. Thus, offerors may not propose an entire ID/IQ or MAC as a past performance contract reference.

In addition, regardless of relevancy, the Offeror shall provide a list of Show Cause Notices, Cure Notices and Terminations for Default received on any and all contracts, task orders, or delivery orders within the past 5 years. If the Offeror has not received any Show Cause Notices, Cure Notices or Terminations for Default in the past five years, the Offeror shall insert a statement to that effect. The list or statement shall not count against the maximum page count.

B. Section 2: Past performance Questionnaires (PPQ)

Should any of the efforts identified in Section 1 be registered in CPARS, the contractor must provide a copy of each completed annual CPARS report(s) for all performance within the above stipulated five years (for example, if an past performance submitted was awarded in November of 2014, the Government would expect two (2) completed annual reports). The Government will utilize the CPARS report(s) as Customer Assessments of contract performance.

For those contract not registered in CPARS or without a completed annual report, the Offeror shall provide the Past Performance Questionnaire (PPQ), Attachment J31 to each of the customer POCs for the identified past performance efforts. In order to expedite the assessment process, the Offeror may complete Section 2, Contract Information, of the PPQ for the convenience of the customer POC. The Offeror shall not, however, complete any other section of the PPQ. The PPQ shall be provided to the customer POC with instructions to complete and submit directly to the MCSC Contracting Office no later than the proposal due date. Electronic submission is preferred; however, hardcopy, mail or fax will be accepted.

As set forth on the PPQ, Offerors shall instruct past performance points of contact to send completed questionnaires to Mr. Erik Halverson, Contract Specialist, via email at erik.halverson@usmc.mil no later than the closing date and time specified in Block 9 on page 1 of the solicitation.

Offerors shall provide in this section of the proposal a one page list of POCs to whom Questionnaires were sent.

C. Section 3: Other Past Performance: The Government reserves the right to use contract performance data provided in the Offeror’s proposal and contract performance data obtained from other sources, including but not limited to the Government’s Contractor Performance Assessment Reporting System (CPARS) data base or the Past Performance Information Retrieval System (PPIRS). As such, Offerors shall submit a list consisting of ALL Federal Government contracts of the Prime Contractor performed in part within five (5) years of this proposal submission date as specified in Block 9 of Standard Form 33 of the RFP, that were awarded under NAICS code 541511. This information will not be evaluated, but may be utilized to narrow searches in CPARS or PPIRS.

L.6 VOLUME III - PRICE

The Offeror shall complete Attachment J32 by filling in unit Prices for FFP CLINs. Please note, Attachment J32 is locked for all NTE and NSP cells. Failure to provide pricing for all non-NTE CLINS may result in rejection of the Offeror’s proposal.

For Attachment J.32, Offerors shall also answer Q1 and Q2 utilizing the drop down menu provided. In accordance with FAR 19.1307 (and 52.219-4), the Contracting Officer shall give Offerors from HUBZone small business concerns a price evaluation preference by adding a factor of 10% to all Offerors except 1) Offerors from HUBZone small businesses concerns who have not waived the evaluation preference, or 2) otherwise successful offers from small business concerns. Therefore, for evaluation purposes, the Government will apply a 10% factor to each FFP CLIN for all those who don’t qualify for the exemptions under FAR 19.1307 (i.e., for any entity that answers “yes” for Q1 and / or “no” for Q2”).

The Offeror shall not propose any Not-To-Exceed (NTE) Cost CLINs, as those will be evaluated using the NTE amount detailed in Section B of the solicitation. The CLINs have been pre-completed in Attachment J32.

Upon successful award, the pricing submitted prior to any FAR 19.1307 increase and NTE Cost CLIN amounts shall be applied to the appropriate corresponding CLIN in Section B of any resulting contract.

L.7 VOLUME IV - Contract Information

The Offeror shall provide the documentation specified below:

A. Section 1: Model Contract.

The Offeror shall submit a signed SF33 with any/all Amendments acknowledged and all appropriate “fill-ins” clauses/provision are completed. This shall include Attachment J.11, “Rights in Data”. PLEASE BE ADVISED THIS INCLUDES ALL REPRESENTATIONS AND CERTIFICATIONS. The SF33 must be signed by an official authorized to bind the Offeror.

1. 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.

2. 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). Provide the same information for your principal subcontractors. If Offeror is a joint venture, provide a copy of the joint venture agreement. The above information will be utilized to help establish responsibility.

3. Statement that pricing shall be valid for a period of 180 days from the date of the proposal submission deadline.

B. Section 2: EEO and VETS 4212 Pre-Award Clearance Information.

To expedite the Government’s EEO pre-award clearance request process, the Offeror 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. The Government plans to request EEO clearances early in the evaluation process to avoid possible delays in making contract awards.

As legislatively mandated under 38 U.S. Code, Section 4212, codified at 41 CFR Section 61- 300, respectively, contractors and subcontractors who enter into, or modify a contract or subcontract with the federal government, and whose contract meets the criteria set forth in the above legislation/regulations, are required to report annually on their affirmative action efforts in employing veterans.

As such, Offerors shall submit a copy of the confirmation of receipt notification (e-mail) for verification of successful submission of VETS 4212 report for the prime contractor. If an Offeror, for any reason, cannot produce a confirmation notification then they may contact the VETS-4212 Service Center to request a verification search to be performed.

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

In order to perform a verification search, the VETS-4212 Service Center will need one or a combination of the following information: Company Name, Company Address, Employer Identification Number (EIN), DUNS Number. Having all of the requested data elements will provide for a more detailed search.

C. Section 3 Non-Disclosure Agreement for the Joint Battle Command – Platform

The Contractor shall submit a completed and signed Non-Disclosure Agreement for the Joint Battle Command – Platform, Attachment J17.

D. Section 4 Notification of Potential Organizational Conflict(s) of Interest Offerors are required to identify actual and potential organizational conflicts of interest (OCI) related to the services described in its proposal for itself, as well as employees, consultants and subcontractors proposed. This includes, but is not limited to:

- The existence of conflicting roles that might bias judgment; and

- Access to nonpublic information that will give the offeror an unfair competitive advantage.

If an actual or potential OCI is identified, the offeror shall submit a mitigation plan as part of its proposal. Offerors shall submit with their proposal an OCI affirmation, using the following language:

“I, (Name and Title), warrant that: 1) I am an official authorized to bind the entity; and 2) to the best of my knowledge and belief , actual and potential organizational conflicts of interest have been identified, and disclosed to the Contracting Officer (identify section of proposal) as of (Date).”

E. Section 5: Property Management System- The Offeror shall provide evidence of an acceptable Property Management System in accordance with FAR 52.245-1 (f).

F. Section 6: Federal Firearms Licensee Requirements- The contractor shall provide signed affidavit (see Attachment J34 of this RFP). evidence of (under the provisions of Title I, Gun Control Act of 1968), an active Class 9 Dealer in Destructive Devices Federal Fire Arms License (FFL) IAW the U.S. Department of Justice Bureau of Alcohol, Tobacco, Firearms and Explosives Regulations.

G. Section 7 Small Business Participation: A Small Business Subcontracting Plan must be submitted in accordance with clauses FAR 52.219-9 with Alternate II by all Large Business Offerors. No Commercial Plans (as defined by FAR 19.701) shall be accepted. Failure to submit an Individual Small Business Contract Plan shall result in the Offeror’s proposal being UNACCEPTABLE.

The Offeror shall also submit with their Individual Contract Plan:

• Percentages associated with dollar amounts provided under 52.219-9(D)(2) with Alternate II. Percentages shall be calculated by dividing the total dollars to be contracted per category by the total overall proposed price of the solicitation. If proposed percentages do not meet the goals delineated in Attachment J33, the Offer shall include an explanation describing why, and what actions are being taken to increase percentage participation to meet the goals.

• Assurances that the offeror will submit the Individual Subcontracting Reports (ISR) and Summary Subcontracting Reports (SSR) under the eSRS

• Assurances that its subcontractors agree to submit ISRs and SSRs

• Offerors are required to break out the base contract and each option in the following CLIN groupings:

- 0001 through 0011

- 0100 through 0109

- 1000 through 1010

- 1100 through 1110

- 1200 through 1210

- 1300 through 1310

- 2000 through 2003

- 2100 through 2103

- 2300 through 2303

- 2400 through 2403

- 3000

- 4000 through 4006

- 6000 through 6011

- 7000 through 7005

- 7100 through 7105

- 7200 through 7205

- 8000 through 8001

L.8 INQUIRIES

Upon release of the RFP, Requests for Clarification (RFCs) will be accepted through Monday, 1400 (local Orlando, FL time), 25 September 2017. RFCs should be submitted directly to the attention of erik.halverson@usmc.mil subject line – M67854-17-R-7832. Answers to RFCs will be provided through Amendments to the solicitation on FBO. Therefore, questions/comments shall not be marked with a restrictive legend and shall not include proprietary information. The Government is not obligated to provide responses to all RFCs, but will consider them and incorporate changes into the RFP as deemed necessary. At its sole discretion, the Government may answer untimely RFCs.

L.9 FORMAL COMMUNICATIONS

All formal communications other than for RFCs (described above) concerning this solicitation shall be submitted in writing to the Contracting Officer:

Marine Corps Systems Command

PM TRASYS

Attn: Edward McGrail Contracting Officer

12211 Science Drive Orlando, FL 32826

Or

Email: Edward.McGrail@usmc.mil Reference: Solicitation No. M67854-17-R-7832

No information concerning this solicitation, including RFC’s, will be provided via telephone.

L.10 SUBMISSION OF PROPOSAL

The minimum offer acceptance period is 180 calendar days from the date specified for receipt of offers. Proposals must be delivered to the addresses provided below, by the time and date specified in Block 9 of the SF 33 “Offer Due Date/Local (Orlando, FL) Time”. The time specified on the SF 33 is Local Time, Orlando, FL. Offers received after the time and date specified will be considered late in accordance with the parameters specified in FAR Part 15.208.

Offerors shall prominently mark all containers used for delivery of proposals with the following statement:

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

For hand carried offers:

PM TRASYS

Partnership III Bldg., 5th Floor

3039 Technology Parkway Orlando, FL 32826 Attn: Mr. Edward McGrail

For mailed offers:

PM TRASYS (Partnership III Bldg., 5th Floor)

12211 Science Drive Orlando, FL 32826 Attn: Mr. Edward McGrail

For those proposals being hand delivered to the above address, the following additional instructions apply: Notify the Contracting Officer by email that you intend to deliver the proposal and an approximate time for delivery to ensure someone is available to receive it.

When arriving at the front of the building, please call Erik Halverson (email for phone number).

The Contracting Officer or representative will arrive in the lobby to receive the proposal and issue a receipt.

Offerors are advised that proposals sent by conventional US MAIL service or shipping service company (e.g., UPS, FedEx) run the possibility that a proposal will not comply with the stated closing date/time exists due to errors by the service. In such cases, the proposal will be considered a “late submission” and treated in accordance with FAR 15.208.

L.11 REQUEST FOR TECHNICAL DATA

Due to the existence of export Controlled information, this solicitation is limited to Qualified U.S. Contractors. As such, any Qualified U.S Contractors wishing to obtain access to the Attachments of the solicitation shall complete, sign, and submit Attachment J12, Technical Data Directions for submission are included within the Attachment.

Completed and signed Attachment J12 may be submitted at any point prior to the solicitation due date. However, the Government will not entertain any requests to extend the due date of proposals due to late requests for solicitation documentation.

Once received, the Government will verify status and FedEx Contractors with a CD with all Contract Documents. Only verified companies will be sent Attachments.

L.12 ALTERNATE PROPOSALS

Offerors shall be limited to one proposal for this Solicitation. No alternate proposal(s) will be accepted.

L.13 PROPOSAL PREPARATION COSTS

This solicitation does not commit the Government to pay any cost for preparation and submission of a proposal. In addition, the Contracting Officer is the only individual who can legally commit the Government to the expenditure of public funds in connection with this acquisition.

SECTION M - EVALUATION FACTORS FOR AWARD

SECTION M

Section M: Evaluation Factors for Award

M.1 GENERAL

The Government will evaluate proposals in accordance with the evaluation criteria below. In accordance with FAR 15.306(a), Offerors may be given the opportunity for clarification of certain aspects of their proposal or to resolve minor or clerical errors.

M.2 AWARD WITHOUT DISCUSSIONS AND COMPETITIVE RANGE

DETERMINATIONS

Any proposal that does not substantially and materially comply with all of the requirements of this solicitation may be rejected and not considered for evaluation. Substantially and materially compliance includes Proposal Format, all Volumes and applicable information submitted Rejection of a proposal on this basis does not constitute creation of a “competitive range.”

In accordance with 52.215-1 (included by reference in this RFP) the Government intends to evaluate proposals and award a contract without discussions with Offerors. Therefore, the Offeror’s initial proposal should contain the Offeror’s best terms from a technical and price standpoint. The Government reserves the right to conduct discussions if the Contracting Officer later determines them to be desired.

If the Government decides to conduct discussions, then in accordance with FAR 15.306(c)(1), the Government will establish a competitive range comprised of all of the most highly rated proposals. In setting this competitive range, the Government may determine that a proposal that receives a rating of “Marginal” or “Unacceptable” for any one, or any combination, of factors is not amongst the most “highly rated” proposals and may choose to exclude it from the competitive range. Furthermore, in accordance with FAR 15.306(c)(2), if the Contracting Officer determines that the number of proposals that would be in the competitive range exceeds the number at which efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

M.3 BASIS FOR AWARD

The Government intends to award one contract from this solicitation. Award will be made to the proposal that results in the best value to the Government as defined in FAR 2.101 on the basis of a tradeoff between technical merit, past performance, compensation plan, and price.

The Government will utilize the following evaluation criteria to identify the best value. The evaluation non-price factors represent key areas of importance to be considered in the source selection decisions. The non-price factors have been chosen to support meaningful discrimination between and among competing proposals.