OnStar System for Cadillac
Case Study for the
Operational Phase of the Life Cycle
Dennis Buede
Department of Systems Engineering and Operations Research
George Mason University
Fairfax, VA 22030-4444
703 993-1727
[email protected]
 1995-2000, Dennis Buede
1
Table of Contents
1.0 INTRODUCTION
2.0 ONSTAR SYSTEM OPERATIONAL PHASE SCENARIOS
3.0 ONSTAR EXTERNAL OPERATIONAL PHASE SYSTEM DIAGRAMS
4.0 ONSTAR SYSTEM FUNDAMANTAL OBJECTIVES
5.0 ONSTAR SYSTEM OPERATIONAL PHASE REQUIREMENTS DOCUMENT
6.0 FUNCTIONAL ARCHITECTURE FOR OPERATIONAL PHASE
7.0 PHYSICAL ARCHITECTURE
8.0 OPERATIONAL ARCHITECTURE
 1995-2000, Dennis Buede
2
1.0
Introduction
The OnStar system is an information system for Cadillac owners to provide emergency
help and a wide range of support. Generally, the operational concept involves a satellite
communication link between the car and a control center run by Cadillac.
The Systems Engineering team that was assembled by Cadillac has developed an
operational concept, external systems diagram, and requirements that address the
operational phase of the OnStar system lifecycle.
2.0
OnStar System Operational Phase Scenarios
User Scenarios
Request f or
directions
1) Driver uses cellular phone to contact control center to
find directions.
a) Driver pushes ia single button on the OnStar cellular
phone.
b) OnStar calls the control center.
c) Control center person responds and inquires where
driver wants to go via the OnStar cellular phone.
d) Driver responds with location (tourist landmark,
restaurant, hotel, ATM, Cadillac dealer, and gas
station) via the OnStar cellular phone.
e) Control center person responds with address and block
by block directions via the OnStar cellular phone.
f) Driver uses OnStar to record these directions and plays
them back as needed.
User request
f or directions
Request
f or location
Where to?
Location to
go to
Request f or
audio directions
Audio
directions
Request to
record directions
Request to play
back directions
Audio replay
of directions
User
2) Driver loses car in parking lot.
a) Driver calls control center using a tollfree number from a pay phone.
b) Control center person sends signal to
OnStar.
c) OnStar activates flashing lights and
honking horn on Driver’s car.
d) Driver goes to car and deactivates light
and horn.
Car lost
Instructions
for light
and horn
Signal to
activate
light and horn
Flashing
horn and lights
Lights and horn off
User
 1995-2000, Dennis Buede
Control
Center
OnStar
Control
Center
Signal to
deactivate
light and horn
OnStar
Car
3
3) Driver locks keys in car.
a) Driver calls control center using a
toll-free number from a pay phone.
b) Control center person sends signal to
OnStar.
c) OnStar deactivates flashing lights
and horn.
d) Driver goes to car and deactivates
lights and horn.
Car locked
Instructions
to unlock car
Signal to
unlock car
Light and horn off
Signal to deactivate
lights and horn
User
4) Emergency support when accident occurs.
a) Car is involved in an accident in
which the air bags are activated.
b) OnStar sends a priority signal to the
control center with the exact location.
c) Control center person calls driver on
the OnStar cellular phone.
d) If contact is not made, control center
person contacts appropriate 911
number (context).
User
e) Control center person provides
information on driver’s location, car,
and license number (context).
f) Police respond to driver (context).
OnStar
Control
Center
Car
Airbag signal
Accident
location
Attempt to
reach driver
Call for accident
No user response
Control
Center
OnStar
Car
5) Vandals/thieves break into driver’s car
Security
and steal the car.
system signal
a) Vandals/thieves break into driver’s car
Car stolen
and drive car away (context).
b) The security system of car is activated
and sends a signal to OnStar.
Tracking signal
c) OnStar sends a signal to the control
center.
Control
d) The control center person calls 911
OnStar
Car
User
Center
and reports the break-in and provides
information on the driver’s car to the police (context).
e) OnStar sends signals to the control center allowing the car to be tracked.
f) The control center person provides this tracking information to the police
(context).
 1995-2000, Dennis Buede
4
6) Car jackers steal car and kidnap driver and passengers.
a) Thieves carjack the car with the driver and possibly passengers (context).
b) Driver pushes a red button on the cellular phone.
Car jacking
Notice of
c) OnStar sends a car jacking signal to the control
car jacking
center with an open phone line so that any
Tracking signal
conversations can be monitored.
d) OnStar sends signals to the control center
Phone link
allowing the car to be tracked.
e) The control center provides information about the
User
OnStar
Control
location of the car to police (context).
Center
7) OnStar is deactivated.
a) OnStar receives its power from the car’s battery.
b) The car’s battery is dead or disconnected causing the
deactivation of OnStar.
Car
Maintainer Scenarios
1) Maintainer checks emergency car jacking capability.
a) Maintainer tests emergency button on the cellular
phone to determine that contact with the control
center is made. If test show a problem, adjustments
are made or cellular phone is replaced to correct any
deficiencies.
b) Maintainer tests link to control center to make sure
conversation can be heard and that car’s location is
transmitted. Adjustments or replacements are made
as necessary to correct any deficiencies.
Pow er
Test of cellular
phone
OnStar
Test of phone link
Test results f or
cellular phone
Test diagnostics phone
Adjustments f or
cellular phone
Control center
link test
Request f or control
center link test
Test results f or
conv ersation
Test results f or
tracking signal
Test diagnostics conv ersation
Test diagnostics tracking signal
Adjustments f or
conv ersation
Adjustments f or
tracking signal
Maintainer
 1995-2000, Dennis Buede
