ESS VII RFP Amendment 01.pdf

N6893620R0120

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 06-Jun-2022 11:00 AM to 16-Jun-2022 11:00 AM.

The following have been added by full text:

AMENDMENT QUESTIONS AND ANSWER

Engineering Support Services (ESS) VII RFP Questions

RFP

Section No.

RFP Sub - Section/Page No.

Question Government Response

1 Section L 3.0

Part A, Page

For Volume 1 Technical, will the government consider allocating equal page count to the Sample Task and Management OR allow flexibility on the individual page count to meet the 70-page combined limit for the Technical volume?

The Government has revised the page count for Volume 1 Technical to 75 pages. The vendor may not use unused pages from one section as excess pages for another section.

2 Section L 3.0

Part B, 1.1

The proposed LCATs in the Sample Task Estimate Attachment L-2 do not exist in the RFP LCATs in attachment L-6. Will the government allow the offeror to map the sample task LCATs to the RFP LCATs?

Attachment L-2 has been updated to -6.

3 SOW

Section 3.4

Please clarify the required education and experience for all LCATs and levels, including the SME and the WD LCATs. For example, the SME levels do not indicate the required education/degree. Also, the WD LCATs do not indicate the required years of experience or education requirements. Please advise.

Attachment 1, SOW Section 3.4.2 Levels of Experience details the education and experience requirements for all LCAT levels.

WD LCAT requirements are detailed in Section 3.4.8 and do not have educational requirements. These are expected to properly classify their employees based on experience, salary, and level requirements as specified in the SCA Directory of Occupations.

4 Attachment L-5

The L-5 attachment provided includes a tab for fully burdened labor rates. Will the Government please consider

The Government has removed the Fully Burdened CPFF Labor Rates tab from Attachment L-5.

removing the requirement for the L-6 as it is duplicate information?

5 Attachment L-5

The L-5 attachment provided is in a format CA-1 that we have previously seen used, but normally a format CA-2 is provided for the subcontractor submissions.

Will the Government please provide the CA-2 spreadsheet for subcontractor use or provide instructions for the format to be used for subcontractor submissions?

Attachment L-5 Cost Summary Spreadsheet is provided for prime and subcontractor submissions. The prime is required to populate a roll up of the cost data including anysubcontractor cost into Attachment L-5. Each subcontractor is required to populate the subcontractor cost data into a separateAttachment L-5.

Attachment L-5 Cost Summary Spreadsheet was mislabeled in the document as Attachment _CA- 1_CLIN_Breakout_Spreadsheet.

Revised to Attachment L-5.

6 Section L, Section 3.0

Section 3.5 Technical Sample Task

The instructions for the sample task pricing indicate

2021 direct/indirect rates as response to Attachment L- However, the instructions for Attachment L-5 do not indicate that offerors are required to use 2021 direct/indirect rates. Can the Government please clarify?

The Government has revised Section L, 3.5 Technical as follows, 7 Are Acronym Tables permitted and excluded from page count.

Acronym Tables are included in the

8 Please confirm due date.

SAM has both June 6th and June 7th.

Please see RFP amendment extending the deadline for proposal submission.

Engineering Support Services (ESS) VII RFP Questions

RFP

Section No.

RFP Sub - Section/Page No.

Question Government Response

9 RFP Section L 3.0, page 57

Question:

To level-set proposals and ensure all offerors are submitting the same amount of data within the page allocations, will the Government consider providing formatting guidelines?

The Government has added formatting language to Section L 3.0.

We suggest the following language:

Proposals should be formatted using a Times New Roman 11 pt.

normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for/printed on standard

8.5 x 11 inch paper. If Government attachments have a different format/font, the Offeror may use the format/font in the attachment as provided. All pages should be numbered with volume and page numbers. If the Offeror uses graphs to convey information, the graphs must show enough detail to easily discern the information described.

Graphs and tables should be presented in no smaller than a 10

pt. font. Text utilized in charts, figures, and graphics should also be no smaller than a 10 pt. font and may use a font type selected by the Offeror.

Issue:

Section L does not specify any formatting guidelines, including minimum font for narrative and tables/graphs nor does it address page size or margin requirements.

As the RFP is currently written, offerors could submit the entire proposal in a very small font (e.g., 8

pt. TNR) and excessively use 11 by 17s to maximize the page limits.

This could result in wildly varying submittals across offerors.

10 RFP Section L 3.0, page 57

Question:

Will the Government consider adding additional page count or alternatively exclude the Transition- In and Transition-Out Plans out of page count?

Issue:

The Management subfactor page limit is 25 pages; however, Section L requires offerors to discuss numerous topics, including detailed management approach, staffing, subcontract management, and transition. It would be very difficult for an offeror to adequately

The Government has determined the page count for this section to be sufficient.

describe their approaches to these areas within the 25 pages.

Section No.

RFP Sub - Section/Page No.

Question Government Response

11 RFP Section L 3.0, page 57

Question:

Will the Government confirm that the Technical volume total is 75 pages and not 70 pages?

Issue:

Section L states 70 pages for the Technical volume; however, it then lists 50 pages for Sample Task and 25 for Management.

