Experience MFIN Data Model One approach, and an important step in the evolution of MBD, is the develop- ment of a Model-Based Feature Informa- tion Network (MFIN) [1]. MFIN describes a self-contained data model expressed in a dedicated XML structured file. Its goal is to provide a meaningful method to capture and connect information at the CAD feature level. The model abstracts key functional aspects of the MCAD model, for example a “hole,” in a way that is traceable to the MCAD design geometries. It also provides for the inclusion of business logic traceable to the design geometries, such as manu- facturing planning processes, quality, testing, and Maintenance/Repair/Over- haul (MRO). While significantly expanding the infor- mational scope of MBD with meaningful design intent elements there remain the persistent issues that can only be addressed by a more complete model. Design Intent The descriptive and behavioral role of the sub-system in the context of the complete system. For example, access to the “connective tissue” of the system as represented in a Model Based Systems Engineering (MBSE) model to properly interpret co- dependencies between various engi- neering design disciplines. Traceability Once an MFIN file is generated and shared it becomes an information island itself without any formalized traceability to the origins or chronolo- gy of the information. Configuration Management An MFIN file is not a data structure and, therefore, it is inherently difficult to describe or control its contents. It is a separate file from the MCAD/PMI data and therefore it is not a compre- hensive answer to configuration con- trol, revision, or ECO processes. A common occurrence would be to have separate MFIN files represent- ing different configurations of the same design with no understanding of the revision levels, differences, or intent. 46 ProductDataJournal 2021-1 An Evolutionary Example Towards MBE An example of the development of model-based MBD information systems for a manufacturing process can be found in the history of the printed circuit board (PCB) industry. In the early days, holes were drilled, and flat brass wires were riveted onto the surface of Masonite or other thin pieces of wood. In today’s multi-billion-dollar industry of highly sophisticate multi-layer intercon- nected structures, the PCB process has followed, and perhaps surpassed, that of the manufacturing evolution of the MBE vision. With the introduction of photoplotters, the PCB design industry transitioned from manual creation of physical films to CAD generated NC files. This replaced the manual “drafting“ process of hand taping interconnects which were then photographed to produce the negative manufacturing film. This was equivalent to the MBD replacement of physical 2D drawings with machine readable MCAD data. Over time the PCB industry adapted a new data packaging standard called ODB++ [2] for delivering information to manufacturing CAM process. Its intent was to normalize the delivery form of additional design intent information (names of electrical signals, pin-pin net- works, etc.) and manufacturing process data routing, placement), beyond the photoplotter NC files (dumb interconnect images) – all packaged into a single ZIP structure of standardized formats and files. Very analogous to the definition of the MBD PMI package and normalization of process related infor- mation resident in MFIN as a companion of the annotated mechanical 3D PDF. Today the PCB industry is in the process of adapting the IPC2581 [3] standard, which uses a single XML model for rep- resenting all information that is con- tained in multiple files in the ODB++. This standard includes the ability to doc- ument configurations, revision, and changes. A similar evolution for MBD would be for MFIN to develop a method of capturing MCAD geometry details, PMI, and design intent into one MBD file. (drilling, informational IPC2581 was designed to communicate information from design to manufactur- ing and vice versa, and therefore it is very well positioned to become a format through which PCB data populates and is extracted from electronic data models in PLM platforms for a specific purpose (a view). This transition is yet to happen, but should it happen, it will be identical to generating MFIN views appropriate to a task directly from PLM platforms instead of having a single monolithic MFIN for all the tasks. MBD and PLM Reliance on a set of individual files, as the current MBD environment supports, is unsustainable from a Configuration Management (CM) perspective, and contrary to the original goal of an authoritative source throughout the lifecycle. A more holistic view is required – one that goes beyond precise geometries, descriptive annota- tions, a manufacturing viewpoint provid- ed by PMI, and an independent MFIN file. What is required, is traceability and permission-controlled views into all ele- ments in system data models such as MBSE, Verification and Validation, Simu- lation, Requirements, Documentation, and Change Management throughout a product’s lifecycle. The concept of a view is essential to seeing MFIN-like structures as specific to a task at hand and therefore limited only to the related information. Today’s comprehensive PLM platforms provide the foundational technology to manage the needed holistic view of an MBD model therefore allowing the extension of the thinking to an enter- prise-wide MBE strategy. This is a plat- form that can manage all the respective models of data required by MBD, as well as element to element relationships between models—traceability. Individual models (MBSE, MCAD, ECAD, ALM) evolve separately under model specific governance and revision control and in their respective model configurations. MBD data views are instantly generated in standard formats (ex: MFIN), guaran- teeing that the output represents the lat- est instance of associated data. This is not limited to the classical MCAD/PDM disciplines, but also includes electronics, electrical, Software (ALM), Simulation, Verification and Validation, Require- ments, Documentation — a holistic