Skip to content
onagero

Analyzing proALPHA data: Onagero alongside your ERP

proALPHA is widely used among mid-sized industrial companies and now offers its own AI platform. When is Onagero still worthwhile? When the workflow needs data from several systems and should run as a tool of its own in your environment.

  • Read only
  • No change to your ERP
  • Connection included in the pilot
  • GDPR ready

In short

Onagero reads proALPHA data through a route your IT releases, usually read-only database access or an export, and combines it with other sources such as BDE, CAQ or Excel. If your workflow lies entirely within proALPHA, check the vendor's offering first; we will tell you that in the demo as well.

Possible ways to the data

Which one fits for you we clarify with your IT before the contract.

Read-only database access

A database user that may only read, on the tables or views the workflow needs.

Export

A scheduled export, if database access is not wanted.

Existing data store

Where proALPHA data already flows into a data warehouse, Onagero reads from there.

What your IT provides

  • read-only access or a scheduled export
  • a short alignment with your proALPHA contact on the relevant tables
  • a server or virtual machine in your network

Good to know

proALPHA markets its own Industrial AI Platform for ERP, CRM and MES data. Onagero complements it: we build and operate a specific tool with you, on your server, including across systems from different vendors.

Turning proALPHA data into a foundation to build on

What stays with you, what Onagero makes of it, and what the language model gets to see.

Onagero creates an analysis copy of the needed data on your server and describes it in the data map: the meaning of each column, relationships, origin and review status. Your people build on that.

In development, the copy holds no personal data. Released applications read from a live view only what their roles allow.

The data path at Onagero Your systems feed, over a read only connection, into a masked analysis copy on your server. Your people build internal tools from it with Onagero. Only the released, masked parts of a request go to the model provider. Your server, your network ERP BDE and MES Excel, files Analysis copyNames masked OnageroYour people build Internal toolwith roles per person Live view, only what thetool may read Model provider, external What goes out is only what a request needs: released and masked. The databasestays in your building. The data path at Onagero, top to bottom Your server, your network ERP BDE, MES Excel Analysis copyNames masked OnageroYour people build Live view, released Internal toolwith roles per person Model provider, external Only what a request needs, released and masked. The database never leaves your building.
The path of your data: platform, analysis copy and tools on your server; only masked parts of single requests go to the language model. Data security in detail

Questions about connecting to proALPHA

Why not use the proALPHA AI platform right away?

If your workflow lies entirely within proALPHA and your partner implements it, that can be the shorter route. Onagero is stronger when several systems are involved or when a tool of your own should be created that we operate with you.

Does Onagero interfere with our proALPHA update?

Onagero reads. If tables change in an update, it shows up in operation and is adjusted; that is part of the maintenance covered by the monthly price.

Does Onagero write data back?

No. Write access to the ERP is ruled out.

Do we need our proALPHA partner?

For a short alignment on tables and access, often yes. It is not a project.

Which problem would
your team solve first?

Show us a real process. We will show you how it could look with Onagero.

Book a demo →

Check first whether a pilot fits: fit check in 2 minutes →