# US 2008/0077530 A1 · System and method for project process and workflow optimization

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0077530 A1
- Document ID: US20080077530A1
- Status: Published application
- Kind: A1
- Application number: 11/860,670
- Filed: 2007-09-25
- Published: 2008-03-27
- Earliest claimed: 2006-09-25
- Inventors: John Banas; Glenn Spreen; Kenneth Russell; Christina Crawford; Doug Lui; Rick Saenz
- Web page: https://patentgrep.com/patent/US20080077530A1

## CPC

- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q 10/06313: {Resource planning in a project environment}
- 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

## Abstract

A system and method for process control and management is disclosed. Various features and applications of the present invention may be suitably adapted to manage, control or otherwise improve compliance and/or project workflow processing. In representative applications, the present invention provides a system and method for control, management, verification, certification and communication of compliance standards.

## Claims

### Claim 1

A system for complying with at least one standard, said system comprising:
a computing device having a central processing unit and at least one input suitably configured to be responsive to data via a graphical user interface and to communicate with said processing unit; and
data that may be suitably organized into a plurality of levels of organization comprising at least global data and project data, wherein global data comprises at least one global parameter and project data comprises at least one project parameter, and wherein said project data optionally comprises at least one stage;
wherein said system is configured to:
permit at least partial system access based on a role, wherein said role comprises at least one of:
an administrator and a user;
provide a protocol for at least one of identifying, characterizing and meeting a standard using at least one control and testing of said control through performance of at least one task;
verify that the standard is met;
prescribe a remediation protocol suitably adapted to meet the standard if the standard has not been met;
at least one of characterize and analyze at least one risk associated with the standard; and
provide a method for certifying that the standard has been met.

### Claim 2 (depends on 1)

The system of claim 1, wherein said graphical user interface is further suitably configured to at least partially limit access to said data.

### Claim 3 (depends on 1)

The system of claim 1, wherein said user comprises at least one of: a read-only user, a guest, and a project coordinator.

### Claim 4 (depends on 1)

The system of claim 1, wherein said user has a status comprising at least one of: active, inactive and modified.

### Claim 5 (depends on 1)

The system of claim 1, wherein said graphical user interface is further configured to display a homepage.

### Claim 6 (depends on 5)

The system of claim 5, wherein said homepage at least one of: comprises an at least partially individualized homepage for a user, is at least partially configured based on the level of access of a user, and comprises a to-do list.

### Claim 7 (depends on 6)

The system of claim 6, wherein said to-do list is substantially configured to be individualized for a user.

### Claim 8 (depends on 6)

The system of claim 6, wherein said to-do list further comprises at least one of: a stage column, a pending assigned task column, a pending approval column, a rejection column, a due date column, and a past due column.

### Claim 9 (depends on 5)

The system of claim 5, wherein at least one status chart at least partially illustrates status of at least one of said task, said project, and said stage, wherein said chart comprises at least one of a pie chart, a table and a graph.

### Claim 10 (depends on 1)

The system of claim 1, wherein said administrator is permitted to at least one of: add, modify, and deactivate said user.

### Claim 11 (depends on 1)

The system of claim 1, wherein said administrator is permitted to query at least one user by at least one of: a user name, name, location, entity, position, status, assignment, and role.

### Claim 12 (depends on 1)

The system of claim 1, wherein said administrator is further configured to filter a list of users to display at least one of: active users, inactive users, and modified users.

### Claim 13 (depends on 1)

The system of claim 1, further comprising at least one security feature to limit at least one of access and use of the system.

### Claim 14 (depends on 13)

The system of claim 13, wherein said security feature further comprises a graphical user interface to at least one of: substantially prevent unauthorized access, at least partially randomly generate new login passwords, and encrypt stored passwords.

### Claim 15 (depends on 14)

The system of claim 14, wherein said user password is further configured to comprise one-way encryption.

### Claim 16 (depends on 1)

