Ericsson AXE 1 Service Manual
Competence Development Centre
AXE Operation & Maintenance Platform
Basic Operation Activities
Help Exit
PREFACE
Target Audience
This book is preliminary intended to be used as a course manual in the
Ericsson AXE Operation and Maintenance training program. The book is
a training document and is not to be considered as a specification of any
Ericsson language or system.
Identification
EN/LZT 101 105 /1, R1A
Responsibility
Training Supply
ETX/TK/XM
Ericsson Telecom AB 1996, Stockholm, Sweden
All rights reserved. No part of this document may be reproduced in any
form without the written permission of the copyright holder.
Table of Contents
1. Introduction 1
1.1 Module Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction to Operation and Maintenance
Activities 3
2.1 APT Source System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Description of Operational Activities . . . . . . . . . . . . . . . . . . . . . . . 5
2.2.1 Maintenance Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3. Exchange Handling Basics 9
3.1 Overview of the Exchange Library. . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.1 AXE 10 Documentation Principles. . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2 The Structure of the Exchange Library . . . . . . . . . . . . . . . . . . . . 14
3.3 Handling the Exchange Library . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.4 B-Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.5 Using the B-Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.5.1 O&M Documentation Structure . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.5.2 Locating the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.5.3 Accessing Information in the B-Module. . . . . . . . . . . . . . . . . . . . 18
3.6 Using FIOL / DocView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.7 Using AXEUSE / Dynatext. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.8 The Exchange Log Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.9 The Command Language and Printouts . . . . . . . . . . . . . . . . . . . 20
3.9.1 Command Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.10 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4. Communication with the System 25
4.1 AXE Terminal Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.1.1 Making Contact with the System . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.1.2 Seizure and Release of Terminal. . . . . . . . . . . . . . . . . . . . . . . . . 26
4.1.3 The Label Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
03802-EN/LZM 112 17 R1 lxi
AXE 10, Basic Operation and Maintenance Activities
4.1.4 Ready Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.1.5 End of Text Character . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.1.6 The Check Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.1.7 Authority Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.1.8 The Time-Out Printout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.1.9 Blocking and De-blocking of the Terminal . . . . . . . . . . . . . . . . . . 28
4.1.10 Queue System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2 Communication Program FIOL/DocView. . . . . . . . . . . . . . . . . . . 28
4.2.1 Basic Functions of FIOL/DocView . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.2 Window Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.3 The Status Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2.4 The Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2.5 The Function Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.2.6 Practical Examples of Using FIOL. . . . . . . . . . . . . . . . . . . . . . . . 32
4.3 Using the Communication Program FIOL / DocView. . . . . . . . . . 33
4.3.1 The User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.3.2 Loading a Document from a Database . . . . . . . . . . . . . . . . . . . . 34
4.3.3 Searching Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.4 Using the Communication Program AXEUSE . . . . . . . . . . . . . . . 38
4.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.4.2 The DynaText Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.4.3 The AXE Application Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.4.4 Interactive Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.4.5 The Active Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.4.6 The Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.4.7 The Command History List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.4.8 Quick Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.4.9 Command Files - Recording and Transmission. . . . . . . . . . . . . . 42
4.4.10 Logging Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.4.11 On Screen Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
4.4.12 Interactive Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.4.13 Access to Technology Based Training (TBT) Sessions . . . . . . . . 44
4.4.14 Online Help and Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.5 Connection to TMOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.5.1 MML Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.5.2 Delayed Responses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.5.3 Spontaneous Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.5.4 File Output from the AXE 10 Exchange. . . . . . . . . . . . . . . . . . . . 46
4.5.5 File Information from TMOS to the AXE 10 Exchange . . . . . . . . 46
4.6 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
lxii 03802-EN/LZM 112 17 R1
Table of Contents
5. Hardware Orientation 49
5.1 Mechanical Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
5.2 Development of the Packaging System. . . . . . . . . . . . . . . . . . . . 50
5.2.1 BYB 101 and BYB 102 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.2.2 BYB 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
5.2.3 The Building Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.3 The Cabinet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5.3.1 Magazines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.3.2 Magazine Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.3.3 Printed Circuit Boards (PCBs). . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.4 Localization of hardware units . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.5 Chapter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
03802-EN/LZM 112 17 R1 lxiii
1. Introduction
1.1 Module Objectives
Module Objectives
After completing this module the participant will be able to:
• Describe what is meant by AXE 10 System Operation and Maintenance Activities
• Describe the general structure of the Exchange Library and maintain the library through the use of the OPI “Handling of the
Exchange Library”
• Describe the layout and contents of the B-Module and its use
• Understand the AXE 10 document numbering
• Understand the basic principles of AXEUSE, FIOL and DocView
• Describe the AXE 10 command structure
• Identify the operational activities that are to be performed based on
information that is supplied in a specific work order and the contents of the associated B-module
• Understand the basic principles of operator-system communication
and the role of I/O devices enabling such communication
• Understand the purpose of using communications programs FIOL
and AXEUSE
• Communicate with the AXE system with the help of FIOL and
AXEUSE
• Locate hardware units in the exchange through the use of commands.
Figure 1.1
Module Objectives
03802-EN/LZM 112 17 R1 1
AXE 10 Basic Operation and Maintenance Activities
1.2 General
AXE 10 Operation and Maintenance training consists of three courses.
AXE 10, Operation and Maintenance Platform. .... LZU 108 1451
AXE 10, Operation Handling................................. LZU 108 1452
AXE 10, Hardware Maintenance ........................... LZU 108 1453
This document describes the basic operational and maintenance activities
that are related toAXE 10 exchanges. The information included corresponds to the AXE 10, O&M Platform course, LZU 108 1451. The course
is intended to be used as a platform for the majority of AXE job-categories.
After completing this course, the participants will have a basic understanding of the most frequently performed activities at AXE 10 exchanges.
They can thereafter continue their training by attending either the Operation Handling or the Hardware Maintenance course, or both.
2 03802-EN/LZM 112 17 R1
2. Introduction to Operation and Maintenance Activities
Chapter Objectives
After completing this chapter the participant will be able to:
• Describe what is meant by AXE 10 Operation and Maintenance
Activities.
Figure 2.1
Chapter Objectives.
2.1 APT Source System
This document deals with the new overall source system which is called
APT 210 12.
The differences between AP T 210 08/R5 and APT 210 12 are also pointed
out when applicable.
APT 210 12 (see figure 1.2) contains the functionality of :
APT 210 08 R5 POTS (Plain Ordinary Telephone Service)
•
4/APT 210 10 R3 ISDN (Integrated Services Digital Network)
•
03802-EN/LZM 112 17 R1 3
AXE 10 Basic Operation and Maintenance Activities
POTS
APT 210 08 R5
POTS/
ISDN
ISDN
APT 210 12/1-n
4/APT 210 10 R3
Figure 2.2
APT 210 12
Three variants have been developed:
APT 210 12/1 R1 for France.
•
APT 210 12/2 R1 for Norway and Spain.
•
APT 210 12/3 R1 for the Netherlands and Switzerland.
•
Note that the countries referred to above were the first to implement the
system. Numerous other countries have subsequently selected AXE local
exchanges.
APT 210 12/1
APT 210 12/1 was originally developed for the French market. It is used
when installing new local AXE exchanges or when upgrading existing
local AXE switches requiring ISDN functionality integrated with POTS.
APT 210 12/2
APT 210 12/2 is a general application, developed initially for the Norwegian and Spanish markets. It is used when installing new local AXE
exchanges or when upgrading existing local AXE exchanges requiring
ISDN functionality integrated with POTS.
In terms of ISDN, both basic rate access (BA) and primary rate access
(PRA) are provided.
APT 210 12/3
APT 210 12/3 is the latest release of the source system APT 210 12 marketed under the product name AXE Local 12.3. Close to complete back-
4 03802-EN/LZM 112 17 R1
Introduction to Operation and Maintenan ce Activities
ward compatibility with the earlier released source systems (APT 210 08
R1-R5 and APT 210 12 R1-R2) has been maintained.
2.2 Description of Operational Activities
Operation
is the normal, everyday running of the exchange when everything is working as it should. The purpose of the tasks included in the
operational activities is to adapt the exchange to the continuously changing demands placed on it.
Sales
Office
TrafficData
Exchange
Data
Office
A
ChargingData
Charging
Office
X
TrafficMeasurement &Statistics
Planning
Office
E
Commands
Printouts
Figure 2.3
Operational Activities
Subscriber
Service
Orders
Exchange
Changes
Order
PC
Data
Charging
Data
Orders
Printers
Operational
Statistics
Orders
Operational
Manuals
5
AXE 10 Basic Operation and Maintenance Activities
Operational activities, (see figure 2.3), are normally initiated by work
orders. Work orders may be the result of operator or subscriber demands.
In either case, a work order instructs the AXE staff to carry out modifications to the exchange, that are required for its adaption to the newly arisen
needs.
W ork orders are executed in accordance with the procedures defined in the
AXE B-Module exchange documentation.
Operation staff communicate with the exchange by means of the AXE
Input/Output system.
The following are a number of examples of operational activities:
Changing subscriber data, e.g. activating a new subscriber line, provid-
•
ing a new service or changing the subscriber class of an existing subscriber
Changing routing data, e.g. initiating a new route
•
Recording statistics, e.g. traffic recording, such as monitoring of traffic
•
measurements for a period and reporting or, in some cases, evaluating
the result.
2.2.1 Maintenance Activities
The purpose of
correction of faults.
One can subdivide maintenance activities into two types:
1.
Preventive Maintenance
tasks that involves checking for suspected fault sources of faults and
their neutralization before such sources give rise to serious system
consequences.
2.
Corrective Maintenance
removing or repairing their immediate causes. Upon the occurrence
of a fault, the system will notify the staff by generating an alarm and
alarm printouts.
Staff may also be notified of the exsistence of a fault as a result of subscriber complaints. Information relating to faults external to the exchange
may also be received from subscribers.
The Ericsson Maintenance Philosophy,
(CCM), seeks to achieve a balance between these two types of
nance
maintenance.
maintenance
activities is essentially the prevention and
entails the performance of a set of routine
involves responding to actual faults by
Controlled Corrective Mainte-
Whatever the source of information, once the existence of a fault is
known, action must be taken to eliminate it. Maintenance Staff use the BModule of the exchange documentation to interpret fault information.The
B-Module also contains the procedures, Operational Instructions (OPIs),
required when dealing with faults, (see figure 2.4).
6 03802-EN/LZM 112 17 R1
Introduction to Operation and Maintenan ce Activities
Figure 2.4
Maintenance Activities
When performing the tasks outlined by an OPI, Maintenance Staff communicate with the exchange using the AXE command language, often
referred to as the Man-Machine Language (MML).
03802-EN/LZM 112 17 R1 7
AXE 10 Basic Operation and Maintenance Activities
The following are a number of examples of various maintenance tasks:
Fault-finding, testing and repair of subscriber lines
•
Fault- finding, testing and repair of trunks
•
Fault-finding, testing and repair of the GSS and SSS units
•
Maintenance of the AXE power supply and power distribution system
•
APZ Maintenance.
•
2.3 Chapter Summary
APT 210 12/1
Used when existing local AXE switches requiring ISDN functionality integrated with POTS.
Only PRA, Primary Rate Access is provided..
APT 210 12/2
Used when existing local AXE switches requiring ISDN functionality integrated with POTS.
In terms of ISDN both BA and PRA are provided.
APT 210 12/3
Marketed under product name AXE Local 12.3.
Backward compatibility with AP T 210 08 R1 - R5 and APT 210 12 R1- R2.
By Operational Activities is meant normal everyday running of the switch
when everything is working as it should.
By Maintenance Activities means preve ntion and correction of faults within
the exchange with the help of relevant OPIs.
8 03802-EN/LZM 112 17 R1
3. Exchange Handling Basics
Chapter Objectives
After completing this chapter the participant will be able to:
• Describe the general structure of the Exchange Library and maintain the library through the use of the OPI “Handling of the
Exchange Library”
• Describe the layout and contents of the B-Module and its use
• Understand AXE 10 document numbering
• Understand the basic principles of AXEUSE, FIOL and DocView
• Describe the AXE 10 command structure
• Identify the operational activities that are to be performed based on
information that is supplied in a specific work order and the contents of the associated B-module.
Figure 3.1
Chapter Objectives
3.1 Overview of the Exchange Library
3.1.1 AXE 10 Documentation Principles
Before proceeding with the description of the exchange library and its contents, a summary of the main principles employed in AXE 10 documentation are provided below.
The system employed for document identification is built on a close relation between the products found in the system and the documents associated with each product.
The system hierarchy defines the products found at the different levels.
From the point of view of documentation identification, all products from
the system level to the individual printed circuit board level are treated
equally, (see figure 3.2).
03802-EN/LZM 112 17 R1 9
Book Title
ExamplesofArticleCode:
Systemlevel1
Systemlevel2
Subsystem
Function Block
Group*
FunctionBlock
FunctionUnit
Note*: The product level Function Block Group does not exist in APT 210 08/R5.
Figure 3.2
BFD CAA CAA
CRZ
CNZ CNZ
AXE
APZ APT
ANZ
CRZ
ANT ANTANZ
CRT
CRT
CNT CNT
BFD CAA CAA
AXE1030210
APT21010
ANT21608
CRT 257 01
CNT2161012
System Structure
A product
is identified by a unique Article Code. An individual Article
Code or individual identity consists of a number of letters and digits that
are combined in accordance with the numbering system rules. The numbering system classifies and groups the products and documents in accordance with their use, system association, their location in the product
hierarchy and their factual contents. Pre-defined basic numbers and classes
are registered in a database which is continuously updated to include new
items.
Figure 3.2 illustrates the hierarchial construction of the system and displays some examples of the logical construction of the identification system:
The AXE system has article codes including APT and APZ codes.
•
All APT subsystems have article codes including ANT prefixes and all
•
APZ subsystems have article codes including ANZ prefixes.
The Function Block Group represents a recent addition to the product
•
level structure in which Function blocks having related functionality
are grouped together, (CR T and CRZ). The Function Bl ock Group level
does not exist in APT 210 08/R5.
All AP T function blocks have article codes including CNT prefixes and
•
all function blocks in APZ have article codes including CNZ prefixes.
10
All function blocks in subsystem ANT 216 xx have article codes
•
CNT 216 yy zz.
Exchange Handling Basics
AXE1011
xx
yy
-"-
-"-
-"-
03
04
05
06
APT210
-"-
-"-
-"-
05
06
07
08
Example:
AXE102 0108
APZ21201
{
APT21008
1
2
3
4
APZ210
{
{
Figure 3.3
AXE Product Number, includes APT and APZ codes
Different versions of the same product are distinguished by the Revision
State. Revision states are advanced in accordace with a given set of rules
and is related to an important product, namely interchangeability, e.g. Article Code: CNT 216 1012, Rev. State: R3.
A document
is identified by a prefix and an unique number. Different versions of the same document are distinguished by a revision letter. Document numbers for documentation relating to products usually consist of
the decimal class and the article code.
decimal class
The
indicates the type of document, and the
article code
indicates the product associated with the document , (see figure 3.4).
Document
1. DescriptionofsubsystemOMS
2. Descriptionoffunctionblock
ROSA
3. Descriptionofacommandthat
belongstofunctionblockROSA
Figure 3.4
Example of Document Numbering
Documentnumber
DecimalClass
-ANT216081551
-CNT21610121551
-CNT21610121/19082
Article Code
Revision
A
B
A
11
Book Title
A document structure exists for each product category which specifically
states the documentation required by the different product handling
phases, i.e. design, manufacturing, etc.
Certain document types are mandatory for every product. Others are
drafted when necessary, depending on the product’s functions, design and
characteristics. Figure 3.5 shows an example of document structure for a
function block.
1095Document
survey
13161Structure
spec.
1551Description
10921
Product
revision
information
n/19082Command
description
Figure 3.5
Document Structure for a Function Unit
15514Signal
survey
n/19083Printout
description
n/15514Signal
description
2/15518-
1/15518-
15518-
Application
information
12
Table 3:1 ( shown on the next page) contains a list of the most frequently
used decimal classes and their contents.
Exchange Handling Basics
Decimal class Contents of document
107 39 Wiring information
107 5 Cabling tables
107 8 Mounting drawings for printed circuits
109 21
109 5 Document surveys
130 1 Article, type and class specification
131 22 Article lists
131 32 Manufacturing specifications
151 80 General instructions
151 87 Mounting drawings
151 88 Assembly drawings
154 31 Operation directions
155 1 Description of articles
155 16 Function description
155 17 Function specification
155 18 Application information
155 19 Interworking description
155 42 Conditions information
155 61 List of contents and documents
190 55 Program source document
190 59 Parameter list
190 72 Signal distribution
190 74 Commands
190 82 Command descriptions
190 83 Printouts
190 84 Command parameter descriptions
190 92 Program information
Product revision information
191 1 Circuit diagrams
193 01 Trunking diagrams
193 04 Block diagrams
193 05 Floor plan drawings
193 06 Floor plan specifications
193 10 Cable group lists
193 11 Cabling tables
193 15 Cabling lists
193 17 Programming documents
193 19 Allocation documents (MDF)
193 25 Allocation documents (Power)
195 1 Allocation documents
195 2 Numbering documents
Table 3.1
Decimal Classes
03802-EN/LZM 112 17 R1 13
AXE 10 Basic Operation and Maintenance Activities
3.2 The Structure of the Exchange Library
All documents relating to the exchange are gathered together to form the
exchange library. The contents range from descriptions of the layout of the
building and floor plans for the exchange equipment to instructions on
how to trace and eliminate software faults. Such a wide range of material
obviously requires some sort of structure so that the information is easily
accessible by AXE staff.
The documents are distributed throughout a set of functionally defined
modules, each of them being contained in one or more binders. Some of
the longer, less frequently used modules may be stored in microfiche format to save space. Today, it is all stored on CD-ROM.
With reference to the basic operation and maintenance of the exchange,
the modules vary a great deal in terms of importance; some will be consulted daily, others never. With this in mind, we will now describe the
modules to a degree of detail corresponding to their importance as regards
the O&M job:
Four of the modules, likely to be used by AXE staff on daily basis, will be
are fully described. They are:
A-Module Library Survey.
B-Module Operation and Maintenance Manuals (Operational
Instructions, Command Descriptions, Printout Descriptions and Application Information).
C-Module Exchange Description (hardware, cabling etc.).
Another three modules are used occasionally by the O&M staff and hence
are dealt with more briefly. They are:
D-Module Functional Product Documents (software descriptions and
flowcharts).
E-Module Software Documents (source and assembly codes).
F-Module Hardware Documents (magazine and circuit layouts).
I-Module Exchange Data (MML commands configurating an
exchange), also known as the Data Transcript.
Finally, there remain six modules which are practically never needed by
the staff dealing with basic O&M. They are listed below:
G-Module Mounting Details.
H-Module Installation Test Instructions.
K-Module Power Supply Documents.
M-Module Signalling Inter-work Information.
S-Module Software Fault Location.
T-Module Correction of Central Software.
14 03802-EN/LZM 112 17 R1
3.3 Handling the Exchange Library
The OPI “Handling of the Exchange Library” found in sub-module B01,
deals with the procedures for:
Checking documents received
•
Inserting and replacing documents
•
Filing delivery notes
•
Borrowing documents from the exchange library.
•
Library maintenance may at firs t gla nc e appear to be a t ri vial ta sk. Rea lity
is however quite the contrary. The complexity of the information coupled
with the need for its frequent updating would quickly lead to complete
chaos without the existence of and compliance with strict document maintenance procedures.
Electronically stored information, (e.g. DocView, AXEUSE) allows the
saving of countless hours of work each time the documentation requires
updating. Instead of thumbing through reams of paper you simply load a
new CD- ROM disk into your PC.
Exchange Handling Basics
3.4 B-Module Overview
The B-Module (OPERATION AND MAINTENANCE MANUALS).
The B-Module is the most frequently consulted module in the library. It
consists of instructions for administrative routines, product handling, manmachine communication, supervision, fault reporting, fault location and
elimination, exchange data modification, spare-part handling, operational
reporting, etc.
The information contained in this module is used both by O&M staff in
their daily work and by the operator when, for example, modifying
exchange data.
The major portion of the B-Module concerns the Operational Instructions
(OPIs) which guide the staff in carrying out their various tasks.
Operational instructions generally refer the staff-member to Command and
Printout Descriptions. Although the experienced user usually manages
with the Operational Instructions alone, others require the help of the
Command and Printout Descriptions.
Because the instructions and descriptions are of a comprehensive nature
and handle a variety of different functions, the B-Module is subdivided
into seven sub-modules. These are listed below:
B01 General Operational Instructions.
B02 Operations Instructions.
B03 Maintenance Instructions.
B04 Test Instructions.
03802-EN/LZM 112 17 R1 15
AXE 10 Basic Operation and Maintenance Activities
B11 Command Descriptions.
B13 Printout Descriptions.
B14 Adaptation Directions, Application Information.
Note: In certain instances the B-Module is subdivided as follows:
B03 contains B01 - B03
•
B14 contains Adaptation Directions
•
B15 contains Application Information.
•
3.5 Using the B-Module
3.5.1 O&M Documentation Structure
We have mentioned earlier that the B-Module is divided into seven submodules, B01 to B04, B11, B13 and B14. The major portion of these submodules is made up of Operational Instructions (OPIs). With the help of
flow charts provided in the OPIs, the operator is guided through the operation and maintenance tasks in a step-by-step fashion. The information
included in each submodule is summarized as follows:
Submodule B01
Administrative routines
•
Product-handling instructions for magazines, printed board assemblies,
•
cables, I/O devices and spare parts
Man-machine Communications including operating instructions for
•
panels, I/O devices and alarm system and command language rules.
Submodule B02
Subscriber-associated changes
•
Changes in the exchange data
•
Collection of statistics
•
Output of charging data
•
Size alteration
•
Functional changes.
•
Submodule B03
Time schedule for inspection
•
(General Operational Instructions):
(Operations Instructions):
(Maintenance Instructions):
Instructions for performing inspection of panels, I/O devices, sub-
•
16 03802-EN/LZM 112 17 R1
scriber line test-equipment
Procedure in event of alarm
•
Procedure in event of fault-observation
•
Instructions for fault-localization and repair.
•
Exchange Handling Basics
Submodule B04
Testing the APT, APZ, and power equipment in an in-service exchange.
•
Submodule B11
Functional descriptions of commands
•
Brief descriptions of parameters
•
Parameter combinations and formats
•
Examples
•
Expected types of printout after command input
•
Fault codes and their interpretations
•
Command category numbers.
•
The commands are listed in alphabetical order.
Submodule B13
Functional descriptions of printouts
•
Print headings
•
(Test Instructions):
(Command Descriptions):
(Printout Descriptions):
Interpretations of abbreviations
•
Procedure to be followed upon the receipt of a printout
•
Printout groups.
•
The printouts are listed in alphabetical order.
Submodule B14
Adaptation Directions
•
Application Information
•
Command Tables
•
Various lists including parameter lists, subscriber categories, alarm cat-
•
egories, size alteration events, end-of-selection codes (in both alphabetic and numerical order).
Adaptation Directions contain detailed functional descriptions of the commands and their parameters.
Application Information consists of documents which provide detailed
information, for each function block, as to the allowable value ranges that
may be assigned to parameters.
(Adaptation Directions):
Command tables are rarely used.
03802-EN/LZM 112 17 R1 17
AXE 10 Basic Operation and Maintenance Activities
3.5.2 Locating the Documentation
As we know now, the B-Module fills a big part of the exchange library.
Each B-submodule consists of one or several binders. They are divided
into sections (grey dividers). Each section is divided into subsections
(green dividers) and sometimes the subsections are divided into parts
(orange dividers). The dividers are numbered from 0 to 9.
The first binder of each sub-module contains a document list. This list provides the contents of all the binders contained in the particular submodule.
3.5.3 Accessing Information in the B-Module
The steps involved in accessing information in the B-Module are as follows:
1. Finding the Title of the Operational Instruction
There are two ways in which the operator is assigned a task and each way
contains the relevant Operational Instruction.
If the task is a response to an alarm, the operational personnel is to
•
access the OPI containing the same title as that found on the Alarm
Printout.
All other tasks are initiated as the result of Work Orders, the contents of
•
which will indicate the name of the necessary OPI.
Whatever the origin of the task, the OPI will be found in submodules B01
to B04:
Type of Task Submodule
Administrative activities B01
Handling I/O devices B01
Operational tasks B02
Maintenance B03
Testing B04
2. Finding Additional Information
Operational Instructions direct the staff to Command Descriptions
(CODs), found in B11, by listing the commands that may be needed. The
Command Description usually suffices, but if more details are required,
they are to be found in the Application Information document identified by
the Command Receiving Block named in the COD.
This course includes a number of operational activity related exercises
which will provide practice in the use of the B-Module.
18 03802-EN/LZM 112 17 R1
3.6 Using FIOL / DocView
DocView is a document retrieval tool for EDML-based Ericsson documentation, such as the Operation and Maintenance (O&M) documents.
EDML stands for Ericsson Document Mark-up Language. EDML was
developed by Ericsson and is an internal documentation standard.
DocView replaces the printed document binders and offers features for
browsing, searching and printing. The application is intended for any user
(designer, test and maintenance personnel) requiring flexible access to the
documents stored in the DocView databases.
The information stored in this document databases is easily accessed.
There are several hierarchical levels and a possibility to use context sensitive searches. Hypertext and Find features are provided to speed up access
to requested document. Any portion of the information may be accessed at
speeds that far surpass manual look-ups in printed binders. AXEUSE /
Dynatex will replace DocView and FIOL in the future.
Chapter 4 describes in detatailed the handling of DocView.
Exchange Handling Basics
3.7 Using AXEUSE / Dynatext
Up to now, Ericsson has provided FIOL as the only standard communication program for local AXE Operation and Maintenance. FIOL was originally designed as a test tool for internal usage within Ericsson, no focus
was originally placed on the needs of AXE 10 end-users.
AXEUSE (AXE US
that provides multi-channel communication with target systems. It is a
successor to FIOL and is a communication program combined with a
“Browser” for an On-screen Operation and Maintenance manual, running
under the MS Windows Graphical User Interface, GUI.
The AXEUSE package includes a copy of the Dynatext Browser, an application which enables the user to view “electronic books”. Using the Dynatext Browser, the user can read documentation pertaining to the
application system.
The approach used when designing AXEUSE was to create an environment which would increase the productivity of the Operation and Maintenance personnel. This is achieved by a graphical user interface designed in
accordance with current standards that meet known customer needs. The
environment also includes on-line documentation retrieval , Dynatext,
which provides context-linked information retrieval removing the tedious
task of browsing through the pile of binders just to perform a maintenance
task.
er Environment) is a Microsoft Windows application
AXEUSE is described in more detail in chapter 4.4 of this document.
03802-EN/LZM 112 17 R1 19
Loading...