Overview
Receipt
Edit
Browse
Enquiry
Reports
|
|
|
| Overview | Other People's Technical Documents are defined as those
over which you no rights except to make comments. Each revision of an Other People's Technical Document may have an attachment, viz the published edition. It is STRONGLY recommended that published editions should be in a format that is not editable, but capable of being marked up, e.g. PDF format. It is strongly suggested that the filename of the electronic versions of a document revision is based on the maker of the document plus the document plus the revision: e.g. MAKER1_DOCUMENT1_REV.pdf . This may involve renaming the document. If the EDM system is enabled (See Setting to Work, Parameters and How TDOC Works, About EDM), then when an attachment is made to a revision of a document, it is automatically moved to the nominated directory for Others Technical Documents. Project (or Secondary) numbering is NOT recommended unless absolutely necessary, and is set at Job level. See Administrative Registers, Jobs Register. Each revision of a document may have a system status and comment allocated to it. There are three ways to allocate this:
The cycle of movements of an Other People's Technical
Document are shown in the diagram below:
|
| Back to Contents | |
|
|
|
| Receipt | The receipt of Other Peoples Technical Documents is
accomplished in three steps:
|
| Transmittal | The transmittal information consists of:
There are two options to speed up data entry:
|
| Detail | |
The detail of the document is split (as indicated in
the overview) into three parts:
Validation is made as the revision date is entered to
ensure that the revision and its dates are in an acceptable sequence.
If this fails, then a warning is shown. The following is a typical
example: The warning shows the existing and new revision and the existing dates, and any appropriate message. The option to allow the revision date to be out of sequence should be used with care. Usually the problem should be corrected immediately by using the Document Utilities module to transform the revisions so that they are in date sequence. Once the information has been saved, then
|
|
| Attachments | The attachments tab serves two purposes:
|
| Back to Contents | |
|
|
|
| Edit | The principal function of the browse is to enable the revision or document to be amended to be located. |
| Browse | |
| Edit | All the information entered when recording the receipt
of a document may be edited apart from:
The following allocations may be made:
|
The revision revision date is checked, and if it is found to be out of sequence, then a message is displayed. The following is an example: A valid date must be entered. |
|
| Status | TDOC keeps the history of the system status for a
revision of a document. A Document inherits the Status of the last
revision to have a status, and indicates if this is NOT for the latest
revision. The Issues mechanism checks that every revision of a document being returned has a Status. Inheritance is not considered. TDOC is designed to operate with a status for a revision of "No Status". Manually allocating such a status negates the checks. |
| When the Status button is clicked, it is assumed that the user wishes to add a new status, so the mode is set to Add. If there is one or more existing status, pressing the Cancel button will put the user into Edit mode. The status which is current cannot be changed except by adding a new one which then becomes the Current Status. | |
| Back to Contents | |
|
|
|
| Browse | The Browse is a means of conducting research within the
document register. The browse has two levels of filtering:
|
| Complex Filter | |
| Document List | The System Status for a documents is inherited from the last revision to have a status. The date shown is that on which the status was allocated. |
The context menu also enables:
|
|
| Document Enquiry | |
| Back to Contents | |
|
|
|
| Enquiry | The enquiry is similar to that generated for a single
document from the browse, except that all Jobs, Makers, and Documents
are shown. The context menu enables:
|
| Others Documents Enquiry |
Click to view sample Report. |
| Back to Contents | |
|
|
|
| Reports | There is only one report for generating the Register of
Other Peoples Technical Documents. One additional and important task is to ensure that documents which have been received and require to be returned have been allocated a Status and Comment, and then returned. There is a report dedicated to monitoring this. Both reports are similar, and have multiple options enabling virtually any report to be generated. There are other reports for expediting actions by third parties, and for maintenance activities, which are listed below. The selection options include:
In order to assess the "scale" of a possible problem, a facility exists via the Count button to count the number of documents and their revisions which meet the specified criteria before a report is generated. |
| Specify Scope | Once the JobNo has been selected, and if a Maker has
been specified, the Scope button is enabled. Its use enables a range of
documents for the specified Maker to be selected. |
| Specify Others Report |
|
The Others Document Report may additionally be filtered
by:
|
|
| View Reports |
Click to view
a sample Documents Only report. Click to view a sample Documents, Revisions, & Movements report. |
| Specify Returns Report |
|
The Returns of Others Documents Report may additionally
be filtered by:
|
|
| View Reports |
Click to view a sample All Returns report. |
| Other Reports |
Please see the following for reports and ways of
expediting actions expected of third parties on other people's
documents:
|
| Maintenance Reports |
There are three reports which assist with the
management of information:
|
| Linked Documents | Click to view a sample report. |
| Incoming Document Numbers | Click to view a sample report. |
| Metrics | Click to view a sample report. |
| Back to Contents | |
|
|
|