R

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

NUMBER IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

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

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

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

16C. DATE SIGNED

Previous edition unusable STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE PAGE OF PAGES

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than Item 6) CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBE

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

Solicitation/Contract Form Continuation

The following changes have been made:

INFORMATION FROM TO

Response Due Date 18 May 2026 25 May 2026

N0018926RL0140002

List of Contract Documents, Exhibits, or Attachments

The following attachments were added:

NCTAMS LANT AOR_Commercial Telephone Contract RFI_PWS_REV4

Miscellaneous text in this section has been modified to:

PERFORMANCE WORK STATEMENT (PWS)

NCTAMS LANT

COMMERCIAL TELEPHONE CONTRACT

1.0 INTRODUCTION: This Performance Work Statement requires the development and sustainment of a comprehensive commercial telephone contract in the Naval Computer and Telecommunications Area Master Station Atlantic (NCTAMS LANT) Area of Operations (AOR). The PWS defines the contractor efforts required to provide commercially available integrated voice services via Central Office based, dial tone facilities to defense activities.

2.0 BACKGROUND: NCTAMS LANT provides critical base level communications to base users and supported commands and is integral to the mission for all users onboard Naval Air Station (NAS) Key West, Naval Station (NAVSTA) Great Lakes, NAVSTA Norfolk, Joint Expeditionary Base (JEB) Little Creek, Naval Support Activity (NSA) Mechanicsburg, NSA Philadelphia, and Philadelphia Navy Yard (PNYA) Philadelphia by providing critical commercial telephone services to all users and supported commands. Those commands have many critical National Defense missions to support operational and readiness requirements for Department of War (DoW), Department of Homeland Security (DHS), National Guard units, federal agencies and allied forces.

3.0 SCOPE OF WORK: NCTAMS LANT requires a comprehensive contract for the complete replacement of existing Time- Division Multiplexing (TDM) commercial telephony services. This effort shall include the installation and long-term support for a new system supporting approximately 19,773 endpoints at the specified locations The core requirement is for an Internet Protocol (IP) based solution, with Voice over IP (VoIP) being the preferred implementation.

3.0.1 ALTERNATIVE AND HYBRID SOLUTIONS: While VoIP is the preferred solution, NCTAMS LANT will consider alternative or hybrid technological solutions if specific site conditions or mission requirements warrant them. Technologies such as Radio Frequency (RF), cellular, satellite, or other secure wireless communications may be deemed acceptable. Any proposed alternative must be fully justified by the offeror, detailing how it meets the requirement for seamless and reliable communication while integrating with the overall IP-based infrastructure.

3.0.2 FEDERAL RISK AND AUTHORIZATION MANAGEMENT PROGRAM (FEDRAMP) REQUIREMENTS: If the proposal includes a Cloud based solution, the vendor must have at least a DoW Moderate Impact FedRAMP Authorization To Operate (ATO) issued by the General Services Administration (GSA). Moderate Impact category is based on the federal government mission and the Federal Information Processing Standard (FIPS) Publication 199. All work and requirements, such as the deliverables, stated in this PWS shall specially address how your firm complies with DoW impact-level 2 (moderate) alongside the FedRAMP ATO/certification.

If the proposal includes a Cloud Service Offering (CSO), it must comply with the current FedRAMP 20x framework and the DoD Cloud Computing Security Requirements Guide (CC SRG). At a minimum, the proposed CSO must possess the unified "FedRAMP Authorized" designation at the Moderate baseline, which is based on the NIST SP 800-53 (Revision 5) control set. The vendor must provide evidence of this authorization as part of their proposal. All work and requirements stated in this PWS must comply with the security controls required for this authorization level.

3.1.1 NAS Key West - 1113 endpoints to include IP replacement for seven (7) T-1 circuit and five (5) ISDN circuits.

3.1.1.1 Features:

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E9111

e. Call Waiting

f. Call Hold

g. Call Forwarding Busy Line

h. Call Forward Don't Answer - All Calls

i. Call Forward Variable

j. Call Transfer

k. Three-Way Calling

l. Direct Inward Dialing

m. Direct Outward Dialing

3.1.1.2 Key West Specific Features

a. Airfield Crash Net Support: The proposed solution must support and seamlessly integrate with the existing

Primary and Secondary Crash Alarm Systems at NAS Key West. The system must provide instant, simultaneous, non-blocking voice conferencing with priority override to all designated emergency response endpoints (e.g., ATC, Fire/Rescue, Medical) without degradation of service.

3.1.2 NAVSTA Great Lakes - 2,300 endpoints

3.1.2.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E9111

e. Call Waiting

f. Call Hold

g. Call Forwarding Busy Line

h. Call Forward Don't Answer - All Calls

i. Call Forward Variable

j. Call Transfer

k. Three-Way Calling

l. Direct Inward Dialing

m. Direct Outward Dialing

