USARCENT_DRAFT_Sections_L-M_7_NOV_19.pdf

W900KK19R0048

Section L - Instructions, Conditions and Notices to Bidders

CLAUSES INCORPORATED BY REFERENCE

52.204-7 System for Award Management OCT 2018 52.214-34 Submission Of Offers In The English Language APR 1991 52.214-35 Submission Of Offers In U.S. Currency APR 1991 52.232-31 Invitation to Propose Financing Terms MAY 2014 52.237-1 Site Visit APR 1984 52.237-10 Identification of Uncompensated Overtime MAR 2015 252.215-7013 Supplies and Services Provided by Nontraditional Defense

Contractors.

JAN 2018

PROPOSAL SUBMISSION

L.1.0. Proposal Submission

L.1.1 Introduction. The ARCENT TSS effort is being competed as full and open competition under NAICS code 541330, Engineering Services, with a size standard of $41.5M in average annual receipts. The ARCENT TSS effort will be a C-type contract and provide annual mission-support services consisting of a 3-month phase-in period, 9-month base period of performance, and two 12-month option periods.

Volume I – Factor 1 proposals are due no later than the date and time annotated on the SF33 coversheet (anticipated to be 10 calendar days after issue). Early delivery is authorized.

The required method of ARCENT TSS proposal delivery is via the DoD Secure Access File Exchange (SAFE) located at https://safe.apps.mil/. Offerors shall ensure the recipients receiving the proposal submitted via DoD SAFE are the ARCENT TSS Primary Point of Contact (POC), Alternate POC, and the Procuring Contracting Officer, identified in Section L.2.8. After the proposal has been submitted via DoD SAFE, the Offerors shall send an email notification to the Primary POC. If there are any technical difficulties with DoD SAFE, the Offeror shall coordinate an alternate method of ARCENT TSS proposal submittal with the Primary POC, no less than 24 hours prior to the due date and time. It is the Offeror’s responsibility to ensure that the entire proposal is submitted prior to the proposal due date and time. All proposals submitted must be in compliance with the full solicitation.

L.1.2 Phased Acquisition Approach

The Government will evaluate Offerors’ proposals in two phases to progressively reduce the number being considered for contract award. The purpose of this procedure is to reduce the time and cost of source selection, both for the Government and for the competing offerors.

Phase I: Offerors shall prepare and submit ONLY Volume I – Factor 1 – Technical Experience proposal in accordance with the criteria established below. The Government will determine the acceptability of each proposal in accordance with the acceptability criteria in Section L and M of this RFP. The Government will eliminate from further consideration any Offerors that submitted unacceptable proposals.

The decision to eliminate any Offeror through this procedure will not constitute the establishment of a competitive range, as described in FAR 15.306[c], and it will not obligate the Government to conduct discussions or to solicit or entertain proposal revisions. However, the Government reserves the right to establish a competitive range and conduct discussions if the PCO decides that it is in the best interest of the Government to do so.

Phase II: Offerors with an “Acceptable” Phase I proposal will be notified by the PCO and requested to submit Volume II – Factor 2 – Program Management, Volume III – Factor 3 – Cost/Price, and Volume IV – Administrative Information of the proposal in accordance with the criteria established below and within the notification.

L.1.3 Proposal Validity: The Government requires that the proposal, in its entirety, be valid for at least two hundred and seventy (270) calendar days from the final, phase II proposal due date which will be annotated in the PCO notification referenced above. Offerors are cautioned that for their proposal to be eligible for award, the proposal shall be in compliance with the terms and conditions set forth in the solicitation. The Offeror shall insert the validity date in Block 12 of the SF 33.

L.1.4 The Offeror’s proposal shall consist of four (4) volumes:

PHASE I

Volume I – Factor 1 - Technical Experience;

PHASE II

Volume II – Factor 2 – Program Management:

Subfactor 2.1 Program Management Approach Subfactor 2.2 Concept of Support Subfactor 2.3 Phase-in / Phase-out Approach Volume III – Factor 3 Cost / Price Volume IV – Administrative Information.

L.1.5 All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the entire requirement and associated risks, and is able, willing, and competent to devote resources necessary to meet the requirement, and has a valid and practical solution for the requirement. Statements that the prospective Offeror understands, can, or will comply with the requirements, and statements paraphrasing the requirements or parts thereof without supporting information/narrative are considered inadequate and unsatisfactory. Mere reiteration of the requirement or standard reference material is discouraged and is considered inadequate and unsatisfactory. The Offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. In presenting material in proposals, Offerors are advised that quality of information is more important than quantity. Offerors are encouraged to use quantitative terms wherever possible and avoid the use of qualitative and subjective terms to the maximum extent practicable. Offerors are cautioned that while the Government will not evaluate every PWS requirement for the purposes of the source selection evaluation, the awardee/Contractor will be required to comply with all PWS requirements during performance of the contract. The offeror’s proposal shall describe its approach to implementing PWS requirements that are being evaluated. The proposal shall reference the related paragraphs of the PWS (e.g. 3.1.2) and Section L, and provide the detail necessary to substantiate the proposed approach and methodology for performance. The proposal should identify any unique or innovative approaches which ensure successful performance. The Government will determine that an Offeror's proposal is non-compliant, and therefore ineligible for award, if the proposal indicates that: it cannot or will not meet all the requirements; provides an approach that clearly does not meet any of the requirements; or, includes data which prompts the Government to question the Offeror's compliance with any of the requirements.

