SystemsDNA

What is systemsDNA platform?

Enabling you to transform a business which uses disparate legacy systems to a unified core plugging into still valuable retained systems. Evolution version iteration is an order of magnitude faster than traditional software development. Breathing new life into legacy software with a continously evolving solution set which keeps your nose ahead of the competition

Platform components

The SystemsDNA Platform consists of the following five components:

Configuration Studio

To manage and maintain a lowcode system means the capability to manage users, access rights, different logins, home pages menus, inboxes, searches, KPIs, reports, email templates, document templates and so on

The configuration studio gives each organisation the capability to do these tasks simply and quickly

Design Studio

Sometimes and organisation requires specific aspects of their version of an application to work in a particular way. Sometimes they need to add in their own object types, or UI features, or business flow data acquisition and triggered actions and so on. These are more complex, but still not classed as core application development. Trained users with a similar capability to Excel level technical skill can manage this configuration through the design studio

Developer Studio

Core application development without code is implemented in the Developer Studio. Whether this is our team or your team or sometimes both, the Developer Studio facilitates this capability

Cyclops

It is important to know that your application is running smoothly. What activities are going on inside the application, what security threats picked up, what volume loading and performance levels it is experiencing. This and other run-monitoring activities are managed in the Cyclops (.one eye)

.one application core

Every .one application which runs does so through the run time application core of .one. This is installed and run on every .one server

Services

Systems Review

SystemsDNA will review existing systems and how they are connected along with what they are intended to deliver. This will include a code review where necessary as well as possible off-the-shelf pre-existing solution options

Based on these findings we present a number of options available with pros and cons of each as well as recommendations

Prototyping/Proof of concept

SystemsDNA will give the option where applicable to build a prototype system. The purpose of this is not necessarily to replace or implement immediately, more as an understanding of what a next-generation system would look like, how it would work, tactile and involving all participants. In a sense it can be thought of a wireframe model that really works. The possible outcomes are:

Hold - reviewing what has been built and whether it meets requirements, whether it should be re-coded in a standard code set approved by the business
Iterate - take the feedback from participants and evolve the solution to the next level
Implement - take what has been built and implement live in the business

Applications

SystemsDNA has a number of pre-existing solutions in a range of sectors. These can be implemented 'as is' or altered to more exactly fit an intended use case

Legacy Transformation

SystemsDNA will review with you pre-existing valuable legacy systems underpinning the business and understand what is required to bring them into the next generation business/systems model. Technically, what API connections are available and what may be needed, how the UI may change, and how the SystemsDNA .one technology can be used to extend and modernise existing functionality

New Application build

For some businesses which are growing fast or for some which want to transform their pre-existing systems through replacement a new enterprise application infrastructure is required. SystemsDNA will review what is currently in place and future business trajectory and propose a new systems design. This will follow the steps of applicabiity of the .one technology to the systems environment, systems design through requirements, functional and technical specifications, prototyping iterations, development, testing, implementation

Why SystemsDNA

What's different about SystemsDNA?

Modernise existing legacy

The reason old systems are still in place is because they are valuable. They have a value to the business which underpins and supports it and swapping them out can be very risky and potentially damaging. That's why we don't want to do that. Instead, what we want to do is wrap these applications in a shell as far as is possible and connect the shell to the outside world and extend it. The .one technology provides the shell and connections and enables these systems to be laterally extended

Large scale, complex enterprise level applications

Business units often empower themselves with tools available to them which gradually evolve into complex systems. Empower your business with tools they can use which are built for purpose. Get the foundations right and complex applications will stand the test of time

With SystemsDNA we believe in putting the appropriate tools into the hands of business users, making it possible for business users to control and drive their own systems

Future proof your business

When new technologies evolve, it's important to be able to access these early through a known mechanism and without necessarily being expert in how the technology works at a low level. Being expert in how to apply these technologies and being enabled to apply them is key

With SystemsDNA, your applications are made independent of technology, and all you need to do is maintain a digital blueprint. This means that applications never need to be redeveloped. With SystemsDNA, you are guaranteed support for new technology and will be able to fully focus on functional development

Rapid iteration

Software which is not evolving with a business is legacy. However valuable this may be, it is better to keep software infrastructure adapting in parallel with the business it serves

With SystemsDNA we implement multiple layers of adaption simultaneously. Some elements of a system can be changed live (production) or pre-live. Some need a deeper level of test and release but still within days, and some need core version design at a low level and this happens in weeks

Business control

We use our own team to implement core systems design and build. We use our customer's teams to take control of that application, whether a pre-existing application altered to fit, or a brand new design and build. Initially customers usually manage only certain aspects of the configuration and tweaking of an application. But in time they are more likely to do increasing amounts of configuration as they learn the capabilities of what can be done. By this time, the customer fully controls their own system

Rapid Legacy Transformation