Description
High level statements of NIH's fundamental values that guide decision-making for systems management.
Principles
Preferred Source for ESM Tools - tools will be selected by preferring: first commercially available packages, then Government-off-the-shelf (GOTS) solutions and then shareware solutions, with custom-built solutions as a last resort.
Rationale: The objective for ordering these preferences is to minimize maintenance efforts through selecting tools that are well supported by a stable, reliable source. Cost, functionality, speed-to-implementation and other considerations will also be evaluated, ranked and included in the decision.
ESM Coverage - ESM tools will integrate across all NIH organizations.
Rationale: NIH needs a complete systems view of all components that support enterprise applications, including within the ICs. This is compatible with the Principal principle.
Self-Service - ESM tools will provide a self-service interface for checking system, network or problem status.
Rationale: ICs should have access to system, network or problem status without calling the Help Desk or NOC. This capability would assist them in their own troubleshooting and service level processes. Leading practices also recommend allowing users to check the status of their own problems.
Support NIH Enterprise Architecture Standards - ESM solution will address NIH Enterprise Architecture products and standards as specified in other domain bricks.
Rationale: The ESM architecture will support the target enterprise infrastructure, databases and applications at NIH.
Time Table
This architecture definition approved on:
April 21, 2004
The next review is scheduled in:
None scheduled.
