---
alias: user-guide-change-resource-state
description: "This documentation outlines the process for modifying a resource’s state, including data and checklist steps"
---

# Change Resource State

:lock: Resource.**ChangeState**

## Overview

This operation changes the state of a **Resource**, following the currently associated State Model.

!!! note
    You can also select transitions that have no role defined, or if a role is defined, you must belong to that role.

## Setup

No special setup is required other than to meet the preconditions of the transaction.

## Preconditions

* The **Resource** is active and has a state model associated to it.
* If the current State model state has a role associated to it, you must belong to that role.
* The state transition exists for the current Resource state model and state.

## Sequence Of Steps

### Step 1: State Selection

This step captures the new state information, as well as the transaction comment.

1. Optionally, review the **Resource** details.
2. Select the new state (the state is usually pre-selected when entering the wizard).
3. If there are **Reasons** defined for the State Transition, it is necessary to select one of them (it pre-selects the default one).
4. Optionally, enter a comment.

### Step 2: Documents

This step is used to display **Documents** which are associated with the transaction context. To open any **Document**, simply select the **Document** icon.

!!! info
	Only used if there are **Documents** associated with the Resource and State Transition Context.

!!! info
	**Documents** are configured in the Document Resource Context.

### Step 3: Data Collection

!!! info
	Only used if there is a **Data Collection** associated to the Resource Context and State Transition

This step is used to capture the **Data Collection** information.

1. Fill in the **Data Collection** plan.

### Step 4: Checklist

This screen is used to complete a pre-defined **Checklist** associated with the state transition.

1. The **Checklist** is immediate and it must be filled completely. Additionally, if the **Checklist** has a previously defined **Data Collection**, you will need to supply a possible **Data Collection Instance**.

!!! info
	Only if there is a **Checklist** associated with the Resource Context and State Transition.

!!! info
	**Checklists** are configured in the Resource Checklist Context.

### Step 5: Request MAO

This step is used to request one or more ad-hoc **Maintenance Activities** for the **Resource**.

1. Optionally, select one ad-hoc **Maintenance Activity** to be requested for the **Resource** as part of the transaction. At maximum, one **Maintenance Activity** can be requested.

!!! info
	Only if the **Resource** property Enable Request MAO on State Change is `true`, if there are Ad-hoc MAOs that can be requested, and if attribute SEMI E10 for the new state model state is set as Unscheduled Down.

![Resource Change State][resourceChangeState]

[resourceChangeState]: ../../images/resourceChangeState.gif