L-0 Section L.pdf

Attachment L-0 N00024-26-R-4114 Section L

1.0 GENERAL

Complete proposals submitted in response to the Request for Proposal (RFP) shall be received prior to the date specified in block 9 of the Standard Form (SF) 33 (solicitation document).

2.0 GENERAL CONTENT REQUIREMENTS

The Offeror’s proposal is the sole basis for evaluating the technical merits of what is being offered, the degree to which the Offeror’s proposed performance capability and capacity are supported, and the ability of the Offeror to perform in accordance with (IAW) the requirements.

Proposals submitted shall be sufficiently detailed as to clearly demonstrate that the Offeror has a thorough comprehension of all requirements, including all special provisions of the RFP, to enable Government personnel to conduct a thorough evaluation of the proposal and to arrive at a sound determination as to whether the prospective Offeror will be able to perform in accordance with the requirements of the RFP.

Offerors are advised to submit proposals that are complete, clear, and consistent in all respects without the need for additional explanation or information. Offerors are cautioned against the use of general, vague, or unsubstantiated statements which prevent concise proposal evaluation.

The format and content of the proposal shall contain a response to the topics noted below.

Information presented shall appear in the same order as outlined by this Section. A master table of contents identifying major subsections by number, title, page number and volume shall be provided in each volume.

The Offeror’s proposal shall address the entire RFP and all its amendments, exhibits, and attachments. The proposal shall constitute an offer and will indicate the Offeror’s unconditional assent to the terms and conditions in this RFP. Objection to any of the terms and conditions will constitute a deficiency which may make the offer unacceptable. Alternate proposals will not be considered and shall not be submitted.

The Offeror shall not submit the Security Classification Specification as a part of the proposal.

The DD Form 254 will, however, become a material part of any resultant contract.

Documents, exhibits, and other attachments that form a part of this RFP and will become part of any resultant contract are identified in Section J. The following RFP sections listed below (which also form a part of this RFP) will not become a part of any resultant contract:

Section K – Representations, Certifications and Other Statements of Offerors Section L – Instructions, Conditions, and Notices to Offerors Section M – Evaluation and Award Factors

Offerors are expected to reach a reasonable understanding of the requirements of this RFP by careful study (particularly Section C—Descriptions/Specifications and Section J—List of Documents, Exhibits, and Other Attachments) and by the application of their qualified knowledge and experience. If such a review establishes the need for correction or clarification, such need should immediately be brought to the attention of the Contract Specialist (CS) and Procuring Contracting Officer (PCO), noted in clause G-242-H001, so that the matter can be resolved and so that, if necessary, official dissemination of such correction or clarification can be made to all Offerors.

3.0 SUBMISSION OF PROPOSALS

SEE BLOCK 9 OF THE SF33.

The Offeror’s proposal shall be detailed, specific, and complete to enable a thorough evaluation of the proposal and a sound determination that the proposal will meet or exceed the requirements and objectives set forth in the RFP. Proposals shall be submitted in accordance with the instructions herein, and non-conformance with the specified required content may be cause for rejection of the proposal.

Offerors are cautioned that pages above the specified page limit within each volume will be removed and not evaluated (i.e. if the maximum page limit is 30 and 35 pages are submitted, pages 31 through 35 will not be evaluated). Offerors are further cautioned that some factors have additional page limitation criteria, specific to that section (e.g., SB Plan/SB participation). The page count will not include cover pages, title pages, and table of contents.

NOTE: Unless specifically excluded above, all pages will count towards the page limitations, including all required plans and any submitted appendices.

Exhibits/Diagrams/Charts are allowable, but shall have type no smaller than 8-point font size, Times New Roman font and 1-inch margins. The narrative material in the proposal shall be single spaced, with type no smaller than 10-point font size, Times New Roman font and have 1-inch margins.

The proposal shall be valid for no less than 270 days from the date of RFP closing. The proposal shall provide comprehensive responses to the areas provided for in this section. The proposal shall be a complete response to the Statement of Work (SOW) and the requirements of this RFP.

Each Offeror must (1) submit an offer, (2) submit written information that pertains to its capability, and (3) submit supporting cost data. When evaluating an Offeror’s capability to perform the prospective contract, the Government will consider how well the Offeror complied with these instructions. The Government will consider an Offeror’s noncompliance with these instructions to be indicative of the type of conduct that it may expect from the Offeror during contract performance.

The first page of each volume shall be in accordance with FAR 52.215-1, “Instructions to Offerors – Competitive Acquisition.” The Offeror shall identify any restrictions to the disclosure of its proposal by marking the proposal in accordance with paragraph (e) of FAR Provision 52.215-1.

One (1) electronic submission of each proposal volume shall be sent through the Procurement Integrated Enterprise Environment (PIEE) website Solicitation Module. The PIEE website is as follows: https://piee.eb.mil. To register, click the “Register” button and agree to the Privacy Act Statement; select “Vendor” as the type of user you are; choose “User ID \Password” as how you will be accessing the PIEE applications and create a User ID and Password; choose security questions and answers; complete the user profile; enter company information; in the Roles screen, select “SOL – Solicitation” under Application and “Proposal Manager” under role and press the “+Add Roles” button; Roles summary will pop up and enter your CAGE under Location Code / CAGE (a Contract Administrator must be in System of Award Management (SAM) prior to entering this information); complete the justification (example: required for proposal submission); and sign the Statement of Accountability Agreement. It is highly recommended that the PIEE Solicitation Module account be established and the communication path confirmed well in advance of the proposal submission deadline.

