User Manual
Preface
9500 MPR Rel. 3.1
3DB18809AAAA Issue 126/980
General on Alcatel-Lucent Customer Documentation
This paragraph describes in general the Alcatel–Lucent Customer Documentation system, details the
association between the product levels and the associated documentation, and explains Customer Doc
-
umentation characteristics as well as the policies for its delivery and updating.
Customer–Independent Standard Customer Documentation
a) Definition
Standard Customer Documentation, referred to hereafter, must be always meant as plant–indepen-
dent and is always independent of any Customization.
Plant–dependent and/or Customized documentation, if envisaged by the contract, is subjected to
commercial criteria as far as contents, formats and supply conditions are concerned.
N.B. Plant–dependent and Customized documentation is not described here.
b) Aims of standard Customer Documentation
Standard system, hardware and software documentation is meant to give the Customer personnel
the possibility and the information necessary for installing, commissioning, operating, and maintain
-
ing the equipment according to Alcatel–Lucent Laboratory design and Installation Dept. choices. In
particular:
• the contents of the chapters associated to the software applications focus on the explanation
of the man–machine interface and of the operating procedures allowed by it;
• maintenance is described down to faulty PCB location and replacement.
N.B. No supply to Customers of design documentation (like PCB hardware design andproduction
documents and files, software source programs, programming tools, etc.) is envisaged.
Product levels and associated Customer Documentation
a) Products
A “product” is defined by the network hierarchical level where it can be inserted and by the whole
of performances and services that it is meant for.
E.g. 9500 MPR-E is a product.
b) Product-releases
A ”product” evolves through successive “product–releases”, which are the real products marketed
for their delivery at a certain ”product–release” availability date. A certain ”product–release” performs
more functionalities than the previous one.
E.g. Rel.1.0 and Rel.2.0 are two successive “product–releases” of the same “product”.
A “product–release” comprehends a set of hardware components and at least one “Software Pack-
age” (SWP); as a whole, they identify the possible network applications and the equipment perfor-
mances that the specific “product–release” has been designed, engineered, and marketed for.
c) Configurations and Network Elements
In some cases, a “product–release” includes different possible “configurations” which are distin-
guished from one another by different “Network Element” (NE) types and, from the management
point of view, by different SWPs.
d) SWP releases, versions, and CD–ROMs
• Each SWP is distributed by means of a specific SWP CD–ROM.
• A SWP is identified by its “Denomination”, “P/N” (Part Number) and “CS” (Change Status), that
are printed on the CD–ROM’s label:
– the first and second digits of the “Denomination” (e.g. 2.0) correspond to the “HW product–
release” number;
– the third digit of the of the “Denomination” (e.g. 2.0.2) identifies the Version Level of the
SWP.
To Next Page
Loading...
