EIMS PWS v2.4 - 7-30-24 (1).pdf

PERFORMANCE WORK STATEMENT (PWS)

Environmental Information Management System

Technical Support Services

1. INTRODUCTION: U. S. Fleet Forces Command (USFF) is tasked by Chief Naval Operations (CNO) to train, certify, and provide combat-ready Navy forces to combatant commanders that are capable of conducting prompt, sustained naval, joint, and combined operations in support of U.S. national interests. Fleet Installations and

Environment Directorate (N46) implements, manages, and oversees programs required to deliver ready platforms and systems to the combatant commanders by leading efforts to integrate infrastructure planning, infrastructure risk management, and infrastructure readiness across Type Commands and to provide synchronization between them. N46 also implements guidance, direction, and statutes pertaining to environmental policies, requirements, and programs, ensuring alignment in support of current and future Fleet readiness.

a. Environmental Information Management System (EIMS). An enterprise geo-referenced information management system that provides multiple integrated tools, capabilities, and data through a single Navy-owned, USFF-managed access point. EIMS supports between approximately 500-1000 users, Navy environmental, natural resources, and range sustainment, in the following ways:

i. Models and automates typical project administrative functions to enhance collaboration and facilitate document production;

ii. Hosts authoritative Navy geospatial and tabular data and documents to promote accurate analysis and reporting, and consistency across product lines;

iii. Hosts applications critical to Navy training and range sustainment;

iv. Protects Navy data in a secure environment; and

v. Provides authorized users with 24/7 access to necessary data and capabilities.

b. EIMS Associated Applications. Applications hosted on EIMS:

i. Protective Measures Assessment Protocol (PMAP). Informs unit commanders of required protective measures for specific at-sea training events to mitigate potential impacts to federally protected marine resources, thereby facilitating compliance with applicable permits and laws.

Navy surface ships, submarines, and aircraft squadrons can access PMAP web-based and downloadable versions on either EIMS or EIMS-Classified (EIMS-C).

ii. Weapon Danger Zone Tool. Models explosive danger zones surrounding aim-points on air-to-ground bombing ranges, calculating footprints from ordnance type, aircraft, run-in heading, surface composition, etc. The Weapons Danger Zone tool resides on EIMS.

iii. Operational Range Clearance. Supports clearance and disposition of munitions and target debris and unexploded ordnance from Navy operational air-to-ground bombing ranges. The Operational

Range Clearance application consists of hand-held field data collectors developed and maintained by the EIMS team to support clearance and disposition processes and supporting tools and database on EIMS.

iv. Sonar Positional Reporting System. Records Navy sonar usage data for permit compliance reporting and marine mammal stranding event response. It includes a parsing tool to extract sonar data from formatted Navy messages, and then stores it in EIMS-C.

v. Permitting Dashboard. A web-based software tool used by Navy and non-Navy partners that work together to schedule events and milestones that can span a seven-year period. The tool pulls a

Project's critical elements (milestones, sub-tasks, action items, responsible party, and task status) into one visually appealing product. The tool automatically imports and displays the data from an uploaded Microsoft Project schedule file indicating Project, consultation, and task status.

vi. Public Commenting Administration. A tool that can accept, process (e.g., check for key words), and store unfiltered comments and attachments until the individual environmental planning projects download them for comment review, adjudication, and inclusion in the Administrative

Record file.

vii. Range Condition Assessment Tool (RCAT). A web-based tool used by CPF, Naval Air Systems

Command, Naval Sea Systems Command and USFF to conduct range condition assessments. The tool contains questions designed to lead users though a range condition assessment.

viii. Stewards of the Sea. Houses Stewards of the Sea outreach materials including videos, printed material, and other resources.

ix. Afloat Environmental Readiness Tracker. Aids the crews of ships and submarines to comply with multiple afloat environmental and waste management regulations and policies, such as Uniform

National Discharge Standards, Afloat Regulated (Foreign) Garbage Guidance, Ocean Dumping, Afloat Oil Spill Response, etc. via an Afloat Compliance Webpage gathers relevant references, training videos and course schedules, points of contact, award guidance, and port environmental manuals into a single convenient webpage.

2. OBJECTIVE

Acquire technical support to develop, manage, maintain, and sustain the capabilities and data of EIMS and associated applications in all its environments.

3. SCOPE OF WORK

a. Tasks and Qualifications. Contractor personnel shall collectively possess the knowledge, skills, and experience to perform all tasks delineated in Section 4. The offeror must provide documentation in the form of personnel qualifications that includes operational experience in each of the personnel requirements areas delineated in Section 5.

b. EIMS Operating Environments. Contractor shall support EIMS in all its environments:

• Navy Commercial Cloud o Unclassified Public Website (shared environment) o Classified Website (shared environment)

c. SECRET Clearance Requirements. This task order includes development, testing, and sustainment of capabilities and data in EIMS-Classified (EIMS-C), a classified environment hosted in a cloud environment. To accomplish these tasks, all Software Application Developers and System Administrator(s) on the Contractor team require SECRET clearances in order to access the Secret Internet Protocol Router

Network (SIPRNET). Unless Contractor has its own Defense Security Service-cognizant controlled access area certified for SECRET information and below, these personnel will need to travel to Government facilities that can provide SIPRNET access on a regular basis. Also, PMAP shipboard application integration testing may require travel to Navy ashore facilities with appropriate shipboard network load-outs and secure compartments on afloat platforms while pier-side.

