The Architectured Enterprise 2.0

The ISIS Papyrus Platform offers a business architecture based methodology – not just an ‘open’ architecture – for process management that automatically discovers and documents any type of user interactive process performed on the entity models. The resulting transparency enables process improvement by user adaptation. Business users have  to the architecture models and can use these to create mission critical processes that link people, information, and applications across geographically distributed, organizational functions. It empowers the process owner to fulfill the strategic goals of the executive.

Papyrus functionality: Analysis, modelling, infrastructure, integration, project management, reporting and auditing, process management, inbound and outbound content, business roles and goals, user engagement and social networking, portal applications, monitoring and optimization, execution, content delivery, and archiving.

Business experts can now rapidly model, measure, and change processes independent of underlying application logic. Papyrus does not require additional separate rule engines or collaborative mapping layers to enable processes to dynamically adapt to changing business needs. The collaborative ISIS Papyrus Platform approach does not restrict the business users in their execution but guides them by the process definitions, monitored by business rules and measured by goal fulfillment without the need for Eclipse based integration between the different product fragments of one or multiple software vendors. Papyrus provides seamless consolidation of freely-definable process, rules, GUI, forms, inbound and outbound content objects.

Key Features of the Papyrus Platform:

  1. Analysis: The Papyrus Platform enables the executive to define the processes in terms of owners and their goals. Flowcharts are used for process dependencies only and not for step by step activities. Activities are auto-discovered and improved or adapted using the auto-documentation functionality of the platform.
  2. Modeling: ISIS Papyrus WebRepository enables the modeling of data and content entities that can be used by business users to assemble collaborative processes from application specific framework libraries. The object-relational database uniquely supports the definition of semantic relationship models.
  3. Infrastructure: The Papyrus Platform is a complete and encompassing application environment that not only reduces the technology stack and associated cost but also provides complete system and network monitoring.
  4. Integration: Papyrus consolidates the functions of process, content and customer communications management without complex SOA functionality, but provides SOA and other interfaces to integrate with ERP.
  5. Project Management and Deployment: The ISIS Papyrus WebRepository is the central management component that also handles all asset version control, project management and deployment processes. It also acts as a service registry (also UDDI) and user/role directory (supporting LDAP). Papyrus was designed and built around the central repository from the outset.
  6. Monitoring and Auditing: Management can continuously measure key performance indicators for process execution and business goal achievement. Auditing can be performed in real-time using boundary rules or by post-verification of archived process tasks.
  7. Process management: Processes in the Papyrus Platform are collaborative activities performed on architecture data models and content. State/event chains of execution are used rather than rigid flowcharts. Event driven diagrams are used to present process, rule and goal dependecies.
  8. Inbound content: Papyrus is uniquely consolidated with its ability to capture ALL incoming content, perform machine learning classification, extract and validate business data, and execute automated business responses and initiate straight-through or user-interactive processes.
  9. Outbound content: Papyrus provides Digital Asset Management for all content types with the relevant administration workflows to create high-quality marketing and business content that can be delived through all channels, such as print/mail, fax, email, web, or mobile messaging.
  10. Business Rules: Papyrus provides Natural Language Rule (NLR) definition for business users than can be executed in the process environment directly and reused as templates in any process. Standalone rule engine servers that have to be data-integrated by means of SOA are not required.
  11. Business Goals: Structured processes without goals that only need execution monitoring are an unecessary simplification. Rather than the additional complexity of adding Business Activity Monitoring, Papyrus presents and monitors goal achievement throughout the process execution.
  12. User Engagement: Process management is in most products a very limited routing of data entry forms from user to user by means of a flowchart. Ajax and FLEX do not improve that, but make user interaction more difficult to develop and maintain. Papyrus EYE allows the user-definition of PC-GUI like, role-specific user interfaces for the browser and thick-client.
  13. Social Networking: Papyrus offers RIA, chat, wikis, blogging, user configurable GUI presentation, social interaction with coworkers, all under control of the role/policy authorization and in CONTEXT with the process.
  14. Portal applications: Process and content management vendors have been purchasing portal software vendors in a try to provide what ISIS Papyrus offers totally consolidated and out of the box: A powerful, in-built portal server, that does not require or enable Java progamming but is managed through the version controlled WebRepository.
  15. Reporting & Optimization: The tightly integrated Application Analyzer provides real-time visualization of system details, such as resource utilization, server load, memory consumption, network load, detailed component response times and gathering of historical trace and log information in a central system facility.
  16. Execution: The node-kernel program of the ISIS Papyrus Platform is a consolidated, distrubuted object-relational database and transaction engine with peer-to-peer communication. That not only enables n-tier application structures but moreover server clustering designed to handle extremely high-volume, mission-critical transactions across multiple servers.
  17. Content delivery: Most process management products are content blind and most content products have no or limited process capability. While Papyrus uniquely consolidates both, it also provides consolidated content delivery through all outbound channels: print/mail, fax, email, web, mobile.
  18. Archiving: The Papyrus Platform can provide the ability to spread long-term, securely encrypted archiving with digital signature across any number of archive servers or link to most existing archive systems for content storage.
