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

 


Help: OASIS Mailing Lists Help | MarkMail Help

plcs-tog message

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


Subject: RE: Dex 4 Capabilities required - first cut


Title: Dex 4 Capabilities required - first cut

Hi Chris

I realise that the discussion about the editors etc of the capabilities was not taking place on the TOG exploder.

 

Please could everyone use the exploders.

Regards
Rob

-----Original Message-----
From: Tim Turner [mailto:tjt@lsc.co.uk]
Sent: 22 November 2005 14:05
To: '
rob.bodington@eurostep.com'; Tim Turner; 'Barker, Sean (UK)'; 'Trine.Hansen@dnv.com'; 'Tor Arne Irgens'; 'Phil Rutland'
Cc: Nigel Newling
Subject: RE: Dex 4 Capabilities required - first cut

 

Not yet - we have been going through a revised set of requirements & building up the list against the required entities.

 

This is next on the list.

 


From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 22 November 2005 03:52
To: rob.bodington@eurostep.com; 'Tim Turner'; 'Barker, Sean (UK)'; Trine.Hansen@dnv.com; 'Tor Arne Irgens'; 'Phil Rutland'
Cc: 'Nigel Newling'
Subject: RE: Dex 4 Capabilities required - first cut

Sean, Tim

Are you updating the DEX with this info?

In other words, can I use the tools on DEXlib to automatically generate the spreadsheet?

 

Regards
Rob

-----Original Message-----
From: Rob Bodington [mailto:rob.bodington@eurostep.com]
Sent: 22 November 2005 08:47
To: 'Tim Turner'; 'Barker, Sean (UK)'; 'Trine.Hansen@dnv.com'; 'Tor Arne Irgens'; 'Phil Rutland'
Cc: 'Nigel Newling'
Subject: RE: Dex 4 Capabilities required - first cut

 

No one identifying templates?

I will draw up a spreadsheet and include the DEX7 capabilities and templates.

 

We can then use this as a basis for planning.

 

May be able to do this today.

 

Tim - You say

C024 - activity_status

 

Where did this come from?

How is it different to representing_activity?

 

Please Please could we use the capability names - not numbers when referring to them!"!!!

Otherwise people have to waste time looking up the numbers

Regards
Rob

-----Original Message-----
From: Tim Turner [mailto:tjt@lsc.co.uk]
Sent: 22 November 2005 08:11
To: 'Barker, Sean (UK)'; 'Trine.Hansen@dnv.com'; 'rob.bodington@eurostep.com'; 'Tor Arne Irgens'; 'Phil Rutland'; Tim Turner
Cc: Nigel Newling
Subject: Dex 4 Capabilities required - first cut

 

These are the first cut of Dex4 capabilities,

Kind regards,
Tim

C060: referencing_product_as_individual
C001: assigning_identifiers
C093: assigning_codes
C019: assigning_approvals
C020: Representing Life Cycle Opp
C010: Assigning_reference_data
C036: Assigning_date_time
C027: Representing_location
C022: Representing_work_package
C007: Representing_State_type 
C041: Representing_state_observed
C066: Representing_work_request
C065: Representing_work_order
C032: Representing_activity
C008: Referencing_part_or_slot
C009: Referencing_product_breakdown_element
C060: Referencing_product_as_individual

C005: Representing_documents
C052: Representing_resource

C037: Referencing_documents
C002: Representing_parts
C078: Representing_properties_numerically
C080: representing_properties_textually
C079: assignng_resource_property
C077: Assigning_process_properties
C046: Representing_variance
C058: Representing_justification
C026: Representing_condition
C055: Representing_project_information

C095: assigning_descriptors
C074: referencing_person_organization
C016: representing_person_organization

C015: Task_structure 
C088: Representing_task_structure
C090: Representing_Task_Associations

Note: C022 and C062: representing_scheme cover exactly the same entities

Note: Most task capabilities refer to DIS of AP239

Note several capabilities still refer to slot and not attachment slot

Note: C024 - activity_status seems to be against rec.practices in others - replaced by C007 & C041

 

-----Original Message-----
From: Barker, Sean (UK) [mailto:sean.barker@baesystems.com]
Sent: 21 November 2005 05:48
To: Trine.Hansen@dnv.com; rob.bodington@eurostep.com; Tor Arne Irgens; Phil Rutland; tjt@lsc.co.uk
Subject: Capabilities required

 

(apologies - I don't remember everyone on the TOG call on Thursday - Trine, could you forward to anyone I missed, please?)

The following capabilities have so far been provisionally identified as being needed by representing_task version 1 (core of DEX 3)

#needs significant update, ##not written ?not assessed in detail

Assigning_identification
Assigning_codes
Assigning_descriptor
Assigning_reference_data
Assigning_approval
#Assigining_process_properties - requires a template - to represent cost and time Assigning_date_time

 

##representing_information_controls - no content - to represent copyright and security classification representing_justification

?referencing_part_or_slot
?referencing_product_breakdown
?referencing_doucment
?referencing_project

DEX 3 will probably NOT reference the following:
assigning_product_poperties
referencing_activity
referencing_scheme
representing_environment_actual
representing_scheme
representing_work_done
representing_work_package

It is quite possible that version 1 may not use some of the other capabilities.

 

Nigel Newling's list (see issues against representing task -NN in upper case, my comments appended) *REPRESENTING_REQUIREMENTS

*REPRESNTING_ENVIRONMENT

*REPRESENTING_CERTIFICATION

*REPRESNTING_EXPERIENCE - not directly used in representing_task but in representing resource *REPRESENTING_INFORMATION_RIGHT - duplicate *ASSIGNING_SECURITY_CLASSIFICATION - suggest incorporating in Representing_information_rights *ASSIGNING_PROCESS_PROPERTIES - duplicate

Sean Barker
0117 302 8184

 

********************************************************************
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.
********************************************************************

 

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





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