Product Sales Benefits	Customer Incentive
Open System / Modular Architecture
Compsee's Mobile Enabler for AS/400 incorporates Open System Architecture, allowing developers to build custom solutions utilizing Industry Standard Development Environments. The independence of a modular design increasing productivity by simplifying the inception to implementation time.	Protects the financial investment in existing data collection infrastructure. No need to obsolete existing equipment and start-over. Reduced development time frees up resource for other applications.
Batch - Real Time Interoperability
The Batch - Real Time Interoperability built into Compsee's Mobile Enabler for AS/400 delivers application freedom to the customer. The Mobile Enabler Environment is flexible enough to allow: The Mobile Enabler Client device to store transactions and messages locally. Upon re-establishing connectivity to the Wireless Network, the Mobile Enabler Client, transfers the stored transactions and messages to the Mobile Enabler Server. The Mobile Enabler Server can then resolve with the Host database or application any responses from the batch transactions, independent of the real time Mobile Enabler Client devices.	The ability to switch from RF to Batch allows the user to roam outside of RF coverage area and continue to capture data. Loss of RF coverage will not impede productivity. Returning to RF coverage can programmatically result in either prompted or automatic download to host. This same ability allows the user to continue capturing data even if the host is down or is being rebooted.
Supports Multile Client Types
Compsee's Mobile Enabler for AS/400 supports Thick Client, and Casual Client Architectures. The Client/Server Architecture places the business rules and application processes at the host level. Compsee's Mobile Enabler Thick Client Architecture can support Batch operations and Real Time operations on a single mobile device. The Thick Client Architecture also supports mobile database implementations of Oracle Lite and Sybase. The Thick Client Architecture places the business rules and application processes at the mobile client level. Compsee's Mobile Enabler "Casual Client Architecture" incorporates the best of Thin and Thick Client Architecture in to one solution. The Mobile Enabler Server supports Windows Printers, and Smart Appliances.	This capability protects your financial investment in existing data collection equipment and infrastructure, providing the ability to gradually phase in new equipment as required to meet the application's demand. By creating one Virtual Machine application in Java Script the application can be easily ported to any portable device that supports the virtual machine.
Supports Multile Client Connectivity Types
The Mobile Enabler Server supports the following interfaces: 802.11b 11MB and 802.11 2MB Wireless Network Symbol Cisco Proxim (2 MB only) Lucent (11 MB only) 900MHz Wireless Network Ethernet Wireless Networks supporting TCP/IP	Open architecture allows easy integration into existing systems. By using 802.11b compatible equipment, diverse hardware can easily coexist on the same backbone running the same application.
Supports Multiple Vendor Devices
The Mobile Enabler Client supports multiple vendor products simultaneously. A customer may choose to implement, Compsee, Symbol, and, Link terminals, all on the same enterprise network. The Mobile Enabler Server is capable of simultaneously supporting multiple Wireless Network technologies. A customer may have the requirement to implement a Symbol 802.11 FHSS network and a Cisco 802.11b DSSS network and still support a legacy 900MHz network in the same facility. You can achieve this by deploying Compsee's Mobile Enabler Server.	Again, Open System Architecture provides that ability to design a custom system solution tailored to the specific requirements. This approach completely eliminates the need to design hybrid systems with unique software for each hardware device deployed.
Supports Multiple Device Operating Systems
A customer can choose to implement a WinCE device in concert with a Symbol Palm OS devices as well as Compsee DOS devices, all in the same facility, all on the same wireless network. By providing a Device Operating System Independence (DOSI) environment, Mobile Enabler is able to support new technologies and vendor independent appliances as they are introduced into the market place. An organization may have a requirement to manage wireless manufacturing r warehouse equipment. At the same time that organizations might also need to collect corporate information with mobile devices over the same wireless network. With Mobile Enabler you have this flexibility!	The right tool for the right job. Create the application one time and then easily port it to any hardware.
Client Device Friendly
By using the Loader facility of the Mobile Enabler Server the developer is able to perform: Automatic Client File update and synchronization Associate Client Devices to transaction types Application Store Forward - Store client applications on the Mobile Enabler Server and forward the application to the client on an as needed bases. By Implementing the Push Technology of the Mobile Enabler Server, the customer is able to freely send messages to Client Devices. By Implementing the Custom Error Handling Technology of the Mobile Enabler Server, the developer can chose to avoid informational messages, system messages, or warnings at the Client Device.	The Loader Facility will eliminate the need to pull in hardware devices from the fields or the production floor for updates. The client can be interrogated at every log-on or power-up to verify the most recent firmware and application revision(s). You will never have to worry about having the most recent revision deployed and never have to invest valuable resources tracking down and inventorying every client to make sure these updates are current and correct.
Host Database Friendly
The Open System Modular design of the Mobile Enabler Server, delivers database independence. The following interfaces are available for the Mobile Enabler Environment: IBM AS/400 EHLLAPI IBM MQ Series TCP/IP	This capability ensures a rapid development cycle with very low risks. A quick development cycle will free-up resources to deploy on other tasks.
Interface with Different Host Environments at the Same Time
From one client device the customer is able to interact with any of the interfaces listed above simultaneously. Providing a one Client to many Hosts relationship. Example: Mobile Enabler Client Device sends the following transaction: Transaction Type, Item Number, Location, Quantity, Customer Order, Flag indicating Customer Order Completed Mobile Enabler Server processes the transaction into multiple transactions: This transaction is forwarded to the Warehouse Management System running on an AS/400 using the AS/400 EHLLAPI interface telling the WMS to reduce the stock quantity for Item 12345 at location ABC by 100. This transaction is forwarded to the Order Entry System running on an MS SQL Server using the ODBC interface telling the OES to record that 100 units of Item 12345 have been picked for Order Number O98765. This transaction is forwarded to the Order Entry System running on an MS SQL Server using the ODBC interface telling the OES to mark Order Number O98765 as completely filled. The transaction is forwarded to the Shipping System informing it to print a shipping label for the Customer identified by the Customer Order 098765' Mobile Enabler Server will resolve responses that are generated by the Host applications. Mobile Enabler Server will generate a completed order message and transmit it back to the Mobile Enabler Client device. Ensemble Client device will display the Completed order	The ability to interact with multiple interfaces is particularly valuable in applications where one company buys another and are faced with the need to seamlessly integrate multiple systems into one. When a customer needs this capability this single feature is usually enough, in and of itself, to cost justify implementing Mobile Enabler.
Multi Form Friendly
The Mobile Enable Server Development Environment allows the developer to merge multiple Forms from an IBM AS/400 process into one Mobile Enabler Client Screen. Example: If the Receive process in an AS/400 environment requires 6 application forms to complete the process, then the required fields necessary to complete the process from each of the 6 forms can be identified and combined into one form (screen) on a single Mobile Enabler Client device. Thus reducing the steps and time necessary to complete the process.	One client form can trigger multiple business processes. Client applications can be designed with user convenience in mind.
Developer Friendly
The Standard Mobile Enabler Server Development Environment provides: ECMA 2.0 complaint JavaScript code. Easy to use GUI Form Designer Rapid Application Development through the use of JavaScript code. WIN32 Client Simulator One Version of Application code to Multiple Vendor devices Compsee's Mobile Enabler incorporates an Open System Modular Design. This feature allows the developer to produce solutions in Industry Standard Development Environments. Mobile Enabler Server JavaScript Mobile Enabler Client JavaScript Scout Builder Code Warrior Mobile Builder Satellite Forms	This open system approach allows you to develop in a familiar, friendly environment. No investment in new software tools, no learning curve, no new headcount to fill voids created by introducing a new server or client environments.
NT Service
Compsee's Mobile Enabler Server is a Windows NT Service. The advantages of a Windows NT Service are: Automatically start on boot up Easy to start and Stop Allow for other components to start before Mobile Enabler Server does Allow for service error recovery or notification. The Mobile Enabler Server is capable of launching other applications as needed to implement the total solution for the enterprise environment.	NT is a ubiquitous, low-cost, reliable easy to maintain platform. Running from an NT platform will require no new technical resources and there will be no learning curve or the risks associated with deploying a new hardware platform.
Multi-threading
The Mobile Enabler Server deploys Multi-threading techniques and supports Multiprocessor Architectures.	Provides scalability to faster machines. Does not require sharing of application resources
Logging
The Mobile Enabler Server leverages comprehensive logging and reporting through the Mobile Enabler Console facilities.	Provides convenient, stable audit path for troubleshooting.