The Government confirms the technical volume total page count has been adjusted to 75 pages.

12 RFP Section L 3.0, page 57

Question:

Will the Government confirm the entire Key Personnel section is out of page count and does not only apply to the resumes?

Issue:

Section L states that there is no page limit for the Key Personnel Section of Technical. Our understanding is that this includes a summary and rationale for selection of our Key Personnel team as well as their resumes.

page limit. The Offeror has the opportunity to provide a summary and rationale in Section L, 1.3, para (3), which counts against the page limit.

13 RFP Section L 3.0, page 57

Question:

Will the Government consider adding 2 pages dedicated to an Introduction/ Executive Summary?

Issue:

The Government prescribes page counts per section within the Technical Volume, which leaves no space for a volume introduction or Executive Summary.

The Government has determined the page count to be sufficient.

Any introduction/executive summary is considered part of the total page count already identified.

14 RFP Section L Part B L.

1.3.a.3, page 60-61

Question:

We believe that this is an incumbent friendly RFP requirement and respectfully request that the requirement to provide these specific details for list below is provided as an example of functions historically the actual proposed indirect staff be deleted from the RFP.

Issue:

Offerors shall provide the employee location, education, years of experience, and description of work experience for each individual proposed in their management strategy for contract support functions requirement, the Government is the contractor must have identified candidates available to provide their individual and description of work ption of the incumbent team, no other offeror will have these specific personnel identified and in place, and therefore able to provide the requested data.

staff already performing these functions (Finance, Contracts, HR, encouraged to propose in accordance with their business are not required positions, with the exception of Key Personnel.

Section No.

RFP Sub - Section/Page No.

Question Government Response

15 RFP /

CDRLs, A003

Section L, Part B, 1.3(d), page 62 (A003 page 3)

Question:

Would the Government please clarify if Transition Out Plan is due with initial proposal?

Issue:

The final RFP requires the inclusion of a Transition Out Plan within the Management section of the Technical Volume; however, CDRL A003 requires a Transition-Out Plan is not due until 90 days prior to completion of contract.

Per Section L Part B, 1.3(d); the Transition Out Plan is a separate document from the Phase Out Transition Plan (CDRL A003).

The Transition Out Plan is due with the proposal and will be used as part of the technical evaluation.

16 RFP Section L,

2.1. page 64

Question:

In order to allow for more relevant PP information, will the Government consider excluding the Consent Letters from the page count?

Issue:

RFP The Offeror shall submit written consent from its

The Government will not include the subcontractor consent letters as part of the Past Performance principal subcontractor(s) and JV team member(s) that will allow the Government to coordinate any past performance issues directly with the Offeror

17 RFP Section L,

3.4 page 67 and 3.3(e)

Question:

Please clarify if the Total Compensation Plan in 3.4 should be provided for both Professional and SCA WD employees.

Issue:

3.4 states that a Total Compensation Plan is to be for each proposed professional employee 3.3(e) indicates that Total Compensation Plan is to be provided for SCA WD employees as well.

The Government intends to evaluate the total compensation plan for both categories of employees.

Section No.

RFP Sub - Section/Page No.

Question Government Response

18 RFP Sectoin L,

3.6.2 page 68-69, and Attachment L-2

Question:

Please provide the correlation of the labor categories in L-2 with those contained within 3.6.2 and L-5.

Issue:

Each of the three labor categories provided in L-2 (Engineer Scientist Senior, Engineering Technician Senior, and Administrative Associate) do not correlate directly to the nomenclature used in the table on page 3.6.2 and the L-5.

Please refer to the answer to question 2 above.

19 SOW

Section C, 3.1.2.1, page

Section L,

3.6.2 page 68-69, and Attachment L-5

Question:

To ensure consistent pricing by all offerors, please provide:

a. A detailed breakout of the labor categories and hours to be proposed for both China Lake and Point Mugu locations.

b. For the China Lake WD positions, please provide a detailed breakout of

For proposal purposes, offerors shall only use the Kern County WD rate tables.

applicable for the locations where labor is performed.

During performance the Section B Composite Rate Table will be used to estimate ceiling at the order level.

the positions applicable to the San Bernardino WD and those for the Kern County WD.

c. Please provide a detailed breakout of the labor categories and hours to be proposed for both Government and Contractor sites.

Issue:

3.1.2.1 of the SOW states, Approximately 94 percent of work will be performed at Government site and 6 percent of work to be performed at Contractor site.

Government site(s) include China Lake, CA and Point Mugu, CA. The breakout of work between China Lake and Point Mugu is estimated at 70% and 30%, respectively hours table in Section L pg. 69 and L- 5 workbook do not provide any details on which positions and hours should be proposed at China Lake and which should be proposed at Point Mugu. It also does not provide any detail on which positions to propose as Government site or Contractor site.

20 RFP Section M, 2.0, page 75

Question:

Does each contract have to meet a minimum of $12M every year of the contract or can an average $12M annually over the life of contract be acceptable? Given the nature of IDIQ/TO contracts, the value could fluctuate with one year being $10M and the following year reaching $14M. Please clarify.

Issue:

The Past Performance evaluation criteria that Magnitude is based on contracts with $12M value in a single year and/or $60M over five years.

As long as the contract has one year valued at $12M or greater, then the contract meets the Magnitude for the Total Contract Dollar Value threshold.

The Government has revised the Description of Work for the Total Contract Dollar Value under Magnitude to the following:

Section No.

RFP Sub - Section/Page No.

Question Government Response

21 RFP Section M, Part B, M.2.0, page

Question:

1) Please clarify that a contract with a CBA is equivalent to a WD contract in evaluating relevancy of

