Information system comprised of synchronized software application moduless with individual databases for implementing and changing business requirements to be automated

• US 20050033588A1
• Filed: 08/04/2003
• Published: 02/10/2005
• Est. Priority Date: 08/04/2003
• Status: Abandoned Application

• Current Assignee: I Now Technologies Incorporated
• Original Assignee: I Now Technologies Incorporated
• Inventors: Kaplan, Alan, Ruiz, Mario, Mejia, Victor
• Application Number:
  US10/633,959
• Publication Number:
  US 20050033588A1
• Time in Patent Office: Days
• US Class Current: 705/35
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

A method and apparatus for a fully integrated Information System (IS) with modules for each business activity, that can be used individually or grouped in a suite of modules, each module containing its own individual database, and connected via a middleware-like integration device, or Enterprise Service Bus, for network based data synchronization and communications, that connect the modules to each other and to existing ERP, CRM, data warehouse and custom legacy systems. Each module therefore acts more efficiently since it is not burdened by the tasks of interfacing with the hardware platforms and operating systems, which are assigned to the programs in the integration server. These smaller and more flexible modules work together and automatically update all related applications, databases and users, when data is entered into one. The modules are quickly implemented as they are written from libraries of core functionality from existing programming code that were developed for implementing similar business requirements, added to custom code, thus quickly and inexpensively implementing precise individual business requirements, fully integrated with the existing legacy IS environment. The invention is considered a next generation ERP technology that can easily adapt to new requirements as market places and best practices dictate. It is called SAIDware and it is especially suited for the migration of legacy systems to more modern platforms, facilitating their step-by-step replacement as time and budgets allow.

Claims

1. A method of establishing an information system comprised of;

a. one, or a plurality of self-contained stand-alone modules,

b. a central data integration and messaging server, to allow said modules to communicate with each other, and to existing applications and databases, and

c. a series of connecting devices for each of said modules, as well as other applications and databases, interfacing them via a network (LAN, WAN, Internet, etc.) to a central data integration and messaging server.

2. A method of establishing a system according to claim 1, wherein each of said modules performs a specific activity, said activity selected from the group consisting of (but not limited to) business activities including accounting, budgeting, engineering, inventory, manufacturing, purchasing, receiving and sales, etc.

3. A method of establishing a system according to claim 1, wherein each of said modules that performs a specific activity, has its own individual database.

4. A method of establishing a system according to claim 1, that has multiple modules that when synchronized, fulfill each business requirement in a highly efficient and effective manner, thus simplifying the construction of software applications and the entire system, giving it cost, performance and efficiency advantages over designs with clustered applications and central databases.

5. A method of establishing a system according to claim 1, that has multiple modules that when synchronized, fulfill each business requirement in a way that allows for independent activity and highly complex combined functionality between the modules, without the need to make larger software applications that would become more and more complex, larger and unwieldy.

6. A method of establishing a system according to claim 1, that has multiple modules that when synchronized, fulfill each business requirement in a way that allows for the setting up of user changeable parameters that can affect the business events, processes, rules and workflow.

7. A method of establishing a system according to claim 1, wherein each of said modules is interconnected by a synchronization and communication device integrating information as an inherent part of its functionality, architecture and design.

8. A method of establishing a system according to claim 1, for network based (LAN, WAN, Internet, etc.) data transfer and messaging, updating each related module, database and user, as well as to existing applications and databases.

9. A method of establishing a system according to claim 1, wherein each of said modules is interconnected by a connecting device for the purpose of extracting and inserting data and messages to be communicated.

10. A method of establishing a system according to claim 1, wherein each of said modules is interconnected by a connecting device directly exchanging information together, in a hub and spoke manner, without the need for a central database that stores and retrieves data in between system components, including said modules and users, as well as to existing applications and databases.

11. A method of establishing a system according to claim 1 that provides a means for synchronizing and communicating information between system components, including said modules and users, as well as to existing applications and databases, in both a near-real time manner and a two-way extract, transform and load (ETL) batch manner.