3.1.3 NAVSTA Norfolk - 10,560 endpoints

3.1.3.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E9111

e. Call Waiting

f. Call Hold

g. Call Forwarding Busy Line

h. Call Forward Don't Answer - All Calls

i. Call Forward Variable

j. Call Transfer

k. Three-Way Calling

l. Direct Inward Dialing

m. Direct Outward Dialing

3.1.4 JEB Little Creek - 4,100 endpoints

3.1.4.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E9111

e. Call Waiting

f. Call Hold

g. Call Forwarding Busy Line

h. Call Forward Don't Answer - All Calls

i. Call Forward Variable

j. Call Transfer

k. Three-Way Calling

3.1.5 NSA Mechanicsburg - 425 endpoints

3.1.5.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E9111

e. Call Waiting

f. Call Hold

g. Call Forwarding Busy Line

h. Call Forward Don't Answer - All Calls

i. Call Forward Variable

j. Call Transfer

k. Three-Way Calling

3.1.6 NSA Philadelphia - 350 endpoints

3.1.6.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E9111

e. Call Waiting

f. Call Hold

g. Call Forwarding Busy Line

h. Call Forward Don't Answer - All Calls

i. Call Forward Variable

j. Call Transfer

k. Three-Way Calling

3.1.7 PNYA - 925 endpoints

3.1.7.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E9111

e. Call Waiting

f. Call Hold

g. Call Forwarding Busy Line

h. Call Forwarding Don't Answer - All Calls

i. Call Forward Variable

j. Call Transfer

k. Three-Way Calling

4.0 System Compatibility and Compliance Requirements

The vendor's solution must be fully compatible and interoperable with the current Information Systems Platform (ISP) infrastructure and end-user instruments at each location. The solution will operate on an independent vendor owned/maintained distribution network and is not expected to interface directly with existing legacy or conventional voice sub-systems. However, it must support all functional and interoperability requirements necessary for reliable connectivity to end-user devices, ISP integration, and provide essential services such as Next Generation 911 (NG911), and crash nets, where applicable.

4.1 System Features: The system must support DoW-specific features including, but not limited to, Automatic Call Distribution (ACD), Uniform Call Distribution (UCD), Call Trace, Pre-Set Conference, call forwarding and voice mail availability.

4.2 End-User Instruments and Equipment: The solution should support continued use of various existing endpoint types including digital and Internet Protocol (IP) phones, Video Teleconferencing (VTC) systems, Secure Terminal Equipment (STE), Voice over Secure IP (VoSIP) devices, TSG-6 approved phones, voice mail systems, and other approved peripheral devices.

4.3 Auxiliary and Collaborative Voice Systems: The system should interoperate with all currently deployed voice auxiliary and collaborative systems, including but not limited to: Enhanced 911 (E-911), Primary Crash Net (PCN), and Secondary Crash Net (SCN). Compliance with all emergency communication requirements is mandatory, including NG911 and 988 services.

4.4 NG911 Integration: The vendor shall interface with NG911 infrastructure to enable advanced emergency communications features including text-to-911, multimedia messaging, and real-time data sharing. The NG911 implementation shall integrate seamlessly with existing 911 and E911 services and support accurate station-level location identification and routing to the appropriate Public Safety Answering Point (PSAP), in accordance with Kari's Law and the Ray Baum's Act. Interoperability with all listed voice auxiliary systems is required, and the system must enable efficient and reliable multi-platform emergency communications.

4.5 The vendor shall be responsible for delivering reliable commercial telephone services with a minimum service availability of 99.9% per calendar month, excluding government-approved maintenance windows. The vendor shall maintain and operate their solution to ensure consistent voice service delivery to all government-designated endpoints.

5.0 Billing/Invoicing Reports: In addition to the submission requirements below, the contractor shall ensure the documents /reports are made available through a contractor portal for the Government to access on an as needed basis.

5.1 Monthly Invoices. The contractor shall bill in arrears on a monthly basis in accordance ith this PWS and the terms and conditions contained within the contract. The contractor shall utilize Wide Area Workflow (WAWF) to submit invoices and receiving reports electronically. Monthly invoices shall be submitted through WAWF at the task order level. Upon receipt of a task order the contractor shall establish an account number specific to that task order. Additional requirements are as follows:

5.1.1 Monthly invoices shall reflect all charges from the first day of the month to the last day of the month. The contractor shall charge for all services, features and equipment within one billing cycle after the services are rendered.

5.1.2 The contractor shall provide a monthly detailed invoice report for each account/task order. The contractor shall ensure that each detailed invoice contains all pricing components in sufficient detail to reconcile the charges with completed orders or actual usage. The contractor shall ensure that all charges, credits and debits are shown on the invoice. The detailed invoice report shall be provided electronically in both PDF and excel format and may be required to be attached to each WAWF invoice as substantiating documentation.

