A02.12 PWS NNOMPEAS.docx

Performance Work Statement (PWS) for Acquisition of Professional Services to Support Development of Enhancements to NNOMPEAS (National Navigation Operation & Management Performance Evaluation & Assessment System)

– System Modification to Support Enhancements for Upload, Processing, and Analysis of Foreign Trade & Domestic Waterborne Coastal Traffic Data from the Waterborne Commerce Statistical Center (WCSC), Ongoing or Periodic Update of Vessel Operating Costs, Update of Power & Emissions Models, Enhancements for Display and Download of Data, Support Requirements for Migration to a Cloud Environment & Measures for Second-Phase Development of Capabilities for Value-to-the-Nation Reporting.

Professional Services to Support Development of Computerized Methods & Procedures for NNOMPEAS System Operation

Performance Work Statement (PWS) for Professional Services

Contract Number: XXXXXX-XX-X-XXXX (To be Assigned)

August 2023

1. Introduction and Background

The Institute for Water Resources of the U.S. Army Corps of Engineers (USACE-IWR) has been tasked by the agency (USACE) to develop and maintain a centralized computer-based system to tabulate waterborne transportation cost structures for coastal deep-draft waterway system projects under Federal sponsorship and the jurisdiction of USACE. Waterborne transportation cost structures and the differentials therein as derived from or associated with waterway project or plan alternatives serve as the primary basis for estimation of economic benefit(s) of waterway improvement and maintenance projects. Under initial and subsequent efforts for development the emphasis of output for system development was (and continues to be) the estimation of waterborne transportation costs for deep-draft ocean-going and coastwise carriers conveying foreign (i.e., imports and exports) and domestic trade serving coastal deep-draft harbors of the United States. Notably, the array of harbors and waterway systems is limited to harbors and locations for which the Corp’s Waterborne Commerce Statistics Center (WCSC) compiles waterway movement or traffic data.

With the development of other separate database efforts within USACE the intent is to develop the capability to compile and tabulate waterway use combined with eventual compilation of operation & maintenance (O&M) data within the framework of requirements for life-cycle cost evaluation with comparability to general program management objectives of the Corps for measurement of applicable return on investment (ROI). In addition, while the emphasis of system development will be for eventual evaluation of operation and maintenance (O&M) of deep-draft waterways, the logic and procedures for life-cycle project economic benefit and cost evaluation(s) are to be comparable with established guidance and USACE analytical procedures applied for navigation project evaluations whether for planning or new work or evaluation of significant O&M efforts. Accordingly, system development will be consistent with logic, practices and methods applied to evaluation of both ongoing O&M as well as planning efforts for new work for proposed, pending or newly constructed general navigation features (GNFs) and marginal or incremental improvement measures to existing waterway system projects.

Comparison of the two realms of costs (project placement and subsequent O&M versus differentials in transportation costs) can provide for reasonable evaluation of return on investment (ROI) subject to requirements of comparability in price levels and basis or context of estimation relative to data compiled and applied for evaluations. Respective to the PWS herein, ongoing development of the transportation cost capabilities of the system constitute current requirements to be further addressed by the associated technical description of work.

For background and orientation, should it be required, a general description of first or baseline phase work and requirements is presented in the first and primary scope of work for initial development or creation of the system (reference contract number W912HQ-11-P-0170).

2. General Statement and Description Concerning Programming Environment (and Supporting Materials and Equipment)

Efficient developmental work by the contractor will require fully proficient or expert knowledge of applicable computer languages and applications best suited to manipulation and modeling of large discrete databases, notably within current technology standards for the Oracle database environment and applicable subcomponents or subsystems. The contractor should have experience in conducting audit or detailed review and verification processes on complex analytical numerical models or analytical systems and notably large or extensive databases. Work efforts by the contractor will require the contractor to access and work with detailed Waterborne Commerce Statistical Center (WCSC) traffic data information and other sensitive information or data including vessel costs and vessel load management practices. Working with this data will require agreements and adherence to terms for non-disclosure and non-alternative or derivative use of sensitive or proprietary information, data, analytical logic and numerical methods or algorithms.

The employed enterprise software standard for handling of waterborne commerce data compiled by the Army Corps of Engineers (USACE) is generally the ORACLE environment. Efficient work efforts will require demonstrated expertise in Oracle 19c through pending or potential upgrade(s) for Oracle 21.1 and possibly later (whichever is identified as most current and as supported within the standardized USACE environment with anticipation of migration or interim update beyond Oracle 19c possibly up through Oracle 21.1 with commensurate update(s) of APEX (version or release level 20x or later) in FY 2023 and FY 2024. It is anticipated that this environment will be the core system language or environment around which other languages or commercial software will need to be employed via translational or interface programming. Accordingly, for integration into the Corps Oracle environment, while applicable certifications are not an absolute requirement (though desired) the work requires a strong working knowledge of the employment or application of all hardware, software and services in the area of Oracle database configuration and design, for both Intranet/Internet transfer and handling of data, input, and screen interfaces for both data entry and reporting or display across the Corps of Engineers CEEIS backbone or applied distribution network presently supported by on-premise systems..

Required knowledge, skills, and abilities shall also include application development using Oracle Application Servers; SQL, Analytical SQL, PL/SQL, SQL Developer and SQL Developer Modeler, Oracle Spatial; Oracle Web Application Development tools including the MOD PLSQL Toolkit, Application Express (APEX), HTML5, JavaScript, XML, KML, Microsoft Excel, Microsoft Access and NMEA message formats. Due to design linkages to GIS information environments, proficiency in use and development of applications for Google/Earth including the decoding, storage, and retrieval of waterborne vessel AIS movement data in the Oracle environment stated above will be required.

All triggers, interface procedures and packages developed for working with and handling data or databases within the environment as described and required by\for USACE shall be fully verified as to functionality and documented for purposes of efficient follow-on maintenance or upgrade by technical programmers and systems administrators. It should be understood that the latter requirement may entail more or supplemental documentation than would accompany the primary documentation of the contractor’s core developmental efforts for the required system. All models or application products including (but not necessarily limited to) numerical methods, logic, numerical relationships, analytical procedures, algorithms for data handling or manipulation and analysis formulated or developed specifically in support of the work efforts required herein shall become the property of the Institute for Water Resources (USACE-IWR) of the U.S. Army Corps of Engineers (USACE) and may not be copyrighted, patented, otherwise lawfully assigned or used for any other associated or derivative purpose without explicit written permission from appropriate authority of USACE-IWR. An example of potential exceptions to this include vendor-owned proprietary or lawfully controlled property or products such as specialized software, equipment or materials already inexistence that may be used in the process of or in support of work described herein, has not been compensated for, and which has been identified or substantiated as such upon initial assignment or outset of contract award. Governance of property disposition as described shall also extend to any prior work or work products prepared by the contractor under prior or present contract(s) in support of the work described herein for continued and ongoing development of associated analytical products.

Wherever computerized systems or applications are developed in support of or as a specified requirement of the PWS as set forth herein, the contractor will comply (to the extent applicable) with DoDI 8500.01 (2014) section 3.c.2, DoDI 8510.01 (2016) section 3.d, and USACE ER 25-1-112 (2014) section 7.1.3. Additionally, all information systems (IS) and platform information technology (PIT) systems developed and/or supported under this contract shall comply with all Department of Defense (DoD), Defense Information Systems Agency (DISA), Department of the Army (DOA), and USACE cybersecurity and architectural requirements in force at the time of contract award unless or where otherwise negotiated. This includes IS/PIT compliance with DISA Security Technical Implementation Guides (STIG) and being categorized IAW CNSSI 1253 using security controls developed IAW the risk management framework (NIST SP 800-53). STIG compliance includes but is not limited to the most current version of the DISA published Application Security and Development STIG and the internet access point (IAP) demilitarized zone (DMZ) STIG.

3. General Introductory Description of Technical Work and Requirements Under this Performance Work Statement (PWS) for Modification and Update to the Existing NNOMPEAS System

NNOMPEAS is being increasingly used as an access or portal for downloading and organizing waterborne commerce statistical data and associated computational relationships related to vessel operations currently handled by the system as it has been developed to-date. The description of required work herein is for annual update of data and continued development or modification of the current NNOMPEAS system to maintain existing technical functionality and development of enhancements to provide for enhanced functionality respective to data viewing, extraction and download capabilities, and data analysis as appropriate and resources allow. These capabilities are for support of project evaluation and analysis for both planners and operations and maintenance or management (O&M) personnel of USACE. The former group of users are largely accommodated within the existing system, but proposed enhancements will make available greater detail for review regarding needs or justification or value of channel systems for potential channel system evaluation and maintenance. In addition to ongoing efforts to improve viewing, query and data extraction functionality, requirements have evolved for many USACE-IWR programs or applications to migrate to a cloud or hybrid cloud environment with accommodation for both application development and operational environments. A significant part of these efforts includes architecture assessment and source code conformance to appropriate impact level (IL) environment and testing for compliance to maintain an authorization for continued operation (ATO; or “authorization to operate”). Correspondingly, such requirements entail ongoing annual review and associated documentation for risk management framework (RMF) procedures for periodic in-process audit or security measures. These measures are applicable to maintaining secure access to varying levels of detail for data depending on whether for needs regarding system application internal to USACE or for allowances needed for a system that would allow some level of defined capabilities for public access or higher levels of data aggregation at a later time. Tentatively, for internal usage, NNOMPEAS has been definitively assessed as requiring an IL4 level environment subject to containment and protections for data and information that falls under classification as CUI (controlled unclassified information). Currently the system is not assessed, presently or foreseeably, as requiring support for a higher IL rating.

General Statement Regarding Contractor Skills and Knowledge for Technical and Analytical Capabilities Associated With Work for Update of Data, Enhancement, and Upgrade of the NNOMPEAS System - In regard to the technical nature of work as set forth in items or deliverables as described in Section 3 herein, the contractor must have and demonstrate in any respective proposal strong working knowledge and skills in the analytical areas of deep-draft waterborne transportation economics (both as applied in the private sector and by the U.S. Army Corps of Engineers [USACE]), naval architecture, and vessel management or evaluation of related management practices to acceptably or more fully understand potential applications of the system and critical needs for system development and modification or improvement. Such experience and knowledge are critical to understanding how enhancements to the system are to be best undertaken and developed incorporating foresight for efficient and practical development and use which in turn will enable an acceptably efficient work\product execution and delivery processes or work efforts.

General areas of relevant knowledge include application of vessel operating costs to respective to Corps civil works project analysis, compilation of ocean-going voyage cost tabulations, and ability to perform or undertake detailed evaluation of load and stowage factor analysis specific to vessel type, vessel capacity class and nature of varying cargo flows and cargo types. With more specific reference to load and stowage factor evaluation, skills or knowledge should include evaluation of vessel displacement and deadweight tonnage (DWT) utilization and stowage operations within the level of detail and context ideally applied for economic evaluations consistent with National Economic Development (NED) analytical criteria for waterborne navigation typically applied by USACE. Additional requisite knowledge should include an understanding of domestic and international cargo flows; awareness and applicable working knowledge of general parameters for stowage factors by cargo commodity type or nature, mode of packing and shipment, and knowledge of related applicability of vessel operating costs and evaluation or estimation of cargo unit costs subject to accounting for load factor evaluations for cargo and non-cargo constituents and associated interrelationships. Applicable skills include identifying critical load factor inputs or variables, experience in applying load factor inputs for synthesized derivation and evaluation of vessel transit draft (and potential changes or variability therein) and evaluation of associated unit costs relative to associated deadweight utilization as can be assessed from limited vessel traffic or movement data. Also of notable value for consideration would be knowledge and familiarity with databases and database structures of USACE’s Waterborne Commerce Statistics Center (WCSC); commercially available maritime data sources, knowledge, and familiarity with publicly available AIS data, publicly available NOAA\NGA data, and maritime databases or data sources generally available in the public realm. Subject to practical application of such general knowledge and skills, modifications or enhancements needed under the performance work statement herein for the NNOMPEAS system are described as follows:

3-1 -- Migration to update(s) beyond the current version of Oracle (currently 19c base) and current or supporting versions of Oracle APEX -- As described above, the USACE Oracle platform is currently fully compatible to operation under Oracle version 19c. The contractor will need capacity to support fully functional migration of NNOMPEAS to the next update(s) of Oracle (potentially up to 21c) expected in FY 2024 with the supporting or succeeding version of Oracle Application Express (APEX; currently supported with 22.2.4), with requirements for full compatibility and functionality for operating environment as generally described under Section 2, preceding (including current version Linux OS and compatible Apache Tomcat application server(s)).

0. -- Update of NNOMPEAS Vessel Movement Database -- The NNOMPEAS vessel movement database is primarily based on the USACE Waterborne Commerce Statistical Center (WCSC) database for deep-draft vessel movements which is maintained and updated annually on a calendar year (CY) basis (and which typically has a one year to sixteen-month lag from occurrence of activity for statistics until acceptable quality-controlled compilation, review, and availability for system update). The current standing of the NNOMPEAS database is inclusive of data from calendar year (CY) 2004 up through CY 2021. Over the course of the contract duration related to technical requirements as described herein, the contractor will be required to perform an update of the NNOMPEAS database to include CY 2022 data when it becomes available (availability is anticipated for early March to late April 2024 or possibly before during late February). In addition, the contractor will be required to develop and\or maintain capability within the NNOMPEAS system to query, tabulate, and display all requisite data and updates of data and data-driven calculations or tabulations (including data extending back through 2004) on both a calendar year and Federal fiscal year (October 1 through September 30) basis with applied capability based on system user selection. The integration of the WCSC data update for CY 2022 will be fully compliant and functional with the NNOMPEAS database system (data query structure and routines) to include cross-reference compatibility and numerical reconciliation with established table view detail and related display formats. Data update will address both foreign and domestic deep-draft movements for coastal harbor or waterway system data as compiled by the WCSC. General capabilities for data compilation, data handling and display will be consistent with the existing structure, level of detail, coverage of ports and detail of vessel traffic as included in the existing database and database structure, and typical response time(s) for query processing execution and return (as a benchmark, generally less than 8 seconds actual processing time for a single port for one year of import and export data plus additional time for communication via data network forwarding or distribution to system user).

3-3 -- Update of Deep-Draft Vessel Operating Costs (DDVOCs) Database and Numerical Model Relationships -- Every one to two years, the self-propelled deep-draft vessel operating costs (DDVOCs) employed within NNOMPEAS are updated by type and size class of carrier for technological and structural changes in the world fleet in addition to price level adjustment for costs of construction, administration, ongoing operation and maintenance, bunkerage consumption and other relevant applicable or associated costs. The contractor will be required to integrate the next update for enhanced-format deep-draft VOCs via derivation and integration of multiple regression relationships for capital asset and operations costs (excluding range(s) of variability for bunkerage consumption) according to carrier type and size or capacity class (as measured appropriate to vessel type according to either deadweight or gross tonnage and volumetric capacity) and vessel registry. Additional specifications employed will include (but not necessarily be limited to) hull length (LOA and LBP), extreme hull breadth, maximum summer loadline draught and service speed rating. Costs for bunkerage consumption and fuel type shall be integrated via formulas or guidance for derivation of subject numerical relationships to be provided to the contractor (by the Government) as derived for bunkerage consumption relative to transit speed and immersed draft which are extractable from the vessel movements database integrated into NNOMPEAS. Vessel operating cost structures will be integrated into NNOMPEAS in a method consistent with application or adjustment of costs based on variability of powering corresponding to vessel type, size, and prime mover configuration as generally required and described for update of vessel powering and emissions model relationships. These relationships shall account for variability of operations applicable to in-port and at-sea operations and other defined modes of operation to also include in-port maneuvering. These efforts will require the contractor to develop a modified format for input, access, and computation of costs as the standard DDVOC model format allows for general but limited differentiation of at-sea and in-port costs with highly aggregated or generalized parameters for estimation of variability of conditions for speed and hull immersion (as it relates to hull configuration and associated hydraulic resistance, applied prime mover power, and associated bunkerage consumed). Such relationships shall extend to and include relationships for any applicable updates or improvements in emissions modeling completed and applicable during the period of performance (to be provided at least six weeks before the end of the period of performance as set forth herein).

Consequently, the contractor will be required to integrate update of the capability to viably apply enhanced numerical relationships of updated VOC modelling consistent with primary existing capabilities within NNOMPEAS. These capabilities will allow for more accurate derivation or estimation of costs based on immersed transit draft data uploaded from the WCSC and potential change in transit or immersed draft information imposed by changes in conditions for waterway depth or specifications for depth as otherwise imposed by the system user. Capabilities will also include accommodation of variability of speed across different data observations as extracted (to the extent available) from data from the WCSC, or as selected by the system user (with service speed or economic speed serving as the default in the absence of historical or indicated data or an estimate as provided by the user). In addition, additional improvements for estimated power consumption for within-port and shallow water areas will include refinement of adjustment(s) for confined water displacement and associated hydraulic resistance and the contractor will also be required to integrate these relationships into VOC cost estimations compiled by NNOMPEAS.

In addition to the update and inclusion of current vessel operating cost structures and numerical model relationships, the contractor will be required to structure NNOMPEAS to retain the current and pending editions of vessel operating cost models so that they can be readily applied or accessed by system users once integrated into the system. This capability is for support of comparative price-level analysis as it applies to NED (National Economic Development) evaluation and respective changes in deep-draft self-propelled vessel operating costs (self-propelled DDVOCs) over time. The anticipated availability of updated vessel operating costs is tentatively estimated as April to June of 2024.

3-4 -- Process Code Enhancement for System Performance (Optional Tasking) -- As the volume of data carried within NNOMPEAS generally increases with each passing calendar year, retrieval and query routines must be able to reference, sort, and discriminate across a larger database or data matrix structure. This tends to impose longer query or tabulation run or execution and response times. In relation to objectives for maximizing performance, the contractor will review the current state of the NNOMPEAS system and database respective to capabilities for operation. As part of annual updates each year, the contractor will maximize optimization of operations for the system and with consideration to foreseeable capabilities, size, structure and detail of query, conduct appropriate technical evaluations to develop data management routines with objectives for minimizing query execution and response times for technical users of the system. Part of this effort will include a basic assessment of applicable software upgrade(s) available during the performance period for the work requirements set forth herein. Currently, performance is relatively optimized but consideration of this work will also include migration of operations to a cloud environment as previously indicated which may require examination of existing data call and compilation routines for data transmission between user and the cloud access and operating environment.

With regard to generally defining parameters of relative volume and duration of time coverage of the database, NNOMPEAS currently contains eighteen (18) calendar years of data (i.e., calendar years 2004 through 2021). It is anticipated that ultimately the system would need to carry or support ready availability of up to the most recent twenty (20) years but perhaps as much as the most recent thirty (30) years of data before discreetly separable archiving or significantly compartmentalized processing is employed. In contexts of these requirements the contractor will review the methods and strategies for management of large databases (under Oracle 19c and potential capabilities as currently defined for 21c) including singularized comprehensive structures (generally the present form for NNOMPEAS) versus other techniques or regimes for management. These may include (but not necessarily be limited to) incremental or dynamic modular data structure push\pull\build routines and possibly precompiled table structures or formats for standardized views of particular routinely-used or accessed aggregations of data. Emphasis for evaluation of alternatives will be limited to present and foreseeably available features for the Oracle environment and APEX as available to USACE in an enterprise environment. Based on Oracle feature availability, the contractor will review the present system and formulate recommendations and supporting actions for present or pending development requirements versus interim and long-term requirements for NNOMPEAS with consideration to support of database and system management and maintenance combined with or balanced against efficient and practical system evolution, operation and usage.

3-5 -- Update and Enhancement of Statistical Views for Vessel Characteristics and Display Format(s) -- Evolving needs for use of NNOMPEAS indicates that with changing data (in terms of both the world fleet and associated traffic or throughput statistics) and requirements for use, views or displays need to be periodically or in an ongoing manner updated and additional views or displays would be of significant value to analysts working in USACE Districts. Correspondingly, the contractor will continue update of linkages for electronic visualizations or views\viewing as required for either update or development and inclusion of the following statistics, data, information, and characteristics of vessel fleet service regime:

· Update allowances for input of estimated underkeel clearance (by vessel type and size or draft class)

· Update allowances for input or disposition of estimated trim (by vessel type and size or draft class)

· Update view of Total Depth required for vessel movement (by vessel type and size or draft class)

· Update view of immersed\immersible margin light-loaded; weighted average by vessel type, draft class and grid cell grouping (with employment of weighted average measurement as appropriate)

· First-phase or initial development of refined estimation of cargo value (cargo value, similar to VOCs will be updated in a manner that allows retention of previous annualized aggregate price levels for comparative analysis).

· Update of view pages for the following physical parameters, with ability to sort discreetly on user selectable fields based on either maximum summer loadline draft (MXSLLD) class, deadweight tonnage class (for cargo carriers, with DWT stratification schema to be determined or provided by the Government technical representative), hull length (LOA and LBP), GRT (for passenger vessels), hull breadth, and moulded depth and volumetric capacities (grain and bale cubic as well as liquid cubic as applicable, with derivation of typical design weight per unit of volume).

· Explore feasibility (without incurrence of excessive response times) of being able to sort on additional characteristics such as height or air draft, with corresponding presentation and basic statistical analysis of:

Vessel Type (Bulk Carrier, Tanker, Fully Cellular Containerized Carrier, etc.)

Date of Build Displacement Light Displacement (estimation) Deadweight Tonnage (DWT; Metric) Net Registered Tonnage (NRT) and Gross Registered Tonnage (GRT) Containerized units (TEUs, FEUs, etc.; as applicable) Volumetric Capacity – Grain Cubic, Bale Cubic, Liquid & Gaseous (as applicable) Length Overall (LOA) and Length Between Perpendiculars (LBP) Extreme Breadth and Moulded Breadth Molded Depth Maximum Summer Loadline Draught (MXSLLD) Bunkerage Capacity and Bunkerage Consumption Bunkerage Type or Bunkerage Type Index Propulsion or Propulsion Type Index Horsepower (separably for Prime Mover and Auxiliaries) Service Speed (knots) Flag or Registry

· Statistical measures for variance or variability including (but not necessarily limited to) minimum, maximum, median, average, standard deviation (all on separate views or table demarcations (i.e., columns) within a view) with capacity for export of workbook function for all applicable statistical views.

Respective to the above specifications for statistics, the contractor will also be required to continue and update support capabilities to allow separable compilation of described statistics according to varying disposition of status as to whether hulls are in-class or in service, laid-up, broken, or otherwise permanently withdrawn from service as originally identified and intended by (hull) design subject to availability of respective data.

3-6 -- Risk Management Framework (RMF); Periodic Review and Compliance -- The present environment for computer network deployment, usage, and security requires ongoing monitoring, review and maintenance or revision to procedures to ensure an acceptable level of technical reliability, security from misuse, unauthorized access, and outside intrusion or breach by entities outside the realm of intended and authorized usership. As a consequence, within the present environment of security assessment under procedures and methodological approach identified as a Risk Management Framework (RMF), USACE must periodically support inquiry regarding structure and needs for computerized systems operation and security. Requirements include acceptable technical documentation for code and logic for application by information management (IM) personnel who support installation and operation of computerized systems employed by IWR and USACE. Under requirements for the PWS herein, should a RMF review be required the contractor will be responsible for answering associated technical inquiries and providing supporting documentation to the extent within purview and knowledge of the work efforts and products which are undertaken or assigned to the contractor. In addition, should source code scans be required, the contractor will also provide current or to-date source code files on request.

While an interim RMF reviews have been conducted during the last and preceding development cycles, it is anticipated that the contractor will be asked to detail any substantive changes to system structure or operation required as a result of fulfilling technical requirements outlined in the PWS herein. This may or could include comparative evaluation of requirements undertaken in FY2022 and FY 2023 (to the extent applicable) combined with any changes for work or development to be foreseeably undertaken in FY 2024. However, the requirement for additional RMF documentation under this PWS may prove not to be required. As RMF documentation is not certain or absolute it is requested that the contractor plan for resource(s) and technical time allowances to comply with potential requirements for one RMF documentation update and submittal over the course of the contract period as an option. To again clarify, this optional task or element will be estimated based on associated efforts to assess the existing structure of NNOMPEAS developed in prior years (2022-2023) with an emphasis on products and specifications set forth by the PWS herein for 2024 as an optional requirement.

In addition to (potential) requirements for compliance with the RMF for the existing or developing (pre-cloud) operating environment, the contractor will be required to prepare and support system development for initial migration to and comparably functional operation within a secure cloud environment expected to begin and be completed during FY 2024 and possibly extending into the beginning of FY 25. It is anticipated that this will require compatibility with Oracle 21c in addition to supporting version(s) of APEX and will require undertaking a RMF assessment particular to needs and specifications for this endeavor. The contractor will be required to prepare an estimate of time and costs based on applicable experience and available technical information as can be reasonably assembled for such efforts.

3-7 -- Development \ Enhancements for Value-to-the-Nation Reporting -- General Introduction - HQUSACE has provided funding to allow for more expedient processing and tabulation of estimates for economic benefits associated with Value-to-the-Nation (VTN) reporting. NNOMPEAS was originally developed for analysis of marginal depths or changes therein associated with potential reductions or variability in waterway system maintenance as well as serving as a data and analysis portal for waterway improvement evaluations. As such it is not ideally suited to expedient processing for Value-to-the-Nation tabulations and reporting given the differences between its original purpose and requirements for VTN tabulations. Requirements for VTN tabulations differ in that they require the estimation of economic cost efficiencies based not a marginal reduction in depth(s) but on estimation of controlling depth based on pre-project conditions. Alternatively stated, this involves evaluation before USACE invoked an active Federally-sponsored dredging program for a given locale and requires research and evaluation of the history for naturally prevailing depths often extending back for extended periods of time, which in many cases, approaches or exceeds 75 to nearly 100 years or more. Employing pre-project or naturally prevailing depths as an initial limitation on waterborne navigation, unit costs for increased depths can be acceptably estimated based on logic of hindcast-like extrapolation from cost structures for waterway systems as they currently operate or are employed for waterborne transport.

In addition to the evaluation of pre-project criteria, VTN reporting requires the ability to expediently tabulate unit cost estimates for projects and harbors across an entire region of the country and in turn the entire nation at a given time so that estimates can be collectively added (or “rolled up”) together for estimation of associated benefits relative to project conditions for the nation as a whole. Currently the process of VTN tabulations for a given year can require a period of approximately three to four man-weeks, sometimes more with some processing efforts performed outside the system. With efforts for increased automation of the task and batch processing, it is the primary objective that it will be accomplished within about four to five man-days of technical labor time allocated across approximately 8 to 12 calendar days.

The development of more automated processing for VTN will be undertaken in phases, the first of which is the framework scoping for automation and batch processing and preliminary verification of regional tallying of statistics. Tasks will include initiation of efforts to develop the baseline data framework including specifications for pre-project conditions of relevant waterways (baseline data for pre-project waterway conditions for development of approach, scoping and creation of the baseline datafile will be provided to the contractor by the Government). The contractor will also initiate development of test application as model framework to develop the basis for batch system processing and nationwide tallying of statistics in combination with utilities or applications as needed for verification of statistics.

4. Travel & Other Reimbursable Expenses

4-1 -- Travel -- It is requested that the contractor formulate and include for proposal estimates for travel resources (time and costs) as deemed prudent or necessary to competently execute requirements, specifications, and needs for the PWS as set forth herein. The contractor will be granted allowances for reimbursement of reasonable technical labor and direct expenses to support travel to conduct in-person or on-site technical review meetings with technical staff of IWR and where necessary, staff of the Waterborne Commerce Statistics Center (WCSC). Travel reimbursement will be limited to or in accordance with allowances for the current or applicable Federal Joint Travel Regulation (JTR) and Office of Personnel Management (OPM) guidance for travel expenses addressing transportation and per diem for civilian service except where marginal or increased costs can be determined to be fair and reasonable given circumstance (i.e., such as ineligibility of contractor staff for Federal lodging rates, seasonal or other market issues impacting lodging rates or other related and justifiable travel costs, etc.). Under circumstances where travel cannot be conducted within standard or typical Federal travel allowances the contractor will be responsible for conducting travel where needed with efforts to prudently limit costs to what is considered fair and reasonable and not excessive given circumstance in an effort to fairly minimize financial costs to the Government.

4-2 -- Should the contractor determine there will exist valid need for other marginal reimbursable expenses such as the acquisition of data in the absence of provision of such data by the Government (such as the alternatives described for optional items where or if applicable), the contractor will formulate a fair and reasonable estimate for inclusion in the overall proposal as a separable direct expense where applicable. In addition, the contractor will document justification based on direct technical needs and other benefit such as cost (and time) efficiencies for accomplishment of required work.

5. Summary of Deliverables & Associated Schedules

5-1 -- Tracking of status of work and products shall be by monthly teleconference or by monthly email submission, the choice of which is up to the discretion of the contractor unless significant technical issues arise where under such circumstance communication shall be by both written and electronic means in the interest of documenting and expeditiously resolving issues wherever possible. In reference to time frames, the notice to proceed (NTP) is based on a projected date coincident with contract award expected no later than 29 September 2023 with any actual timeframes as applied for contract requirements adjusted in reference to this date or any described calendar dates anticipated for data or material availability as appropriate. Based on current availability of information concerning data or products, it is anticipated that total time for completion of all tasks should not require more than 380 calendar days from the initial or contract general Notice to Proceed (NTP) Corresponding to description of the technical requirements as described, the following deliverables have been identified:

Initial Meeting - An initial meeting is to be held via teleconference with the contractor within fifteen days of contract award and prior to or by 29 September 2023. The purpose of this meeting will be for the Government technical representative to confirm directives for work efforts (i.e., such as the resolution of DWT and other hull parameters for sort routines or capabilities) and answer any post-award questions the contractor may have before proceeding with work.

Task 3-1 -- (Required Tasking) -- Migration to Current\Upcoming Oracle Version (beyond or supplemental to 19c) and Current Version of Oracle \ APEX

Time allowance(s): Based on finalized deployment of Oracle 19c and the updated version of Oracle Express within USACE (projected by the fourth quarter of FY 2024); accordingly, this tasking is to be completed within the three-hundred sixty (360) calendar days from the contract general notice to proceed (NTP) for the associated work requirement(s) therein.

Task 3-2 -- (Required Tasking) -- Update of NNOMPEAS Vessel Movement Database

Time allowance(s): Based on allowances for access or provision of the 2022 calendar year WCSC dataset within two-hundred and fifty (250) calendar days or less from the general notice to proceed (NTP) this task will be completed by the contractor within forty-five (45) calendar days after access to associated data or the date of projected availability of associated data (whichever is appropriate) with availability for access projected no later than 15 April 2024.

Task 3-3 -- (Required Tasking) -- Update of Deep-Draft Vessel Operating Costs (DDVOCs) Database and Supporting Numerical Model Relationships

Time allowance(s): Within one-hundred ten (110) calendar days of provision of revised power and emission model relationships by the Government with anticipated availability of subject model relationships by no later than 30 June 2024.

Task 3-4 -- (Optional Tasking) -- Process Code Enhancement for System Performance

Time allowance(s): If assigned or exercised per specification as an optional tasking; to be completed within three-hundred forty (340) calendar days from the general contract notice to proceed (NTP).

Task 3-5 -- (Optional Tasking) -- Update and enhancement of statistical view(s) formats for vessel characteristics and Display(s) Enhancements

Time allowance(s): If assigned or exercised per specification as an optional tasking; to be completed within three-hundred twenty (320) calendar days from the general contract notice to proceed (NTP).

Task 3-6 -- (Required Tasking) -- Risk Management Framework (RMF); Periodic Review and Compliance; Support for Migration to Cloud Environment

Time allowance(s): To be completed within three-hundred forty (340) calendar days from the general contract notice to proceed (NTP) with applied time allowances of within thirty (30) calendar days when requirements for review are announced (anticipated within 180 to 210 days) after the general contract notice to proceed (NTP).

Task 3-7 -- (Required Tasking) -- Enhancements for Value-to-the-Nation (VTN) Reporting - The contractor will complete first phase development of a more automated VTN framework including creation of the baseline data file structure for pre-project depths based on data to be provided by the Government with development of the base framework for tallying of needed computations on a nationwide level employing an efficient mode of batch system processing.

Time allowance(s): Required within one-hundred and ninety (190) to two-hundred and ten (210) calendar days after the general contract notice to proceed (NTP).

Completion and Closeout of contract obligations -- Not to exceed three-hundred ninety (390) calendar days from the initial notice to proceed (NTP) which includes all allowances for forwarding of materials and supporting documentation that is property of the Government subject to requirements of the PWS.

Contract Specifications for Compliance with Handling Sensitive or Proprietary Information and Operational Security (OPSEC) Requirements

The work associated with the performance work statement (PWS) as set forth for this contract will be unclassified but the contractor will be required to handle and work with information considered sensitive and proprietary to interests in the private sector who provide data to the Government (voluntarily and otherwise) and the U.S. Army Corps of Engineers (USACE) that is protected under limitations of disclosure subject to Section IV of the Freedom of Information Act (FOIA; current and as amended). Correspondingly, much of the data handled herein is considered to be assessed as controlled unclassified information (CUI) and will be protected accordingly. Correspondingly, within twenty-two (22) calendar days of contract award, the contractor’s official representative for this contract and any of its employees who will have access or handle data identified by USACE as sensitive or proprietary will be required to sign agreements for non-disclosure (NDA) and non-alternative \ non-derivative use (NANDU) that will limit the access and use of subject data only to activities and requirements essential to execution of the work and technical requirements as set forth by the (PWS) objectives and specifications described herein.

In addition to the handling of sensitive and proprietary data as described additional requirements will or may apply depending on requirements for execution of work specification set forth herein. Such requirements under this contract are defined to include the following clauses associated with, and deemed applicable under, operational security (OPSEC):

Clause 1 -- General Security Requirements & Guidance (AT\OPSEC Review Clause 1; ENG Form 6055; May 2022): The security requirements described below apply to all contract personnel (including employees of the prime Contractor (“Contractor”) and all subcontractor employees (or any other employee affiliated with working requirements) supporting the performance requirements of this contract. The Contractor is responsible for compliance with these security requirements. Questions regarding security matters shall be addressed to the designated Government representative (e.g., Contracting Officer Representative (COR), Requiring Activity (RA) representative, or Contracting Officer (if a COR or other RA representative is not appointed)). Contract personnel are critical to the overall security and safety of US Army Corps of Engineers (USACE) installations, facilities and activities, and security awareness training contributes to those efforts. The Department of Defense (DoD) and Army security training requirements specified below, if applicable, are performance requirements; all applicable contract personnel shall complete initial training within thirty (30) days of contract award or the date new contract personnel begin performance on the contract. Within five (5) business days from the completion of training, the Contractor shall provide written documentation (e.g., email or memorandum) to the Government representative. The documentation shall include the names of contract personnel trained and which training they completed; the Contractor shall maintain training records as part of their contract files and be prepared to provide copies of training certificates to the Government representative. Contractor personnel and vehicles are subject to search when entering federal installations. Additionally, all contract personnel shall comply with Force Protection Condition (FPCON) measures, Random Antiterrorism Measures (commonly referred to as “RAMs”), and Health Protection Condition (HPCON) measures. The Contractor is responsible for meeting performance requirements during elevated FPCON and/or HPCON levels in accordance with applicable RA plans and procedures --this includes identifying mission essential and non-mission essential personnel. In addition to the changes otherwise authorized by the changes clause of this contract, should the FPCON or HPCON levels at any individual facility or installation change, the Government may implement security changes that affect contract personnel. The Contractor shall ensure all contract personnel are aware of their security responsibilities, including any site-specific requirements identified in local policies or procedures.

Clause 2 -- Antiterrorism (AT) Level I Training (AT/OPSEC Review Clause 2; ENG Form 6055; May 2022): Specific to contractor employees with an area of performance within an Army-controlled installation, facility or area, all contractor employees, to include associated subcontractor employees (or any other employee affiliated with working requirements of this contract), requiring access to Army installations, facilities, controlled access areas, or who require network access, shall complete AT Level I awareness training within 30 calendar days after contract award or start date or effective date of incorporation of this requirement into the contract, whichever is applicable.