EMS FastStart Manual

EMS FastStart Manual–133701
2-1
2
Brief Review of Event Design
This section provides guidelines and standards for programmers to follow when
designing events. EMS FastStart is designed to simplify the process of generating EMS
event messages. It is necessary to design event standards for programmers to follow,
whether EMS is used by itself or with EMS FastStart. These standards can increase the
overall efficiency of development efforts as well as enable more efficient operation and
management of the subsystem. Figure 2-1
shows the EMS event generating and
reporting process.
An event is any significant hardware or software incident that you want reported, either
to a person or to a program. For example, a message to a person goes to Viewpoint to be
read and a message to a program can be used by an application to cause an action or to
accumulate statistics. The number of messages created and their design depends on what
you need to convey to the people or programs that use the messages.
Some of the questions that need to be considered when developing and using the
standards for event message design for applications are:
•
What type of information is included in an event?
•
What events are critical?
•
What event number is assigned to an event?
•
Should the event be displayed?
•
Who or what will be reacting to the event (people or programs)?
Good event message planning and design before using EMS FastStart helps you benefit
from the streamlined event message generation and testing the EMS FastStart program
provides. Refer to the Event Management Service (EMS) Manual for more information
on events. Event message design is described in this section in a series of steps with 12
sample event messages.
Figure 2-1. Event Generation and Reporting
User Application
Event Management
Services
Operations/
Management
Subsystem
Process
Event
ATM Low on Cash
$0
Collector
Event
Log
VIEWPOINT
003