KR102695715B1 - Configuration management system for large-scale capital projects - Google Patents

Abstract

Configuration management systems manage template configuration information more efficiently and effectively across multiple large capital projects running multiple applications across multiple project sites.

Description

Configuration management system for large-scale capital projects

preference

This patent application claims the benefit of U.S. Provisional Patent Application No. 62/315,178, filed March 30, 2016, entitled "Method and Apparatus for Managing Template Configuration Information Across a Plurality of Large Scale Projects," Ewan D. Botterill and Alain Mouyal are inventors, the disclosure of which is incorporated herein by reference in its entirety.

Field of invention

The present invention relates generally to large scale capital projects for building units and construction elements, and more particularly to configuration management systems used in large scale capital projects of building units and construction elements, such as power generation facilities.

The design, construction and management of large capital projects such as process facilities (e.g., refineries and pharmaceutical plants), power generation facilities (e.g., coal-fired power plants), ships (e.g., military vessels, cruise ships or cargo ships) and offshore oil platforms require coordination of processes and configuration data on a much larger scale than smaller, more traditional projects (e.g., building and selling a ten room house). As a result, large capital projects often require much more comprehensive production and management solutions.

In response to this need, engineers in the field have developed comprehensive facility design programs (e.g., SmartPlant®Enterprise, distributed by Intergraph, Inc., Huntsville, Ala.) that are specifically designed for the rigors of such large-scale capital projects. In particular, this type of facility design program can be implemented as a comprehensive application suite that manages most or all phases of a large-scale capital project, from initial conception through design, construction, transfer, maintenance, management and decommissioning.

Many facility design programs often create templates from which users can access specific configuration data to develop and manage various phases of their capital projects. Each project template has thousands of different types of configuration data and requirements (often tens of thousands) that are difficult to maintain and update as projects progress. Prior art configuration management systems known to the inventors are not suited to handling such amounts of data.

In one embodiment of the present invention, a method manages template configuration information across a plurality of large-scale capital projects executing a plurality of applications at a plurality of project sites with a configuration management system ("CMS"). To this end, the method transmits project templates from a central site having a master template having a plurality of master template configuration options to the plurality of project sites. Since the project templates are based on the master templates, they can have thousands of project configuration options for developing the large-scale capital projects. The method can also update the master template configuration options at the central site and transmit the updated master template configuration options from the central site to the plurality of project sites and/or one or more staging areas. Each project template has a set of existing project configuration options prior to receiving the updated master template configuration options.

Using one or more automated comparators, at each project site and/or staging area(s), the method determines differences between updated master template configuration options and existing project configuration options for each project. The one or more automated comparators then generate a difference report having master template configuration options that differ from the existing project configuration options for each project. Next, the method selects a subset of the master template configuration options from the difference report for each project. Each project template has a particular subset of project configuration options to be updated from the difference report. Finally, the method updates each existing project configuration options for each project template using the particular subset of template configuration options to generate new existing project configuration options for each project template.

The method can also transmit the new existing configuration options for each project to the central site, and update the updated master template configuration options with the new existing configuration options for each project. To this end, the updated master template configuration options can be determined for each project using one or more automated comparators at the central site and/or in the staging area, for differences between the updated master template configuration options and the new existing configuration options. The one or more automated comparators can then generate an additional difference report having the new existing configuration options and the updated master template configuration options that are different from the new existing configuration options for each project. The method can then select a subset of the new existing configuration options for each project from the additional difference report, and further update the updated master template configuration options using the subset of the new existing configuration options for each project from the additional difference report. The central site can then update the updated master template configuration options again after updating the updated master template configuration options with the new existing configuration options for each project.

The central site may be geographically distant from at least one of the project sites. Alternatively, the central site may be geographically close to at least one of the project sites. Additionally or alternatively, the plurality of project sites may have a physical site having a structure and a computer system. In some embodiments, the structure is distant from the computer system.

The method can utilize one or more automated comparators to first determine differences between updated master template configuration options and existing project configuration options for each project at the staging area(s) and then determine second differences between updated master template configuration options and existing project configuration options for each project at one of the project site(s). Furthermore, the method can be selectable by allowing a human to select a subset of master template configuration options from a difference report for each project.

Some embodiments may use one or more automated comparators in the preparation area(s) rather than in other areas.

In another embodiment, the CMS manages templates between a central site and a plurality of large capital projects, wherein the plurality of large capital projects run a plurality of applications at the plurality of project sites. Specifically, the CMS includes a template generator at the central site. The template generator is configured to generate a master template for at least one large capital project, the master template having a plurality of master template configuration options. The CMS also has a central site updater configured to update the master template configuration options at the central site, and an interface at the central site operably coupled with the central site updater. The interface is configured to transmit the project template to the plurality of project sites. In a manner similar to the other embodiments, the project template is based on the master template, and thus can have thousands of project configuration options for developing large capital projects.

