I guess this reply was not received by the TOG as Gerry is not on the exploder

Regards Rob

------------------------------------------- Rob Bodington Eurostep Limited Web Page: [1]http://www.eurostep.com [2]http://www.share-a-space.com Email: Rob....@eurostep.com Phone: +44 (0)1452 810 960 Mobile: +44 (0)7796 176 401 Skype: rbodington

------------------------------------------------------------------------------

From: Radack, Gerald [mailto:Rad...@ctc.com] Sent: 21 February 2007 12:58 To: Mason, Howard (UK); Rob Bodington Cc: plcs...@lists.oasis-open.org; Hunten, Keith A Subject: RE: PLCS TC - the next edition ????

Howard:

In addition to CM issues, the disadvantage of a TC is that hyperlinks would not work. And when somebody buys an AP, don't they get all the modules also? It would be a mess if they have buy the AP, then paste in the changed modules in order to get the correct configuration. So I believe that a complete new version of AP 239 should be built. I thought it was easy to do a build with STEPMOD. And now that EuroSTEP developed the CM tool, it should be even easier to do a build with the configuration that is needed.

I do not believe that we have a policy requiring a modular AP to use all the latest editions of the modules. You can use the modules that AP 239 currently uses, as long as they are still published by ISO. Has SC4 been requesting that ISO keep older versions of modules on the books? Assuming that is the case, if the error is only in part 439, then you only need to create new versions of parts 439 and 239.

Would ISO allow us to use the TC process (which does not require ballot) but to provide a complete new package, rather than the usual change document?

Gerry

------------------------------------------------------------------------------

From: Mason, Howard (UK) [mailto:Howa...@baesystems.com] Sent: Wednesday, February 21, 2007 7:10 AM To: rob....@eurostep.com Cc: plcs...@lists.oasis-open.org; Hunten, Keith A; Radack, Gerald Subject: RE: PLCS TC - the next edition ????

Interesting question, which has not been addressed before.

It is SC4 policy not to do TCs on modules, but to issue new editions, in order to minimise the configuration management issues.

TCs can be created for modular APs, referencing particular versions of modules (not necessarily the latest)

My feeling is that the AP module should be regenerated in the updated form, to avoid ambiguity. I have copied this to Keith and Gerry to see if they have different opinions.

Howard

------------------------------------------------------------------------------

From: Rob Bodington [mailto:rob....@eurostep.com] Sent: 21 February 2007 06:31 To: Mason, Howard (UK) Cc: plcs...@lists.oasis-open.org Subject: RE: PLCS TC - the next edition ????

Hi Howard

I am attempting to understand what is required to produce a TC for AP239 to fix some select omissions.

You indicate in the mail from July last year that there are no TCs on modules permitted.

I am not sure how this will work.

Does this mean that modular APs cannot have TCs?

Does this mean that we need to produce a 2^nd edition of at least the AP module? (That is where the express is)

If we do, does that mean that we need to use the latest editions of the modules?

The most straightforward approach for us would be modify the EXPRESS in the AP module as a TC.

At some later date, these changes could then be rolled into the relevant modules.

The reason for asking is the TOG needs to make a policy decision here.

We are busy writing templates and it would be good to do it once.

Regards Rob

------------------------------------------- Rob Bodington Eurostep Limited Web Page: [3]http://www.eurostep.com http://www.share-a-space.com Email: Rob....@eurostep.com Phone: +44 (0)1452 810 960 (note new number) Mobile: +44 (0)7796 176 401

------------------------------------------------------------------------------

From: Mason, Howard (UK) [mailto:howa...@baesystems.com] Sent: 07 July 2006 09:01 To: rob....@eurostep.com Subject: RE: PLCS TC - the next edition ????

We agreed not to go through the administrative hassle of managing TCs on modules.

Howard

------------------------------------------------------------------------------

From: Rob Bodington [mailto:rob....@eurostep.com] Sent: 07 July 2006 08:59 To: Mason, Howard (UK); plcs...@lists.oasis-open.org; plcs...@lists.oasis-open.org Subject: RE: PLCS TC - the next edition ????

Thanks Howard

One thought .... The changes are to the EXPRESS, so are therefore to the modules .... I heard that we were not allowed to do a TC on a module, it had to be a 2^nd edition. Is that correct?

Regards Rob

------------------------------------------- Rob Bodington Eurostep Limited Web Page: [4]http://www.eurostep.com [5]http://www.share-a-space.com Email: Rob....@eurostep.com Phone: +44 (0)1452 810 960 (note new number) Mobile: +44 (0)7796 176 401

