Capability (C006):— assigning_effectivity Date: 2008/02/25 12:17:46
Revision: 1.25
CoverContentsIntro.Overview Info. modelTemplatesCapabilities.Ref. dataIssues

Issue raised against: assigning_effectivity

GENERAL issues

Open issue Issue: GYL-1 by Leif Gyllstrom (2005-11-10) minor_technical issue
Resolution: Accept. Status: open

Effectivity_assignment should be classified according to its role, e.g. Effectivity_taget, Effectivity_domain or any other applicable role.

Open issue Issue: RBN-2 by Rob Bodington (05-11-23) minor_technical issue
Resolution: Accept. Status: open

Add TEMPLATE: assigning_effectivity TEMPLATE: representing_dated_effectivity (and the similarly for the other types of effectivity)

Open issue Issue: RBN-3 by Rob Bodington (06-02-08) minor_technical issue
Resolution: Accept. Status: open

It is not clear how to represent an end date effectivity when the start date effectivity is not know. E.g. the fact that a component is removed from an aircraft is reported. I have no idea when it was installed, but I know when I took it off. The EXPRESS forces a start effectivity ENTITY Dated_effectivity SUBTYPE OF (Effectivity); start_bound : date_or_event; end_bound : OPTIONAL date_or_event; END_ENTITY; One suggestion is to use 1900-01-01 as dummy date.

Open issue Issue: DNV-45 by Sylvia Schwab on behalf of DNV (07-03-07) major_technical issue
Resolution: Accept. Status: open

There is a need to assign product_as_individual_effectivity to product and support data, e.g. to relate a breakdown_element to it's parent product.

Proposal: Add NEW template Assigning_product_as_individual_effectivity (asg_p_a_ind_eff) containing Effectivity_assignment (classified) and a Product_as_individual_effectivity (optional classification) relating to a Product_as_individual.

Open issue Issue: RBN-6 by Rob Bodington (2008-02-26) minor_technical issue
Resolution: Accept. Status: open

When implementing translators, there will be cases where the end effectivity is known, but the start effectivity is not known. The start dates are mandatory in template representing_dated_effectivity. To get around this, it is suggested to create a new template 'representing_dated_effectivity_end' that would use an event for the start_bound of Dated_effectivity.

ENTITY Dated_effectivity
SUBTYPE OF (Effectivity);
start_bound : date_or_event;
end_bound : OPTIONAL date_or_event;
END_ENTITY;

The Event could be simply Event.id="start_effectivity"

GENERAL issues

Closed issue Issue: TJT-1 by Tim Turner (05-04-11) minor_technical issue
Resolution: Accept. Status: closed

Version 1.8 of this capability contains material developed for the example Dex and introduces tables of contraints, rules and sections which will be moved to the business DEXs area. This capability needs to be reset to the previous version to effect this.
Comment: (Tim Turner 19th Apr 2005)
Capability 1.8 was updated with the content from version 1.7

Closed issue Issue: RBN-1 by Rob Bodington (04-01-16) minor_technical issue
Resolution: Accept. Status: closed

Need a Business Overview section Split the content into effectivity and representing_product_configuration
Comment: (Tim Turner 28th Jun 2004)
Accepted. Done.

Closed issue Issue: RBN-4 by Rob Bodington (06-06-28) minor_technical issue
Resolution: Accept. Status: closed

TEMPLATE: representing_dated_effectivity Error in path: %^dated_effectivity = Dated_effectivity.% should be %^dated_effectivity = Dated_effectivity% Template assigning_time. Rather than biding directly to the reference parameter of a sub template. e.g. Dated_effectivity.start_bound -> $representing_date_time.date_time% It is better to introduce a local ref parameter. E.g. %^start_date_time = $representing_date_time.date_time% Dated_effectivity.start_bound -> ^start_date_time
Comment: (Rob Bodington 06-06-28)
Modified

Closed issue Issue: RBN-5 by Rob Bodington (07-08-09) minor_technical issue
Resolution: Accept. Status: closed

Moved template assigning_product_effectivity to NDLO/templates