Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies Centrevu Cms Administration Guide
Lucent Technologies Centrevu Cms Administration Guide
Have a look at the manual Lucent Technologies Centrevu Cms Administration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Task: viewing and changing system setup values CentreVu CMS Administration Archiving data in the historical database10-21 ........................................................................................................................................................................... 5In the Date field, type the date (MM/DD/YY) for which you want the data summarized. Use the following as a guide: • A daily summary consists of a partial day. Daily summaries must be complete for each day of the week or month before CentreVu CMS archives the data for that week or month. • For a weekly summary, set a date that falls within your predefined week (as set in the Storage Intervals window) or any date after that week but before the next weeks start date. • For a monthly summary, set any day during the month for which you want the monthly data summarized. END OF STEPS........................................................................................................................................................................... Reference • If the date you set does not fall within your predefined week, the previous week is summarized (as long as each day of the previous week has been archived successfully). So if your designated week is Monday through Friday and you enter a date that falls on Saturday, the data is archived for the previous week. • If the date you choose sets a week or month for which a daily summary is not complete, archiving does not occur for the week or month. You cannot archive partial weekly or monthly data. • You can use the drop-down list, Single Date Input browse window, or Multiple Daily Input browse window to enter the dates. • Your data is automatically archived based on your storage intervals. • Data summarizing is done on demand from the Data Summarizing window and happens immediately. • Before you start a manual archive, a message warns you that archiving data can take a long time and cannot be canceled. You can back out from this message field before you start the archive. • Multiple data-summarizing requests are queued and are run in the order you request.
Task: viewing and changing system setup values CentreVu CMS Administration Archiving data in the historical database10-22 • “Archiver started” displays on the status line for the first request and “Archiver request submitted” displays if there is already a data summary in progress. • Scheduled daily, weekly, and monthly data summaries are queued with manual requests so that just one type of data summarizing runs at one time. • You cannot request a manual archive without existing data for the day, week, or month summarized. You must allocate space in the Data Storage Allocation window before you can archive. • The results of daily, weekly, and monthly data summaries are written to the error log. You can use the error log report to see when the summaries ran and whether or not they were successful. The Archiving Status window also shows this information. • The Archiving Status window shows the status, date, and time of the last archive for interval, daily, weekly, and/or monthly summarizing. If CentreVu CMS is down when a data summarizing timetable is scheduled to run, an error message directs you to do a manual archive from the Data Summarizing window. See “Task: maintaining CentreVu CMS” for more information. • The Data Summarizing window is automatically put on a timetable to run at the data-summarizing time that you set in the Storage Intervals window. You can also put manual archiving on a timetable. See “Task: using timetables and shortcuts” for more information.
Task: viewing and changing system setup values CentreVu CMS Administration Starting or stopping external applications10-23 ............................................................................................................................................................................................................................................................Starting or stopping external applications OverviewUse these steps to turn on or turn off the External Application feature, to start or stop external applications, or to view the status of external applications. This feature sends CentreVu CMS real-time data to an external device such as a wallboard or to an external program such as an employee scheduler. External Application is a separately purchased CentreVu CMS feature. Steps........................................................................................................................................................................... 1On the controller window, select Tools | CMS System Setup. The CMS System Setup selector window opens. ........................................................................................................................................................................... 2Select Operations | External Application Status. The External Application Status input window opens. ........................................................................................................................................................................... 3In the External Applications field, select the name of the external application. If you do not know the name, select External Application and select List all on the Actions menu or on the toolbar. ........................................................................................................................................................................... 4In the Application Status field, click Start to start the external application, or Stop to stop the external application. END OF STEPS...........................................................................................................................................................................
Task: viewing and changing system setup values CentreVu CMS Administration Starting or stopping external applications10-24 Reference The status of an external application can be one of the following: • Starting — a request to start the external application has been made. • Running — the external application has started and is still running after 10 seconds. • Stopping — a request to stop the external application has been made. • Stopped — all processes associated with the external application have stopped. • Failed — the external application has failed repeatedly and is no longer being restarted. • In the United States, the external applications are designed and administered by the Technical Service Center. For more information about external applications, call the National Customer Care Center Call Center Helpline at 1-800-242-2121. For help outside the United States, contact your local Lucent distributor or representative. • A standard or custom real-time report collects the CentreVu CMS data that is sent to the external application. See “Task: running, printing, exiting, and restarting a report” for more information. • You can script the External Application Status window. See “Task: automating your activities with scripting” for more information. • You can put the External Application Status window on a timetable. See “Task: using timetables and shortcuts” for more information.
Task: viewing and changing system setup values CentreVu CMS Administration Allocating storage space10-25 ............................................................................................................................................................................................................................................................Allocating storage space OverviewUse these steps to specify how much data CentreVu CMS saves and for how long. The amount of data and the length of time the data is saved affects disk space, and is limited by your system configuration. Data storage parameters are initially set during installation. PrerequisitesWait to begin a second modification If you are in the process of modifying data, do not open another Data Storage Allocation window to start another modification. Wait until the first modification finishes. You could lose data tables by doing simultaneous modifications. Check free space Check the amount of free space in the Free Space Allocation window and determine where you can allocate space for data storage. This window shows the amount of disk space that is available for use. The values you set in the Data Storage Allocation window affect the amount of free space still available. See “Specifying how CentreVu CMS stores data” in this task for more information. Know your permission status To view how space has been allocated, you need read permission for the CMS System Setup command. To change data storage allocation, you need write permission. See “Task: assigning user permissions” for more information. Steps........................................................................................................................................................................... 1On the controller window, select Tools | CMS System Setup. The CMS System Setup selector window opens. ........................................................................................................................................................................... 2Select Operations | Data Storage Allocation.
Task: viewing and changing system setup values CentreVu CMS Administration Allocating storage space10-26 The Data Storage Allocation input window opens. This window shows the values set during installation: the maximum number of splits/skills, agents, trunk groups, trunks, call work codes, vectors, and VDNs for your system. You can allocate storage space for those maximums or you can change those maximums to meet the needs of your call center. You can also enter shift times (at least one) and the number of agents for those shifts. END OF STEPS...........................................................................................................................................................................
Task: viewing and changing system setup values CentreVu CMS Administration Allocating storage space10-27 Steps to set field valuesThe following steps include only the fields that need an explanation: ........................................................................................................................................................................... 1In the # of Items field, type the number of items for splits/skills, trunk groups, trunks, call work codes, vectors, and VDNs for which you want space allocated. ........................................................................................................................................................................... 2In the Days of Daily field, type the number of days for which you want daily data stored for splits/skills, agents, trunk groups, trunks, call work codes, vectors, and VDNs. If you type , CentreVu CMS does not save daily data. Each entry (split/skill, trunk group, etc.) can be different. To store daily data for a complete month, type ........................................................................................................................................................................... 3In the Weeks of Weekly field, type the number of weeks for which you want weekly data stored for splits/skills, agents, trunk groups, trunks, call work codes, vectors, and VDNs. Each entry (split/skill, trunk group, etc.) can be different. If you type , CentreVu CMS does not save weekly data. ........................................................................................................................................................................... 4In the Months of Monthly field, type the number of months for which you want monthly data stored for splits/skills, agents, trunk groups, trunks, vectors, and VDNs. Each entry (split/skill, trunk group, etc.) can be different. If you type , CentreVu CMS does not save monthly data. ........................................................................................................................................................................... 5In the Shift 1 (2, 3, or 4) field, type the shift start and stop times for each shift of agents (up to four shifts) for your ACD. Shifts can overlap. If you specify a shift that starts before the data collection start time or ends after the data collection stop time, you get an acknowledgment. ........................................................................................................................................................................... 6In the Maximum agents logged in field, type the maximum number of agents logged in during the shift. ........................................................................................................................................................................... 7In the field for total split/skill members, summed over all splits/skills (0- 9,999), type the maximum number of measured split/skill members summed over all splits/skills.
Task: viewing and changing system setup values CentreVu CMS Administration Allocating storage space10-28 ........................................................................................................................................................................... 8In the field for Number of Agent login/logout records (0–999,999), type the number of agent login/logout records you want to store. A record is generated each time an agent logs in, one record per login/logout session. ........................................................................................................................................................................... 9In the field for Number of agent trace records (0–500,000), type the number of agent trace records for this ACD (not for all ACDs). To calculate how many records you need, multiply the number of days for which you want to save this information times the number of agents who log in and out each day times the number of times each agent logs out each day. ........................................................................................................................................................................... 10In the field for Number of unmeasured trunk facilities, type the number of unmeasured trunk facilities. Set this number high enough to handle the traffic expected over these unmeasured trunk facilities but not to exceed the maximum number of trunks minus the number of measured trunks. ........................................................................................................................................................................... 11In the field for Number of exceptions records (0–2,000), type the total number of exceptions (for example, agents, splits/skills, VDNs). ........................................................................................................................................................................... 12In the field for the Number of call records (0–5,000) or (0–999,999), type the number of call records you want to store for this ACD. If you collect and report these records on CentreVu CMS itself, this is the number of records that are stored. The value can be from 0 to 5,000. If you send the records to another computer for storage and analysis, this is the amount of buffer space set aside to collect the records before transmission to the other system. The value can be from 0 to 999,999.
Task: viewing and changing system setup values CentreVu CMS Administration Allocating storage space10-29 ........................................................................................................................................................................... 13When you are done changing field values, do one of the following: • Select Modify on the Actions menu or on the toolbar to accept your changes. • Select Exit on the Actions menu or on the toolbar to exit the window without saving your changes. END OF STEPS........................................................................................................................................................................... Reference Always: • Turn off data collection for all real ACDs. When the status line reads “Successful,” you can turn data collection back on. For a pseudo-ACD, data collection can be on when you change data storage parameters. • Put CentreVu CMS in single-user mode before you change data storage parameters. If you log out while in single-user mode, you must wait at least 10 seconds before logging in again. Calculate storage needs: Data storage allocation needs vary among installations. Base your CentreVu CMS data needs on these criteria: • Available disk space on your system configuration • Number of ACDs (real ACD and pseudo-ACDs) on CentreVu CMS • Size of the real ACDs and all pseudo-ACDs (number of agents, trunks, etc.) • Length of time for data to be stored (for example, 30 days versus 100 days versus two years) The historical database probably uses the most disk space. You can reduce the amount of historical data saved by using the Data Storage Allocation command. Your CentreVu CMS reporting priorities also determine how you set your data storage allocation. The maximum amount of storage space for each data type (agent, split/ skill, trunk, trunk group, etc.) is limited by the amount of free space available in that file system and the maximum storage needs.
Task: viewing and changing system setup values CentreVu CMS Administration Allocating storage space10-30 Assuming that free space is available, the maximum storage capabilities are: • Intrahour storage: 62 days • Daily storage: five years (1,825 days) • Weekly/monthly storage: 10 years (520 weeks/120 months) Understand implications The length of the intrahour interval affects how much disk space is needed to store the days of intrahour data. For example, if you set your intrahour interval to be 15 minutes, the amount of disk space required is four times larger than if you set your intrahour interval at 60 minutes for the same number of days of data. The start time, stop time, weekly start day, and weekly stop day set in the Storage Intervals window also affect disk space. Existing values and what they mean • The values in this field are calculated to include expected growth. For example, if space is allocated for three splits/skills, displays under the # of Items heading in the row corresponding to the splits/skills data item. • Days of Intrahour: this field shows the number of days for which you are currently storing intrahour data. For example, if the Days of Intrahour field is set to store 31 days of intrahour data, displays under the Days of Intrahour heading in the row corresponding to the appropriate data item. • Days of Daily: this field shows the number of days for which you are currently storing daily data. For example, if the Days of Daily are set to store daily data for 387 days, displays under the Days of Daily heading in the row corresponding to the appropriate data item. • Weeks of Weekly: this window shows the number of weeks that you are storing weekly data. For example, if you have the Weeks of Weekly currently set to store weekly data for 104 weeks, then displays under the Weeks of Weekly heading in the row corresponding to the appropriate data item. • Months of Monthly: these fields show the number of months for which you are storing monthly data. For example, if the Months of Monthly field is set to store monthly data for 60 months, displays under the Months of Monthly heading in the row corresponding to the appropriate data item.