Connecting existing systems
Established workflows and records
A business may already have useful software and established processes. We identify what to retain, which information needs to connect and where the system needs to change.
The system’s starting point
The starting point is the company’s current operating model. Existing systems, data and processes determine the work required.
Processes to develop
Processes to define or rework
When a process depends on unwritten knowledge or needs redesign, we work with the people who perform it. That work defines the process before we build it into the system.
Defining the required change
We review the operating need, the information available and the way the team works. This establishes the system changes and any process work required before we propose an implementation.
Data and business judgement
We design reporting around the decisions the business needs to make. Each measure has a defined meaning and source, so the business can examine what its numbers represent.
We connect performance measures with the work and decisions behind them. This lets the business compare plans with outcomes and examine how the work developed.
Over time, that history helps the business recognise patterns and anticipate constraints. It provides evidence for deciding what to change and where to focus next.
Scope and investment
Each implementation is a bespoke project. We define the system work and any process development required before confirming the scope and investment.
System implementation
From $5,000 AUD plus GST
A bespoke operating system for the business. The implementation connects the agreed information, workflows and reporting. Testing, training and handover prepare the team to use and maintain it.
Contact SOL-
Operational audit and Implementation Plan
-
We assess the affected systems and workflows, then document what will be built, connected or migrated. You approve the Implementation Plan before configuration begins.
-
-
Connected operating structure
-
We organise the business’s information around the agreed workflows and reporting needs. The system keeps records connected to the work and decisions they describe.
-
-
Data migration and connections
-
Where agreed, we migrate the named information and connect the relevant systems. We define the information each connection carries and the behaviour it supports.
-
-
Automation and AI
-
Automations follow the agreed workflow rules. Where AI is included, we define its task, source information and human review.
-
-
Testing and client review
-
We test the working system against the approved plan before client review. The review checks the agreed workflows and system behaviour, with corrections completed before training and go-live.
-
-
Training, handover and initial support
-
Training covers the agreed users and workflows, with operating guidance and access confirmed at handover. Initial support runs for 30 calendar days from go-live. It includes corrections, reasonable usage guidance and up to three hours of minor configuration adjustments.
-
Process development
Quoted to scope
Where processes need to be defined or reworked. We establish how the affected work should progress, then turn that method into procedures and requirements for the system.
Contact SOL-
Process review and team input
-
We work with the people who perform the affected processes. Their knowledge establishes the stages, decisions and information the workflow needs.
-
-
Workflow design and decision rules
-
We define or redesign the agreed process, including its starting point, stages and handoffs. Decision rules establish how the work should progress.
-
-
Procedures and operating guidance
-
We document the agreed method in the procedures or checklists named in the scope. The team has a practical reference for carrying out the work.
-
-
System requirements
-
The documented process sets out what the system needs to support and record. Those requirements guide the configuration and automation work agreed for implementation.
-
What determines the investment
The required behaviour determines the build. Individual workflows can involve different users, decision rules and connections. We define those relationships and reporting needs before estimating the implementation.
Data needs its own assessment. We identify the records to move, their condition and the preparation required. Mapping and agreed cleaning are considered alongside the connections between systems.
The rollout is part of the scope. We agree the users, training, operating guidance and single or staged launch. Timely access, accurate information and participation from the relevant team shape the delivery estimate.
Our Process
We go in-depth to understand your goals
// STEP 01
Understand the operation
We audit the systems, workflows and data already in use against the agreed business requirements. The resulting implementation plan defines the changes, connections and migration needed. You review and approve the plan before we build.
// STEP 02
Build and connect
We configure the agreed operating structure and workflows, with the reporting, automations and integrations needed to support them. Where migration is included, we bring the agreed information into the system and check it.
// STEP 03
Test and review
We test the completed system against the approved plan before presenting it for client review. The review checks its behaviour and the way the team will use it, with corrections completed before approval.
// STEP 04
Train and hand over
Training and operating guidance cover daily use, administration and reporting. We confirm access and the agreed rollout, then provide handover and initial support as the team begins using the system.
How the business operates
The business’s goals and operating needs determine what we build. We examine how work moves through the company, the information it depends on and the decisions the system needs to support.
We build bespoke systems using SOL Systems™, developed through our own studio’s operations. We connect records with the processes they inform, so information carries through as work progresses.
The business controls how its information is captured, maintained and used.
-
That follows the requirements. We establish which tools to retain, connect, migrate or replace, and how information needs to move between them. The proposal and implementation plan record the agreed approach.
-
-
-
Adapting the system
As the business’s needs change, new workflows can build on the information and connections already in place. We design each addition around how it will work with the rest of the system.
We design automations around how work should progress, reducing repeated handling as information moves between connected processes. The business retains control over the rules and information those actions use.
Where AI forms part of the system, it draws on the business’s own knowledge and operating information. We define the task it should support and the information it can use, with human review of its output.
Discuss your business systems
The starting point is the business’s goals and the work its systems need to support.
Contact SOLWe review the current systems, information and processes with you, then recommend the implementation and process work required. The proposal sets out the scope, investment and delivery estimate.
