Appendix C — Module & Master Mapping¶

Reference Document | Audience: Admin, Owner

Overview¶

This appendix provides a two-way mapping between operational modules and master data entities. Use it to understand which master data must be set up before using a module, and which modules are affected when master data changes.

Module → Master Data (What each module needs)¶

Module	Required Master Data
Asset Management	Asset Categories, Asset Statuses, Asset Conditions, Locations, Departments, Manufacturers, Models, Suppliers, Users
Asset Transfer	Locations, Departments, Users, Vehicles
Asset Disposal	Asset Categories, Locations, Departments
Audit Management	Asset Categories, Asset Statuses, Asset Conditions, Locations, Departments, Users
Schedule Management	Activity Types, Locations, User Groups, Cost Templates, Checklist Templates, Assets, Vehicles
Depreciation	Asset Categories (for defaults), Assets (financial info)
Workflow Management	Roles, Users
RFID Management	Locations, Reader Types, Manufacturers, Models, Floor Plans
Floor Plans	Locations, Assets (for positioning)
Bulk Upload	All master data (varies by entity type being uploaded)
User Management	Departments, Locations, Roles
Reports	Asset Categories, Asset Statuses, Locations, Departments, Activity Types, User Groups

Master Data → Modules (Where each master is used)¶

Master Data	Modules That Use It
Asset Categories	Asset Management, Asset Disposal, Audit Management, Depreciation, Bulk Upload, Reports, Supplier Configuration, Role Access Control
Asset Statuses	Asset Management, Audit Management, Reports, Role Access Control
Asset Conditions	Asset Management, Audit Management
Locations	Asset Management, Asset Transfer, Audit Management, Schedule Management, RFID Management, Floor Plans, User Management, Reports, Supplier Configuration, Site Configuration
Departments	Asset Management, Asset Transfer, Asset Disposal, Audit Management, User Management, Reports
Manufacturers	Asset Management (Purchase Details), RFID Vehicle Management
Models	Asset Management (Purchase Details — filtered by Manufacturer), RFID Vehicle Management
Suppliers	Asset Management (Purchase Info, Warranty, AMC)
Sites	Location Configuration
Countries	Site Configuration, State Configuration
States	Site Configuration
Activity Types	Schedule Management
User Groups	Schedule Management
Cost Templates	Schedule Management (Activity Execution)
Checklist Templates	Schedule Management (Activity Execution)
Roles	User Management, Workflow Management, Role Access Control
Users	Asset Management (Custodian), Asset Transfer (Assigned To), Audit Management (Auditor, Re-Verifier), Schedule Management (Assigned User), Workflow Management (Approvers, Delegation), User Management (Reporting Manager), Supplier Configuration (Contact Person), Notifications
Reader Types	RFID Management
Floor Plans	RFID Management (Reader Configuration), Floor Plan Management
Vehicles	Asset Transfer (Movement Tracking), Schedule Management (Movement Tracking)
Workflow Templates	Asset Management, Asset Transfer, Asset Disposal, User Management (automatic trigger on entity events)

Impact Analysis: Master Data Changes¶

When modifying master data, consider the downstream impact:

Change	Impact
Deactivate a Category	Assets in that category remain; new assets cannot use it; audit/disposal filters exclude it
Deactivate a Status	Assets with that status remain; new assets cannot use it; report filters exclude it
Deactivate a Location	Assets at that location remain; new assets/transfers cannot target it
Deactivate a Department	Users in that department remain; new users cannot be assigned to it
Delete a Manufacturer	Models under it become orphaned; existing assets retain the manufacturer reference
Deactivate a Supplier	Existing warranty/AMC records remain; new records cannot use it
Deactivate a Role	Users with that role lose associated permissions; reassign users first
Modify Category Depreciation Defaults	Only affects new assets; existing assets retain their configured values

Best Practice: Deactivate rather than delete master data to preserve historical references. The system uses soft-delete for most entities.

Back to: Index · Master Data Configuration