Attachment 0009 - RFP Section L - Instructions Amendment 2.docx

CUI

RFP W15P7T-24-R-0021

SECTION L

FOR THE

Post Deployment Software Support and Post-Production Software Support Maintenance and Sustainment

Amendment 2

TABLE OF CONTENTS

A. PROPOSAL SUBMISSION (Section L)

1. PROPOSAL SUBMISSION REQUIREMENTS

a. Proposals shall be submitted to Contracting Officer, Christopher Winfield at christopher.m.winfield.civ@army.mil and Contract Specialist Chere Benson, chere.v.benson.civ@army.mil via email no later than (NLT) 5:00 pm Eastern Standard Time on 17 May 2024 Close of Business. The size per email shall not exceed 24MB. If necessary, Offerors may submit multiple emails. All proposals received after the exact time specified for receipt shall be treated as late submissions and will not be considered except for award. It is the responsibility of the Offeror to contact the Government’s POCs identified below to confirm their proposal is received. Confirmation of receipt does not equate to confirmation of contents of the proposal.

b. All questions shall be submitted via email to the POCs identified above NLT Close of Business Eastern Standard Time on 17 April 2024. Questions shall be submitted in a generic format; contractors shall not ask company specific questions or include proprietary information. It is preferred that only one set of questions be submitted by each Offeror instead of submitting multiple sets of questions. Questions received after the date and time may not be answered prior to the closing date/time for receipt of submissions. If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall notify the Government POCs identified above during the question period in writing with supporting rationale; the notification shall also include the remedies the Offeror is asking the Government to consider as related to the omission or error. All questions and answers shall be shared with all potential offerors. Responses, if required, will be posted to the SAM Website.

c. For best value trade off awards: When award is made to the Offeror whose overall proposal is deemed sufficiently more advantageous to the Government so as to justify the payment of a higher Cost/Price, the Government reserves the right to incorporate the parts of the proposal deemed to provide the added value into the Contract. Additionally, the Government will modify the Quality Assurance Surveillance Plan (QASP) to specify that the Government will monitor the extent to which the Awardee provides the added value throughout the term of the Contract.

d. All inquiries shall be conducted in writing and directly to the Government POCs identified above. Offerors shall not contact any Government personnel other than the Government POCs identified above concerning this requirement. Contacting any Government personnel other than the individual identified above may result in an organizational conflict of interest (OCI) and may result in an Offeror being excluded from competition and award.

e. Offerors shall not submit any assumptions, terms, conditions, caveats, or exceptions with their proposals. All concerns shall be addressed and resolved by submitting questions by the date specified in the RFP. No assumptions, terms, conditions, caveats, or exceptions submitted with proposals in response to RFPs will be accepted or incorporated into the contract award.

f. Offerors may encrypt and/or password protect proprietary information as they see fit. Proprietary information shall be clearly marked. However, if the Government is unable to access the documents, the proposal will not be considered for award. Proposal submittal shall consist of separate file as set forth and named in the table below. Microsoft Office 2016 software or higher, and Adobe software if applicable, shall be used to create the required files. Proposals shall not contain any classified data or information.

g. Each volume shall be properly identified, numbered, clearly indexed, and logically assembled. Each volume shall also contain clearly identified sections and all pages shall be numbered and identified by the complete company name, date, and solicitation number in the header and/or footer. Any portion of the proposal that is changed (as a result of negotiations or proposal revisions) should be annotated and dated.

h. Subcontractor cost proposals shall be submitted electronically directly to the above Government POC’s email prior to the proposal due date and time if the subcontractor deems its proposal contains proprietary data. If the subcontractor does not deem that its proposal contains proprietary information, then the subcontractor shall submit its cost proposal to the prime contractor for inclusion in its proposal. The size per e-mail shall not exceed 24MB, and its proposal shall include all necessary supporting documents and narrative.

i. The entire proposal shall remain valid for a minimum of 180 days from receipt by the Government and shall not contain classified data or information. Proposals offering a shorter period of time will not be considered for award.

j. In order to reduce proposal size, proposals shall be limited to the number of pages as outlined below for each volume. All proposal information shall be confined to the appropriate file. The page limit (identified in the table below) is viewed as total pages within a file, excluding a table of contents, cover page, and glossary page. The Government will not evaluate any pages that exceed the page limitation(s) identified below. Pages containing text shall be typewritten using the standard letter size (8.5 x 11) in Microsoft Word. Text shall be a minimum of 12- point Times New Roman or Arial font and no less than one-inch margins/borders. Each paragraph should be single spaced and shall be separated by at least one blank line. Any headers/footers, call out boxes, captions, table, or graphic shall use a minimum of 10-point Times New Roman or Arial font. Drawings or other graphics shall be reduced only to the extent legibility is not lost.

k. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but, rather, shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities or experience and will base its evaluation on the information presented in the Offeror's proposal.

l. All Information the Offeror intends to have considered, including the Offeror’s best cost, shall be submitted with the initial proposal. The Government proposal evaluation will be limited to the information provided by the Offeror, and nothing will be assumed. Offerors are responsible for including sufficient details to permit a complete, thorough, and accurate evaluation of the submitted proposal.

m. The following volumes of material shall be submitted:

Table 1 - Proposal Volumes

Cost Proposal - Offerors shall use the format found at Federal Acquisition Regulation (FAR) 15.408, Table 15-2 format. The Cost Proposal (xxxx COST.xlsx) SHALL be submitted in Excel format (.xlsx) with all formulas visible in each cell with a value

Offerors shall replace “xxxx” with the Offeror’s name and the date of the proposal. For example: OfferorNameCOST03202023.xlsx.

NOTE 1: Pages that exceed the required page limitations will not be evaluated. Additional pages over the maximum allowed will be removed or not read and will not be evaluated by the Government. If there are more than forty-five (45) lines of text on any page, the lines that exceed the line count will not be evaluated. The Cover Page, Table of Contents, and Glossary of Abbreviations and Acronyms will not be included in the page count for any of the volumes.

NOTE 2: All or portions of the winning Offerors proposal may be incorporated into the contract as attachments.

2. PROPOSAL FILES

a. Format. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date, and Request for Proposal (RFP) number in the header and/or footer. A Table of Contents should be created using the Table of Content feature in MS Word. MS Word (docx) files shall use the following page setup parameters:

Margins – Top, Bottom, Left, Right – 1” Gutter – 0” From Edge – Header, Footer 0.5” Page Size, Width – 8.5” Page Size, Height – 11”

The following additional restrictions apply:

b. File Packaging. All of the proposal files shall be compressed (zipped) into one file entitled proposal zip using WinZip version 6.2 or later, or as separate uploads in their native format, i.e., docx, xlsx, pptx, etc., and provided via electronic mail (e-mail). Files shall be in read-only format, using PDF files. All price breakdown information to aide in the cost/price evaluation shall be submitted in Microsoft Office Excel Read/Write format and viewable in Microsoft Excel 365. All files must be submitted and accepted by the closing date and time identified in the RFP. Files shall not contain classified data.

**Please note – Self extracting exe files are not acceptable.

c. Content Requirement. All information shall be confined to the appropriate file and Volume. The offeror shall confine submissions to essential matters, sufficient details to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. Each file of the proposal shall consist of a Table of Contents, Summary Section, and the Narrative discussion. The Table of Contents and Glossary of Abbreviations and Acronyms for each applicable volume will not apply to the page limitations. The Summary Section shall contain a brief abstract of the file. Each volume shall be prepared on a stand-alone basis, so that its contents may be evaluated without any need for cross-referencing to other volumes of the proposal. Proprietary information shall be clearly marked.

VOLUME I – Technical Oral Presentations

1. Oral Presentations will be used to present the technical volume for this RFP. Slides are permitted to support the Offeror’s live oral presentations. Offerors shall provide a copy of their slide presentation following their live oral presentations. The Government will only consider the slides presented during the oral presentation for evaluations. In the event ambiguities or conflicts exist between the oral presentation and the written slide, the oral presentation will take precedence over the written slides. Any slides not presented in the Offerors allotted time will be removed from the slide presentation and disregarded by the Government. The Government reserves the right to delete any slides that are illegible. Unsolicited changes to the presentation submission will not be accepted.

2. The Contracting Officer will schedule oral presentations for the offerors, and the dates/times will be emailed out on 20 May 2024. The maximum number of Contractor logins for Oral Presentations is limited to five individuals. The Government recommends Contractors utilize key personnel who will perform, or personally direct the work that describes their relevant portions of the presentations. This may include teaming partners.

3. Each Offeror will be allotted a 2.5-hour window to conduct their presentation. The Oral Presentation schedule is as follows:

a. Introductions: Up to 15 minutes

b. Presentation: 1 hour

c. Break: 15 minutes

d. Completion of Presentations – up to 1 hour

Offerors shall assume that the Government has no prior knowledge of Offeror’s experience, as the Government will base its evaluation solely on the information contained in the Offeror’s presentation. Offeror’s may not electronically record any part of the Oral Technical Presentation process. The Government will record the Oral presentation in whole.

4. At the completion of the presentation, the oral presentation will be considered complete.

