Performance Work Statement

Contractor Support Services for Resilient Command, Control, and Communications (RC3), Information Technology (IT) Transport & Networks, Naval Computer and Telecommunications Platforms

(NCTP) Command, Control, Communications, Computers, Combat Systems, and Intelligence (C5I) Shore

Command’s Core Tactical Baseline Requirements

Navy Information Forces, Suffolk, Virginia

SECTION 1: BACKGROUND AND GENERAL INFORMATION

1.1 BACKGROUND: Navy Information Forces (NAVIFOR) is the Information Warfare (IW) Type Commander

(TYCOM) for Command, Control, Communications, Computers, Combat Systems, and Intelligence (C5I).

NAVIFOR is responsible for the Manned, Trained, Equipped (MT&E) functions for Fleet requirements.

NAVIFOR’s mission is to provide commanders ashore and afloat with forward deployable, combat-ready

Information Warfare forces capable of conducting prompt and sustained naval, joint, and combined operations in support of U.S. national interests. The C5I Programs and Requirements Directorate (N8) develops MT&E requirements and assesses current and future IW capability areas across the Assured

Command and Control (AC2) Operations, Integrated Fires, and Battle Space Awareness mission areas.

In support of NAVIFOR N8’s mission, and in keeping with the Chief of Naval Operations (CNO) and U.S. Fleet

Forces’ Command (USFFC) guidance, the N8 Assured C2 Branch, in collaboration with other Navy stakeholders, must ensure the Fleet possesses the C5I tools required to ensure Navy’s mission success when presented with adversaries or challenges to communications, IT Transport & Networks, and C2 systems.

As such, Resilient Command, Control, and Communications (RC3), IT Transport & Networks, Naval Computer and

Telecommunications Platforms (NCTP) C5I Shore Command’s Core Tactical Baseline expertise is critical to

NAVIFOR's leading role in shaping the development of RC3 capabilities for maritime operations and logistical planning within communications contested environments, provide support to Operational Continuity planning (COOP) for afloat and ashore platforms and to execute RRL Information Systems and Transport (IS&T) requirements and capability gap development.

1.2 GENERAL: This is a non-personal services contract to provide contractor personnel to assist NAVIFOR N8 in identifying Resilient Command, Control, and Communications (RC3), IT Transport & Networks, NCTP C5I

Shore Command’s Core Tactical Baseline, and RRL IS&T requirements and capability gaps. Functions include afloat and ashore radio frequency (RF), satellite communications (SATCOM), IT Transport & Networks (Navy and Coalition), RRL related capability gap determination, analyzing solution options, and developing requirements to effectively counter current and future threats. This service supports development of end-to-end integrated and whole capabilities for RC3, IT Transport & Networks, RRL, and C5I Core Tactical Baseline including Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and

Policy (DOTMLPF-P) considerations, Concept of Operations (CONOPS) development, and prioritization processes.

1.3 TYPE OF CONTRACT: The Government intends to award a firm-fixed price Purchase Order with option periods.

1.4 OVERVIEW OF TASKS: This Performance Work Statement (PWS) describes technical and management support services to be provided to the NAVIFOR N8 Directorate. The scope of this PWS includes support services to develop and execute Navy RC3, IT Transport & Networks, NCTP C5I Shore Command’s Core

Tactical Baseline, RRL IS&T, and operational strategy documents to proactively manage the effects of

Communications Contested Environments (CCE), maintain operational continuity, effectively execute

Electromagnetic Maneuver Warfare EMW, and provide Assured C2.

1.5 PERIOD OF PERFORMANCE: The period of performance shall be for a base year of twelve (12) months and four (4) 12-month option periods. The Period of Performance reads as follows:

Period of Performance Dates

Base Year Period of Performance (PoP) to begin 30 days after contract award

Option Year I PoP to begin 12 months after Base Year PoP begins

Option Year II PoP to begin 12 months after Option Year I PoP begins

Option Year III PoP to begin 12 months after Option Year II PoP begins

Option Year IV PoP to begin 12 months after Option Year III PoP begins

FAR 52.217-8 Option PoP to begin 12 months after Option Year IV PoP begins

1.6 LOCATION OF PERFORMANCE: Navy Information Forces, 115 Lakeview Parkway, Suffolk, VA 23435.

1.7 HOLIDAYS: The contractor is generally not required to provide services on these days.

New Year’s Day Labor Day

Martin Luther King Jr.’s Birthday Columbus Day

President’s Day Veteran’s Day

Memorial Day Thanksgiving Day

Juneteenth National Christmas Day

Independence Day

1.8 WORK ENVIRONMENT AND HOURS OF OPERATION: Hours of Operation for contractor personnel are between the hours of 0600 and 1800 Monday thru Friday and shall provide support services IAW

