Legacy App Modernization in Denver for Energy, Cannabis and Aerospace

ZTABS modernizes legacy applications for Denver enterprises in energy utilities, cannabis operations, aerospace and government. Denver's energy utilities operate legacy CIS and SCADA systems deployed 15 to 20 years ago. Cannabis operators run seed-to-sale platforms needing Metrc integration modernization. Aerospace manufacturers maintain legacy MES systems. ZTABS is remote-first by design from our Houston, Texas office.

Denver's legacy modernization demand spans utility CIS systems that cannot support modern rate structures and demand response, cannabis platforms needing current Metrc API integration, aerospace MES systems approaching vendor end-of-support, and government applications requiring citizen digital access.

Legacy app modernization in Denver at a glance

Need	What we build	Key requirement
Energy utility	CIS and SCADA modernization	NERC CIP, rate calculations
Cannabis	Seed-to-sale platforms	Metrc integration, compliance
Aerospace	MES modernization	AS9100, traceability
Government	System replacement	Citizen UX, records
Oil and gas	Field operations	ECMC compliance, safety

Energy utility CIS modernization

Denver energy utilities operate legacy customer information systems for billing, meter management, service orders and customer service. Systems deployed 15 to 20 years ago cannot support modern rate structures, distributed energy resources, demand response programmes or customer self-service.

Billing system modernization. Legacy rate engines with complex tiered, time-of-use and demand-based rate structures modernized. Business rules for rate calculation, usage-based billing, demand charges and renewable energy credits extracted from legacy code and validated with utility rate analysts. Historical billing data migrated with reconciliation against financial records.

Meter data management. Legacy meter reading and data management modernized for AMI smart meter integration, interval data processing and real-time usage analytics. Historical meter data migrated with read verification.

Customer portal. Legacy customer service interfaces replaced with modern self-service portals. Online payment, usage analytics, outage reporting and distributed energy resource management. Mobile-first design for field access.

Service order management. Legacy service order systems modernized for mobile workforce management, automated scheduling and real-time status tracking. Historical service order records preserved.

SCADA and OT modernization

Denver energy companies operate legacy SCADA systems for generation, transmission and distribution operations.

SCADA historian. Legacy historians migrated to modern time-series platforms preserving years of operational data. Cloud analytics enabled while maintaining OT security boundaries. OPC UA connectivity for modern equipment integration.

HMI modernization. Legacy human-machine interfaces upgraded for modern displays, mobile access and improved alarm management. Operator effectiveness maintained during transition.

EMS modernization. Legacy energy management systems modernized for real-time market operations, renewable integration and advanced distribution management. Historical operational data preserved.

Cannabis seed-to-sale modernization

Denver cannabis operators run seed-to-sale platforms needing Metrc integration modernization and operational efficiency.

Metrc integration. Metrc integration requires tenant, facility and licence specific integrator credentials. Legacy systems modernized with current Metrc API integration for plant tracking, harvest management, package creation and transfer tracking. Each facility and licence has distinct integration requirements.

Inventory management. Legacy inventory systems modernized with real-time tracking, batch genealogy and automated Metrc synchronisation. Historical inventory records migrated with lot traceability.

Point of sale. Legacy POS systems modernized with Metrc-compliant transaction recording, real-time inventory deduction and customer management. Compliance reporting automated.

Aerospace and defence modernization

Denver aerospace companies operate legacy MES and quality systems for defence and space programmes.

MES modernization. Legacy MES replaced with modern platforms. AS9100 is an organisational QMS applied to programme and contract scope, not a software certification or automatic continuous compliance. Complete lot genealogy preserved. The National Renewable Energy Laboratory (NREL) was renamed to the National Laboratory of the Rockies (NLR) on 1 December 2025. Current entity naming used in compliance documentation.

Quality and configuration. Legacy quality management and configuration control modernized. Engineering change history preserved. Bill of materials accuracy verified.

Colorado regulation

SB 26-189. SB 26-189 repeals and re-enacts SB 24-205. Covers automated decision-making technology (ADMT) with material influence in enumerated consequential domains effective January 1 2027. Both developers and deployers must retain compliance records for at least 3 years. Developers must provide technical documentation and material updates. Deployers must provide point-of-interaction notice and a plain-language description of the ADMT role within 30 days after an adverse consequential decision. Separate rights to request data correction and meaningful human review and reconsideration also apply. Not all legacy systems must rewrite to meet the law, and this is not the older impact-assessment-only regime.

CPA. Colorado Privacy Act applies to controllers processing 100K or more Colorado consumers OR 25K or more consumers AND deriving revenue or receiving a discount from the sale of personal data, with actual nexus conditions, consumer context and specific entity and data category exemptions. Legacy systems handling Colorado consumer data modernized with CPA-compliant data handling.

NERC CIP. NERC applies to actual registered entities with applicable standard BES (bulk electric system) function. CIP standards for cybersecurity apply to BES cyber systems within scope. Billing CIS is not automatically CIP-scoped. Control mapping and approved validation apply, not guaranteed continuity for all systems. Utility rate approval involves actual PUC or, for municipal and cooperative utilities, the applicable governing authority. Legacy SCADA and EMS modernization must maintain NERC CIP compliance throughout transition for in-scope systems.

ECMC. ECMC (Colorado Energy and Carbon Management Commission) is the current name, replacing the former COGCC (Colorado Oil and Gas Conservation Commission). Oil and gas field operations systems reference current regulatory entity names.

Modernization methodology

Application archaeology. Reverse-engineering business rules from legacy CIS, SCADA and seed-to-sale code. Utility rate calculation rules often have decades of accumulated regulatory orders embedded. Each rule documented, validated and categorised.

Seam selection. Utility CIS seams: billing, meter data, customer service, field operations. Cannabis seams: inventory, POS, compliance reporting, customer management. Each function extracted independently.

Data migration. Automated migration with row-count verification, aggregate validation and sample record comparison. Utility billing data reconciled against financial records. Cannabis inventory data reconciled against Metrc records. Legacy preserved in read-only mode.

Strangler fig coexistence

Single authoritative write for each object and period. Utility billing: which system calculates and posts bills during coexistence. Cannabis inventory: which system is authoritative for Metrc-reportable quantities.

Dual-write only with engineered CDC design. Idempotency keys enforced by receiving side. Unknown outcomes require reconciliation before replay, especially for utility payments, cannabis sales and inventory transactions. Finite retries with DLQ and quarantine for conflicting events. Retrieve current external state and reconcile before uncertain payment or inventory replay.

Data mapping of types, nulls, time zones, currency, rounding, identifiers, encoding, history, retention and crosswalks. Utility-specific: rate schedule effective dates, meter constants, demand windows and billing periods. Cannabis-specific: plant identifiers, harvest batch numbers, package UIDs and Metrc tag assignments.

Regression and testing

Representative business-critical paths: utility billing cycle, meter-to-cash, service order lifecycle, cannabis seed-to-sale tracking, Metrc compliance reporting. Meaningful integration, performance and manual UAT with domain expert approval. Utility testing includes rate calculation verification against PUC-filed rates.

Cost and timeline

Legacy system modernization follows the published cost guide.

Tier	Range	Timeline	Example
UI Modernization	$40K to $100K	8 to 16 weeks	New frontend, API wrapper, improved UX
Re-Platforming	$100K to $250K	16 to 32 weeks	Modern stack, containerization, cloud, data migration
Re-Architecture	$250K to $400K	8 to 14 months	Decompose monolith, event-driven, modern data layer
Full Rebuild	$400K to $500K+	12 to 18+ months	Ground-up rebuild with agreed availability target, rehearsed staged cutover and maintenance windows

Vendor comparison

These 2026 US-buyer planning ranges illustrate re-platforming a 10 to 15 year old business-critical system using a strangler fig approach, modern stack, API wrappers, phased data migration and regression harness. They are guide-based illustrations, not empirical market surveys or independent local quotes.

Vendor route	Typical cost	Timeline
Freelance or dev collective	$40K to $130K	5 to 12 months
Offshore systems integrator	$60K to $200K	8 to 14 months
ZTABS	$100K to $280K	6 to 12 months
Large consultancy	$300K to $1M+	10 to 18 months
SaaS replacement (where a vendor fits)	$50K to $200K implementation	4 to 9 months

The published re-platforming guide's combined allowance for parallel-running infrastructure, knowledge-transfer from senior staff and where-applicable compliance revalidation is $100K to $500K or more regardless of vendor path, with SOX, HIPAA and FDA as the guide's example regimes. This is a scope-dependent planning illustration, not a universal surcharge or all-regime requirement. Actual project regimes such as NERC CIP validation and shared-infrastructure costs are separately scoped per engagement. Selected licences, vendor contracts, data cleansing, dual-run support and revalidation boundaries apply. Oracle Utilities, SAP IS-U and similar platforms may require implementation through a licensed or qualified provider depending on the selected customer contract, product edition and vendor programme.

Proposal evaluation criteria

Use these criteria when evaluating any vendor proposal for this engagement, including ZTABS:

Criterion	What to verify
Strategy, deliverables and acceptance	Agreed modernization approach with keep, upgrade, configure or replace alternatives for each system and documented acceptance criteria
Data source-of-truth and reconciliation	Which system is authoritative for each object and period, CDC and reconciliation design evidence, data ownership boundaries
Rehearsal, cutover and rollback	Phased rehearsal with actual maintenance windows, rollback feasibility after new writes and schema changes, record and control validation with approved RTO and RPO
Security, privacy and compliance	Access, safety and compliance evidence during and after migration, exception register with owner acceptance, residual risk documentation
Full recurring costs	Licences, parallel-run infrastructure, third-party vendor, support, data cleansing and revalidation costs separately itemised
Human roles and responsibility	Trainer, validator and support responsibility split, agreed staff languages, documentation, review, translation and onsite terms

Inventory and discovery

Denver enterprise modernization begins with complete inventory: applications, users, scheduled jobs, database procedures, reports, file and EDI dependencies, vendor contracts, supported versus end-of-life versions. Energy utilities commonly have legacy systems accumulated over decades of rate case proceedings with rate calculation rules embedded in code reflecting years of PUC orders.

Business rules discovered with users through representative transaction analysis. Utility rate calculation rules validated against PUC-filed tariffs. Cannabis compliance rules validated against MED regulations and Metrc requirements. Aerospace manufacturing rules validated against programme specifications and AS9100 procedures.

Integration and dependency management

Utility integrations. AMI meter data feeds, SCADA historian connections, outage management interfaces, payment processor connections and regulatory reporting. Each integration supporting continuous utility operations.

Cannabis integrations. Metrc state tracking system with tenant, facility and licence specific credentials. Payment processor connections. Delivery tracking. Lab testing result integration. Each integration documented and tested against current API specifications.

Aerospace integrations. Customer programme data exchange, supplier quality data, MES equipment interfaces and regulatory reporting. Defence programme security requirements for data handling.

Authentication versus authorisation. Authentication identity distinct from facility-level, licence-level and role-level authorisation. Cannabis systems require licence-specific access controls. Utility systems require jurisdiction-specific access controls.

Logs and retention

Logs minimise and redact secrets and regulated payloads with actual retention and legal holds. Utility billing records retained per PUC requirements. Cannabis transaction records retained per MED requirements. NERC CIP logs retained per compliance requirements.

How delivery works

ZTABS is remote-first by design from our Houston, Texas office. Mountain time alignment managed with Central time. Energy utility operations often require coordination with field crews and control centre staff.

Assessment. Application archaeology, business rule extraction, regulatory mapping and modernization strategy. Utility assessment includes rate rule analysis and NERC CIP scope determination. Cannabis assessment includes Metrc integration analysis and MED compliance review.

Incremental migration. Strangler fig extraction with phased cutover. Utility migration phased around billing cycles and rate case proceedings. Cannabis migration phased around harvest and inventory cycles.

Cutover and decommission. Documented rollback plans. Utility cutover timed for billing cycle boundaries. Cannabis cutover coordinated with Metrc reporting periods. Legacy decommission with data archived for regulatory retention.

Risks and mitigations

Rate calculation errors. Utility billing rules validated against PUC-filed tariffs with parallel billing verification. No billing cutover without rate analyst approval.

Metrc synchronisation. Cannabis inventory reconciled against Metrc at every migration stage. Cutover requires the customer licensee and compliance owner to validate current MED and Metrc obligations and confirm actual API credentials and permissions for the modernized system.

NERC CIP gaps. CIP compliance maintained throughout for BES cyber systems. Security controls documented and verified at each stage.

Modernization approach selection

Denver enterprises need clear criteria for choosing between approaches.

Targeted remediation. Adding specific capabilities. Example: adding AMI smart meter data ingestion to legacy CIS while keeping the core billing engine.

Re-platforming. Moving to modern infrastructure. Example: migrating legacy CIS from on-premises to cloud while preserving rate calculation logic.

Re-architecture. Decomposing into services. Example: extracting billing engine, meter data management, customer portal and field operations as independent services.

Full rebuild. Ground-up development. Example: replacing a legacy cannabis POS system on unsupported platform.

SaaS replacement. Replacing custom with commercial products. Low build risk but high fit risk for utility rate structures and cannabis compliance requirements. Oracle Utilities, SAP IS-U and similar platforms may require implementation through a licensed or qualified provider depending on the selected customer contract, product edition and vendor programme. Cannabis point-of-sale SaaS must meet current MED and Metrc API integration requirements for Colorado operations.

Handover

Modernization handover includes runbooks, data lineage, licensing, support contacts and accountable owners. Utility handover includes rate rule documentation, NERC CIP compliance documentation and operational procedures. Cannabis handover includes Metrc integration specifications and MED compliance documentation.

When ZTABS is not the right fit

These describe the boundaries of this proposed modernization engagement, not company-wide limitations.

• The system still works and nobody is asking for changes. Wait for a real forcing function.
• Oracle Utilities or SAP IS-U full implementation. Licensed vendor scope. A separately scoped assessment or integration engagement may apply.
• On-site embedded team at utility facility. ZTABS is remote-first by design. If the engagement requires permanent on-site staff, a separately scoped arrangement would apply.
• NERC CIP or ECMC regulatory advisory. This engagement builds platforms, not regulatory advice. Regulatory advisory is a separately scoped professional service.

White-label AI products

ZTABS builds custom white-label AI products for clients to brand and resell. Denver energy and cannabis companies can commission white-label AI platforms for distribution under their own brand.

Data type mapping for utilities

Energy utility data has unique types requiring careful migration planning. Meter readings with timestamp, read type, demand readings and interval data. Rate schedule effective dates with PUC or applicable governing authority order references. Billing determinants including usage tiers, demand windows, power factor, time-of-use periods and seasonal adjustments. Service point addresses with GIS coordinates and transformer associations. Outage records with device, duration, cause and customer impact. Distribution asset records with inspection history, test results and replacement schedules.