I noted the reference to the Formula 1 racing application of DE on pages 10-11.
"Let’s use a real-life example where real lives depend on the answer: Formula 1 Racing. Highly competitive, this sport seeks every opportunity to gain even the slightest performance edge. What makes a car design fast enough to win is not simply answered. Aerodynamics, mass, engine torque, turn handling, even tire interaction with the road, all contribute as functions of speed and acceleration. Then there are driver preferences to consider, and the list goes on. You can see why teams historically do not know their true performance until their prototypes hit the track. Today, there are no prototypes in Formula 1, not physical ones anyway. Every aspect of future cars — from parts and assembly; to the complicated physics of material interactions, engine combustion, and even tire deformation; to maintenance across a grueling racing season — is meticulously modeled. These models, interconnected from upfront supplier specs to backend logistics, form one digital thread. And this digital thread is used to eCreate millions of eCars in pursuit of a winning design.
Only one physical racecar is ever built — the final car — which hits the track only two weeks later. ”Fly before you Buy” no longer exists in Formula 1: digital acquisition made it completely obsolete. Taking the hint from Morpheus, “…speed is still based on a world that is built on rules.” Digitally recreate that world, and you can create, iterate, and eventually dominate its speed, as real-world checkered flags attest."
Does anyone have more information on there application? Questions arise. For example, looking at a Bill of Materials or list of sub systems, is everything created in two weeks or are there long lead time items that must be addressed? Any suggestions or comments are welcome.