M67854-22-R-2076 Amendment 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:

1. Extend the closing date for solicitation M67854-22-R-2076 From: 1:00 PM 08 April 2022 To: 1:00 PM 15 April 2022;

2. To update Attachment 8 in Section J by removing documents from the TSOA section that are outdated and no longer apply to this requirement, to update the delivery of the source code, and to update the date of Attachment 8;

3. To add Attachment 13 in Section J to answ er questions in response to the solicitation; and

4. Update Sections L and M.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 32

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

16C. DATE SIGNED

BY 09-Mar-2022

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 M6785422R2076

X 9B. DATED (SEE ITEM 11)

14-Feb-2022

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

09-Mar-2022

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:

M6785422R2076

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

SECTION J

SECTION J ATTACHMENTS AND EXHIBITS

Attachment Document Pages Date

1 Performance Work

Statement

32 11 Feb 2022

2 DD254 6 13 Jan 2022

3 Pricing Workbook 5 11 Feb 2022

4 Instructions to Request

Solicitation Supporting

Documentation

3 11 Feb 2022

5 SF1048-14 Preaward

Survey of Prospective

Contractor Accounting

System

2 11 Feb 2022

6 RESERVED N/A N/A

7 MCSC Controlled

Unclassified Information

(CUI) Guidance

11 Feb 2022

8 Solicitation Supporting

Documentation

1 09 March 2022

9 Sample Task Order 1

C2PC Security Manager

Update PWS

6 11 Feb 2022

10 Sample Task Order 1

Security Manager Jazz

78 11 Feb 2022

11 Sample Task Order 2

C2PC MIL-STD 2525D

Upgrade PWS

2 11 Feb 2022

12 Sample Task Order 3

TSOA Service Oriented

Infrastructure PWS

3 11 Feb 2022

13 Questions and Answers 3 09 March 2022

Exhibit A Contract Data

Requirements List A001 –

A00C

36 02 Feb 2022

Exhibit B Contract Data

Requirements List B001 –

B003

9 02 Feb 2022

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

SECTION L

SECTION L: Instructions, Conditions, and Notices to Offerors

L-1 – PROPOSAL SUBMISSIONS

L-1.1 INTRODUCTION

The Government intends to meet its requirements by selecting a single contractor for award of an

Indefinite Delivery Indefinite Quantity contract consisting of a five, 1-year ordering periods, utilizing Firm-Fixed-Price (FFP), Cost-Plus-Fixed-Fee (CPFF), and Cost Reimbursable Contract

Line Item Numbers (CLINs).

L-1.2 GENERAL

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

1) Offerors requesting the restricted documents on SAM.gov, must have a completed Use and

Non-Disclosure Agreement (NDA) on file, prior to receiving access to the controlled attachments to the Request for Proposal (RFP). The NDA will be posted on SAM.gov as an unrestricted document and can be downloaded, completed, signed, and then submitted to

Patricia Peterson, Lisa Burns, and Taylor Cross at Patricia.Peterson@usmc.mil, Lisa.Burns@usmc.mil, and Taylor.Cross@usmc.mil.

2) A single concise and comprehensive proposal is required. Organization, clarity, accuracy of information, relevance, and completeness are of prime importance. The proposal shall be complete and clear in all respects without the need for additional explanation or information.

The proposal shall be drafted in sufficient detail and scope to permit the Government to evaluate it with respect to the technical and price factors specified under Section M of this solicitation.

3) It is the offeror’s responsibility to submit a well-written proposal which demonstrates its clear understanding of, and compliance with, the solicitation requirements. Offerors are cautioned against general, vague, or unsubstantiated statements; statements such as “will comply,” or

“noted and understood,” without further elaboration may cause an offeror to be evaluated as unacceptable. The Government will not assume that an offeror possesses any capability, demonstrates understanding of a requirement, or commits to an approach that is not specifically described in its proposal. Proposals that merely restate the requirement or state that the requirement will be met, without providing supporting rationale or substantiating data, are rarely acceptable.

4) Proposals submitted for consideration for award must address the full scope of the solicitation. Proposals which address only part of the solicitation will be considered mailto:Patricia.Peterson@usmc.mil mailto:Lisa.Burns@usmc.mil mailto:Taylor.Cross@usmc.mil unacceptable. Limits on the number of pages in the proposal have been imposed, as indicated in the sections below. In the event an offeror exceeds the maximum page limit, the

Government will evaluate only the number of pages prescribed (starting with page one and continuing until the maximum number is reached) for the respective volume. All pages, or any other material, in excess of the maximum number of pages stated, will not be evaluated.