5.1.3 Monthly invoices shall reflect only charges for the current month of service. Any unpaid balances from prior periods shall not carryover to future invoices. Any unpaid balances shall be reconciled on a month to month basis. The Government shall not be double billed for the same services.

5.1.4 For other reimbursable charges, the contractor shall ensure that the invoices reflect the contractor's actual charge for a specific service order. The Government will not pay any charges that are not agreed upon between the contractor and the Government point-of-contact, and that are not specifically stated in the service order. Examples of other reimbursable charge include but are not limited to the following: line connection, installation service charge and "add" service.

5.1.5 The Government reserves the right to withhold a partial or entire payment of an invoice in dispute as detailed in FAR 52.232-1 (Payments).

5.1.6 The Federal, State and Local Government Taxes, Fees, Surcharges, and Tariffs Not to Exceed Line Item established in the Pricing Spreadsheet shall account for any and all applicable taxes, fees and surcharges at the current prevailing rates in accordance with applicable law. To ensure these rates remain accurate during the term of the contract, the contractor shall provide substantiating documentation detailing the prevailing rates with each invoice. Each invoice shall contain the total amount and a breakdown of each service charge so that the Government may distinguish the taxes, fees and surcharges and verify that they are being billed in accordance with the prevailing rates.

5.1.7 The contractor shall prepare and deliver a Monthly Statement Report. The report is to be cumulative over the life of the Delivery Order and shall show changes during the current reporting period with respect to the previous reporting period.

6.0 PERIOD OF PERFORMANCE: The period of performance for this requirement is:

Ordering Period 1 is 01 February 2027 through 31 January 2028

Ordering Period 2 is 01 February 2028 through 31 January 2029

Ordering Period 3 is 01 February 2029 through 31 January 2030

Ordering Period 4 is 01 February 2030 through 31 January 2031

Ordering Period 5 is 01 February 2031 through 31 January 2032

FAR clause 52.217-8 Ordering Period is 01 February 2032 through 31 July 2032

6.1 For this Performance Work Statement, "business days" shall be construed to mean all weekdays excluding the eleven Government holidays to include New Years' Day, Dr. Martin Luther King, Jr. Day, President's Day, Memorial Day, Juneteenth, July 4th, Labor Day, Columbus Day, Veteran's Day, Thanksgiving Day, and Christmas Day.

7.0 LOCATION OF SERVICES: Below are the contract service locations:

Naval Air Station (NAS) Key West, Florida, (FL).

Naval Station (NAVSTA) Great Lakes, Illinois, (IL).

NAVSTA Norfolk, Virginia (VA).

Joint Expeditionary Base (JEB) Little Creek, Virginia, (VA).

Naval Support Activity (NSA) Mechanicsburg, Pennsylvania (PA).

NSA Philadelphia, Pennsylvania (PA).

Philadelphia Naval Yard Annex (PNYA) Pennsylvania, (PA).Technical Points of Contact

7.1 Technical Points of Contract (TPOC): Below are NCTAMSLANT BCO (TPOC)

Naval Air Station (NAS) Key West, Florida, (FL)- Shannon Cox - shannon.c.cox.civ@us.navy.mil Naval Station (NAVSTA) Great Lakes, Illinois, (IL)- Greg Powroznik - greg.m.powroznik.civ@us.navy.mil NAVSTA Norfolk, Virginia (VA)- Lachana Hill - lachana.j.hill.civ@us.navy.mil Joint Expeditionary Base (JEB) Little Creek, Virginia, (VA)- Lachana Hill - lachana.j.hill.civ@us.navy.mil Naval Support Activity (NSA) Mechanicsburg, Pennsylvania (PA)- Jewanna Owens - jewanna.f.owens.civ@us.navy.mil NSA Philadelphia, Pennsylvania (PA)- Jewanna Owens - jewanna.f.owens.civ@us.navy.mil Philadelphia Naval Yard Annex (PNYA) Pennsylvania, (PA)- Jewanna Owens - jewanna.f.owens.civ@us.navy.mil

8.0 Service-Contractor Reporting

9.0 Contractor Unclassified Access to Federally Controlled Facilities, Sensitive Information, Information

10.0 Technology (IT) Systems or Protected Health Information

Homeland Security Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors. The Deputy Secretary of Defense Directive-Type

Memorandum (DTM) 08-006 - "DOD Implementation of Homeland Security Presidential Directive - 12 (HSPD12)" dated November 26, 2008 (or its subsequent DOD instruction) directs implementation of HSPD-12. This clause is in accordance with HSPD-12 and its implementing directives.

APPLICABILITY

This clause applies to contractor employees requiring physical access to any area of a federally controlled base, facility or activity and/or requiring access to a DON or DOD computer/network/system to perform certain unclassified sensitive duties. This clause also applies to contractor employees who access Privacy Act and Protected Health Information, provide support associated with fiduciary duties, or perform duties that have been identified by

