AMENDMENT No. 003: Fuel Management Cloud Software & Integration (SaaS) at North Dakota National Guardview on SAM.gov

AMENDMENT No. 003: Questions raised by interested Vendor with the Government Answers NOTE: These are the answers to the final set of questions received, specifically related to software and digital processing of information areas. The DUE DATE has been extended until COB Tuesday 1SEP2026 in order to allow all interested small business companies enough time to prepare their quotes. Section 3: Existing Databases and PetroVend Environment Question: Where are the existing PetroVend card libraries and Phoenix SQL databases hosted? Answer: The environment operates on a multi‑tier on‑premises architecture within the NDNG secure network enclave: Database Server: A4‑120 hosting the master PhoenixSQL database and card/account libraries. Application/Web Server: C2‑120 hosting the OPW Phoenix application services and polling engine. Question: What database platforms/versions are currently being used? Answer: Microsoft SQL Server 2019 Standard Edition (64‑bit), Version 15.0.4435.7, running on Windows Server 2025 Standard. The environment uses the standard, unmodified OPW PhoenixSQL relational schema (Card, Account, Transactions, Site, SiteTanks, SiteTankInventory, TG* tables). Question: Are the databases accessible through standard interfaces (e.g., SQL/API), or are there restrictions? Answer: The database tier supports T‑SQL, ODBC, and OLE DB. Direct inbound access from external commercial endpoints is prohibited under DoD and NDNG cybersecurity policy. Administrative access requires CAC/PKI (ASCL) multi-factor authentication. For data migration, we could provide a full SQL server backup (.bak file) of the PhoenixSQL database. Question: What is the approximate size of the database(s) that would need to be migrated? Answer: The active PhoenixSQL database size is 91.50 MB total (56.06 MB data / 35.44 MB log). Question: Is the requirement to migrate historical data, or only what is necessary to establish the new system? Answer: Per discussion with MAJ Malo, the requirement is to migrate all active master configuration records (Card, Account, Site, SiteTanks, Products), along with 100% of all posted historical transaction records stored in dbo.Transactions. Section 4: Data Extraction and Integration (Database Scope) Question: Is the requirement to retrieve transaction data after posting, or is real‑time/direct fueling hardware integration required? Answer: From the database tier, transaction records are accessible post‑settlement once posted to the dbo.Transactions table. Real‑time hardware integration questions fall under the State Fuel Logistics/Facilities team. Question: Are there existing APIs, interfaces, or integration documentation available? Answer: There is no proprietary REST API available. Integration relies on standard OPW PhoenixSQL relational tables and views (Transactions, Card, Account, SiteTanks, SiteTankInventory) accessible via SQL within the internal environment. ------- END of AMENDMENT No…