RE: Capability (C045): representing_product_as_realized - Representing a product as realized - Issues [2/5]

[Gordon Robb <gor@lsc.co.uk>]

Title: Capability (C045): representing_product_as_realized - Representing a product as realized - Issues [2/5]

Hi Rob,

This dialogue could be long and tedious.

In my example the move from a a GR5 to a GR7 was a operational requirement that saw all the products moving to the new configuration standard.It occurred by a product recall to the manufacturers, the output was a GR7.

 

In the Mil Aerospace world (Def Stan 00-970 //00-971// 05-57/4// 05-10 etc..) all major assemblies and components have mod plates to which implemented mods (changes) are added therefore I could (and will have) a GR7 ZX 139 to mod  670 standard (version), a GR7  ZX 140 to mod 699 standard (version) but the overall operational capability of the serialized product will not have changed. The rules managing the change in mark number are very strict and not cheap.

 

Line Replaceable Unit(LRU) (US Weapon Replaceable Unit (WRU) type components can have strike off plates, this is usually dependent on the size of the LRU. A strike off plate is usually  numbered from (for example) 1 thru 10,on the 11th mod a new strike off plate is issued as part the mod set and its change notice (mod leaflet) ( the plate is obviously part numbered as well as it is part of the overall configuration e.g strike off plate xxxx123 Issue 2) ( The same rules occur for the major assembly mod plates) Therefore a serialised LRU (WRA) could be to a different part number/strike off standard/version.

On LRUs (WRA) which have embedded software you could (should) find a serial number for the LRU, a part number for the hardware' box, a part number for the software. Version control of that serialised item is predominantly managed via the software part number.

 

Its nice to see that after placing the issue up on Dexlib 4 months ago you are getting a dialogue on the subject, when this one is 'put to bed', there is still Sean Bs issue on 'scrap'.

 

regards

Gordon

 

 

 

 

  -----Original Message-----
From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 13 July 2004 09:54
To: 'Gordon Robb'
Cc: 'Plcs-Dex teams (E-mail)'
Subject: RE: Capability (C045): representing_product_as_realized - Representing a product as realized - Issues [2/5]

Thanks Gordon

I see what you are saying but I would have thought that what you describe is really a different configuration of an individual Harrier, not a version.

 

I always understood a version to mean a product that has had a change made to it. E.g.

My car has had a product recall and a new brake assembly fitted.

The car is now at version 2.

The change to the brake assembly was not a configuration option, but the result of a change directive (choose your favourite business term). Hence there is a new version of the car. I would never remove the brake assembly unless another change was to be implemented. In your Harrier examples, the Harrier is being configured according to mission, not according to product changes.

 

I understand that some products have a "strike" plate which gets marked according to the changes that have been implemented.

The product has the same serial number, but the changes has been applied, so the configuration record reflects a new version.

 

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

-----Original Message-----
From: Gordon Robb [mailto:gor@lsc.co.uk]
Sent: 13 July 2004 09:16
To: 'Rob. Bodington (E-mail)
Cc: Plcs-Dex teams (E-mail)
Subject: Capability (C045): representing_product_as_realized - Representing a product as realized - Issues [2/5]

 

Hi Rob,
I  note the following issue is still open

Issue: RBN-1 by Rob Bodington (04-03-13) minor_technical issue
Resolution: Accept. Status: open

 

How are Product_as_realized versioned? Does each version keep the same serial number and then just have a new version number assigned?

ANSWER - Yes - the product keeps its original serial No. thru life. The version depicts its operational 'capability'.
e.g - A Harrier GR 5 serial ZX 138 is a day attack fighter/bomber, the same aircraft (ZX 138) converted to a GR 7 version provides an additional night attack capability. On the product configuration status record (CSR) it would show additional OEM references, a CUM No. ( a as designed serial number as identified on the drawings; a LBS (line build sequence) No as depicted on the manufacturing process. This provides the traceability of the product thru both 'design and manufacture linked to the actual operators serial (in this example 138)

I understand in a commercial aircraft environment the OEM serial for the product would  be the 'master' in respect to the realized products CSR, the tail no. would be a 'master' in respect to operator.

In the PLCS bike example the serial of the bike remains the same irrespective if it is in racing or road wheel 'trim'/version.

regards
 Gordon

 

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