To submit your proposal, please follow the PIEE instructions on how to attach documents. The link is noted here: https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf. Also posted as additional attachment to the RFP (but removed at award).

The PIEE proposal shall be submitted in accordance with due date listed in block 9 of the SF33.

Responses not received at the time specified will be considered late and not considered for award. The Offeror is responsible for the condition of its delivered proposal. Timely submission to PIEE does not constitute complete submission. As such, Offerors are strongly encouraged to submit early to allow time to confirm receipt of the proposal materials with the PCO or CS.

Note: Hand-carried and mail delivered proposals will not be accepted. Submission of e-mail offers is not authorized for this solicitation. The PIEE website is the only acceptable method of submission.

Electronic proposal submissions and supporting information shall be suitable for reading in the standard Microsoft Windows suite, in accordance with DFARS 252.215-7012

REQUIREMENTS FOR SUBMISSION OF PROPOSALS VIA ELECTRONIC MEDIA (JAN

2018). Submitted electronic files shall not be compressed. Included files shall be created/prepared using Microsoft Office 2010 compatible applications. Spreadsheets, worksheets, and workbooks shall be prepared using Microsoft Excel compatible applications.

Schedules shall be created and submitted using Microsoft Project compatible applications. In addition, the Offeror shall submit schedules as a higher-level PDF. Graphics, photographs, and other data beyond the capability of Microsoft Office 2010 compatible applications may be submitted in Adobe Acrobat format. Electronic spreadsheets shall not be compiled or password protected; and all cells and formulas shall be visible, editable, and unprotected. Formulas shall be maintained in each Excel sheet to permit verification of calculations, and revision of output(s) through variation of inputs(s). Any tables contained within submitted narrative shall be capable of being edited (i.e. not embedded pictures or screenshots). Submitted files shall not reference external data. The Offeror shall screen all proposal submission and supporting information for computer viruses prior to submittal. Submitted electronic files shall be limited to the following extensions:

.docx Microsoft Word .xlsx Microsoft Excel

.pptx Microsoft PowerPoint

.pdf Adobe Acrobat

.mmpx Microsoft Project

SUBCONTRACT INFORMATION

In requesting proposals from prospective subcontractors, Offerors shall provide all necessary information for the contemplated purchase. The Government will not advise prospective subcontractors as to the requirements of their transactions with Offerors, nor will the Government respond to direct inquiries from prospective subcontractors concerning clarifications of specification or solicitation requirements. ALL SUCH REQUESTS FOR

CLARIFICATION MUST BE SUBMITTED TO THE GOVERNMENT THROUGH THE

PRIME CONTRACTOR (OFFEROR).

The Chief of Naval Operations (CNO) Availability Schedules (Attachments J-16 and J-17) will not be posted as a separate attachment to the solicitation on www.sam.gov. Offerors interested in receiving a copy are required to submit a request via email to Mr. Tyler Pacak at tyler.p.pacak.civ@us.navy.mil and Mr. Jerry Low at jerry.low.civ@us.navy.mil and a copy will be provided via email.

3.1 PROPOSAL OVERVIEW

A. Proposal Structure

1. (4) Four separate volumes: Volume I (SF33 Solicitation Set), Volume II (Technical), Volume III (Past Performance), and Volume IV (Cost) are required. The page limitations are identified in table L1 below. The Offerors shall ensure consistency— defined as “free from variation”—between the technical proposal and cost proposal.

During the course of evaluating the technical and cost proposals, the PCO will validate that the technical proposal and cost proposal are consistent. Specifically, the costs proposed will be evaluated and verified using historical and current market information to confirm costs proposed are within reason and consistent with the technical approach. Any inconsistencies between the technical and cost proposals may be viewed as weaknesses and/or risks in the proposals, and the offer may, at the Government’s discretion, be considered unacceptable and eliminated from competition for award.

Table L1 – Volume Descriptions

Volume / Section

Title Page Limitations Electronic via PIEE

I SF33 Solicitation Set No Page Limit 1 i Cover Letter No Page Limit ii Title Page No Page Limit iii Table of Contents No Page Limit

1.1 Offer (items identified in 3.4.1) No Page Limit

1.2 General Information (items identified in 3.4.2) No Page Limit

II Technical Capability NTE 95 Pages 1 i Title Page No Page Limit ii Table of Contents No Page Limit iii Introduction Part of the 95-pg.

count

1.0 Factor 1: Management Approach (3.5.1)

1.1 Overall Management Approach/Management Plan Part of the 95-pg.

1.2 Organization Plan Part of the 95-pg.

1.3 Transition Plan Part of the 95-pg.

1.4 Subcontract Management Plan No Page Limit

