Search for the Right Document
-
Planning and Strategy
-
Requirements
-
- Customer Feedback Report
- Capacity Planning Report
- Stakeholder Input Record Example
- List of Customer Journeys
- Reverse Engineering: Legacy Inventory Management System
- Task Analysis: Customer Support Ticketing System
- Requirements Workshop: Employee Onboarding System
- Mind Mapping Session: Mobile Travel Planning App
- SWOT Analysis: New Food Delivery App
- Storyboarding Session: Mobile Health & Fitness App
- User Story Mapping Session: Online Grocery Shopping Platform
- Focus Group: Requirements Gathering for Fitness Tracking App
- Prototyping Session Example: E-Commerce Website
- Document Analysis Example: Hospital Management System Requirements
- Observation Session: Warehouse Operations
- Survey: E-Learning Platform Requirements
- Workshop Session Example: Requirements Gathering for Mobile Banking App
- Interview Session Example: Requirements Gathering for CRM System
- Event Storming Session: Retail Order Management System
- Generate Requirements from Meeting Transcripts
- Requirements Definition Process Example
- ISO/IEC/IEEE 29148 Systems and Software Requirements Specification (SRS) Example Template
- Show all articles ( 7 ) Collapse Articles
-
- Customer Requirement Document (CRD)
- Customer Journey Map
- Internal Stakeholder Requirement Document (ISRD)
- Internal System Use Case Example: CI/CD System
- User Stories & Acceptance Criteria
- Technical Specification Document Example
- BDD Scenarios Example for User Login
- Non-Functional Requirements Example
- Functional Requirements Specification Example
- Use Case Example: User Login
-
-
Communication
-
Design
- Functional Specification for Inventory Management Workload
- Technical Specification for Inventory Management System
-
- Overview of Design Diagrams
- High-Level System Diagram Standards
- User-Flow Diagram Standards
- System Flow Diagram Standards
- Data-Flow Diagram (DFD) Standards
- Sequence Diagram Standards
- State Diagram Standards
- Flowchart Standards
- Component Diagram Standards
- Network Diagram Standards
- Deployment Diagram Standards
- Entity-Relationship Diagram (ERD) Standards
- Block Diagram Standards
-
Operations
-
-
- Creating a Visualization Dashboard Guide
- Business Outcome Metrics Dashboard Guide
- Trace Analysis Dashboard
- Dependency Health Dashboard
- Guidelines for Creating a Telemetry Dashboard
- Guidelines for Creating a User Behavior Dashboard
- Improvement Tracking Dashboard
- Customer Status Page Overview
- Executive Summary Dashboard Overview
- Operations KPI Dashboard Example
- Stakeholder-Specific Dashboard Example
- Business Metrics Dashboard Example
- System Health Dashboard Example
- Guide for Creating a Dependency Map
-
-
-
- Event Management Policy Example
- Incident Management Policy
- Problem Management Policy
- Example Training Materials for Escalation
- Runbook Example: Incident Management with Escalation Paths
- Escalation Path Document Example
- Incident Report Example: Failed Deployment Investigation
- Incident Playbook Example: Investigating Failed Deployments
- Contingency Plan for Service Disruptions
-
-
-
Testing
-
Development
< All Topics
Print
Unused Asset Decommissioning Checklist Example
PostedMarch 29, 2025
UpdatedMarch 29, 2025
ByKevin McCaffrey
ID: SUS_SUS2_4_unused-asset-decommissioning-checklist
Code: SUS2_4
Overview
Efficient removal of unused cloud assets directly impacts your sustainability goals, helping you reduce unnecessary resource consumption and minimize overall operational costs. Below is a step-by-step checklist to guide Cloud Operations Managers in identifying and decommissioning unused assets.
Checklist
- Asset Inventory & Tagging
- Implement a consistent tagging strategy for all cloud resources.
- Maintain a real-time inventory to quickly locate and identify unused or underutilized resources.
- Usage Analysis
- Use monitoring tools to track resource utilization (CPU, memory, storage, network).
- Set up automated alerts when resource usage falls below a specific threshold.
- Validation & Approvals
- Contact the relevant application owners or teams to confirm assets are no longer required.
- Document approvals to ensure accountability and reduce disruptions.
- Decommissioning Procedure
- Follow a standard operating procedure (SOP) for gracefully shutting down services.
- Ensure backups and snapshots of data are taken if needed for compliance.
- Delete or terminate resources after final approval to prevent accidental reactivation.
- Post-Decommission Review
- Verify all dependencies have been updated or removed.
- Conduct a cost impact analysis to confirm savings realized.
- Report on successes, lessons learned, and opportunities for further optimization.
Tips for Success
- Automate wherever possible: Use scripts and alerts to reduce manual overhead and prevent human error.
- Regular reviews: Schedule periodic assessments to detect new unused assets.
- Continuous improvement: Update policies and procedures as you learn from decommissioning efforts.
By systematically identifying and eliminating unused assets, you streamline cost management, reinforce sustainability, and reduce operational complexity in your cloud environment.
Table of Contents