The system of claim 1, wherein said global data is at least substantially accessible to a plurality of users and administrators.

### Claim 17 (depends on 1)

The system of claim 1, further comprising at least one domain, wherein said domain comprises at least one of a global parameter and a project parameter that is suitably configured to at least one of: group, add, edit, delete and reorder at least one of said global parameter and said project parameter.

### Claim 18 (depends on 17)

The system of claim 17, wherein said parameter may be suitably configured to be identified by at least one of a code value and a data value.

### Claim 19 (depends on 1)

The system of claim 1, wherein at least one global parameter is only accessible by said administrator.

### Claim 20 (depends on 1)

The system of claim 1, wherein said graphical user interface is further configured to comprise at least one administrator tool, wherein said administrator tool is substantially accessible only by said administrator.

### Claim 21 (depends on 20)

The system of claim 20, wherein said administrator tool comprises at least one form-based screen that is suitably configured to at least partially facilitate bulk loading of data into at least one of said project data and said global data.

### Claim 22 (depends on 1)

The system of claim 1, wherein project data is substantially accessible to at least one of a user and administrator after assignment to said project.

### Claim 23 (depends on 1)

The system of claim 1, further configured to allow at least one of said user and said administrator to search said data.

### Claim 24 (depends on 1)

The system of claim 1, wherein said graphical user interface comprises a survey suitably configured to facilitate said input of data based on at least one of said global parameter and said project parameter.

### Claim 25 (depends on 24)

The system of claim 24, wherein said survey comprises a template based on at least one of said global parameter and said project parameter.

### Claim 26 (depends on 25)

The system of claim 25, wherein said template is suitably configured to be at least one of customized and saved.

### Claim 27 (depends on 1)

The system of claim 1, further configured such that a change in at least one of said project data and said global data may be propagated throughout substantially each project.

### Claim 28 (depends on 1)

The system of claim 1, wherein said project comprises at least one stage and wherein said stage comprises at least one task.

### Claim 29 (depends on 28)

The system of claim 28, wherein said task uses at least part of said project data.

### Claim 30 (depends on 1)

The system of claim 1, wherein said task is suitably configured to be assigned to a plurality of users.

### Claim 31 (depends on 1)

The system of claim 1, wherein said task is assigned to one user.

### Claim 32 (depends on 1)

The system of claim 1, wherein said task comprises at least one status comprising at least one of: assign, complete, approve, not started, in progress, past due, reject, re-assign, and re-open.

### Claim 33 (depends on 32)

The system of claim 32, wherein said task status comprises ‘assign’ and wherein said status places an initial assignment of said task to at least one user.

### Claim 34 (depends on 32)

The system of claim 32, wherein said task status comprises ‘complete’ and wherein said status signals at least one user to complete said task.

### Claim 35 (depends on 32)

The system of claim 32, wherein said task status comprises ‘approve’ and wherein said status signals to a user that said task should be approved.

### Claim 36 (depends on 34)

The system of claim 34, further comprising a task status engine that is suitably configured to communicate at least one of: a new task assignment, a task assignment rejection, a password reset, and a new user added to the system.

### Claim 37 (depends on 36)

The system of claim 36, wherein said task status engine is further configured to transmit at least one alert via email.

### Claim 38 (depends on 36)

The system of claim 36, wherein said task status engine is further configured to send a stage reminder to indicate at least one of: a new task assignment, task assignment rejection, password reset, and a new user added to the system.

### Claim 39 (depends on 36)

The system of claim 36, wherein said task status engine is further configured to at least partially automatically determine at least one due date for a task assignment when said task assignment is generated.

### Claim 40 (depends on 39)

The system of claim 39, wherein at least one due date is calculated using at least one milestone date.

### Claim 41 (depends on 40)

The system of claim 40, wherein said due dates for a completed task are set by said user and are before an assignment due date and past the day a task assignment is made.

### Claim 42 (depends on 39)

