Attachment L-02 - Section L Rev 1.pdf

FA2521-21-R-0023, Attachment L-02

Source Selection Information – See FAR 2.101 and 3.104

CONTROLLED UNCLASSIFIED INFORMATION

Section L - Instructions, Conditions, and Notices to Offerors

1. General

1.1. Proposal Overview: The following instructions cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein.

The offeror's proposal shall include all data and information requested and shall be submitted in accordance with (IAW) these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), Contract Data Requirements List, and additional attachments. Non-conformance with the instructions provided may result in an unfavorable proposal evaluation.

1.1.1. General Requirements: 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 experience and will base its evaluation on the information presented in the offeror's proposal. Only one proposal may be submitted for each offeror.

1.1.2. Alternate Proposals: Alternative proposals will not be accepted for this acquisition. The contract types specified for each Contract Line Item Number (CLIN) in the solicitation are mandatory.

1.2. Information

1.2.1. Point of Contact: The Procuring Contracting Officer (PCO), Ms. Tammy Davis is the sole point of contact for this acquisition. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO at tammy.davis@spaceforce.mil, with a courtesy copy to Mr. Oren Gilbert at oren.gilbert@spaceforce.mil. Note: Be sure to include the Request for Proposal (RFP) number on all correspondence.

1.2.2. Debriefings: The PCO will promptly notify offerors of any decision to exclude them from the competitive range; whereupon they may request and receive a debriefing IAW FAR 15.505. Offerors excluded from the competitive range may request a preaward debriefing or they may choose to wait until after the source selection decision to request a postaward debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The PCO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable.

mailto:45CONS.CLOIS@us.af.miltammy.davis@spaceforce.mil

1.2.3. Discrepancies, Errors, Omissions, and Questions:

1.2.3.1. Discrepancies, Errors, and Omissions: If an offeror believes that the requirements in these instructions contain an error, omission or are otherwise unsound, the offeror shall immediately notify the PCO in writing with supporting rationale as well as the remedies the offeror is asking the PCO to consider as related to the omission or error. Government responses will be placed on System for Award Management (SAM) website at https://sam.gov for access by all offerors.

1.2.3.2. Questions: Address all questions or concerns to the point of contact (POC) listed above in paragraph 1.2.1 using the format provided in RFP Attachment L-01 Question and Answer Template. Offerors are encouraged to submit all questions and requests for clarifications no less than 10 days prior to the RFP closing date.

The decision to respond to questions and requests for clarifications made less than 10 days prior to the RFP closing shall be at the sole discretion of the PCO.

1.2.4. Electronic Reference Documents: All referenced documents for this solicitation are available on SAM and the Procurement Integrated Enterprise Environment (PIEE) Solicitation Module. Potential offerors are encouraged to subscribe for real-time email notifications when information has been posted to the website for this solicitation.

1.2.5. Communications: Exchanges of source selection information and Controlled Unclassified Information between Government and offerors will be controlled by the PCO. Email may be used to transmit such information to offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104 --- Controlled Unclassified Information” in the subject line. In order to facilitate the sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption.

1.2.6. Pre- Award Survey:

1.2.6.1. If the information on hand or readily available to the PCO is not sufficient to make a determination of responsibility IAW FAR 9.1, the offeror may be required to participate in a pre-award survey to determine if the offeror meets the responsibility requirements in FAR 9.104. The pre-award survey is conducted with the assistance of the offeror to determine its eligibility and ability to perform.

Refusal to participate in a pre-award survey and provide all requested information may be cause for rejection of the offer. If the offeror is aware of some circumstances in its performance record or current ability to perform which may result in a negative report, offeror should provide any information on mitigating circumstances or corrective action planned or taken.

https://sam.gov/ file://52sxht-as-d0tw1/CLOIS/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc#T2101 file://52sxht-as-d0tw1/CLOIS/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b3104

1.2.6.2. The pre-award survey may include performance of a formal financial capability risk assessment or audit by the Defense Contract Audit Agency (DCAA), or other personnel assigned by the PCO to perform the task. This effort would be performed IAW DFARS 232.072-1, and the information required for audit would include but not be limited to that identified in DFARS 232.072-2.

The contractor agrees to provide the financial information for such financial capability effort in a timely manner. Failure to provide the required data could result in the offeror being determined ineligible for award.

