Platform
Manufacturing, site energy management and verification
INDUSTRY, SPACES and VERIFY serve different decisions. Current demonstrations use simulated data; their results are not customer achievements or guaranteed savings.
- Fieldmeter · sensor · count
- Edgecollect · qualify
- ATSAVE Cloudoperational foundation
- Carbokacontext · evidence
- Decisionhuman-directed action
The data chain
Give every signal a place in the operation.
Field and edge
Collect readings from the agreed measurement points and preserve units, timestamps and equipment references.
Operational context
Relate records to production periods, outputs and the conditions that explain them.
Decision and review
Present the evidence for a responsible person to assess and act on.
Manufacturing, site energy management and verification
INDUSTRY, SPACES and VERIFY serve different decisions. Current demonstrations use simulated data; their results are not customer achievements or guaranteed savings.
INDUSTRY
Manufacturing energy management: connect equipment states, work orders, production and quality to energy. Current demonstrations include start/pause/resume, quality reporting and frozen batch-energy records.
Explore the workflowSPACES
Site energy management: compare premises, zones, equipment, operating schedules and parent/submeter relationships. Keep electricity, estimated cost and electricity-related emissions separate; incomplete periods remain marked.
Explore the workflowVERIFY
Measurement and verification: connect plans, instruments, baseline models, changes, reporting data, review and released reports. Client and analyst workspaces show authorized project records.
Explore the workflowINDUSTRY | Trace energy from work order to product.
Manufacturing energy management: connect equipment states, work orders, production and quality to energy. Current demonstrations include start/pause/resume, quality reporting and frozen batch-energy records.
MES and output reconciliation
Five paths cover hardware counts with hourly or daily MES good output, hourly or daily good output without a counter, and manual reporting. Align equipment, periods and units; a count difference is not automatically a reject.
Product energy flow
Trace sources, equipment, orders and batches. Keep finished-product, work-in-progress, non-processing and unallocated energy distinct; do not double-count main and submeters. Footwear demonstrations follow model, size and six stages within one simulation.
Product ECO and its evidence
Compare energy and output against the applicable product standard, retaining rule versions and reasons. Missing quality, energy or attribution remains unknown. A green indicator neither clears safety alarms nor certifies a product.
Include production, warm-up, changeovers, idle time, rejects/rework and shared loads. Allocated energy plus the unallocated remainder must reconcile to the measured boundary. Do not add parent and submeters twice.
Arrange a software demoSPACES | Turn site energy into accountable action.
Site energy management: compare premises, zones, equipment, operating schedules and parent/submeter relationships. Keep electricity, estimated cost and electricity-related emissions separate; incomplete periods remain marked.
Data quality
Identify gaps, duplicates, delays and meter changes. Missing readings remain missing, not zero.
Cost reconciliation
Review electricity and estimated charges line by line, with differences and tariff versions. Demo tariffs are not current tariffs for every country.
Savings opportunities
Link unusual consumption to evidence, an owner and a next action. Separate essential continuous loads and approved overtime.
Site comparison
Compare authorized sites by operating hours, area or output. Do not rank sites with missing denominators.
Demand analysis
Use complete 15-minute energy intervals to examine average power and peaks; retain incomplete-data notices.
Version snapshots
Preserve inputs, quality and processing versions so a team can revisit the basis of a decision.
VERIFY | Connect savings conclusions to traceable evidence.
Measurement and verification: connect plans, instruments, baseline models, changes, reporting data, review and released reports. Client and analyst workspaces show authorized project records.
Five-step project plan
Define goals, method and boundary, measurement, judgement and review, then check the draft. Completing a form starts a plan; it does not approve it.
Establish and freeze the baseline
Connect instrument calibration, data quality, baseline models and intervention records for comparison under reporting-period conditions.
Independent review
Seven system record gates and twelve human review items distinguish record completeness from the suitability of methods and evidence.
Release and receipt
Review a specified report version before releasing the client summary, report and next steps. Technical review, client receipt and formal acceptance remain separate.
The demonstration supports five Option B equipment methods and an Option C daily-energy model. Option A calculations and Option D external calibrated models are not enabled. Formal conclusions still require project evidence and independent review.
Branded client workspaces can show authorized projects, progress, released reports and discussions. Technical review, report release and customer receipt are separate records. This is not a universal supplier-ranking or product-footprint portal.
Arrange a software demoChoose a role, then follow the relevant workflow.
Brands explore products and suppliers; manufacturing teams explore orders, quality and energy flow; site managers explore consumption and actions; analysts explore plans, review and delivery. Share your role and question to arrange a focused software demonstration.
Arrange a software demoCurrent software scope and project readiness
Available demonstrations
Product energy flow, product ECO, site energy analysis and verification workflows have demonstrations using simulated or synthetic data. Real projects require measurement and implementation acceptance.
Local previews
Domestic load classification and equipment/product ECO modes, plus international people-related energy flow, remain local builds in these documents and are not yet in the cloud demo. The people-energy preview offers Traditional Chinese and English; it allocates electricity, not a complete personal carbon footprint.
Integration roadmap
Cameras, intercoms, staff calls and buzzer control still require integration and device validation. They are not presented as connected hardware, autonomous control or legally qualified signatures.
Capability status follows product documents dated 2026-10-07. Confirm availability for the selected demonstration and project.
Software entry and verification workflows offer Traditional Chinese, Simplified Chinese, English, Japanese and Korean. Coverage varies by module and screen; website language coverage does not imply identical software coverage.
A real deployment requires instruments, time alignment, quality sources, access rights, persistent storage and backups. Equipment connections, enterprise-system exchange and notification delivery must be tested for the actual site.
Demonstrations explain decisions. A software report or content fingerprint is not third-party certification, a carbon credit or a complete product carbon footprint. Site management reports are not independently verified savings reports.
Implementation questions
Plan the connection before the integration.
Can it connect to our existing equipment?
The equipment model, protocol, data access, sampling needs and network constraints must be reviewed. Share an equipment and source inventory to start a compatibility discussion.
Will AI control production automatically?
Current scheduling demonstrations compare candidate actions using rules, capacity, maintenance and delivery constraints. Tariff and carbon signals are assumptions. People approve trials and retain stop and rollback decisions; this is not autonomous machine control or fault prediction.
Can we see the actual product?
Request a scoped demonstration. The diagrams on this website explain the operating model; they are not screenshots of a configured customer environment.
What should IT and operations prepare?
Identify source owners, allowed access methods, site connectivity, timestamp conventions and any restrictions on data leaving the site. Do not submit credentials or confidential production files through the public form.
Carboka and ATSAVE: clear, complementary roles.
Carboka · Carboka connects IE+E, OEE+E, TPM+E and ROI+E with product context, comparable indicators and improvement records, helping teams understand a result and decide what to do next.
ATSAVE · ATSAVE handles hardware selection, metering installation, site integration and ongoing maintenance. The actual project defines responsibilities and acceptance criteria.
Your next step
Request a scoped platform discussion.
Describe your systems and operational question so the demonstration can focus on a relevant workflow.