The Source Selection Authority may reject all proposals received in response to a solicitation, if doing so is in the best interest of the Government. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal. Proprietary information shall be clearly marked. “

L.1.6. The proposed approach should be specific, detailed, and contain sufficient information to clearly and fully demonstrate the offeror’s understanding of the requirements and the inherent risks associated with this procurement.

It is inadequate to simply state that the offeror understands and will comply with the requirements, or to paraphrase the requirements. The proposal shall comprehensively explain how the offeror proposes to comply with the applicable requirements, as well as describe the techniques and procedures the offeror proposes to implement.

L.2. PROPOSAL SUBMISSION REQUIREMENTS

L.2.1 Failure to submit documents in the correct format is grounds for non-compliance determination, at the sole discretion of the PCO.

L.2.2 It is the sole responsibility of the Offeror to ensure that the electronic files submitted are virus free and can be opened and read by the Government. Proposal submissions shall not be locked, encrypted, or otherwise contain barriers to opening. All files shall be clearly identified with a filename appropriate to the content (e.g., Volume- I_Technical_Experience_Attachment_1). Use separate files to permit rapid location of all portions, including exhibits, annexes, and attachments, if any. Compressed files are not allowed. When submitting proposals, Offerors shall follow these instructions.

L.2.3 File Packaging. All of the proposal files shall be separate documents in their native format; i.e. xls, doc, ppt,.

An Adobe Portable Document Format (PDF) version of all electronic documents shall also be included as a control copy. All price breakdown information to aid in the cost/price evaluation shall be submitted in Microsoft Office Excel Read/Write format and viewable in Microsoft Excel 2013. Please note – Self extracting .exe files are not acceptable. PDF documents shall use Adobe Acrobat 9.0 or later. Do NOT submit main documents in the PDF “image.” Teaming Agreements or Letters of Commitment may be in the image format.

L.2.4 All proposal files shall be verified to be free of any virus or malware.

L.2.5 All submitted files (MS Office and PDF) shall be created with textual search and copy functions enabled.

Non-searchable signature pages are acceptable, but other submitted materials that are not searchable may not be evaluated, and the Offeror may be determined non-compliant, at the sole discretion of the PCO.

L.2.6 The following volumes of material shall be submitted:

VOLUME TITLE

PAGE LIMIT

I – Factor 1 - Technical Experience Unlimited II – Factor 2 –Program Management Subfactor 2.1 – Program Management Approach Subfactor 2.2 – Concept of Support Subfactor 2.3 – Phase-in / Phase-out Approach

III – Factor 3 – Cost / Price Unlimited IV – Administrative / General Information Unlimited

NOTE: Pages that exceed the required page limitations will not be evaluated. Additional pages over the maximum allowed will be removed or not read and will not be evaluated by the Government.

L.2.7 Acronym lists, cover pages, title pages, table of contents, cross reference matrices, dividers, index tabs lists of tables or figures, will not be counted as part of the page count, so long as they are inserted solely for the purpose of reading ease and locating sections of the proposal. Pages marked: "This page is intentionally left blank" will not be counted nor evaluated.

A formal Technical Experience Volume Overview is not required and should be used only if the contractor needs to explain the supporting data submitted in responses to Solicitation Attachment, Technical Experience Project Worksheet, or to summarize the Technical Experience Volume. The Contractor can provide as much data and/or pages as required to validate each Technical Experience Project.

L.2.8 ARCENT TSS RFP Points of Contact:

Primary: Procuring Contracting Officer

Daniel Steinhauer Phil Davis Contract Specialist Branch Chief/Contracting Officer U.S. Contracting Command – Orlando U.S. ARMY Contracting Command - Orlando 12211 Science Drive, Orlando, FL 32826-3224 12211 Science Drive, Orlando, FL 32826-3224 Ofc: (407) 208-5820 Ofc: (407) 384-5335 daniel.j.steinhauer.civ@mail.mil phillip.b.davis16.civ@mail.mil

Alternate:

Dan Veenstra Contract Specialist U.S. Contracting Command – Orlando 12211 Science Drive, Orlando, FL 32826-3224 Ofc: (407) 208-3308 daniel.l.veenstra.civ@mail.mil

L.2.9 Beneficial features offered beyond the requirements of this solicitation will be incorporated into the awardee’s contract. The Offeror will be expected to perform based on the entire proposed approach, including any over-and-above features and/or merits contained within its proposal.

L.2.10 If there are any questions resulting from this solicitation, each respective Offeror shall coordinate its questions through one company representative. The Government will provide responses to these questions via email to all Offerors. All questions regarding the solicitation shall be submitted in writing, via email, to the ARCENT TSS RFP Primary and Alternate POCs identified within Section L, via email, NLT 1400 hours ET, 7 calendar days after the RFP issue date annotated on the SF 33 coversheet. Questions shall be submitted using the RFP attachment entitled “Question/Comment Form.”

L.2.12 Information previously submitted to the Government should be assumed unavailable during this proposal evaluation and source selection process. Proposal data shall not be incorporated into the proposal by referring to another proposal volume or other source. Proposals submitted will not be returned. Alternate proposals will not be evaluated or accepted.

L.2.13 In accordance with FAR Subpart 52.215-1, Instructions to Offerors – Competitive Acquisition, the Government intends to evaluate proposals and award a contract without discussions with Offerors (except clarifications as described in FAR 15.306(a)). Therefore, the Offeror’s initial proposal should contain the Offeror’s best terms from a cost or price and technical standpoint. However, the Government reserves the right to conduct discussions if the Contracting Officer later determines them to be in the best interest of the Government. The Contracting Officer will schedule the discussion sessions, and each Offeror within the competitive range will be notified of the time and place. The Contracting Officer will provide additional instructions with the notification.

L.2.14 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. Clarifications are not discussions. Offerors may be given the opportunity to clarify certain aspects of the proposal or resolve minor or clerical errors (see FAR 15.306(a)(1) and (2)). Clarifications shall be documented on, and conducted via transmittal of, Evaluation Notices (EN) to the applicable Offeror.

L.2.15 Any proprietary information submitted separately for major subcontractors shall be furnished in the same format, level of detail, and submission due date as prescribed for the prime Offeror. Subcontractor proposals submitted separately are considered part of the Offeror’s proposal, including the page count. All subcontractor proposals submitted separately must identify the prime contractor and be clearly marked IAW L.2 and L.3. If subcontractor proposals are late or not in accordance with the other submission requirements, the entire proposal may be considered non-compliant.

L.3 PROPOSAL FILES

L.3.1 Format. The submission shall be clearly indexed and logically assembled, including the attached Cross- Reference Matrix within Volume I – Factor 1 and Volume II – Factor 2 proposal. A Table of Contents should be created to delineate the paragraphs and subparagraphs within that volume. As annotated above, each volume’s Cross-Reference Matrix and Table of Contents does not count against that volume’s respective page limitations.

Tab indexing shall be used to identify sections. Standard proposal text format shall be 12 point Arial or Times New Roman font.

All pages of each volume shall be appropriately numbered (X of Y) and shall contain the company name, date and solicitation number in the header and/or footer. Pages shall be numbered sequentially within each volume. All pages shall be marked: “SOURCE SELECTION INFORMATION -- SEE FAR 2.101 AND 3.104” in the footer.

Additional data use restrictions shall be located in the header/footer area of each page where applicable. The signed Standard Form (SF) 33, each SF30 – as applicable – and Section K – Certifications and Representations may be submitted in Adobe.pdf file format. Microsoft Word and PDF files shall use the following page setup parameters:

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

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and can utilize an alternate paper size of 11x17, if necessary. For page-count purposes, each side of an 11x17 page with content will count as two pages.

L.3.2 Cross-Reference Matrix –The intent of the attached Cross-Reference Matrix is to ensure that all requirements for Volume I – Factor I and Volume II and Factor 2 are addressed and easily accessible to evaluators.

The Cross-Reference Matrix must provide a single integrated index for the corresponding proposal Volume/Factor.

L.3.3 Compliancy Screening. The proposal volumes will be evaluated in accordance with the Instruction to Offerors and Evaluation Criteria provided in Section L and M, respectively. Failure of an Offeror to provide all requested proposal information may render the Offeror's proposal non-compliant, and as such, the Offeror's proposal will not be evaluated, at the sole discretion of the PCO. If determined to be non- compliant, the PCO will notify the Offeror as soon as practicable.

L.3.5 All information shall be confined to the appropriate file. The Offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal. The Offerors shall ensure that each proposal volume submitted contains only the information relevant to that specific volume. The Offerors are cautioned that each volume of the proposal is evaluated standalone against the criteria set forth in Section M and the evaluators for one volume may be different than the evaluators of another volume. It is incumbent upon the Offerors to ensure they properly submit their proposals. If the data is not contained in the appropriate volume of the proposal, it will not be evaluated. For example, if Program Management information is submitted under the Price Volume rather than the volume specified, the proposal will be evaluated as if the information was not submitted at all.

L3.6 PWS References. Section L and M PWS references includes corresponding PWS subparaphs.

L.4.0. Volume I – Factor 1 – Technical Experience

L.4.0.1 The Offeror's proposed Technical Experience shall be submitted using Solicitation Attachment entitled.

“Technical Experience Reference Workbook.” Each reference submitted shall clearly delineate how the reference meets the requirements of the ARCENT PWS paragraph during the example’s performance of the following ARCENT TSS Core Experience areas:

a) Experience executing a service contract with range control operations. PWS Reference: 3.2.2; 3.5.1; 3.7.

b) Experience executing a service contract with TADSS instructor services. PWS Reference: 3.2.1; 3.4.1.2.

c) Experience executing a service contract with TADSS operator services. PWS Reference: 3.4.2.

d) Experience executing a service contract with TADSS maintenance services. PWS Reference: 3.3.1; 3.4.13;

3.4.14; 3.4.15; 3.4.23; 3.5.1.17; 3.5.1.22; 3.5.1.26; 3.5.1.30.

e) Experience complying with and implementing Kuwaiti Labor laws - regulations. PWS Reference: 2.2.2;

4.4.

f) Experience executing a contract in the CENTCOM area of responsibility, to include SPOT compliance, with a workforce in excess of 100 Full-Time Equivalent contractor personnel. This may be inclusive of sub-contractor personnel. PWS Reference: 1.3; 2.2.1; 3.1.6.1

