Item | Features/Functions | Vendor Response (CF / CP / NC / LC / NS) | Vendor Comments |
|---|---|---|---|
| 1.0 Operating System Support | |||
The software implementation must be compatible with both Linux and Windows Server operating systems compatibility for server installations | |||
| 2.0 Database Engine Support | |||
The upgrade should support databases like firebird or MySQL among other databases like MS SQL, Oracle. | |||
| 3.0 System Administration | |||
Support for one defined System Administrator | |||
Support for unlimited Assistant System Administrators with defined roles below those of the System Administrator | |||
| 4.0 Licensing and Source code | |||
The system should support both perpetual unlimited licenses for the users in order to drop on overhead costs of support | |||
Support flexible regimes of user groups based on preference like read only, concurrent usage… | |||
The consultant shall be required to provide the working source code of the upgrade | |||
The source code shall be property of the Ministry of Energy and Mineral Development. | |||
| 5.0 Web interface | |||
Support for customizable multi-portal web pages | |||
Provide customer facing dashboards with unlimited usage for both individuals and companies | |||
Support multipage or tabbed portal structure with other convenient tools available on pages or tabs | |||
Support for determining which pages appear in portals in order to limit access to facilities and resources for specific user categories | |||
Support for placement of shortcut tools on the hope page or any other page of portals to ease operations such as uploading content and extracting content without having to open the repository cabinets | |||
| 6.0 Workflows and form builders | |||
Support for a single person or group of persons to be responsible for an action in the execution process of the workflow with option of one or all persons being required to complete or approve an action defined in the workflow process | |||
Workflow defined as in (a-c) above should be saved and reused by authorized users without them needing to modify the designed process | |||
Workflow should provide for the option of a blank action person for the first task to enable the submitter select the person to execute the first task in the series of tasks comprising the workflow design. This feature is important to enable a single workflow to take multiple paths through selection of first task players at the time of assigning an automation sequence | |||
Workflow should support dasboard notification and mail notification for assigned workflow tasks to assignees, assigners and supervisors | |||
Workflow should provide for notification of assigners on completion or delay in completion of assigned tasks | |||
Workflow should provide for notification of assigners the successful completion of tasks | |||
Workflow should provide for notification of assigners the rejection of an approval process originated by an assigner | |||
Workflow should support inclusion of supervisors in the chain for escalation of unfinished tasks | |||
Workflow should allow for attachment of additional content in the execution path apart from the main content which triggers process | |||
Workflow should allow for the applying comments to content | |||
Workflow should allow for editing content in workflow | |||
Workflow should allow for submission of content from other applications to facilitate integration of processes from other | |||
The form builder should support easy and dynamic building and updating of the forms in the system | |||
The form builder should allow easy updating, publishing and unpublishing of the organizational forms | |||
The form builder should be able to support building of sections of the data that is to be captured | |||
The form builder must support both generic and user defined data types, including integration of administrative units in Uganda up to village level | |||
| 7.0 Ad hock Tasks | |||
The system should support creation of ad hock tasks on the fly which are used once and expire on completion | |||
Ad hock tasks should have all the features stated in workflow above except that they should be limited to a single step of execution | |||
| 8.0 Content Search and Retrieval | |||
Support for Google like such using operators "AND", "OR", "NOT" used to concatenate search strings | |||
Support an Advanced search engine which enables the user to select among a large variety of search parameters such as:
| |||
Support saved searches to facilitate reuse of common search parameters | |||
Support special saved searches for quick finding of content such as "all invoices whose value is Shs 1,000,000/- and above" | |||
Support text search for document content types so that documents containing a specified text string can be found | |||
| 9.0 Content security | |||
Support structured access security to cabinets, sub-cabinets and content | |||
Provide for the following minimum levels of content access classes:
| |||
| 10.0 User related features | |||
Support creation of users within the system using in-built user authentication | |||
Support importation of users and user groups from Active directory so that users can login using their Windows Authentication | |||
Support creation of user groups for ease of system security administration | |||
Support the declaration of a user active or inactive while remaining in the system | |||
Support deletion of users from the system | |||
Support allocation of content access classes to individuals and groups | |||
Support allocation of a user to more than one group | |||
Support re-assignment of user ownership for content and workflow to handle cases such as delegation, out of office etc | |||
Support the creation of super users to assist the system Administrator in managing the system | |||
Provide personal dashboards which offer quick convenient tools to users to be able to access features like:
| |||
| 11.0 System Audit trails | |||
Support Audit trails for all security related functions. As a minimum, the system should provide audit trails for the following activities
| |||
| 12.0 Systems Integration | |||
Integrate with the Uganda Revenue Authority portal for tracking of taxation | |||