Simple Asset and Repair Manager

Introduction

SARM is an application for managing physical assets. The goal is to make it simple to install and use for somebody who is not a system admin. In particular it does not require the user to install and manage databases or application servers.

It has 2 principle functions:

a) Allow a user to update and search an asset register that holds details of all physical assets.

b) Maintain information on warranties and repairs, notifying a user if action should be taken in the near future.

In addition it produces reports on assets, their value and location, and maintenance activities over a specified time period. It is not intended to cover trouble ticketing and work orders.

SARM is a single user application written in Java using Swing and should be suitable for someone who simply needs to keep track of a few domestic appliances in a small number of locations. However no size limitations are designed into the program and its use will be restricted only by the design goal to keep functions simple. If my mother can use it then it’s OK.

Requirements

1. Manage a list of assets. The asset record must include sufficient details to identify the asset and location, identify the agent responsible for managing it, and the entity to be contacted in case of problems with data required by that entity.
2. Manage warranty information for assets.
3. Manage a list of repairs made to the assets. The repair information must identify the agent performing the repair, date and cost, new warranty period (if any), and asset(s) repaired.
4. Manage list of agents/entities. Details must include contact information, and agent role (owner, supplier, manager, maintainer, etc.).
5. Manage list of locations.
6. Provide option to backup (and restore) entered information in a file which may be archived separately from SARM and has a documented format that may be used by other systems.
7. View list of all assets, with possibility to filter by location, with drill down to asset details or location details.
8. View all repairs and warranty information for an asset, with links to repair agent and warranty agent.
9. View list of all agents, with drill down to assets for which they are responsible (or have repaired, or warrant, or own) depending on role type.
10. Produce a printable report of activities over a defined time-period.
11. The program must prevent the user from creating inconsistent data (example new warranty without identifying the agent responsible for warranty) and allow the user to create missing data at the point it is required without losing the data already entered.
12. The program must be resilient to errors in the database information in the event that saved information is changed by other mechanisms. It must provide understandable explanations of what is wrong and guide the user in correcting the data.
13. The program should provide a means to schedule notification of events by e.g email, SMS, or similar.
14. The UI and all error messages must be configurable to the user’s preferred language. It must be possible to change the text and add languages without recompiling the program.

Last updated 26/03/2004 18:22