FACR data collection audit is performed at the switch level. The function of the audit is to collect and
summarize NSEP feature package usage data within the office. NSEP feature packages consist of a group of
features that have an associated RTU fee. The audit queries the office data base and examines the feature
content of every line and trunk in the office. Once all feature package data has been collected the program will
formulate the NSEP feature package use counts.
The FACR-RSCANS communication package provides the mechanism for transferring the feature count data
file from any 5ESS-2000 switch to the FACR-RSCANS computer. The Communication Package software
utilizes an enhanced version of RSCANS which provides automatic password generation to retrieve the data
files from the applicable 5ESS-2000 switch. There is a software interface between the FACR-RSCANS
computer and the PC workstations. This interface handles requests for data transfer between the PC and
FACR-RSCANS computer.
Both the Lucent Technologies Billing Center and the Customer Purchasing Center PC consist of
communications software and bookkeeping programs.
The communications software will allow for file transfer to and from the FACR-RSCANS computer. The
customer PC initiates all data file retrieval requests from the 5ESS-2000 switch to the FACR-RSCANS
computer. Once the data files are on the FACR-RSCANS computer the files can then be downloaded to
the PC via the communication software. The customer has control over which 5ESS-2000 switch FACR
output files that the Lucent Technologies PC is allowed to access by the type of FACR audit that is
executed on the 5ESS-2000 switch (Refer to Section 5.16.3 for further details).
The PC bookkeeping program allows for Lucent Technologies and the Customer to generate identical
FACR "true-up" reports. This data can then be used for reconciliation of RTU NSEP software features.
5.16.3 FACR AUDIT
5.16.3.1 Password Initialization
On initial start-up, every office which is using the FACR feature is required to initialize the FACR-RSCANS
password. This must be done through consultation with the FACR coordinator. The FACR coordinator should
provide the 5ESS-2000 switch maintenance technician with the initial password and office key. (It is
STRONGLY
RECOMMENDED
that the password and key be unique for each office.)
The maintenance technician then uses the FACR password and office key as input for the "INIT:FACR" input
message. Once the password has been initialized for the first time, all subsequent file requests will automatically
generate the next password to be used. If the password should for any reason be lost on the switch, the FACR
coordinator should contact the maintenance technician to reinitialize the password.
5.16.3.2 Scheduling
The FACR audit has two modes of execution: Immediate or Scheduled. The FACR audit is considered a
maintenance tool and is only allowed to execute between the times of 6 p.m. and 6 a.m. Therefore all immediate
requests should be made during these times. If the request is made outside of the permitted times, the audit will be
scheduled for execution at 6 p.m.
The schedule option allows the user to schedule the audit to begin execution any day of the calendar year during the
times of 6 p.m. and 6 a.m. There are no restrictions in place as to the number of entries that can be scheduled at
one time. However, all scheduled entries should be adequately spaced apart so that the previously scheduled
request can complete. All scheduled requests will be carried over from one calendar year to the next calendar year,
and all scheduled requests will be preserved when an office is upgraded to a new software release.
235-105-210
October 1999
Copyright © 1999
Page 62
Summary of Contents for 5ESS-2000
Page 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Page 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Page 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Page 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Page 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Page 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Page 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Page 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...