Hopefully the title is worded accurately, here goes.
I have built a data management framework for my client. Gather data, organize, save to database, provide web portal so they can monitor the field, and notification system. The client is looking to add workorder management to the system. Automated workorder generation would be triggered by unit shutdown (alarm condition) and the preventative maintenance schedule. The system would also include inventory management. Workorders would be manually added as well.
The client sent out the work scope last week. They had mentioned that the spouse of one of their employees could contribute to this project. We all met this morning and the spouse spoke of her idea of how to implement the system.
Her system would involve building a java application that would be installed on each user's machine. Other option is a web interface written in java.
The existing application is a web-based interface built with Python & Flask. MySQL is the database backend.
My concern is that we would both be working in completely different technological ecosystems, thereby providing the client essentially two completely disparate systems that logically should exist as one entity.
I would like to provide the WO management as a section of our existing web application. For various reasons, it is intimately tied to the underlying database. Some refactoring of the schema is in order, but extending the existing application to provide this functionality seems like the best choice for a few reasons*.
Obviously, I am trying to approach this pragmatically. I don't want to give the impression that I am pushing my offerings selfishly. I really don't want them to deal with two systems that perform the work of one. I see that as the source of headaches, costs, delays, more headaches.
The spouse already has a full time employment commitment. I have already told the client that I am available to devote primary effort to this project. I don't think that this is a case of "lets throw some work to X as a favor". I see the client as choosing what is best for their needs.
ADVANTAGES OF 1 vs 2 SYSTEMS: 1) The system is one system instead of two.
2) It is an extension of the existing application.
3) consistency on the UI
4) web application does not require install. The user login system on the website is already in place. HTML5's WebStorage allows offline functionality to be incorporated.
5) current system already interacts with the database.
6) Listing a site's current workorders would be easier, not requiring back and forth communication.
TL;DR How to pragmatically show that incorporating a layer of isolated technology to solve a problem that could be solved by an extension of the client's existing technology is not ideal?
My plan is to formalize my proposal from a tech perspective and share it with all parties involved, and hope that it speaks for itself.
What do you think?