Revit models constructed for the purposes of fabrication, coordination and as-built conditions are typically not going to function well in a facilities environment if they are used “as is.” It’s important for AEC service providers and consultants to understand their customer needs. Chuck Mies from Autodesk sums this up best by posing the following three questions that you should be asking a building owner if they intend to use a Revit model for facilities management:
- Who on the facilities team is going to use the data?
- What data is going to be collected during the AEC process for future FM purposes, and how?
- How will it be maintained once operations begin?
By asking these questions and engaging a building owner you can have greater confidence that a Revit model turned over for the purposes of FM will be more successful and actually used during operations. I also recommend that you ask your customer to really think about what data is critical and who in their facilities team will be responsible for maintaining the information once the model is turned over. This will ensure that you don’t over model or provide excessive detail in equipment families that are not critical and will be difficult for a facilities team to maintain…
[Admin: To see other related posts, use the BIM tag or Revit tag.]
We’re developing some generic components that we would like users to access from various different UX apps (e.g. allow a user to set their primary location or update their photo). Is it possible to configure each app to access its own model plus one or more generic models to support features shared between apps/views?
[Admin: This post is related to the 09.12.16 post about reusing an existing UX model. To see other related posts, use the UX Framework tag or Perceptive tag.]
One of the challenges that building owners who implement lifecycle BIM face is the difference between the BIM models created for design and construction and the BIM models needed for operation. Although with proper procedures, building data can and should flow from one phase to the next, it is useful to identify at least four types of BIM models…
- BIM Design Models: These are created by architects and engineers with the objective of first defining the conceptual design and ultimately producing construction documents…
- BIM Construction Models: Contractors and subcontractors will use these models to aid in staging and detect potential conflicts using clash detection before encountering the issues in the field.
- BIM As-Built Model: This is created by the general contractor, subcontractors and suppliers. Traditionally, this information has been provided as a set of paper working drawings…
- BIM FM Model: This model is derived primarily from input from the BIM As-Built Model. When creating the BIM FM Model, the following modifications are made…
[Admin: To see other related posts, use the BIM tag.]
I have a couple of software development life cycle (SDLC) questions about Perceptive apps using the TRIRIGA UX Framework:
- How do you export changes to Perceptive app components from one environment to another, without exporting the whole application? Example components include web view files and data sources. Currently, if we only change and test a data source or web view in Dev, we cannot figure out how to export them from the Dev environment and import them into the system integration testing (SIT) environment.
- How do you add an existing data source to an existing model? We only found an Add button to add a new data source. We would like to associate a pre-defined data source to a model.
TRIRIGA currently supports exporting of the whole app, so you cannot export only a data source. For web view files, you have the option to use the WebViewSync tool to pull the files from one environment and push them into another.
About adding an existing data source, the data sources were designed to be part of a model and that’s why there is no button to add an existing data source to a model. However, you can manually associate them by using the Association tab.
[Admin: To see other related posts, use the UX Framework tag.]
Many real estate managers are rather surprised when their contractor shows up with loads of information at the hand-over of a new construction project. “It is all the information you need for the operational phase” he will say. Adding, “As we are really innovative, you will find everything in a digital model, called BIM.” After a discussion, in which the real estate manager explains that he only needs a small portion, a common response of the contractor is: “Real Estate & Facility Management is still old-fashioned, they don’t know what they need!” Is this a fair response?
The information challenge
Typically, users of an Integrated Workplace Management System (IWMS) have dealt with this challenge for many years. They have probably invested in maintaining CAD drawings to be able to import the gross and net m² of their spaces and updated their building assets at a relative high level. They have had to make maintenance budgets based on estimations of the amount of glass m² of their facades. When preparing for a renovation, they hire an architect to do exact measurements, which has always been the base for comparing offers of contractors to do their work.
Getting the most out of BIM
As contractors and architects are currently re-developing their business plans based on the use of Building Information Modelling (BIM), real estate managers are still investigating what this could mean for them. What possible benefits exist for maintaining a space with 3D dimensions? Or, which self-service/job-handling processes can really be improved by walking through a 3D model? Real estate managers that receive a BIM model will now have a hundred times more assets available than before. However, who will benefit from this type of information?
[Admin: To see other related posts, use the Planon tag.]
We’ve been integrating bi-directionally between our FM:Interact Integrated Workplace Management System (IWMS) and Revit models since 2010 and have been on the forefront of Lifecycle BIM since then. For the most part, building owners who are going to utilize Revit models for day-to-day facilities operations primarily relied upon 2D plan views generated from the model for all aspects of managing their facilities including space and occupancy planning, assets and maintenance management, etc.
Traditionally, plan views have provided a tremendous amount of information to facilities teams, especially intelligent plans, where users can query a drawing and get direct feedback on space and assets on the plan. Over the past two years, we’ve been integrating 3D viewing technology from Autodesk to help our customers take better advantage of the entire model.
We’ve recently updated FM:Interact to the latest Forge Viewer from Autodesk and the results are truly fantastic. The Autodesk Forge Viewer gives us the next generation graphics engine that enables our customers to take greater advantage of their Revit models for operations. Here are some of the top reasons why the time is right now and why we are now making this fantastic viewer available to FM:Interact customers who are using Revit models in their implementations of our software.
- Speed: Revit models can be large…
- Data: 3D model viewers have been around for years…
- Ease of use: The majority of the end users on facility teams…
- Accessibility: Facility team members are more mobile than ever…
I would like to create a page, which uses an existing model. How can this be done? I have already written some models, and wanted to reuse them in the new application I am writing. Are there any samples I can go through?
Assuming your new application relies on the same BO and fields defined in the model you’re attempting to reuse, you can link the new application in the Model-and-View Designer. For example: Your existing UX application will include Model (M1), View (V1), Model and View (M1V1), and Application (A1). So, for the new app, you would to create: View (V2), Model and View (M1V2), and Application (A2). Basically, the configuration needs to be done in Model-and-View Designer.