OnStar
Control
Center
5
2) Maintainer tests ability of OnStar to unlock car.
a) Maintainer checks that unlock signal is
received by OnStar.
b) Maintainer checks that OnStar unlocking
signal is activated when control center
unlock signal is received.
c) Maintainer checks that car locks are
unlocked when OnStar unlocking signal is
sent.
d) Maintainer makes repairs as needed.
Request test of unlock feature
Test instructions
for unlock feature
Test signal to unlock car
Test results for unlock feature
Adjustment for
for unlock feature
Maintainer
 1995-2000, Dennis Buede
OnStar
Control
Center
Car
6
3.0
OnStar System Operational Phase External Systems Diagram
USED AT:
George Mason
University
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
x
DATE: 08/15/00
REV:
NOTES: 1 2 3 4 5 6 7 8 9 10
Request for directions,
Location to go to,
Request to record directions,
Request to play directions,
Lights and horn off,
Car jacking
Request for location,
Audio directions, Instructions
for lights and horn, Instructions to
unlock car, Attempt to reach driver,
Test results for cellular phone,
Test results for conversation,
Test results for tracking signal
Use
On-Star
Car lost,
Car locked
Test instructions
for unlock feature
Signal to activate
lights and horn,
Signal to
unlock car,
Signal to
deactivate
lights and horn,
Test signal to
unlock car
USED AT:
George Mason
University
Test results
for unlock
signal
A-0
Test of cellular
phone,
Adjustments for
cellular phone,
Control center
link test,
Adjustments for
tracking signal,
Adjustments for
conversation,
Adjustments for
unlock feature
A-13
Maintain
On-Star
System
Air bag signal,
Security system
signal, Power
Control
Center
User
On-Star
System
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
Car
x
DATE: 08/15/00
REV:
NOTES: 1 2 3 4 5 6 7 8 9 10
A-14
Flashing
horn and
lights
Test diagnostics - phone,
Test diag. - tracking signal,
Test diag. - conversation
TITLE: Cadillac On-Star System Operational Phase External System
A-1
Maintainer
feedback
Provide
OnStar
Capability
Perform
Car
Functions
User request for directions,
Request for audio directions,
Accident location, No user
response, Car stolen,
Notice of car jacking,
Tracking signal, Phone
link, Test of phone link,
Request for control center
link test
NODE:
None
User Feedback
A-12
Where to?,
Audio replay
of directions,
Call for accident
DATE CONTEXT:
READER
Cadillac Policies
and Procedures
Control
Center
feedback
Perform
Control
Center
Operations
A-11
WORKING
DRAFT
RECOMMENDED
PUBLICATION
WORKING
DRAFT
RECOMMENDED
PUBLICATION
Request test
of unlock
feature
Maintainer
NUMBER:
P. 1
DATE CONTEXT:
READER
Top
Cadillac Policies
and Procedures
User Feedback
Request for directions,
Location to go to,
Request to record directions,
Request to play directions,
Lights and horn off,
Car jacking
Control
Center
feedback
Where to?,
Audio replay
of directions,
Call for accident
Request for location,
Audio directions, Instructions
for lights and horn, Instructions to
unlock car, Attempt to reach driver,
Test results for cellular phone,
Test results for conversation,
Test results for tracking signal
Signal to activate
lights and horn,
Signal to
unlock car,
Signal to
deactivate
lights and horn,
Test signal to
unlock car
Provide
OnStar
Capabilities
Test instructions
for unlock feature
A0
Test of cellular
phone,
Adjustments for
cellular phone,
Control center
link test,
Adjustments for
tracking signal,
Adjustments for
conversation,
Adjustments for
unlock feature
User request for directions,
Request for audio directions,
Accident location, No user
response, Car stolen,
Notice of car jacking,
Tracking signal, Phone
link, Test of phone link,
Request for control center
link test
Maintainer
feedback
Air bag signal,
Security system
signal, Power
On-Star
System
Test diagnostics - phone,
Test diag. - tracking signal,
Test diag. - conversation
PURPOSE: To describe the Operational Phase for the Cadillac OnStar System
VIEWPOINT: The Systems Engineering Team
NODE:
A-0
TITLE:
 1995-2000, Dennis Buede
Provide OnStar Capability
NUMBER:
P. 2
7
4.0 OnStar System Fundamental Objectives
The following diagram summarizes the fundamental objectives for the OnStar System:
ON-Star System - Fundamentals Objectives Hierarchy
Operational
Objectives
Monthly Operating Costs
$15 to $20, Wt = 0.2
Operating Performance
Objectives, Wt = 0.8
User ability to operate from reading User
Manual. 20 - 30 minutes. Wt = 0.25
Reliability of On-Star to receive its
intended inputs. Wt = 0.25
Air bags signal, 95-99%, Wt=0.40
Security system signal, 95-99%, Wt=0.40
Lights/horn off, 85-90%, Wt=0.10
Time for On-Star to process its intended
inputs. Wt = 0.25
User request for directions, 5 - 10 sec,
Wt= 0.10
Inst. for lights&horn 20 - 30sec, Wt = 0.15
Inst.. to unlock car, 20 - 30 sec, Wt = 0.15
Airbag signal, 2- 3 sec, Wt = 0.20
Carjacking, 2 - 3 sec, Wt = 0.20
Security system signal, 5 - 10 sec, Wt =
0.20
Reliability of On-Star to provide its
intended outputs. Wt = 0.25
Tracking Signals, 95-99%, Wt=0.25
Audio Directions, 85-90%, Wt=0.05
Signal for Lights/Horn, 90-95%, Wt=0.10
Signal to Unlock Car, 90-95%, Wt=0..10
Notice of Carjacking, 95-99%, Wt=0.15
Accident Location, 95-99%, Wt=0.15
Car Stolen, 95-99%, Wt=0.15
Signal to Deactivate Lights/Horn,
85-90%,Wt=0.05
 1995-2000, Dennis Buede
8
5.0
OnStar Operational Phase Requirements Document
5.1
Input/Output Requirements
5.1.1 Input Requirements
5.1.1.1 The OnStar system shall be able to accept a request from the user to contact the
Control Center to ask for directions.
5.1.1.2 The OnStar system shall be able to accept a request from the Control Center to
ask the User for the location they want to go to.
5.1.1.3 The OnStar system shall be able to accept the location the user wants to go to.
5.1.1.4 The OnStar system shall be able to accept a request from the user to record
directions from the Control Center.
5.1.1.5 The OnStar system shall be able to record audio directions received from the
Control Center.
5.1.1.6 The OnStar system shall be able to accept a request from the user to play back the
audio directions.
5.1.1.7 The OnStar system shall be able to accept instructions from the Control Center to
turn on flashing lights and sound the horn.
5.1.1.8 The OnStar system shall be able to accept instructions from the Control Center to
unlock the car.
5.1.1.9 The OnStar system shall be able to accept a signal from the air bag when the air
bags are activated.
5.1.1.9.1 The OnStar system shall be able to perform this function 95% of the time. The
design goal is 99% of the time.
5.1.1.10 The OnStar system shall be able to accept a request from the Control Center to
contact the User to verify if there is an accident.
5.1.1.11 The OnStar system shall be able to accept a signal from the security system
when the security system is activated.
5.1.1.11.1 The OnStar system shall be able to perform this function 95% of the time. The
design goal is 99% of the time.
 1995-2000, Dennis Buede
9
5.1.1.12 The OnStar system shall be able to accept a signal from the user that a car
jacking has occurred.
5.1.1.13 The OnStar system shall be able to accept power from the car’s battery to
perform its intended functions.
5.1.1.14 The OnStar system shall be able to accept a signal from the user to turn off the
flashing lights and horn.
5.1.1.14.1 The OnStar system shall be able to perform this function 85% of the time. The
design goal is 90% of the time.
5.1.1.15 Input from the Maintainer.
5.1.1.15.1 The OnStar system shall be able to accept input from the Maintainer to test the
cellular phone.
5.1.1.15.2 The OnStar system shall be able to accept input from the Maintainer to test the
link with the Control Center.
5.1.1.15.3 The OnStar system shall be able to accept test results from the Control Center
to test the operation of the cellular phone.
5.1.1.15.4 The OnStar system shall be able to accept test results from the Control Center
to test conversation with the Control Center.
5.1.1.15.5 The OnStar system shall be able to accept adjustments from the Maintainer to
correct problems with the cellular phone.
5.1.1.15.6 The OnStar system shall be able to accept adjustments from the Maintainer to
correct problems with the conversation with the Control Center.
5.1.1.15.7 The OnStar system shall be able to accept adjustments from the Maintainer
correct problems with sending tracking signals to the Control Center.
5.1.1.15.8 The OnStar system shall be able to accept test instructions from the Control
Center to unlock the car.
5.1.1.15.9 The OnStar system shall be able to accept test results from the for the unlock
feature test.
5.1.1.15.10 The OnStar system shall be able to accept adjustments from the Maintainer to
correct problems with the unlock feature.
 1995-2000, Dennis Buede
10
5.1.2 Output Requirements
5.1.2.1 The OnStar system shall call the Control Center after the user makes a request for
directions.
5.1.2.1.1 The OnStar system shall be able to perform this function within 10 seconds
after the user makes the request. The design goal is 5 seconds.
5.1.2.2 The OnStar system shall instruct the user to provide the location the user wants to
go to.
5.1.2.3 The OnStar system shall be able to request audio directions from the Control
Center for the location provided by the user.
5.1.2.4 The OnStar system shall be able to replay audio directions received from the
Control Center.
5.1.2.4.1 The OnStar system shall be able to perform this function 85% of the time. The
design goal is 90% of the time.
5.1.2.5 The OnStar system shall be able to send a signal to activate the flashing lights and
sound the horn after instructions are received from the Control Center.
5.1.2.5.1 The OnStar system shall be able to perform this function within 30 seconds
after the signal is received. The design goal is 20 seconds.
5.1.2.5.2 The OnStar system shall be able to perform this function 95% of the time. The
design goal is 90% of the time.
5.1.2.6 The OnStar system shall be able to send a signal to unlock the car after
instructions are received from the Control Center.
5.1.2.6.1 The OnStar system shall be able to perform this function within 30 seconds
after the signal is received. The design goal is 20 seconds.
5.1.2.6.2 The OnStar system shall be able to perform this function 95% of the time. The
design goal is 90% of the time.
5.1.2.7 The OnStar system shall be able to notify the Control Center that a car jacking has
occurred after OnStar receives a signal from the user.
5.1.2.7.1 The OnStar system shall be able to perform this function within 3 seconds after
the signal is received. The design goal is 2 seconds.
5.1.2.7.2 The OnStar system shall be able to perform this function 95% of the time. The
design goal is 99% of the time.
 1995-2000, Dennis Buede