For the purpose of evaluating relevancy of an offerors past

2) Please clarify that a CBA with multiple locations is equivalent to multiple WDs in evaluating performance.

Issue:

PP evaluation table states minimum of two wage of Labor (DOL) WDs are issued based on geographical area (counties) where the contract work is performed. DOL has stated that Collective Bargaining Agreements (CBA) replace WDs where unions and employers have negotiated them. A CBA, which covers SCLS employees, can cover multiple work locations within the same contract consisting of several counties and even cross state lines and end up replacing multiple WDs with just one CBA.

r single and multiple locations.

22 RFP Section M Part B M.2.0, Question:

Recommend the Government please remove, this competition restricting requirement or include wording to increase competition of the contract.

Issue:

In the Relevancy table under Total Contract Dollar Value the RFP draft RFP included additional verbiage that was removed in the

The Government will place special attention to the value of contracts an Offeror has experience in managing, whether the value is from a single contract or an aggregate of contracts SDVOSB contract, this last minute change in the requirement highly favors the incumbent as there are very few or limited number of SDVOSB companies that have relevant engineering contracts to meet this $60M single contract value requirement and would likely

The language in this section has been updated to reflect result in bidders making a no-bid decision

Section No.

RFP Sub - Section/Page No.

Question Government Response

23 RFP Section M Part B M.2.0, Question:

Would the Government please confirm that a contract bridge may be included with the base contract in a past performance citation to requirement?

Issue:

In the Relevancy table under Total Contract Dollar Value the five years

The Government will not include a bridge contract with the base contract, as a bridge is a new separate contract. As they are separate contracts they will be evaluated separately for meeting the threshold requirement.

24 Attachment L-2

Direct Labor Table, page

There is an asterisk next to the labor category, Engineering Technician Senior in the table.

What is the asterisk for? There is no legend or footnotes to indicate what that stands for.

The Government has removed the asterisk and revised the labor categories in Attachment L-2..

25 Attachment L-3

PP

Information Form

Question:

Please clarify if the conversion of Attachment L-3 to MS Word format is allowed to give a proper Contract Effort Description narrative.

Issue:

Section M, 2.0 Past Performance, second aspect of performance evaluation (Relevancy). This

The Government will use the following aspects to determine relevancy for this

Scope, Complexity, and Magnitude. Our assumption is to include this in the Contract Effort Description field. However, this is a fillable field with scrolling text.

Only eight lines are visible at a time. This is a very difficult format to use either for offerors to write

The Government has determined that Attachment L- 3 shall be submitted in PDF form.

their responses or for Government reviewers reading those responses.

Section No.

RFP Sub - Section/Page No.

Question Government Response

26 Attachment L-3

PP

Information Form

Question:

Please clarify where in Volume 2 PP, offerors should provide items 1 through 5 of the overall quality section. As provided, page two of Attachment L-3 PPIF only addresses item 6, the demonstrated systemic improvement actions taken to resolve past problems.

Issue:

Section M, 2.0 Past Performance, third aspect of performance evaluation (Overall Quality). This

Offeror, principal subcontractors, and JV team members performance and focus its evaluation on the following areas:

1) meeting technical requirements, i.e., the quality of technical performance; 2) meeting schedule requirements, e.g., on time or late delivery; 3) controlling contract cost; 4) managing the contracted effort; 5) regulatory compliance, and 6) the demonstrated systemic improvement actions taken to

Attachment L-3 has two areas to address; Contract Effort Description and Demonstrated Systemic Improvement Information. Section L or Attachment L-3 do not address where Quality items 1 through 4 must be located within the Past Performance volume.

Offerors are to address items 1 through 6 in the Demonstrated Systematic Improvement Information Section of Attachment L-3 PPIF.

27 Page 28 Section I includes DFAR clause

252.204-7021 (pg 28) Contractor Compliance with the Cybersecurity Maturity Model Certification Level Requirement.

Per the DOD CIO, the CMMC certification requirements have been suspended until further DOD delegation. There are currently no DIB contractors externally assessed by a third party C3PAO;

therefore, it is very unlikely that any contractors bidding this RFP will be able to achieve an external third party certification by contract award. At this time, teams can be qualified through self-certification up through NIST requirements.

Request that self-certification through NIST requirements is acceptable at award and that the clause be removed.

DFAR clause 252.204-7021 from the RFP. Contractors are allowed to self certify under

DFARS 252.204-7012.

28 Page 57 Section L Part A 3.0 , in the table of authorized Annexes (pg 57) The Volume 1 total page count is 70 pages, however the Technical Sample Task plus Management volume page limits total 75 pages.

