From the Editor
It was this month in 1985 that I began writing about computer-aided design, as CADalyst magazine hired me to be their new technical editor.
Now it's 35 years later, and thanks to you amazing readers, I'm still reporting on our favorite software.
- Ralph Grabowski
|
|
Open Design Alliance
DevCon 2020
Compiled by Ralph Grabowski
|
|
We were supposed to be in Munich for this event, but then coronavirus ruined the trip. The Open Design Alliance’s DevCon 2020 was, as a result, online, just like other CAD software conferences this year.
In ODA president Neil Peterson overview of the industry, he noted that this is a down year for BIM [building information modeling], but then expects it to grow by an annual average of 14.5% through to 2025. Some of the issues (pro and con) that define the market are the many design programs available, multiple data formats, a growing number of stakeholders, and the biggest problem of all: the gap between design tools and offsite prefabrication, as details in BIM are too low for CAM [computer-aided manufacturing].
The ODA wants to make BIM (and other aspects of CAD) transparent: to view, publish, collaborate, exchange data, and manipulate data openly. (See figure 1.) The idea of an open standard created by industry stands in contrast to those proprietary formats preferred by software vendors. ODA backs up its slogan "transparent BIM" with SDKs [software development kits] named BIMrv (for Revit) and BIMnv (for Navisworks).
Figure 1: The technology stack from Open Design Alliance (all images sourced from DevCon prsentations)
ODA + bSI + OGS
Last year, ODA partnered with buildingSmart International (bSI) to provide the SDKs for the IFC [industry foundation classes] format used by the BIM industry to exchange data. This year, ODA inked an agreement with Open Geospatial Consortium (OGC); the two are exploring how they might work together. I assume ODA will make SDKs for OGC.
There has always been an obvious link between CAD and GIS [geographic information systems]; indeed, that is how Intergraph got its start in 1969. As long ago as 2007 GIS-CAD became “3D information management,” because more than just CAD data works with GIS, such as BIM. (See figure 2.) And so OGC agreed this year to work with ODA.
Figure 2: The sorts of things handled by OGC
This Year’s IFC v4.3
IFC v4.3 includes more of the built environment, while two dozen object types have been deprecated or replaced by new schema. Built environment means physical structures, such as roads, canals, and shopping centers. (See figure 3.) IFC schema have to be proved by actual implementation before they can be approved as ISO standards, and so for 4.3 this is happening through a number of railroad and road organizations in North America and Europe.
Figure 3: The built environments supported by IFC 4.3
The nomenclature has changed: bSI replaced the x in version numbers with ., so the old (and confusing) 4x3 is now 4.3.
The Future IFC 5
IFC version 5 will be more efficient and less confusing.
More efficient, because IFC data will become available in a larger number of file formats, such as adding XML, OWL, JSON, HDF5, and so on to the current STEP; UML [unified modeling language] will be the primary format. HDF5 [hierarchical data format] in particular offers smaller file sizes and faster load times due to compression and structure; see ogc.org/standards/HDF5. (See figure 4.) We talked about HDFs in upFront.eZine #1,058.
 Figure 4: The advantages to using HDF5 with IFC
Less confusing, because right now model view definitions (MVD) allow software vendors to cherry-pick parts of IFC to implement in their software; the idea was that they wouldn't need to implement the entire standard, which is huge. But if an IFC file is exported according to one MVD, and the recipient software package is written to another MVD, then confusion reigns when there is insufficient overlap between the two MVDs.
MVDs will change in the future. The replacement will be IDS [information delivery system] in which the vendor says what information is needed from an IFC file.
The new information delivery standard of IFC 5 means there will be a single IFC base for all programs for long-term . The root of IFC will have fewer updates for stability (every three to five years) with entity definitions having more frequent ones to keep current (every one to three years).
IFC will be publicly available on GitHub. The ODA demo’ed using IFC files in HDF5 format. Their IFC viewer for Windows and MacOS supports the newest IFC versions. It does all the tasks we expect of viewers today, such as sections, but now also displays shadows and handles collision detection. It exports the IFC model to PDF. Anyone can download it fro free from openifcviewer.com
SDKs for Revit and Navisworks
The ODA supports Revit file formats up to today's RVT 2021 (see figure 5).
Figure 5: The capabilities of ODA's BIimRv API
During the online conference, we saw some of the new functions being made available from the ODA:
- Several kinds of sectioning (see figure 6)
- Color-filled 2D plans based on function
- User worksets, which isolate grouped elements by name
- Conditional load/unloads that save can 1GB RAM, on average
Figure 5: Sectioning of Revit models by BimRv
While the ODA’s BimRv SDK reads and displays Revit files, the big deal (and tougher job) is creating RVT files, which also means being able to edit them. This is still under development. The ODA has a road map to show which functions will be released over the next sixteen months. (See figure 7.) Creation functions include curves, custom parameters, connectors, materials, view-based elements (sheets), forms, families, Boolean operations, and openings.
Figure 7: Roadmap from ODA for BimRv
We also saw the progress being made with Navisworks compatibility, which for Autodesk is a kind of universal file format on the AEC side. See figure 8 for the roadmap.
 Figure 8: Roadmap from ODA for BIMnv
