I would suggest property name such as AvailableStates and AvailableTransitions

Text I would include;
In some Servers instance of StateMachines may restrict the States and / or Transistions that are available on the StateMachine. This restriction can be the results of internal design of the instance, for example the statemachine for limit alarms for a instrument that only supports Hi and HiHi and can not produce a Low or LowLow. Another could be a StateMachine for a peice of equipment, where the available States and Tranistions might change dynamically, fir example when the machine is in maintence mode a different subset of the defined statemachine might be available then when the machine is in production mode. The list of available States and Transition is very import for some clients, especially for StateMachine has where many of the HasCause are method invocations. Clients would like to be able to display a restricted list of actions to the operator, but without the list of currently available states and transition this would not be possible.

The AvailableStates variable provides a list of the NodeIds of the States that are currently available on the StateMachine. Clients that are interested in restricting the list of States supported by the statemachine should subscribe for this list. The list may changes during operation of the server.

The AvailableTransitions variable provides a list of the NodeIds of the Transitions that are currently available on the Statemachine. Client that are interested in restricting the list of tranistion supported by the Statemachine should subscribe for this list. The list may change during operation of the server.

Added the two optional Variables "AvailableStates" and "AvailableTranistions" to the FiniteStateMachineType definition in Part 5.

Paul to supply example figure.

text and sample figure added

Agreed to changes in telecon.