g) Each Technical Experience submitted in support of any of the above letters (a) through (f) shall have been gained during a period of at least 12 consecutive months, with six-months of that performance taking place within three years of the RFP release date.

h) Each Technical Experience submitted in support of any of the above letters (a) through (f) shall have an annual value of equal to or greater than $10 million, inclusive of profit/fee, for the completion of definite requirements.

L.4.0.2 The Offeror shall provide up to five Technical Experience references for evaluation. Offerors shall submit Technical Experience References using the attached Technical Experience Reference Workbook. At least one of the up to five Technical Experience references shall provide verifiable experience for Section L4.0.1 paragraphs (a) thorough (f). These requirements may be met separately, in the up to five Technical Experience references submitted. Each Technical Experience reference submitted shall fully comply with Section L4.0.1 paragraphs (g),

(h) and (i).

L.4.0.3 An overarching Indefinite Delivery / Indefinite Quantity (ID/IQ) base contract, Blanket Purchase Agreement (BPA), or Basic Ordering Agreement (BOA) shall not be submitted as an individual Technical Experience reference.

Offerors may submit multiple orders issued from a single ID/IQ contract, BPA, or BOA as one Technical Experience reference or multiple references to show experience in each relevant area. Each Technical Experience reference shall comply with the criteria established within this RFP.

L.4.0.4 The Offeror shall include applicable verification documents required to unambiguously and sufficiently validate the individual Technical Experience references submitted.

L.4.06 Technical Experience references may include references of major subcontractors for this effort. Joint Ventures may include references executed by individual member(s) of the Joint Venture. Technical Experience References shall only include major subcontractors or members of a Joint venture when the major subcontractor or the member of a Joint Venture executed the requirements within the Technical Experience Reference as the Prime contractor. For the Technical Experience Factor, a major subcontractor is considered a subcontractor executing at least 10% of the total proposed value.

L.4.07 Teaming agreements and/or Joint Venture documentation, applicable to this Volume, shall be submitted as an attachment to this Volume. Agreements shall be submitted and bilaterally signed, by authorized representatives from each organization, for all major subcontractors citing their Technical Experience in this Volume.

In addition, Offeror may submit a Factor 1 Technical Experience Overview. There is no benefit to submitting up to five Technical Experiences when a fewer number will suffice.

Additional instructions are contained within the attached Technical Experience Reference workbook.

L.4.1 Volume II -- Factor 2 – Program Management

The Offeror shall prepare and submit a standalone Program Management Volume organized IAW the factor description below.

This volume provides Offerors with an opportunity to demonstrate their approach in meeting the solicitation requirements. While Offerors will not be evaluated on all requirements of the ARCENT TSS PWS, they must comply with, and be able to accomplish, all PWS requirements throughout the contract’s performance.

** NO COST/PRICE INFORMATION SHALL BE INCLUDED WITHIN THIS VOLUME. **

L.4.1.1 Subfactor 2.1 Program Management Approach

The Program Management Approach shall be submitted as a standalone document and contain all of the elements outlined below. An omitted item is grounds for non-compliance and may result in the PCO determining the proposal unacceptable.

L.4.1.1.1 Management Structure. Offeror must provide a realistic approach to creating its management structure for the geographically separated sites in the required area of operation, from general staff oversight by first line supervisors, through its local organizational structure to the company headquarters management.

PWS Reference: 2.5.11.1; 2.6; 3.1.2

L.4.1.1.2 Recruitment and Retention Plan:

The Offeror shall describe the methodology to be employed by the Offeror to recruit, retain, and develop personnel with the requisite knowledge, skills, education, experience and clearances to ensure successful accomplishment of ARCENT TSS PWS. At a minimum, for proposed EXPAT and Foreign National positions, the plan shall address:

how lessons learned will be incorporated to improve recruitment and retention practices; current recruitment and hiring practices; process and procedures for addressing performance issues; process for ensuring individuals are trained properly to perform PWS requirements; process for ensuring continuity of quality services during personnel absences due to leave, terminations, and resignations such that impact to the Government is minimal; and any other processes or business practices to ensure a stable workforce over the life of the contract.

The Offeror shall explain its established business practices, processes, procedures, and methodologies that will be employed to ensure uninterrupted support, to include an explanation of its internal personnel pool, and other sources for personnel, and how those resources will be employed to meet to accomplish the required performance-based tasks at the PWS’ required locations.

PWS Reference: 2.6

L.4.1.1.3 Contractor Work Breakdown Structure (CWBS). Offeror shall provide a CWBS with all proposed labor categories executing performance-based requirements within the PWS. Each CWBS shall identify, for the proposed labor categories, clearly defined lines of responsibility, clearly defined levels of decision authority, location of personnel, and the communications/interfaces (e.g., Contractor/Subcontractor to Government, Prime to Subcontractor, Prime to Site/Site Manager, and Subcontractor to Site/Site Manager).

CWBS shall identify:

a) Labor categories, broken out by PWS section

b) Position Descriptions for each labor category

c) Qualifications (experience, specialized education, and certification(s)) for each labor category

d) Number of personnel for each labor category, broken out by PWS section

e) Number of hours proposed for each category, broken out by PWS section