1.5 Small Business Participation No Page Limit

1.6 Key Labor Category/Personnel NTE 2 Pages Per

Resume (Limited to a total of 17 resumes)

2.0 Factor 2: Technical Approach (3.5.2)

2.1 Overall Technical Approach/Technical Plan Part of the 95-pg.

2.2 Quality Assurance Program Plan (QAPP)/ Quality

Management System (QMS)

Part of the 95-pg.

2.3 Offerors’ and Major Subcontractor’s safety organization Part of the 95-pg.

2.4 Technical Maritime based aircraft carrier/surface ship work experience

Part of the 95-pg.

3.0 Factor 3: Resource Capabilities (3.5.3)

3.1 Overall Resource Plan Part of the 95-pg.

3.2 Staffing Plan Part of the 95-pg.

III Factor 4: Past Performance Required 3 efforts 1 ii Table of Contents No Page Limit

1.0 Past Performance Example 1 No Page Limit

2.0 Past Performance Example 2 No Page Limit

3.0 Past Performance Example 3 No Page Limit

IV Factor 5: Cost No Page Limit 1 ii Table of Contents No Page Limit

1.0 Prime Contractor Cost Exhibits (Attachment L-3) No Page Limit

2.0 Subcontractor Cost Data No Page Limit

3.0 Contractor Estimating Rationale/Cost Proposal Narrative No Page Limit

4.0 Other Data No Page Limit

Note: The RFP response must be submitted in four (4) separate volumes (each Volume is a separate e-file if it fits in the 1.9GB size but can be separated into individual files if needed) as delineated above, with any subheadings divided and easily recognizable upon viewing each volume. No additional volumes or pages will be reviewed. Sub-headings are for organizational purposes.

2. Offerors are cautioned that, in accordance with the clause “Instructions to Offerors-

Competitive Acquisitions” (FAR 52.215-1), the Government intends to award a contract on the basis of initial proposals received, without discussions. Therefore, each proposal shall contain the Offeror’s best terms from a cost and technical standpoint.

Proposal Outline: The proposal shall be organized in accordance with the Volume, Factor, and layout detailed in the following outline:

Each of Volumes I, II, III, and IV shall contain the following items in addition to the Offeror’s proposal data required by this RFP:

a) Cover Letter (Vol I only)

i. i. The following statement: “The Offeror confirms that

Volumes I, II, III and IV comply with the requirements of N00024-26-R-4114, as amended, including all terms, conditions and provisions and agrees to furnish any items upon which prices are offered and

ii. Is valid for a period of 270 days from the date established for the receipt of proposals

iii. Name, Point of Contact Information, address, telephone number, and email address of the Offeror of the person authorized to negotiate and sign the proposal, cage code and Unique Entity ID (UEI).

iv. Signature and Date

b) Title Page (Volume I, II, III, IV)

a. The title page shall include the following:

i. Title of Proposal

ii. Volume number and title

iii. RFP number

iv. Name, Point of Contact Information, address, telephone number, and email address of the Offeror

c) Table of Contents (Volume I, II, III, IV)

a. The table of contents shall provide sufficient detail, including page numbers, so that factors and sections can be easily located.

B. Solicitation Responsiveness

Offerors are advised to submit proposals that are complete, clear, and consistent in all respects without the need for additional explanation or information. Offerors are cautioned against the use of general, vague, or unsubstantiated statements, which prevent concise proposal evaluations. Each factor will be evaluated on how well the response meets the requirements of the solicitation. The response that completely addresses all the solicitation requirements may be judged superior to the response that minimally addresses solicitation requirements.

C. Competitive Range

If an award is not made on the basis of initial proposals, the PCO will make the determination as to which proposals are in the “competitive range.” The competitive range shall be determined based on the results of the evaluation of initial technical and cost proposals, considering all evaluation criteria, and shall include the most competitive proposals. The number of proposals within the competitive range may also be reduced if the PCO determines the number of most competitive proposals that might otherwise be included within the competitive range exceeds the number at which an efficient competition can be conducted.

D. Discussions/Final Proposal Revision (FPR)

1. If discussions are held, all Offerors selected to participate shall be advised of areas for discussion in their proposals and shall be offered a reasonable opportunity to correct or resolve those areas and to submit such technical and cost information, or other revisions to their proposal, that may result from such discussions.

2. The PCO intends to make award without conducting discussions. At his or her discretion, the PCO may determine the competitive range and elect to conduct either verbal or written discussions, or both. If the PCO elects to conduct discussions, the PCO reserves the right to conduct oral discussions, consisting of presentations of discussion question responses followed by a question-and-answer session. At such time, the PCO will also provide the Offerors with information as to the format, length and rules which will govern the conduct of oral presentations of discussion question responses. Responses to discussion questions, both written and oral, will become part of the proposal only if subsequently specifically referenced in the FPR. When discussions are completed, the PCO will close discussions and request FPRs.

3.2 CROSS REFERENCING

Each volume shall be written to the greatest extent possible on a stand-alone basis so that its content may be evaluated with a minimum amount of cross-referencing to other volumes of the proposal. Cross referencing within a proposal volume is permitted where its use would conserve space without impairing clarity. Information required for proposal evaluation that is not found in its designated volume will be assumed to have been omitted from the proposal.

