RFP_ARCENT_TSS_W900KK-20-R-0048__Amendment 0001_13_DEC_19.pdf

W900KK20R0048

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to:

1. Incorporate revisions to Sections L and M;

2. Provide responses to potential offeros ARCENT TSS Phase-I RFP questions; and

3. Provide an updated PWS.

There are no significant changes to the RFP criteria. Therefore, there is no extension to the ARCENT TSS Phase I proposal submission due date and time.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 27

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

16C. DATE SIGNED

BY 13-Dec-2019

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W900KK20R0048

X 9B. DATED (SEE ITEM 11)

02-Dec-2019

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

13-Dec-2019

CODE

ARMY CONTRACTING COMMAND - ORLANDO

ATTN: DELTA DIVISION

12211 SCIENCE DRIVE

ORLANDO FL 32826-3224

W900KK 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The number of offeror copies required has decreased by 1 from 2 to 1.

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

EXHIBITS AND ATTACHMENTS

Item Description

Exhibit A CDRLS A001 – A021

Attachment 1 ARCENT TSS PWS

Attachment 1(a) ARCENT TSS PWS Appendix A – Government Furnished Property

Attachment 1(b) ARCENT TSS PWS Appendix B – UDAIRI RANGE COMPLEX Maintenance Responsibility

Attachment 1(c) ARCENT TSS PWS Appendix C - ASG-KU Udairi Range Complex (URC) Policy and Procedures (PAP)-Standard Operating Procedures

(SOP)

Attachment 1(d) ARCENT TSS PWS Appendix D – TADSS Locations and Availability

Attachment 1(e) ARCENT TSS PWS Appendix E – Kuwait Work Order Data as of 1

NOV 2019

Attachment 1(f) ARCENT TSS PWS Appendix F – Program of Instructions

Attachment 1(g) ARCENT TSS PWS Appendix G – TADSS Tech Manuals

Attachment 2 DD254 (DRAFT with solicitation, FINAL at award)

Attachment 3 Procedures for Government Property

Attachment 4 Question/Comment Form

Attachment 5 Technical Experience Reference Workbook

Attachment 6 ARCENT Price Workbook

Attachment 7 Cross-Reference Matrix

Attachment 8 ARCENT SF 1408 Checklist

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

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

$38.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 SF 33 coversheet. 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/. Hard copy proposals will not be accepted.

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 (PCO), identified in Section L.2.8.

Offerors are encouraged to test the DoD SAFE proposal exchange methodology by sending a copy of the ARCENT TSS PWS to the aforementioned POCs at least 72 hours prior to the proposal due date/time. The Government will confirm receipt, via email, within one business day. If confirmation email is not received, please coordinate directly with the PCO to resolve issue.

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 received by the Government 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 Microsoft Word documents shall also be included as a 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 Technical Exp. Ref. Workbook plus a supplemental Technical Experience Narrative, up to ten Microsoft Word pages.

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. Documents submitted in their native format will be the control document and take precedence over PDF copies. (e.g. difference in page count and/or content)

L.2.7 Acronym lists, cover pages, title pages, table of contents, cross reference matrices, dividers, index tabs, and 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. Additionally, teaming agreements, letters of commitment, and the Staffing Plan, attached to their respective volume, will not be counted as part of the page count.

A supplemental Technical Experience Narrative 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 Reference Workbook, or to summarize the Technical Experience Volume. For the supplemental Technical Experience Narrative, the Offeror can provide up to ten pages, as required.

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 the Government Point of Entry in which the RFP was posted or 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, NLT 1400 hours ET, 7 calendar days after the RFP issue date annotated on the SF 33 coversheet. The Government will respond to questions/comments specific to Phase I prior to the proposal due date for Phase I. Responses specific to questions/comments regarding Phase II of the RFP may be provided by the Government after the Phase I due date and prior to the Phase II due date. Offerors with an acceptable Phase I proposal will be afforded an additional opportunity to submit questions/comments regarding Phase II; specific instructions will be within the PCO notification referenced in L.2. The subject line of the email for Offeror’s questions/comments shall include the RFP Solicitation number, W900KK-20-R-0048. Questions/comments shall be submitted using the RFP attachment entitled “Question/Comment Form.”

