Working from the Asset Requirements tab, you create the baseline inventory and the project requirements for the space and equipment assets allocated to the selected floors for the project. For information on how the workflow rule creates these, see Baseline inventory and space and asset requirements.
The asset requirement includes a count of equipment by equipment standards and a list of individual assets. See Assets by standard count and individual assets.
Note: You can assign equipment, but not furniture as a requirement. You can assign buildings from the Locations tab, but you cannot assign property.
Each record in the Space Budget Items table will represent either a space allocation or an asset. Assets and space requirement items are stored in the same space requirement. The way to distinguish between the two is that the space allocation records contain a value in the Room Standard field, and the asset records contain a value in the Equipment Standard field.
You create asset requirements by running the Create Requirements action on either the Space Requirements or Asset Requirements tab. The workflow rules creates both the baseline inventory (Period 0 Value) and the asset requirements (Period 1 Value.) For asset requirements, the baseline is your current equipment inventory, and the requirements are the new or re-purposed equipment that you need for the project.
The workflow rule gives the requirement (the Period 1 Value) the same value as the baseline (Period 0 Value.) You can then modify the requirement value as your planning evolves.
The workflow rule that runs when you create asset requirements inserts records by count of equipment standard. For assets that do not have an equipment standard, the workflow rule inserts records into the Individual Assets (eq_req_items) table. See Individual Assets.
The Asset Requirements tab presents the assets that your project requires in two lists. Each list can include both existing assets that will be re-purposed for the project, and new assets that need to be purchased. Re-purposed assets are existing assets, so they have an Equipment ID. New (proposed) assets have an Asset Planning ID, a temporary ID that indicates that the asset is not yet in inventory.
You can enter assets that do not yet exist in inventory as either assets by standards count, or as individual assets.
For equipment that has an equipment standard, the application uses the equipment standard to get the area and cost values. For individual assets, you enter this data manually.
The following are some suggested steps for getting started with creating asset requirements.
When you run the Create Requirements action, the workflow rules counts equipment by its equipment standard and adds the equipment to the requirement. For equipment, asset requirements are based on the count of equipment by standard.
Note that the application uses the following values from the equipment standard to calculate the asset requirements:
You might want to review or edit your equipment standards before creating the space requirements. See Adding and Editing Equipment Standards for a description of the data stored in an equipment standard.
You can run the Create Requirements action from either the Space Requirements or the Asset Requirements tab to create the baseline and requirements values for your equipment assets. When the workflow rules runs, it adds equipment that has an equipment standard to the requirement, and creates a list of individual assets that do not have an equipment standard.
See Creating Asset Requirements.
You can add asset requirement by the standard count for the asset. See Adding or Editing Equipment by Standard Count.
Individual assets are specialized pieces of equipment that you are not acquiring in bulk. You might eventually add an equipment standard for these assets, but initially, they are typically entered manually without a standard. See Adding or Deleting Individual Assets.
As your planning evolves, you will need to modify the asset requirements.
See
The workflow rule groups the data by the selection you make for the requirement: business unit, division, department, or functional group. If the requirement is at the Department or Functional Group level, then the application also groups by the Department Code found in the Equipment table. There is no organizational structure of “Functional Group” in the database; this is strictly used for creating new space requirements that will exist within or across Departments. For this reason, all baseline inventory will have a NULL value for the Functional Group.
Here's how the application groups the asset requirements:
The Individual Asset List includes the following:
Individual assets are stored in the List of Individual Assets table. This table works differently than the Space Budget Items (sb_items) table in that there are no Count and Period values. All records in the Individual Asset List table are considered required assets, not baseline, and always have a count of 1.
The area and cost values in the List of Individual Assets table are derived in the following ways:
The Asset Planning ID is used to identify an individual asset during the planning process for a Proposed project. The Asset Planning ID does not become the new Equipment Code. Rather, new equipment enters the inventory from the purchase and shipping process when it is checked in at the loading dock.
Each record in the Individual Asset List (EQ_REQ_ITEMS) table represents a single asset, so this query will not perform any grouping.
The Summary of Required Assets presents the counts and totals for asset cost and area broken down for new and re-purposed assets. Each is a virtual field. These values are updated whenever a record is edited. The following statistics are listed for the asset requirement associated with the selected project:
| Copyright © 1984-2015, ARCHIBUS, Inc. All rights reserved. |