5. The Government anticipates the Contracting Officer, Contract Specialist, Office of Counsel, and the Evaluation Team members will be in attendance for the presentations. The Contracting Officer retains sole discretion to require, invite, or allow other Government personnel to attend.

7. The volume shall be organized into the following subfactors:

Subfactor 1: Technical Approach:

a) Oral Presentations will be used to assess the Offeror’s technical approach on demonstrating a clear understanding of the PWS requirements, and solutions to the following subsection of the PWS 3.1.4, and the objectives stated in PWS section 3.2 as it relates to 6.1 through 6.12. The Offeror shall demonstrate their technical understanding and experience in technical domains similar to those identified in PWS 6.1-6.12.

· Oral Presentations shall include measures put in place to ensure schedules are met and quality deliverables are provided. Identify objectives that are part of the offerors’ organizational quality policy. The offeror’s presentation shall establish controls, set standards, establish measurement methods, and implement the quality control measures.

· The Offeror shall demonstrate their ability to code against a wide array of Military Standards (MIL-STD) to include MIL-STD-6016, MIL-STD-6017, MIL-STD-2525, MIL-STD-2045-4700, MIL-STD-6020, and MIL-STD-6040 specifications. The Offeror shall demonstrate their ability to code against industry data exchange standards such as Simple Object Access Protocol (SOAP), Extensible Markup Language (XML), Representational State Transfer (REST) and JavaScript Object Notation (JSON), in addition to developing Application Programing Interfaces (API) specifications. The Offeror shall demonstrate their ability to analyze legacy software and provide solutions to modernizing components into a containerized or cloud-based infrastructure. The Offer shall demonstrate their understanding of radar-based algorithms and data processing methods. The Offeror shall demonstrate experience in identifying members of the Department of Defense (DoD) Cyberspace Workforce Framework (DCWF) based on the cyberspace work role(s) of the position(s) assigned, as described in DoD Instruction (DoDI) 8140.02.

b) Offerors shall demonstrate their experience and knowledge in their response to the following questions:

1. Offerors shall demonstrate experience in product development and explain how they deal with changes to scope and requirements.

2. Demonstrate case studies of Agile projects with similar complexity involving a product performed by your company.

3. Describe how your company applies Continuous Integration / Continuous Delivery (CI/CD) into your development process.

4. Offerors shall demonstrate experience in project management process and approaches.

5. Describe your team’s experience with Agile methodologies (e.g. Scrum, Kanban, Scaled Agile Framework (SAFE), etc.).

6. Describe your company’s approach for estimation and capacity planning for specified tasks.

7. How does your company measure performance and effectiveness?

8. Describe how your company evaluates its maturity implementing Development, Security, and Operations (DevSecOps), and describe the methods used to continually improve on DevSecOps pipeline? Offerors shall demonstrate their delivery process.

9. How would you explain a minimum viable product (MVP) based on your delivery approach?

10. What process does your company use to identify end-users and capture their needs?

11. How does your company execute integration communications, testing and release management?

12. Offerors shall demonstrate experience in Cyberspace Management. Identify efficiencies, improvements, and innovations associated with the Cybersecurity Operations and Network Operations Support Objectives defined in the PWS sections 3.2.7.4 through 3.2.7.8. The offeror shall define your team’s experience with Cyberspace Operations objectives by addressing each of the following:

a. Maintaining Government networks and IT infrastructure to Army Policy and Directives.

b. Maintaining continuous monitoring under Risk Management Framework. Maintaining a compliance to Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG), execution of Vulnerability Management procedures, and configuration management of all Risk Management Framework documentation and testing.

c. Providing network operations and sustainment to include Network Asset Management, troubleshooting networks failures and resolution, Network Hardware and Software Inventory, network topology and Ports Protocol and Services Management (PPSM) documentation.

Subfactor 2: Staffing Approach:

a) Offerors shall demonstrate their ability to hire and have in place all Key Personnel within thirty (30) days of contract award, and the ability to ramp up to roughly fifty percent (50%) of the total Level of Effort (LOE) referenced in Attachment 0001 – Labor Categories. with Secret clearances within one hundred twenty (120) days. Offerors shall demonstrate their ability to quickly expand staff to meet increased workloads and describe how they will assure appropriate specialized technical expertise is obtained.

b) Offerors shall describe potential personnel retention risks and describe risk mitigation measures. Offerors shall describe potential risks of not being able to retain the proposed team members and describe risk mitigation measures. Offerors shall discuss their methods for attracting, hiring, developing, training, and retaining a workforce with all the skills and knowledge necessary to support the PDSS/PPSS requirements. The offeror’s proposal shall describe the approach to provide the training and mentoring necessary to keep the work force up to date on current technologies, trends, and best business practices. The offerors plan shall also take into consideration the impact of an environment of fluctuating workloads, demanding schedules, and complex project issues.