L.2.11 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. For Volume II – Factor 2 – Program Management the Offerors may refer to another Subfactor within this Factor. Proposals submitted will not be returned. Alternate proposals will not be evaluated or accepted.

L.2.12 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.13 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.14 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 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.

Format requirements provided in this section do not apply to Government provided documents, such as: SF forms, Section K, DD254, Pricing, etc. RFP Attachment – Technical Experience Reference Workbook – shall use the text format, size and style, provided with the attachment, as is. For example, if Attachment 5 provides for 11pt, Calibri font for the Offeror fill-in boxes, the Offeror shall complete this attachment with text in 11pt, Calibri font.

Additionally, attachments to the Offeror’s proposal, such as: Teaming agreements, verification documents for Vol I, etc., are not required to be compliant with the format requirements.

L.3.2 Cross-Reference Matrix –The intent of the attached Cross-Reference Matrix is to ensure that all requirements for Volume II - 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. The Cross-Reference Matrix is to assist evaluators during the evaluation; however, the Cross-Reference Matrix will not be evaluated.

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.4 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.5 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 operations. PWS Reference: 3.2.2; 3..5.1.1; 3..5.1.2;

3..5.1.2; 3..5.1.3; ;3.5.1.3..3; 3.5.1.4; 3..5.1.7; 3.5.1.8; 3.5.1.9.1; 3.5.1.9.2; 3.5.1.10; 3.5.1.10.1; 3.5.1.10.3;

3.5.1.10.5; 3.5.1.11; 3.5.1.15; 3.5.1.16; 3.5.1.19; 3.5.1.22; 3.5.1.24.; 3.5.1.30 ; 3.5.1.36; 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.2.1; 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 six consecutive months, with three-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 equal to or greater than $5 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) and (h).

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.04 Technical Experience references may include references of the Offeror’s proposed major subcontractors for this effort. Joint Ventures may include references executed by individual member(s) of the Joint Venture. For the Technical Experience Factor, a major subcontractor is considered a subcontractor executing at least 10% of the total proposed value.

L.4.0.5 Each Technical Experience reference submitted may have been executed in the capacity as the prime contractor or subcontractor. If Technical Experience submitted was executed in the capacity of a subcontractor, the submission requirements of L.4.0.1 (a) through (h) are applicable to the subcontracted work performed and NOT applicable to the prime contractor’s work performed.

L.4.0.6 The Offeror shall include applicable verification documents, which unambiguously and sufficiently validate the individual Technical Experience references submitted. When a Technical Experience reference submitted was executed in the capacity of a subcontractor, the Offeror shall ensure the applicable verification documents patently differentiate the subcontractor’s Technical Experience from the prime contractor’s Technical Experience. Failure to provide verifiable documents, which unambiguously and sufficiently validate the individual Technical Experience, will result in the Government not considering the individual submittal for evaluation.

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 or individual members of a JV citing their Technical Experience in this Volume.

In addition, the Offeror may supplement the Technical Experience Workbook with a narrative, up to ten- Microsoft Word pages, total, for all technical experience references. This narrative, if provided, shall be included within Volume I, Factor 1 proposal. There is no benefit to submitting up to five Technical Experience references when a fewer number will suffice.

Additional instructions are contained within Attachment 5 – 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 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, for the ARCENT contract: how lessons learned will be incorporated to improve recruitment and retention practices;

recruitment and hiring practices that will be used for this contract; 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 Staffing Plan. Within Microsoft Project, the Offeror shall provide, as an attachment to this volume, a Staffing Plan with all proposed labor categories executing performance-based requirements within the PWS. Each Staffing Plan shall identify, for the proposed labor categories, clearly defined lines of responsibility, clearly defined levels of decision authority, reporting structures, 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).

Staffing Plan 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)

Staffing Plan rationale and assumptions: Within this the Volume, 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.11.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) Describe their methodology and approach to managing multiple subcontractors, joint venture, and/ or teaming partners in order to execute multiple requirements;

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

