Docstoc

Maintenance Template

Document Sample
Maintenance Template Powered By Docstoc
					   Issue
            Template Name
  Number
           DEX (D011):-
           aviation_maintenance
BCR1-004   Date: 2008/03/10
           10:36:16 Revision:
           1.145


           DEX (D011):-
           aviation_maintenance
BCR1-005   Date: 2008/03/10
           10:36:16 Revision:
           1.145




           DEX (D011):-
           aviation_maintenance
BCR1-006   Date: 2008/03/10
           10:36:16 Revision:
           1.145




           DEX (D011):-
           aviation_maintenance
BCR1-007   Date: 2008/03/10
           10:36:16 Revision:
           1.145



           DEX (D011):-
           aviation_maintenance
BCR1-008   Date: 2008/03/10
           10:36:16 Revision:
           1.145
           DEX (D011):-
           aviation_maintenance
BCR1-009   Date: 2008/03/10
           10:36:16 Revision:
           1.145




           DEX (D011):-
           aviation_maintenance
BCR1-010   Date: 2008/03/10
           10:36:16 Revision:
           1.145




           DEX (D011):-
           aviation_maintenance
BCR1-011   Date: 2008/03/10
           10:36:16 Revision:
           1.145




           DEX (D011):-
           aviation_maintenance
BCR1-012   Date: 2008/03/10
           10:36:16 Revision:
           1.145




           DEX (D003):—
           task_set
BCR1-022   Date: 2008/03/11
           17:07:00 Revision:
           1.67


           Template:
BCR1-030
           assigning_concession
           PLCS DEXs Version
BCR1-060
           R1




           DEX (D003):—
           task_set Date:
           2008/03/11 17:07:00
           Revision: 1.67, and
BCR1-079   DEX (D011):-
           aviation_maintenance
           Date: 2008/03/10
           10:36:16 Revision:
           1.145
           DEX (D003):—
           task_set Date:
           2008/03/11 17:07:00
           Revision: 1.67, and
BCR1-094   DEX (D011):-
           aviation_maintenance
           Date: 2008/03/10
           10:36:16 Revision:
           1.145
           DEX (D003):—
           task_set Date:
           2008/03/11 17:07:00
           Revision: 1.67, and
BCR1-128   DEX (D011):-
           aviation_maintenance
           Date: 2008/03/10
           10:36:16 Revision:
           1.145
           DEX (D003):—
           task_set Date:
           2008/03/11 17:07:00
           Revision: 1.67, and
BCR1-129   DEX (D011):-
           aviation_maintenance
           Date: 2008/03/10
           10:36:16 Revision:
           1.145
           DEX (D003):—
           task_set Date:
           2008/03/11 17:07:00
           Revision: 1.67, and
BCR1-132   DEX (D011):-
           aviation_maintenance
           Date: 2008/03/10
           10:36:16 Revision:
           1.145


           Reference Data
BCR1-189
           comments



           Reference Data
BCR1-190
           comments




           Reference Data
BCR1-191
           comments
           Reference Data
BCR1-192
           comments
           Reference Data
BCR1-193
           comments




           PLCS Help & Info
BCR1-203
           Pages




           PLCS Help & Info
BCR1-204
           Pages




           PLCS Help & Info
BCR1-205
           Pages
           PLCS Help & Info
BCR1-216
           Pages




           PLCS Help & Info
BCR1-217
           Pages




           DEX (D011):-
           aviation_maintenance
BCR1-239   Date: 2008/03/10
           10:36:16 Revision:
           1.145



           DEX (D011):-
           aviation_maintenance
BCR1-244   Date: 2008/03/10
           10:36:16 Revision:
           1.145


           DEX (D011):-
           aviation_maintenance
BCR1-253   Date: 2008/03/10
           10:36:16 Revision:
           1.145




           Terminology
BCR1-254
           comments




           Reference Data
BCR1-258
           Classes



           Reference Data
