Informix announces an aggressive Sybase Migration Plan to allow Sybase users to ... The SQLServer product is being extended to support exchange tools.
Groupware Market and Trends. Yoshihisa Aono. President ... Market Share. Market Size in Japan = about â20 bil. yenâ. Growth rate is only a few percent.
The global bring your own device (BYOD) market is projected to exceed 350 billion by 2022
The global 3D scanner market is expected to reach USD 7.4 billion by 2024
The global oligonucleotide testing market to reach USD 1,746.52 million by 2024
... an employee benefits portal allows every employee to check accrued vacation .... Sun, Tibco, Web Collage, SAP Portal and SeeBeyond. ... Leaders include IBM, SAP, Sun, BEA Systems, Plumtree and Sybase. ... engine with a Web interface.
Worldwide Solar PV (photovoltaic) installed capacity for 2020 will be more than 480GW
The global beta carotene market size is anticipated to reach to USD 621.0 million by 2024.
The global animal health market is poised to witness steady expansion in terms of revenue over the forecast period of 2017 to 2025.
The global jewelry market is likely to exhibit strong growth in the coming years.
Abstract. Since the 90s of last century, there is a substantial increase of the Chinese equity market and M&A market. In order to explain the phenomenon of the ...
May 24, 2016 - The 10-Yr Muni/Treasury ratio is currently around 88%, with munis moderately rich by .... Variable rate pegged to SIFMA and LIBOR. The size of ...
Apr 11, 2011 - IMS presentation to GOIC April 2011. 2 ... Sources: IMS Health, Datamonitor, PhRMA, Ernst & Young, ... Both KSA and UAE are strong performers in the broader MENA .... The healthcare system consists of 3 tiers: primary.
Similarly, retail (in the wake of the omni-channel experience) and transport ... 'Digitally Disrupted' Retail and Banking ... greatest in Banking and Retail in 2015 ...
The global tactile paving market is expected to witness a considerable growth over the forecast period.
Japan frozen food market is expected to reach USD 5,631.0 million by 2024
Japan frozen food market is expected to reach USD 5,631.0 million by 2024
The U.S. savory snacks market size is anticipated to reach worth USD 49.37 billion by 2025
The U.S. rail infrastructure market is projected to reach USD 5.93 billion by 2025.
Canada alcoholic drinks market is expected to reach USD 35.08 billion by 2025
Jul 11, 2002 - market inequality on changes in government redistribution in 14 OECD countries from the mid-1980s to the mid-1990s. ..... hence our measure of redistribution ignores the effects of pensions and other cash benefits targeted to the elder
The availability of reference designs from chip manufacturers and original design ... 802.11n completely redefines Wi-Fi speed, ushering in a whole new level of.
among the S&P 500 index, index futures price, and cost-of-carry. Thus, a finding ... are the k-period interest rate and dividend yield at time t J k. The stock ... where StJk J dt,tJk is the dividend-adjusted value of the stock index.4 If the interes
drivers. â¢ Drop-out rates. â¢ Consequences of hearing loss. â¢ Understanding end- ... No new players of significance have entered the market for the past three decades .... Co-op. Supply-based loans. Loans for expansion. Minority ownership.
Workflow on Intelligent Distributed database Environment ESPRIT Project 20280
1. Introduction This document constitutes the second market analysis carried out in the context of WIDE. In the first delivery of this document [reference], a detailed explanation of different aspects in the computer market in general and in the workflow and database market in particular were presented. In the last six months no major movements have been produced in the market. Some trends already detected six months ago have been confirmed and the market in general continues the recuperation after some years of bad results. In addition to the main aspects detected in the market in the last six months we start in this document a series on a comparison of different workflow tools in the market. In this document we include FORO from Sema, FlowMark from IBM and FileNet from FileNet Corporation.
2. Computer Industry Panorama The panorama in the computer industry during 1996 continues with the recuperation started during 1995. Some examples are Sun Microsystems or Digital Equipment that during the first half of 1996 have increased their profit with respect to the same period of 1995. Six months ago we presented important movements in the field of software vendors. During the period between this version and the last document in this WP, strategic movements has not been so important. We can mention: • Staffware acquires CSE. With this movement, Staffware consolidates its position in the field of workflow systems. Established in Austria, CSE is a very active workflow developer and vendor. • Wang acquires document management developer and integrator Vantage Technologies. Vantage's software will be used to deliver integrated document management as part of an enterprise-wide work management system from Wang. Vantage's Impresario Ovation was specifically developed for the Microsoft BackOffice and Windows NT environment. This aligns with Wang's relationship with Microsoft. • Sema Group acquires InfoServicios, the company that provides computer support to Caja de Ahorros de Madrid. One of the main saving banks in Spain. With this acquisition, Sema Group enforces its position in the banking sector in Spain. An important aspect during the last semester has been the confirmation of Internet/Intranet as a platform to support workflow systems. We already mentioned the tool developed by Action Technologies. During this semester more and more people is considering to have a Web client for their workflow tools. This is in line with the consolidation of Intranet as the future middleware. Intranet is becoming a new model for sharing information within a company network. The main advantage is the large number of applications at a low cost, or even free, and that the development made can be used on a variety of platforms. According to press reports almost half of USA companies has already given any step to study the implantation of Intranet in the organisation. We can mention that Netscape announced a revenue of $100M revenue for its third quarter, 400% greater than last year's. The 85% of this revenue is related to Intranet sales. The main lack detected is that only a good support is provided, but the tools on top of Intranet that are able to provide higher level primitives are yet to come. Nevertheless, given the high number of companies devoted to this area of business, we expect that more and more solution on top of this technology will come in the short future.
2.1 Technical Aspects In the field of interoperability, it is remarkable that CORBA is taking a good share of the market and that it is being differentiated clearly from OLE having each of them their specific area of applicability. CORBA is also taking advantage over DCOM. The latter is a Microsoft specific distribution solution while CORBA products are available from over 20 different vendors and support Microsoft and non Microsoft operating systems. The fact that CORBA has existed since 1990, with commercial implementations available since 1992, while DCOM has been made available in beta form in 1996, makes that CORBA has had more time to mature. And the market has perceived this. DCOM is well suited to front end application development and if entire distributed application runs under Microsoft platforms, DCOM might be a good choice. Nevertheless DCOM can also be used along side CORBA.
Another important fact is the extension of Java as the new language for Internet/Intranet applications. Java is an Object Oriented language with some specific characteristics that allow to move this code from one machine to other and to be executed in different architectures. Some of its characteristics are: • Object Oriented, without multiple inheritance but with abstract classes. • Simplicity, removing some aspect of C++ that make it more complex as operator overloading, pointer management, etc. • Compilation in byte-code that are similar to machine code but independent on the architecture. • Architecture neutral • Robustness • Low overloading • Multi-threading capabilities • Garbage collector As a symptom of this success of Java, we may mention that In 1996 the ODMG Board created a new working group, chartered to define an object database standard for Java. All of the ODMG voting members and most of the reviewer members have joined the working group, chaired by Rick Cattell from JavaSoft. The group has been meeting monthly and has already reached agreement on a working draft specification. This draft will eventually become Chapter 7 of the ODMG specification. ODMG expects object databases to be particularly popular on the Java platform. In addition to the above mentioned characteristics, Java is safe, so database integrity cannot be compromised. Strong compile-time type checking, and automatic storage management substantially improve programming productivity. The ability to dynamically load new classes, including over the Internet, provides additional flexibility. The Java types map quite well to the existing ODMG object model. The Java syntax and semantics are easy for C and C++ programmers to learn. In the Internet environment, the ability to cache data in object databases on the client side provide important advantages in Java.
3. Database Market For what concerns active databases, the following events are noticed. 1. The inclusion of triggers in the SQL3 standard is making good progress. Thanks to the big effort made by IBM Almaden researchers in the context of DB2-6000, a revised version of the SQL3 standard for triggers was approved by ANSI. The new features include: a) Limitation on the expressive power of triggers acting "before" events, thus making the related computations simpler (in particular, before triggers cannot activate other triggers) b) Clarification of trigger management with respect to integrity constraints, in particular for what concerns integrity constraints with a repair action, such as referential integrity. 2. Thanks to this push, it appears that relational vendors will soon converge towards a common approach to trigger development, and thus will provide comparable syntax and semantics. 3. Another noticeable extension programmed for Version 8.0 of Oracle, which is currently ongoing the first alpha-testing, concerns the development of transactional support for time and external events. Convergence occurs with respect to the WIDE architecture; as in WIDE, triggers correspond to immediate rules and external or temporal events are supported by an orthogonal, deferred mechanism. Contacts are ongoing with the chief designers of Oracle's extended transaction support in order to compare their approach to time management with the one developed in WIDE. It could be possible to use the advanced features of Oracle V. 8 for a revised implementation of WIDE. 4. In contrast, object-oriented vendors seem not to be very interested in further exploring reactive processing. The research projects in the area (e.g., Samos, Reach, Naos) do not report significant steps forward. Commercial products are too busy in trying to compete with relational technology to be able to devote energies to active rules. Given all the above points, it appears that our choice of using a relational technology system for WIDE was very appropriate; the developments of Oracle 8 are quite interesting for their impacts on workflow management.
4. Workflow Market Overview As stated in the previous report, workflow has consolidated itself as a technology in its own right. Nevertheless, the implantation of workflow systems in Europe is still weak. From a French consulting company, the number of workflow systems in operation in France is only fifty sites. This is still a reduced number for a whole country. On the other hand, from a Japanese company, the number of groupware sites expected to be installed in Japan during 1996 is 2 millions. The message for European workflow vendors is clear: the society has not yet acquired enough culture and, on the other hand, workflow systems are not yet technologically advanced enough to cover the user requirements, specially in terms of flexibility, cost of integration with previous systems and strategies for implantation to reduce the risks. The expected broad implantation of Intranet and the trend of workflow system to use this platform is positive to ease the implantation of workflow systems. There is also an important trend of integration of workflow with groupware platforms. The reality is that most of the customers require a mixed approach that comprises both structured work processes where a workflow tool can be used, and also some free cooperation, where the services provided by groupware tools would be useful. In this context it is necessary to provide an integrated environment.
4.1 Technology Analysis Topics mentioned last issue as flexibility, distribution keep on being essential. As mentioned above, the integration with workflow is another key issue and this integration can help workflow systems to provide enhanced flexibilty and better distribution. Nevertheless, we firmly believe that the workflow system, with or without a groupware layer, must be able to provide more advanced paradigms for distribution and flexibility.
4.1.1 Perspectives Perspectives confirm the trend detected the previous semester. Internet/Intranet technologies are dominating the short future. More and more companies are facing to port their workflow user desks to html/http or even Java. In the short future we will witness the appearance of many workflow tools on top of Internet/Intranet. As mentioned in the previous report, there are many issues not covered by current workflow systems that are to be considered. Problems as teleworking, mobile users, inter-companies processes, support to temporal join ventures, outsourcing, will be tackled in an easier manner using Internet/Intranet technology.
With respect to technical aspects, some news of the Coalition are: • The Workflow Description Language (WFDL) is progressing towards the production of the first verstion. Up to the moment, the language is in their 0.6 draft. With this draft some prototypes are going to be carried out. It is expected to get some feedback from these prototypes and to integrate then in the language so that a first version of the tool can be finally obtained. • The working group for interoperability is giving a demo at the GIGA conference in Amsterdam. In the conference the interoperability among seven workflow tools was demonstrated. The demo was quite successful from the point of view of the press attendees. Some vendors participating in the demo expressed, however, their concern in how the investment made in such a demo is really got back. In the technical point of view, from the abstract specifications, concrete binding for MIME compliant e-mail has been provided and the demo is based on this binding. Additional bindings for CORBA are in progress. • A new version of the Glossary (version 2) has been completed. It will be delivered soon. • The work group on Workflow and the Internet has started working. As preliminary outputs, it is clear that some modifications are required to adapt the standards to the way of working of a Web client. • The Workflow Handbook will be published at the beginning of 1997.
6. Appendix: Tools Survey: IBM Flowmark, Filenet, FORO 6.1 platforms
6.1 IBM FLOWMARK
IBM AIX/6000, Sun, HP-UX, HP/MPEiX, IBM AIX , Sun 4.1, Solaris Windows NT
AIX(UNIX), OS.2, Windows
Database Flexibility :Oracle 7, SYBASE Proprietary System 10, HP Allbase Release G.0.29 (Oracle 7 in the future)
6.2 architecture 6.2 IBM FLOWMARK
high added value Yes: two servers levels: database, server, No: several server levels. But only Yes, servers can be configured at different server can be distributed repository management and queue services levels and distributed geographically on server cooperative servers
Yes, several servers on one DB
Yes, several servers on one database
Yes, several servers on one database and also cooperating servers through the network
Yes: Visual WorkFlo/Enterprise Edition Being developed using WAN software : multiple servers and applications can be linked. WorkObjects can migrate between systems, but no communication optimisation
mobile user support Not presently
Claimed, but not verified.
Async is difficult
6.3 integration facilities
6.3 IBM FLOWMARK
It is thus relatively easy to integrate by In order to cooperate with Visual Workflo, There are two main ways: registering: OS/2 & windows EXE, COM, a driver (DLL) must be written for each • Tool integration, via Data Server (using BAT, DLL, OS/2 CMD & Windows PIF, application CORBA) the suitable agent must be AIX executables and shell scripts, ASF written for each application to cooperate
V3.1 for host integration. In addition, any tool can be included into the activity user view for direct invocation. IBM delivers building blocks (reusable sample code for integration of a module)
at the server level and via DLL, (the suitable driven must be written) • Data integration, via the fields in the forms defined for the process, data in the corporate database can be accessed.
client hosted APIs
Yes, AIX, OS.2, Windows
Yes, Visual WorkFlo SDK for Windows No where users can build applications from a library of predefined job functions. InstructionSheet and WorkOrders are object-designed
server hosted APIs
Yes, AIX, OS.2
WorkFlo Programming Language (not No workflow specific) under UNIX, RS/AIX, HP-UX, Sun
OLE 2 support
Through Visual Basic API
Yes limited to Windows-compatible Under implementation. applications that are OLE 2.0 compliant and if dll adapter is developed for that application
half a dozen of CC
6.4 IBM FLOWMARK
Yes through ASF V3.1 No directly but through Visual Yes, mainframe terminals are emulated and Building Block for 3270 host application, WorkFlo/Performer emulation script integrated in the tool. and CICS OS/2 Integration with host emulators under WBS is available with embedded DLL support for 3270, 5250, VT220 (Third Party),RJE, LU6.2
WorkFlo was document centric, Visual No specific features for imaging, this is WorkFlo is know fully object oriented. carried out by Key-Doc that is easily therefore doc integration is heavier unless integrated into FORO. using IMS. Other integration possible but programming is then mandatory 11/15
Yes: WorkGroup/Fax software
Building Block for cc:Mail
Yes through MAPI & VIM but no The user’s e-mail is integrated into the standardised product level client.
Yes but no standardised product level
6.5 administrati 6.5 IBM FLOWMARK on security
Through user profile definition. Password encryption.
• organisation administration • process definition • process categories • other actors work user management
Very powerful tools, organisation units no notion of role, category, dispatching, Notion of role and roles hierarchy. Each represented levels of authority supported poor queue user may have as many roles as required. A excellent drag and drop dedicated tool allows to enter organisational information.
Nothing specific on that subject in the workflow specific reports (Work status, The following is maintained: documentation ressource allocation, load balancing) must • Case and task duration be developed using workflow SDK • History of documents • Users statistics • Processes average
• Incidences, exceptions case archival
Nothing provided to date
Yes, seems to be basic
All the information relevant to cases, including the managed documentation, is maintained in a dedicated database.
(activity Yes if programs already registered (no Visual WorkFlo/Composer for designing, FORO Graphical designer. activity library provided, must be built by constructing and implementing workflow each site) application
(form No form design tool, but automatic forms AutoForm for Windows generations for processes variables handling, and for activity variables displaying
object reusability Yes, programs AND sub-net (activity / sub-net)
Yes through drag and drop of objects and Yes item lists. But Instruction Sheets building needs template definitions to get associated WorkPerformers
Yes, no need to have registered needed What if on external conditions programs, they are simulated VRC like control metaphor including step forward and backward
Very powerful definition with arrays and Basic variables (string, int, float, date, ...) structures, expands at any depth, and supports «typing»
Basic variables (string, int, float, date, ...)
6.7 case management
6.7 IBM FLOWMARK
graphical follow-up history
process Yes, with same view as builder, and real Yes time update of the view as it evolves
Yes, with same view as builder, and real time update of the view as it evolves
With graphical view Each activity details Yes ( Visual WorkFlo Conductor) but log With graphical view Each activity details
file of date and time maintained by LAN or can be shown host database appears not maintained with case
Special exception control link in each Yes activity : • Exit condition failure
Mechanisms provided for the user to cancel, reject and redirect tasks to a different user
• Role expression failure with default affectation task dispatching
Role expression includes role, level, organization (self service) not same as manager of No load balancing mode
No sophisticated dispatching. Using script Tasks are dispatched to one of the user with design, a case can go to any number of the role specified in the task. The selection queues either automatically or by user criteria may be modified. choice, also could have multiple access to some case in single queue
limited through WAL
Manual task redirection to a user.
No real event management
Yes, through the definition of alarms by the user at specific points of the process.
Yes, with notification
Task priority management
Yes, with notification
Cases can be sorted according to any of the No case fields, as well as the predefined priorities established at case definition (10 levels)
6.8 user interfaces
6.8 IBM FLOWMARK
user defined baskets with customisable No standard actor interface : 8 templates Standard user interface. sorting and iconic activity status layout, are provided with their sources select process categories shown activity selection against status, process type, name (wildcarding), type, and priority icons or parametrised list shown beep on incoming activities toolbox for tools activation
create, start, monitor, stop / restart, different notion, facilities available as design and administration tasks are suspend / resume process administrator can administration tools endowed with a responsible. In the future handle process notifications and activity the monitorisation, creation, cancellation notifications Activity can be reassigned to and deletion will have also a responsible. actors and force activity status from pending, ready, running to ready or finished