ISIS Papyrus Software

Posts Tagged ‘business architecture’

Business Architecture: Consolidation vs. Integration

In benefits, markets on November 12, 2009 at 2:30 am

The enterprise IT market is often characterized by fragmented products for specific applications. Although their hard-coded functionality may seem sufficient for the intended purpose it is time and again overlooked how much effort it takes to integrate them via XML and SOA.

The Business Architecture concept of ISIS Papyrus therefore provides businesses with a single consolidated information system that offers collaboration, process coordination and role coaching on top of the background data processing. This single information platform enables a business to model its key information assets, to support its process workgroups and to create and retain the knowledge about how the business actually performs its processes. All this knowledge and experience is shared between workgroups according to authority. Management can monitor quality criteria and audit each single process if needed. Because it is a single life-cycle platform, software borders do not exist and process optimization is a continuous exercise that does not require complex projects.

Enterprise architects who hope to  create an infrastructure of replaceable components by segmenting and layering various products have to consider poor compliance to standards and continuously changing products. These are major stumbling blocks for an enterprise architecture, whereas ISIS Papyrus integrates seamlessly with legacy applications to provide instant benefits with its rich functionality and platform and output channel independence. On the long term it provides an application infrastructure that allows for a gradual enterprise strategy towards consolidation with no additional integration efforts.

Handling Enterprise Growth Without Java

In scalability on October 22, 2009 at 2:02 am

With many Papyrus Platform installations experiencing substantial growth the topic of application scalability has come to the foreground. Owing to its design the scalability of the Papyrus Platform is unlimited in principle but it is restricted by certain synchronicity needs. Simply reading or displaying documents or content from storage has no limitation, but keeping multiple write accesses in sync creates scalability issues. Clearly, when the number of users is doubled from 1,000 to 2,000 users then it does require monitoring and, if necessary, scaling of the hardware. When the number of documents or process tasks is doubled from 1,000 to 2,000 per hour that also requires consideration how that load can be safely spread across server nodes. However, scaling Papyrus Platform applications is very simple compared to, for example, three-tiered Web/Java/SQL/SOA application clusters, explains Max J. Pucher, Chief Architect at ISIS Papyrus.

User complaints about a ‘slow application’ without any measurable details do not really help, yet have to be carefully considered. Users are often unaware of different processing requirements for documents looking rather similarly. The document might be simple for the user but the back-end process can be fairly complex and proactive monitoring is advised, which Papyrus Platform provides with easy-to-use dashboards and summary reports.

Scalability is not only about tuning or maintaining an acceptable response time for a growing number of users. It is unreasonable to expect that the system will handle growth in users and transactions automatically. No system does. Papyrus has many load balancing and tuning options and many are set either by default or by the system. Document applications are a complicated conglomerate of GUI, process, and rule execution threads that read and write data from a number of service interfaces or databases. The performance of the SOA back-end service interfaces or the database is much more relevant to the scalability than the user front-end. Using common database or transaction measurements the Papyrus Platform executes millions of transactions per hour and provides substantially simplified systems management and tuning without neglecting the user experience.

The Need For A Business Architecture

In value proposition on October 20, 2009 at 2:31 am

The main goal of a Business Architecture as has been stated by Max J. Pucher, Chief Architect at ISIS Papyrus, is to enable the business to improve the quality of its customer services quality through transparent, flexible and adaptable business operations. Fast-paced changes in the market environment and the use of new technologies by customers have dramatic impacts on how to run a business. Some industries face changes in their calculation processes, marketing programs, business rules and content already on a weekly rather than a monthly basis.

It is obvious that the state of the communication content controls the process and not its meaningless steps. Business communication is not just a document or an email, but can be anything: a selection menu, a web page, a sticker on the document, a data record, images, or even a voice recording or video. No matter how much time and money is spent on business process analysis, there will always be one more communication item needed for a business process once it gets going. This is why collaboration tools and email are now so pervasive. They don’t require analysis to communicate.

With this in mind ISIS Papyrus has developed its Platform that does not require a huge technology stack and does not need complex programming but a simple modeling and rule definition methodology to build a flexible and adaptable Business Architecture that is mostly under the control of the business and not the IT department. Business experts can now rapidly model, measure, and change processes independently 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 processes, rules, GUI, forms, inbound and outbound content objects.

ISIS Shows Innovations in Paris

In event on August 18, 2009 at 7:55 am

In a series of events during the coming fall ISIS Papyrus will show its innovative costumer communication and process management solutions at the Forum des Acteurs du Numérique (FAN – Forum of Digital Actors) in the French capital Paris on September 29-30.

Among the featured products and solutions will be Papyrus EYE, which empowers business users with a Web-enabled, centrally managed GUI offering the same layout and functionality as desktop applications without additional coding. Papyrus EYE is a unified RIA (Rich Internet Application) platform for all kind of applications that cover capture (scan, verify, manual correction, manual classification), document output management (interactive documents, web-to-print, campaign management and on-demand) and document management, as well as archiving, records management, case management, Automated Document Factory and management information.

Other highlights will include the unique ISIS Papyrus Business Architecture that provides seamless consolidation of freely-definable processes, rules, GUI, forms, and inbound and outbound content objects. This concept provides for transparent process optimization by user adaptation, linking people, information, and applications across geographically distributed, organizational functions and allowing business users to fulfill the strategic goals of the enterprise.

Empowering the Business

In general, system management on August 6, 2009 at 8:29 am

Many organizations these days strive to cut the costs of their IT operations while maintaining their customer service quality. This may seem hard to achieve at first sight but the solution is to shift the control of business-relevant processes from IT to business users without giving up the integrity of the core systems.

This is a key idea behind the concept of the Business Architecture from ISIS Papyrus which empowers expert business users. In fact they are enabled to adapt processes as necessary with complete independence of the underlying application logic.  This allows them to fulfill strategic business goals without relying on a rigid and complex custom-coded IT infrastructure.

The approach behind this is not to restrict business users in their execution but to guide them collaboratively by process definitions, monitored by business rules and measured by goal fulfillment without the need for integrating different product fragments of one or multiple software vendors. Papyrus provides seamless consolidation of freely-definable processes, rules, GUI, forms, and inbound and outbound content objects.