The interface is also configured to transmit the updated master template configuration options to a plurality of project sites and/or one or more staging areas. Also, as in other embodiments, each project template has a set of existing project configuration options prior to receiving the updated master template configuration options. One or more automated comparators of the CMS are configured to determine differences between the updated master template configuration options and the existing project configuration options for each project at each project site and/or staging area(s). Accordingly, the one or more automated comparators are configured to generate a difference report having different master template configuration options than the existing project configuration options of each project.

To select appropriate configuration options, the CMS has a manual selection interface operatively coupled with one or more automated comparators. The manual selection interface enables a user to select a subset of the master template configuration options from the difference report for each project. Each project template preferably has a specific subset of the project configuration options to be updated from the difference report. The CMS also has a project site updater configured to update each existing project configuration options for each project template using the specific subset of template configuration options to generate new existing project configuration options for each project template.

Exemplary embodiments of the present invention are implemented as a computer program product having a computer-usable medium having computer-readable program codes thereon. The computer-readable codes can be read and used by a computer system according to conventional processes.

Those skilled in the art will more fully appreciate the advantages of various embodiments of the present invention from the following “Description of Exemplary Embodiments,” which is illustrated and illustrated with reference to the drawings summarized immediately below.
Figure 1a schematically illustrates some of the large-scale capital projects that may utilize exemplary embodiments of the present invention.
FIG. 1b schematically illustrates part of a configuration management system that may be used in exemplary embodiments of the present invention.
FIGS. 2A and 2B are single flow diagrams illustrating a process for managing CMS configuration information across multiple large-scale capital projects, according to exemplary embodiments of the present invention.
Figure 3 schematically illustrates an environment in which exemplary embodiments of the present invention can be implemented.

Exemplary embodiments optimize a configuration management system to efficiently update large amounts of configuration data of facility design program templates used across multiple different project sites, each of which is preferably associated with a large capital project. To this end, a central site directs configuration updates to the various project sites, which then selectively update their local configuration databases. Both automated and manual processes are combined to more efficiently and easily implement the selected configuration updates at the project sites. Some embodiments utilize a staging area to perform much of the comparison and update processing, thereby improving project efficiency by minimizing downtime at a project site where hundreds of designers and engineers are continuously working on the project. The project sites then transmit their updated configuration data back to the central site for subsequent update purposes. Among other benefits, this update process minimizes both the amount of time required to update local template configuration databases and the potential for user error during the update process. Details of exemplary embodiments are described below.

FIG. 1A generally illustrates a portion of an example of a large-scale capital project (10) (more generally, a "capital project (10)") that may implement exemplary embodiments of the present invention. More specifically, as is known to those skilled in the art, a capital project (10) is generally a long-term investment made to build, augment, add to, or improve a highly capital-intensive project, requiring significant amounts of both financial and labor capital to undertake, and often taking several years to complete. Capital projects (10) are often defined by their large cost compared to other investments (e.g., building a home or a truck) that require less planning and resources. Both private and public sectors may be included in a capital project (10). Some examples of capital projects (10) include developing and maintaining refineries, power generation facilities, ships, offshore oil platforms, dams, and factories.

The capital project (10) illustrated in Figure 1a is a power plant having a number of different components that cooperate to accomplish its generating function, as is known to those skilled in the art. For example, in particular, the power plant of this drawing has a number of large and small buildings, chimneys, pipes, valves, fuel tanks, ladders, and electrical systems. In fact, the design, construction, and maintenance of such a project requires a tremendous amount of planning and coordination. Without careful planning and coordination, the power plant may never have been built or operated.

To this end, engineers in the field have developed facility design programs/products (“facility design programs”) to aid in the planning/design, development, maintenance and decommissioning of capital projects (10) such as those illustrated in FIG. 1a. As noted above, one such widely used facility design program is known as the SmartPlant®Enterprise product (hereinafter, the “SmartPlant®product”) distributed by Intergraph, Inc. of Huntsville, Alabama. In a manner similar to other such products, the SmartPlant®product has at least the following related functions and components:

- 3D modeling and visualization

- Engineering and schematics

- Information Management

- Procurement, manufacturing and construction

- Open integration with other proprietary and open systems

Accordingly, designers, engineers, developers, managers and other interested parties use these and other features of facility design programs such as SmartPlant®products to design, construct, renew, manage and decommission capital projects (10), such as the power plant (10) illustrated in FIG. 1a. As is known to those skilled in the art, such 3D or 2D design programs often generate templates that, in conjunction with a number of software tools, serve as the primary mechanism for designing and managing their projects. In particular, templates typically include a number of options, configurations and layouts that enable the user to develop their projects more accurately and efficiently.

