In the earlier paper ``Local Reconfiguration Policies,'' a system was viewed as a collection of components configured to provide a set of user services. Components are not simply hardware devices, but functional combinations of hardware and software. To study fault tolerance and reconfiguration, we focussed attention on the fact that different sets of components can support the same service. Then, if some components fail, they can be replaced by others in a different configuration. A service is characterized by the set of alternative configurations that can support it. A service configuration assigns components to support a service. The earlier view of a system was flat. A component was thought of as atomic, and different from a service. Taking a deeper view, now, we look at components through a microscope, and we see that a component is (sometimes) a lower-level service with its own components and configurations. The definition and nature of survivability are re-examined in a hierarchical setting. The rewards for doing so include the concept of vertical dependency between services and a characterization for a lattice-valued measure of survivability.