The system of claim 39, wherein said due dates for approval of tasks are configured using at least one of said project parameters.

### Claim 43 (depends on 40)

The system of claim 40, wherein said computing device is further configured to create at least one documentation task, wherein said documentation task may be assigned to at least one of said global data and said project data.

### Claim 44 (depends on 43)

The system of claim 43, wherein said documentation task is suitably configured to be assigned at least one of: annually, biannually, quarterly, biweekly, weekly, and daily.

### Claim 45 (depends on 44)

The system of claim 44, wherein said documentation task is suitably configured to record at least one change to said task.

### Claim 46 (depends on 1)

The system of claim 1, further comprising a project maintenance page, wherein said maintenance page allows for at least one of viewing, editing, archiving and copying said project.

### Claim 47 (depends on 1)

The system of claim 1, further comprising an audit trail, wherein said audit trail is configured to record at least one task.

### Claim 48 (depends on 47)

The system of claim 47, wherein said audit trail comprises at least one of the following descriptions: stage initiated, pending assign task, assigned task, rejected task, re-assigned task, completed task, pending completed task, pending approval, approved, rejected approval, and send to next stage.

### Claim 49 (depends on 1)

The system of claim 1, further comprising a document library suitably configured to comprise a central point where at least one attachment is added to at least one of said project and said global data, and wherein said attachment may be at least one of: searched, viewed, added, updated, and deleted.

### Claim 50 (depends on 1)

The system of claim 1, further comprising a query page configured to run at least one query search.

### Claim 51 (depends on 50)

The system of claim 50, wherein the query search displays at least one result based on at least one term selected by at least one user, and wherein said result comprises at least part of at least one of said project data and said global data.

### Claim 52 (depends on 51)

The system of claim 51, wherein said query search results are suitably configured to be displayed to said user in a grid format.

### Claim 53 (depends on 50)

The system of claim 50, wherein said query further comprises at least one of: a definition, a display field, a condition, and sorting.

### Claim 54 (depends on 1)

The system of claim 1, wherein said graphical user interface is further configured to allow said user to at least one of: at least partially write at least one custom report, upload at least one custom report to said project, and at least partially run at least one custom report.

### Claim 55 (depends on 53)

The system of claim 53, wherein results of said custom reports are suitably configured to be at least one of: view, printed, and exported.

### Claim 56 (depends on 1)

The system of claim 1, wherein said standard comprises at least one of: a law, a rule, a cannon, a regulation, a requirement, a goal, and a procedure.

### Claim 57 (depends on 1)

The system of claim 1, wherein said device is suitably configured for at least one of: remote access, real-time updates, and archiving.

### Claim 58 (depends on 1)

The system of claim 1, wherein said global organization comprises a business and wherein said project comprises at least one of: a department, a subsidiary, a division, and a branch.

### Claim 59 (depends on 1)

The system of claim 1, further comprising a root node and at least one child node.

### Claim 60 (depends on 61)

The system of claim 61, wherein said root node links global data and wherein at least one child node links project data.

### Claim 61 (depends on 62)

The system of claim 62, wherein said root node and child node comprise a navigation tree.

### Claim 62 (depends on 62)

The system of claim 62, wherein a global level comprises a root node and at least one child node, and wherein said child node comprises a root node for a project level.

### Claim 63 (depends on 61)

The system of claim 61, wherein said child node links to a root node.

### Claim 64 (depends on 1)

The system of claim 1, wherein said graphical user interface allows said user to provide said global data and project data via a data input; and displays said data output to said user.

### Claim 65 (depends on 1)

The system of claim 1, further comprising a flag that is set when at least one of: new project data and new global data is added; wherein said flag saves values corresponding to author, date, and time of change as modification data.

### Claim 66