Can the government please confirm that the total page count for volume is 75 pages?

The Government has updated the table to reflect 75 pages.

Section No.

RFP Sub - Section/Page No.

Question Government Response

29 Page 68

Section L Part B 3.6.2 (pg 68) the Offeror shall propose the labor categories/hours as outlined specifics the LCATs and hours which total 1,103,050. However, in Section 1.3 part b paragraph (3) deviate from the Government estimated labor mix, the Offeror shall provide, justification/rationale for the variance that addresses mix and related technical

Any deviation from the labor requirements in Section L Part B 3.6.2, shall provide justification/rationale for the variance as detailed in Section

1.3 Part B Paragraph (3).

approach should be considered suitable to ensure successful performance of tasking

Can the government please confirm that all offerors are required to propose the LCATs and hours as defined in the solicitation and not deviate?

30 Page 69

Section L Part B 3.6.2 Table (pg 69). The LCAT Engineering Technician IV does not have an asterisk beside it although it does have an SCA code next to it.

Can the government please clarify if this position is wage-determined?

Asterisk has been added to LCAT Engineering Technician

IV.

31 SOW Page 27 Statement of Work 3.4.8 provides functional requirements for Drafter/CAD Operator II (SCA- 30062), however Attachment L-5 does not include any LCAT entries for Drafter/CAD Operator II (SCA- 30062) there are no hours assigned in the LOE matrix.

Can the government govern whether or not the Drafter/CAD Operator II (SCA-30062) is to be included in the offerors priced proposal?

the Drafter/CAD Operator II from the SOW.

32 Section L Part B 3.6.1 (pg 68) provides an ODC table with Materials estimated number as $6,280,990 and the Travel as $4,623,476. That number is inconsistent with the amounts by year in Attachment L-5, where materials total is $5,699,111 and the travel total is $ 4,321,006.

Could the government provide a table in Section L clarifying the correct amounts before burdens for each year of the POP for the ODCs plug numbers for travel and material?

The Government has updated Attachment L-5 to match the

RFP.

33 How does the government plan to evaluate the cost based on original award value of $87M knowing the contract was increased to $99M?

The Government is not evaluating the proposals based on the cost of any other contract.

34 Would the Government kindly consider a page increase to 30 pages for the Past Performance volume.

The Governments has determined the Past Performance Volume page count to be sufficient.

SECTION I - CONTRACT CLAUSES

The following have been deleted:

252.204-7021 Contractor Compliance with the Cybersecurity Maturity

Model Certification Level Requirement

NOV 2020

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

GENERAL INSTRUCTIONS

L 1 CONTENT OF PROPOSALS (SERVICES)

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

The Offeror must respond to all requirements of the solicitation and not alter or rearrange the solicitation. The Offeror is advised that the Government may incorporate contract.

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization shall be emphasized during proposal preparation. Statements that the prospective Offeror understands, can comply with, or will comply with, the specifications, and paraphrasing the requirements or parts thereof without supporting information are considered inadequate by the Government, and may result in assessing weaknesses and/or deficiencies.

The Offeror must include any data that illustrates the adequacy of the various assumptions, approaches, and solutions to problems. Failure to address a specific factor clearly may be considered a deficiency. Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and effective proposal is neither necessary nor desired.

The Government advises the Offeror that taking exception to or deviating from any term or condition of the RFP may result in the assessment of a deficiency to the proposal.

Limitation on Subcontracting and Notice of Service-Disabled Veteran-Owned Small Business Set-Aside in accordance with FAR 52.219-14 and FAR 52.219-27 respectively, or who provides at least 20% of proposed total sponding to this solicitation.

2.0 ELECTRONIC PROPOSAL FORMAT

This section is intended to provide information to the Offerors on the format and application software to be used for submitting proposals. Use of the software and procedures described in this section will reduce the amount of time and effort needed to receive and upload proposals and will ensure the proposals received are suitable for reading electronically during evaluation.

Proposals must be formatted using a Times New Roman 12 pt Normal font (no reduction permitted), single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. All pages should be numbered with section and page numbers. Graphs and tables shall be presented in no smaller than a 10 pt font and should contain a grid, which allows values to be read directly from the graph. Graphs and page will be counted as one page. Drawing may be of any size and will count as one page. Graphic resolution, including such data as tables or charts, should be consistent with the purpose of the data presented. When using Government supplied templates (e.g. Attachment P3, Attachment P6, Attachment P7), no modifications to font or scaling required. All proposal documents must be compatible with the Microsoft Office 2016 and/or the latest Adobe Acrobat Reader Portable Document Format (PDF), where applicable.

