N6893625R0026 A0002.docx

N6893625R0026

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The following have been modified:

ANSWERING VENDOR QUESTIONS

Addressing Questions and Answers for the Vendors Q1: Section 2.0 requires all pages to be numbered with volume, paragraph and page numbers. Generally there are multiple paragraphs on a single page. Does the government wish the paragraph to be the first full paragraph or last full paragraph incorporated into the page number?

A1: If the question is understood correctly, in the sentence referred to in Section L, Part A, 2.0, is not referring to the actual page numbering of the proposal. The Government is requesting that volume numbers, paragraph numbers, and page numbers used on all pages.

Q2: Table G-1 does not appear to have file naming conventions as discussed in the paragraph above. Will the government provide discussed file naming conventions?

A2: The Government shall remove "The Offeror shall follow the basic structure of the file naming convention in Table G-1 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices), where “#” represents the sequential numbering of files. Offeror’s shall keep file names short (i.e., under 40 characters) so that the files are accessible on Government share drives. Files with longer names often become corrupt or inaccessible." Change made in this amendment.

Q3: Will the government adjust the Equivalent Categories to reflect the SCA occupational categories of 23000 - Mechanics and Maintenance and Repair Occupations, rather than the 30000 - Technical Occupations?

A3: The Diesel Engine Specialist has a SCA code of 23530.

Q4: Does the government have requirements beyond the SCA job descriptions for degrees, years of experience, etc. for the LCATS listed?

A4: The degree, years of experience, etc, are as stated in the Statement of Work Section 8.0. The contractor shall complete attachment L-3.

Q5: Attachment L-8 Vol 5 CA-1 Business Systems Status does not match the Table on page 114, section 5. Volume 5 - Contract Administration of the Solicitation. 1. Will the government update and re-issue Attachment L-8 to reflect the information that is to be provided in Volume 5 pertaining to Business Systems?

A5: See corrected attachment in this amendment.

Q6: Will the government extend the due date for this solicitation?

A6: The Government will extend the close date to January 5, 2026 at 12PM PST.

Q7: If a past performance has no CPARS, we have to submit the L-4 form to our government contracting POCs, to then send back to you. The L-4 form is a form to acquiring CPARS. Therefore, the Prime contractor would receive CPARS for the L-4 form submission. Does this mean that bidders cannot use subcontractor Past Performance? (Subcontractors cannot receive CPARS) If subcontractor Past Performance is allowed, can the government send a questionnaire that we can send to our Prime contractors Program Manager directly?

A7: Subcontractor Past Performance is allowed. If Attachment L-4 does not apply, Attachment L-5 can be used.

Q8: Will the government clarify that only The key person requires the information asked for in subsections (a), (b), (c) and (d)? Specifically, are summaries, Resumes and LOIs only required for the Program Manager?

A8: Resumes and LOIs are only required for the Program Manager, who is a key person.

Q9: Since the only Key person is the Program Manager, is the offeror required to provide the information in the columns of L-3 for non-key personnel?

A9: Attachment L-3 is for non-key and key personnel.

Q10: Will the government consider using a T&M rate rather than CPFF for this opportunity?

A10: The contract will remain CPFF.

Q11: How many FTEs from each of the labor categories does the Government expect?

A11: FTE is equivalent to 1920 hours. Refer to the solicitation for level of effort.

Q12: Does the Government expect any of these FTEs to be “full-time” or will all FTEs be “part-time” as needed?

A12: The Government cannot tell the contractor how to propose in this situation. Refer to the solicitation for level of effort.

Q13: Given that the PM is only funded part-time, it is reasonable to assume that all other categories are part-time as well.

A13: The Government cannot tell the contractor how to propose in this situation. Refer to the solicitation for level of effort.

Q14: Why does Section 5.1.2 require that “The Program Manager shall be local, on-site at China Lake” when the position is designated as part-time?

A14: The Government needs the Program Manager to be on-site.

Q15: Will the government please confirm there is only one Key Personnel – specifically “the Program Manager”?

A15: Yes, the Government confirms there is only one Key Personnel- the Program Manager.

Q16: Are any positions or labor categories on this contract anticipated to require full‑time support in any given contract year?

A16: The Government cannot tell the contractor how to propose in this situation. Refer to the solicitation for level of effort.

Q17: Can you please provide the names and contact information for the incumbent personnel?

A17: The incumbent is stated in Section L.

Q18: Is the incumbent contractor currently performing on this contract? Or has the contract ended?

