US20030135481A1 - Rules based method and system for project performance monitoring - Google Patents
Rules based method and system for project performance monitoring Download PDFInfo
- Publication number
- US20030135481A1 US20030135481A1 US10/314,678 US31467802A US2003135481A1 US 20030135481 A1 US20030135481 A1 US 20030135481A1 US 31467802 A US31467802 A US 31467802A US 2003135481 A1 US2003135481 A1 US 2003135481A1
- Authority
- US
- United States
- Prior art keywords
- data
- project
- project data
- oversight
- rule
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
Definitions
- This invention relates to a method and system for monitoring the performance of a project and, more particularly, to a method and system which provides for rules based monitoring and a dashboard like console for reporting the projects progress and performance.
- the tools that are used in the planning phase to develop the project plan are also typically used in the management phase to oversee that the project proceeds according to that plan.
- the project is broken down into a series of steps or sub-projects which are typically represented on a GANTT chart as the milestones which are used to monitor and report the project's progress in the oversight process.
- Additional tools such as electronic spreadsheets and graphs are also used in the planning phase to develop budgets and time tables which are subsequently used in the oversight process.
- the management of these projects can involve a complex interaction between the project owner or stakeholder (the party which commissioned the project) and a group of Project responsible Parties (PRPs) which include the contractors and other participants who have been hired under contract by the stakeholder to perform the work to complete the project or a portion thereof.
- PRPs Project responsible Parties
- the PRPs are responsible for periodically reporting the status and progress of the project to the stakeholder.
- PRPs gather data on a daily basis which reflects that amount of money spent, the materials used, the amount of time and degree of completion for each subproject or job as well as the project as a whole and prepare reports transmitted to the stakeholder which are intended to meet the reporting requirements of the contract.
- the PRPs either have specialized internal organizations or hire outside third parties that perform the data gathering and reporting functions.
- independent auditors can be called in, from time to time to audit and certify the data gathering and reporting functions.
- the present invention is directed to a method and system for monitoring and reporting the status and progress of a project.
- the project data which reflects the status and progress of the project is gathered and transferred to an independent data store that cannot be modified by the PRPs. This insures that the status and progress reporting functions are independent of the data gathering functions.
- the invention also includes a method and system which includes one or more rules that are used in the monitoring and reporting functions.
- the rules can be used to define variances in data points that are analyzed which result in the triggering of an event or the presentation of a status indicator.
- the data points can be data that is extracted directly from the source data, i.e. the project data, or the data points can be a function of the project data that is obtained from the source data.
- a rule or a set of rules can be defined which can use different types or sources of data or data points to trigger events or status indicators.
- the events can include the invocation of additional rules or processes that provide further analysis and/or status and progress monitoring and reporting functions.
- the present invention is also directed to a method and system for presenting the status and progress of the project to the stakeholder.
- the stakeholder can be provided with a customized display of the information concerning the status and progress of the project.
- the display can provide a single indicator of the status and/or the progress of the project to be monitored.
- the single indicator can comprise a colored indicator, wherein the different colors indicate different status levels or progress levels.
- the single indicator can include a set of symbols or icons, in which each symbol or icon is representative of a level of status or progress.
- Other indicators can include numeric values, words or terms that can be representative of the level of status or progress.
- FIG. 1 is a diagrammatic view of a system in accordance with the invention.
- FIG. 2 is a diagrammatic flowchart of a method in accordance with the invention.
- FIGS. 3 - 5 are diagrams of forms of the presentation dashboard in accordance with the invention.
- the present invention is directed to a method and system for monitoring and reporting the status and progress of a project.
- an illustrative embodiment of the invention, as applied to a construction project is set forth below.
- the stakeholder has contracted with several PRPs to complete the project that has been broken into several subprojects.
- the PRPs gather the data that is used for project status and progress reporting and an independent third party is tasked with reporting and presenting the status and progress of the project to the stakeholder.
- the method and system according to the invention provide for the oversight and management of the project as a function of selected performance data, independent of the Project responsible Parties (PRPs).
- PRPs Project responsible Parties
- all the participants to a specific project or projects who have a contract with the Stakeholder entity are designated as the PRPs.
- the data being collected by these parties can include project data that relates to characteristics of the project, such as schedule or time; budget, cost and revenue; quality inspection; safety inspection; and other project related performance information.
- the data being collected and the processing time is a clear contract requirement between the Stakeholder and the PRPs.
- the system and method in accordance with the invention can include comparing baseline estimates against actual quantities, which can be a combination of dollar, commodity or date quantities, and reporting variances between the actual quantities and the baseline estimate as well as trends as the project moves toward completion.
- the method and system provide for the electronic replication and transfer of project data from one or more client databases created and managed by the PRPs to an independent oversight server system database.
- the data transfer is uni-directional and the PRPs cannot modify the data in the independent oversight server system database.
- the data transferred is identical to the data that resides in the client database(s) as of the effective date of the data transfer.
- the oversight server system database is independent of all client server(s) and retains an accurate record of transferred project data at specific points of time and preserves the integrity of the imported data. Once the independent database system is populated, the data can be organized, analyzed, and/or selected in order to accomplish the data reporting and presentation functions.
- the method and system can electronically collect the data from one or more client databases contemporaneously and the oversight server system database can serve as a repository for contemporaneous project data and in effect become the general ledger of data transactions.
- the oversight server can collect the data as it is made available by the client databases, so that it is the most current and up-to-date data at the time it is collected.
- the project data can be collected from the client databases on regular or periodic intervals, e.g. the same time every day, week or month.
- This repository provides for the separation of the data entry function from the data analysis and the reporting functions in the independent oversight process.
- the method and system according to the invention can measure actual project performance, forecast project performance and report project performance using a rules-based methodology.
- the rules can be defined and established by one or more Stakeholders in order to closely correspond to their reporting requirements.
- the rules can provide the baseline from which selected data variance analyses are performed.
- the data can be project data or data derived from project data. When the variance exceeds the range or criteria established by the rule, an indicator can highlight where actual and/or forecast performance exceeds the baseline or threshold values.
- the system processes project data and generates performance indicator(s), which alerts the Stakeholder(s) on a variance or excessive variance from pre-established parameters, rules, or algorithms that define the expected project performance.
- This status, progress and/or performance of the project can be presented through a customized user interface to highlight current and forecast performance against pre-determined project performance objectives.
- the user interface can include indicator(s), such as a symbol, colored light, flag, sound, or any other alphanumeric or symbolic designation that notifies the Stakeholder whether the current and/or forecast performance is or is not in compliance with one or more of the predetermined rules established for that project.
- the method and system in accordance with the invention provide for a rules-based presentation that includes exception indicators to indicate management action.
- the rules based presentation can provide a presentation system analogous to a performance indicating dashboard.
- the performance dashboard can restrict the stakeholder to read-only access to the original data.
- the performance dashboard can include a keystroke interface, a mouse interface, a touch-screen interface, a voice-activated interface, an eye-movement-activated interface, or any other user interfaces developed.
- the performance dashboard can function as an electronic tool for performing “real time” management oversight.
- the real time reporting capabilities of the system may be limited due to the data entry and data collection capabilities of the project.
- PRPs provide real time project data that can be used to update the data used for performance monitoring and reporting (such as the independent oversight server database, although another non-independent system could be used), the system can provide real time monitoring and reporting functions.
- FIG. 1 shows a system 100 in accordance with the invention.
- the system 100 includes one or more PRP systems 110 , a project source database 112 , a data transfer system 114 , an oversight database 116 , an oversight system 130 , a network 140 and stakeholder workstation 150 .
- the oversight system 130 can include a data analysis component 132 , a rules processing component 134 , a data presentation component 136 and a rules database 138 .
- the PRP system 110 is adapted to collect the data relating to the performance of the project. Data can be collected manually (such as by manual data entry), semi-automatically (such as using barcode and magnetic stripe scanning systems) or automatically (such as electronic reporting and measuring systems, bank accounts, Electronic Data Interchange—“EDI”). While PRP system 110 is shown as a computer system, the PRP system 110 can be any device that provides for data entry including barcode and magnetic stripe scanning devices and handheld devices such as cellular telephones and so-called personal digital assistants (PDAs).
- PDAs personal digital assistants
- the project data can be stored in a client project database 112 which can be in any accessible format.
- the PRP system 110 is an IBM compatible personal computer configured with the Windows Operating system (available from Microsoft Corp., Redmond, Wash.).
- the PRP system can include a commercial database such as Access (available from Microsoft Corp., Redmond, Wash.) or an SQL database, or a proprietary system for collecting data can be provided.
- the project data can be stored in a project database 112 that serves as a central repository for all PRPs or each PRP can maintain its own project database for the project or portion of the project that it is managing.
- the system 100 further includes a data transfer system 114 that is adapted for replicating the project source database 112 in the oversight database 116 .
- the data transfer system 114 can be adapted for replicating each project source database 112 in the oversight database 116 .
- the data transfer system 114 can include a system and a procedure by which the data from the project source database 112 is replicated in the oversight database 116 .
- the data transfer system 114 can be as simple as a function that copies the project source database 112 and transmits the copy to the oversight database 116 or it can include a more complex database replication process.
- the data transfer system 114 can be adapted or configured to collect the project data from the source database on a periodic basis, for example, a daily basis or the data can be collected in real time as it changes. While, the data transfer system 114 can be adapted to replicate all the data in the project source database or databases 112 , it is not essential to the invention that all the data is transferred to the oversight database 116 . Where oversight is only required or being provided for a portion of a project, only the project data concerning the portion of the project being monitored need be replicated at the oversight database 116 .
- the oversight database 116 provides an independently controlled data source for the project data. As a result, if the project data is changed between the extractions from the source database 112 , the oversight database 116 can reflect the change as the difference in data between extraction transactions. In this regard, the oversight database 116 serves as the general ledger of data transactions of the project.
- the system 100 can further be provided with tools that allow the data to be audited, for example, on a transaction by transaction basis to identify anomalies and errors in the project data.
- the oversight system 130 can be connected to the oversight database 116 via any data connection, including a direct physical connection, a local area network, a storage area network or any wired or wireless communication technology.
- the oversight system 130 and the oversight database 116 can be connected to the stakeholder workstation 150 via a network 140 or any wired or wireless communication technology.
- the oversight system 130 can also include an analysis component 132 that is adapted for processing and analyzing the data stored in the oversight database 116 as may be necessary to provide the management and oversight reporting functions.
- the rules processing component 134 is adapted to apply the rules to either data stored in the oversight database 116 or data derived (such as by analysis component 132 ) from data stored in the oversight database 116 .
- the data presentation component 136 can interact with the rules processing component 134 in order to determine the state of the indicators provided in the performance dashboard.
- the oversight system 130 can also include a rules database 138 that can be used to store the rules used by the rules processing component 134 and the data presentation component 136 to report the status, progress and/or performance of the project to the stakeholder.
- the data analysis component 132 , the rules processing component 134 , the data presentation component 136 and the rules database 138 can reside on the oversight computer system 130 or they can each reside on a separate computer system that is connected to the others, such as via a private network or a public network, such as the Internet.
- the oversight system 130 can be run on a Microsoft Windows based desktop computer or a more powerful server computer (or cluster of server computers), operating under Windows 2000 Server or a Unix or Linux based Server.
- the oversight database 116 can be an SQL database that resides a Microsoft SQL Server 2000.
- the oversight system 130 can include a web server (such as Microsoft Internet Information Server) and be adapted to provide the project status, progress and performance reports as web pages accessed by a secure, access controlled transaction between the web server and the stakeholder workstation 150 .
- a separate web server (not shown), such as Microsoft Internet Information Server can be located between the oversight system 130 and the network 140 .
- the stakeholder workstation 150 can be any system that can access the oversight system 130 , such as a Microsoft Windows based personal computer with a web browser.
- the stakeholder workstation 150 can be connected to the oversight system 130 via a wired or wireless connection such as the Internet or a private network.
- the oversight system 130 can include a web server module (not shown) and be adapted to present the project status, progress or performance information in the form of one or more web pages.
- the stakeholder workstation 150 can be any web enabled device including, for example, a personal computer, a personal digital assistant (PDA) or a web enabled cellular telephone.
- PDA personal digital assistant
- the status, progress and/or performance can be simply reported in the form of a non-interactive display, such as an email message, or instant message, facsimile message or other report provided by a non-interactive media.
- a non-interactive display such as an email message, or instant message, facsimile message or other report provided by a non-interactive media.
- the stakeholder can simply receive a fax or an email which identifies those projects or subprojects which have an exception or a variance which exceeds the defined limits. The message can omit those projects or subprojects that do not have exceptions or variances.
- the project status, progress and/or performance reporting function can be accomplished using a dedicated application that produces reports in the project dashboard format.
- the dedicated application can reside on the oversight system 130 and the stakeholder workstation 150 can be connected to the oversight system 130 via a secure connection, such as a direct physical connection or a virtual private network connection.
- the dedicated application can reside on the stakeholder workstation 150 and receive presentation data from the oversight system 130 which can be used to generate the project reports.
- the method 200 according to the invention for monitoring and reporting the status and progress of a project can include the steps of applying the rules to the data to produce information representative of the status, progress and/or performance of the project and presenting the information representative of the status, progress and/or performance of the project to the stakeholder.
- the method 200 can include the steps of gathering and storing the project data 210 , transferring the project data to the oversight data store 212 , processing the data 214 ; applying the rules to the data in the oversight data store 216 , and presenting information representative of the project's status, progress or performance to the stakeholder.
- the data can be gathered by the PRPs, the stakeholder or a third party.
- the oversight data store 212 may not need to be the step of transferring the data the oversight data store 212 as the data can be directly input by the stakeholder or the third party into the oversight data store.
- it may not be necessary to further process the data at step 214 (except for retrieving or selectively retrieving the data used by a particular rule) if the data that is gathered and stored in a form in which the oversight system 130 can directly apply the rules to the data.
- the data is gathered and stored at step 210 in a format that permits the rules to applied to the data at step 216 without any further transfer or processing and the steps of transferring the data 212 to an oversight data store and further processing the data 214 can be omitted.
- the system at step 214 will need to process the data in that it will selectively retrieve (from wherever it is stored) the data need to for each rule. In some cases many data elements will be need, and in other cases only a few data elements will be needed.
- the data can be presented to a user of the system.
- the performance of the project as a function of the project data can be presented to the user as a single indicator, symbol or icon.
- the single indicator, symbol or icon can represent to the performance of one or more characteristics of the performance of the project with respect to one or more predefined rules.
- the rules can defined baseline values and rule variances which can be applied to select project data to determine whether the project data varies from the baseline and whether the variance is significant (greater than the rule variance) such that the user would consider the variance to outside the acceptable range or require the user to take some action.
- FIGS. 3 - 5 show a method and system for presenting information representative of the status, progress and/or performance of the project. This information can be determined by applying the rules to the project data. For example, for any project and each subproject, there can be an associated budget and a contingency for unexpected issues.
- the current dollar estimate for a subproject can be compared against the baseline dollar estimate that was used for budget planning purposes. Through a mathematical computation the variance between the current and baseline estimate is calculated. This calculated variance can be used to forewarn the stakeholder of its exposure relative to its baseline estimate. The stakeholder can take any of the following actions: ignore the issue, modify scope, adjust the program budget immediately, implement appropriate control mechanisms to ensure meeting the program budget objective.
- the actual installation rate can be compared against its planned installation rate.
- This rate may be, for example, represented in terms of dollars per time unit or commodities per time unit.
- the measured rate may be across multiple objectives or across a single program objective.
- Table 2 below provides an example that concerns time related metrics where the actual rate is less than the planned rate by $4000 per month. TABLE 2 Planned Rate ($/month) Actual Rate ($/month) Variance ($/month) 20,000.00 16,000.00 4,000.00
- a rule-based method can be applied wherein the variance calculation is compared against one or more pre-determined tolerance levels for the calculated variance.
- the comparison of the calculated variance and the tolerance level can trigger one or more system algorithms or processes that enable the variance to be represented in the dash board as a visual or audible performance indicator.
- the rule which can be defined by the stakeholder, can reflect the target expectations during project execution and can provide variability in alerting management by clearly identifying any exception.
- the variability may be a range of values around the target expectations, values above or below the target expectations, or any combination thereof.
- the system can provide that the rules can change over time such that a the variance or tolerance level can change over the course of the project or as a function of prior actual data or estimates of future data that can be revised over time.
- Table 3 below provides some examples of the application of rules to the variances determined in Tables 1 and 2 above.
- FIG. 3 shows a first level of a dash board 300 which includes a single indicator 310 that is representative of the status, progress and/or performance of several projects and subprojects 315 .
- the indicators 310 associated with Project 1 , Project 2 , Subproject A and Subproject C are a predefined color (such as green) and show that no variance has been exceeded or is expected to be exceeded at the current time.
- the indicators associated with Project 3 (shown in a different color such as yellow) and Subproject B (shown in yet another color such as red) indicate that a variance within the project has been or is likely to be exceeded. This form of presentation of information allows the stakeholder to view all the projects and subprojects and quickly assess which items require further consideration.
- the stakeholder can confidently move on to reviewing other projects.
- the stakeholder can, in accordance with the invention, investigate the source of the variances by “drilling down” into the information used to produce the indicators in order to identify the source of the variance or exception.
- the web page can be configured to allow the stakeholder to click on the project name (e.g. Project 1 ) or the indicator to “drill down” or view the next level to view more detailed information about the specific project.
- the next level can display all the elements or subprojects that are part of the project and contribute to the reporting indicator of the project.
- the system can selectively present only those elements or subprojects that exceed there variances resulting in the project being, for example, over budget or not on schedule.
- the next level can be presented on a web page that provides several indicators, each representative of different aspects of the project or subproject being reviewed, such as the budget, the schedule, the safety or the inspection/approval of the project or subproject.
- project dashboard can be configured to present different levels of displays depending upon the status of the indicators on the previous level.
- the drill down function can bring the stakeholder to a second level which presents indicators of the individual aspects of the project or subprojects that where considered in the presenting the previous level, whereas when a project indicates a variance or exception, the drill down function can immediately bring the stakeholder to the web page the presents the specific aspect of the project or subproject that indicated or is the basis for the variance or exception.
- FIG. 4 shows an alternative embodiment wherein the project dashboard 400 shows the individual elements or aspects of the project for which rules have been defined and applied to the project data.
- the status of both the time schedule and the budget for each project and subproject can be presented together.
- the stakeholder can define the project elements or aspects that are to be monitored and the status, progress or performance of each separate element can be presented as a separate indicator. Similar to the embodiment above, the stakeholder can review the details of each element on a separate screen or separate level.
- FIG. 5 shows a second level of a project dashboard 500 , in which the project being reviewed (e.g. Project 2 of FIG. 4) has indicated a variance or exception (for example, by a red indicator) in the time schedule.
- the second level of the project dashboard can include more detailed information about each of the subprojects that make up a given project.
- Subproject A shown, for example, with a red time indicator
- the illustrative example also shows, with respect to Subproject B that there is a positive variance or exception (shown, for example, by a yellow indicator) in this subproject, specifically the subproject is 5 days ahead and is $5000 under budget.
- the positive variance can be indicated by another color, such as blue, in order to distinguish it from yellow which indicates a negative variance.
- the budget indicator has not changed, probably because the $5000 variance is below the level that would change the budget indicator, but that the time schedule indicator did change (to indicate a positive variance), probably because the 5 day variance exceeds the level that would change the time schedule indicator.
- the comment also indicates that subproject B is awaiting materials, suggesting that if the subproject might stay ahead of schedule if materials could be delivered within the 5 day lead.
- the project dashboard can use symbols or icons that represent the status of a characteristic of a project. For example, a set of arrows, up arrow indicating a positive variance, a horizontal arrow indicating no variance and a down arrow indicating a negative variance. A set of symbols or icons, such as a thumbs up, thumbs down can be used.
- the symbol can be presented along with one or more numeric values indicating, for example, planned baseline, the variance defined by the rule, variance according to the project data; and/or how the project data deviates with respect to the baseline and/or the variance.
- the method and system can include additional steps or processes that can be used to extract the source data from the project or client database and convert it to a format that facilitates analysis and/or the application of the rules which provide for the dash board reporting.
- Attached hereto as Appendices A through J are specifications for a system and method in accordance with the invention.
- Appendices A and B include a flow chart and a description of an alternative method for processing the project data from a client database.
- Appendices C and D provide a description of a system architecture in accordance with the invention.
- Appendix E provides a description of system for transferring data from the source database to the oversight database in accordance with the invention.
- Appendix F provides a description of a system for presenting data in accordance with the invention.
- Appendix G provides a description of system security in accordance with the invention.
- Appendices H, I and J provide a description of the data structures and designs for a system in accordance with the invention.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/314,678 US20030135481A1 (en) | 2001-12-07 | 2002-12-09 | Rules based method and system for project performance monitoring |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US33838801P | 2001-12-07 | 2001-12-07 | |
US10/314,678 US20030135481A1 (en) | 2001-12-07 | 2002-12-09 | Rules based method and system for project performance monitoring |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030135481A1 true US20030135481A1 (en) | 2003-07-17 |
Family
ID=23324623
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/314,678 Abandoned US20030135481A1 (en) | 2001-12-07 | 2002-12-09 | Rules based method and system for project performance monitoring |
Country Status (5)
Country | Link |
---|---|
US (1) | US20030135481A1 (fr) |
EP (1) | EP1451744A4 (fr) |
AU (1) | AU2002366554A1 (fr) |
CA (1) | CA2468825A1 (fr) |
WO (1) | WO2003050656A2 (fr) |
Cited By (53)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030088943A1 (en) * | 2001-10-31 | 2003-05-15 | Hubert Neukotter | Door hinge for a covered arrangement between door post and door |
US20030225602A1 (en) * | 2002-05-31 | 2003-12-04 | Thomas Hagmann | Perspective representations of processes |
US20030222896A1 (en) * | 2002-05-31 | 2003-12-04 | Thomas Hagmann | Dynamic representations of processes |
US20040119752A1 (en) * | 2002-12-23 | 2004-06-24 | Joerg Beringer | Guided procedure framework |
US20040133413A1 (en) * | 2002-12-23 | 2004-07-08 | Joerg Beringer | Resource finder tool |
US20040131050A1 (en) * | 2002-12-23 | 2004-07-08 | Joerg Beringer | Control center pages |
US20050198486A1 (en) * | 2004-01-20 | 2005-09-08 | Accenture Global Services Gmbh | Information technology development transformation |
US20050289051A1 (en) * | 2004-06-29 | 2005-12-29 | Allin Patrick J | Construction payment management system and method |
US20070016456A1 (en) * | 2005-07-12 | 2007-01-18 | International Business Machines Corporation | System, method and program product for reporting status of contract performance or a process |
US20070078771A1 (en) * | 2004-06-29 | 2007-04-05 | Allin Patrick J | Construction payment management system and method with document tracking features |
US20070130113A1 (en) * | 2005-10-11 | 2007-06-07 | Ting Heng T | Method and system for navigation and visualization of data in relational and/or multidimensional databases |
US20070198556A1 (en) * | 2006-02-21 | 2007-08-23 | Lawson Software, Inc. | Data unification models |
US7274375B1 (en) * | 2002-11-19 | 2007-09-25 | Peter David | Timekeeping system and method for graphically tracking and representing activities |
US20070276693A1 (en) * | 2004-09-02 | 2007-11-29 | Cox Gregory F | Method for providing both automated and on demand project performance measurements |
US20070288290A1 (en) * | 2006-06-07 | 2007-12-13 | Tetsuro Motoyama | Use of a database in a network-based project schedule management system |
US20070288288A1 (en) * | 2006-06-07 | 2007-12-13 | Tetsuro Motoyama | Use of schedule editors in a network-based project schedule management system |
US20080027789A1 (en) * | 2006-07-31 | 2008-01-31 | Carsten Busch | Generating a View of Measured Performance |
US20080046350A1 (en) * | 2004-06-29 | 2008-02-21 | Textura, Llc | Construction payment management system and method with automated electronic document generation features |
US20080137550A1 (en) * | 2006-12-11 | 2008-06-12 | Radu Jurca | System and method for monitoring quality of service |
US20080255907A1 (en) * | 2007-03-15 | 2008-10-16 | Ricoh Company, Ltd. | Class object wrappers for document object model (DOM) elements for project task management system for managing project schedules over a network |
US20080281735A1 (en) * | 2004-06-29 | 2008-11-13 | Allin Patrick J | Construction payment management system and method with document exchange features |
US20080313595A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for estimating project plans for packaged software applications |
US20080313110A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for self-calibrating project estimation models for packaged software applications |
US20080312980A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for staffing and cost estimation models aligned with multi-dimensional project plans for packaged software applications |
US20080313008A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for model-driven approaches to generic project estimation models for packaged software applications |
US20080313596A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for evaluating multi-dimensional project plans for implementing packaged software applications |
US20080312979A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for estimating financial benefits of packaged application service projects |
US20090083104A1 (en) * | 2003-07-10 | 2009-03-26 | Computer Associates Think, Inc. | Single point of entry for web applications |
US20090287522A1 (en) * | 2008-05-16 | 2009-11-19 | Tetsuro Motoyama | To-Do List Representation In The Database Of A Project Management System |
US20090287521A1 (en) * | 2008-05-16 | 2009-11-19 | Tetsuro Motoyama | Managing Project Schedule Data Using Separate Current And Historical Task Schedule Data |
US20090287730A1 (en) * | 2008-05-16 | 2009-11-19 | Tetsuro Motoyama | Managing To-Do Lists In Task Schedules In A Project Management System |
US20090287731A1 (en) * | 2008-05-16 | 2009-11-19 | Tetsuro Motoyama | Managing To-Do Lists In A Schedule Editor In A Project Management System |
US20090287718A1 (en) * | 2008-05-16 | 2009-11-19 | Tetsuro Motoyama | Managing Project Schedule Data Using Separate Current And Historical Task Schedule Data And Revision Numbers |
EP2137643A1 (fr) * | 2007-04-10 | 2009-12-30 | Heng Toon Ting | Procédé et système pour une navigation et une visualisation de données dans des bases de données relationnelles et/ou multidimensionnelles |
US20100070321A1 (en) * | 2008-09-16 | 2010-03-18 | Tetsuro Motoyama | Project Management System With Inspection Functionality |
US7953625B2 (en) | 2002-10-29 | 2011-05-31 | Sap Aktiengesellschaft | Available resource presentation |
US20110184771A1 (en) * | 2010-01-28 | 2011-07-28 | Wells Robert Frances | Implementation resource project management |
US20120226510A1 (en) * | 2011-03-03 | 2012-09-06 | Enterprise Signal Inc. | System and method for providing project status metrics |
US8306883B2 (en) | 2007-04-30 | 2012-11-06 | Textura Corporation | Construction payment management systems and methods with specified billing features |
US20120323605A1 (en) * | 2010-12-22 | 2012-12-20 | Toshiba Medical Systems Corporation | Medical image processing system |
US8407078B1 (en) | 2009-01-20 | 2013-03-26 | Perot Systems Corporation | Method of and system for managing projects, programs and portfolios throughout the project lifecycle |
US20130198676A1 (en) * | 2011-12-22 | 2013-08-01 | Dental Equipment, Llc | Method and system for interactive computer-implemented project management |
US8533027B1 (en) * | 2004-07-30 | 2013-09-10 | Hewlett-Packard Development Company, L.P. | User interface enabling approval/disappoval of revised contract performance indicators |
US20140053127A1 (en) * | 2012-08-17 | 2014-02-20 | Hartford Fire Insurance Company | System and method for monitoring software development and program flow |
US8666794B1 (en) * | 2007-03-26 | 2014-03-04 | Sprint Communications Company L.P. | Project management tool |
US20140142990A1 (en) * | 2012-11-19 | 2014-05-22 | Syntel, Inc. | Performance measurement reporting system and method for insurance industry |
US8826282B2 (en) | 2007-03-15 | 2014-09-02 | Ricoh Company, Ltd. | Project task management system for managing project schedules over a network |
US20140344353A1 (en) * | 2013-05-17 | 2014-11-20 | International Business Machines Corporation | Relevant Commentary for Media Content |
US20140350985A1 (en) * | 2013-05-24 | 2014-11-27 | Construx Solutions Advisory Group Llc | Systems, methods, and computer programs for providing integrated critical path method schedule management & data analytics |
US9378115B2 (en) * | 2014-09-18 | 2016-06-28 | Sap Se | Base line for code analysis |
US9378478B2 (en) * | 2014-09-19 | 2016-06-28 | Tata Consultancy Services Limited | System and method for facilitating quality assurance of a software application |
WO2017004104A1 (fr) * | 2015-07-01 | 2017-01-05 | Schlumberger Technology Corporation | Procédé et système permettant une gestion d'offre de service |
CN114722789A (zh) * | 2022-04-07 | 2022-07-08 | 平安科技(深圳)有限公司 | 数据报表集成方法、装置、电子设备及存储介质 |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070130328A1 (en) * | 2005-12-07 | 2007-06-07 | Nickolaou James N | Progress tracking method for uptime improvement |
CA2708911C (fr) | 2009-07-09 | 2016-06-28 | Accenture Global Services Gmbh | Systeme de determination d'un modele de commercialisation |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5226118A (en) * | 1991-01-29 | 1993-07-06 | Prometrix Corporation | Data analysis system and method for industrial process control systems |
US5726914A (en) * | 1993-09-01 | 1998-03-10 | Gse Systems, Inc. | Computer implemented process and computer architecture for performance analysis |
US5826252A (en) * | 1996-06-28 | 1998-10-20 | General Electric Company | System for managing multiple projects of similar type using dynamically updated global database |
US5907490A (en) * | 1997-06-10 | 1999-05-25 | Electronic Data Systems Corporation | System and method for project management and assessment |
US5970476A (en) * | 1996-09-19 | 1999-10-19 | Manufacturing Management Systems, Inc. | Method and apparatus for industrial data acquisition and product costing |
US6036345A (en) * | 1993-03-11 | 2000-03-14 | Lear Corporation | Design and engineering project management system |
US6308164B1 (en) * | 1997-04-28 | 2001-10-23 | Jeff Nummelin | Distributed project management system and method |
US6591278B1 (en) * | 2000-03-03 | 2003-07-08 | R-Objects, Inc. | Project data management system and method |
-
2002
- 2002-12-09 AU AU2002366554A patent/AU2002366554A1/en not_active Abandoned
- 2002-12-09 EP EP02791405A patent/EP1451744A4/fr not_active Withdrawn
- 2002-12-09 US US10/314,678 patent/US20030135481A1/en not_active Abandoned
- 2002-12-09 CA CA002468825A patent/CA2468825A1/fr not_active Abandoned
- 2002-12-09 WO PCT/US2002/039553 patent/WO2003050656A2/fr not_active Application Discontinuation
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5226118A (en) * | 1991-01-29 | 1993-07-06 | Prometrix Corporation | Data analysis system and method for industrial process control systems |
US6036345A (en) * | 1993-03-11 | 2000-03-14 | Lear Corporation | Design and engineering project management system |
US5726914A (en) * | 1993-09-01 | 1998-03-10 | Gse Systems, Inc. | Computer implemented process and computer architecture for performance analysis |
US5826252A (en) * | 1996-06-28 | 1998-10-20 | General Electric Company | System for managing multiple projects of similar type using dynamically updated global database |
US5970476A (en) * | 1996-09-19 | 1999-10-19 | Manufacturing Management Systems, Inc. | Method and apparatus for industrial data acquisition and product costing |
US6308164B1 (en) * | 1997-04-28 | 2001-10-23 | Jeff Nummelin | Distributed project management system and method |
US5907490A (en) * | 1997-06-10 | 1999-05-25 | Electronic Data Systems Corporation | System and method for project management and assessment |
US6591278B1 (en) * | 2000-03-03 | 2003-07-08 | R-Objects, Inc. | Project data management system and method |
Cited By (96)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030088943A1 (en) * | 2001-10-31 | 2003-05-15 | Hubert Neukotter | Door hinge for a covered arrangement between door post and door |
US7983940B2 (en) * | 2002-05-31 | 2011-07-19 | Sap Aktiengesellschaft | Perspective representations of processes |
US20030225602A1 (en) * | 2002-05-31 | 2003-12-04 | Thomas Hagmann | Perspective representations of processes |
US20030222896A1 (en) * | 2002-05-31 | 2003-12-04 | Thomas Hagmann | Dynamic representations of processes |
US8015046B2 (en) | 2002-05-31 | 2011-09-06 | Sap Aktiengesellschaft | Dynamic representations of processes |
US7953625B2 (en) | 2002-10-29 | 2011-05-31 | Sap Aktiengesellschaft | Available resource presentation |
US7274375B1 (en) * | 2002-11-19 | 2007-09-25 | Peter David | Timekeeping system and method for graphically tracking and representing activities |
US20040133413A1 (en) * | 2002-12-23 | 2004-07-08 | Joerg Beringer | Resource finder tool |
US7849175B2 (en) | 2002-12-23 | 2010-12-07 | Sap Ag | Control center pages |
US8095411B2 (en) * | 2002-12-23 | 2012-01-10 | Sap Ag | Guided procedure framework |
US8195631B2 (en) | 2002-12-23 | 2012-06-05 | Sap Ag | Resource finder tool |
US20040131050A1 (en) * | 2002-12-23 | 2004-07-08 | Joerg Beringer | Control center pages |
US20040119752A1 (en) * | 2002-12-23 | 2004-06-24 | Joerg Beringer | Guided procedure framework |
US20090083104A1 (en) * | 2003-07-10 | 2009-03-26 | Computer Associates Think, Inc. | Single point of entry for web applications |
US8271614B2 (en) * | 2003-07-10 | 2012-09-18 | Ca, Inc. | Single point of entry for web applications |
US20050198486A1 (en) * | 2004-01-20 | 2005-09-08 | Accenture Global Services Gmbh | Information technology development transformation |
US10621566B2 (en) | 2004-06-29 | 2020-04-14 | Textura Corporation | Construction payment management system and method with automatic notification workflow features |
US20060271477A1 (en) * | 2004-06-29 | 2006-11-30 | Allin Patrick J | Construction payment management system and method with real-time draw notification features |
US7925584B2 (en) | 2004-06-29 | 2011-04-12 | Textura Corporation | Construction payment management system and method with document tracking features |
US7899739B2 (en) | 2004-06-29 | 2011-03-01 | Textura Corporation | Construction payment management system and method with real-time draw notification features |
US20050289051A1 (en) * | 2004-06-29 | 2005-12-29 | Allin Patrick J | Construction payment management system and method |
US7818250B2 (en) | 2004-06-29 | 2010-10-19 | Textura Corporation | Construction payment management system and method with automatic workflow management features |
US20080046350A1 (en) * | 2004-06-29 | 2008-02-21 | Textura, Llc | Construction payment management system and method with automated electronic document generation features |
US7797210B2 (en) | 2004-06-29 | 2010-09-14 | Textura Corporation | Construction payment management system and method with graphical user interface features |
US7734546B2 (en) | 2004-06-29 | 2010-06-08 | Textura Corporation | Construction payment management system and method with hierarchical invoicing and direct payment features |
US20080281735A1 (en) * | 2004-06-29 | 2008-11-13 | Allin Patrick J | Construction payment management system and method with document exchange features |
US10453039B2 (en) | 2004-06-29 | 2019-10-22 | Textura Corporation | Construction payment management system and method with draw notification features |
US9355417B2 (en) | 2004-06-29 | 2016-05-31 | Textura Corporation | Construction payment management system and method with draw notification features |
US9336542B2 (en) | 2004-06-29 | 2016-05-10 | Textura Corporation | Construction payment management system and method with automatic notification workflow features |
US7725384B2 (en) | 2004-06-29 | 2010-05-25 | Textura Corporation | Construction payment management system and method with one-time registration features |
US7672888B2 (en) | 2004-06-29 | 2010-03-02 | Textura Corporation | Construction payment management system and method with automated electronic document generation features |
US20070078771A1 (en) * | 2004-06-29 | 2007-04-05 | Allin Patrick J | Construction payment management system and method with document tracking features |
US7490064B2 (en) | 2004-06-29 | 2009-02-10 | Textura Corporation | Construction payment management system and method with budget reconciliation features |
US7983972B2 (en) | 2004-06-29 | 2011-07-19 | Textura Corporation | Construction payment management system and method with graphical user interface features |
US20060271478A1 (en) * | 2004-06-29 | 2006-11-30 | Allin Patrick J | Construction payment management system and method with hierarchical invoicing and direct payment features |
US20060271397A1 (en) * | 2004-06-29 | 2006-11-30 | Allin Patrick J | Construction payment management system and method with automatic workflow management features |
US20060271479A1 (en) * | 2004-06-29 | 2006-11-30 | Allin Patrick J | Construction payment management system and method with budget reconciliation features |
US8533027B1 (en) * | 2004-07-30 | 2013-09-10 | Hewlett-Packard Development Company, L.P. | User interface enabling approval/disappoval of revised contract performance indicators |
US8103948B2 (en) | 2004-09-02 | 2012-01-24 | International Business Machines Corporation | Method for providing both automated and on demand project performance measurements |
US20070276693A1 (en) * | 2004-09-02 | 2007-11-29 | Cox Gregory F | Method for providing both automated and on demand project performance measurements |
US7315977B2 (en) | 2004-09-02 | 2008-01-01 | International Business Machines Corporation | Storing, updating, and reporting on migration data using automated agents |
US20070016456A1 (en) * | 2005-07-12 | 2007-01-18 | International Business Machines Corporation | System, method and program product for reporting status of contract performance or a process |
US9336267B2 (en) * | 2005-10-11 | 2016-05-10 | Heng Toon Ting | Method and system for navigation and visualization of data in relational and/or multidimensional databases |
US20070130113A1 (en) * | 2005-10-11 | 2007-06-07 | Ting Heng T | Method and system for navigation and visualization of data in relational and/or multidimensional databases |
US20070198556A1 (en) * | 2006-02-21 | 2007-08-23 | Lawson Software, Inc. | Data unification models |
US8050953B2 (en) | 2006-06-07 | 2011-11-01 | Ricoh Company, Ltd. | Use of a database in a network-based project schedule management system |
US20070288288A1 (en) * | 2006-06-07 | 2007-12-13 | Tetsuro Motoyama | Use of schedule editors in a network-based project schedule management system |
US20070288290A1 (en) * | 2006-06-07 | 2007-12-13 | Tetsuro Motoyama | Use of a database in a network-based project schedule management system |
US20080027789A1 (en) * | 2006-07-31 | 2008-01-31 | Carsten Busch | Generating a View of Measured Performance |
US20080137550A1 (en) * | 2006-12-11 | 2008-06-12 | Radu Jurca | System and method for monitoring quality of service |
US8843385B2 (en) * | 2006-12-11 | 2014-09-23 | Ecole Polytechnique Federale De Lausanne (Epfl) | Quality of service monitoring of a service level agreement using a client based reputation mechanism encouraging truthful feedback |
US20080255907A1 (en) * | 2007-03-15 | 2008-10-16 | Ricoh Company, Ltd. | Class object wrappers for document object model (DOM) elements for project task management system for managing project schedules over a network |
US9152433B2 (en) | 2007-03-15 | 2015-10-06 | Ricoh Company Ltd. | Class object wrappers for document object model (DOM) elements for project task management system for managing project schedules over a network |
US8826282B2 (en) | 2007-03-15 | 2014-09-02 | Ricoh Company, Ltd. | Project task management system for managing project schedules over a network |
US8666794B1 (en) * | 2007-03-26 | 2014-03-04 | Sprint Communications Company L.P. | Project management tool |
EP2137643A4 (fr) * | 2007-04-10 | 2012-03-21 | Heng Toon Ting | Procédé et système pour une navigation et une visualisation de données dans des bases de données relationnelles et/ou multidimensionnelles |
EP2137643A1 (fr) * | 2007-04-10 | 2009-12-30 | Heng Toon Ting | Procédé et système pour une navigation et une visualisation de données dans des bases de données relationnelles et/ou multidimensionnelles |
US8306883B2 (en) | 2007-04-30 | 2012-11-06 | Textura Corporation | Construction payment management systems and methods with specified billing features |
US20080313110A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for self-calibrating project estimation models for packaged software applications |
US20080313595A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for estimating project plans for packaged software applications |
US20080313008A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for model-driven approaches to generic project estimation models for packaged software applications |
US7971180B2 (en) | 2007-06-13 | 2011-06-28 | International Business Machines Corporation | Method and system for evaluating multi-dimensional project plans for implementing packaged software applications |
US20080312980A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for staffing and cost estimation models aligned with multi-dimensional project plans for packaged software applications |
US8006223B2 (en) | 2007-06-13 | 2011-08-23 | International Business Machines Corporation | Method and system for estimating project plans for packaged software applications |
US20080312979A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for estimating financial benefits of packaged application service projects |
US8290806B2 (en) | 2007-06-13 | 2012-10-16 | International Business Machines Corporation | Method and system for estimating financial benefits of packaged application service projects |
US8055606B2 (en) * | 2007-06-13 | 2011-11-08 | International Business Machines Corporation | Method and system for self-calibrating project estimation models for packaged software applications |
US8032404B2 (en) | 2007-06-13 | 2011-10-04 | International Business Machines Corporation | Method and system for estimating financial benefits of packaged application service projects |
US20080313596A1 (en) * | 2007-06-13 | 2008-12-18 | International Business Machines Corporation | Method and system for evaluating multi-dimensional project plans for implementing packaged software applications |
US8352498B2 (en) | 2008-05-16 | 2013-01-08 | Ricoh Company, Ltd. | Managing to-do lists in a schedule editor in a project management system |
US20090287730A1 (en) * | 2008-05-16 | 2009-11-19 | Tetsuro Motoyama | Managing To-Do Lists In Task Schedules In A Project Management System |
US8321257B2 (en) | 2008-05-16 | 2012-11-27 | Ricoh Company, Ltd. | Managing project schedule data using separate current and historical task schedule data |
US20090287718A1 (en) * | 2008-05-16 | 2009-11-19 | Tetsuro Motoyama | Managing Project Schedule Data Using Separate Current And Historical Task Schedule Data And Revision Numbers |
US8706768B2 (en) | 2008-05-16 | 2014-04-22 | Ricoh Company, Ltd. | Managing to-do lists in task schedules in a project management system |
US20090287522A1 (en) * | 2008-05-16 | 2009-11-19 | Tetsuro Motoyama | To-Do List Representation In The Database Of A Project Management System |
US20090287731A1 (en) * | 2008-05-16 | 2009-11-19 | Tetsuro Motoyama | Managing To-Do Lists In A Schedule Editor In A Project Management System |
US20090287521A1 (en) * | 2008-05-16 | 2009-11-19 | Tetsuro Motoyama | Managing Project Schedule Data Using Separate Current And Historical Task Schedule Data |
US20100070321A1 (en) * | 2008-09-16 | 2010-03-18 | Tetsuro Motoyama | Project Management System With Inspection Functionality |
US8862489B2 (en) * | 2008-09-16 | 2014-10-14 | Ricoh Company, Ltd. | Project management system with inspection functionality |
US8407078B1 (en) | 2009-01-20 | 2013-03-26 | Perot Systems Corporation | Method of and system for managing projects, programs and portfolios throughout the project lifecycle |
US20110184771A1 (en) * | 2010-01-28 | 2011-07-28 | Wells Robert Frances | Implementation resource project management |
US20120323605A1 (en) * | 2010-12-22 | 2012-12-20 | Toshiba Medical Systems Corporation | Medical image processing system |
US10685087B2 (en) * | 2010-12-22 | 2020-06-16 | Canon Medical Systems Corporation | Medical image processing system |
US20120226510A1 (en) * | 2011-03-03 | 2012-09-06 | Enterprise Signal Inc. | System and method for providing project status metrics |
US20130198676A1 (en) * | 2011-12-22 | 2013-08-01 | Dental Equipment, Llc | Method and system for interactive computer-implemented project management |
US10255066B2 (en) | 2012-08-17 | 2019-04-09 | Hartford Fire Insurance Company | System and method for monitoring software development and program flow |
US20140053127A1 (en) * | 2012-08-17 | 2014-02-20 | Hartford Fire Insurance Company | System and method for monitoring software development and program flow |
US9134999B2 (en) * | 2012-08-17 | 2015-09-15 | Hartford Fire Insurance Company | System and method for monitoring software development and program flow |
US20140142990A1 (en) * | 2012-11-19 | 2014-05-22 | Syntel, Inc. | Performance measurement reporting system and method for insurance industry |
US9509758B2 (en) * | 2013-05-17 | 2016-11-29 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Relevant commentary for media content |
US20140344353A1 (en) * | 2013-05-17 | 2014-11-20 | International Business Machines Corporation | Relevant Commentary for Media Content |
US20140350985A1 (en) * | 2013-05-24 | 2014-11-27 | Construx Solutions Advisory Group Llc | Systems, methods, and computer programs for providing integrated critical path method schedule management & data analytics |
US9378115B2 (en) * | 2014-09-18 | 2016-06-28 | Sap Se | Base line for code analysis |
US9378478B2 (en) * | 2014-09-19 | 2016-06-28 | Tata Consultancy Services Limited | System and method for facilitating quality assurance of a software application |
WO2017004104A1 (fr) * | 2015-07-01 | 2017-01-05 | Schlumberger Technology Corporation | Procédé et système permettant une gestion d'offre de service |
CN114722789A (zh) * | 2022-04-07 | 2022-07-08 | 平安科技(深圳)有限公司 | 数据报表集成方法、装置、电子设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
WO2003050656A2 (fr) | 2003-06-19 |
EP1451744A4 (fr) | 2008-10-29 |
AU2002366554A1 (en) | 2003-06-23 |
EP1451744A2 (fr) | 2004-09-01 |
WO2003050656A3 (fr) | 2003-09-12 |
CA2468825A1 (fr) | 2003-06-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20030135481A1 (en) | Rules based method and system for project performance monitoring | |
US12038978B2 (en) | Annotation of data in an operating plan data aggregation system | |
Larcker et al. | ESG ratings: A compass without direction | |
US20170147960A1 (en) | Systems and Methods for Project Planning and Management | |
US8234136B2 (en) | Document processes of an organization | |
US8041647B2 (en) | System and method for an automated project office and automatic risk assessment and reporting | |
US7805497B2 (en) | Method and product for calculating a net operating income audit and for enabling substantially identical audit practices among a plurality of audit firms | |
US20070055596A1 (en) | System for preparing financial disclosures by unifying financial close and financial control steps | |
US20150227869A1 (en) | Risk self-assessment tool | |
US20150227868A1 (en) | Risk self-assessment process configuration using a risk self-assessment tool | |
EP1692648A1 (fr) | Systemes et procedes d'organisation et de gestion de flux de travaux | |
US20140025593A1 (en) | Compliance Analysis System | |
US20140129286A1 (en) | Analyzing Operational Results Using Rule-Based Policy Models | |
US20100121746A1 (en) | Financial statement risk assessment and management system and method | |
AU2020100138A4 (en) | System and Method for Identifying, Analysing and Managing Risk for Products in the supply network | |
US20100179898A1 (en) | Methods and systems of purchase contract price adjustment calculation tools | |
Iskandar et al. | Financial management performance of public sector: quality of internal auditor | |
Cha | GAO cost estimating and assessment guide: Best practices for developing and managing capital program costs | |
Leonard | GAO Cost estimating and assessment guide: Best practices for developing and managing capital program costs | |
US20080183743A1 (en) | Method and computer based system for performance management | |
Estiyanti | Audit of Accounting Information System Governance Using the Cobit 5 Framework (Case Study: CV. XYZS) | |
Hussain | CONTINUOUS QUALITY IMPROVEMENT OF FINANCIAL REPORTING USING TOTAL QUALITY MANAGEMENT (TQM) | |
JP2004157693A (ja) | リスク管理方法、リスク管理システム、及びそのプログラム | |
JP2003296535A (ja) | 環境会計システム、そのサーバ、クライアント、環境会計装置、環境会計方法、プログラム、及びそのプログラムを記録した記録媒体 | |
JP2002203088A (ja) | 環境マネジメント支援システム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |