NDARNG __ USPFO Fuel System PWS (JUL2026) Software Only.pdf

PERFORMANCE WORK STATEMENT (PWS)

Fuel Management Cloud Software & Integration (SaaS) North Dakota National Guard (NDNG)

1.0 GENERAL INFORMATION

1.1 Background: The North Dakota National Guard (NDNG) currently operates physical fuel dispensing and monitoring hardware across up to six (6) locations. The Government requires a modern, cloud-based Software-as-a-Service (SaaS) platform to replace aging, locally hosted management software while retaining the existing physical site hardware.

1.2 Scope: The Contractor shall provide all software licensing, cloud hosting, data migration services, connectivity gateways (if required to bridge legacy hardware), and training to implement a centralized cloud-based fuel management platform. Note: This contract is strictly for software, data migration, and connectivity; no physical fuel dispensers, ATGs, or island terminals will be replaced under this PWS.

2.0 SYSTEM ARCHITECTURE & COMMUNICATION REQUIREMENTS

2.1 Cloud-Based Platform (SaaS): The Contractor shall provide a Commercial-Off-The- Shelf (COTS) cloud-based software solution hosted on an enterprise-grade commercial cloud infrastructure (e.g., Microsoft Azure). The platform's user interface must utilize a customizable, widget-based dashboard allowing users to drag and drop reporting modules (e.g., tank levels, recent transactions, active alarms) onto a personalized home screen.

2.2 Legacy Hardware Connectivity: The Contractor shall provide any necessary edge-networking devices or software gateways required to connect the Government’s existing legacy fuel island controllers to the cloud platform.

2.3 Primary Communication (Wi-Fi/Ethernet): The system must utilize the Government’s existing Wi-Fi or Ethernet networks as the primary mode of data transmission between the legacy site hardware and the cloud platform.

2.4 Secondary/Contingency Communication (Cellular): The Contractor shall provide a cellular connection/modem as a secondary, backup means of communication to prevent data loss in the event of a local network interruption. The Contractor is responsible for the recurring annual subscription/data costs associated with this connection.

2.5 System Security & Access: The cloud platform must require Multi-Factor Authentication (MFA) for administrative access. The software must support Role-Based Access Control (RBAC) to allow tiered permissions (e.g., Global Administrator, Site Manager, Read-Only Auditor).

3.0 LEGACY INTEGRATION & DATA MIGRATION REQUIREMENTS

3.1 Native Hardware Integration: The cloud software must natively communicate with the Government’s existing legacy PetroVend hardware and OPW-protocol Automatic Tank

Gauges (ATGs) to poll real-time transaction, leak detection, and compliance data without requiring the Government to purchase third-party protocol converters.

3.2 Legacy Data Migration: The software implementation must include native, middleware-free ingestion and translation of the Government’s existing legacy PetroVend card libraries and Phoenix SQL databases. The Contractor guarantees zero data loss or required manual data re-entry during the migration to the new cloud environment.

3.3 Authentication Tracking: The software must retain the ability to track existing WEX/Voyager card transactions and existing legacy PetroVend magnetic swipe cards currently used by the Government.

3.4 Active Alarming: The cloud dashboard must capture existing hardware alarms (e.g., low fuel, ATG leak alerts) and generate automated user notifications (e.g., SMS, email) to designated NDNG personnel.

4.0 REPORTING & DATA MANAGEMENT

4.1 Immutable Audit Trails: The system must maintain an unalterable log of all administrative actions within the software (e.g., adding users, manual inventory adjustments, acknowledging alarms) complete with time and date stamps.

4.2 Custom Reporting: The software must generate scheduled and on-demand reports regarding fuel usage, inventory levels, and environmental compliance, exportable in PDF, CSV, and TXT formats. Automated email distribution of these reports must be supported.

4.3 Offline Data Sync: If the local network and cellular backup fail, the edge connection device must be capable of polling the legacy hardware's stored offline transactions and automatically syncing that data to the cloud once connectivity is restored.

5.0 TRAINING & SUPPORT

5.1 Software Training: Upon successful software migration and system testing, the Contractor shall conduct comprehensive training (virtually or on-site) for NDNG personnel.

Training must cover dashboard navigation, report generation, user management, and administrative functions.

5.2 Technical Support: The Contractor must maintain a technical support helpdesk to troubleshoot software bugs, cloud access issues, and connectivity drops between the legacy hardware and the cloud platform.

6.0 DELIVERABLES MATRIX

Deliverable Description Due Date

Software Implementation Plan

Detailed schedule of network gateway installation, database migration, and cloud rollout.

15 days after contract award

Legacy Database Migration

Complete ingestion of existing Phoenix SQL/PetroVend libraries to the cloud.

Per approved Implementation Plan

Software Access Provision of administrative and user accounts to the cloud dashboard.

Upon completion of migration

Software Training Training session(s) for designated NDNG administrators and managers.

Within 14 days of final migration

System Manuals Digital copies of Software User and Administrator manuals.

Prior to Training