VOLUME II – Past Performance This volume shall contain past performance information regarding similar contracts. The Offeror shall submit information regarding up to three (3) recent and relevant contracts for the prime and up to (2) recent and relevant contract for major subcontractors. This volume shall not exceed nine (9) pages, approximately three (3) pages per contract for the prime offeror and not to exceed six (6) pages, approximately three (3) pages per major subcontractor, excluding the Past Performance Questionnaire Form. Offerors shall submit associated Government and/or commercial contracts for the prime Offeror and/or each major subcontractor in performance or awarded during the past three (3) years, from the issue date of this RFP, which are relevant to the efforts required by this solicitation. Relevant efforts are defined as services/efforts that are the same as or similar to the effort (as compared to North American Industry Classification System (NAICS) code 541511 Custom Computer Programming Services required by the RFP. Data concerning the offeror shall be provided first, followed by each proposed major subcontractor. The Offeror shall also submit the written consent of its major subcontractors to allow the disclosure of its subcontractor’s past performance information to the Offeror. Major Subcontractors shall be defined as any subcontractor whose total expected subcontract value will be 25% or greater of the total proposed contract price, including all Ordering Periods. In addition, letters of commitment shall be included for all major subcontractors for their past performance to be considered.

This volume shall be organized into the following sections:

Section 1 – Contract Descriptions.

This section shall include the following information in the following format.

a. Contractor/Subcontractor place of performance, Commercial and Government Entity (CAGE) Code, Unique Entity ID on the System for Award Management website, and Data Universal Numbering System (DUNS) Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone).

If submitting a contract from a CAGE code other than the prime or major subcontractor, then the offeror must include a narrative explaining why the Government should consider the contract to be relevant. The Government, during its evaluation, may determine that an example from a different CAGE code is not relevant.

b. Government contracting activity, and current address, Procuring Contracting Officer’s name, e-mail address, and telephone number.

c. Government’s technical representative/Contracting Officer’s Representative and current email address, and telephone number.

d. Government contract administration activity and the Administrative Contracting Officer’s name, and current e-mail address, and telephone number.

e. Government contract administration activity’s Pre-Award Monitor’s name, and current e-mail address, and telephone number.

f. Contract Number and, in the case of Indefinite Delivery type contracts, General Service Administration contracts, and Blanket Purchase Agreements, include Delivery Order Numbers.

g. Contract Type (specific type such as Fixed-Price (FP), Cost Reimbursement (CR), Time & Material (T&M), etc.). In the case of Indefinite Delivery contracts, indicate specific type (Requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (FP, CR, T&M, etc.).

h. Awarded price/cost.

i. Dollar value of the portion of the work completed by the prime offeror or major subcontractor.

j. Final or projected final price/cost.

k. Original delivery schedule, including dates of start and completion or work.

l. Final or projected final, delivery schedule, including dates of start and completion of work.

Section 2 – Performance.

Offerors shall provide a specific narrative explanation of each contract listed in Section 1, Contract Description, describing the objectives achieved and detailing how the effort is relevant to the requirement of this RFP. In considering the similarity of services performed/provided as compared to the requirements defined in the PWS, the extent to which past performance is similar with respect to complexity, dollar value, contract type, and degree of subcontract/teaming will be considered in the relevancy assessment.

a. When assessing performance risk, the government will focus its inquiry on the past performance of the offeror as it relates to all solicitation requirements. These requirements include all aspects of schedule, performance, and supportability, including the offeror’s record of:

1) compliance of services, documents, and related deliverables to specification requirements and standards of good workmanship

2) effectiveness of project management (to include use and control of subcontractors)

3) timeliness of performance for services and deliverables, including the administrative aspects of performance

4) effectiveness in forecasting and controlling project cost.

5) commitment to customer satisfaction and business-like concern for customer’s interest

6) overall satisfaction

b. For any contracts that did not/do not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All Requests for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions. The offerors shall also provide copy of any Cure Notices or Show Cause Letters received on each contract listed and a description of any corrective action implemented by the offeror or proposed subcontractor. The offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

Section 3 – Subcontracts.

