![\"\"](\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/24\/2020\/02\/Fig-1-Wiring-synthesis-1024x576.jpg\")
Advanced wiring synthesis solutions\nsupport complex wiring types, multiple shielding materials, and various network\nprotocols. With robust design rules, wiring synthesis can generate designs that\nimplement multicore cabling and appropriate shielding to protect the wiring as\nneeded. In other areas of the harness, wiring synthesis will optimize the use\nof wiring and shielding types to reduce cost while ensuring proper\nfunctionality.<\/p>\n\n\n\n
Wiring synthesis also generates\nwiring that correctly supports every buildable vehicle configuration. Each\nwiring harness must be able to support a variety of optional features that\nconsumers may choose, and the millions of harness configurations that result\nfrom such feature choice. The automated wiring synthesis can generate wiring\nfor all these buildable vehicle configurations, ensuring as much common wiring between\nconfigurations as possible to minimize cost.<\/p>\n\n\n\n
The platform context<\/h3>\n\n\n\n
As engineers employ generative\ndesign to generate and optimize vehicle systems, they must be able to assess\nthese system designs in the context of the entire vehicle platform. Vehicle\nsystem complexity affects all facets of the vehicle design. The vast\ninterrelations between subsystems within the vehicle also means that design\nwork in any system or sub-system may have effects elsewhere in the architecture.\nDesigning in the context of the overall vehicle platform promotes accuracy in\nthe design and supports comprehensive validation that can prevent costly\nrecalls.<\/p>\n\n\n\n
The platform context also has\nbenefits for understanding the cost impact of architectural decisions across\nthe vehicle. Platform changes can have effects that manifest across the entire\nvehicle. These effects, in turn, affect the cost of the design as wiring properties,\nsensor type, or the number of ECUs required could all change. The cost\nimplications must be captured and measured. With this data, engineering teams\ncan compare and assess design alternatives to arrive at optimal solutions. <\/p>\n\n\n\n
Cross-domain Integration<\/h3>\n\n\n\n
Automated wiring synthesis, cost analysis, and other capabilities within the platform context can\u2019t exist in isolation – they must form part of an overall flow (figure 2).<\/p>\n\n\n\n Data inputs are needed to drive the automated synthesis process that\ngenerates outputs, such as wiring and architectural designs, to feed into downstream\ntools and processes. The data comes from design domains that are undergoing\nchange. The automated synthesis must take this data and generate outputs that\ncomply with the design requirements and any relevant standards. At this stage,\nthe team can employ their existing knowledge and expertise to assess and\nvalidate the correctness of the design. Then, control can be exerted over the\nautomated process to enhance its accuracy.<\/p>\n\n\n\n Changes come into the synthesis solution from various inputs including\nthe bundle topology, logical system design, marketing requirements, and device\ninterface properties. Wiring synthesis must combine these inputs to generate\noutputs in the form of synthesized wiring designs. Tight integrations with the entire\nE\/E and vehicle engineering flow allows engineering teams to use the\nsynthesized data, including wiring diagrams, in downstream processes such as\nmanufacturing design and the creation of service documentation.<\/p>\n\n\n\n The whole process is driven by\nre-usable and configurable rules. These control every aspect of the automation\nand ensure compliance with marketing, manufacturing and certification\nrequirements. The engineering teams can also use configurable metrics to\nmeasure and assess designs, providing insight into the impact of changes or\nalternative implementations.<\/p>\n\n\n\n Finally, generative design supports\nextensive design data reuse. To reduce cycle-time and development costs, engineering\nteams should re-use as much validated data as possible. Integrating existing\ndesigns into the platform context reduces the volume of work by eliminating the\nneed to design new systems or sub-systems to serve a given function. Reuse also\nremoves the need to verify the functionality of a new design. <\/p>\n\n\n\n Therefore, once a system design is\nvalidated and released, the design must be captured and made re-usable across\nmultiple platforms without the need for platform-driven changes. In addition to\ndesigns, it is important that settings, requirements, and other process\ncontrols are re-usable and transferrable across domains and designs. Highly\nautomated processes need sophisticated controls to ensure repeatable results\nthat meet business standards and needs. These controls can be created by capturing the expertise of engineers\ninto instructions or constraints that force or restrict the behaviour of\nautomated design systems. <\/p>\n\n\n\n Change in the automotive industry\nis only accelerating. Growing automotive complexity, tight budgets, and\nfrequent design change combine to make automotive E\/E systems design incredibly\nchallenging. Engineering teams need a new design methodology to cope with the\npressures inherent in modern automotive design. <\/p>\n\n\n\n Design automation, a holistic platform context, and seamless integration between design tools are essential to empowering engineering teams to design accurate, optimized designs under budget and on schedule. In addition, this new design methodology equips engineers to manage the staggering complexity of modern E\/E systems. With a generative design flow, teams can ensure that the design supports all possible vehicle configurations, integrate new systems without additional workers, manage dozens of multi-domain change orders, and optimize the entire system for functionality and profitability.<\/p>\n\n\n\n![\"\"](\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/24\/2020\/02\/Fig-2-Bringing-it-all-together-1024x576.jpg\")
Reusable Design Data <\/h3>\n\n\n\n
Summary<\/h4>\n\n\n\n