representing_physical_breakdown

Template:— representing_physical_breakdown (rep_phys_bkdn)
Capability:representing_breakdown_structure

Date: 2008/01/03 16:46:02
Revision: 1.22

Cover Contents Description Model diags.Input params.Ref. params.Instantiation path Instance diags.Characterizations Issues in situ

Issue raised against: representing_physical_breakdown

GENERAL issues

Issue: DNV-8 by Fredrik Lied Larsen, DNV (2007-12-11) minor_technical issue
Resolution: Accept. Status: open

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\DNV_completed_checklists_20071231\DNV_template_issues_20071231.xls Template: representing_physical_breakdown Check list clause: 14 The input parameter "id" should have a reference to Physical_breakdown. Same goes for "vn_id".

Issue: DNV-9 by Fredrik Lied Larsen, DNV (2007-12-11) minor_technical issue
Resolution: Accept. Status: open

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\DNV_completed_checklists_20071231\DNV_template_issues_20071231.xls Template: representing_physical_breakdown Check list clause: 16 One link is wrong, link to figure 4 leads to figure 3. Link is located under heading "Instance_diagrams" under the first example.

Issue: DNV-10 by Fredrik Lied Larsen, DNV (2007-12-11) minor_technical issue
Resolution: Accept. Status: open

Issue: DNV-11 by Fredrik Lied Larsen, DNV (2007-12-11) editorial issue
Resolution: Accept. Status: open

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\DNV_completed_checklists_20071231\DNV_template_issues_20071231.xls Template: representing_physical_breakdown Check list clause: 48 Reference parameters only shown for full representation, but at the same time they are located below the figure.

Issue: DNV-12 by Fredrik Lied Larsen, DNV (2007-12-11) minor_technical issue
Resolution: Accept. Status: open

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\DNV_completed_checklists_20071231\DNV_template_issues_20071231.xls Template: representing_physical_breakdown Check list clause: 53 Entrance class is the same as the entity in several of the parameters.

Issue: DNV-13 by Fredrik Lied Larsen, DNV (2007-12-11) minor_technical issue
Resolution: Accept. Status: open

Issue: DNV-14 by Fredrik Lied Larsen, DNV (2007-12-11) minor_technical issue
Resolution: Accept. Status: open

Issue: DNV-15 by Fredrik Lied Larsen, DNV (2007-12-11) minor_technical issue
Resolution: Accept. Status: open

Issue: DNV-16 by Fredrik Lied Larsen, DNV (2007-12-11) minor_technical issue
Resolution: Accept. Status: open

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\DNV_completed_checklists_20071231\DNV_template_issues_20071231.xls Template: representing_physical_breakdown Check list clause: 82 Same error as the EXPRESS instance representation

Issue: DNV-17 by Fredrik Lied Larsen, DNV (2007-12-11) minor_technical issue
Resolution: Accept. Status: open

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\DNV_completed_checklists_20071231\DNV_template_issues_20071231.xls Template: representing_physical_breakdown Check list clause: 88 Uniqueness constraints exists but does not describe what makes a unique instance of this template.

Issue: DNV-18 by Fredrik Lied Larsen, DNV (2007-12-11) minor_technical issue
Resolution: Accept. Status: open

Issue file: D:\users\rbn\projects\010937_DNV_dexlib\docs\review\DNV_completed_checklists_20071231\DNV_template_issues_20071231.xls Template: representing_physical_breakdown Check list clause: 91 Each characterization should be explained by it self.

Issue: PHX-1 by Patrick Houbaux (08-04-16) minor_technical issue
Resolution: Accept. Status: open

REPRESENTING_PHYSICAL_BREAKDOWN is not part of the OASIS release ... I think it should

Issue: MWD-1 by Mike Ward (2008-08-08) minor_technical issue
Resolution: Accept. Status: open

The bkdn_type parameter (i.e. the reference data assignment for physical breakdown type) should be a characterization rather than a mandatory part of the Template. It is difficult to think of any reasonable (general) examples of different types of physical breakdown and the examples provided are redundant.

GENERAL issues

Issue: TRO1 by Trisha Rollo (07-06-06) minor_technical issue
Resolution: Accept. Status: closed

The short name does not comply with validation requirements

Comment: (Trisha Rollo 07-06-06)
Short name changed to comply with validation rules.

Issue: TRO2 by Trisha Rollo (07-06-06) minor_technical issue
Resolution: Accept. Status: closed

The entities are being referenced rather than the reference parameters; does not comply with validation requirements

Comment: (Trisha Rollo 07-06-06)
Entity references changed to reference parameters to comply with validation rules.

Issue: TRO3 by Trisha Rollo (07-06-06) minor_technical issue
Resolution: Accept. Status: closed

Figure one shows characterizations therefore does not comply with validation rules

Comment: (Trisha Rollo 07-06-06)
Characterizations removed from figure 1

Issue: TRO4 by Trisha Rollo (07-06-06) editorial issue
Resolution: Accept. Status: closed

Instance diagrams contains incorrect attribute names.

Comment: (Trisha Rollo 07-06-06)
corrected

Issue: TRO5 by Trisha Rollo (07-06-06) editorial issue
Resolution: Accept. Status: closed

Instance diagrams would be clearer if individual templates used in the template are described.

Comment: (Trisha Rollo 07-06-06)
individual templates used in the template added