TSM - Description of the Symptom and Area Classification

Introduction
Symptom and Area classification is a four tier hierarchical structure that reflects both the functional
areas and the symptom areas.
Symptom area contains information about the "problem" of the machine (Product).
Each symptom will guide you, by means of a script, to a functional area in where you can find the
solution.
In the Area Classification you will find the solutions of the "Symptoms"

Symptom Classification
The symptom classification can contains of the following categories.
(The Symptom areas can be different per product).
Symptom area Description Example
Image Quality Problems with the quality of the image on
Spots
the copy.
Patches

Stripes

Colour
Registration Problems with the position of the image on The image
the paper.
Too high or too low

Shifted to the left or right

Skewed
Paper Path Problems with the copied paper that moves
Paper jam
through the machine.
Paper feed problems
Document handling Problems with the movement of the
Skewed original
original.
Stuck in the scanner

No recognition of the document
Display message A display message (text or pictogram) with Message
an instruction or warning machine
Remove the paper jam
message.
Error message A message on the console that results in a A 5 digit number
system stop
00 2 10
Power A power problem. Power problem
The system does not receive power.
Machine death

No power
Printing Problems with the actions to print a digital
Does not print
document (file).
Scanning Problems with the actions to scan an
The image is not good
original to a digital document (file) (Scan to
file).
Noise Any strange sound / noise that can not be
explained.
Operator handling Questions that relate to the use of the
How to add an inktank
machine / software.
How to replace a print head

Area classification
The Area Classifications describes in a four tier hierarchical structure the functional areas.

Known problems

Frequently Asked Questions

Installation

Adjustments

Etc.
The Area classification can contains the following categories. (The Areas can be different per
product)
Symptom area Description Example
Job Submission This area handles about issues while All drivers
submitting data to the device. All
Autocad HDI
information about drivers and jobsubmitIT
Autocad ADI
can be found in this area. Job submission
Print Exec LT Web
is done on a user environment (e.g.
workstation).
Job Control This area handles about issues that Controls of a job
controls the job on a device.
RCF

Océ Job Ticket

Controller applications

Remote Logic
Job Processing This area handles about issues that Interpreters
translates jobs from a PDL (page definition
HPGL / HPGL/2
language) to a device specific format.
PS3
Job processing is handled on the
PDF
controller.
Communication The area handles about all communication Protocols
protocols between network and device
LPR/LPD
resides. For example.
FTP
Controller The area handles everything that is directly Hardware issues
related to the controller.
Operating system

Hardware

Interfaces
Engine This area handles all engine-related
Ink Handling
information about the physical Engine
Measurement & Control
(previous known as CAS codes).
Print Head
Scanner This area handles all scanner related
Originals
information about the physical scanner.
Image Processing

Power & Control
TSM - How to Navigate in the documentation

Introduction
The entrance of the TSM is always the Symptom and Area Classification (SAC).
The SAC shows always the same structure.
It depends on the slected view what you see in the SAC structure.
The sections below describes:

Main Navigator buttons

TSM subject buttons

Partslist subject buttons

SDS subject buttons

Note:

Use the Main Navigator Button TSM if you want to have all the information available about a
specific Area (e.g. Engine / 02 ink Handling).

Use the TSM Subject Buttons if you search for a specific type of information (e.g. Only
installation documents).

Main Navigator Buttons

Main Navigator Buttons Function
This view shows all the functional documents per SAC group. All informati
about a functional area is put in a SAC group.

This view shows all the parts list documents per SAC group.

When the Bulletins / local information database is available, the button lin
to the database.

This view shows all the SDS tests per SAC group.

This view shows all the non-product related information.

Examples are:

How to start SDS

How to set-up communication between the laptop and the Océ 940

TSM Subject Buttons

TSM Subject Buttons Function
Shows all the Diagnostic documents only.
The Diagnostic documents are put in the group Symptom Classifcation an
 the Area Classification only.

Shows all the Frequently Asked Questions (FAQ) in the same SAC structu

Shows all the Known Problems in the same SAC structure.

Shows all installation documents in the same SAC structure.

Shows all Specification in the same SAC structure.

Shows all Maintenance documents in the same SAC structure.

Shows all Adjustments in the same SAC structure.

Shows all Dis-assemblies in the same SAC structure.

Shows all Functional Descriptions in the same SAC structure.

Shows all Component locator in the same SAC structure.

Shows all Electrical Diagrams in the same SAC structure.

Show all the CAS-Cards in the Area Classification group.

