The Isis Papyrus Business Information Platform

In 2008 ISIS Papyrus celebrates 20 years continual innovation. From the first forms design product in 1998 to its current platform, Papyrus uses artificial intelligence for process management, ISIS Papyrus has always been to innovate in the first place, too. More than 2,000 customers worldwide use ISIS Papyrus products for strategic applications such as managing the issuing and renewal of more than half of the United States credit cards. By far the largest share of all financial, insurance and telecom documents in the EU is created by ISIS Papyrus Software. The upcoming ISIS Papyrus V7 is already offering, which will be announced with Microsoft, IBM and Oracle as
ISIS Papyrus - built on its Papyrus Objects integration architecture - delivers an open, as well as standards-enabling platform for business process management across Papyrus Inbound and Outbound, third-party and legacy applications. Papyrus is delivering pre-built business processes across ERP, CRM, ECM, as well as business intellligence and industry applications using a meta-object model, SOA-compatible and general messaging interfaces, and a powerful freely definable portal user interface. Inbound and Outbound document management is tightly integrated with the central Change Management repository. Additionally, business users are able to extend the object model with their own meta-data definitions, store it to the repository and have full upgrade protection across any future product versions.

"The Papyrus architecture solves the long-term managment problem of processes that are linked to multiple applications," said Max J. Pucher, Chief Architect of ISIS Papyrus Software. "By not depending on late-to-the-market standards such as BPEL we can focus on true long-term and cross-platform compatibilty to give our customers the flexibility to make changes to the underlying applications as well as the processes without disrupting the business users."

Using thePapyrus WebRepository customers can immediately use Papyrus' existing business objects, interface services, process and business case samples and infrastructure components to define specific end-to-end process integrations with or without related documents. Using a proven reference architecture and reusable service interfaces, Papyrus WebRepository significantly reduces the time, cost and risk associated with implementing Service Oriented Architecture projects. Our common model approach for application integration provides the foundation for creating composite processes while ensuring long-term process durability. WebRepository allows customers to define processes and integrations with the same development efficiency, control and visibility that ISIS Papyrus employs for its own software systems and inhouse applications. The Papyrus WebRepository not only manages the modeling and deployment of how processes and services are utilized and how they relate, it further enables customers to run complete integration tests, and most of all ensures the rentention of process analysis as well as implementation knowledge.

Why not Business Process Execution Language (BPEL)?
While BPEL is a standard, it is common practice to utilize jBPEL (BPEL with Java) that is proprietary to each vendor. The software user has therefore the worst of BOTH worlds - it is outdated (because it is built on a standard) but it is still proprietary. Each software vendor adds complex service links as API's and SOA interfaces to make the integration with their own tools easy and reduce the cost to deploy and maintain integration. That makes the process implementation completely proprietary!

Despite a papyrus system installation and documentation of the design does not require Java or C language programming, customers do expect and receive a complete analysis, training and implementation of the service pack. ISIS experience, in the world's major adviser.

We understand the challenges of ISIS Papyrus, large face, manage processes and to produce, manage and distribute personalized, data-and process-stay communications with customers in today's competitive market. ISIS consultants analyze the company unique communication goals and give us the tools and knowledge are needed to high volume, personalized paper and electronic communications, generate significantly improve customer and prospect responses and customer satisfaction.

The ISIS Papyrus Solution Spectrum

* CRM, ECM and BPM processes in a consolidated environment
* Client Response Management, Front-to-Back office processes, complaint Handling
* Account opening, claims handling, case management, call center management
* Automated correspondence, client reporting, utility and telecom billing
* SOA-enabled, process-focused integration into portal applications
* Interactive client communication for financial and insurance companies
* Internet document distribution and presentation in HTML / GIF, Java, AFP, PDF and Flash
* Short term re-print staging and long-term archiving for customer care
* Document Capture, Classification and Data Extraction
* PC based dynamic business document design for batch and client/server
* Document consolidation without changes to your existing applications
* Production formatting on the platform of your choice from MVS to UNIX to any Intel OS
* Campaign management for a multi-channel, electronic and print marketing approach
* Post production, sorting, testing post continuity, discounting, and file import
* Network print management for IPDS, Xerox, PCL5, Postscript, and Scitex.

Data Management Solutions