BCR1-259
           Classes
BCR1-261   Reference data
                                                                                             Core Team
                                Issue Description
                                                                                              Review?
Aviation maintenance Business Information Overview - Message wrapper

Use of data is incorrect. Change to information


Aviation maintenance Business Information Requirements -
Engineering_instruction

Routine Technical Instructions - is this RAF jargon [or RAF CE Instruction etc]. The
use of Special Technical Instruction & Servicing Instructions are not 'routine'

Change para to read Technical Instructions. See Def Stan 05-123 Pt 4 for
guidance

Aviation maintenance Business Information Requirements -
Engineering_Instruction

Last sentence [EIs are the main authority for making changes, although changes to
part numbers may also be effected by a design amendment and changing the life
or required maintenance of an item may also be effected by the Engineering
Authority, without an EI (provided that the part number does not change ] - EIs are
the main authority for making changes, although changes to part numbers may also
be effected by a design amendment Design Amendment DO NOT change Pt. No's.
This could be a case of using a 'bad expression' "amendment". An amendment in
the Design world is a minor change to the design that does not change the Pt.No. A
Modification leaflet WILL change the Pt.No.

Change design amendment to 'modification leaflets'
Aviation maintenance Business Information Requirements -
Resource_part.supplier_code

Note - The supplier code is the code identifying the manufacturer/supplier. Often
                                                                                  Core Team Review
CAGE code. ..CAGE is incorrect. NCAGE is the correct term: See NCB web site
http://www.isisweb.mod.uk/wwwisis/navigate.do Change to NCAGE throughout the
DEX

Aviation maintenance Business Information Requirements - Message -
Controlled_exchange

This activity reports when there is any removal of a serviceable reportable item from
one aircraft for installation on another aircraft This activity is usual referred to as Ac
Robbing Certificate [RAF Form 7213-a]

Insert reference to the 'Robbing certificate'
Aviation maintenance ISO 10303-239 Representation - Representing a
reportable item, PLCS representation

The Stock Code, e.g. NSN is a definition of the fit, form and function, or
interchangeability of a part.

This is an incorrect statement. FFF disappeared [correctly] in the 1980s and was
replaced with interchangeability. See DS 05-970//123

Amend sentence to read "The Stock Number, e.g. NSN is a definition of the
interchangeability of a part.
Aviation maintenance ISO 10303-239 Representation - Representing change
of Part Number, Serial Number, and NSN, Business information

This typically occurs when a change is made to the fit, form or functionality. It may
also be the case that temporary identifiers are allocated as the correct identifier,
e.g. Part number is not known.

Used of Form, Fit Function is incorrect. Change to interchangeability
Aviation maintenance ISO 10303-239 Representation - Representing change
of Part Number, Serial Number, and NSN, PLCS representation

The Unique Identification (IUID) from the Department of Defense (DoD) is another
identification of the Product_as_individual and is represented by an
Identification_assignment represented by template #7 and #15
assigning_identification and classified as "UID" (urn:plcs:rdl:std:UID).

This statement requires amending. The DoD refers to it as Item Unique
Identification [IUID]. This DEX incorrectly uses the correct abbreviation and the
wrong description in a number of areas.
Aviation maintenance ISO 10303-239 Representation - Representing deferred
activities, Business information

The statement "There will be occasions due to operational constraints when these
tasks need to be delayed or brought forward due to damage or stress. ”

Seems inappropriate. If it stress related or damaged there is usual one course of
action in that the activity is brought forward

Change to read "There will be occasions due to operational constraints when these
tasks need to be brought forward due to damage or stress."


Reference Data Library

The element labour_time_planned has the same definition as
labour_time_consumed.

Revise definition for labour_time_planned to indicate that it is planned labour hours.
Reference data has been assigned to the Approval entity. The reference data
should have been assigned to the Assigning_approval entity - as a replacement for
the Assigning_approval.role attribute.
OASIS PLCS committee draft public review

The following format of central terms should be used through out the specification
(not the case in the reviewed edition);

DEX
Data Exchange Specification
Template
Capability
Reference Data


DEX comments - Common to both DEXs

DEXlib has the functionality to link terms to the definitions in the terminology       Core Team Review
section. Shouldn't this possibility be used in the DEXs, e.g to link "ICAM" in the AAM
section of the DEXs to its definition.




DEX comments - Common to both DEXs
Terms

A link to the 'Terminology' section of DEXlib at the the end of the Terms page could
be useful if a user needs to understan terminology not specific to the DEX.




DEX comments - Common to both DEXs
Reference Data

The URN-links doesn't lead to the specific class, only to the "Referernce Data Class
Viewer" "All classes" view.




DEX comments - Common to both DEXs
Reference Data

The table should show the class label, not the id, e.g. instead of
"Access_description" the table shall show "Access description".
DEX comments - Common to both DEXs
Conformance

The Referernce Data Classes used by the DEX are not only listed in the 'Ref. data'
section, but also here. Could a link to the 'Ref. data' section be enough?!


Reference Data

The Reference Data in the review package has not been through any of the
                                                                                            Core Team Review
intended review stages and are in general in a poor condition/does not conform to
the guidance in the (not balloted) Reference Data Checklist in DEXlib. A detailed
review of this part of DEXpub is not useful at this stage.
Reference Data

Links to the Reference Data Class viewer do not lead to the class referernced by
the link, but to the top of the viewer page.
Reference Data
RD class viewer
The linked document "RD viewer comments.doc" contains a suggestion for a
new layout for the RD Class viewer.

RDL File: developer-draft/plcs-std-rdl.rdf-xml.owl (1)
Filtered by OASIS Stage : Developer Draft
Title:
Version:
Stage:
Description:

Class Activity_identification_code [urn:plcs:rdl:std:Activity_identification_code] [file:
developer-draft/plcs-std-rdl.rdf-xml.owl 1]
Source:PLCS OASIS Creator:Rob Bodington, Eurostep Limited
Definition:
An Activity_identification_code is an Identification_code that is used to identify an
activity that is planned or has happened. EXAMPLE: The identification of of a
planned activity in a project plan or the identification of a maintenance activity that
happened last week. CONSTRAINT: An Identification_assignment classified as an
Activity_identification_code can only be assigned to an Activity or Activity_actual or
their subclasses.

CLASS Activity_identification_code;
SUBCLASS OF ( Identification_code );
END_CLASS;
Reference Data
RD class viewer (cont'd)
The linked document "RD viewer comments.doc" contains a suggestion for a
new layout for the RD Class viewer.

Comments on RD class and the current presented view in DEXlib (personal
opinions)

1. Line break after the Class identifier
2. Move source and creator to the bottom, (add date?), and reduce font size
3. All small letters in class identifier
4. Start definition text with small letter
5. Start definition text with superclass label
6. All definitions should be able to replace the label of the defined class in running
text
7. Hyperlink all defined RD used in the definition text, example text and constrain
text
8. Create OWL properties named ‘example’ and ‘constraint’
9. Display examples and constraints in separate sections
10. Remove the code section and replace with a note only on the super class
11. Creators of PLCS std RD should state role/group in TC instead of company (?)
Reference Data
RD class viewer (cont'd)
The linked document "RD viewer comments.doc" contains a suggestion for a
new layout for the RD Class viewer.

I believe all my format related comments are according to the 15926 guidelines!
This would look like;

Class activity_identification_code
 [urn:plcs:rdl:std:activity_identification_code] [file: developer-draft/plcs-std-rdl.rdf-
xml.owl 1]

Label: activity identification code (English)

Definition:
an identification code (identification_code) that is used to identify an activity
(activity) that is planned or has happened.

Example:
The identification of a planned activity in a project plan or the identification of a
maintenance activity that happened last week.

CONSTRAINT:
An identification assignment classified as an activity identification code can only be
assigned to an activity, activity actual or their subclasses.

SUBCLASS OF: identification_code

Source: PLCS OASIS
Creator: Rob Bodington, OASIS PLCS TC - Technical Oversight Group
Creation Date: 2008-03-03
PLCS Help & Info Pages
OWL - Web Ontology Language

OWL concepts section; 'Individual' is explained and said to to be used for PLCS
Reference Data, but this in not the case?! 'Superclass_of', 'Disjoint_with' is used for
PLCS RD, but not explained.
PLCS Help & Info Pages
OWL - Annotation properties

The annotation properties 'OASIS_stage' and 'OASIS_revision' are not Dublin Core
meta data and should therefore not use the 'dc' prefix.
PLCS Help & Info Pages
PLCS Techical Description

The definitions of the PLCS components should be the same as in the Terminology
section, with the difference that the name of the component should be included in
the text when in the 'Help/Information' section, but not when in the 'Terminology
section'.
PLCS Help & Info Pages
PLCS Techical Description
Templates

There is a lot of text in the beginning of the 'chapter' that has no chapter title. A
sutible chapter title should be inserted.
PLCS Help & Info Pages
PLCS Techical Description
Reference Data

There is a lot of text in the beginning of the 'chapter' that has no chapter title. A
sutible chapter title should be inserted.
DEX 011 Aviation Maintenance
General
The spread sheet "LG-Issues.xls" contains comment from Leif Gyllström on
D003, D011 and Infrastructure.

Use of 'urn:plcs:rdl:AVM' should not be allowed within an OASIS std DEX. Replace
by use of 'urn:plcs:rdl:std'.
E.g. Template table #3 (figure 21) for value property 'property_ecl_id'.'
DEX 011 Aviation Maintenance
Template table #11 (figure 13)
The spread sheet "LG-Issues.xls" contains comment from Leif Gyllström on
D003, D011 and Infrastructure.

Parameter 'org_type_class_name' need to be redefined. Should at least be a
subtype of class 'Organization_type'.
Terminology

Generally agreed Terminology principles (as used by ISO 15926 and described in
the OASIS PLCS Reference Data Checklist) should be used regarding the format of
the definitions, e.g. the defined term should not be used in the definition. The
complete list of terms should go through a quick review if time doesn't allow a
complete review.
Terminology
Terminology start page

The 'Terminology' section doesn't have a start page explaining it's use or content.
Such a page would be better to load when the 'Terminology' field in the nav bar is
clicked. From this page one could then chose to load the t.o.c. to the left pane. (I
actually clicked the link three times without noticing that the index appeared to the
left. I thought something was wrong... /MatsN)
Reference Data Classes

The reference data classes included in the review are insufficient. We had earlier      Core Team Review
classes for each unit which has disappeared, so now it is not possible to say (with
ref data) that the length of something is 0.34 metres.
Reference Data Classes

Also, reference data should possibly be managed differently if the data is really a
class (subtype of a PLCS entity) or if the data is a member of such a class ("metre"
is a member of a possible class "length_unit").
Reference Data

The OWL reference data files contains HTTP URIs - the documentation contains
URN.

The documentation should be changed to use URIs as per the OWL file, or it    Core Team Review
should be made clear that the URN in the documentation which HTTP URI the URN
resolves to.

The HTTP URIs should reflect the location of the OWL files on the OASIS site
docs.oasis-open.org
Resolver         Resolution (Accept, Reject, Comments)


Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group
Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group



Reference Data
Project Group
Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group
Reference Data
Project Group




Reference Data
Project Group



Reference Data
Project Group




Reference Data
Project Group
Reference Data
Project Group
Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group
Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group




Reference Data
Project Group



Reference Data
Project Group
Reference Data
Project Group

				
DOCUMENT INFO
Description: Maintenance Template document sample