A method for complying with at least one standard with a data management system, said method comprising the steps of:
providing a computing device having a central processing unit and at least one input suitably configured to be responsive to data via a graphical user interface and to communicate with said processing unit;
assigning a role, wherein said role corresponds to at least one of an administrator and a user,
where said role at least partially determines a level of access granted to said system;
organizing data into a plurality of levels of organization corresponding to at least one of global and project data, where global data comprises at least one global parameter and where project data comprises at least one project parameter, and wherein said project optionally comprises at least one stage;
providing a protocol for at least one of identifying, characterizing and meeting the standard using at least one control and testing said control through performance of at least one task; and
optionally prescribing a remediation protocol substantially configured to meet the standard.

### Claim 67 (depends on 66)

The method of claim 66, further comprising the step of at least partially analyzing at least one risk associated with the standard.

### Claim 68 (depends on 66)

The method of claim 66, further comprising the step of certifying that the standard has been met.

### Claim 69 (depends on 66)

The method of claim 66, wherein said graphical user interface is suitably configured to at least partially limit access to said data.

### Claim 70 (depends on 66)

The method of claim 66, wherein said user comprises at least one of: a user, a read-only user, a guest, and a project coordinator.

### Claim 71 (depends on 66)

The method of claim 66, wherein said user has a status comprising at least one of: active, inactive and modified.

### Claim 72 (depends on 66)

The method of claim 66, wherein said graphical user interface is further configured to display a homepage.

### Claim 73 (depends on 72)

The method of claim 72, wherein said homepage at least one of: comprises an at least partially individualized homepage for a user, is at least partially configured based on the level of access of a user, and comprises a to-do list.

### Claim 74 (depends on 73)

The method of claim 73, wherein said to-do list is substantially configured to be customized for a user.

### Claim 75 (depends on 73)

The method of claim 73, wherein said to-do list further comprises at least one of: a stage column, a pending assigned task column, a pending approval column, a rejection column, a due date column, and a past due column.

### Claim 76 (depends on 73)

The method of claim 73, wherein said homepage further comprises at least one of: a user preference link, an inbox, and a logout option.

### Claim 77 (depends on 73)

The method of claim 73, further comprising the step of providing a status of at least one of a project, a stage and a task through said homepage.

### Claim 78 (depends on 77)

The method of claim 77, further comprising the step of providing at least one status chart that at least partially illustrates status of at least one of said task, said project, and said stage, wherein said chart comprises at least one of a pie chart, a table and a graph.

### Claim 79 (depends on 66)

The method of claim 66, wherein said administrator is suitably configured to at least one of: add, modify, and inactivate a user.

### Claim 80 (depends on 66)

The method of claim 66, wherein said administrator may filter a list of users to display at least one of: active users, inactive users, and modified users.

### Claim 81 (depends on 66)

The method of claim 66, further comprising the step of providing at least one security feature to limit at least one of access and use of the system.

### Claim 82 (depends on 81)

The method of claim 81, wherein said security feature further comprises a graphical user interface to at least one of: substantially prevent unauthorized access, at least partially randomly generate new login passwords, and encrypt stored passwords.

### Claim 83 (depends on 82)

The method of claim 82, wherein said user password is further configured to comprise one-way encryption.

### Claim 84 (depends on 66)

The method of claim 66, wherein said global data is at least substantially accessible to all users and administrators.

### Claim 85 (depends on 66)

The method of claim 66, further comprising at least one domain, wherein said domain comprises at least one of a global parameter and a project parameter that is suitably configured to at least one of: group, add, edit, delete and reorder at least one of said global parameter and said project parameter.

### Claim 86 (depends on 85)

The method of claim 85, further providing the step of identifying at least one project parameter by at least one of a code value and a data value.

### Claim 87 (depends on 66)

The method of claim 66, further comprising the step of providing an administrator with access to at least one global parameter.

### Claim 88 (depends on 66)

The method of claim 66, wherein said graphical user interface is further configured to comprise at least one administrator tool that is substantially accessible by said administrator.

### Claim 89 (depends on 88)

