EMS FastStart Manual

Brief Review of Event Design
EMS FastStart Manual–133701
2-3
Step 3: Identify Data in the Messages
Example:
1. ATM SFMAIN01 is up at 245 A St. San Francisco.
2. ATM SFMAIN02 is up at 245 A St. San Francisco.
3. Insufficient funds in account 34503933. Access denied on ATM OAKWEST1 at 245
Oak St. Oakland.
4. Insufficient funds in account 23409344. Access denied on ATM SACTO99 at
341 Main St. Sacramento.
5. ATM SFMAIN02 at 245 A St. San Francisco is low on funds.
6. ATM SFMAIN01 at 245 A St. San Francisco is low on funds.
7. ATM LACENT99 is down at 9320 Main St. Los Angeles.
8. ATM LACENT91 is down at 9320 Main St. Los Angeles.
9. Security breach on account 23457320. Number of accesses attempted 3; ATM
SACTO02 is down at 230 State St. Sacramento.
10. Security breach on account 34094443. Number of accesses attempted 2; ATM
SACTO01 is down at 230 State St. Sacramento.
11. Hardware failure on ATM LACENT99 at 125 8th Avenue. Component failed is cash
dispenser; subcomponent 321561ac; serial number 231234093; sense status
0101110101.
12. Hardware failure on ATM LACENT98 at 125 8th Avenue. Component failed is cash
dispenser; subcomponent 321576xx; serial number 343223480; sense status
1010111011.
Step 3: Identify Data in the Messages
Identify each part of a message as either fixed text or variable data. The variable data
and the fixed text are the two elements that define each event and comprise its template.
The variable data become the fields into which you move values when you generate your
event messages.
The sample messages below show the variables
underlined. Fixed text is not underlined.
Example:
1. ATM SFMAIN01 is up at 245 A St. San Francisco.
2. ATM SFMAIN02
is up at 245 A St. San Francisco.
3. Insufficient funds in account 23457320
. Access denied on ATM OAKWEST1 at 245
Oak St. Oakland.
4. Insufficient funds in account 23409344
. Access denied on ATM SACTO99 at
341 Main St. Sacramento.
5. ATM SFMAIN02
at 245 A St. San Francisco is low on funds.