Settings and activity
40 results found
-
40 votes
Dan Miller
supported this idea
·
An error occurred while saving the comment -
7 votesDan Miller
shared this idea
·
-
8 votesDan Miller
shared this idea
·
-
11 votesDan Miller
shared this idea
·
-
19 votesDan Miller
shared this idea
·
-
49 votesDan Miller
shared this idea
·
-
28 votesDan Miller
shared this idea
·
-
21 votes
This is scheduled for release in 2023
An error occurred while saving the comment Dan Miller
commented
Fred, you are correct, there may be changes that need to happen within the product to comply with issues found during the FedRamp process. From our experience, we are not aware of any specific features that need to change, though other BPs can chime in. As a first step, I would recommend starting discussions with a company that can guide Archibus through the FedRamp process as quickly as possible. The longer the product is not certified, the more business we lose.
In addition, please make sure this is not just an Archibus Cloud issue within Archibus. We need the Enterprise application certified. Most (if not all) Government implementations are perpetual onsite or hosted.
An error occurred while saving the comment Dan Miller
commented
Will this certification apply to ARCHIBUS Enterprise as well? If not, the primary push should be to get ARCHIBUS Enterprise FedRamp compliant. There are many Civilian US Government agencies that have ARCHIBUS installed onsite, and most US Government ARCHIBUS installations could not migrate to ARCHIBUS Cloud due to the level of customization applied to the system.
Dan Miller
supported this idea
·
-
15 votesDan Miller
shared this idea
·
-
6 votesDan Miller
shared this idea
·
-
5 votesDan Miller
shared this idea
·
-
13 votesDan Miller
supported this idea
·
An error occurred while saving the comment Dan Miller
commented
I think this is a good idea, though I would suggest a more general concept of "sticky restrictions". Let the user specify a filter (buildings, departments, etc) and have that restriction apply to all views that user visits until they remove the restriction.
-
63 votesDan Miller
supported this idea
·
-
36 votesDan Miller
shared this idea
·
-
7 votesDan Miller
supported this idea
·
-
10 votesDan Miller
supported this idea
·
-
18 votesDan Miller
supported this idea
·
-
78 votesDan Miller
supported this idea
·
-
120 votes
An error occurred while saving the comment Dan Miller
commented
I agree with Thomas that the level of effort would not be trivial, however this is something that should be done. As implementers, we are constantly trying to fit a customers n-tier hierarchy into 2 levels (dv/dp) and it never fully meets the customers expectations. Changing ARCHIBUS to start using n-tier hierarchy for organizations will be a long overdue enhancement.
Dan Miller
supported this idea
·
-
34 votesDan Miller
supported this idea
·
I agree this feature would be helpful so we can better control the user experience. I would recommend configuring at the role or user level the ability to specify if the user sees domains or applications as the top level that displays.