The FACR audit also has two types of execution: "OFC" (official) or "UNOFC" (unofficial). The request type is used
to indicate the type of output file to be created upon completion of the audit. (Refer to Section 5.16.3.4 for further
information.) When the audit is run with the OFC type, both the customer and Lucent Technologies will have access
to the FACR data once the files have been retrieved from the 5ESS-2000 switch and stored on the FACR-RSCANS
computer. If the customer wants the data access to be restricted to just their PCs, then the UNOFC request type
should be used.
5.16.3.3 Execution
Before the FACR audit actually begins execution, a check is made to ensure that it is within the allowed execution
time (6 p.m. to 6 a.m.). If this check passes, then the audit creates a list of all operational SMs/SM-2000s in the
office. For each line and trunk in the SM/SM-2000, the audit collects all associated feature data. When all the
feature data has been collected in the SM/SM-2000, feature package analysis is performed to determine what
NSEP feature packages are being used. If a package is identified as being used, the count associated with the
feature package is incremented by 1.
Upon completion of each SM/SM-2000, all feature package counts are written to the data file. Prior to execution of
the next SM/SM-2000, a time check is made to verify that the FACR audit is still within the allowed execution time. If
it has progressed outside of the allowed time, the audit stores the number of the next SM/SM-2000 to process and
terminates normally. At the same time, the audit is scheduled to resume processing at the original start time for the
next day. When it resumes, the audit begins processing where it left off using the saved SM/SM-2000 number.
5.16.3.4 Output Files
There are three types of data files that could be produced by the FACR audit, depending on how FACR was
invoked. The three types are as follows:
Interim storage file
Final FACR file
Error data file.
All files are stored under the /rclog/FACR directory. The following list provides a description of each file and its
function.
The interim storage data file "facr.data" is used as a scratch pad while an existing FACR audit is in progress.
This file holds general office information, cumulative NSEP feature package counts, the audit request type, and
time and date of execution. This file is updated upon completion of each SM/SM-2000 in the office. Once the
audit has completed processing the entire office, the NSEP feature package counts are extracted to produce
the final FACR data file.
The final FACR data "file" actually consists of a FACR data file and a FACR error file. The files have the
following naming convention:
File Names : 9257d012.94f, 9257d012.94u, 9257d012.94d or 9257d012.94e
BASE & CONTROL = 9257d0
Month = 12
Year = 94
File Type = f (official) , u (unofficial), d (detail or e (error)
9257d012.94f The official data file is created when the "OFC" parameter is used in the input message. Both
the Lucent Technologies PC and the Customer PCs have access to official FACR data files.
235-105-210
October 1999
Copyright © 1999
Page 63
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 ...