A18: The current contract ends March 31, 2026.

Q19: What is the last date that the incumbent contract performed on this contract?

A19: The current contract ends March 31, 2026.

Q20: Given the requirement is to be fully staffed in 7 days after award, are the incumbent personnel still available or have they moved on to other contracts?

A20: The current contract ends March 31, 2026.

Q21: How many positions must contractors have filled within the 7 days to be considered “fully staffed”? One FTE, the PM? Two FTEs, the PM and Fiber Optic Network Engineer, Seven FTEs, one for each labor category, etc?

A21: The contractor shall have the positions filled to meet the requirements of the contract.

Q22: Can this requirement be fulfilled after the contract award, during the transition?

A22: The contract will be awarded with a transition period prior to award start date.

Q23: Would the Govt please provide a 2 week extension to the proposal due date?

A23: The proposal closing date will be extended until 06 Jan 2026 at 3PM PST.

Q24: Since the Program Manager appears to be part time, can they be dual hatted?

A24: The contractor shall meet the needs of the contract. The Government cannot tell the contractor how to propose in this situation.

Q25: Would the government clarify the location of “SOW Attachment 1, Section J?”

A25: SOW attachment 1 Section J, is Section C. See changes in Section L below.

Q26: Would the government confirm the numbering and paragraphs should align with Section L of the RFP and not with the provided content of the CRM, in attachment L-2?

A26: The table was provided as an example. See Section L, 2.0.

Q27: Is an employee Interim Secret adequate at the start of work?

A27: Yes.

Q28: IF we provide ALL relevant contracts to include commercial and government work to include individual task orders, we are estimating nearly 50 citations with all appropriate documentation. Would the government like to put a maximum number limit on the number of relevant contracts?

A28: The maximum number is five (5) citations for each of the principal entities.

Q29: Would the government confirm that CPARS will be the primary method used to retrieve CPARS?

A29: See Section L, 3.0

Q30: If the last CPARS was the close out CPARS, i.e. the work was finished, does the government require the CPARS Update form?

A30: The Government cannot tell the contractor how to propose in this situation.

Q31: Could the Government confirm that the information listed in Attachment L-6 is correct for this opportunity?

A31: The table was provided as an example. See Section L, 3.2.

Q32: Would the government validate the Attachment L-8 is correct?

A32: See amendment 0001.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

SECTION L

L-1 CONTENT OF PROPOSALS (SERVICES)

PART A GENERAL INSTRUCTIONS

1.0 GENERAL

Offerors are required to submit sufficient information concerning all evaluation factors to enable Government personnel to fully assess the capabilities of the Offeror to perform all requirements. The proposal must be sufficient in detail and scope to enable evaluation and provide the evaluators a clear understanding of the Offeror’s approach, expertise, and capability as required by the solicitation. Proposals must demonstrate that the Offeror has a thorough understanding of all requirements and associated risks and is able, willing, and competent to devote the resources necessary to meet all requirements. The Offeror shall not alter or rearrange the solicitation. The burden of proof for all substantiation within the proposal rests with the Offeror. Offerors are advised that the Government may incorporate any part of the Offeror’s proposal deemed beneficial to the Government, into the final contract, with or without discussions. Cost/Price information, (e.g., dollar values and/or hourly rates) shall appear only in Volume 4 (Cost/Price).

In presenting material in the proposal, the Offeror is advised that quality of information is more important than quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the responsibility of the Offeror to present enough information to allow the Government to evaluate its proposal without discussions. Unsubstantiated statements that the prospective Offeror understands, can or will comply with the specifications, or paraphrasing the requirements or parts thereof are considered inadequate and may render a rating of unacceptable.

The Offeror shall include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. There is no need to repeat information in more than one volume. The detailed information must be included in the most logical place and summarized and referenced in other areas if an overlap exists. Do not provide elaborate brochures or other presentation material beyond that sufficient to present a complete and effective proposal.

Throughout these instructions, “Offeror” is defined as the prime contractor with its CAGE code identified in Block 15A on Standard Form (SF) 33, Solicitation, Offer, and Award. A “Joint Venture” (JV) is a partnership or teaming arrangement that is formed for the purpose of responding to this solicitation when the prime contractor consists of more than one legal entity. “JV Team Members” are the entities that make up a Joint Venture. The term “entity” is used to mean any or all of the following: prime contractor, JV, JV team members, any subcontractor, and corporate parent, division, subsidiary, or affiliate (e.g., any contractor with a different CAGE Code/DUNS than the Offeror). The following entities are defined as principal entities and only principal entities will be used in the past performance evaluations: (a) the prime contractor; (b) JV Team Members; and (c) other entities that are proposed to perform at least 15% of the proposed total cost/price for the contract. Offerors are advised that in order to demonstrate work commitment, each principal entity must be identified in Volume 4 Cost/Price and associated with a commensurate dollar value.

