RE: [plcs] New DEX 8 - Overview - V3

["Mcbride, Robert M" <robert.m.mcbride@lmco.com>]

Title: Message

Thanks Gordon, often takes me more than once.  It will help to see some practical applications that I know you and others are putting in place.  Discussions tomorrow in Norfolk will be timely.  Mind that shower door.

 

Mike

-----Original Message-----
From: Gordon Robb [mailto:gor@lsc.co.uk]
Sent: Thursday, September 02, 2004 11:02 AM
To: Mcbride, Robert M; Gordon Robb
Cc: Plcs E-mail; Tim Turner (Offsite); Tom Hendrix E-mail
Subject: RE: [plcs] New DEX 8 - Overview - V3

Hi  Mike,

How is LMCO.

We seem to be getting into the basic fundamentals of what a DEX is setting out to achieve.We see it as in principal sharing/exchanging a part of the AP 239 Assured Product and Support Information to meet a business requirement through a prescribed life cycle. The APSI (and its related information) could be held within a central repository and the ability of exchange/sharing a subset of that information is provided by the DEX.

 

DEX 8 was always going to describe the actual product in focus i.e what is the current configuration of my JSF.

 

My reworded DEX 8 business application words of 28 July 2004 tried to show the interfacing between the DEX's

 

" This DEX enables the exchange of information about a product as individual for the purpose of supporting that product throughout life (product in focus (PIF))

It provides unambiguous identification of the PIF for support management purposes, its life and usage is reported on by utilising other DEXs (see Dex D002: fault_states), the analysis of tasks required to be performed (see Dex D003: task_set), and the generation of a logical plan for support (see Dex D005: maintenance_plan).

The support solution is put in place (commissioned) for when the PIF is in build and thereafter in service. From this point on, information is collected and feedback is provided to the support facility (see Dex D007: operational_feedback).

If maintenance is required, then a package of work is defined (see Dex D004: work_package_definition).

Once the work is authorized and carried out, a report is produced to indicate when the work was completed together with any documentation required for the item repaired (see Dex D009: work_package_report)."

 

I thought those words 'bounded' the activities of the DEX 8.

 

If DEX 7 business application model is viewed it identifies all the requisite activities to report on usage against DEX 8, NigelN is following the DEX 7 model for the DEX 9 activities.

 

I hope this provides the clarification required.

 

regards

 

Gordon

 

 

 -----Original Message----- From: Mcbride, Robert M [mailto:robert.m.mcbride@lmco.com]
Sent: 02 September 2004 13:37
To: Gordon Robb
Cc: Plcs E-mail; Tim Turner (Offsite); Tom Hendrix E-mail
Subject: RE: [plcs] New DEX 8 - Overview - V3

Gordon:

 

Does the discussion on maintenance history include a reference from DEX 8 to the appropriate areas in 7 and 9?  My thought is that usage and maintenance history are attributes of Product as Individual/Realized and should be visible to users exchanging this type of data.  I agree the data should not be duplicated.  I guess it comes down to the expectation for a DEX.  If the intent is to provide for all of the attributes that could define Product as Individual/Realized then I would think the referencing would be expected and tailored down by users for specific needs.

 

Regards,

 

Mike

-----Original Message-----
From: Gordon Robb [mailto:gor@lsc.co.uk]
Sent: Thursday, September 02, 2004 5:16 AM
To: Tim Turner (Offsite); 'Tom Hendrix E-mail'
Cc: Mcbride, Robert M; 'Plcs E-mail'
Subject: RE: [plcs] New DEX 8 - Overview - V3

Hi Tim,

Hope you arrived safely and ready to represent our LSC thoughts to the OASIS PLCS TC.

In response to your email and to our conversion of yesterday - I (+ LesD & NigelN) do not think that usage and maintenance history are part of DEX 8. These are catered for by DEX 7 and DEX 9.

Also when looking at the PAP it must cater for the "In Service" environment where there is a 'product in focus' which is a realized product i.e. its got all the requisite identifiers including serialisation which is planned to be installed/fitted/integrated/implemented into/onto another product OR replace another product.

 

regards

Gordon

-----Original Message----- From: Tim turner [mailto:timturner11@bellsouth.net]
Sent: 01 September 2004 04:57
To: timturner11@bellsouth.net; 'Tom Hendrix E-mail'
Cc: 'Robert M Mcbride E-mail'; 'Plcs E-mail'
Subject: [plcs] New DEX 8 - Overview - V3

Attached is the latest Dex8 overview offering.

 

Dex 8 has a requirement to be able to represent usage and maintenance history.

 

At present I have interpreted maintenance history to be a set of representing_work_done. This is obvioulsy done with respect to the scheme that has been devised for the product, though this is not necessarily the same thing (i.e. scheme is not providing a record of what *has* been done). The Introduction of this capability (representing_work_done) states "The purpose of the "Representing work done" capability is to describe how a record of work that has been done can be represented. Examples of work done are:

• a maintenance task performed on some equipment;
• change made to some equipment in accordance with a technical bulletin.

Thus, I believe that this and it's dependant capabilities should suffice. Note this subsumes several other dependant capabilities.

 

With respect to the recording of usage, what are the other items (other than covered in feedback) that are required for this? Les, Gordon - any thoughts? I noted from Mike's earlier diagram that 2 capabilities are now no longer available (C025-Assigning Observation & C033-Representing Product Usage ) - have they been overtaken by others?

 

New items (dependant) on the overview have been circled - I had missed analysis result.

 

Again any feedback appreciated!

 

Regards,

Tim

-----Original Message-----
From: Tim Turner [mailto:timturner11@bellsouth.net]
Sent: 31 August 2004 09:30
To: timturner11@bellsouth.net; john.dunford@eurostep.com; 'Tom Hendrix E-mail'
Cc: 'Robert M Mcbride E-mail'; 'Plcs E-mail'
Subject: [plcs] New DEX 8 - Overview

All,

 

attached is a re-work of the Dex 8 overview for comment.

 

I think it still needs a little more work, but I'd valvue further comments on this.

 

Note, I have generated this from the Introduction where thee functional heading have come from (except for the generic parts).

 

Kind regards,

Tim

DISCLAIMER: ***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This e-mail originates from LSC Group. Registered in England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG

DISCLAIMER: ***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This e-mail originates from LSC Group. Registered in England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG