Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / CriticalAssetManagement/CAMS issues and pull requests

#163 - Issues Moved to CAMS-Dashboard [Link in Comment]

Issue - State: open - Opened by luke-feeney about 2 years ago

#161 - Asset owners for the cascading failure chain

Issue - State: closed - Opened by OJ423 over 2 years ago
Labels: enhancement

#160 - Contact owners don't display for assets with no dependencies

Issue - State: closed - Opened by OJ423 over 2 years ago
Labels: enhancement

#159 - Load asset issues

Issue - State: closed - Opened by OJ423 over 2 years ago
Labels: enhancement

#158 - Asset List Problems

Issue - State: closed - Opened by OJ423 over 2 years ago
Labels: enhancement

#157 - People Form Field Order

Issue - State: closed - Opened by OJ423 over 2 years ago
Labels: enhancement

#156 - People vs Owners - Are owners necessary?

Issue - State: closed - Opened by OJ423 over 2 years ago
Labels: Discussion

#155 - Unable to edit existing assets: Asset history, asset update history, applicable events

Issue - State: closed - Opened by OJ423 over 2 years ago - 4 comments
Labels: bug

#154 - Dropdown menu contrast needs fixing

Issue - State: closed - Opened by OJ423 over 2 years ago
Labels: invalid

#153 - Adding owner to an asset is not user friendly

Issue - State: closed - Opened by OJ423 over 2 years ago
Labels: invalid

#152 - Updating asset errors

Issue - State: closed - Opened by OJ423 over 2 years ago - 1 comment
Labels: bug

#151 - Unable to add owner to an existing asset

Issue - State: closed - Opened by OJ423 over 2 years ago - 1 comment
Labels: bug

#150 - Add a field or hazard to monitor depreciation of an asset

Issue - State: closed - Opened by KittyJose over 2 years ago

#149 - Add a checklist tab

Issue - State: closed - Opened by KittyJose over 2 years ago

#148 - Print options with correct setView (zoomed position) and also print the links effectively

Issue - State: closed - Opened by KittyJose over 2 years ago

#147 - use Bezeir curve logic to make asset links curved

Issue - State: closed - Opened by KittyJose over 2 years ago

#146 - Stylize the map vector layers and eventually use the layer as a sidebar/ control tool bar

Issue - State: closed - Opened by KittyJose over 2 years ago

#145 - Download CSV file with owner contact numbers

Issue - State: closed - Opened by KittyJose over 2 years ago

#144 - Critical Warning Sytems

Issue - State: closed - Opened by luke-feeney over 2 years ago

#115 - The tool should meet cybersecurity concerns - It should comply with Dominica’s new data protection law (tbd).

Issue - State: closed - Opened by sreyac almost 3 years ago - 2 comments
Labels: question, sustainability

#114 - The tool should meet cybersecurity concerns - It should enable the location of assets designated by their owners to be blurred from view – or status (with dependencies up and downstream) to be reported but exact location not shown.

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, help wanted, sustainability, Discussion

#113 - The tool should meet cybersecurity concerns - It should enable security and confidentiality protections to [SOC2] standard, and should minimize as far as possible exposure to ransomware and other intrusive threats.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: sustainability

#112 - NFR: The tool will have a pre-set limit on users and data volumes enabled and supported for free in the cloud version, and free enablement/support will be for a prescribed period of time.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: help wanted, question

#111 - The tool should meet cybersecurity concerns - It should provide role-based access controls.

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, sustainability

#110 - NFR: The tool should be accompanied [format tbd] by Training, tutorials.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: documentation, help wanted, sustainability

#109 - NFR: The tool should be accompanied [format tbd] by Guidance on usage, risk assessment, formation of action plans;

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: documentation, help wanted, sustainability

#108 - NFR: If possible, both the cloud and on-premises variants should offer an option for ongoing support [funding tbd].

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, help wanted, sustainability

#107 - NFR: The cloud variant should Have an availability of 99.9%.

Issue - State: closed - Opened by sreyac almost 3 years ago - 2 comments
Labels: enhancement

#106 - NFR: The cloud variant should - Be hosted in multiple territories to minimize data residency issues.

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: help wanted, sustainability

#105 - NFR: The tool should support access via - Should be available for cloud or standalone/on-premises usage.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: sustainability

#104 - NFR: The tool should support access via - Tablet/smart-phone based app

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, sustainability

#103 - NFR: The tool should support access via - Web page

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: sustainability

#102 - NFR: Maximize the use of/consistency with open data and process standards - Data standards and taxonomies should be fully open and published.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: documentation, sustainability

#101 - NFR: Maximize the use of/consistency with open data and process standards - Use of spatial web standards for asset referencing, cross-linked to the user’s own reference(s)

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, sustainability, Discussion

#100 - Asset Data: The Tool should prompt at defined intervals for validation and/or updates of dynamic data items, including but not limited to names and contact details of key skills.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: enhancement, help wanted, sustainability