Offerors shall provide an outline of how the effort required by the RFP will be assigned for performance within the offeror’s corporate entity and among the proposed subcontractors. The information provided for the prime offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number, Unique Entity ID, and type of work to be performed by citing the applicable Government PWS subparagraph number. This includes all subcontractors who will be providing critical hardware/services or whose subcontract is for more than 25% of the total proposed cost/price. This section will further include written consent of major subcontractors to allow the disclosure of their subcontractor’s past performance information to the Offeror. In addition, letters of commitment shall be included for all major subcontractors.

Section 4 – New Corporate Entities.

New corporate entities may submit data on prior contracts involving its offices and employees. However, in addition to the other requirements in this section, the offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above. Letters of Commitment shall be included in the proposal for these employees in order to be considered.

Past Performance Questionnaire.

For all contracts identified in Section 1, Contract Descriptions, a Past Performance Questionnaire must be completed and submitted. The offeror shall complete Part I of the Past Performance Questionnaire and e-mail the questionnaire to both the Government contracting activity and technical representative responsible for the past/current contract. The POCs shall be instructed to electronically complete Part II of the questionnaire and e-mail the entire questionnaire to the Contracting Office no later than the proposal due date, to Contracting Officer, Christopher Winfield, christopher.m.winfield.civ@army.mil and Contract Specialist, Chere Benson, chere.v.benson.civ@army.mil. The offeror shall e-mail to the Contracting Officer a list of all the POCs who were sent a questionnaire. The Government must receive this list no later than the proposal due date. The POC List shall be submitted in Word for Windows Table Format to include the following fields: Solicitation Number; Company Name; Contract Number; Government Agency; POC Last Name, First Name; POC Title; POC Telephone Number; POC E-mail Address; and Date of E-Mail to POC (month/day).

Submissions.

Offerors are discouraged from providing points of contact with another contractors’ facility, i.e., in case an offeror (or one of his/her team members) is in a subcontract with another contractor who has submitted a proposal on the same requirement. Offerors shall provide and submit the prime contract number and all Governmental agency POCs in lieu of subcontract numbers or prime contract POCs in situations as described above. The Government reserves the right to use information provided in the Corporate Experience element, check, and utilize the Contractor Performance Assessment Reporting System (CPARS), and the Federal Awardee Performance and Integrity Information System (FAPIIS) or any other extrinsic source available to the Government for past performance information. For each proposed major subcontractor, the Offeror shall include a Letter of Consent authorizing the Government to discuss the proposed subcontractor(s) past performance with the Offeror. The Government is not required to interview all points of contact identified by Offerors.

Small Business Participation Past Performance.

All Offerors shall submit information substantiating the Offerors past performance in complying with FAR 52.219-8, Utilization of Small Business Concerns, maximizing opportunities for U.S. small business subcontractors. Offerors shall also provide a statement indicating whether any negative information has been reported in the past five years concerning the Offerors past compliance with FAR 52.219-8. If any such negative information has been reported, the Offeror may submit explanations or comments responding to such negative information. Offerors with no prior contracts containing FAR 52.219-8 shall certify the same.

VOLUME III – Small Business Participation All Offerors (both other than small businesses (OTSB) and small businesses) shall submit a Small Business Participation Commitment Document (SBPCD) as outlined in Attachment 0008 - SBPCD and provide substantiating documentation to demonstrate how the Offeror will meet the objective for the Government to use Small Business Concerns to the maximum extent practicable. The Offeror shall follow the instructions set forth below and in the SBPCD. The information that the Offeror provides will be used to evaluate the Offeror’s proposed participation /commitment to use U.S. small businesses in the performance of this acquisition (as a small business prime, joint venture, teaming arrangement, and/or small business subcontractors) relative to Section M, Volume III – Small Business Participation. The SBPCD will be incorporated into the base contract vehicle as binding commitments and are considered enforceable contractual requirements.

NOTE: The small business participation plan outlines the "specifics" or the "how" or the "details" of the Offeror’s firm intentions to maximize the utilization of small businesses within this acquisition. The Offeror shall articulate small business contributions to contract performance at the Prime contract through first tier subcontract levels. Second and lower tier small business subcontractors will not be considered towards the total small business participation percentage. Small Business Participation annotated in the Offeror’s SBPCD is a separate requirement from the FAR 19.704 Subcontracting Plan Requirements, which will only be reviewed for acceptability for the Offeror deemed to be apparent awardee.

1. The Offeror shall provide the Prime Offeror’s Size as outlined in the SBPCD.

2. Pursuant to FAR Part 19, the Government’s objective is that Small Business Concerns (SBC) are used to the maximum extent practicable in the Offeror’s proposed approach to satisfy the requirements of this solicitation for the entire performance period. The Offeror shall identify SBCs that are to be used in their proposed approach to satisfy the requirements. As outlined in the SBPCD, the Offeror shall:

