Technical

The Broker is a Web service created using .Net Technology. It needs a client application to consume it. SOAP is used as the communication protocol which enables XML packets to be sent between systems. A custom adapter is built for each business system facilitating the ability to package metadata and electronic data into a structure supported by DIEM Broker. The adaptor includes the ability to un-package data received for subsequent display/use by a Business Application. Adapters are relatively easy to develop as they do not need to be aware of TRIM business rules. For each Business Application that requires access to TRIM an adapter is created using that system’s SDK, scripting or programming language. The adapter needs to access the DIEM Broker’s web service (developed in .NET and easily interfaced with .NET languages), a SOAP interface whose methods are exposed with WSDL on the DIEM Broker server.

Technical requirements

Following is a list of system requirements on client machines:

• Trusted site needs to be set by systems administrator making the Broker accessible.
• The .NET 2.0 framework exists on the Webserver/s
• TRIM 6.1 or above is installed on the Webserver/s and has Test User names IDs configured with security and location metadata.
• IIS is installed and functional on the server.
• A shared folder is created for staging documents
• Windows 2003 or Windows XP Professional based server

Implementation

Diem Broker is installed as a virtual directory/website under IIS. The configuration of Diem broker includes path to a staging folder which is used by Diem Broker to store/retrieve documents from TRIM.

Case studies

Grains Research & Development Corporation has integrated their CA Clarity Grants Management System to TRIM via our Broker to:

• create Clarity project files within TRIM
• Migrate old Clarity project files into TRIM

NSW Department of Corrective Services has integrated their Syscon Justice Systems Offender Information Management System (OIMS) to TRIM to

• retrieve Word templates stored within HP TRIM (from which new documents are created)
• Store OIMS generated documents into HP TRIM
• Store documents imported into OIMS into HP TRIM.

Resources

Resources such as business case information and white papers will be available on this site. Currently there are three iCognition White Papers available:

1. EDRMS Business Cases (short form and long form versions): This white paper conducts a comprehensive cost-benefit analysis of three implementation options for Electronic Document and Records Management Systems (EDRMS): Records Management, Business-specific, and Enterprise Information Implementations. There is a short form version for managers and executives, and a long form version for those who need detail. The paper outlines the business case for each option and determines in what circumstances each option would be considered. The EDRMS business cases are compared to a ‘Do Nothing’ option. In the example used in this analysis, of an organisation of 500 staff and using the assumptions detailed in this paper, a pure cost-benefit analysis approach shows the Enterprise Information implementation is ahead by an order of magnitude over the next best option. The Enterprise Information option further consolidates its lead when taking into account the non-quantifiable benefits. This must be tempered by the change management effort of transitioning the organisation to predominately EDRMS usage and limited access to other repositories, which can be significant. The results can also be influenced by key business drivers that can heavily influence the non-quantifiable benefits and justify other implementation options.
2. HP TRIM Interface Options: High user adoption rates are a key measure of success for the implementation of TRIM Context as an Electronic Document and Records Management System (EDRMS). While the solution itself is not solely responsible for the achievement of take-up or adoption, the solution architecture must facilitate user adoption through ease of capture, search, retrieval and management of information. The solution architecture must therefore provide easy to use interfaces that are familiar to current technology paradigms, so that there is little change to the way people already work. This paper investigates the various interface options for TRIM Context and provides analysis on their applicability to enterprise-wide use depending on the environment outcomes desired, and makes comment on each interface’s benefits and disadvantages.
3. Collaborative Workspaces for HP TRIM: An Analysis of Two Options: This White Paper provides an analysis of two options for collaborative workspaces for Hewlett-Packard’s HP TRIM Electronic Document and Records Management System (EDRMS). Generally, organisations have a number of technology options to choose from to develop a collaborative information management workspace. This White Paper provides an analysis of two popular options for collaborative workspaces using HP-TRIM EDRMS as the core capability. The options that are the most popular for HP TRIM are Microsoft SharePoint and iCognition Diem Portal. An alternative option of integrating the two will also be discussed. It should be noted that this is a comparison of two different approaches: although Microsoft SharePoint can be installed ‘out-of-the-box’, to achieve good outcomes it requires design and development; where as Diem Portal is a Commercial-Off-The- Shelf (COTS) product implementation. iCognition implements both Diem Portal and the HP TRIM integration to SharePoint, and we recommend either solution based upon an analysis of business needs and overall requirements.

Contact iCognition for copies of these white papers.