NEC Attendant Console Statistics Operations Manual

							NDA-30122   Revision 1 Page 13
Attendant Console Statistics Operations Manual INSTALLATION & CONFIGURATION
After Installation
The Console Stats application can be used with the Hospitality Center System 
(HCS) or Medical Center System (MCS) applications. If Console Stats i s  t o  b e  u s e d  
with either of these applications, perform the following steps as appropriate:
HCS ConfigurationIf HCS is to be used with Console Statistics, then HCS must be configured as 
follows:
Step 1:
Halt all HCS applications.
Step 2:
Add the following line to “/oai/app/hcs/cfg/Matcsii.cfg”:
- /oai/app/stats/cfg/api.cfg
Step 3:
Create a file called “/oai/app/hcs/cfg/Mserver.cfg” and insert the 
following line:
- /oai/app/stats/cfg/api.cfg
Step 4:
Use the APM Administrator to set the User Defined #13 value of all 
HCS_ServerX applications (HCS_Server1, HCS_Server2, etc.) to the 
following:
- /oai/app/hcs/cfg/Mserver.cfg
Step 5:
Restart all HCS applications.
MCS Configuration
If MCS is to be used with Console Statistics
, then MCS must be configured
as follows:
Step 1:
Halt all MCS applications.
Step 2:
Add the following line to “/oai/app/mcs/menus/Mcs.cfg”:
- /oai/app/stats/cfg/api.cfg
Step 3:
Create a file called “/oai/app/mcs/menus/Mserver.cfg” and insert the 
following line:
- /oai/app/stats/cfg/api.cfg
Continue to Steps 4 and 5 on the next page... 
						

							Page 14 NDA-30122   Revision 1
INSTALLATION & CONFIGURATION Attendant Console Statistics Operations Manual
MCS Configuration 
(Cont.)Step 4:
Use the APM Administrator to set the User Defined #10 value of all 
Mcs_ServerX applications(Mcs_Server1, Mcs_Server2, etc.) to the 
following:
- /oai/app/mcs/menus/Mserver.cfg
Step 5:
Restart all MCS applications.
Proceed to the next page to configure the APM and various components... 
						

							NDA-30122   Revision 1 Page 15
Attendant Console Statistics Operations Manual INSTALLATION & CONFIGURATION
Application Configuration
Since Console Stats is internally supported by the APM, its two components must 
be configured in the APM environment. This section provides the information that 
must be entered into the APM configuration file.
Console Stats is set-up in the APM system using the Add function of the 
Application Configuration option on the APM System Administration menu.
A Note on Selecting Commands
In the following procedures, a step may call for pressing the Tab key to select 
a command. It may be necessary to press the Tab key multiple times in order 
to select the specific command. When reading a step, understand to press the 
Tab key (as needed) to select the specified command.
APM System 
ConfigurationFollow the steps to configure the APM system for Console Stats.
Step 1:
Enter the APM option from the APM Platform Management menu.
Step 2:
Enter the System Administrator password at the APM password screen.
Step 3:
Select the Application Configuration option from the System 
Administration menu.
Console Stats 
ComponentsConsole Stats has two components that must be configured through the APM.
StatPatroller–Clears the database of old records, clears directories of old 
reports and old log files, and date-stamps the log files.
StatLogger –Logs attendant on-line, off-line, login, and logout messages. It 
also logs call messages — incoming, answer, abandon, recall, 
and release. Messages are logged in the Informix database.
Proceed to the next page to define these components... 
						

							Page 16 NDA-30122   Revision 1
INSTALLATION & CONFIGURATION Attendant Console Statistics Operations Manual
Component 
CharacteristicsDefine the two components exactly as shown in the table:
Parameter
Definition
OAI Application Whether (Yes or No) the component communicates 
with the NEAX2400 using OAI processes.
CRT  Application Whether (Yes or No) the component runs on the same 
screen as the APM, rendering the APM temporarily 
inaccessible.
Communication Queue Whether (Yes or No) the component  needs an IPC 
queue to communicate with other processes.
Proceed to the next page to set the Primary Configuration Parameters...
Characteristic StatPatroller StatLogger
OAI Application N N
CRT Application N N
Communication Queue N Y 
						

							NDA-30122   Revision 1 Page 17
Attendant Console Statistics Operations Manual INSTALLATION & CONFIGURATION
Primary 
Configuration 
ParametersFrom the APM Configuration Entry screen, configure each component as follows. 
All parameters marked with asterisks (*) should be entered exactly as shown. The 
rest of the entries in the table below are just examples.
Parameter
Definition
Application Name The name to be displayed in the APM menus. This name 
is displayed as it is entered here — i.e., capital letters, 
lowercase, etc.
Executable Filename* The path name of the executable file.
Group* The group that the component belongs to. Make no entry.
Response Mode* The action that the APM is to take with the component 
should a member of the group terminate.
Initialization Batch Whether (Yes or No) the component is to be initialized 
automatically when the OAI system is initialized.
Termination Mode* How the APM is to notify the component to terminate.
Standard Output  Where any output is sent.
Number of Restarts  How many times the APM may restart the component 
after it terminates in error.
Queue Key The interprocess communication key by which the 
component communicates with other processes.
This completes the configuration of Console Stats into the APM.
Proceed to the next page to review database support for Console Stats...
Pa rame te rStatPatroller
Va l u e sStatLogger
Va l u e s
Application Name StatPatroller StatLogger
Executable Filename* /oai/app/stats/bin/patroller /oai/app/stats/bin/logger
Group* STATS STATS
Response Mode* I(gnore) I(gnore)
Initialization Batch   N(o) N(o)
Termination Mode* T(erminate) M(essage)
Standard Output /dev/null /dev/null
Number of Restarts 0 0
Queue Key 112 
						

							Page 18 NDA-30122   Revision 1
INSTALLATION & CONFIGURATION Attendant Console Statistics Operations Manual
Database SupportConsole Stats requires one database of its own in the APM. The Console Stats 
database (statcfg) was loaded during software installation from the release media 
and contains default field entries, most of which should not be changed without 
first consulting an NEC representative. The statcfg database structure and contents 
are described in the table below:
The only field in this database whose entry should be changed is the Max Days to 
Keep Records. This value reflects the number of days for which attendant data is 
maintained in the database and can be any number of days, from 1 to 730. If you 
need to change this value, use the Database Administration option on the APM 
System Administration Menu. Refer to the APM Operations Manual for more 
detailed instructions.
Proceed to the next page to initialize the Console Stats components...
Field NameMaster File Definition
(statcfg)App. File
Definition
(Statcfg)Master
Database
(statcfg)
Type Size Min.
Va l u eMax.
Va l u eData Type Default Entry
Automated Reports Dir A 25 ASCII /oai/log/stats/arpts
Non-Automated Reports Dir A 25 ASCII /oai/log/stats/narpts
Login Reports Dir A 25 ASCII /oai/log/stats/lrpts
Log Directory A 25 ASCII /oai/log/stats
Report Generator Process A 25 ASCII /oai/app/stats/bin/rptgen
Database Name A 9 ASCII statsdb
Max Days to Keep Records N 3 1 730 Short Integer 365
Max DB Records to Query N 2 1 50 Short Integer 50
Attendant Statistics A 1 ASCII Y
Call Queue Statistics A 1 ASCII Y 
						

							NDA-30122   Revision 1 Page 19
Attendant Console Statistics Operations Manual INSTALLATION & CONFIGURATION
Initialize 
ComponentsThe two Console Stats components must be initialized from the APM as follows:
StatLogger Component
Follow the steps below to initialize the StatLogger component:
Step 1:
On the APM System Operations Menu, select the Non-CRT 
Application Control option.
Step 2:
Use the Initialize command to start up the “StatLogger” component.
StatPatroller Component
Follow the steps below to initialize the StatPatroller component:
Step 1:
On the APM System Administration Menu, select Control Options.
Step 2:
On the Application Selection screen, select StatPatroller.
Step 3:
On the Application Control Options screen, create a schedule for 
StatPatroller to automatically initialize every midnight by making the 
following entries:
Minute (0-59): 0
Hour of Day (0-23): 0
Day of Month (1-31): *
Month of Year (1-12): *
Day of Week (0-6): *
This completes all the application configuration.
Proceed to the next page to start-up the Console Stats application... 
						

							Page 20 NDA-30122   Revision 1