1.2.7. Amendment of Solicitation Prior to Proposal Closing: The Government reserves the right to revise and amend the solicitation prior to the proposal closing time.

Such revisions or amendments will be communicated by amendment(s) to this RFP. If such amendments require material changes in quantities or prices, the proposal closing date may be postponed by enough days to enable offerors to revise their proposals. In such cases, the amendment will include announcement of the new proposal closing date and time. Amendments will be posted at SAM and the PIEE Solicitation Module with the solicitation documents without notice. Offerors are responsible for accessing all amendments prior to proposal submission at Sam.gov or https://piee.eb.mil.

1.3. Submission: All volumes shall be delivered electronically using the PIEE Solicitation Module (https://piee.eb.mil). The maximum file size that can be uploaded into the PIEE Solicitation module is 1.9 GB. Offerors submitting via PIEE Solicitation Module should follow up via email to confirm receipt. Further information on the PIEE Solicitation Module can be found at: https://pieetraining.eb.mil/wbt/xhtml/wbt/sol/index.xhtml. They must be received no later than the date and time listed in block 9 of the SF 33. Offeror and offeror’s team are responsible for confirming proposal submission is received prior to the proposal due date.

NOTE: Proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3).

1.4. Proposal Organization and Format:

1.4.1. Organization: The offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits as specified in Table 1.

https://piee.eb.mil/

Table 1 Proposal Organization

Volume # Title Page Limit

Volume I Technical 50 page maximum (excluding Cross Reference Matrix and Staffing Matrix)

Volume II Past Performance Information 50 page maximum (excluding PPQs and Client Consent Letter)

Volume III Cost/Price No page limit

Volume IV Administrative Documents No page limit

1.4.1. General Format Instructions: Page size shall be 8.5 x 11 inches. Pages shall be single-spaced and shall be Times New Roman and of a size no less than 12-point font size with normal character spacing. Use at least one-inch margins on the top and bottom and 3/4-inch side margins. The background color of each page shall be white. Pages shall be numbered sequentially by volume. These page format restrictions shall apply to responses to evaluation notices (ENs). Hypertext links shall be the same minimum font size. However, the offeror may indicate hyperlinks by any color font or with a visible rectangle.

1.4.1.1. Page Limitations: Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to ENs. The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following: cover pages, table of contents, glossaries/acronym lists.

1.4.1.2. Cost or Pricing Related Data: All pricing information shall be addressed ONLY in the Cost/Price Proposal, Administrative Document Volumes, and in Section B of the Schedule of the RFP. Cost tradeoff information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and tradeoff decisions.

1.4.1.3. Cross Reference Matrix: To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. The offeror shall provide a Solicitation Cross Reference Matrix indicating specific PWS paragraph number, and the corresponding proposal paragraph in that section which addresses the referenced item. The Cross Reference Matrix will not count against the page count requirements.

1.4.1.4. Indexing: Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Table of Contents will not count against the page count requirements.

1.4.1.5. Tables, Charts, Graphs and Figures: Elaborate tables, charts, graphs, and figures are not desired. However, simplified tables, charts, graphs, and figures may be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and shall not exceed 11 x 17 inches in size. The font shall be Times New Roman and of a size no less than 10-point font with normal character spacing.

1.4.1.6. Glossary of Abbreviations and Acronyms: Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each.

Glossaries do not count against the page limitations for their respective volumes.

1.4.1.7. Cover Sheet and Labeling: A cover sheet shall be included in each volume, clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. Each volume shall be appropriately marked as prescribed by FAR 52.215-1(e), Restriction on disclosure and use of data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information. All proposals shall be clearly marked as "Source Selection Information--See FAR 2.101 and FAR 3.104 -- Controlled Unclassified Information".

1.4.1.8. PDF and Excel Format: To enable the Government to successfully view the proposals electronically, the offeror’s electronic copy of the proposal shall be submitted in Adobe Portable Document File (PDF) format. For files prepared in MS Excel XLS format, the XLS file shall have open cells allowing the Government to view/evaluate all formulas and shall not contain pivot tables. The offeror shall generate “bookmarks” within each PDF file for at least each section and subsection of the document. Bookmarks shall be generated based on indexed entities appearing in the document Table of Contents. The PDF file has a built-in security function. The offeror shall set all security options in each PDF file to “allowed.” All text, including tables and figure identifiers, shall be indexed and 100% searchable text.

