: Public Text
Created: |
15/08/2009 17:01:01 |
Modified: |
01/09/2011 13:03:42 |
|
Project: |
|
Author: |
T. Kostic |
Version: |
1.0 |
Phase: |
1.0 |
Status: |
Proposed |
Complexity: |
Easy |
Difficulty: |
|
Priority: |
|
Multiplicity: |
|
Advanced: |
|
UUID: |
{E1043BC4-8BC2-4ade-863A-075B99E49C10} |
Appears In: |
InfTransformerObservationsBushing |
[<b>tanja</b>] How to refactor test- and observation-related classes, to consolidate with DistributionWindingTest? What of this is per model, what is per asset? [<b>tom</b>] Any of these Observation classes will be per Asset, since they are done in field inspections of specific instances. To me, it would help if we had an Observation class between IdentifiedObject and the observation-related classes, to hold the status and some other common attributes of inspection tests. This idea would also apply to switches and other assets, although we are not looking at them right now. The DWTest classes were intended for the model-specific tests. If we try to splice in the instance-specific tests, it could lead to more confusion. [<b>tanja</b>] We also have some Procedure classes, with related data sets, so let's address instance-related stuff when needed (probably with Part 4 or 6?).<br/>[tanja, 2009-08-20]<br/><ul>
<li>What ElectricalInfo attributes (if any) are needed for BushingModel?</li><li>PowerRating is really not a good name for what the class is really used.</li></ul>
[tanja, 2010-01-31]<br/><ul>
<li>Reexamine relationships to PSR-related classes</li></ul>
[tanja, 2011-09-01]<br/><ul>
<li>Added hyperlinks to diagrams: The first three are normative, appearing in 61968-11. The last one shows informative xformer-related *Info classes (as this diagram is showing old xformer asset-related classes).</li><li>Renamed PowerRating to CoolingPowerRating.</li></ul><p/>