f) Identify if the position is CONUS or OCONUS

g) For CONUS positions, identify if position is Exempt or Non Exempt from the Service Contract Act

h) Identify if the position will be filled by Expat (US Citizen) or Foreign National (FN)

CWBS rationale and assumptions: The Offeror must provide its overarching methodology for determining its proposed Qualifications by Labor Category and assumptions supporting staffing decisions or explanations needed to clarify staffing decisions made in order to ensure proper execution of the effort. The numbers of hours, personnel and labor categories must match the numbers in the Offeror’s Cost/Price Workbook. The Offeror shall provide rationale and calculations that clearly identify the methodology used to arrive at the labor categories, number of personnel, and/or proposed hours for each labor category listed in the PWS.

PWS Reference: 2.5.1

No cost/price data shall be included in this volume.

L.4.1.1.4 Management Methodology. As part of its Program Management Approach, the Offeror shall:

a) Provide an Organization Chart that clearly outlines, by labor category, reporting structures and lines of authority;

b) Describe their methodology and approach to managing multiple subcontractors, joint venture, and/ or teaming partners in order to execute multiple requirements;

c) Describe their methodology and approach to managing its workforce alongside the workforces of other contractors in shared spaces;

d) Describe their methodology and approach to providing on-site management with authority, flexibility and the efficiency to quickly and effectively resolve all performance-related issues; and

e) Identify risks and corresponding risk-mitigation strategies that will be employed during execution.

PWS Reference: 2.3; 2.4; 3.1

L.4.1.1.5 Quality Control Plan. ARCENT TSS Quality Control Plan (i.e., onsite quality control procedures) capable of providing continuous improvement and problem resolution in coordination with local management and supported Government unit and/or higher headquarters.

PWS Reference: 2.12

L.4.1.1.6 Joint Venture/Teaming or Major Subcontracting Arrangements. Each Offeror shall provide, if applicable, a summary describing the joint venture or subcontracting arrangement established for this solicitation and a bilaterally signed document (format as established by Offeror) specifying an agreement (e.g., Teaming Agreements) among the parties. Offeror shall identify for each proposed team member/subcontractor: a) what PWS section each joint venture team member/subcontractor will support; b) the team member/subcontractor’s name; c) the actual services to be provided; d) the percentage of work it will perform. The summary and Teaming Agreements shall be attached to this volume and not included in the page count.

PWS Reference: 2.3; 2.4; 3.1.2; 3.1.12

L.4.1.2 Subfactor 2.2 Concept of Support

L.4.1.2.1 TADSS Maintenance. The Offeror shall describe in detail its maintenance management approach to track/report system level work orders, to identify spares/stock levels to support demand, to identify and manage tracking/ordering/ long lead items, and format of work order data, to include consumption of material, hours and re-order rate.

The Offeror shall describe its approach to ensuring work order accuracy, completeness, and timeliness. The Offeror shall describe how its approach minimizes the possibility for errors when populating work orders, and detects or remedies errors through the life-cycle of the work order until it is closed out. The Offeror shall describe its sampling and analysis methods for ensuring work order accuracy, completeness, and timeliness during contract performance.

The Offeror shall describe its approach to ensure accurate, timely and complete data entry in remote environments.

The Offeror shall address its approach for capturing different types of maintenance and maintenance-related items, such as corrective maintenance, preventative maintenance, operational activities, and depot/vendor activities. The Offeror shall describe the type(s) of work orders used and their relationship to each other. The Offeror shall describe how all maintenance and supply actions required to return a TADSS and Government equipment maintained by the contractor to Fully Mission Capable (FMC) condition can be tracked from the originating maintenance action. The Offeror shall describe in detail its approach to provide the data in a usable format with sufficient information to facilitate transition of the information to a follow-on contractor or allow for competition.

PWS Reference: 3.3.1; 3.4.13; 3.4.14; 3.4.15; 3.4.23; 3.5.1.17; 3.5.1.22; 3.5.1.26; 3.5.1.30

L.4.1.2.2 Udairi Range Complex (URC) Execution Plan

L.4.1.2.2.1 The Offeror shall provide a detailed approach of execution for all items required to operate the URC.

The approach shall include all action from contract award through full performance. The URC execution approach shall use the PWS– Section 3 Table 1, Table 2 and Table 4 schedule as the basis for estimates.

L.4.1.2.2.2 The URC approach shall provide Range Operations staffing schedules that identify each shift / position / location during training operations, road maintenance, burn and range maintenance, range security, and target installation and removal.

PWS Reference: 3.2.2; 3.5.1; 3.7.

L.4.1.2.3 Surge Capability. The Offeror shall describe its approach to meet an increase in the quantity of supplies or services called for under this contract (via a Request for Resources) to handle unscheduled training and/or exercise support requirements, a change in the ARCENT security posture, other support due to an increase of units, and Acts of God that are considered a bona fide Government need.

PWS Reference: 2.5.3

L.4.1.3 Subfactor 2.3: Phase-in / Phase-out:

L.4.1.3.1 Phase-in. The Offeror shall provide a 90-day Phase-in approach that provides for continuity of ARCENT TSS operations with no loss of service and minimal loss of operational knowledge. The plan shall address the following elements:

a) Detailed 90-day Milestone Chart