DON as National Security Position, as advised by the command security manager. It is the responsibility of the responsible security officer of the command/facility where the work is performed to ensure compliance.

Each contractor employee providing services at a Navy Command under this contract is required to obtain a 5512 Defense Biometric Identification System (DBIDs). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.

ACCESS TO FEDERAL FACILITIES

Per HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this clause will require a 5512 DBIDs. When access to a base, facility or activity is required, contractor employees shall in-process with the Navy Command's Security Manager upon arrival to the Navy Command and shall out-process prior to their departure at the completion of the individual's performance under the contract.

ACCESS TO DOD IT SYSTEMS

In accordance with SECNAV M-5510.30, contractor employees who require access to DON or DOD networks are categorized as IT-I, IT-II, or IT-III. The IT-II level, defined in detail in SECNAV M-5510.30, includes positions, which require access to information protected under the Privacy Act, to include Protected Health Information (PHI). All contractor employees under this contract who require access to Privacy Act protected information are therefore categorized no lower than IT-II. IT Levels are determined by the requiring activity's Command Information Assurance Manager.

Contractor employees requiring privileged or IT-I level access, (when specified by the terms of the contract) require a Single Scope Background Investigation (SSBI) which is a higher level investigation than the National Agency Check with Law and Credit (NACLC) described below. Due to the privileged system access, a

SSBI suitable for High Risk public trusts positions is required. Individuals who have access to system control, monitoring, or administration functions (e.g. system administrator, database administrator) require training and certification to Information Assurance Technical Level 1, and must be trained and certified on the Operating System or Computing Environment they are required to maintain.

Access to sensitive IT systems is contingent upon a favorably adjudicated background investigation. When access to IT systems is required for performance of the contractor employee's duties, such employees shall in-process with the Navy Command's Security Manager and Information Assurance Manager upon arrival to the Navy command and shall out-process prior to their departure at the completion of the individual's performance under the contract.

Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. The decision to authorize access to a government IT system/network is inherently governmental. The contractor supervisor is not authorized to sign the SAAR-N; therefore, the government employee with knowledge of the system/network access required or the COR shall sign the SAAR-N as the "supervisor".

The SAAR-N shall be forwarded to the Navy Command's Security Manager at least 30 days prior to the individual's start date.

Failure to provide the required documentation at least 30 days prior to the individual's start date may result in delaying the individual's start date.

When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. The Contractor's Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

INTERIM ACCESS

The Navy Command's Security Manager may authorize issuance of a 5512 DBIDs and interim access to a DON facilities upon a favorable review of the investigative questionnaire and advance favorable fingerprint results. When the results of the investigation are received and a favorable determination is not made, the contractor employee working on the contract under interim access will be denied access to the computer network and this denial will not relieve the contractor of his/her responsibility to perform.

DENIAL OR TERMINATION OF ACCESS

The potential consequences of any requirement under this clause including denial or termination of physical or system access in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have unclassified access to a federally controlled facility, federally-controlled information system/network and/or to government information, meaning information not authorized for public release.

CONTRACTOR'S SECURITY REPRESENTATIVE

The contractor shall designate an employee to serve as the Contractor's Security Representative. Within three workdays after contract award, the contractor shall provide to the requiring activity's Security Manager and the

Contracting Officer, in writing, the name, title, address and phone number for the Contractor's Security Representative. The Contractor's Security Representative shall be the primary point of contact on any security matter. The Contractor's Security Representative shall not be replaced or removed without prior notice to the Contracting Officer and Command Security Manager.

BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR

CONTRACTORS ASSIGNED TO NATIONAL SECURITY POSITIONS OR PERFORMING SENSITIVE DUTIES

Navy security policy requires that all positions be given a sensitivity value based on level of risk factors to ensure appropriate protective measures are applied. Navy recognizes contractor employees under this contract as NonCritical

Sensitive [ADP/IT-II] when the contract scope of work require physical access to a federally controlled base, facility or activity and to perform unclassified sensitive duties. This designation is also applied to contractor employees who access Privacy Act and Protected Health Information (PHI), provide support associated with fiduciary duties, or perform duties that have been identified by DON as National Security Positions. At a minimum, each contractor employee must be a US citizen and have a favorably completed NACLC to obtain a favorable determination for assignment to a non-critical sensitive or IT-II position. The NACLC consists of a standard NAC and a FBI fingerprint check plus law enforcement checks and credit check. Each contractor employee filling a noncritical sensitive or IT-II position is required to complete: SF-86 Questionnaire for National Security Positions (or equivalent OPM investigative product)

Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission) Original Signed Release Statements Failure to provide the required documentation at least 30 days prior to the individual's start date shall result in delaying the individual's start date. Background investigations shall be reinitiated as required to ensure investigations remain current (not older than 10 years) throughout the contract performance period. The Contractor's

Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required.

