OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

plcs-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Comments on Public View of Task DEX


Comments by Gordon Robb - LSC Group

 

1. Introduction 

 

Reference: - information required for through life configuration change
management of a product and its support solution.

 

This should be changed to just Configuration Management. The subject
matter of Task deals with the overall CM of the product and not just
CCM.

 


2. Related DEXs


The information exchanged by the Task Specification DEX is normally
between a product developer and a customer/end-user. It is assumed that
each party has access to the Product information including breakdowns,
equipments, components, effectivities etc. 

The Product Information should be changed to the correct terminology of
Product Configuration Information.

DEX (D001):- Product Breakdown for Support. This DEX can be used to
specify the as designed product structure of an aircraft, including
configuration effectivities. It will incorporate a breakdown structure
detailing what parts can be fitted into which positions on the aircraft.


*	I would have expected this cross-reference to DEX1 to read
exactly the same as the Avn Mnt DEX viz DEX (D001):- Product Breakdown
for Support. This DEX can be used to specify the as designed product
structure of an aircraft. It will incorporate a breakdown structure
detailing what components can be fitted into which positions on the
aircraft; 

*	The 'configuration effectivities' is basically incorrect - the
DEX does not use the "Configuration Effectivity" module but a series of
'effectivity' templates

*	Why isn't the DEX using DEX 8? There will be occasions where the
'product' is in-service and requires additional Tasks.

3. Scope

Identification of the product (supported item), to which the task
applies. The Avn Mnt DEX uses "Reporting the authorisation to undertake
a maintenance task on a reportable item (an asset)"

This diversion from 'standardized PLCS jargon' between the 2 OASIS PLCS
DEXs COULD be confusing for new 'players'. This Task DEX uses PIF
[Product in Focus] throughout. Could this be resolved to a 'PIF'
statement in both DEXs?

 


4 ISO 10303-239 Activity model definitions 


Identify potential task


*	2nd bullet - configuration change management tasks to be
undertaken by support participants such as fitting a local modification
or conducting an audit of product configuration; 


*         This statement seems very confusing. The subject matter should
be Configuration Management not CCM.


*         What is a 'local modification'


*         What is 'an audit of product configuration' 


The statement should be corrected to read "Configuration Management
tasks to be undertaken by support participants such as modification
implementations or conducting a physical configuration audit of the
product'.


5. Detailed Information Requirements 


Product in focus identification 


*         Identification of the product in focus to which the task
specification applies. Identification of the product in focus includes
the progression codes such as revision numbers. 

What are progression codes?


6. Information Requirements Overview


*         Task effectivity / applicability


	*	The validity of a task, or part thereof, may be
constrained to a specific context. These constraints are referred to as
effectivity or applicability

Why a 'or' when the rest of the script uses '/' and (_) and in reality
why mention applicability at all when no reference is placed on its
usage. 

 

 

 


 


 


 


 

 

 


 


 

 

________________________________


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 Ltd. Registered in England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, 
Plymouth, PL1 4SG, having a place of business at Lincoln House, Wellington Crescent, Fradley Park, Lichfield, Staffordshire WS13 8RZ and at Catherine House, 
40a St Thomas Street, Weymouth, Dorset DT4 8EH. VAT number: GB 655 1330 55. 

Please consider whether it is necessary to print this e-mail


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]