Catalog Lifecycle Management, Enterprise Software - Sell Project

SIGNIFICANT PRICE REDUCTION!!! MAKE AN OFFER! I know this description is long, but this is a major project that requires a lot of explanation. After reading the description thoroughly, feel free to contact me with any additional questions - seriously interested parties only, please. What is the problem? As companies grow, so do the data they generate. Unfortunately, as that data grows larger it makes it more and more difficult for companies to maintain. In most cases, the databases that store said data get copied off to multiple locations for offline analytics, merging with other systems, audit purposes, and so on. However, as that data gets replicated to other locations, users tend to access, modify, and work off the duplicate data instead of the data in its original form and location. This leaves companies with multiple copies of inconsistent data which can lead to products being incorrectly manufactured, processes following obsolete policies, and other mismatched and unwanted results. That is where MDM (Master Data Management) comes in. The purpose of MDM is to provide a single location (the "golden record" or "single source of the truth") that all applications and users can reference for making sure data is accurate and consistent. Instead of modifying the same data in multiple locations, users are expected to make changes to their data only in the MDM system, called the "Master Data". If changes need to propagate out to other systems, it will be done through automation, but that replicated data is still expected to not be modified. If it does need to be modified, users are required to go back and modify it in the MDM system so that it remains consistent and accurate across the company. What is the solution? Catalog Lifecycle Management (CLM) provides users with a single system for capturing and maintaining company data across the enterprise. This data can consist of anything from facility data (i.e., warehouses, machines, other assets, etc) to customer data, employee data, and so on. The idea is to provide a central repository for enterprise level data. CLM is an enterprise Master Data Management web application that can be sold to and deployed on-premise. With a little work, CLM can be updated to be multi-tenant so that it can be deployed to the cloud and sold/licensed as a SaaS (Software-as-a-Service) solution. It provides a simple-to-use UI (User Interface) that requires very little IT involvement. Using the Catalog Manager, business users can create new repositories (aka database tables) that will capture MDM data. Business users have complete control over: The entire web UI is end-user customizable, meaning they can move, collapse, close, and confgure panels on the Dashboard, and even change the entire look (color scheme) of the web UI via a simple drop down menu in the top-right corner of the UI. Additional themes can also be created for things such as favorite sports teams, kids' school colors, etc... What makes it work? CLM is a web app that runs on Apache Tomcat (or other web container) and uses MySQL (or other RDBMS) for storing Master Data. The backend is written in Java using Hibernate and the Spring Framework while the frontend is written purely in Javascript using ExtJS. In-app reports are provided by Crystal Reports (I used CR for Eclipse for the development). As managers (i.e., business users) create new repositories, corresponding tables are auto generated in the database. The app then creates a dynamic screen/page for users to enter data into these tables/repositories. As users enter data into those dynamic pages, the data flows thru the app's built-in workflow and business rules engines before getting persisted into the database. Workflows and business rules are also user created and configurable. When providing data using the dynamically generated page, data must conform to the rules as set forth by the manager during the Catalog creation process (i.e., required fields must be provided, date fields only accept dates, numerical fields only accept numbers, etc...). Data in CLM can be accessed via the frontend web UI, dynamic webservices, printed, exported as PDF, and saved to file using integrated Crystal Reports. Every action performed in the app is recorded for historical purposes and a complete audit trail is available via the left-side menu. There is also a built-in session tracker for monitoring the app's usage. Basically, everything in the app is end-user customizable and configurable - everything from the menus to the repositories to the reports to the overall look and feel of the app itself. How does it make money? CLM is an enterprise application and is intended to be sold/licensed as such. A recent assessment of the app calculates it can be licensed as-is for $75,000 - $100,000 USD on-premise for 2 cores. Additional cores can be licensed for $10,000 - $15,000 USD per core. An additional 20% annual maintenance fee can also be charged on an on-going basis for customers of this...