At the risk of oversimplifying the various embodiments, a template used in a large capital project context may be analogized to a word processing template that is displayed when a user opens a word processing program. In particular, the word processing template may be configured to allow the user to select from a number of fonts, colors, shapes, line spacing, and formats. The user then begins to prepare their document using the different options provided by the template. In fact, the word processing user may create any number of different documents, such as letters, memos, spreadsheets, books, etc. In a similar manner, a template used for a capital project (10) may also be used for other very different types of capital projects, such as the capital projects (10) described above.

However, the configuration data of the template often changes over the life of the capital projects (10). Specifically, the template configuration required during the life cycle of a capital project (10), such as a power plant, refinery, or vessel of FIG. 1a, depends on many factors including the owner's requirements, the specifics of the industry, and the configuration options available to the software systems used at the various project sites (16). The configuration of such capital projects (10) typically includes thousands of types of items such as user-defined properties, symbols, drawing templates, rules, etc. In addition, the configuration requirements typically vary between the various life cycle stages of the facility, such as conceptual design, detailed design, commissioning, construction, operation, maintenance, decommissioning, etc.

Another level of complexity involves the various software applications used at each project site. In particular, each software application running at a project site may have its own set of configuration types and options, and specific methods for comparing and updating configuration data as well as existing design data. Furthermore, these options and methods may depend on or change with specific versions of the software applications. Another level of complexity involves the integration of the applications into a system, and the interdependencies between configuration types and software applications.

Given these complexities, it is easy for a facility owner or engineering firm to spend years developing a complete set of template configurations to use with their facility design program. To avoid this potential delay, in exemplary embodiments, the owner or engineering firm managing the project can begin the project using a partially completed template. Each individual project can then further configure the applications (e.g., facility design program) used for the project by modifying the configuration data inherited from the template to suit its needs and begin the design process.

At some convenient time, typically between life cycle stages, the owner or engineering firm may need to update the configuration of the active project site(s) (16) to adopt some new or modified template configurations. This presents a number of technical issues that are addressed by various embodiments. Specifically, such technical issues may include:

1. Software application versions may differ between the template and the active project, possibly causing conflicts or difficulties when comparing or updating configurations.

2. Each software application has its own set of configurations, dependencies and methods for comparing and updating configuration data/files.

3. The amount of time to complete these comparisons and update the configuration files is preferably kept to a minimum to reduce project downtime. Manually comparing dozens of properties of each of the thousands of configuration items between templates and active projects across multiple software applications would be impractical, extremely time-consuming, and error-prone.

4. When updating the configuration of an active project, there is a risk to the existing configuration and design data within it.

Various embodiments mitigate some or all of these technical risks and provide a robust and efficient method for comparing updated configuration data of an integrated template system with the configuration of an integrated active project. In addition, such embodiments preferably selectively update the configuration of an integrated active project based on differences, thus not adversely affecting the active project configuration or existing design data. Furthermore, exemplary embodiments can complete the process in reverse order, meaning that the primary or master template configuration can also be updated using differences that exist in the active project configuration(s).

Accordingly, exemplary embodiments may address some or, preferably, all of these technical issues using a specially configured configuration management system (“CMS (17)”, FIG. 1b). Specifically, as is known to those skilled in the art, a CMS systematically manages configuration changes to a computer system or network over time in order to maintain system integrity. Accordingly, a CMS may implement techniques, policies, tools, and procedures for managing and evaluating changes to configurations and configuration options in a computer system or network. To this end, FIG. 1b schematically illustrates an exemplary embodiment of a CMS that may be configured to more efficiently update configuration requirements of templates used for large-scale capital projects, such as the capital project (10) of FIG. 1a.

The CMS (17) of FIG. 1b includes a plurality of components that cooperate to efficiently update large-scale capital project template configuration options between a central site (12) and one or more project site(s) (16) (see FIG. 3 below for details of the central site (12) and project site(s) (16)). Each of these components is operably connected by a conventional interconnection mechanism. FIG. 1b schematically illustrates a bus (19) connecting each of the components. Those skilled in the art should appreciate that this generalized representation may be modified to include other conventional direct or indirect connections. Accordingly, the description of the bus (19) is not intended to be limiting of the various embodiments.

The components include a template generator (18) for generating new templates, an updater (20) for updating templates, and a port/interface (22) for communicating with other components external to the CMS (17) or elsewhere in the CMS (17) (e.g., an instance of the CMS (17) at another site). In addition, the CMS (17) also includes a manual user interface (24) that enables a person to administer the system and select desired configuration updates. Exemplary embodiments of the manual user interface (24) include a graphical user interface (24) (“GUI”) having a presentation display that easily enables a user to find configuration information, system information, etc., and to select configuration data for the updater (20). The CMS (17) also has an automated comparator (26) for comparing configuration data in a quick and automated manner without human intervention, and a memory (28) for storing the configuration data, for example, in the form of a database.

