[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emix] Pulling the power together
From CIM ElectricalProperties: Used to define either the required electrical properties of a type of asset or the actual electrical properties of an asset model. An ElectricalTypeAsset or ElectricalAssetModel may have multiple ElectricalProperties associated with it, with the ElecTAElecPropRole/ElecAMElecPropRole defining which roles in the Asset these properties refer to. e.g. a Transformer TypeAsset or AssetModel will have an ElectricalProperties association for each winding. This can also be used to define ElectricalProperties for each phase individually by using the phases attribute thus allowing an ElectricalTypeAsset or ElectricalAssetModel to have an individual entry for each phase. Not every property will be required for each typeof ElectricalTypeAsset. e.g. a Transformer may only have requirments for ratedKV, ratedMVA and phases, while a LinearConductor will have r,x,b and g requirements per unitLength on top of a ratedAmps and ratedKV. Apparent Power: Product of the RMS value of the voltage and the RMS value of the current (MegaVoltAmperes) Reactive Power: Product of RMS value of the voltage and the RMS value of the quadrature component of the current (Megavoltamperes Reactive) VoltagePerReactivePower: Voltage variation with reactive power BasePower: The BasePower class defines the base power and base voltages that are used in the per unit calculations. PowerFactor: Ratio of ActivePower to ApparentPower "If something is not worth doing, it`s not worth doing well" - Peter Drucker
From: Toby Considine [mailto:tobyconsidine@gmail.com] On Behalf Of Toby Considine PDF attached if you lose the formatting. Email attachments to bring comments back onto the list What we have in EMIX is a few layers. A family of ways to contract: discrete purchases, option contracts (with associated performance terms) We have a layer of pricing options: price negotiations, price taking (w/ or w/o tiers) and a few odd-balls And then we have the low-level mangoes being bought and sold. It appears that we can eliminate the odd-balls by creating a rough taxonomy of mangoes as follows.
If we can fill in the blanks, fully characterize the mangoes, then, I think we can eliminate the odd-balls and complete the power/resource side in EMIX. This suggestion aligns with Dr. Burns suggestions that we expand on the Reading Types as described in the NAESB PAP10 process. If understand the many helpful suggestions, we have so far focused on Yellow
I am trying to fill out the product descriptions. I have recently sent out several requests about the Red column
Dr Snyder has recently sent me some encouraging, but not fully actionable (to me) suggestions, Both Marty AND Aaron have suggested that I take the scalar descriptors and abstract them elsewhere.
I think I am missing something here, something perhaps so obvious that others don’t see what I am missing… Can we take this and turn this into something similar to 6 mangoes, each with Quantity Scale Enumerated Unit-types tc “It is difficult to get a man to understand something, when his salary depends upon his not understanding it” -- Upton Sinclair.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]