2.0 PROPOSAL FORMAT AND SUBMISSION

Offerors shall format all proposals using a Times New Roman 12 point normal font (no reduction permitted), single-spaced. The Offeror shall number all pages with volume, paragraph, and page numbers. If the Offeror uses graphs to convey information, the graphs must show enough detail to understand the information described. The Offeror shall present graphs and tables in no smaller than a 10 point font.

2.1 Electronic Submission of Proposal

All volumes of the proposal shall be submitted electronically through the Solicitation Module of the Procurement Integrated Enterprise Environment (PIEE) at https://piee.eb.mil. No other submissions, such as mail, hand-carried, or other electronic system (e.g., DOD SAFE) are authorized by the solicitation unless specifically authorized by the Contracting Officer pursuant to the paragraphs regarding PIEE System outages below. For instructions on how to post an offer, please refer to the Posting Offer demo: https://pieetraining.eb.mil/wbt/sol/Posting_Offer.pdf.

It is the Offeror’s responsibility to follow the registration instructions found on the PIEE website. It is advised that all potential prime Offerors and their subcontractors ensure the proper company points of contact are registered in the site based on their CAGE codes and have the proper roles assigned well in advance of the solicitation closing date. Subcontractors are only required to register in PIEE if they want to submit their proprietary proposal information separate from the prime offer. Documents submitted by the subcontractor directly to the Government must have the prime contractor’s name, CAGE, and RFP number on the first page of the document.

It is also the Offeror’s responsibility to confirm receipt of proposals and all electronic communications. Screen shots of the submission should also be taken to validate a submission was accepted in the PIEE system against this solicitation. The Government is not obligated to search for incorrectly submitted proposals in PIEE.

The submission date for all Volumes shall be no later than the date and time specified in Block 9 of the SF 33 of the RFP.

If there is an unanticipated PIEE System outage within 24 hours of the proposal due date and the outage has interrupted normal Government processes so that proposals cannot be received by the exact time specified in the solicitation, the Contractor shall immediately notify the Contracting Officer. This notification shall occur prior to the proposal submission deadline and shall be made in writing. The notification may be in conjunction with verbal notification, but verbal notification alone shall not be sufficient. The Offeror shall obtain written approval from the Contracting Officer to submit the proposal via an alternate method as shown in the paragraphs below or the Contracting Officer may advise the Offeror that the Government will follow the procedures set forth in FAR 15.208(d) for amending the solicitation closing date.

The following alternate methods may be utilized when there is a PIEE system outage and the Offeror receives authorization from the Contracting Officer:

Contractor Proposals Submitted by Carrier: The Offeror shall submit electronic CD-ROM proposals via United States Postal Service or through a commercial carrier with next day delivery using the address provided below.

Email address: Erika.m.martin6.civ@us.navy.mil

U.S. Postal Service Mailing Address:

Direct Delivery Address (UPS, FedEx, etc.):

Solicitation Number: N6893625R0026

Hand Carried Proposals: Hand carried proposals must be delivered to the address above, attention Contracting Officer, Erin Strand, and/or Contract Specialist, Erika Martin, 760-793-3151. If a proposal or amendment is hand carried, the Contractor must have current base access for delivery of the proposal. Without base access, the Contractor may not get beyond the installation security gate to deliver its proposal. Guards are not authorized to accept proposals. Each Volume shall be on a separate CDROM. Delivery time shall be coordinated with the contracting office to ensure availability to sign for the package.

Regardless of which alternate method is used, the Offeror shall package the CD-ROMs in the most efficient manner possible grouping like volumes to the maximum extent possible. Each Volume shall be on a separate CDROM. The package shall include all proposal volumes including the digitally signed document(s) submitted as part of the Cost/Price Volume. The package shall include a packing slip detailing the contents to include the volume number, title, and copy number. Also, the package shall be stamped or marked “Controlled Unclassified Information” and “Source Selection Information – See FAR 2.101 and 3.104.”

2.1.1 Electronic Proposal Media

