Introduction
TaaS, Technology as a Service. But what is that exactly? This is a service to the customer where the solution is developed with a team within Nalys itself with a Nalys team. This team can exists out of 1 or more Nalys engineers/managers/… working on the best possible solution for the customer requests.
There are 3 different TaaS projects that will be covered by this paper: Proof of Concepts [PoC], Demos and Complete Projects.
TaaS types
Proof of concept
In a proof of concept we provide the interested customer with a proposition of architecture. This proposition can be backed by a small proof of concept which proves that the proposed solution is possible to deliver.
The goal of a proof of concept is to get projects at customers. This can be achieved by investing just a small amount of resources and this has thus a relative small cost.
For a customer the advantage is that at the end of the PoC, they have a clearer understanding of the feasibility of a project, as well as the resources required to bring it to life.
Demo
A demo differs from a PoC in which a demo is a more extended implementation than a PoC. Typically a demo is ran over a longer time frame than a PoC.
The first goal of a demo is not to implement a complete project, but implement a part of the functionality as it should be. A second goal is to prove to a customer that we are capable of providing the complete solution.
Demos can be provided on different ways, on sprint basis, feature, … . This has as a consequence that there are deliverables to the customer.
Complete projects
When a customer has a complex technical demand, and it doesn’t want to develop itself, it’s also an option to develop the complete project for the customer from start to finish.
This could be a result of a positive evaluation after a proof of concept or a demo.
Examples
- Modernise CI infrastructure / Cloud solutions
- Setup of build systems
- Automated test processes in production environment
- Functional testing
- End Of Line testing
- Custom applications