Get systems working with each other

Back in the day, an organization might have had a single computer with a single piece of software. Fast forward to now where organizations have on average 110 different SaaS offerings in use – and that’s just SaaS; adding in on prem apps, and systems that your suppliers and customers ask you to use, and who knows what the figure is.

...
Christian Hampshire
  • LinkedIn
  • Facebook
  • Twitter
...

Back in the day, an organization might have had a single computer with a single piece of software. Fast forward to now where organizations have on average 110 different SaaS offerings in use – and that’s just SaaS; adding in on prem apps, and systems that your suppliers and customers ask you to use, and who knows what the figure is.

The number of systems means anything is possible but its not efficient. Data is stored on so many systems and when you need to make an update, you need to make that update everywhere.

Let’s look at this a different way:

As Sysflows is applicable to every industry, we need some common ground. We’ll use a school as an example organization as concepts are broadly understood.

A school typically has a Learning Management System (such as Canvas or Moodle), the IT network systems such as Active Directory/Azure and then there’s typically Excursion/Camping systems, systems for Anti-Bullying, Harassment, Systems for Curriculum, evacuation & alerting systems, government applications and so much more.

Now let’s say a parent changes their phone number. Simple yeah? Just update it in the ‘Learning Management System’? or would it be in Active Directory? Oh, maybe in the myriad of government application? Or is it Jane’s master spreadsheet that needs updating? The answer is probably different depending on who you ask because really it needs to be updated almost everywhere. Did anyone think about the evacuation and alerting system that sends out automated SMS alerts though?

The problem

  1. Multiple staff involved doing mundane record keeping
  2. Mistakes are easy to make, and systems quickly become untrustworthy
  3. Data integrity is low because people have a different way of entering details (for example: a plus in front of a phone number or St instead of Street)
  4. No “link” between data so current or future reporting isn’t possible

The solution

Using Sysflows, you could setup a form for “Change of details”. When someone updates details, it automatically updates all the different systems using a combination of inbuilt connectors, SQL queries, string manipulation, and API calls.