a. Identify the type, variety, and complexity of work to be performed by small business concern IAW the associated PWS Section 3.0 Requirements.

b. Describe and demonstrate a substantive commitment to small business firms.

c. All Small Businesses submitted as part of the Small Business Concerns will be verified to ensure they are a small business. The Government will use websites or databases such as, the Dynamic Small Business Search (DSBS) or Sam.gov to verify small business status.

3. The Offeror shall propose the total contract value for this effort and provide the participation percentage of businesses in terms of the total contract value as outlined in the SBPCD.

a. For this requirement the Governments market research shows that a minimum percentage of the work can be performed by small business concerns; therefore, the minimum quantitative requirement has been established at 20%.

b. The Offerors proposed total contract value for this requirement shall include all ordering years.

c. The Offeror shall provide explanation and documentation to support small business participation percentages. Binding commitments shall become enforceable, contractual requirements.

d. Large business contractors may achieve the small business participation requirements through subcontracting to small business. Small business contractors may achieve small business participation requirements through their own performance/ participation as a prime and also through a joint venture, teaming arrangement, and subcontracting to other small businesses.

NOTE: All supporting documentation is excluded from the page count. Supporting documents will not be incorporated into any resulting contract.

4. The Offeror shall submit past performance information to demonstrate that it complied with the requirements of FAR 52.219-8, Utilization of Small Business Concerns, for the past five years, as outlined in the SBPCD. Information included here will not be evaluated for Factor 2 – Past Performance.

5. Only Other Than Small Businesses (OTSB) shall provide a separate Small Business Subcontracting Plan that contains all of the elements required by FAR 52.219-9. The Small Business Subcontracting Plan shall be submitted separately from the information required above and in the SBPCD that both OTSB and small businesses are required to submit. The plan, at a minimum, shall address the elements set forth in FAR Clause 52.219-9(d)(1) through (15). Subcontracting Plans shall reflect and be consistent with the commitments offered in the SBPCD. OTSB Firms shall submit acceptable subcontracting plans to be eligible for award. Subcontracting plans will only be reviewed for acceptability for the Offeror deemed to be apparent awardee. The Small Business Subcontracting Plan will be incorporated into the resultant contract and is excluded from the small business page count limit.

NOTE: Paragraph 5 will not be evaluated as part of the Volume III submission, but it is required for the awardee to have an acceptable plan and for an offeror to be eligible for award.

6. The work to be performed directly by a small business Prime Offeror shall be evaluated as Small Business Participation. Small business Prime Offerors shall include their information in the above requested subparagraphs and SBPCD as required.

7. The SBPCD, which is an enforceable, contractual requirement, shall require periodic progress reporting to facilitate government monitoring in the event of an award. The Offeror shall propose semi-annual reporting of the requirements set forth in the SBPCD paragraphs 1-3 (contractor format is acceptable) in accordance with CDRL A029 – Small Business Utilization Report (DI-MGMT-82041B).

8. Offerors that have enforceable agreements shall provide fully executed copies (i.e., the entire agreement and not just first and last pages). An enforceable commitment is defined as a written and signed agreement (by both parties) detailing that all parties have agreed to a business relationship for this procurement; the agreement shall be specific in nature. The agreement shall be clear that both parties have defined and agreed to the extent of the relationship to include the type or types of work the subcontractors/partners shall perform. These agreements are excluded from the small business page count limit.

VOLUME IV – Property Management Plan Offerors shall submit a Property Management Plan to describe its approach to managing government property throughout performance of this contract, per FAR 45.202(b). This plan shall address each of the following ten (10) outcomes and provide a brief overview of how it is addressed within Offerors’ written Property Management Procedures:

Table 2 - Property Management Outcomes

VOLUME V – Cost/Price

The volume shall be organized into the following sections:

1. The contractor shall submit a Summary Cost Proposal, by Cost Element, as depicted in the sample provided below in Table 3 for its total proposed price. The summary cost proposal shall be a Microsoft Excel workbook (xxxxCOSTxxxx.xlsx) that includes a detailed cost element worksheet for each separate CLIN. These cost element values shall roll up to each Period of Performance (PoP), which then rolls up to the Summary Total Cost as depicted in Table 3 below. Offeror shall also include a separate CLIN rollup Summary Table within its proposal. A separate direct labor rate worksheet, and an indirect rate worksheet shall also be included within the xxxxCOSTxxxx.xlsx workbook. The set of worksheets as described shall repeat for the Prime and each subcontractor/interdivisional entity (S/IE) proposing on a CPFF basis in its separate proposal submission to the government. Offerors are responsible for submitting support for proposed pricing; noncompliance with these instructions may result in a proposed cost being deemed “undeterminable” and ineligible for award.

Note 1: Subcontractors proposing on a Firm-Fixed-Price (FFP), Time and Materials (T&M), and Labor Hour (LH) basis are not required to provide any support beyond the Fully Burdened Labor Rates (FBLRs) submission.

Note 2: Subcontractors proposing on a Cost-Plus-Fixed-Fee basis are required to provide the same full level of detail and support as required of the Prime.

2. Proposed direct and indirect rates shall be referenced (not hard-numbered) between the direct labor rate and indirect rate worksheets and its respective CLIN worksheets. Each PoP shall have a worksheet detailed by cost element. Instructions for Cost Elements are identified in the following subparagraphs of this section. Submit the Cost/Price proposal in Microsoft Excel format, utilizing any of the following versions: Microsoft Office 2016, or more current versions. Excel spreadsheets must be sent in an unlocked workbook that includes all formulas, and format information. No links to external worksheets or workbooks are acceptable. No Macros are to be included in any Excel spreadsheet submissions. Offeror and its subcontractors shall not include pivot tables in Excel spreadsheets. Hard numbers shall not be included in the Microsoft Cost volume, all formulas must be present and visible. Print image is not acceptable.

Table 3 - Sample - Cost Element Summary

(Your cost elements may differ)

Direct Labor

Fringe

Overhead

Subcontractor

SHC

**IOT

Material

MHC

ODC

Travel

Subtotal

G&A

Subtotal

Fixed Fee - Prime

Fixed Fee - Subcontractor

FCCOM

Total

a. A cost volume proposal is complete if the offeror provides Cost/Price data for RFP requirements as required and the proposed costs are traceable and accurate. The proposed costs are traceable if they can be tracked from the offeror’s xxxxCOSTNARRxxxx.docx (or .PDF) to the xxxxCOSTxxxx.xlsx workbook. Offerors shall incorporate the Attachment 0002 “Direct Labor Rate Workbook” into its xxxxCOSTxxxx.xlsx workbook submission.

IMPORTANT NOTE: The offeror is required to propose to the total level of effort (LOE) provided to meet the work described in the PWS per CLIN and IAW its labor categories and hours as provided in Attachment 0001 Labor Categories.

3. Cost Plus Fixed Fee (CPFF) Term, and Cost

a. Period of Performance:

Six-month (6-month) Extension Option 31 July 2029 thru 30 January 2030

Note: Estimated dates for proposal and evaluation purposes may change at the time of award; the 60 business days excludes holidays. The Transition Period contract type will be CPFF, with the Ordering Periods also being performed on a CPFF Term basis.

b. Offeror and any subcontractor(s) shall be responsible for ensuring compliance with the Service Contract Labor Standards (SCLS) for all applicable labor categories. If offerors determine that labor categories are subject to the SCLS, they shall identify such labor categories as “SCLS Labor” on their respective proposals. Offerors shall also disclose the state and county in which the proposed SCLS labor categories will be performing their effort, the Wage Determination Schedule used for their proposed SCLS Labor rates, and the Occupation Code and Title for each proposed SCLS labor category. Offerors are advised that SCLS submissions are also subject to Probable Cost adjustments.

c. Each offeror shall provide whatever information is necessary to assist the Government in understanding why the proposed costs are realistic in the xxxxCOSTNARRxxxx.docx (or PDF). Additionally, each offeror shall ensure any proposed cost-reimbursement subcontractors provide whatever information is necessary to assist the Government in understanding why the proposed subcontractor costs are realistic in the subcontractor’s xxxxCOSTNARRxxxx.docx (or PDF). Each offeror's cost proposal shall contain sufficient quantitative and narrative documentation to adequately support and explain the costs proposed, to include subcontractor proposed costs. If the offeror’s proposal includes accounting approaches that deviate from standard industry accounting practices or caps proposed on indirect rates, the offeror shall include documentation from the Defense Contract Management Agency (DCMA)/Defense Contract Audit Agency (DCAA) showing that the offeror’s accounting system/cost accounting standards allow for the deviation and/or rate cap. DCMA/DCAA approved deviations and/or rate caps will be incorporated into the resulting contract. Offeror and its subcontractor(s) shall disclose the location (Government site or the contractor site per the PWS) of each proposed labor category’s performance in their respective cost proposals.

