diff --git a/user-stories/proposed/fleet-management.rst b/user-stories/proposed/fleet-management.rst
index 32d1382..d90b508 100644
--- a/user-stories/proposed/fleet-management.rst
+++ b/user-stories/proposed/fleet-management.rst
@@ -104,6 +104,11 @@ Use Cases
   threshold for each alert so the resolving system does not take action on
   auditor alerts which happen repeatedly.
 
+* FLT015 - As a cloud operator, I need to be able to replace failed HW: server,
+  switch, storage node, and to ensure that the replacement hardware is treated
+  the same as the replaced hardware I should be able to clone the meta-data and
+  appropriate settings.
+
 Use Case Prioritization
 +++++++++++++++++++++++
 **Phase 1** - Modularity and Inventory Management
@@ -121,6 +126,7 @@ Use Case Prioritization
  #. FLT008
  #. FLT009
  #. FLT010
+ #. FLT015
  #. FLT014
 
 Usage Scenario Examples
@@ -168,6 +174,23 @@ Here is a real world description of this process:
 * Cloud operator returns resource to resolving system management
 * Resolving system returns physical resources to production pool
 
+**Operator Notification and Manual HW Replacement**
+
+* Monitoring triggers a warning on physical resources
+* Auditing system determines physical resource in question is in appropriate
+  state
+* Resolving system moves failed physical resources into maintenance mode
+* Resolving system informs cloud operator of need for investigation, and
+  replacement away from automated system management.
+* Cloud operator investigates and determines cause of issue
+* Cloud operator replaces failed HW. Cloud operator maintains HW UUID in
+  system management system. Cloud operator configures replaced HW to
+  identical configuration of replaced HW.
+* Cloud operator returns resource to resolving system management
+* Resolving system returns physical resource from maintanence mode to
+  operation one.
+* Resolving system returns physical resources to production pool
+
 **Cloud Operator Definition or Adjustment of Automated Remediation**
 
 * Cloud operator identifies pattern causing requirement for manual remediation