5) 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.

6) Any inconsistency between proposed 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.

7) As prescribed by Federal Acquisition Regulation (FAR) Clause 52.215-1, the Government may award on the basis of initial offers received, without discussions. Therefore, each initial offer should contain the offeror’s best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions and award on the basis of proposal revisions. Each offeror may submit only one proposal in response to this solicitation.

Proposals shall not contain classified information. Please refer to Attachment 2, Security

Classification Guide, to ensure classification compliance.

L-1.3 OFFEROR’s PROPOSAL REQUIREMENTS

L-1.3.1 QUESTION AND ANSWER PERIOD

A. Questions

1) All questions regarding the solicitation documents are due no later than 10:00 A.M. (local time, Quantico, VA) on 28 February 2022.. Please use a table format, similar to Table 1 below, when submitting your questions. Do not bundle multiple questions into one.

Table 1: Example Format

Question

Number

Solicitation

Section

Document Page /

Paragraph / Line

Number

Comment/Questions

2) Questions shall be sent via email (Microsoft (MS) Office Word format) to Patricia Peterson at Patricia.Peterson@usmc.mil, Lisa Burns at Lisa.Burns@usmc.mil, and Taylor Cross at

Taylor.Cross@usmc.mil with a subject line of TSA&S SM Support and ST/DT Support

M67854-22-R-2076 Offeror Questions.

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

mailto:Patricia.Peterson@usmc.mil

B. Answers

1) The Government intends to publish written vendor questions and Government answers via

SAM.gov. The Government reserves the right not to answer irrelevant or late-submitted questions, to combine or edit questions, and to include questions it has drafted to clarify matters for offerors.

L-1.3.2 PROPOSAL SUBMISSION

A. The Government does not anticipate that offerors will need to submit cost or pricing data, as defined in FAR Section 2.101; however, the Government reserves the right to require the submission of Certified Cost or Pricing Data or Other Than Certified Cost or Pricing Data if it is deemed necessary for the purposes of evaluation and negotiation. By submission of an offer to this solicitation, the offeror acknowledges that Certified Cost or Pricing Data or

Other Than Certified Cost or Pricing Data may be required. The decision for the need of

Certified Cost or Pricing Data or Other Than Certified Cost or Pricing Data will be solely at the discretion of the Contracting Officer. In the event that Cost or Pricing Data or Other

Than Cost or Price Data are required, the requirement shall be in accordance with FAR

Clause 52.215-20.

B. Proposals in response to this solicitation must be valid for 180 calendar days from date of submission.

THE GOVERNMENT RESERVES THE RIGHT TO REJECT ANY PROPOSAL, OR PART

THEREOF, THAT DOES NOT COMPLY WITH THESE PROPOSAL PREPARATION

INSTRUCTIONS. THIS INCLUDES, BUT IS NOT LIMITED TO, PROVIDING COMPLETE

AND COMPREHENSIVE SECTIONS IN ALL VOLUMES. ANY PERCEIVED ATTEMPT

BY THE OFFEROR TO CIRCUMVENT SUBMISSION REQUIREMENTS OR ACTION

THAT RENDERS IT MORE DIFFICULT FOR THE GOVERNMENT TO EVALUATE

PROPOSALS ON A CONSISTENT BASIS MAY RESULT IN THE PROPOSAL BEING

REJECTED.

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

2) 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 (where applicable), and technical diagrams must be 75% picture and 25% verbiage and shall be no larger than 11 inches x 17 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 and a page number in the footer.

3) 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. Foldouts are allowed for technical diagrams, shall be no larger than 11 inches x 17 inches, and shall be counted as two pages.

4) Page Limitations: Page limitations are identified for each Volume/Section of the proposal, as described in Table 2 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 pages providing graphics, charts, illustrations, and pictures.

5) Format: The proposal must be submitted in MS Office 2016 format and/or Adobe PDF format. The Price breakdown submitted shall 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 electronic copy will take precedence.

6) Binding: Bind each printed proposal volume in three-ring binders. Individual sections should be removable and replaceable within the volumes. Each volume shall contain a title page, table of contents, and list of tables and figures for that volume Use tab separators to separate required sections within a volume. Tab separators also do not count against page count.

Number all pages sequentially. Only material allocated to a specific section shall be in that section; i.e., the pages in a given section shall address only the topic specified to be addressed in that section.

7) Technical Data and Software: In conformance with Defense Federal Acquisition Regulation

