Skip to content
Eptura
Feedback by UserVoice
← Archibus

How can we improve Archibus?

Archibus: Assets

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Equipment standard based bulk asset generation Improvement

The equipment standard and bulk generation needs to be improved. The use case is if I'm going to make the effort to define an equipment standard where I've added in manufacturer information, CSI information, costs and model information, this should have copied over for the asset registry.

So here's the use case. I have to create 10 extra equipment that came in a batch. The only thing different about these 10 items is the serial number and the unique asset ID. Meaning it's the same model number, same cost, same extra attributes, same warranty, same PO invoice.

The improvements that should be made are:
1. When defining asset standards - there should be an asset attribute feature here too.
2. when using the asset registry, and choosing the bulk option, if you took that time to setup the first one properly with all the warranty, service contract, equipment owners, costs, telecom for software versions, additional attributes, model number, manufacturer, CSI values etc...Then hit save and next, you're forced to repeat all that manually (even if you had an equipment standard) it really should be a button to copy all values over to the next asset. Then the user can just change the serial number or location values (if different).

If a user is trying to generate 30/40/50 assets that are arriving in batches, it's a lot of work to have to manually setup that tabs of information for each one.

8 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Tiffany Lam shared this idea  ·   ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • ashley.nuttall commented  · 

    If the data is held in the eq standard table and you have assigned the eq_std value to the asset, why are you needing to enter the data into the asset table also? this make no sense when using a relational database. The eq_std data is linked to the asset, repeating the data entry is really bad practice, if you going to re-enter the data why bother with the eq standard in the first place? Unless I'm missing the point.

  • Tiffany Lam commented  · 

    The method you suggested technically works but it probably is less attractive as a product stand point and comparing to other product that have library stamping abilities. I would find it hard to convince someone that they should export and re-import data that lives in 3 separate tables. So the intent is if a client has say 25 fields they want stamped into several new assets, why are they adding them one at a time per asset? Why wouldn't the equipment standards be setup to help stamp in all the fields so that all the user has to change is a unique value such as a serial number?

    Let me show you the comparison
    Current method for adding in 10 assets that are pretty the same:
    1. Add bulk assets via the registry
    2. Pick a standard, opt to fill in the location, department value and status
    3. Go next, now fill in all the other fields such as manufacturer, PO number, warranty supplier, warranty end dates, service contract, install dates, service dates, Telecom software operating system, CSI values 1, CSI values 2, CSI values 3, Descriptions, Equipment use values, custodian, purchase price, replacement cost
    4. Go save and edit next
    5. Repeat steps 3 and Step 4 for asset 2
    6. Repeat steps 3 and Step 4 for asset 3
    7. Repeat steps 3 and Step 4 for asset 4
    8. Repeat steps 3 and Step 4 for asset 5
    9. Repeat steps 3 and Step 4 for asset 6
    10. Repeat steps 3 and Step 4 for asset 7
    11. Repeat steps 3 and Step 4 for asset 8
    12. Repeat steps 3 and Step 4 for asset 9
    13. Repeat steps 3 and Step 4 for asset 10

    Can you see how that is time consuming? It'll take anywhere from half an hour to an hour to update these 10 assets. The intent would be that this is a user who wouldn't need the smart client tool as they are registering new assets.

    So the purposed way would be to simplify the 3rd step.

    Let me show you the comparison if we had a method to just stamp in the fields that could be linked to the equipment standard level.
    Current method for adding in 10 assets that are pretty the same:
    1. Add bulk assets via the registry
    2. Pick a standard, opt to fill in the location, department value and status
    3. Go next, change the serial number of the asset.
    4. Go save and edit next
    5. Repeat steps 3 and Step 4 for asset 2
    6. Repeat steps 3 and Step 4 for asset 3
    7. Repeat steps 3 and Step 4 for asset 4
    8. Repeat steps 3 and Step 4 for asset 5
    9. Repeat steps 3 and Step 4 for asset 6
    10. Repeat steps 3 and Step 4 for asset 7
    11. Repeat steps 3 and Step 4 for asset 8
    12. Repeat steps 3 and Step 4 for asset 9
    13. Repeat steps 3 and Step 4 for asset 10

    Does that make sense on how I have less tabs of less fields to need to copy and repeat over again and thus reduce the chance of making data errors too in the process? So turning this to a 3 minute process.

  • AdminFred Kraus (Admin, Eptura) commented  · 

    Thanks for the idea and detail, Tiffany. Would import/export help in this case? I'm not sure if that would address the need you mention here, but thought I'd ask.