Technology
Tempo Technology and Architecture
Tempo is built on the Microsoft.NET framework and makes use of Windows Communication Foundation to support standards-based service communication and a flexible set of deployment scenarios.
Tempo leverages the Minemax optimization and 3D visualization technologies that have been developed and refined over many years. These technologies have been extended to support important features for inter-schedule compliance.
The architecture consists of the following key components:
| Component | Description |
|---|---|
| Tempo Professional Client | The desktop client application that runs on each scheduler's PC. The client application provides rich visualisation and reporting functionality to schedulers. |
| Tempo Modules (Optimization Module, Resource Module and others) | A set of modules that augment the core functionality of the application. |
| Tempo Services – Application | Services used internally by the Tempo Application. |
| Tempo Services – Integration | A set of service interfaces designed to support interaction with other stores or systems. These services are designed to support a push of data into Tempo (such as equipment availability or reserve updates). Where Tempo is to initiate retrieval of external data, integration connectors can be used to facilitate this. |
| Tempo Services – Collaboration | The set of services used to support the Collaborative features of Tempo. |
| Local Schedule Database | Schedule data store used for stand-alone deployments. Schedule data is held within SQL Server Compact databases (which are simply files on the user's PC). |
| Schedule Database | SQL Server store of Schedule data used for any deployment type other than Stand-alone. |
| Collaboration Database | Store of collaborative data generated by Tempo that is shared across a site or organization. |
| Web Reporting | A Web Reporting interface that provides a browser-based view of the data generated by Tempo. |
The components described above are combined or deployed in one of several supported modes.
Stand-alone Deployment
This deployment mode is intended for single user working alone. This is the simplest mode of deployment and requires only the installation of Tempo Professional Client.
Network Deployment – Direct Data Connection
This deployment mode supports the storage of Tempo data in a SQL Server database. Each scheduler connects to a shared store of Tempo schedules and if appropriate, to a shared store of Collaboration data.
Network Deployment – Services
This deployment mode is similar to that described above, except that Tempo Services are hosted on an application server. Tempo Clients connect through this shared set of services. This deployment mode supports more complex interactions with external systems.
The Tempo architecture supports the deployment types illustrated above along with other variations that can be discussed to determine the best configuration for your environment and needs.