The method of claim 88, wherein said administrator tool comprises at least one form-based screen that is suitably configured to at least partially facilitate bulk loading of data into at least one of said project data and said global data.

### Claim 90 (depends on 66)

The method of claim 66, wherein said project data is substantially accessible to at least one of said user and said administrator after assignment of said project.

### Claim 91 (depends on 66)

The method of claim 66, further comprising the step of allowing at least one of said user and said administrator to search said data.

### Claim 92 (depends on 66)

The method of claim 66, further comprising the step of providing a survey suitably configured to facilitate said input of data based on at least one of said global parameter and said project parameter.

### Claim 93 (depends on 92)

The method of claim 92, wherein said survey comprises a template based on at least one of said global parameter and said project parameter.

### Claim 94 (depends on 93)

The method of claim 93, wherein said template is suitably configured to be at least one of customized and saved.

### Claim 95 (depends on 66)

The method of claim 66, further comprising the step of at least partially propagating a change in at least one of said project data and said global data throughout substantially each project.

### Claim 96 (depends on 66)

The method of claim 66, wherein said project comprises at least one stage and said stage comprises at least one task.

### Claim 97 (depends on 96)

The method of claim 96, wherein said task uses at least part of said project data.

### Claim 98 (depends on 66)

The method of claim 66, further comprising the step of assigning said task to more than one user.

### Claim 99 (depends on 66)

The method of claim 66, wherein said task comprises a status comprising at least one of:
assign, complete, approve, not started, in progress, past due, reject, re-assign, and re-open.

### Claim 100 (depends on 99)

The method of claim 99, wherein said task status comprises ‘assign’ and wherein said status places an initial assignment of said task to at least one user.

### Claim 101 (depends on 99)

The method of claim 99, wherein said task status comprises ‘complete’ and wherein said status signals at least one user to complete said task.

### Claim 102 (depends on 99)

The method of claim 99, wherein said task status comprises ‘approve’ and wherein said status signals to a user that said task should be approved.

### Claim 103 (depends on 101)

The method of claim 101, further comprising the step of providing a task status engine, wherein said task status engine is suitably configured to communicate at least one of: a new task assignment, a task assignment rejection, a password reset, and a new user added to the system.

### Claim 104 (depends on 103)

The method of claim 103, wherein said task status engine is further configured to transmit at least one alert via email.

### Claim 105 (depends on 104)

The method of claim 104, wherein said task status engine is further configured to send a stage reminder to indicate at least one of: a new task assignment, a task assignment rejection, a password reset, and a new user added to the system.

### Claim 106 (depends on 103)

The method of claim 103, wherein said task status engine is further configured to at least partially automatically determine at least one due date for a task assignment when said task is generated.

### Claim 107 (depends on 106)

The method of claim 106, wherein at least one due date is calculated using at least one milestone date.

### Claim 108 (depends on 107)

The method of claim 107, wherein said due date for a completion of a task is set by said user and occurs before an assignment due date and after the day a task assignment is made.

### Claim 109 (depends on 107)

The method of claim 107, wherein said due date for task approval is configured using at least one project parameter.

### Claim 110 (depends on 107)

The method of claim 107, wherein said computing device is further configured to create at least one documentation task, wherein said documentation task may be assigned to at least one of said global data and said project data.

### Claim 111 (depends on 110)

The method of claim 110, further comprising the step of assigning said documentation task at least one of: annually, biannually, quarterly, biweekly, weekly, and daily.

### Claim 112 (depends on 111)

The method of claim 111, wherein said documentation task is suitably configured to record at least one change to said task.

### Claim 113 (depends on 66)

The method of claim 66, further comprising the step of providing a project maintenance page, wherein said maintenance page allows for at least one of: viewing, editing, archiving, and copying said project.

### Claim 114 (depends on 66)

The method of claim 66, further comprising the step of providing an audit trail, wherein said audit trail comprises at least one of the following descriptions: stage initiated, pending assign task, assigned task, rejected task, completed task, pending competed task, pending approval, rejected approval, and send to next stage.

