Installation, Implementation and Integration

Installation and implementation of the solution are the phases of operative and technical execution of everything conceived in the design phase and defined in the project plan. Installation refers to the physical setting up of the equipment and software on the place and in the form defined in the project plan. Implementation refers to making the equipment and software functional as foreseen by their characteristics and the project plan i.e. to making it do what it was meant to do. It is in this phase important to say that due to the general increase in IT industry maturity level, there are relatively few companies in which we would have a chance to build the IT system from scratch, which is why the term “integration” is becoming ever more popular. The term integration has more meanings, and here it is used in its both IT industry-relevant meanings:

  • Integration as the procedure of bringing various technologies together to make them fulfil requested functions in a harmonized way and
  • Integration as the incorporation of new systems or elements into existing IT systems and bringing together and expanding their functions.

All components in this phase are crucial for obtaining the desired result. Their implementation is thus strictly monitored. Monitoring is defined by project methodology, which covers all the phases up to the consignment of the finished functional solution. ECS uses PMI project methodology (adapted to IT to a certain extent) and partly MSF. In brief, it is necessary to take the following steps into account:

  • Implementation plan – defines deadlines and operative elements of the implementation. It is necessary to coordinate the resources of both the service provider and the customer, the representatives of whom must be project team members.
  • Testing – the extent to which testing is carried out and its scope guarantee that the solution will perform what it was designed to perform and how it was designed from the moment of consignment.
  • Delivery – the document in which both sides, the provider and the customer, state that the job was performed according to the contracted parameters, regarding both quantity and function.
  • Documentation of the performed job – the documentation customers can use throughout the lifespan of the solution in order to control its functions, but also as the basis for future changes and upgrades.
  • Operating manual – the documentation assisting in operating and monitoring of the system.