NAVIFOR’s core hours policy with the exception of Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The ability to provide support from an alternate location (includes working from an employee’s residence or other non-Government facility) is dependent on the type of support required, the contractor employee’s ability and trustworthiness, and the company’s employment policy. Allowing work to be performed at an alternate location is not an option for all positions and personnel. The ultimate decision to allow work performed at an alternate work location shall be determined by the COR. If alternate work locations are allowed, the company shall have defined criteria addressing the minimum requirement to have continuous, secure internet connectivity. Each applicable contractor employee shall have an established signed telework agreement between the company and employee. For each contractor employee proposed to work at an alternate location, the contractor shall submit a written request and justification to the COR with a copy of the applicable employee’s signed telework agreement which becomes part of the COR files. If the requirements for teleworking and/or alternate work locations are not outlined/specified in the employee agreement documentation, the contractor shall include a copy of those requirements with the signed employee agreement. Working at an alternative location shall not adversely affect the response time required in support of the task order. The Government reserves the right to discontinue the ability to work from an alternate location at any time without cause. The inability of a contractor to respond to the requirements of the task order due to telework conditions may be negatively reflected in the Contractor Performance Assessment

Reporting System (CPARS).

All contractor personnel working in NAVIFOR Building 115 shall muster daily in accordance with NAVIFOR policies and procedures. Such daily mustering is for Anti-Terrorism/Force Protection/Active Shooter purposes only.

1.9 CONTRACTING OFFICER’S REPRESENTATIVE (COR):

The COR will be identified by separate letter and in the resultant contract. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the requirements of the contract, perform inspections necessary in connection with contract performance, maintain written and oral communications with the Contractor concerning various aspects of the contract, issue written interpretations of requirements, monitor Contractor's performance and notify both the Contracting Officer and Contractor of any deficiencies, coordinate availability of Government furnished property/training sites, and provide or coordinate site entry of Contractor personnel.

A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting contract.

1.10 CONTRACTOR LEAD: The Contractor shall designate an employee to serve as the Contract Lead. This

Contract Lead shall be the primary Contractor point of contact for the COR. The Contract Lead should be empowered to make decisions on behalf of the Contractor.

1.11 IDENTIFICATION OF CONTRACTOR PERSONNEL: All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

1.12 ACRONYMS: A listing of acronyms related to this effort is provided in section 7.7 Acronyms.

SECTION 2: SCOPE

2.1 ESTIMATED LABOR MIX: This effort is estimated at two (2) contractor-provided personnel in various labor categories as summarized in the following table:

Labor Category Support Expertise Quantity Hours

Senior and Staff

Officer SME (Lead)

Requirements, doctrine, experimentation, policy & implementation. Requirements letter generation. POM/IPCL support. IT Transport &

Networks, NCTP C5I Shore

Command’s Core Tactical

Baseline, and RRL IS&T support.

1 1,912

C5I, Networks, Transport & RC3

SATCOM SME

EHF, SHF, Commercial, Shore, and SATCOM Transport to include Narrowband and

Protected SATCOM, MUOS

WCDMA, Integrated Waveform, and legacy. Wideband

SATCOM. RF, HF Afloat and

Ashore Networks Operations

Requirements. RC3 Doctrine and

TTP development. POM/IPCL

Support. IT Transport &

Networks, and NCTP C5I Shore

Command’s Core Tactical

Baseline support.

1 1,912

The Contractors shall focus efforts on key tenets of a structured, process-focused, metrics-driven Navy capability-based enterprise approach to guide NAVIFOR through the strategic planning and execution of an integrated Resilient C2, CCE, and EMW strategy.

2.2 SENIOR REQUIREMENTS, DOCTRINE, AND STAFF OFFICER SME

The Requirements, Doctrine and Experimentation SME will perform the following tasks:

2.2.1 Support NAVIFOR N8 Requirements Directorate by providing necessary consulting, managerial, analytical, and organizational skills to assist in managing Navy IW communications requirements.

2.2.2 Research and produce Flag level staff correspondence and products to include, but not limited to: “ghost emails,”

Power Point presentations, point papers, and white papers.

2.2.3 Retrieve data from a variety of sources and individuals to identify the scope and breadth of communications gaps, to analytically and creatively evaluate the data, and to craft collaborative and well researched solution proposals.

Interact with NAVIFOR, FCC, USFF, OPNAV staff, Fleet and Type Commanders, Platform Agents, Warfare

Centers of Excellence, Program Offices, and other relevant Navy organizations, services, and DOD agencies.

2.2.4 Manage and coordinate IW Domain input for the USFF Annual Fleet CONOPS data call and produce an IW

Domain CONOPS tracker that is updated monthly to provide a status to senior personnel.

2.2.5 Validate NAVIFOR/USFF Navy-wide IW-related Operational Tasking (OPTASK) implementation and make recommendations on effective implementation.

2.2.6 Evaluate multinational capability requirements and participate in capability and TTP development for BFTN, Battlefield Information Collection and Exploitation System (BICES), and other coalition communications systems, as required.

2.2.7 Explore concepts, including technological, doctrinal, and organizational capabilities for the future.

2.2.8 Develop meaningful metrics gathering strategies and evaluate the evidence to provide recommendations, insights, findings and observations regarding the effectiveness of Doctrine.

2.2.9 Assist in identifying and tracking required Communications DOTMLPF-P actions.

2.2.10 Assist in executing Assured C2, CCE, and EMW DOTMLPF-P actions under NAVIFOR cognizance.

