A significant gap also exists between the format of established material property databases and access to this data with various modeling and simulation environments. Many commercial solvers have custom database formats that either require extensive scripting or manual entry of data. These methods are prone to error and can disconnect the analysis from the source material rendering these solutions unreliable for use in future programs. A universal format is needed to eliminate the need to translate data into solvers and readily allow engineers to conduct an analysis with reliable information. This format must allow for interchange between various solvers that extract from or populate to the infrastructure database.
Success of this infrastructure will rely on three areas:
(a) establishing a universal format that is open, simple, expandable and interfaces with commercial solvers and user API,
(b) development of a user friendly interface that is easy to learn, adopt and interface with existing databases, and
(c) interface this environment within a cloud based storage environment that allows for synchronous data exchange with embedded security controls, data management and oversight.
All three of these areas must work for this process to be successful. An open format is needed to allow the user to define how data is built. Users will not adopt to new standards for data capture and maintenance without a user friendly GUI and the system will not work unless a synchronous method is available for data sharing within the organization.