Change Process

2CLIX knows that your security and privacy are important and cares deeply about them.

SYSTEM CHANGE PROCEDURE

System changes and auxiliary applications must be formally requested in writing, and the approval process for this documentation is the responsibility of Administration. The change request must present the costs, benefits, risks and justification for the use of the new system or application.

Once approved, Administration must record the approval and notify the Projects team so that the installation process and training for the teams that will start using the new system can begin.

CHANGE ADOPTION AND MONITORING PROCESS

The Projects team must prepare an implementation plan for the change and allocate the resources required for installation and initial use of the new system.

Once this phase is completed, the team must begin training the teams that will use the new application to perform their duties. During this adaptation phase, the Projects team must start revoking user access to the previous system, as well as uninstalling the replaced application from workstations, if necessary.

After training, the Projects team must follow up with the other teams to monitor usage and feedback on the new platform, as well as measure the impact on the productivity of the affected teams.

The adaptation process must not exceed two months; the third month after the change is dedicated to a critical review by Administration of the processes affected by the change.

CHANGE RESTRICTIONS AND REQUIREMENTS

For a change to be approved, the new system must deliver clear and measurable improvements, in addition to meeting the Information Systems security requirements, providing a level of security that is equal to or greater than that of the previous system.

The cost must reflect the productivity gains, and its use must be aligned with the estimated benefits.

The risks presented in the request must be validated by the Security team, as well as compliance with the minimum security requirements and the specific requirements related to the role the new system will perform.

Finally, a change must be in accordance with contracts signed with clients. Therefore, if any contract contains restrictions regarding certain software or changes, this must also be taken into consideration in the change approval process.