Supplement (DFARS) 252.227-7017, Identification and Assertion of Use, Release, or

Disclosure Restrictions, the offeror shall identify, to the extent known at the time its offer is submitted to the Government, the technical data or computer software that the offeror, its subcontractors or suppliers, or potential subcontractors or suppliers, assert should be furnished to the Government with restrictions on use, release, or disclosure. The offeror’s assertions, including the assertions of its subcontractors or suppliers or potential subcontractors or suppliers, shall be submitted as an attachment to its offer in the format prescribed at DFARS 252.227-7017(d), dated and signed by an official authorized to contractually obligate the offeror.

8) Copies: The offeror shall submit one printed copy of Volumes I-V and VII, as listed below in

Table 2, in one three-ring binder, and one printed copy of Volumes VI, VIII and IX in a separate three-ring binder. An electronic copy of all Volumes, each as a separate file, will be submitted through Department of Defense (DoD) Secure Access File Exchange (SAFE) at https://safe.apps.mil/, as described below.

9) Electronic file naming convention: Please name all electronic files submitted via DoD

SAFE in this manner: company name - document title.xxx; where xxx is the file type (i.e., .xls or .doc).

https://safe.apps.mil/

D. Pricing Information: NO PRICING INFORMATION OF ANY KIND SHALL BE

INCLUDED IN ANY VOLUME EXCEPT VOLUMES VIPRICE, VOLUME VIII SMALL

BUSINESS, AND VOLUME IX CONTRACT INFORMATION.

E. Supporting Solicitation Documentation: For any documentation that will be needed to prepare proposals listed in Attachment 8 of Section J of the solicitation, please email a request to Patricia Peterson at Patricia.Peterson@usmc.mil, Lisa Burns at Lisa.Burns@usmc.mil, or

Taylor Cross at Taylor.Cross@usmc.mil.

F. Proposal Submission Location, Time, and Date:

1) Proposals shall be delivered as detailed below by 1:00 p.m. (local time, Quantico, VA) on

15 April 2022. Any proposal received after such date and time will be considered a late submission. Late submissions will be treated in accordance with FAR Clause 52.215-1(c)(3).

Proposals shall be valid for a period of not less than 180 days from the submission deadline listed above. Offerors shall prominently mark all containers used for delivery of proposals with the following statement:

“REQUEST FOR PROPOSAL – SOLICITATION M67854-22-R-2076”

PRINTED PROPOSALS SHALL BE HAND CARRIED TO:

Marine Corps Systems Command – M67854

105 Tech Parkway, 2nd Floor

Stafford, VA

Attn: Patricia Peterson/Lisa Burns/Taylor Cross

(703) 432-8738/(703) 432-2874

Additional Instructions: Prior to delivery of the paper copy, please notify the Contract Specialist by email with the date and approximate time for delivery to ensure someone is available to receive the proposal. Upon arrival at 105 Tech Parkway, please call Patricia Peterson at (703)

432-8738 or Lisa Burns at (703) 432-2874. The Contracting Officer or representative will arrive in the lobby and receive the proposal, establishing the time of receipt, and will issue a receipt.

Other forms of submission are not authorized and will not be considered.

2) The ELECTRONIC COPY SHALL BE DELIVERED VIA DOD SAFE, accessible at https://safe.apps.mil. The offeror shall email patricia.peterson@usmc.mil and taylor.cross@usmc.mil requesting a drop off be created, and provide a name and email for the point of contact (POC) that should receive the drop off request. An automated email will be sent notifying the POC the drop off is open along with the required verification code. The drop off is valid for 14 days upon creation. Directions on how to execute the drop off, once the POC has received the request, can be found in the DoD SAFE User Guide published at https://safe.apps.mil. Ensure to allow sufficient time for proposals to be uploaded to DoD SAFE.

Proposals must be fully uploaded no later than the delivery date and time listed above.

mailto:Taylor.Cross@usmc.mil mailto:patricia.peterson@usmc.mil mailto:taylor.cross@usmc.mil https://safe.apps.mil/

Table 2: Proposal Volumes

Volume Title Max Pages

I EXECUTIVE SUMMARY

2 Pages, excluding the

Financial Statement

II

EXCEPTIONS, DEVIATIONS

AND WAIVERS

No Limit

III PASS/FAIL CRITERIA – As Defined Below

Section 3.1 Accounting System Certification 2 Pages

Section 3.2 Secret Facility Clearance 2 Pages

IV TECHNICAL APPROACH – As Defined Below