The CMS (17) of FIG. 1b can be implemented in a variety of ways. In one implementation, the CMS (17) can have local, independent, and cooperative versions at different project sites (16) and at the central site (12). For example, the CMS (17) can have one updater (20) at the central site (12) and another updater (20) at the project sites (16). As another example, the interface (22) can be at the central site (12), at the project sites (16) (e.g., at least at portions that serve as input or output ports), and/or at some other location remote from both the central site (12) and the project sites (16). Similarly, the CMS (17) can be distributed across the entire network. In the latter embodiment, the components of FIG. 1b operate on both the central site (12) and the various project sites (16). FIG. 2, described below, provides more details on how exemplary embodiments of the CMS (17) and its components function to provide various technical benefits.

It should be noted that FIG. 1B merely schematically illustrates each of these components. Those skilled in the art should appreciate that each of these components may be implemented in a variety of conventional ways, such as using hardware, software, or a combination of hardware and software across one or more other functional components. For example, the updater (20) may be implemented using a plurality of microprocessors executing firmware. As another example, the updater (20) may be implemented using one or more application-specific integrated circuits (i.e., "ASICs") and associated software, or a combination of ASICs, discrete electronic components (e.g., transistors), and microprocessors. Accordingly, the representation of the updater (20) and other components within a single box in FIG. 1B is for the purpose of simplicity only. In fact, as noted above, the components of FIG. 1B may be distributed across a plurality of different machines, not necessarily within the same housing or chassis.

It should be reiterated that the representation in Fig. 1b is a significantly simplified representation of an actual CMS. Those skilled in the art will appreciate that such systems typically have many other physical and functional components, such as central processing units, various utilities, controllers, short-term memory, etc. Accordingly, this description is not intended to imply that Fig. 1b represents all of the elements of a CMS.

Figure 2 illustrates a preferred process used by the CMS (17) to manage configuration information in a manner that alleviates some or all of the technical issues described above. It should be noted that this process may be considered a streamlining from the longer process normally used to update template configuration data. Thus, the process of updating template configuration data may have many different steps that those skilled in the art may likely use. Furthermore, some of the steps may be performed in a different order or concurrently than those depicted. Thus, those skilled in the art may modify the process as appropriate.

The process of FIG. 2 begins at step 200 where a template generator (18) generates a master template at a central site (the central site (12) described above). More specifically, FIG. 3 schematically illustrates a geography or network over which various embodiments described in FIG. 2 update template configuration data. The network includes a central site (12) (typically managed by some central authority) that communicates directly or through an intermediate staging area (14) with a plurality of specific project site(s) (16). In exemplary embodiments, the various sites/areas (12, 14, 16) are geographically distant from one another. However, other embodiments may place one or all of the sites/areas (12, 14, 16) in close proximity to one another.

A central site (12) manages the initial and template configuration updates, while the multiple project site(s) (16) are locations where the projects are executed. For example, the central site (12) may be managed by a single entity, such as a large energy company or owner, while the project site(s) (16) may be separate power generation facilities, fuel storage facilities, drilling platforms, or other projects managed under the direction of the same energy company. Each of these different project site(s) (16) may be several miles apart or in a common area. Furthermore, the project site (16) may have a physical site having a structure (e.g., a power plant building) and a computer system (e.g., a computer system that executes the update process or some other process). The computer system may be in the same building as the structure or may be remote from the structure.

Although it is certainly expected that there will be some local management at the project site(s) (16), a central site (12) typically provides general management of the various projects and facilitates collaboration between the various project site(s) (16) (e.g., when the project is implemented at multiple locations). The project site(s) (16) use templates and facility design applications to shape and manage the life of the project. Thus, the project site (16) starts with a master template (e.g., version 1.0) and transforms that master template into a project using the facility design program and associated programs. As is known to those skilled in the art, the facility design program/applications use configuration options from the template inherited by the project to design and manage the project.

The staging area (14) is an intermediate location where template configurations can be at least partially updated and implemented for the active project site(s) (16). As described in more detail below, the staging area (14) effectively offloads some of the local configuration update processes from the project site(s) (16), thus allowing projects to continue to operate without interruption. However, some embodiments may omit the staging area (14), and instead perform more of the configuration update processing at the project site(s) (16), the central site (12), and/or some other region/area (depending on the process). Some embodiments that include the staging area (14) may also perform some of the processes directly at the project site(s) (16) and/or the central site (12). Thus, the description of processing at the staging area (14) is not intended to imply that such processes cannot be performed at the project site(s) (16) and/or the central site (12). Furthermore, although not shown, some embodiments also have an intermediate CMS location for managing multiple configuration versions.

It should be reiterated that FIG. 3 is a schematic diagram and thus each block may represent one or more functions and/or physical entities. For example, the central site (12) may include a distributed computer network spanning a wide geographic area. Alternatively, the central site (12) may include only a single building or a single room within a single building. Similarly, the staging area (14) and the project site(s) (16) may or may not also be geographically and/or logically extensive.

