System integration The SIS, the LMS, HR and finance stay where they are. They finally agree. Integration Hub + Historian + Facility Organizer + Security Each system keeps running. Students, programs, terms and departments line up in one record, so the board’s question gets answered from one place. See how it works 1 It connects Student information system Learning management system HR Finance 2 What runs, and what it does Integration HubReads the SIS, the LMS, HR and finance, and logs every message. HistorianKeeps timestamped readings from building and lab systems, like a lab freezer temperature. Facility OrganizerSets up campuses, buildings and departments once, so every Module reads the same list. SecurityControls who signs in and which campuses and departments each role sees. 3 What you get One student record SIS LMS Recruitment CRM
Knowledge and training A new advisor asks how a program policy applies and gets the policy page. Knowledge Library + Retrieval Engine + Q&A Engine + Security + Form Builder Your policies and program rules go in one library. An advisor asks the question the way a student asked it and gets the answer from your own policy, with the page cited. See how it works 1 It connects SharePoint Policy documents Academic calendar 2 What runs, and what it does Knowledge LibraryHolds your policies, program rules and training material, by department or institution-wide. Retrieval EngineFinds the exact passage that answers the question. Q&A EngineAnswers in plain words with the page cited, and says so when no document has the answer. SecurityEach person gets answers only from the collections their role can see. Form BuilderPuts the policy page beside the petition form, so advisors learn it while they process the request. 3 What you get can a student drop a course after the deadline
Expert knowledge capture What your registrar knows about every exception gets written down before they move on. Form Builder + Knowledge Library + Retrieval Engine + Q&A Engine Procedures, policies and resolved cases stay in the library after the person who wrote them moves on. A new advisor finds how the last exception was handled without asking around. See how it works 1 It connects Resolved cases Shared drives 2 What runs, and what it does Form BuilderGives the registrar a structured way to write down how each exception is handled. Knowledge LibraryKeeps it beside your policies and resolved cases. Retrieval EngineFinds the passage that answers the question. Q&A EngineAnswers in plain words, with the source shown. 3 What you get can a student withdraw late for medical reasons
Recurring inspections Lab safety checks and building inspections arrive on time and get recorded. Workflow Engine + Form Builder + Notification Center The Workflow Engine assigns each check on its schedule. The Form Builder holds the checklist. The Notification Center puts it on the owner’s bell, and anything late is marked. See how it works 1 It connects Staff directory Calendar 2 What runs, and what it does Workflow EngineCreates each check on its schedule and marks it late if it slips. Form BuilderKeeps every answer with who signed and when. Notification CenterPuts the check on the bell of the person who owns it. 3 What you get FRI18 Safety walk due 07:30
Spreadsheet replacement The waitlist in Excel becomes a form and a screen the registrar’s office runs. Form Builder + Screen Configurator + Facility Organizer + Integration Hub The waitlist leaves Excel and the exception log leaves the notebook. Every change is logged with who made it, next to the student record. See how it works 1 It connects Excel waitlist Student information system 2 What runs, and what it does Form BuilderTurns the hand-kept exception log into a form. Screen ConfiguratorTurns the waitlist spreadsheet into a screen. Facility OrganizerGives every form and screen the same list of campuses and departments. Integration HubReads the SIS the spreadsheet was copying from. 3 What you get Waitlist_Fall_FINAL.xlsx, edited 2 min ago
Data sovereignty Data would stay in the region you choose, with access by role and campus. Security + Model Router + Governance + Authority Matrix Singularity for Education is in development. The controls it would use run today: you pick the region at onboarding, Canadian data stays in AWS Canada Central in Montreal and US data in AWS US-East or US-West, and sign-in goes through your identity provider. See how it works 1 It connects Identity provider Student information system 2 What runs, and what it does SecuritySigns people in through your identity provider and limits each person to their role and their campuses. Model RouterUses the model you set for each digital employee and records every choice with its reason. GovernanceChecks every action before it runs and writes down every decision. Authority MatrixSets the authority each digital employee acts inside, action by action. Anything outside it waits for a person. 3 What you get Region: AWS Canada Central, Montreal
Custom screens Screens for registrar and advising staff, built without a developer. Screen Configurator + Form Builder + Security Build the petition screen your advisors need, preview it and publish it. Each answer stays with its form version, next to the student it’s for. See how it works 1 It connects Student information system 2 What runs, and what it does Screen ConfiguratorBuild a screen in the editor, preview it, publish it. No development ticket. Form BuilderPuts the petition or the checklist on that screen. SecurityEach role sees only its own screens. 3 What you get New screen: Late drop petitions Lay out Preview Publish