In Plantsight, user can use a template for each branch/fork off the facility iModel with user-set IRS forms (such as Technical query form), permissions (such as a different set of permissions for each of the roles, inlcuding the team member, proje...

In Plantsight, on the project landing page, and/or on the facility landing page, and/or on a separate landing page in any other product like Synchro, user can see all the issues assigned and all the issues s/he is tracking on a single page, even i...

SPPID export into PlantSight/iModel has differences between what was exported and what is visable in the iTwin viewers (PS0 for ALIM). Hidden text in SPPID is visible in iTwin viewer Change propertie markers are unable to to be turned off as in SP...

Audit Logging Configuration setting – Any evidence (Screenshots or SDD) of the Audit log Configuration from applications (ALIM and PlantSight). Audit Logging must be enabled for : Failed/ unauthorized login attempts & Logout logs must be captu...

For EDM's Query Browser, in order for query results to be editable, we have to add several new fields that users do not want (ECInstanceId, ECClassId, Model) in order to make the query results editable. Additionally, we cannot use aliases for the ...

The APX-RYD project, part of the Pangaea initiative, currently has only one iModel. When users open the project or the iModel viewer, they must click on the iModel selection popup window to proceed. While this selection process is necessary for pr...

Equip local administrators with more tools for troubleshooting the iTwin publishing and PlantSight data. Issues that could benefit include resetting coordinate systems (vs. removing and reprovisioning the iTwin), identifying/showing components tha...

We would like the ability to be able to manually select which classes to view in the Tag Browser tree from a list of all available classes, regardless of whether or not there are any active records in the database for a particular class.

We would like to have the option to display the actual property name rather than the property display label as the column alias in the Tag Browser results. This will help us in creating custom queries to know which properties to reference. Example...

In Plantsight IRS, the dashboards allow additive filters to be applied, but not an 'exclude' filter such I want to filter on all open items but 'exclude' ones created by me.