1 option
An Open Versus Closed Architecture for Multimedia Systems Ford Motor Company
- Format:
- Book
- Conference/Event
- Author/Creator:
- Robinson, Ralph L., author.
- Conference Name:
- Convergence 2000 International Congress on Transportation Electronics (2000-10-16 : Detroit, Michigan, United States)
- Language:
- English
- Physical Description:
- 1 online resource cm
- Place of Publication:
- Troy, MI Convergence Transportation Electronics Association 2000
- Summary:
- For many years, carmakers have developed unique system designsto gain a competitive advantage using some unique technology or anoptimization of a design to cut costs or improve quality. Thisleads to continual increase in complexity, long development timesand high development costs.A common platform, based on an "openarchitecture,'' provides a solution for many of theproblems associated with the conventional automotive approach toelectrical/electronic system designs. The PC industry is a primeexample of how an open architecture can provide benefits to theconsumer, manufacturers of software and hardware components, aswell as complete system integrators.The PC, based on the initial IBM computer developed in the earlyeighties, has become a de facto standard that has survived 20 yearsof fast and dramatic changes in the fundamental technologies usedwithin the platform.The carmakers have come together to develop an "openarchitecture'' for the new rapidly growing multimedia,telematics and communication systems for in-car use. Thedevelopment of this new architecture is intended to meet the everchanging customer demands by shortening time-to-market of newcomponents, broadening available feature choices and providing amethod to easily upgrade older vehicles which have obsoletetechnologies.The Automotive Multimedia Interface Collaboration (AMI-C),comprised of 12 car manufacturers, is working to develop an openarchitecture using interface standards and specifications formultimedia, telematics and navigation systems.The resulting AMI-C architecture will include requirements andspecifications for software interfaces, networking protocols,network gateways, APIs, physical connectors, packaging, andenvironmental specifications
- Notes:
- Vendor supplied data
- Publisher Number:
- 2000-01-C065
- Access Restriction:
- Restricted for use by site license
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.