Help / Overview

Overview

Tula at a glance — the four systems and how they fit together.

What is Tula?

Tula is a four-part platform for member care, fulfillment, billing, and analytics:

System Role
TulaERPUINeo The MVC web app you're using right now. Front-end for clients, members, items, orders, inventory, billing.
TulaERP The core business API + Service Fabric services. Owns the operational database (clients, members, orders, invoices).
TulaImporter Pulls member/clinical data out of partner product databases on a schedule and lands it in the ERP.
TulaDW Data warehouse + SSAS tabular model. Receives a stream of pushed rows from the ERP and exposes them for reporting.

How they relate

graph LR A[Partner Product DBs<br/>BiometricsProd · ConnectProd · GatewayProd] B[TulaImporter<br/>Stateful Service] C[(TulaERP DB)] D[TulaERP API + SF Services] E[SFDataWarehouseSendQueue] F[(TulaDW + SSAS)] G[TulaERPUINeo<br/>MVC App] A -->|hourly pull| B B -->|writes| C D --- C D --> E E -->|HTTP push| F G -->|REST| D G -->|read| F classDef src fill:#0c1120,stroke:#00b4c5,color:#c8d0dc classDef svc fill:#0a0f1a,stroke:#1cd4e6,color:#c8d0dc classDef db fill:#060a12,stroke:#48bb78,color:#c8d0dc classDef ui fill:#0a0f1a,stroke:#ed8936,color:#c8d0dc class A src class B,D,E svc class C,F db class G ui

Getting around

Use the sidebar on the left. The Data Import section is where scheduled imports and job history live; System > System Status shows the health of the ERP, importer, and warehouse APIs in one place.

For the deeper "why does X exist" questions, dig into any of the topic pages from the Help index.