Referring again to FIG. 2, step 200 first generates (at the central site (12)) a master template by first generating a template configuration that takes into account many or all of the software applications intended to be used at the plurality of project sites (16). Next, using the template generator (18) and/or some testing facility, step 200 also tests the configurations with sample data to generate an initial master template. The configuration data/files may then be stored in the memory (28) of the CMS (17). As is known to those skilled in the art, the configuration data/files may include a set of options, settings and reference data that may be used to manage any project at the project site(s) (16). For example, the configuration files may include externalized configurations (from their applications) as used directly by the software during design operations. Such configuration data may include "configuration artefacts", which are configuration data or groups of configuration data that are normally embedded in a database and packaged primarily for externalization and archiving purposes and for comparison and updating purposes, but are not necessarily used directly by application programs or templates in normal operation.

Step 200 ends by directing the template configuration information to the project site(s) (16) along with the templates using the port/interface (22). After receiving the master template, the project site(s) (16) can start their local processes (e.g., production, maintenance, etc.) that require the template. Accordingly, at this point, the local project site(s) (16) uses the master template along with its current copy of the configuration data.

After transmitting the template and its configuration data via its interface (22), the updater (20) starts updating the software versions and template configuration information at the central site (12), and may then update the configuration of the master template as needed (step 202). For example, this updated master template may be considered as version 2.0. Accordingly, the central site updater (20) may store the updated configuration files together with its configuration artifacts (e.g., version 2.0 configuration information) in the CMS memory (28) and copy the active project from the project site(s) (16) to the staging area (14) via the relevant interface (22). In a corresponding manner, this step also copies the updated configuration files to the CMS memory (28) in the staging area (14) (step 204).

At this point, the staging area (14) has updated configuration information from the updated master template as well as configuration data from the project site(s) (16). Therefore, the version 2.0 configuration data of the master template should be used to update the configurations of the active projects.

As mentioned above, such configuration data of a template can include hundreds of configuration types such as graphic symbols, rules, properties, drawing templates, menus, etc. In addition, configuration files can have hundreds of thousands of specific configuration items. This large number of configuration items within a single template can vary based on a number of factors. For example, such factors can include:

- Software applications and their integration used on the project site(s) (16)

- Software versions of such applications

- Interdependencies between configuration types and software applications.

- Industries with various projects (e.g. oil and gas, mining, chemicals, power, etc.)

- Geographic location of various project sites (16)

- Local and regional laws, regulations and standards at the project site(s) (16)

- Project stages (conception, detailing, design, construction, maintenance, dismantling, etc.) and

- Custom configuration items for each project and the evolution of each project since development began.

In practice, a large amount of configuration data must be compared to determine the differences between the current configuration data used by the projects and the updated master template configuration data. To improve efficiency, exemplary embodiments use an automated device, such as an automated comparator (26), to compare the two sets of configuration data (step 206). In other words, in the staging area (14), the automated comparator (26) compares the updated configuration data from the CMS memory (28) (sometimes referred to as the "source") with the master template configuration data from the active project (sometimes referred to as the "target"). Accordingly, this step generates a report, referred to as a "difference report", for the configuration data associated with each software application. Specifically, the difference report identifies specific configuration items and/or data that are indicated as being updated from the CMS updater (20) (i.e., from the central site (12)). To this end, some embodiments of the difference reports have configuration items that exist only in the source, configuration items that exist only in the target, and configuration items that exist in both the source and the target but are different. Such examples may also enumerate such differences.

Next, step 208 involves a responsible and knowledgeable user from each project site (16) (and/or pre-programmed intelligent logic) to review the difference report. Specifically, using the manual user interface (24), the user manually determines/selects which template configuration options/data (within the difference report) should be updated for their particular project in the staging area (14). Such user or logic should carefully consider the potential engineering impact on the existing design data in the project relative to previous configurations. Accordingly, the updater (20) selectively updates their target project configuration data based on these determinations and stores the configuration files/data in the CMS memory (28) (step 210). Despite these updates, there may still be some updated configuration data from the master template that is not implemented in the update of the target project. Accordingly, in such a case, this final updated configuration data is structured as described immediately below.

Specifically, after the updated configuration information has been transmitted from the staging area (14) to the project site(s) (16) (step 212), the project site(s) (16) now update their software application versions and copy the configuration files that were finally stored in the CMS memory (28). Again using the comparator (26), but this time at the project site(s) (16), the process compares the configurations between the configuration files copied from the CMS memory (28) in step 214 with the configuration data of the active project itself. In a manner similar to step 206, this step generates a different difference report for each software application that lists a) which configuration items exist only in the source, b) which configuration items exist only in the target, and c) configurations that exist in both the source and the target but are different (and details such differences). Since the previous processes have already updated much of the configuration data, this difference report may have less configuration information than the difference report described above.

