Objective
- Ensure accurate and up-to-date records of all software assets, configurations, and their relationships
Scope
- Databases that support the enterprise can reside on-premise, cloud or a workstation client - includes the follow key elements:
- Identification: Database inventory managaement
- Relationship Mapping: Maintain relationships between different software elements
- Integration with Change Management process: Used for Impact analysis
- Regular Audits and Updates: Ensures accuracy of the configuration
- Configuration status tracking and reporting: Auditing and tracking
Environment
- 157673: Service Asset & Configuration Management (SACM)
Automation
- Database Instances are tracked manually as automation currently does not exist
Reviews/Audit
- Review and audit of the database occur within the database tools, and manually in TDX.
User
- IT Services: Database Groups are the owners of Database Instances/Databases
Environment
- 10374: TeamDynamix (CMDB) Database
- 12568: Service Asset & Configuration Management (SACM)
Must (required)
Crucial to the integrity of most or all CIs; will be regularly audited for accuracy and completeness by the Practice Owner
- Form: Provides a template of fields to complete - Form Name: Database
- Serial Number: Provides the database name of the asset (where there is a test and production version) specify Prod or Test after the name
- External ID: Same as the Serial Number - this is what TDX uses as it's unique key name
- Status: A Status of the asset is required (Key Statuses listed below)
- Build Phase: Is in build process - ie. New databases that are in the process of build configuration phase and have not been implemented
- In-Use: Active - in use
- Retired: No longer in use but not disposed
- Disposed: No longer under control of Miami and removed from the environment
- Supplier: Set to Miami University
- Product Model: Set to Database
- Owning Acct/Dept: Solver Team that contains deepest level of technical expertise
- Audited Date: This is the date that this configuration item record was last audited for completeness and accuracy by the configuration item owner
Should
Necessary for continuous improvement of SACM capabilities; will be regularly audited for accuracy and completeness by the Practice Owner
- Requester: Individual in business office who serves as the business owner
- Owner: The current owner of the asset
- Requesting Account / Department: Primary business unit beneficiary of asset
- Escalation Instructions: Instructions for ticket logger on where to escalate if unable to solve. Most commonly a link to an escalation procedure article in the knowledge base
- Description: Purpose of the application or any pertinent information
- Server Environment:
- Last Known Upgrade Date: For manually tracking of when an application was last upgraded. Ideally, there should be a change ticket with details of that upgrade that corresponds with this date.
- mu.database.Database Engine
- mu.database.Database Version
Could
The attribute is relevant and desirable to at least some Configuration Item Owners in managing the baseline configuration of their CIs
- Attachment(s): File attachments associated with the asset