The Offeror shall submit all volumes of its proposal electronically and ensure compatibility with the operating system and applications defined in Section 2.1.2 below. The Offeror shall keep the portions of the proposal that contain pricing information separate from the portions of the proposal that do not contain pricing information. For this solicitation, only Volume 4 Cost/Price shall contain cost/price information and shall be delivered in separate files from the remainder of the proposal. The Offeror is responsible for ensuring electronic proposals are virus free in accordance with Section 2.1.4.

2.1.2 Operating System and Applications

The Government uses Microsoft Windows 11 Operating System to access proposals. Offerors shall submit proposal information using the following applications: Microsoft Word 2016, Microsoft Excel 2016, and Microsoft PowerPoint 2016. However, Offerors shall submit letters and other signed documents as a fully searchable Portable Document Format (.pdf) file. Use of other application software for submission of proposals is prohibited.

2.1.3 Hyperlinks

The Offeror shall not use hyperlinks in proposal volumes.

2.1.4 Virus Free Electronic Submission

The Offeror is responsible for ensuring that its electronic proposal is virus free. The Offeror shall certify, in its proposal cover letter, that all electronic proposal information delivered throughout the evaluation (e.g., original proposal submission, responses to evaluation notices, Final Proposal Revisions) are virus free. The Offeror shall specify the software, version, and virus definition used to check the data

2.1.5 Multimedia

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.

2.1.6 File Naming Conventions

Valid extensions for files using their associated applications follow:

The Offeror shall follow the basic structure of the file naming convention in Table G-1 (Offeror Electronic File Naming Convention) for electronic file submissions (e.g., proposal volumes, attachments, appendices), where “#” represents the sequential numbering of files. Offeror’s shall keep file names short (i.e., under 40 characters) so that the files are accessible on Government share drives. Files with longer names often become corrupt or inaccessible.

The Offeror should provide one folder for each volume or annex, containing all electronic files requested within the volume or annex. Please submit each volume, or annex as one file if possible. Offerors should not provide each section/paragraph as separate files.

The following do not count toward page count: Cover pages, Title pages, Table of Contents pages, Resumes.

Table G-1 Proposal Structure

3.0 PROPOSAL CONTENT AND VOLUMES

The Offeror shall present its proposal information in a manner that facilitates a one-for-one comparison between the information presented and these proposal instructions. Offerors shall structure proposal information such that the proposal paragraph numbers/letters correspond to the proposal instructions paragraph numbers/letters, although the Offeror may add lower tier subparagraphs.

Information submitted as an Annex to a particular proposal volume could include manuals, specifications, plans, procedures, and company policies, as well as other information requested in Section B Specific Instructions and do not count towards the suggested page count.

Cost/price information, (e.g., dollar values and/or hourly rates) shall not be included in any volume other than Volume 4 Cost/Price.

Table G-2 Section L List of Attachments

4.0 PROPOSAL SUBMISSION AND PACKAGING

All Proposals shall be UNCLASSIFIED.

4.1 PROPOSAL SUBMISSION

The submission date for all volumes shall be no later than the date and time specified in Block 9 of Standard Form 33 of the solicitation.

Questions: Offerors may submit questions requesting clarification of solicitation requirements by emailing the contract specialist at Erika.m.martin6.civ@us.navy.mil. It is required that all questions be received within 15 calendar days of the date this solicitation is issued. Each question or comment should reference the applicable document, page number, and paragraph number.

Offerors shall not include any proprietary information in a question, because the Government will provide the question and answer to all potential offerors. All questions must be submitted no later than 12:00 PM Pacific Time on the 15th calendar day after the date that this solicitation is issued. Questions received after the deadline above may be answered at the Government’s sole discretion.

Method of delivery, such as by hand, United States Postal Service or commercial carrier, are not authorized. Offerors will follow the directions for electronic submittal identified in paragraph 2.1.

5.0 CHANGES TO SOLICITATION

The Government will post all amendments to this solicitation at https://www.sam.gov/

Search the database for the solicitation number N6893625R0026

PART B SPECIFIC INSTRUCTIONS

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

1. VOLUME 1 – EXECUTIVE SUMMARY

Note: This volume shall not contain any reference to cost or price aspects of the offer.

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

The purpose of the Executive Summary is to provide the Government with an overview of the Offeror’s entire proposal, excluding cost/price. The Executive Summary volume should be divided into the sections outlined below:

a. Offeror Summary Table

