I’m designing my first app for work. It will be used by several internal service departments within the company; the first will be maintenance, followed closely by IT. Other departments are pending.
My initial design draft was OK but not very flexible for multi-dept use; then I saw the “Universal” Inspection app by @MultiTech_Visions and thought that it may provide a better and more universal platform to be used by any of our service departments.
I’d like to get some feedback on my revised draft design (see below) and whether or not I’m on the right track or literally barking up the wrong tree.
---------My riff of the Universal App--------
An Entity Group groups similar Entities (tangible or intangible) and is associated with multiple Activities (corrective, preventative, training, procurement, administrative, safety, etc…) These Activities are tailored to the Entity Group through the context of referenced Categories/Sub-Categories, ensuring relevance and applicability.
An Entity, belonging to an Entity Group, is the subject of multiple Work Logs, which document the execution of Work (see below).
The Activity Catalog groups series of Activity Steps/Stages, ordered to define a coherent process/workflow. Steps/Stages may have expected completion times and escalations based on a priority matrix.
Activity Steps/Stages comprise a group of Activity Items/Elements which are required or situational data-points/actions to be completed before moving to the next Step/Stage. An Activity Step/Stage could be the execution of another Activity (e.g., “Diagnostics” or “Procurement” Activity within a “Corrective Action” Activity)
JTOs (Jobs/Tickets/Operations) are instances of Activities; JTOs can be created by users, techs, or via automation depending on the associated Activity. JTOs may have triaged priority which will set the time limits for the Steps/Stages. The triggering of another Activity within a JTO creates a “sub-JTO” assigned to the same/different Tech and may or may not require full completion of the sub-JTO before progressing.
The Work Log reflects the execution of Work, containing records of Work.
Work logs the resource utilization (time & materials) and completed data-points/actions of the instance of Activity Items/Elements within a JTO.
Other apps/tables such as Inventory, Vendors, Users, Techs, etc… would round out the “suite” which is tentatively being named “SOS” (Service Operations Suite).
I apprecaite any suggestions/feedback you can provide.
Thanks!