1.4.1.9. Other Requirements: The offeror shall not embed sound or video files into the proposal files. Minimize the use of scanned images and keep embedded graphics as simple as possible.

https://cs1.eis.af.mil/sites/afcc/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc#T2101 https://cs1.eis.af.mil/sites/afcc/knowledge_center/Documents/AFFARS_Library/5315/templates/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b3104

2. Volume I – Factor 1 –Technical (50-page maximum excluding Cross Reference Matrix and Staffing Matrix)

2.1. Factor 1 –Technical Specific Instructions:

2.1.1. General. The Technical Volume should be specific, complete, and address your technical solution for meeting the Government’s minimum performance or capability requirements of the technical factor. Legibility, clarity, and coherence are very important. Your responses to the Technical Capability Factor will be evaluated against the assessment criteria defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying this subfactor. By your proposal submission you are representing that your firm will perform all the requirements specified in the RFP. It is not necessary or desirable for you to say so in the proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the RFP.

2.1.2. Format and Specific Content: The following information shall be provided in the written technical proposal and will be evaluated to assess the proposed technical approach and associated technical risk IAW Section M, Evaluation Basis for Award. The written technical proposal shall address each of the following subfactors to describe the offeror’s proposed approach to performing the requirements set forth in the PWS and all attachments. The Technical volume shall be organized according to the following general outline:

(1) Cover Sheet

(2) Table of Contents

(3) Glossary

(4) Cross Reference Matrix

(5) Technical Capability Factor

2.1.3. Technical Capability Factor (Acceptable/Unacceptable): Program Management. The Government will evaluate each offeror’s Program Management approach detailed in its proposal on an Acceptable/Unacceptable basis using the following criteria listed as subfactors. For each subfactor, the offeror shall identify risks, if any, associated with the proposed approach and actions the offeror will take to mitigate the identified risks. If no risks/mitigations are identified in the offeror’s proposal, it indicates the offeror does not consider there to be any risk associated with their proposed approach.

2.1.3.1. Subfactor 1 – Organization: Offeror’s proposal shall include an organizational chart and staffing plan that demonstrate a sound organizational structure that defines responsibilities of all organizational elements. Offeror’s organizational chart shall define a hierarchical structure of positions proposed by the offeror to include supervisory functional roles and relationships. Offeror’s staffing plan shall provide overall proposed staffing levels (rolled up by labor category), broken down by work area and function, and shall include a description of each labor category. For positions subject to Collective Bargaining Agreement (CBA), if labor categories titles are different than shown on the current CBAs provide a cross reference table linking existing titles with the proposed. Offeror’s proposal shall acknowledge Key Personnel identified in the ABOS PWS.

2.1.3.2. Subfactor 2 – Resource Management: Offeror’s proposal shall include a filled-out ABOS Staffing Matrix (see RFP Attachment L-04) to define adequate staffing levels and skills to accomplish program requirements in alignment with the PWS that enables organizing, managing, and coordinating of resources.

Staffing Matrix differs from staffing plan by providing a breakdown of proposed labor for each labor category by CLIN. Total proposed staffing identified in the staffing plan for each labor category shall match the Staffing Matrix breakdown for each category. Offeror’s Staffing Matrix shall identify any variance in labor hours by labor category and performance year. Offeror’s proposal shall include a narrative explanation for variance in labor hours across performance years.

Offeror’s proposal demonstrates an acceptable approach to managing personnel in a manner conducive to executing a fluctuating workload driven by quick-response requirements of the PWS that represents an acceptable level of risk. The proposal provides an acceptable approach to manage any variance between staffed FTEs captured under FFP CLINs and labor called up via work orders under CPFF CLINs (Reference Attachment 19 – ABOS Workload Indicators).

2.1.3.3. Subfactor 3 – Transition Plan: The offeror shall provide an outline for transition (separate from the detailed transition plan required IAW the ABOS PWS), consisting of a high-level overview (with a description of the required task(s) to meet major milestones, and timelines), which demonstrates the ability to achieve full performance within 90 days from start of the transition period (IAW PWS para. 1.11).