Enterprise Data Management (EDM) is the basic concept of managing data in a central repository with protected access along with ways to share data responsibly.? Various approaches have been pushed into a production environment with this goal in mind.? These uncoordinated approaches by various segments of the organization can result in data conflicts and quality inconsistencies – making it difficult for users to trust the data as it is incorporated into models, mapped to applications, used to perform calculations, shared among participants and relied upon for decision-making.? Enterprise level data search capabilities has proven to be very useful for a fast paced environment and can provide a rapid return of input that is valuable.? This technology helps the end user make faster decisions based on the same information that could have taken days to receive instead of a few seconds.? Many developers and companies have created a wide variety of this same concept, but over the years that concept has strayed off course.? The basic concept is to create a single source search capability with the ease of use for the end user along with reliable results that pertain to the end users request in a timely manner.?? Now we have a large amount of software that performs similar functions each with a slightly different take on the overall objective.?? Operational DataTek puts the simple concept back in the forefront and pull the efforts of different communities into one management system.

BUILDING THE OBJECTIVE:?
While the Operational DataTek solution was being design and conceptualized, the key fundamentals were never overlooked.? Provide the user with what they need to do their job faster and more efficiently than ever before.? How can this be achieved?? Simple, listen to their request and learn from there needs.? In order to do this the system will also have to conform to change.? A dynamically changing system is what holds the key to success.? If the user is searching for a specific location in an area of interest, those results will be packed with information on that item.? Now the system knows the users is doing research on this particular item and will automatically let that user know when new items come in that meet the criteria either by instant message, email or notification the next time they login.? We can even provide a cross reference to more information that has commonalities besides the original keywords that were used to return the result set.? Now you’re getting results that are specific to your search without providing a cross reference of key words to pull back data.? A basic keyword search doesn’t have to return the basic results; it should contain a rich set of content that can help the end user expand their view on the problem set.? Our system provides that technology for the user.

Technical solutions designed for simplicity and security requirements working together without compromise to the purpose is our solution.? Empower your analysts with a single source solution and open the door to data sharing across the board that will result in answers that didn’t exist before.

AUTOMATION, NOT PERSPIRATION!???
Building a data management system that maintains itself is the ideal solution for any agency or command utilizing these tools.? Even with computer technology today, a 100% automated solution isn’t realistic, but the closer you are to that percentage the lower overall cost of maintenance.? We have created a system that is automated to the max.? It is automated where is should be automated and manual process are kept where necessary.? As new data sets are added or existing sets change, the system will adjust itself to maximize on productivity and system resources.? An end user can login to the system and manage their own datasets by either uploading products or creating them on the fly.? Simple data entry forms make it easy to create a standardized product.? As a product is created, it can automatically be searchable by other users doing similar research.? The creator of the product can manage how the document is handled, which means the end user can simply make a few changes to their settings and their products are either shared with the entire network or specific users and groups.? This is data sharing at its finest.? Let’s let the people who create these products share them out to who needs to know and get problems sets resolved.? The automated system will share out the products created or uploaded by users based on how the user wants their information shared; there is nothing they need to do to incorporate them into any search results.

DATA, DATA & MORE DATA:
Data is the heart of the system. Our system will provide a capability for users to create their own data sets and these, in their own profile. Together with the creation of products, the user other user products can as long as the user to access search. In addition to the user to create and maintain their own products, there are alternative methods to obtain data, and we are prepared. Some records can be automatically recorded worldwide locations. Either via FTP, basic file system locations or allows a direct connection to another database with permission.

• FTP (File Transfer Protocol) - 100% Automation


• Data starts out from the original source and is transferred to the Common File System location


• Data will be tagged and parsed and ready for final ingestion process in the System Database


• Data is now searchable by users?


• File System Transfer - 50% Automation


• Data starts out from the original source and is manually dropped into a folder on the Common File System location


• Data will be tagged and parsed and ready for final ingestion process in the System Database


• Data is now searchable by users?


• DB 2 DB: - 100% Automation


• The system connects to a remote database with given permissions by source owner


• Database structure of remote database is mapped and individual products are created and dropped into a folder ready for ingestion
  Data will be tagged and parsed and ready for final ingestion process in the System Database


• Data is now searchable by users?

DATASHARE:?
Each user will be able to create and maintain its use of easy to use interface their products. Once a product has been created, it will achieve the best performance of the other data set indexes. Even if the main objective of data sharing, some of which data sets require more secure access. These data sets will only be right with the user credentials. With the products created by individual users to share one set of data can come into the system automatically from the external sources.

DATASTREAM:?
Streaming data will also be available using multiple methods including File Transfer Protocol, Drop Folders and Database Connections.? The file system is automatically maintained so you don’t end up with folder names that have very little meaning to someone looking at it for the first time. The system maintains its own naming convention to keep file system organization standardized.? Information moving in and out of the file system will be monitored for inconsistencies and maintain structure.???

DATAPROC:
Each dataset is parsed individually with a process geared towards that particular format.? Each parsing procedure is based on a common standardization format, but this can be customized for each data set that might have unique aspects that need to be exploited.? This portion of the Dataflow process is extremely importation because this is where the data is optimized for search capabilities.

