Solicitation Amendment N0018926RL0300001 SF 30.pdf

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

Created On:

25 Sep 2026, 13:49 PM Greenwich Mean Time

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 28 Sep 2026 02 Oct 2026

N0018926RL0300001

List of Contract Documents, Exhibits, or Attachments

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, Norfolk, Joint Expeditionary Base (JEB) Little Creek, Naval Support Activity (NSA) Mechanicsburg, NSA Philadelphia, NAVSTA 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 16,360 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) & Cloud Security Requirements:

If the proposed solution incorporates a Cloud Service Offering (CSO) or hosted Unified Communications as a Service (UCaaS), it must comply with federal cloud cybersecurity standards for handling sensitive communications and Controlled Unclassified Information (CUI). Because the system operates on an independent, vendor-owned distribution network and does not physically or logically interface with the DoD Information Network (DoDIN), DoDIN Approved Products List (DoDIN APL) certification and DISA Cloud Access Point (CAP) approvals are not required. At a minimum, the proposed CSO must possess an active FedRAMP Authorized designation at the Moderate baseline (based on NIST SP 800-53 controls) and comply with DFARS 252.204-7012 requirements for protecting covered defense information. If required by the Authorizing Official (AO) for mission-essential command voice and emergency services, any hosted cloud repository storing call recordings, CUI metadata, or emergency logs must satisfy the equivalent security control baseline of DoD Cloud Computing Security Requirements Guide (DoD CC SRG) Impact Level 4 (IL4).

The vendor must provide evidence of their FedRAMP authorization (Package ID) and documented security posture with their proposal.

3.1.1 NAVSTA Norfolk - 10,560 endpoints

3.1.1.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E911

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 NAVSTA Norfolk-Chambers Field 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 NAVSTA Norfolk-Chambers Field. 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 JEB Little Creek - 4,100 endpoints

3.1.2.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E911

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 NSA Mechanicsburg - 425 endpoints

3.1.3.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E911

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.4 NSA Philadelphia - 350 endpoints

3.1.4.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E911

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 PNYA - 925 endpoints

3.1.5.1 Features

a. Local and Long-Distance Dialing

b. Voicemail

c. Caller ID

d. E911

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

3.2 Off-Net Calling Services

The contractor's proposed solution shall include a flat-rate billing model for all calls within the North American Numbering Plan (NANP). This model should provide unlimited usage without per-minute charges for calls to destinations covered by the NANP. For all non-domestic (international) calls, a separate Contract Line Item Number (CLIN) shall be established. This CLIN will be for the procurement of call blocks for non-domestic calling minutes as detailed in the contract's pricing schedule.

4.0 System Compatibility and Compliance Requirements

The vendor's solution must be fully compatible and interoperable with the current Inside Plant (ISP)Information Systems Platform 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. The physical and operational demarcation between the Government and Vendor will be established at the Main Distribution Frame (MDF).

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 shall support continued operation and full backward compatibility with all existing Government 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 instruments, voice mail systems, and approved peripheral devices. For secure communications and encrypted data streams (including STE and VoSIP), the contractor is responsible for providing clear-channel, uncompressed transport (G.711 or equivalent approved baseline) and engineering all voice trunking, gateways, and call-processing paths to guarantee zero crypto-resynchronization failures, zero modem negotiation drops, and no degradation of encrypted sessions. The vendor must allocate all necessary bandwidth and configure Quality of Service (QoS) across their network to ensure jitter remains under 20 ms and packet loss remains below 0.1% under peak call volume.

4.3 Auxiliary and Collaborative Voice Systems: The system shall interoperate with all currently deployed voice auxiliary and collaborative systems, including but not limited to: Enhanced 911 (E-911), Next Generation 911 (NG911), 988 Suicide & Crisis

Lifeline, Primary Crash Net (PCN), and Secondary Crash Net (SCN). Where existing crash nets operate over dedicated analog circuits, the vendor is responsible for providing all necessary bridging, conversion, and interfaces required to integrate these circuits into the core voice solution without requiring modification to legacy airfield crash systems. The proposed bridging solution must ensure zero-failover tolerance, maintain immediate ringdown/push-to-talk call delivery, and preserve autonomous local operation during any wider network or WAN interruption.

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 Regional Dispatch Center (RDC), 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.999% 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 with 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 invoice shall clearly distinguish between the flat-rate domestic calling services and any charges incurred against the separate CLIN for non-domestic calls, providing detailed usage data for the latter.

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:

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)

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 SECNAVINST 5510.30C, 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 SECNAVINST 5510.30C, 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 Systems 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.

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 TIER 3to obtain a favorable determination for assignment to a non-critical sensitive or IT-II position. The TIER 3consists 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 Defense Counterintelligence and Security Agency (DCSA) Trusted Decision (Adjudications) (TD(A)) system of record 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 DCSA Defense Information System for Security (DISS) or a hard copy VAR directly from the contractor's Security Representative. Although the contractor will take DISS

"Owning" role over the contractor employee, the Navy Command will take DISS "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 SECNAVINST 5510.30C 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 TIER 1including 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 TIER 1or 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

ATTENTION CODE 301, 1968 GILBERT STREET SUITE 600

NORFOLK, VA 23511-3392

UNITED STATES

JAMES KEEGAN, Email: james.p.keegan7.civ@us.navy.mil Telephone: (757) 443-1419 AdminBy:

SCD: PAS: