Blueprinting of a Normalized Supply Chain Processes: Results in Implementing Normalized Software Systems

With the technology evolving every day and with the increase in global competition, industries are always under the pressure to be the best. They need to provide good quality products at competitive prices, when and how the customer wants them.  In order to achieve this level of service, products and their respective supply chain processes need to be flexible and evolvable; otherwise changes will be extremely expensive, slow and with many combinatorial effects. Those combinatorial effects impact the whole organizational structure, from a management, financial, documentation, logistics and specially the information system Enterprise Requirement Planning (ERP) perspective. By applying the normalized system concept/theory to segments of the supply chain, we believe minimal effects, especially at the time of launching an organization global software project. The purpose of this paper is to point out that if an organization wants to develop a software from scratch or implement an existing ERP software for their business needs and if their business processes are normalized and modular then most probably this will yield to a normalized and modular software system that can be easily modified when the business evolves. Another important goal of this paper is to increase the awareness regarding the design of the business processes in a software implementation project. If the blueprints created are normalized then the software developers and configurators will use those modular blueprints to map them into modular software. This paper only prepares the ground for further studies;  the above concept will be supported by going through the steps of developing, configuring and/or implementing a software system for an organization by using two methods: The Software Development Lifecycle method (SDLC) and the Accelerated SAP implementation method (ASAP). Both methods start with the customer requirements, then blue printing of its business processes and finally mapping those processes into a software system.  Since those requirements and processes are the starting point of the implementation process, then normalizing those processes will end up in a normalizing software.

• Bassam Istanbouli

• Blueprint
• ERP
• SDLC
• Modular.

[1] https://normalizedsystems.org/
[2] Langlois, R.N., 2002. Modularity in technology and organization. Journal of Economic Behavior & Organization, Vol. 49, pp 19-37
[3] Shehab, E.M., Sharp, M.W., Supramaniam, L., and Spedding, T.A., 2004. Enterprise Resource Planning: An integrative review. Business Process Management Journal 10(4).
[4] Parnas, D.L., Clements, P.C. and Weiss, D.M., 1984. The Modular Structure of Complex Systems. IEEE, 1984, pp 408-417.
[5] Ciraci, S. and van den Broek, P., 2006. Evolvability as a quality attribute of software architectures. Journal of Physics Conference Series, January 2006.
[6] Motwani, B., 2017. Impact of Resources in Enterprise Resource Planning (ERP) Implementation Process on Internal Process of an Organization. Amity Business Review, 2017. Vol. 18, No. 1.
[7] Supply Chain Management: theory and practices (2004) - Dr. Ir. Jack G.A.J. van der Vorst
[8] Normalized Systems Theory, From Foundations for Evolvable Software Toward a General Theory for Evolvable Design, Herwig Mannaert – Jan Verelst – Peter De Bruyn.
[9] https://toughnickel.com/business/ASAP-Methodology-SAP-Implementation-Phases
[10] Modern Systems Analysis & Design by J.A. Hoffer, J.F. George and J.S. Valaxich
[11] Mannaert, H., Verelst, J., De Bruyn, P., 2016. Normalized Systems Theory, From Foundations for Evolvable Software Toward a General Theory for Evolvable Design.
[12] SAP R/3 Process Oriented Implementation, Gerhard Keller, Thomas Tenfel.