2.2.11 Assist with capability gaps identification and review related / draft briefs, white papers, and other documents for comment.

2.2.12 Support the annual Information Warfare AC2 Integrated Prioritized Capability List as related to the OPNAV

Program Object Memorandum process.

2.2.13 Assist in advocating for the fleet’s SATCOM requirements with program sponsors and program offices. Develop analytics, briefs, and other persuasive or informational briefs for flag level review.

2.2.14 Develop data gathering and coordination plans for updating and representing Fleet data rate requirements to resource sponsors and acquisition.

2.2.15 Participate in staff planning meetings, briefings, and VTCs.

2.2.16 Based on guidance from the supported Fleets and related Navy organizations and commands, develop agendas, focus material, and session summaries for C5I capability gaps identification and analysis and validation events.

2.2.17 Organize material and technical support for work sessions, briefings, and other meetings that support C5I development and result in finished documents.

2.2.18 When requested, provide paper or oral briefings and white papers to update chain of command on document progress.

2.2.19 Review and provide CRM input to N8 assigned documents via Tasker System (ETMS2/CTS). When directed provide consolidation of staff’s CRM inputs and close out tasker.

2.2.20 Assist NAVIFOR Government lead in performing LNO functions when representing Navy in Joint or international forums.

2.2.21 Support NAVIFOR N81 at meetings, conferences, and workshops regarding current and future doctrine/requirements development and integration. This will require the Contractor to liaising with other directorates within NAVIFOR, USFF, PACFLT, FCC, and other service-specific or DOD organizations.

2.2.22 Provide subject matter expertise in formal writing, ghost emails, and documenting military communications requirements.

2.2.23 Participate in the development of NCTP C5I Shore Command’s Core Tactical Baseline requirements and document in NAVIFOR instructions or readiness processes.

2.2.24 Provide SME support for equipment mapping of C3 Shore Command’s Core Tactical Baseline requirements to Navy

Mission Essential Tasks (NMETs) for all NCTPs.

2.2.25 Develop and support NCTP C5I Shore Command’s Core Tactical Baseline enclosures by reviewing CCDR

OPLANs, ICPs, COMMPLANS, Thin-line, Global Force Management Plan (GFMP), and other related documents to determine baseline C5I equipment requirements needed to support extended theater-wide major combat operations for all AORs.

2.2.26 Assist NAVIFOR N8 government leads by providing necessary consulting, subject matter expertise, analytical, and organizational skills to assist in capturing and documenting fleet requirements and gaps for Navy afloat and ashore legacy and existing IT Transport & Networks systems that support Fleet, joint, and coalition operations.

2.2.27 When requested, coordinate with major staffs from Navy Headquarters, Fleet Commanders, Type Commanders

(TYCOMS), Combatant Commanders (COCOMs), and System Commanders (SYCOMs) on communication requirements for maritime forces. Contractor must have a strong ability to collaborate effectively across organizational boundaries, and a broad technical knowledge base with a solid understanding of communication concepts, dependencies, and system interrelationships.

2.2.28 Provide subject matter expertise in writing and updating IT Transport & Networks requirements letters related to

Consolidated Afloat Network Enterprise Services (CANES), Piers Enterprise Piers Connectivity Architecture (Piers

EPCA), Automated Digital Network System (ADNS), Combined Enterprise Regional Information Exchange System

- Military (CENTRIXS-M), Naval Messaging, Wireless and Mobility, Shore Tactical Assured Command and

Control (STACC), and other letters, memo, or instructions related to IT Transport & Networks.

2.2.29 Verify fulfillment of and provide updates for Ready, Relevant Learning Information Systems and Transport (IS&T) requirements letter.

2.2.30 Conduct analysis and coordinate with Fleet stakeholders to support Naval Information Warfare Systems Command

5.0 & PEO MLB RRL Architecture Development.

2.2.31 Provide any updates needed for Ready Relevant Learning Application Information Technology (IT) hosting and transport Fleet Concept of Operations (CONOPS).

2.2.32 Support operationalizing the IS&T architecture in support of achieving Initial Operational Capability (IOC) and Full

Operational Capability (FOC).

2.2.33 Support IS&T architecture initiatives and developments to deliver RRL modernized content at the point of need.

2.2.34 Support IPT working groups focused on tasks/deliverables associated with IOC and FOC.

2.3 C5I, Networks, Transport & RC3 SATCOM SME SUBJECT MATTER EXPERT (SME).

The AEHF and Protected SATCOM, Wideband MILSATCOM/COMSATCOM, Shore Telecommunication Station SME will perform the following tasks:

2.3.1 Support NAVIFOR N8 Requirements Directorate by providing necessary consulting, managerial, analytical and organizational skills to assist in identifying and analyzing Navy IW and communications related capability gaps.

2.3.2 Provide subject matter expertise in Navy SATCOM requirements including EHF and protected, wideband

MILSATCOM and COMSATCOM, and related telecommunication station functions, gateway support, and planning/authorization processes. Additionally, the Contractor shall support all facets of capability gaps identification and analysis, and support to include review of concepts, communications requirements, OPLANs, acquisition documents, concept of operations, and other technical and non-technical documents.