Matrix PWS Cross Reference Matrix NOT Included in 25 page limit

Section 4.1 Software Maintenance and

Development Approach Included in 25 page limit

Section 4.1.1 Agile Development Process Included in 25 page limit

Section 4.1.2 Systems Engineering Practices Included in 25 page limit

Section 4.1.3 System Test and Delivery Included in 25 page limit

Section 4.1.4 Three Sample Task Order

Development Approaches Included in 25 page limit

Section 4.2 Cybersecurity Approach Included in 25 page limit

Section 4.3 Software Trouble Reports (STR) Included in 25 page limit

V MANAGEMENT APPROACH As Defined Below

Matrix PWS Cross Reference Matrix NOT included in 20 page limit

Section 5.1 Systems Engineering Processes Included in 20 page limit

Section 5.1.1

Systems Engineering Processes for Sample Task Orders 1 through

Included in 20 page limit

Section 5.2

Integrated Master Plan, including

Integrated Master Schedule and

Work Breakdown Structure

Separate Document in

MS Project or MS Excel-

No page limit

Section 5.2.1 Integrated Master Plan for

Sample Task Orders 1 through 3

Separate Document in

MS project or MS Excel

- No page limit

Section 5.3 Staffing Plan Included in 20 page limit

Section 5.3.1 Staffing Plan for Sample Task

Orders 1 through 3 Included in 20 page limit

Volume VI PRICE/COST As Defined Below

Section 6.1 Pricing Workbook

Basis of Estimate (BOE)

Workbook

Provided/BOE 5 pages

BOE: 5 pages Section 6.1.1 Sample Task Orders 1 through 3

Pricing No Limit

VII PAST PERFORMANCE As Defined below

Section 7.1 Past Performance 15 Pages; No more than

5 references

VIII SMALL BUSINESS 5 Pages

Section 8.1 Small Business Achievements Included in the 5 page limit

Section 8.2 Small Business Participation and

Commitment Strategy

Included in the 5 page limit

Section 8.3

Small Business Subcontracting

Plan

(Applies Only to Large

Businesses)

Included in the 5 page limit

Volume IX

CONTRACT INFORMATION

As Defined Below

Section 9.1 Model Contract No Limit

Section 9.2 Model Compensation Plan 5 pages

Section 9.3 EEO/VETS 4212 Pre-Award

Clearance Information 1 page

INTENT TO INCORPORATE PORTIONS OF CONTRACTOR’S PROPOSAL

Portions of the successful offeror’s proposal may be incorporated in any contract resulting from this solicitation, based solely on the Government’s discretion. Nothing contained in the successful offeror’s proposal shall constitute a waiver to any requirement of the solicitation or other terms of the contract.

L-1.4 INSTRUCTIONS FOR PREPARATION OF PROPOSAL CONTENT

L-1.4.1 VOLUME I. EXECUTIVE SUMMARY

A. Volume I shall include the following information:

1) Confirmation: Offerors shall confirm that representations, certifications, acknowledgments, and statements have been completed electronically in the System for Award Management

(SAM), in accordance with FAR 52.204-7.

2) Valid Period: Include a statement of the period for which the proposal is valid (not less than

180 calendar days).

3) Authorized Offeror Personnel: Provide the name, title, email address, and direct telephone number of the company/division point of contact for your proposal who is authorized to contractually bind, and negotiate on behalf of, your company. Additionally, please provide an alternate point of contact (with the same contact information) who may be reached for general matters, or in the absence of the individual listed above.

4) Company/Division Address, Identifying Codes, and Applicable Designations: Provide the company/division's street address, county and facility code, Commercial Activity and

Government Entity (CAGE) code, Data Universal Numbering System (DUNS) code, Tax

Identification Code (TIN), and size of business (large or small). Provide the same information for your major subcontractors, projected for the 5-year ordering period.

5) Organizational Financial Information: Submit a copy of the latest available financial statement covering each company, prime and subcontractor, 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.

Subcontractors may submit their financial statements directly to Patricia Peterson at patricia.peterson@usmc.mil and Taylor Cross at taylor.cross@usmc.mil with a subject line of: Financial Statement for Contractor XX in Support M67854-22-R-2076.

6) Agency POCs: Identify the offeror’s cognizant DCMA, DCAA, and Defense Finance and

Accounting Services payment office POCs.

L-1.4.2 VOLUME II. EXCEPTIONS, DEVIATIONS, CONDITIONS, AND WAIVERS

