Please fill all required fields
Instructions will go on this sheet. Press a tab above to continue . . . .
CRITICAL & UNIQUE
Requirements
A requirement describes functionality you expect to find in an ERP software application. Requirements come in two
flavors: typical and "Critical & Unique".
Typical requirements are what ERP vendors see all the time. Some examples of typical requirements include:
- The general ledger must suppot double entry accounting (debits, credits) with a complete audit trail.
- The accounts payable module must be able to generate checks based on a preset calendar or on demand.
- Inventory must maintain a master list of products that we manufacture or stock to support the manufacturing process.
Try to avoide "typical" requirements. Software vendors have seen them 1,000's of times and their software has
addressed those requirements since 1989.
We suggest you focus your requirements on those which are CRITICAL & UNIQUE. What do those terms mean?
CRITICAL - this is application functionality that the application MUST have. If it does NOT have this funcationality,
the application will be eliminated from further consideration OR the software will have to be customized to address it.
UNIQUE - you believe, based on your knowledge of your industry or related industries, that this requirement is unique to
your business.
Here are some examples of Critical and Unique requirements:
Process: CRM            
Line
Number
Sub-
Process
Requirement Critical Unique Comments  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
Process: PLM / Engineering      
Line
Number
Sub-
Process
Requirement Critical Unique Comments
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
   
©2012 Counsel Funding | All rights reservedPowered By SpreadsheetConverter