B08 Attachment 0014 - CHS 6 Section L (31 Oct 2022).docx
DOCX document 146 KB Posted
- Attached to
- Common Hardware Systems 6th Generation (CHS-6) W15P7T-23-R-0001 Federal contract opportunity
- Solicitation number
- W15P7T23R0001
About this file
This is a request for proposal for the Common Hardware Systems Sixth Generation contract. The contract is an indefinite delivery, indefinite quantity contract with a ten year period of performance to provide total lifecycle management solutions for commercial information technology hardware and services to the U.S. Army, Department of Defense, and federal agencies. Requirements include task orders, delivery orders, technology insertions, logistics support, engineering services, and system integration. The total estimated value is $7.9 billion. Proposals are due by November 22, 2022 and will be evaluated using best value tradeoff. Awards will be fixed price for hardware and either fixed price or cost plus fixed fee for services. The solicitation outlines submission requirements and evaluation criteria for cost, technical, past performance, small business participation, and certifications volumes.
View the file
Other files for this federal contract opportunity
Show all 50
Common Hardware Systems 6th Generation (CHS-6) W15P7T-23-R-0001 has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Solicitation: W15P7T-23-R-0001 Attachment 14, Section L 31 October 2022
COMMON HARDWARE SYSTEMS (CHS)
SECTION L
INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS
SOLICITATION SUBMISSION INSTRUCTIONS
L.1.1 PROPOSAL SUBMISSION INSTRUCTIONS
L.1.1.1 Each Offeror shall submit no more than one (1) proposal via Procurement Integrated Enterprise Environment (PIEE) https://piee.eb.mil, no later than 22 November 2022 at 2:00 PM Eastern Standard Time. Offerors shall follow the upload instructions provided on the website for Non-CAC Users. All questions shall be submitted electronically via email by 20 October 2022 to the Contracting Specialist, Mr. Todd M. Strasavich, todd.m.strasavich.civ@army.mil, and to the PCO, Mr. Phillip S. Vitakis, phillip.s.vitakis.civ@army.mil. The Offerors proposal shall remain valid for 365 days after the date of submission.
L.1.1.2 PROPOSAL FILES
The Offeror’s proposal shall be submitted in the file format set forth below. The Offeror’s proposal shall consist of six volumes. The Volumes are: I – Executive Summary; II –Technical; III – Cost/Price; IV – Past Performance; V – Small Business Participation; and VI – Solicitation, Offer and Award Documents and Certifications and Representations. Files shall not contain classified data. The use of hyperlinks in proposals is prohibited.
L.1.1.3 FORMAT
L.1.1.3.i 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 with the complete company name, date and solicitation number in the header and footer. A Table of Contents for each volume shall be created using the Table of Contents feature in MS Word. MS Word (.docx) files shall use the following page set-up parameters:
Margins – Top, Bottom, Left, Right - 1” Gutter – 0” From Edge – Header, Footer - 0.5” Page Size, Width – 8.5” Page Size, Height – 11” L.1.1.3.ii Each paragraph of narrative text shall be separated by at least one blank line of width meeting 12-point font. The Offeror shall use a standard, 12-point minimum font size. Arial or Times New Roman fonts are required. Tables and illustrations may be landscape and use a reduced font size not less than 8 point.
L.1.1.3.iii Pages formatted in violation of these instructions, for example by exceeding the margin, or not complying with font or spacing restrictions, may not be evaluated.
L.1.1.3.iv The format of the Technical Volume of the Offeror's proposal shall be paragraphed and numbered consistent with the factors and sub-factors described below.
L.1.1.4 FILE PACKAGING
L.1.1.4.1 All volumes shall be saved individually, then consolidated into one compressed (zipped) file. This compressed file shall be saved using the following naming convention: “Company Name.proposal.zip” using WinZip version 19 or later, or as separate uploads in their native format using MS Office 2016 or earlier, i.e. docx, xlsx, pptx, etc. Signature pages can be submitted as a consolidated PDF file. Each volume shall be named with date, company name, then the file name (ex: Date_CompanyName_EXSUM_Docx). Please note - Self extracting .exe files are no longer accepted.
| VOLUME |
| VOLUME TITLE |
| PAGE LIMIT |
| File Name |
| I |
| Executive Summary |
| 10 Pages |
| EXSUM.DOCX |
| II |
| Technical |
| *160 Pages |
| TECH.DOCX |
| III |
| Cost/Price |
| No page limit |
| CHS6PRICE.XLSX |
| IV |
| Past Performance |
| *50 Pages |
| PASTPERF.DOCX |
| V |
| Small Business |
| **25 Pages |
| SMALLBIZ.DOCX |
| VI |
| Solicitation, Offer, and Award Documents, and Certifications and Representations |
| No page limit |
| SOL.DOCX |
* Page count excludes Certifications, Cross Reference Matrix, Past Performance Questionnaire Forms, Past Performance Letters of Commitment, and Written Consent to release Major Subcontractor past performance information.
** Page count excludes the SB Subcontracting Plan and the Small Business Commitment Participation Document (SBPCD) supporting documentation.
L.1.1.4.2 Each printed 11”-x-17” page of a foldout for only Tables and Standalone Graphics without supporting paragraphs shall count as one (1) page and shall be numbered accordingly. Past Performance, Volume IV, shall not exceed 50 total pages including Offeror and each Major Subcontractor.
L1.1.4.3 PLEASE NOTE: No cost or price information shall be presented in Volumes I, II, IV, V or VI. No volume shall incorporate portions of any other volumes by reference. Information included by reference within one volume to other volumes will not be evaluated.
L.1.1.5 PAGE COUNT
Any pages that exceed the page counts in the above Table for each volume or attachment will not be evaluated. The page count will be determined by counting the pages in the order they come up in the print layout view. Annexes, documentation, attachments, Contract Data Requirements List (CDRLs) etc., specifically required by this solicitation will not count against the Offeror’s page limitation. The following will not count towards any page limitations: any pages that are not evaluated due to violation of the margin, font or spacing restrictions; the title page; table of contents; and acronym list.
L1.1.6 GENERAL CONTENT REQUIREMENTS
All information shall be confined to the appropriate file. The Offeror shall confine submissions to essential matters, sufficient to define the proposal and provide an adequate basis for evaluation. Offerors are responsible for including sufficient details, in a concise manner, to permit a complete and accurate evaluation of each proposal. Proprietary information shall be clearly marked.
CONTENT INSTRUCTIONS
L.2.1 VOLUME I – EXECUTIVE SUMMARY
The Offeror shall provide an overview of its proposal and its teaming/subcontracting arrangements (if applicable) summarizing all parts of the proposal except Volume III and Volume VI. Offerors are reminded that the Executive Summary is an introductory summation of the proposal. No information shall be in the Executive Summary which does not appear elsewhere in the proposal. Information that is only in the Executive Summary will not be evaluated.
L.2.2 VOLUME II – TECHNICAL
L.2.2.1 The proposal shall not reflect a marketing or sales presentation. Unnecessarily elaborate proposals beyond those sufficient to present a complete and effective response to this solicitation are not desired. The proposal shall illustrate the Offeror’s capability and clearly demonstrate the organization and methodology that will satisfy the solicitation requirements. The proposal shall clearly describe the technical solution and overall approach to the solicitation requirements and shall address all of the sub-factors and elements identified in Section L.2.2.2 of Volume II – Technical. The Offeror may include information about its related experience performing proposed processes and procedures in its Volume II – Technical proposal for evaluation of specific technical approaches and related technical proposal risk. However, any information about the Offeror’s experience that is included in the technical proposal will not be considered for the Volume IV – Past Performance. Any past experience that an Offeror would like to be evaluated for Past Performance shall be included in Volume IV – Past Performance. No part of the technical proposal shall incorporate portions of other volumes of the proposal by reference.
L.2.2.2 Volume II – Technical shall be broken into the following Technical Sub-Factors and Elements:
Technical Sub-Factor 1: Processes Processes Element 1: Technology Insertion Processes Element 2: Delivery Order Processes Element 3: Task Order (Other than Design & Engineering Services) Processes Element 4: Design and Engineering Services Technical Sub-Factor 2: Logistics/Warranty Program Logistics/Warranty Program Element 1: Warranty and Repair Support Technical Sub-Factor 3: Configuration Management (CM), Quality Assurance (QA) and Supply Chain Risk Management (SCRM) CM, QA, and SCRM Element 1: Configuration Management CM, QA, and SCRM Element 2: Quality Assurance CM, QA, and SCRM Element 3: Supply Chain Risk Management Technical Sub-Factor 4: Program and Data Management Program and Data Management Element 1: Program Management Program and Data Management Element 2: Integrated Data Environment (IDE) and Integrated, web-based system
L.2.2.3 TECHNICAL SUBFACTOR AND ELEMENT CONTENT INSTRUCTIONS
L.2.2.3.1 Technical Sub-Factor 1 – Processes L.2.2.3.1.i Processes Element 1 -- Technology Insertion (TI):
L.2.2.3.1.i.1 The Offeror shall describe its approach to the TI process in detail. The TI process includes the time period from the date on which the Government provides draft specifications to the Prime, to the date on which the Prime provides a proposal to the Government. The approach shall meet the requirements set forth in PWS paragraph 3.3. The Offeror shall provide a detailed step-by-step outlined approach and associated processing time (number of business days) of:
i. one (1) TI for V1 Dell Laptop 7720 (210-ATEG) Part #: 751737751 equipment; and
ii. TIs for the following equipment being processed at the same time: V1 NetApp FAS2750 Storage, V1 Intellipower UPS FA10480, V1 Pelican 1560 Protector, V1 Catalyst 9300 48-port PoE+, PN: C9300-48P-A; and V1 Mercury Systems - RES XR6-GREY 2U 4-Socket Server.
L.2.2.3.1.i.2 In each of the above approaches, the Offeror shall describe the following, in addition to meeting the requirements set forth in PWS 3.3:
| i. | the processes that the Offeror would use to effectively derive the best material cost for each item; and |
| ii. | the vendor/OEM relationship with the Offeror (including any vendor/OEM discount that the Offeror and/or the CHS contract would receive). |
NOTE: For proposal purposes, the number of days between the date on which the Government provides draft specifications to the Prime and the date on which ACC sends the RFP to the Prime is 12 business days.
NOTE: If the approach to the processes differs between L.2.2.3.1.i.2.i & L.2.2.3.1.i.2.ii, then the Offeror may provide an explanation for each. However if the processes are the same, the Offeror shall annotate that in their proposal.
L.2.2.3.1.ii Processes Element 2 -- Delivery Order (DO):
L.2.2.3.1.ii.1 The Offeror shall describe its approach to the DO process in detail. The DO process includes the time period from the date on which the Government sends draft order request to the Prime, to the date on which the DoD/Federal Customer receives the equipment. The approach shall meet the requirements set forth in PWS paragraph 3.4.
L.2.2.3.1.ii.2 The Offeror shall provide a detailed step-by-step outlined approach for a DO for a quantity of:
i. 100 V1 Dell Laptop 7720 (210-ATEG) Part #: 751737751; and
ii. 150 V1 Dell Laptop 7720 (210-ATEG) Part #: 751737751 that are ordered within 30 days of the above DO in L.2.2.3.1.ii.2.i being awarded; and
iii. 100 of each of the following items being processed at the same time: V1 NetApp FAS2750 Storage, V1 Intellipower UPS FA10480, V1 Pelican 1560 Protector, V1 Catalyst 9300 48-port PoE+, PN: C9300-48P-A; V1 Mercury Systems - RES XR6-GREY 2U 4-Socket Server; and
iv. 150 of each of the following items: V1 NetApp FAS2750 Storage, V1 Intellipower UPS FA10480, V1 Pelican 1560 Protector, V1 Catalyst 9300 48-port PoE+, PN: C9300-48P-A; and V1 Mercury Systems - RES XR6-GREY 2U 4-Socket Server.
a. The DOs for the items in L.2.2.3.1.ii.2.iv shall also meet the following requirements:
1. Be processed at the same time; and
2. Be ordered within 60 days of the DO in L.2.2.3.1.ii.2.iii being awarded; and
3. Be delivered to multiple locations simultaneously (including Continental United States [CONUS] and Outside the Continental United States [OCONUS]); and
4. The Offeror shall complete one Attachment 0012 for each facility that will handle CHS-6 equipment (Contractor and Major subcontracts only).
L.2.2.3.1.ii.3 In addition to the above approaches, the Offeror shall describe the following, in addition to meeting the requirements set forth in PWS 3.4:
i. The processes that the Offeror would use to effectively derive the best unit cost for each item; and
ii. The maximum time period between DOs of the same items that will allow the Government to receive a discount; and
iii. Define the process the contractor will use to apply the negotiated warranty fee for the same part number being ordered multiple times
NOTE: If the approach to the processes differs between L.2.2.3.1.ii.2.i, L.2.2.3.1.ii.2.ii, L.2.2.3.1.ii.2.iii & L.2.2.3.1.ii.2.iv, then the Offeror may provide an explanation for each. However if the processes are the same, the Offeror shall annotate that in their proposal and provide the singular approach.
L.2.2.3.1.iii Processes Element 3 -- Task Order (Other than Design & Engineering Services):
L.2.2.3.1.iii.1 The Offeror shall describe its approach to the TO process (other than Design & Engineering Services) in detail. The approach shall meet the requirements set forth in PWS 3.6, except for Design and Engineering Services (PWS paragraph 3.6(a)).
L.2.2.3.1.iii.2 The Offeror shall provide a detailed approach for how the Offeror proposes to do the following tasks In Accordance With (IAW) PWS 3.8.2.8:
i. Provide technical assistance for CHS equipment to support field exercises under the CHS Extended warranty for a CONUS location. The Offeror shall assume that the Government would provide the contractor with a list of CHS equipment that would be used at the field exercise, as well as the starting and end dates of the exercise; and
ii. Provide Contractor support to CHS hardware during military contingency operations, both CONUS and OCONUS. The Offeror shall assume that the Government would provide the contractor with a list of CHS equipment that would be used at the military contingency operations; and
iii. Develop Technical Manuals (TMs), Electronic Technical Manuals (ETM), and Interactive Electronic Technical Manuals (IETM) for a V1 NetApp FAS2750 Storage CHS item on contract.
L.2.2.3.1.iv Processes Element 4 -- Design and Engineering Services:
L.2.2.3.1.iv.1 The Offeror shall describe its approach to meet the Design and Engineering Services requirements for an Operational Transit Case (OTC) in detail. The approach shall meet the requirements set forth in PWS paragraphs 3.6(a), 3.8.2.5, 3.10, 3.11 and 3.12.
L.2.2.3.1.iv.2 The proposal shall include a detailed outlined proposal of:
i. The Design approach for the OTC (i.e. Computer Aid Design prototyping and simulation, drawings….); and
ii. How the Offeror will maintain the ability to continuously provide design and engineering services for the OTC for the life of the contract; and
iii. How the Offer will provide a Technical Data Package (TDP) for the OTC to the Government at the conclusion of the design and engineering phase IAW PWS paragraph 3.11; and
iv. The design and engineering process for an OTC IAW PWS paragraph 3.6(a) and the survivability criteria that is defined in Attachment 0002 (PWS Appendix A [Survivability, Reliability, Verification])
L.2.2.3.2 Technical Sub-Factor 2 – Logistics/Warranty Program
L.2.2.3.2.i Logistics/Warranty Program Element 1 -- Warranty and Repair Support:
L.2.2.3.2.i.1 The Offeror shall describe its approach to Warranty and Repair Support in detail. The approach shall meet the requirements set forth in PWS 3.18. The Offeror shall provide a detailed approach to:
i. The repair process for any warrantied item covered by an Extended warranty (IAW PWS 3.18.1), including support for items CONUS and OCONUS. The repair process includes the time from when the contractor receives the hardware to the time the hardware is shipped to the customer; and
ii. How the Offeror will meet the requirements in PWS 3.18.4, Out-of-Warranty and Other-Than-Fair-Wear-and-Tear (OTFWT). The equipment evaluation process includes the time period from the date on which the evaluation request is sent to the Offeror, to the date on which the evaluation quote is returned to the customer. The Offeror shall describe how it will determine which items are OTFWT and which items are warranty items, and shall describe its process for approval or declination of CHS warranty items.
L.2.2.3.3 Technical Sub-Factor 3 – Configuration Management (CM), Quality Assurance (QA) and Supply Chain Risk Management (SCRM)
L.2.2.3.3.i CM, QA, and SCRM Element 1 -- Configuration Management:
L.2.2.3.3.i.1 The Offeror shall describe its approach to CM in detail. The approach shall meet the requirements set forth in PWS 3.14, 3.15, 3.16, 3.17 and CDRL A004 (Configuration Management Plan DI-SESS-80858D).
L.2.2.3.3.i.2 The proposal shall include a detailed Configuration Management Plan (CMP), IAW CDRL A004, which outlines the approach to the implementation and application of CM for multiple items simultaneously. The CMP shall address CM of multiple hardware and Operating Systems versions, firmware, and Basic Input Output Systems (BIOS) configurations for unique items and integrated systems to maintain exact configurations for repeatable orders.
L.2.2.3.3.ii CM, QA, and SCRM Element 2 -- Quality Assurance:
L.2.2.3.3.ii.1 The Offeror shall describe its approach to QA in detail. The Quality Management System shall meet the requirements of PWS 4.9 (including all sub-paragraphs) and CDRL A006 (Quality Assurance Program Plan, DI-QCIC-81794A).
L.2.2.3.3.ii.1 The proposal shall include the following information:
i. A detailed Quality Assurance process to monitor Sub-contractors for hardware quality assurance through supply chain management and structured engineering processes.
ii. A detailed approach for how the Offeror proposes to manage multiple hardware and Operating Systems versions, firmware and Basic Input Output System (BIOS) configurations for unique items.
L.2.2.3.3.iii CM, QA, and SCRM Element 3 -- Supply Chain Risk Management:
L.2.2.3.3.iii.1 The Offeror shall describe its SCRM Plan in detail. The SCRM Plan shall meet the requirements set forth in PWS 1.10 and CDRL A008 (Supply Chain Risk Management Plan DI-MGMT-82256).
L.2.2.3.4 Technical Sub-Factor 4 – Program and Data Management
L.2.2.3.4.i Program and Data Management Element 1 -- Program Management:
L.2.2.3.4.i.1 The Offeror shall describe its approach to Program Management and describe its overall Program Management strategy in detail. The Program Management strategy shall meet the requirements set forth in PWS 4.1, 4.2, 4.5, and 4.6.
L.2.2.3.4.i.2 The proposal shall include the following information:
i. The overall management strategy to (1) lower cost over the life of the contract; (2) meet or exceed schedule; and (3) meet or exceed performance of the CHS-6 contract. The strategy shall include the Offeror’s approach to interacting with the Government.
ii. A detailed outline of the planned execution of the first year of the contract, IAW PWS 4.2 as outlined in CDRL A005 (Phase-in Transition Plan).
L.2.2.3.4.ii Program and Data Management Element 2 -- IDE & Integrated, web-based system:
L.2.2.3.4.ii.1 The Offeror shall describe its approach to the Integrated Data Environment (IDE) and the integrated, web-based system in detail. The IDE and integrated, web-based system shall meet all of the requirements in PWS 4.7 through 4.7.4 and Attachment 0003, Appendix B (Data Item Tables).
L.2.2.3.4.ii.2 Additionally, the proposal shall describe how the IDE and integrated, web-based system provide the user with the capability to track each TI/DO/BPO/TO from the point in time that the Prime receives a TI/DO/BPO/TO request from the Government, to the point in time when the TI/DO/BPO/TO is awarded.
L2.3 VOLUME III – COST/PRICE
L.2.3.1 COST/PRICE EVALUATION SPREADSHEET
In order to facilitate the Government’s Cost/Price evaluation, the Offeror shall use and complete the Solicitation Attachment 0008 – Pricing Spreadsheet and Instructions.xlsx MS Excel Document in accordance with the Instructions Tab of the spreadsheet. The Offeror shall use the spreadsheet provided as Attachment 0008, rather than creating its own spreadsheet or document. All prices shall be in U.S. dollars. Proposals received in other than U.S. dollars may be rejected.
L.2.3.1.1 Pricing Period The Offeror shall propose rates for the time period starting in October 2023 for the purposes of this evaluation.
L.2.3.2 FIRM FIXED-PRICE INSTRUCTIONS
L.2.3.2.1 The Offeror shall use RFP Attachment 0008 – Pricing Spreadsheet and Instructions.xlsx to propose prices/percentages (as applicable) of the Fixed Price items IAW the “Instructions” Tab of Solicitation Attachment 0008. The Firm Fixed Price Items are on the “Proposed Material Prices,” “Proposed Bonded Storage Prices,” “Proposed Percentages,” and “Proposed Eval for Repair Prices” tabs.
L.2.3.2.2 The proposed material prices for the 14 individual hardware items on the “Proposed Material Prices” tab, shall be priced IAW with the technical specifications provided in Solicitation Attachment 0009 on the “Categories Definitions- CHS” Tab. These items along with their associated pricing and rates will become the base hardware items for the CHS-6 contract. The Offeror shall provide copies of vendor quotes for the initial 14 items with its proposal, so that the Government can verify the validity of the proposal. The quotes shall be valid for 365 days from the date of submission.
L.2.3.2.3 IAW FAR 52.211-6, Offerors may elect to propose an “or Equal item(s)” from the items listed in the “Proposed Material Prices” tab in Attachment 0008. If an Offeror is proposing an "or Equal" item(s); they shall overwrite the new nomenclature and the new OEM P/N in the designated cell in column B and they shall color those cells yellow to indicate an "or Equal" item. Offerors shall adhere to the requirements set forth in FAR 52.211-6.
L.2.3.3 COST-PLUS-FIXED-FEE INSTRUCTIONS
L.2.3.3.1 The Offeror shall propose the direct labor costs, indirect costs and fixed fee on the “Proposed CPFF” Tab of the Solicitation Attachment 0008 – Pricing Spreadsheet and Instructions.xlsx IAW the “Instructions” Tab of the spreadsheet. Within the spreadsheet, the Offeror shall insert all formulas to build up the proposed cost in accordance with its approved cost accounting standards disclosure statement. The Offeror shall insert or remove rows between Lines 11 “Indirect Costs” and 20 “General and Administrative” of the “Proposed CPFF” Tab as necessary to align with its cost accounting standards. The Offeror shall ensure that all subtotals and totals are properly calculated within Attachment 0008 to reflect the proposed cost. Inconsistent totals and subtotals within Attachment 0008 may make the Offeror ineligible for award.
L.2.3.3.2 The Offeror shall submit a “Cost Narrative” which details each cost element build up and provides support for the proposed costs. The cost narrative shall be submitted in Adobe PDF or MS Word format. When a date is used in the document, the date format shall be MMDDYY. There is no page limit.
L.2.3.3.3 The Offeror may include attachments to the Cost Narrative as support, if the attachments are clearly labeled and identified within the cost narrative. All information in any attachment provided as support shall match the cost narrative and “Proposed CPFF” tab of Solicitation Attachment 0008. Inconsistencies between the Cost Narrative, Attachment 0008 and supporting attachments may make the Offeror ineligible for award.
L.2.3.3.4 The Offeror is advised that the proposed direct labor and indirect expense rates will NOT be incorporated in the contract as ceiling rates and that they are proposed for evaluation purposes only. However, the proposed Fixed Fee percentage WILL be incorporated as the MAXIMUM Fixed Fee percentage for CPFF Task Orders under the awarded IDIQ for all ten years.
L.2.3.3.5 Labor Categories and Labor Hours:
The total level of effort proposed shall exactly match the following direct labor categories and labor hours, as disclosed in Attachment 0008 – Pricing Spreadsheet and Instructions.
| LABOR CATEGORY | LABOR HOURS | ||
| Program Manager | 6 | ||
| Purchasing Agent | 6 | ||
| Electronics Mechanic | 12 | ||
| Electronics Engineer | 5 | ||
| Quality Assurance Analyst | 3 | ||
| Logistics Coordinator | 8 |
L.2.3.3.5.i Labor Descriptions and Requirements:
L.2.3.3.5.i.1 Labor Category: Program Manager
i. Description: Manages repair program to ensure that implementation and prescribed activities are carried out in accordance with specified objectives. Plans and develops methods and procedures for implementing repair program, directs and coordinates program activities, and exercises control over personnel responsible for specific functions or phases of program.
ii. Requirements: Bachelor’s degree, with minimum of 3 years of relevant experience.
L.2.3.3.5.i.2 Labor Category: Purchasing Agent
i. Description: Procures materials or other goods and/or coordinates activities involved with purchasing products and services, such as raw materials, equipment, tools, parts, supplies, and advertising, for establishment. Receives and reviews requisitions requesting goods or services. Selects products for purchase by testing, observing, or examining items. Expedites orders and requests as needed.
ii. Requirements: High School Diploma or equivalent, with minimum of 3 years of relevant experience.
L.2.3.3.5.i.3 Labor Category: Electronics Mechanic
i. Description: Repairs electronic equipment, such as computers, industrial controls, audio and video systems, radar systems, telemetering and missile control systems, transmitters, antennas, and servomechanisms, following blueprints and manufacturers' specifications, and using hand tools and test instruments.
ii. Requirements: High School Diploma or equivalent, with minimum of 3 years of relevant experience.
L.2.3.3.5.i.4 Labor Category: Electronics Engineer
i. Description: Researches, develops, designs, tests, and analyzes electronic components, products, and systems for commercial, industrial, medical, military, and scientific applications, applying principles and techniques of electronic engineering.
ii. Requirements: Bachelor’s Degree, with minimum of 3 years of relevant experience.
L.2.3.3.5.i.5 Labor Category: Quality Assurance Analyst
i. Description: Conducts routine and non-routine tests using variety of testing devices and procedures to maintain product quality. Constructs and alters quality assurance test plans according to product specifications. Assists in the creation and maintenance of testing standards, processes and systems that align with industry standards.
ii. Requirements: Bachelor’s Degree, with minimum of 3 years of relevant experience.
L.2.3.3.5.i.6 Labor Category: Logistics Coordinator
L.2.3.3.5.i.6.i. Description: Coordinates the organization's daily logistical operations, including inventory control, order fulfillment, and distribution. Organizes warehousing for goods. Reviews inventory to ensure that product adjustments are properly applied. Plans and schedules inbound and outbound shipments to internal or external customers based on needs.
L.2.3.3.5.i.6.ii. Requirements: Bachelor’s Degree, with minimum of 3 years of relevant experience.
L.2.3.3.6 The Offeror shall provide whatever information is necessary to help the Government understand why the proposed costs are realistic in its cost narrative. The Offeror's cost proposal(s) shall contain sufficient quantitative and narrative documentation necessary to adequately support and explain the costs proposed. The Offeror shall propose the performance location as Contractor-site and provide the location used in developing the cost proposal within its cost narrative.
L.2.3.3.7 The Offeror shall provide evidence of an Adequate Accounting System as determined by either DCMA or DCAA to support future potential cost-reimbursement task orders.
L.2.3.3.8 Cost Element Support:
L.2.3.3.8.i Direct Labor Rates
L.2.3.3.8.i.1 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 (a, b or c):
a. Forward Pricing Rate Agreements (FPRA) or Forward Pricing Rate Recommendations (FPRR) from DCAA or DCMA or DCAA/DCMA-approved Compensation Rate Tables mapped to the proposed labor categories
b. Payroll records and/or paystubs showing rate of pay and referenced to the labor category in the proposal.
c. Salary survey data to include copies or screen shots of the actual salary survey data, which at a minimum, shall include the following:
1. Source of data;
1. Job title and description;
1. Geographic location; and,
1. Range of salary amounts with reference to applicability of amounts.
NOTE 1: If using salary survey data to support direct labor rates, the Offeror should not propose any direct labor rates below the 50th percentile for any labor. Proposed rates below those percentiles may be found unrealistic.
NOTE 2: If the 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 or other sources to make necessary adjustments.
L.2.3.3.8.i.2 The Offeror shall provide a direct mapping of proposed direct labor categories and other supporting rate information to the corresponding labor categories proposed (See information in L.2.3.3.5).
L.2.3.3.8.i.3 The Offeror shall propose direct labor rates based on a 40 hour work week ONLY.
L.2.3.3.8.ii Indirect Expense Rates
L.2.3.3.8.ii.1 In support of the proposed indirect expense rates, the Offeror and its subcontractor(s) shall provide documentation of the most recent indirect expense rates, to include at least one (1) of the following (a, b, c, d, or e):
1. Most recent FPRA(s) with DCAA or DCMA
1. Most recent FPRR(s) from DCAA or DCMA
1. Most recent Forward Pricing Rate Proposal (FPRP)
1. Approved Provisional Rates Proposal
1. Other statement of current rates
NOTE for paragraphs c, d, and e: If an Offeror supports proposed indirect rates utilizing documentation options c. – e. above, the Offeror shall include forecasted pools and bases for the current year (by expense account). Additionally, the Offeror shall support these rates with three (3) years historical actual pools and bases information (by expense accounts) that validates the calculations. Below is a sample (formats and dates may vary):
L.2.3.3.8.ii.2 The rates reflected in the FPRA, FPRR, FPRP, Approved Provisional Rates Proposal or other statement of current rates shall directly match the proposed rates as detailed in the proposal. If the rate proposed does not match, the Offeror shall provide sufficient quantitative and narrative support for why the government should consider the proposed rate to be realistic. Failure to provide support for why it is realistic may result in the cost being found unrealistic and adjusted upward accordingly.
L.2.3.3.8.iii All documents provided in support of the proposed rates shall be referenced and explained within the DATE_COMPANYNAME_VOL_ III_COST_NARRATIVE.docx (and any proposed attachments). This explanation shall include a mapping for all proposed rates to the applicable supporting documentation and how the proposed rate was developed.
NOTE1: The Contracting Officer has determined this acquisition has a high probability of adequate price competition IAW FAR 15.403-1(c)(1), and therefore is not requiring certified cost or pricing data at this time IAW FAR 15.403-1(b)(1). However, if at any time during this solicitation the Contracting Officer determines that adequate price competition does not exist, then the Offeror may be required to submit certified cost and pricing data to the Contracting Officer. IAW FAR 15.403-5(b)(1), when required by the contracting officer, certified cost and pricing data shall be submitted IAW Table 15-2 of FAR 15.408.
NOTE2: IAW FAR 15.403-1(b)(3), when commercial product or commercial service is being acquired, the Contracting Officer may require date other than certified cost or pricing data as defined in FAR 2.101 to support a determination of a fair and reasonable price or cost realism.
IMPORTANT: Offerors that fail to follow the above instructions and/or fail to provide all of the above submission requirements may not be eligible for award.
L.2.4 VOLUME IV – PAST PERFORMANCE
L.2.4.1 The Offeror (referring in this Volume to the prime offeror and Major subcontractors together) shall submit no more than five (5) recent and relevant Government and/or commercial contracts for the prime Offeror, and no more than one (1) recent and relevant Government and/or commercial contract for each proposed Major subcontractor for the Government to assess the Offeror’s probability of meeting solicitation and PWS requirements based on a demonstrated record of performance. If an Offeror utilizes an IDIQ as one of the five contracts, then they shall not use an associated TO or DO from that IDIQ as a separate contract.
L.2.4.2 Data concerning the prime Offeror shall be provided first, followed by each proposed Major subcontractor, in alphabetical order.
L.2.4.3 The Past Performance volume shall not exceed 50 total pages. The page count includes the past performance information for the Prime Offeror and each proposed major subcontractor. The page count does not include Past Performance Questionnaire Forms, the Cross Reference Matrix, Letters of Commitment, or Written Consent to Release Major Subcontractor past performance information.
L.2.4.4 Past Performance Definitions
L.2.4.4.1 Major subcontractor: Major subcontractor is defined as a subcontractor who is expected to perform 7% or more of the proposed contract price.
L.2.4.4.2 Recency: For purposes of this RFP, contracts (prime contracts, TO/DO, and/or subcontracts) performed, in whole or in part, during the past five (5) years from the date of issuance of this RFP will be considered recent. The contract need not be completed to be considered recent.
L.2.4.4.3 Relevancy: For this acquisition, factors in addition to recency that will be considered to determine relevancy include:
L.2.4.4.3.i Complexity of support; and
L.2.4.4.3.ii Dollar value; and
L.2.4.4.3.iii Similarity of support
L.2.4.5 Organization: The past performance volume shall be organized into the following sections:
L.2.4.5.1 Section 1 - Contract Descriptions. This section shall include the following information in the following format.
L.2.4.5.1.i Contractor/Major Subcontractor place of performance, CAGE Code and DUNS Number. If the work was performed as a Major subcontractor under the provided contract, then the Offeror shall 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 and fax numbers).
L.2.4.5.1.ii Government/commercial contracting activity, and current address, Procuring Contracting Officers name, e-mail address, telephone and fax numbers.
L.2.4.5.1.iii Government/commercial technical representative/COR and current email address, telephone and fax numbers.
L.2.4.5.1.iv Government/commercial contract administration activity and the Administrative Contracting Officers name, and current e-mail address, telephone and fax number.
L.2.4.5.1.v Government/commercial contract administration activity Pre-Award Monitor's name, and current e-mail address, telephone and fax numbers.
L.2.4.5.1.vi Contract Number and, in the case of Task Orders or Delivery Orders under Indefinite Delivery type contracts, and GSA contracts include Order Numbers.
L.2.4.5.1.vi Contract Type (specific type such as Fixed-Price (FP), Cost Reimbursement (CR), Fixed Price Incentive (FPI), etc.). In the case of Indefinite Delivery contracts, indicate specific type (Requirements, Indefinite Delivery, and Indefinite Quantity) and secondary contract type (FP, CR, FPI, etc.).
L.2.4.5.1.viii Awarded price/cost.
L.2.4.5.1.ix Final or projected final price/cost.
L.2.4.5.1.x Original delivery schedule, including dates of start and completion or work.
L.2.4.5.1.xi Final or projected final, delivery schedule, including dates of start and completion of work.
L.2.4.5.2 Section 2 - Performance. The Offeror shall provide a specific narrative explanation of each contract listed in Section 1 - Contract Descriptions, to describe the objectives achieved in that contract and detail how the effort in that contract is relevant to the requirements of this Solicitation.
L.2.4.5.2.i For any contracts that did not/do not meet original schedule or technical performance requirements, the Offeror shall provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The Offeror shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. The Offeror shall provide the cause and corrective action for each Request for Deviation and Request for Waiver that the Offeror received on each contract listed. The Offeror shall provide a 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. The Offeror shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.
L.2.4.5.3 Section 3 - Subcontracts. The Offeror shall provide an outline of how the current RFP effort will be assigned for performance within the Offeror’s corporate entity and among the proposed major 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, and type of work to be performed by citing the applicable Government SOW subparagraph number.
L.2.4.5.4 Section 4 - New Corporate Entities. New corporate entities proposing as the Prime Offeror or as a major subcontractor 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. Letters of Commitment shall be included in the proposal for these employees in order to be considered.
L.2.4.6 Past Performance Questionnaire. For all contracts identified in Section 1 – Contract Descriptions, a Past Performance Questionnaire must be completed and submitted (Attachment 0011). The Offeror shall complete Part I of the Past Performance Questionnaire and email the Questionnaire to both the Government/commercial contracting activity and technical representative or commercial entity responsible for the contract no later than the proposal due date and time. The Offeror shall provide a PDF copy of the emailed Questionnaire(s). The Offeror shall also provide a POC List identifying who was sent a Questionnaire. The POC List shall be submitted in Word for Windows Table Format and include the following fields: Solicitation Number; Company Name; Contract Number; Government Agency; POC Last Name, First Name; POC Title; POC Telephone Number; POC Email Address; and Date of Email to POC.
L.2.4.7 The Government may, but is not required to, obtain past performance information from any other sources available to the Government, including but not limited to, the Contractor Performance Assessment Reporting System (CPARS), the Past Performance Information Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information System (FAPIIS), Electronic Subcontract Reporting System (eSRS), or other databases; the Defense Contract Management Agency; and interviews with Program Managers, Contracting Officers, and Fee Determining Officials.
L.2.5 VOLUME V – SMALL BUSINESS PARTICIPATION
L.2.5.1 All Offerors (both other than small businesses (OTSB) and small businesses) shall submit a Small Business Participation Commitment Document (SBPCD) as outlined in Attachment 0007 – 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 V – Small Business Participation. The SBPCD will be incorporated into the base contract vehicle as binding commitments and are considered enforceable contractual requirements.
L.2.5.2 NOTE: The SBPCD 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.
L.2.5.3 The Offeror shall provide the Prime Offeror’s Size as outlined in the SBPCD.
L.2.5.4 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:
L.2.5.4.1 Identify the type, variety, and complexity of work to be performed by small business firms in accordance with PWS Section 3 and Section 4.
L.2.5.4.2 Describe and demonstrate a substantive commitment to small business firms.
L.2.5.5 The Offeror shall provide the participation percentage of small businesses in terms of the Total Contract Ceiling Value, as outlined in the SBPCD.
L.2.5.5.1 The Total Contract Ceiling Value for this requirement is the total $7.9B USD. For this requirement the Governments market research shows that a minimum of 15% of the work can be performed by small business concerns; therefore, the minimum quantitative requirement has been established at 15%.
L.2.5.5.2 The Offeror shall provide explanation and documentation to support small business participation percentages. Binding commitments shall become enforceable, contractual requirements.
L.2.5.5.3 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.
L.2.5.6 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 Volume IV – Past Performance.
L.2.5.7 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.
L.2.5.8 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.
L.2.5.9 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 annual reporting of the requirements set forth in the SBPCD paragraphs 1-3 (contractor format is acceptable) in accordance with CDRL B007 – Small Business Utilization Report (DI-MGMT-82041B).
L.2.5.10 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.
L.2.5.11 A small business joint venture offeror must submit, with its offer, the representation required in paragraph (c) of FAR solicitation provision 52.212-3, Offeror Representations and Certifications-Commercial Products and Commercial Services, and paragraph (c) of FAR solicitation provision 52.219-1, Small Business Program Representations, in accordance with 52.204-8(d) and 52.212-3(b) for the following categories:
(A) Small business;
(B) Service-disabled veteran-owned small business;
(C) Women-owned small business (WOSB) under the WOSB Program;
(D) Economically disadvantaged women-owned small business under the WOSB Program; or (E) Historically underutilized business zone small business.”
L.2.6 VOLUME VI – SOLICITATION, OFFER, AND AWARD DOCUMENTS, AND CERTIFICATIONS AND REPRESENTATIONS
L.2.6.1 Certifications and Representations: Each offeror shall complete (fill-in and signatures) SF 1449 and an authorized official of the firm shall sign all Representations, Certifications and Other Statements of Including Exceptions to Terms and Conditions, if any. An Adobe Acrobat PDF file shall be created to capture the signature page of the SF 1449 for submission. The remainder of Volume VI shall be submitted in Word.
L.2.6.2 The Offeror shall disclose any potential Organizational Conflict of Interest (OCI) or unfair competitive advantage situations with itself, subcontractors, partners or any other Offeror as it applies to this RFP for the CHS-6 base contract awards to the Contracting Officer as soon as the OCI is identified; including if identified prior to proposal submission, or the Offeror shall submit an affirmation statement in its proposal that they are not aware of any OCI or unfair competitive advantage in accordance with FAR 9.5. The disclosure shall include the facts and an analysis of the actual or perceived conflict or unfair competitive advantage and recommend an approach to neutralize, mitigate, or avoid the potential conflict or unfair competitive advantage. The Contracting Officer will determine if resolution is necessary and promptly respond to resolve any potential conflicts or unfair competitive advantages, which may include notifying an Offeror of their exclusion from the competition. If an Offeror fails to submit either a disclosure of potential OCI or unfair competitive advantage situations or an affirmative statement that the Offeror is not aware of any OCI or unfair competitive advantage, the Offeror may not be considered for award. This information shall be submitted with Volume VI and there is no page limit in this volume.
L.2.6.3 All proposals will be subject to evaluation by a team of Government personnel. Booz Allen Hamilton (BAH) provided assistance in the development of the CHS-6 documentation. In its support to CHS, BAH has subcontracted with companies Sev1Tech, LLC, JANUS Research Group, LLC, and NetWerx. Any Offeror teaming/partnering with these companies shall submit an OCI mitigation plan that explains the facts of the partnership in detail, and include an analysis of the actual or perceived conflict and recommend an approach to neutralize, mitigate, or avoid the potential conflict.
L.3 DISCUSSIONS AND CLARIFICATIONS
L.3.1 This procurement is subject to DFARS 215.306 and therefore, the intent of the Government is to favor discussions. However, the Government reserves the right to exercise its discretion not to enter into discussions in accordance with DFARS 215.306 if it is determined that discussions are inappropriate. Therefore, the offeror’s initial proposal should contain the offeror’s best terms from a cost or price and technical standpoint.
L.3.2 If the Contracting Officer conducts discussions, then such discussions will be held with offerors whose proposals have been determined to be within the competitive range, in accordance with FAR 15.306(c). If the Contracting Officer determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the Contracting Officer may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals. Therefore, the offeror’s initial proposal should contain the offeror’s best terms from a cost or price and technical standpoint.
L.3.3 Offerors excluded from the competitive range or otherwise eliminated from the competition before award will receive prompt written notice of this decision in accordance with FAR 15.503.
L.3.4 Clarifications are limited exchanges between the…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .