Computer systems are currently in wide use. In order to implement an instance of a computer system, the computer system is often modeled first and then configured.
By way of example, some computer systems include business systems, such as enterprise resource planning (ERP) systems, customer resource management (CRM) systems, line-of-business (LOB) systems, etc. In order to implement an instance of a business system, the business system is first often modeled by one or more analysts. The system is then often configured by one or more consultants. The analysts and consultants are often on two separate teams and information is often lost when the process moves from the analysis (or modeling) part of the process to the configuration (or implementation) part of the process. Also, this type of process has conventionally been almost entirely manual.
More specifically, the team of analysts often analyzes and models the business system before any configuration is done. The configuration consultant team then obtains information that represents the analysis and modeling, and configures a system based on that information. However, it is common for at least some of the modeling information generated by the team of analysts to be lost (or otherwise not carried forward) when the information is transferred for configuration.
Therefore, once the team of consultants configures the business system, it often does not entirely match the model that the analysts had created. This results in a relatively large amount of rework that is needed in order to make the configured system match the modeled system. Thus, because all of this is almost entirely manual, return on investment realized for the business system suffers.
The discussion above is merely provided for general background information and is not intended to be used as an aid in determining the scope of the claimed subject matter.
A configuration architecture automatically links the output of a business process modeler to a business system configuration tool. The output of the business process modeler is translated into a representation of a source business process that is used by the business system configuration tool to automatically generate configuration templates. A user can provide configuration information through the configuration templates. The configuration inputs are applied to an implementation of a business system to obtain a configured, working business system instance with the same functionality as the source business process.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.
Business data store 104 illustratively includes a variety of different business information and business records. For instance, in one embodiment, business data store 104 includes entities 116, forms 118, workflows/processes 120, and other information 122. Entities 116 are illustratively business records that identify business items. For example, a vendor entity identifies and represents a vendor; a product entity identifies and represents a product; a customer entity identifies and represents a customer; an opportunity entity identifies and represents a business opportunity, etc. Business applications 108 illustratively run workflows/processes 120 and operate on entities and other business data in business data store 104 to implement an instance of a business system. By way of example, it can be an instance of an ERP system, a CRM system, an LOB system, etc. However, for the sake of simplicity, it will be described herein as an instance of an ERP system. Forms 118 illustratively present user interface elements to user 110 so that the user can access and manipulate business applications 108 and other items in business system 100.
The business applications 108 illustratively include components or other types of applications that run on business system 100 to perform business operations, tasks, activities, workflows, etc. For instance, a business application 108 can be a general ledger application, an inventory application, a billing application, among others.
Processor 102 is illustratively a computer processor with associated memory and timing circuitry (not separately shown). It is illustratively a functional part of business system 100 and is activated by, and facilitates the functionally of, other applications and components or other items of business system 100.
User interface component 106 illustratively generates user interface displays, with corresponding user input mechanisms, for interaction by user 110. The user input mechanisms can take a wide variety of forms. For instance, they can be dropdown menus, icons, links, check boxes, text boxes, buttons, etc. In addition, the user input mechanisms can be actuated in a wide variety of different ways. Where the display device has a touch sensitive screen, the user input mechanism can be actuated using touch gestures. In addition, where the device used by user 110 or business system 100 includes a speech recognition system, then the user input mechanisms can be activated by voice commands. Also, the user input mechanisms can illustratively be actuated using a point and click device (such as a mouse or track ball), a keyboard, a keypad, a soft keyboard, a stylus, a thumbpad, or other methods.
In one embodiment, user 110 accesses business system 100 in order to perform business tasks, activities or operations or to generally manipulate business system 100 in order to conduct business. User 110 illustratively accesses business system 100 by logging onto it, and providing authentication information (such as a user name and password). Of course, other ways of accessing business system instance 100 can be used as well.
More specifically, configuration architecture 130 illustratively includes business process recorder 136, business process modeler 138, translator/synchronizer component 140, business system configuration tool 142 (that includes a template and question generation model 144), processor 146 and user interface component 148.
In another embodiment, user 134 (or another user) has already recorded a business process and stored it in a place that is accessible by business process modeler 138. In that embodiment, business process modeler 138 simply accesses the already-recorded business process 160. Accessing an already-recorded, stored source process is indicated by block 166. Of course, business process modeler 138 can obtain access to a recorded source business process in other ways as well, and this is indicated by block 168.
Once the user has selected the business process to be configured, user interface component 148 illustratively generates a user interface display with a user input mechanism that receives a user synchronization input to send the selected business process to a configuration tool. In response, user interface component 148 generates a user interface display such as display 204, shown in
In one embodiment, business process recorder 136 generates recorded business process 160 as a zip file which can be uploaded to a service instance of business process modeler 138. The zip file illustratively includes a variety of files (such as XML files) each corresponding to some activity (and hence each corresponding to a leaf node in the hierarchy 202). The files serve as the recorded business process 160 that is provided to business process modeler 138, and they illustratively include a description of tables that are to be configured in order to complete the business process implementation for the selected process.
Having received its input, business process modeler 138 generates a process diagram (or another representation) for the selected business process. This is indicated by block 170 in the flow diagram of
Table 1 shows one illustrative embodiment of a sample schema that embodies a representation 174 that is expected by business system configuration tool 142.
Once the representation 174 is sent to business system configuration tool 142, template and question generation model 144 is used to generate and output configuration templates, and a template hierarchy, corresponding to the selected business process. This is indicated by block 182 in
In one embodiment, the configuration templates include templates 186, subtemplates 188, functional areas 190, question groups 192 and questions 194. The configuration templates can also classify or group the questions that are applicable to various regions, industries, versions of the business system that generated the business process, etc. This is indicated by block 196 in
The XML in Table 1 automatically generates a template hierarchy which shows a number of different things. First, it identifies the parent node of the business process which generated it. It also identifies the subnode for which the configuration templates are generated, and all sub-templates and functional areas are based on a suitable heuristic. A list of questions and question groups are also automatically generated. In one embodiment, template and question generation model 144 reduces the number of questions to a minimal set and categorizes them for an easy answering experience. That is, it illustratively reduces the redundancy in the question and groups questions together so that the user can answer like questions in a group. This enhances the ability of the user to perform the process.
Once configuration templates 184 are generated, they can be provided to user 134 either directly, or through a user device such as user device 132. In the case where they are provided directly, UI component 148 generates user interface displays 154. However, where they are provided through user device 132, UI component 152 generates user input displays 154. Displays 154 present the templates, subtemplates, question groups and questions to user 134 so that user 134 can provide configuration inputs 250, through the templates, subtemplates, question groups and questions. Receiving user inputs through the configuration templates 184 is indicated by block 252 in the flow diagram of
Table 2 below shows one illustrative description that template and question generation model 144 can use to automatically generate configuration templates 184.
User 134 can then provide configuration inputs 250 (shown in
It will be noted that there can be many other question types as well. For instance, the question types can include relations, abstract types, etc.
It should be noted that a large percent of parameters may be duplicated across different functional areas in a category. Therefore, in one embodiment, a functional area is created with a name referred to as “Parameters: Name of the category”. This functional area contains all the parameters that are to be configured for the category. This avoids duplication and redundancy to expedite the process.
The questions and question groups, along with templates, subtemplates and functional areas are displayed for user 134 on UI displays 154. The user 134 provides configuration inputs 250 through the templates. This configuration information is then applied against an implementation of a business system to obtain a configured, working business system instance with the same functionality as the source business process. This is indicated by block 350 in
It can thus be seen that configuration architecture 130 provides an automated way of creating configuration templates 184 and questions based on an input which represents a business process. Translator/synchronizer 140 automatically links business process modeler 138 to business system configuration tool 142 by providing the representation 174 of the business process being configured, in a form that is acceptable to business system configuration tool 142. The representation 174 can be an XML input file (or another file or it can be distributed in a database management system that the configuration architecture has access to) that contains the configuration objects which are needed to configure the source business process. It includes details about tables, fields which require values, regions for which the configuration is applicable and definition of a template hierarchy. While business process modeler 138 and business system configuration tool 142 are two separate tools, they are linked together, or integrated, in a way that allows the user to choose a service instance of tool 142 to which the representation 174 is to be sent. Tool 142 uses metadata from representation 174 to automatically generate the complete configuration templates, including templates, subtemplates, question groups and questions. The templates can be classified for region, industry and applicable business system version. These steps can be repeated multiple times so that additional components (or business processes) can be configured as easily as the first ones, or updates can be made easily as well.
In addition, configuration tool 142 can be used to configure other things as well, and not just business processes. For instance, input 174 to tool 142 can include information that describes system settings from business system 100. Tool 142 can be used to configure system settings in the new business system instance using this same template-based approach.
The configuration tool 142 can be used in different environments as well. For instance, instead of business process modeler 138, a more abstract scenario modeler can be used to model a system at a higher abstraction level than a business process (such as at a factory level). As an example, all roles and their corresponding activities can be modeled, mapped, and synchronized to tool 142. Tool 142 can then be used to generate configuration templates for the modeled system. Those templates can then be used to configure an autonomous system with the same behavior as the modeled system.
The description is intended to include both public cloud computing and private cloud computing. Cloud computing (both public and private) provides substantially seamless pooling of resources, as well as a reduced need to manage and configure underlying hardware infrastructure.
A public cloud is managed by a vendor and typically supports multiple consumers using the same infrastructure. Also, a public cloud, as opposed to a private cloud, can free up the end users from managing the hardware. A private cloud may be managed by the organization itself and the infrastructure is typically not shared with other organizations. The organization still maintains the hardware to some extent, such as installations and repairs, etc.
In the embodiment shown in
In addition, the representation 174 used as input to configuration tool 142 can be obtained from an on-premise system or a cloud-based system. The configuration templates 184 can then be used to generate output 158 which can be imported into another cloud-based or on-premise system. Alternatively, the configuration templates 184 can be exported from architecture 130 and imported into another system (cloud-based or on-premise) where they are used for configuration.
It will also be noted that architecture 130, or portions of it, can be disposed on a wide variety of different devices. Some of those devices include servers, desktop computers, laptop computers, tablet computers, or other mobile devices, such as palm top computers, cell phones, smart phones, multimedia players, personal digital assistants, etc.
Under other embodiments, applications or systems are received on a removable Secure Digital (SD) card that is connected to a SD card interface 15. SD card interface 15 and communication links 13 communicate with a processor 17 (which can also embody processors 146 or 150 from
I/O components 23, in one embodiment, are provided to facilitate input and output operations. I/O components 23 for various embodiments of the device 16 can include input components such as buttons, touch sensors, multi-touch sensors, optical or video sensors, voice sensors, touch screens, proximity sensors, microphones, tilt sensors, and gravity switches and output components such as a display device, a speaker, and or a printer port. Other I/O components 23 can be used as well.
Clock 25 illustratively comprises a real time clock component that outputs a time and date. It can also, illustratively, provide timing functions for processor 17.
Location system 27 illustratively includes a component that outputs a current geographical location of device 16. This can include, for instance, a global positioning system (GPS) receiver, a LORAN system, a dead reckoning system, a cellular triangulation system, or other positioning system. It can also include, for example, mapping software or navigation software that generates desired maps, navigation routes and other geographic functions.
Memory 21 stores operating system 29, network settings 31, applications 33, application configuration settings 35, data store 37, communication drivers 39, and communication configuration settings 41. Memory 21 can include all types of tangible volatile and non-volatile computer-readable memory devices. It can also include computer storage media (described below). Memory 21 stores computer readable instructions that, when executed by processor 17, cause the processor to perform computer-implemented steps or functions according to the instructions. Similarly, device 16 can have a client business system 24 which can run various business applications or embody parts or all of business system 100 or architecture 130. Processor 17 can be activated by other components to facilitate their functionality as well.
Examples of the network settings 31 include things such as proxy information, Internet connection information, and mappings. Application configuration settings 35 include settings that tailor the application for a specific enterprise or user. Communication configuration settings 41 provide parameters for communicating with other computers and include items such as GPRS parameters, SMS parameters, connection user names and passwords.
Applications 33 can be applications that have previously been stored on the device 16 or applications that are installed during use, although these can be part of operating system 29, or hosted external to device 16, as well.
The mobile device of
Note that other forms of the devices 16 are possible.
Computer 810 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 810 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media is different from, and does not include, a modulated data signal or carrier wave. It includes hardware storage media including both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 810. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
The system memory 830 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 831 and random access memory (RAM) 832. A basic input/output system 833 (BIOS), containing the basic routines that help to transfer information between elements within computer 810, such as during start-up, is typically stored in ROM 831. RAM 832 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 820. By way of example, and not limitation,
The computer 810 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only,
Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.
The drives and their associated computer storage media discussed above and illustrated in
A user may enter commands and information into the computer 810 through input devices such as a keyboard 862, a microphone 863, and a pointing device 861, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 820 through a user input interface 860 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A visual display 891 or other type of display device is also connected to the system bus 821 via an interface, such as a video interface 890. In addition to the monitor, computers may also include other peripheral output devices such as speakers 897 and printer 896, which may be connected through an output peripheral interface 895.
The computer 810 is operated in a networked environment using logical connections to one or more remote computers, such as a remote computer 880. The remote computer 880 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 810. The logical connections depicted in
When used in a LAN networking environment, the computer 810 is connected to the LAN 871 through a network interface or adapter 870. When used in a WAN networking environment, the computer 810 typically includes a modem 872 or other means for establishing communications over the WAN 873, such as the Internet. The modem 872, which may be internal or external, may be connected to the system bus 821 via the user input interface 860, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 810, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
It should also be noted that the different embodiments described herein can be combined in different ways. That is, parts of one or more embodiments can be combined with parts of one or more other embodiments. All of this is contemplated herein.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
The present application is a continuation of and claims priority of U.S. patent application Ser. No. 14/157,756, filed Jan. 17, 2014, which is based on and claims the benefit of U.S. provisional patent application Ser. No. 61/840,247, filed Jun. 27, 2013, the content of which is hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
5774667 | Garvey | Jun 1998 | A |
6374224 | Horiguchi | Apr 2002 | B1 |
6892192 | Geddes | May 2005 | B1 |
20040015465 | Gill | Jan 2004 | A1 |
20040034857 | Mangino | Feb 2004 | A1 |
20040153368 | Freishtat | Aug 2004 | A1 |
20040230404 | Messmer | Nov 2004 | A1 |
20050091093 | Bhaskaran | Apr 2005 | A1 |
20050154742 | Roth | Jul 2005 | A1 |
20060149568 | Dreiling | Jul 2006 | A1 |
20060195781 | Jatavallabha | Aug 2006 | A1 |
20070093916 | Sanghvi | Apr 2007 | A1 |
20080086350 | Ponessa | Apr 2008 | A1 |
20080270973 | Edwards | Oct 2008 | A1 |
20080294485 | Takeuchi | Nov 2008 | A1 |
20080320441 | Ahadian | Dec 2008 | A1 |
20090037013 | Hendler | Feb 2009 | A1 |
20090112666 | Guo | Apr 2009 | A1 |
20090210858 | Son | Aug 2009 | A1 |
20100114618 | Wilcock | May 2010 | A1 |
20110191128 | Chao | Aug 2011 | A1 |
20110258138 | Kulkarni | Oct 2011 | A1 |
20110292429 | Morskate | Dec 2011 | A1 |
20120023345 | Naffziger et al. | Jan 2012 | A1 |
20120109664 | Krishnapuram | May 2012 | A1 |
20120109984 | Clark, Jr. | May 2012 | A1 |
20120124553 | Eschenroeder | May 2012 | A1 |
20120137205 | Pandrangi | May 2012 | A1 |
20120246611 | Sawant | Sep 2012 | A1 |
20120296687 | Satyanarayana | Nov 2012 | A1 |
20130018994 | Flavel | Jan 2013 | A1 |
20130060596 | Gu | Mar 2013 | A1 |
20130067456 | Khilnani | Mar 2013 | A1 |
20130144786 | Tong | Jun 2013 | A1 |
20130159060 | Steinbach | Jun 2013 | A1 |
20130159898 | Knospe | Jun 2013 | A1 |
20130304530 | Chodavarapu | Nov 2013 | A1 |
20140067016 | Kaula | Mar 2014 | A1 |
20140310052 | Foehr | Oct 2014 | A1 |
20140380308 | Hassine | Dec 2014 | A1 |
20150007129 | William | Jan 2015 | A1 |
20170228649 | Chatterjee | Aug 2017 | A1 |
Number | Date | Country |
---|---|---|
1629869 | Nov 2012 | CN |
102799460 | Nov 2012 | CN |
2002069142 | Sep 2002 | WO |
2007041537 | Apr 2007 | WO |
Entry |
---|
Process Integration Handbook (Year: 2009). |
Gutsche, Peter, “Process Integration Handbook”, Retrieved from: <<https://archive.sap.com/kmuuid2/8078cff3-e045-2c10-9bae-abf0ca5040c5/Process%20Integration%20(PI)%20Handbook.pdf>>, Jun. 30, 2009, 108 Pages. |
“Search Report Issued in European Patent Application No. 14740075.8”, dated Sep. 29, 2017, 7 Pages. |
“Corrected Notice of Allowance Issued in U.S. Appl. No. 14/157,756”, dated Oct. 28, 2016, 2 Pages. |
“Final Office Action issued in U.S. Appl. No. 14/157,756”, dated Jun. 2, 2016, 10 Pages. |
“Non Final Office Action Issued in U.S. Appl. No. 14/157,756”, dated Nov. 23, 2015, 9 Pages. |
“Notice of Allowance Issued in U.S. Appl. No. 14/157,756”, dated Oct. 11, 2016, 8 Pages. |
Wolfel, Klaus, “Automating ERP Package Configuration for Small Businesses”,In Diploma Thesis, Jul. 21, 2010, 86 pages. |
Smaizys, et al., “Business Rules Based Agile ERP Systems Development”, In Journal of Informatica, vol. 20, Issue 3, Aug. 2009, 22 pages. |
Mendling, et al., “Towards the Interchange of Configurable EPCs: An XML-based Approach for Reference Model Configuration”, In Proceedings of the Enterprise Modelling and Information Systems Architectures, Oct. 24, 2005, 15 pages. |
“Set Up a Company With RapidStart Services for Microsoft Dynamics NAV”, Published on: Jul. 31, 2012, Available at: http://msdn.microsoft.com/en-us/library/hh179428(v=nav.70).aspx. |
Bucher, et al., “Automatic Parameter Configuration for Inventory Management in SAP ERP/APO”, In the Working Paper, Aug. 20, 2010, 32 pages. |
International Search Report and Written Opinion for International Patent Application No. PCT/US 14/43747, dated Sep. 22, 2016, date of filing: Jun. 24, 2014, 8 pages. |
“First Office Action and Search Report Issued in Chinese Patent Application No. 2314800371014”, dated Nov. 21: 2018, 23 pages. |
Number | Date | Country | |
---|---|---|---|
20170337053 A1 | Nov 2017 | US |
Number | Date | Country | |
---|---|---|---|
61840247 | Jun 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14157756 | Jan 2014 | US |
Child | 15403666 | US |