Asset_Management_Requirements_v2.pdf

Request for Information (RFI) # 70VT15-19-N-00001

ASSET MANAGEMENT SOFTWARE REQUIREMENTS

1. Provides the ability to manage fixed assets in a law enforcement organization’s inventory.

a. Includes the ability to add/remove/update inventory items directly within the application.

b. Includes the ability to bulk update inventory items based on Excel spreadsheet imports.

c. Allows for user-defined templates and fields for each item.

d. Includes pre-defined categories for:

i. Firearms

ii. Bulletproof vests

iii. Badges and Credentials

iv. Vehicles

v. Computer hardware

vi. Computer software

vii. Tech equipment (cameras, body wires, etc.)

viii. General office-based fixed assets

e. Categories include user-definable fields

f. Stores procurement information for the above, including the vendor and contract number.

g. Includes acquisition valuation of inventory.

h. Stores full asset history, including past ownership and transfers.

i. Supports digital sign-off of transfers and acceptance.

j. Allows for the marking of items as lost/stolen/destroyed and unmarking as appropriate.

k. Allows for the bulk export of inventory in Excel spreadsheet format.

2. Includes built-in notifications for renewals and/or disposition.

a. Notifications should be built into the system and also support external email notifications.

b. The periods of notification should be configurable for each item type to support annual renewal or other pre-define renewal period and end-of-life tracking.

3. Role-definable views are included.

a. Views seen by specific roles should be definable as to what features they have available.

b. Role definition should include the ability to limit views to specific items types (e.g. a national firearms coordinator can view all firearms across the inventory and modify that but not vehicles).

c. Roles should allow limitation based on scope (a particular region) or function

(viewing/adding/deleting content).

4. System Audit

a. All changes to records must be maintained in a system audit log.

b. Access to the log should be role-based and limited.

5. Annual inventory audit support should be included.

a. Supports bar code and hand-entered inventory confirmation.

b. Supports offline inventory and upload of results.

c. Includes information on prior inventories, including who conducted the inventory and the results.

d. Provided configurable notifications for overdue inventories.

6. Bar Code Support

a. Supports industry standard (non-proprietary) bar code readers.

Request for Information (RFI) # 70VT15-19-N-00001

b. Allows for both bar coded and non-bar coded inventory.

7. Training

a. System should support the storage of law enforcement specific training credentials.

b. Training must include quarterly/annual/triennial training event management and confirmation, including but not limited to:

i. Firearms qualifications

ii. First aid/CPR certifications

iii. Bloodborne pathogens certifications,

iv. Defensive tactics certifications

v. Legal refresher certifications

c. Stores copies of certificates for training.

d. Generates exception reporting for overdue training

e. Notifies users and managers of pending training expirations

f. Allows for electronic waivers of training with the appropriate role

8. Technical

a. Must support deployment in a DHS owned Microsoft Azure cloud environment.

b. Integrates with Active Directory for user authentication using single sign on.

c. Allows encryption at-rest with a FIPS approved encryption algorithm.

d. Allows encryption in transit through TLS 2.0 or greater.

e. Supports web-based access using Microsoft Edge and Firefox browsers without requiring plug-ins.

f. Supports stand-alone management by DHS with no requirement for external connectivity.