Company's History and Growth: Strengths
Company's History and Growth: Strengths
SWOT analysis
Ford Motor Company (Ford) is one of the largest automotive manufacturers in the
world. The company's automotive vehicle brands include Aston Martin, Ford, Jaguar,
Land Rover, Lincoln, Mazda, Mercury and Volvo. The company manufactures and
distributes automobiles in 200 markets across six continents. The Ford Asia, Africa
and Ford Mazda operations recorded strong performance in fiscal 2005. Strong Ford
Asia, Africa and Ford Mazda could prove to be a significant revenue and profit driver
in the coming years. Intense competition from Japanese companies, however, could
lead to further deterioration in the North American operations of Ford.
Strengths
Weaknesses
Opportunities
Hybrid vehicles:
By 2010, more than half of Ford, Lincoln and Mercury products are expected to switch
over to hybrid electric engines. Ford is planning to expand its capacity to produce up
to a quarter of a million hybrid vehicles a year. Demand for hybrid vehicles is
increasing worldwide owing to stringent emission standards, higher fuel prices and
growing environment-consciousness. Hybrid engines are more fuel efficient and less
polluting than conventional gasoline and diesel engines. Ford's focus on hybrid
electric vehicles could help in turning around its North American operations.
Threats
Increasing competition:
Ford's market share in the US light vehicle market has declined from 22.8% in 2001 to
18.2% in 2005 thanks to competition from Japanese companies among other
reasons. Ford is facing intense competition from Japanese vehicle manufacturers
such as Toyota and Honda. Toyota's share of US light vehicle market has risen from
10% in 2001 to 13% in 2005, while Honda's share has improved from 6.9% in 2001 to
8.4% in 2005. Nissan, another Japanese competitor, improved its market share from
4.1% to 6.2% during the same period. After establishing a strong market position in
the passenger cars segment, Japanese companies are now eyeing the lucrative light
trucks segment. Toyota, for instance, is aggressively pursuing market share in the
light trucks segment through its Tundra range of trucks. Intense competition from
Japanese companies could lead to further deterioration in the North American
operations of Ford.
Recession:
The financial crisis from 2007 to the present is considered by many economists to be the
worst financial crisis since the Great Depression of the 1930s. It contributed to the failure
of key businesses, declines in consumer wealth estimated in the trillions of U.S. dollars,
substantial financial commitments incurred by governments, and a significant decline in
economic activity. America giant auto makers are facing bankruptcy.
Analysis
The most critical part that Ford has to tackle effectively is the weakening North American
automotive operations. There are two basic ways to solve this problem:
1. Web Technologies
2. Knowledge Management
Web Technologies
Advantages:
Disadvantages:
Knowledge Management
Advantages:
Disadvantages:
Product Development at Ford involves three major stages, leading up to the manufacture
of the vehicle:
Planning is the first stage of product development, where customer/market wants &
program scope are identified, timing plans developed and engineering team is named.
The engineering team develops the target cascade and the initial design / verification
plans. The design stage involves the designing of the components, systems and vehicle to
meet the pre-determined requirements. The Verification process makes assessment on
the designs and verifies/documents that they meet or exceed the requirements. Making
the product involves manufacture of the components and assembling the vehicle.
Managing product verification costs contributes both to the top-line growth of the
automotive business (through improved quality and increased sales) and to the bottom-
line growth of the company (through cost reductions, thereby enhancing shareholder
value). Ford management seeking to improve both shareholder value and product quality
targeted the product verification process and commissioned a team to review the
corporate verification strategy (with Mckinsey & company as consultants). This team
developed the verification strategy, code named “Eureka”, which drove home the need
for KM within Ford.
Development of prototypes and physical testing of vehicles contributed to more than half
of product verification costs. Hence, the logical way to reduce costs was to reduce the
amount of testing, which also would reduce the number of prototypes required. Vehicle
testing could be reduced only through Re-Use of past verification information, increased
use of CAE (Computer-aided Engineering or computer simulation) and the rigorous
implementation of Systems Engineering principles (where components and systems were
individually tested and verified, thereby limiting total vehicle tests). These principles
became the corner stones of the Eureka Verification Strategy.
Re-use of prior product verification information, thus became a critical aspect of the
Verification Strategy. To successfully reuse legacy data, the data should be available
(stored), should be accessible (meta-data) and delivered to the user in the right format at
the right time (context). Decisions whether to carry-over a part or use anew parts,
historical quality and warranty metrics, development of the verification plan and use of
CAE or physical prototypes are made up-front in the product design process. The
product verification process was revised to accommodate additional decision making
steps, due to the incorporation of the re-use strategy and systems’ engineering principles.
The information and data needs of the new product verification process were supported
by Verification Product Information Management (VPIM). VPIM, therefore, focused not
on what Ford had in its databases but what it needed to have to optimize the design
engineering process.
VPIM is the complete management of all verification information (both physical and
analytical), to maximize customer satisfaction and product quality. VPIM integrates
engineering processes, business logic, web technology, and enables seamless integration
of multiple databases to manage verification information. The User interface to VPIM is
a Portal named myVerification Portal. myVerification Portal is a Web-enabled
Knowledge Management system that allows Ford engineers to Manage, Review,
Document and Sign-off on product verification deliverables based on requirements,
historical data and warranty issues.
Vehicle Requirements are set using generic requirements, historical verification reports,
Program Direction Letters, Failure Modes and Effects Analysis (FMEA), competitive tear
down studies, potential new technologies and warranty/reliability analysis to develop the
next generation vehicles that are more robust than the previous models and are best in
class in competition. The target cascade process takes the vehicle requirements and
breaks it down to the system, sub-system and component levels. The verification process
ensures that component/systems meet their targets individually and collectively in a
complete vehicle. The aim of the Verification PIM is to enable users to seamlessly access
relevant information from data repositories to reduce the time required to validate a
requirement by:
Streamlining the individual procedures in the process.
Enabling the "look" into different data repositories via user preferences.
Linking the requirements to verification methods/procedures, along with their
confidence
Maximizing reuse of historical data so that requirements can be signed off without
testing.
Integrate expert tools that can be used for "what-if" scenarios, enabling cross
attribute communication.
Automatic Archival of the information for reuse for the next generation.
Correlation between CAE & Test as well as CAE/Test & customer life cycles.
3. Strategy Endorsement
In May of 1999, Chief Technical Officer and VP, Mr. Neil Ressler, endorsed the
EUREKA Product Verification Strategy. This strategy included the proposal for
verification information knowledge management to facilitate reuse, as one of 7 key
elements. The knowledge base team from Eureka was reconstituted as Verification PIM
(VPIM) to implement the knowledge management within the Enterprise product
information management system.
4. VPIM Methodology
Business Objectives
VPIM, a key enabler to implement the Eureka Verification Strategy.
Enable re-use of CAE & Test information (from data elements to complete sign
off)(Eureka identified $6 Million savings in Verification costs for Durability
Attribute)
Use workflow to streamline the product verification process and reduce time to
market.
Create an "Umbrella" structure to manage ALL product verification information.
Ensure linking of CAD, CAE and Test data to customer requirements.
Easy, automated storage/archival of test & CAE information.
Create efficiencies through the elimination of Design and Release (D&R)
Engineers aimlessly searching for information.
Provide the end user (D&R) all information required to make engineering
decisions
Provide information in the context and steps that an engineer can easily complete
a task/deliverable.
Document and track current CAE/Test capabilities and facilitate prioritization of
future development.
Implement a robust knowledge management process within PD and use the " best
" knowledge to make decisions
Process Deliverables
Technology Interface
Management Profiles would generate a birds-eye view of the process, current state of the
requirements (red/yellow/green), graphical representation of the "program health" and
metrics documenting cost savings due to reuse of material, commodities & processes &
use of CAE or lab testing. The portal enables comparisons with historical programs and
the generation of reports where snapshots can be dragged-and-dropped into a
collaboration folder.
myVerification Portal is the user interface to the customers of verification PIM. The key
customers are D&R Engineers, CAE & Attribute engineers, Test Engineers and
Management.
Engineering User
The portal provides the relevant information to the user, using a sophisticated set of
personalization and customization rules using LDAP and preferences. The mapping also
can reflect the deliverables of the milestone - early milestones would place more
emphasis on Expert Tools and CAE and after prototype build, they would have full
vehicle tests. There are several different ways to navigate through the process - hierarchy,
blocks based on set preferences or navigation map. Charting and process flow definitions
using NetCharts from Visual Mining are used to depict Metrics to check on the
robustness of the process and data validity studies. A salient feature of the portal
implementation is that "ease of use" takes precedence to "functionality". Constant and
critical reviews of the development with the engineering community ensured that the end
product will be used exclusively to conduct verification business on the programs.
Management User
1. Metrics to assess the state of "Program Health", along with associated risk.
2. Summary information Product Verification Status, with access to detailed
information, if necessary.
3. Metrics to measure cost savings within Product Verification including.
1. Benefits
Business case developed for Verification PIM on Durability attribute for Suspension
system using the myVerification Portal showed significant gains, both to the user of the
tool (product engineers) and to the corporate stakeholders. These benefits are listed
below:
Tangible benefits
Intangible