A. Volume II must include a certification that the volume addresses all exceptions, deviations, and waivers that the offeror takes from the provisions of the RFP and its applicable documents. An exception is an offeror’s statement that it will not comply with a requirement, usually involving a contract term or condition. A deviation is an offeror’s statement that it will not, or cannot, comply with a requirement, but that it proposes an alternative to meet the intent of the requirement, usually involving a specification. A condition is an offeror’s expression that its obligation to perform will be contingent upon some precedent occurrence. A waiver is where an offeror requests authorization for the mailto:patricia.peterson@usmc.mil mailto:taylor.cross@usmc.mil

Government to accept an item or performance that will depart from specified requirements, but would nevertheless be considered suitable.

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

B. The offeror shall provide a detailed description of each exception, deviation, condition, or request for waiver. The description shall indicate the offeror's difficulty with the applicable requirement and the offeror's proposed solution and shall specifically identify the portion of the RFP and the offeror's proposal that are affected.

L-1.4.3 VOLUME III. MANDATORY REQUIREMENTS–PASS/FAIL CRITERIA

The following documents shall be provided with the offeror’s proposal for evaluation under the

Mandatory Requirements—Pass/Fail Criteria:

Section 3.1, Accounting System Certification: The proposal shall include valid documentation from DCMA, DCAA, or another approved Federal audit agency evidencing that the offeror has an adequate accounting system for performing Government cost type contracts. The offeror shall complete and submit the Pre-award Survey of Prospective Accounting System Checklist

(Attachment 5) with supporting documentation. If the offeror is proposing subcontractor(s) and cost-reimbursement subcontract CLINs will be used, the proposal shall include that documentation for the subcontractor(s). Offerors are cautioned that the accounting system identified for use must be determined adequate to be eligible for contract award. Therefore, offerors shall be prepared to cooperate with and support DCAA auditors upon the initiation of the audit.

Section 3.2, 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. Offerors are to provide information for block 7 of the DD Form 254, (Attachment 2). In addition, offerors shall provide, if applicable, an SF328.

L-1.4.4 VOLUME IV, Factor 1: TECHNICAL APPROACH

This section shall consist of the offeror’s technical approach to performing the work identified in the Performance Work Statement (PWS), Attachment 1, to include the specific work efforts described in the Sample Task Order PWSs. Include the completed PWS Cross Reference Matrix at Section 4.1 and use that document to indicate where in the proposal (Vol, Sect, Page and

Paragraph) each listed requirement is addressed. Do not include narrative substance in the PWS

CRM.

Volume IV, Factor 1, Subfactors:

Software Maintenance and Development Approach

Agile development process

Systems engineering practices

System test and delivery

Cybersecurity Approach

Software Trouble Reports (STR)

Matrix: PWS Cross Reference Matrix: Include the completed PWS Cross Reference Matrix and use the document to indicate where in the proposal (Vol, Sect, Page and Paragraph) each listed requirement is addressed. Do not include narrative substance in the PWS CRM.

Section 4.1, Subfactor 1: Software Maintenance and Development Approach: The offeror shall provide a detailed approach, based on an Agile Development methodology, which demonstrates an in-depth and comprehensive understanding of the work to be performed based on the requirements stated in the PWS. At a minimum, the described approach shall include both

Scrum and Kanban methodologies and, if deemed appropriate, include other methodologies.

Include the following technical processes and practices in your description of software maintenance and development approach:

A. Section 4.1.1, Agile Development Process: Describe the Agile Development lifecycle process you will use to design and build the required software. When describing your process, explain how the Agile principles that have been adapted for DoD and federal systems are implemented. Include specific details of the management of requirements decomposition and the product backlog, to include prioritization of work with the

Government. Discuss the orchestration of demonstrations to collaborate with the users and stakeholders on product evaluations and the definition of “done.” Include any other items specific to the Agile approach.

B. Section 4.1.2, Systems Engineering Practices: Describe the systems engineering process and any other specific engineering processes that will be used to perform the required work based on the requirements stated in the PWS (Attachment 1). Discuss system capabilities and provide a features roadmap that maps capabilities and features to the development iterations and system build deliveries. Discuss meeting the entrance, exit, and review criteria for the technical reviews.

C. Section 4.1.3, System Test and Delivery: Describe the testing that will be used prior to delivering the required software to the Government. Include specific details for automated test, functional, integration, vulnerability, and defect tracking. Also, describe how support will be provided during Government test and evaluation. This should include test environment, test data/connections to external systems/stub to simulate outside systems, test scripts, support, training, and response to issues.