Advertisements

Is security finally a mainstream subject?

When we announced in 2003 that we were adding a tightly integrated security functionality into the Papyrus Platform the response was absolutely amazing.

ZERO!

Till today I am amazed at the lack of professionalism that such a nonchalant security attitude presents. How can any executive or IT manager simply ignore it? Now that more and more data thefts and security breaches become public maybe the tide is turning. A couple of years ago EMC bought Authentica – a 20 head startup – to do the same thing. The focus of Authentica was to secure content on remote and mobile devices. I was amazed at the time to hear that Documentum had no such functionality up to that point. EMC has acquired a long list of software products before and after that to try and get anywhere close to what the Papyrus Platform offers as a total. But it is a huge difference if you are playing mix and match or if the system as a whole employs a full security strategy.

The Role/Policy authorization of Papyrus is not just for outer shell protection – stop people from braking in – but it controls what a particular user role can do with any particular kind of object in a particular business unit. It is more than just simple access control. Papyrus also offers to properly authenticate the user by either password or SmartCard access and if necessary using Biometrics such as fingerprint readers. But that is not all. The content (actually any object) has to be protected from prying eyes by encryption even if it has been copied to the PC of an authorized user. The Papyrus Object Space database offers that facility.

Yes, EMC is compared to ISIS Papyrus a big cheese and they are still filling the holes!

Content Management Interoperability Services (CMIS)

Since 2001 we have been making businesses aware that there is a need for Inbound/Outbound business content to be managed in a consolidated business process with common business rules. We never saw these as separate processes.

Finally, EMC, IBM and Microsoft have announced a jointly developed specification called CMIS, which uses Web Services and Web 2.0 interfaces to enable applications to interoperate with multiple Enterprise Content Management ‚repositories‘ by different vendors. (Psst – an archive is not a repository …)

They intend to submit the CMIS specification to OASIS (Organization for the Advancement of Structured Information Standards). The ultimate goal of CMIS – Content Management Interoperability Services – is to dramatically reduce the dramatic cost for multi-vendor, multi-archive environments. Businesses spend a huge amount of time and money to create and maintain custom integration code and one-off integrations for ECM systems as we proposed for so long.

Now with CMIS we can push the clunky archive systems to the server back-end and give the business users the consolidated, easy-to-use, user front-ends for ECM, BPM and CRM with the Papyrus Platform that they actually need.

We can now use CMIS (an SOA like interface spec) to link multiple existing archives (repositories in their diction) to unlock content they already have by adding modern Web 2.0 or RIA user interfaces that exhibit the business processes (ideally trained with the UTA) and the related boundary business RULES.

We are already working to define the CMIS specification for the Papyrus Platform in sync with the available information. Because of our powerful integration features it is fairly easy to do so. As soon as our analysis is complete and we can estimate an availability date, we will officially announce support for the CMIS specification.

Papyrus for Records Management and more …

These were questions that were posted about doing Records Management with Papyrus:

  1. – Can retention policies be declarative described and dynamically assigned (rules)? YES
  2. – Can records be divided in so called sub-files to apply different retention policies? YES
  3. – Is there support for classification schemes aka taxonomy (industry specific) and if so how is classification being done (manual, automatic, pre-defined)? Yes, the taxonomoy is definable and classification can be trained and then highly automated. It is part of our Capture process.
  4. – Is there support for audit trailing? YES.
  5. – Is there support for Retention and Disposition Schedules? YES
  6. – How is backup and Recovery of the records and meta-data addressed? The internal back procedure of Papyrus takes care of archiving data on nodes.
  7. – Is there support for shredding (destroying)? YES (date triggered)
  8. – Is there support for “disposal holds” (to prevent destroying of specific documents)? YES
  9. – What about the workflow (e.g. review, approval) of certain actions like disposition? YES, is freely definable.
  10. – Can records being transfered to other locations, systems? If so, is the original then destructed afterwards? That is freely definable.
  11. – Could you tell a bit more about Inbound (capture) does it include also email management? YES. Emails are captured and then classified.
  12. – Do i understand correctly that ISIS supports RM for Outbound (how)? YES. Once the document is ready to be sent it an be archived as record without additional functionality needed.
  13. – Is DoD 5015.2-STD supported (how) and if so is Papyrus certified? NO.
  14. – Is MoReq2 (European) supported (how) and if so is Papyrus certified? NO. In the plans.

You will find my complete position on Records Management on my ‘Welcome To The Real World’ blog.