Field Name |
Description |
Choices |
Default |
Required |
|---|
| Submitted By | This will be prefilled with your name. If you are submitting the request on behalf of someone else, enter that person's name. | Any person whit an active UCINetID. | Submitter name | Yes |
| Date Submitted | Enter the date the request was submitted. This will default to the current system date. | Valid date. | Current date | Yes |
| CI Action | Indicate the appropriate action to be taken with the CI. | | Expand |
|---|
| title | View Options for CI Action... |
|---|
| - New - A new CI will be added to the CMDB.
- Update - An existing CI requires an update. Any information you provide when requesting an update will be used in its entirety to replace the corresponding existing information. For example, if you provide a Description in the update request, the description you provide will replace the description currently on file. If you leave a field blank in the request then no change will be made to the corresponding field in the existing CI record.
- Bulk Import - A list of CIs will be imported into the CMDB. When using this action provide a link to the list (if it is online) or attach a document containing the list to the request. If attaching a document, enter "See attached."
- Retire - An asset is being retired.
|
| None | Yes |
| Cause for Request | Describe the configuration change that provided cause for this request. If request is a result of a project or change request, then provide the project or change request number. | Free form | None | Yes |
| Special Instructions | Describe any special considerations that apply to the CI. If you are adding a new CI or you are changing any dependencies or relationships, provide the name(s) of the CI at the other end of the relationship and indicate the type of relationship. For example: - Runs on: server.uci.edu
- Uses database: db-dbname
- Gets data from: Sendmail
| Free form | None | No |
| New CI Name | If you selected New or Update for the CI Action then provide the unique name used to identify the asset represented by the CI. Naming standards exist for most CI classes and these should be followed as closely as possible. Naming standards are outlined in Configuration Item Life Cycles and Configuration Item Naming Standards. If you are requesting a new CI or a name change of an existing CI then this field is required. If you selected Retire for the CI Action then select the CI to be retired from the reference list. | Free form | None | Yes |
| Current CI Name | If you selected Update for the CI Action then look up the current CI record using the reference list. | Reference list | None | Yes |
Description | A concise description of the asset that can be used to clarify the CI name. The description should never be more than a paragraph and rarely more than a few sentences. If a more detailed description is needed then either include a link in the description or provide a document that can be attached to the CI record. | Free form | None | Yes |
| Class | Select the appropriate asset class for the CI. If the CI belongs in a class that is not included in the choice list then select the Other option and use the Special Instructions field to indicate where the CI belongs. If you select Update for the CI Action and you are reclassifying a CI then select the class the CI should be moved to. | Select from choice list | None | Yes |
| Support group | Provide the name of the primary group responsible for supporting the asset in production. This is usually the group that would be contacted first for questions and technical support. This will already be filled in if you are requesting an update to an existing CI. | Select from reference list | None | Yes |
| Supported by | If there is one specific person in the support group who provides support for the asset, name that person here. It is generally not a good idea to name a person in this way since assignments and responsibilities change frequently. It is recommended that this field be left blank. | Select from reference list | None | No |
| Assignment group | If there is a specific support group that should be automatically assigned to all incidents relating to the asset then name that group here. Leave this field blank if the assignment group is the same as the support group. It is recommended that this field be left blank. | Select from reference list | None | No |
| Assigned to | If there is one specific person in the assignment group who should be automatically assigned to all incidents relating to the asset then provide that person's name here. It is generally not a good idea to name a person in this way since incidents will be assigned to that person whether he or she is available or not. It is recommended that this field be left blank. | Select from reference list | None | No |
| Installation Status | Select the appropriate installation status of the physical asset represented by the CI. See the table at right for a list of options. This will already be filled in if you are requesting an update to an existing CI. | | Expand |
|---|
| title | View Installation Status options and definitions... |
|---|
| - Absent - Asset is cannot be located or otherwise accounted for.
- In Maintenance - Asset is offline or otherwise unavailable due to maintenance.
- In Stock - Asset is not currently being used but is in inventory and can be deployed if needed.
- Installed - After project tasks are completed and the work is in production, an evaluation is performed to highlight project performance.
- On Order - Asset has been ordered or is being developed and is not yet ready for installation.
- Pending Install - Asset has been acquired or development is complete but the asset has not yet been installed for use.
- Pending Repair - Asset requires maintenance and is not available for use but maintenance has not yet started.
- Retired - Asset has reached its useful life and has been removed from service. Retired assets are typically salvaged or otherwise disposed of.
- Stolen - Asset has been physically removed without permission or acknowledgement of OIT management.
|
| None | Yes |
| Operational status | Select the appropriate operational status of the physical asset represented by the CI. See the table at right for a list of options. This will already be filled in if you are requesting an update to an existing CI. | | Expand |
|---|
| title | View Operational Status options and definitions... |
|---|
| - Operational - Asset is fully deployed and is ready for use. This status should only be used when the installation status is Installed.
- Non-Operational - Asset is offline or otherwise unavailable due to maintenance or repair.
- Repair in Progress - Asset is offline being repaired.
- DR Standby - Asset is installed and ready to be used for disaster recovery purposes. Assets marked with this status should not be used for any other purposes as they must be immediately available when needed.
|
| None | Yes |
| DR Criticality | Disaster Recovery criticality used to prioritize the recovery of assets in the event of a major disaster. A knowledge base article that contains details of what the options mean is available Here. This field is mandatory for the Business Service and Application classes. However, it can also be used by individual support teams to document DR priority for assets supported by the team and only appears when one of those classes is selected in the Class field. | | Expand |
|---|
| title | View Details of DR Criticality options... |
|---|
| - 15 Minutes
- 6 Hours
- 24 Hours
- 5 Days
- 30 Days
|
| None | No |
| Link to Bulk Import Sheet | This field only appears when you have a list of CIs to be imported and Bulk Import is selected as the CI Action. Either provide a link to the document that contains the import list or attach a document to the request. (Drag the document from your desktop to any part of the request form and the document will be uploaded and attached to the request.) If attaching a document, enter "See attached" | Free form | None | No |