Verify/Create your Bentley Connect ID and join the APM BeCommunity…
If this is the first time and you are not sure you have an ID:
Go to APM BeCommunity: https://communities.bentley.com/products/assetwise/asset_performance_management/
Click on the avatar to log in and join the APM BeCommunity…
You can Bookmark the page, and setup notification options for the Forum to be notified of new posts specifically related to APM,
Important to setup:
Notifications for Support Alerts:
Go to the Asset Reliability Wiki/Support Alerts page'
Click on More:
Notifications of news posts on our Blog, including announcements of upcoming SIG webinars and new Release announcements.
Go to the Blog tile:
You can introduce yourself to others in the community and invite them to connect with you. Go to Welcome APM Users
Here are some useful links:
Bentley Communities Helpful Guidelines
Bentley Communities Forum Tips
To submit an Service Request go to https://connect.bentley.com/, navigate to My Support section:
Also see this article for techniques for reporting APM product SRs
Bentley CONNECT Ids for all the users at your account can be managed and maintained by users that have an Admin or Co-Admin role assigned to their Bentley CONNECT ID.
If you need help with setting up users, or need to find out who are Administrators/Co-administrators for your account, submit an SR to the Website Assistance Team.
Here is a short video on managing users:
User Management video
Here is the link where the administrators need to go to do this task:
If you need further help with setting up users, or need to find out who are Administrators/Co-administrators for your account, submit an SR to the Website Assistance Team
Priority 1 (P1)
An incident that has or is likely to have a major impact on users’ ability to maintain business operation. The incident results in any outage or loss of any key functionality of a critical application or service. The incident affects multiple locations, or all users in one (1) location.
Users at multiple sites cannot access the system and no workaround exists.
Priority 2 (P2)
Incident which impairs the users’ ability to maintain business operation causing a severe degradation of service or resulting in some important functionality being unavailable. There is no long term acceptable workaround for the business, however operation can continue in a restricted fashion. The incident results in loss of the "normal" functionality of an application or service for multiple users, but not all, in one (1) or more locations.
Users can access system and, while a workaround exists, there is material
degradation of functionality or performance
Priority 3 (P3)
Incident which causes a loss of some important functionality. There is an acceptable workaround for the business and operation can continue in a restricted fashion. The incident results in loss of functionality of a "normal" application or service.
A non-critical service is not available to some users.
Priority 4 (P4)
Incident which has little or no significant impact on the business. Low impact and low urgency.
The behavior varies from user expectations, but the system works as designed. Resolution would occur during a future update.