DRAFT Performance Work Statement IT Support.docx

Project: Puget Sound Naval Shipyard and Intermediate Maintenance Facility (PSNS & IMF)

Performance Work Statement (PWS)

Project: United States Navy – Puget Sound Naval Shipyard & Intermediate Maintenance Facility (PSNS & IMF) – IT Support Services

C.1 BACKGROUND

Puget Sound Naval Shipyard was originally established in 1891 as a Naval Station and was designated Navy Yard Puget Sound in 1901. During World War I, the Navy Yard constructed ships and during World War II, the Shipyard’s primary effort was the repair of battle damage to ships of the U.S. Fleet and those of its Allies. In 1990 the U.S. Navy authorized a program to recycle nuclear powered ships at Puget Sound Naval Shipyard. Approximately 6% of the Shipyard’s workload involves inactivation, reactor compartment disposal, and recycling of ships. This process places the U.S. Navy in the role of being the world's only organization to design, build, operate, and recycle nuclear powered ships. In 2003, Puget Sound Naval Shipyard and the Naval Intermediate Maintenance Facility, Pacific Northwest (located at Bangor, Bremerton and Everett, WA) consolidated into one maintenance activity - creating PSNS & IMF. The consolidation improves fleet readiness by allowing the Navy to accomplish the highest priority, real-time ship maintenance requirements while achieving the most maintenance effort possible for the tax dollar.

The Naval IMF, Pacific Northwest, first known as TRIDENT Refit Facility (TRF), Bangor, was established on July 31, 1981, as the primary maintenance facility for the West Coast TRIDENT submarine fleet. In 1998 TRF consolidated with Shore Intermediate Maintenance Activity (SIMA), at Everett and Bremerton, and became Naval Intermediate Maintenance Facility (NAVIMFAC) Pacific Northwest.

In addition to the Shipyard and IMF consolidation, in 2003 surface ship maintenance organizations including the Supervisor of Shipbuilding, Puget Sound (SSPS), portions of the Commander, Naval Surface Group, Pacific Northwest Maintenance Staff (CNSGPNW), and Fleet Technical Support Center, Pacific Detachment Everett (FTSCPAC Det Everett) joined PSNS & IMF in standing up the Northwest Regional Maintenance Center (NWRMC). The NWRMC is now one of the few regions that provide maintenance for every class of Navy Vessel.

The sharing of expertise and resources between the Bremerton and Bangor sites provides the Navy with a streamlined approach to maintenance and allows for the savings to be reinvested in the fleet. PSNS & IMF is the Pacific Northwest's largest Naval shore facility and one of Washington State's largest industrial installations.

PSNS & IMF IT support covers sites in Bremerton, WA (the shipyard and Trident Refit facility); Bangor, WA; Everett, WA; San Diego, CA; Pearl Harbor, Honolulu, HI; Portsmouth Naval Shipyard, Kittery, ME; Norfolk Naval Shipyard, Portsmouth, VA; Yokosuka, Japan; NAVSEA Headquarters, Washington DC; and Naval Base Guam. 85-90% of support will be performed at the Puget Sound Naval Station in Bremerton, WA, with on-site support in San Diego, CA, and Yokosuka, Japan. There is also remote auxiliary support to the sites. Additional sites may be supported in the future due to the unpredictability of ship repair work. PSNS & IMF employs more than 14,000+ engineering and industrial personnel (12,800 computer users) and serves as a major maintenance depot for the U.S. Navy. PSNS & IMF proactively maintains an IT architecture that supports users on a real time basis to ensure access to needed corporate information is available from Navy Marine Corps Intranet (NMCI) and Government owned workstations at CONUS and OCONUS sites.

The entire customer base by site can be found in Section J, Attachment P as well as hours of operation by site.

C.1.1 PURPOSE

Information Technology (IT) support for PSNS & IMF is a dynamic and complex requirement that supports the IT requirements of fleet. The primary purpose of this requirement is to provide IT operations, application management, maintenance, and customer support to PSNS & IMF including remote sites and detachments in order to meet mission requirements.

C.1.2 AGENCY MISSION - VISION

PSNS & IMF is a large industrial complex whose mission is to provide logistical support for assigned ships and surface craft by performing overhauls, repairs, alterations, dry- docking, and outfitting; and providing services and materials to other activities and units as directed. PSNS & IMF is organized into departments designated by a number, referred to as codes and are outlined in the organizational chart. Code 100 is the PSNS & IMF Commander’s designations. IT is responsible for the overall accomplishment of the Command’s missions. All other PSNS & IMF codes are subordinate to the Commander level and are responsible for accomplishing the mission of the activity. The contractor is supporting the IT & Cyber Security (IT&CS) Division (Code 109). The Organization Chart for Code 109 is included as Attachment R. The overall vision is to streamline and align all efforts and actions to support the non-stop execution of workflow while increasing the productive capacity.

C.2 SCOPE

The scope of this effort is for operations and maintenance of the PSNS network, corporate and local application management, application processing, Information Assurance (IA) and security, and customer support at the primary maintenance facility in Bremerton Washington and at regional centers. This work will be performed on Government sites, primarily in Bremerton (unless telework is approved by the Government – see Section G.9 below). Full-time on-site support is required in San Diego, CA , and Yokosuka, Japan. As PSNS is part of the NAVSEA enterprise network of naval shipyards, there may be additional site support at various NAVSEA activities/locations that support the IT functionality at PSNS. Long-distance travel will be required. For acronyms listed within this task order, see the Acronym List in Section J, Attachment F.