d. Each offeror shall identify all proposed subcontractors and the contract type the offeror has with each subcontractor in its xxxxCOSTNARRxxxx.docx (or PDF). IAW FAR 15.404-3(b), the prime contractor or subcontractor shall: (1) Conduct appropriate cost or price analyses (CAPA) to establish the reasonableness of proposed subcontract costs/prices; and (2) Include the results of these analyses and methodology utilized in these analyses in the cost/price proposal. The offeror or subcontractor shall identify whether it relied upon its approved purchasing system to establish its subcontracts; if the offeror relied upon its approved purchasing system, it shall provide documentation of its approved purchasing system (including date of approval) within its xxxxCOSTNARRxxxx.docx (or PDF) (see FAR 15.404-3).

e. Reference FAR 15.404-3: If the offeror is unable to obtain the required documentation from its subcontractor(s) necessary to conduct the appropriate cost or price analysis (CAPA) as required, then the subcontractor(s) shall provide the information directly to the Government following the exact submission instructions of this RFP. In this scenario, the offeror shall provide the rationale detailing exactly why the offeror is unable to conduct the subcontractor price or cost analysis required by FAR 15.404-3 in its xxxxCOSTNARRxxxx.docx (or PDF). For example: if it is required for a subcontractor to provide a price/cost analysis that has a breakout of the individual cost elements, but the subcontractor is unable to provide its proprietary data to the offeror, then the offeror shall conduct a total price analysis, according to FAR 15.404-1(b), and the subcontractor shall submit its proprietary cost breakout directly to the government.

f. IAW FAR 15.403-3, data other than certified cost or pricing data is required to support cost realism. Each offeror and its subcontractors cost proposal shall be broken out by cost element as specified in FAR 15.408, Table 15-2 and depicted in Table 2 above. If a subcontractor submits its cost proposal directly to the government, the subcontractor’s xxxxCOSTNARRxxxx.docx (or PDF) and xxxxCOSTxxxx.xlsx shall contain all the same documentation, by cost volume, required of offerors (primes) if it is a cost reimbursable contract type. Subcontractors that propose on a Firm-Fixed-Price, Time and Materials (T&M), or Labor Hour (LH) basis are not required to provide any support beyond the Fully Burdened Labor Rates (FBLRs). The subcontractor shall identify in its xxxxCOSTNARRxxxx.docx (or PDF) the offeror and the RFP number.

g. Proposed direct and indirect rates shall be referenced (not hard numbered) between the direct labor rate and indirect worksheet(s) and their respective CPFF worksheets. Offerors and their subcontractors shall add direct labor rate and indirect rate sheets as required to comply with their accounting practices and financial disclosures.

h. Each Labor Category proposed within the CPFF five (5) year Ordering Period worksheets shall include a corresponding Position Number (PN) as depicted in Attachment 0002 Direct Labor Rate Workbook.

i. In support of the proposed direct labor rates, the offeror and its subcontractor(s) shall provide documentation of the most recent direct labor rates, to include at least one (1) of the following (1, 2, 3, or 4):

1. Most recent Forward Pricing Rate Agreements (FPRA) with DCAA or DCMA

2. Most recent Forward Pricing Rate Recommendations (FPRR) from DCAA or DCMA

3. Most recent Forward Pricing Rate Proposal (FPRP)

4. Letter(s) of Intent (LOIs), which include, at a minimum, the following:

i. Position Number/LCAT.

ii. Direct hourly labor rate.

iii. Submitted on offerors or subcontractor’s letterhead;

iv. Signed by the employer and prospective employee; and

v. A statement that the LOI is for RFP W15P7T-24-R-0021

vi. Payroll records and/or paystubs showing labor rate of pay and referenced to the labor category in the proposal.

vii. Salary survey data to include copies or screen shots and or the Excel export results of the actual salary survey data, which at a minimum, shall include the following:

viii. Source of data.

ix. Job title and description, corresponding percentile, and minimum number of years’ experience.

x. Geographic location; and

xi. Range of salary amounts with reference to applicability of amounts.

Note 1: If the labor rates proposed are not fully supported and/or the Government is unable to determine the realism of proposed labor rates, the Government may use salary survey data from Economic Research Institute (ERI), or other salary survey sources to make necessary Probable Cost adjustments.

Note 2: If using salary survey data to support direct labor rates, the offeror shall not propose any direct labor rates below the 50th percentile for any labor category. Note that each LCAT and skill level has a predefined minimum number of years’ experience, as outlined in Attachment 0001 Labor Categories, and identified by Position Number (PN), which must be accounted for in the salary survey source data. Proposed annual salary and hourly direct labor rates below the 50th percentile may be found unrealistic and subject to Probable Cost adjustments. Additionally, direct labor rates proposed shall also serve as “ceiling direct labor rates” in the event of award.

Note 3: The Prime shall provide an example, in Excel, of its wrap…