d. Cybersecurity. Contractor shall maintain EIMS and associated applications in all environments in a compliant cybersecurity posture in accordance with Cybersecurity (reference a) and Department of Navy

(DON) Cybersecurity Policy (reference b) at all times. U.S. adversaries conduct persistent, increasing attacks on Department of Defense (DOD) information systems, resulting in stringent and frequent cybersecurity orders, guidelines, bulletins, etc. Contractor will need to quickly and correctly identify and correct vulnerabilities to ensure continuous system operation.

4. TASKS/REQUIREMENTS

4.1 Engineering and Integration Services

Contractor shall provide software systems engineering and integration services to achieve continuous improvement in reliability, ease of operation and maintenance, optimal performance, and increased efficiency via updated technology from concept development through deployment, operations and system retirement. Specifically:

a. System Evaluation. Evaluate system configuration and integrated software compatibility of EIMS and associated applications, system and equipment design concepts, and operational performance. Identify issues and recommend possible system improvements. Evaluate opportunities for EIMS and associated applications to interoperate, to the maximum extent practicable, with existing and planned systems and applications of other DOD and federal departments and agencies, and non-governmental agencies, as required based on operational context, in accordance with Interoperability of Information Technology (IT), Including National Security Systems (reference c).

b. System Update Planning. Gather and prepare requirements for the software engineering update process.

Develop and submit for government approval technical plans for system design, evaluation, installation, and integration.

c. Development Guidelines. Use object-oriented principles to include Object/Class, Inheritance, Polymorphism, Information Hiding, and Interfacing coding methods to make source code modular and easy to update.

d. Commercial Off-the-Shelf (COTS). Favor modifying COTS software to satisfy system requirements over creating custom code. Investigate alternative COTS software and data system architecture, considering implementation schedules, interface problems and solutions, life cycle support issues, and plans of actions and milestones.

e. (S) System Update Implementation. Incorporate and integrate software and hardware updates according to government-approved documentation, drawings, test plans and procedures. Develop and adhere to coding standards and conduct code reviews during all cycles of development. Provide technical support to EIMS users and the EIMS program manager including investigating, troubleshooting, and hands-on assistance with government cloud brokers, and other government laboratory, shore, or shipboard sites during installation.

f. (S) Configuration Management. Use a Government approved software subversion tool to maintain version control and a historical archive of all EIMS, PMAP, and associated application source code. Check in all in-work development at least every ten-business days.

g. Meetings. Provide development updates for EIMS Project meetings. Highlight any system unavailability resulting from development work. Compile and distribute meeting minutes to all Government attendees if required and assist with action items.

4.2 Operational Engineering Services

Contractor shall sustain operations of EIMS and associated applications with a system availability of at least 95%

(not including downtime contributions caused by data center issues) through adherence to established procedure, expeditious response to issues, and preventive maintenance. Specifically:

a. Facility Evaluation. Assess suitability and condition of existing and proposed computer facilities on all

EIMS environments.

b. System Sustainment. Repair deficiencies of EIMS and associated applications installed at all environments found during normal operations. Provide technical support to deployed systems. Recommend options for long-term fixes when appropriate. Develop system approaches for recommended improvements, installation, and maintenance of equipment systems, subsystems, or components.

c. Standard Operating Procedures (SOP). Operate and maintain assigned systems in accordance with government-approved standard operating and maintenance procedures that define system security, operations, maintenance, data management, configuration management, user training and user problem reporting and tracking mechanisms.

d. System Documentation. Provide technical input to the business analyst on system and equipment documentation such as Software Design Documents, Software Requirements Specifications, Operational

Capability Requirements, system operating and maintenance manuals, and other technical manuals and drawings.

