Compass AE Console is an application that sits on top of the Compass AE framework that allows the user to interact with their rails application with a simulated rails console.

The Agreements Engine implements model classes for storing Contracts and Agreements data, including AgreementItems, which represent the terms of the Agreement. Contracts are a special case of Agreements, specifically Agreements which are legal in nature. Agreements and Terms are often used as the execution context of a rules engine to govern other behaviors of a system.

Provides an application infrastructure based on the Sencha/extjs UI framework, as well as several utilities and example applications. It houses the core application container framework and component model infrastructure that play a key role in the RAD/Agile orientation of CompassAE.

The CompassAE Commerce Engine uses the engines that implement Parties, Products and Orders, and adds the ability to conduct commerce. It implements a pricing engine, fees, payment gateways.

ErpCommunicationEvents add models and services to CompassAE's ERP core to handle contacts between Business Parties. For example, tracking inbound or outbound emails, customer contact events, support requests, etc. These models would be used for support and ticketing systems, marketing communications applications and the like. CommunicationEvents can be typed and can relate to one another, providing the functionality to treat several related communication events as a group.

The CompassAE Financial Accounting Engine implements the basic classes that allow either interface or implementation of general ledger, accounts payable and accounts receivable modules. This module is experimental at this stage.

ErpForms provides dynamic form capability to existing and dynamic models. Form Builder coming soon.

The Inventory Engine in CompassAE implements a set of models for storing information about the availability and location of ProductTypes and optionally Product Instances. It is also the root for yield and revenue management requirements to segment and allocate inventory for different purposes.

ErpInvoicing adds models and services to the CompassAE core to handle invoicing and billing functions. It includes extensions to the core ERP classes for accounts and things that are 'billable' (products, work efforts), and additional models for the invoices/items, payments and the application of payments to invoices or invoice items. It also includes application hooks to make it easy to add electronic bill pay functionality to Web applications.

The Orders Engine in CompassAE implements models for Orders, Order Items and Order status tracking. It also houses models for charge lines associated with Orders (although it could be argued that this functionality should reside in Commerce).

The Products Engine implements ProductType and ProductInstance, as well as a number of classes to support product catalog-type functions and search/shopping scenarios.

The Rules Module of CompassAE includes classes which act as helpers in externalizing the execution context of CompassAE value objects for processing by a rules engine. It also includes an integration with Ruleby, which is a pure ruby implementation of the forward chaining Rete algorithm.

The CompassAE Search Engine provides functionality to facilitate both dimensional and index-based searches. CompassAE by default will search for an instance of SOLR/Sunspot and use it if it is available, otherwise it will attempt to use SQL to implement content searches. This engine also contains a demonstration of how to implement a denormalized search fact table using the Party entity.

This engine is implemented with the premise that services like logging, tracing and encryption would likely already exist in many organizations, so they are factored here so they can easily be re-implemented. There are default implementations here, and we track several excellent Rails projects as potential implementations of services like security and content/digital asset mgt.

The Transactions and Accounts Engine implements the root classes for adding business transactions and accounts to parties. The key marker interface classes here are BizTxnEvent, which represents a common interface for all manner of management accounting transactions, and BixTxnAcctRoot, which is the root class for the accounting of transactions. CompassAE uses separate structures for management and financial accounting.

Description of ErpWorkEffort.

Knitkit is CompassAE's content and digital asset management application. It is based on ideas and code adapted from Mephisto and adva_cms, with significant changes to integrate with the CompassAE object-relational layer and to harmonize the user interface with the rest of CompassAE.

RailsDB Admin is similar in functionality to PHPMyAdmin and other database browsing and data editing tools. It uses the CompassAE database connection information to discover the schema for an installation, and generates Extjs UIs for creating queries and performing grid-based data inspection and editing.