C.3 CURRENT IT/NETWORK ENVIRONMENT

The PSNS & IMF local area network (LAN) is a general support sensitive unclassified network that operates in UNIX, Linux, and Windows environments. The network provides office automation tools to PSNS & IMF administrative, investigative, analytical, technical, engineering, and production personnel in carrying out their mission-related functions. Administrative support is facilitated through the use of commercial off-the-shelf (COTS) products and Government developed applications (both locally developed applications and corporate applications). The PSNS & IMF LAN provides access to information resources via commercially obtainable equipment (COE) including communication equipment, servers, workstations, and peripherals. This environment also supports OCONUS infrastructure providing network connectivity to approximately 300 OCONUS workstations. See Section J, Attachment P for specifications of the network environment, to include core hardware/software, physical and virtual network capacity.

C.4 TASKS

The contractor shall provide support for the following task areas.

Task 1 – Transition Task 2 – Program Management Task 3 – Network Support Task 4 – Applications Management Task 5 – Applications Operations Support Task 6 – Systems Administration Task 7 – Information Assurance & Cyber Security Task 8 – Customer Support Services Task 9 – Provide Support to Yokosuka, Japan Task 10 – Additional Site Support for Tasks 2-9 - Optional

C.4.1 TASK 1 - TRANSITION

C.4.1.1 SUBTASK 1 – TRANSITION-IN

Transition-in shall facilitate the accomplishment of a seamless transition from the incumbent to the incoming contractor. Transition-in shall be accomplished in accordance with the Transition-In Plan (see Section F, Deliverable 01) submitted and evaluated by the Government with the contractor’s proposal. All transition-in activities shall be completed within 30 calendar days after Task Order start, after which time the incoming contractor shall be responsible for taking over 100% of the effort, ensuring that all required background investigations and personnel security clearance requirements have been met, and that there will be no service degradation after transition-in.

C.4.1.2 SUBTASK 2 –TRANSITION-OUT

The Transition-Out Plan shall facilitate the accomplishment of a seamless transition, with no service degradation, from the incumbent to an incoming contractor during the final calendar 30 days of the Task Order. The contractor shall provide for Government review and approval an initial Transition-Out Plan (see Section F, Deliverable 02) no later than (NLT) one hundred twenty days prior to the expiration of the Base Period, which shall be updated as necessary NLT 120 days before the end of each exercised option period. The contractor shall identify how it will coordinate with the incoming contractor and/or Government personnel to transfer knowledge regarding the following:

a. Project management processes

b. Points of contact

c. Location of technical and project management documentation

d. Status of ongoing technical initiatives

e. Appropriate contractor to contractor coordination to ensure a seamless transition

f. Identify schedules and milestones

g. Identify actions required of the Government, including any Government-furnished property that must be returned to the Government

h. Establish and maintain effective communication with the incoming contractor/ Government personnel for the period of the transition via weekly status meetings

The contractor shall implement the transition-out IAW the Government-approved Transition-Out Plan.

C.4.2 TASK 2 –PROGRAM MANAGEMENT

The contractor shall provide program management support under this Task Order. This includes the management and oversight of all activities performed by contractor personnel, including subcontractors, to satisfy the requirements identified in this Performance Work Statement (PWS). The contractor shall identify a Program Manager (PM) by name, who shall provide management, direction, administration, oversight of quality assurance (for Government Quality Assurance Surveillance Plan (QASP), see Section J, Attachment E), and leadership of the execution of this Task Order. Government office space will be provided at PSNS for the PM.

C.4.2.1 SUBTASK 1 – COORDINATE PROJECT KICKOFF MEETING

The contractor shall schedule, coordinate and provide an agenda for the Project Kick-Off Meeting (see Section F, Deliverable 03) which will be held at PSNS, Bremerton, WA. The meeting will provide an introduction between the contractor personnel and Government personnel who will be involved with the Task Order. It will be held no later than five working days after project start date. The meeting will provide the opportunity to discuss technical, management, security issues, travel authorization, and reporting procedures. At a minimum, the attendees shall include key contractor personnel, relevant Government personnel, the CO, and the COR. At a minimum, the contractor shall provide the following at the kickoff meeting:

a. Points of contact

b. Status of clearances

c. Status of the Draft Project Management Plan (PMP)

d. For each proposed new personnel, his/her full name and date of birth to allow the Government to confirm the current status of required background investigations via the Joint Personnel Adjudication System (JPAS)

C.4.2.2 SUBTASK 2 – PREPARE A MONTHLY STATUS REPORT (MSR)

The contractor shall develop and provide a MSR (see Section J, Attachment B, and Section F, Deliverable 04), using Microsoft (MS) Office Suite applications, by the 10th of each month via ASSIST to the CO, COR and the PSNS Technical Point of Contact (TPOC). The MSR shall include the following:

a. Activities during reporting period, by task (Include: On-going activities, new activities, completed activities, progress to date on all above-mentioned activities). Start each section with a brief description of the task. Contract employees shall record their time spent and identify which tasks correlate to the project, network, site, and system the task supported. This backup data shall be included in the MSR, in addition to a summary of this data (i.e. hours by major tasks, projects, sites, system supported) during the month. This will assist the Government to associate, combine, analyze, and determine the work required to support the various sites, networks, systems, and particular projects or maintenance requirements with the reporting required by the Federal Service personnel; these include sites (e.g. Bremerton, Bangor, Everett, and Yokosuka), networks (e.g., NNPPNet, CMDNet, NMCI, and AACS), systems (e.g. Corp Apps, Telephones, Tablets, Wireless, local software tools and utilities, Citrix, Servers, Firewalls, etc.) and particular projects or requirements (e.g. STIGs, Upgrades, Enhancements, Expansion, Repair, Replacement, etc.).

b. Problems and corrective actions taken. Also include issues or concerns and proposed resolutions to address them.

c. Personnel gains, losses and status (security clearance, etc.).

d. Government actions required or expected, with requested completion date (e.g. visit requests, badge & CAC renewal forms, vehicle passes, etc.).

e. Schedule (Shows major tasks, milestones, and deliverables, planned and actual start and completion dates for each).

f. Summary of trips taken, conferences attended, etc. (Attach trip reports to the MSR for reporting period).

g. Accumulated invoiced cost for each CLIN up to the previous month.

h. Projected cost of each CLIN for the current month.

i. Level of effort breakouts by task for the previous month.

j. Comparison data / monthly performance reports.

k. Any recommendations for updated processes and/or procedures to enhance efficiency.

C.4.2.3 SUBTASK 3 - PREPARE A PROGRAM MANAGEMENT PLAN (PMP)

The contractor shall document all support requirements in a PMP, which shall be submitted within 30 calendar days after the Task Order start date (see Section F, Deliverable 05). The PMP shall describe and formalize the proposed technical and management approaches that will be performed and implemented during the Task Orders’ period of performance. The PMP shall include milestones, tasks, and subtasks required in this Task Order. The PMP shall provide for an overall Level 3 Work Breakdown Structure (WBS) and associated responsibilities and partnerships with Government organizations.

The PMP is a living document. At a minimum, it shall be updated no later than 30 calendar days after the beginning of each option period. The contractor shall work from a Government-approved PMP. The contractor shall work from a new version of the PMP once approved by the Government.

C.4.2.4 SUBTASK 4 – PREPARE TRIP REPORTS

The contractor shall keep a summary of all long-distance travel including, but not limited to, the name of the employee, location of travel, duration of trip, and point of contact (POC) at travel location and provide a Trip Report (see Section F, Deliverable 06) documenting the activities. Trip Reports will be submitted for all Trip Requests.

C.4.2.5 SUBTASK 5 – UPDATE QUALITY CONTROL PLAN (QCP)

The contractor shall submit the QCP with its proposal. The contractor shall periodically update the QCP (see Section F, Deliverable 07) throughout the Task Order POP as changes in contractor quality control processes are implemented.

C.4.2.6 ATTEND WEEKLY STATUS MEETINGS

The contractor shall attend a weekly status meeting at PSNS with the COR and TPOC. Discussions will focus on any issues/concerns and the status of the following: projects, personnel (new hires or personnel leaving), tool purchases, anticipated travel, outstanding Government actions from MSR, and open items from the previous week. The contractor shall document any results of the meeting in a Weekly Status Report (see Section F, Deliverable 08).

C.4.2.7 SUBTASK 7 – IN-PROGRESS REVIEWS (IPR)

The contractor shall conduct Quarterly In-Progress Review Meetings at PSNS (see Section F, Deliverable 09) to discuss program, project and service status, existing or potential problems, and projected tasks and milestones. The contractor shall provide the CO, COR, and the TPOC an e-mail 3 calendar days before the meeting containing the agenda for the meeting and any materials that will be discussed during the meeting (e.g. PowerPoint presentations to be displayed, etc.). The contractor shall submit the minutes for each IPR by the close of business the following day in ASSIST.

C.4.3 TASK 3 –– NETWORK SUPPORT

The contractor shall provide support for workstations, servers, peripherals, and other telecommunications devices. The basic infrastructure components to be supported by site can be found in Section J, Attachment P. An average 80,000 feet of fiber is installed, repaired or replaced, 160,000 feet of copper is installed, repaired or replaced and approximately 9,000 network ports are installed annually.

Through escalated tiered customer support and innovation initiative projects, the contractor shall support the following operational, maintenance, and administrative functions necessary to ensure that the Navy’s IT systems at PSNS & IMF are operational and available to the users.

a. Install, maintain, design, change, troubleshoot, and remove fiber optic and copper cables for network devices, fiber and copper patch panels, wall ports, infrastructure cabinets, and maintain industry standards for labeling of all installed cable plant.

b. Install, maintain, design, change, troubleshoot and remove network devices such as routers, switches, VPN concentrators, TACLANE encryption devices and device configuration within said devices.

c. Implement, sustain, and ensure compliance to Department of Defense, and Department of the Navy, security configuration policies and accreditation requirements.

The contractor shall provide this support primarily located at the Bremerton site to devices, components and infrastructure supporting the three primary networks, datacenters and campus networks called “Command Network” (CMDNet), “Automated Access Control System” (AACS) and “Naval Nuclear Propulsion Program Network” (NNPPNet) at all PSNS & IMF Sites. The Datacenter infrastructure supports the processing, protection and transport of sensitive unclassified and classified information, specifically Navy Nuclear Propulsion Information (NNPI). The network topologies of these networks are interconnected and extend from Bremerton, WA to Bangor, WA, Everett, WA, Pt. Loma, CA, North Island San Diego, CA, and Yokosuka, Japan; as well as with our partner networks (separately accredited and administered) at Norfolk Naval Shipyard, Portsmouth Naval Shipyard, Pearl harbor Naval Shipyard and the NMCI Enterprise.

