Billing has to follow what the meter actually measured.
What does industry-depth work actually mean?
Industry-depth energy work means project operations for solar EPC and metering-to-billing loops that reconcile — not a slide deck about green IT.
Energy buyers often get either a project tool or a meter API. The hard part is the join. Survey, design, BOQ, subsidy paperwork, and commissioning have to become a system. Meter readings have to become billable truth.
We productized rooftop and C&I solar operations as Solar EPC on Odoo 19 Community. Metering and device estates route through Metering, Energy & Devices. Prior solar delivery includes Teravon (named in prose only; case page retired). Nordic energy partner work stays anonymous until cleared.
Does any of this sound familiar?
Project paperwork and the ERP project record are not the same job.
Meter readings arrive; invoices still need a human to invent the line.
Subsidy or government paperwork sits outside the system of record.
A solar implementation was left without a product path for the next site.
Device credentials and feeds expire without an owner.
Quotes compare IoT brands, not reconciliation schedules.
If you recognised three of these, you do not need another green brochure. You need field truth that becomes a commercial record.
What this looked like when it had to hold.
Solar EPC · productized project operations
Rooftop and C&I solar on Odoo 19 Community: survey, design, BOQ, government paperwork, subsidy, commissioning, AMC — a finished application path when the pattern kept repeating.
Solar EPC product →Metering & devices · feeds that must reconcile
Energy metering and device integrations under Integration Engineering — readings, credentials, and recovery paths treated as standing liabilities, not a one-time API demo.
Metering, Energy & Devices →Teravon · prior solar delivery (textual reference)
Earlier solar-industry implementation work delivered under the Teravon engagement. The dedicated case URL is retired; the name remains as unlinked prose only.
A Nordic energy partner estate (metering → billing → e-invoice → accounting sync) remains anonymous until naming clearance (D41a).
What an industry engagement covers, and what it does not.
In scope
- Solar EPC operations via product or custom delivery.
- Metering and device integration with reconciliation in scope.
- Honest fences when the need is only a connector or only a brochure site.
Not in scope
The interesting engineering starts when the meter and the invoice disagree.
We build for operators who bill energy and deliver solar projects. How we work is on How we work.
How an industry engagement runs.
-
01
Situation call
What breaks in operations, what cannot pause, and whether something is already failing users.
-
02
Estate map
Name the processes, systems, and conflict cases that define this vertical.
-
03
Options on paper
Implement, migrate, integrate, product, process-only, or rescue first. Each option carries what you give up.
-
04
Recommended path
One primary recommendation and the conditions under which we would change it.
-
05
Hand-off into Services or stop
You keep the write-up. Delivery lands on a named Service, Solution, or Product page — not a vague phase two.
Questions we get first.
Should I buy Solar EPC or a custom build?
If you fit rooftop or C&I solar operations, start at Solar EPC. If you do not fit, we say so and route to custom delivery.
Is Teravon a live case study?
No. The case URL is retired. Teravon may be named in prose only.
Can you name the Nordic energy partner?
Not yet. Anonymous until clearance.
What does this cost?
Product pricing or scoped delivery after the situation call — in writing before work starts.
Get an energy path that bills what was measured.
Tell us whether the pain is EPC operations or metering truth. We will say product, integrate, or custom delivery.