c) 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

d) 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.11.6

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 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, Table 4, and Table 6 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.1; 3.5.1.31; 3.5.1.8; 3.5.1.4; 3.5.1.10.3; 3.5.1.10.4; 3.5.1.11; 3.5.1.15; 3.5.1.18;

3.5.1.19; 3.5.1.25; 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.2.4 Materials and Other Direct Costs (ODCs).

L.4.1.2.4.1 The Offeror shall identify, by each year of contract performance, a complete listing of the known materials and ODCs required to support ARCENT TSS PWS requirements. For each material identified in each year of performance, the Offeror shall identify the specific part name, quantity, PWS paragraph in which the material will support, and description of how the material will be specifically applied. For each ODC identified, in each year of performance, the Offeror shall identify the ODC description, quantity, PWS paragraph in which the ODCs will support, and description of how the ODC will be specifically applied. The listing of known materials and ODCs shall be provided as an attachment to this Volume.

L.4.1.2.4.2 The Offeror shall describe its approach to the proposed Materials and ODCs and how it minimizes the need to request additional materials and ODCs for the performance or ARCENT TSS PWS requirements.

PWS Reference: 2(e); 2.7.2; 3.1.5.3.3; 3.3.1; 3.5.1.8; 3.5.1.10.1; 3.5.1.18; 3.5.1.29; 3.5.1.36; 4.4.2

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 (shall be submitted in Microsoft Project as Attachment to this Volume)

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 the 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:

a) Detailed 90-day Milestone Chart (shall be submitted in Microsoft Project as Attachment to this Volume)

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 Factor 3 must match the numbers proposed in the Offeror’s Technical Factor (L.4.1.1.3 Staffing Plan).

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.1.1 . If the Offeror’s accounting system was disapproved or deemed to be not adequate, the Offeror will identify all deficiencies along with steps taken, or to be taken, to correct the deficiencies and a timeline to include audit by the cognizant audit agency after corrective action has been implemented. If the Offeror’s accounting system has never been audited by their cognizant federal audit agency, the Offeror will so state. If the Offeror does not have an approved accounting system, the Offeror shall complete SF1408 - Preaward Survey of Prospective Contractor Accounting System Checklist, and return the documentation as part of the Price Volume of the proposal. Within this survey, mark “X” in the appropriate column; and on Page 2, provide a narrative describing how the current accounting system supports your response to each item.

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 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.4. 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 performance 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. Offerors may add worksheets within the cost/price workbook to provide requested information. Inserted information shall editable and executable by the Government evaluator(s), clearly showing the calculations and formulas used in each cell.

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 may render the proposal non-compliant with the terms of the RFP, at the sole discretion of the PCO, and therefore ineligible for award.

L.4.2.5 The specific direct labor rates utilized to price the proposal must be identified in the cost and pricing proposal only. The proposal shall set forth a complete breakdown of the direct and indirect rates by category. The Offeror and all proposed Major Subcontractors shall provide the hours and the burdened rate build-up for each labor category, including Fringe, Overhead, Other Indirect(s), General & Administrative (G&A), DBA Insurance, DSSR uplift, Profit, and any additional indirect rates as applicable.

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.6 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.6.1 If neither a FPRA nor FPRR are available (or, if the agreement/recommendation does not include direct labor rates), the offeror shall provide the following:

Direct labor rates: Offeror shall submit the most recent actual average rate for each proposed category. Offeror shall submit the actual average rate, as of the end of each of the last two completed fiscal years, for each proposed category. The "as of" date must be shown for each calculation. For each category and each year, the offeror shall identify the number of employees in each calculation. The timing of wage/salary increases will be identified in the offeror's proposal (i.e., employee's anniversary date, yearly during [month], or other [with explanation]). If the above is not available, the offeror shall provide sufficient justification for the proposed direct labor rates through the most appropriate means available. The direct labor rate information shall be submitted for both the offeror and all major subcontractors.

Indirect rates (for each and every proposed indirect rate): Offeror shall identify the start and end of their fiscal year and the allocation/application base for each indirect rate.