Specifications

Windows Embedded Automotive 7 Deep Dive: Phone Core and Media Core 5
stations, make or answer phone calls, and more. By supporting complex grammar, UVO needs
only short voice commands to connect drivers and passengers with their desired functions. An
interactive system, UVO responds to inquiries such as “What’s playing?” and provides audible
responses and related functions, allowing drivers to stay safely focused on the road.
Fiat
Fiat Blue&Me empowers customers to connect their personal mobile
devices with the integrated solution found in many vehicle models from
Fiat, Alfa Romeo, Lancia, Iveco, and Fiat Light Commercial Vehicles. First presented in 2006,
Blue&Me was originally developed as an infotainment system capable of allowing mobile
phones and MP3 players to be used in the car safely with voice-recognition commands and
steering wheel controls.
In 2008, the system evolved further with the introduction of eco:Drive, a free application
exclusive to Fiat that helps drivers understand how their driving style can affect consumption
and CO2 emissions. Fiat continues to press forward with development of the Blue&Me system,
from Blue&Me Nav to TomTom integration, from Nokia Ovi integration to eco:Drive―numerous
applications continue to make Fiat Blue&Me an international success.
And More!
Microsoft is also partnering with other automobile manufacturers and original equipment
manufacturers (OEMs), such as Chrysler, PACCAR, and Alpine, to bring new Windows Embedded
Automotive–powered products to market.
With a proven track record of deployed products, Automotive 7 provides a flexible, mature
platform for OEMs, centered on Phone Core and Media Core components.
Simplified UI Development with Silverlight for Windows Embedded
Today’s consumers expect a compelling user experience (UX), but creating these user
experiences can consume a lot of time and resources.
Typically, Human-Machine Interface (HMI) design follows these steps:
1. Create the design using Adobe Photoshop and Microsoft PowerPoint.
2. Define the HMI behavior in Microsoft Excel worksheets and Microsoft Word documents.
3. Roll the design and behavior into a rapid prototype (in Adobe Flash, for example).
4. Build the prototypes into an actual HMI.
Essentially, the work is being done twice: once by the designer and again by the developer. This
system also adds delays and imposes additional risk. After the developer re-creates the UX code,
the back-end code must be created as well (or at least enough of the code must be created to
get the HMI running). It is only at this point that the HMI can be reviewed. If there is a problem,
the HMI goes back to the developer to be corrected; if the UX designer created an interface that
is not practical, the cycle may need to start over from the beginning.
With Microsoft Silverlight for Windows Embedded, a new design/develop paradigm is possible: