No organisation has only one IT-system. On the contrary, most large organizations have dozens of different systems. In many cases, there are benefits to be achieved by limiting the number of systems by combining more features into fewer systems. However, very often a successful strategy is to designate the needed resources to specialist- and niche systems, and then integrate these systems into a larger sharing platform. 

The philosophy behind Orbit is not that it should be a system for everything. Very large systems tend to become very expensive, as the complexity increases exponentially. Orbit is not an ERP system, Orbit is not a CRM system, Orbit is not SAP. Nonetheless, many of the features and processes in Orbit can profit from being integrated with such systems. This makes it possible to "fit" a project with economy data from the ERP system and customer information from the CRM, and project team data from the AD and HR system, thereby allowing Orbit to serve as a dashboard for all relevant information regarding a specific project.

In most cases integrations with Orbit will be a one-way integration, meaning that data will flow from other back-office systems and into Orbit - but not the other way around. However in special cases two-way integrations can be a good idea. 

Active Directory (AD)