The offeror shall submit all volumes of its proposal electronically via DoD Safe (https://safe.apps.mil/). An email shall be submitted to Chris Bachman at christopher.p.bachman2.civ@us.navy.mil no later than 12:00 PM PST ten must specify a point of contact name and email address for the Prime contractor and for each individual allow them to submit proposal documents to the Government independently as needed. The Prime and Subcontra -than three (3) days prior to the proposal due date. This code authorizes access to submit proposal documents securely via DoD SAFE. Each submission package in DoD SAFE is limited to 25 documents totaling 8 GB. If a

-Off Request

The Offeror shall send an e-mail to Chris Bachman at christopher.p.bachman2.civ@us.navy.mil immediately after submittal of proposal electronically to DoD SAFE to document time of delivery.

The Offeror is responsible for ensuring electronic proposals are virus free. Offerors may use hyperlinks within and among proposal volumes that do not include price information. However, there shall be no links from any other volume into the Price Volume or into any other portion of the proposal that contains price information. In order to reduce file sizes, the Offeror shall not embed sound or video (e.g., MPEG) files within the proposal submission. The Offeror is encouraged to simplify the color palette used in creating figures; and minimize size of graphics files; and avoid scanned images.

3.0 PROPOSAL CONTENT AND VOLUMES

The Offeror must present proposal information in a manner that facilitates a one-to-one comparison between the information presented and this Proposal Instruction. Proposal information must be structured such that its r tier subparagraphs. The Offeror must provide reasons it will not provide information for a particular paragraph. The proposal information instructions are structured by paragraph numbers where first, second, third, and fourth parts correspond to the vo

Each volume of the proposal shall be submitted as specified in the table below. The table below supersedes the copies requested in Block 9 of the Standard Form (SF) 33. All volumes of the proposal shall be received electronically via DoD SAFE, prior to the closing date/time stated in this solicitation. Page limitations for each volume, if any, are also specified in the table below; title and table of contents pages do not count towards the page limit. Any pages submitted exceeding the page limit shall be disregarded and NOT evaluated.

Information submitted as an Annex to the proposal includes manuals, specifications, plans, procedures, and policies that exist as an official document of the company or facility, as well as other information requested in Part B Specific Instructions. Page limitations for Annexes, if any, are specified below. The authorized Annexes are summarized in the table below.

Volume Number Volume Title Page Limit (Electronic) Copies Required 1 TECHNICAL 75 Pages 1 Original

1.1 Technical Sample Task 50 Pages

1.2 Key Personnel No Page Limit

1.3 Management 25 Pages

2 PAST PERFORMANCE 20 Pages 1 Original 3 PRICE/COST No Page Limit 1 Original Annex # 1 Statements of Work

(SOW)/Performance Work Statements (PWS)

No Page Limit 1 Original

Each volume shall contain the following information:

-Cover and title page -Title of proposal and proposal number as applicable -RFP number -Proposal volume number

-Table of Contents (The table of contents must provide sufficient detail to enable easy location of important elements)

The Offeror shall submit a Cross Reference Matrix (CRM) for the Technical Volume, similar to the example below, to help ensure that all solicitat proposal. The CRM should be a single integrated matrix and cross-reference the proposal volumes and paragraphs to specific RFP requirements, as well as other parts of CRM may be identical to the example below or revised such as to add columns to indicate the page number on which information may be found, identify where other relevant information in the proposal is located, or provide other comments. The CRM does not count against any of the proposal page limitations.

EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)

Section L Proposal Instructions

Government

SOW/PWS

Section M Evaluation Factor Reference

CLIN

Reference

Volume 1 Technical

Example: Para 3.1 Note: This column shall address all paragraphs in Sections xx and xy of the

SOW/PWS.

2.A Proposal Volume I Technical. Example: Refer to appropriate page number in

The following is a list of Section L Attachments that the Offeror shall utilize to provide information for this solicitation:

Attachment L-1 Technical Sample Task Attachment L-2 Technical Sample Task Estimate Attachment L-3 Past Performance Information Form Attachment L-4 Past Performance Assessment Questionnaire (CPAQ) Attachment L-5 Cost Summary Spreadsheet Attachment L-6 Fully Burdened Labor Rates Spreadsheet

4.0 ELECTRONIC PROPOSAL SUBMISSION:

