Amendment 0002.pdf

W911S020R0006

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 revise PWS Attachment #3, 'Task Breakdow n by Site' at Fort Leonard Wood and to provide the Government's responses to Industry questions already received. Additional Government responses to Industry questions w ill be provided after the period for question submission ends. See file, "Government Responses to Industry Questions Summary.xlsx"

1. CONTRACT ID CODE PAGE OF PAGES

S 1 74

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

16C. DATE SIGNED

BY 14-Apr-2020

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 W911S020R0006

X 9B. DATED (SEE ITEM 11)

30-Mar-2020

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

14-Apr-2020

CODE

MICC - FORT EUSTIS

705 WASHINGTON BLVD

FORT EUSTIS VA 23604

W911S0 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 SF 1449 - CONTINUATION SHEET

The following have been modified:

ADDENDUM TO 52.212-1

A. INTRODUCTION

Contract Type: The Government contemplates awarding a Firm Fixed Price (FFP) contract which will include Cost Reimbursable Contract Line Item Numbers (CLINs) for Travel and Other Direct Costs (ODC) utilizing the best value trade‐ off approach.

B. PROPOSAL SUBMITTAL AND INQUIRIES

1. Closing Date/Time: 30 April 20 12:00PM, EST. It is the Offeror’s responsibility to assure its proposal is received by the date and time specified. In accordance with (IAW) FAR 52.212-1, if your proposal is not received at the initial point of entry to the Government (e‐mail by the exact date and time specified above), it will be determined late and will not be evaluated. Proposal, as the term is used here, means ALL volumes and/or parts of the RFP. Any proposal that fails to comply with all the requirements of the RFP may be rejected from further consideration.

2. Questions regarding this RFP shall be in writing and directed via e‐mail to both the Contracting Officer, Roger McAughan, and Contract Specialist, Melinda Paynter. All correspondence shall reference RFP Number W911S0‐20‐R‐0006. The cut‐off for questions is 16 April 20, 12:00PM, EST. All questions will be answered electronically, allowing all Offerors access to each question and corresponding answer. Contractors will see both the question and the answer. However, the identity of the person/company asking the question will not be disclosed. Emails shall be clearly marked RFP W911S0‐20‐R‐0006 in the subject line to:

Roger McAughan, Contracting Officer, roger.j.mcaughan.civ@mail.mil (757) 501‐8331; Melinda Paynter, Contract Specialist, melinda.c.paynter.civ@mail.mil, (757) 501‐7093.