Also, as with the previous processes, at step 216, a responsible and knowledgeable user from each project site (16) and/or pre-programmed intelligent logic reviews this new difference report and manually determines/selects which template configuration options/data should be updated for their particular project using the manual user interface (24). However, unlike the previous difference report, this difference report is generated at the project site (16). The updater (20) then selectively updates the target project configuration (step 218) based on the decisions made during step 216 and updates the CMS memory (28).

At this point, the templates at the project site(s) (16) are updated (for the time being) with configuration changes from the central site (12). Next, the process selectively updates the master template at the central site (12) with any appropriate configuration updates that have been made to the project site template(s) since the initial receipt of the latest master template (e.g., version 2.0 of the master template). For example, some of these updates may be applicable to future projects. More specifically, despite the recent project site update described above, the project site(s) (16) may also have updated their templates with configuration information based on the evolution of their particular project. Accordingly, exemplary embodiments update the master template with such applicable updates. Thus, updates flow in both directions between the project site(s) (16) and the central site (12). To this end, the process transfers updated configuration options/data from the project site(s) interfaces (22) to the central site (12) interface (22) (step 220), so that the central site (12) can update the master template with these project-based updates.

Specifically, the process may copy/transfer recently modified project configuration files/data from the CMS memory (28) of the project sites (16) to the central site (12). The CMS comparators (26) of the central site (12) then compare the differences between the configuration files copied from the CMS memory (28) with the configuration data of a master template (e.g., version 2.0) that is deemed most up-to-date. In a similar manner to the previous steps, this step generates a different difference report for each software application (step 222) that enumerates a) which configuration items exist only in the source, b) which configuration items exist only in the target, and c) configurations that exist in both the source and the target but are different (and enumerates such differences).

Also, as with the previous processes, a responsible and knowledgeable user from the central site (12), one or more project site(s) (16), and/or pre-programmed intelligent logic reviews this new difference report and, using the manual user interface (24), manually determines which template configuration options/data from the project configuration(s) in the master template should be updated (step 224). Among other reasons, this step helps to adopt the revised best practices. In fact, some specific configuration options from some projects may not be applicable to other projects, so the user may not select such options. Next, the updater (20) updates the master configuration data specified by this person and/or logic (step 226). After it has been updated with the updated configuration data, the central site (12) tests the new updated configuration data with sample data and stores the new configuration data that passes the test, thereby generating a new master template with the updated configuration data. Thus, the process ends by storing the new configuration data/files in the CMS memory (28).

Steps 202 through 218 may be repeated as the central site (12) generates new updated configuration data (e.g., a version 3.0 master template). Similar and related embodiments may repeat steps 202-226. Moreover, as described above, other embodiments may omit processing at the staging area (14) and only process at the central site (12) and the project site(s) (16).

As described above, the exemplary embodiments provide a number of technical benefits, such as one or more of the following:

1. It allows for safe and selective updates to the active project of an evolving template configuration. It also allows for the reverse operation of "harvesting" useful additional custom configurations made by the project site(s) (16) back into the master template configuration for the benefit of future projects.

2. Protect active design data using multiple locations and update configuration data of active projects while minimizing production downtime (e.g., typically hundreds of engineers).

3. Use comparators (26) with detailed difference reports of thousands or tens of thousands of features to make informed, timely and efficient decisions.

4. Enables selective updates of target active projects using update utilities to be used after comparison, preserving existing configuration and existing design data.

5. The work process directs the correct sequencing of updates by software applications, maintaining and preserving dependencies between them.

6. The CMS (17) (or other similar function) manages the various versions of the configuration files and configuration artifacts. This is important because in some instances the comparator (26) requires that the templates and projects being compared exist on the same version of the software. In addition, there may be many files from various products and many versions of the configuration templates. It is desirable that these files be carefully managed, because it may be necessary to retrofit a project with the correct set of files from various versions (software and configuration versions) that may be years old. Therefore, a clear naming convention is preferably adopted for naming the configuration files and artifacts.

Compared to the prior art CMS manual update process, the exemplary embodiments provide robust, effective, efficient, and complete updates of desired configuration changes. Manual CMS and other methods are too laborious, error-prone, and comprehensive. That is, comparing all configuration items is typically impractical when attempted manually. Comparison utilities facilitate the task and clearly identify differences, for example, by using color-coding.

Various embodiments of the present invention may be implemented, at least in part, in any conventional computer programming language. For example, some embodiments may be implemented as a visual programming process, in a procedural programming language (e.g., "C"), or in an object-oriented programming language (e.g., "C++"). Other embodiments of the present invention may be implemented as pre-configured stand-along hardware elements and/or pre-programmed hardware elements (e.g., application-specific integrated circuits, FPGAs, and digital signal processors) or other related components.

In an alternative embodiment, the disclosed devices and methods (e.g., see the methods described above) may be implemented as a computer program product for use with a computer system. Such an implementation may include a series of computer instructions fixed on a non-transitory, non-transient medium, such as a computer-readable medium (e.g., a diskette, a CD-ROM, a ROM, or a fixed disk). The series of computer instructions may implement all or part of the functionality previously described in connection with the system herein.

