Guiding Principles

Three principles determine the technical underpinnings of LeaseWave and inform Odessa’s design choices:

Use of leading technologies

  • Typically, the price for a mature leasing system is old legacy-based technologies. LeaseWave aims to break this correlation: its functional comprehensiveness is complemented by its use of industry-leading technologies. Odessa uses only non-proprietary tools for development. It has a long history of affiliation with Microsoft (dating back to 1997) and is committed to remain in step with advancements in web-based enterprise technology:
  • Current Version: LeaseWave 4.0
    • Development Platform: .NET 2.0
    • Language: C#
    • Database: SQL Server 2005, 2008, Oracle 10.
  • Next Version: LeaseWave 5.0 (in development)
    • Development Platform: .NET 4.0
    • Database: SQL Server 2008, Oracle 11.

Open architecture

  • To work successfully in any leasing company, lease management systems need to interact freely with other software products. Recognizing this, LeaseWave maintains an open architecture: the system has been designed to accommodate both inbound and outbound interfaces with ease
  • True Service Oriented Architecture:
    • Integrations are straightforward external applications can communicate through exposed web services
    • All LeaseWave business functions are available for consumption. LeaseWave can also talk easily with outside systems; support for any standard outbound interfacing mechanism (XML, flat files, CSV, etc.) is available.

Customizable design

  • LeaseWave is engineered specifically to be configurable & customizable to tailor-fit each leasing business, not just at implementation, but on an ongoing basis as requirements change. LeaseWave employs the concept of Rapid and Continuous process improvement to respond to changes in the decision-making process, growth, market conditions and customer requirements with maximum agility.
  • Customization-oriented design:
    • Loosely coupled layers
    • Web-service enabled middleware
    • Coarse-grained interfaces
    • Extensible class design
  • Built-in workflow
    • Automated decision making to accurately control any approval process
    • Continuous fine-tuning of workflows for efficiency based on metrics
    • Workflow-based user security and control