-----Original Message----- From: Mason, Howard (UK) [mailto:howa...@baesystems.com] Sent: 06 July 2006 14:03 To: Rob Bodington; plcs...@lists.oasis-open.org; plcs...@lists.oasis-open.org Subject: RE: PLCS TC - the next edition ????

I attach for your information the relevant extract from the SC4 Handbook on Change Management, which highlights the relevant options.

Either Amendment or Revision (to get a new edition) require the normal ballot cycle. TCs can be issued by the Working Groups. Minor revisions, resulting in a complete new document, require an FDIS ballot.

In response to Rob's questions:

This raise several questions about the TC process.

1) How long does it take to produce a TC?

HGM> drafting time plus a couple of weeks to approve and process in ISO

2) What do we need to produce? A complete new AP package?

HGM> Not for a TC - you might wish to generate a monor revision if htere are many changes

3) Does it require a ballot process?

HGM> Not for a TC - just agreement in the WG

4) How many can we produce? I.e should we wait until we have a number of issues addressed then release the TC, or release a TC everytime we address an issue?

HGM Wait- there is normally a maximum of two TC before you issue a new edition - sometimes can stretch to three.

5) Can we make major modifications in the TC? E.g. bring the Risk module, address the config management of tasks, or should we just address clear errors like missing select extensions

HGM> This sounds like a new edition - we can hardly call it a minor revision.. Just fix errors in a TC.

------------------------------------------------------------------------------

From: Rob Bodington [mailto:rob....@eurostep.com] Sent: 19 June 2006 14:48 To: plcs...@lists.oasis-open.org; plcs...@lists.oasis-open.org; Mason, Howard (UK) Subject: PLCS TC - the next edition ????

*** WARNING ***

This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message.

Hi

I was wondering what the process for producing a Technical Corrieganda PLCS would be.

As we are developing the capabilities, we are finding some selects that should have been extended. In a couple of cases, this is preventing us from completing the capabilities, or forcing us to represent something in a less optimal way.

I was thinking that we need a formal process for dealing with modifications to the AP that takes into account the short term requirements to make fixes to the AP for implementations and the requirement to ensure that these fixes are rolled back into the ISO document.

My proposal is that we:

1) Record the issues against AP239 in a single issue log in dexlib - i.e. dexlib/docs/issues/ap239_issues.xml

2) Raise the issue as SEDS so that they are registered against ISO 10303-239, recoding the seds number in the issue log

3) Copy the EXPRESS models for the AP to DEXLIb. Have two files. One a concatenation of all module ARMs, and the other being the long form derived from the ARMs. Fix the EXPRESS according to the issue.

4) Modify the capabilities to use the modified EXPRESS and include a note in the capability referring to the issue and SEDs and to say that it deviates from the standard, but that the issue has been raised against the standard.

5) At some point in time, raise a TC against PLCS.

This raise several questions about the TC process.

1) How long does it take to produce a TC?

2) What do we need to produce? A complete new AP package?

3) Does it require a ballot process?

4) How many can we produce? I.e should we wait until we have a number of issues addressed then release the TC, or release a TC everytime we address an issue?

5) Can we make major modifications in the TC? E.g. bring the Risk module, address the config management of tasks, or should we just address clear errors like missing select extensions

I realise that this opens a potential Pandora's box of changes that we might be tempted to make, but given where we are with PLCS, I think that we should limit the TC to fixing errors.

What does everyone think?

In the mean time, I will create:

1) The issue log at: dexlib/docs/issues/ap239_issues.xml

2) The EXPRESS files: dexlib/docs/ap239/ap239_arm_lf.exp dexlib/docs/ap239/ap239_arm_lf.xml (derived from ap239_arm_lf.exp) dexlib/docs/ap239/ap239_arm_sf.exp dexlib/docs/ap239/ap239_arm_sf.xml (derived from ap239_arm_lf.exp)

Regards Rob

------------------------------------------- Rob Bodington Eurostep Limited Web Page: [6]http://www.eurostep.com [7]http://www.share-a-space.com Email: Rob....@eurostep.com Phone: +44 (0)1452 810 960 Mobile: +44 (0)7796 176 401

******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ********************************************************************

------------------------------------------------------------------------------

This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392

------------------------------------------------------------------------------

References

Visible links 1. http://www.eurostep.com/ 2. http://www.share-a-space.com/ 3. http://www.eurostep.com/ 4. http://www.eurostep.com/ 5. http://www.share-a-space.com/ 6. http://www.eurostep.com/ 7. http://www.share-a-space.com/