My expectation was that this model is covered by Warm and/or ServiceLevel

ServiceLevel will not work because of the way we define its use by clients. It is specifically designed to assume a load balancing use case. It will not work for primary backup use cases. Specifically in part 4 the definition of 'healthy' last paragraph about not switching to another server

Agreed at Dallas Face2Face Mar 23, 2023 to add a new subtype of NonTransparentRedundancyType to address the Primary/Standby use cases. Agreed on the following:

• failover approach fits best with Warm but the definition of Warm needs to relaxed
• The ServiceLevel of the standby which is fully ready to take over will be defined as Degraded 199 and explained to be fully functional as a standby. Other lower levels would be used to indicate a standby that is not prepared to take over due to some vendor specific reason.
• A property will be included in the new subtype which indicates the overall status of the primary and standby. At least representing 4 states (primary with standby, primary with no ready standby, standby ready to be primary and standby not ready.
• A method will be included in the new subtype which is used to manually fail over. Can be call in the primary or the secondary(s). If more than 1 secondary a call to the primary will result in the primary deciding which standby will take over.

Proposed types attached here.

Jeff will propose the updated text for Part 4.

Proposed additions to Part 4.

In Table 109 - ServiceLevel ranges, in Row 'Degraded' change the second paragraph to the following:
"Servers that report a ServiceLevel in the Degraded sub-range are partially able to service Client requests. The degradation could be caused by loss of connection to underlying systems or functioning in a mode which results in some less than full functionality being available. Alternatively, it could be that the Server is overloaded to the point that it is unable to reliably deliver data to Clients in a timely manner."

In Table 110 Server Failover modes, in Row 'Warm" change the first sentence to the following:
"Warm Failover mode is where the backup Server(s) can be active, but is not operating in a mode which delivers the same level of functionality available from the primary Server. For example it cannot connect to actual data points (typically, a system where the underlying devices are limited to a single connection). "

Added proposed text to "Table 109 – ServiceLevel ranges"
Added proposed text to "Table 110 – Server Failover modes"
Added also to Table 110:
The ServiceLevel of the primary Server will be in the Healthy ServiceLevel sub-range. The ServiceLevel of the available standby Server will be in the Degraded ServiceLevel sub-range.

Agreed to changes in Virtual F2F.