2.3.3 Retrieve data from a variety of sources and individuals to identify the scope and breadth of communications gaps, to analytically and creatively evaluate the data, and to craft collaborative and well researched solution proposals.

2.3.4 Interact with NAVIFOR, Fleet Cyber Command (FCC), USFF, Office of the Chief of Naval Operations (OPNAV) staff, Fleet and Type Commanders, Platform Agents, Warfare Centers of Excellence, Program Offices, and other relevant Navy organizations, services, and Department of Defense (DOD) agencies.

2.3.5 Review Navy’s Navy Multiband Terminal (NMT) and other SATCOM terminal and modem capability delivery strategies. Working with other services and stakeholders, identify fleet capability gaps and related analysis for

SATCOM requirements.

2.3.6 Identify gaps in SATCOM management processes and recommend improved methodologies to most effectively manage satellite and support system resources for surface, submarine, and other Navy consumers.

2.3.7 Identify best practices for Numbered Fleets to assist in resilient communications. Recommendations should include strategies for Protected SATCOM communication planning, shore capability support, and contingency mission planning.

2.3.8 Assist the NAVIFOR SATCOM Database (SDB) Manager with tracking, updating and maintaining SDB requirements.

2.3.9 Assess Space operations and threats including satellite capability for imagery, detection, and intelligence, surveillance, and reconnaissance (ISR) transport.

2.3.10 Codify recommendations for resilient fleet communications planning and operations in CONOPS, CONEMP, NTPs, Tactics, Techniques, and Procedures (TTPs), or other guiding documents as required by NAVIFOR.

2.3.11 Evaluate SATCOM continuity of system fielding and fleet training and make specific recommendations for improvement if ineffective fielding or training strategies are identified.

2.3.12 Assist in identifying required SATCOM Doctrine, Organization, Training, Materiel, Personnel, Leadership, Facilities, and Policy (DOTMLPF-P) actions.

2.3.13 Assist in executing SATCOM DOTMLPF-P actions under NAVIFOR cognizance.

2.3.14 Assist with the identification and analysis of SATCOM related capability gaps, requirements analysis and review related / draft briefs, white papers, and other documents for comment.

2.3.15 Assist in advocating for the fleet’s SATCOM requirements with program sponsors and program offices. Develop analytics, briefs, and other persuasive or informational briefs for flag level review.

2.3.16 Support the annual Information Warfare Integrated Prioritized Capability List as related to the OPNAV Program

Object Memorandum process.

2.3.17 Participate in staff planning meetings, briefings, and Video Teleconferences (VTC).

2.3.18 Based on guidance from the supported Fleets and related Navy organizations and commands, develop agendas, focus material, and session summaries for C5I capability gaps identification and analysis, and validation events.

2.3.19 Organize material and technical support for work sessions, briefings, and other meetings that support C5I development and result in finished documents.

2.3.20 When requested, provide papers or oral briefings and white papers to update the chain of command on document progress.

2.3.21 Assist NAVIFOR Government lead in performing Liaison Officer (LNO) functions when representing Navy in Joint or international forums.

2.3.22 Review and provide CRM input to N8 assigned documents via Tasker System (ETMS2/CTS). When directed provide consolidation of staff’s CRM inputs and close out tasker.

2.3.23 Support NAVIFOR N8 at meetings, conferences, and workshops regarding current and future doctrine/requirements development and integration. This will require liaising with other directorates within NAVIFOR, USFF, FCC, and other service-specific or DOD organizations.

2.3.24 Provide subject matter expertise in formal writing, ghost emails, and documenting military communications requirements.

2.3.25 Participate in the development of NCTP C5I Shore Command’s Core Tactical Baseline requirements and document in NAVIFOR instructions or readiness processes.

2.3.26 Provide SME support for equipment mapping of C5I Shore Command’s Core Tactical Baseline requirements to

Navy Mission Essential Tasks (NMETs) for all NCTPs.

2.3.27 Develop and support NCTP C5I Shore Command’s Core Tactical Baseline enclosures by reviewing CCDR

OPLANs, ICPs, COMMPLANS, Thin-line, Global Force Management Plan (GFMP), and other related documents to determine baseline C5I equipment requirements needed to support extended theater-wide major combat operations for all AORs.

2.3.28 Assist NAVIFOR N8 government leads by providing necessary consulting, subject matter expertise, analytical, and organizational skills to assist in capturing and documenting fleet requirements and gaps for Navy afloat and ashore legacy and existing IT Transport & Networks systems that support Fleet, joint, and coalition operations.

2.3.29 When requested, coordinate with major staffs from Navy Headquarters, Fleet Commanders, Type Commanders

(TYCOMS), Combatant Commanders (COCOMs), and System Commanders (SYCOMs) on communication requirements for maritime forces. Contractor must have a strong ability to collaborate effectively across organizational boundaries, and a broad technical knowledge base with a solid understanding of communication concepts, dependencies, and system interrelationships.

2.3.30 Provide subject matter expertise in writing and updating IT Transport & Networks requirements letters related to

Consolidated Afloat Network Enterprise Services (CANES), Piers Enterprise Piers Connectivity Architecture (Piers

EPCA), Automated Digital Network System (ADNS), Combined Enterprise Regional Information Exchange System