The Contractor employees shall accurately complete the required investigative forms prior to submission to the Navy Command Security Manager. The Navy Command's Security Manager will review the submitted documentation for completeness prior to submitting it to the Office of Personnel Management (OPM). Suitability/security issues identified by the Navy may render the contractor employee ineligible for the assignment.

An unfavorable determination made by the Navy is final (subject to SF-86 appeal procedures) and such a determination does not relieve the contractor from meeting any contractual obligation under the contract. The Navy

Command's Security Manager will forward the required forms to OPM for processing. Once the investigation is complete, the results will be forwarded by OPM to the DON Central Adjudication Facility (CAF) for a determination.

If the contractor employee already possesses a current favorably adjudicated investigation, the contractor shall submit a Visit Authorization Request (VAR) via the National Background Investigation System (NBIS) or a hard copy VAR directly from the contractor's Security Representative. Although the contractor will take NBIS "Owning" role over the contractor employee, the Navy Command will take NBIS "Servicing" role over the contractor employee during the hiring process and for the duration of assignment under that contract. The contractor shall include the IT Position Category per SECNAV M-5510.30 for each employee designated on a VAR. The VAR requires annual renewal for the duration of the employee's performance under the contract.

BACKGROUND INVESTIGATION REQUIREMENTS AND SECURITY APPROVAL PROCESS FOR

CONTRACTORS ASSIGNED TO OR PERFORMING NON-SENSITIVE DUTIES

Contractor employee whose work is unclassified and non-sensitive (e.g., performing certain duties such as lawn maintenance, vendor services, etc.) and who require physical access to publicly accessible areas to perform those duties shall meet the following minimum requirements: Must be either a US citizen or a US permanent resident with a minimum of 3 years legal residency in the

United States (as required by The Deputy Secretary of Defense DTM 08-006 or its subsequent DOD instruction) and Must have a favorably completed National Agency Check with Written Inquiries (NACI) including a FBI fingerprint check prior to installation access. To be considered for a favorable trustworthiness determination, the Contractor's Security Representative must submit for all employees each of the following:

SF-85 Questionnaire for Non-Sensitive Positions

Two FD-258 Applicant Fingerprint Cards (or an electronic fingerprint submission)

Original Signed Release Statements

The contractor shall ensure each individual employee has a current favorably completed National Agency Check with Written Inquiries (NACI) or ensure successful FBI fingerprint results have been gained and investigation has been processed with OPM.

Failure to provide the required documentation at least 30 days prior to the individual's start date may result in delaying the individual's start date.

* Consult with your Command Security Manager and Information Systems Security Manager for local policy when

IT-III (non-sensitive) access is required for non-US citizens outside the United States

Addendum to 52.212-1, Instructions to Offerors - Commercial Products and Commercial Services

Miscellaneous text in this section has been modified to:

The Government intends to award up to seven single Indefinite-Delivery, Indefinite-Quantity (IDIQ) Contracts with Firm Fixed-Price (FFP) provisions as a result of this solicitation in accordance with FAR Part 12, FAR Part 15, and FAR Subpart 16.5. Award will be made to that offeror whose proposal represents the best value to the Government under the selection criteria set forth in this solicitation. The Government intends to evaluate proposals and award multiple contract(s) based on initial proposals. Therefore, the offeror's initial proposal should contain the offeror's best terms from a Technical, Past Performance, Small Business Participation Plan and Price standpoint. The Government reserves the right to award a FFP contract to other than the lowest priced offeror; award a FFP contract without discussions; or award a FFP contract after discussions, whichever is in the best interest of the Government.

The Government intends for a single contractor to perform the services in each service location (i.e. multiple contractors will not be performing in the same service location). The contractor chosen for each service location will be the responsible offeror whose proposal represents the best value after evaluation in accordance with the factors in the solicitation. The offeror's proposal shall be in the form prescribed by, and shall contain a response to each of the areas identified in Section L.

An offeror may be chosen for multiple service locations, if determined to be the best value for that particular location (i.e. each location is not required to have a different contractor from the others). In such cases, an offeror may receive multiple contracts for multiple service locations; or multiple service locations may be covered by a single contract awarded to a single vendor, if that vendor was chosen for those locations.

QUESTIONS: Offerors may submit questions regarding clarification of solicitation requirements to Jim Keegan and Samantha Ballance via email at and samantha.a.ballance.civ@us.navy.mil. It is requested that all questions be received by byjames.p.keegan7.civ.@us.navy.mil 05 May 2026 1000

, as time may not permit responses to questions received after that date to be prepared and issued prior to receipt of proposals.Eastern Time

SUBMISSION OF PROPOSALS

