István Orosz

Company level Big Data Management

Carefully Processing enormous data in Company-level evokes new tools and methods in Enterprise Data Management. The volume of information and data increases in an exponential way, which makes strategic issues not only for individuals but also in Company-level. Typical approaches are well known for these kinds of problems. Date is stored in Databases, Data warehouses and Cloud applications. There are various well-known and appropriate solutions are ready-to-use for any of the above listed applications, but they are rarely complete at Corporation levels. Therefore, Enterprises require temporary solutions. The current article discusses the main issues together with the complete and temporary solutions for typical Data management. Effectiveness, efficiency and costs are demonstrated in different point of views, e.g. Project and Knowledge Management.

Business Process Reengineering project in Local Governments with ERP

Local Governments use several different IT methods and tools to provide services required. Chosen business processes and software products should certainly provide suitable and reliable applications for long term. Nevertheless, due to the sudden change and improvement of IT Technology, some solutions become obsolete and those should be replaced sooner or later. However, as sustainability is requested in Local Governments, such changes have to be handled carefully. A new Business Process Reengineering, BPR, methodology is being built to support Local Governments-specific IT change and technology management. This paper introduces our methodology applied to an initial Dynamics AX business process implementation project. A mini- Dynamics AX project is defined to complete the so-called Business BluePrint phase of Dynamics AX Methodology. This approach is found to be suitable to support the Local Governments BPR project.

Information technology systems in logistics and roles of ERPs

Chosen business processes and software products should certainly provide suitable and reliable applications for long term. However, because of the sudden improvement and change of modern IT Technology, some solutions become out of date and those should be replaced sooner or later, even if we consider the world of Enterprise Resource Planning systems. One can figure out that business requirements for software change management depend on specific business functions, industry, technologies and so on. This is true for the IT needs of logistics as well. With the existence of supply chain management, strong needs for a solid IT background came to life. These needs cover the fields of data mining, advanced business intelligence tools, and the move towards cloud computing and mobile devices as well. After overviewing some of the basic elements and challenges of supply change management, this paper tries to analyse two widespread ERPs, SAP and Dynamics AX, and compare them from logistics point of view. In this area the need for a long term reliable and supported solution and the need for the latest technology exist parallel. There is only a slight difference in the used technology, but a greater difference in the way business flows are handled.

Local Governments-specific BPR mini-project with SAP applications

Local Governments use multiple IT methods and tools to provide services required. Chosen business processes and software products should certainly provide suitable and reliable applications for long term. Nevertheless, due to the sudden change and improvement of IT Technology, some solutions become obsolete and those should be replaced sooner or later. However, as sustainability is requested in Local Governments, such changes have to be handled carefully. A new Business Process Reengineering, BPR, methodology is being built to support Local Governments-specific IT change and technology management. This paper introduces our methodology applied to an initial SAP business process implementation project. A mini-SAP project is defined to complete the so-called Business BluePrint phase of SAP ASAP Methodology. This approach is found to be suitable to support the Local Governments BPR project.

Software as a service in cloud based ERP change management

Cloud based technology heavily changed the way how Enterprise Resource Planning (ERP) systems are handled through the whole lifecycle. The previous release-by-release driven by main version change (from pre-alpha to gold release) was developed into a continuous release management. Business processes although remained the same, but how can be determined, which part of the software needs to remain untouched, while evolving to continuous lifecycle support. One of the key questions is to ensure the continuous reliability of the software product. Due to the sudden change and improvement, this type of lifecycle management can be described as Software-as-a-Service (SaaS) type methodology. As from the current implementations, this process does not necessarily leads to a Business Process Reengineering (BPR). This paper introduces change management methodology applied to a specific ERP system, Microsoft Dynamics AX business process lifecycle maintenance implementation project. This approach seems to be suitable for supporting the long term sustainability of the software product.

Workflow processing using ERP Objects

Enterprise Resources Planning (ERP) Systems, and Workflow Management Systems (WFMS) evolved parallel in the past. The main business drivers for automation came from the ERP world, but the WFMS solutions discovered their own way figuring out the necessity of such applications without ERP as well. In our paper we follow only the usage of workflows in ERP systems. The central elements of built-in workflows are the ERP objects, which embed and handle the business data providing real life meaning of business objects as well. The capabilities of built-in workflow systems of such ERP solutions are presented via two market-leaders: SAP and Microsoft Dynamics AX. Both solutions are dealing with ERP objects in sence of the workflow management. We recognized and present the weaknesses and restrictions of the built-in workflow systems on these two ERP examples. In our paper we describe the results of our analysis of the interoperability of the built-in workflow systems as well and demonstrate the required add-on functionalities to provide usable cross-system workflows in such an environment. We also mention the possibility of using a built-in workflow as a full-featured

Change management and workflow processing using Dynamics AX objects

M Microsoft Dynamics AX continuously extends functional and technical approaches. Former Axapta and Navision applications are being replaced with the modern and smart AX and NAV solutions, like the other Dynamics modules and components. A brand new MS Dynamics implementation follows standard methodologies of Sure Step. However, companies, where one can find former Microsoft ERP systems, like Axapta or Navision, face to several change management issues and problems. One can figure out that business requirements for Software change management depend on specific business functions, industry, technologies and so on.

Inherited SAP development concepts using genuine IT programming tools

Program development concepts are highly dependent on software architecture, complexity of algorithm, re-usability purposes, efficiency, efficacy, etc. The evolution of SAP development concepts reflects the changes through important milestones, such as mainframe, client-server and service-oriented architecture. Those issues can easily be resolved by making new programs which were impossible to handle the requirements due to the memory resources, or the speed of the computer either at client or servers side. Procedural and object-oriented SAP programs use vastly different approaches. There is a lack, however, to build an architecture-independent set of SAP development concepts that can be re-used in any SAP versions and architecture. This paper introduces a new approach to build an SAP Development Repository, in which re-usable concepts are collected applied in different architectures and versions.