Each volume shall contain a glossary of all abbreviations and acronyms used.

Glossaries do not count against the page limitations for their respective volumes.

3.3 COMMUNICATIONS WITH THE GOVERNMENT

3.3.1 Solicitations and Amendments

Solicitation information and amendments will be made available through the Government Contract Opportunities website found at: www.sam.gov, as well as PIEE.

Offerors are required to periodically check for responses to questions and any issued amendments.

3.3.2 Questions Concerning the Solicitation

Offerors may submit questions requesting clarification of RFP requirements by electronic mail to Mr. Tyler Pacak at tyler.p.pacak.civ@us.navy.mil and Mr. Jerry Low at jerry.low.civ@us.navy.mil using Attachment L-1.

Offerors shall use the subject heading for the email correspondence: N00024-26-R-4114 RFP Bidder Questions.

Only questions submitted by electronic mail will receive a response. Questions and responses will be distributed electronically via www.sam.gov/PIEE to all potential Offerors as an amendment to the solicitation and will not be attributed to any individual or organization. Questions/comments must contain at a minimum: the document name, document date, specific page, paragraph, clause, or other definitive citation requiring clarification, in addition to the question posed. Questions should not include proprietary or otherwise protected information of the Offeror, in accordance with NAVSEA clause L-215-H007.

3.4 INSTRUCTIONS FOR VOLUME I – SF33 SOLICITATION SET

3.4.1. Offer

The offer is the document that will be used to make an award to the successful Offeror and must include the following:

a. Standard Form 33, “Solicitation, Offer and Award”, with blocks 12 through 18 completed by the Offeror.

b. Solicitation Amendment(s) (if any) – The Offeror shall submit a signed complete copy of each amendment.

c. RFP Sections B through J - The Offeror shall submit Sections B through J with all appropriate information required by the RFP completed by the Offeror.

d. RFP Section K, “Representation, Certifications and Other Statements of Offerors”, shall be completed by the Offeror or a statement verifying the information has been completed in the System for Award Management with the date through which the registration remains valid.

e. Exhibit(s), Attachments, and Schedules – The Offeror shall submit a copy of or provide written acknowledgement and acceptance of all Exhibits, Attachments, and Schedules, which will form a part of any resultant contract. All Exhibits, Attachments, and Schedules that require the Offeror to provide information shall be completed in their entirety.

f. Small Business Subcontracting Plan as required by FAR 19.302, if applicable.

g. Miscellaneous: In the event that any portion of the technical proposal is written by an individual or individuals who are not bona fide employees of the Offeror, a certificate to this effect shall be signed by a responsible officer of the Offeror and shall identify the proposal writer's name, employment capacity, the name of his/her firm, the relationship of that firm to the Offeror’s, and the specific portions of the technical proposal written by that person.

3.4.2 General Information

Offerors shall provide the source of approval, the latest dates, and the current status in which the Offeror had the following:

a. Accounting System. Offerors are cautioned that this contract contains cost reimbursement requirements, and a cost reimbursable contract may only be awarded to an Offeror that meets the limitations set forth in FAR 16.301-3;

b. Purchasing System;

c. Estimating System;

d. Adequacy of the Offerors Disclosure Statement pursuant to FAR 30.204(a) and FAR

52.230-1. Offerors shall identify the cognizant Administration Office (DODAAC,POC name, phone number, email address, and physical address) and provide copies of the letters transmitting the approvals of the above identified systems with its proposal submission.

Offerors shall provide a summary of this information in the following format:

Table L2: General Information

Business System Current Status

Review Date ACO/Cognizant Administration Office POC/Dodaac

Telephone Number

Email Address

Accounting System

Purchasing System Estimating System

Disclosure Statement Adequacy

3.5 INSTRUCTIONS FOR VOLUME II – TECHNICAL CAPABILITY

Instructions for Technical Proposal Preparation

NO COST INFORMATION TO BE PRESENTED IN THIS VOLUME.

The Technical Capability Volume shall be sufficiently detailed and complete to fully demonstrate the Offeror’s understanding of the scope of the acquisition and an overall capability to provide the required work in accordance with all requirements of the solicitation.

Offerors may provide an overview of technical capability, to address specific areas in the SOW that are not otherwise explicitly captured. Offerors are encouraged to demonstrate the full breadth of their understanding.

The PCO reserves the right to request such additional information regarding scheduling, manpower, facilities, and management organization and capabilities as may be necessary to determine the Offeror’s qualifications for award of a contract, to determine the relative merit of the Offeror’s proposal, or to otherwise clarify any aspect of the proposal.

Offerors should note that if awarded a contract based upon this solicitation, the Offeror’s technical proposal or a portion thereof may be incorporated into the contract by reference.