e. Software Versions. Perform software systems maintenance and configuration management. Incorporate updated versions of COTS software as soon as practicable after briefing (Contracting Officer

Representative (COR) on potential system impacts and gaining Government approval.

f. Cybersecurity. Perform system and code scans. Assist with implementing cybersecurity guidelines, orders, bulletins, etc. as required by law, regulation or Navy/DoD policy. Policies include, but may not be limited to those in section 14.1.

g. Accreditation. Manage processes for periodic reauthorizations and emergent changes to authorizations for

EIMS, EIMS-C and downloadable PMAP accreditations in accordance with Risk Management Framework

(RMF) for DOD Information Technology (reference d) and Navy Authorizing Official (NAO) Guidance

Memo; Approval of Changes to RMF Authorized Systems, Networks or Applications (reference e), respectively. Update and maintain technical diagrams and documentation as required to support accreditation processes in Enterprise Mission Assurance Support Service (eMASS) per the eMASS User’s

Guide (reference f).

h. Certification. Maintain the shipboard interoperability certification for downloadable PMAP via the application integration process outlined in USFF/CPF C5ISR [Command, Control, Computers, Communications, Cyber, Intelligence, Surveillance and Reconnaissance] Modernization Policy (reference g).

4.3 Software Design Services

Contractor shall continuously strive to extend the interface design and organization of the EIMS web portal and

PMAP application to improve the user experience. Specifically:

a. Requirements Generation. Work with end users and other stakeholders to gather user requirements, then translate complicated business problems into actionable designs and highly usable Web applications.

b. Design Standards. Develop design standards in consultation with EIMS user community and inputs/feedback received that create a consistent experience across the EIMS portal, ensuring all interfaces adhere to a consistently high standard of user-centered design.

c. Software Update Design. Lead the interaction design for product updates that have a user interface design component, guiding project teams through user-centric design methodology. Determine appropriate architecture and other technical solutions and make relevant recommendations to the Government.

d. Design Documentation. Create interaction design documentation, including site maps, process flows, wireframes, storyboards, and design documents.

4.4 Database Support Services

Contractor shall provide database development and administration support to develop, upgrade, and maintain database capabilities, and monitor database performance and tune as necessary. Specifically:

a. Database Development. Maintain, update, and upgrade Structured Query Language database hardware and software on EIMS and EIMS-C Production systems, applications, and technology platforms. Establish and apply standards and best practices for Structured Query Language and Procedural Language for Structured

Query Language using Packages, Procedures, Functions, Triggers, Sequences, Indexing, Views, and

Materialized Views. Develop and maintain normalized schemas using relational and object hierarchical practices. Establish and comply with SOPs for operating, maintaining, and improving data sources and schemas. Provide configuration management of all Oracle objects. Document all database changes, job schedules, and developmental tasks.

b. Database Development Support. Assist application and web developers as needed.

c. Database Administration. Perform database security administration, data integrity checks, back-ups, recovery planning, capacity planning, data dictionary maintenance, performance monitoring, troubleshooting, and tuning. Review system event logs daily to identify issues. Manage and continuously monitor scheduled jobs and security including user accounts, security roles, auditing, and checking for security problems. Provide quarterly summary reports detailing the status of backups conducted.

d. Database Administration Support. Assist system administrator as needed to install, configure, secure, and optimize database engines and tools for data analysis, data transfer, messaging, and scheduled jobs.

4.5 Systems Administration Services

Contractor shall provide system administration services to monitor, manage, troubleshoot issues, configure, and maintain all EIMS environments and individual team members’ Government-furnished laptops and peripherals.

Specifically:

a. Monitoring. Audit System and Security logs for problems and vulnerabilities. Analyze and report system resource utilization and system availability for each of the EIMS components on a monthly basis.

b. Troubleshooting. Conduct end-to-end analysis of networking problems involving switches, routers, workstations, servers, virtual local area networks, and other IT devices and services. Assist users with

Common Access Card (CAC) problems including installation and driver issues. Identify, mitigate and resolve cybersecurity issues.

c. Configuring. Serve as Information Systems Security Engineer for EIMS and associated applications.

Integrate new technologies. Install, configure, and manage Operating Systems, including Windows Servers and workstations, and all application-level COTS software products. Coordinate with geographically dispersed personnel on the Contractor team and at cloud to install approved software patches and upgrades according to established procedures. Load and configure multi-Vendor applications in a Citrix or other required environment. Create, update, and maintain accurate EIMS system drawings.

d. Backups. Create, maintain, and adjust backup strategies for EIMS assets and service. Maintain and verify scheduled backups. Create and maintain backups of Oracle data.

e. Documentation. Create, update, and maintain user and administrative SOPs.

f. System Access. Manage Users and Groups (Local and Domain), Group Policies and key Internet

Information Services administration functions on Windows Server Update Service to include installation, configuration, and testing.

g. Dynamic Host Configuration Protocol. Setup and maintain scopes, authorize and de-authorize, and add and remove functions from test servers. Work with redundant scopes without causing internet protocol address conflicts.

h. Domain Controller. Manage Active Directory.

i. Certificates. Generate, request, and install server certificates.

4.6 Cybersecurity/Information Assurance Services

Contractor shall provide cybersecurity/information assurance services for all EIMS environments and ensure compliance with all RMF and Authorization to Operate (ATO) requirements. Specifically:

a. Cybersecurity. Analyze, monitor, and maintain the EIMS cybersecurity posture in accordance with references a and b. Contribute to EIMS security guidelines, plans, and policies. Comply with

Communications Tasking Orders and Security Technical Implementation Guidelines, and apply COTS, Government Off-the-Shelf, Operating System (OS), and application-level security patches including

Information Assurance Vulnerability Alerts, Information Assurance Vulnerability Bulletins, Technical

Advisories, etc. within required timelines. Report information assurance status monthly, including

Communications Tasking Orders remediation strategy, compliance metrics, or mitigation plan templates for reporting in Vulnerability Risk Assessment Management System. Support compliance with RMF requirements.

b. Accreditation and Certification. Assist with accreditation and shipboard certification processes (Sections

4.2 g and h, respectively) as required.

c. Monitoring. Audit System and Security logs for problems and vulnerabilities.

4.7 Data Management Services

Contractor shall create, acquire, review, and integrate geospatial data into EIMS and maintain its currency and availability to the EIMS user community. Specifically:

a. EIMS Data Working Integrated Product Team (WIPT). Provide member(s) to the USFF-chaired Data

WIPT and support its strategic planning and data assessment functions. Participate in periodic meetings as scheduled by the Data WIPT Lead, and compile and distribute meeting minutes to all attendees as required.

b. Data Research. Identify external data sources relevant to Navy environmental, natural resources, range sustainment, and operational energy missions. These sources could be governmental [National Oceanic and

Atmospheric Administration, National Geospatial Intelligence Agency, Bureau of Energy and Mines, etc.] or non-governmental such as private university natural resources datasets. Determine their compatibility with EIMS and document their access and acquisition requirements.

c. Geospatial Data Specifications. Ensure Geographic Information System (GIS) data for EIMS and associated applications from external sources and project deliverables comply with format and specifications in the Fleet Project Electronic Information Guidance Document, Section 12.2 a. Relevant standards include, but are not limited to, Spatial Data Standard for Facilities, Infrastructure, and

Environment and Federal Geographic Data Committee. Conduct Quality Assurance of project GIS data deliverables and work with project GIS Subject Matter Experts (SME) to make corrections as necessary.

d. Geospatial Data Integration. Work with EIMS Data WIPT to create new data and/or integrate newly acquired GIS data from external sources and project deliverables into EIMS and associated applications.

Test new data in the Development and Test/Quality Assurance environments to ensure it displays properly and does not compromise system functions, then publish it on the Production servers. Facilitate data exchange with multiple data providers and other systems.

e. Geospatial Data Maintenance. Maintain data items and services as needed, including maintaining metadata records and managing links to data and data services. Review, document, and propose updates to EIMS data models and technologies to maintain data currency. Maintain a catalog listing all current web map services and associated descriptive data available in EIMS, updated quarterly.

f. Outreach. Assist with the development of training materials of EIMS GIS capabilities and data products, and work with team Training Specialist to provide face-to-face and video teleconference demonstrations and tutorials to EIMS user community. These activities may require occasional travel to regional offices, installations, or other Continental United States (CONUS) or Outside of the Continental United States

(OCONUS) locations.

g. Customer Interface. Manage GIS Data Requests submitted in the EIMS Feedback Log, and work directly with users through the EIMS Data WIPT to formulate and implement solutions. Assist users to generate maps, presentations, tutorials, and detailed program reports when requested.

h. GIS Administration. Assist in GIS component configuration.

4.8 Documentation and Quality Control Services

Contractor shall generate clear, concise technical documents to record contract compliance, system performance and configuration, information security posture, routine program administration, and other matters as directed by the

Government. Specifically:

a. System Documentation. Maintain and update system and equipment documentation such as Software

Design Documents, Software Requirements Specifications, Operational Capability Requirements, system operator, maintenance and configuration management manuals and guides, as well as other technical manuals and drawings.

b. System Alterations. Document impact of engineering changes on system configuration, performance, reliability, maintainability, availability, logistics support, safety, information security posture, life cycle cost, etc.

c. Cybersecurity. Assist with cybersecurity documentation (Sections 4.5 a) as required.

d. Accreditation and Certification. Assist with accreditation and shipboard certification documentation

(Sections 4.2 g and h, respectively) as required.

e. Administration. Prepare, update, and distribute as required routine administrative documentation including

SOPs, software documentation, deliverable documents delineated in Section 10, and other documents as directed by the Government. Maintain and provide all documents in electronic format and hardcopies when requested.

f. Technical Writing. Generate required technical documentation that is accurate, comprehensive, properly formatted, and understandable to the intended audience.

g. Quality Assurance/Quality Control. Provide quality assurance and quality control for existing system capabilities and system capabilities under development. Document deficiencies and participate in creating corrective action plans to address deficiencies.

4.9 Training, Orientation, and Outreach Services

Contractor shall provide training, orientation, and outreach services to the EIMS user community, primarily online with up to approximately four face-to-face sessions per year as required. Specifically:

a. System Familiarization. Assist with the design, development, and delivery of Training & Orientation curricula for the EIMS user community. Update to accommodate new data or capability releases, or when indicated from user feedback.

b. Outreach. Inform the EIMS user community of new datasets and capabilities via the EIMS Welcome Page News section, periodic newsletters, blast emails, etc. Organize and promote Training, Orientation, and

Outreach opportunities to the EIMS user community. These activities will require travel to regional offices, installations, or other CONUS or OCONUS locations up to approximately four times per year.

c. Online Help. Maintain online Help content, including mouse-over hover tips, Quick Guides, etc. Develop computer-based training modules, and support interactive training, either via video teleconference or in person.

4.10 Help Desk and User Liaison Services

Contractor shall provide the EIMS user community with convenient access to the team to ask questions, report problems, and receive status or disposition of their issues.

a. EIMS Application Help Desk Hours of Operations. 0800 -- 2200 EST Monday through Friday excluding federal holidays.

b. Response Times.

i. Calls received during Help Desk Hours of Operation. Respond same day to callers with questions

(Tier 1) and procedural issues (Tier 2). Report system failures and outages (Tier 3) to cloud brokers and EIMS SMEs immediately and provide caller with status within one hour of notification and periodic updates thereafter until issue has been resolved.

ii. Calls received outside Help Desk Hours of Operation. Respond to Tiers 1, 2, and 3 callers no later than 0900 the next business day. Team may delay initiating corrective action for an EIMS and associated applications issue until normal working hours unless notified by COR that it requires immediate response.

c. Feedback Log. Monitor, update status, and maintain EIMS Feedback Log, alerting appropriate EIMS SMEs of new issues. Send email acknowledgement to users who enter feedback into a Feedback Log and periodic email updates thereafter.

d. Documentation. Document user trouble calls placed directly to EIMS Help Desk. Compile monthly the list of trouble calls and user feedback from all sources and their dispositions.

e. User Liaison. Assist users to register accounts and other routine operational matters. Manage user accounts and report metrics as required.

4.11 Test and Evaluation Services

Contractor shall test functionality and outputs following an engineering change to ensure system continues to work as advertised and has not been inadvertently impacted. Specifically:

a. Standard Operating Procedures (SOP). Conduct independent engineering review and technical evaluation of design, functional and test specifications, plans, and user procedures. After each review, confirm accuracy, completeness, and conformance to directives and adequacy of test requirements and schedules using applicable guidelines.

b. Testing Protocol Research. Research available military, government, and commercial specifications and other technical documents, and provide test-planning inputs, including test scenarios and data requirements.

c. Test Planning. Prepare test plans using case scenarios for users and design processes for developers.

Review program test and evaluation plans to assure compliance with test objectives and methodologies.

Evaluate proposed equipment solutions against requirements documentation and mission profiles.

d. Acceptance Testing. Examine Government-furnished engineering development deliverables for adequacy of technical approach, adherence to specification and PWS requirements, software and hardware designs, and related deliverables.

e. Developmental Testing. Evaluate system alterations per the test plan (Section 4.10 c) and document system responses. For changes to user interface or functionality, employ members of the user community to test system operation and output.

f. System Health Monitoring. Perform routine operational and systems testing.

g. Test Result Analysis. Assess government equipment and systems design under test by comparing actual performance to system specifications and equipment. After each test, provide recommended improvements for Government approval.

h. Independent Review of Test Results. Conduct independent engineering reviews and technical evaluations of written test results, test reports, and technical reports. After each review, provide inputs relative to the accuracy and adequacy of the documentation.

i. Cybersecurity. Perform computer security test and evaluation activities.

j. Test Reports. At the conclusion of each testing cycle, produce test report for Government review and approval. Coordinate meeting to discuss test result findings if requested.

k. Automated Testing. Evaluate automated testing solutions and implement when approved and warranted.

4.12 Market Research Services

Contractor shall stay abreast of trends and developments in the IT commercial market to identify candidate new and emerging technologies for potential longer-term system upgrades and enhancements of EIMS and associated applications. Specifically:

a. Market Surveys. Research options available on the open market, including applicable COTS software, to resolve system issues, improve performance, or facilitate system migration into the DOD cloud if directed.

Describe objectives and capabilities of alternatives. Research best practices within government and industry for applicable market processes.

b. Research Vehicles. Conduct technology research, technology assessments, risk analyses, and project reviews. Participate in Advanced Concept Technology Demonstrations and other DOD Programs and develop prototypes.

c. Concept Evaluation. Conduct proof of concept demonstrations, usability testing, customer studies of prototypes and existing interfaces, etc. to evaluate candidate technologies. Estimate difficulty in achieving project goals with planned or proposed technical approaches, costs, schedules, and/or technical risks.

Provide recommendations for further development or revised course of action to Government.

d. Risk Management. Develop risk management strategies for candidate technologies and identify other related technical issues.

4.13 Program Management Services

Contractor shall oversee task order execution and administration to ensure contractor team complies with task order requirements. Specifically:

a. Administration Management. Conduct efficient management of the Contractor workforce and project administration, financial, and reporting tasks.

b. Task Order Principal. Function as point of contact to the COR for all contractual matters, including contractor-to-contractor teaming arrangements.

5. PERSONNEL REQUIREMENTS

a. Contractor shall organize, maintain, supervise, and direct a workforce qualified and capable of effectively performing the work identified in this PWS, and maintain uninterrupted support service as stated in their recruitment and retention plan. The following table provides estimated Full-time Equivalent (FTE) EIMS

Technical Support Services team composition.

ESTIMATED LEVEL OF EFFORT PER YEAR

Labor Category FTE Hours Total

Software/Application Developer 3 1,920 5,760

Systems Administrator 1 1,920 1,920

Cybersecurity/Information Assurance 1 1,920 1,920

GIS Analyst 1 1,920 1,920

Business Analyst/Training Specialist 1 1,920 1,920

Help Desk Administrator/Tester 1 1,920 1,920

Task Order Manager 0.1 104 104

TOTAL 15,464

b. Personnel must be current employees with current requisite clearances, or contingent hires with signed letters of commitment and current requisite clearances for the proposed positions. Government acknowledges that contractor administrative processes for new contingent hires are not immediate, and the transfer of clearances may cause delay in availability of such personnel. The Phased Transition Plan shall account for these factors (see Section 8.2.1).

NOTE: Government does not pay for contractor certifications or certification preparation training.

5.1 Software/Application Developer

5.1.1 Responsibilities.

a. Implement Section 4 Tasks/Requirements:

• 4.1 Engineering and Integration Services

• 4.2 Operational Engineering Services

• 4.3 Software Design Services

• 4.4 Database Support Services

b. Assist with Section 4 Tasks/Requirements:

• 4.8 Documentation Services

• 4.9 Training, Orientation, and Outreach Services

• 4.10 Help Desk and User Liaison Services

• 4.11 Test and Evaluation Services

• 4.12 Market Research Services

5.1.2 Education.

• Bachelor's Degree in computer science or information technology (IT)-related field with at least 5 concurrent years of relevant experience within the past 10-15 years (see Section 5.1.3); or

• Associate’s Degree in IT-related field or Professional Developer Certificate in a field relevant to EIMS with at least 10 concurrent years of relevant experience within the past 10-15 years; or

5.1.3 Qualifications.

• SECRET Clearance. Required.

• Relevant Experience.

o Developed geospatial web and desktop applications in .NET framework via ASPX, C#, Visual

Basic, and Java Script while leveraging Environmental Systems Research Institute and Oracle spatial products.

o At least one developer on the team shall have geospatial development experience.

o At least one developer on the team shall have database development and administration experience.

• Cybersecurity Workforce (CSWF) Designations. Information Assurance Technical (IAT) Level II in accordance with Cyberspace Workforce Management (reference h) and Information Assurance Workforce

Improvement Program (reference i). Contractor personnel shall obtain and maintain CSWF qualifications per following timelines:

o Task Order Start Date.

▪ IAT Level II DOD-approved 8570 Baseline Certification. List of acceptable baseline certifications available at https://cyber.mil/cwmp/dod-approved-8570-baseline-certifications/. Steps to obtain and register a DOD 8570 Baseline Certification available at https://cyber.mil/cwmp/steps-to-obtain-a-dod-8570-baseline-certification/.

▪ Appropriate Computing Environment/Operating System (CE/OS) Certificate.

Information about CE/OS Certificates at https://cyber.mil/cwmp/cwmp-faqs/#toggle-id-

33.

o Within 6 Months of Task Order Start Date. Balance of qualifications for IAT Level II

Certification. Summary of qualification requirements available at https://cyber.mil/cwmp/summary/.

NOTE: Contractor shall provide at least one fully certified IAT Level II Software/Application

Developer at Task Order Start Date.

o Sustainment Training/Continuing Education Requirements. 20 to 40 hours annually, and at least

120 hours over 3 years.

5.2 Systems Administrator

5.2.1 Responsibilities.

• 4.5 Systems Administration Services

b. Assist with Section 4 Tasks/Requirements:

• 4.6 Cybersecurity/Information Assurance Services

• 4.8 Documentation Services

• 4.9 Training, Orientation, and Outreach Services

• 4.10 Help Desk and User Liaison Services

5.2.2 Education.

• Bachelor’s Degree in an IT-related field with at least 5 concurrent years of relevant experience within the past 10-15 years (see Section 5.2.3); or

• Professional system administration certificate in a field relevant to EIMS with at least 10 concurrent years of relevant experience within the past 10-15 years

5.2.3 Qualifications.

https://cyber.mil/cwmp/dod-approved-8570-baseline-certifications/ https://cyber.mil/cwmp/dod-approved-8570-baseline-certifications/ https://cyber.mil/cwmp/steps-to-obtain-a-dod-8570-baseline-certification/ https://cyber.mil/cwmp/cwmp-faqs/#toggle-id-33 https://cyber.mil/cwmp/cwmp-faqs/#toggle-id-33 https://cyber.mil/cwmp/summary/

• Relevant Experience.

o Performed System Administration on DOD systems.

o Operated with latest version of VMWare Windows Server 2019 or later.

• CSWF Designation. IAT Level II. Same requirements as Section 5.1.3.

5.3 Cybersecurity/Information Assurance

5.3.1 Responsibilities.

• 4.6 Cybersecurity/Information Assurance Services

b. Assist with Section 4 Tasks/Requirements:

• 4.5 Systems Administration Services

• 4.8 Documentation Services

• 4.9 Training, Orientation, and Outreach Services

• 4.10 Help Desk and User Liaison Services

5.3.2 Education.

• Bachelor’s Degree in an IT-related field with at least 5 concurrent years of relevant experience within the past 10-15 years (see Section 5.3.3); or

• Professional cybersecurity certificate in a field relevant to EIMS with at least 10 concurrent years of relevant experience within the past 10-15 years

5.3.3 Qualifications.

• Relevant Experience.

o Performed System Administration and cybersecurity functions on DOD systems.

o Operated with latest version of VMWare and Windows Server 2016 or later.

• CSWF Designation. IAT Level II. Same requirements as Section 5.1.3.

5.4 GIS Analyst

5.4.1 Responsibilities.

• 4.7 Data Management Services

b. Assist with Section 4 Tasks/Requirements:

• 4.8 Documentation Services

• 4.9 Training, Orientation, and Outreach Services

• 4.10 Help Desk and User Liaison Services

5.4.2 Education.

• Associate’s Degree in Geography or related field with at least 5 concurrent years of relevant experience within the past 10-15 years (see Section 5.4.3); or

• Professional GIS certificate in a field relevant to EIMS with at least 10 concurrent years of relevant experience; or

• At least 15 concurrent years relevant experience within the past 15-20 years

5.4.3 Qualifications.

• SECRET Clearance. Not required.

• Relevant Experience.

o Created and managed geospatial data using the full suite of Esri products, including ArcGIS server and Arc Spatial Database Engine.

o Used other GIS applications such as global positioning systems, etc.

o Prepared geospatial products in accordance with data standards such as Spatial Data Standards for

Facilities Infrastructure and Environment.

5.5 Business Analyst/Training Specialist

5.5.1 Responsibilities.

• 4.8 Documentation Services

• 4.9 Training, Orientation, and Outreach Services

b. Assist with Section 4 Tasks/Requirements:

• 4.10 Help Desk and User Liaison Services

5.5.2 Education.

• Bachelor’s Degree in English, Business, or related field, with at least 5 concurrent years of relevant experience within the past 10-15 years (see Section 5.5.3);

5.5.3 Qualifications.

• Relevant Experience.

o Prepared and edited technical documents, diagrams, and drawings in prescribed formats, and maintaining a technical library; or o Prepared on-line training and orientation materials, including presenting orientation and training material face-to-face and via video teleconference.

5.6 Help Desk Administrator/Tester

5.6.1 Responsibilities.

• 4.10 Help Desk and User Liaison Services

b. Assist with Section 4 Tasks/Requirements:

• 4.8 Documentation Services

• 4.9 Training, Orientation, and Outreach Services

5.6.2 Education.

• High School Diploma with at least 10 concurrent years of relevant experience (see Section 5.5.3).

5.6.3 Qualifications.

• SECRET Clearance. Not required.

• Relevant Experience.

o Provided customer service via a Help Desk.

o Supported a technical team with routine testing, document preparation, etc.

5.7 Task Order Manager

5.7.1 Responsibilities. Implement Tasks/Requirements of Section 4.13 Program Management

Services.

5.7.2 Education.

• Bachelor’s Degree in Computer Science, Management, or related field, with at least 5 concurrent years of relevant experience (see Section 5.6.3); or

• Professional Certificate in managing IT systems or similar with 10 concurrent years of relevant experience;

or

• At least 15 concurrent years of relevant experience.

5.7.3 Qualifications.

• SECRET Clearance. Not required.

• Relevant Experience.

o Served as corporate program/project manager of an IT network or information management system that provides multiple integrated tools, capabilities, and data.

o Managed a diverse technical workforce of IT professionals.

6. PLACE OF PERFORMANCE: Since the environments are not geographically co-located, team personnel may perform their tasks via remote access as applicable. Note that not all tasks can be done via remote access.

7. PERIOD OF PERFORMANCE: The resulting award to include a transition period in the event that the awardee is not the same as the incumbent contractor, an 11-month base period, four 12-month option periods and include

FAR clause 52.217-8 Option to extend services for an additional 6-months.

PERIOD DATE

Transition Period 12 April 2025 - 11 May 2026

Base Period 12 May 2025 - 11 April 2026

Option I 12 April 2026 - 11 April 2027

Option II 12 April 2027 - 11 April 2028

Option III 12 April 2028 - 11 April 2029

Option IV 12 April 2029 - 11 April 2030

52.217-8 12 April 2030 - 11 October 2030

8. OTHER PERFORMANCE REQUIREMENTS

8.1 Contractor Personnel Qualifications.

a. Background Checks. All team members require access to the Non-classified Internet Protocol Router

Network at this task orders commencement to perform required work. Therefore, all Contractor personnel

(including administrative and subcontractor personnel) shall be eligible for SECRET security clearances in accordance with the DON Personnel Security Program (reference j). Each shall have at a minimum favorable National Agency Check with Local Agency Check and Credit Check (NACLC) Trustworthiness

Determination and FBI fingerprint checks.

b. SECRET Clearances. All Software Application Developers, System Administrator(s) and Cybersecurity personnel on the Contractor team require SECRET clearances to access the SIPRNET to perform assigned tasks per Section 3. c. Contractor shall have procured their SECRET clearances prior to starting work on this task order.

c. CSWF Designations. All Software Application Developers and System Administrator(s) on the Contractor team will require privileged access to the Production and Continuity of Operations environments to perform assigned tasks. They shall qualify for and maintain Information Assurance Technical (IAT) Level

II designations in accordance with Cyberspace Workforce Management (reference h) and Information

Assurance Workforce Improvement Program (reference i).

8.2 Phased Transition Plan (PTP). EIMS and associated applications require uninterrupted support during the transitions between contracts. If the Awardee of this solicitation is not the Incumbent Contractor, they shall work together to turnover contract responsibilities during a 30-calendar day overlap period between the beginning of this contract and expiration of the Incumbent task order.

a. Phase-In Period. Develop and implement the PTP in coordination with the Incumbent Contractor within the following framework:

• During the first week of the new contract, Awardee project leads (at a minimum, the Task Order

Manager, Project Technical Lead, and senior developer) shall participate in an initial face-to-face transition coordination meeting at the Incumbent Contractor facility. Address issues such as pairing up personnel and determining ground rules for transition coordination and turnover of specific tasks, procedures for requesting access to key facilities and websites, turning over passwords, introductions to third parties, mitigation of potential impacts to other Navy programs, etc.

• Submit PTP within five days of concluding this initial transition meeting for Government review and comment.

• All Awardee team members shall engage their Incumbent counterparts remotely beginning second week of new contract for system familiarization, review of relevant technical and process documents, best practices, etc.

• All Awardee team members and their Incumbent counterparts shall marry up during the last business week of the outgoing contract for a face-to-face on-the-job experience, turnover of responsibilities and Government-furnished Property (GFP), primarily individual workstations, etc.

NOTE: A PTP is not required if the Incumbent is Awardee for this solicitation.

b. Phase-Out Period. If the Awardee of this solicitation is not the awardee of the follow-on EIMS Technical

Support Services solicitation, the Awardee of this solicitation shall coordinate with the follow-on Awardee who will need to prepare its own PTP.

8.3 Security Requirements.

8.3.1 Protection of Government Information. The contractor must comply with applicable security classification guidance contained in the National Industrial Security Program Operating Manual (DOD 5220.22-M), DOD

Information Security Program: Protection of classified information (DODM 5200.01 V1-V4), DON Information

Security Program (SECNAV M-5510.36), COMUSFLTFORCOMSTAFFINST 5531.1 Series and local USFF security policies. The contractor shall not release any Government information e.g. classified, controlled unclassified information without the express permission of the Government representative or COR.

8.3.2 Operational Security (OPSEC). In accordance with DODM 5205.02M, contractor shall protect information listed in the Critical Information List (CIL) and any other sensitive, but unclassified information that may be useful to our adversaries. Contractor shall abide by OPSEC policies and procedures, as detailed in DODM 5205.02M, COMUSFLTFORCOMINST 3432.1A, and/or as directed by the OPSEC Manager/Officer or an OPSEC

Coordinator. Contractor shall accomplish USFF initial OPSEC training within 90 days of in-processing and complete refresher OPSEC training annually. Contractor shall notify their OPSEC Coordinator or the OPSEC

Manager/Officer of recommendations for the OPSEC program or potential OPSEC concerns. POC: USFF OPSEC

Program Manager, phone 757-836-4462.

8.4 Substitution. The contractor must promptly notify the COR and contracting officer immediately when substitution of personnel is anticipated. The contractor must follow-up the notification, in writing, to the COR and contracting officer providing the reasons for the substitution and proposed qualified replacement. The Government shall notify the contractor within ten days of receipt of the request for substitution if such substitution is acceptable.

8.5 ADP Environment. All reports, technical documentation, etc. must comply with standard Navy Marine Corps

Intranet desktop, portable Microsoft windows operating based systems, data and quality control standards unless otherwise specified.

8.6 Contractor Identification.

Personnel shall clearly identify themselves as contractor personnel as follows:

1. Meetings: Contractor personnel shall identify themselves as and/or be introduced as “contractor personnel” and display distinguishing badges or other visible identification for meetings with government personnel.

2. Written Correspondence: Contractor personnel shall identify themselves as contractor personnel in all formal and informal written correspondence with government personnel.

3. Telephone Correspondence: Contractor personnel shall identify themselves as contractors during the initial greeting when participating (initiating or receiving) in telephone conversations with government personnel.

8.7 Mandatory Contractor Training: The Contractor is responsible for its employees (and subcontractors) supporting this contract completing and staying up to date on all training required by USFF and supported activities for individuals working on Government installations. Some examples of required training and their requisite course numbers/references are listed below. The required training is subject to change throughout the life of this contract;

however, the Contractor should assume at least a total of eight hours for all required training courses annually per

Contractor/Subcontract employee. The Contractor shall provide documentation (copies of training certificates) to the

COR confirming that Contractor employees have completed the required training within five days of the specific training due date.

Program Course Reference

Cyber Awareness DOD-IAA-V18.0 SECNAVINST 5239.3 Series

Privacy Act &PII DOD-PRIV-2.0 SECNAVINST 5211.5 Series

Antiterrorism Awareness Level I CENSECFOR-AT-010-2.0 DODI 2000.16

OPSEC NOST-USOPSEC-3.0

OPNAVINST 3432.1 Series and

COMUSFLTFORCOMINST 3432.1 Series

Suicide Prevention CPPD-GMT-SAP-1.0 OPNAVINST 1720.4 Series

Records Management DOR-ROM-010-1.2 OPNAVINST 5210.20

Counterintelligence Awareness NCIS Face-to-Face SECNAVINST 5210.30 Series

Security Awareness Local Brief/Seminar SECNAVINST 5510.30

Active Shooter TWMS-567015 USFF Commander directed.

Derivative Classification TWMS-576351

Controlled Unclassified

Information

TWMS-686564

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

Technology (IT) Systems or Protected Health Information

Executive Order 13467, Reforming Processes Related to Suitability for Government Employee, Fitness for

Contractor Employees and Eligibility for Access to Classified National Security Information, Homeland Security

Presidential Directive (HSPD)-12, requires government agencies to develop and implement Federal security standards for Federal employees and contractors. The 5 CFR 32 Part 157 in concert with DOD Manual 1000.13, Vol

1, implements the Federal Standards.

APPLICABILITY

This text applies to all DOD sponsored individuals who require CAC eligibility (or login and P/W if acceptable per contract) for: Physical access to DOD facilities or non-DOD facilities on behalf of DOD; Logical access to information systems (whether on site or remotely); or remote access to DOD networks that use only the CAC logon for user authentication, or access to sensitive and protected information. This applies to the Office of the Secretary of Defense (OSD), the Military Departments, the Office of the Chairman of the Joint Chiefs of Staff and the Joint

Staff, the Combatant Commands, the Office of the Inspector General of the DOD, the Defense Agencies, the DOD

Field Activities and all other organizational entities within the DOD (hereinafter referred to collectively as the

"DOD Components").