- Military (CENTRIXS-M), Naval Messaging, Wireless and Mobility, Shore Tactical Assured Command and

Control (STACC), and other letters, memo, or instructions related to IT Transport & Networks.

2.3.31 Support Arctic Communications Fleet CONOPS DOTMLPF-P actions and status updates.

2.3.32 Support Resilient Command, Control and Communication (RC3) Fleet Concept of Operations (CONOPS)

DOTMLPF-P actions and status updates.

2.3.33 Develop and deliver RC3 Assured Mission Planning support concepts, doctrine, and fleet tactics, techniques, and procedures for deployed maritime forces.

2.3.34 Conduct analysis on DoD hybrid military and commercial SATCOM implementation; deliver updates to RC3 recommended capabilities.

2.3.35 Support the development of the Fleet Information Warfare Integrated Prioritized Capabilities List.

2.3.36 Update Fleet Bandwidth SATCOM requirements Letter.

2.3.37 Deliver Fleet High Frequency (HF) Communications products in support of Navy and DOD HF Requirements.

2.3.38 Provide analytical support and deliver reports for Fleet RC3 experimentation during periods of reduced and degraded communications.

SECTION 3: PERSONNEL REQUIREMENTS

3.1 SENIOR REQUIREMENTS, DOCTRINE AND STAFF OFFICER SME

Area(s) of Expertise: Requirements development, relevant Navy Major Staff Experience, Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy (DOTMLPF-P) analysis, Doctrine, Experimentation & Implementation, Coalition Communications. IT Transport & Networks, NCTP C5I Shore Command’s Core Tactical Baseline, and RRL IS&T support.

Education: Master’s Degree

Experience: A minimum of 8 years of experience working with requirements, doctrine or capability development; a minimum of 20 years of experience with tactical or strategic military operations; a minimum of

6 years of experience with Joint or Maritime operations and requirements; and a minimum of 6 years of experience with DOD DOTMLPF-P actions, or PPBE management.

Security Clearance: Top Secret (SCI)

3.2 C5I, Networks, Transport & RC3 SATCOM SUBJECT MATTER EXPERT (SME)

Area(s) of Expertise: Advanced Extremely High Frequency (AEHF) and Protected SATCOM. IT Transport &

Networks, and NCTP C5I Shore Command’s Core Tactical Baseline support.

Education: Bachelor’s Degree. Undergraduate degree must include a major in Science, Engineering, or

Information Systems.

Experience: A minimum of 8 years of experience working with Protected systems (i.e. MILSTAR, AEHF). A minimum of 6 years of experience with tactical or strategic military operations; a minimum of 8 years of experience with military communications systems, to include practical experience with; a minimum of 8 years of experience with DOD DOTMLPF-P actions or Planning, Programming, Budgeting and Execution (PPBE) management; a minimum of 6 years of experience working with Navy Communications Programs and Navy or

Joint operational stakeholders.

Security Clearance: Top Secret (SCI)

SECTION4: TRAVEL

4.1 TRAVEL: The contractor shall be required to travel in the performance of the tasking detailed in this PWS. Travel costs for transportation, lodging, meals and incidental expenses are allowable if incurred by contractor personnel on official business. Travel related costs shall be reasonable. Costs for transportation may be based on mileage rates, actual costs incurred, or a combination thereof, provided the method used results in a reasonable charge. Costs incurred for lodging, meals and incidental expenses shall be considered reasonable and allowable only to the extent they do not exceed on a daily basis the maximum per diem rates in effect at the time of travel. See FAR 31.205-46 for more information on travel costs.

Travel costs are further limited by funds specified in the contract.

The Contractor shall submit a request, via email, to the COR seeking approval to deviate from the trips listed in the table below before initiating any travel plans. Failure to gain prior approval may result in disallowance of invoiced travel claims. Contractor shall research the most current rules, regulations, policies, restrictions, etc., prior to travel.

Local travel within the Hampton Roads area is authorized, but will not be reimbursed. The following table is an estimate of the amount of travel required in the accomplishment of this effort. Each Contractor shall possess a passport in anticipation of foreign travel. The Contractor may be required to embark onboard U.S or Coalition

Naval vessels (ship/airplane/submarine/expeditionary unit) in port or underway. The Contractor shall generate and submit a trip report in accordance with Section 7.0 Deliverables.

# Est.Trips # Personnel each Trip From To Duration each Trip

(Days)

4 1 Norfolk/Suffolk, VA

San Diego CA 5

2 1 Norfolk/Suffolk, VA

Charleston, SC 5

3 1 Norfolk/Suffolk, VA

Washington, DC 3

4 1 Norfolk/Suffolk, VA

Colorado Springs, CO 5

2 1 Norfolk/Suffolk, VA

Kirtland AFB, NM 5

1 1 Norfolk/Suffolk, VA

Mclean, VA 5

1 1 Norfolk/Suffolk, VA

Omaha, NE 5

1 1 Norfolk/Suffolk, VA

Suitland, MD 5

3 1 Norfolk/Suffolk, VA