Bricsys told us how it uses the ODA’s SDKs for DWG, civil, BIM, and mechanical components. As of v21 BricsCAD will import RVT files, not just IFCs as in earlier releases. RVT elements are translated into native geometry, which for BricsCAD means DWG format. The translated elements can then be directly modeled, sectioned, and edited – and saved as DWG files for use in other software. (See figure 9.)
 Figure 9: BricsCAD v21 with RVT-format model
BricsCAD v21 will place RVT files as underlays, which means they can be seen as references, but are not editable. Specific entities, such as walls, can be imported from the underlay, I think they said. BricsCAD 21 is due to ship by the end of October, 2020.
Q&A
Ralph Grabowski: I did not catch the line by Mr Ouellette about IFC. Does he think IFC can handle all forms of data (like DFM, digital twins) -- or not? If not, then what is the alternative to accessing that data?
Jeffrey Ouellette: The simple answer would be the use of linked data methodologies. bSI is exploring the use of IfcOWL, as well as implementations of JSON / IfcJSON to make it easier to link to other data sources and exchange them on a transactional basis.
Grabowski: I am not sure we heard exactly what is ODA doing with OGC?
Neil Peterson: We are looking at cooperation in a similar manner to the cooperation between ODA and bSI, where ODA would provide implementations for certain OGC standards. For example, CityGML has been discussed as a possible first project.
Fabio: Regarding Civil SDK, how much of API has been migrated to .Net? Is this SDK the same as AutoCAD Civil SDK?
Ivan: Currently, we wrapped all Civil into a public API. The API is the same as the C++ ODA Civil SDK.
John: The main point is I notice that the library seems more granular now.
Sergey: You can get an idea of the optional modules that you can skip from docs.opendesign.com/td/tdrawings_libraries.html
John: Is there still an ActiveX install?
Sergey: Yes. It's still supported
Ralph Grabowski: Is the Android ODA viewer for anyone, or just members of ODA?
Alexander Federov: This application is for the ODA members, as a sample of using our Visualize SDK under the Android platform.
John: What are the main differences between Drawing vs. Visualize SDKs?
Alexander Federov: Visualize SDK is for the rendering of the different kinds of the data. It is not connected with some specific format. But strictly speaking, since Drawings SDK uses Visualize SDK for rendering contents of the DWG files, it is possible to transfer data to DWG first, and then render it with Visualize SDK as a contents of the DWG database. But such a transformation is sometimes not possible or efficient.
Fabio: Is it possible to use .Net C# to integrate all stacks (DWG SDK, Visualize, Publish) in order to develop cross-platform -- Windows, Mac, and mobile (IOS and Android)?
Alexander Borobikov: We provide wrappers for C++ code. Wrappers are generated for a large set pf SDKs: Drawings SDK, Visualize SDK, Publish SDK. But for now our wrappers are Windows-only.
Guido: Does Visualize support huge point cloud data that might not fit into memory?
Alexander Federov: Yes. We have the RCS [Re Cap source]-based point cloud object, which allows the use of LOD [levels of detail] for the huge point cloud data. Yesterday [at the conference], there was a demonstration of such a technique. It will be possible to see the recordings of yesterday's presentation and find some details about it.
Guido: Do you have any plans to support AR [augmented reality] or VR [virtual reality] in Visualize?
Alexander Federov: We created a VR sample two years ago. But it was frozen since then. We have a plan to reanimate activity with it next year. With AR, no plans yet.
Ben: Will recordings of these presentations be available later?
Alexander Borobikov: We will upload the materials to our Youtube channel, so they will be available.
What Ralph Grabowski Thinks
The importance of the Open Design Alliance is that it sets the pace for other CAD systems. In this way it is like the firms that produce kernels: numerous CAD systems depend on the capabilities delivered by updates to kernels, and likewise on the ODA.
Fortunately for members, the ODA sees DWG as more than just a file format, and so over the last decade has created a framework for application development around DWG. With its APIs and SDKs, members can create software like 2D/3D CAD programs that handle solids, custom file viewers of multiple file formats, PDF import/export, revisioning, and so on – for software running on desktop computers, Web browsers, and mobile devices. (See figure 10.)
 Figure 10: Mobile version of DWG viewer and its capabilities