#99 - Asset Data: The Tool should report on the age and completeness of data – with an option for users to override if a given field or asset class does not apply.

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, good first issue, sustainability

#98 - Asset Data: Drill downs into asset data as applicable.

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, sustainability

#97 - Asset Data: Individual failure chains and which asset can trigger the failure chain it fails, or in which it may be located (using hazard or criticality view)

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, help wanted, sustainability

#96 - Asset Data: Asset linkages (network view – using hazard view or criticality view as desired by the user)

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, sustainability

#95 - Asset Data: Asset criticality (High/Medium/Low)

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, good first issue, sustainability, Discussion

#94 - Represent Asset Data: Key standing data about each asset

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, good first issue, sustainability

#93 - Asset Data: Individual assets and hazards faced (High/Medium/Low)

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, good first issue, sustainability, Discussion

#92 - Emergency Response: Enable SMS/chat based communications between users.

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, help wanted, sustainability

#91 - Emergency Response: Enable workflow management for each SOP and recommendation (response to event), so execution can be monitored as required.

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: documentation, enhancement, help wanted, question, sustainability

#90 - Emergency Response: Generate context-aware action recommendations either on a rules basis, or (preferably) using AI to generate recommendations.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: documentation, enhancement, help wanted, question, sustainability

#89 - Emergency Response: In aftermath of storms, location of designated individuals (maybe via cellphone tracking) – to be turned off in normal circumstances – N (phone tracker will supply Lat/Long)

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, help wanted

#88 - Emergency Response: Send alerts when assets are flagged as vulnerable to damage

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: enhancement, help wanted, sustainability

#87 - Emergency Response: Make all standing data about critical assets available for export to other emergency management tools via an API.

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, help wanted, sustainability

#86 - Emergency Response: Tool could generate summary reports (.pdf. or similar) for public consumption - T

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: enhancement, help wanted, sustainability

#85 - Asset owners should be able to flag the status on specific assets after an event, and estimated service restoration time – C/T

Issue - State: closed - Opened by sreyac almost 3 years ago - 2 comments
Labels: enhancement, good first issue, sustainability

#84 - Asset owners should be able to flag asset status: That specific assets/all assets for which they are responsible are likely to be damaged in an event, or will have to be shut down until the event is past – C/T

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: enhancement, good first issue, sustainability

#83 - Asset Risk Mitigation: Enable inclusion of supporting documentation as reference documentation.

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: documentation, enhancement, sustainability

#82 - Evaluate contingency plans to provide resource through other means (eg. distributed power systems, RE options).

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, help wanted, question, sustainability

#81 - Asset Risk Mitigation: Evaluate other operating dependencies that assets may have (fuel, electricity etc).

Issue - State: closed - Opened by sreyac almost 3 years ago - 2 comments
Labels: enhancement, help wanted, question, sustainability

#80 - Asset Risk Mitigation: Evaluate whether trained operators and key skills are available, and how to ensure their continued availability.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: help wanted, question, sustainability

#79 - Asset Risk Mitigation: Model the costs and benefits of different asset replacement strategies.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: enhancement, help wanted, question, sustainability

#78 - Model the cost and benefit of different potential mitigation measures (assume these are assessed and calculated outside the tool) and show the effects on impact and criticality, and on associated failure chains.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: enhancement, help wanted, question, sustainability

#77 - Mitigating Asset Risk: Enable a full failure modes effects and criticality analysis (FMECA) on each asset.

Issue - State: closed - Opened by sreyac almost 3 years ago
Labels: enhancement, help wanted, question, sustainability

#76 - Enable calculation of depreciation and reserve rates (of assets), to guide investment in replacement.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: enhancement

#75 - Mitigating Asset Risk - Capture asset deterioration and rate, along with remaining asset life.

Issue - State: closed - Opened by sreyac almost 3 years ago - 1 comment
Labels: enhancement, sustainability

#74 - Asset Risk Mitigation: The tool should provide a library of key considerations for the hardening and/or replacement of different classes of asset. This should be updatable by the GE.

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, help wanted, question, sustainability

#73 - Asset Risk Mitigation: Include supporting documentation

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: question, sustainability

#72 - Asset Risk Mitigation: Enable assessment of the cost and benefit of different mitigation measures on the failure chain as a whole, and assemble suggested spending profiles.

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, help wanted, question, sustainability

#71 - Asset Risk Mitigation: Enable calculation (or input from external sources) of financial and economic impacts of given failure chains.

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, question, sustainability

#70 - Asset Risk Mitigation: Enable Mathematical modeling of probabilities of specific failure chains occurring in each scenario (different disasters & asset failures with associated impacts).

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, help wanted, question, sustainability

#69 - Asset Risk Mitigation: Include supporting documentation.

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, question, sustainability

