Inventory Management System Checklist

Requirements for Inventory Management System (Software) 1. Backu Backup/R p/Rest estor ore e o

 The system must have options to backup backup and restore restore full data.

o

 Take  Take Automatic Automatic backup with set time time

2. Bar Barcodi coding ng / R!" R!" #. $ost $ost Tra Track ckin ing g %. $ustom $ustom &rici &ricing ng 'odel 'odels s (. "ata "ata $ap $aptu turre o

o

o

o

o

Accept data from multiple input methods including) bar code* R!" +nter the value desired directly or from a drop down table of valid values through standard mouse selection procedure procedure Re,uire mandatory -elds to be -lled before the user can eit the screen upport real time data entry auditing ,uality control upport real time data entry feedback preventing data entry errors from being recorded

o

&rovide appropriate appropriate calculations at time of data entry

o

0og transactions at time of data entry

o

'aintain transaction log history

o

&rovide asynchronous asynchronous and synchronous data synchroniation

. "ata "ata 3al 3alid idat atio ion n

o

 The system must validate every entry before saving. i.e. &revent from saving duplicates

4. "ocumentation and 5elp ystem Re,uirements o

o

o

o

o

o

A user manual shall be provided which describes the operation of  the system and provides references to the commands and user interface displays of the system.  The user manual shall contain a brief tutorial covering the basic aspects of each part of the system 6e.g. inventory update* reporting access* etc.7.  The user manual shall be available in both on8line and printed versions.  The user manual shall be available in Amharic and +nglish  There shall also be an !T help form that can be -lled out if more help is needed.  The vendor of the system must provide periodic maintenance and should be available all time in the event of a failure re,uiring immediate attention during working hours* by identifying the location or device.

9. +ase of Access o

o

o

o

:o more than 2 levels of navigation shall be re,uired for a user to enter or retrieve item information &rovide simple navigational tools on all forms* with links to other data entry items. 'ust conform to 'icrosoft ;
o


o

&rovide =type8ahead> functionality on list and combination boes.

o

o

o

o

&rovide search capabilities on appropriate lists. 'aintain a balance between the number of windows and the amount of information contained on each window. This will reduce the di?culty of navigation and the amount of information that is re,uired for viewing on a single screen. 5ave the ability for an administrator to add or eliminate -elds* organie the arrangement or tab order on data entry forms. "ynamic forms shall be generated where applicable. An eample of this is in the =+lement> ob@ect* where each element type can be customied with uni,ue attributes and uni,ue links.

. !nventory orecasting o

1.

orecast inventory sales from history !nventory Cptimiation

o

o

o

o

o

11.

Reorder pointD the number of units that should trigger a replenishment order Crder ,uantityD the number of units that should be reordered* based on the reorder point* stock on hand and stock on order 0ead demandD the number of units that will be sold during the lead time tock coverD the number of days left before a stock out if no reorder is made AccuracyD the epected accuracy of the forecasts !nventory Cverview

o

!nventory !tem "escriptions 

All of the items should have well8de-ned uni,ue descriptions* for many of the same reasons that apply to locations.

o

12.



!tem :umbers




how the current status of inventories by 

tock location of item



"ate item stocked



:ame of stocker

'ulti80ocation o

1#.

Eell8Crganied 0ocation :ames F 0ocation 0abels That Are +asy to Read and
o

!nventory management program must have multiple users/pro-les and the ability to edit or restrict permissions/scope of use

1%.

Crder +ntry

1(.

&erformance o

 The following performance re,uirements apply for the !T system and software. 




 The system shall not eceed an average transaction time of 1 second as measure over a 1 hour period of time.







 The system shall not eceed a maimum transaction response time of ( seconds.  The system shall support a minimum transaction rate of  transactions per minute.

$apacityD The system shall be capable of supporting a minimum of ( users at one time

1.

&urchase Crder 'anagement

14.

Reorder 'anagement o

19.

hould inventory reach a speci-c threshold* a companyGs inventory management system can be programmed to tell managers to reorder that product. This helps companies avoid running out of products or tying up too much capital in inventory. Report ;eneration

o o

o

o

 The system shall provide a means to ,uery and report data.  The system must track and generate pick lists* inventory* and reports sorted on various data points* such as item number* <&$* name* etc.  The user shall have the ability to de-ne standard reports and allow the user to input ,uery parameters. ;enerate Reports in multiple formats including but not limited to +cel ormat &" ormat 



1.

earch / ilter •

2.


o

Ehen a product is in a warehouse or store* it can be tracked via its tracking criteria* such as serial number* lot/batch number or revision number. :owadays* inventory management software

often utilies barcode* radio8fre,uency identi-cation 6R!"7* and/or wireless tracking technology.

21.

upplier 'anagement o

 The system must maintain a detailed information of vendors i.e :ame* T!: no. Address etc.

22.

Traceability

2#.

Training o

o

 Training shall re,uire from one to two days depending on users ollow8up training shall be available

2%.

Transfer 'anagement

2(.

Earehouse 'anagement

2.


+ach user will have the following attributesD 




$ontact !nformation.







Assignment !nformation I these -elds will identify which group and department this individual is assigned to* or what role they play.
Active I The user is currently active in the system.



Retired I The user is no longer active in the system.  These will be retained in the user list* however* to maintain the integrity of the database.