Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:m:manageability [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:m:manageability [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Manageability ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | Manageability describes the ability to monitor, configure, control, operate, suspend, restore, and review a Qualified Node or governed function. In the Governed Node Service Market, Manageability supports operational control, qualification continuity, service-level oversight, suspension handling, restoration, | ||
| + | |||
| + | Manageability matters because a Qualified Node must remain observable and controllable after it receives eligibility for governed work. Operators and governance processes need current information about status, configuration, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | //ability to monitor, configure, control, operate, suspend, restore, and review a Qualified Node or governed function// | ||
| + | |||
| + | ===== Source ===== | ||
| + | Financial Systems Archetype, Part 7: Governed Node Service Market | ||
| + | |||
| + | ===== Note ===== | ||
| + | Manageability supports operational control and governance review. | ||
| + | |||
| + | A manageable Node exposes status, configuration, | ||
| + | |||
| + | Manageability differs from Maintainability. Maintainability concerns analysis, correction, update, testing, and controlled change of the implementation. Manageability concerns operational monitoring, configuration, | ||
| + | |||
| + | ===== Example ===== | ||
| + | An operator observes that a fraud screening Node has degraded service status, suspends new work assignments, | ||