(1) The Offeror shall complete Table ES-1 (Offeror Summary), provided in Attachment L-1 (Executive Summary Tables), according to the instructions within the attachment, and submit it within this section and as a separate electronic file. This table summarizes the Offeror and its entities’ proposed type and level of work, indicating a commitment to that effort during contract performance. Offerors are advised that in order to demonstrate work commitment, each entity identified in Table ES-1 (Offeror Summary) must be identified in Volume 4 (Cost/Price) and associated with a dollar value commensurate with the Percent of Total Proposed Cost/Price identified in Table ES-1 (Offeror Summary). Therefore, this table must be a reflection of what is proposed in Volume 4 (Cost/Price).

(2) For the Past Performance evaluation, contract references that relate to a different CAGE code/DUNS than the proposed entity will be considered if the CAGE code/DUNS was created as a result of a corporate acquisition, reorganization, merger, or other administrative reason and refer to the same division in the same physical location for where the work is being performed or from where the work is being directed in accordance with the proposed roles and responsibilities. All current CAGE Codes/DUNS must appear in Table ES-1 (Offeror Summary Table) which indicates a commitment of work for those entities. To facilitate the Relevancy determination for Past Performance, the Offeror shall provide a written explanation if multiple CAGE codes/DUNS for the same physical location are applicable to one entity. The written explanation shall detail the distinct roles and responsibilities for entities with different CAGE codes/DUNS at the same physical location for where the work is being performed or from where the work is being directed. The description shall include all changes in the organization as a result of a corporate acquisition, reorganization, merger, or other administrative reason and explain how the changes impact the relevance of any contract references provided.

Note: “Place of Performance” for this solicitation pertains to the physical location of the prime or other entities that are deploying personnel or responsible for the work; not the Government site where the work is being performed. If work is being performed at a contractor site, then that would also pertain to Place of Performance.

(3) Additionally, if applicable, the Offeror shall provide a description of the legal relationship between JV entities.

Table ES-1 Offeror Summary

Offeror:

of Entity

b. Relevant Contract Summary Table The Offeror shall complete the Table ES-2 (Relevant Contract Summary) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance for the principal entities. The Offeror shall complete the table according to the instructions within the attachment and submit it within this section and as a separate electronic file. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 3 Table PP-1 (Past Performance Contract Data). For example, the contracts identified as P1, T1, S1, or C1 in the Relevant Contract Summary Table are the same P1, T1, S1, or C1 contracts identified in the Past Performance Contract Data Table.

Table ES-2 Relevant Contract Summary For Past Performance

Offeror:

Reference

P2

P3

T2

T3

T4

S2

S3

S5

* Contracts deleted should be identified in a narrative paragraph following Table ES-2.

c. Technical The Offeror shall provide a succinct summary of what is proposed for each element, describing the approach or the design configuration and/or the proposed solution. In general, the description should be a short paragraph that provides only the factual description of what is proposed without adjectives or discussions of benefit. In a separate paragraph, identify approaches of its proposal that exceed requirements, enhance performance or operations, or reduce risk with benefit to the Government. Specifically identity where in the Technical Volume (e.g., paragraph and page number as a minimum) the details of these approaches are provided.

d. Contract Administration The Offeror shall provide a summary of any exceptions or deviations, and proposed Section H clauses addressed in Volume 5 (Contract Administration).

2. VOLUME 2 - TECHNICAL

Note: This volume shall not contain any reference to cost or price aspects of the offer.

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

Attachment L-2 T-1 Technical Cross Reference Matrix (CRM)

The Offeror shall complete Table T-1 (Technical CRM), provided in Attachment L-2 and submit it as the first page of Volume 2 (Technical), and as a separate electronic file. The Technical CRM is included to help the Offeror develop its proposal and to ensure traceability of Section L paragraphs to the requirements. The Offeror’s Technical CRM may be identical to the one provided or revised to add information. For example, the Offeror’s Technical CRM may cross-reference its proposal volumes, paragraph numbers, and pages to specific solicitation requirements identified within the table, as well as other parts of the proposal that contain relevant information.

Table T-1 Technical Cross Reference Matrix (CRM)

Example: Para 3.1 Note: This column shall address all paragraphs in Section 3.0 of the SOW.

Provide reference to Offeror’s Proposal Volume 2 Technical. Example: Refer to appropriate page number in Offeror’s written proposal

In this volume, provide the information described below:

Throughout the Technical Volume the Offeror should identify any proposed capability, approach or feature that reduces risk inherent in the program. Specifically, explain the benefits to the Government in technical terms and the degree of impact it will have to performance, operations and/or risk. Offerors are advised that any offer to exceed a requirement or to provide a feature with performance and/or operational benefits may be included in the resulting applicable Contract within the proposed cost/price.

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:

· Workforce/Personnel Qualifications/Key Personnel

· Event Scenario Technical Approach

· Organization

· Staffing

· Security

· Transition Plan

· Subcontract Management

2.1 Workforce/Personnel Qualifications/Key Personnel

Workforce

The Offeror shall propose personnel that meet all labor category requirements. Personnel must also have the required minimum level of security clearance as outlined with the solicitation. Submission of an offer hereunder indicates the Offeror’s understanding and agreement that all personnel requirements shall be met throughout contract performance.

Personnel Qualifications See Section L, Attachment L-3, Key and Non-Key Personnel Qualifications, for a list of labor categories and qualifications.

Key Personnel The Offeror shall provide all Key Personnel information in accordance with the content defined in the Key Personnel Qualifications, Attachment L-3, of this solicitation. Note that years of professional experience required by the Key Personnel attachment shall be within the applicable number of years of the solicitation release date. The Offeror’s narrative regarding Key Personnel shall include the following:

My name is ______________ [insert proposed employee’s name]. I agree to work for _____________ [insert company’s name] as a _____________ [insert appropriate labor category title from Attachment L-3] at an hourly rate of $____________ from to [insert current dates]. I can be reached at ____________[insert current phone number] .

2.2 Event Scenario Technical Approach

The Offeror shall provide a technical proposal in accordance with the Event Scenario. The scenario response shall demonstrate that the processes, approaches, and personnel proposed in the scenario are consistent with those responses proposed in Technical Volume Section 2.1. No cost/price information shall be provided for this scenario.

With the information provided below, please provide a detailed plan that satisfies the requirement (layout is at Offeror’s discretion).

Customer is requesting multiple networks to be installed into a new ICD-705 Facility at NAWCWD China Lake, California.

· Drop Info:

• 15 modular workstations and 5 offices, each with 3 drop locations:

• Unclassified (Copper, capable of 1 Gbps)

• Classified (Copper, capable of 1 Gbps)

