An IT system is the tip of the iceberg of optimization processes taking place in a company. Therefore a key stage before making the decision about implementing an IT system is to perform an analysis of the processes taking place in the company.

Our consultants, cooperating with representatives of the Client’s company, will map the processes taking place in the area of key operations (present state). Afterwards, in the course of the advisory process, responding to the diagnosed challenges of the organization, they will develop an optimized map of processes (future state) which will constitute the basis for implementing changes in the organization.


Thanks to the many years of experience of our experts in development of logistics systems, responding to the challenges imposed by the e-commerce market, our Clients can be sure that the recommended changes in processes and the following IT system implementation will give the optimum business effect. On the basis of thus prepared documentation it is possible to develop functional requirements, and then a technical specification for the IT system contractor.

Beyond the vision

Every design begins with a vision. In the course of workshop meetings with our Client we refine their expectations and ideas regarding the system functionality, forging them into precise requirements. The key result of realization expected by the Client is decomposed into factors:


  • We define the factors that will correspond to proper realization of the goal, and specify their co-dependencies
  • We map and optimize processes
  • We design functionalities on the basis of a set of defined activities corresponding to processes
  • We design user interfaces and management panels envisaged in the solution (scope of available data, presentation method, filtering methods)
  • We design workflow for every user role envisaged in a given system


The solution documentation and the specific action plan are created in stages, in close cooperation with the Client. Each successive stage is connected with a meeting during which we communicate the status to the Client and present our suggestions and recommendations.

The result of the workshop works at the design stage is a detailed documentation:


  • functional specification – defining in every detail which processes will be supported by the designed solution, and how. This documentation is expressed in business language. It includes detailed maps of processes, illustrating, which activities will be performed in the course of the process, and in what sequence
  • technical specification – a documentation for programmers. It precisely describes the method of operation of the implemented solution and all relations between the system elements. It is executed according to standards ensuring its complete legibility to every programmer who will want to make changes in the system in the future
  • schedule – specifying the exact duration of the entire realization, as well as of its individual sections.


Development Perspective

The solution design is realized so as it does not constitute a closed element of an IT system. Wherever during the design specification we envisage further design development, we state it in the documentation. Such approach guarantees to our Client the exact knowledge of development of the implemented system.

Development works started after the stage of business analysis (see consulting) and designing, which results in a complete functional and technical documentation of the solution, proceed in stages, precisely according to a specific schedule. The advances of realization are communicated to the Client in specific cycles. Every schedule envisages the dates on which successive stages will be delivered to the Client for partial acceptance.

Every realization we undertake is led by a dedicated Project Manager who represents us in contacts with the Client. The Project Manager is responsible for effective communication on the line with the Client, proper flow of information, and is personally responsible for timely realization of actions in accordance with the schedule and for removing obstacles on the way to the goal. The Project Manager gets to know perfectly the realized implementation, and leads the project from the start to the end, which ensures the continuity of realization.

Customized Design Method

We choose proper design methodology for each realization. It depends on the complexity of the implementation, its duration, and Client’s preferences. The choice of methodology affects the frequency of meetings and the method of communicating the status of realization.

Every project is different, therefore there is no one single scheme of conduct. Basing on the experience, we choose such a method of operation that will maximize its efficiency and lead to the expected goal in the shortest possible time.

Continuous Technical Support

Every implementation is preceded by detailed tests in an environment which imitates/replicates the environment of everyday functioning of the system. Tests are performed using real data, often on a group selected on the basis of data about the cross-section of the target group of real clients (although this is decided by the Client).
Within the framework of cooperation in the period of time after implementation, we guarantee continuous technical service responding to requests from the Client in a very short time. Functioning of the implemented solution is monitored by us in order to eliminate the possible exceptions from the tested usage scenarios.


Our maintenance services are provided according to proven, effective procedures created on the basis of good ITIL practices. The maintenance services we provide include:


  • Continuous monitoring of processes critical for system functioning (in accordance with Client’s requirements or procedure). Current inspection of the system efficiency is supported by:
    • Early warning system (automatic notifications for critical values of specific parameters in the system)
    • Dedicated team of technicians, ready to intervene in the event of signaled irregularities
  • Providing safety for strategic data collected and processed by the system
  • Management of requests from the business owner concerning:
    • Incidents
    • Events
    • Problems
  • Management of requests concerning realization of functional changes:
    • Receiving a request
    • Refinement
    • Feasibility/time consumption analysis
    • Keeping a formal documentation
  • Management of user access rights
  • Management of communication on the line: Client technical support

All the above processes are realized on the basis of detailed procedures proven in practice.

General maintenance procedure specifies:

  • Platform maintenance model
  • System structure description, emphasizing the critical business processes
  • Maintenance team make-up and member role assignment
  • Other procedures in force within the framework of system maintenance

Data backup

Backup copy creation procedure defines:


  • Scope of data subject to backup (process areas, data categories)
  • Method of making, testing, and restoring backup copies: frequency of performing, method of recording
  • Backup copy storage method
  • Backup copy making schedule
  • Rules for processing the requests for reinstating/restoring data from copies
  • Make-up of the team responsible for procedure realization and role assignment of its members

Monitoring procedure

Monitoring procedure specifies:


  • methods of monitoring (control dashboards, automatic notifications)
  • system elements/processes subject to monitoring and recording in system logs
  • schedule of all monitoring activities
  • methods of archiving, storing, and deleting the system logs
  • monitoring team make-up – role assignment and scope of responsibility
  • procedure for granting the access to control panels
  • procedures of operation in the event of failure/malfunction of monitored functions,
  • rules for communicating irregularities (communication chain/escalation path)

Detailed conditions for request management are determined individually and apply to:


  • categorization of requests (priority)
  • guaranteed request response time
  • maximum time for finding a provisional solution (in order to maintain the system efficiency)
  • maximum time for solving the reported problem