11
5.1.2.8 The OnStar system shall be able to send a priority signal with the exact location
of the car to the Control Center after OnStar receives a signal from the airbag.
5.1.2.8.1 The OnStar system shall be able to perform this function within 3 seconds after
the signal is received. The design goal is 2 seconds.
5.1.2.8.2 The OnStar system shall be able to perform this function 95% of the time. The
design goal is 99% of the time.
5.1.2.9 The OnStar system shall attempt to call the user to verify that an accident has
occurred.
5.1.2.10 The OnStar system shall notify the Control Center if there is no response from
the user.
5.1.2.11 The OnStar system shall be able to notify the Control Center that the car has
been stolen after OnStar receives a signal from the security system.
5.1.2.11.1 The OnStar system shall be able to perform this function within 10 seconds
after the signal is received. The design goal is 5 seconds.
5.1.2.11.2 The OnStar system shall be able to perform this function 95% of the time. The
design goal is 99% of the time.
5.1.2.12 The OnStar system shall be able to establish a phone link with the Control
Center to allow conversations to be monitored.
5.1.2.13 The OnStar system shall be able to send tracking signals to the Control Center to
allow the Control Center to locate the car.
5.1.2.13.1 The OnStar system shall be able to perform this function 95% of the time. The
design goal is 99% of the time.
5.1.2.14 The OnStar system shall deactivate the lights and horn when OnStar gets request
from the user to turn off the lights and horn.
5.1.2.14.1 The OnStar system shall be able to perform this function 85% of the time. The
design goal is 90% of the time.
5.1.2.15 Output to Maintainer.
5.1.2.15.1 The OnStar system shall provide test diagnostics to the Maintainer for the
operation of the cellular phone.
 1995-2000, Dennis Buede
12
5.1.2.15.2 The OnStar system shall provide test diagnostics to the Maintainer for the
conversation between the user and the Control Center.
5.1.2.15.3 The OnStar system shall provide test diagnostics to the Maintainer for the
tracking signals sent to the Control Center to locate the car.
5.1.2.15.4 The OnStar system shall send a request to the Control Center to test the
conversation with OnStar.
5.1.2.15.5 The OnStar system shall send a request to the Control Center to test the phone
link for emergency situations.
5.1.2.15.6 The OnStar system shall send a request to the Control Center to allow the
Maintainer to test the link with the Control Center.
5.1.2.15.7 The OnStar system shall send a test signal to unlock the car after it receives
test instructions from the Control Center.
5.1.2.16 Feedback
5.1.2.16.1 The OnStar system shall provide feedback to the User about the operation of
the OnStar system.
5.1.2.16.2 The OnStar system shall provide feedback to the Control Center about the
operation of the OnStar system.
5.1.2.16.3 The OnStar system shall provide feedback to the Maintainer about the
maintenance of the OnStar system.
5.1.3 Interface Requirements
5.1.3.1 OnStar shall interface with a cellular network to provide OnStar cellular phone
communications.
5.1.3.2 OnStar shall interface with a location system like the Global Positioning System
(GPS) to find the location of the car.
5.1.4 Functional Requirements
5.1.4.1 The OnStar system shall accept user requests and provide feedback
5.1.4.2 The OnStar system shall determine OnStar responses to inputs received.
5.1.4.3 The OnStar system shall communicate with the Control Center
5.1.4.4 The OnStar system shall communicate with the car
 1995-2000, Dennis Buede
13
5.1.4.5 The OnStar system shall provide features to maintain the OnStar system.
5.2 System-Wide and Technology Requirements
5.2.1 OnStar shall remain in an operational state when the car is not being used.
5.2.2 OnStar shall provide easy to use features that will not impact the driver’s ability to
operate the car while using OnStar.
5.2.3 The operations of the OnStar system shall conform to Cadillac’s Policies and
Procedures.
5.2.4 The system MTBF shall be greater than 18 months. The design goal is 24 months.
Failure is defined to be the inability for OnStar to perform its intended functions.
5.2.5 The system MTTR shall be less than 4 hours. The design goal is 2 hours. Repair
means the system is returned to full operating capacity.
5.2.6 The purchase price of the system shall not exceed $1,000. The design goal is $900.
5.2.7 The monthly operating cost of the system shall not exceed $20.00 per month. The
design goal is $15.00 per month.
5.3 Trade-Off Requirements.
5.3.1 Performance Trade-Offs. The right side of the Operational Objectives Hierarchy
shows the relative weight of the performance requirements. The value curves for the
performance requirements are yet to be determined.
5.3.2 Cost Trade-Offs. The left side of the Operational Objectives Hierarchy shows the
relative weight of the cost requirement. The value curves for the cost requirement is yet
to be determined
5.3.3 Cost-Performance Trade-Offs. The relative weight of the cost and performance
requirements are 0.2 and 0.8, respectively.
 1995-2000, Dennis Buede
