text
stringlengths
0
1.99k
FACS is used by many departments and work centers in the BOC network. A
general example of telco interaction will be included later in the article.
PREMIS
------
PREMIS supports the customer negotiation (i.e. while a customer talks with
a BOC service rep, PREMIS is the computer system the rep has access to) and
service order (SO) preparation process (a SO is basically a request for
service). PREMIS is a computer-based information storage and retrieval system
designed to support the Residence/Residential Service Center (RSC), and in
some cases, the Business Service Center (BSC). The RSC is the center that
residence customers deal with, and the BSC is the center that business
customers deal with.
PREMIS provides fast easy access to customer address verification for
numbered and unnumbered addresses (information is stored by telephone number
not address), telephone service status at an address (whether the phone is in
service, disconnected, pending connect, pending disconnect, disconnected due
to non-payment, etc.), telephone number assignment for customers (PREMIS can
generate a list of available telephone numbers in a given exchange and the
available TNs come from COSMOS) and facility assignment data for outward
orders.
The following PREMIS features are available to the service reps and have
special significance to the LAC:
Customer Negotiation:
Provides customer service address check against a mechanized Street
Address Guide (SAG).
Provides customer status check to a mechanized facility address file
which identifies potential Interfering Station (IS) conditions.
Provides new telephone number assignments through an available TN
(Telephone Number) file.
Service Order Preparation:
Provides SAG data.
Provides correct address spelling.
PREMIS, as far as I know, does not have any direct dialups so don't get
your hopes up high. There may be other ways to access information in PREMIS
however.
SOAC
----
The SOAC system is what interfaces FACS with the BOC SOP (Service Order
Processor). The SOP is what the service reps enter SO information into and
the SOP sends the data entered to the SOAC system. The SOAC system interprets
and validates this input data.
SOAC generates Assignment Requests (ARs) which are sent to LFACS and
COSMOS (see respective sections of this file) to request outside plant (OSP)
and CO facility assignments, respectively.
SOAC receives AR Responses (ARRs) from LFACS and WM/COSMOS and merges this
data and formats the output into a Universal Service Order (USO) assignment
section. This USO is returned to the SOP after SOAC has processed it.
SOAC returns status information and error notification to the SOP. Status
information is what tells the service rep who entered the data into the SOP
whether or not FACS can process that Service Order. Error notifiers are sent
back to the SOP when part of the SO is in error.
SOAC keeps record of status and control information on all SO requests, as
well as the input image and specific data that came from processing. This
information, along with the input image and processing results are referred to
as the pending assignment data.
SOs do not automatically flow through SOAC in all cases. SOAC can analyze
an order to determine if manual assistance is required, and if it is, a
Request for Manual Assistance (RMA) notice is sent to the LAC. LAC personnel
will use SOAC, and possibly other systems in FACS, such as COSMOS/WM and
LFACS, to complete the assignment on that SO.
SOAC also may receive COSMOS system output from certain commands. One
such command may be the IJR command, which sets up a circuit for jeopardy
status. Jeopardy status means that the assignment looks as if it will be (or
already is) behind schedule for completion. An example of this is as follows
(showing COSMOS messages).
WC% IJR
H ORD nxxxxxxxx/TN nxx-xxxx/JR nx
RMK NEED TIE PR FOR nxx
-.
**ORDER nxxxxxxxx HAS BEEN GIVEN JEOPARDY STATUS
CKTID: TN nxx-xxxx
**JEOPARDY REASON: nx mm-dd-yy hh:mm
OUTPUT SENT TO SOAC