BDI Cloud is a cloud platform for instrumentation and monitoring programs. It collects readings from the instruments on your site, keeps them in one place, and gives the people responsible for that site a way to see what the data is doing and be told when something changes.
Monitoring programs usually accumulate hardware from several vendors, each with its own portal, export format, and login. BDI Cloud sits above that. You configure a connection to each data source once, and from then on every reading lands in the same project alongside the others, ready to chart, calculate from, and alert on.
What you can do
| Area | What you use it for |
|---|---|
| Overview | The state of a project at a glance: what is reporting, what is not, and what needs attention. |
| Dashboards | Build and share views of your data using graph, profile plot, wind rose, system health, text, and image cards. |
| Pipeline Manager | Add connections, see the devices each one has discovered, and confirm data is arriving. |
| Virtual Devices | Derive new values from readings you already collect, then chart and alert on them like any other metric. |
| Alerts | Get told when a reading crosses a limit, or when a device stops reporting at all. |
| Settings | Manage project configuration, users, and permissions. |
Note: What you see depends on the project you are in and the role you have been given. If something described here is missing from your navigation, your role or your project's configuration may not include it.
How your data gets in
BDI Cloud does not talk to instruments directly. You create a connection for each data source, choosing the integration that matches your hardware and entering the credentials and polling schedule for it. From then on the source is polled on that schedule without further action.
Each connection brings in devices, and each device reports one or more metrics. Those three words are the selection path everywhere in the product: to chart something, calculate from it, or alert on it, you pick a device and then one of its metrics.
Devices register themselves as data arrives rather than being entered by hand. How readings are divided into devices depends on the integration, which is worth understanding early because it is the most common source of confusion for new users. Connections, devices, and metrics covers it.
How projects are organized
Your organization sits at the top. It holds your users, your roles, and every project you run.
Projects are where the work happens. A project usually corresponds to one monitoring engagement: a bridge, a dam, an excavation, a mine site. Each keeps its own data, dashboards, connections, Virtual Devices, alerts, and access controls, and nothing crosses between projects unless someone with the right permissions puts it there.
Access is role-based, which is why your view of a project may not match a colleague's. Projects and access explains how membership and roles combine.
Where to start
If you are new, read Navigating BDI Cloud for the interface and Projects and access for how permissions work.
If you are setting up a project from nothing, the order that gets you to useful data fastest is Pipeline Manager first, then Dashboards, then Alerts. Get data arriving and confirm it looks right before you build views on top of it or configure anything to notify you.
If you are stuck, contact BDI Cloud Support.
Comments
0 comments
Article is closed for comments.