Release of Technical Information: All technical information submitted pursuant to this solicitation is for the exclusive use of Government representatives, and will be treated as business confidential and will not be publicly disclosed, provided that, where a request for disclosure of such technical information is submitted to the Government pursuant to the Freedom of Information Act (5 U.S.C. 552a), the Government will not disclose the Offeror’s technical information if public disclosure of information would substantially harm the Offeror in its competitive position. In order to help ensure non-disclosure, the title page of the technical proposal and other sheets of proposal data should be marked with restrictive legends contained in the solicitation instruction in Section I entitled

“DFARS 252.227-7037 VALIDATION OF ASSERTED RESTRICTIONS ON

TECHNICAL DATA,”

CAUTION: The Technical Capability Volume should contain brief statements of fact rather than wordy, generalized narratives.

The Volume shall be properly paginated, with the appropriate page number marked on each page. For formatting purposes, each electronic page shall be counted as one page, with the exception of the following items:

(a) The first page shall consist of a single title page containing only the following basic information: volume number and category name; the solicitation number; the name of the contract; Offeror’s name; and the Offeror’s position regarding disclosure of proposal data. No pages placed before this title page will be evaluated.

(b) The table of contents for the proposal, which shall immediately follow the title page described in item (a) above.

(c) The resume(s) shall not exceed two (2) pages for each individual with a total limit of seventeen (17) resumes. Pages in excess of two (2) will be counted toward the 95-page limit for the technical proposal.

(d) Up to ten (10) pages of exhibits included in the technical proposal. Each page in excess of the ten (10) page allowance for exhibits will count as one (1) page towards the 95-page limit for the technical proposal. Exhibits/Diagrams/Charts must not contain any text other than simple explanations pertinent to the exhibit.

(e) Letters of commitment from major subcontractors, as described below in section 3.5.3 C, “Resource Capabilities”.

3.5.1 - Volume II, Factor 1.0: Management Approach

Factor 1: Management Approach Instructions

In preparing a response for this section, the locations and percentages of work to be performed for Aircraft Carriers are in Table L3. Percentages are of total number of work labor hours:

Table L3 – Aircraft Carrier Work Percentage by Location Location % of Work Facility Requirement Norfolk, VA 60% Required San Diego, CA 20% Required Bremerton, WA 15% Required Yokosuka, Japan 5% None anticipated

*Offices must be located within 50 miles of Government location listed above.

For Surface Ships the locations and percentages of work to be performed are in Table L4.

Table L4 – Surface Ship Work Percentage by Location Location % of Work Facility Requirement Norfolk, VA 5% None anticipated Everett, WA 5% None anticipated Pearl Harbor, HI 10% None anticipated San Diego, CA 35% None anticipated Yokosuka, Japan 30% None anticipated Sasebo, Japan 15% None anticipated

Offerors should provide a systematic approach that demonstrates a comprehensive understanding and application of management techniques, methods and procedures required to efficiently execute the requirements of this solicitation. Task orders under CLIN 0001 may be issued on the date the contract becomes effective. The awardee is required to be staffed and operational with key personnel whose resumes were submitted within 30 days after the effective date of the contract. Further, the awardee shall be 100% fully staffed and operational within 45 days after the effective date of the contract. The Government prefers an individual Program Manager (PM) on each coast.

Offerors should address the following areas, taking into account all the Offerors’ current Government and commercial efforts under contract, the proposed effort under this solicitation, and any other submitted proposals.

(a) Describe the program management organization to be used for this effort and how it will contribute to the planning and execution of work requirements.

(b) Describe the formation, function and responsibilities of the project organizations and information-sharing techniques to be utilized. Specifically discuss the information-sharing techniques between Government Agencies, the Prime Contractor and its major subcontractors during the production availability.

(c) Describe the organization’s plan for management control of subcontractor effort including a comprehensive description of the roles and responsibilities for each Major Subcontractor and the rationale for selecting each Major Subcontractor.

Major Subcontractor is defined in two ways: those subcontractors providing effort consisting of ten percent (10%) of total proposed dollars. Total proposed direct dollars is defined as all costs proposed (direct, indirect, material, travel) excluding fee.

(d) Provide the plan to integrate and familiarize all subcontractors with the prime Contractor’s execution philosophy and strategy.

(e) Provide the total allocation of work that will be accomplished by the prime, by each Major Subcontractor and by other subcontractors, and describe the basis and computation for which the work allocation was developed (total man-hours, dollars, production hours, etc.). The work allocation percentages must be traceable to the cost proposal and shall be consistent with supporting cost documentation such as Total Proposal Contract Value Summary and CLIN Cost element breakdown in the Cost Proposal.

(f) Discuss the organization’s lines of communication and authority with the

Navy as well as Major Subcontractor key personnel. Discuss the percentage of time that key personnel identified will be dedicated, on an annual basis, to this effort as well as to existing and other currently submitted proposed work.

(g) Provide resumes for prime and Major Subcontractor (as defined in item (c), above) key personnel. Provide cross-referential information and/or definitions of company-unique personnel titles proposed.

(h) Identify any Offeror and/or Major Subcontractor labor agreements that expire during this stated contract Period of Performance (POP) and contingency plans for labor strikes.