Data definitions and tagging: One of the main challenges associated with EDM is the ability to transfer data, comparing from several internal and external sources. In many cases these sources are inconsistent terms and definitions used to describe the data content itself - make it difficult to relate data to compare hard-to-business processes, hard to complex applications and automate difficult to exchange data feed too. This often leads to a difficult process of data mapping and cross-references. Normalization of all concepts and definitions on the data attribute level is designated as part of the EDM metadata and is an essential prerequisite for effective data management.

STRUCTURE:
Database, each record has a good basis for a wealth of information associated with. As a product into the system intake, multiple runs of the product development process, information may be missed, and has created the most primitive Meta record and related products. Interested in this process to create a few items:
Full text extraction of original source
Word tagging based on content in full text extraction
XML markup of text extraction
Global variables that are populated with each record
Original product format for future reference
Metrics for each record and data set as a whole
Associated data relationships between other related products
Data Model Theory: A data model theory has three main components:
The structural part: a collection of data structures which are used to create databases representing the entities or objects modeled by the database.
The integrity part: a collection of rules governing the constraints placed on these data structures to ensure structural integrity.
The manipulation part: a collection of operators which can be applied to the data structures, to update and query the data contained in the database.
DATABASE INDIVIDUALITY:
What drives the usefulness of the data, how the data can be retrieved and used in an operational environment. Each user receives a certain amount of space to host it in the database for their own products. The data, which has created by a user, will also be integrated with other data sets that are taken by different methods. Each record has its own data, but each has also built boards that connect the data connection. Running a cross between two single tops have never been so easy with this method. Cross reference material displayed so that the user assumes that this particular product data, which contains the original question in context. The associated data can not use the key words in order to obtain this information, but it is directly on the keyword and tagging technology.

FRONT-END USABILITY:
And difficult when using a set of tools, how the end user in mind, once these users, the layout, to create an interface must correspond to the arrival of multi-function button required. Graphical interface is good, and must be understood not see, understand its intent. Users can see the screen, you should be able to understand what information is displayed or the function of each button.

• Web based user interface:
  
  
  
  • This application will be the most widely accessible application.?
  
  
  
  


• DataTek light java based application:
  
  
  
  • This application is a smaller version of the web based application and the desktop application.? It can pull results back fast and easy with limited capability.? It’s good for a quick and dirty way of getting results.? The application can be downloaded online or installed via CD depending on availability.?
  
  
  
  


• Desktop application
  
  
  
  • The desktop application has the same functionality as the web based application except for a few additional features.
  
  
  
  

GEOSPATIAL INTEGRATION
Geospatial tools are becoming more important than raw data itself.? For a user to visualize message traffic on a graphical representation of any given location helps the user see how the data relates spatially.? The open source community has created many unique web enabled geospatial applications which helps lower overall development costs and gives us the ability to create geospatial tools exactly how we see need.?
A geospatial application has shown its use in the field as necessary as any other tool out there.? When a product has a geospatial coordinate associated with it, the ingestion process will pick up that information and mark the product as geo operable.

TRAINING:?
Training is always a key asset to any system in the field.? With the simple ease of use, training becomes a community effort where the user next to you will have the answer.?? This system is designed from a quick and easy Google type search to a more advanced and detailed search.? If an end user doesn’t fully grasp the more advanced features, or they don’t have the time, they can still utilize the system to its full operational capability with the basic functions at their fingertips.

.NET RIA Services links

One of the common tasks that .NET RIA Services developers have to undertake is testing their mid tier business logic code. Mid tier code typically uses a data access layer (DAL) like Linq to SQL or Linq to Entities for persisting data. However directly coupling the business logic code to the DAL will pose challenges for unit testing and causes tests to depend on the database. One possible solution to avoid this problem is to adopt the repository pattern and write business logic code to go against repository.

The following steps demonstrates an implementation of a domain service class using a repository to make it unit testing friendly. The example code uses the .NET RIA services walkthrough application as its starting point and is modified to use Linq To SQL as DAL.

( Unit Testing Business Logic in .NET RIA Services: http://blogs.msdn.com/vijayu/archive/2009/06/08/unit-testing-business-logic-in-net-ria-services.aspx )

Microsoft .NET RIA Services simplifies the traditional n-tier application pattern by bringing together the ASP.NET and Silverlight platforms. RIA Services provides a pattern to write application logic that runs on the mid-tier and controls access to data for queries, changes and custom operations. It also provides end-to-end support for common tasks such as data validation, authentication and roles by integrating with Silverlight components on the client and ASP.NET on the mid-tier.