C.4.3.1 SUBTASK 1 - NETWORK ENGINEERING AND OPERATIONS

The contractor shall support the design, engineering, installation, operation, maintenance and configuration of all network device infrastructure systems. This includes interconnecting and administering switches, routers, and other network layer devices to provide data connectivity/communication to and from all Navy activities operated or supported by PSNS & IMF. The contractor shall provide the following support:

a. Engineer, configure, and manage network connectivity via DOD approved devices for routing, switching, and VPN encryption for local PSNS&IMF Unclassified Naval Nuclear Propulsion Information (UNNPI) and NNPP networks.

b. Network monitoring, reporting and support for all PSNS&IMF accredited networks and sites. This includes permanent facilities located at: Bremerton, Bangor, Everett, San Diego (North Island & Point Loma), and Yokosuka, Japan.

c. Configure and manage all network devices to standard DoD/DoN cyber security requirements (STIG, SRG, IAVA, etc.) and NAVSEA08 (Naval Reactors – OPNAVINST9210.3) for routing, switching, distribution and protection of unclassified and classified NNPI.

d. Administrate data ingress and egress of all information entering and leaving the protected enclave via Firewalls and other multiple layers of Network defense.

e. Work with the regional Electronic Key Management Systems Manager to support required classified encryption for specified connections as needed.

If performing any of the following roles the contractor will need to have a completed T5 security investigation in accordance with the Section H.4 Security Requirements of this task order:

Firewall Administrator

C.4.3.2 SUBTASK 2 - CABLE PLANT ENGINEERING AND SUPPORT

The contractor shall install, test, evaluate, certify all Outside/Inside Plant (OSP/ISP) to industry standards as well as maintain, and repair all cable plant damage due to man-made, natural or environmental damage. Cable-plant is to be tested and certified upon initial installation and at future irregular periodicities where changes or repairs occur. An average 80,000 feet of fiber is installed, repaired or replaced, 160,000 feet of copper is installed, repaired or replaced and approximately 9,000 network ports are installed annually.

The contractor shall provide the following:

a. Perform site surveys as needed and submit to PSNS&IMF Network Engineers for concurrence prior to performing new work. As part of the surveys, the contractor shall provide recommendations for placement and installation of the cable plant, type of cabling, and maintenance support requirements of cabling (located both indoors and outdoors) will be required. The contractor shall deliver a Final Site Survey Report (see Section F, Deliverable 11) within 10 working days from completion of work.

b. Installation and maintenance of datacenter cable plant, cable routing/management (e.g. tray, strapping and looming) and associated infrastructure (i.e. cabinets, enclosures, locking mechanisms, splice trays, fiber optic and copper patch-panels).

c. Maintain cable plant test results, as-built installation CAD drawings and rack elevation documentation of all network related cabinets in the datacenter and across the campus environment; to include man-hole OSP pathways and OSP penetration points (see Section F, Deliverable 12); such as Cable Plant Upgrade Design Documentation, Cable Plant Upgrade Design Drawings, Cable Plant As-Built LAN Upgrade Design Drawings, Maintenance and Repair Status Reports, Configuration Management Documentation, Operational Manuals, and Engineering Data. Updates to documentation are due 10 working days from completion of work.

d. Work directly with local facilities personnel and network engineers to coordinate outages, work permits and ongoing initiatives for infrastructure upgrades, improvements and repairs.

e. Perform pulling, installing, testing, troubleshooting OSP/ISP, copper cabling, multimode and single mode fiber optics as well as LC/SC/ST cleaning, polishing and termination; as well as supporting cable-plant installations with core-drilling, wall penetrations, installation of conduit, cable tray, various types of network cabinetry and other supporting hardware as jobs require.

f. Install and validate wireless (802.11) access points and RFID antenna spread and coverage in a wide variety of places to include but not limited to the top of light towers, the edge of buildings, drop ceilings of standard office spaces; as well as, on board naval vessels.

g. Transport cable plant and network related tools and equipment using contractor-provided vehicles to PSNS & IMF locations in support of this requirement.

C.4.4 Task 4 – Application Management

There are two major categories of application management at PSNS & IMF, i.e. corporate or enterprise applications and those developed and used locally. See Section J, Attachment Q for a list of each. The contractor shall use the Government-provided testing environment to test applications and patches. Troubleshooting and resolution shall be escalated to other contractor support personnel in this Task Order if Tier 1 Customer Support is unable to resolve the issue.

Corporate Applications The first category is support of shipyard enterprise applications, also known as corporate applications, which are developed by a central design authority (CDA), who is responsible for the management and operation for application development for all local shipyards.

Local Applications The second category is support of locally developed and maintained applications. The locally developed applications (Section J, Attachment Q) will require support at various intervals. The contractor shall provide support as either the primary application sponsor or as a backup to Government personnel. The contractor shall also support application updates and any issues that may arise within the application. The contractor shall perform re-platforming efforts and new development in.

The following is the breakout of the types of applications to be supported:

a. Access Applications that require VBA support. They may move to SharePoint or may be re-platformed over time.

b. .NET applications, both VB.NET and .NET C#. The contractor shall provide maintenance and support for new efforts. They will be updated to C# over time.

c. Coldfusion applications that are primarily Government supported. They will be updated to .NET C# over time.

d. A Powerbuilder application that is primarily contractor supported.

e. Additional applications and/or Web pages.

The corporate and local applications make use of the following technologies:

a. Microsoft .NET Framework

b. Microsoft .NET Core

c. Visual Studio

d. ColdFusion

e. MSAccess/VBA

f. Powerbuilder 12

g. Adobe CS Suite

h. Oracle

i. SQLServer

j. HPFortify

k. Relational Database Management System (RDBMS)

l. SQL server management studio

m. Adobe Acrobat X Pro

n. Office VBA

o. GIT

p. Azure DevOps 2019

q. SharePoint 2016

r. Agile development practices using source code repositories, front-end UI design, and JavaScript frameworks

s. Visual Basic Application (VBA) Solution to pull data from DBMSs for reporting and data mining

For both corporate and local applications, the contractor shall: The number of Local and Corp Apps supported listed in Attachment Q.

a. Plan, schedule, and manage the implementation of GOTS and COTS software

b. Manage and install routine and regularly scheduled GOTS and COTS applications updates

c. Prepare Test and Implementation Plans (see Section F, Deliverable 13) for COTS/Government developed applications updates

d. Execute and validate COTS/Government developed applications requirements and specifications including batch and interface processes during application release testing

e. Continuously examine and evaluate the COTS/Government developed applications data interface and batch processes, proposing technically feasible improvements to automation that will benefit the shipyard

f. Troubleshoot COTS/Government developed applications application anomalies

g. Work with internal departments as well as outside activities and agencies diagnosing and resolving problems in response to user-reported incidents, customer functional issues, technical problems, questions, or concerns

h. Provide application-level user account management consisting of:

1. Creation

2. Modifications

i. Assist the user community in creating and maintaining Business Object reports

j. Provide analysis, design, evaluation, and programming support for IT systems deployed locally at PSNS & IMF

k. Provide analysis, design, evaluation, programming, and support for web-based systems deployed at PSNS & IMF

l. Maintain working knowledge of Navy standard software

m. Troubleshoot, resolve, and document inquiries and report possible discrepancies in corporate data and associated output

n. Issue application-level passwords and maintain password database(s)

o. Manage computer-aided design/computer-aided manufacturing CAD/CAM Software

p. Install, test, and manage PSNS & IMF corporate software systems

q. Provide production customer technical support and problem resolution

r. Ensure availability and integrity of corporate software systems

s. Provide support to PSNS&IMF users of Trident maintenance and logistics systems (e.g. training, user trouble calls, software issues, etc.)

t. Execute the Strategic Systems Program (SSP) Trident Logistics Data System (LDS) Configuration Management Plan

u. Manage corporate Trident software releases from the central design authority (CDA)

v. Develop and maintain maintenance and logistics software in support of the Trident mission

w. Maintain compliance with the Navy software portfolio and certification and accreditation requirements

x. Manage Trident data and process interfaces with other Navy systems

y. Provide local application support - design, development, and maintenance

z. Provide SharePoint support - design, customization, and maintenance

aa. Provide Web Application design, development, and maintenance

ab. Provide Web Server maintenance

The contractor shall provide this support primarily on-site at Bremerton (unless telework is approved by the Government – see Section G.9 below) to networks and components located at Bremerton and other PSNS & IMF Sites (see Section J, Attachment P).

C.4.5 TASK 5 – BANGOR PRODUCTION OPERATIONS SUPPORT

At the Bangor, WA, site the contractor shall be responsible for daily printing of submarine maintenance planning and management packages and delivery of these print packages to customers in time for daily production planning meetings. Contractor production support staff shall also execute scheduled tasks, jobs, and reports using Reflections X to access TRIM12 and CmdNet to access LDS. Select tasks, jobs, and reports are scheduled to be generated regularly (e.g. daily, weekly, monthly) while others are to be generated in response to ad hoc or emergent requests from Bangor IMF production manager requests. The contractor shall contact their contractor Task Lead and the Government LDS POC if there are problems with the running of the print jobs, delivery of print jobs, or execution of requested jobs or reports. The Bangor site requires a continual presence (unless telework is approved by the Government – see Section G.9 below) five days a week, Monday – Friday, 8 hours per day, 04:30-13:00 Pacific Time.

The contractor shall:

a. Operate data processing computers and high-volume printing equipment.

b. Execute print jobs and production of large hard copy packages.

c. Distribute/deliver print packages to Bangor production planning team POCs IAW daily schedule to support mission essential Production Planning and Execution Management meetings.

d. Run and deliver production schedule reports.

e. Update parameters; run and deliver payroll reports.

f. Capture, troubleshoot, and report any problems or anomalies in task, job, or report generation or any problems with printer outputs or performance of the high-volume printers. For urgent (work stoppage) printer problems contact the printer vendor to initiate a problem report/service request and notify the Bangor POC, contractor Task Lead, and LDS POC.

g. Monitor Real-Time jobs and report issues.

h. Perform testing as requested by the Government POC.

i. Provide consumables support for Bangor users.

C.4.6 TASK 6 – SYSTEMS ADMINISTRATION

