Automation as a product · for machine builders

Software becomes a business.
Even after delivery.

For machine and equipment builders with an installed base who engineer similar functions again and again.

Develop once. Deploy a thousand times. With logiccloud, automation software becomes a digital product: build functions as apps, bring them to delivered machines and sell them as upgrades or services — vendor-neutral and under your brand.

logiccloud ORCHESTRATElive
Installed base · X200 / Europe
MachineCustomer · siteVersionState
X200-0142Customer A · Lyon4.8.0current
X200-0156Customer B · Graz4.7.2outdated
X200-0161Customer B · Graz4.7.2outdated
X200-0177Customer C · Brno4.8.0current
X200-0183Customer D · Linz4.6.9outdated

3 machines not on the released version

Rollout 4.8.0 · canary
MachineHardwareVersionRollout
X200-0156WAGO CC1004.7.24.8.0canaryupdated
X200-0161Kontron KBox4.7.24.8.0waitingupdated
X200-0183ctrlX CORE4.6.94.8.0waitingupdated

Auto-rollback once the failure rate passes the threshold

Evidence
  • Version 4.8.0 from the registrysha256 checked
  • Batches approved by an admincanary → rest
  • All machines in the group on 4.8.05 / 5
  • Every change in the audit logimmutable · CSV
Illustrative example — names and values are made up.

Starting point

The problem: recurring engineering does not scale.

Many machine builders sell similar functions again and again as bespoke projects.

  • High engineering effort

    Similar functions are engineered repeatedly for customers and machines.

  • Slow rollouts

    Software distribution, versions and approvals create manual effort.

  • A service business that is hard to scale

    New digital functions can only be rolled out by adding people.

  • Media breaks all the way to billing

    Purchase, deployment and the ERP process are often disconnected.

How it works

Develop once. Sell digitally. Deploy automatically.

Know-how becomes a product: functions such as energy monitoring, condition monitoring or process functions are built once as a standard app and then sold again and again. They are sold through the MARKETPLACE — not a product of its own, but an app store under your brand, built on the FLECS Marketplace and part of the white-label platform. ORCHESTRATE handles the controlled deployment.

  1. 1ControlDevelop the appBuild standard apps with logiccloud CONTROL and publish them in the MARKETPLACE.
  2. 2MarketplaceSell the appThe customer selects and buys the function they need.
  3. 3OrchestrateDeployThe right app version onto the right target system — reproducible and scalable.
  4. 4ERPBillAfter a successful deployment, the transaction is handed over to the ERP.

The products behind it.

  • logiccloud CONTROL — know-how becomes a product

    Control logic, HMI and connectivity become one Automation App: developed once, versioned and then sold again and again.

  • logiccloud ORCHESTRATE — sales become deployment

    One deployment process from the single device to the large-scale rollout: one machine, a hundred machines, edge systems, sites and fleets.

White label

Your platform. Your brand.

Your customers see your product, not ours. Technology by logiccloud, customer experience by you.

  • IDE in your look

    Your organisation’s logo and colours in the logiccloud IDE.

  • HMI themes

    Your own themes for operator interfaces, reusable across all projects.

  • One tenant per customer

    In ORCHESTRATE customers are strictly separated, each tenant with its own branding.

  • Your pricing model

    Upgrades, apps, subscriptions or lifecycle services — you decide what your customers pay for.

logiccloud ORCHESTRATE · machine X200CRA
Provable in the field
  • Which software runs on which machineinventory
  • Vulnerability scan (premium module)2 findings
  • Fixed version built and released4.8.1
  • Update rolled out in stagescanary → all
  • Every change recordedaudit log, CSV export

CRA conformity of the overall product remains the manufacturer’s responsibility.

Illustrative example — names and values are made up.

The installed base

Every delivered machine becomes a channel to the customer

After delivery, the longest part of the software lifecycle begins. With ORCHESTRATE you see which version runs on which machine and bring new functions and security updates there in stages — across vendors.

Impact

The business effect: software becomes recurring revenue.

Standardisation changes more than the engineering — it changes the business model.

  • New digital revenue

    Sell automation apps again and again instead of re-engineering the same functions.

  • Less engineering

    Standardised products reduce customer-specific repeat work.

  • Faster time-to-value

    Purchase and deployment become one continuous process.

  • A scalable service business

    More installed apps and machines without a proportional rise in headcount.

Frequently asked questions from machine builders

Do we have to replace our control hardware?

Not necessarily. CONTROL runs on edge devices from many vendors, such as WAGO, Bosch Rexroth (ctrlX) or Phoenix Contact (PLCnext). And ORCHESTRATE also distributes software not built with CONTROL to your existing edge systems.

Can our customers see the platform under our brand?

Yes, as far as is documented today: logo and colours in the logiccloud IDE, your own HMI themes, and in ORCHESTRATE a separate tenant with its own branding for each customer.

What does this have to do with the Cyber Resilience Act?

The CRA requires you to deliver and prove security updates for the whole support period. The same infrastructure you use to sell and roll out new functions also delivers these updates — with a log of every change.

How do we get started?

With one machine function and one machine series. In the demo we show you the path using your example — from the standard app to the rollout on delivered machines.