Settings and activity
80 results found
-
63 votes
Tiffany Lam
supported this idea
·
-
33 votesTiffany Lam
supported this idea
·
-
21 votesTiffany Lam
shared this idea
·
-
3 votesTiffany Lam
shared this idea
·
-
2 votesTiffany Lam
shared this idea
·
-
14 votesTiffany Lam
supported this idea
·
An error occurred while saving the comment -
4 votesTiffany Lam
shared this idea
·
-
4 votesTiffany Lam
shared this idea
·
-
3 votesTiffany Lam
shared this idea
·
-
6 votesTiffany Lam
supported this idea
·
-
5 votesTiffany Lam
shared this idea
·
-
33 votesTiffany Lam
supported this idea
·
-
4 votesTiffany Lam
shared this idea
·
-
10 votesTiffany Lam
shared this idea
·
An error occurred while saving the comment Tiffany Lam
commented
A few clients had approached us with wanting options to display the desk photo in the protal just like how the reservations shows the photo of a room during a reservation booking under the portal. Here is a suggestions of how that could work in Archibus:
1. Have a reference library for photos by leverage the reference library table set
2A. Either in the room table, have a field that references the photo in the reference library. That way we don't have to upload a photo per desk.
2B. Set up the properties to the reference library to say a building, floor, room or even if possible, type of room.This allows clients to control if they have types of desk photos that are only applicable to a certain floor of a building or to a specific wing of the building.
Then in the portal:
1. When the user is selecting a room, then the preview of the photo can pop up 2. When the user selects a type of desk to filter for, show a catalog library of room types with the photos (similiar to requesting a problem on the workplace portal)
3. When the user searches for a room on the search filter, they can also see a photo of the room. -
20 votesTiffany Lam
shared this idea
·
-
33 votesTiffany Lam
supported this idea
·
-
3 votesTiffany Lam
shared this idea
·
-
46 votes
Reviewing this idea.
An error occurred while saving the comment Tiffany Lam
commented
This should be prevalent across any document field. For example it's pretty common to use sharepoint or other consultant tools for project management where it makes more sense to link to a file instead.
For lease management, most can agree that overtime, lease agreements are better stored within sharepoint for version control etc, so a link to the location of a file would be substantially better.
Tiffany Lam
supported this idea
·
-
6 votesTiffany Lam
shared this idea
·
-
3 votesTiffany Lam
shared this idea
·
This is becoming even more relevant we have clients working with BIM. It's not just equipment and furniture but everything treated as an asset in a client's definition. Calling the main table equipment is confusing to clients because they really think of equipment as hvac or a piece of equipment like a sound system.
Here's something needs we really need to start seeing in archibus:
1. BIM models contain all the properties of Walls, Piping, duct work, windows, doors, floors, ceilings, roofs, lights, etc.
2. Ability to have URL parameters in the bim viewer to start up at looking at a piece of asset or system.
3. It would be good to have that table have ability to configure what fields align to a asset category ie.
Walls for example contain information about:
- paint color
- wall type (fire wall, heritage wall, sound proof)
-materials (brick, concrete, wood)
-Condition
-dates installed, age etc)
-classification
-replacement cost, we know the volumne/area and the material so to replace it will cost $x
most of this looks like the stuff we see in the equipment tables.
Carrying this information and having it display in the bim viewer would be a big win, this can appear as a popup that shows the data that derived from Revit or it can be captured in Archibus. This also powers users to work with more interconnected work with CMMS and how this impacts space and surrounding systems.
So now as a maintenance person you can find out information about an asset such as a wall, find out how it can affect other systems, ie. sound system that is attached to the wall, the plumbing system behind the wall, the ventilation system behind the wall, etc. So in maintenace to repair something behind a wall, someone needs to create multiple tickets like tear down the wall, disable affected systems, fix the problem, patch up the wall.