D. Section 4.1.4, Sample Task Order Development Approach: Provide a detailed approach, based on an Agile Development methodology, that demonstrates in detail the offeror’s design approach to fulfill the requirements addressed in the three Sample Task Order PWSs at

Attachments 9, 11, and 12.

Section 4.2, Subfactor 2: Cybersecurity Approach: The offeror shall provide a detailed approach to meeting PWS Cybersecurity requirements, demonstrating that the offeror understands those requirements and has the ability to maintain the appropriate Cybersecurity posture for C2PC and TSOA.

Section 4.3, Subfactor 3: Software Trouble Reports (STRs): The offeror shall provide a detailed approach to meeting PWS STR requirements that demonstrates the offeror’s ability to successfully diagnose and resolve Software Trouble Reports.

L-1.4.5 VOLUME V, Factor 2: MANAGEMENT APPROACH

This section shall consist of the offeror’s management approach to performing the work identified in the Performance Work Statement (PWS), Attachment 1, to include the specific work efforts described in the three Sample Task Order PWSs. The offeror’s proposal shall concisely, but thoroughly, demonstrate the offeror’s ability to perform the PWS requirements and establish that its firm possesses, or has the ability to obtain, personnel with appropriate experience, as described in the PWS.

Volume V, Factor 2, Subfactors:

Systems Engineering Processes

Integrated Master Plan

Staffing Plan

Matrix: PWS Cross Reference Matrix: Include the completed PWS Cross Reference Matrix and use the document to indicate where in the proposal (Vol, Sect, Page and Paragraph) each listed requirement is addressed. Do not include narrative substance in the PWS CRM.

Section 5.1, Subfactor 1: Systems Engineering Processes: The offeror shall describe in detail its approach to Requirements Management, Product Backlog Management, Configuration

Management, Technical Data Management, Risk Management, Technical Assessments, and

Decision Analyses, providing sufficient detail to demonstrate an understanding of what is required in a Software Development Plan.

A. Section 5.1.1, Systems Engineering Process for Sample Task Orders 1 through 3: The offeror shall describe in detail its approach to Requirements Management, Product Backlog

Management, Configuration Management, Technical Data Management, Risk Management, Technical Assessments, and Decision Analyses for the Sample Task Order PWSs at

Attachments 9, 11, and 12, providing sufficient detail to demonstrate an understanding of what is required in a Software Development Plan to address the Sample Task Order requirements.

Section 5.2, Subfactor 2: Integrated Master Plan. The offeror shall submit an Integrated

Master Plan (IMP) in MS Project 2016 or MS Excel 2016.

1) The submitted IMP shall use a systematic approach to planning, scheduling and executing the development of software components; and controlling and accomplishing the work described in the PWS. The IMP should be a top level plan consisting of a hierarchy of program events required.

2) The offeror shall also submit a draft Integrated Master Schedule (IMS) that supports the networked, multilayered plan showing the time based detailed tasks defined in the PWS. The

IMS should go no further than level three to demonstrate understanding of the intricacies of development in conjunction with working with the DoD process.

3) The offeror shall also submit the Work Breakdown Structure (WBS) from which the IMP was developed. The WBS shall demonstrate the offeror’s understanding of the scope of the

PWS.

A. Section 5.2.1, Integrated Master Plan for Sample Task Orders 1 through 3: The offeror shall submit an IMP for each of the three sample task orders in MS Project 2016 or MS Excel

2016. The IMP should be a top-level plan, consisting of hierarchal events for producing software components and accomplishing the work described in each of the three Sample

Task Order PWSs. In addition, the IMP should define and describe the integration of events, criteria required, and outcomes. The IMP shall include a draft Integrated Master Schedule for each of the three Sample Task Orders that supports the tasks defined in the Sample Task

Orders and shall include a Level 3 WBS that effectively reflects the scope of the work in each Sample Task Order PWS.

Section 5.3, Subfactor 3: Staffing Plan*: The offeror shall describe its proposed labor categories (by competency and level of experience), the qualifications the offeror will use in staffing those categories (including education, experience, roles, responsibilities, and professional certifications), and the number of hours proposed for each category to perform the work required by the PWS. Offerors shall not identify any individual intended to work on this effort but should instead identify the qualifications it will use in hiring for, and staffing, the effort. (Note: the Government reserves the right to incorporate into the contract, the staffing qualifications the offeror proposes to use.)

