Enumerations for system status

[cwhanse]

Currently, the taxonomy has

• OperationalPhaseItemType (Commissioned, Decommissioned, Proposed, UnderConstruction). Used by OperationalPhase which is in the System base class.
• OperationalStatusItemType (Curtailed, Offline, Online). Used by OperationalStatus which is in the System base class.
• SystemAvailabilityModeItemType (Emergency, Environment, Forced, Grid, Islanded, Shutdown, Standby). Unused.
• SystemOperationalStatusItemType (CommunicationFailure, Decommissioned, Operational, UnderMaintenance). This is unused.

I found these when I was added a fifth, to provided values for a Status element for Availability #159

OperationalPhaseItemType refers to business/construction/permitting etc. The other three refer to operational states.

OperationalStatusItemType could subsume SystemAvailabilityModeItemType and SystemOperationalStatusItemType, and have its values extended.

The new OperationalStatusItemType should apply to PV, battery, and other systems, as well as components (inverters, communications, monitoring and data collection systems).

[cwhanse]

When closing, also do this: https://github.com/Open-Orange-Button/Orange-Button-Taxonomy/issues/187#issuecomment-1435355076_

[kevinkirkl3y]

@cwhanse Can you elaborate on what you mean by, "Have the values extended"?

[cwhanse]

Adding values that enumerate the states in this diagram.

[kevinkirkl3y]

@cwhanse It seems like some of these exist already, with slightly different naming conventions. I.E Operative (New)/Operational (Existing). Shall I add all of them and we can pare down redundant Enums after review?

[cwhanse]

@kevinkirkl3y If you can make a start we can adjust/add/remove through the review. Thanks for moving this ahead. I'm going to merge #187 so that hopefully will reduce the risk of merge conflicts for you.