13. The method of establishing an ERP or other type of information system according to claim 3, with less code inside each module, providing a means for said modules to be more easily developed, tested, implemented, maintained, modified (for future requirements) and migrated to new platforms.

14. The method of establishing an ERP system according to claim 3, further comprising a library of core functionality, with custom code to implement exact business requirements, interfaces and data input screens of a customer, said codes being a means to implement industry best practices into a customer'"'"'s business, reducing, or eliminating the need for a gap assessment.

15. The method of establishing an ERP system according to claim 3, further comprising a library of core functionality, with custom code to implement exact business requirements, including the events, processes, rules, interfaces and data input screens of a customer, said combination of codes being a means to implement industry best practices into a customer'"'"'s business, reducing, or eliminating the need for a parameter setting layer of interfacing code that attempts to customize pre-made applications.

16. The method of establishing custom developed system according to claim 3, further comprising a library of core functionality, with custom code to implement exact business requirements, including the events, processes, rules, interfaces and data input screens of a customer, said combination of codes being a means to implement exact functional requirements of the users, instead of trying to make custom applications from scratch or by means of reusable code, objects and services, that do not have the advantages of being developed in a development environment comprised of synchronized simplified modules with individual databases.

17. The method of establishing a system according to claim 1, further comprising a variable parameter settings feature that consists of a layer of code which adjusts the user'"'"'s workflow and processes to pre-approved and pre-made sets of variations, enabling users who wish to change the way they do their work, to change the system at a functional level themselves, without the need for programmers.

18. The method of establishing a system according to claim 1, further comprising a secondary near-real time data path as an inherent part of its design, to improve data sharing and increase database availability by reducing the need for batch processing, across a mixed legacy environment.

19. The method of establishing a system according to claim 1, that has a less invasive means of implementation, starting with data integration purposes primarily, and secondarily providing business functionality.

20. The method of establishing a system according to claim 1, which has a low risk of implementation, often starting with low cost or no cost proofs of concepts.

21. The method of establishing a system according to claim 1, which has a means of being more sensitive to the existing IT culture and political events in an organization, that effect the outcome of any software implementation project.

22. The method of establishing a system according to claim 1, which has a means of reorganizing existing code that has a conventional application with a central database and/or traditional ERP design, into modules for each business activity, that can be used individually or grouped in a suite of modules, each module containing its own individual database, and connected via a middleware-like integration device, or Enterprise Service Bus, for network based data synchronization and communications, that connect the modules to each other and to existing ERP, CRM, data warehouse and custom legacy systems.

23. The method of establishing a system according to claim 1, which has a means of reorganizing code that has been rewritten or translated from other programming languages into modules for each business activity, that can be used individually or grouped in a suite of modules, each module containing its own individual database, and connected via a middleware-like integration device, or Enterprise Service Bus, for network based data synchronization and communications, that connect the modules to each other and to existing ERP, CRM, data warehouse and custom legacy systems.

24. The method of establishing a system according to claim 1, that has data integration via a synchronization and communications device as a part of its inherent design, and is, as a result, fully supportive of Enterprise Application Integration (EAI), Enterprise Information Integration (EII), and other standards and organizations that encourage the sharing of information.

25. The method of establishing a system according to claim 1, that has data quality inherent in its design, whereby integrated data is generally of a higher quality (with established data rules and better conformity of the data to their rules) than stand alone data.

26. The method of establishing a system according to claim 1, that has data quality and data integration inherent in its design, whereby said data is generally more supportive of business intelligence (i.e. better function data warehouse, customer data repositories, etc.) than data found in stand alone applications and independent databases.

12. The method of establishing any ERP or custom designed system with a built-in middleware-like integration server, providing a means for synchronization and communications with existing legacy applications, databases and users to connect and integrate them as an integral (and integrated) part of its design, without the need for external and/or additional middleware or Enterprise Service Bus type devices.