Honolulu, HI 7

1 1 Norfolk/Suffolk, VA

Pensacola, FL 5

1 1 Norfolk/Suffolk, VA

Annapolis, MD 5

1 1 Norfolk/Suffolk, VA

Camp Smith, HI 5

SECTION 5: SECURITY REQUIREMENTS

5.1 SECURITY: The contractor shall be responsible for adhering to all DOD, Department of the Navy and

Command instructions, guidance, orders, directives, and supplements relative to performing tasks set forth in this

PWS. Access will be granted to Government facilities as required in support of the tasking. Contractor personnel performing work under this contract must meet all requirements for gaining access to US Government installations.

The contractor shall conform to all DoD, DoN, and local (base/installation) security instructions (refer to

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

Technology (IT) Systems or Protected Health Information provided below).

The scope of work requires access to NATO, SECRET and TOP SECRET (SCI) information for contractor personnel. Contractor personnel shall have the appropriate security clearance as of the first day of the period of performance. Both Senior and Staff Officer SME and C5I, Networks, Transport & RC3 SATCOM SME require a

TOP SECRET (SCI) clearance on day one.

For the C5I, Networks, Transport & RC3 SATCOM SME, work performed shall include access to TS/SCI data, information and spaces. TS/SCI access is required by contractor personnel for access to correspondence, reports, and documentation for analysis, product, and presentation development informed by threat, intel, and Fleet plans.

Participation in TS/SCI meetings is required both locally and at other command and Fleet sites.

The Government will provide access to TS/SCI spaces if required. The Government will provide, commercial and government developed software, as required. The Government will provide access to systems as required for developmental purposes. The Government will provide access to classified systems that are necessary for classified documentation development and testing.

All work is to be performed in accordance with DOD and Navy Operations Security (OPSEC) requirements and in accordance with the OPSEC attachment to the DD254.

The Government Contractor CAC card serves as the primary method of identification for the contractor employees, as well as providing the basis of Public Key Infrastructure (PKI) access to the Navy/Marine Corps Intranet (NMCI), and numerous

Navy web sites, which may also require PKI access. The COR shall assist in providing the contractor the appropriate documentation for obtaining CAC cards. The Contractor shall be responsible for obtaining any Government issued identification cards from former employees or employees whose access has been terminated and to turn those items over to the Command Security Officer upon termination of employment or access.

5.1.2 INTELLIGENE OVERSIGHT (IO): Contractors requiring TS/SCI shall complete Intelligence Oversight (IO) training within 30 days of assignment and annually for personnel engaged in intelligence functions and activities.

Contractors shall familiarize themselves with intelligence oversight regulations and procedures in DoDM 5240.01

Procedures (1-10), report questionable intelligence activities to the NAVIFOR Inspector General, command’s IO

Officer (IOO), and cooperate with the Office of Inspector General and others requiring information on potential violations.

5.2 PRIVACY ACT COMPLIANCE: The Contractors may be in contact with data and information subject to the

Privacy Act of 1974 (Title 5 of the U.S. Code Section 552a). The Contractors shall ensure that its employees assigned to this effort understand and adhere to the requirements of the Privacy Act and to Department of Defense and Department of the Navy regulations that implement the Privacy Act. Department of Navy policy and procedures implementing the Privacy Act are detailed in SECNAVINST 5211.5E (Department of the Navy Privacy

Act (PA) Program). The Contractors shall identify and safeguard data, information and reports accordingly. In addition, the Contractors shall ensure that Contractors employees assigned to the contract are trained on properly identifying and handling data and information subject to the Privacy Act prior to commencing work.

5.3 GOVERNMENT FURNISHED INFORMATION: GFI will be provided to contractor employees as needed to complete the tasks set forth in this performance work statement. Access to classified information must be granted in accordance with the terms and conditions contained in DOD Manual 5220.22-M and DD Form 254 (Contract

Security Classification Specification). The Contractor shall comply with all current information assurance awareness, information security policies, procedures, and statutes applicable to DOD information technology;

including the July 3, 2007 DOD CIO Policy Memorandum on Encryption of Sensitive Unclassified Data at Rest on Mobile Computing Devices and Removable Storage.

SECTION 6: ADMINISTRATIVE REQUIREMENTS

6.2 PERSONNEL CHANGES: During the first one hundred twenty days of performance, the Contractors shall make no substitutions of personnel unless the substitution is necessitated by changes to contractor workforce brought on by resignation or calamity. The Contractor shall notify the COR at least 15 days prior to any personnel changes, when possible, during the life of the contract.

6.3 CONTRACTOR QUALITY ASSURANCE: The contractor shall develop and maintain a Quality Assurance

Plan (QA Plan) in order to ensure only qualified personnel, as stipulated in Section 3, are assigned to fulfill the requirements stated in this PWS. The contractor shall detail in its quality assurance plan how it intends to maintain personnel qualifications and ensure contract employees have up-to-date training and knowledge in their respective areas of endeavor.

This QA Plan shall detail the methodology to be used by the contractor to monitor and grade the performance of its personnel as they carry out the requirements of this PWS. The QA Plan shall address the contractor’s courses of action to address under-performing employees.