### Claim 115 (depends on 66)

The method of claim 66, further comprising the step of providing a document library, wherein said document library is suitably configured to comprise a central point where at least one attachment is added to at least one of said project and said global data, and wherein said attachment may be at least one of: searched, viewed, added, updated, and deleted.

### Claim 116 (depends on 66)

The method of claim 66, further comprising a query page, wherein said query page is suitably configured to run at least one query search.

### Claim 117 (depends on 116)

The method of claim 116, wherein said query search displays at least one result, wherein said result is based on at least one term selected by at least one user, and wherein said result comprises at least part of at least one of said project data and said global data.

### Claim 118 (depends on 117)

The method of claim 117, wherein said query further comprises at least one element corresponding to at least one of: definition, display field, condition, and sorting.

### Claim 119 (depends on 66)

The method of claim 66, wherein said graphical user interface is further configured to allow said user to at least one of: at least partially write at least one custom report, upload at least one custom report to said project, and at least partially run at least one custom report.

### Claim 120 (depends on 119)

The method of claim 119, wherein results of said custom reports are suitably configured to be at least one of: viewed, printed, and exported.

### Claim 121 (depends on 66)

The method of claim 66, wherein said graphical user interface allows said user to provide said global data and project data via a data input, and displays said data output to said user.

### Claim 122 (depends on 66)

The method of claim 66, further comprising the step of setting a flag when at least one of new project data and new global data is added, wherein said flag saves values, user making modification, date and time of change as modification data.

### Claim 123 (depends on 66)

The method of claim 66, wherein said standard comprises at least one of: a law, a rule, a cannon, a regulation, a requirement, a goal, and a procedure.

### Claim 124 (depends on 66)

The method of claim 66, wherein said computing device is suitably configured for at least one of: remote access, real-time updates, and archiving.

### Claim 125 (depends on 66)

The method of claim 66, wherein said global organization comprises a business and wherein said project comprises at least one of: a department, a subsidiary, a division, and a branch.

### Claim 126 (depends on 66)

The method of claim 66, further comprising the step of providing a root node and at least one child node.

### Claim 127 (depends on 126)

The method of claim 126, wherein said root node links global data and wherein said child node links project data.

### Claim 128 (depends on 126)

The method of claim 126, wherein said root node and child node comprise a navigation tree.

### Claim 129 (depends on 126)

The method of claim 126, wherein a global level comprises a root node and at least one child node, and wherein said child node comprises a root node for a project level.

### Claim 130 (depends on 126)

The method of claim 126, wherein said child node links to a root node.

### Claim 131

A computing device suitably configured to provide a system for complying with at least one standard relating to Sarbanes-Oxley requirements, said computing device comprising:
a central processing unit;
at least one input substantially configured to be responsive to data via a graphical user interface and to communicate with said processing unit;
wherein said graphical user interface comprises at least one security feature; and
wherein said computing device is substantially configured to:
organize data into a plurality of levels of organization comprising at least one of global, project and optionally stage, wherein global data comprises at least one global parameter and project data comprises at least one project parameter, and further comprising at least one domain suitably configured to at least one of: group, add, edit, delete, and reorder at least one of said global parameter and said project parameter, and
wherein said computing device is substantially configured to at least one of:
permit access to the system at least partially based on a role, wherein said role comprises at least one of: an administrator and a user, and wherein a user comprises at least one of a user,
a read-only user, a guest, and a project coordinator;
provide a protocol for at least one of identifying, characterizing and meeting the standard using at least one control and testing said control through performance of at least one task;
organize at least one document verifying at least one of completion and approval of at least one task;
provide a query search of substantially all of at least one of global data and project data;
verify that the standard is met;
prescribe a remediation protocol suitably configured to meet the standard;
at least one of characterize and analyze at least one risk associated with the standard; and
provide a method for certifying that the standard has been met.