14
5.4 System Test Requirements.
5.4.1 Test Requirements.
5.4.1.1 The operation team shall verify requirement 5.1.1.9 by activating the airbags on
the car.
5.4.2 The operation team shall verify requirement 5.1.1.11 by activating the security
system on the car.
5.4.3 Verification Plan. The verification tests shall be done by inspection, test and
simulation.
5.4.4 Validation Plan. The validation tests shall examine each operating scenario ten
times with pre-production prototypes and must achieve success nine out of ten times.
5.4.5 Acceptance Plan. The acceptance tests shall be conducted by providing preproduction prototypes to twenty-five Cadillac owners. Twenty or more owners/testers
shall indicate they want OnStar.
 1995-2000, Dennis Buede
15
6.0 Functional Architecture for Operational Phase
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
USED AT:
George Mason
University
x
DATE: 08/15/00
REV:
NOTES: 1 2 3 4 5 6 7 8 9 10
WORKING
DRAFT
RECOMMENDED
PUBLICATION
DATE CONTEXT:
READER
Top
Cadillac Policies
and Procedures
User Feedback
Request for directions,
Location to go to,
Request to record directions,
Request to play directions,
Lights and horn off,
Car jacking
Control
Center
feedback
Where to?,
Audio replay
of directions,
Call for accident
Request for location,
Audio directions, Instructions
for lights and horn, Instructions to
unlock car, Attempt to reach driver,
Test results for cellular phone,
Test results for conversation,
Test results for tracking signal
Signal to activate
lights and horn,
Signal to
unlock car,
Signal to
deactivate
lights and horn,
Test signal to
unlock car
Provide
OnStar
Capabilities
Test instructions
for unlock feature
A0
Test of cellular
phone,
Adjustments for
cellular phone,
Control center
link test,
Adjustments for
tracking signal,
Adjustments for
conversation,
Adjustments for
unlock feature
User request for directions,
Request for audio directions,
Accident location, No user
response, Car stolen,
Notice of car jacking,
Tracking signal, Phone
link, Test of phone link,
Request for control center
link test
Maintainer
feedback
Air bag signal,
Security system
signal, Power
On-Star
System
Test diagnostics - phone,
Test diag. - tracking signal,
Test diag. - conversation
PURPOSE: To describe the Operational Phase for the Cadillac OnStar System
VIEWPOINT: The Systems Engineering Team
NODE:
TITLE:
A-0
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
USED AT:
George Mason
University
NUMBER:
Provide OnStar Capability
DATE: 08/15/00
REV:
x
NOTES: 1 2 3 4 5 6 7 8 9 10
Process Control
Policies
User Interface
Policies
Request for directions,
Location to go to,
Request to record directions,
Request to play directions,
Lights and horn off,
Car jacking
Power
Request for location,
Audio directions, Instructions
for lights and horn, Instructions to
unlock car, Attempt to reach driver,
Test results for cellular phone,
Test results for conversation,
Test results for tracking signal
Accept User
Requests &
Provide
Feedback
Communication
Policies
Audio replay
of directions
Determine
OnStar
Responses
Test instructions
for unlock feature
A2
Audio directions
for user, Call to user
for accident
Test of cellular
phone,
Adjustments for
cellular phone,
Control center
link test,
Adjustments for
tracking signal,
Adjustments for
conversation,
Adjustments for
unlock feature
Power
Power
Lights and horn on,
Request to unlock car,
Unlock feature test,
Request from user to
turn off lights and horn
Cellular phone test,
Tracking signal test,
Results of phone test,
Results of conversation test,
Results of tracking signal test,
Cellular phone adjustments,
Conversation adjustments,
Tracking signal adjustments,
Unlock feature adjustments
Air bag signal,
Security system
signal, Power
Power
READER
Cadillac Policies
and Procedures
Request from user for directions,
Location user wants to go to,
Request from user to record directions,
Request from user to play directions,
Request from user to turn off lights and horn,
Report from user of car jacking
A1
No response
from user
WORKING
DRAFT
RECOMMENDED
PUBLICATION
DATE
Car Interface
Standards
User Feedback
Maintenance
Policies
User
Feedback
Where to?,
Audio replay
of directions,
Call for accident
User requested directions,
CC request for location,
User location to go to,
CC Directions,
User request to record
directions,
User report of car jacking,
Airbag activated,
User unresponsive,
Security system activated,
Conv. Test, Unlock Test
Control
Center
feedback
Where to?,
Call for Accident
User request for directions,
Request for audio directions,
Accident location, No user
response, Car stolen,
Notice of car jacking,
Tracking signal, Phone
link, Test of phone link,
Request for control center
link test
Communicate
with Control
Center
A3
Signal to activate
lights and horn,
Signal to
unlock car,
Signal to
deactivate
lights and horn,
Test signal to
unlock car
Communicate
with
Car
A4
Maintain
On-Star
Maintainer
feedback
A5
NODE:
A0
TITLE:
 1995-2000, Dennis Buede
