|Publication number||USRE38633 E1|
|Application number||US 09/137,186|
|Publication date||Oct 19, 2004|
|Filing date||Aug 20, 1998|
|Priority date||Mar 17, 1994|
|Also published as||US5548506|
|Publication number||09137186, 137186, US RE38633 E1, US RE38633E1, US-E1-RE38633, USRE38633 E1, USRE38633E1|
|Inventors||Seshan R. Srinivasan|
|Original Assignee||Srinivasan Seshan R|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (8), Non-Patent Citations (16), Referenced by (78), Classifications (20), Legal Events (2)|
|External Links: USPTO, USPTO Assignment, Espacenet|
1. Cross-references to Related Applications
A patent search revealed no patent under the categories, Automatic Project Management, or under Electronic Mail based Project Management or Groupware Project Management.
The category Project Management revealed two patents:
(1) U.S. Pat. No. 4,451,067, A Comprehensive Central Scheduling Folder for Project Management offers a non-computerized method for planning and tracking projects. This has no similarity with the proposed electronic network based project management system, as it does not involve computers.
(2) U.S. Pat. No. 4,875,162, An Automated Interface of Design Software with Project Management Software. The scope of this is narrow, focuses on design organizations only and involves automatic status update of files between design software and project Management software. This is not for general purpose management of multiple work-groups. Also it does not address the design of a general purpose auto-server for project management, which will perform automatic project database creation, project follow-up, multi-project resource planning and project reporting.
2. Field of Invention
The invention described here is the design and application of an electronic network based project management server system. The product termed in this application as an ‘AUTO MULTI-PROJECT SERVER’. The use of the product will result in an improved organizational process for compiling, tracking and managing multiple projects within an organization.
The goal of the ‘Auto Multi-Project Server’ is to act as an automated computer based project coordinator to manage the goals of multiple organizational work-teams. Activities of the automated computer based server comprise of collating/compiling project data, flagging inconsistencies, follow-up with work-team members, obtain updated project tracking data, communicate project progress to work-team, resolve inter-project conflicts by re-allocation of critical resources based on project priorities and generate management reports for flagging time and cost overruns and critical path information.
Future re-engineered corporations will demand heavy computing needs for managing large number of work-teams with different project goals, schedules, dependencies and priorities running simultaneously. The present techniques for static project-management tools and for limited project-management groupware technologies will no longer be adequate.
3. Discussion of Prior Art
Presently the following types of project management systems are available:
1. Project planning tools, with software for generating charts such as Gantt, Pert/CPM etc. Many of the techniques were invented during the Second World War Majority of project management is perceived as belonging to this area. These are static standalone tools and do not impose any particular process in the organization. Organizations have to figure out methods for input, tracking and report distribution. Typically a project coordinator is hired by organizations to manually compile input data, run the tools and distribute progress reports.
Examples: Commercial tools such as PRIMAVERA and MICROSOFT-PROJECT offer computerized static software approach to planning projects, i.e. a person has to supervise the input data collection and output report generation, and there is no automatic process specified by the manufacturer.
A survey of existing project management tools showed no use of electronic mail or faxing methods to do any automatic creation, updating, planning or reporting. (Reference: DATAMATION—Oct. 1, 1993, Article: Project Management Software that's IS friendly, has a survey of the capabilities of Project Management tools and there is no mention of any automatic server based tools, driven by electronic messaging.)
2. Group collaboration and Work flow management tools, provide technologies to automate the flow of documents. These are directed at a wide variety of needs such as facilitating group conferences, meetings' management, project database management, information flow control and other custom mail enabled applications. The tools by themselves do not impose any organizational process, but offer an underlying technology to build applications, including the design proposed by this patent.
Example (1): U.S. Pat. No. 5,168,444 for a Work-flow shipment system, including processing of document images. This is not related to automatic project management for multiple work-groups.
Example (2) Lotus NOTES is a leading groupware product offering the necessary technology to build organizational processes including Project Tracking examples. The system is not designed to handle large multi-project/multi-priority environments. There is no automatic system proposed by the manufacturer and it is left for each organization to design its own process or system of project management.
Example (3) The nearest commercial product design is a product called SYZYGY from Information Research Corp., which builds on inherent capability of local area networks (LAN) to tie workers together. The system has a central database on organizational projects and can be automatically be programmed by managers to broadcast reminder messages. (Reference: Personal Computing, Volume 14, Issue 4, Date: Apr. 27, 1990, Page: 152), The differences I see between this product and the invention under this patent:
Syzygy is not ideal for managing large or complex projects since it lacks critical path analysis. The invention under this patent includes a complete computation engine for computing critical path activities,
Syzygy does not do complex inter-task dependency computations.
Syzygy is not targeted for multiple work-teams with inter-conflicting priorities.
Syzygy does not attempt any resources leveling or resource re-allocation.
The product in this patent application the ‘Auto Multi-Project Server’ consists of a centralized automatic project management server software, based in a computer and accessible via electronic mail or fax messages.
No Programming is involved by people using the system, the ‘Auto Multi-Project Server’ automatically computes task completion/start dates and triggers messages based on data mailed to it. Thus the data itself is used to program the ‘Auto Multi-Project Server’.
The ‘Auto Multi-Project Server’ reads electronic mail or fax messages, such as project plans and flags project data inconsistencies. It then compiles project management data into a usable project database with information to include details on goals, milestones, budgets etc.
The ‘Auto Multi-Project Server’ follows-up with task leaders on pending tasks by reminding them on task start and finish dates
The ‘Auto Multi-Project Server’ includes extensive dependency calculations, such as taking into account complex inter-task dependencies and start/finish lags between dependent activities.
The ‘Auto Multi-Project Server’ goes beyond just reminding people about their start and finish dates, it also serves as a project information system by informing the group team members on their inter-dependencies.
The ‘Auto Multi-Project Server’ includes resolution of multi-project priorities, which is an essential component for managing multi-groups with divergent priorities. It allows for example a program or general manager to examine multiple-projects under his program and assign priorities for completion. Individual task deadlines and resource usage would be controlled by the priorities assigned to the completion of the project.
The ‘Auto Multi-Project Server’ will re-allocate critical resources based on project priorities and re-compute completion dates. The project database would automatically be updated with the new dates. Thus there is automatic resolution of priority conflicts. The project leader does not have to have to constantly escalate issues up the management hierarchy for resolution.
Security issues are handled by the authorization of ell input mail or faxes, prior to processing. For electronic mail and faxes the incoming mail is checked against a valid list of passwords prior to processing. Also each project is assigned a unique identifier to prevent mix-up of information between projects.
In summary the ‘Auto Multi-Project Server’ is a necessary requirement for the needs of future HORIZONTAL CORPORATIONS where the information to manage multiple projects will be too complex to be done via manual present-day tools.
Further objects and advantages of my invention will become apparent from a consideration of the drawings and ensuing description.
FIG. 1—Architecture drawing to show the different components of an ‘Auto Multi-Project Management Process’, which is required for implementing the ‘Auto Multi-Project Server’.
FIG. 2—Internal architecture of the ‘Auto Multi-Project Server’.
FIG. 3—Project database example, format to serve as the primary communication and storage format for information on the different project(s).
FIG. 4—Build Program Flowchart, to compile together data on inter-dependent tasks for each project and build a reference database (with all necessary project information). To compute completion dates based on resource limits and inter-project dependencies.
FIG. 5—Dependency computation flowchart, to compute task start and finish dates based on relationship to dependent predecessors.
FIG. 6—Reminder program flowchart, to track pending tasks and remind task owners on a pre-determined frequency on when to start/finish tasks. To update task owners on status of dependencies.
FIG. 7—Inform flowchart, to track task completion and inform dependent tasks on start or finish status of their predecessors, thus acting as a formal channel of communication eliminating the chance of misinformation. Also to inform project and task leaders on re-computed completion dates based on resource re-allocation between projects (based on project priorities).
FIG. 8—Update flowchart, to update the ‘build’ file with status changes in task details or task inter-dependencies or inter-project priorities.
FIG. 9—Inter-project priorities and resource allocation flowchart. To allocate common resources based on inter-project priorities and re-compute task duration.
FIG. 10—Reports flowchart, to generate project management reports for reporting progress of projects(s).
10 Project(s) databases, contains information on the project, also referred to as the ‘BUILD’ file. Format for this file is shown in FIG. 3.
20 Auto project management server. This software system is the heart of the process and its workings are explained in the flowcharts contained in FIG. 4 through FIG. 10.
30 Messaging system such as Fax or Email (Electronic Mail)
40 Network Operating System, is a general term used to refer to the communication protocol used to allow users communicate with the ‘Auto Project Server’.
50 Fax, LAN (local area network), WAN (wide area network) or telephone network is the media for communication.
60 Work-team members communicating to the ‘Auto Multi-Project Server’, these may be program managers, project leaders, task leaders etc.
10 Project updates, module to parse and read project updates,
20 Database updating, module to update the project database with new information.
30 Database creation, module to open a new database project file.
40 Project data computation, module to compute all project data, (Dates etc.)
50 Project creation, module to parse and read in project data on new projects.
60 Project database, centralized complete information on the project.
70 Resource re-allocation, re-assigns critical resources if limit exceeded.
80 Database access, to retrieve task information from project database.
90 Reminder processing, to send out reminders to pending task owners.
100 Inform status, to communicate status of dependencies.
110 Project reporting, to generate and send out project progress reports.
The design and implementation of an ‘Auto Multi-Project Server’ for Automatic Multiple Project Management is described in this patent. This involves a self-running software system running on a central server computer system with capabilities for automatic data compilation, tracking and management, handle multiple projects, resolve inter-project resource conflicts and communicate with users via electronic mail or fax mail.
FIG. 1 shows the overall process of using the invention in an organization to manage multiple projects vi an automatic computer server. FIG. 2 shows the internal architecture of the invention which is an ‘Auto Multi-Project Server’.
FIG. 1, Part 10—refers to the set of project database files stored, one for each project. These files are also referred to as the ‘build’ file. Refer FIG. 3 for a sample format. This file contains information about the project, such as the start date and other global information such as the project leader's name, mail identity, holidays, weekends etc. It also contains detailed information about each task such as the description, task leader's name/mail identity, task duration or planned completion date. In addition it contains information about the dependencies for each task, in terms of the predecessor task id, the type of dependency whether FS(predeceseor finishes and task starts), FF(predecessor and task finish together) or SS (predecessor and task start together), and the lag between the predecessor and task activities. Finally the database contains information about which resources, amount of resources and budget for resources required for doing the task.
FIG. 1, Part 20 is the ‘Auto Multiple Project Server’. This is a software system which is the head of the new process. Details of its internal architecture are contained in FIG. 2. Its workings are explained in the flowcharts contained in FIG. 4 through FIG. 10. The server is a software process that runs at fixed intervals (example: at the end of the day) and performs the task of project management coordination by performing date compilation, data validation, database update, follow-up reminders to task leaders, inter-project resource conflict resolution and allocation and management reports generation on critical tasks and overruns. The main modules of the server software are described below:
Creation functions consisting of:
Project creation module to read and check for consistency, project data on new projects. (Component 50, FIG. 2)
Data computation module, to compute completion dates for all activities in the project based on dependency information and project start date. (Component 40, FIG. 2)
Database creation, this module creates a new database project file. (Component 30, FIG. 2).
Project database, holds centralized complete information on the project. (Component 60, FIG. 2).
Conflict-resolution functions consisting of:
‘Resource’ module, to check for resource usage and to re-allocate resources on the basis of inter-project priorities, if resource are limits exceeded. Project database has to be re-created if resources are re-allocated.(Component 70, FIG. 2).
Updating functions consisting of:
‘Project Update’ module, to receive and parse updates from project/task leaders (Component 10, FIG. 2)
Database updating, module to update the project database with new project status information.(Component 20, FIG. 2).
Information functions consisting of:
Database access, to retrieve task information from project database. (Component 80, FIG. 2).
‘Remind’ module, to send auto reminders to task leaders of pending tasks. (Component 90, FIG. 2).
‘Inform’ module, to inform task leaders on completion of dependent activities. (Component 100, FIG. 2)
Project reporting, to generate and send out project progress reports. (Component 110, FIG. 2)
The server software system has been implemented in C language, making it easier to port to different machines and also providing the necessary performance for handling the largest projects. The server system has to work closely with the Messaging system and the Network Operating System, the components of which are described below.
FIG. 1, Part 30—Messaging system is used to refer to the communication protocol used to allow users communicate with the ‘Auto Multi-Project Server’. This has to work under and is closely related to FIG. 1, Part 40 which is the Network Operating System. The network operating system controls the network operation.
The ‘Auto Multi-Project Server’ has to be configured separately for each type of messaging system/network operating system. The following are some of the example environments, they are provided for clarity and do not exclude other environments:
UNIX mail system running under a UNIX server machine such as a 486 PC, PENTIUM PC, SUN Workstation, DEC workstation, IBM RS6000 workstation etc. and communicating to other machines via an electronic network (Part 40). Users send electronic mail to the server machine on new project information and status updates, which is processed by the ‘Auto Multi-Project Server’. The ‘Auto Multi-Project Server’ in turn sends back electronic mail reminders and management reports.
Mail system running on a network of PCs'. The mail system may be LOTUS CCMAIL or LOTUS NOTES or MICROSOFT MAIL etc. The Network Operating System may be NOVELL NETWARE or VINES or PC-NFS etc.
Fax based communication system, based on fax board inside PC coupled with OCR software to read fax messages. Here the fax board and software functions as the messaging system, as well as the network operating system. The fax system must have automatic transmission, automatic receipt and optical character recognition capability.
FIG. 1, Part 50 is the communication network, which may be Fax, LAN (local area network), WAN (wide area network) or telephone network is the physical media for communication. This is generally transparent for the ‘Auto Multi-Project Server’, as it is handled by the Network Operating System (Part 40).
FIG. 1, Part 60 are the different Project Work-team members communicating to the ‘Auto Multi-Project Server’, these may be program managers, project leaders, task leaders etc. The program manager assigns inter-project priorities, the project leader creates the first plan for the project and the task leaders update the project database with progress of project.
The ‘Auto Multi-Project Server’ is designed to change the organization process of planning, tracking and management of work-team projects. The entire process is planned to be automated with managers focusing only on the exceptions and crisis situations. I describe below the process of using the ‘Auto Multi-Project Server’, as well as the logic used by the Invention to manage projects.
Step 1—Set up the environment, this involves creating an environment configuration file with an entry in it to show the command string to be used in submitting an input file for electronic mail or for faxing it out. Also the command string to be used in reading an electronic mail or fax, and the input file name. The environment file is also used to indicate week-ends, holidays and default reminder frequency and default reminder window.
In addition a separate file containing authorization information is required for ‘project leaders to allow them to create new projects. The authorization will consist of a list of ‘user names’ and valid passwords’.
The above environment configuration files are the only manual operation and is a one time operation. These can be performed by a Systems Manager, who does not require to have any knowledge of ‘Project management processes’. Based on the configuration values the appropriate communication procedures are invoked.
Step 2—The project leader creates a project plan in the format as per FIG. 3. This has information on the project, tasks, dependencies and resources to be used.
Step 3—The ‘Auto Multi-Project Server’ reads the project plan and invokes the ‘Build’ Procedure as per flowchart in FIG. 4. The first step is to validate the user/password and then parse the input for errors such as if names, descriptions, mail ids etc. are missing. Based on dependencies, the server computes the completion dates for each task. Completion dates are based on work-days only, so the software accounts for week-ends and holidays. Refer FIG. 5—Dependency Computation Flowchart for details on how dependencies are handled.
Step 4—Resolving Inter-project resource conflicts. The ‘build’ procedure is not complete unless critical common resource usage has been compared against the resource limits. Refer FIG. 9 for the flowchart for the re-allocation of critical resources and the re-computing of completion dates.
Prior to this the Program Manager is mailed a list of projects and is requested to assign a rank priority. In addition the program manager is requested to supply a list of critical resources and their usage limits. The actual usage is compared against this limit.
Step 5—Task Reminders are accompanied by information about the task, to allow task leaders to provide change updates such as changes in the task duration or the estimated completion date or to inform on amount of resources actually consumed. Refer FIG. 8 for the procedure flowchart on updating the project database.
Step 6—The ‘Inform’ procedure is invoked each time there is a change in a dependent task status such as starting or completion. Refer FIG. 7 for the flowchart. Thus the ‘Auto Multi-Project Server’ serves also as a formal mode of communication of task status, and does not leave it to be communicated via other informal means.
Step 7—The ‘Reports’ procedure shown in FIG. 10, is invoked to generate the necessary management reports on time/cost overruns and critical path analysis. In addition managers are informed on re-allocation of any resources, to explain re-computation of completion dates.
Automatic Operation—It should be noted that the operations of the ‘Auto Multi-Project Server’ are automatic (or self-running) and there is no manual intervention. Only at the staff-up stage is there any manual customization of the environment, by changing some of the program variables and setting up the environment file. In general the operation is driven by mail messages received from users. The ‘Auto Multi-Project Server’ responds to the messages and is thus ‘event driven’, though the response does not occur immediately but rather batched together for the end of day processing, as explained in the next paragraph.
Night processing—It is suggested that given the heavy amount of processing for each project, all ‘build’, ‘reminder’, ‘inform’, ‘reports’, ‘resource re-allocation’ procedures be run at night. This will allow for lowered load on the server and also allow accumulation of all status updates to be handled together eliminating database file access problems. Real time response to user messages is not necessary.
I have described so far the architecture and working of an ‘Auto Multi-Project Server’ which is necessary to implement the proposed ‘Automatic Multiple Project Management Process’. As can be seen from the product description and operation so far, the ‘Auto Multi-Project Server’ is a first of its kind product with some very unique features to handle large and multiple number of projects, including where there are resource conflicts. The future organizations will be greatly demanding in terms of number end size of projects and only an automated software system can prove to be useful. Existing static tools will be overwhelmed by the amount of project data.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4451067 *||Jun 1, 1982||May 29, 1984||Williams M E||Comprehensive, central scheduling folder for project management|
|US4809170||Apr 22, 1987||Feb 28, 1989||Apollo Computer, Inc.||Computer device for aiding in the development of software system|
|US4875162 *||Oct 28, 1987||Oct 17, 1989||International Business Machines Corporation||Automated interfacing of design/engineering software with project management software|
|US5168444 *||Nov 15, 1989||Dec 1, 1992||Teknekron Transportation Systems||Shipment system including processing of document images|
|US5255181 *||Jun 1, 1990||Oct 19, 1993||Motorola, Inc.||Method of planning organizational activities|
|US5301270||Dec 18, 1989||Apr 5, 1994||Anderson Consulting||Computer-assisted software engineering system for cooperative processing environments|
|US5381332 *||Dec 9, 1991||Jan 10, 1995||Motorola, Inc.||Project management system with automated schedule and cost integration|
|US5530861||Nov 28, 1994||Jun 25, 1996||Hewlett-Packard Company||Process enaction and tool integration via a task oriented paradigm|
|1||*||"Groupware Rocks the Enterprize", by Mtch Irsfeld, Open Systems Today, p. 32(1), Aug. 1993.*|
|2||*||"High-End Project Manager Coordinate Enterprisewide Project with Desktop Flexibility," Heck, Mike, InfoWorld, v15, n5, p. 59(9), Feb. 1993.*|
|3||*||"Is Lotus Notes Groupware in your company's future: Lotus Notes 3.0," Michael miley MacWeek, vol. 7 issue 22, pp. 22-24, May 31, 1993.*|
|4||*||"Primavear Project Planner: Project Management Sortware", PC Magazine, p. 170(1), Aug. 1992.*|
|5||*||"Project Management Software That's IS Friendly", Lee, Datamation p. 55(4), Oct., 1993.*|
|6||*||"Software Review-Primavera Project Planner 5.0," by Jay Medlock, Cost Engineering, v34, n8, p. 25 (2), Aug. 1992.*|
|7||*||"Syzygy: Aiding a Stellar of Resources" by Joseph Devlin, Personal Computing, v 14, n4, p. 152(1), Apr. 1990.*|
|8||"Software Review—Primavera Project Planner 5.0," by Jay Medlock, Cost Engineering, v34, n8, p. 25 (2), Aug. 1992.*|
|9||1992David King, Project Management Made Simple (1992).|
|10||Anthony Welsh, "Project Management In Action-The Future of project Management," May 1992.|
|11||Anthony Welsh, "Project Management In Action—The Future of project Management," May 1992.|
|12||InConcert version 2.5, Mar., 1993.|
|13||Microsoft7 Project 4.0, including Microsoft7 Project Workgroup Extensions and Project Scheduler Template, Feb., 1994.|
|14||Richard E. Westney, Computerized Management of Multiple Small Projects (1992).|
|15||Steve Gilliland, Project Managers: Upping the Organization, PC Sources, v. 3, n. 12, Dec. 1992.|
|16||TeamEffort by Saratoga Software, Inc. Aug., 1990.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US6901446 *||Feb 28, 2001||May 31, 2005||Microsoft Corp.||System and method for describing and automatically managing resources|
|US7031963 *||Nov 9, 1998||Apr 18, 2006||Unisys Corporation||Green ice printout sorting and delivery program|
|US7043486 *||Sep 20, 2002||May 9, 2006||Wellogix, Inc.||Process and system for tracking versions of field documentation data collection configurations in a complex project workflow system|
|US7159206 *||Nov 26, 2002||Jan 2, 2007||Unisys Corporation||Automated process execution for project management|
|US7222330 *||May 22, 2002||May 22, 2007||Bicknell Barbara A||Project planning system with content loaded project planning template generator and a plurality of content loaded project planning templates|
|US7257635||Mar 14, 2005||Aug 14, 2007||Microsoft Corporation||System and method for describing and automatically managing resources|
|US7260772 *||Oct 20, 2003||Aug 21, 2007||The Boeing Company||System and method for creating a pert chart|
|US7302401 *||Apr 4, 2000||Nov 27, 2007||Single Source Oy||Data management mechanism for project planning|
|US7302674 *||Aug 6, 2003||Nov 27, 2007||Unisys Corporation||Automating document reviews in a project management system|
|US7386797 *||May 22, 2002||Jun 10, 2008||Oracle Corporation||Framework to model and execute business processes within a collaborative environment|
|US7584078||Aug 9, 2006||Sep 1, 2009||Iav Gmbh Ingenieurgesellschaft Auto Und Verker||Creating, designing, managing, scheduling, developing and producing products|
|US7613623 *||Nov 3, 2009||Hewlett-Packard Development Company, L.P.||Enterprise management using an enterprise program office (EPO)|
|US7729924 *||Oct 16, 2003||Jun 1, 2010||Knowledge It Corporation||Virtual knowledge management system|
|US7765520 *||Jul 27, 2010||Bea Systems, Inc.||System and method for managing cross project dependencies at development time|
|US7788237 *||Aug 31, 2010||Microsoft Corporation||Method and system for tracking changes in a document|
|US7949610||May 24, 2011||International Business Machines Corporation||Method and system for discovering dependencies in project plans of distributed system|
|US8024303||Jul 29, 2005||Sep 20, 2011||Hewlett-Packard Development Company, L.P.||Software release validation|
|US8250525||Mar 2, 2007||Aug 21, 2012||Pegasystems Inc.||Proactive performance management for multi-user enterprise software systems|
|US8335704 *||Dec 18, 2012||Pegasystems Inc.||Methods and apparatus for work management and routing|
|US8463636||Jun 11, 2013||Field Nation, Llc||Field servicing|
|US8464263||Jun 11, 2013||International Business Machines Corporation||Scheduling work requests to performing centers based on overall cost and duration of multiple assignment options|
|US8479157||Dec 29, 2009||Jul 2, 2013||Pegasystems Inc.||Methods and apparatus for integration of declarative rule-based processing with procedural programming in a digital data-processing evironment|
|US8521663||May 9, 2011||Aug 27, 2013||C4Cast.Com, Inc.||Community-selected content|
|US8578262||Apr 17, 2007||Nov 5, 2013||Charles W. Williams||Cad-interfaced, automated system for assisting the architectural process|
|US8676919||Jun 26, 2008||Mar 18, 2014||Microsoft Corporation||Asynchronously editing a synchronous data store, such as a project management data store|
|US8719174||Nov 15, 2006||May 6, 2014||International Business Machines Corporation||Method, system, and computer program product for collaborative and integrated intellectual property management|
|US8812339||Aug 27, 2009||Aug 19, 2014||Jack D. Stone, Jr.||System and method for scheduling tasks|
|US8880487||Feb 18, 2011||Nov 4, 2014||Pegasystems Inc.||Systems and methods for distributed rules processing|
|US8924335||Feb 18, 2011||Dec 30, 2014||Pegasystems Inc.||Rule-based user interface conformance methods|
|US8924931 *||Aug 30, 2007||Dec 30, 2014||Serena Software, Inc.||Method and system for determining dependencies in a mainframe development environment|
|US8954361||Jul 31, 2013||Feb 10, 2015||C4Cast.Com, Inc.||Community-selected content|
|US8959480||May 31, 2013||Feb 17, 2015||Pegasystems Inc.||Methods and apparatus for integration of declarative rule-based processing with procedural programming in a digital data-processing environment|
|US9110870||Oct 2, 2013||Aug 18, 2015||Visions Computer Imaging Systems Ltd.||Automated system for assisting the architectural process|
|US9189361||Jun 28, 2012||Nov 17, 2015||Pegasystems Inc.||Proactive performance management for multi-user enterprise software systems|
|US9195936||Dec 30, 2011||Nov 24, 2015||Pegasystems Inc.||System and method for updating or modifying an application without manual coding|
|US9270743||Oct 29, 2014||Feb 23, 2016||Pegasystems Inc.||Systems and methods for distributed rules processing|
|US20010007977 *||Dec 27, 2000||Jul 12, 2001||Geary Stuart Lloyd||Reminder and actioning system|
|US20020035608 *||Aug 9, 2001||Mar 21, 2002||Rajko Milovanovic||Automated follow-up to a request|
|US20020049657 *||Oct 9, 2001||Apr 25, 2002||Main Peter T.||Web site for retail marketing program|
|US20020064460 *||Nov 29, 2000||May 30, 2002||Industrial Technology Research Institute||Integrated 3-D blade structure|
|US20020120744 *||Feb 28, 2001||Aug 29, 2002||Chellis Eugene C.||System and method for describing and automatically managing resources|
|US20020156671 *||Nov 7, 2001||Oct 24, 2002||The Boeing Company||System and method for collaborative action|
|US20020178044 *||May 22, 2002||Nov 28, 2002||Bicknell Barbara A.||Adaptable integrated-content product development system|
|US20020184071 *||May 22, 2002||Dec 5, 2002||Bicknell Barbara A.||Adaptable integrated-content product development system|
|US20030061330 *||Sep 28, 2001||Mar 27, 2003||Frisco Lynn A.||Web-based collaborative project and process management solution|
|US20030078874 *||Sep 20, 2002||Apr 24, 2003||Cope Warren Scott||Process and system for tracking versions of field documentation data collection configurations in a complex project workflow system|
|US20030105657 *||Nov 16, 2001||Jun 5, 2003||Nandigama Murali K.||Personal resource management tool|
|US20040010772 *||Nov 13, 2002||Jan 15, 2004||General Electric Company||Interactive method and system for faciliting the development of computer software applications|
|US20040054565 *||Jan 17, 2003||Mar 18, 2004||Nemecek Carole M.||Enterprise management using an enterprise program office (EPO)|
|US20040083480 *||Oct 20, 2003||Apr 29, 2004||The Boeing Company||System and method for creating a pert chart|
|US20040111328 *||Dec 10, 2002||Jun 10, 2004||International Business Machines Corporation||Method, system, and storage medium for facilitating procurement functions over a computer network|
|US20040143477 *||Jul 8, 2003||Jul 22, 2004||Wolff Maryann Walsh||Apparatus and methods for assisting with development management and/or deployment of products and services|
|US20040205531 *||Aug 17, 2001||Oct 14, 2004||Innes Bruce Donald||Method and application for developing a statement of work|
|US20050192866 *||Mar 2, 2005||Sep 1, 2005||Nintendo Of America Inc.||System and method for managing a retail marketing program utilizing dynamic forms|
|US20050262471 *||Nov 8, 2004||Nov 24, 2005||Bea Sytems, Inc.||System and method for managing cross project dependencies at development time|
|US20060111953 *||Oct 16, 2003||May 25, 2006||The Knowledge It Corporation||Virtual knowledge management system|
|US20060136510 *||Dec 17, 2004||Jun 22, 2006||Microsoft Corporation||Method and system for tracking changes in a document|
|US20060173724 *||Jan 28, 2005||Aug 3, 2006||Pegasystems, Inc.||Methods and apparatus for work management and routing|
|US20060241994 *||Apr 17, 2006||Oct 26, 2006||Kumar Anand||Automated support for monitoring and managing knowledge work|
|US20070027934 *||Jul 29, 2005||Feb 1, 2007||Burkhard Roehrle||Software release validation|
|US20070038893 *||Aug 9, 2006||Feb 15, 2007||Christine Junghans||Creating, Designing, Managing, Scheduling, Developing and Producing Products|
|US20070073572 *||Sep 27, 2005||Mar 29, 2007||The Q Llc||Data collection and distribution system|
|US20070251988 *||Apr 28, 2006||Nov 1, 2007||Century Solutions Limited||Field servicing|
|US20070288842 *||Apr 17, 2007||Dec 13, 2007||Averitt John W||Cad-Interfaced, Automated System for Assisting the Architectural Process|
|US20070294155 *||Sep 21, 2006||Dec 20, 2007||Renegade Swish, Llc||Apparatus, system, method, and computer program for managing transactions involving aviation assets|
|US20080059946 *||Aug 30, 2007||Mar 6, 2008||Jeremy Harding||Method and system for determining dependencies in a mainframe development environment|
|US20080065460 *||Sep 29, 2006||Mar 13, 2008||Renegade Swish, Llc||Apparatus, system, method, and computer program for task and process management|
|US20080114668 *||Nov 15, 2006||May 15, 2008||International Business Machines Corporation||Method, system, and computer program product for collaborative and integrated intellectual property management|
|US20080270267 *||Apr 26, 2007||Oct 30, 2008||Caterpillar Inc.||System and method for logistics management|
|US20080288322 *||May 9, 2008||Nov 20, 2008||Kevin Kennedy & Associates, Inc.||Methods and systems for project management|
|US20090198531 *||Jan 31, 2008||Aug 6, 2009||International Business Machines Corporation||Method and system for discovering dependencies in project plans of distributed system|
|US20090204463 *||Feb 12, 2009||Aug 13, 2009||Lockheed Martin Corporation||Method, tool, and system for analyzing a project|
|US20090307035 *||Jun 4, 2008||Dec 10, 2009||Microsoft Corporation||Resolution of resource over-allocations in project plans|
|US20090307115 *||Dec 10, 2009||International Business Machines Corporation||Facilitating procurement functions over a computer network|
|US20090327403 *||Jun 26, 2008||Dec 31, 2009||Microsoft Corporation||Asynchronously editing a synchronous data store, such as a project management data store|
|US20100211957 *||Feb 19, 2009||Aug 19, 2010||International Business Machines Corporation||Scheduling and assigning standardized work requests to performing centers|
|WO2006091978A2 *||Feb 27, 2006||Aug 31, 2006||Douglas Baker||Mission console|
|WO2016003728A1 *||Jun 24, 2015||Jan 7, 2016||Tuul, Inc.||System and method for implementing workflow management using messaging|
|U.S. Classification||709/226, 709/219, 707/999.01, 707/999.009, 705/7.17|
|International Classification||G06Q10/06, G06Q10/10, G06F17/50, G06F17/30|
|Cooperative Classification||G06Q10/10, G06Q10/063114, G06Q10/06312, Y10S706/919, G06Q10/063118, G06Q10/06313|
|European Classification||G06Q10/10, G06Q10/06312, G06Q10/06311D, G06Q10/06311H, G06Q10/06313|
|Jan 24, 2008||AS||Assignment|
Owner name: ENPAT, INC., FLORIDA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RAJ, SESHAN S, MR.;REEL/FRAME:020403/0684
Effective date: 20040401
|Jan 24, 2008||FPAY||Fee payment|
Year of fee payment: 12