Process Modeling vs. Configuration Management

Process Modeling vs. Configuration Management

Project Procurement Management Bus 437

Strayer University

Which is more applicable across the widest possible range of situations: process modeling or configuration management?

Configuration management is more applicable in several organizations that are project driven or non-project driven. Many companies support this technique because it supports the control of the design, manufacturing, and support of the product. ISO 10007 (ISO 1197) defines configuration management as: A management discipline that applies technical and administrative direction to the development, production and support life cycle of a configuration item. The discipline is applicable to hardware, software, processed materials, services, and related technical documentation (Morris & Pinto). Managing the product is not the only essential part of configuration management but managing everything that defines the product and system across the life cycle. This should be began when the first definitive information is issued and not when configuration is needed to be managed. It is beneficial to have the right information in the right format in the right place at the right time in order to be successful project manager.

The success of the organization relies on effective configuring database and its data. This is essential as it is the detailed recording and updating of information that describes the organizations hardware and software applications. A configuration management system includes the set of policies, practices, and tools that help an organization maintain software configurations. The primary purpose of a configuration management system is to maintain the integrity of the software artifacts of an organization. Consequently, configuration management systems identify the history of software artifacts and their larger aggregate configurations, systematically control how these artifacts change over time, and maintain interrelationships among them (nasa.gov).

Process modeling is a system that is often used to enhance team coordination and communication by using simple mechanisms such as flow and Gantt charts. Researchers have concluded that every successful organization should have a formal blue print, road map or template that drives a new project. In order to avoid a description process that is too detailed, a design of the project process should begin with a model that is high leveled and is able to engage the management team. A detailed model will not in engage the management team and may possibly decrease motivation. In the 1960’s the new product development (NPD) was implemented and had several discrepancies because throughout each phase of the activity process, the other phase was acting alone and with little communication with the activity previously. This led to long lead times, late product launches, increased development cost, the lack of an effective information flow, and the lack of flexibility for change in the process (Morris &Pinto, 2007). However, the advantage of using a configuration management application, the systems can be reviewed in order to ensure that one system will not negatively affect any of the other systems. Activities that are performed within construction projects can adopt the model techniques that use hierarchy, data flows, IDEFO techniques, and flow charts designed in process modeling.

In conclusion, configuration management is best described as a process for managing the composition of a product, and defining the product that supports the documentation and other data and products. It is innovative and can adapt to the rapid changes that are consistently occurring. Incorporating new methods that change into new products, systems and services is important to the configuration management process. As more and more organizations seek to exploit the benefits of life cycle support and service agreements, the role of configuration management becomes pivotal in maximizing value (Morris & Pinto, 2007).

References

Morris, P., & Pinto, J. (Eds.). (2007). The Wiley guide to project technology, supply chain &

procurement management. Hoboken, NJ: John Wiley & Sons. www.nasa.com