A. Section 5.3.1, Staffing Plan Sample Task Orders 1 through 3*: The offeror shall describe its proposed labor categories (by competency and level of experience), the qualifications the offeror will use in hiring for, and staffing, those categories (including education, experience, roles, responsibilities, and professional certifications), and the number of hours proposed for each category to perform the work required by each Sample Task Order PWS, 1 through 3.

* Offerors shall not specifically identify individuals, by name or otherwise, who are proposed for this effort. Offerors who indicate specific individuals, whether by name or otherwise identified, as proposed to work on this effort may be deemed unacceptable and have their proposal rejected. The Government anticipates incorporating the proposed personnel qualifications into the contract award.

L-1.4.6 VOLUME VI. PRICE PROPOSAL

Volume VI shall include the offeror’s Price Proposal.

If subcontractors are proposed, subcontractors shall provide all of the same information and rates required of the prime, as instructed below, in the Pricing Workbook, Subcontractor and Sample

Task Order Pricing (Attachment 3). Subcontractors may submit the Pricing Workbook

(Attachment 3), directly to the Government if the data is 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:

Patricia.Peterson@usmc.mil and Taylor.Cross@usmc.mil with a subject line of “TSA&S SM

Support and ST/DT Support M67854-22-R-2076-Subcontractor Pricing.” Primes must ensure that their price submissions are clear, particularly if subcontractor pricing information is being submitted separately. All pricing submitted by the prime should be clear as to whether the subcontractor’s pricing is already included, or the separate subcontractor submission must be added to the prime’s prices.

Section 6.1, Pricing Workbook: Attachment 3 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.

Tab 2 - Contract FFP CLINS Prime worksheet: Offerors shall submit pricing for FFP CLINs

1001 through 1009 for all ordering periods. Pricing under this worksheet shall match pricing provided in the Model Contract, Section B, CLINs 1001 through 1009 and the corresponding ordering periods CLINs. Pricing for CLINs 1010 through 1015 shall not be entered into the

Pricing Workbook or the Model Contract, Section B. The Government will provide the Not-To-

Exceed amounts for CLINs 1016 and 1017 and corresponding ordering period CLINs at time of award.

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 and sample task orders. Any additional supporting documentation may be provided at the offeror's discretion. The BOE shall include all cost elements. The Labor Rates and Categories used for the FFP CLINs shall come exclusively from the offeror’s Proposed Contract Labor Rates and

Categories Worksheet. In addition, the BOE for each CLIN shall include the cost associated with applicable Contract Data Requirements Lists.

1) Tab 4, Labor Rates and Categories worksheet: under this worksheet offerors shall submit the following:

Labor Categories, and for each:

Roles and Responsibilities

Required Education

Required Years of Experience

Professional Certifications

2022 hourly Compensation Rate

2022 hourly Fringe

Years 1 through 5 Fully Burdened Rates

The Government intends to utilize the proposed fixed hourly burdened rates and individual labor categories for all task orders awarded under the contract. Therefore, the offeror shall provide, in the Pricing Workbook (Attachment 3), all labor categories and fully burdened rates necessary to complete the requirements identified in the PWS, whether or not every category will be proposed for one of the three Sample Task Orders. All task orders with FFP, CPFF, and Cost CLINs based on proposals will require the use of current Forward Pricing Rate Agreements. All labor categories and fully burdened labor rates will be incorporated into the resulting contract, along with the offeror’s qualifications for each labor category.

2) 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.

A. Section 6.1.1, Sample Task Orders 1 through 3 Pricing: Offerors shall provide, in three separate Excel spreadsheets, pricing information for each Sample Task Order (C2PC Security

Manager Update, C2PC MIL-STD 2525D Upgrades, and TSOA SOI). Offerors should understand that the Government may award any or all of the Sample Task Orders (1-3) as proposed. The offeror shall provide sufficient information to support its cost/price for each

Sample Task Order. The offeror’s cost proposal shall include supporting information for each cost element that is consistent with offeror's cost accounting system. The supporting breakdown should include such elements as materials, direct labor, indirect cost, and other costs. If the offeror proposes rates which are not DCAA approved, the offeror shall provide complete documentation and the rationale for their use at the time of proposal submission. In addition, the:

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

Order. The Sample Task Orders are CPFF and cost (unburdened) for any proposed Travel or

Material. Offerors are not entitled to costs for preparing proposals for these three Sample

Task Orders.

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 in each task order.

L-1.4.7 VOLUME VII. PAST PERFORMANCE

Volume VII shall include the Offeror’s Past Performance submission.

