I think most of the people commenting here have no experience on the leadership side of a large, complex software project (from either side of the table, consultant or customer). Let alone, what's involved in an RFP or vendor/consultant selection process (again, from either side).

A project like this will stress the capabilities of even the most competent management and execution teams, and are simply beyond the capabilities of any one person (yes, even the armchair experts posting here).

Technology is rarely the issue (these problems get solved). Things like the internal politics and culture are among the real problems - they are hard to manage, and are always unique in each organization.

To boil this down to "SAP Sucks" or "Consultants Suck" is ridiculous and unhelpful.

In the interest of accuracy, this is not MES.

MES = Manufacturing Execution Systems. MES systems connect ERP systems (such as SAP) to Plant Floor Control Systems (typically implemented using PLC or DCS systems, and a wide array of configurable off-the-shelf software applications.)

SematicIT, specifically, is a sequence and logic engine that is typically installed across several servers. You use the SematicIT logic to join systems that don't know/understand each other. I can buy a Blender from Manufacturer A, and connect it to a Weigh-Scale from Manufacturer B, and use SematicIT to make them work together (say, transfer setpoints and collect/store report data and then send that information up to SAP to update my inventory and WIP).

The ECU is just an embedded system. Siemens has experience with embedded systems because of the other components they manufacture (such as the PLCs that do actual plant floor control) as well as numberous consumer products.

As many people know, Microsoft has been moving towards embedded systems for years. This is just another step. Automotive companies have used racing as a way to develop and imporve technology for years -- it's good and interesting to see software companies trying the same thing.