Synchronization with external systems (ERP)

Premium

Synchronization with external systems: Omniscol connects to ERPs and school information systems — Aurion, Auriga, and others — to import their reference entities (instructors, student populations, rooms, resources, sites…) and send back the lessons produced by scheduling. The framework is generic: support for a new system, like extending the synchronized scope to other entities, is scoped as a project with the Omniscol team.

Omniscol interfaces with schools' external ERPs and information systems through a unified synchronization framework. Omniscol acts as the central point: it drives the imports and the exports, while the external system remains the administrative source of truth.

Synchronization with external systems is available on Premium accounts, when a connector is configured for the account. What is handled as a project is the addition of a new ERP or a new information system not yet supported, with scoping of the mapping and the flows.

Flow model

The framework covers two directions of flow:

  • Entities (inbound) — Omniscol can retrieve from the ERP the teachers, subjects, classrooms, classes, students and their external identifiers, depending on the connector and the configuration. The ext-id references are kept in Omniscol for matching.
  • Lessons (outbound) — Omniscol pushes the lessons produced by its scheduling to the ERP, with the correct ext-id references. Depending on the connector, the export can be triggered on demand, scheduled, or replayed as a full batch to catch up on divergences.

Omniscol orchestrates the configured imports and exports, keeps the external identifiers, manages the synchronization passes and exposes verification screens to reconcile the data between Omniscol and the external system.

Source and local creation rights

For each entity type (teachers, subjects, classrooms, etc.), you select the source system and indicate whether local creation and local updates remain allowed. The screen also exposes an Association button to match a local Omniscol entity with an ERP entity when both already exist.

Bridging ontologies

Each ERP has its own vocabulary (for example a "subject" in Omniscol = Unité Pédagogique in Auriga = Cours in Aurion). The framework handles the mapping: Omniscol links the concepts on one side to those on the other, so you do not have to rewrite your nomenclature.

Available connectors

Available

  • Aurion — connector available in production. An ERP published by the Auriga company, particularly widespread in French higher education (engineering and business schools). See integrations.aurion.
  • Auriga — connector available in production. Auriga the software is the full-web evolution of Aurion, by the same company. See integrations.auriga.

Directory standard

  • OneRoster — instead of a vendor-specific connector, Omniscol supports the international OneRoster standard (1.2 and advanced groups) to exchange a school directory with a compliant SIS, digital workspace or LMS. Importing a OneRoster directory falls under this Premium synchronization; the export side is served read-only and controlled by OAuth2 scopes. See OneRoster.

On request

Any ERP or information system exposing a documented API for the import / export actions and a working sandbox can be integrated as a project. Contact Omniscol support to scope the addition of a new connector.

Difference with systems that query Omniscol

Some systems can also consume Omniscol through the GET endpoints of the public API: in that case, Omniscol does not orchestrate an ERP synchronization, the third-party system only queries the data its token gives access to. This model is different from the synchronization orchestrated by Omniscol:

Model Who orchestrates? Direction Example
Synchronization with external systems Omniscol Bidirectional (entities in, lessons out) Auriga, Aurion
Partner pull The partner The partner performs GET calls Third-party connector via API

The partner-pull model needs no synchronization-with-external-systems configuration: the public API and the authentication tokens are enough. See Omniscol API.

Configuration

Setting up synchronization with external systems typically requires a session with Omniscol support to:

  1. List the objects to synchronize — users, classes, instructors, subjects, classrooms, etc.
  2. Calibrate the ontology mapping — which ERP concept corresponds to which Omniscol concept.
  3. Define exclusivity per entity type.
  4. Schedule the frequency of the passes (on demand, hourly, daily, more for catching up on divergences).
  5. Test on an ERP sandbox before going live.

Verifications and routine operations

  • Verification of the configured favorites or datasets, depending on the connector.
  • Manual triggering of a lesson export from the administration screen.
  • Scheduled full export when the option is configured in the export block.
  • Aurion XML Pivot when the Aurion connector is used.
  • Verification of the matches: the association screens flag the entities to pair or to correct.

How-to

Verify and trigger a synchronization

  1. Once synchronization has been configured by Omniscol support, routine operations are done from the administration screen: verify the favorites/datasets, pair the entities, trigger a one-off export, download the Aurion pivot when available, or purge the export state in case of a switchover.

  2. In the system configuration, use the Verify buttons of the configured favorites or datasets. Omniscol retrieves the connector's data and reports configuration or format errors when the connector returns them.

  3. To push the lessons immediately to the ERP without waiting for the next scheduled pass, click Trigger. Useful after an urgent change.

  4. With Aurion, the XML Pivot button downloads a file that the ERP administrator injects manually through the ERP console when this mode is chosen.

  5. In case of a major switchover (structure change, end of year), the Purge Omniscol button deletes on the ERP side all the lessons Omniscol exported there, to start from scratch. The action targets the selected connector and is irreversible: only to be used after agreement from support.

See also