Section 7.1, Past Performance: The offeror shall submit a minimum of three, and maximum of five, recent and relevant efforts it performed as the prime, preferably with the DoD or another federal agency, and preferably developing software of the same nature as is required by this solicitation. 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.

3) Note that the submission should not characterize the quality of the offeror’s performance as such assertions would be presumably biased. The Government seeks independent information regarding the offeror’s performance of prior efforts.

4) Offerors shall submit this information in the following format:

- CAGE code for the referenced company;

- Customer name, address, and telephone number;

- Customer’s Procuring Contracting Officer’s name, telephone number, and email address;

- Contracting activity’s technical representative or Contracting Officer Representative, telephone number, and email address;

- Customer Program Manager, telephone number and email address;

- Government contract administration activity and the name, telephone number, and email address of the Administrative Contracting Officer and the Chief of Program and

Technical support;

- Contract number;

- Customer Program title;

- Contract’s 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 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;

- 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. These responses will not be included in the page count;

L-1.4.8 VOLUME VIII. SMALL BUSINESS

Both large and small businesses shall provide the described information in Volume VIII in order for the Government to assess the offeror’s historical achievements in using small business concerns as subcontractors, its proposed small business participation, and its commitment strategies.

Section 8.1, Small Business Achievements: All offerors shall provide a narrative to describe their achievements in supporting the Government’s policy to provide maximum practicable opportunities for small business, veteran-owned small business, service-disabled veteran-owned small business, historically underutilized business zone small business, small disadvantaged business, and women-owned small business concerns to participate as subcontractors, consistent with efficient contract performance.

Section 8.2, Small Business Participation and Commitment Strategy: All offerors shall submit a Small Business Participation and Commitment Strategy to include the following:

1) Identify, in terms of dollar value and percentage of the total ceiling, the extent of work the offeror will self-perform as the prime contractor. If submitting an offer as a joint venture, identify the percentage of work each member will be responsible for and indicate the size status of each member (e.g. small business, woman-owned small business, other than small business).

2) The anticipated prime and first tier overall small business participation rate for this acquisition (i.e., work to be performed by small businesses as the prime and/or subcontractors) is 1% - 5% of the contract value, at a minimum. Offerors are encouraged to exceed this percentage and seek meaningful levels of participation in each of the small business socioeconomic programs consistent with efficient contract performance. Offerors shall explain in their participation and commitment strategies how proposed participation rates were established. The small business participation and commitment strategy must be in agreement with any required small business subcontracting plan at time of award and will be made a part of the contract upon award.

Section 8.3: Small Business Subcontracting Plan (OTHER THAN SMALL BUSINESSES

ONLY): The Small Business Subcontracting Plan is only required from Other than Small

Businesses and will be incorporated into any resultant contract. FAR 52.219-9 sets forth the

Small Business Subcontracting Plan’s required elements.

L-1.4.9 VOLUME IX CONTRACT INFORMATION

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.

Section 9.1, Model Contract: The offeror's proposal shall include the model contract with all proposed pricing, including a completed copy of SF 33 and acknowledgment of any solicitation amendments (SF 30), each signed by a person authorized to enter into the proposed contract on behalf of the offeror. In addition, offerors shall include all RFP Provisions and Clauses that require completion by the offeror.

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.

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) An itemized list of Fringe benefits provided, noting the hourly rate;

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.

Section 9.3. Equal Employment Opportunity (EEO) and VETS 4212 Pre-award

Clearance Information:

1) 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: company 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).

2) Confirmation of Receipt: In addition, 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 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 4212 Service Center to request a verification search to be performed.

Phone: (866) 237-0275

Email: vets4212-customersupport@dolncc.dol.gov

Please note that to perform a verification search, the VETS 4212 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

The Government will review the offeror’s representations and certifications to ensure they meet or exceed the requirements of the solicitation.

SECTION M - EVALUATION FACTORS FOR AWARD

SECTION M

SECTION M: Evaluation Factors for Award

M-1 BASIS FOR AWARD

M-1.1 EVALUATION SUMMARY

A. The Government will evaluate proposals as described below:

1) In accordance with Federal Acquisition Regulation (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.

2) Any proposal that does not substantially and materially comply with all of the material requirements of this solicitation may be rejected and not considered for further evaluation.

Rejection of a proposal on this basis does not constitute creation of a “competitive range.”

M-1.2 BASIS OF AWARD

A. The following conditions must be met in order to be eligible for award:

1) The proposal must comply in all material respects with the requirements of the law, regulation, and conditions set…