Topics started by John Smale

3 Posts

John Smale
John SmaleObserver

Assets - Centralise / Globalise 'Custom Field' ManagementDiscussion ongoing

Hi everyone!Long time listener, first time idea poster!I had an idea about for the Assets feature. I apologise if I have overlooked something here but it would be great if we could centralise / globalise Asset’s Custom Fields Current Approach My understanding is that custom fields are only able to be defined at the individual each asset type. This means users may knowingly or unknowingly create duplicate custom fields for the same attribute multiple asset type (e.g Calibration Dates) Impact Cause the asset register view column selection to be ‘bloated’ Cause duplication and inconsistent reporting + data exports Feature RequestProvide a centralised area for users to manage ‘global’ custom fields to help with standardisation + data validation + minimise duplications  Enabling users to assign custom fields to required asset types (via matrix or dropdown tick box) Whilst I recognise there is a bulk upload engine which is awesome, consider providing other field types (choice, look up) to he

6
Duncan Heuer
SafetyCulture Crew
2 months ago
John Smale
John SmaleObserver

Separate Inspection Status from Archived StatusNew

Ideas SC consider separating “Inspection Status” and “Archived” status as from my perspective these are represent different things. Inspection Status - If inspection has been completed or not and should be included in organisations dataset  Archived Status - If inspection (whether in progress/abandoned or completed) has been archived in accordance with records management policy and / or to reduce amount of records being synced to mobile devices BenefitI think this will really help support integrity of reporting in Analytics or external BI tools, especially when undertaking long term summary or trend analysis (e.g. datasets greater than 30 days and up to 5 years) For example - I want all completed inspections (including those in archive) to remain in the dataset visible in Analytics and Power BI.  However, if we want to report on all completed inspections, we have to select both “Archived” and “Completed” status to get the full dataset. However, if we leave the inspection reports in com

1
Paddy Bell
SafetyCulture Crew
10 months ago
John Smale
John SmaleObserver

Support Centralised Registers/Tables at Org Level for Other 'Entities' (Risks, Hazards, Objectives, Aspects)New

Hi AllWhilst I was commenting on another post about having a table function inside inspection templates, it got me thinking about the benefits of being able to maintain ‘registers’ at the organisational level which could be used for anything e.g. Hazards/Risks Contextual Issues  Product Specifications  Objectives & Targets Aspects & ImpactsFeatures that would be important to get the most out Org Level Registers or Lists like this include:Ability to associate with parent or child elements of Site Hierarchy  Numbering / Unique ID for each row Data validation support for fields (global response/look ups) Custom Matrices (Likelihood/Probability + Consequence / Impact)  Formula and Calculated Fields + Conditional formatting Permissions (Site / Group)  Support for Attachments Ability to raise or schedule inspections and or assign actions at overall register level or individual ‘row’ level, Ability to develop centralised ‘content library’ for objects that could leverage standardised c

1
Paddy Bell
SafetyCulture Crew
1 year ago
Terms & ConditionsCookie settings