• ICD-705 (Fiber, capable of 10 Gbps

· Connectivity Info:

• No OSP (outside plant) fiber at the facility.

• Nearest tie point is 500 ft away in an existing telecom manhole.

· Facility Layout

• 3000 sq ft ICD-705 compliant facility (layout is flexible)

• TR/TEF is (12’ x 12’) in secure interior area.

• Workstations arranged in pods or rows, each with 3 drops at desk height.

• Drop Ceiling throughout facility excluding the TR/TEF

Information to include in your response:

· Provide a list and describe the technical codes, regulations, or guidelines associated with performing this task.

· Provide list of required materials and equipment

· Provide an estimate of labor hours required to execute the installation, standard installation crew size 2 technicians.

· Provide procurement timeline

The Offeror shall provide all information and data required to conduct a thorough and complete plan. The Offeror shall provide its approach in accordance with the content defined in the SOW.

2.3 Organization

The Offeror shall address the following:

(a) Provide an overview of its proposed organization, including an organization chart showing interfaces, physical locations, and lines of communication among the Government, the Prime, and its subcontractors. Specifically show where the proposed Key Personnel are located in the organizational chart and their lines of reporting and authority. Also specifically show how proposed lines of responsibility, authority, and communication through which the tasks will be managed.

(b) Provide a description of the duties and responsibilities of contract support functions/activities personnel to be employed on this contract. The description shall describe how the Offeror plans to manage the following examples of contract support functions/activities, if applicable.

Contract support personnel may be proposed to support multiple or single functions. Identify multiple function positions and the anticipated level of effort for each function. The Offeror will be evaluated on its ability to maximize management and resource efficiency. The Offeror shall add any direct hours to be charged for these tasks to the Section B CLINs 0001, 0005, 0009, 0013 and 0017 level of effort, if applicable. Proposing these tasks as direct costs does not necessarily improve efficiency or reduce cost to the Government; as such, Cost Realism analysis may reflect that cost. If any individual performing a contract support function will charge direct, identify the technical task(s) to be performed under each labor CLIN, justifying direct charges and the percentage time to be charged direct. The description shall include whether the individuals are employed full time or part time. If part time, please include the percentage of the work year expected to be billed to the contract. Identify the method used for determining the amount of indirect support required for task orders and show how these costs would be charged, whether direct, or indirect. The Offeror will be evaluated on its ability to maximize management and resource efficiency.

(c) Adequacy of corporate management and resources to support the technical requirements of the solicitation and ability to function as a viable and productive provider of contracted services to the Government.

(d) Proposed management roles of the Offeror’s proposed workforce for this requirement.

(e) Procedures to be taken to ensure quality and cost control.

(f) Processes for managing the requirement from start to finish, including the role of program manager in product/process quality and how these functions are accommodated in the acquisition and overhead structures.

(g) Plan for early identification and resolution of problems.

(h) Identification of potential performance risks and proposed risk mitigation strategies.

2.4 Staffing

The Offeror shall address the following:

(a) Describe the processes used in hiring, recruiting, retaining, and training personnel for both the transition and throughout the life of the contract.

(b) Identify the number of personnel by labor category that will be maintained on staff in order to be ready to respond to emerging task order requirements. Describe the approach used to fill all positions required for each labor category in a time phased staffing chart.

(c) Describe the approach to and timeframes for hiring qualified personnel in order to take on new task orders. Identify the labor pools from which recruiting is expected and demonstrate the ability to hire and train the requisite staff without impacting the level of support.

(d) Describe the approach for the qualification/recruitment that would provide workforce improvements and upgrade the skills of motivated personnel.

(e) Describe the approaches for maintaining technical competence to perform the tasks in the SOW.

2.5 Security

The Offeror shall address the following:

(a) Describe the process, including timelines, for visit requests, and visitor badges, including situations involving shipboard access and foreign travel.

(b) Describe the vetting process for new employees Describe the process to ensure employees maintain appropriate clearances, reporting of derogatory information, and submission of reinvestigations.

(c) Describe the process for ensuring Common Access Cards (CACs), and area access badges (if applicable) are returned to the government when an employee is no longer supporting the contract regardless of the employee’s performance location.

2.6 Transition Plan

The Offeror is required to submit a written narrative delineating a transition plan that ensures a smooth workplace changeover from an incumbent with no loss of service 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;

(b) quality assurance;

(c) training;

(d) risk mitigation strategies;

(e) security requirements to include OPSEC, facility clearances, and base access; and

(f) data transfer.

2.7 Subcontract Management

If proposing subcontractors, the Offeror shall address the following:

(a) Provide the subcontract management strategy for assembling teams, selecting subcontractors, maintaining subcontractor relationships, communicating information to the subcontractor, managing subcontractor performance, and resolving problems. Explain 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.

(b) Discuss the approach to determining the work to be performed in-house and the work to be subcontracted.

(c) Describe how the subcontract management strategy addresses those aspects that will be accomplished through a subcontracting approach, including how the subcontract management strategy will be employed, consistent with the subcontract management processes. Describe the process that will be used to determine the complexity and variety of the work subcontractors are to perform. Describe the process that will be used to ensure maximum practicable small business participation.

(d) If proposing multiple subcontractors, demonstrate the ability to manage large amounts of subcontractors. Provide past/current contracts that are considered relevant under the Past Performance factor that would substantiate the experience related to this effort. Specifically identify the number of subcontractors, the dates of performance, and role and responsibility on that contract.

(e) Describe the value that will be added by proposing subcontractor(s) and how use of subcontractor(s) will not add unnecessary levels of management, impede communication, or delay work completion.

(f) Describe the internal process to fund subcontractors and how that process ensures timely subcontractor payments with no loss of productivity to the Government.

3. VOLUME 3 - PAST PERFORMANCE

Note: This volume shall not contain any reference to the cost or price aspects of the offer.

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

For this volume, the Offeror shall identify all relevant contracts (where for the purpose of these instructions the term contract also refers to delivery order or task order), or those portions of a relevant contract, whose performance is within 5 years of the proposal due date for the principal entities, identified in Table ES-1 (Offeror Summary). The relevant contracts provided for each principal entity shall be relative to its proposed role and responsibilities identified in Table ES-1 (Offeror Summary). Commercial contracts may be included. Offerors shall also identify relevant contracts within the past 5 years of the proposal due date that had any show-cause notices, cure notices, or termination for default. The Offeror shall complete Table ES-2 (Relevant Contract Summary For Past Performance) provided in Attachment L-1 (Executive Summary Tables), for all contracts proposed as relevant for Past Performance.

In Annex A (Final Versions of Previous Statement of Work (SOW)/Performance Work Statement (PWS)/Other Supporting Documentation for Past Performance), the Offeror shall provide electronic copies of the complete final versions of the SOW/PWS or other supporting solicitation/contract documentation from each contract or delivery/task order reference identified in Table ES-2 (Relevant Contract Summary). Annex A should only be provided in electronic format and should not be provided in paper copy. For contract references that contain delivery/task orders, additionally provide the work description for each specific delivery/task order. For contract references where the Offeror performed as a subcontractor, the Offeror shall also provide a complete electronic copy of the SOW/PWS or other documentation of the agreement between the prime and subcontractor that clearly defines the portions of the work effort of the Prime’s SOW/PWS that the Offeror performed as a subcontractor.

Contract Performance Assessment Reporting System (CPARS) and Questionnaires will be the primary customer feedback data used to evaluate the Offeror’s past performance. The Past Performance Information Reporting System (PPIRS) will be the primary method used to retrieve the CPARS for this source selection. For all contracts identified that do not have a CPARS, the Offeror shall forward a copy of Attachment L-4 CPARS Update Questionnaire to that contract’s Procuring Contracting Office (PCO), Administrative Contracting Officer (ACO), and Program Manager (PM); or commercial contractor equivalents. Please forward all questionnaires within 2 weeks from this solicitation’s release date to allow adequate time for the recipient to respond. Note that the Offeror should not reference this solicitation’s number when distributing the past performance questionnaires to customers. The Offeror should include instructions for the customers to send completed questionnaires within two weeks of its receipt via e-mail to the PCO/Contract Specialist. The Offeror shall ensure that all points of contact are current and include an email address and phone number. The Offeror shall not conduct follow-up actions with regard to this questionnaire, other than to confirm receipt by the recipient. The Government may contact customers identified by the Offeror to obtain follow-up Past Performance Information as needed.

Offerors are reminded that the Government reserves the right to use information to evaluate past performance obtained from sources other than those identified by the Offeror. The Government may send additional questionnaires and/or obtain information from sources identified by the Government evaluation team.

0. Authorization Letter(s)

The Offeror should submit a signed “Release of Adverse Past Performance Authorization Letter(s)” with written consent from each principal entity (including JV team members), authorizing the release of adverse past performance information to the Prime. The signed letter(s) should be included in a separate tab within Volume 3 (Past Performance). This authorization letter allows the Government to coordinate past performance issue(s) with the Prime Offeror. For any principal entity (including JV team members) that does not provide an authorization letter with such written consent, the Offeror shall provide point of contact information for each principal entity. This contact information shall include a name, address, phone number, and email address (including JV team members), with whom the Government may coordinate any issues and obtain responses as needed. Offerors are advised that if it does not submit the Release of Adverse Past Performance Authorization Letters with written consent, then the Government will address any past performance issues directly with the principal entity (including JV team members), and the Offeror will forfeit the opportunity to participate in any related discussions.

3.2 Relevant Contract Data

For each contract identified for past performance in Table ES-2 (Relevant Contract Summary) provided under Attachment L-1 (Executive Summary Tables), the Offeror shall complete Attachment L-6 Table PP-1 (Past Performance Contract Data), according to the instructions within the attachment and submit it within this section and as a separate electronic file. Please note that this form is a summary of the principal entities’ relevant contract data. All detailed information and comparative analysis of the past performance contract references to this solicitation’s requirements shall be provided in Volume 3 (Past Performance), Section 3.3 (Evaluation), of the Offeror’s proposal. The contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing Volume 3 (Past Performance) and all contract references shall be numbered the same throughout all of the Offeror’s proposal volumes (i.e., the contracts identified as P1, S1, T1, C1 etc.)

If a contract has D.O.s/T.O.s, provide a separate contract reference and separate PP-1 tab for each D.O/T.O. The Offeror may use one reference number/PP-1 tab for multiple D.O.s/T.Os if they are the same work effort and performed under the same CPAR; however, identify the dollar amount and period of performance for each. Do not provide a contract reference to the basic contract.

In general, recent performance will be considered a better indicator of future performance. If the Offeror is proposing as a JV, the Offeror should provide the relevant contracts for the JV as a whole, and for each team member of the JV.

Table PP-1 Past Performance Contract Data

Offeror Name:

Period of performance – End Date

Dollar value of contract (Annualized)

Brief Work Description and/or Program Responsibility for this past contract.