dashboarding:dashboarding
This is an old revision of the document!
When designing a dashboard, there are multiple things to consider:
- Reporting Method
- Are calculations required?
- Does data need to be stored?
This Implementation Table provides details on a variety of methods that could be used when working towards building dashboards.
For Calculations
| Method | Scale Limit | Responsibility for Scaling | Possible Complexity | Ease of Replication | Experience Required | IP Protection | Effort to create single dashboard | Effort to create many dashboards |
|---|---|---|---|---|---|---|---|---|
| Templated Script Tags | ASC Server | Intelligent Plant | Low (Orchestrated) | Upload Instances (Easy) | Basic Configuration (Select Tags) | Tags can be seen by client admin, new instances can be created by admin | Low | Low (import) |
| Custom Script Tags | ASC Server & Code Efficiency | Developer | Low (Orchestrated) | Developer Responsible | Basic Code (Scripting) | Code can be seen and copied/modified by admin | Low | High (Up To Developer) |
| Custom Script Tags With DLL | ASC Server & Code Efficiency | Developer | Low (Orchestrated) | Developer Responsible | Medium Code (Compilation/Linking) | DLL code can be obfuscated but decompilation possible. | Low | High (Up To Developer) |
| Jupyter Hub | Bandwidth & Capacity Of Server Instance | Developer | Medium (Manually Run) | Developer Responsible | Basic Python | Scripts are stored on intelligent plant server - could be accessed by someone if they broke contract. | Medium | High (Up To Developer) |
| App Implementation (Ext. Host) | Bandwidth & Server Host & Code Efficiency | Developer | High (Fully Open) | Developer Responsible | Advanced Coding | No one else can possibly see how your app does something, but they could attempt to replicate results through reverse engineering | Depends On App | Depends On App |
| App Implementation (Local Install) | Server Host & Code Efficiency | Developer | High (Fully Open) | Developer Responsible | Advanced Coding | A local install would mean anyone with access to the client host could decompile or attempt to reuse code. | Depends On App | Depends On App |
| Power Automate | Bandwidth & Azure Limits On Data, Executions Etc.. | Developer | Very Low (Orchestrated, Restricted) | Developer Responsible | Drag And Drop | Depends on sharing level | Low |
For Displays
| Method | Shareable with Users | Real-time Updates | Embeddable | User Configurable |
|---|---|---|---|---|
| PnID | Yes | Yes | Yes | Yes |
| Power BI | Yes | No | No | Yes |
| Trend | Yes | Yes | Yes | Yes |
| Jupyter Hub | No, this must be run by the developer, but when it works then it could be used as start of app | No | No(Developer Only) | No |
| New App | Developer Responsible | Developer Responsible | Developer Responsible | Developer Responsible |
For Storage
| Storage of Data | Write-ability |
|---|---|
| Client Historian | Unlikely |
| IP Hist | Yes |
| Alarm Analysis | Yes |
dashboarding/dashboarding.1645389621.txt.gz · Last modified: 2022/02/20 20:40 by su