$19.95 Buy and instantly download this paper now
This paper relates that Flextronics International needs to implement a newly designed system specific to its Hewlett Packard contract, yet be able to interface with current MRP systems devised for other company clients. The paper describes the necessary considerations and architectural elements of such a system including the data, processes, interfaces and networks. The paper shows how systems architecture design is a multifaceted and often an ongoing process involving some amount of trial and error. The paper emphasizes that proper foresight, coupled with adequate levels of information gathering and analysis, can greatly reduce this rather inefficient and thus costly period of initial systems implementation.
From the Paper:"The data that will need to be collected on an ongoing basis for the effective operation of the MRP system is fairly straightforward. Information regarding orders from Hewlett Packard, including unit requirements and shipping deadlines, will need to be collected from the client on an ongoing and largely (if not wholly) automatic basis, third-party shipping carriers' schedules will need to be regularly (and again automatically, if possible) updated, and individual assembly line capabilities will also be a necessary piece of input data. Each of these essential pieces of data should be classed separately, and this should be reflected in the architecture of the system with little inter-class connection (Satzinger et al 2004).
"The reduced amount of interconnectivity between data classes ensures a simplified and efficient system; though the nature of the MRP system is, of course, to analyze each piece of data in terms of the other in order to deliver the necessary time schedules and output levels of each manufacturing line in order to reach productivity and efficiency needs, the system architecture should clear reflect the different sources and natures of these data. Output data consisting of time schedules, necessary productivity levels, manufacturing line assignments, and shipping carrier notification of booking should be similarly separated."
Sample of Sources Used:
- Berger, A. (2002). Embedded systems design: an introduction to processes, tools, and techniques. Lawrence, KS: CMP Books.
- Laplante, P. (2004). Real-time systems design and analysis. Hoboken, NJ: John Wiley & Sons.
- Satzinger, J.; Jackson, R. & Burd, S. (2004). System analysis and design in a changing world, Third Edition. New York: Course technology.
Cite this Case Study:
Workplace Application Architecture and Process Design (2013, January 03) Retrieved September 18, 2020, from https://www.academon.com/case-study/workplace-application-architecture-and-process-design-152129/
"Workplace Application Architecture and Process Design" 03 January 2013. Web. 18 September. 2020. <https://www.academon.com/case-study/workplace-application-architecture-and-process-design-152129/>