(i) Describe the Offeror and Major Subcontractor cost reporting systems for compiling internal costs and subcontractor costs, and discuss how costs are budgeted, monitored and controlled. Describe how costs are reported to the Accounting Classification Reference Number (ACRN) level and how growth funding and incurred costs will be tracked.

(j) Discuss the data deliverable requirements of the contract including execution planning, availability progress reports and project completion reports to the Government.

(k) Describe the Offerors’ method for tracking actual progress versus planned progress and processes to regain planned progress when variance occurs.

1.1 Approach

Offeror shall address their overall management approach and ability to plan, manage, and execute all efforts required by the SOW under this solicitation, including, but not limited to, controlling personnel, controlling utilization of resources, tracking deliverables, monitoring performance and obtaining Government feedback. Offeror shall describe processes to be used by Delivery Order technical leadership to ensure specific subtasks are being performed effectively and efficiently.

1.2 Organizational Plan

Offeror shall provide an organization chart that demonstrates the location of this work in the Offeror’s organization and demonstrate how this effort will receive sufficient corporate level attention during performance. The plan shall describe the Offeror’s corporate structure and ability to manage a high- performing team, describe the procedures in place for monitoring and controlling costs, and also demonstrate that the Offeror will be successful in undertaking these management and cost control efforts.

1.2 Transition Plan

The Offeror shall describe the transition process in detail including all steps the Offeror intends to take in order to assume responsibility from the incumbent Contractor within forty-five (45) days upon contract award. Offeror shall address how personnel are properly trained and skilled with adequate security clearances;

and how the Offeror will assume responsibility for support of current programs without discontinuity of workflow or loss of integrity of the programs' current operation. The Offeror shall demonstrate its ability to meet the facility clearance requirement and safeguarding capability requirement identified in the DD254 attached in Section J herein. If the Offeror does not currently possess the required facility clearance, the Offeror shall demonstrate its completion of the preparatory steps necessary to be granted the facility clearance in a timely manner upon contract award. The Offeror shall provide a plan for hiring personnel after contract award. The proposed plan should include a schedule for hiring ramp up and a timeframe of when staffing actions will be completed and any risk mitigation strategies. Staffing actions shall be completed NLT forty-five (45) days after contract award. The plan shall include, but not be limited to: start date, end date, and detailed Plan of Action & Milestones (POA&M) with measurable elements. The Transition Plan shall be consistent with the Offeror’s Technical Approach and Cost proposal. Specific elements to consider include:

(a) Transition Team Responsibilities - Offerors shall describe its start-up plan with a detailed explanation regarding how full performance will be achieved on the first day of contract performance. Offerors shall describe their intended mode of establishing management and project staffs, assuming responsibility for support of the programs’ current operation without discontinuity of workflow or loss of integrity of the program’s current operation and creating interfaces for technical and contract administration. Identify the risks in accomplishing transition of this requirement in a seamless manner and identify specific risk mitigation measures that will be implemented. Costs unique to the implementation of the proposed transition plan shall be clearly identified in the cost proposal.

(b) Work Turnover - The Offeror shall provide a plan of action to effectively transfer tasks that are in process at the expiration of the current Contract from the incumbent Contractor, including how the awardee will coordinate communications with the incumbent

Contractor and how it will ensure uninterrupted workflow during the transition process.

(c) Incumbent Capture – If the Offeror intends to hire incumbent personnel, the Offeror shall address how the Offeror will transition incumbent personnel and discuss risk mitigation if the Offeror is unable to hire incumbent personnel.

(d) Security Requirements – The Offeror shall provide a discussion regarding OPSEC, facility clearances, and base access. The Offeror shall provide a plan to implement the required security clearances and physical access requirements of the Contract during the transition period so that service is not interrupted.

(e) 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.

(f) 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 to the successful Offeror.

(g) Archived Material - The Offeror’s plan shall address proposed procedures, tools, and processes for the transfer and storage of all archived programmatic documentation and the establishment of accounts and roles for access to data held in government-managed Information Technology systems, while protecting sensitive information such as Personally Identifiable Information, Business Sensitive, Business Proprietary, Classified, and other Unclassified but Controlled Information. The plan shall indicate if there are any actions that must be completed by the Government to support successful completion of transition actions.

1.4 Subcontract Management Plan

If Subcontracting or teaming is proposed, the Offeror shall propose a Subcontract Management Plan (SMP). The Offeror’s SMP shall describe its processes and techniques used to manage subcontract performance (technical, schedule, and cost), billing, and reporting. The SMP shall be fully consistent with other portions of the proposal. The SMP shall only include those subcontractors, which are priced in the cost proposal. The Offeror shall address the technical reason(s) for selecting each Subcontractor; identify the portions of the SOW that will be subcontracted and the contractual relationship to the subcontractor. This section has no page limit.

1.5 Small Business Participation

To evaluate small business utilization, this solicitation utilizes two distinct documents: the Small Business Subcontracting Plan (for large businesses only) and the Small Business Participation Commitment Document (SBPCD) (for all Offerors).

The instructions for each are provided below. This section has no page limit.

A. Small Business Subcontracting Plan (SBSP for Large Businesses only)

Offerors shall allow the maximum practicable opportunity for Small Business to participate in contract performance and shall submit a SBSP as required by FAR

