Why Do We Need a Neutral File Format?

6 January, 2019

Sharing models with different toolsets is a well-known, costly industry problem. At Intel, we led the movement, in collaboration with Future Facilities and Motorola Mobility, to establish a vendor-neutral file format, the open ECXML file format, and eliminate the problem altogether.

For almost 40 years, engineers have been sharing CAD data with their peers using vendor-neutral file formats. In 1980, the American National Standards Institute (ANSI) published the IGES format, which facilitated the sharing of CAD between engineers using different design tools. Fast forward to today, and CAD can be exchanged and distributed throughout the supply chain with unparalleled ease. This has not been the case for data exchange in the Thermal Simulation world.

Typically, component manufacturers provide CFD models of components to their customers. This practice is challenging and inefficient, often requiring component manufactures to develop, validate and support three or more native formats. This challenge is not limited to component manufacturers; any company who builds equipment that is then supplied to third parties for use in a larger system may be expected to provide thermal models. From a customer perspective, this process can be equally frustrating. Nobody wants to ask for a thermal model from a supplier only to find out that it can’t be provided in the format you need.

Through our close work with Future Facilities, we have seen first-hand the struggle of maintaining multiple thermal models of the same product. This gave us an idea: surely the industry would be better served if there was a vendor-neutral file format? We pitched this idea to our contacts in the industry and received an overwhelmingly positive response. In 2015, we began working with Future Facilities and Motorola to define what data such a file should contain, and this information was published by Intel in early 2018. Subsequently, we co-hosted a meeting where we announced that we would only release thermal models in the neutral file format. Shortly thereafter, Mentor Graphics and Ansys joined the initiative. The net result of this is the adoption of the open ECXML file format.

ECXML allows a selection of objects – along with material properties and environment settings - to be imported and exported as non-rotated cuboids or cylinders (or their 2D forms). Objects that can be imported/exported include PCBs, solids, heatsinks, fans, 2R components, chassis, sub-assemblies, heat sources, vents and porous obstructions.

The ECXML format represents the first step toward standardization across the electronics thermal simulation field, as well as toward productive co-simulation. By coupling CFD with different engineering disciplines, this format can encourage collaboration across engineering teams and synthesize the design process. Over time, this format can be improved with the addition of more complex geometries, additional objects and a wider selection of environment settings. Additionally, the plan is to form a JEDEC sub-committee that will take responsibility for maintaining and the growing the scope of the NFF.

Blog written by: Dave Ochoa, Senior Thermal Engineer at Intel Corporation's Data Center Group & Matt Evans, Product Engineer at Future Facilities

David Ochoa received a BS and MS in Mechanical Engineering from the University of California, Davis. He has been working in the electronics cooling field since 2001 and is currently employed by Intel Corporation’s Data Center Group as a Senior Thermal Engineer. David has experience with multiple commercial CFD packages and has created custom analysis tools specific to Intel’s thermal challenges. It has been in this work that David realized the need for a standard format for CFD and is committed to its success for the benefit of the electronics cooling industry.