The Offeror shall submit all proposal documents electronically via DoD SAFE (https://safe.apps.mil/) in accordance with Section L, Part A, paragraph 2.0. It is requested that Volume 2 Past Performance information be submitted by the submission date specified in Block 9 of the SF 33 of the RFP.

5.0 CLASSIFIED DATA

All proposals must be UNCLASSIFIED.

6.0 SOLICITATION CHANGES

For notice of any changes and additional information provided by the Government for the solicitation, please go to https://www.beta.sam.gov.

PART B SPECIFIC INSTRUCTIONS

Cost or pricing information shall only appear in the Price/Cost volume.

1.0 VOLUME 1: TECHNICAL

The Offeror shall provide all information and data required to conduct a thorough and complete technical evaluation.

Throughout the Technical Volume the Offeror should identify any proposed capability, approach, or feature that reduces risk inherent in the program. The Offeror shall address the following in the proposal:

1.1 Technical Sample Task

1.2 Key Personnel

1.3 Management

1.1 Technical Sample Task

The Offeror shall provide all information as instructed in paragraph 1.1.1, in accordance with Attachment L-1 Technical Sample Task. The Level of Effort (LOE), Attachment L-2, includes the Government's estimate of labor hours, labor mix, and ODC's. The Offeror shall complete Attachment L-2 by providing proposed direct and indirect rates in accordance with instructions at Section L-1, Part B, Volume 3, paragraph 3.5 of this solicitation. Do NOT include cost in this volume.

1.1.1 -1, Technical Sample Task, shall include the following information and outline below:

Team Attachment L-1 has identified the Technical Personnel believed necessary to perform the requirements. The Offeror shall identify any additional contractor team members that need to participate in the effort, and if applicable, describe the roles and responsibilities of any subcontractors, and/or JV team members required to perform the work. The Offeror shall also state if they agree, or disagree, with the proposed personnel and shall provide the basis of, or rationale behind, their position.

Assumptions The Offeror shall detail all assumptions (as applicable) relative to the sample task and the technical approach to ensure full understanding of response by the Government.

Technical Approach The Offeror shall provide a detailed description of the technical approach including a step-by-step procedures and methodologies which would be used in accomplishing the task.

Performance Risk Analysis The Offeror shall identify contingent events inherent to the nature of the effort that could, if they were to occur, endanger satisfactory performance. The Offeror shall focus on critical events that are realistically likely to occur and that would pose serious problems (do not try to identify every event that could cause some minor difficulty). Additionally, the Offeror shall provide a contractor mitigation plan for each event identified.

Work Breakdown Structure/Integrated Master Schedule The Offeror shall provide a detailed schedule of events and briefly describe each activity with its inputs and outputs and the interrelationships and interdependencies among each of the activities.

Models & Tools The Offeror shall identify and describe the models and / or other tools that would be utilized to perform the task. Additionally, the Offeror shall identify and describe the process to track progress towards completion of the task.

Reports The Offeror shall provide a list, and brief description, of recommended reports to document the task.

LOE The LOE and ODC estimate is provided by the Government in Attachment L-2.

1.2 Key Personnel & Functional Positions

Resumes will not count against page count limitations identified in Section L-1, Part A; paragraph 3.0.

Resumes. The Offeror shall provide resumes for all current, prospective, or contingent Key Personnel identified in Section L-1, Part B, Volume 3, paragraph 3.6.3, to include the work assignments, training, etc., which demonstrates the experience and specialized qualifications of each key position proposed. Resumes shall contain, at a minimum, the following information:

responsibilities nd employer

The Government may check educational background to verify degrees or certifications received.

If the qualification (e.g. education, experience) does not readily or easily compare to the minimum qualification stated in the SOW, the Offeror shall provide an explanation as to the equality of the proposed qualification to meet the minimum qualification. Definitions and additional instructions for prospective and contingent may be found in Section L, Part B, Volume 3, paragraph 3.3b.

1.3 Management

(a) Management: The Offeror shall address the following.

(1) Management Approach The Offeror shall describe the process, procedures, and approach to managing overtime (OT), travel, and materials purchasing. Additionally, the Offeror shall describe the methodology to allocate overhead functions, such as management, payroll, personnel, and finance etc.

Additionally, the Offeror shall include the approach to ensuring that procedures and processes regarding OT, travel, and material purchases are adhered to.

(2) The Offeror shall provide an overview of its proposed organization, including an organizational chart showing interfaces, locations, and lines of communication among the Government, the Prime, and its subcontractors. Specifically, the Offeror shall show where the proposed Key Personnel are located in the organizational chart and their lines of reporting and authority. Also, the Offeror shall specifically show proposed lines of responsibility, authority, and communication through which the tasks will be managed for this requirement.

(3) The Offeror shall specify if personnel supporting specific functions will be charged direct or indirect and justify the benefit to the Government. Offerors shall provide the employee location, education, years of experience, and description of work experience for each individual proposed in their management strategy for contract support functions. The Government desires that contract support personnel be charged indirectly with the exception of Key Personnel. If the Offeror decides to direct charge contract support personnel, please see paragraph (7) below for justification requirements.The list below is provided as an example of functions historically necessary for successful contract performance, and Offerors are encouraged to propose in accordance with their business practice and strategy. Contract support personnel may either support single or multiple functions, and offerors should identify those functions, if any, where a single individual will support multiple functions. The list below is not inclusive of all positions an Offeror may employ in their management strategy. As it relates to this contract, the Government considers only those positions listed in Section L-1, Part B, Volume 3, paragraph 3.6.3 as Key Personnel.

a. General Operations Manager (Program Manager)*

b. Deputy General Operations Manager (Deputy Program Manager)*

c. Financial Manager

d. Contract Administration

e. Cost Accounting

f. Task Order Processing

g. Task Order Reporting

h. Subcontracting

i. Personnel/Human Resources

j. Facilities Security Officer

k. Property Administration

(4) support the technical requirements of the solicitation and the ability to function as a viable and productive provider of contracted services to the Government.

(5) On average, ESS has thirty five active task orders, each with one to three customers. The Offeror shall approach to managing a large volume of orders and customers.

(6) system. The Offeror shall provide enough detail to determine whether the Offeror will have sufficient, timely accounting information to manage the contract at the task order level. The Offeror shall specifically address the capability to track and invoice the costs at the sub-task level and identify to what level of the work breakdown structure w

(7) Moving indirect charges to direct does not necessarily improve efficiency or reduce cost to the

Government, and a Cost Realism analysis may reflect such cost. If any individual performing an indirect function will charge direct, the Offeror shall identify and describe the technical task to be performed and justify the benefit to the Government, of direct charges, and state the percentage time to be charged direct. Offerors should note that insufficient detail supporting their use of direct charging may constitute an area of risk to the Government.

(8) Describe the role of the General Operations Manager (Program Manager) in product/process quality and how these functions are accommodated in the acquisition of overhead structures.

(9) The Offeror shall describe the procedures to be taken, and implemented, to ensure both quality and cost control. In terms of cost control, the Offeror shall include a description of internal mechanisms or controls which will be implemented to ensure accurate cost reporting and how the Offeror intends to control / mitigate overruns at all task levels. This section shall also describe how the Offeror will ensure timely and accurate invoicing of all subcontractors and/or JV team members.

(10) The Offeror shall discuss their process and/or procedures for early identification and resolution of problems, identification of potential performance risks, and proposed risk mitigation strategies.

(b) Staffing: The Offeror shall address the following.

(1) The Offeror shall describe the processes to be used in hiring, recruiting, retaining, and training personnel throughout the life of the contract. Additionally, address if the Offeror intends to hire the incumbent personnel, percentage, and process for determining their rate of pay and benefits.

(2) The Offeror shall describe the approach for providing workforce improvements, upgrading skills of motivated personnel, and preserving technical competence within the workforce essential in performing tasks detailed in the SOW.

(3) If the Offeror chooses to deviate from the Government estimated labor mix, the Offeror shall provide technical approach should be considered suitable to ensure successful performance of tasking requirements.

(c) Sub-contract Management: The Offeror shall address the following.

(1) The Offeror shall describe the subcontract management strategy for assembling teams, selecting subcontractors, maintaining subcontractor relationships, communicating information to the subcontractor, managing subcontractor performance, and resolving problems. The Offeror shall also explain the approach to selecting the best technical capability needed and the technical cost trade-off approach to ensure that the best value subcontractors are used for the effort.

(2) The Offeror shall describe the approach to determining the work to be performed in-house and the work to be subcontracted.

(3) The Offeror shal lead system integrator. In describing its subcontract management strategy, the Offeror shall also address those aspects that will be accomplished through a subcontracting approach, including how the subcontract management strategy will be employed consistent with the processes.

a. The process that will be used to determine the complexity and variety of the work small businesses are to perform.

b. The process that will be used to ensure maximum practicable participation of small businesses for each task order.

(d) Transition Plan: The Offeror shall address the following.

(1) Transition In The services under this solicitation are vital to the Government and must continue without interruption. The Offeror is required to submit a written narrative delineating a transition plan based on a 45-day period after award that ensures a smooth workplace changeover from the incumbent with no loss of service as described in 3.6.2 Labor Hours, and minimal loss of corporate knowledge.

The plan should take into consideration the following elements as well as any additional elements deemed necessary by the Offeror:

a. Subcontracts: The Offeror shall provide a plan of action to ensure that all subcontracts are signed within the 45-day transition period.

b. Incoming Personnel: The Offeror shall provide a plan of action to ensure that all personnel, within the 45-day transition period, are prepared to begin their work duties.

c. Quality Assurance: The Offeror shall provide a plan of action to ensure continuation of quality review processes during the transition period from the incumbent to the successful Offeror.

d. Training: The Offeror shall provide a plan of action to implement personnel training needed during the transition period to ensure continuity between the services provided by the incumbent and the successful Offeror.

e. Risk Mitigation Strategies: The Offeror shall provide a plan of action to mitigate contract performance risk that could be encountered during the transition period.

f. Security Requirements to include OPSEC, Facility Clearances and Base/Building Access: The Offeror shall provide a plan of action to obtain the required security clearances and physical access requirements of the contract during the transition period so as to not interrupt services.

(2) Transition Out: The services under this solicitation are vital to the Government and must continue without interruption. The Offeror is required to submit a written narrative delineating a transition plan based on a 45-day period after award that ensures a smooth workplace changeover from the incumbent with no loss of service as described in 3.6.2 Labor Hours, and minimal loss of corporate knowledge.

The plan should take into consideration the following elements as well as any additional elements deemed necessary by the Offeror:

a. Work Turnover: The Offeror shall provide a plan of action to effectively transfer tasked work that is in process at the expiration of the current contract from the incumbent to the successful Offeror of the follow-on contract.

b. Quality Assurance: The Offeror shall provide a plan of action to ensure continuation of the quality review processes during the transition period from the incumbent to the successful Offeror.

c. Training: The Offeror shall provide a plan of action to implement personnel training needed during the transition period to ensure continuity between the services provide by the incumbent and the successful Offeror.

d. Risk Mitigation Strategies: The Offeror shall provide a plan of action to mitigate contract performance risks encountered during the transition period.

e. Security Requirements to include OPSEC, Facility Clearances and Base/Building Access: The Offeror shall provide a plan of action to implement the required security clearances and physical access requirements of the contract during the transition period so as to not interrupt services.

f. Data Transfer: The Offeror shall provide a plan of action for the efficient inventory and transfer of program data from the incumbent to the successful Offeror.

2.0 VOLUME 2: PAST PERFORMANCE

2.1 General

Sources of past performance evaluation information include information provided by the Offeror in response to the solicitation, information obtained from questionnaires, and any other sources available to the Government, to include, but not limited to, the Past Performance Information Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information Systems, Electronic Subcontract Reporting System, or other databases; the Defense Contract Management Agency; and interviews with Program Managers, Contracting Officers, and Fee Determining Officials.

The Offeror shall complete the Past Performance Information Form, Attachment L-3, for each past performance reference (contract or delivery/task order) performed within five years of the solicitation release date. The Offeror shall submit no more than five Past Performance Information Forms as the Prime Contractor, no more than three forms for each principal subcontractor, and/or no more than three forms for each JV team member. For contract references that contain delivery/task orders, additionally provide the work description(s) for each specific the Offeror performed as a subcontractor, the Offeror shall clearly identify the applicable portion of the contract requirements that they performed. The Offeror shall submit written consent from its principal subcontractor(s) and JV team member(s) that will allow the Government to coordinate any past performance issues directly with the Offeror. If the Offeror does not submit the written consent, the Government will address any past performance issues directly with the principal subcontractor(s) or JV Team member(s) and the Offeror will forfeit the opportunity to participate in any related discussions. Consequently, for any principal subcontractor(s) and JV team member(s) that does not provide the written consent, the Offeror shall provide the name, address, phone number, and email address with whom the Government may address any past performance issues.

t work effort that matches the relevancy definitions specified in Section M of this solicitation. Additionally, the Offeror shall provide the

Performance Volume.

The primary source of past performance information will be PPIRS. If a Contractor Performance Assessment Report (CPAR) exists for multiple years for the same contract/order, all periods of performance within the recency period will be used for evaluation. In the event a CPAR does not exist for a past performance reference, the Offeror shall submit a Contractor Performance Assessment Questionnaire (CPAQ), Attachment L-4, to the Contracting Officer, Administrative Contracting Officer, and Program Manager. The Offeror shall include instructions for the Contracting Officer, Administrative Contracting Officer, and Program Manager to send completed questionnaires within two weeks of its receipt via e-mail to Christopher Bachman, Contract Specialist, at christopher.p.bachman2.civ@us.navy.mil, thereby allowing the customer approximately two weeks to complete their response. All CPAQs should be received by the Government concurrently with submission.

3.0 VOLUME 3: PRICE/COST PROPOSAL

3.1 Volume Content:

(a) This Volume shall contain the Contract Compliance information specified below as follows:

i. Offeror Summary Table: The Offeror shall complete the table below. The Offeror shall include all subcontractors and JV team members who will be involved with the performance of the contract and list all sites where the work will be performed. If a JV teaming or subcontracting arrangement is proposed, identify the work share, distribution elements, and ratios that each contractor will perform using the table below. Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship.

Contractor Name (Indicate Prime, JV Team Member, or Sub)

Place of Performance/

CAGE

CODE/DUNS #

Brief Work Description and/or Program Responsibility

% of Total Proposed Price

ii. Signed SF33 or SF1449 for basic solicitation and acknowledgment of each amendment, including completion of any RFP clause or provision that requires a fill-in or response.

iii. Signed Representations, Certifications, and Acknowledgements and/or System for Award Management

(SAM).

iv. Guarantee the length of proposal validity (for at least 210 days after proposal submission).

(b) This Volume shall also contain a copy of Section B with the Contract Line Item (CLIN) and Sub-CLIN Unit Prices and, for evaluation purposes, the Total Prices filled in using the estimated quantities value in the solicitation and the instructions below. Offerors shall complete the composite rate tab in Attachment L-5 Cost Summary Spreadsheet with fully burdened labor rates exclusive of Fee to be used for B-TXT-STRMLND table at award.

Section B prices shall be provided separately in one digital data copy in MS Office 2016 Excel format. Within all Excel spreadsheets, the Offeror shall use formulas and functions to the maximum extent possible and avoid using

If links are utilized, supply those referenced files. Spreadsheets shall not be protected.

(c) All price/cost and price/cost supporting information shall be contained in Section B and the price/cost proposal.

No price or pricing information shall be included in any other technical volume including cover letters. Offerors are responsible for submitting sufficient information to enable the Government to fully evaluate their price/cost proposal.

3.2 Ground Rules and Assumptions:

(a) As this is a competitive acquisition, with adequate price competition anticipated, certified cost or pricing data in accordance with FAR 15.403-1 is not required. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data as necessary from both the Offeror and subcontractors. Further, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award, pursuant to FAR 15.406-2.

(b) The Offeror shall provide sufficient information to support its price/cost as well as an explanation of all ground rules and assumptions that affect the price/cost estimates.

(c) If subcontractors are proposed, they shall provide the same information required for the prime contractor, unless otherwise noted in the Price/Cost Information section below

3.3 Price/Cost Information:

Offerors shall submit their fully completed cost/price proposal utilizing the Cost…