1. Catalog driven APIs & Operations Patterns
Nigel Davis

2. Background See first 6 slides in oimt.2019.ND.004.00
Consider intention/expectation
All requests can be seen as orders related to agreement where the order represents the agreed intention/expectation (see TR (V1.4))
An order may be arbitrarily complex or extremely simple
The paradigm can be applied on all interfaces
The structure degenerates to traditional-looking for basic cases
In sophisticated cases the Task acting out the order needs to be monitored and controlled (see TR Figure 5.4 (V1.4))
See also oimt.2019.ND “Modes of operation”

3. Different perspectives
Provider has responsibility for all capability supporting contract and will carry out all recovery and repair actions
Note that the provider will negotiate with other organizations who share physical space and may acquire capability on a similar “provider has responsibility…” basis
Provider deals with some urgent recovery but is dependent upon a client to deal with significant proportion of fault repair.

4. Two distinct views Opaque to client where full responsibility is taken
Transparent to client where responsibility for recovery is taken
Equipment and usage is necessary for repair
Provider could do some “in box” projection to take load off client
Geography will be at client level OR will be a peer.

5. Opaque to client
Peer and subordinate interactions take place in provider to fully resolve all fault scenarios
Degree of peer trust changes operational dynamics
Client
Third party
provider
Con
Con
Con
GIS
Con
Con
Con

6. Semi-Opaque to client
Peer and subordinate interactions take place in provider to fully resolve all fault scenarios
Degree of peer trust changes operational dynamics
OSS
Third party
provider
Con
Con
Con
GIS
Con
Con
Con

7. Semi-Opaque to client
Peer and subordinate interactions take place in provider to fully resolve all fault scenarios
Degree of peer trust changes operational dynamics
OSS
Third party
provider
Con
Con
Con
GIS
Con
Con
Con

8. Semi-Opaque to client
Peer and subordinate interactions take place in provider to fully resolve all fault scenarios
Degree of peer trust changes operational dynamics
OSS
Third party
provider
Con
Con
Con
GIS
Con
Con
Con

9. Transparent to client
Really semi-transparent as self contained nodes are expressed as units and diagnosed as units

10. Need Diagnosable down to single circuit pack
Identifies linkage into GIS and/or other external controller

11. Some considerations Physical inventory Geographical inventory
Geographical and physical structure
Functions and systems
Physical realization of functions