Why permissions are important
- Data protection is extremely important and needs to be managed carefully.
- Within any organisation there will be many AWM users with varying roles and responsibilities.
- The permissions in AWM around access, and which actions can be performed on assets and other data are extensive.
- The Database Owner has the ability to control who has access to the database, which AWM applications they can use, and specifically what actions they can perform within each application.
Database Management Roles
Database Controller and Database Owner
There aren't too many differences between the roles. The Database Owner would be the first point of contact that Thinkproject goes to for approval when adding new users to your database or altering the permissions for existing users. That person will also act as one of our main contacts for all things client related where AWM is concerned.
The Database Controller is a similar backup role in case the Owner is not available, and has the same permissions as the above. For this, it's usually best to have two different users for the role.
Area of access to AWM
Initially, a user requires access to the database. Once access is granted, there are then further permissions for:
- Asset Management - Permissions allowing access to Security Zones (Areas), and to different assets in that Security Zone, as well as permissions for specific AWM applications.
- Work Management - Permissions to create a Project/Contract and perform work on the assets in the database. Projects/Contracts are linked to a Security Zone. You can learn more about Work Management in our Jobs/Dispatches course.
Asset management
- Security Zone Access - Asset Management
- Within each database there will be one or more Security Zones. Users are granted access to the zone or zones where the assets are that they are responsible for maintaining.
- Within each Security Zone individual users can be granted permissions in these areas:
- General - Range of general database permissions for the Security Zone
- Assets - Permissions for individual assets
- Staff - Permissions for editing staff access
- Specialist - Permission to access more specialised AWM applications.
Organisation management- where you create a new user log-in or update your password
User management- lets you view user permissions
Current users with access
Permission areas in AWM
Access permissions- tells you if the user has permission to view other users and/or if the user can edit other user permissions
Asset Management - shows you the security zone/s a user has access to as well as the users level of permissions in terms of updating/editing asset and inventory data
Work Management - shows all of the contracts a user has access to
Asset management permission levels
View only access - where you cannot edit asset data but can view all data
Full control - where you can edit all asset data
Contractor - default AWM permissions set up for a contractor
Custom – where you can edit/view pre-selected asset data
Custom AWM settings
General- covers permissions for things such as exporting data from the database/importing files, adding UDTs, SQL access
Assets- covers permissions for individual asset types
Staff- covers permissions for other AWM users
Specialist- covers permissions for AWM functions that are specialised such as high speed data, forward works programming, centreline segments
Bridge asset permissions example
Update
Insert
Delete
Bulk Update
Approve (if turned on for the asset type)
AWM permissions key facts
- AWM permissions can be customised to only include certain assets per user
- Anyone can have view only access for all asset data
- Generally 1-2 users will be able to update/edit user permissions as well as add new users
- Currently the entire PNG road network is a single security zone
AWM help videos
https://go.ramm.com/?help=UserManagement
https://go.ramm.com/?help=OrganisationManagementQuickStart