Perhaps the key to the ODA’s success is that it is a member-owned non-profit, ensuring long-term support. Being member-owned means that members determine the direction of development; being non-profit means that it does not need to satisfy a Wall Streetian demand for higher profits that comes at the expense of customer needs. www.opendesign.com |
|
The following posts appeared on the WorldCAD Access blog during the summer:
|
|
I miss your Quotable Notables. I thought the irony was great. - Paul Bertram
The editor replies: It became, frankly, hard work for me to hunt down a steady supply for each week. I am glad that you liked them. If you want similar irony, follow @managerspeak on Twitter. Here is one of his aphorisms: "90% of success is showing up. We’re going to have to do that on Zoom for a while."
Here is a bonus one, to be filed under 'Spin Doctor of the Moment': "This account was incorrectly actioned. This has been reversed and the account has been reinstated." - Twitter
Re: Spaceclaim Success
It's hard to say how successful Spaceclaim's marketing was. And my experience is that nobody knows about Spaceclaim outside the CAD-nerd echo chamber -- and actually most CAD users have no clue what direct modeling is.
So if nobody knows about Spaceclaim, and it was not successful in terms of selling many seats, then can we say that their marketing was successful? - Istvan Csanady, CEO Shapr3D
The editor replies: They certainly gained mindshare, fostered the push in mainstream MCAD to emphasize direct modeling, and then disappeared from the CAD-nerd echo chamber with their acquisition by Ansys.
Nice detective work. Thanks! - Greg Morehouse (via WorldCAD Access) New Zealand
- - -
This is in response to this guy’s complaint, “Their unwillingness to offer any sort of help to repair or replace my far superior Performance MX mouse with a failing left-click button.” Tell him he may be able to open the mouse, and then buy a replacement switch from DigiKey. I’ve done that to my mouse before, so maybe it’s possible for him? Doing so requires minimal mechanical and soldering skills. - Chris Cadman
- - -
Commenting on 3Dconnexion/Logitech, I ran across this last month. They are indeed separate from Logitech. I was surprised. See the last post in this forum topic: 3dconnexion.com/forum/viewtopic.php?f=25&t=35706 -Brian Cranston, CAD Administrator LSI Industries
The editor replies: Yah, there is a lot of confusion on this. 3dconnexion could help by making it clearer on their Web site.
Re: Dassault Systemes vs Solidworks, Part II
This is really a great eye-opening article. I use Solidworks every day at work. Though cloud-based has its benefits, I live in an area that sometimes has a poor internet connection. I rely on this software to get my job done and to get accurate and high-quality production drawings for our production facility.
If Solidworks starts getting phased out to introduce a new system, it will cost us years of learning and hard work to get our drawings where they are. Thank you for the eye opening article. I will be keeping closer tabs on this and will think towards what our future may look like in the Solidworks and 3D design world. Thank you so much for this article. - Josh Hixon Duluth Tree Service Pros
Ah, those where the days! Nth Engine's birds-eye view was the thing I missed most when switching to Matrox graphics cards.
I also remember the fiddling with jumpers / rocker switches on network cards, graphic cards and other ISA cards to get them to use different IRQ, DMA en I/O addresses. And particularly to optimize the I/O space so QEMM [Quarterdeck Expanded Memory Manager] could make the most of upper memory. Oh, well. - Simon Weel (via WorldCAD Access) The Netherlands
The editor replies: AutoCAD for a time also had a bird's-eye view (DsViewer command, expired in 2012), but I never found it particularly useful as it tended to be small, so as not take up much screen real estate (see figure below, credit cadforum.cz). If, back then, I could have afforded two monitors (they tended to be around $1,500 each in the 1990s), then a bird's eye view in one monitor might have been pretty nifty.
Bird's-eye view window at left
|
|
Thank you to readers who donate towards the operation of upFront.eZine:
- Bricsys (small corporate donation)
- Dave Edwards Consulting
To support upFront.eZine through PayPal, then the suggested amounts are these:
Should Paypal.me not operate in your country, then please use www.paypal.com and the account of [email protected].
Or mail a cheque (US$ or CDN$ only, please) to upFront.eZine Publishing, Ltd., 34486 Donlyn Avenue, Abbotsford BC, V2S 4W7, Canada. |
|
|
|
Recent Comments