SOFTWARE · AUTOMATION · DATA
Solution examples
for industry and business.
A business application, production data or a machine that needs to connect to a new system. Explore how software, automation, data and engineering can work together in your environment.
Below are typical use scenarios and possible approaches.
SOFTWARE DEVELOPMENT
A business application instead of scattered spreadsheets.
Custom software development for companies whose actual workflows are not covered by an off-the-shelf product.
- Business process
- Data and rules
- Custom application
- Challenge
- Orders, work instructions and records are spread across spreadsheets and email. The same information is entered repeatedly, and colleagues struggle to identify the correct version.
- Approach
- We define users, data and process steps first. Then we build a business or desktop application with appropriate permissions, validation and a record of changes. Backend development and API integration connect the application to existing information systems.
- Expected outcome
- A shared view of work, less duplicate entry and an application that follows your process. The initial scope can cover one important task and expand after practical evaluation.
WEB DEVELOPMENT
A web portal for customers or your internal team.
Custom web application development that makes information and tasks accessible through a browser.
- Existing systems
- Secure access
- Web portal
- Challenge
- Customers call or email to check their order status. Employees need access from several locations, but the current tool is only available on a particular computer.
- Approach
- We design a web portal, internal tool or dashboard with a clear user interface. We connect it to your backend, database or API and implement authentication and user permissions. Web development also includes layouts suitable for phones and tablets.
- Expected outcome
- Customers or colleagues can check information and complete agreed steps themselves. The application can run on your infrastructure or in the cloud, according to access and maintenance requirements.
INDUSTRIAL SOFTWARE AND DATA
Production data that supports everyday decisions.
Production data acquisition, industrial software development and MES integration for visibility into machines and processes.
- Machines and measurements
- Acquisition and database
- Production overview
- Challenge
- Information stays in controllers, local files or separate manufacturing systems. Reports are assembled manually, and it is difficult to connect measurements, orders and machine states when an event occurs.
- Approach
- We define data sources, timestamps and the required acquisition frequency. We connect PLCs, SCADA or MES systems to an industrial database and application. Data pipelines include quality checks, interruption handling and process context. Reporting, time-series data or traceability support can be added where needed.
- Expected outcome
- A clearer view of production status and event history. Industrial data provides a basis for process monitoring, analytics and manufacturing digitalization, without manually assembling each report.
INDUSTRIAL AUTOMATION AND INTEGRATION
Machines and information systems speaking the same language.
PLC integration, SCADA connectivity and OT/IT integration between physical processes and business applications.
- PLC and SCADA
- Communication protocols
- MES and applications
- Challenge
- A machine runs independently while operators enter order details by hand. Production and business systems use different interfaces, preventing reliable data exchange.
- Approach
- We review controllers, communication options and process constraints. PLC programming on Siemens, Allen-Bradley or GE platforms can be combined with HMI/SCADA and higher-level system integration. We connect devices and systems using suitable communication protocols based on supported interfaces and process requirements. A communication gateway can separate the OT and IT environments where necessary.
- Expected outcome
- An agreed data flow between machine and application, with defined error handling. Integration can transfer machine states, verified production data or orders; permitted changes to the process are specified before implementation.
DATA, AI AND EDGE
Recognition and data processing close to the device.
Machine vision, OCR and edge computing where local processing, response times or connectivity matter.
- Image or sensor
- Edge processing
- Data and review
- Challenge
- Information exists as an image, label or document and someone transcribes it manually. A device operates with limited connectivity, or sending every image to the cloud is impractical.
- Approach
- A prototype checks image acquisition, lighting, input quality and recognition. We connect OCR or machine vision to an application, on an edge device such as NVIDIA Jetson where appropriate. AI is used when it helps solve the specific problem; uncertain results can be passed to a person for review.
- Expected outcome
- A proposed solution evaluated on your data, with its limitations defined. Local processing can support label reading, assisted inspection or anomaly detection before a wider rollout is considered.
ENGINEERING AND MODERNIZATION
New functionality for equipment that still works well.
Legacy system modernization without unnecessarily replacing an entire machine or application.
- Existing equipment
- Diagnostics and upgrade
- New functionality
- Challenge
- Equipment still performs its main task, but lacks a modern interface, adequate data acquisition or connectivity to a newer system. Documentation may be incomplete and the cause of faults unclear.
- Approach
- We start with diagnostics and a review of architecture and communication options. We assess which parts can be retained and where software upgrades, middleware, measurements or a prototype are needed. Changes are planned incrementally, with testing and an agreed rollback approach.
- Expected outcome
- A useful extension to existing equipment with a clearly defined scope. A new solution does not always require a new system: a connection, an additional application or better data access may be enough.
CONNECTED ENGINEERING
From machine to user interface.
CELEON is a technology and engineering business based in Slovenia. Technologies are chosen according to your process, existing equipment and deployment requirements.
Software
Custom applications, web interfaces, backend systems and APIs. Connecting business rules to a useful tool for everyday work.
Automation
PLC, HMI/SCADA, MES and industrial communication. Understanding machines and processes provides the foundation for higher-level integration.
Data
Acquisition, databases, time-series data and reporting. Data quality and context first, followed by analytics and decision support.
Engineering and edge
Architecture, diagnostics, prototypes and local processing. Deployment into your existing environment, on your infrastructure or in the cloud.
Before we start a project.
Can you connect existing machines without replacing the controller?
Often, but it depends on the available interfaces, documentation and equipment condition. We first check communication options. If a direct connection is not feasible, we assess a gateway or additional data acquisition.
What is the difference between a web and an industrial application?
A web application describes browser-based access; an industrial application describes its purpose. A solution can be both, such as a web dashboard displaying production data from a MES system or PLC.
Does the solution have to run in the cloud?
No. Software can be designed for your infrastructure, the cloud or a local edge device. The choice depends on connectivity, access, data sensitivity and maintenance requirements.
Can we start with a smaller prototype?
Yes. Where requirements are unclear or technical risks exist, a limited prototype makes sense: one machine, one data flow or one task. We can evaluate feasibility before defining a wider rollout.
What do you need for an initial conversation?
A brief description of the problem, the project goal and information about existing systems. Current workflows, controller types, available interfaces and constraints are helpful. If documentation is missing, we start with a basic review.
Facing a similar challenge?
Tell us what needs to work, what you already have and where things get stuck. Together we can define a sensible first step.