The contractor shall plan, coordinate, install, test, operate, troubleshoot, and maintain system-level PSNS & IMF hardware and software systems as listed in Attachment P. The CMDNET Windows environment is 95% virtualized in a VMware environment. CMDNET hosts around 450 servers in the virtual environment and support a user base of over 12,000 people. The Windows server environment has approximately 400 servers running versions of Windows Server 2008R2, 2012R2, and 2016. CMDNET uses Cisco Call Manager, Citrix, Microsoft Exchange, Microsoft System Center Configuration Manager [SCCM], System Center Operations Manager [SCOM], SolarWinds Orion (multiple add-ins), Splunk, Tenable Security Center [ACAS], and VMware vCenter to manage and troubleshoot various aspects of the environment.

If performing any of the following roles the contractor will need to have a completed T5 security investigation in accordance with the Section H.4 Security Requirements of this task order:

Any SECNET/NNPPNET administrator CMDNET Domain Admin CMDNET Enterprise Admin CMDNET Unix admin with ROOT access

The contractor shall perform the following:

Windows System Administration/CITRIX/VM (virtual machine)

a. Manage server account access to systems and equipment

b. Manage systems resources including performance, capacity, availability, serviceability, and recoverability

c. Implement security procedures and tools

d. Develop and document Systems Administration Procedures as needed (see Section F, Deliverable 15 for Standard Operating Procedures)

e. Resolve hardware/software interface and interoperability problems

f. Ensure systems availability, functionality, integrity, and efficiency

g. Maintain each system’s configuration

h. Manage the installation and integration of system fixes, updates, and enhancements

i. Ensure the rigorous application of information security and information assurance policies, principles, and practices in the delivery of systems administration services

j. Maintain configuration documentation of systems and equipment

k. Update disaster recovery documentation on an add needed basis

l. Maintain, monitor, and provide performance tuning (Balancing the load on the servers)

m. Perform Data backup and recovery

n. Maintain the environment of the computer data center(s) (temperature, humidity, cleanliness, etc.)

o. Monitor and analyze audit logs, report any irregularities

p. Monitor server disk storage (by user and by program) including temporary storage requirements (print queues, etc.)

q. Archive and delete unneeded files

r. Recover disk space from deleted users

s. Maintain structure of rights for accounts and groups

t. Perform system back-up functions on a daily, weekly and monthly basis as required

u. Build, maintain, troubleshoot, and repair Windows server hardware and software

v. Monitor and manage use of disk space, permissions, and connections

w. Perform physical and data security

x. Maintain server backups for disaster recovery

y. Monitor server performance and tune as necessary

z. Develop and maintain Windows server documentation

aa. Manage the Command Shipyard e-mail program (currently using Microsoft Exchange)

ab. Maintain Domain system policies to administratively enforce application and security setting for users and computers

ac. Assist in the enforcement of the Naval Shipyard Corporate Network (NSCN) INFOSEC Policy

ad. Protect NNPI and other Confidential Data as stated in NAVSEA Instruction 9210.3 series

ae. Support change and configuration management

af. Manage shared network applications

ag. Provide processes for increased functionality of centralized administration of Windows clients

ah. Provide technical support for Windows server related issues

ai. Provide anti-Virus Administration

aj. Support COTS software testing

ak. Assist in automating processes that can be automated to save man-hours, be more efficient, and have more consistent results

al. Review, plan, test, and implement applicable security technical implementation guidelines (STIG) on technologies under area of responsibility

am. Coordinate, collaborate, and work with other branches and stakeholders as needed

an. Assist/Mentor other SAs (Contractor/Government as needed)

ao. Assist in capturing metrics to assist Government on visibility of the server environment

ap. Assist other technical branches with their products and databases

UNIX System Administration

a. Manage UNIX Server user accounts

b. Monitor system performance and tune as necessary

c. Schedule and Perform system backups (Operating system and Oracle database)

d. Perform physical and data security IAW SECNAV M5510.36

e. Maintain the operating system and software

f. Build, maintain, troubleshoot, and repair UNIX server hardware and software

g. Develop and maintain Unix System Documentation (see Section F, Deliverable 16)

h. Maintain server backups for disaster recovery

i. Assist in the enforcement of the Naval Shipyard Corporate Network (NSCN) Information Security (INFOSEC) Policy

j. Facilitate protection of for official use only (FOUO), personally identifiable information (PII), and Business Sensitive Data IAW DODI 5400.11

k. Perform change and configuration management

l. Provide technical support for UNIX server related issues

m. Maintain the environment of the computer data center(s) (temperature, humidity, cleanliness, etc.) via currently utilized software for environmental monitoring.

n. Monitor and analyze audit logs, report any irregularities

o. Monitor server disk storage

p. Manage server print queues

q. Monitor system performance and tune/system resources (i.e. memory, processors)

r. Protection of NNPIand Confidential Data

s. Change and configuration management

t. Review, plan, test, and implement applicable security technical implementation guidelines (STIG) on technologies under area of responsibility

Unix Database Administration

a. Install and maintain database support software (Oracle RDBMS, Enterprise Manager, Weblogic Suite, UC4 Application Software, interface menus) in Unix production, pre-production, and development environments which includes configuration management, patching and upgrading to support hosted corporate application and interface requirements.

b. Create, maintain, and administer test, pre-production, and production databases required to support the hosted corporate applications, approximately 2-3 per week. Including the following functions:

1. Apply Application Releases, Patches, Data Releases, Emergent Data Surgery

2. Apply configuration changes

3. Maintain configuration for interfaces and Crons

4. Maintain Batch processing configuration

5. Review, plan, test, and implement applicable security technical implementation guidelines (STIG) on technologies under area of responsibility

6. Schedule Maintenance Downtimes to maximize use of production systems

7. Monitor Database Availability and Performance

8. Maintain Database Backups and Verify Backup Recoverability

9. Maintain integrity, security and access to the production databases

10. Maintain an Oracle Dataguard Configuration for the centrally hosted EFEM application database

c. Create, maintain, and administer test, pre-production, and production local databases used to supplement, extend, or maintain the databases for hosted corporate applications. (OEM, OAT, DBAPPS, NAD), approximately 2-3 per week

d. Create, maintain, and administer test, training, development databases required to support the hosted corporate applications, including periodic cloning of production environments and or refreshing back to known configurations, approximately 2-3 per week

e. Assist Application Managers to troubleshoot, trace, capture and/or diagnose application problems related to malformed data or functionality of the application or application interfaces in the database environment

f. Maintain documentation to support baseline processes, repeatable processes, database casualty recovery, server casualty recovery, and database/server disaster recovery

The contractor shall provide support primarily on-site at Bremerton (unless telework is approved by the Government – see Section G.9 below) to networks and components located at Bremerton as well as remotely at the other PSNS & IMF Sites.

Splunk System/Application Administration

a. Manage Splunk Server user accounts

b. Monitor system performance and tune as necessary

c. Schedule and Perform system backups (Splunk system and Splunk database)

e. Maintain the operating system and software

f. Build, maintain, troubleshoot, and repair Splunk server hardware and software

g. Develop and maintain Splunk System Documentation

h. Maintain server backups for disaster recovery

i. Assist in the enforcement of the Naval Shipyard Corporate Network (NSCN) Information Security (INFOSEC) Policy with minimum impact to the daily Shipyard business

j. Facilitate protection of for official use only (FOUO), personally identifiable information (PII), and Business Sensitive Data

k. Perform change and configuration management

l. Provide technical support for UNIX server related issues

m. Monitor and analyze Splunk audit logs, report any irregularities

n. Monitor server disk storage

o. Manage UNIX Server user accounts

p. Monitor system performance and tune as necessary

q. Maintain operating systems and software

r. Protection of NNPI, NOFORN, and other Confidential Data

s. Change and configuration management

t. Provide technical support for UNIX server related issues

u. Implement and monitor Navy security policies

System Architect Services

a. Problem analysis, requirements analysis, solution alternatives analysis, design and planning of IT systems and data center systems

b. Contribute to and propose innovations, continually evaluate new technologies and trends and deliver proposals/recommendations for projects, technology or processes to improve efficiency and effectiveness across systems

c. Develop strategies for IT system and data center modernization; deliver architecture and technology recommendation

d. Consult with Government to support perform analysis of Data Center environmental systems, architecture and management systems and aid in the management of Data Center maintenance

e. Support Technical Division with strategic planning of systems maintenance and maintenance and upgrade planning that greatest stability, scalability, and uptime

f. Lead or assist project teams in delivering technical evaluations, risk analysis, analysis of alternatives, and in developing project charters, project schedules, stakeholder analysis and other artifacts

g. Assist the Government in defining quality standards, quality measurement, effective resourcing options for its IT and engineering projects

h. Collaborate with technology and business stakeholders to gather requirements and successfully deliver projects and IT systems into Test and Production environments

i. Develop and recommend IT business processes and technology solutions that contribute to effective system administration, continual improvement of IT service delivery within the Technical Division and IT Department

j. Propose and develop tools and processes that automate system administration and monitoring tasks

k. Assist PSNS Technical Division in communications and cross-shipyard collaboration to promote automation and adoption of high-availability systems

l. Plan and perform maintenance and upgrades for critical IT systems and infrastructure including Data Storage Systems (e.g. NETAPP), Network Monitoring and Management systems (e.g. SOLAR WINDS, SCCM, CENTRIFY)

m. Assist in defining, planning and executing a multi-year IT Technology Roadmap; addressing lifecycle planning of infrastructure, applications, CI/CD, business processes, and data center infrastructure

n. Recommend and assist in developing processes, metrics, and SLAs

o. Lead and assist in configuration, maintenance, optimization of network and IT monitoring tools/systems; continually improve automation processes and increase effectiveness of system alerts in order to increase the efficiency and effectiveness of systems administrator, network management and cyber security teams

C.4.7 TASK 7 – INFORMATION ASSURANCE

Information Assurance (IA) supports the Cybersecurity Policy, Audit, and Defense of the organization.

The contractor shall work closely with the PSNS & IMF Information Systems Security Manager (ISSM) and staff to assist in the development of formal policies and procedures to facilitate the protection of U.S. Government sensitive unclassified and classified information and the security of the various PSNS & IMF information systems and networks. The contractor shall review PSNS & IMF, Naval Sea Systems Command (NAVSEA), Department of Defense (DoD) and Department of Navy (DON) policies, procedures and guidelines and shall assist in the creation / update of appropriate policy documents for implementation across the organization as required. The contractor shall assist appropriate Government personnel in determining IA requirements, aid in the development of policies and procedures for implementation and provide support in implementing these mechanisms and processes to ensure policy enforcement. This includes all activities in support of Cybersecurity Administration, Assessment and Authorization (A&A), and Cyber Network Defense required to proactively ensure the confidentiality, integrity, and availability of organization’s networks.