b) Identification of any risks and describe how those risks will be mitigated

c) Inventory Plan describing how the Offeror will support the Government and outgoing Contractor with inventories and property accountability

d) Approach to ensure open communication with incumbent Contractor and the Government to include periodic meetings documenting progress

e) Personnel plan describing how the contractor will provide personnel in order to assume Full

Performance after the Phase-in period, as required by this PWS

f) Approach to ensure proper, timely requisition / issuance of (as required): appropriate licenses, installation badges and visas for Kuwait or country of deployment IAW ASG Installation Access security clearances

g) Requirements Turnover/Handoff

h) Data and/or Property Transfer

i) Security Requirements to include OPSEC

j) Assess serviceability of current parts on-hand and parts required to ensure prepared for full performance to meet CPF and Ao

k) Capability and approach to support a shortened phase-in period (less than 90 days), and identification of total calendar days needed to fully meet a phase-in requirements at no additional cost to the Government

PWS Reference: 2.5.7.1; 2.5.7.2.1; 2.5.11.1

L.4.1.3.2 Phase-out. The Offeror shall provide a 90-day Phase-out approach that provides for continuity of ARCENT TSS operations with no loss of service and minimal loss of operational knowledge. The plan shall address the following elements:

c) Inventory Plan describing how the Offeror will support the Government and incoming Contractor with inventories and property accountability

d) Approach to ensure open communication with incoming Contractor and the Government to include periodic meetings documenting progress

e) Personnel plan describing how the contractor will support the transition of personnel to incoming contractor

f) Requirements Turnover/Handoff

g) Data and/or Property Transfer

h) Security Requirements to include OPSEC

i) Assess serviceability of current parts on-hand and parts required to support transparent transition.

j) Capability and approach to support a shortened phase-out period (less than 90 days), and identification of total calendar days needed to fully meet a phase-out requirements

PWS Reference: 2.5.11.2

L.4.2 Volume III -- Factor 3 – Cost/Price

This volume shall consist of all information, required to support proposed costs and prices. There are no page limitations for this volume.

Certified cost and pricing data are not currently required; however, the Government reserves the right to request such data prior to award. The information submitted in this volume shall comply with FAR 15.408, Table 15-2, and the requirements set forth below.

The numbers of hours, personnel and labor categories proposed in Volume III must match the numbers proposed in the Offeror’s Technical Factor (L.4.1.1.3 Contractor Work Breakdown Structure (CWBS)).

L.4.2.1 The Offeror shall submit contact information (name, telephone number and email address) for their cognizant Defense Contract Management Agency (DCMA) ACO and cognizant DCAA supervisory auditor. If the Offeror is not assigned to DCMA for contract administration or is not assigned to DCAA for contract audit, the Offeror will identify their cognizant federal auditing agency or agencies (and include the individual contact information). The Offeror shall submit a copy of the most recent ACO letter regarding the status of their accounting system. If that letter is more than a year old and the Offeror has a more current DCAA audit report commenting on the status of their accounting system, a copy of that report will also be submitted and included in the Proposal Volume IV – Cost/Price.

L.4.2.2 If applicable, the Offeror shall disclose information pertaining to any proposed Joint Venture (JV), JV mentor-protégé or mentor-protégé agreement. If a subsidiary or JV, then the Offeror shall provide information identifying all affiliates and provide a copy of the binding documentation (e.g. Contract, Agreement, Evidence) validating the legally binding business relationship. A properly executed Corporate Guaranty Agreement should also be provided.

L.4.2.3 The Offeror shall ensure that the information submitted in this volume is consistent with and fully supports the amounts set forth in the SF33. The total proposed cost shall match the summation of the signed SF 33 in Volume V Administrative / General Information.

L.4.2.4 All elements of the Offeror’s estimated phase-in cost/price shall be included separately in the Offeror’s cost/price volume and in CLIN 0001. Offerors shall not put any phase-in costs/prices in any CLIN other than CLIN 0001.

L.4.2.5. Price Workbook. The Offeror shall complete the RFP attachment entitled, ‘ARCENT Price Workbook,’ provided with this solicitation (to include all Worksheets within the Workbook), to submit prices for the entire ordering period, excluding amounts for which the Government has provided estimated COST values for evaluation purposes. Offerors may not alter pre-existing formulas or values within the workbook. Utilization of the Price Workbook is mandatory and “.pdf” files are not acceptable. The ARCENT Price Workbook shall not be changed, reformatted, or otherwise altered, except as noted in the “Instructions” contained in the Price Workbook, to allow for data input by the Offeror.

The submitted Price Workbook shall not be password protected. Failure of the Offeror to include pricing for all requested elements in the Pricing Workbook will render the proposal non-compliant with the terms of the RFP and therefore ineligible for award.

L.4.2.6 The specific direct labor rates utilized to price the proposal must be identified in the cost and pricing proposal only. For all COST REIMBURSABLE CLINs, the proposal shall set forth a complete breakdown of the direct and indirect rates by category, and the rationale thereof. The Offeror, all proposed Major Subcontractors*, and any Subcontractor providing support under a COST REIMBURSABLE CLIN shall provide the hours and the burdened rate build-up for each labor category, including Fringe, Overhead, Other Indirect(s), General & Administrative (G&A) and Profit.