2.1.3.4. Subfactor 4 – Foreign National Workforce: Describe your approach to manage a foreign national workforce in a foreign remote environment, and interface with Host Nation representatives. (IAW PWS paragraph 1.10)

3. Volume II – Factor 2 Past Performance (50 Page Limit excluding Past Performance Questionnaires (PPQS) and Client Consent Letter)

3.1. General Instructions: The offeror shall submit present and past performance information IAW the format contained in the “FACTS Sheet” (See RFP Attachment L-06) and the following paragraphs. A summary page shall be provided for this acquisition, describing the proposed role of the offeror and the offeror’s team (nature of work and percentage of overall work). Each offeror shall submit a separate FACTS sheet for up to a total of four of the most recent and relevant contracts for the offeror or offeror’s team. Offeror is defined as the prime contractor or prime offeror to which the contract will be awarded. If the offeror is a mentor protégé, past performance of either the mentor, the protégé, or mentor protégé will count as past performance of the prime offeror/contractor rather than as a subcontractor in accordance with 13 CFR 125.8(e).

Note: At least one FACTS sheet must be submitted from the prime contractor in order to receive other than a neutral rating for Performance Confidence Assessment.

The Government will consider the past performance performed by a predecessor, affiliates, other divisions, or corporate management of the offeror or team member if the Government can determine that the assets or resources of the predecessor, affiliates, other divisions, or corporate management would be brought to bear in performance under the instant contract. The FACTS Sheet shall clearly indicate the division or corporate organization that performed or is presently performing the contract.

3.2. Format and Specific Content: The following information shall be provided in the written past performance proposal and will be evaluated IAW Section M, Evaluation Basis for Award. The past performance volume shall be organized according to the following general outline:

(3) Summary Page

(4) FACTS Sheet

3.3. Ordering Type Contracts Submission: If the contract you are submitting is an ordering type contractual vehicle (for example, including but not limited to an Indefinite Delivery “D” type contract per FAR 16.5), only after issuance of a delivery/task order does performance occur. Given this, an individual order (or series of orders) under the basic ordering contract shall be submitted, in lieu of just the basic ordering contract itself.

All information provided to the Government, for an ordering type contractual vehicle, shall be at the order level (i.e. a delivery/task order).

3.3.1. When determining what order (or series of orders) to submit for evaluation, please reference Section M for details on how the Government will evaluate each submitted effort for recency, relevancy, and quality. In order to convey the optimal programmatic scope and magnitude of effort and complexities, the offeror should consider submitting a series of orders, if possible. However, a series of orders should only be submitted if the series of orders is for continuous technical scope demonstrating relevancy to the instant acquisition. Not all ordering type contractual vehicles will have series of orders that meet these criteria. In this instance, only the single order demonstrating relevant technical scope should be submitted for evaluation.

3.3.2. When submitting an individual order (or series of orders) under an ordering type contractual vehicle, it is important that the offeror’s past performance information be accurate, complete, and in the correct format. If the information is not submitted in the correct format, the Government will not be able to evaluate the effort for recency, relevancy, and quality. There are specific places for submission of this information in the FACTS Sheet (See RFP Attachment L-06).

Please ensure the information submitted, in the FACTS Sheet RFP Attachment L-06, is for each order (or series of orders), in lieu of just the basic ordering contract itself. This includes but is not limited to information such as the dollar value and period of performance for each order.

3.3.3. Series of Orders: When submitting a series of orders for evaluation, the offeror should list the recent orders under the basic ordering type contractual vehicle that demonstrate relevancy, as defined in Section M paragraph 3.4.1. Per the Section M paragraph 3.5., if an offeror submits a series of orders for evaluation, the total dollar value of each order (in the series of orders), the period of performance dates of each order (in the series of orders) shall be submitted.

The total dollar value of each order (in the series of orders) shall be added up to calculate the Total Dollar Value to be used in the evaluation, for the submitted effort. The total period of performance of each order (in the series of orders) shall be added up to calculate the Total Period of Performance to be used in the evaluation, for the submitted effort. The type and complexity of data deliverables provided on each order (in the series of orders) shall be evaluated as a whole for the series of orders. Caution: All orders within the series of orders, being submitted, should be for the same continuous technical scope demonstrating relevancy to the instant acquisition. The Government reserves the right to request additional information from the offeror or Points of Contacts provided to verify that the series of orders is for the same continuous technical scope.

3.4. FACTS Sheet: The offeror shall submit up to four FACTS Sheets. FACTS Sheet responses shall clearly correlate present and past performance with the requirements of this RFP. The FACTS Sheet responses must address all of the information requested in RFP Attachment L-06.

3.4.1. Points of Contact (POCs): Provide the most current information for the POCs identified on each FACTS Sheet. At least two of the following (listed in descending order of availability) should be identified as current POCs on the FACTS Sheets:

(1) Procuring Contracting Officer/Administrative Contracting Officer/Contract Negotiator/Contract Administrator or equivalent

(2) Program/Project Manager, or equivalent

(3) Other (As specified in your FACTS Sheet)

3.4.2. Performance Problems: If problems were encountered during the performance of the identified contracts, provide evidence of the ability to isolate the root causes of problems and include in the FACTS Sheet a description of programs or actions taken to resolve those causes. Problems not addressed in the FACTS Sheet but found by the Government during the evaluation of the information in this volume, will be assumed to still exist. Note: In the case of Contractor Performance Assessment Report System

(CPARS), if your input has already been provided and the rationale/circumstances have not changed, DO NOT repeat them here.

3.5. Past Performance Questionnaire (PPQ): The PPQ (see RFP Attachment L-05) will be one means used by the Government to obtain present/past performance information. Offerors shall not submit PPQs to contract POCs for which they did not submit a FACTS Sheet. The Government reserves the right to change, alter, and/or supplement the questionnaire without further notice to the offeror(s). The offeror shall send out and track the completion of the PPQ (See RFP Attachment L-05) to each of the POCs identified in each FACTS Sheet. Once the PPQs are completed by the POCs, the information contained therein shall be considered source selection sensitive and shall not be released to the offeror. Therefore, any exchange/contact between the offeror or offeror’s team and the POCs in regard to comments made on the questionnaire is not permitted. Offerors should exert their best effort to ensure that at least two POCs per relevant contract submit a completed PPQ directly to the Government not later than the date established in the RFP for receipt of proposals. The responsibility to send out and track the completion of the Present/Past Performance Questionnaires rests solely with the offeror.

3.6. Consent/Client Letter: The offeror shall submit a consent letter executed by each of the offeror’s team members authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter authorizing release to the Government of requested information on the offeror's performance. Submit the Consent/Client Letters as an Appendix to Volume II Past Performance. The Consent/Client Letters will not count against the page count requirements.

3.7. Follow-up Discussions: The Government may conduct follow-up discussions with any of the people identified in the FACTS Sheets, PPQ, or in the offeror’s Present/Past Performance Volume. Pursuant to FAR 15.305(a)(2)(ii), the Government may obtain other information by sending out additional questionnaires and through other sources, other than those listed within the FACTS Sheets.

4. Volume III – Factor 3 Cost/Price (No page limit)

4.1. General: This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness/realism of your proposed cost/price to determine the price fair and reasonable. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal.

Additionally, unbalanced pricing may pose an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Data shall be provided IAW FAR 15.403-5. If, after receipt of proposals, the PCO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit additional cost or pricing data.

4.2. Format and Specific Content: The cost/price proposal shall be based on the offeror’s technical approach to meeting the Government’s PWS (and other attachments) requirements. The offeror shall explain any inconsistency, whether real or apparent, between promised performance and cost/price. It is the offeror’s responsibility to demonstrate cost/price reasonableness. The Cost/Price volume shall be organized according to the following outline:

(3) Introduction

(4) Accounting System Information

(5) Purchasing System Information

(6) Indirect Rate Descriptions

(7) Subcontractor Information

(8) Explanation of Proposed Cost

(9) Cost Mischarging Plan

(10) Glossary/Acronyms list

(11) Cost Workbook

4.2.1. Cover Sheet: The Cost/Price Volume shall include a cover sheet as instructed in paragraph 1.4.1.7 that contains the name, address, and telephone number of the cognizant auditor office that is responsible for your audit review including whether your auditor office has approved your accounting/estimating system. If you have reached an agreement with your auditor office on use of forward pricing rates/factors, identify the agreement, include a copy, and describe its nature.

4.2.2. Table of Contents: Provide a table of contents as instructed in paragraph