(1) Proposals shall be submitted electronically no later than the due date of the solicitation to Jim Keegan and Samantha Ballance via email at james.p.keegan7.civ.@us.navy.mil and samantha.a.ballance.civ@us.navy.mil Offerors shall comply with the detailed instructions for the format and content of the proposals contained herein; proposals that do not comply may be considered unacceptable and may render the proposal ineligible for award. All electronic files and versions of offerors proposals shall be compatible with the current release of Adobe Acrobat and Microsoft Office Suite version 2016. The offeror shall be responsible for ensuring that their electronic proposals are virus free.

(2) Proposals shall specify which service location(s) the offeror is bidding on (if bidding on multiple locations, then specify which ones):

Location

Norfolk

PNYA

Mechanicsburg

Philadelphia

Little Creek

Key West

N0018926RL0140002

mailto:james.p.keegan7.civ.@us.navy.mil mailto:james.p.keegan7.civ.@us.navy.mil mailto:james.p.keegan7.civ.@us.navy.mil

Great Lakes

If bidding on multiple locations, the price proposal must provide complete pricing for each location.

(3) Volumes I & II - Technical Approach and Past Performance These volumes shall address Technical Approach and Past Performance and include all information required for proposal evaluation. These volumes of the proposal shall exclude any pricing information. Proposals shall include the following legend on each page:

Source Selection Information See FAR 2.101 and FAR 3.104

(4) Volume III - Small Business Participation Plan (all Offerors) and Volume V - Small Business Subcontracting Plan (other than small business offerors only) These volumes shall address the Small Business Participation Approach and Small Business Subcontracting Plan (if applicable) include all information required for proposal evaluation. Each page of each copy shall be affixed with the following legend:

Source Selection Information See FAR 2.101 and FAR 3.104

(5) Volume IV - Price Proposal This volume shall include the completed solicitation documents and a complete and detailed price breakdown with all supporting information. If bidding on multiple service locations, this volume must contain complete pricing for each location. Each page of each copy shall be affixed with the following legend:

Source Selection Information See FAR 2.101 and FAR 3.104

REQUIREMENTS FOR PROPOSAL CONTENT

The offer should contain the following items in addition to other information required by this solicitation. The cover page should indicate the following:

Title of the proposal Volume Number (I, II, III, IV, or V) Proposal Category (Factor/Sub-factor) Request for Proposal Number Name and Address of Offeror, CAGE Code, EUI number, and applicable Tax I.D. Number (TIN) Point of Contact name, telephone number, and email address Proposal valid until performance start date Name the service location the offeror is proposing on (see table above)

Proposals shall be prepared in five (5) separate and distinct volumes:

Volume I - Factor I: Technical Approach Volume II - Factor II: Past Performance Volume III - Factor III: Small Business Participation Plan (all offerors) Volume IV - Factor IV: Price Volume V - Small Business Subcontracting Plan (other than small business offerors only)

Table of Contents: The table of contents should provide sufficient detail as to allow the important elements to be easily located.

1. Requirements for Style: Each offeror shall submit a proposal that clearly and concisely describes and defines the contractor's response to the requirements contained in the RFP. Unnecessary elaboration or other presentations beyond that sufficient to present a complete and effective proposal are not desired and may be construed as an indication of the offeror's lack of understanding of cost consciousness. The proposal shall contain all the pertinent information in sufficient detail in the one area of the proposal where it contributes most critically to the discussion of the same information. When necessary, the offeror shall refer to the initial discussion and identify its location within the submitted proposal.

2. Proposal Page Limitations

Volumes I, II, & III Non-Price Proposal and Volume V Small Business Participation Plan (and, if applicable, Small Business Subcontracting Plan) - The following page limitations are established:

Title Proposal Quantities Page Limit*

Factor I: Technical 1 Electronic Submission 12 Pages

Factor II: Past Performance 1 Electronic Submission 12 Pages

Factor III: Small Business Participation Plan

1 Electronic Submission No limit

Small Business Subcontracting Plan 1 Electronic Submission No limit

All submission and attachments shall be in Microsoft Office Suite. Submissions are page limited to the maximum number of pages as defined above.

These page limitations are inclusive of the executive summary and any charts, diagrams, and/or other graphics. Graphics (including tables) in the proposal may use an alternative font with 8-point size type or larger. Each "page" is defined as one sheet, 8 1/2 "x 11", with at least one inch margins on all sides, using a font with a font size of 12 or greater (e.g., "Times New Roman" style with 12-point font), and shall be in portrait orientation.

Lines shall, at a minimum, be selected as single-spaced in Microsoft Word with Microsoft Word Normal character spacing. Pages shall be consecutively numbered. Multiple pages, double pages, two-sided pages, or foldouts will count as an equivalent number of 8 1/2" x 11" pages. The offeror is permitted to submit no more than one page for each of the following, which will not be included in the page count: a cover sheet, list of tables, list of figures, compliance matrix, table of contents, tabs, and dividers.

Volume IV - Price Proposal - is not page limited.

Title Proposal Quantities Limit* Software

