CriticalAssetManagement / CriticalAssetManagement/CAMS-Dashboard
Better Reporting Functions
- Dominant language
- JavaScript
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
There are a range of improvement that could help here. Some of them are direct reporting extracts - we currently just report on the number of links per assets to give an idea of the **most connected assets** but much more could be used by folks wanting to use the tooling.
- Generate a checklist of potentially affected facilities and provide a questionnaire to facilitate the assessment of actual damages, and/or level of disruption to continuity.
- Generate list of affected assets that have not responded to the messages by a certain cut-off time period, appended to a list of contacts, so that the person in charge can check over the phone.
- A better report function to make it possible to compare and contrast risk levels between different assets and output the results. Meteorological information.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing reporting function that currently reports the number of links per asset. Clarify which of the requested outputs—facility checklists, non-responsive asset contacts, risk comparisons, or meteorological information—is in scope; done means the agreed report outputs are available in the dashboard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- analytics, data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100