1.4.1.4. containing an overview of all data accompanying or identified in the Cost/Price Volume.

4.2.3. Introduction: The introduction will describe the offeror’s team structure, on a total cost basis. Define each team member’s role and clearly identify which CLINs (or portions thereof) are anticipated to be subcontracted to each team member. Identify the planned contract type for each subcontractor.

4.2.4. Accounting System Information: IAW FAR 16.301-3(a)(3), Limitations, offerors are not eligible to receive cost-type contract or task orders unless their accounting system is adequate for determining costs applicable to the contract or order. Furthermore, the Government cannot approve a cost-type subcontract to a proposed subcontractor that does not have an adequate accounting system.

Indicate whether each subcontractor’s accounting system has been audited and determined acceptable, audited and determined not acceptable, or never audited unless the planned subcontract type is firm-fixed price. Identify the Government agency that audited the accounting system and provide evidence if determined acceptable. Evidence shall be in the form of the most recent applicable Government agency correspondence. If the offeror's accounting system has been audited and not accepted, provide details such as date of audit, deficiencies identified, corrective steps taken since disapproval, and reasons why approval of the accounting system is now assured. If the offeror's accounting system has never been audited, the offeror must explain its understanding of the characteristics of an acceptable accounting system for Government cost-type contracts, describe the accounting system employed, identify the software package used, and indicate any other steps the offeror has taken to ensure that Government approval will occur. An offeror who fails to provide evidence that their accounting system complies with all the requirements in DFARS 252.242- 7006 may be deemed non-responsible IAW FAR 9.104-1(e).

4.2.5. Purchasing System: Provide a summary description of your purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Also, identify any deviations from your standard procedures in preparing this proposal. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

4.2.6. Indirect rates: The offeror shall submit a narrative description of each indirect rate utilized for all Cost CLINs in the proposal and the rates relationship to direct cost. Show the composition of each burden and indirect expense pool proposed. Submit a separate breakdown to the lowest transparency for each indirect overhead expense pool, such as local, division, and home office overheads, procurement and material handling burdens, and service center burdens. Identify the allocation base for each pool and application of each rate.

4.2.6.1. Rate Table: Complete the proposed indirect rate table 2 showing proposed rates for each performance year. Identify if the rates are defined in a Forward Price Rate Agreement (FPRA) or are established elsewhere.

If the rate is established elsewhere, please explain the basis for which the rate was developed. For rates not based on an FPRA, include the latest annual final audit which identifies current company rates. Identify your fiscal year period and how any calendar difference from the performance year period (1 Jan – 31 Dec), except Year 10 will be separated in two six months performance periods from (1 Jan – 30 Jun) and (1 Jul – 31 Dec) impacts the proposed rate. If composite rates are used, provide a complete breakdown of calculations for the rates proposed. If rates are adjusted from the FPRA, or final rates in the latest completed fiscal year, provide a narrative description as to how the rates were developed. Provide an explanation of the basis of future year rate projections and the impact the ABOS award would have to the rates. Provide the same information for all members of the offeror’s team performing under cost CLINs.

Table 4.1.1.5A Indirect Rate Table Indirect Rates: Year 1 Year 2 Year 3 Year 4 Year 5

Fringe Benefits Overhead Material Handling Subcontractor Handling G&A etc.

Table 4.1.1.5A Indirect Rate Table (Cont’d) Indirect Rates: Year 6

Year 7

Year 8 Year 9 Year 10

1 Jan – 30 Jun Year 10

Option to Extend Services

1 Jul – 31 Dec Fringe Benefits Overhead Material Handling Subcontractor Handling

G&A Etc.

4.2.7. Subcontractor Information: Proposals for all subcontractors performing under a cost CLIN shall be submitted within the offeror’s proposal.

Subcontractor cost proposals should be submitted through the offeror to the PCO.

However, if the subcontractor considers its cost proposal information proprietary, it may be submitted directly to the PCO no later than the date and time the offeror contractor’s proposal is due. If the offeror is a Joint Venture (JV), all JV information shall be submitted in the same cost proposal and cost workbook. The offeror’s proposal shall uniquely identify subcontractor costs within the supporting cost documentation. Subcontractor cost documentation shall be submitted at the same level of detail and in the same format as the prime’s cost proposal. The offeror’s cost detail must clearly identify portions of the proposal where supporting detail is provided by the subcontractor. The offeror is responsible for the consistency of the cost data between the offeror’s submission and any subcontractor data submitted directly to the PCO.

