Open topic with navigation

Asset Management / Enterprise Asset Management / Project Proposal Console

Getting Started with Asset Requirements

Working from either the Asset Requirements or Space Requirements tab, you create the baseline inventory and the project requirements for the space, equipment, and furniture 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, a count of furniture by furniture standard, and a list of individual assets. See Assets by standard count and individual assets.

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 or Furniture Standard field.

Baseline inventory and space and asset requirements

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 or furniture inventory, and the requirements are the new or re-purposed equipment or furniture 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 or count of furniture standard. For assets that do not have an equipment or furniture standard, the workflow rule inserts records into the Individual Assets (eq_req_items) table. See Individual Assets.

Assets by standard count and 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.

• List of Required Assets by Standard Count. This list presents the standard counts for all the required assets that belong to this space requirement. These are the equipment or furniture assets for this project that have a value for the Equipment Standard or Furniture Standard. For example, this pane might list 30 PCs of the same standard. This makes it easy to estimate a large number of the same type of assets.
• List of Required Individual Assets. This list includes special assets that you do not acquire in bulk, or individual assets that do not have an equipment standard. Typically, the individual asset list will represent a few special assets (either existing or potential) that you add manually. For example, this pane might list one electron microscope. This makes it easy to account for special assets that have a significant impact on the project budget, schedule, or required services. See Individual Assets.

For equipment or furniture that has an equipment or furniture standard, the application uses the standard to get the area and cost values. For individual assets, you enter this data manually.

Getting Started

The following are some suggested steps for getting started with creating asset requirements.

Step 1. Review equipment and furniture standards

When you run the Create Requirements action, the workflow rules counts equipment or furniture by the equipment or furniture standard, and adds the equipment or furniture to the requirement.

Note that the application uses the following values from the equipment or furniture standard to calculate the asset requirements. If you do not use a standard for the asset, the application summarizes the manual entries you make for these fields.

• Standard Price and Standard Cost to Move are summed for each piece of equipment and furniture assigned to this standard to calculate costs.
• The Standard Area (for equipment) or Depth x Width from the Furniture Standards table s used to calculate area for furniture.

You might want to review or edit your equipment and furniture standards before creating the asset requirements. See Adding and Editing Equipment Standards for a description of the data stored in an equipment standard.

Step 2. Create asset requirements

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 and furniture assets. When the workflow rules runs, it adds equipment and furniture that has a standard to the requirement, and creates a list of individual assets that do not have a standard.

See Creating Asset Requirements.

Step 3. Adding Assets by Standard Count

You can add asset requirement by the standard count for the asset. See Adding or Editing Assets by Standard Count.

Step 4. Add Individual Assets as Needed

Individual assets are specialized pieces of equipment or furniture that you are not acquiring in bulk. You might eventually add a standard for these assets, but initially, they are typically entered manually without a standard. See Adding or Deleting Individual Assets.

Step 5. Modify asset requirements as needed

As your planning evolves, you will need to modify the asset requirements.

See

• Adding or Editing Assets by Standard Count.
• Adding or Deleting Individual Assets

How the application groups asset requirements

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:

• If the Equipment or Tagged Furniture record does not contain a value for division / department, and those fields are required for the grouping, then the application uses the division / department in the Rooms table.
• If the Equipment or Furniture record has no division /department and no Room Code, then that equipment is excluded from the space requirement.
• The application groups the assets by building and / or floor only if you selected this in the “Summarize Allocation” section of the form. However, the application always inserts the Building, Floor, and Room data from the Equipment or Tagged Furniture table into the space requirement, regardless of whether you have selected to summarize by building and floor on the Create Requirements form.

Individual Assets

The Individual Asset List includes the following:

• A few special assets (either existing or potential) that you have added manually. This is what the list typically includes. As the project progresses, you might ask a scientist or doctor for the specific model or specification for key pieces of equipment, and attach those as documents for an individual asset.
• Assets that do not have an equipment or furniture standard. When the workflow rule that creates asset requirements runs, any Equipment or Furniture records that are part of the selected buildings and floors, but do not have a standard are added to the Individual Asset List table (eq_req_items) with the Asset Type distinguishing equipment and furniture. This ensures that all assets are accounted for. However, you can delete these records from the table after the action completes, if the project does not actually require those assets.

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.

How the cost and area value are derived for individual assets

The area and cost values in the List of Individual Assets table are derived in the following ways:

• If the individual asset represents an existing asset, the Unit Area (unit_area) value comes from eqstd.area or the fnstd.depth multiplied by the fnstd.width; if it represents a proposed asset, the area is based on your manual entry.
• For an existing asset, the Baseline Cost comes from the Purchase Price (eq.cost_purchase or ta.value_original; if Purchase Price has no value, then the Standard Price (eqstd.price or fnstd.price) is used.
• If you are adding a new asset that doesn’t exist in your Equipment or Furniture tables, then area and cost will come from your entries.

Entering the Asset Planning ID in the Individual Asset List table

The Asset Planning ID is used to identify an individual asset during the planning process for a Proposed project. When you are ready to add the asset to your inventory, you can copy information entered for the asset requirement from the Individual Asset List (EQ_REQ_ITEMS) table to the new Tagged Furniture or Equipment record. The Asset Planning ID becomes the new Equipment or Furniture Code unless you enter an Equipment or Furniture Code before copying the information, See Copying data for equipment or furniture added as a requirement

Statistical Summary of Required Assets

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:

• Count of Grouped by Equipment Standards: This is the sum of the units for asset requirements for the baseline inventory (P 01 Value) for assets for the selected project that have an equipment standard.
• Count of Grouped by Furniture Standards: This is the sum of the units for asset requirements for the baseline inventory (P 01 Value) for assets for the selected project that have a furniture standard.
• Cost of Grouped by Equipment Standards: This is the sum of the equipment cost and moving cost for the count of assets in the baseline inventory for the selected project. This is calculated as the sum of the Standard Price from the Equipment Standards tables + the Standard Cost to Move
• Cost of Grouped by Furniture Standards: This is the sum of the furniture cost and moving cost for the count of assets in the baseline inventory for the selected project. This is calculated as the sum of the Standard Price from the Furniture Standards tables + the Standard Cost to Move
• Area of Equipment Standards. This is the sum of the Standard Area from the Equipment Standards table x the count of the baseline units for the selected project.
• Area of Furniture Standards. This is the sum of the Depth x Width taken from the Furniture Standards table x the count of the baseline units for the selected project.
• Count of Individual Equipment . This is the count of records in the Individual Asset List table with Asset Type Equipment for the selected project.
• Count of Individual Furniture. This is the count of records in the Individual Asset List table with Asset Type Furniture for the selected project.
• Cost of Individual Equipment / Cost of Individual Furniture: This is the sum of the Cost - Est. - Baseline entered for the individual asset in the Individual Asset List table.
• Area of Individual Equipment / Area of Individual Furniture. This is the sum of the Area (unit_area) for the furniture or equipment assets in the Individual Asset List table for the selected project.