Retain a record of current capital and non-capital assets for VAM's fleet 1.1 Asset records should allow for easy look-up of history of tags usage. Functional Requirement Important 1.2 All records must be stored for a minimum of seven years after the disposal of the asset. Technical Requirement Critical 1.3 The system should have a functionality for assets to be searched under all categories that are recorded (e.g., make, model, type, meter reading, using agency, cost, et al). Functional Requirement Important G2 Process and retain records for VAM's procurement of fleet assets. 2.1 The system should track requests for vehicles and group them by type. Functional Requirement Important 2.2 The system should have the ability to create Purchase Orders for procuring assets. Technical Requirement Critical 2.3 The system should track the Purchase Orders from the time sent to the vendor to the physical receiving and tagging of the asset. Functional Requirement Important 2.4 The system must allow for making multiple copies of an existing asset (whether capital or non-capital) and allow modification of copies as needed. Technical Requirement Critical 2.5 Asset record keeping should allow for various types of tags to be assigned to one vehicle simultaneously. Technical Requirement Critical 2.6 Asset record should allow for an easy "look-up of history " of individual tag usage (especially in the case of switched tags). Functional Requirement Important 2.7 The system should keep records of agencies' requests for assets. Functional Requirement Important 2.8 The system's record keeping functionality should allow grouping requests for assets by various categories (e.g., asset types, agencies, costs). Functional Requirement Important
