Currently we have the Search & Manager Work Requests view that allows viewing all work requests (including archived work) as long as the user has the proper security group assigned.
I would like to understand what are the concerns with using this report vs. creating a new report that has the look-and-feel of the Maintenance Console.

Hi, Same console would be great so we can have the same look & feel, and most of all, the same fields (because not all of the current reports display the same information). And as mentioned Ryan, an option that would display/hide archived requests to keep good performances. We have customers with several hundreds of active requests.

Both would be nice. However, my concern with the console is that it would affect performance. Seeing archived requests would definitely have to be an option that doesn't show by default.

Hi All,
Question : If we build the functionality to view the Archived work requests then should it be available as a separate report or should it be part of the main console grid ?

JLL has actually created this functionality on behalf of several clients and it is associated to a Security Group assigned to a User Role. In our use case, it provides visibility of "All WRs" as a Show selection list item while maintaining action and editing functionality as per default BOC Work Team assignments to craftsperson records. An example user for this functionality would be the residences team in a University who have WRs that fall within their purview and WRs that are serviced by a separate maintenance group within the University that they need to monitor regardless of who created them. They maintain the ability to action their own WRs but can monitor work being done by others with no ability to action them or be a part of the Work Teams that work is assigned to. Functionality such as this should be part of the default BOC setup.

We often get issues with lost WR's or WR's that are stuck at a status because of some quirk in the SLA and a change (return or status change) that for whatever reason gets locked and cant be change, by anyone except the requester or sometime no one at all. In most cases this is due to a helpdesk sept log setting. It would be good if a super user could access all WR's and override the issues and adjust the status to get things moving. In many cases this will be to cancel/stop or close but should allow for all other status reset to the matching SLA. The step log should include comments to log the super user intervention.

I also think direct access to the history via the console is a good idea but should be a switch so not to overload the active console and should be controlled by a forced restriction as the hwr table is often holding a large amount of data at the same status.

Along the same lines would be good to have access to the reports like other consoles

@Fred - In my view it would be good to have a way to allow someone in the Helpdesk Role to have the ability to:

2) See all active work requests no matter the team

The Closed / Archived WRs are also important but the maintenance console is more geared towards the active queue. Maybe having another version of the console for the closed requests rather than having it all together will be good from a performance perspective.

I like the idea of having a security group to control edit access to the console as well.

Creating a security group similar to SPACE-CONSOLE-ALL-ACCESS would be perfect. Then, having all the data accessible in the same screen as the other wr would eliminate the need to customize the Search & Manage as we have done numerous times.
Even then, for the lost/hidden wr, if you don't know its missing, you don't know to look for it.

This is so needed. RSC is entertaining developing this for one of our clients. We can hold off on this if we know that this will be developed. Please advise.

I believe its essential to be able to see ALL types of request from one single place, so the super user idea is the right way. But please, please, please can this include an option for the super user to see all requests in read only mode as well as an option to edit etc. We get lots of requests for users who do not need edit access and read only mode for maintenance requests is an area we feel Archibus doesn't support our requirements.

Adding to this request for a "super user" to view all work requests, no matter the supervisor/team assigned, should this extend to allowing that "super user" to see all closed requests (read-only) without going to the separate "Search & Manage" view? This would be a different setting, but is allowing the user to see closed requests in the Maintenance Console another, related wish? Happy to get your thoughts...

1) See all active work requests for your team (exists)
2) See all active work requests no matter the team
3) See all closed requests for your team
4) See all closed requests no matter the team

This seems to be a no brainer for most Maintenance Console users. A super user to monitor all work requests (possibly in a stealth mode) would be awesome.

We need a read only building ops console. We have managerial/supervisor type users who need to see work across many sites, work teams etc. The basic options in Archibus via craftsperson settings don't really allow for an option for a user to be able to see "everything" in the building ops console but in read only. For us these users do not update/edit/complete work, they just need to be able to see it, view updates and possibly print it out.
You can make the space console read only via having a security group or not... but this is not available to the building ops console.

This would be a very helpful feature. Similarly, when a user manages to assign a request to both a supervisor and work team, it cannot be found in the console at all. A better behavior would be for it to be found by the assigned supervisor or the supervisor(s) on the work team.

I agree, this has been an issue for quite some time and unless a user has access to Smart Client to display the work requests, there is no way of finding the "lost" or hidden work request.