January 2019
·
64 Reads
The topic of this paper was born out of the pratical need for improving collaboration also within planning, and it deals with synchronising a) constant improvement of Planning Systems (principles, concepts, processes, structure, software sulutions etc.) of the Supply Chain members (SCPS) and b) limited ability of the SC members (especially if they are of the small and medium enterprise type-SMEs) to maintain the required software solutions needed to support such a dynamic planning system in SC. Bearing in mind: a) the different types of SC and their members (big business and/or SME), b) the complexity of planning per se, c) the different ways of organising for planning in LS and d) the difficulty in applying software changes within SCPS (stress, waiting, cost etc.), the problem is how to ensure adequate, but not overly expensive software support (new or improved) in a timely fashion for the new SCPS concept. The initial hypothesis is that there is at least one way in which it is possible to develop SCPS and, at the same time maintain the adequacy of the software solution supporting it. The paper is intended for those who design and construct SCPS, as well as all users of it, with the intention to increase awareness of the necessity for constant development of that particular system and about the need for its flexibility, as well as the awareness of the significance and possibilities of planning system engineering. At the same time it is also intended for those who create SCPS software-so that they bear in mind that their software should be functional even if significant changes within SCPS occur. In this paper we have shown a SC model followed by the relevant problem areas (and related works): planning in SC, with the need for SCPS improvement, and the standard software solutions in SC planning/management. In the section about research and results, we have defined seven research questions; we have then pointed out the significant elements of participant collaboration complexity within SC, as well as the possibility for maintaining the adequacy (relevancy) of the software solutions whilst constantly imporving SCPS.