| Originally Posted by damuw Below is a list of projects. IF YOU HAVE EXPERIENCE AND WANT TO WORK ON ANY OF THESE PROJECTS CONTACT ME AT damuwinston@rufarotechnology.com . I am also on AIM as damuw2 and yahoo as damuw.
___________________________________________________
*ECMS is my Team
The projects shall include but not limited to: _
Create electronic folders, which are built and maintained in accordance with a classification scheme; _ Manage folders, including their documents, records, and metadata; _ Declare an electronic document as an ORM corporate record and maintain its integrity as an authentic representation of a business action or decision; _ Search for and retrieve records; _ Consistently manage the retention and disposition of whole folders and records, retaining what should be kept and disposing of what should not, whether by transfer to another organization or destruction _ Control access to folders and records, and to maintain an auditable track of actions taken on them; _ Provide manageable, usable and robust mechanisms to carry out core ORM functions, capture documents, classify those documents as records and allowing the management of those records; _ Incorporate the functionality of the existing WBTS into the capabilities of the broader ECMS. Record Organization Record Capture, Declaration and Management Electronic documents that are generated or received in the course of ORM business processes originate from both internal and external sources. The electronic documents may be in various formats, may be produced by different authors; and may be received as single documents and as multiple document files. They may arrive through different communication channels e.g. local area network, wide area network, electronic mail, facsimile, letter post (to be scanned), and at variable arrival rates and volumes. The contractor shall develop a flexible input system to capture documents with good management controls so that these diverse requirements are addressed. The contractor shall develop a system that will ensure electronic documents can be captured, so that they can be declared and stored as electronic records from: _ Standard ORM office applications _ Operating system directory management facilities _ E-mail applications _ Images created by a document scanning system The contractor shall develop a system capable of supporting document capture from new office applications, including open source software, as these are brought into use by ORM. The contractor shall support the capture and declaration of any electronic document that is stored as a single electronic file. Examples include: _ XML documents and forms _ word processing documents _ documents produced by text editors _ spreadsheets _ e-mail messages _ e-mail messages with attachments _ e-mail receipts _ encapsulated _web pages_, with all components, in a single physical file _ presentations _ desktop publishing documents _ PDF format documents _ document images from a scanning system _ single static images in common formats _ bit-mapped and vector graphics. Declaration Management Search, Display and Presentation The contractor shall provide the capability to search, retrieve, and display classes, folders, and electronic records. The contractor shall provide the capability to search and display interface via a web browser platform to support the retrieval and display of folders and records, and the subset of folders and record metadata normally available to ORM end users. The contractor shall provide the capability to support graphical browsing of the classification scheme, and browsing directly from a class to the folders created under that class; and the direct selection, retrieval and display of electronic folders and their contents through this mechanism. The contractor shall provide a search system that is capable of: _ Searching all records management metadata elements; _ searching the full-text content of electronic records; _ searching both metadata and record content through an integrated interface; _ constructing searches by combining multiple terms, from multiple sources; _ defining and storing saved searches for reuse by end users; _ retrieving a complete electronic folder and all its parts and records; and _ displaying a list of all or designated parts and records in the context of that folder as a discrete group and in a single retrieval process. Display Presentation The contractor shall provide the capability for the presentation of folder metadata, records and record metadata to a destination external to the ECMS, in a form suitable for electronic publication. The contractor shall provide the capability for the presentation of folder metadata, records, and record metadata to a destination external to the ECMS, in a form suitable for electronic publication. The contractor shall provide the capability for presenting classes, folders and records in one or more of the following formats: _ an XML format suitable for publication _ a non-proprietary HTML format suitable for publication _ an e-GIF approved format suitable for publication. The contractor shall provide the capability for allowing an e-mail retrieved by browsing or searching to be copied to a compatible e-mail application, for transmission in a manner normally achieved by that application. Retention and Disposal A fundamental aspect of records management is the use of retention schedules to govern the removal of records from operational systems. Retention schedules define how long the records have to be kept by the ECMS, and how they should be disposed. The contractor shall provide a function that specifies retention schedules, automates reporting and destruction actions, and provides integrated facilities for exporting records and metadata. Review Transfer, Export and Destruction Access Control Audit An audit trail is a record of actions taken that involves the ECMS. This includes actions taken by users or Administrators, or actions initiated automatically by the ECMS as a result of system parameters. The audit trail for records can be viewed as metadata of the records (because it consists of information describing some aspects of the records_ history), though this is not essential. The ECMS must be capable of management and control of electronic records according to the standards necessary for compliance with requirements for legal admissibility and security, and must be capable of demonstrating this compliance. The audit trail is a key factor in meeting these requirements by maintaining a complete record of all the actions on every record. The ECMS must keep an unalterable audit trail capable of automatically capturing and storing information about: _ all the actions that are taken upon an electronic record, electronic file or classification scheme; _ the user initiating and or carrying out the action; _ the date and time of the event. The contractor shall provide the capability that once the audit trail functionality has been activated, the ECMS must track events without manual intervention, and store in the audit trail information about the events. The contractor shall provide the capability to maintain the audit trail for as long as required, which will be at a minimum for the life of the electronic records or electronic files to which it refers. Backup and Recovery Reporting The contractor shall provide flexible reporting facilities for the Administrator. The contractor shall include, at a minimum, the ability to report the following: _ numbers of files, volumes and records; _ transaction statistics for files, volumes and records; _ activity reports by user. The contractor shall provide the capability for Administrators to query and produce reports on the audit trail. These reports must include, at a minimum, reporting based on selected: _ classes; _ files; _ volumes; _ records; _ users; _ time periods. The contractor shall provide the capability for Administrators to enquire on and produce audit trail reports based on selected: _ security categories; _ user groups; _ other metadata. The contractor shall provide the capability to produce a report listing of files and volumes, structured to reflect the classification scheme, for all or part of the classification scheme. The contractor shall provide the capability to include features for sorting and selecting report information. The contractor shall provide the capability to include features for totaling and summarizing report information. The contractor shall provide the capability to allow Administrators to request regular periodic reports and ad-hoc reports. The contractor shall provide the capability to allow Administrators to restrict users_ access to selected reports. Usability The contactor shall follow the accepted standard rules for the user interface of each operating system or platform for which it is supplied (for example, a Windows-based version of an ECMS should follow Microsoft Official Guidelines for User Interface Developers and Designers) _ follow consistently present user interface menus, commands and other facilities in all parts of the ECMS application. _ use consistent terminology to label functions and actions in all parts of the ECMS application. _ Be consistent with the e-government guidelines for web design where a web browser interface is employed for the ECMS. Authentication and Encryption The contractor shall provide the capability to retain the information relating to electronic signatures, encryption and details of related verification agencies. |