RE: [plcs] Global rules in the AP

[Tim King <tmk@lsc.co.uk>]

Title: RE: [plcs] Global rules in the AP

Dear All,

I think David makes important points.  I take Les' perspective to be the informed business one but I think that we should avoid business constraints as opposed to information sensibility constraints in the AP (especially at this stage in the game ... let us keep something for the Edition 2 that we are all no doubt looking forward to preparing ;-).  I would agree that there is probably a hazy line between the two types of constraint.  However, if business practice throws up any counter example (however counter intuitive?) then the desirable business constraint is too rigid to be compatible with likely data sets.  The Norwegian frigate has thrown up a counter example that suggests that it is possible to not assign a serial number to a product as realised and that the link through to the Resource_item identifies the product as realised in that context.  Given this situation, I think we have sufficient grounds to reject what is otherwise a reasonable candidate for a global rule.  (But what do I know ... I am only a mechanical engineer ...)

Cheers,
Tim.

-----Original Message-----
From: David Price [mailto:david.price@eurostep.com]
Sent: 28 October 2004 14:35
To: plcs@lists.oasis-open.org
Subject: RE: [plcs] Global rules in the AP

Hi all,

I think the AP239 approach to having a flexible model standardized in ISO that can be specialized outside ISO is a great idea. It also makes it very different from AP203, AP210, etc. I'd suggest not adding anything except the most obvious global rules to the schema itself. For example, I even think you'll have a problem with the identification_assignment requirement as that means you've made many conforming PDM schema files non-AP239-conforming. Many STEP exchanges use attributes for id and name.

Cheers,
David

-----Original Message-----
From: Les Debenham [mailto:lad@lsc.co.uk]
Sent: 28 October 2004 14:35
To: 'Rob Bodington'; plcs@lists.oasis-open.org
Subject: RE: [plcs] Global rules in the AP

Rob,

The 2 example rules you give are exectly right. I reserve judgement on the (many) unspoken global rules that may ensue.

LesD
-----Original Message-----
From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 28 October 2004 08:38
To: plcs@lists.oasis-open.org
Subject: [plcs] Global rules in the AP

Hi
One of the issues in the recent debate about NSN and identification was the need for global rules.

AP239 had several major technical  ballot comments against it complaining about the lack of global rules.
This was one of the reasons for Germany initially voting NO.

One of the ballot comments was about global rules enforcing what is already documented in the mapping tables. This has been resolved.

The other comment is about the lack of global rules in general.

We have also had a discussion about the need to have some global rules in capabilities.

I agree with Per-Ake, think that we need to be very careful about adding global rules as they can restrict the use of the AP.

Having said that, I think that there are a few areas where we will benefit from global rules in the AP as opposed to the DEXs/capabilities.

E.g.

Any identification assignment must have an organization assigned to it.

Any product_as_individual, product_as_realised, product_as_planned, part, part_version (note the model has changed!!!) must have at least one identification assigned to it.

Note, I am not enforcing any classification or anything, just enforcing an instantiation template.

What do people think to having such global rules in the AP as opposed to the capabilities?
One reason at least is keeping the bargain on changing the German No vote to a Yes.

Are there any other instantiation templates that we want to enforce?

Regards
Rob
-------------------------------------------  
Rob Bodington
Eurostep Limited
Web Page: http://www.eurostep.com http://www.share-a-space.com
Email: Rob.Bodington@eurostep.com
Phone: +44 (0)1454 270030
Mobile: +44 (0)7796 176 401

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