Factor IV, Price 1 Electronic Submission No limit Microsoft Excel

The Price Proposal is not page limited; however, the Price Proposal is to be strictly limited to price information and completed solicitation documents as described in the General Section at the beginning of this text.

* Page limits represent the maximum pages the Government will evaluate and are not construed as de facto standards for the amount of material expected in the proposal.

Pages submitted in excess of the page limitations described within will not be evaluated.

Volume I, Factor I - Technical Approach

The offeror shall provide a technical approach which demonstrates an understanding of the requirement and details how the offeror intends to perform the required tasks and provide the specific services and requirements identified in PWS sections 3.0 and 4.0 and one or more of the following sections: 3.1.1, 3.2.1, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.1.7.

Volume II, Factor II - Past Performance

To demonstrate its past performance, the offeror shall identify up to three (3) of its most relevant contracts performed within five (5) years of the solicitation issuance date. Those contracts must reflect at least one year of completed performance within the five years prior to the closing date of this solicitation. Offerors shall provide a detailed explanation demonstrating the relevance of the contracts to the requirements of the solicitation.

To demonstrate its past performance, the offeror shall identify up to three (3) of its most relevant contracts within the past (5) five years from the solicitation closing date. In addition, performance data will only be assessed for those references demonstrating at least one year of completed performance within the five (5) years prior to the closing date of this solicitation. Offerors shall provide a detailed explanation demonstrating the relevance of the contracts to the requirements of the solicitation. For purposes of this solicitation, a contract is defined as a single contract or a single task order placed under an ID/IQ contract, a Blanket Purchase Agreement (BPA), or a Federal Supply Schedule. If an offeror submits the IDIQ contract, FSS contract, or BPA itself as a reference, then the offeror must identify: a) the total number of orders actually awarded to the offeror during the ordering period in the past five (5) years from the solicitation closing date; and b) the total dollar amount of those orders. The total dollar amount shall be the sum of the orders actually awarded, not the contract maximum or ceiling. Orders is defined as either delivery orders (DOs), task orders (TOs), technical direction letters (TDLs), and/or technical area tasks (TATs) placed under an ID/IQ or BPA or Federal Supply Schedule contract.

Orders must also meet the recency requirements stated above: each order must have been performed within five (5) years of the solicitation closing date. If an offeror submits an IDIQ contract, FSS contract, or BPA itself as a reference, the ordering period must be at least one (1) year in length and any ordering period prior to the five-years before the solicitation date will not be considered. If an IDIQ contract, FSS contract, or BPA itself is submitted as a reference, the offeror shall state the specific experience claimed from the orders (i.e. the offeror shall identify what work was actually completed on the orders and the relevance to this solicitation, as opposed to generically stating that orders were merely awarded). A Past Performance example that does not provide the level of detail required may not be evaluated.

If a proposed subcontractor's past performance is provided as part of the three (3) of its most relevant contracts or efforts, the percentage and type of work to be done by the subcontractor on the solicitation requirement must be stated. The offeror's submittal shall also detail clearly the aspects of the work in the solicitation that the subcontractor is proposed to perform. A Past Performance example which does not detail clearly the aspects of the work in the solicitation that the subcontractor is proposed to perform may not be evaluated.

If the prime offeror or intended subcontractor/partner submits a past performance example in which it served as a subcontractor, the prime/sub/partner shall detail clearly the work that it performed and the magnitude (dollar value) of that subcontracted work only. A Past Performance example that does not differentiate between the overall contract effort and the subcontractor effort may not be evaluated.

The past performance of subcontractors who will be performing major or critical aspects of the solicitation will be considered as highly as a prime contractor's past performance.

Failure of offerors to provide the required information and level of specificity may result in the contract reference not being evaluated.

With respect to joint ventures, the procuring activity will consider work done individually by each member of the joint venture as well as any work done by the joint venture itself previously. Joint venture references must meet the temporal requirements described in section L (within five years and must reflect at least one year of completed performance prior to the closing date of this solicitation). Additionally, if a joint venture member submits a past performance reference, the joint venture member shall detail clearly the work that it performed in that effort and the magnitude (dollar value) of that work. A reference that does not differentiate between the overall contract effort and the joint venture member's effort for that reference will may not be evaluated. The past performance of a joint venture member who will be performing major or critical aspects of the solicitation will be considered as highly as the joint venture's past performance.

The references will be evaluated in the in order to allow the offerors who may not have the entire scope and magnitude of the requirementaggregate under one individual contract to still be evaluated for quality if past performance with the full scope and magnitude of the requirement can be demonstrated within the allotted number of references as described above.

The offeror shall complete a "Past Performance Information Form" for each reference submitted. The form is an attachment to the solicitation.