C.4.7.1 CYBERSECURITY DIVISION

a. Planning. Support strategic analysis, planning, and communication of current and future Cybersecurity Policy, Audit, and Defense products and services provided to the PSNS & IMF. Workload includes Managing Branch Descriptions, List of Products and Services aligned to employees on Organization Charts, analysis of work hours mapped to the Products and Services, long range goal planning, project tracking, and Self-Assessments for Division of 40 Cyber employees in three Branches.

b. Analysis. Provide technical data analysis of various Key Performance Indicator (KPI) metric data and format for presentation in Excel, PowerPoint, and Email communications. Workload supports weekly Cyber Metrics reports like, Always Be Compliant (ABC), Cyber Security Compliance Assessment (CSCA), and NAVIFOR Spot check reports that tracks key indicators across several Branches in the IT Department to help ensure Cyber Readiness at All Times.

c. Reports. Prepare the existing weekly and Monthly Analysis reports for management. Additional examples include weekly Commanding Officer’s summary report, monthly cyber metrics reporting, and training status reports. Anticipate 20% flexible capacity for unplanned data calls and Ad-hoc reporting for external agencies and continual process improvement (CPI).

d. Inspections. Perform Project Management of past and future Inspections. Workload includes up to twelve weeks of Cyber Inspections per year, managing resolutions for previous inspection findings, managing future inspection logistics, inspection requirements, weekly status meetings, reports, coordinating Executive level briefings, documenting new findings, and producing Lessons Learned PowerPoint presentations.

C.4.7.2 CYBERSECURITY ADMINISTRATION

e. Policy. Develop and maintain Cybersecurity (CS) instructions, Standard Operating Procedures (SOPs), and Desk Guides for the implementation of mandatory technical and IT security standards. Workload includes 4 primary Shipyard Instructions, 30+ Departmental SOPs, and Desk Guides for approximately 30 Cybersecurity Services each with up to 5 specific work tasks. Additional work includes Memoranda Of Understanding (MOUs); all formatted in accordance with the Navy standard correspondence manual.

f. Training. Develop, present, and continuously improve Cybersecurity training materials for the organization. Provide Cybersecurity training for small and large audiences. Workload may include presentations, articles, public emails, flyers, electronic displays, social media, education material, CBT training, Annual training tracking and reporting, which leads to developing a Cyber Safety working culture in the organization and drives user behavior to meet inspection requirements of Zero Cyber Events in the previous 6-month period. Weekly – New Employee Orientation for 50-100 people; Monthly – IT Coordinator Training for 50, Monthly Shop stand up QA for 30, weekly Cybersecurity Vulnerability briefings for 25, Quarterly – Leadership development training for 50.

g. Records Management. Maintain current and updated Cybersecurity documentation in accordance with Navy Records Management and retention requirements as listed in DON Records Management Program manual. All correspondence must be technically correct and formatted in accordance with governing instructions. Maintain a Documents Library and SharePoint Presence for centralized Cyber communications organization.

h. CSWF. Assist with management, tracking, reporting, and documentation required for up to 300 employees of the organization in the Cybersecurity Workforce (CSWF) Program.

i. Programs. Manage Cybersecurity programs like removable media, physical security inspections, Cyber incidents investigations, Server Certificates, Functional Tokens, reporting and record keeping. Workload includes over 100 encrypted USB devices, 200 Functional Tokens, 500 Server Certificates, and 2 to 3 Cyber Incident investigations each week requiring up to 6 hours of tracking and reporting requirements each.

j. Accounts. Assist with the management, tracking and processing of various PSNS&IMF computer accounts, which include NNPPNET, NMCI/NNPI, CMDNET, Privileged Access, SIPRNET and Functional Accounts. Workload includes accounts for approximately 15,000 employees and an average of 100 Account tickets every week.

k. Spills. Maintain Electronic Spillage Tracking for all Electronic Spillage (classified information passed over an unclassified line) activities across PSNS & IMF enterprise. PSNS & IMF tracks E-Spills based on classification code, violator of the spill, source, recipients, and subject. PSNS & IMF reports immediately when a spill is committed and weekly until the spill is closed. Workload includes 5 to 10 Spills each week that can potentially require full time support for investigation, documentation, coordination, and communication.

C.4.7.3 CYBERSECURITY AUTHORIZATION

l. RMF. Provide Assessment and Authorization (A&A) documentation for submission to the Navy Authorizing Official (NAO) using DISA Risk Management Framework (RMF) principles, generally reporting in the DoD eMASS program. Workload includes 4 Authority to Operate (ATO) packages typically requiring 3 FTE per ATO to maintain Documents, Technical Testing, Record Keeping, Tool Proficiency, Web Reporting, stakeholder coordination, and professional communication with external agency representatives.

m. Tools. Provide technical expertise in a broad spectrum of technical tools required to effectively perform A&A tasks. Workload includes proficiency in eMASS, Splunk, Palo Alto, Red Seal, Tenable NESSUS ACAS, LEM, VRAM, SCCM, which are constantly evolving. The contractor is required to have or attain and maintain training and performance proficiency in the tools required.

n.…