Att_C_Performance_Work_Statement.docx
DOCX document 59 KB Posted
- Solicitation number
- N6230619R0012
About this file
Att C Performance Work Statement
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Att_D_Questions_Request_Form_1.docx | DOCX document | |
| Att_D_Questions_Request_Form_2.docx | DOCX document | |
| Att_E_DD254_CEIPB.pdf | ||
| Att_A_Terms_and_Conditions.pdf | ||
| Combined_Synopsis_Solicitation_-_Collector-EIPB.pdf | ||
| Att_D_Questions_Request_Form.docx | DOCX document | |
| Att_B_Evaluation_Price_Schedule.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
PERFORMANCE WORK STATEMENT
COLLECTOR-ENVIRONMENTAL INTELLIGENCE
PREPARATION OF THE BATTLESPACE (C- EIPB)
25 March 2019
| 1. | BACKGROUND: |
| 1.1 | COLLECTOR - Environmental Intelligence Preparation of the Battlespace, (C-EIPB) is a Geographical Information System (GIS) used for the storage, retrieval, mapping and analysis of geographic data for command and control systems within the Navy, converting data into actionable information for the warfighter. C-EIPB contains highly-specialized extensions, applications, and data layers supporting various critical mission requirements of NAVOCEANO and Navy commands. Individual extensions within C-EIPB are distinct but share core functionality and data requiring seamless cross tool functionality. C-EIPB and its geospatial data must be continually maintained and updated in order to continue supporting Navy missions. |
| 2. | SCOPE: |
| 2.1 | The contractor shall maintain an up-to-date and efficient C–EIPB application and shall enhance the C-EIPB application to meet operational requirements of NAVOCEANO and other Navy commands. |
2.2 All tasks outlined in below sections shall be completed per month with a possibility of multiple customers, simultaneously.
| 3. | BASIC C-EIPB SUPPORT |
| 3.1 | BASIC C-EIPB SUPPORT is general support for C-EIPB. |
| 3.2 | The contractor shall: |
| 3.2.1 | Use Microsoft Windows software such that the C-EIPB application will function on the latest Windows operating system (currently Windows10 64-bit) |
| 3.2.2 | Provide support for C-EIPB installation and usage on standalone workstations, networked workstations, servers, and virtual machines. |
| 3.2.3 | Provide maintenance and updates to the C-EIPB and its extensions and tools, including transitioning to newer software versions to preserve C-EIPB functionality. |
| 3.2.4 | Provide maintenance, updates, and enhancements to C-EIPB and its extensions and tools, including fixing bugs, improving performance, and incorporating additional functionality. |
| 3.2.5 | Maintain and update C-EIPB documentation, including metadata, on-line help, user guides, training materials, and software description documents. |
| 3.2.6 | Maintain and update C-EIPB geodatabases, databases, and data to meet changing standards and/or requirements, improve data retrieval and display functionality for faster access and display, and incorporate new data and databases as required. |
| 3.2.7 | Provide error trapping and identification interfaces within all C-EIPB software functionality that interactively corrects data fields to the maximum extent possible. |
| 3.2.8 | Maintain and update C-EIPB import/export capabilities, including standard messages, images, data, and databases. |
| 3.2.9 | Integrate a multi-user services environment connecting to various types/kinds of external Commercial Off the Shelf (COTS) databases (e.g. Oracle data bases, Microsoft Office Access data bases, My Structured Query Language (MySQL) data bases, etc.). |
| 3.2.10 | Maintain and update C-EIPB installation package to allow for installation and certification on enterprise IT. |
| 3.2.11 | Maintain and update STIG status of the C-EIPB code set for Information Assurance and accreditation requirements. |
| 3.2.12 | Shall enter all source code deliveries into the source code control system(s). All documentation and support files to create executables from source code must be included. Software code should be packaged and delivered to COR/ACOR. |
| 3.2.13 | Test and then prepare, host security review, and package C-EIPB for delivery to COR and/or ACOR. Up to two (2) versions upgrades expected each year, each upgrade preceded by one or more beta versions. |
| 3.2.14 | Provide briefs, demonstrations, and customer support, including installation support, technical support, technical training, and troubleshooting. Customer support includes answering emails and telephone inquiries. Travel may be required. |
| 4. | C-EIPB LINUX |
| 4.1 | C-EIPB LINUX provides support to sponsors and customers requiring LINUX version of C-EIPB |
| 4.2 | The contractor shall: |
| 4.2.1 | Use LINUX software such that the C-EIPB application will function on the latest Linux operating systems (currently Red Hat 7 64 bit). |
| 4.2.2 | Provide support for C-EIPB installation and usage on standalone workstations, networked workstations, servers, and virtual machines. |
| 4.2.3 | Provide maintenance, updates, and enhancements to C-EIPB, its extensions and tools, and data, including transitioning to newer software versions to preserve C-EIPB functionality. |
| 4.2.4 | Provide maintenance, updates, and enhancements to C-EIPB, its extensions and tools, and data, including fixing bugs, improving performance, and incorporating additional functionality. |
| 4.2.5 | Maintain and update C-EIPB documentation, including metadata, on-line help, user guides, training materials, and software description documents. |
| 4.2.6 | Maintain and update C-EIPB geodatabases, databases, and data to meet changing standards and/or requirements, improve data retrieval and display functionality for faster access and display, and incorporate new data and databases as required. |
| 4.2.7 | Provide error trapping and identification interfaces within all C-EIPB software functionality that interactively corrects data fields to the maximum extent possible. |
| 4.2.8 | Maintain and update C-EIPB import/export capabilities, including standard messages, images, data, and databases. |
| 4.2.9 | Integrate a multi-user services environment connecting to various types/kinds of external COTS databases. |
| 4.2.10 | Maintain and update C-EIPB installation package to allow for installation and certification on enterprise IT. |
| 4.2.11 | Maintain and update STIG status of the C-EIPB code set for Information Assurance and accreditation requirements. |
| 4.2.12 | Shall enter all source code deliveries into the source code control system(s). All documentation and support files to create executables from source code must be included. Software code should be packaged and delivered to COR/ACOR. |
| 4.2.14 | Test and then prepare, host security review, and package C-EIPB for delivery to COR and/or ACOR. Up to two (2) versions upgrades expected each year, each upgrade preceded by one or more beta versions. |
| 4.2.15 | Provide briefs, demonstrations, and customer support, including installation support, technical support, technical training, and troubleshooting. Customer support includes answering emails and telephone inquiries. Travel may be required. |
| 5. | TRACKING |
| 5.1 | TRACKING is used to import, database, quality control, query, display, playback, and analyze tracks for pre-deployment analysis, post-event reconstructions, and historical analyses. |
| 5.2 | The contractor shall: |
| 5.2.1 | Provide maintenance and updates to C-EIPB’s extensions and tools essential to Tracking, including transitioning to future software versions to preserve C-EIPB functionality. |
| 5.2.2 | Provide maintenance, updates, and enhancements to C-EIPB Tracking extension and its components. |
| 5.2.3 | Provide maintenance, updates, and enhancements to Tracking database, including sponsor-held master databases. |
| 5.2.4 | Provide maintenance, updates, and enhancements to Data Display extension and its components. Maintain and update sponsor-specific C-EIPB geodatabases, databases, and data to meet changing standards and/or requirements, improve data retrieval and display functionality for faster access and display, incorporate new data and databases as required. Synchronized the Data Display menus for new and additional datasets. |
| 5.2.5 | Provide and enhance import/ingest functionality that will allow user to import updated C-EIPB environmental data layer packages to include ESRI file geodatabase structure and standardized XML metadata and synchronize the Data Display extension listing/menu as part of the import process. |
| 5.2.6 | Provide maintenance, updates, and enhancements to 0TPL extension and its components. |
| 5.2.7 | Provide maintenance, updates, and enhancements to the DBDBV extension and its components. |
| 5.2.8 | Provide maintenance, updates, and enhancements to the Playback Manager and its components. |
| 5.2.9 | Provide maintenance, updates, and enhancements to the Corridor Tool and its components. |
| 5.2.10 | Maintain and update Tracking components of C-EIPB documentation, including metadata, on-line help, user guides, C-EIPB and sponsor-focused training materials, and software description documents. |
| 6. | MCAT |
| 6.1 | Multi-Criteria Analysis Toolkit (MCAT) computes and displays RP33 parameters, also referred to as Acoustic Parameters (APARMS), determines and displays Acoustic Path Availability (APA), generates and displays Acoustic Terrain Analysis (ATA), determines and displays Least Cost Paths (LCP), and displays selected sound speed profiles and their associated parameters with Sound Speed Plot Viewer. |
| 6.2 | The contractor shall: |
| 6.2.1 | Provide maintenance, updates, and enhancements to MCAT, including transitioning to newer software versions to preserve C-EIPB functionality. |
| 6.2.2 | Provide maintenance, updates, and enhancements to MCAT, including addressing bugs, deficiencies and improving new data and functionality. |
| 6.2.3 | Incorporate Naval Operational Maritime Acoustic Database (NOMAD) database application into C-EIPB, including functionality to open and display its data to the user. |
| 6.2.4 | Integrate new MCAT tools developed by NAVOCEANO into MCAT tool suite, including ensuring MCAT tool interoperability and adding software required for tool functionality with C-EIPB. |
| 6.2.5 | Maintain and update MCAT documentation, including metadata, on-line help, user guides, training materials, and software description documents. |
| 6.2.7 | Maintain and update MCAT geodatabases, databases, and data to meet changing standards and/or requirements, improve data retrieval and display functionality for faster access and display, and incorporate new data and databases as required. Includes different DBDB-V Levels. |
| 6.2.7 | Maintain and update C-EIPB import/export capabilities, including standard messages, images, data, and databases. |
| 6.2.8 | Maintain and update MCAT installation package to allow for installation and certification on enterprise IT. Includes different DBDB-V Levels, resulting in up to three (3) different C-EIPB packages per C-EIPB version. |
| 6.2.9 | Maintain and update STIG status of the MCAT code set for Information Assurance and accreditation requirements. |
| 6.2.10 | Shall enter all source code deliveries into the source code control system(s). All documentation and support files to create executables from source code must be included. Software code should be packaged and delivered to COR/ACOR. |
| 6.2.11 | Test and then prepare, host security review, and package C-EIPB for delivery to COR and/or ACOR. up to three (3) different C-EIPB packages required to handle the different DBDB-V Level. Up to two (2) versions upgrades expected each year, each upgrade preceded by one or more beta versions. |
| 7 | MISSION PLANNING TOOL (MPT) |
| 7.1 | The Mission Planning Tool (MPT) is used utilized forward to plan run geometries for the Submarine Mobile Acoustic Training Target (SUBMATT) vehicle. |
| 7.2 | The contractor shall: |
| 7.2.1 | Provide maintenance and updates to MPT, including transitioning to future software versions to preserve its functionality. |
| 7.2.2 | Maintain and update MPT documentation, including on-line help, user guides, and training materials. |
| 7.2.3 | Test and then prepare, host security review, and package MPT. |
| 7.2.4 | Participate in meetings and provide technical support for MPT. |
| 7.2.5 | Reformat environmental data for distribution with and use within MPT. |
| 8 | FOMMAP |
| 8.1 | Figure of Merit Map (FOMMAP) is used to compute and display acoustic performance variability based on variability in sonar equation parameters. |
| 8.2 | The contractor shall: |
| 8.2.1 | Provide maintenance and updates to FOM MAP, including transitioning to future software versions to preserve its functionality. |
| 8.2.2 | Provide maintenance, updates, and enhancements to FOM MAP and its components, including addressing reported bugs and deficiencies and incorporating new data and functionality. |
| 8.2.3 | Incorporate NOMAD database application into FOM MAP, including functionality to read and utilize its data for use within FOM MAP. |
| 8.2.4 | Restructure current implementation as FOM MAP standard option. Enhance GUIs and software to incorporate FOM MAP advanced option, including GUIs and software to exercise UBAND to compute transmission loss distribution, convolve transmission loss distribution with the ambient noise distribution for specified fixed depth/moving depth combinations. |
| 8.2.5 | Maintain and update FOM MAP documentation, including metadata, on-line help, user guides, training materials, and software description documents. |
| 9 | API |
| 9.1 | Acoustic Propagation Interface (API), encompasses environmental, sensor, and target databases, and acoustic models allowing its user to model, display, and analyze acoustic performance predictions. |
| 9.2 | The contractor shall: |
| 9.2.1 | Provide maintenance and updates to API, including transitioning to future software versions to preserve its functionality. |
| 9.2.2 | Provide maintenance, updates, and enhancements to API and its components, including addressing reported bugs and deficiencies and incorporating new data and functionality. |
| 9.2.3 | Maintain and update API documentation, including user guide, software description document, and changes document. |
| 10 | ACOUSTIC DATA ARCHIVE |
| 10.1 | The Acoustic Processing Division NP52 is responsible for archiving acoustic measurement data and making the data accessible for in-house use and extraction for customers. This requirement includes processing/reformatting data for ingest into databases such as the Data WareHouse (DHW), ingest and manipulation software for DHW, data analysis/viewer tools such as the Acoustic Station Inventory System Query Builder (ASIS-QB). |
| 10.2 | The contractor shall provide critical maintenance, essential updates, and required enhancements for the DHW, ASIS-QB, ingest, and production software: |
| 10.2.1 | Provide technical support for AN DataBase (ANDB), Low Frequency Bottom Loss (LFBL), High Frequency Bottom Loss (HFBL), Bottom Backscattering Strength (BBS), and Volume Scattering Strength (VSS) technical support for transfer of Acoustic Data from original tape, disc and paper archives to modern digital media. |
| 10.2.2 | Provide maintenance, updates, enhancements, and documentation for DWH load script tools for ambient noise and the propagation measurements. These data are loaded into the database and cataloged by data type, location, date-time-group and other metadata pertinent to each observation. |
| 10.2.3 | Provide maintenance, updates, and enhancements as required for ASIS-QB software and documentation, including data search, local archive inventory holdings, and DWH data quality control and viewing software functions. |
| 11 | AMBIENT NOISE |
| 11.1 | Ambient Noise requirements encompass digital signal processing software, geo-processing software, data analysis/viewer tools, databases, and other custom software tools utilized by the Acoustic Processing Division for the on-going maintenance, development, and utilization of ambient noise and shipping databases and associated measurement data. |
| 11.2 | The contractor shall provide critical maintenance, essential updates, and required enhancements for Ambient Noise (AN) production software and derived products: |
| 11.2.1 | A data processing software example would be to update and maintain the Environmental Acoustic Recording System (EARS) ambient noise processing software. |
| 11.2.2 | Provide maintenance, updates, and enhancements to Ambient Noise Map Generator (ANMG), software and documentation for ArcGIS AN map layer generation software. This includes ESRI format conversion software that converts ESRI format to the format of the Oceanographic and Atmospheric Master Library (OAML) ANDB Hierarchical Data Format (HDF). |
| 11.2.3 | The contractor shall provide maintenance, updates, and enhancements to Ambient Noise Data Viewer (ANDV), data, and documentation including data search, compilation, handling, analysis, reformatting, and visualization software. |
| 11.2.4 | The contractor shall provide maintenance, updates, and enhancements to AN models and example of which would be Dynamic Ambient Noise Model (DANM) software, data, and documentation. The contractor shall provide AN technical support for performing wide area and multi frequency batch runs using DANM. |
| 11.2.5 | OAML ANDB Upgrade (OANU), data analysis/viewer tools and documentation for all. Also includes, generation/build, and extraction software for ANDB and Wind and Residual Noise (WRN) databases. |
| 11.2.6 | OAML Shipping and Fishing Estimate (SAFE) build, ingest, extraction, and viewer tools and documentation for all. Also includes analysis software as needed for upgrades. |
| 11.2.7 | Update, maintain, and enhance to meet Fleet requirements for the Ambient Noise Toolkit (ANT) software, data, and documentation. Functions include parsing Naval messages to extract AN information gather by the Fleet aircraft squadrons; viewing/analysis comparison of measurements with climatology database ANDB; and AN forecasting. |
| 11.2.8 | The contractor shall provide maintenance, updates, and enhancements to Vertical Ambient Noise (VAN), data, and documentation to data search, compilation, handling, reformatting, editing, and visualization software. |
| 11.2.9 | The contractor shall provide maintenance and updates to all Ambient Noise software and its components, including transition to future software versions to preserve its functionality. |
| 12 | BOTTOM LOSS AND SCATTERING |
| 12.1 | Bottom Loss and Scattering includes programming support for Low Frequency Bottom Loss (LFBL), High Frequency Bottom Loss (HFBL), Bottom Backscattering Strength (BBS), and Volume Scattering Strength (VSS) databases. Programming support may expand to include the Consolidated Bottom-Loss Upgrade (CBLUG) Category Display Database. Support focuses on database generation software and database extraction software. |
| 12.2 | The contractor shall: |
| 12.2.1 | Provide maintenance and updates to bottom loss and scattering database software components, including transitioning to future software versions to preserve their functionality. |
| 12.2.2 | Provide maintenance, updates, and enhancements to bottom loss and scattering database software and their components, including addressing reported bugs and deficiencies and incorporating new data and functionality. |
| 12.2.3 | Provide maintenance, updates, and enhancements to CBLUG software, including software to compute CBLUG parameters from LFBL, generate database, and extract from database. |
| 12.2.4 | Provide maintenance, updates, and enhancements to survey data compilation and reformatting software, including updating its documentation. |
| 12.2.5 | Maintain and update bottom loss and scattering database software documentation. |
| 12.2.6 | Maintain and update STIG status of the bottom loss and scattering code set for Information Assurance and accreditation requirements. |
| 12.2.7 | Shall enter all source code deliveries into the source code control system(s). All documentation and support files to create executables from source code must be included. Software code should be packaged and delivered to COR/ACOR. |
| 12.2.8 | Test and then prepare, host security review, and package bottom loss and scattering database software for delivery to COR and/or ACOR. Typically, one version upgrade per database is expected each year, each upgrade preceded by one or more beta versions for testing purposes. |
| 13 | CUSTOM DISTRIBUTION | |
| 13.1 | Custom Distributions are a subset of C-EIPB, its extensions, tools, and data, prepared in accordance with requirements specified by the Foreign Disclosure Office and NAVOCEANO security. Each custom distribution is based on the most current version of C-EIPB. | |
| 13.2 | The contractor shall: | |
| 13.2.1 | Attend meetings with Foreign Disclosure Office and NAVOCEANO security to discuss which C-EIPB components can be included in custom distribution. | |
| 13.2.2 | Prepare custom distribution of C-EIPB in accordance with requirements specified by the Foreign Disclosure Office and NAVOCEANO security. Includes removing data identified as not releasable, subsetting data if required to isolate specific geographic region(s), adding custom/unique data, modifying C-EIPB software to accommodate customizations. | |
| 13.2.3 | Update documentation after the customization to reflect changes made during customization and release ability requirements. | |
| 13.2.4 | Test and then prepare, host security review, and package C-EIPB for delivery to COR and/or ACOR. |
| 14 | MISCELLANEOUS TOOLS |
| 14.1 | Miscellaneous Tools are a number of C-EIPB tools and capabilities that are utilized for specific purposes. |
| 14.2 | The contractor shall: |
| 14.2.1 | Provide maintenance, updates, and enhancements to Glider Tool and its documentation. Glider Tool is utilized by the NAVOCEANO’s Glider Operations Center (GOC) to archive, subset, and display data collected from gliders, unmanned surface vehicles (USVs), and autonomous underwater vehicles (AUVs). |
| 14.2.2 | Provide maintenance, updates, and enhancements to Ocean Profile Analysis (OPA) tool and its documentation. OPA imports bathythermograph (BT) profiles in JJVV format, computes sound speed using GDEM merge, and provides a profile viewer with RP33 parameters. |
| 14.2.3 | Provide maintenance, updates, and enhancements to Brief Builder tool. Brief Builder allows the user to design a brief template and then systemically incorporate EIPB data to generate the finished brief. |
| 14.2.4 | Provide updates and enhancements to C-EIPB import and export capabilities, including capabilities to import and export specific messages, images, data, and databases. |
| 15. | TRAVEL |
| 15.1 | The contractor(s) shall travel to provide C-EIPB technical training, perform software installations, troubleshoot reported problems, exchange technical and system interface information, interview participants for functional requirements, and provide software demonstrations. |
| 16. | PERIOD OF PERFORMANCE AND WORKING HOURS |
| 16.1 | The Period of Performance is a base plus four option years. |
| 16.2 | Specific period of performance will be provided at each Task Order. |
| 16.3 | NAVOCEANO core working hours are between 6:00 a.m. and 6:00 p.m. Monday – Friday. Contractor personnel are only allowed in workspaces when NAVOCEANO employees are present in designated workspaces. Designated workspaces will be closed on all Federal holidays. Federal holidays are available at the Federal Holiday OPM Site. |
| 17 | PLACE OF PERFORMANCE: |
| 17.1 | All work will be performed at the Naval Oceanographic Office (NAVOCEANO), located at Stennis Space Center, Mississippi. |
| 18. | PERSONNEL EDUCATION / EXPERIENCE REQUIREMENTS |
| 18.1 | Contractor personnel associated with this effort shall have the following level of education and experience: |
| 18.1.1 | All contractor personnel shall have, at minimum, the combination of education and experience required to qualify for the Office of Personnel Management (OPM) General Schedule Qualifications Standard, Computer Science Series, 1550, grades 5 - 12. |
| 18.1.2 | All contractor personnel shall have a working knowledge of the UNIX / LINUX and Windows operating systems, relational databases, scientific programming languages, and geospatial datasets. |
| 18.2.3 | All contractor personnel shall have a working knowledge of virtual machines and secure cloud environments. |
| 18.1.4 | Contractor personnel shall be proficient, in programming and utilizing Geographical Information System (GIS), specifically the Commercial Joint Mapping Toolkit (CJMTK), an ESRI ArcGIS suite of commercial software developer components and end user applications including ArcGIS Runtime; ArcGIS Engine; ArcGIS extensions including 3-D Analyst, Geostatistical Analyst, Network Analyst, Spatial Analyst, and Tracking Analyst; and ArcGIS Server. Its software components comprise a comprehensive package that provides visualization capabilities of charts/maps, geospatial information, analyst tools, and data storage. |
| 19. | PROGRAM MANAGEMENT |
| 19.1 | The contractor shall provide program and project management support as follows: |
| 19.1.1 | The contractor shall assign a Program Manager (PM) to act as the single primary interface with NAVOCEANO. The PM has the responsibility of interfacing with NAVOCEANO on all matters pertaining to this Performance Work Statement (PWS). The PM shall direct the contractor’s effort through the company’s internal management system. This management system shall provide project progress visibility to assure on-time completion of all requirements. |
| 19.1.2 | The contractor shall utilize standard processes based on industry best practices wherever applicable. |
| 19.1.3 | The contractor shall sponsor quarterly program management reviews to monitor contractor performance and discuss any issues that the contractor and/or NAVOCEANO are experiencing with the project. NAVOCEANO will schedule this review and submit a suggested agenda to the contractor. The contractor shall be responsible for all briefing slides and materials. |
| 20 | Software Revision Milestones: |
| 20.1 | The contractor shall brief or demo C-EIPB application, emphasizing completed tasks, within 60 days (2 months), 120 days (4 months), 180 days (6 months), and 270 days (9 months) after contract award date, or on schedule specified by COR based on tasks, operational requirements, and delivery dates. The purpose of the demonstration is for checking status of functionality and customer feedback on application. |
| 20.2 | The contractor shall demonstrate the C-EIPB application with all completed tasks at end of contract period. All modifications and revisions must be fully demonstrated and functional for system acceptance by NAVOCEANO. If the tasks are not completed, written justification is required. |
| 21. | DELIVERABLES: |
| 21.1 | Specific software, documentation, and data deliverables are required for each task area. |
| 21.1.1 | The contractor shall make intermediate (i.e. beta) deliverables to COR, ACOR, or designated NAVOCEANO subject matter expert for test and evaluation purposes. |
| 21.1.2 | The contractor shall make final deliveries to the Contracting Officer’s Representative (COR) or Alternate COR (ACOR) after NAVOCEANO security review and packaging prior to required delivery date or end of contract. All deliverables of C-EIPB applications shall be stored on shared network storage assessable by contractors, COR, and ACOR. COR and ACOR shall be notified by email when deliverable is posted. |
| 21.1.3 | Specific reports and/or status documentation are required for each task area. |
| 21.1.4 | The contractor shall provide status documentation in bi-weekly status meetings with COR/ ACOR and SMEs to include: |
· Status report summarizing accomplishments made during the previous two weeks.
· Problem report summarizing problems encountered during the previous two weeks, especially any problems that could potentially delay project completion.
21.1.5 The contractor shall provide monthly and quarterly reports for projects describing the following no later than the 10th of each month. Report shall include:
· Task list with percentage completed for each task
· Task accomplishments supporting percentage completed with sufficient detail to allow NAVOCEANO to determine and assess the contractor’s technical progress
· Problems or issues encountered
· Timeline changes and updates
· Intermediate and final deliveries
· Funding expended during period, including travel, total expended and remaining balance.
| 21.1.6 | The contractor shall provide a C-EIPB Software Design Document for all applications (written description of a software product, that a software designer writes in order to give a software development team overall guidance to the architecture of the software project- Source Code). |
| 21.1.7 | NAVOCEANO will accept or reject the deliverables in writing or via email. |
| 21.1.8 | NAVOCEANO will have thirty (30) business days to complete its review of the deliverables. If notification of acceptance is not provided to the contractor within thirty (30) business days, the deliverables will be deemed accepted. |
| 21.1.9 | In the event of the rejection of any deliverable, the contractor shall be notified in writing by NAVOCEANO, giving the specific reason(s) for rejection. The contractor will be allowed five (5) business days to correct the rejected deliverable and return it to the NAVOCEANO. |
| 22. | GOVERNMENT FURNISHED RESOURCES |
| 22.1 | NAVOCEANO shall provide working space, office equipment, hardware, and software necessary for the completion of the assigned tasks. All data and software provided to the contractor shall only be used under the terms of fulfilling their contractual obligations. All data and software shall be transitioned back to NAVOCEANO upon project completion or contract performance period. |
| 22.2 | All equipment and materials provided by the government shall remain in designated government spaces during project. All equipment and materials will be returned to NAVOCEANO upon completion of this project or as directed. |
| 22.3 | System access for scientific workstations will be provided by NAVOCEANO within 30 business days of the contractor completing all required security training, security application paperwork, and system access requests. Computer accounts for unclassified and classified systems, including NAVOCEANO's scientific and Navy Marine Corps Intranet (NMCI) systems, will be established for the contractor as needed for project completion. |
| 22.4 | Designated NAVOCEANO personnel will provide tasking familiarization and coordinate / facilitate project efforts. Familiarization for new contract employees shall consist of C-EIPB overview and software orientation. The duration of this familiarization shall be at the discretion of NAVOCEANO and shall not exceed five business days. |
| 23. | QUALITY CONTROL/ASSURANCE |
| 23.1 | The contractor shall perform inspections prior to requesting acceptance of the work by NAVOCEANO. Contractor-performed inspections are independent of those performed by the Government. |
| 23.2 | The PM shall attend meetings with the COR and other NAVOCEANO personnel to resolve quality considerations and problems that may arise in the course of the work. |
| 23.3 | The contractor shall submit a Final Quality Control Plan to the COR for approval within 30 days after contract award. The Quality Control Plan will outline the contractor’s inspection system and method(s) of documentation. |
| 24. | SECURITY REQUIREMENTS: | |
| 24.1 | A majority of the work performed under this SOW will be at the SECRET level, and a portion will be at the TOP-SECRET (TS) Sensitive Compartmented Information (SCI) (TS/SCI). SCI deliverables are required with this contract, but programming tasks are typically performed in GENSER SECRET spaces with simulated data sets prior to software transfer into SCI facilities (SCIFs). Contractor access in SCIFs are necessary to test and validate software, and generate deliverables. There are eight (8) allowable TS clearances based on a Single Scope Background Investigation (SSBI) with eligibility for SCI through the duration of this contract. Other contractor personnel shall maintain up to GENSER SECRET clearances. Facility Level Clearance shall be the same or above contract requirement. | |
| 24.2 | All contractor personnel planned to be assigned to this contract shall have appropriate security clearances at the time of contract award. | |
| 24.3 | All Contractors require IT Level II (sensitive information access) as defined in SECNAV M5510.30. | |
| 24.4 | The contractor shall ensure the required security training, security application paperwork, and system access requests for all new employees are submitted to NAVOCEANO in sufficient time such the required facility and system access credentials can be provided by NAVOCEANO prior to the contractor reporting to the facility. | |
| 24.5 | All contractor personnel shall in-process with the Navy Command’s Security Manager and Information Assurance Manager upon arrival to the Navy command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. | |
| 24.6 | All information, products delivered, or services performed may not be disclosed by any means without prior approval of the authorized COR. Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nationals or other person or entity; publication of technical or scientific papers; advertising and or other proposed public release. | |
| 24.7 | The potential consequence for failing to meet any of the requirements listed above includes a determination on untrustworthiness and denial of access for the proposed contractor employee. Failure to obtain a favorable trustworthiness determination in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees for working in non-sensitive positions, with sensitive information, and/or on Government IT systems. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have physical access to a federally controlled facility and/or access to a federally-controlled information system/network and/or access to Government information. |
24.8 “All information technology (IT) solutions will adhere to Department of Defense (DoD) and Navy cybersecurity requirements as defined in DOD Instruction 8500.01, OPNAV Instruction 5239.1D, and applicable Security Technical Implementation Guides (STIGs). In particular, all applications developed for use on Navy information systems must adhere to the latest active release of the Application Security and Development (ASD) STIG. All data transmitted to a Navy information system must be protected in accordance with transmission confidentiality controls defined in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53 and protection measures mandated by the Defense Information Systems Agency (DISA) Ports, Protocols, and Services Management (PPSM) Category Assurance List (CAL) and Vulnerability Assessments (VAs). No function of the aforementioned information systems may circumvent or weaken the cybersecurity mechanisms of existing Navy information systems. Security Technical Implementation Guide (STIG) V-32372 requires "IT position designations (which) are assigned to each civilian and military position or contractor employee duties contained in statements of work in which an employee has duties requiring access to a Government Information System. In most cases this will encompass 100% of all employees." IT levels are defined in SECNAV M5510.30.
Compliance strategy shall conform to the cybersecurity risk management best practices set forth in the NIST framework for improving critical infrastructure cybersecurity and DISA STIGs. These methods and processes shall be documented in the system security plan and updated as necessary to ensure continuing compliance throughout the period of performance.”
| 25. | TRAINING REQUIREMENTS: |
| 25.1 | Government contractors shall complete the training requirements as specified in the DON Mandatory Training List for Contractors. |
| 25.1.1 | Contractor performing on this contract are required to conduct required DoD and command training that is not uniquely specified at the time of contract award. |
| 25.1.2 | Contractor shall provide COR with copy of all training certificates as required. The COR shall provide the contractor training certificates to the NAVOCEANO training office. |
| 25.1.3 | Additional training requirements may be required by DON. |
| 26. | INFORMATION ASSURANCE CONTRACTOR TRAINING & CERTIFICATION: |
| 26.1 | The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program. The Contractor shall meet the applicable information assurance certification requirements, including: |
· The contractor shall follow current IA regulations and guidelines.
· DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; and
· Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M
| 26.2 | Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions. |
| 26.3 | Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions. |
| 26.4 | IA training identified above is not required for non-system administrators, which includes C-EIPB software developers. |
| 27. | IT SYSTEM ACCESS |
| 27.1 | When access to IT systems is required for performance of the contractor employee’s duties, such employees shall in-process with the Navy Command’s Security Manager and Information Assurance Manager upon arrival to the Navy command and shall out-process prior to their departure at the completion of the individual’s performance under the contract. Completion and approval of a System Authorization Access Request Navy (SAAR-N) form is required for all individuals accessing Navy Information Technology resources. |
| 27.2 | When required to maintain access to required IT systems or networks, the contractor shall ensure that all employees requiring access complete annual Information Assurance (IA) training, and maintain a current requisite background investigation. The Contractor’s Security Representative shall contact the Command Security Manager for guidance when reinvestigations are required. |
| 27.3 | The potential consequences of any requirements under this clause, including denial of access for a proposed contractor employee who fails to obtain a favorable trustworthiness determination, in no way relieves the contractor from the requirement to execute performance under the contract within the timeframes specified in the contract. Contractors shall plan ahead in processing their employees and subcontractor employees for working in non-sensitive positions, with sensitive information, and/or on Government IT systems. The contractor shall insert this clause in all subcontracts when the subcontractor is permitted to have physical access to a federally controlled facility and/or access to a federally-controlled information system/network and/or access to Government information. |
| 28. | DISTRIBUTION OF TECHNICAL INFORMATION |
| 28.1 | All Government Furnished Information (GFI), technical data, provided to the contractor by the government will be protected from public disclosure and disclosure to other government agencies in accordance with the markings contained thereon. All other information relating to the items to be delivered or services to be performed under this contract may not be disclosed by any means without prior approval of the authorized government representative. The contractor shall provide adequate physical protection to such information so as to preclude access by any person or entity not authorized such access by the government. Dissemination or public disclosure includes, but is not limited to, permitting access to such information by foreign nationals or other person or entity; publication of technical or scientific papers; advertising; or any other proposed public release. The contractor shall provide adequate physical protection to such information so as to preclude access by any person or entity not authorized such access by the government. At completion of the contract, all GFI will be returned to NAVOCEANO. |
| 29. | DATA RIGHTS |
| 29.1 | It is NAVOCEANO’s intent to retain unlimited rights to all software, documentation, and data produced in performance of this statement of work. |
| 30. | IDENTIFICATION REQUIREMENTS |
| 30.1 | All contractor personnel performing under this statement of work shall identify themselves as a contractor employee to avoid creating any impression that they are Government officials. Such identification shall be made in all meetings attended, when answering Government telephones, on all e-mails, and when working in other situations where their contractor status is not obvious to third parties. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. |
| 31. | CONTRACTOR MANPOWER REPORTING |
| 31.1 | The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Naval Oceanographic Office via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/. |
| 31.2 | Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2016. Contractors may direct questions to the help desk at help desk at: http://www.ecmra.mil/. |
UNCLASSIFIED
UNCLASSIFIED
| 32. | PERFORMANCE REQUIREMENTS SUMMARY |
| 32.1 | Performance Requirements Table. This PWS not only discusses work to be performed, but also contains performance standards and acceptable performance levels (APL). Performance standards are "tools" the government uses to measure level of performance. A standard is an optimum performance level against which actual performance can be measured or evaluated. For example, in the statement "complete a service call in 24 hours" the standard is 24 hours. The number of days actually taken to finish this task is the performance indicator, which determines if the work performed was below, met, or exceeded the standard. Developing accurate performance standards is crucial to ensuring that the actual performance received, regardless of the service provider, meets the requirements of the Statement of Work. This PWS includes performance standards for each of the Functional Areas of the PWS. The performance standards provided with this PWS seek to state the characteristics of properly completed outputs. Each performance standard contains standards for both quality and timeliness. |
| 32.2 | Quality Assurance. The COR will inspect for compliance with Contract terms throughout the Contract period. Evaluation will be based on the Contractor’s compliance with the requirements set forth in the Performance Requirements Summary (PRS). The Government will monitor the Contractor's performance under this Contract by performing surveillance using the PRS. The PRS is used primarily to determine if the Contractor is performing all required outputs. The PRS also indicates for contractors the importance of each required service. |
32.3 Incentive or Disincentive for meeting/not meeting the Required Service and Performance Standard/Measurement will result in the following:
32.3.1 Incentive: Satisfactory or above ratings on past performance.
32.3.2 Disincentive: Delivery of document not within the performance standard and guidance contained in the PWS or failure to meet agreed schedules for delivery; Negotiated consideration for deficiency or delay.
32.4 Performance Requirements Summary Table:
Desired Outcomes
PWS
Paragraph
| Required Service |
| Performance Standard/ |
Measurement Monitoring Method
Maintain and update current capability of C-EIPB Toolkit
PWS Sections 3&4
| Provide bug fixes, software enhancements, database improvements, and technical support as required by customer base (Specific bug fixes, enhancements, improvements, and technical support tasking will be determine at Kick off Meetings of Task Order award). |
| Briefs or demos of C-EIPB application, emphasizing completed tasks, within 60 days (2 months), 120 days (4 months), 180 days (6 months), and 270 days (9 months) after contract award date, or on schedule specified by COR based on tasks, operational requirements, and delivery dates. The purpose of the demonstration is for checking status of functionality and customer feedback on application. |
| 100% Inspection of status reports, demonstrations, briefs, and record of bug fixes. |
| Maintain and update current operability of C-EIPB Tools: Tracking, Mission Planning Tool (MPT), Multi-Criteria Analysis Toolkit (MCAT), Figure of Merit Map FOMMAP, Acoustic Propagation Interface (API), Ambient Noise, Acoustic Databases ANDV/ODNDV/ LFBL/HFBL/ VSS/BBS, and Miscellaneous Tools |
| PWS Section 5-15 |
| Provide bug fixes, software enhancements, database improvements, and technical support as required by customer base specific to C-EIPB Tools (Specific tasks determined at Kick off Meetings of Task Order award). |
| Briefs or demos of C-EIPB application, emphasizing completed tasks, within 60 days (2 months), 120 days (4 months), 180 days (6 months), and 270 days (9 months) after contract award date, or on schedule specified by COR based on tasks, operational requirements, and delivery dates. The purpose of the demonstration is for checking status of functionality and customer feedback on application. |
| 100% Inspection of status reports, demonstrations, briefs, and record of bug fixes. |
| Upgrade Supporting Databases |
| PWS Sections 10, 11 & 12 |
| Review and compile NAVO and outside data sources converting them into shapefile, geodatabase formats, and/or other formats as requested. |
| a) No more than one (1) unresolved data deficiency. |
(b) Any discrepancies in data must be corrected within 7 Days of SME review Random Sampling, Unscheduled Inspections, Customer Complaints
| Data Modeling and Data Dissemination |
| PWS Sections 10, 11 & 12 |
| Conform data layers to required data standards and make available as required to NAVO networks. |
| a) No more than one (1) unresolved data deficiency. |
(b) Any discrepancies in data must be corrected within 7 Days of SME review Random Sampling, Unscheduled Inspections, Customer Complaints
| Custom Distributions |
| PWS Section 13 |
| The contractor shall prepare limited distribution versions of C-EIPB in accordance with requirements specified by Foreign Disclosure Office and security. This includes setting data, removing data, software modifications, and documentation changes. |
| 100% review and approval through demonstration and documentation to the Foreign Disclosure Office (FDO) and security. |
| 100% Inspection of status reports, demonstrations, briefs, through-out task order prior to final delivery. |
| C-EIPB Deliverables |
| PWS Section 21 |
| Monthly and Quarterly reports for projects (specifics outlined in Paragraph 11) |
| Reports to be received No Later than the 10th of the Month via email. |
| 100% review and acceptance by Subject Mater Expert (SME) and COR/ACOR via email. |
| C-EIPB Deliverables |
| PWS Section 21 |
| C-EIPB Software Design Document for all applications (written description of a software product, that a software designer writes in order to give a software development team overall guidance to the architecture of the software project- Source Code). |
| NAVOCEANO will have thirty (30) business days to complete its review of the deliverables. If notification of acceptance is not provided to the contractor within thirty (30) business days, the deliverables will be deemed accepted. |
| 100% review and acceptance by Subject Mater Expert (SME) and COR/ACOR. |
| C-EIPB Deliverables |
| PWS Section 21 |
| DVD of C-EIPB Toolkit Application Delivery |
| NAVOCEANO will have thirty (30) business days to complete its review of the deliverables. If notification of acceptance is not provided to the contractor within thirty (30) business days, the deliverables will be deemed accepted. |
| Briefs or demos of C-EIPB application, emphasizing completed tasks, within 60 days (2 months), 120 days (4 months), 180 days (6 months), and 270 days (9 months) after contract award date, or on schedule specified by COR based on tasks, operational requirements, and delivery dates. The purpose of the demonstration is for checking status of functionality and customer feedback on application. |
33. THE FOLLOWING NAVSUP LOCAL TEXT IS HEREBY MADE PART OF THE STATEMENT OF WORK/PERFORMANCE WORK STATEMENT.
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, 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").
Each contractor employee providing services at a Navy Command under this contract is required to obtain a Department of Defense Common Access Card (DoD CAC). Additionally, depending on the level of computer/network access, the contract employee will require a successful investigation as detailed below.
ACCESS TO FEDERAL FACILITIES
Per HSPD-12 and implementing guidance, all contractor employees working at a federally controlled base, facility or activity under this clause will require a DoD CAC. When access to a base, facility or activity is required contractor employees shall in-process with the Command’s Security Manager upon arrival to the Command and shall out-process prior to their departure at the…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it.