Publish RELEASE, HOLD or UNKNOWN for every model before an energy-efficiency market-access gap interrupts revenue
Bind the approved catalog and source paths once. SAXUM continuously reconciles every in-scope model against DOE CCMS filing evidence, California MAEDbS and NRCan evidence, derives DOE annual filing deadlines from the customer-approved category, and publishes a machine-readable RELEASE, HOLD or UNKNOWN state—then surfaces only the models that need action.
No fuzzy model matching. No invented DOE dates. No unbound regulator source can earn autonomous release. No inferred legal scope.
The three systems do not mean the same thing
DOE requires covered basic models to be certified before distribution in commerce and annually thereafter through CCMS; DOE also states that public-database listing is not DOE approval and that CCMS submission confirmation is proof of submission. California states that regulated models must be certified to MAEDbS before sale and that an Approved listing is the compliance evidence. SAXUM does not automatically turn Archived into a no-sale conclusion because product-specific sell-through/grandfathering exceptions can exist; archival therefore fails closed to review unless an approved rule basis is bound. For Canada, NRCan states that a dealer must ensure an energy-efficiency report is on file before import or interprovincial shipment, and that a new report is required only when the model is not already listed. SAXUM therefore accepts an exact current compliant-list match for the assured regulatory node as the reporting/listing control, while verification-mark evidence and material-change controls remain separate; absent or unmatched models require report/CREED evidence.
A regulatory library cannot tell you whether the model you plan to sell is actually controlled today
Requirements intelligence answers “what should apply?” Energy Market Access Control answers a different operating question: “For the exact active models in our catalog, what decisive evidence do we have in each customer-approved market right now?”
Download the redacted model-control template →
What usually breaks
New SKUs launch before every registry is reconciled; archived California models remain active in commerce data; a Canadian submission is still pending; or the business assumes a DOE public listing proves the underlying filing state.
What SAXUM changes
The model catalog becomes a controlled population. Every controlled cycle explains which required market is controlled, blocked, pending, unknown or missing evidence, carries forward the prior release state, and emits only material SKU changes for downstream action.
Built for brands large enough to feel model sprawl, small enough to hate enterprise compliance software
Private-label appliance and equipment brands, importers and manufacturers managing 20–500 regulated models across the U.S., California and Canada
Strong fit
Recurring product launches, multiple brands/OEMs, three-market exposure, spreadsheet-heavy regulatory operations and no large internal product-compliance platform team.
Weak fit
A handful of models, one jurisdiction, or a fully integrated enterprise product-compliance stack with current registry reconciliation already embedded.
Fastest onboarding
A clean active-model export plus recurring source-bound CCMS/MAEDbS/CREED or searchable-list exports. Existing labs and certifiers stay in place; SAXUM controls the portfolio around them.
One catalog in. A daily market-access control loop out.
Bind the catalog
SKU, exact model, brand, manufacturer and active status become the controlled population.
Approve scope once
For every model, the customer explicitly marks DOE, California and Canada as required or not required. SAXUM never infers legal coverage.
Connect evidence feeds
Use scheduled file drops or saved HTTPS, SFTP, Drive, OneDrive, S3, IMAP or directory connectors for customer-authorized current exports.
Reconcile exactly
Model identity is exact by default. Known naming differences require an explicit approved alias, not similarity scoring.
Escalate only exceptions
BLOCKED, UNKNOWN, PENDING, CONFLICT and renewal signals create work. Clean models need no repetitive review after autonomy approval.
Retain proof
Each cycle produces a model register, evidence register, exception list, renewal worklist and signed outcome evidence inside SAXUM.
No vague “probably compliant” status
CONTROLLED
Every customer-required market has decisive exact-identity evidence under the configured truth boundary.
BLOCKED
An explicit negative/rejected state, conflicting evidence, disabled required market or unconfirmed scope prevents reliance.
UNKNOWN / PENDING
Evidence is missing, unsupported, pending, California-archived without an approved sell-through basis, or—in DOE’s case—only a public listing without bound CCMS submission evidence.
A control pack management can actually use
Not a regulation feed. A current portfolio answer with evidence and an action queue.
Market-access register
Every active SKU/model, explicit scope flags, DOE/California/Canada state, overall control state and reason.
Exception worklist
Only models requiring action, with deterministic reason codes rather than generic “review” messages.
Evidence register
Source file, source row, evidence type, status, reference and date retained against the exact model/jurisdiction check.
Renewal worklist + control report
Customer-supplied DOE annual-certification dates can trigger due/overdue work without SAXUM inventing dates, alongside JSON/HTML control reports.
Daily monitoring without creating a daily job for your team
Two-cycle shadow onboarding
SAXUM proves mappings and evidence behavior before straight-through clean-cycle closure is enabled.
Source-change awareness
Scheduled source watchers surface government requirement changes without silently changing a model’s approved jurisdiction scope.
Exception-only human work
Once autonomy is approved, zero-actionable-finding cycles close automatically. Blocking or actionable findings remain reviewable and auditable.
Run the same deterministic control across multiple brands without mixing their evidence
Each client/entity keeps separate scope approvals, aliases, source evidence, exceptions and outcome proof while approved mappings and operating policy remain reusable.
Make the first subscription cycle earn its place
The first controlled cycle shows exactly which models were checked, which official-source evidence was bound, which markets are unresolved and what changed. Internal completion remains separate from external/provider acceptance.
Portfolio coverage
Active models, required market checks, controlled checks, scope gaps and source-role coverage are explicit—not hidden behind a single score.
Evidence-graded scorecard
Verified customer/source facts remain separate from estimates. Observed catalog/feed values or customer-supplied annual sales value can show the commercial portfolio affected without claiming hypothetical penalties or invented savings.
Outcome assurance
SAXUM only promotes the portfolio to a controlled outcome when there are no blocked or unknown models, scope is bound and all configured authority-source roles are present.
Pay for continuous portfolio control, not another seat-based compliance library
Onboarding includes the initial model/scope mapping and first controlled baseline. The recurring subscription covers scheduled reconciliation, exceptions, evidence retention, source-change monitoring and reports.
No regulator credentials are required by SAXUM. Existing labs, certifiers and regulatory advisers stay in place.
Run my model portfolio →Move from registry monitoring to launch and revenue control
SAXUM now separates commercial SKUs from customer-approved regulatory basic models, detects regulatory-material changes, projects known filing obligations through the planned launch date, and closes correlated regulator receipts back into the evidence cycle.
Lifecycle + delta
Commercial SKUs inherit control from their approved regulatory basic model where appropriate. New basic models, material modifications, commercial variants, rebindings and removals remain distinct, so adding a colour/packaging SKU does not automatically become a new regulatory filing while a real technical change cannot silently inherit the old state.
Launch + exposure gate
Join launch date, open-order value, inventory value and sales exposure to the regulatory state. The Launch Gate also looks forward to known deterministic obligations before the planned launch date, so a model that is RELEASE today is not mislabeled ready if a known DOE filing is due first.
Filing preparation, not invented authority
When a filing or recertification action is indicated, SAXUM produces a deterministic preparation JSON/workbook and requires customer authorization. DOE importer/certifier authority and optional exact submitted-workbook hash binding remain explicit; the preparation artifact is not represented as an official regulator form or legal attestation.
Energy Market Access Control FAQ
No. You or your qualified adviser approve the jurisdiction-scope flags for each model. SAXUM continuously controls evidence against that approved scope.
No. DOE expressly says public listing is not approval. SAXUM treats it as corroborative only and requires customer-held CCMS submission evidence before the DOE filing control is marked controlled.
No. Keep them. SAXUM is the portfolio-control layer that continuously reconciles your active commercial catalog against their/customer-held filing evidence and official status data.
SAXUM does not fuzzy-match decisive evidence. A known naming difference can be bound through an explicit approved alias, but release still requires a unique assured regulatory node combining the approved responsible party, product/equipment class and basic model; otherwise the model stays unresolved.
Yes. After two successful shadow cycles and owner autonomy approval, clean cycles can close straight through only when every required regulator role is machine-refreshed from an approved source binding. Manual or unbound sources remain attended. Exceptions remain visible for human resolution.
SAXUM does not silently equate Archived with prohibited sale. The model stays unresolved unless a current Approved record exists or an approved, authority-bound product-specific exception rule is explicitly attached to that model. Free-text customer notes cannot promote Archived into a controlled state.
When the exact assured regulatory node is currently present on NRCan's compliant searchable list and no energy-efficiency-affecting change breaks that identity, SAXUM can mark the reporting/listing predicate controlled. If the model is absent or cannot be matched exactly, report/CREED evidence is required. Verification-mark evidence remains a separate control.
The importer identity, certifier/submitter identity and any required third-party authorization remain explicit. A filing receipt does not silently establish authority for the wrong importer or an unauthorized submitter.
Verify the operating boundary yourself
The product is deliberately built around what the agencies themselves say their systems prove.
Primary-source review date: 16 August 2026. Re-check before each engagement.
Extend the same evidence discipline
Start with the catalog you already have
Send the shape of your model export—not credentials or sensitive regulator access. SAXUM can qualify the first control cycle from scoped sample data.