EnterpriseFlow been carefully crafted to give you the following key features, viz., Vendor and platform independence, Openness, and
Agility. To know more about BPM system architectures, desired features, and competitive offerings, you are invited to go over Other Resources

Vendor and platform independence
Cost- and performance- considerations demand that your application software should be platform- and vendor- neutral. EnterpriseFlow
Runtime, being a J2EE web application, achieves this objective in large measure. EnterpriseFlow Runtime comes with a built-in Electronic
Office Suite; so you can start using the product from day one, without having to wait for process designs to be completed. 
A whitepaper compares Email with EnterpriseFlow Office; we hope this will give you compelling reasons to adpopt EnterpriseFlow Office 
for implementing an Electronic Office in your organization. User authentication can be by password, or if identity theft must be 
absolutely ruled out, by hardware-token based strong authentication.

Openness
EnterpriseFlow is an open software system. This openness is due to the fact that the database is pure XML. A Developer's Guide gives
complete information about the database schemas. Therefore, users can easily customize, or develop extensions to, EnterpriseFlow.
EnterpriseFlow provides a number of process-independent utilities to the users, as well as, to Administrators. These cover viewing
and printing archived processes, exception handling, and database backup.

Agility
Business processes are continually evolving. Your BPM System must therefore have the necessary agility, in order to rapidly adapt 
to these changes. And in achieving this objective, EnterpriseFlow IDE beats all other process design systems hands down! The IDE generates 
process designs as compact XML files. And from these XML files, the IDE goes on to automatically generate the process-specific software.