|
|
|
|

I've got to say, I've seen a lot of enterprise software and what you guys deliver makes sense. It's always very solid stuff.

|
| |
|
|
Webiplex DocuPeak - Architecture Matters
Webiplex delivers innovation in, and differentiates itself with, the DocuPeak system architecture. Webiplex engineering embodies decades of experience in business process and document management systems, and weaves that into cutting edge concepts in openness, scaleability (in both capacity and performance), modularity of system components, and advanced business process control. Below are a few key concepts of the architecture. |
| |
| DocuPeak “Documents” |
| DocuPeak is designed around a central premise: everything is a document. Even if there is no physical file associated with the document (e.g. a “data-only” document) it is still treated as a first class document in DocuPeak. This means you do not have to determine the difference between meta data that might just be a “list” and meta data that might actually be a real media file (e.g. scanned image, electronic document, transactional XML, etc.) |
| |
| DocuPeak Database |
DocuPeak does not impose database limitations on the document or data model. For example, while you cannot have different record definitions in one database table, DocuPeak folders CAN contain documents with different meta data on each.
DocuPeak is also designed so that the physical implementation limits within a database are not apparent in the business data model. Folders, repositories, storage locations – are all abstracted from one another to provide unlimited growth and scalability. |
| |
| Business Process Execution |
DocuPeak’s integration with the Microsoft.NET Workflow and Business Rules engine is innovative and flexible. In addition to simple single-document focused workflows and triggers, DocuPeak rule sets can analyze sets of related documents and can be triggered in a content and time sensitive manner.
In addition, pertinent data for automated process execution is not necessarily the content in its entirety. DocuPeak uses content intelligence to “mine” required data from documents where this data is not already in the document record. |
| |
| Services and Openness = Independence |
Your business process and document management system should be stand-alone from your portal technology or your line of business (LOB) systems . Portal technologies are relatively new, and are rapidly changing in fashion so tying business process technology to one could be a risk. And, your LOB (e.g. accounting or ERP) is designed to be the “system of record”, and not necessarily be aware of any of the dynamics involved in creating that record.
For maximum flexibility, your business process system must be implemented as a service that adheres to a Service Oriented Architecture (SOA) model. Without that, you will lose the independence of the system, and the ability to substitute other business systems around it easily. SOA is the key to not being tied down to existing or past IT choices. |
| |
| Provider Architecture Underneath |
DocuPeak uses a “provider” model when integrating various engines or components. Providers allow for the easy “plug-n-play” of new components or engines without disruption to the system using these engines.
Full-text indexing and searching, Optical Character Recognition (OCR), the DocuPeak Content Intelligence Framework (CIFX) are all provider categories. Providers are easily swapped in and out with a simple change to a “config” file. |
Links
|
|
|
|
|
|
|
|