#68 - Asset Risk Mitigation: Assessment of criticality of asset loss or damage.

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, sustainability

#67 - Asset Risk Mitigation: Construction of scenario content and assignment of probabilities

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, help wanted, sustainability

#66 - Non-Functional Requirement: The tool should provide open, published APIs or similar to provide data to Third parties, eg. asset owners, public or community organizations, investors or development banks

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, sustainability

#65 - Non-Functional Requirement: The tool should provide open, published APIs or similar to provide data to Asset management systems;

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, sustainability

#64 - Non-Functional Requirement: The tool should provide open, published APIs or similar to provide data to Digital twins, in effect as a layer in the “twin”, where this technology is in use;

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, sustainability

#63 - Non-Functional Requirement: The tool should provide open, published APIs or similar to provide data to Emergency management systems - input risks and so allow responses and/or SOPs to be generated;

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, help wanted, sustainability

#62 - Non-Functional Requirement: The tool should be able to consume data Via data ingestion tools from other sources, eg. from citizens/asset users.

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, help wanted, sustainability

#61 - Non-Functional Requirement: The tool should be able to consume data from other systems Via commonly found APIs provided by asset management systems to allow capture of asset reference data (where available);

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, help wanted, sustainability

#60 - Non-Functional Requirement: The tool should be able to consume data from other systems via commonly found APIs provided by GIS systems, to provide base visualization and spatial reference layer;

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, sustainability, Discussion

#59 - Create a Color coded view of asset criticality capturing High / Medium / Low criticality

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, good first issue, sustainability, Discussion

#58 - Capture the Likely duration of each impact (of a hazard event) where applicable – N

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: enhancement, sustainability

#57 - Capture consequences of projected loss or damage: Loss of life, livelihood, economic, social fabric/community access, environmental damage and so on – C/T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, sustainability, Discussion

#56 - Create Documentation to Guide Users of CAMS

Issue - State: closed - Opened by luke-feeney almost 3 years ago
Labels: documentation

#55 - Documentation and help screens on the tool, to advise on how to define risk and damage levels. Helpful if taken from GE's documentation on same, if available – T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: documentation, help wanted, question, sustainability

#54 - For each asset, a total risk “picture” for the combination of hazard probability and likelihood of damage once mitigation measures are factored in. Could just be a red/yellow/green scale - more red = more risk – C/N

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, sustainability

#53 - For each hazard - Capture mitigation measures that have been taken, and when, and their likely benefit - T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, question, sustainability, Discussion

#52 - For each level of hazard severity, capture the likely direct impacts on the asset (for example, “High impact” – catastrophic destruction; “Medium impact” - substantial loss of service and consequent disruption for months; “Low impact”– disruption limited to a few hours only – T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, sustainability, Discussion

#51 - Capture 3 levels of hazard severity as high/medium/low and capture probabilities of asset damage (H/M/L). Enable values for the three levels to be assigned by the user

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, sustainability, Discussion

#50 - Other risks not noted prior that may disable, damage or destroy an asset - T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, question, sustainability, Discussion

#49 - Capture links to other assets - in event of a hazard - failure chains - Captutre Links to other assets

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, question, sustainability

#48 - Tool should capture Security events, including terrorism, that could disable, damage, or destroy each asset – C

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, good first issue, Discussion

#47 - Capture Manmade events that pose a risk to each asset (eg., power failure, risk of damage from explosion from neighboring plant) - C

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, good first issue, Discussion

#46 - Factors in the asset’s location (eg, “located on coast”, or “located in landslide zone”) that pose a risk in the event of a hazard – C/T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, good first issue, question, sustainability, Discussion

#45 - Tool must capture any hazards that could directly disable, damage or destroy the asset - Natural events – C/T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, good first issue, sustainability

#44 - Asset Inventory - Asset Data: Service level agreements, if any, on assets not covered by a disaster optout - T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: documentation, help wanted, question

#43 - Construction standards embodied in the asset, if known – C/T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: documentation, enhancement, question

#42 - Estimated remaining asset life – N

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, good first issue, question, sustainability, Discussion

#41 - Asset deterioration potential and rate (if known) – T/N

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, question, sustainability, Discussion

#40 - Asset operating history – notable adverse events (eg. flood damage, earthquake damage, accidents) – T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement

#39 - Nature and date of significant upgrades, if any – T/N

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, sustainability

#38 - Asset age/ year of first operation – N

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, good first issue, sustainability

#37 - Asset economic risk owner (who is responsible for mitigating impact of loss of the asset?) and contact details – T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement

#36 - Asset financing risk owner (who is responsible for cost of a replacement?) and contact details – T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement

#35 - Other asset operating dependencies (fuel, electricity, etc) – C/T

Issue - State: closed - Opened by luke-feeney almost 3 years ago - 1 comment
Labels: enhancement, question, sustainability, Discussion