--- title: "Automation as software for machine builders | logiccloud" description: "For machine and equipment builders: build functions as software, roll them out across the installed base and sell them as upgrades, apps or services." url: https://logiccloud.com/en/solutions/machine-builders/ language: en-GB --- 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. [Request a demo](https://logiccloud.com/en/demo/) [Discuss your product business](https://logiccloud.com/en/contact/) logiccloud ORCHESTRATE live Installed base · X200 / Europe Machine Customer · site Version State X200-0142 Customer A · Lyon 4.8.0 current X200-0156 Customer B · Graz 4.7.2 outdated X200-0161 Customer B · Graz 4.7.2 outdated X200-0177 Customer C · Brno 4.8.0 current X200-0183 Customer D · Linz 4.6.9 outdated 3 machines not on the released version Rollout 4.8.0 · canary Machine Hardware Version Rollout X200-0156 WAGO CC100 4.7.2 4.8.0 canary updated X200-0161 Kontron KBox 4.7.2 4.8.0 waiting updated X200-0183 ctrlX CORE 4.6.9 4.8.0 waiting updated Auto-rollback once the failure rate passes the threshold Evidence - Version 4.8.0 from the registry sha256 checked - Batches approved by an admin canary → rest - All machines in the group on 4.8.0 5 / 5 - Every change in the audit log immutable · 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. 1 Control Develop the app Build standard apps with logiccloud CONTROL and publish them in the MARKETPLACE. 2. 2 Marketplace Sell the app The customer selects and buys the function they need. 3. 3 Orchestrate Deploy The right app version onto the right target system — reproducible and scalable. 4. 4 ERP Bill After 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. [Explore CONTROL](https://logiccloud.com/en/products/control/) - ### 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. [Explore ORCHESTRATE](https://logiccloud.com/en/products/orchestrate/) 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 X200 CRA Provable in the field - Which software runs on which machine inventory - Vulnerability scan (premium module) 2 findings - Fixed version built and released 4.8.1 - Update rolled out in stages canary → all - Every change recorded audit 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. [Software updates in the field](https://logiccloud.com/en/solutions/field-software-updates/) [CRA for machine builders](https://logiccloud.com/en/cra/) 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. ## Discuss your Automation-as-a-Product business. Bring one of your machine functions along — we will show you the path from standard app to recurring revenue. [Request a demo](https://logiccloud.com/en/demo/) [Get the CRA checklist](https://logiccloud.com/en/cra/checklist/)