As part of a current project involving the modification of an existing software installation, both technical and organizational questions have arisen. While the original assignment calls for the migration of a multi-user installation to a single-user installation, an alternative approach has been proposed: implementing a server/client structure with only one active workstation. On the hand, this approach offers the customer several advantages for future expansions. At the same time, however, it raises questions regarding the proper execution of the assignment, documentation requirements, and potential implications related to billing and employment responsibilities.
Main
The customer currently uses the affected software, which can be operated either as a standalone installation or as a multi-user installation within a server/client architecture. Licensing and pricing are based on the type of installation being used.
The customer currently has a multi-user installation and would like to operate the solution on a single device in the future. Despite reducing the setup to one workstation, the existing two licenses are to remain in place, as there should be an option to reconnect an additional client in the future if needed.
The commissioned scope of work includes converting the existing multi-user installation into a single-user installation so that the application is operated entirely on one device.
During implementation, the employee is requested not to perform the installation strictly as a standalone system, but instead to configure the existing server as a client as well. As a result, a server/client architecture would technically remain in place, even though only one workstation would initially be used.
This approach offers several advantages for the customer. The technical foundation for connecting an additional client at a later date would already be in place, eliminating the need for another restructuring of the installation should future expansion become necessary. Instead, only an additional client would need to be connected. Furthermore, this could improve customer satisfaction, as adding a client at a later stage is generally less expensive and requires significantly less effort. The intention is to document this approach accordingly.
The open question is whether implementing the project in this manner involves any risks. In particular, there is concern that other departments, such as Inside Sales or Sales, could identify a discrepancy during billing between the commissioned single-user conversion and the actual server/client configuration that was implemented. In addition, there is uncertainty due to an employment contract provision under which damages caused by an employee may, under certain circumstances, be charged to that employee. Therefore, before deviating from the original assignment, it should be verified that this approach has been approved and that it can be clearly justified and tracked from a billing perspective.
Conclusion
The customer agent carried out the work in accordance with the professional requirements and instructions provided by the team leader. All work performed is documented completely for aim for good transparently.
The executing employee explicitly documented that the decision to configure the system in the described manner, particularly with regard to retaining the server/client architecture while operating with only one active workstation, was made at the request and according to the instructions of the team leader.
The documentation serves to ensure transparent traceability of the decision made and to clearly attribute the professional directive within the scope of the assignment.
0 comments