Parts list Subject Button

Parts list Subject Buttons Function
 Show the parts list per SAC-group.

Visualises the break-down of the machine.

SDS Subject Button

SDS Subject Buttons Function
Show all the SDS 01 - 29 Function tests per SAC-group.

Show the Analysis tests (on highest level of Area Classification).

Show the System tests (on highest level of Area Classification).

Show the Installation tests (on highest level of Area Classification).

Show the Marketing info tests (on highest level of Area Classification).

Show the Service info tests (on highest level of Area Classification).

Make a link to the Web SDS if available.

TSM - How to navigate through the TSM with the keys of the keyboard

Introduction
You can use the mouse to navigate through the TSM.
Another method is to use the keys of the keyboard.
This section gives you a description of the keys of the keyboard and their result.

Component - function table

Keyboard Result on View-level Result on Document-level
stroke
Alt The number is displayed on buttons of the The number is displayed on buttons of
Toolbar. Press the number results in: the Toolbar. Press the number results in:

Activation of the button.
Activation of the button.

Opens the pull down menu.
Opens the pull down menu.
Alt 3: Activates the SDS session Alt 2: Creates an Annotation
Esc Closes the TSM. Closes the current document.
Enter Depends on the position of the cursor.Opens Opens the next document in the opened
the: SAC-level.

SAC level.

Type of document.

Document.
Tab / F4 Selects the next not read document. Opens the next document.
Arrow left / Moves the view to the left / right. Select the next / previous Section or Link.
right
Arrow up / Moves to the next Level, document. Moves the contents up / down (scrolls).
down
Space bar Selects a level / document ((v) in front of the
Opens / closes the section.
selection).
Opens / closes the section.
+ Expand the current View. None
- Collaps the current View. None

Note:

You can find more keystrokes in the Help of the Lotus Notes TSM.
TSM - The function of the buttons in the toolbar of the TSM

Introduction
The toolbar supports you if you use the TSM.
This document describes the function of the buttons of the toolbar in the TSM.

Component - function table

Toolbar buttons Function
The
Navigation
button allows you to Expand / Collap

The
Exit Database
button closes the
database (You can use the Esc-key also).

The
Collapse All
button closes the
complete SAC structure.

The
Collapse Selected Level
button cl
complete current SAC level.

The
Expand All
button expands th
complete SAC structure (shows all the levels).

The
Expand Selected Level
button ex
the complete current SAC level.
The Annotations are the remarks a person makes on the TSM.

The
Create New
button creates a n
annotation. A new document is made. The annotation is put in the SAC
of the view opened.

The
Open Database
button opens the
annotation database.
Note:

For the complete information about the annotations, go to the documen
TSM - The process of the annotations in the TSM
Opens the SDS session document. The test in the document starts the SD
connection between the system and your laptop.

Search on text strings.

Result: All documents sorted on Title - Path - Type of document.
Print the selected documents.

Supports you in using the manual.

The
Help
button opens a help databa
the Manual.

The
About this document
button sh
the status, the release date and version of the selected document.

The
About this TSM
button shows you
Version and Design number of the TSM.
Select
Release Notes
and press the OK
The release notes give an overview of main changes (e.g. Software rel
TSM - The process of the annotations in the TSM

Introduction
The function of annotations is to make remarks, hints on the TSM to improve your efficiency.
These remarks can be for your own use, or even for your colleagues in your country.
If the annotation is useful for the complete Océ organisation, then you escalate the annotation to
Océ Venlo (HQ). The quality of the TSM improves with this feedback.
This document has 2 subjects.
1 The process of the annotations.
2 How you create and how you read the annotations.

Illustration

The process of annotations

You can make the annotation on a specific document or view.
The illustration shows you the process flow and the table below explains the flow.
Stage Description Action
 Create annotation Create the annotation for Privat use.
Only the owner can see the annotation

Escalate to SPM The Annotation is sent to the SPM.

Only the owner of the annotation and the SPM
can see the annotation.

Publish to OPCO The SPM decides to send the Annotation to all

the local users of this TSM.

Publish to HQ The SPM decides to send the Annotation to

HQ.

The annotation must be in the English
language.

The annotation gets a number
(HQ-Language-Year-sequence number).

Handled by HQ The annotation is handled by HQ and the Action by HQ employee.

information is added or changed in the TSM.

Note:

The action depends of the role of the user.

The users with the role TeCo can publish the annotation to OpCo and HQ. The users with the role
TeCo can delete (public) annotations also .