For COST REIMBURSABLE CLINs, A separate rate build-up shall be included for each labor category provided for the base and each out year. Provisions for overtime and shift differential charges shall be clearly addressed on a per-hour basis. Bid codes (applicable codes used to identify a labor category in the Offerors accounting system), employee names and/or other documentation (such as assigned letter of commitment for key personnel not currently employed by the Offeror) to support the rates proposed shall be provided. Letters of commitment shall clearly identify the prospective employees’ pertinent conditions of employment. The same detailed support data shall be furnished for all major subcontractors. The Government will accept sealed subcontractors’ packages in the proposal.

IAW FAR 52.237-10, the Offeror shall provide a copy of its policy addressing uncompensated overtime.

L.4.2.7 The Offeror and its major subcontractors shall provide the following information according to the following order of preference as supporting information to enable the Government’s evaluation. Current Forward Pricing Rate Agreement (FPRA) or Current Forward Pricing Rate Recommendation (FPRR) provided by the cognizant Administrative Contracting Officer(s) (ACO). Forward Pricing Rate Proposals and provisional billing rates are not acceptable.

L.4.2.8 Offerors are reminded of the requirements of Section 39 of the Office of Federal Procurement Policy (OFPP) Act (41 U.S.C. § 1127, formerly 41 U.S.C. § 435), as amended, which limits allowable costs for senior executive personnel compensation to $693,951 per year.

L.4.2.9 Initiation of contract performance is 01 July 2020.

L.4.2.10 The Offeror shall submit a complete breakdown of costs by major subcontractor. A major subcontractor is defined as a member of the Offeror’s overall team that will perform 10% or more of the proposed effort, yearly, for evaluation purposes.

L.4.2.11 Narratives regarding the Cost/Price Volume shall be submitted in PDF format; however, all MS Excel spreadsheets included as exhibits supporting the Cost and Price Volume (e.g., supporting basis of estimates, etc.)

must be in MS Excel 2013 format that is editable and executable by the Government evaluator(s), clearly showing the calculations and formulas used in each cell. There shall be no hidden formulas or protected cells. Spreadsheets shall show the formulas used to calculate the rates/factors for each entry and shall not be included as an un-executable, un-editable or flat file such as an embedded picture (Enhanced Metafile). Mathematical explanations shall be provided for any embedded macro/extended formula utilized, clearly describing the functioning of the macro or extended formula.). The Narrative shall include the total proposed cost.

L.4.3 VOLUME IV – Administrative / General Information

The Offeror shall prepare and submit an Administrative Volume that contains the following:

L.4.3.1 Proposal Compliance: Each Offeror shall include a statement indicating their complete compliance with the solicitation, or a detailed analysis of any objections, exceptions, contingencies, or additions. Any objection, exception, contingency, or addition shall be cross-referenced to the applicable solicitation document and corresponding paragraph(s). An objection, exception, contingency, or addition to the solicitation taken in the proposal may result in the offer being non-compliant. As part of this statement, an authorized official IAW 52.215(c)(2)(v) shall sign, certifying the following:

(1) The proposed Contract Line Item Number (CLIN) prices within the Pricing Workbook are binding and will be utilized for the life of the contract;

(2) The direct and fully burdened labor rates (inclusive of profit/fee), along with the associated escalation factors used, within the Cost/Price Workbook, as proposed or, if required, negotiated, are binding and will be utilized for the life of the contract.

(3) All requirements of the ARCENT TSS PWS, and all other terms within the solicitation, will be met or identification of exceptions IAW above paragraph.

L.4.3.2. Completed and signed Standard Form (SF) 33 [blocks 12-18] including completion of any solicitation clause or provision that requires a fill-in or response and signed acknowledgment of each amendment (SF30).

The Government requires the ARCENT TSS be valid for at least two hundred and seventy (270) calendar days from the final, phase II proposal due date. The Offeror shall complete Block 12 of each SF 33 submitted with full cognizance of the minimum acceptance period of 270 calendar days. The Offeror's legal name and address in Block 15A on the SF33 must match the information for the Offeror in at SAM.gov, including the corresponding CAGE Code Number and DUNS (note: the address listed in Block 15A will be the official mailing address used by the Government for letter correspondence, if necessary). The name, title, signature, and date identified in Block 16, 17, 18, must be an authorized representative with authority to commit the Offeror to contractual obligations.

L.4.3.3. RFP Sections K - Completed Representations, Certifications, and Other Statements accurately completed and certified.

L.4.3.4 Binding Teaming Agreements, Joint Vent Venture Agreements, Letters of Commitment, Distribution agreements and other legal agreements required for team members identified in Volumes I-III.

L.4.3.5 The Offeror shall provide a property management plan in accordance with FAR Clause 52.245-1(f) requirements applicable to Government Property Management under this contract. The property management plan is a requirement for award and will be incorporated into the resultant contract

L4.3.6 All Offerors, both Small Business and Other Than Small Business (Large Business), are required to provide a Small Business Participation Commitment Document, which shall clearly demonstrate a viable plan for meeting or exceeding the Small Business Participation goal of no less than 10% of the total proposed contract value in each year of contract performance. The Small Business Participation Commitment Document is not a requirement for evaluation in source selection, but rather a requirement for award to a large business and will be incorporated into any resultant contract. The Small Business Participation Commitment Document shall be completely stand-alone, and not require any reference to another source, volume, or proposal. A Small Business Offeror can meet the Small Business Participation requirement through performance as a Small Business, or a combination of performance and Small Business subcontracting. Negotiations with the apparently successful offeror regarding the Small Business Subcontracting Plan do not constitute discussions. The Subcontracting Plans shall reflect and be consistent with the commitments offered in the Small Business Participation Plan.