4.2.7.1. Subcontractor Analysis: For each proposed team member, the offeror shall provide an analysis to determine the price reasonableness of the member’s proposal. Include the team member’s methodology to estimate costs and results of your reviews and evaluations of those proposals. Explain how the team member’s effort relates to the overall effort. Any price adjustment to the team member’s proposed prices that are included in the offeror’s proposal submission, including discounting or expected decreases to be achieved in negotiations, shall be fully identified and explained. Offerors are required to provide the results of their price or cost analysis of subcontractor proposal as required in FAR 15.404-3(b).

4.2.8. Explanation of Proposed Cost: In order to support evaluation of price reasonableness and cost realism, offerors shall submit narrative data explaining how proposed cost/price were derived. The burden of proof for credibility of proposed prices/costs rests with the offeror. IAW FAR 15.403-1(b) and 15.403- 3(a), data other than certified cost or pricing data may be required to support a determination of cost/price reasonableness.

4.2.8.1. Productive Man-Year Hours: The offeror shall identify productive labor hours associated with one (1) man-year effort (Full-Time Equivalent (FTE)) for each type of labor (Service Contract Act (SCA), Collective Bargaining Agreement (CBA), etc.). The offeror shall identify productive labor hours for all team members if different from the offeror’s. The offeror shall also include information regarding productive man-year hours within the cost workbook (See 4.2.11) in the format specified.

4.2.9. Cost Mischarging Prevention Plan: Due to the similar nature of labor categories which may be used to perform work under both fixed price and cost type CLINs, the offeror must clearly identify positions which may be used for both. Any labor category which will be treated as an indirect labor cost must be identified in the proposal narrative. The offeror shall identify any proposed labor category which will be utilized under both Firm Fixed Price (FFP) and Cost-Plus Fixed Fee (CPFF) CLINs, describe controls which will be implemented to ensure labor is charged to the correct CLIN and identify internal audit processes which will validate cost allocation accuracy. Provide the same information for subcontractor performing under both FFP and CPFF CLINs. Supporting cost documentation must clearly identify the FTE division among CLINs for the total number of positions identified in the organization chart in the Technical Volume.

4.2.10. Glossary/Acronym List: The offeror shall include a glossary/acronym list defining unique terms and acronyms used in the cost/price proposal.

4.2.11. Cost Workbook: Offerors shall submit the cost data in the Government provided Cost/Price Workbook (RFP Attachment L-03). Offerors shall submit the level of data required to support the cost proposed as it correlates to the proposed technical approach. Instructions are included in the first tab of the cost workbook, with additional instructional notes on each subsequent tab.

5. Volume IV – Administrative Documentation (No Page Limit)

5.1. General Administrative Information:

5.1.1. Contractor Responsibility Information: Concurrent with submission of the documents required in Table 1, the offeror shall contact their cognizant auditor for instructions on how and when to submit documents for use in a pre-award survey.

Provide a listing of contracts performed by the offeror contractor within the last three years. For each contract, include contract number, title, whether you were the prime contractor or subcontractor, contract amount and point of contact (email and phone number) for the Contracting Officer or Program Manager. Provide a copy of the offeror’s financial statements for the last three completed fiscal years. For contracts performed as a subcontractor, provide point of contact information for the prime contractor. For offerors proposing as a JV, include the contract number, title, whether the contract was performed by the same JV or a single partner, contract amount and Contracting Officer or Program Manager point of contact (email and phone number) for each. For offerors proposing as a JV, provide a copy of the JV agreement identifying the financial structure and financial statements for the last three completed fiscal years. If the JV does not have financial statements for three completed fiscal years, provide the information of each JV partner. The Government may collect additional information from additional sources to include, but not limited to, the Past Performance Information Retrieval System, Federal Awardee Performance and Integrity Information System, Electronic Subcontract Reporting System, or other databases; interviews with Program Managers, Contracting Officers, and Fee Determining Officials; the Defense Contract Management Agency, and commercial sources.