Those skilled in the art should recognize that such computer instructions may be written in a number of programming languages for use with a number of computer architectures or operating systems. Furthermore, such instructions may be stored in any memory device, such as semiconductor, magnetic, optical or other memory devices, and may be transmitted using any communication technology, such as optical, infrared, microwave or other transmission technologies.

Among other ways, such computer program products may be distributed as removable media accompanying printed or electronic documentation (e.g., shrink-wrapped software), preloaded into a computer system (e.g., on a system ROM or fixed disk), or distributed from a server or electronic bulletin board over a network (e.g., the Internet or the World Wide Web (WWW)). In fact, some embodiments may be implemented in a SaaS ("software-as-a-service") model or a cloud computing model. Of course, some embodiments of the present invention may be implemented as a combination of software (e.g., computer program products) and hardware. Still other embodiments of the present invention are implemented entirely in hardware or entirely in software.

While the above description discloses various exemplary embodiments of the present invention, it will be apparent to those skilled in the art that various modifications can be made therein to achieve some of the advantages of the present invention without departing from the true scope of the invention.

Claims (22)

A central site for managing initial and configuration updates of templates used for large-scale capital projects, and a computer-implemented configuration management system for managing templates for facility design programs among a plurality of large-scale capital projects, wherein the plurality of large-scale capital projects execute a plurality of applications as the facility design programs at a plurality of project sites, which are locations where the projects are executed, the configuration management system comprising a computer:
The above computer:
A template generator at a central site, wherein the template generator is configured to generate a master template for at least one large-scale capital project, the master template having a plurality of master template configuration options;
A central site updater configured to update said master template configuration options at said central site;
An interface to said central site, operatively coupled to said central site updater, said interface configured to transmit a project template to said plurality of project sites, said project template having thousands of project configuration options for developing said large-scale capital projects, said project template being based on said master template, said interface further configured to transmit said updated master template configuration options to said plurality of project sites and/or to one or more staging areas which are intermediate locations where template configurations can be at least partially updated and implemented for the project sites, each project template having a set of current project configuration options prior to receipt of said updated master template configuration options;
One or more automated comparators at each of the project sites and/or staging area(s) configured to determine differences between said updated master template configuration options and existing project configuration options for each project, wherein said one or more automated comparators are configured to generate a difference report for each project having said master template configuration options that are different from said existing project configuration options;
A manual selection interface operatively coupled to said one or more automated comparators, said manual selection interface enabling a user to select a subset of said master template configuration options from said difference report for each project, each project template having a particular subset of project configuration options to be updated from said difference report; and
A project site updater configured to update each existing project configuration option for each project template using said specific subset of template configuration options, thereby generating new existing project configuration options for each project template.
A computer-implemented configuration management system configured to run. In the first paragraph,
Further comprising a project output operably coupled to said project site updater, said project output configured to transmit said new existing configuration options for each project to said interface at said central site;
A computer-implemented configuration management system, wherein said central site updater is configured to update said updated master template configuration options using said new existing configuration options for each project. In the second paragraph, the central site updater:
For each project, determine the differences between the updated master template configuration options and the new existing configuration options, and generate an additional difference report for each project having the updated master template configuration options that are different from the new existing configuration options,
Allows the user to select a subset of the new existing configuration options for each project from the additional difference report;
A computer-implemented configuration management system configured to further update said updated master template configuration options using said subset of said new existing configuration options for each project from said additional difference report. A computer-implemented configuration management system, wherein in the second paragraph, the central site updater is configured to update the updated master template configuration options using the new existing configuration options for each project, and then update the updated master template configuration options again. A computer-implemented configuration management system, wherein the central site is geographically distant from at least one of the project sites. A computer-implemented configuration management system, wherein the plurality of project sites include physical sites having structures and computer systems. A computer-implemented method for managing template configuration information across multiple large-scale capital projects with a CMS,
The above multiple large-scale capital projects run multiple applications as facility design programs at multiple project sites where the projects are being executed, the method comprising:
A step of managing initial and configuration updates of templates for said facility design program, wherein a central site having a master template having a plurality of master template configuration options transmits project templates to said plurality of project sites, said project templates having thousands of project configuration options for developing said large-scale capital projects, said project templates being based on said master template;
A step of updating said master template configuration options at said central site;
A step of transmitting the updated master template configuration options from the central site to one or more staging areas, which are intermediate locations where the plurality of project sites and/or template configurations can be at least partially updated and implemented for the project sites, wherein each project template has a set of existing project configuration options prior to receiving the updated master template configuration options;
At each project site and/or said staging area(s), a step of determining, for each project, differences between said updated master template configuration options and existing project configuration options using one or more automated comparators, wherein said one or more automated comparators generate a difference report for each project having said master template configuration options that are different from said existing project configuration options;
For each project, a step of receiving a selection of a subset of said master template configuration options from said difference report via a manual selection interface operably coupled with said one or more automated comparators, wherein each project template has a particular subset of project configuration options to be updated from said difference report; and
A step of updating each existing project configuration option for each project template using said specific subset of template configuration options to generate new existing project configuration options for each project template.
A computer-implemented method comprising: In Article 7,
a step of transmitting said new and existing configuration options for each project to said central site; and
Step of updating the above updated master template configuration options using the above new existing configuration options for each project.
A computer-implemented method further comprising: In the 8th paragraph, the step of updating the updated master template configuration options is:
At said central site and/or staging area, using one or more automated comparators, determining differences between said updated master template configuration options and said new existing configuration options for each project, wherein said one or more automated comparators generate an additional difference report having said updated master template configuration options that are different from said new existing configuration options for each project;
selecting a subset of the new existing configuration options for each project from the additional difference report; and
A step of further updating said updated master template configuration options using said subset of said new existing configuration options for each project from said additional difference report.
A computer-implemented method comprising: A computer-implemented method, comprising the step of updating the updated master template configuration options using the new existing configuration options for each project, and then updating the updated master template configuration options again. A computer-implemented method in claim 7, wherein the central site is geographically distant from at least one of the project sites. A computer-implemented method in claim 7, wherein the step of using one or more automated comparators comprises the steps of first determining, for each project in said staging area(s), first differences between said updated master template configuration options and existing project configuration options, and subsequently determining, for each project in one of said project site(s), second differences between said updated master template configuration options and existing project configuration options. delete A computer-implemented method in claim 7, wherein the plurality of project sites include physical sites having structures and computer systems. A computer-implemented method in claim 14, wherein the computer system of the physical site is remote from the structure. In Article 7,
The step of transmitting to the above multiple project sites or one or more staging areas comprises the step of transmitting to the above one or more staging areas,
Additionally, the step of using one or more automated comparators at each of the project sites and/or the staging area(s) comprises the step of using one or more automated comparators at the staging area(s). A computer-implemented method. A non-transitory computer-usable storage medium for use on a computer system to manage CMS template configuration information across multiple large-scale capital projects,
The above multiple large-scale capital projects run multiple applications as facility design programs at multiple project sites where the projects are being executed, the computer usable storage medium having computer readable program codes, the computer readable program codes comprising:
A program code for managing initial and configuration updates of templates for said facility design program, and for transmitting project templates to said plurality of project sites from a central site having a master template having a plurality of master template configuration options, said project template having thousands of project configuration options for developing said large-scale capital projects, said project template being based on said master template;
Program code for updating said master template configuration options at said central site;
Program code for transmitting the updated master template configuration options from the central site to one or more staging areas, each of which is an intermediate location where the plurality of project sites and/or template configurations can be at least partially updated and implemented for the project sites, wherein each project template has a set of current project configuration options prior to receiving the updated master template configuration options;
At each of the project sites and/or the staging area(s), program code for determining, for each project, differences between the updated master template configuration options and existing project configuration options, using one or more automated comparators, wherein the one or more automated comparators generate a difference report for each project having said master template configuration options that are different from the existing project configuration options;
For each project, program code for selecting a subset of said master template configuration options from said difference report, wherein each project template has a particular subset of project configuration options to be updated from said difference report; and
Program code for generating new existing project configuration options for each project template by updating each existing project configuration option for each project template using said specific subset of template configuration options.
A computer-usable storage medium, comprising: In Article 17,
Program code for transmitting said new and existing configuration options for each project to said central site; and
Program code for updating the above updated master template configuration options using the above new existing configuration options for each project.
A computer-usable storage medium further comprising: In the 18th paragraph, the program code for updating the updated master template configuration options:
At said central site and/or staging area, program code for determining, for each project, differences between said updated master template configuration options and said new existing configuration options, using one or more automated comparators, wherein said one or more automated comparators generate an additional difference report for each project having said updated master template configuration options that are different from said new existing configuration options;
Program code for selecting a subset of the new existing configuration options for each project from the additional difference report; and
Program code for further updating said updated master template configuration options using said subset of said new existing configuration options for each project from said additional difference report.
A computer-usable storage medium, comprising: A computer-usable storage medium comprising program code for updating the updated master template configuration options using the new existing configuration options for each project, and then updating the updated master template configuration options again. A computer-usable storage medium, wherein the program code for using one or more automated comparators in claim 17 comprises program code for determining first differences between the updated master template configuration options and existing project configuration options for each project in the staging area(s), and program code for determining second differences between the updated master template configuration options and existing project configuration options for each project in one of the project site(s). A computer-readable storage medium, wherein the program code for selecting comprises program code for providing a manual user interface or enabling a person to select a subset of the master template configuration options from the difference report for each project.