Component Center - Replication?

Great vid on CC. The efficient use of components is pretty key to making sure BIM workflows are as frictionless and lucrative as possible.

Some questions:

1. Component tracking / indexing: Is there a way to track which files the component is inserted into? This will be key to replacing / updating components when something new comes along. They always do. The lack of a reliable tracking mechanism has always held  Mstn back in the past by preventing the user from getting Cells to behave like Refs on demand.

2. Linking to manufacturer's or BIM libraries: Is there a way to subscribe to portal services like NBS, BIMObject etc? It would be good to be able to access their components using the same CC interface. And also get notification when a component is updated.

3. What about all the .xml schema information or Excel data sheets that are needed for OpenPlant; and OpenBuildings' older Datagroup System .xsd filles? I think that even Revit has its Shared Parameter file. These are currently stored on the local server or PW. Updates / synchronisation will be required. Scripting or MS Flow tools? It would be unreasonable to expect the user to have to manually convert / synchronise the thousands of components available without some automation help. Disciplines like MEP would suffer most.

4. Will CC be able to function like a Parametric Cell Studio or Revit Family Editor environment? It only seems to accommodate uploading and superseding components. Ideally, the user would open the file and edit the component before saving it back to the 'online' store. Having duplicated unmanaged files would be very inefficient and a recipee for errors.

5. Will CC be able to support GenerativeComponents? Please note that GC now supports multiple models. GC components would have nested components. Automatic updates or notification? Ditto for Functional Components.

6. Replication: RFA components currently need to be converted into Functional Components using re-mapping a lot of parameters/properties, and vice versa. This would be stored as an xml or settings file. It would be good to be able to store this on CC to allow automatic replication of any components regardless of originating format. This would allow cross platform teams to share the same component repository/library. A Revit user would see the RFA while the Mstn/OBD user would see a Functional Component replica of the same component. I think that Structural Synchronizer-type workflows would be subsumed/leveraged to deal with components (more granularity)....

Parents
  • Hi Dominic:

    1)  Component tracking / indexing - We're building our component analytics on the web service and the clients now.  We intend to start with reporting on downloads, placements and files that components are inserted into to allow you to track your components and how they make it into your designs. 

    2) BIM Libraries: We've been looking into integrating both BIM Objects and BIMStore into our Brands to allow you to do just that.  we did meet with NBS but have not heard back from them on our request.  This is not currently in planning as our analytics and catalog sharing features are taking precedence at the moment.

    3) OpenPlant: We're relying on each product group to integrate Components Center into their solution in a way that makes sense for their users and their workflows.  We've met with the OpenPlant team to discuss the possibilities and will assist them in that effort when they schedule the integration efforts.  Currently we're integrated with MicroStation, OpenSite, OpenRoads, OpenRail, OpenBuilding and Concept Station.

    4) From Revit you can open an rfa and edit it, however you do have to upload it as a new component.  Are you asking for us to be able to open a file, edit it and create a new version?  Currently we don't have proposed versions which is what would be required.  That's a great enhancment request, do you have a set of steps and personas I could use to write that up?

    5) We've talked that over briefly with the MicroStation team.  I think it's completely possible since CC is file agnostics and can store multiple files per component, but the MicroStation team would need to build in a publishing element to do if effectively.  I'll send this request over to them.

  • 3. Yea, it would be good to understand how the settings that require external data/resources are handled. In OBD, the symbology of the component will require a designated Family+Part, and Datagroup System catalog entry. Rendering materials? This info is usually stored externally to the component. For maximum portatbility it would be good to be able to package this with the component, with some scripts to insert the info into the active project's dataset?

    4. No. What would be great is if CC would emulate the way Revit's FE works. Mstn's Cell Manager also allows you to select a Cell and open the dgn where the cell is stored for editing. When you close it everything is saved. Revit's FE does a 'Load into Project' when the user is finished editing the RFA.

    Essentially, the Component (RFA, dgn etc) would live in the cloud, bypassing the need to have duplicate copies on the local drive or server that would need to repeatedly uploaded post-editing. Need to be recognise that a lot of components are not 'whole' first time, especially when parametrics / constraints are involved.

Reply
  • 3. Yea, it would be good to understand how the settings that require external data/resources are handled. In OBD, the symbology of the component will require a designated Family+Part, and Datagroup System catalog entry. Rendering materials? This info is usually stored externally to the component. For maximum portatbility it would be good to be able to package this with the component, with some scripts to insert the info into the active project's dataset?

    4. No. What would be great is if CC would emulate the way Revit's FE works. Mstn's Cell Manager also allows you to select a Cell and open the dgn where the cell is stored for editing. When you close it everything is saved. Revit's FE does a 'Load into Project' when the user is finished editing the RFA.

    Essentially, the Component (RFA, dgn etc) would live in the cloud, bypassing the need to have duplicate copies on the local drive or server that would need to repeatedly uploaded post-editing. Need to be recognise that a lot of components are not 'whole' first time, especially when parametrics / constraints are involved.

Children
No Data