6.4 GOVERNMENT QUALITY ASSURANCE SURVEILLANCE: The Government shall evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP).

This plan is primarily focused on what the Government must do in order to ensure that the contractor is performing in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

6.5 COMPLAINTS LODGED AGAINST CONTRACTOR PERSONNEL: In the event that a complaint is made regarding the conduct or ability of contractor personnel, the individual receiving the complaint will contact the

COR. The COR will notify the Contractor Lead. The Contract PM Lead and COR will cooperate in investigating complaints made against contractor employees. If the results of the investigation prove the complaint(s) to be valid, the Contractor Lead shall have a maximum of three (3) working days to propose a corrective plan for resolving the matter and preventing future similar occurrences. This plan shall be submitted in writing to the

Contracting Officer and COR. In the event that the Government deems the corrective plan insufficient for resolution of the problem, a written response to the Contractor Manager shall be provided within three (3) working days.

6.6 OFFICE SPACE: Government will provide office space, desk, chair, and common office supplies. In addition to office space, each contract employee shall be provided with access to government computers and telephones, but not cellular phones, for official use only. Under no circumstances will contractor- provided personal computers be connected to the Navy/Marine Corps Intranet (NMCI). Contractor personnel shall comply with all DOD and Navy internet usage and cybersecurity policies.

6.7 STATEMENT OF NON-PERSONAL SERVICE: Contractor employees performing services under this contract will be controlled, directed, and supervised at all times by management personnel of the contractor. Contractor management shall ensure that employees properly comply with the performance work standards outlined in the PWS.

Contractor employees shall perform their duties independent of, and without the supervision of, any Government official. The tasks, duties, and responsibilities set forth in this contract shall not be interpreted or implemented in any manner that results in any contractor employee creating or modifying Federal policy, obligating the appropriated funds of the United States Government, overseeing the work of Federal employees, providing direct personal services to any

Federal employee, or otherwise violating the prohibitions set forth in Parts 7.5 and 37.1 of the Federal Acquisition

Regulation (FAR) http://farsite.hill.af.mil/vffar1.htm. The Government shall control access to the facilities and shall perform the inspection and acceptance of completed work.

6.8 INVOICING: Invoices shall be submitted via the Wide Area Workflow system.

SECTION 7: DELIVERABLES

7.1 DELIVERABLES: The Contractors shall provide the deliverables listed per Section 2: Scope. Deliverables shall be prepared in Contractor’s format where not otherwise specified by the Government. Deliverables shall be provided to the COR. All final deliverable submissions shall remain the property of the U.S. Government. All revisions will be due in the specified timeframe as identified by the Government. All methodologies and recommendations shall be reviewed and approved by the Government prior to submission/implementation.

a. Contractors shall provide deliverables for Resilient Command, Control, and Communications (RC3), Information

Technology (IT) Transport & Networks, Naval Computer and Telecommunications Platforms (NCTP) Command, Control, and Communications (C5I) Shore Command’s Core Tactical Baseline, and Ready Relevant Learning

IS&T Requirements as listed in Section 2: Scope.

b. Contractors shall develop and provide NCTP C5I Shore Command’s Core Tactical Baseline requirements instruction, enclosures and equipment mapping to NMETs by reviewing CCDR OPLANs, ICPs, COMMPLANS, Thin-line, Global Force Management Plan (GFMP), and other related documents to determine baseline C5I equipment requirements needed to support extended theater-wide major combat operations for all AORs, to include http://farsite.hill.af.mil/vffar1.htm specific tasks listed in Section 2: Scope.

c. Contractors shall provide necessary consulting, subject matter expertise, analytical, and administrative support for the RRL IS&T architecture to include specific tasks listed in Section 2.2.

d. Contractors shall assist NAVIFOR N8 government leads by providing necessary consulting, subject matter expertise, analytical, and administrative support to assist in capturing and documenting fleet requirements and gaps for Navy afloat and ashore legacy and existing IT Transport & Networks systems that support fleet, joint, and coalition operations, to include specific tasks listed in Section 2: Scope.

e. Contractors shall assist NAVIFOR N8 government leads by providing necessary consulting, subject matter expertise, analytical, and administrative support for DOTMLPF-P actions, IPCL, POM, Requirements Letters, and Comment Resolution Matrix (CRM) input via document reviews, to include specific tasks listed in Section 2:

Scope.

7.2 CONTRACTOR QUALITY ASSURANCE PLAN: Due within 30 days of period of performance start date and updated annually thereafter (refer to paragraph 6.4).

7.3 CONTRACTOR INCLEMENT WEATHER/DISASTER PLAN: Provide COR with copy of Contractor’s rules/policies governing situations when personnel are affected by emergencies of a man-made (civil disturbance, local terrorist activity, war) or natural (hurricane, earthquake, hazardous weather) nature. Should contractor personnel be members of a union, those sections of Collective Bargaining Agreement (CBA) that specify reporting/schedule/muster details (as they relate to contractor personnel assigned duties in accordance with the pertinent PWS) shall be provided to the COR, as well as any subsequent modifications. Due within 30 days of period of performance start date.

