Skip to content
Orchestron.

Business outcomes

  • Four ways we transform organisations with AI

Systems and teams

  • Product modernisation
  • The platforms we run in production

Operations

All services
  • Product and process teams
  • Build. Operate. Transfer.
Results. AI in production Six deployments and the outcome each one produced.

Sectors

All sectors
  • Life sciences Patient facing services, records integration, applied AI
  • Manufacturing CAD, CAM, PLM, MES, and digital twin
  • Energy and utilities Smart grids, point of charge, SCADA, asset management
  • Banking and financial services Regulatory compliance, digital insurance, payment platforms
  • Transportation and logistics Customer service and shipment operations
Copilot. Customer service copilot Case study in logistics

Portfolio

  • Products and ventures Products launched with partners
  • Customer service copilot Case study in logistics
  • Document classification Case study in commercial finance
  • Predictive maintenance Case study in heavy industrial
Ventures. Products and ventures Products launched with partners

Working with us

  • How we work Models, routes, and the path to a working pilot
  • Build. Operate. Transfer. The whitepaper on ownership without permanent dependency
  • Whitepapers Expert Outlook, with the full papers on request
  • Direct and partner delivery For clients directly, and inside consulting and integrator programmes
  • How an engagement starts Three steps from first contact to a clear decision
  • Collaboration models Project based, product and process team, delivery organisation
  • Routes to work together Vendor, technology partner, go to market partner
BOT. Build. Operate. Transfer. We build a dedicated unit, run it to full performance, then transfer it to you.

Orchestron.

  • Corporate overview Where we deliver and how the team is built
  • Offices Tirana, Zagreb, Chicago, and Riyadh
  • Governance How the firm is directed and held to account
  • Careers Open roles across our technology practices
  • Security and data protection How we handle confidentiality, access, and client data
Careers. Careers Tell us what you build. A short description of your work is enough.
Contact

Whitepaper

Edge AI: when to run AI on the device

Artificial intelligence · Summary

On this page

  • What edge AI is
  • When to use it
  • What makes it possible
  • Privacy and security
  • How to operate it
  • Full whitepaper

What edge AI is

Edge AI runs a model on a device near the data, not on a distant cloud server. The device can be a sensor, a camera, a vehicle, or an industrial controller. Edge AI is not a replacement for the cloud. Many systems use both.

When to use it

Use edge AI if one or more of these conditions apply:

  • Response time: The system must act before a cloud server can answer.
  • Connection: The site has a slow connection, or the connection can stop.
  • Data volume: Devices make more data than you can send at an acceptable cost.
  • Data location: Sensitive data must stay on the site.

Use the cloud if the model is large, if you must change it frequently, or if it needs data from many sites. A plant can detect a machine fault on the device and send a summary to the cloud for analysis of the full fleet.

What makes it possible

Devices now have special chips for AI, such as the Apple Neural Engine, Google Edge TPU, and Qualcomm Hexagon. These chips run models with less power than general processors.

Teams can also make models smaller with quantisation, pruning, and knowledge distillation. These methods can decrease accuracy. Test the smaller model on real data from the site before you release it.

Privacy and security

Local processing can decrease the personal data that you send to other systems. It does not remove your legal obligations. If a camera processes images of people on the device, data protection law such as the GDPR can still apply.

Devices also have a different risk. People can get physical access to them. Protect the model, the data, and the update procedure on each device.

How to operate it

One model on one device is a test. A fleet of devices is an operation. Plan these items before you start:

  • Safe updates for each device, with a procedure to go back to the previous version
  • Regular checks of model quality when the site conditions change
  • Clear responsibility for faults at each site
  • Support with an agreed service level

These items are the reason why edge AI needs consulting, engineering, and operations together.

Get the full whitepaper

This page is a summary. Contact us to ask for the full whitepaper.

Ask for the full whitepaper

← All whitepapers · Discuss an opportunity

Orchestron.

Consulting, engineering, and managed operations for scaleups and enterprises.

Main delivery in Tirana. Representation in Zagreb, Chicago, and Riyadh.

Site

  • Services
  • Industries
  • How we work
  • Whitepapers
  • Corporate overview
  • Products and ventures
  • Careers
  • Contact

Legal

  • Privacy Policy
  • Cookie Notice
  • Terms of Use
  • Security & Data Protection
  • Company Information

© Orchestronlab d.o.o. All rights reserved.

This website does not use cookies for analytics or advertising. Read our Cookie Notice