Aims Of Standard Customer Documentation - Alcatel-Lucent 1850 TSS-320 Engineering Rules

General on Customer Documentation
............................................................................................................................................................................................................................................................

Aims of standard Customer Documentation

Standard Customer Documentation, referred to hereafter, is always meant as plant–
independent.
Plant–dependent documentation, if specified by the contract, is subject to commercial
criteria based on content, format, and supply conditions. Plant–dependent documentation
is not discussed in this document.
Standard hardware and software documentation is meant to provide customers with the
information necessary to install, commission, operate, and maintain the equipment
according to ALCATEL-LUCENT Laboratory design choices.
In particular, the content of documents associated with software applications focus on the
explanation of the man–machine interface and the operating procedures allowed.
Maintenance is covered to the faulty PCB location and replacement level.
Consequently, design documentation (like PCB hardware design and production
documents and files, software source programs, programming tools, etc.) is not supplied
to customers.
Hardware-specific documents (usually the "Technical Document") and software-specific
documents (usually the User Provisioning Guide, see
not part of the standard documentation set because they are not necessarily impacted by
product changes.
For example, only the Technical Document might be revised because of hardware
configuration changes (for example, replacing one unit with another that performs the
same function but has a different P/N).
On the other hand, the User Provisioning Guide, see
be updated because of a new software version. Changes in software versions do not impact
the Technical Document as long as it does not imply hardware modifications.
Both document types can be updated to improve content, correct errors, etc.
Updating document
The documents associated with this product release are listed in
(p. 1-x). Each document is identified by:
the name of the product–release (and version when the document is applicable to the
•
versions starting from it, but not to the previous ones)
the document name
•
the document Part Number (P/N)
•
............................................................................................................................................................................................................................................................
A - 2
Aims of standard Customer Documentation
"Related information" (p.
"Related information" (p.
"Related information"
1-x)) are
1-x), may
PN 8DG 08763 GAAA
Issue 1 March 2009