In my post “Why ECM should play an important role in the Business Process and SOA discussion” of February 11th, 2008 I made a statement “that we need to close the loop between inbound – outbound – inbound communication” and find a way to “prevent each developer, application and PC user to become its own document developer” and let Business get control back on all communication processes in the company.
The answer to this should be “Enterprise Content Management” (ECM) which is the technologies used to “capture, manage, store, preserve, and delivery content and documents” related to organizational processess.
BUT…… Everyone of you who has been involved in ECM projects knows that there are a lot of Vendors and Products out there each and everyone specialised in their own area. A typicall project involves easily 3 or more Products and always from different vendors. E.g. Scanning software, Capturing software, Email management software, Classifying software, routing / workflow software, Document Management software, Document Output Management software, Printers, etc. Of course they all need their specific version of hardware, operating system, database and this constellation has to be expensively managed for the coming years by specialized staff.
Wouldn’t it be nice if instead there was a common infrastructure for Document generation, printing, archiving and a Repository that allowed it all to be managed centrally.
Component Repository Management
As Wikipedia states “Component repository management is a field of configuration management that seeks to ensure the safe storage of different components of a software product and all its versions. This topic includes product model, revision control, and software configuration management”. The Component repository we are looking for should contain the business domain model, document building blocks, resources, business rules and should provide Services for authorization and authentication, version management, release management, audit trail, business intelligence, Integration with third party systems and legacy using webservices, messaging, http, sql.
A central Repository allows us to manage the domain classes centrally, shielding the business user from the back-end systems that are needed (e.g. client, contract, account, claim, insurance, etc). A further advantage is that it allows for the creation of an enterprise wide consistent client experience due to document templates being made from standardized building blocks. Furthermore, an integrated authorization system means that modifications can be allowed or prevented within the organization (e.g. department, end-user).
As the requirements become more complex would it not be nice if an “inheritance mechanism” (from the Object Oriented world) was used so that every aspect of the system was fully referenced? This would allow for the simplification of repetitive tasks such as changing a company logo which could be achieved by checking the old logo out, the new one in, and applying it to all documents where the logo is used. This methodology would also allow for document creation and modification starting from certain base documents where the correct usage of legal text, consistent usage of fonts and logo’s, etc could be entirely ensured.
But a common infrastructure is also needed to be able to manage application components, printers, print pools and print streams (documents). Why? Because in each enterprise there is a variety of printers that need to function for both local and central printing. Moreso, customers demand uniformity in their documents whether they be in an email, PDF, on the web or on paper. Furtunately there are some accepted standards that can be used for this.
The most common is TCP/IP which allows for the location and management of the different instances of the ECM application suite as well as with printers, faxes and mail servers. The other required standard is one that guarantees a 100% consistent look & feel of produced documents on each and every output device. IBM’s AFP is a standard that describes such a document and with specific adapters for specific devices we can ensure production of 100% equal documents.
I’m aware of only one Vendor that can offer a business communication infrastructure and services as described above and much more and this vendor is ISIS-Papyrus . They offer an unique product that is years ahead of competition because they can close the loop and they provide a repository that fulfills all mentioned requirements and even more. They have built-in support for Event Processing, User Trained Agent and a very strong User Interface based on FLASH which can all be maintained by a super user in the repository. But above all they provide the Business truly Agility because of their integrated version management and release management. Without intervention of IT an administrative user can promote changes to Test and Production but also reverse it if necessary and this all in minutes not weeks or months.
Doesn’t sound this to much as a fairy tail? I challenge you to check-out their Papyrus product suite. Be warned, it takes an open mind and at least a second read to grasp the innovative approach they took some years ago.
3 thoughts on “Business Communication Infrastructure and Utility Services”
Roel, obviously standards are good, because that is what enables interoperation, but what if you don’t need interoperation? What if you consolidate and do not need to match up your best of breed products wth extremely complex SOA? What if you don’t have to analyze and rigidize your processes? I suggest that before standards would help you to move to another tool all your processes would have changed anyway! I understand that companies do not want to depend on a single vendor, but then who can really drop Microsoft or step away from SAP or Oracle once in use? No one …
We at Isis Papyrus always look for standards that we can use practically. You are right that there are just a few in ECM and BPM. The problem with standards is the time it takes to standardize. By the time things are standardized it is far behind the scale of things needed by the marketplace. BPEL 2.0 is a good example of lagging standardization. Everyone claims to use standards and no one really does, just look at XML. You can not standardize ‘a little’ just as you can not be ‘a little pregnant’. Either you follow a standard or you don’t. Once you follow a standard, forget innovation. You are no longer on the forefront of technology. Do we need to be on the forefront? Could we not see IT as purely a commodity, as Nicholas Carr has suggested in ‘Does IT matter?’ I do not think so. IT is not about technology, IT is not about standards, IT is not about cost reduction – IT must be about human focused quality and the best available is just good enough. Holding IT back to standardize will hold back the users and thus the business. As long as IT is focused on improving service quality swiftly and dynamically as needed the business wins. So no big projects and no long-term plans. Nike got it right – JUST DO IT. (pun intended)
All the best, Max J. Pucher
Chief Architect ISIS Papyrus Software
This sounds as a very good product that can solve a lot of problems for our business.
However, as you stated in the beginning of your post, isn’t the real problem the lack of open standards in the ECM enterprise? Several vendors being involved in one organization/project should not be a problem with proper standards.
Readying your post I started to think about this and did a bit of google-ing…
As far as I can oversee it, the first steps towards such standards are taken by: http://www.aiim.org/standards.asp?ID=29284
Anyway, maybe you can share your view on the absence of standards in ECM in one of your next posts?
I will keep following your blog!
I’ve looked at ISUS Papyrus but fail to see it as another apple in the basket that is filled with apples like EMC Documentum, and IBM FileNet. To me it is the orange. A juice orange however.
I’ve not gone into the depth (yet) with ISIS-Papyrus to understand how it deals with the side of ECM that is not related to business communication. I think of collaboration in projects where lot’s of MS Word documents are created and of which the majority is of no interest after the project has delivered. Wehere tasks are being created, milestones defined and discussion is captured. I think of Case Management parts e.g. just storing a scanned copy of an identity paper in the client dossier. I thionk of the next generation ECM (e.g. Alfresco) that will be incorporating Enterprise 2.0.
I have the open mind if only it were because you can’t trust neither IBM nor EMC on there blue eyes as they tell you that they can do anything. And maybe it requires a third read as well. As for now, I’m willing to beleive ISIS-Papyrus can all handle it – open mind ;-). Maybe you can elaborate about the examples in one of your nexts post (my 3rd read…)
Looking forward to it!
Comments are closed.