Provide OnStar Capabilities
P. 2
CONTEXT:
NUMBER:
Test diagnostics - phone,
Test diag. - tracking signal,
Test diag. - conversation
P. 3
16
USED AT:
George Mason
University
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
x
DATE: 08/15/00
REV:
WORKING
DRAFT
RECOMMENDED
PUBLICATION
NOTES: 1 2 3 4 5 6 7 8 9 10
DATE CONTEXT:
READER
User Interface
Policies
Acknowledgment of
request for directions
Accept User
Request for
Directions
Request for
Directions
Request from user
for directions
A11
Request for directions,
Location to go to,
Request to record directions,
Request to play directions,
Lights and horn off,
Car jacking
Acknowledgment of
user requests
Acknowledgment
that location
received
Accept
Location User
Wants to Go To
Location to
go to
User
Feedback
Audio replay
of directions
A12
Location user
wants to go to
Process
Audio
Directions
Audio directions
for user, Call to user
for accident
Request to
record directions,
Request to play
directions
Request from user for directions,
Location user wants to go to,
Request from user to record directions,
Request from user to play directions,
Request from user to turn off lights and horn,
Report from user of car jacking
A13
Request from user
to record directions,
Request from user to
play back directions
Accept User
Report of Car
Jacking
Audio directions
for user
A14
Car jacking
Report from user
of car jacking
Request from user to
turn off lights and horn
Accept User
Request to Turn
Off Lights and
Horn
A15
Call to user
for accident
Call User
After
Accident
Lights and horn off
No response
from user
A16
NODE:
TITLE:
A1
USED AT:
George Mason
University
NUMBER:
Accept User Requests & Provide Feedback
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
x
DATE: 08/15/00
REV:
WORKING
DRAFT
RECOMMENDED
PUBLICATION
NOTES: 1 2 3 4 5 6 7 8 9 10
P. 4
DATE CONTEXT:
READER
Process Control
Policies
Request from user for directions,
Location user wants to go to,
Request from user to record directions,
Request from user to play directions,
Request from user to turn off lights and horn,
Report from user of car jacking
No response
from user
Determine
Responses
to User
User requested directions,
User location to go to,
User request to record directions,
User report of car jacking,
User unresponsive
Determine
Responses
to Control
Center
Call to user
for accident
Air bag signal,
Security system
signal, Power
A2
Lights and horn on,
Request to unlock car,
No response from user
Determine
Responses
to Signals
from Car
Lights and horn on,
Request to unlock car,
Unlock feature test,
Request from user to
turn off lights and horn
Airbag activated,
Security system
activated
Results of phone test,
Results of conversation test,
Results of tracking signal test
A23
Test of cellular
phone,
Adjustments for
cellular phone,
Control center
link test,
Adjustments for
tracking signal,
Adjustments for
conversation,
Adjustments for
unlock feature
NODE:
CC request for
location,
CC directions,
Unlock test
A22
Test instructions
for unlock feature
User requested directions,
CC request for location,
User location to go to,
CC Directions,
User request to record
directions,
User report of car jacking,
Airbag activated,
User unresponsive,
Security system activated,
Conv. Test, Unlock Test
Request from user to
turn off lights and horn
A21
Request for location,
Audio directions, Instructions
for lights and horn, Instructions to
unlock car, Attempt to reach driver,
Test results for cellular phone,
Test results for conversation,
Test results for tracking signal
Audio directions
for user, Call to user
for accident
Audio directions
for user
Unlock feature test
Determine
Responses
to
Maintainer
Conversation test
Cellular phone test,
Tracking signal test,
Results of phone test,
Results of conversation test,
Results of tracking signal test,
Cellular phone adjustments,
Conversation adjustments,
Tracking signal adjustments,
Unlock feature adjustments
A24
Cellular phone test,
Tracking signal test,
Cellular phone adjustments,
Conversation adjustments,
Tracking signal adjustments,
Unlock feature adjustments
TITLE:
 1995-2000, Dennis Buede
Determine OnStar Responses
NUMBER:
P. 6
17
USED AT:
George Mason
University
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
x
DATE: 08/15/00
REV:
NOTES: 1 2 3 4 5 6 7 8 9 10
Where to?
User requested directions,
CC request for location,
User location to go to,
CC directions, User request
to record directions
DATE CONTEXT:
READER
Communication
Policies
User request for directions,
Request for audio
directions
Communicate
User Request
for Directions
to CC
Where to?,
Call for Accident
A31
Notice of Car jacking,
Tracking signal,
Phone link
Communicate
User Report of
Car Jacking to
CC
User report
of car jacking
User requested directions,
CC request for location,
User location to go to,
CC Directions,
User request to record
directions,
User report of car jacking,
Airbag activated,
User unresponsive,
Security system activated,
Conv. Test, Unlock Test
WORKING
DRAFT
RECOMMENDED
PUBLICATION
Call for
Accident
A34
User request for directions,
Request for audio directions,
Accident location, No user
response, Car stolen,
Notice of car jacking,
Tracking signal, Phone
link, Test of phone link,
Request for control center
link test
Communicate
Notification of
Accident
Airbag activated,
User unresponsive
A32
Accident
location,
No user response
Car stolen,
Tracking signal,
Communicate
Notification
of Stolen Car
A35
Security system
activated
Test of phone link,
Request for control center
link test
Communicate
Test from
Maintainer
Conv. Test,
Unlock Test
A33
NODE:
TITLE:
A3
USED AT:
George Mason
University
NUMBER:
Communicate with Control Center
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
DATE: 08/15/00
REV:
NOTES: 1 2 3 4 5 6 7 8 9 10
x
WORKING
DRAFT
RECOMMENDED
PUBLICATION
READER
P. 7
DATE CONTEXT:
Car Interface
Standards
Ack. horn and light
signal received
Lights and
horn on
Control
Center
feedback
Communicate
Signal to Flash
Lights and
Sound Horn
Signal to activate
lights and horn
A41
Ack. unlock signal
received
Lights and horn on,
Request to unlock car,
Unlock feature test,
Request from user to
turn off lights and horn
Signal to activate
lights and horn,
Signal to
unlock car,
Signal to
deactivate
lights and horn,
Test signal to
unlock car
Communicate
Signal to
Unlock Car
A42
Request to
unlock car
Communicate
Signal to
Deactivate
Lights and Horn
Request from user to
turn off lights and horn
A43
Signal to unlock
car
Signal to
deactivate
lights and horn
Test signal to
unlock car
Communicate
Test of Unlock
Feature
A44
Unlock feature test
NODE:
A4
TITLE:
 1995-2000, Dennis Buede
Communicate with Car
NUMBER:
P. 8
18
USED AT:
George Mason
University
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
x
DATE: 08/15/00
REV:
NOTES: 1 2 3 4 5 6 7 8 9 10
WORKING
DRAFT
RECOMMENDED
PUBLICATION
READER
DATE CONTEXT:
Maintenance
Policies
Perform
Maintenance
Tests
Cellular phone test,
Tracking signal test
Cellular phone test,
Tracking signal test,
Results of phone test,
Results of conversation test,
Results of tracking signal test,
Cellular phone adjustments,
Conversation adjustments,
Tracking signal adjustments,
Unlock feature adjustments
A51
Feedback from
tests
Evaluate
Results of
Tests
Test diagnostics - phone,
Test diag. - tracking signal,
Test diag. - conversation
A52
Results of phone test,
Results of conversation,
Results of tracking signal test,
Test evaluation
feedback
Accept
Adjustments
for Problems
Maintainer
feedback
A53
Feedback from
adjustments
Cellular phone adjustments,
Conversation adjustments,
Tracking signal adjustments,
Unlock feature adjustments
NODE:
A5
TITLE:
 1995-2000, Dennis Buede
Maintain On-Star
NUMBER:
P. 9
19
7.0 Physical Architecture
7.1 Generic Physical Architecture for the ATM system
OnStar
System
User Interface
Module
OnStar Processor
Control Center
Communication
Module
Car
Communication
Module
Maintenance
Module
7.2 Instantiated Architectures based on the Morphological Box.
FEATURES
OPTIONS
User Interface
Monochrome text
with keyboard
entry.
Graphical interface
with touch screen
capability.
Voice input/output.
 1995-2000, Dennis Buede
OnStar Processor
CC Comm.
Module
Analog connection
Car Comm.
Module
Scan for inputs
every 30 seconds
Intel Pentium III
586 processor
Digital connection
Scan for inputs
every 15 seconds
Intel 733 Pentium
III processor
Dedicated
connection
Continuous
scanning for inputs
Celeron 586
processor
20
7.3 Instantiated Physical Architecture
Theme: low cost.
INSTANTIATED Architecture #1
Feature
User Interface
OnStar Processor
CC Communication Module
Car Communication Module
Option
Monochrome text with keyboard entry.
Celeron 586 processor.
Analog connection.
Scan for inputs every 30 seconds.
Theme: fast throughput with medium security.
INSTANTIATED Architecture #2
Feature
Option
Monochrome text with keyboard entry.
User Interface
Pentium III 733 processor.
OnStar Processor
Digital connection.
CC Communication Module
Continuous scanning for inputs.
Car Communication Module
Theme: User-friendly, medium cost, and high security.
INSTANTIATED Architecture #3
Feature
Option
Graphical interface with touch screen
User Interface
capability.
Pentium III 586 processor.
OnStar Processor
Dedicated connection.
CC Communication Module
Scan every 15 seconds for inputs.
Car Communication Module
 1995-2000, Dennis Buede
21
8.0 Operational Architecture
USED AT:
George Mason
University
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
x
DATE: 08/15/00
REV:
NOTES: 1 2 3 4 5 6 7 8 9 10
WORKING
DRAFT
RECOMMENDED
PUBLICATION
DATE CONTEXT:
READER
Top
Cadillac Policies
and Procedures
User Feedback
Request for directions,
Location to go to,
Request to record directions,
Request to play directions,
Lights and horn off,
Car jacking
Control
Center
feedback
Where to?,
Audio replay
of directions,
Call for accident
Request for location,
Audio directions, Instructions
for lights and horn, Instructions to
unlock car, Attempt to reach driver,
Test results for cellular phone,
Test results for conversation,
Test results for tracking signal
Signal to activate
lights and horn,
Signal to
unlock car,
Signal to
deactivate
lights and horn,
Test signal to
unlock car
Provide
OnStar
Capabilities
Test instructions
for unlock feature
A0
Test of cellular
phone,
Adjustments for
cellular phone,
Control center
link test,
Adjustments for
tracking signal,
Adjustments for
conversation,
Adjustments for
unlock feature
User request for directions,
Request for audio directions,
Accident location, No user
response, Car stolen,
Notice of car jacking,
Tracking signal, Phone
link, Test of phone link,
Request for control center
link test
Maintainer
feedback
Air bag signal,
Security system
signal, Power
On-Star System
Test diagnostics - phone,
Test diag. - tracking signal,
Test diag. - conversation
PURPOSE: To describe the Operational Phase for the Cadillac OnStar System
VIEWPOINT: The Systems Engineering Team
NODE:
TITLE:
A-0
USED AT:
George Mason
University
NUMBER:
Provide OnStar Capability
AUTHOR: SYST 520 Student
PROJECT: Cadillac On-Star System
x
DATE: 08/15/00
REV:
NOTES: 1 2 3 4 5 6 7 8 9 10
Process Control
Policies
User Interface
Policies
Request for directions,
Location to go to,
Request to record directions,
Request to play directions,
Lights and horn off,
Car jacking
Power
Request for location,
Audio directions, Instructions
for lights and horn, Instructions to
unlock car, Attempt to reach driver,
Test results for cellular phone,
Test results for conversation,
Test results for tracking signal
Request from user for directions,
Location user wants to go to,
Request from user to record directions,
Request from user to play directions,
Request from user to turn off lights and horn,
Report from user of car jacking
Audio replay
of directions
A1
Determine
OnStar
Responses
Test instructions
for unlock feature
A2
Power
Power
Lights and horn on,
Request to unlock car,
Unlock feature test,
Request from user to
turn off lights and horn
A0
TITLE:
 1995-2000, Dennis Buede