7.4 MONTHLY STATUS REPORT: The Contractor shall provide NAVIFOR N8 a monthly project In Progress

Review (IPR) no later than the 20th day of the month. The IPR shall be a formal review whereby the Contractors will discuss matters such as project requirements, current and planned project activities, contract personnel status, and problems encountered or anticipated that may project schedule. The report shall contain the following information at a minimum

a. Task/project status (include originator/customer, personnel assigned to complete, goal/end- state, estimated completion date, percent complete)

b. Personnel issues

c. Upcoming Travel

d. Anticipated activity for next reporting period

7.5 TRIP REPORT: The contractor shall provide a trip report to the COR within 5 days of return from any periods of travel. The trip report shall be in a format prescribed by the contractor, but at a minimum, shall address the objectives of the travel and whether those objectives were or were not achieved. If not achieved, the circumstances preventing the accomplishment of the objective shall also be provided.

7.6 MONTHLY FINANCIAL REPORT: The Monthly Financial Report shall be submitted not later than 10 business days after end of the month reported on. The report shall contain the following information at a minimum:

a. Current month travel expenses per trip and contract to date travel expense

b. Invoices submitted but not paid

Deliverable Product Format: All reports and documentation will be developed using recent versions of Adobe

Acrobat, Microsoft Office Professional Products to include Word, Excel, PowerPoint, etc. unless otherwise specified by the COR. Electronic submission shall be made via email, unless otherwise agreed upon with the COR. Oral status reports may also be requested periodically.

The COR will have the right to reject or require correction of any deficiencies found in the deliverables that are contrary to the information contained the Contractors’ accepted proposal. In the event of a rejected deliverable, the

Contractors shall be notified in writing by the COR of the specific reasons for rejection. The Contractors shall have five (5) workdays to correct the rejected deliverable and return it per delivery instructions.

7.7. Acronyms:

A2AD Anti-Access Area Denied

ACAS Assured Compliance Assessment Solution

ADNS Automated Digital Network System

AEHF Advanced Extremely High Frequency

AT/FP Anti-Terrorism/Force Protection

BFTN Battle Force Tactical Network

BICES Battlefield Information Collection and Exploitation System

C2 Command and Control

C3 Command, Control, and Communications

C2DE Command and Control in a Denied Environment

C5I Command, Control, Communications, Computers, Combat Systems, and

Intelligence

CANES Consolidated Afloat Network Enterprise Services

CCE Communications Contested Environment

CCDR Combatant Commander

CENTRIXS-M Combined Enterprise Regional Information Exchange System - Military

COB Close of Business

CONEMP Concepts of Employment

CONOPS Concepts of Operations

COOP Continuity of Operations

COR Contracting Officer's Representative

DECC Defense Enterprise Computing Center

DISA Defense Information Systems Agency

DMR Digital Mobile Radio

DOD Department of Defense

DOTMLPF-P Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy

DOTMLPF-P/I Doctrine, Organization, Training, Materiel, Leadership and Education, Personnel, Facilities, and Policy/Interoperability

EHF Extremely High Frequency

EMW Electronic Maneuver Warfare

EPCA Enterprise Piers Connectivity Architecture

FAM Fleet Advisory Message

FCC Fleet Cyber Command

FFG Foreign Clearance Guide

FIMS Fleet Experimentation Management System

FPC Final Planning Conference

GBS Global Broadcast Service

GCIB Global Communication Information Bulletins

GFMP Global Force Management Plan

GFR Government Furnished Resources

HBSS Host Based Security System

HF High Frequency

ICP Integrated Contingency Plans

IW Information Warfare

IFOR Information Forces

IM Information Management

IP Internet Protocol

IPC Initial Planning Conference

IPCL Integrated Priority Capabilities List

ISR Intelligence, Surveillance and Reconnaissance

JCA Joint Capability Area

JTR Joint Travel Regulations

LNO Liaison Officer

MOE Measures of Effectiveness

MOP Measures of Performance

MPC Mid/Main Planning Conference

MUOS Mobile User Objective System

NATO North Atlantic Treaty Organization

NAVIFOR Naval Information Forces

NCTP Naval Computer and Telecommunications Platforms

NMT Navy Multiband Terminal

NTP Naval Telecommunications Publications

NTRP Navy Tactical Reference Publications

NTTP Navy Tactics, Techniques, and Procedures

NWP Navy Warfare Publications

OPLANS Operational Plans

OPNAV Office of the Chief of Naval Operations

OPSEC Operational Security

OPTASK Operational Tasks

PA Privacy Act

PWS Performance Work Statement

RF Radio Frequency

RC2 Resilient Command and Control

SATCOM Satellite Communications

SDB SATCOM Database

SME Subject Matter Expert

STACC Shore Tactical Assured Command and Control

TACBUL Tactical Bulletins

TACMEMO Tactical Memorandums

TOM Task Order Manager

TTP Tactics, Techniques, and Procedures

UAV Unmanned Aerial Vehicle

UJT Universal Joint Task

UNTL Universal Naval Task List

USFFC United States Fleet Forces Command

VLAN Virtual Local Area Network

VPN Virtual Private Network

VTC Video Teleconference