ISIS Papyrus Software

Posts Tagged ‘consolidation’

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.

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.