19.302 with the Cost Proposal.

Offerors shall endeavor to achieve the congressionally mandated five percent (5%) goal for Small Disadvantaged Business (SDB) concerns. It is the intent of the Government to encourage the use of Small Businesses whenever practicable. For purposes of bidding, the Offeror shall propose thirty percent (30%) small business-subcontracting goal for the SBSP. The Offeror shall describe the extent to which its company has identified and committed to provide for participation by small businesses, including Veteran-Owned Small Businesses (VOSB), Service-Disabled Veteran-Owned Small Businesses (SDVOSB), HUBZone small business, SDB, Women-Owned Small Businesses (WOSB), historically black colleges and universities, and minority institutions for the performance of this contract.

Of special interest is the amount and type of work to be performed by the subcontractors. The Offeror shall provide sufficient information to demonstrate that the contributions that small business subcontractors make will be meaningful in the sense that they will be performing functions important to the overall success of the program and also broaden the subcontractor’s technical capabilities. The Offeror shall explain the reasons for, and advantages of, selecting the particular subcontractors (this explanation need not include material vendors).

For small businesses proposing as prime contractors, information relative to the overall breakout to subcontracting partners is desired under this section.

The Offeror shall describe its management approach for enhancing the technical capabilities. The Offeror shall include a list of the effort(s) to be provided by the small businesses.

B. Small Business Participation Commitment Document (SBPCD) (All Offerors)

Separate from the small business subcontracting plan, all Offerors, regardless of size status, shall submit an SBPCD within this section of Volume II. The SBPCD is a key evaluation document used to assess the extent to which an Offeror commits to utilizing small businesses in the performance of the contract. This SBPCD shall at the minimum, contain the following:

A narrative describing the Offeror’s commitment to providing meaningful participation opportunities for small business concerns, including Service-Disabled Veteran-Owned (SDVOSB), HUBZone, Small Disadvantaged (SDB), and Women- Owned (WOSB) small businesses.

A list of the specific products and/or services to be provided by small business concerns. For each, identify the name of the small business, UEI and Cage Code, and describe the type and complexity of the work they will perform.

A description of the Offeror's management approach for integrating and enhancing the capabilities of its small business partners.

To support the SBPCD evaluation, Offerors should provide evidence of commitment (e.g., letters of intent, teaming agreements) and past performance in small business utilization (e.g., eSRS reports, CPARS). This supporting evidence will not be incorporated into the contract.

This section has no page limit.

1.6 Key Labor Category

Resumes are required for the key labor categories specified in Table L5. All resumes are limited to two (2) pages per person. The personnel whose resumes are provided (and accepted) will be subject to the terms of NAVSEA clause C-237- H002, Substitution of Key Personnel (Oct 2018). The Government may elect to identify the requirement for additional key personnel, for any of the identified labor categories, at the order level if determined to be necessary for completion of an order. Offerors who are submitting resumes of personnel who are not currently employed by the company shall submit a Letter of Intent (LOI) demonstrating the individual’s commitment to supporting the effort if awarded the contract. LOIs are limited to one page and are not counted against the resume page limitation.

Offerors shall only propose key personnel resumes for individuals that, at the time of proposal submission, the Offeror has a good faith expectation of providing during the life of the contract. Failure to utilize the specific individuals proposed as key personnel may result in negative CPARS findings during contract performance. Additionally, the Government considers the submission of LOI for proposed contingent key personnel to be material to the proposal since these LOI demonstrate the Offeror's ability to hire personnel with the qualifications bid at the salary proposed.

The minimum educational and experience levels delineated for the key labor categories should be demonstrated and detailed in the resume. A description of the minimum educational and experience levels personnel categories can be found under paragraph “Key Personnel Resumes (and minimum qualifications).”

For each key labor category, Offerors shall only submit resumes for the number of such key personnel listed in Table L5. If an Offeror submits resumes for more than the number of key personnel requested, the government will only evaluate resumes for the number of personnel listed below, beginning with the first resume for that personnel type. The government will not evaluate additional resumes than the number designated below for each of the key personnel labor categories and will not make decisions about which personnel best meet the minimum qualifications for that personnel type.

Table L5 – Key Personnel Requirements

Key Personnel Category # of Resumes Required Program Manager 2 Project Manager 5 Production Manager 10

Key Personnel Resumes (and minimum qualifications)

Position 1: Program Manager (Key Personnel, two (2) resumes required)

(a) Bachelor's Degree with ten (10) years’ experience in related engineering management field, or Associate's Degree with fifteen (15) years’ experience in related engineering management field.

(b) Five (5) years’ experience in program management support relating to aircraft carrier /surface ship (as applicable) maintenance. It is required that the individual has verifiable, extensive organizational knowledge of public naval shipyards, aircraft carrier/surface ship departmental structure, TYCOM structure, and /or the applicable RMC structure, as well as commercial structure.

(c) Five (5) years’ experience in actual operation, repairs, and maintenance of Navy aircraft carrier main propulsion, auxiliary, electrical, and damage control systems either in technical or management positions which include supervision of personnel. Three