Control
Center
feedback
Where to?,
Call for Accident
User request for directions,
Request for audio directions,
Accident location, No user
response, Car stolen,
Notice of car jacking,
Tracking signal, Phone
link, Test of phone link,
Request for control center
link test
Provide OnStar Capabilities
Signal to activate
lights and horn,
Signal to
unlock car,
Signal to
deactivate
lights and horn,
Test signal to
unlock car
Communicate
with
Car
CC Communication
Module
OnStar Processor
On-Star System
NODE:
Where to?,
Audio replay
of directions,
Call for accident
A3
Cellular phone test,
Tracking signal test,
Results of phone test,
Results of conversation test,
Results of tracking signal test,
Cellular phone adjustments,
Conversation adjustments,
Tracking signal adjustments,
Unlock feature adjustments
User Interface
Module
User Feedback
Maintenance
Policies
Communicate
with Control
Center
Power
Air bag signal,
Security system
signal, Power
Car Interface
Standards
User
Feedback
User requested directions,
CC request for location,
User location to go to,
CC Directions,
User request to record
directions,
User report of car jacking,
Airbag activated,
User unresponsive,
Security system activated,
Conv. Test, Unlock Test
Audio directions
for user, Call to user
for accident
Test of cellular
phone,
Adjustments for
cellular phone,
Control center
link test,
Adjustments for
tracking signal,
Adjustments for
conversation,
Adjustments for
unlock feature
DATE CONTEXT:
READER
Cadillac Policies
and Procedures
Communication
Policies
Accept User
Requests &
Provide
Feedback
No response
from user
WORKING
DRAFT
RECOMMENDED
PUBLICATION
P. 2
A4
Maintain
On-Star
Maintainer
feedback
A5
Car Communication
Module
Test diagnostics - phone,
Test diag. - tracking signal,
Test diag. - conversation
Maintenance
Module
NUMBER:
P. 3
22
The following set of FFBDs completes the operational architecture:
1.0
Accept User
Requests &
Provide Feed...
Ref.
AND
AND
Ref.
for each input received
4.0
response for car
Communicate
with Car
2.0
3.0
response for control center
Determine
OnStar
Responses
IT
Communicate
with Control
Center
OR
IT
5.0
response for maintenance
Maintain OnStar
Date:
Thursday, August 10, 2000
Author:
Number:
Name:
(Trial) Provide OnStar Capabilities
0.0
Trial User
for each request for directions
1.2
IT
Accept
Location User
Wants to Go To
1.1
1.3
Accept User
Request for
Directions
Process Audio
Directions
IT
1.4
Accept User
Report of Car
Jacking
Ref.
AND
AND
Ref.
1.5
Accept User
Request to
Turn Off Light...
1.6
Call User After
Accident
Date:
Thursday, August 10, 2000
Author:
Number:
Name:
(Trial) Accept User Requests & Provide Feedback
1.0
 1995-2000, Dennis Buede
Trial User
23
2.1
Determine
Responses to
User
4.0
Communicate
with Car
2.2
Determine
Responses to
Control Center
Ref.
3.0
AND
AND
every second until loss of power
2.3
LP
OR
Communicate
with Control
Center
5.0
Determine
Responses to
Signals from...
LP
Maintain OnStar
2.4
Determine
Responses to
Maintainer
Date:
Thursday, August 10, 2000
Author:
Number:
Name:
(Trial) Determine OnStar Responses
2.0
 1995-2000, Dennis Buede
Trial User
24
3.1
Communicate
User Request
for Direfctions...
3.2
Communicate
Notification of
Accident
2.0
3.3
Determine
OnStar
Responses
AND
Communicate
Test from
Maintainer
AND
Ref.
3.4
Communicate
User Report of
Car Jacking t...
3.5
Communicate
Notification of
Stolen Car
Date:
Thursday, August 10, 2000
Author:
Number:
Name:
(Trial) Communicate with Control Center
3.0
 1995-2000, Dennis Buede
Trial User
25
for each signal to activate lights and horn
IT
2.0
4.1
4.3
Communicate
Signal to Flash
Lights and Horn
Communicate
Signal to
Deactivate Lig...
IT
4.2
Determine
OnStar
Responses
Communicate
Signal to
Unlock Car
AND
AND
Ref.
4.4
Communicate
Test of Unlock
Feature
Date:
Thursday, August 10, 2000
Author:
Number:
Name:
(Trial) Communicate with Car
4.0
Trial User
for each test performed
no corrections made
2.0
Determine
OnStar
Responses
5.1
IT
Perform
Maintenance
Tests
5.2
Evaluate
Results of
Tests
OR
corrections made
Ref.
Accept
Adjustments
for Problems
Date:
Thursday, August 10, 2000
Author:
Number:
Name:
(Trial) Maintain OnStar
5.0
 1995-2000, Dennis Buede
IT
5.3
Trial User
26