In addition to the information requested above, offerors shall contact their past performance references and request that each reference complete the Past Performance Report Form attached to the solicitation and e-mail the completed survey form directly to James Keegan and Samantha Ballance via email to and samantha.a.ballance.civ@us.navy.mil by the DUE DATE OF THIS SOLICITATION. The james.p,keegan7.civ@us.navy.mil Government reserves the right to consider past performance report forms received after the due date of the solicitation and to contact references for verification or additional information.

Volume III, Factor III- Small Business Participation Plan lAl offerors, h e d l , e d o e a n g o s bot larg an smal businesses ar require t provid Small Business Participation Pla respondin t the element below:

The t o h l s s e y exten t whic smal busines concern ar specificall identified;

The f t o e l s s r e s l e extent o commitmen t us smal busines concern (fo example, enforceabl commitment wil b d e y n eweighte mor heavil tha non-enforceabl ones);

The complexity and variety of the work small firms are to perform;

o Past e f e r n g h s f s t R , n f l s , performanc o th offero i complyin wit requirement o the clause a FA 52.219-8 Utilizatio o Smal Busines Concerns d , l s gan FAR 52.219-9 Smal Busines Subcontractin Plan;

- When subcontracting possibilities existed on the contracts submitted by the offeror in the Past Performance volume, address to small business concerns, veteran-owned small business concerns, service-whether or not the offeror awarded subcontracts

N0018926RL0140002

mailto:james.p,keegan7.civ@us.navy.mil disabled veteran-owned small business concerns, HUBZone small business concerns, small disadvantaged business concerns, and women-owned small business concerns to the fullest extent consistent with efficient contract performance.

- If utilizing small businesses in current or prior contracts was not practicable, the offeror shall explain why.

- Provide any information substantiating the offeror's track record of utilizing small business on past contracts in detail.

Include, at a minimum, two most recent Summary Subcontract Reports (SSR) from eSRS.

The t f n f l s s n s f e f e l exten o participatio o smal busines concern i term o the valu o th tota acquisition.

Small Business Subcontracting Plan (for other than small businesses only)

Each offeror that is not a small business shall provide a Small Business Subcontracting Plan that contains all elements required by FAR clause 52.219- 9 Alt II (Deviation), and as supplemented by DFARS clause 252.219-7003, by .the closing date and time of this solicitation The small business

Offerors are permitted subcontracting plan is not an evaluation factor and will not be evaluated as part of the formal source selection process.

to submit a master subcontracting plan as long as it is created in accordance with FAR 19.701 and FAR 19.704(b). Small Business Subcontracting Plans are not required from offerors that qualify as small business concerns under NAICS code 517111 with a size standard of 1,500 employees.

It is the goal of this solicitation that prime contractors subcontract with small businesses to the maximum extent practicable. For other-than-small prime contractors, the Small Business Subcontracting Plan goals shall be expressed in terms of whole dollars and percentages based on total planned subcontracting dollars. Of the total planned subcontracting dollars, the Small Business Subcontracting Plan shall include goals for small businesses, small disadvantaged businesses, woman-owned small businesses, HUBZone small businesses, veteran-owned small businesses, and service-disabled veteran-owned small businesses. The Government will consider prior achievement of small business subcontracting plan goals as well as the proposed dollar values and percentages related to this solicitation.

Volume IV, Factor IV - Price

The Price Proposal shall include the completed solicitation documents. The price proposal shall include all elements of price, and such other price information considered appropriate to support the proposal. Vendors are required to complete the Price Spreadsheet Attachment, and any information such as commercial pricing listings or any information, which can be used in evaluating the submitted price quote. The pricing information shall be completed in accordance with the following:

Completed CLINs completed by the offeror along with the completed Attachment XII "Pricing Spreadsheet". Using "Attachment XII "Pricing Spreadsheet" to the RFP offerors must submit fully burdened monthly rates and extended prices (i.e. fees, taxes) for each ordering period identified on the spreadsheet and for the 6-month option period pursuant to FAR 52.217-8. The Contractor's price shall be inclusive of all the Contractor's direct costs, indirect costs, and profit and shall include all costs associated with providing the items/services described in the Performance Work Statement and the solicitation. For the purpose of preparing a price proposal, the offeror shall assume that the period of performance consists of a 5-year ordering period, and FAR clause 52.217-8, Option to Extend Services up to six months, as established in the Schedule.

The proposed rates shall be provided by the offeror in Attachment XII of the solicitation and will be incorporated into the resultant contract as the ceiling rates for each category. Failure to include a rate for all of the provided categories within Attachment XII may deem an offeror to be non-responsive.

A completed and signed page 1 of the solicitation and a completed and signed page 1 of any amendments;

Unless completed in SAM, RFP Section, "Representation, Certification and Other Statements of Offerors" completed by the offeror in accordance with FAR 52.204-8, FAR 52.204-24, FAR 52.204-26 and DFARS 252.204-7007 Alt. A.

All price and price supporting information shall be…