(3) of the five (5) years should include experience with steam propulsion plants. Two (2) of the (5) years should include experience in actual operation, repairs and maintenance of carrier auxiliary, electrical and damage control systems either in technical or management positions which include supervision of personnel. One

(1) of the five (5) years should include direct experience with Naval Nuclear Propulsion Secondary Systems and/or Non-Nuclear Interface Systems and verifiable knowledge of NNPI in either technical or management positions. For Surface Ship Program Manager support, key personnel should have five years of experience on surface ship propulsion, auxiliary, electrical and damage control systems including at least three (3) years of experience in gas turbine propulsion systems.

Experience should include two (2) years of actual ship auxiliary, electrical, propulsion, damage control, or distributed ship's system maintenance and operations including supervision of personnel.

(d) Three (3) years of supervisor or managerial experience with one (1) year at the level equivalent to a Civil Service GS-12 rating or Navy Lieutenant (O-3), or Chief Warrant Officer (CWO) involving direct supervision of subordinate groups working in an engineering discipline.

Position 2: Project Manager (key Personnel, five (5) resumes required)

(a) Bachelor's Degree with ten (10) years’ experience in related engineering management field, or Associate's Degree with fifteen (15) years’ experience in related engineering management field.

(b) Five (5) years’ supervisory experience in the area of technical assistance, maintenance, or design related to Navy Aircraft Carriers/surface ships (as applicable) and three (3) years should be closely involved with practical aircraft carrier/surface ship (as applicable) maintenance, design, operation, and troubleshooting/installing main propulsion, auxiliary, electrical, and damage control equipment associated with shipboard level maintenance.

(c) Two (2) years direct experience with auxiliary, electrical, and damage control systems and included steam propulsion plants.

(d) Two (2) years direct experience with auxiliary, electrical and damage control systems for U.S. Naval Ships.

(e) One (1) year direct experience in Naval Nuclear Secondary Plant Systems and/or Non-Nuclear Interface Systems and verifiable knowledge of NNPI (for CVN Project Engineer position only).

(f) Two (2) years of supervisory experience.

Position 3: Production Manager* (Key Personnel, ten (10) resumes required)

(a) Ten (10) years experience in aircraft carrier or surface ships as applicable Hull, Mechanical, and Engineering (HM&E) engineering, including:

(b) Five (5) years’ experience in coordinating and supervising personnel effort in accomplishing shipboard HM&E repairs. Two (2) years should be closely involved with aircraft carrier or surface ships during maintenance availabilities, including procedures, work integration, administration and maintenance scheduling.

(c) Four (4) years’ experience in administration of the Navy Quality Assurance Program, 3M and Supply System.

*Note: All Production Manager FTEs remain as Key Personnel positions, however, only 10 resumes for this specific category will be required for evaluation purposes only. Once the contract is awarded, the Government maintains the right to review any and all additional resumes within this Key Personnel category at any given time during contract performance.

3.5.2 - Volume II, Factor 2.0 Technical Approach This part of the proposal should provide a technical approach laid out in a systematic fashion to convey a detailed and complete explanation of how the Offeror plans to complete the technical requirements. The Offeror shall demonstrate its ability to perform the technical requirements of the solicitation.

Explain any innovative procedures and identify and describe specific application to the RFP elements. Descriptions and discussions of processes, procedures and programs should flow in a narrative format without information gaps and must convey the complete picture. Offerors shall address the following areas taking into account all of the Offeror’s current Government and commercial efforts under contract, the proposed effort under this solicitation and any other submitted proposals:

(a) Discuss the Offerors’ technical approach to: 1.) planning through validation of GFI/GFM; 2.) pre-fabrication / advance staging; and 3.)

rip-out, repair, (re)installation, 4.) test of the work requirements, and 5.) compartment closeout.

(b) Offeror should demonstrate a robust quality assurance program and how its application would meet the technical requirements of the contract. Describe how the Offeror verifies the Major Subcontractor’s quality performance.

(c) Describe the methods used to integrate subcontractors, Government sponsored AITs, and Government agency representatives tasking with availability work scope, specifically to include planning and execution of integrated equipment and system testing.

(d) Provide a description of the Offeror’s and Major Subcontractor’s safety organization and how it complies with each of the requirements of NAVSEA Standard Items 009-07 and 009-10.

(e) The Offeror shall demonstrate PRIOR TECHNICAL EXPERIENCE, meaning specific instances and problem resolution, on specific projects that are similar to this solicitation’s SOW requirements. This should not be confused with past performance, which is how the Offeror performed and was rated. This should encompass specific maritime based Aircraft Carrier and Surface Ship experience covering specific timeframes. The Offeror shall provide examples of maintenance experience by company-certified craftsmen, technicians, and engineers qualified in hull, mechanical, electrical, and electronic systems and equipment. These individuals are required to be familiar with Carrier and Surface Ship maintenance procedures, hull coatings, COMNAVSEASYSCOM Logistics Support Center (ILS) procedures and functions of the Ship’s Maintenance Support Center (MSC), and Integrated Technologies (IT) Specialists familiar with fleet database management systems.