INSTALLATION & CONFIGURATION Attendant Console Statistics Operations Manual
Application Start-Up
Logging in to 
Console StatsThe Console Stats application executes on a UAP (User Application Processor). 
From the UAP terminal, follow the steps below to login and start Console Stats:
Step 1:
At the Login: prompt, type ’stats’ (lower case) and press Enter.
-  If the system is configured for a password
, a password prompt will be dis-
played. Type your password at the prompt and press Enter.
Step 2:
The Console Stats application will start and display the Main Menu 
screen. See Figure 2-1.
General Key UseThroughout Console Stats, the keys shown in the table will produce the associated 
action:
Key Action
Enter or Return Accept a chosen selection or field entry
Escape Exit the current screen or window
Tab Move to the next field on the screen or window
Back Tab Move to the previous field on the screen or window
Down Arrow • Move down one line in a scrolling window or selection list
 Move to the next field on the screen or window
Up Arrow  Move up one line in a scrolling window or selection list
 Move to the next field on the screen or window
Left Arrow Move left one character in a field
Right Arrow Move right one character field
Backspace Move left one character in a field, then delete the character
Delete Delete the current character in a field
Home  Move to the first character in a field
 Move to the first line in a scrolling window
End  Move to the last character in a field
 Move to the last line in a scrolling window
Page Up Move up one page in a scrolling window
Page Down Move down one page in a scrolling window 
						

							NDA-30122   Revision 1 Page 21
Attendant Console Statistics Operations Manual INSTALLATION & CONFIGURATION
Main Menu
Following the Console Stats login, the Console Stats Main Menu will be displayed 
(Figure 2-1).
Figure 2-1   Main Menu Screen
Console Stats call processing reports can be designed with statistics to be computed 
by hour or by day over a definable range of time or for today only. For example, 
Console Stats can calculate the amount of time out of every hour that all logged-in 
and active attendants spent talking to callers over the past week. The format for this 
report would contain these settings:
Time Interval: Hourly
Statistic: Total Talk Time
The range of time set for this formatted report when it is being generated on August 
17, 1999 would look like this:
Starting Date: 08/17/1999
Starting Time: 08:00  AM
Ending Date: 08/10/1999
Ending Time: 08:00  AM
The Console Stats Main Menu shows the sequential approach to report production.
The first step is to create a format
 the report, giving it a name and identifier (for 
storage and retrieval), naming the interval by which its statistics are calculated 
(e.g., by hour), and naming the specific statistics that are to be calculated from 
call processing data.  
						

							Page 22 NDA-30122   Revision 1
INSTALLATION & CONFIGURATION Attendant Console Statistics Operations Manual
Main Menu (Cont.)
The second step is to generate the formatted report or schedule it for automatic 
generation. Generating the report involves naming the range of time over which 
the formatted statistics are to be calculated from the call processing data 
collected for that time (for instance, over the past three days) and showing 
whether the report is to be displayed, printed, and/or saved. Scheduling 
automatic report generation involves naming a time at which the formatted 
report will be generated, either once or on a recurring basis.
Lastly, formatted and generated reports can be viewed and printed.
Main Menu 
OptionsThis sequence (described above) to produce a report is reflected in the Main Menu  
(Figure 2-1) options. 
Report Formats –Create formats for reports of statistics calculated by 
attendant or by the types of calls that are queued for and 
by attendants. 
Report Generation –Generate a formatted report of statistics calculated from 
call processing data collected before. Note that reports 
formatted with a Current interval can only be generated 
through this option. They cannot be scheduled for 
automatic generation.
Automated Report –Schedule the specific time at which a formatted
Generation report is automatically generated once or on a recurring
basis. Note that only reports formatted for statistics
calculated by the hour and by the day
can be scheduled for automatic generation.
Report Viewing –Display existing attendant login, automated and non-
automated reports for viewing and printing.
Route Groups –Create trunk route groups
Station Groups –Create station groups
These option selections and their functions are described in detail in other chapters 
of this manual. Refer to the following:
Report Formats –See Chapter 3
Report Generation –See Chapter 4
Automated Report –See Chapter 5
Generation
Report Viewing –See Chapter 6
Route Groups –See Chapter 7
Station Groups –See Chapter 8