Outlook Insight, Modern Technology

THE SIXDOT STORY

How SixDot fits together

Three apps that each do one job well, connected where it counts, on one platform that does the rest.

1. START WITH THE PROGRAM

SixDot BE runs the Business Enterprise Program

A Randolph-Sheppard program is vendors, facilities, equipment, agreements, monthly statements, set-aside, commissions and federal reports. SixDot Business Enterprise holds all of it in one accessible system that works for your staff and for your vendors.

It also manages the repairs. When a cooler fails, the vendor raises a work order in BE against that facility and that piece of equipment, where the history already lives.

What SixDot BE holdsA SixDot BE tile in the centre surrounded by six labels: vendors, facilities and equipment, monthly statements, set-aside and commissions, RSA-15 and reports, work orders.SixDot BEvendorsfacilities and equipmentmonthly statementsset-aside and commissionsRSA-15 and reportswork orders
Figure 0. Everything the program needs, in one record system.

2. REPAIRS WITHOUT THE BLOAT

SixDot TM takes the work order from there

A ticketing system is a product in its own right: routing, assignment, statuses, internal notes, approvals, notifications and history. Building all of that inside BE would turn a program system into a help desk.

So BE hands the work order to SixDot Ticket Manager. TM routes it to the service provider, tracks it to resolved, and sends status back to the vendor and the program manager inside BE. BE stays a BEP system. TM stays a service desk. Nobody learns a second tool.

The work order loop between SixDot BE and SixDot TMAn vendor raises a repair in SixDot Business Enterprise. The work order becomes a ticket in SixDot Ticket Manager, routed to a service provider. Status flows back to the vendor and program manager in BE.SixDot BEvendors, facilities, reportsSixDot TMrouting, status, historywork orderstatus backbvvendor reports a broken coolerspservice provider fixes it
Figure 1. The work order leaves BE as a ticket, is worked in TM, and its status returns to BE.

3. ANSWERS WHERE THE QUESTION IS ASKED

SixDot KI answers policy questions inside BE, and on its own

BEP staff have questions all day: what the regulation allows, what the state policy says, what the operating agreement requires. They want to be compliant, and the manual is six hundred pages.

SixDot Knowledge Interpreter is built as a component. Docked inside BE, it answers from your approved policies with the citation, right beside the record the question is about. On its own, the same KI serves every staff member and the public. One corpus, one set of answers, wherever the question is asked.

SixDot KI inside SixDot BE, and on its ownA large SixDot BE window with a Knowledge Interpreter panel docked on its right side, labelled ask a policy question here. Beside it, a smaller standalone SixDot KI window labelled the same app, on its own.SixDot BE: Vendor recordSixDot KIask a policy questionwithout leaving the record34 CFR 395.3SixDot KIthe same app,on its own
Figure 2. The same Knowledge Interpreter, docked inside BE for program staff and standing alone for everyone else.

4. FOCUSED APPS, FAMILIAR EXPERIENCE

Each app keeps its job. Each makes the others better.

This is the principle behind the whole platform. We do not bolt every feature into every product. BE runs the program, TM tracks the requests, KI answers the policy. They connect at exactly the points where your staff would otherwise switch tools, re-key data or guess.

Because they share one sign-in, one layout and one accessibility standard, moving between them feels like moving between pages of a single application. That is what lets each app stay focused without your staff feeling the seams.

Three focused apps that strengthen each otherThree circles labelled SixDot BE, SixDot TM and SixDot KI, each with its own job. Arrows between them read: BE sends work orders to TM, TM returns status to BE, KI answers policy questions inside BE, and KI stands alone for all staff.SixDot BEruns the programSixDot TMtracks the requestsSixDot KIanswers the policywork orders out,status backpolicy answers,inside the recordEach app keeps its own job. None of them gets the others’ bloat.
Figure 3. Three apps, three jobs, two connections that make each one better.

5. ALL ON ONE PLATFORM

The SixDot platform carries everything underneath

None of the apps carry their own security, hosting or monitoring. The platform does. Identity through Microsoft Entra ID, isolated data per agency, encryption, notifications by email and Teams, monitoring and audit, accessibility checks on every build, cross-app reporting and one support relationship are all shared services.

All of it runs on Microsoft Azure Government. When you add an app, it lands on that foundation on day one, and your IT team reviews the platform once rather than three products.

See the full list of shared services on the platform page.

The SixDot platform stackFour layers from top to bottom. Top: the three apps, SixDot BE, TM and KI. Second: a familiar shared user experience. Third: shared services: identity, security, data isolation, notifications, monitoring, accessibility checks on every build, reporting and support. Bottom: Microsoft Azure Government hosting.SixDot BESixDot TMSixDot KIOne familiar user experiencesame sign-in, same layout, same keyboard and screen reader behaviourShared servicesidentity, security, notifications, monitoring, reporting, accessibility checks per buildMicrosoft Azure GovernmentUS-only data residency, FedRAMP High infrastructureThe SixDot platform. Add an app and it lands on all of this.
Figure 4. Every app sits on the same experience, the same services and the same hosting.

NEXT STEP

Start with the app that solves your hardest problem

Most agencies begin with SixDot KI or SixDot BE. Tell us what your staff struggle with today and we will show you where it fits.

Get in contact
Explore the SixDot platform