3. All questions received in a timely manner (within seven (7) working days following the issue date of the solicitation, shall be answered by Amendment. Questions received after that time may not be answered in sufficient time for Offerors to adjust their proposals and meet the closing date/time of the solicitation. All questions shall annotate source document, page, and paragraph number.

4. Resolution of Issues. The Contracting Officer reserves the right to withdraw and cancel the proposed RFP. In such event, the Offeror will be notified in writing of the Contracting Officer’s decision. This decision is final and conclusive and shall not be subject to the “Disputes” clause or the “Contract Disputes Act.”

5. All questions shall be included on Attachment 13 of this Addendum, see “Attachment 13 - Question Format”.

C. GENERAL INSTRUCTIONS

1. The Offer: The submission of the documentations specified below will constitute the Offeror's acceptance of the terms and conditions of the RFP, concurrence with the Performance Work Statement (PWS), provisions, and contract type.

2. The proposal shall be in full compliance with the instructions in this RFP. The proposal (to include price) shall be valid for 180 calendar days.

3. The Government will conduct evaluations using the best value Trade-Off Approach and will follow FAR 15.3, Source Selection evaluation criteria set forth in ADDENDUM TO 52.212-2 (Evaluation- Commercial Items) considering solely the Offeror’s response to this RFP.

4. The award will be based upon an integrated assessment of all price and non-price factors. Trade-offs between cost and non-cost factors are permitted. A proposal that demonstrates a Superior Technical Approach (Factor I) in the Work Processes and Work Scheduling Elements may be worth more to the Government than a proposal that only meets minimum requirements in Work Processes and Work Scheduling Elements. Evaluation and discussion procedures at FAR 15.3, Source Selection, does apply to this acquisition.

5. The Offeror shall submit an unclassified proposal that demonstrates its ability to perform and meet the requirements in the PWS. Proposals shall conform to all the requirements of this RFP. Failure to conform may result in your proposal being rejected and no longer considered for award.

6. Offerors are notified that the Government will not reimburse costs incurred for proposal preparation, to include pre-award site visits.

7. Although the Government does not intend to hold discussions/communications, the Government does reserve the right to negotiate with one or more but not necessarily all Offerors, for any reason. Any proposal revisions may be limited to the items negotiated.

8. For labor categories that are non-exempt under this RFP, calculate price using the wage determination for the specific location the individual will be assigned. Go to beta.SAM.gov to locate the applicable wage determination. All proposals submitted in response to this RFP shall reflect the use of current, updated fringe benefit rates. The contractor’s wage rate shall comply with the DOL wage rate minimum requirements for the area in which the work is to be done. The contractors shall specify the city, state, and country in which the work will take place. This is necessary so that the appropriate DOL rates can be provided. Where multiple places of performance apply, provide a separate wage determination for each place of performance that is required under this RFP.

9. If the value of this contract is expected to exceed $10,000,000.00 your firm shall be in compliance with the Equal Employment Opportunity (EEO) regulations before award of the resultant TO. Ensure your firm is on the Department of Labor (DOL) EEO National Pre-Award Registry or that you can provide verification of EEO compliance if requested by the Government. See https://ofccp.dol-esa.gov/preaward/pa_reg.html for more information. This registry is updated every two years and it does not provide information on the Parent Organization or other facility locations that have not been reviewed.

10. Offerors are cautioned that e‐mail is not instantaneous. We recommend you submit your proposal prior to the closing date, allowing enough time to ensure the entire proposal is received on time to be considered for award. If any e‐mailed portion of the Offeror’s proposal is not received by the RFP closing deadline, the proposal shall be rejected as late (see FAR 52.212-1). Re‐send your e‐mail submission if you do not receive a receipt confirmation. If you do not receive a receipt confirmation after the second transmission, contact the Contract Specialist. Due to Government exchange size limitations, we cannot receive individual e‐mails that exceed 10 MB, including the e‐mail itself plus all attachments. If your electronic proposal, including all attachments, is larger than 10 MB, you shall segment your proposal into a series of two (2) or more separate e‐mails that individually are no larger than 10 MB. We cannot receive e‐mails if they contain compressed attachments. Our security software blocks these types of e‐ mails.

11. Offerors shall identify in the e‐mail subject line the following: W911S0‐20‐R‐0006, closing date/time, content, and the Offeror’s name. For example: “fill in RFP number, day/time/content, name, Message 1 of 5, XYZ Company”.

12. In the body of each e‐mail message of the proposal, the Offeror shall provide a brief statement accounting for each e‐mail in relation to the entire proposal. For example, “Message 3 or 5, as well as inventory of attachments” or “Attachment 1 of 4” or “This message 3 of a total of 5 messages constituting the Request for Proposal of XYZ Company” or “This message provides attachments 2 and 3 of a total of 6 attachments to our complete Request for Proposal.”

13. Pages are limited to 8 ½” x 11”. Number all pages. Graphs and tables included in the technical proposal need not be double-spaced, but to ensure legibility, the text in graphics may be 9-point; however, all text not in graphics shall be no smaller than 12- point type. Inclusion of any graphs or tables is counted within the page limitation. Any pages submitted in excess of the page limit stated in Table 1 will not be evaluated and will be returned to the Contractor. Volume Cover, Table of Contents, Glossary, and Compliance Matrix pages included in an offerors proposal are exclusive of the page count. Contractors are cautioned that failure to follow these instructions may result in an incomplete evaluation of the proposal. Offerors shall submit separate electronic documents, by volume, with its proposal.

14. Offerors are not authorized to include citations for, or linkages to, websites in the RFP.

15. Ensure that all volumes are submitted in response to this RFP. Failure to do so may result in your proposal not being considered. Your proposal shall be structured in a manner that clearly addresses the requirements for this RFP. Responses that are overly verbose or include marketing material are not desired.

D. INSTRUCTIONS AND PROPOSAL CONTENT

1. *IMPORTANT ‐ Offerors simply providing general statements or paraphrasing/parroting the PWS in whole or in any part shall result in a rating of unacceptable. The proposal shall be clear, concise, and include sufficient detail for effective evaluation and for substantiating the validity of stated claims in the offeror’s proposal. Legibility, clarity and coherence are very important. Your responses will be evaluated against the factors defined in the ADDENDUM TO 52.212‐2 – (Evaluation, Commercial Items).

2. The proposal should not simply rephrase or restate the Government's requirements, but rather shall provide convincing rationale to address how the offeror intends to meet these requirements. Statements that the offeror understands, can, or will comply with the PWS (including referenced publications, technical data, etc.); statements paraphrasing the PWS or parts thereof (including applicable publications, technical data, etc.); and phrases such as “standard procedures will be employed” or “well known techniques will be used,” etc., will be considered unacceptable. Offerors shall assume that the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the information presented in the Offeror's proposal. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

3. The length of your response to this RFP is limited, as identified below. Take extreme care and attention to ensure that all required documents are included in the RFP. Information submitted beyond the page limitations, identified below, will not be evaluated and may be considered cause for rejection of your proposal. Offerors are required to submit their proposals in four (4) separate Volumes as follows:

Section Page Limitation Volume I: General Information Tab A‐NTE* 5 pages Volume II: Technical Capability Tab B & C‐NTE* 75 pages Volume III: Past performance Tab D‐NTE* 5 pages

Volume IV: Price Tab E–Unlimited

*NTE‐ Not to Exceed

4. The Offeror’s proposal volumes shall be organized and contain the information specified below in Table 1.

Table 1: Request for Proposal Content Volume Tab Section Page

Limit Title File

Submission

I. General Information A NTE 5 Word or

PDF

A1 Offeror’s General Information

A2 Executive Summary:

Organization Conflicts of Interest (OCI), OCI Risk and OCI Risk Mitigation and Teaming Arrangements (Including Sub- Contractors)

A3 Exceptions/Assumptions

II. Technical Capability

B&C

NTE 75

Technical Capability

Word or

PDF

Technical Approach (Factor I)

40 Technical Approach (Factor I)

Element I B1 Work Processes

Element II B2 Work Scheduling

Element III B3 Quality Control Approach

Management Approach (Factor II)

35 Management Approach (Factor II)

Element I C1 5 Phase-In Approach

Element II C2 10 (Excluding Resumes)

Staffing, Resource Management and Key Personnel

Element III C3 10 Management Controls

Element IV C4 10 Organizational Interfaces and Communications

III. Past Performance D

5 Past Performance (Factor III)

Word or

PDF

IV. Price Factor E Unlimited Price (Factor IV)

Excel

E1 Pricing Notes Excel

E2 Proposal Pricing Breakdown

E3 Proposed Labor Categories and Hours

E4 SCLS Proposed Labor

E5 Total Compensation Plan

5.1 Volume I: General Information: The General Information Volume shall contain the identified information detailed below and shall not exceed five (5) pages.

TAB A1 - Standard Form 1449 (SF 1449) & Offeror’s General Information: The SF 1449 shall be submitted fully completed. The Offeror is cautioned that the SF 1449 must contain an original signature in block 30a of the form. Offeror’s General Information: The Offeror shall also provide the name, title and telephone number of the company/division point of contact regarding decisions made with respect to Offeror’s proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

TAB A2 – Executive Summary: OCI, OCI Risk and OCI Risk Mitigation and Teaming Arrangements (Including Sub-Contractors)

TAB A3 - Exceptions/Assumptions (if required): The Offeror shall identify and provide an explanation of any exceptions or deviations. If the Offeror finds it necessary to take exception to any of the requirements specified in the solicitation, the Offeror shall clearly identify the applicable Volume and exceptions with a complete explanation of why the exception was taken, what benefit accrues to the Government (if any), and its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation.

Each exception shall be specifically related to each paragraph and/specific part of the solicitation to which the exception is taken. Offerors are cautioned that taking an exception may render the Offer ineligible for award. This information shall be provided in the format outlined below in Table 2. Additionally, any assumptions used in the proposal preparation must be identified.

Table 2 – Solicitations Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion

Rationale & Impact

Section B, PWS, Applicable Identify the Describe etc. Page and requirement The rationale

Paragraph or portion to which and impact of Numbers. exception is taken. the exception.

5.2 VOLUME II: Technical Capability: The Technical Capability Volume is inclusive of the Technical Approach (Factor I) and Management Approach (Factor II) and shall not exceed 75 pages.

5.2.1 Technical Approach (Factor I): The Technical Approach Factor I is inclusive of the Work Processes, Work Scheduling and Quality Control Elements. The Offerors shall demonstrate their understanding of the Technical Approach by clearly discussing the Technical Elements identified below with respect to specific requirements indicated in Part 5, Sections 5.1 through 5.6.5 of the PWS. The Offeror is highly encouraged to use the information provided in PWS Attachment 1--Contractor Responsibilities, PWS Attachment 2--Site Specific Duties, and PWS Attachment 3--Task Breakdown by Sites in the PWS to develop their Technical Approach. The Technical Approach shall include the following and shall not exceed 40 Pages:

TAB B1 - Work Processes (Element I): The Offeror’s Work Processes shall demonstrate a full understanding of LLC’s capabilities and mission. The Offeror’s Work Processes shall ensure efficient, quality and timely performance of the tasks in the PWS. The Work Processes element shall address how the Offeror will meet the following requirements as described in Part 5-- Specific Tasks of the PWS and how it will fulfill the requirements listed below:

a. Identifying and describing the major work processes that will be used to meet the requirements in the PWS.

b. Identifying and describing the interfaces between the work processes.

c. Defining the inputs and outputs of these processes.

TAB B2 - Work Scheduling (Element II): The Offeror’s proposal shall describe how work will be scheduled, to include employment of any automated systems or work loading procedures. The Offeror’s proposed Work Scheduling element shall describe the following requirements below:

a. Managing and scheduling work for the entire LLC effort at ALL the sites identified in the PWS.

b. Identifying the resources and activities needed for assigned tasks.

c. Provide coverage for work surges and after duty hours.

TAB B3 - Quality Control (Element III): The Offeror’s Quality Control Approach shall describe how it will ensure quality performance and compliance of all key control elements, deliverables and metrics IAW the PWS Paragraph 1.5.3 and the PWS Performance Requirements Summary (PRS) Paragraph 6.1. The Offeror’s Quality Control Approach shall address the following requirements below:

a. Quality Control Management processes.

b. Quality Control roles and responsibilities.

c. Methods of surveillance/monitoring.

d. Methods for identifying and correcting deficiencies.

e. Methods for customer feedback.

f. Measures of performance.

g. Reporting requirements and their frequencies.

5.2.2 Management Approach (Factor II): The Management Approach Factor II is inclusive of the Phase- In, Staffing, Resource Management, and Key Personnel, Management Controls, and Organizational Interface and Communication, elements. Each element will be assigned a rating to allow the Government to conduct “trade-offs” amongst the various management elements. The Offerors shall demonstrate their understanding of the various management elements identified below with respect to requirements indicated in the PWS. The Management Approach shall include the following and shall not exceed 35 pages (Excluding Resumes):

TAB C1- Phase-In Plan (Element I): The Offeror will assume full responsibility for all areas of operation in accordance with the contract terms and conditions in order to ensure a smooth transition of the contracted operations. The proposed phase-in approach shall discuss the organization structure, staffing, tasks, and approach used to adequately complete transition of services from the current Contractor to the new Contractor, within the required time. The Offeror’s phase-in plan shall demonstrate how to ensure smooth transition of the contractual requirement.

The Phase-In Plan shall not exceed five (5) pages.

TAB C2 – Staffing, Resource Management, and Key Personnel (Element II): This element shall clearly describe the following and shall not exceed 10 pages.

a. Staffing: The Offeror shall include sufficient details to clearly describe its method(s) of providing a sufficiently skilled and adequate workforce capable of meeting the LLC PWS requirements. The Offerors’ staffing methods shall demonstrate the following:

i. Proposed staffing with estimated personnel numbers and labor categories for each site identified in the PWS.

ii. Methods for cross-utilization of personnel at and between sites.

iii. Training strategies to ensure personnel have the necessary skill levels for contract execution.

b. Resource Management and Key Personnel: The Offeror shall clearly detail the experience, qualifications, and abilities of their proposed key personnel, management and administrative teams. Resumes are required for all proposed key which demonstrate the proposed Key Personnel are capable of meeting the PWS requirements. The Offerors’ resource management and key personnel methods shall demonstrate the following:

i. How its program manager and other key personnel will be utilized to meet the requirements of the PWS.

ii. Staffing processes and tools to be used such as headhunter and recruiting sites.

iii. Key personnel possess required certifications, security clearances, education and work experience established by the PWS to perform the work requirements.

TAB C3 - Management Controls: (Element III): The Offeror’s proposal shall describe its management procedures and the manner in which personnel will be monitored to ensure they are capable of meeting the requirements detailed in the PWS. The Offeror’s Management Controls shall address the following areas and shall not exceed 10 pages.

a. Performance monitoring procedures.

b. Performance indicators to ensure timely and quality work.

c. Management Risk Mitigation and problem escalation processes.

TAB C4 - Organizational Interfaces and Communications (Element IV): The Offeror’s Organizational Interfaces and Communications element shall clearly describe the methods, strategies, and tools used to facilitate information exchange. This approach shall demonstrate interfaces and communications between its different work groups (i.e. departments, teams, offices, etc.) subcontractors and/or team members, and Government representatives. The Offeror’s Organizational Interfaces and Communication tab shall not exceed 10 Pages.

5.3 VOLUME III: Past Performance (Factor III): The Past Performance Volume shall include the Past Performance information as described below and shall not exceed five (5) pages.

TAB D- Past Performance information described herein is required on the Offeror and all subcontractors, teaming partners, and/or joint venture partners proposed to perform 25% or more of the proposed effort based on the total proposed price. The Offeror shall submit, along with the information required in this paragraph, a consent letter, executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the offeror can respond to such information. Attachment 6, Subcontractor/Teaming Partner Consent Form for the Release of Past Performance Information to the Prime Contractor, is provided as a SAMPLE. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offeror's performance. In addition, the Offeror shall identify no more than three (3) of its most recent/relevant experienced Contracts/TOs/Delivery Orders (DOs) that either (i) it has successfully completed or (ii) it has performed in part, within the past three (3) years, including proposed Subcontractors.

a. Both recent and relevant are defined as follows:

i. Recent Contracts: Contracts, TOs, and/or DOs are those performed within (or currently performing) three (3) years from the date of issuance of this RFP.

ii. Relevant Contracts: Contracts, TOs, and/or DOs are those, which are similar in scope, magnitude, and complexity to the requirements in this RFP. Where prior relevant experience is under a broader Blanket Purchase Agreement (BPA) or IDIQ - type Contract, do not just cite the broader BPA or IDIQ Contract. Rather, include the specific individual TOs or Dos and dollar value of the firm’s portion, considered to be representative of relevant prior experience. Each prior Contract, TO, and/or DO identified by the Offeror as being responsive will be evaluated as evidence of relevant prior experience.

b. Relevancy Narrative: The Offeror shall address the relevancy of referenced contracts, TOs and/or DOs as well as similarity to the effort contemplated by the RFP. The discussion of similarity shall include a description of services or related tasks similar to those that it will be performed in support of LLC. In addition, the Offeror shall provide the following information:

i. Identify information on significant achievements. Describe any challenges or obstacles that were encountered during contract performance and the measures taken to overcome them.

ii. Include a discussion of the events or circumstances affecting any termination decision and/or performance litigation for any contracts/subcontracts identified as fully or partially “Terminated for Convenience or Default”, or was subject to litigation regarding performance.

c. The Offeror shall provide the following contract description information for each contract and/or subcontract in the order listed below. Table format is acceptable.

i. Contract number.

ii. Title of Program/Project.

iii. Identify whether you were the Prime or Subcontractor. If you were the

Subcontractor, provide the name of the Prime Contractor to whom the effort was awarded.

iv. Contract type.

v. Period of performance.

vi. Prime Contractor Awarded price/Subcontractor Award Amount.

vii. Prime Contractor Final or projected final price/Subcontractor Final or projected final price.

viii. Prime Contractor Annual dollar value/ Subcontractor Annual dollar value.

ix. Original delivery schedule.

x. Final or projected final delivery schedule.

xi. Government or commercial contracting activity, address, telephone and e-mail address.

xii. Government or commercial contracting activity technical representative or

Contracting Officer’s Representative (COR), name, telephone number and e-mail address.

xiii. Status on referenced contract (prime or major Subcontractor).

d. Offerors without a record of relevant past performance shall clearly state that the Offeror does not have a record of relevant past performance information.

Note: The Government reserves the right to use data provided in the Offeror’s proposal and data obtained from other sources during past performance evaluation. To ensure inclusion of all references in the evaluation process, the Offeror is encouraged to provide the Government with the most current data on each reference. Please note that references provided on classified contracts cannot be verified. Also, it is recommended that Offerors limit references for performance as a first tier Subcontractor unless it cannot be avoided. In both of these cases, the Government could be limited to the amount of data available to perform the evaluation process.

5.4 VOLUME IV: Price (Factor IV): The Price Volume shall include the following information:

5.4.1 The Offeror shall submit its Price proposal in Microsoft Excel format, utilizing Microsoft Office 2013.

Spreadsheets shall be sent in a file format that includes all formulas, macro, and format information. Print image is not acceptable.

5.4.2 If proposing Subcontractors, the Offeror shall explicitly detail on its price proposal the amount of work subcontracted, in terms of both dollars and percentage.

5.4.3 The Contractor Manpower Reporting (CMR) requirements including CLINs 0005, 1004, 2004, and 3004 are not separately priced (NSP).

5.4.4 Travel and ODCs are anticipated; therefore, the Government has included NTE travel and ODC amounts as detailed in table 3 below. All Offerors shall propose the NTE travel and ODC amounts as identified in table 3 below for all identified travel and ODCs CLINs, for the Base and Option Years. The following amounts shall be utilized for evaluation purposes only in determining the total price for the entire contract.

Table 3: NTE Travel and ODC Amounts Description Base Period Option Year 1 Option Year 2 Option Year 3 Travel $100,000.00 $100,000.00 $100,000.00 $100,000.00

ODC $10,000.00 $10,000.00 $10,000.00 $10,000.00

5.4.5 Offerors are required only to price the base and option periods. Offerors shall not propose price for the potential six-month extension of services period (see FAR Clause 52.217-8). Procedures for price evaluation of the FAR 52.217-8, Option to Extend Services, are stated in paragraph 2.4.3 of Addendum to Clause 52.212-2.

5.4.6 The Price Volume shall include the following tabs:

TAB E1: Pricing Notes - This tab shall identify the Offeror’s proposed pricing and shall be submitted IAW with Attachment 4, CLIN Structure. This tab shall also be used to explain the Offeror’s Price Proposal, e.g., discounts offered, remittance address, explanation of Contractor-site and Government-site rates, not separately priced pricing data, etc.

TAB E2: Proposal Pricing Breakdown - This tab shall identify the Offeror’s proposal price for the full performance period of the requirement. The Offeror must clearly state the PWS Section, labor categories, occupation titles, proposed number of hours for each location, fully burdened labor rate for each occupation title and the total labor price. The Offeror’s total proposed price must be INCLUSIVE of the NTE Travel and ODC Government amounts reflected in Table 3 above. Attachment 5, Proposal Price Breakdown is provided as a SAMPLE.

TAB E3: Proposed Labor Categories and Hours - The Offeror shall identify labor categories, occupation titles and hours deemed necessary to successfully perform the contract. Attachment 6, Proposed Labor Categories and Hours, is provided as a SAMPLE.

Note: This Tab shall NOT include any proprietary information.

TAB E4: SCLS Labor Rates - The Offeror shall identify all proposed labor categories subject to the SCLS. When the SCLS applies, the Offeror shall cross reference the proposed labor classification with the applicable DOL Wage Determination and identify the corresponding labor category within the Wage Determination by occupation code and occupation title. The Offeror should price its proposal using the wage determination for specific location where the individual will be performing the work. The Offeror’s (and subcontractors) wage rates shall comply with the DOL Wage Rate minimum requirements for the area in which the work is to be done. The Offeror shall specify the city, state, and country in which the work will take place if other than that specified in the PWS. The Offeror is responsible for compliance with the SCLS. Attachment 7, SCLS Mapping Table, is provided as a SAMPLE.

TAB E5: Total Compensation Plan - Total Compensation Plan for Professional Employees (TCPPE). This solicitation incorporates FAR Clause 52.222-46. In its Price Proposal Volume, the Offeror shall submit a TCPPE setting forth direct labor rates and total fringe benefits proposed for labor categories identified by the Offeror as professional employees as defined by FAR 22.1102.

The TCPPE shall demonstrate the Offeror’s clear understanding of the work to be performed. The Offeror’s TCPPE shall indicate the capability of the proposed compensation structure to obtain and keep qualified personnel to meet mission objectives and provide uninterrupted high-quality work. The Offeror’s TCPPE shall address recruitment and retention, realism, and its consistency with a total plan for compensation. The Offeror’s TCPPE shall describe how the proposed salary rates for professional employees account for differences in skill, complexity of various disciplines, and professional job difficulty. The Offeror’s TCPPE shall include supporting information, such as national and regional compensation surveys and studies of professional, public and private organization used in establishing the total compensation structure Incumbent contractors shall submit information pertaining to the salaries and fringe benefits paid to incumbent contractor personnel who are currently performing, or have performed in the three (3) years prior to the date set for submission of proposals, in labor categories, or labor categories equivalent to, those identified by the offeror as professional employees. Attachment 8, Employee Total Compensation Plan, is provided as a SAMPLE. Professional Employee" is defined in FAR 22.1102 and may not apply to all labor categories. If applicable, the professional employee compensation plan must be submitted in addition to Attachment 6.

(END TO ADDENDUM 52.212-1)

ATTACHMENTS & EXHIBITS

PERFORMANCE WORK STATEMENT (PWS)

For

LIFELONG LEARNING CENTER (LLC) CONTRACTOR TECHNICAL SUPPORT

COMBINED ARMS CENTER-TRAINING

ARMY TRAINING SUPPORT CENTER

FORT EUSTIS, VA 23604

PART 1

GENERAL INFORMATION

1.0 General: This is a non-personal services contract to provide US Army Training and Doctrine Command (TRADOC) Proponent-Lifelong Learning Center (LLC) Technical Support for the LLC Program. The purpose of the LLC Program is to provide lifelong learning capability at TRADOC schools. Lifelong learning gives TRADOC the ability to create a training and education environment that takes advantage of major developments in information technologies and training and education methodologies. It provides the ability to support a force in transformation by providing relevant, standardized training and education, on demand, to the right Soldier, leader, or unit, at the teachable moment, regardless of location. The LLCs specifically address that portion of TRADOC’s mission to train and educate the Army’s Soldiers; develop leaders; and support training in units. Key in the development of the lifelong learning process is ensuring the process is user-friendly. All players associated with the mission to train and educate the force will improve their ability to perform their jobs and more importantly, the Soldier and leader will benefit from a process that allows them to learn, grow, and achieve in their profession throughout their career, wherever they serve.

1.0.1 The LLC is the technical hub of the lifelong learning process and is essential for all lifelong learning development. It is the community of interest for the proponent. The LLC is the portal for all Soldiers/leaders to access their proponent training and education content. The LLC provides training and education content, courses and courseware, collaboration, information, discussions, all related to the professional needs of the user. The LLC has a student management function to monitor, manage, and provide relevant training content to a Soldier throughout their career. The LLC has a digital library for creation, storage and delivery of all standardized proponent training and education content, and has a human element with support available 24 hours/7 days a week via the Army Training Help Desk. LLC Technical support is currently provided at the following locations: Ft.

Eustis, VA; Ft. Gordon, GA; Ft. Leavenworth, KS; Ft. Leonard Wood, MO; the Judge Advocate General Legal Center and School (TJAGLCS), Charlottesville, VA; the Warrant Officer Career College (WOCC), Ft. Rucker, AL;

and the United States Army Sergeants Major Academy (USASMA), Ft. Bliss, TX, with the Contractor Program Manager on-site at the Ft. Eustis location.

1.0.2 The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, supervision, and other items necessary to perform TRADOC Proponent-LLC Technical Support as outlined in this Performance Work Statement (PWS) except for those items specified as government furnished property and services.

1.2 Background: The initial execution of lifelong learning in the Army was done at the Army Signal School at Fort Gordon, GA. A year-long study was conducted for Ft. Gordon in 2001 to examine current training and education methodologies and proposed a plan to take their training mission into the future. The result was a plan created in July 2001 titled “The University of Information Technology and Digital Training Master Plan”. The plan was the birth of the lifelong learning process. The LLC program was extended to Ft. Leavenworth, KS and Ft. Leonard Wood, MO in 2006. The enterprise LLC was established at Ft. Eustis, VA in 2007.

1.2.1 It is TRADOC’s methodology of providing training and education along with the opportunity to acquire the skills, knowledge, and attributes needed to perform the missions of the Army’s Future Forces. The four established LLCs (Forts Eustis, Gordon, Leonard Wood, & Leavenworth) and three separate locations at TJAGLCS in Charlottesville, VA, WOCC at Ft. Rucker, AL, and USASMA at Ft. Bliss, TX currently have more than 299,000 resident and non-resident registered users annually using the Learning Content Management System (LCMS) (Blackboard Learn™) capability on the .mil (NIPR), .smil (SIPR), and commercial (.com) networks.

1.3 Objectives: The contractor shall maintain Web Portal capability, Support Desk and Digital Library functionality, Student Management (database) and Extension Campus support capability, and LCMS (Blackboard Learn™) capabilities that facilitate the sustainment of the LLCs on all three networks - .mil, .smil, and .com. The LLCs will provide community of interest training support for students. The LLCs LCMS is accessible to students in all three environments (.mil, smil, and .com) on a 24-hour basis as classrooms without walls, making training content accessible on demand to Soldiers in every theater of operations. The LLCs LCMS will provide commanders in the field with Extension Campus capability, enabling them to bring training content to it, in the environment in which that training is crucial, diminishing the need to send Soldiers to the resident school.

1.4 Scope: The TRADOC Capability Manager (TCM) for Army Training Information System (ATIS) is responsible for maintaining standardized LLC capabilities for both TRADOC and non-TRADOC schools. The Combined Arms Center-Training (CAC-T), Fort Leavenworth, KS, has designated the US Army Training Support Center (ATSC) at Fort Eustis, VA to serve as the Program Manager (PM) for this effort. LLCs expand/enhance each proponent school with an “always–on” 365/24/7 capability. The LLC infrastructure leverages cutting-edge technologies and are adaptable to future technology evolutions focused on improving the lifelong learning concept such as injecting load balancing solutions, updating authentication methods, using content caching solutions The contractor shall provide support services for four (4) LLCs and three (3) separate operating locations; however, the requirement may evolve into more or less locations and work effort dependent upon DoD future needs.

1.4.1 This strategy uses a Firm Fixed Price (FFP) contract platform, encompassing the four LLCs and other supported training detachments, becoming effective on or about 12 August 2020. The current requirement may expand or contract dependent upon Army requirements and or budgetary constraints.

1.4.2 In accordance with Department of the Army lifelong learning strategy and pursuant to TRADOC guidance, the LLC’s support capabilities shall be maintained at Fort Eustis, VA; Ft. Gordon, GA; Ft. Leavenworth, KS; Ft.

Leonard Wood, MO; TJAGLCS, Charlottesville, VA; the WOCC, Ft. Rucker, AL; and the USASMA, Ft. Bliss, TX.

The scope of this order applies to personnel required to establish, operate, and maintain LLC capability at each location.

1.5 General Information

1.5.1 Deliverables: A Contract Deliverable Requirements List (CDRL) is included in the contract. Typical CDRL items are monthly status reports, trip reports, in-progress reviews, lessons learned reports, etc. Unless otherwise indicated, monthly reports shall be submitted to the Contracting Officer’s Representative (COR) in the mutually agreed upon Microsoft office product format by no later than ten (10) Working Days after the end of each month.

The contractor shall create or maintain the following documents for each location.

1.5.1.1 System Architecture Document: The contractor shall update and maintain the document. The LLC system architecture document shall identify the servers associated with the system and its interdependency with other systems such as Enterprise Authentication Management System - Army (EAMS-A) and the Army Training Resources and Requirements System (ATRRS). This documentation shall include server topology and configuration documents as required, clearly articulating what services are being hosted. The System Architecture Document report shall include system information sheets and be submitted to the COR five (5) working days after changes occur.

1.5.1.2 Continuity of Operations Document: The contractor shall be required to maintain a job book articulating operations and maintenance processes and procedures. This document includes but is not limited to system and content battle drills. This continuity document serves as the document to clarify how to operate and sustain the evolving environment in accordance with best practices and experiences. The contractor shall maintain an Operational Journal to serve as a permanent record for summarizing the system architecture changes to include patches applied and system incident reports. The Continuity of Operations Document shall be submitted to COR thirty (30) working days after contract award and subsequently five (5) working days after changes occur, unless circumstance dictates otherwise.

1.5.1.3 System Metrics: The contractor shall define, collect, and analyze metrics to be used as a measurement of the usefulness and effectiveness of the system to include: number of distinct logons per day and module accessed. This information will be used to determine the effectiveness of the module/component and will be the basis to reallocate resources/depreciate a module/application that is not being utilized. This report shall be produced every month and shall be submitted as part of the monthly progress reports. This shall include working with the Army Training Help Desk (ATHD) and schools to assess system usage to advise TRADOC to prioritize/consolidate resources/capabilities based upon facts.

1.5.1.4 System Accreditation: The contractor shall monitor system accreditation packets and risk assessments conducted or reviewed, including tracking accreditation renewals, etc. The contractor shall be responsible for creating, monitoring, and updating system accreditation packets that may include but are not limited to the following: operational process documents, Whitelist documentation, Security Technology Implementation Guide (STIG) execution, documentation, and Plan of Action and Milestones (POAM) for any STIGs that cannot be implemented, addressing the results of Information Assurance Vulnerability Alert (IAVA) scans, generating Certificate of Networthiness (CON) documentation for system software as needed, and any documentation required to support the Risk Management Framework (RMF) accreditation process for network Authority to Operate (ATO).

The contractor shall maintain access to reporting systems. The System Accreditation report shall include all applicable information and shall be submitted to the COR monthly.

1.5.1.5 Monthly Progress Reports: Progress reports shall be provided to COR. The monthly progress report includes enterprise-level system metrics, tasks accomplished, problems/solutions, training provided, projected travel, personnel gains/losses, and tasks to be accomplished during the next reporting period. Subject Matter Expert (SME) critiques shall be attached to the progress report as required by the COR.

1.5.1.6 Process Documentation: The contractor shall document the procedures and processes to deliver approved services. These process documents shall provide the “how to” for system administrators to manage the technology and for customer support personnel to respond to customer requests for services, etc. The Process Documentation procedures shall be submitted to the COR within thirty (30) calendar days after contract award and subsequently within five (5) calendar days after changes occur.

1.5.1.7 Delivery Provisions: All deliverables produced as a result of work performed in response to this PWS and any correspondence shall be provided to the COR or an authorized alternate Point of Contact (POC).

1.5.1.8 Contractor performance shall be reviewed by the designated COR on a routine basis and as indicated in the Quality Assurance Surveillance Plan (QASP).

1.5.1.9 Written Reports: The contractor shall provide the following reports to the COR. Complete and accurate records of all work shall be maintained by the Contractor to ensure accurate data is used to develop reports. All records are subject to review/audit by the COR. The Contractor shall provide all necessary assistance in such review/audit at no additional cost to the Government. Documents and reports shall be delivered in electronic format, at a minimum, and in hard copy when requested in the CDRL(s). The documents shall be free from locks or protections that would prevent (or inhibit) text being copied or edited by the Government after delivery.

ITEM DATA NUMBER DUE DATE

Monthly Progress Report (MPR) CDRL A001 10 Working Days after each end of month

In-Progress Review AARs CDRL A002 5 Working Days following the

IPR

Continuity of Operations Document CDRL A003 30 Working Days after contract award and subsequently 5 working days after changes occur

System Architecture Views CDRL A004 30 Working Days after changes occur

Application Configuration Documentation

CDRL A005 30 Working Days after changes occur

Government Furnished Property (GFP) Report

CDRL A006 Annually NLT 31 October

1.5.2. Reserved.

1.5.3 Quality Control: The contractor shall submit a complete Quality Control Plan (QCP) to the COR within fifteen (15) working days after contract award. The QCP shall be implemented on the contract start date. Changes to the QCP shall be submitted to the COR for approval not less than seven (7) working days prior to the effective date of change. The Government will make a final review and acceptance of the QCP and any subsequent changes.

The basic tenet of this plan is that the Contractor is responsible for quality. The contractor’s QCP shall:

1.5.3.1 Be a comprehensive plan to deliver quality services to the Government.

1.5.3.2 Describe a method acceptable to the Government, for identifying deficiencies in quality of service performed under this contract, before the level of performance becomes unacceptable. The QCP shall also describe the process for corrective actions, without relying on Government direction.

1.5.3.3 Include a customer feedback system to immediately notify the Government of validated complaints and corrective action taken. As a minimum, the customer complaint system shall contain: 1) procedures for the customer to file complaints with the Contractor, 2) forms for customer use, 3) procedures for investigation of complaints, and 4) methods of feedback to the customer and the COR. Feedback shall consist of corrective actions taken with results, and shall be compatible with the reporting and communication systems of the QCP.

1.5.4 Reserved.

1.5.5 Reserved.

1.5.6. The Contractor is not required to perform services on Federal holidays listed below or established by Federal Statute or Executive Order, unless an exception is specified in an individual Task Order. If a holiday falls on a Saturday, it is observed on Friday; if the holiday falls on a Sunday, it is observed on Monday.

New Year’s Day 1st day of January Martin Luther King Jr.'s Birthday 3rd Monday of January Presidents Day 3rd Monday of February Memorial Day Last Monday of May Independence Day 4th day of July Labor Day 1st Monday of September Columbus Day 2nd…