Offerors shall submit a single Small Business Participation Commitment Document, which shall include the following:

a. Type of Business of prime contractor (Check all applicable boxes):

{ } Large { } Small (also check type of SB below):

{ } Small Disadvantaged Business { } Woman-Owned Small Business { } Historically Underutilized Business (HUB) Zone SB { } Service Disabled Veteran Owned Small Business

b. Total Contract Ceiling (BASE plus OPTIONs): $____________

c. Dollar Value performed by offeror as Prime Contractor: $____________

d. Dollar Value and Percentage of Total Contract Value awarded to both large and small businesses. All percentages should use Total Contract Value as a baseline. Include only first tier subcontractors. Fill in all applicable sections of the table below.

Dollar Value Percentage of Total Contract Value Large: $ % Small*: $ % Total**: $ 100%

*NOTE 01: Small includes: Small Business (SB), Small Disadvantaged Business (SDB), Women-Owned Small Business (WOSB), Historically Underutilized Business Zones (HUBZone), and Service-Disabled Veteran-Owned Small Business (SDVOSB). Only include once regardless if represented in multiple groups.

**NOTE 02: Include the Prime Offeror’s dollars and percentage(s). When combined, Large and Small Business totals must equal 100% of the Total Contract Value.

e. The Offeror shall populate the following table to identify all anticipated Prime and subcontracted supplies/services. When combined, Prime and anticipated subcontracted totals must equal 100% of the Estimated Contract Ceiling Value. The sum of the Estimated Total Dollars for Each Service/Supply for the stated SB subcontractors should ultimately lead to achieving the Small Business Participation goal of no less than 10% for each year of contract performance (BASE plus OPTIONs). The Offeror shall create as many rows and tables as necessary to adequately identify all subcontractors for each year of contract performance (BASE plus OPTIONs).

Pursuant to Section 8(d) of the Small Business Act, a concern is Small for subcontracts which relate to Government procurements if it does not exceed the size standard for the North American Industry Classification System (NAICS) code that the prime contractor believes best describes the product or services being acquired by the subcontract. In other words, the size of the Offeror’s subcontractors and suppliers is determined by the NAICS code of the subcontract, which may or may not be the same NAICS code as the one for Offeror’s contract with the Government.

BASE PERIOD

Name of Company (Include CAGE Code)

Anticipated NAICS Code for Each Subcontractor

Type of Service/Supply

Estimated Total Dollars for Each Service/Supply

Prime Offeror:

Large:

Small:

OPTION YEAR 01

Name of Company (Include CAGE Code)

Anticipated NAICS Code for Each Subcontractor

Type of Service/Supply

Estimated Total Dollars for Each Service/Supply

OPTION YEAR 02

Name of Company (Include CAGE Code)

Anticipated NAICS Code for Each Subcontractor

Type of Service/Supply

Estimated Total Dollars for Each Service/Supply

The Offeror shall provide a short description of the specific services to be provided and the nature of complexity by each SB, the rationale supporting SB selection(s), and the estimated total dollar value for each service. Complexity is defined as the level of involvement for performance of functions provided by the SB concerns.

The Offeror shall provide an explanation pertaining to the process the Offeror uses for identifying and selecting SBs for subcontracted work and how the process will be used on this contract to meet the Offeror’s SB Participation requirement.

f. Extent of Commitment: The Offeror shall provide documentation regarding individual and enforceable commitments to utilize any SB firms, as defined in FAR Part 19, as subcontractors. Copies of such commitments shall be provided as part of Volume IV – Administrative Information.

L.4.3.7 The Offeror shall establish and maintain acceptable business systems (Cost Estimating, Material Management and Accounting, Purchasing, and Property Management - see DFARS 252.215-7002, 252.242-7004, 252.244-7001, and 252.245-7003, respectively) IAW DFARS Clause 252.242-7005, Contractor Business System.

The Offeror shall submit contact information (name, telephone number and email address) for the cognizant Defense Contract Management Agency (DCMA) Administrative Contracting Officer (ACO) and cognizant Defense Contract Audit Agency (DCAA) Supervisory Auditor. If the Offeror is not assigned to DCMA for contract administration or is not assigned to DCAA for audit, the Offeror shall identify the cognizant federal agency or agencies (and include the individual contact information). If any of the Offeror's business systems have never been audited by DCAA or DCMA, the Offeror shall so state. The Offeror shall submit a copy of the most recent ACO letter regarding the status of their applicable business systems.

BASIS FOR AWARD

Section M - Evaluation Factors for Award

M.1 The award will be made on the best overall (best value) proposal using a combination of Phase 1 - Acceptable/Unacceptable and Phase II - Subjective Tradeoff Source Selection Processes in accordance with FAR Part 15.101-1 for Best Value Decision, the Department of Defense (DOD) Source Selection Guide, the Army Source Selection Supplement (AS3), and applicable…