5.1.2. Department of Labor Equal Employment Opportunity (EEO) Clearance. IAW FAR Part 22.805, the PCO must request pre-award clearance on the offeror or members of the offeror’s team (excluding subcontractors) from the appropriate Office of Federal Contract Compliance Programs (OFCCP) regional office. If an offeror is listed in OFCCP’s National Pre-award Registry, located at https://www.dol.gov/agencies/ofccp/pre-award/registry, the offeror shall provide the PCO a copy of the database registration for Government verification as part of the proposal submission. If an offeror is not listed in the registry, include a statement providing this information and the PCO will request an EEO clearance review.

5.2. Format and Specific Content: The Administrative volume shall be organized according to the following outline:

(3) Section A

(4) Section B

(5) Section G

(6) Section I

(7) Section K

(8) Proposal Assumptions and Exceptions to Terms and Conditions

(9) Mission Essential Services Plan

(10) Organizational Conflict of Interest

(11) JV and Mentor/Protégé Agreement (If applicable)

5.2.1. Cover Sheet: The Administrative shall include a cover sheet as instructed in paragraph 1.4.1.7 in addition to the following information.

5.2.1.1. Authorized Personnel: Provide the name, title and telephone number of the company/division point of contact regarding source selection decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

5.2.1.2. Company/Division Information: Provide company/division's street address, county and facility code; CAGE code; DUNS code and/or Unique Entity ID (UEI); TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether it’s a subcontractor and the percentage of work to be performed at each location.

5.2.2. Table of Contents: Provide a table of contents as instructed in paragraph

1.4.1.4. containing an overview of all information in the Administrative Volume.

5.2.3. Section A – SF 33: Complete blocks 13, 14, 15, 16, 17 and 18 of the RFP Section A, SF 33; in doing so, the offeror accedes to the contract terms and conditions as written in RFP Sections A through K. These sections constitute the model contract. An official having the authority to bind the offeror contractually must sign the SF 33. One copy of SF 33 must bear an original signature. The offeror shall make a clear statement on the SF 33 of the proposal contract documentation volume that the proposal is valid until 240 days after proposal due date and acknowledge all amendments issued (if applicable).

5.2.4. Section B – Supplies or Services and Prices: Completed pricing information in Section B of the model contract. CLIN level pricing in Section B shall be consistent with the information provided in Volume III Cost/Price Volume.

5.2.5. Section G – Contract Administrative Data. Complete any fill-ins required.

5.2.6. Section I – Contract Clauses. Complete any fill-ins required.

5.2.7. Section K – Representations, Certifications, and other Statements of Offerors. Complete representations, certifications, acknowledgments, and statements. Offeror must have filled out an online provision FAR Clause 52.204-8 Annual Representations and Certifications (September 2021), Online Reps and Certs at System for Award Management (http://www.sam.gov). Offer shall ensure certification as a small business under North American Industry Classification System (NAICS) 561210.

5.2.8. Proposal Assumptions and Exceptions to Terms and

Conditions: Offerors must clearly identify any proposal assumptions or exceptions to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken.

Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements. Failure to meet a requirement may result in an offer being ineligible for award.

5.2.9 Mission Essential Services Plan. The offeror shall submit a written plan describing how it will continue to perform the essential contractor services during periods of crisis. The offeror’s plan shall address, at minimum, the requirements laid out in DFARS 252.237-7024, Notice of Continuation of Essential Contractor Services, and DFARS 252.237-7023, Continuation of Essential Contractor Services.

5.2.10. Organizational Conflict of Interest (OCI): Submit a mitigation plan for PWS paragraphs 2.5.8.1. and 2.5.11.6. and any other potential areas that may cause an organizational conflict of interest or a statement of assurance that no plan is required. If a plan is provided, the plan should address the considerations addressed in AFFARS 5352.209-9000 (Oct 2019).

5.2.11. JV and Mentor Protégée Agreements: Offerors proposing as a JV must provide a copy of the JV agreement that is signed and dated by all JV members.

Offerors proposing under a Mentor Protégée Agreement must provide a copy of the approved Small Business Administration agreement, identify the percentage of work to be completed by the mentor and the protégée, identify the Responsible Manager (also known as a named employee of the small business managing venture as the manager with ultimate responsibility for performance of the contract) and provide proof of employment with the protégée or a commitment letter. The individual identified as the Responsible Manager shall not be employed by the mentor and become an employee of the small business for purposes of performance under the JV.