System And Method For Network-based Project Management - Patent 7756816

The present invention relates to the field of project management, and more particularly to network-enabled project management for coordinating different levels of an organization.BACKGROUND OF THE INVENTIONWhen an entity, such as a business, academic, government or other organization undertakes a large project, it is desirable to have a system to manage information about the project. For example, it may be desirable to accumulate schedules, costs,and other information related to the project and to produce reports from the project-related information.Although some project management systems are available, existing packages are limited in scope and flexibility. For example, the databases storing the project information often have limited storage or other capacities, so that the reports thatmay be generated using the project management systems are correspondingly limited.Further, operationally speaking, each department, line of business or other unit of an organization may employ its own project management system. The project management system used by one unit may not be compatible with the project managementsystem of another unit or a general project management system used by the business, or by suppliers and other vendors. Sharing data, such as schedules or lists of personnel, between levels of the company or other organization may therefore be difficult. Setting a consistent security policy across all levels of the company or other organization may also be difficult or impossible. Other problems exist.SUMMARY OF THE INVENTIONThe invention overcoming these and other problems in the art relates in one regard to a system and method for managing project information over a network. The inventive system may include a project information database associated with thenetwork, and a project information management tool. The project information database may store information associated with a project being carried out by a corporate or other organization having at least

United States Patent: 7756816
&nbsp;
( 1 of 1 )
United States Patent
7,756,816
Scott
July 13, 2010
System and method for network-based project management
Abstract
A system for managing a project and its associated information over a
network is presented. The system includes a project information database
associated with the network and a project information management tool.
The project information database stores information associated with a
project being carried out by a corporate entity having at least one
sub-entity. The project information management tool includes a project
information module to manage the information associated with the project,
and at least one cross-sub-entity project-component module. The
cross-sub-entity project module manages and tracks overall information
and sub-entity specific information, of the information associated with
the project, related to the project-component.
Inventors:
Scott; Kelly W. (Columbus, OH)
Assignee:
JPMorgan Chase Bank, N.A.
(New York,
NY)
Appl. No.:
11/247,132
Filed:
October 12, 2005
Related U.S. Patent Documents
Application NumberFiling DatePatent NumberIssue Date
10262286Oct., 20027058660
Current U.S. Class:
1/1 ; 707/999.102
Current International Class:
G06F 17/00&nbsp(20060101)
Field of Search:
707/100-102
References Cited [Referenced By]
U.S. Patent Documents
3665162
May 1972
Yamamoto et. al.
3705385
December 1972
Batz
3860870
January 1975
Furuya
3896266
July 1975
Waterbury
3938090
February 1976
Borison et al.
3938091
February 1976
Atalla et al.
4013962
March 1977
Beseke et al.
4123747
October 1978
Lancto et al.
4200770
April 1980
Hellman et al.
4302810
November 1981
Bouricius et al.
4321672
March 1982
Braun et al.
4405829
September 1983
Rivest et al.
4453074
June 1984
Weinstein
4454414
June 1984
Benton
4567359
January 1986
Lockwood
4575621
March 1986
Dreifus
4605844
August 1986
Haggan
4614861
September 1986
Pavlov et al.
4633397
December 1986
Macco
4650981
March 1987
Foletta
4695880
September 1987
Johnson et al.
4696491
September 1987
Stenger
4697072
September 1987
Kawana
4701601
October 1987
Francini et al.
4713761
December 1987
Sharpe et al.
4725719
February 1988
Oncken et al.
4745468
May 1988
Von Kohorn
4747050
May 1988
Brachtl et al.
4752676
June 1988
Leonard et al.
4799156
January 1989
Shavit
4801787
January 1989
Suzuki
4823264
April 1989
Deming
4845347
July 1989
McCrindle
4859837
August 1989
Halpern
4868877
September 1989
Fischer
4882675
November 1989
Nichtberger et al.
4926255
May 1990
Von Kohorn
4941090
July 1990
McCarthy
4964043
October 1990
Galvin
4965568
October 1990
Atalla et al.
4977501
December 1990
Lefevre
4984272
January 1991
McILroy et al.
4992940
February 1991
Dworkin
5005200
April 1991
Fischer
5016270
May 1991
Katz
5016274
May 1991
Micali et al.
5018196
May 1991
Takaragi et al.
5025372
June 1991
Burton et al.
5050207
September 1991
Hitchcock
5072380
December 1991
Randelman et al.
5084816
January 1992
Boese
5097115
March 1992
Ogasawara et al.
5117355
May 1992
McCarthy
5122950
June 1992
Mee
5157717
October 1992
Hitchcock
5161244
November 1992
Maurer
5163098
November 1992
Dahbura
5175682
December 1992
Higashiyama
5189606
February 1993
Burns et al.
5196840
March 1993
Leith et al.
5202826
April 1993
McCarthy
5212792
May 1993
Gerety et al.
5220501
June 1993
Lawlor
5225664
July 1993
Iijima
5231668
July 1993
Kravitz
5233654
August 1993
Harvey et al.
5235509
August 1993
Mueller et al.
5237620
August 1993
Deaton
5241594
August 1993
Kung
5257486
November 1993
Holmwall
5265033
November 1993
Vajk
5267314
November 1993
Stambler
5276311
January 1994
Hennige
5287268
February 1994
McCarthy
5297026
March 1994
Hoffman
5302810
April 1994
Gauthier et al.
5305456
April 1994
Boitana
5311594
May 1994
Penzias
5315504
May 1994
Lemble
5317683
May 1994
Hager et al.
5319710
June 1994
Atalla et al.
5321841
June 1994
East
5341428
August 1994
Schatz
5351186
September 1994
Bullock
5351187
September 1994
Hassett
5352877
October 1994
Morley
5367572
November 1994
Weiss
5381332
January 1995
Wood
5382784
January 1995
Eberhardt
5412708
May 1995
Katz
5420405
May 1995
Chasek
5430644
July 1995
Deaton et al.
5432326
July 1995
Noblett et al.
5446740
August 1995
Yien
5448471
September 1995
Deaton et al.
5450134
September 1995
Legate
5450491
September 1995
McNair
5450537
September 1995
Hirai et al.
5465206
November 1995
Hilt et al.
5466920
November 1995
Nair et al.
5467269
November 1995
Flaten
5473143
December 1995
Vak
5473732
December 1995
Chang
5479530
December 1995
Nair et al.
5483444
January 1996
Marlark
5485370
January 1996
Moss et al.
5495981
March 1996
Warther
5500890
March 1996
Rogge et al.
5511117
April 1996
Zazzera
5513102
April 1996
Auriemma
5524073
June 1996
Stambler
5532689
July 1996
Bueno
5532920
July 1996
Hartrick
5534855
July 1996
Shockley et al.
5537314
July 1996
Kanter
5537473
July 1996
Saward
5541583
July 1996
Mandelbaum
5544086
August 1996
Davis et al.
5546452
August 1996
Andrews
5550734
August 1996
Tarter
5551021
August 1996
Harada
5555303
September 1996
Stambler
5557334
September 1996
Legate
5557518
September 1996
Rosen
5560008
September 1996
Johnson et al.
5568489
October 1996
Yien
5570295
October 1996
Isenberg
5570465
October 1996
Tsakanikas
5576951
November 1996
Lockwood
5583778
December 1996
Wind
5583933
December 1996
Mark
5590038
December 1996
Pitroda
5590197
December 1996
Chen
5590199
December 1996
Krajewski et al.
5592378
January 1997
Cameron
5592553
January 1997
Guski et al.
5592560
January 1997
Deaton et al.
5594837
January 1997
Noyes
5598557
January 1997
Doner
5602936
February 1997
Lynn
5603025
February 1997
Tabb
5604490
February 1997
Blakley et al.
5606496
February 1997
D'Agostino
5611052
March 1997
Dykstra
5617474
April 1997
Ditzig et al.
5621201
April 1997
Langhans
5621789
April 1997
McCalmont
5621812
April 1997
Deaton et al.
5625767
April 1997
Bartell
5634101
May 1997
Blau
5638457
June 1997
Deaton et al.
5640577
June 1997
Scharmer
5642419
June 1997
Rosen
5642485
June 1997
Deaton et al.
5644493
July 1997
Motai
5644723
July 1997
Deaton et al.
5644778
July 1997
Burks et al.
5646998
July 1997
Stambler
5649114
July 1997
Deaton et al.
5649118
July 1997
Carlisle et al.
5652786
July 1997
Rogers
5653914
August 1997
Holmes et al.
5657383
August 1997
Gerber
5657390
August 1997
Elgamal et al.
5659165
August 1997
Jennings
5659469
August 1997
Deaton et al.
5661807
August 1997
Guski et al.
5664115
September 1997
Fraser
5666493
September 1997
Wojcik et al.
5671285
September 1997
Newman
5675637
October 1997
Szlam et al.
5675662
October 1997
Deaton et al.
5677521
October 1997
Garrou
5677955
October 1997
Doggett et al.
5678046
October 1997
Cahill et al.
5680459
October 1997
Hook et al.
5682524
October 1997
Freund
5684870
November 1997
Maloney
5687322
November 1997
Deaton et al.
5689100
November 1997
Carrithers et al.
5692132
November 1997
Hogan
5698837
December 1997
Furuta
5699528
December 1997
Hogan
5703344
December 1997
Bezy et al.
5704044
December 1997
Tarter et al.
5706452
January 1998
Ivanov
5710886
January 1998
Christensen et al.
5710887
January 1998
Chelliah
5710889
January 1998
Clark et al.
5715298
February 1998
Rogers
5715314
February 1998
Payne
5715399
February 1998
Bezos
5715402
February 1998
Popolo
5715450
February 1998
Ambrose
5724424
March 1998
Gifford
5727163
March 1998
Bezos
5734838
March 1998
Robinson
5737414
April 1998
Walker et al.
5740231
April 1998
Cohn et al.
5742845
April 1998
Wagner
5745555
April 1998
Mark
5754840
May 1998
Rivette
5758126
May 1998
Daniels et al.
5758328
May 1998
Giovannoli
5761288
June 1998
Pinard et al.
5761647
June 1998
Boushy
5761661
June 1998
Coussens
5764789
June 1998
Pare et al.
5765141
June 1998
Spector
5765143
June 1998
Sheldon
5768382
June 1998
Schnier et al.
5774122
June 1998
Kojima
5778178
July 1998
Arunachalam
5781909
July 1998
Logan et al.
5784562
July 1998
Diener
5787403
July 1998
Randle
5787404
July 1998
Fernandez-Holmann
5789732
August 1998
McMahon et al.
5790650
August 1998
Dunn
5790785
August 1998
Klug et al.
5793032
August 1998
Bard et al.
5793861
August 1998
Haigh
5794178
August 1998
Caid et al.
5794207
August 1998
Walker
5794259
August 1998
Kikinis
5796395
August 1998
De Hond
5796827
August 1998
Coppersmith et al.
5797127
August 1998
Walker et al.
5798508
August 1998
Walker et al.
5802498
September 1998
Comesanas
5802502
September 1998
Gell
5805719
September 1998
Pare et al.
5815657
September 1998
Williams et al.
5815665
September 1998
Teper et al.
5815683
September 1998
Vogler
5818936
October 1998
Moshayekhi
5819092
October 1998
Ferguson
5819285
October 1998
Damico
5825863
October 1998
Walker
5825870
October 1998
Miloslavsky
5825871
October 1998
Mark
5825890
October 1998
Elgamal et al.
5826023
October 1998
Hall et al.
5826241
October 1998
Stein
5826245
October 1998
Sandberg-Diment
5826250
October 1998
Trefler
5826252
October 1998
Wolters et al.
5828734
October 1998
Katz
5828751
October 1998
Walker et al.
5828812
October 1998
Khan et al.
5828833
October 1998
Belville et al.
5832090
November 1998
Raspotnik
5832211
November 1998
Blakley, III et al.
5832457
November 1998
O'Brien
5832460
November 1998
Bednar
5832476
November 1998
Tada
5835087
November 1998
Herz
5835580
November 1998
Fraser
5835603
November 1998
Coutts
5838903
November 1998
Blakely, III et al.
5838906
November 1998
Doyle
5842178
November 1998
Giovannoli
5842211
November 1998
Horadan
5844553
December 1998
Hao
5845259
December 1998
West et al.
5845260
December 1998
Nakano et al.
5847709
December 1998
Card
5848143
December 1998
Andrews
5848190
December 1998
Kleehammer et al.
5848400
December 1998
Chang
5848427
December 1998
Hyodo
5852811
December 1998
Atkins
5852812
December 1998
Reeder
5857079
January 1999
Claus et al.
5859419
January 1999
Wynn
5862223
January 1999
Walker
5862323
January 1999
Blakley, III et al.
5864830
January 1999
Armetta et al.
5864871
January 1999
Kitain et al.
RE36116
February 1999
McCarthy
5866889
February 1999
Weiss et al.
5870456
February 1999
Rogers
5870718
February 1999
Spector
5870721
February 1999
Norris
5870724
February 1999
Lawlor
5870725
February 1999
Belinger et al.
5871398
February 1999
Schneier et al.
5873072
February 1999
Kight
5873096
February 1999
Lim
5878141
March 1999
Daly et al.
5880769
March 1999
Nemirofsky
5883810
March 1999
Franklin et al.
5884032
March 1999
Bateman
5884270
March 1999
Walker et al.
5884272
March 1999
Walker et al.
5884274
March 1999
Walker et al.
5884288
March 1999
Chang
5884312
March 1999
Dustan et al.
5889863
March 1999
Weber
5892900
April 1999
Ginter et al.
5898780
April 1999
Liu et al.
5898838
April 1999
Wagner
5899982
May 1999
Randle
5903878
May 1999
Talati et al.
5903881
May 1999
Schrader
5905908
May 1999
Wagner
5907142
May 1999
Kelsey
5909486
June 1999
Walker et al.
5910988
June 1999
Ballard
5913202
June 1999
Motoyama
5914472
June 1999
Foladare et al.
5915244
June 1999
Jack et al.
5918214
June 1999
Perkowski
5918217
June 1999
Maggioncalda
5918239
June 1999
Allen et al.
5920847
July 1999
Kolling et al.
5921864
July 1999
Walker et al.
5923763
July 1999
Walker et al.
5926796
July 1999
Walker et al.
5926812
July 1999
Hilsenrath
5930764
July 1999
Melchione
5933816
August 1999
Zeanah et al.
5933817
August 1999
Hucal
5933823
August 1999
Cullen
5933827
August 1999
Cole et al.
5936541
August 1999
Stambler
5940811
August 1999
Norris
5940812
August 1999
Tengel et al.
5943656
August 1999
Crooks
5944824
August 1999
He
5945653
August 1999
Walker et al.
5946388
August 1999
Walker et al.
5947747
September 1999
Walker et al.
5949044
September 1999
Walker et al.
5949875
September 1999
Walker et al.
5950173
September 1999
Perkowski
5950174
September 1999
Brendzel
5950206
September 1999
Krause
5952639
September 1999
Ohki et al.
5952641
September 1999
Korshun
5953710
September 1999
Fleming
5956695
September 1999
Carrithers et al.
5958007
September 1999
Lee et al.
5960411
September 1999
Hartman et al.
5961593
October 1999
Gabber et al.
5963635
October 1999
Szlam et al.
5963925
October 1999
Kolling et al.
5963952
October 1999
Smith
5963953
October 1999
Cram et al.
5966695
October 1999
Melchione et al.
5966699
October 1999
Zandi
5967896
October 1999
Jorasch et al.
5969318
October 1999
Mackenthun
5970143
October 1999
Schneier et al.
5970470
October 1999
Walker et al.
5970478
October 1999
Walker et al.
5970480
October 1999
Kalina
5970482
October 1999
Pham
5970483
October 1999
Evans
5974148
October 1999
Stambler
5978467
November 1999
Walker et al.
5983196
November 1999
Wendkos
5987434
November 1999
Libman
5987454
November 1999
Hobbs
5987498
November 1999
Athing et al.
5991736
November 1999
Ferguson et al.
5991738
November 1999
Ogram
5991748
November 1999
Taskett
5991751
November 1999
Rivette et al.
5991780
November 1999
Rivette
5995948
November 1999
Whitford
5995976
November 1999
Walker et al.
5999596
December 1999
Walker et al.
5999907
December 1999
Donner
5999971
December 1999
Buckland
6000033
December 1999
Kelley et al.
6000832
December 1999
Franklin et al.
6001016
December 1999
Walker et al.
6003762
December 1999
Hayashida
6005939
December 1999
Fortenberry et al.
6006205
December 1999
Loeb et al.
6006249
December 1999
Leong
6009415
December 1999
Shurling et al.
6009442
December 1999
Chen et al.
6010404
January 2000
Walker et al.
6012088
January 2000
Li et al.
6012983
January 2000
Walker et al.
6014439
January 2000
Walker et al.
6014635
January 2000
Harris et al.
6014636
January 2000
Reeder
6014638
January 2000
Burge et al.
6014641
January 2000
Loeb et al.
6014645
January 2000
Cunningham
6016476
January 2000
Maes et al.
6016810
January 2000
Ravenscroft
6018714
January 2000
Risen, Jr.
6018718
January 2000
Walker et al.
6024640
February 2000
Walker et al.
6026398
February 2000
Brown et al.
6026429
February 2000
Jones et al.
6029153
February 2000
Bauchner et al.
6029890
February 2000
Austin
6032134
February 2000
Weissman
6032136
February 2000
Brake, Jr. et al.
6032147
February 2000
Williams et al.
6036099
March 2000
Leighton
6038547
March 2000
Casto
6038552
March 2000
Fleischl et al.
6042006
March 2000
Van Tilburg et al.
6044362
March 2000
Neely
6044402
March 2000
Jacobson et al.
6045039
April 2000
Stinson et al.
6047268
April 2000
Bartoli et al.
6049778
April 2000
Walker et al.
6049782
April 2000
Gottesman et al.
6049835
April 2000
Gagnon
6055637
April 2000
Hudson et al.
6061665
May 2000
Bahreman
6064987
May 2000
Walker et al.
6065120
May 2000
Laursen et al.
6065675
May 2000
Teicher
6067531
May 2000
Hoyt et al.
6070147
May 2000
Harms et al.
6070153
May 2000
Simpson
6070244
May 2000
Orchier et al.
6073105
June 2000
Sutcliffe et al.
6073113
June 2000
Guinan
6075519
June 2000
Okatani et al.
6076072
June 2000
Libman
6081790
June 2000
Rosen
6081810
June 2000
Rosenzweig et al.
6081900
June 2000
Subramaniam et al.
6085168
July 2000
Mori et al.
6088444
July 2000
Walker et al.
6088451
July 2000
He et al.
6088683
July 2000
Jalili
6088686
July 2000
Walker et al.
6088700
July 2000
Larsen et al.
6091817
July 2000
Bertina et al.
6092057
July 2000
Zimmerman et al.
6092192
July 2000
Kanevsky et al.
6092196
July 2000
Reiche
6095412
August 2000
Bertina et al.
6098070
August 2000
Maxwell
6101486
August 2000
Roberts et al.
6104716
August 2000
Crichton et al.
6105006
August 2000
Davis et al.
6105007
August 2000
Norris
6105012
August 2000
Chang et al.
6105865
August 2000
Hardesty
6111858
August 2000
Greaves et al.
6112181
August 2000
Shear et al.
6115642
September 2000
Brown et al.
6115690
September 2000
Wong
6119093
September 2000
Walker et al.
6119099
September 2000
Walker et al.
6128599
October 2000
Walker et al.
6128602
October 2000
Northington et al.
6131810
October 2000
Weiss et al.
6134549
October 2000
Regnier et al.
6134592
October 2000
Montulli
6135349
October 2000
Zirkel
6138106
October 2000
Walker et al.
6138118
October 2000
Koppstein et al.
6141651
October 2000
Riley et al.
6141666
October 2000
Tobin
6144848
November 2000
Walsh et al.
6144946
November 2000
Iwamura
6144948
November 2000
Walker et al.
6145086
November 2000
Bellemore et al.
6148293
November 2000
King
6151584
November 2000
Papierniak et al.
6154750
November 2000
Roberge et al.
6154879
November 2000
Pare et al.
6161113
December 2000
Mora et al.
6161182
December 2000
Nadooshan
6164533
December 2000
Barton
6170011
January 2001
Beck et al.
6178511
January 2001
Cohen et al.
6182052
January 2001
Fulton et al.
6182059
January 2001
Angotti et al.
6182142
January 2001
Win et al.
6182220
January 2001
Chen et al.
6182225
January 2001
Hagiuda et al.
6185242
February 2001
Arthur et al.
6188309
February 2001
Levine
6189029
February 2001
Fuerst
6189787
February 2001
Dorf
6195644
February 2001
Bowie
6199077
March 2001
Inala et al.
6201948
March 2001
Cook et al.
6202005
March 2001
Mahaffey
6202054
March 2001
Lawlor et al.
6202066
March 2001
Barkley et al.
6202151
March 2001
Musgrave et al.
6202158
March 2001
Urano et al.
6208978
March 2001
Walker et al.
6208984
March 2001
Rosenthal
6213391
April 2001
Lewis
6216115
April 2001
Barrameda et al.
6219639
April 2001
Bakis et al.
6219706
April 2001
Fan
6222914
April 2001
McMullin
6223168
April 2001
McGurl et al.
6226623
May 2001
Schein et al.
6226679
May 2001
Gupta
6226752
May 2001
Gupta et al.
6227447
May 2001
Campisano
6230148
May 2001
Pare et al.
6243688
June 2001
Kalina
6243816
June 2001
Fang et al.
6253327
June 2001
Zhang et al.
6253328
June 2001
Smith, Jr.
6256664
July 2001
Donoho et al.
6260026
July 2001
Tomida et al.
6266648
July 2001
Baker, III
6266683
July 2001
Yehuda et al.
6267292
July 2001
Walker et al.
6269348
July 2001
Pare et al.
6275944
August 2001
Kao et al.
6278996
August 2001
Richardson et al.
6289322
September 2001
Kitchen et al.
6292786
September 2001
Deaton et al.
6298330
October 2001
Gardenswartz et al.
6298356
October 2001
Jawahar et al.
6301567
October 2001
Leong et al.
6308273
October 2001
Goertzel et al.
6308274
October 2001
Swift
6311275
October 2001
Jin et al.
6315195
November 2001
Ramachandran
6317834
November 2001
Gennaro et al.
6317838
November 2001
Baize
6324524
November 2001
Lent et al.
6327573
December 2001
Walker et al.
6327575
December 2001
Katz
6327578
December 2001
Linehan
6330543
December 2001
Kepecs
6332192
December 2001
Boroditsky et al.
6336104
January 2002
Walker et al.
6339423
January 2002
Sampson et al.
6341724
January 2002
Campisano
6343279
January 2002
Bissonette et al.
6343323
January 2002
Kalpio et al.
6345261
February 2002
Feidelson
6349242
February 2002
Mahaffey
6349290
February 2002
Horowitz et al.
6349336
February 2002
Sit et al.
6363381
March 2002
Lee et al.
6366682
April 2002
Hoffman et al.
6370562
April 2002
Page et al.
6381587
April 2002
Guzelsu
6385591
May 2002
Mankoff
6385652
May 2002
Brown et al.
6401125
June 2002
Makarios et al.
6401211
June 2002
Brezak, Jr. et al.
6405181
June 2002
Lent et al.
6408389
June 2002
Grawrock et al.
6411933
June 2002
Maes et al.
6411947
June 2002
Rice et al.
6418457
July 2002
Schmidt et al.
6424949
July 2002
Deaton et al.
6438594
August 2002
Bowman-Amuah
6438666
August 2002
Cassagnol et al.
6446053
September 2002
Elliott
6449765
September 2002
Ballard
6452613
September 2002
Lefebvre et al.
6453353
September 2002
Win et al.
6460141
October 2002
Olden
6470357
October 2002
Garcia, Jr. et al.
6484149
November 2002
Jammes
6487641
November 2002
Cusson et al.
6490601
December 2002
Markus et al.
6493677
December 2002
von Rosen et al.
6493685
December 2002
Ensel et al.
6496855
December 2002
Hunt et al.
6496936
December 2002
French et al.
6498657
December 2002
Kuntz et al.
6507912
January 2003
Matyas, Jr. et al.
6510523
January 2003
Perlman et al.
6513019
January 2003
Lewis
6519763
February 2003
Kaufer et al.
6526404
February 2003
Slater et al.
6532284
March 2003
Walker et al.
6535855
March 2003
Cahill et al.
6535917
March 2003
Zamanzadeh et al.
6535980
March 2003
Kumar et al.
6539424
March 2003
Dutta
6557039
April 2003
Leong et al.
6560581
May 2003
Fox et al.
6567791
May 2003
Lent et al.
6574348
June 2003
Venkatesan et al.
6580814
June 2003
Ittycheriah et al.
6581040
June 2003
Wright et al.
6584505
June 2003
Howard et al.
6584508
June 2003
Epstein et al.
6589291
July 2003
Boag et al.
6592044
July 2003
Wong et al.
6607127
August 2003
Wong
6609106
August 2003
Robertson
6609113
August 2003
O'Leary et al.
6609125
August 2003
Layne et al.
6609198
August 2003
Wood et al.
6609654
August 2003
Anderson et al.
6618579
September 2003
Smith et al.
6618806
September 2003
Brown et al.
6623415
September 2003
Gates et al.
6631849
October 2003
Blossom
6640302
October 2003
Subramaniam et al.
6641050
November 2003
Kelley et al.
6668322
December 2003
Wood et al.
6671818
December 2003
Mikurak
6675261
January 2004
Shandony
6684212
January 2004
Day et al.
6684248
January 2004
Janacek et al.
6684384
January 2004
Bickerton et al.
6687222
February 2004
Albert et al.
6687245
February 2004
Fangman et al.
6697947
February 2004
Matyas, Jr. et al.
6714987
March 2004
Amin et al.
6718482
April 2004
Sato et al.
6718535
April 2004
Underwood
6725269
April 2004
Megiddo
6727802
April 2004
Kelly et al.
6735695
May 2004
Gopalakrishnan et al.
6738779
May 2004
Shapira
D490840
June 2004
Arakaki et al.
D491186
June 2004
Arakaki et al.
D491953
June 2004
Arakaki et al.
6751654
June 2004
Massarani et al.
6754833
June 2004
Black et al.
6755341
June 2004
Wong et al.
6763388
July 2004
Tsimelzon
6766370
July 2004
Glommen et al.
6769605
August 2004
Magness
6772146
August 2004
Khemlani et al.
6785810
August 2004
Lirov et al.
D496365
September 2004
Liu et al.
6789115
September 2004
Singer et al.
6792572
September 2004
Frohlick
6805288
October 2004
Routhenstein et al.
6810395
October 2004
Bharat
D498236
November 2004
Liu et al.
6819219
November 2004
Bolle et al.
6820202
November 2004
Wheeler et al.
6826696
November 2004
Chawla et al.
6832202
December 2004
Schuyler et al.
6832587
December 2004
Wampula et al.
6836803
December 2004
Swartz et al.
6847991
January 2005
Kurapati
6856970
February 2005
Campbell et al.
6865547
March 2005
Brake Jr. et al.
6868391
March 2005
Hultgren
6892231
May 2005
Jager
6907566
June 2005
McElfresh et al.
6925481
August 2005
Singhal et al.
6934848
August 2005
King et al.
6937976
August 2005
Apte
6938158
August 2005
Azuma
6950936
September 2005
Subramaniam et al.
6954932
October 2005
Nakamura et al.
6957337
October 2005
Chainer et al.
6965939
November 2005
Cuomo et al.
6970830
November 2005
Samra et al.
6976164
December 2005
King et al.
6980962
December 2005
Arganbright et al.
6983421
January 2006
Lahti, et al.
6992786
January 2006
Breding et al.
6999938
February 2006
Libman
7006983
February 2006
Packes, Jr. et al.
7010512
March 2006
Gillin et al.
7020696
March 2006
Perry et al.
7032110
April 2006
Su et al.
7051199
May 2006
Berson et al.
7051330
May 2006
Kaler et al.
7051929
May 2006
Li
7058660
June 2006
Scott
7058817
June 2006
Ellmore
7069434
June 2006
Ilnicki et al.
7076453
July 2006
Jammes et al.
7080036
July 2006
Drummond et al.
7089203
August 2006
Crookshanks
7089208
August 2006
Levchin et al.
7089503
August 2006
Bloomquist et al.
7093020
August 2006
McCarty et al.
7093282
August 2006
Hillhouse
7103556
September 2006
Del Rey et al.
7117161
October 2006
Bruce
7117239
October 2006
Hansen
7124101
October 2006
Mikurak
7134075
November 2006
Hind et al.
7137006
November 2006
Grandcolas et al.
7139686
November 2006
Critz et al.
7163153
January 2007
Blossom
7185094
February 2007
Marquette et al.
7188181
March 2007
Squier et al.
7191952
March 2007
Blossom
7195154
March 2007
Routhenstein
7197470
March 2007
Arnett
7203909
April 2007
Horvitz et al.
7225249
May 2007
Barry
7228155
June 2007
Saunders
7249112
July 2007
Berardi et al.
7299201
November 2007
Jammes
7312707
December 2007
Bishop et al.
7321864
January 2008
Gendler
7357331
April 2008
Blossom
7370011
May 2008
Bennett
7395241
July 2008
Cook et al.
7480631
January 2009
Merced et al.
7493288
February 2009
Biship et al.
7506806
March 2009
Bonalle et al.
2001/0002487
May 2001
Grawrock et al.
2001/0011250
August 2001
Paltenghe et al.
2001/0011255
August 2001
Asay et al.
2001/0012974
August 2001
Mahaffey
2001/0016835
August 2001
Hansmann et al.
2001/0027441
October 2001
Wankmueller
2001/0027474
October 2001
Nachman et al.
2001/0029464
October 2001
Schweitzwer
2001/0032183
October 2001
Landry
2001/0032184
October 2001
Tenembaum
2001/0032312
October 2001
Runje et al.
2001/0034663
October 2001
Teveler et al.
2001/0038033
November 2001
Habib
2001/0047295
November 2001
Tenembaum
2001/0047342
November 2001
Cuervo
2001/0051917
December 2001
Bissonette et al.
2001/0054003
December 2001
Chien et al.
2001/0054059
December 2001
Marks et al.
2002/0002479
January 2002
Almog et al.
2002/0007313
January 2002
Mai et al.
2002/0007460
January 2002
Azuma
2002/0010599
January 2002
Levison
2002/0010627
January 2002
Lerat
2002/0010668
January 2002
Travis et al.
2002/0018585
February 2002
Kim
2002/0019938
February 2002
Aarons
2002/0023108
February 2002
Daswani et al.
2002/0029269
March 2002
McCarty et al.
2002/0031230
March 2002
Sweet et al.
2002/0032613
March 2002
Buettgenbach et al.
2002/0032650
March 2002
Hauser et al.
2002/0042808
April 2002
Smith et al.
2002/0059141
May 2002
Davies et al.
2002/0069172
June 2002
Omshehe et al.
2002/0077964
June 2002
Brody et al.
2002/0077978
June 2002
O'Leary et al.
2002/0087447
July 2002
McDonald et al.
2002/0087471
July 2002
Ganesan et al.
2002/0095443
July 2002
Kovack
2002/0099826
July 2002
Summers et al.
2002/0099936
July 2002
Kou et al.
2002/0104006
August 2002
Boate et al.
2002/0104017
August 2002
Stefan
2002/0107788
August 2002
Cunningham
2002/0111890
August 2002
Sloan et al.
2002/0128977
September 2002
Nambiar et al.
2002/0143874
October 2002
Marquette et al.
2002/0152163
October 2002
Bezos et al.
2002/0156900
October 2002
Marquette et al.
2002/0165949
November 2002
Na
2002/0174010
November 2002
Rice, III
2002/0178113
November 2002
Clifford et al.
2002/0184507
December 2002
Makower et al.
2002/0188869
December 2002
Patrick
2002/0191548
December 2002
Ylonen et al.
2002/0198806
December 2002
Blagg et al.
2003/0001888
January 2003
Power
2003/0018915
January 2003
Stoll
2003/0023880
January 2003
Edward et al.
2003/0034388
February 2003
Routhenstein et al.
2003/0037131
February 2003
Verma
2003/0037142
February 2003
Munger et al.
2003/0040995
February 2003
Daddario et al.
2003/0041165
February 2003
Spencer et al.
2003/0046587
March 2003
Bheemarasetti et al.
2003/0046589
March 2003
Gregg
2003/0051026
March 2003
Carter et al.
2003/0055871
March 2003
Roses
2003/0061168
March 2003
Routhenstein
2003/0070069
April 2003
Belapurkar et al.
2003/0070084
April 2003
Satomaa et al.
2003/0074580
April 2003
Knouse et al.
2003/0079147
April 2003
Hsieh et al.
2003/0084345
May 2003
Bjornestad et al.
2003/0084647
May 2003
Smith et al.
2003/0085286
May 2003
Kelley et al.
2003/0088489
May 2003
Peters et al.
2003/0088552
May 2003
Bennett et al.
2003/0097574
May 2003
Upton
2003/0105981
June 2003
Miller et al.
2003/0110399
June 2003
Rail
2003/0149594
August 2003
Beazley et al.
2003/0154171
August 2003
Karp et al.
2003/0154403
August 2003
Keinsley et al.
2003/0159072
August 2003
Bellinger et al.
2003/0163700
August 2003
Paatero
2003/0163733
August 2003
Barriga-Caceres et al.
2003/0167229
September 2003
Ludwig et al.
2003/0177067
September 2003
Cowell et al.
2003/0182246
September 2003
Johnson et al.
2003/0187787
October 2003
Freund
2003/0191549
October 2003
Otsuka et al.
2003/0204460
October 2003
Robinson et al.
2003/0218066
November 2003
Fernandes et al.
2003/0225688
December 2003
Dobbins
2004/0029569
February 2004
Khan et al.
2004/0031856
February 2004
Atsmon et al.
2004/0049451
March 2004
Berardi
2004/0049702
March 2004
Subramaniam et al.
2004/0078328
April 2004
Talbert et al.
2004/0094624
May 2004
Fernandes et al.
2004/0111610
June 2004
Slick et al.
2004/0117409
June 2004
Scahill et al.
2004/0133787
July 2004
Doughty et al.
2004/0146159
July 2004
Rosen
2004/0149544
August 2004
Dal Ferro
2004/0153378
August 2004
Perkowski
2004/0159700
August 2004
Khan et al.
2004/0162773
August 2004
Del Rey et al.
2004/0210498
October 2004
Freund
2004/0215514
October 2004
Quinlan
2004/0232223
November 2004
Beenau et al.
2004/0236688
November 2004
Bozeman
2004/0239481
December 2004
Beenau et al.
2004/0252012
December 2004
Beenau et al.
2004/0254991
December 2004
Malik et al.
2005/0033619
February 2005
Barnes et al.
2005/0035847
February 2005
Bonalle et al.
2005/0040242
February 2005
Beenau et al.
2005/0055306
March 2005
Miller et al.
2005/0060579
March 2005
Dickelman et al.
2005/0071637
March 2005
Shirakawa
2005/0077349
April 2005
Bonalle et al.
2005/0080747
April 2005
Anderson et al.
2005/0082362
April 2005
Anderson et al.
2005/0086160
April 2005
Wong et al.
2005/0086177
April 2005
Anderson et al.
2005/0091126
April 2005
Junger
2005/0091138
April 2005
Awatsu
2005/0091492
April 2005
Benson et al.
2005/0116024
June 2005
Beenau et al.
2005/0120180
June 2005
Schornbach et al.
2005/0171898
August 2005
Bishop et al.
2005/0193056
September 2005
Schaefer et al.
2005/0206499
September 2005
Fisher
2005/0216421
September 2005
Barry et al.
2005/0278641
December 2005
Mansour et al.
2005/0289051
December 2005
Allin et al.
2006/0029261
February 2006
Hoffman et al.
2006/0036553
February 2006
Gupta et al.
2006/0041540
February 2006
Shannon et al.
2006/0116949
June 2006
Wehunt et al.
2006/0173706
August 2006
Allin et al.
2006/0249574
November 2006
Brown et al.
2006/0261927
November 2006
Kelly et al.
2006/0271397
November 2006
Allin et al.
2006/0271477
November 2006
Allin et al.
2006/0271478
November 2006
Allin et al.
2006/0271479
November 2006
Allin et al.
2006/0271480
November 2006
Allin et al.
2006/0274970
December 2006
Seki et al.
2007/0034700
February 2007
Poidomani et al.
2007/0078771
April 2007
Allin et al.
2007/0136211
June 2007
Brown et al.
2007/0208671
September 2007
Brown et al.
2007/0215688
September 2007
Routhenstein
2007/0265924
November 2007
Schwarz
2008/0010202
January 2008
Schwarz
2009/0043651
February 2009
Schwarz
2009/0100508
April 2009
Labaton
2009/0192940
July 2009
Mann, III et al.
Foreign Patent Documents
2430549
Jun., 2002
CA
19731293
Jan., 1999
DE
0855659
Jul., 1998
EP
0884877
Dec., 1998
EP
0917119
May., 1999
EP
1014318
Jun., 2000
EP
1022664
Jul., 2000
EP
1056043
Nov., 2000
EP
1089516
Apr., 2001
EP
H10187467
Jul., 1998
JP
2000/324329
Nov., 2000
JP
2001/134672
May., 2001
JP
2005/242976
Sep., 2005
JP
WO 97/43736
Nov., 1997
WO
WO 9810368
Mar., 1998
WO
WO 99/40507
Aug., 1999
WO
WO 99/52051
Oct., 1999
WO
WO 00/68858
Nov., 2000
WO
WO 01/18656
Mar., 2001
WO
WO 01/35355
May., 2001
WO
WO 01/43084
Jun., 2001
WO
WO 01/88659
Nov., 2001
WO
WO 02/17082
Feb., 2002
WO
WO 2004/079603
Sep., 2004
WO
WO 2005/101975
Nov., 2005
WO
WO 2006/011904
Feb., 2006
WO
WO 2006/011904
Feb., 2006
WO
WO 2006/060370
Jun., 2006
WO
WO 2006/105092
Oct., 2006
WO
WO 2006/116772
Nov., 2006
WO
Other References
Kutler, A Different Drummer on the Data Highway, American Banker, Section: No. 91, vol. 160, May 12, 1995, p. 14. cited by other
.
Epper, A Player Goes After Big Bucks in Cyberspace, American Banker, vol. 160, No. 86, ISSN: 0002-7561, May 5, 1995, p. 17. cited by other
.
Berry et al., A potent new tool for selling databse, Business Week, Cover Story, Sep. 5, 1994, pp. 56-62. cited by other
.
Applets, java.sun.com, May 21, 1999. cited by other
.
Associates National Bank (DE) Credit Card, The Associates, www.theassociates.com/consumer/credit.sub.--cards/main.html, Apr. 6, 1999, 6 pages. cited by other
.
At Your Request, www.wingspanbank.com, Sep. 28, 1999. cited by other
.
Anonymous, Aversion Therapy: Banks Overcoming Fear of the 'Net to Develop Safe Internet-based Payment System w/ Netscape Communicator, Network World, ISSN: 0887-7661, Dec. 12, 1994. cited by other
.
JAVA, Banking on JAVA(TM) Technology, java.sun.com, May 21, 1999. cited by other
.
Bechtel Construction Operations Incorporated Standardizes on Primavera's Expedition Contract Management Software, Business Wire, Jul. 27, 1999. cited by other
.
Anonymous, CORBA Overview, arch2.htm at pent21.infosys.tuwien.ac.at, May 25, 1999. cited by other
.
Vandenengel, Cards on the Internet: Advertising on a $3 Bill, Industry Intelligence, Feb. 1, 1995, pp. 46-48. cited by other
.
Kutler, Cash Card Creator Looking Beyond Mondex, Feb. 9, 1995. cited by other
.
Bank, Cash, Check,Charge--What's Next?, Seattle Times, Mar. 6, 1995. cited by other
.
Consortium Created to Manage Common Electronic Purse Specifications, http://www.visa.com/av/news/PRmisc051199.vhtml, printed Feb. 23, 2001. cited by other
.
Construction Financing to Build Your Own Home, ISBN: 0962864307, Jul. 1990. cited by other
.
Civitello Jr., Construction Operations Manual of Policies and Procedures, Third Edition, 2000. cited by other
.
Marchman, Construction Scheduling with Primavera Project Planner, May 25, 1999. cited by other
.
Chester, Cross-platform integration with XML and SOAP, IT PTO Sep.-Oct. 2001. cited by other
.
Mitchell, Cyberspace: Crafting Software . . . , Business Week, Feb. 27, 1999, pp. 78-86. cited by other
.
Friedman, Dictionary of Business Terms, Barron's Third Edition, Copyright 2000. cited by other
.
Strassel, Dutch Software Concern Experiments with Electronic `Cash` in Cyberspace, The Wall Street Journal, Apr. 17, 1995. cited by other
.
Post, E-Cash: Can't Live With It, Can't Live Without It, The American Lawyer, Mar. 1, 1995, pp. 116-117. cited by other
.
Thomas, Enterprise Javabeans(TM) Technology: Server Component Model for the Java(TM) platform, java.sun.com, May 2, 1999. cited by other
.
Maize, Fannie Mae on the Web, Doucment ID: 52079, May 8, 1995. cited by other
.
FreeMarkets, printed on Apr. 26, 1999. cited by other
.
The Gale Group, G&D America's Multi-application Smart Card Selected for Combined Payroll and `Virtual Banking` Program in Mexico, Business Wire, Apr. 24, 1998, p. 241047. cited by other
.
Getting Smart with Java: Sun Micro Says American Express to Use Java for Smart Card, ABCNews.com, printed on Jun. 6, 2000. cited by other
.
Getting Started: Specific GE TPN Post Service Use Guidelines, printed on Apr. 26, 1999. cited by other
.
Harris, Harris InfoSource, printed on Apr. 26, 1999. cited by other
.
Knowles, Improved Internet Security Enabling On-Line Commerce, PCWeek, vol. 12, No. 11, ISSN: 0740-1604, Mar. 20, 1995. cited by other
.
Meredith, Internet bank moves closer to virtual reality, USA Today, May 5, 1995. cited by other
.
Radosevich, Is Work Flow Working?, CNN.com, Apr. 6, 1999 at &lt;http://www.cnn.com/TECH/computing/9904/06/workflow/ent.idg, p. 1 of 5, retrieved from the internet on Nov. 28, 2005. cited by other
.
JAVA, JAVA (TM) Technology in the Real World, java.sun.com, May 21, 1999. cited by other
.
JAVA, JAVA(TM) Remote Method Invocation (RMI) Interface, java.sun.com, 05/32/1999. cited by other
.
JAVA, JAVA(TM) Servlet API, java.sun.com, May 21, 1999. cited by other
.
OMG, Library, www.omg.com, May 25, 1999. cited by other
.
Method of Protecting Data on a Personal Computer, IBM Corporation, TDB 11-85, Order 85A 62426, Nov. 1, 1995, p. 2530. cited by other
.
Clark, Microsoft, Visa to Jointly Develop PC Electronic-Shopping Software, The Wall Street Journal, Nov. 9, 1994, WSJ B9. cited by other
.
Sirbu, et al, NetBill: An Internet Commerce System Optimized for Network Delivered Services, printed on Feb. 27, 1995. cited by other
.
Mitchell, Netlink Goes After An Unbanked Niche, Card Technology, ISSN: 1093-1279, Sep. 1999, p. 22. cited by other
.
Houlder, OFT Gives the Individual Top Priority: Report Calls for Deregulation of Business Lending, Document ID: 91716, Jun. 8, 1994. cited by other
.
Omware, Inc., Web Pages, Feb. 2000, Retrieved from http://web.archive.org/web20000226033405/www.omware.com/products.html, Retrieved from the interneet on Nov. 28, 2005. cited by other
.
Anonymous, Overview of CORBA, May 25, 1999. cited by other
.
Harris, Planning Using Primavera Project Planner P3 Version 3.0, User Guide, Copyright 1999 by Eastwood Harry Pty Ltd., 1999. cited by other
.
Johnston, Pondering Passport: Do You Trust Microsoft With Your Data?, www.pcworld.com/resource/printable/article/0.aid,63244,00.asp, Sep. 24, 2001. cited by other
.
Primavera Systems, Inc.--How the World Manages Projects, Expedition Contract Control Software, www.primavera.com, Jun. 23, 2005. cited by other
.
Primavera and PurchasePro.com to Create E-Commerce Marketplace for Construction Industry, Primavera Ships P3, version 3.0, www.purchasepro.com/, Sep. 21, 1999, pp. 1-3. cited by other
.
Product Data Integration Technologies, Inc., Step Integratin Authors, printed on Apr. 26, 1999. cited by other
.
Resource Center: Consolidated Edison Selects GE TPN Post, printed Apr. 26, 1999. cited by other
.
Kormann, Risks of the Passport Single Signon Protocol, Computer Networks, Elsevier Science Press, vol. 33, Sep. 20, 2003, pp. 51-58. cited by other
.
SBA: Pro-Net, U.S. Small Business Administration Procurement Marketing and Access Network, Last Modified: Apr. 1, 1999. cited by other
.
Jepsen, SOAP Cleans up interoperability problems on the web, IT PTO, Jan./Feb. 2001. cited by other
.
Safe Single-Sign-On Protocol with Minimal Password Exposure No Decryption and Technoloy Adaptivity, IBM Corporation, TDB 03-95, Order 95A, Mar. 1, 1995, pp. 245-248. cited by other
.
Sun Microsystems, Inc., Schema for Representing CORBA Objects in an LDAP directory, May 21, 1999, pp. 1-9. cited by other
.
Jakobsson et al., Secure and lightweight advertising on the web, Computer Networks, 31 (1999) 1101-1109. cited by other
.
Servlet/Applet/HTML Authentication Process with Single Sign-On, IBM Corporation, IBM Order: 00A6004, Jan. 1, 2000. cited by other
.
Shibata, Seventh International Conference on Parallel and Distributed Systems: Workshops, IEEE Computer Society, Jul. 4-7, 2000. cited by other
.
Siebel, Siebel: Ensuring Customer Success, www.siebel.com, Nov. 17, 1999. cited by other
.
SmartAxis, How it works, http://www.smartaxis.co.uk/seller/howitworks.html, printed on Feb. 23, 2001. cited by other
.
Thomas Publishing Company, SoluSource: For Engineers by Engineers, Thomas Publishing Company, Apr. 26, 1999. cited by other
.
JAVA, Staying in Touch with JNDI, java.sun.com, May 21, 1999. cited by other
.
Summary of The At Your Request Architecture, First USA Bank Confidential and Proprietary, Apr. 2, 1999, pp. 1-8. cited by other
.
Temporary Global Passwords, IBM Corporation, IBM TDB v36, n3, 03-93, Order 93A 60636, Mar. 1, 1993, pp. 451-454. cited by other
.
JAVA, The JDBC(TM) Data Access API, java.sun.com, May 21, 1999. cited by other
.
The check is in the email, Information Today, vol. 12, No. 3, ISSN: 8755-6286, 03/01995. cited by other
.
Thomas Publishing Company, ThomasNet, 04/26,1999. cited by other
.
Ritz, Total Construction Project Management, McGraw-Hill, 1994. cited by other
.
Welcome to MUSE, Apr. 26, 1999. cited by other
.
OMG, Welcome to OMG's CORBA for Beginners Page!, www.omg.co, May 25, 1999. cited by other
.
OMG, What is CORBA?, www.omg.com, May 25, 1999. cited by other
.
Fujimura et al., XML Voucher: Generic Voucher Language, Feb. 2003. cited by other
.
eCharge, eCharge Corporation, www.echarge.com, Dec. 3, 1999. cited by other
.
Hasting, Nelson et. al., A Case Study of Authenticated and Secure File Transfer The Iowa Campaign Finance Reporting System, (1997). cited by other
.
Alshawi, M et. al., An IFC Web Based Collaborative Construction Computer Environment Wisper, (1999). cited by other
.
Fusaro, Roberta, Builders Moving to Web tools Computerworld, Nov. 16, 1998, vol. 32, No. 46, pp. 51, 53. cited by other
.
Microsoft, CNBC on MSN Money; Microsoft Money 2003 Deluxe Reviewer's Guide, Aug. 2002. cited by other
.
Seibert, Paul, Facilities Planning & Design for Financial Institutions Bankline Publications, ISBN: 1-55738-780-X, (1996). cited by other
.
Owens, David, Facilities Planning & Relocation RSMeans, ISBN: 0-87629-281-3, (1993). cited by other
.
Larsen, Amy, Internet goes to Work for Builders, InterWeek, Nov. 16, 1998, Issue 741. cited by other
.
Frank, John N. Frank, Beyond Direct Mail, Credit Card Management, vol. 9, Iss. 5, Aug. 1996, 4pgs. cited by other
.
Mary C. Lacity, et al., Mary C. Lacity, et al., The Information Systems Outsourcing Bandwagon, Sloan Management Review, vol. 35, No. 1, Fall 1993, p. 73-86. cited by other
.
Kilian-Kehr, Roger, Mobile Security with Smartcards Dissertation, Apr. 2002. cited by other
.
Youll, James, Peer to Peer Transactions in Agent Mediated Electronic Commerce, Aug. 2001. cited by other
.
Point for Windows Version 3.x Interface Marketing Guide.pdf, Copyright .COPYRGT.1999. cited by other
.
Primavera Expedition User Guide, Copyright .COPYRGT.1998. cited by other
.
Primavera Systems Delivers Expedition Express,Business Wire, Feb. 23, 1999. cited by other
.
Van Collie, Shimon Craig, Problem Disbursement Control Needed Construction Loan Tool from PriMerit NewTrend, Apr. 1990. cited by other
.
Deckmyn, Dominique, San Francisco manages $45M project via web-based Service, Computerworld, Aug. 9, 1999, vol. 33, No. 32, p. 14. cited by other
.
Mosig, Richard, Software Review: the Construction Project Manager Cost Engineering, Jan. 1996, vol. 38, No. 1, pp. 7-8. cited by other
.
Hernandez, Tomas et al., Software Solutions Building Design & Construction, Nov. 1999, vol. 40, No. 11, pp. 38-40. cited by other
.
Taylor, Telecommunications Demand Analysis in Transition, Proceedings of the 31st Hawaii International Conference on System Sciences, vol. 5, Jan. 6-9, 1998, pp. 409-415. cited by other
.
Brown, Keith, The Builders Revolution, Jan. 1998. cited by other
.
Cotts, David, The Facility Management Handbook Second Edition AMACM, ISBN: 0-8144-030-8, (1998). cited by other
.
Carden, Philip, The New Face of Single Sign-on, Network Computing, http://www.networkcomputing.com, printed Dec. 29, 2000, 4 pages. cited by other
.
Yee, Bennet, Using Secure Coprocessors, May 1994. cited by other.
Primary Examiner: Al-Hashemi; Sana
Attorney, Agent or Firm: Hunton & Williams LLP
Parent Case Text
RELATED APPLICATIONS
This patent application is a Continuation of U.S. patent application Ser.
No. 10/262,286, filed on Oct. 2, 2002 now U.S. Pat. No. 7,058,660
entitled "System and Method for Network-Based Project Management", which
are hereby incorporated by reference in its entirety.
Claims
What is claimed is:
1. A project management system, comprising: a project database associated with a network, the project database storing information associated with at least one project being
carried out by at least a first entity having at least one sub-entity, wherein the first entity comprises a business organization of one or more persons and the at least one sub-entity comprises a business organization of one or more persons and is
associated with the first entity in a business relationship; a project management tool including: a project information module to manage information associated with the at least one project and one or more related sub-projects in a relational project
hierarchy, at least one project-component module to manage at least sub-entity specific project information, in cooperation with the project information module; and at least one user system connected to the network to access the project management tool
over the network, based on an access level associated with the user, wherein the access level associated with the user is determined at least in part by input information regarding the access level received from the user, wherein the access level
associated with the user is verified by the project management system, wherein the access level comprises at least one of (1) reader access, (2) editor access, (3) coordinator level access and (4) administrator access; wherein the reader access includes
reader access function comprising access to one or more documents and information based on one or more projects to which the user has access; wherein the editor access includes editor access function comprising the reader access function and an
additional editor function of creating one or more records associated with one or more of programs, projects and sub-projects; wherein the coordinator access includes coordinator access function comprising the editor access function and an additional
coordinator function of editing and creating one or more of programs, projects and sub-project records; wherein the administrator access includes administrator access function comprising the coordinator access function and an additional administrator
function of determining access for one or more programs and projects.
2. The system of claim 1, wherein the first entity comprises a corporation and the at least one sub-entity comprises at least one of a line of business of the corporation, a division of the corporation, a subsidiary of the corporation and a
support unit of the corporation.
3. The system of claim 1, wherein the project database comprises a relational database.
4. The system of claim 1, wherein the project management tool is configured to interface with at least one other project management system, so that a one time entry allows a user to access the at least one other project management system.
5. The system of claim 1, wherein the project management tool further comprises a search module to search the project database for information requested by other modules within the project management tool to create at least one of displays and
reports.
6. The system of claim 1, wherein the at least one project-component module comprises at least one or more of a home module, a project information module, a milestones module, an issues module, a change controls module, a documents module, a
project status reports module, a team member status reports module, a contacts module, a management decisions module, a meetings module, an action items module, a financials module, a new items module, a search module, an archive module, a project
management system coordinator module and a central project management system administrator module.
7. The system of claim 1, wherein the at least one project-component module allows each sub-entity of the first entity to produce at least one report, wherein the at least one report comprises at least one of a consolidated report and a
individualized sub-entity report.
8. The system of claim 1, wherein the project database stores information associated with a plurality of projects.
9. The system of claim 1, wherein the project-component module allows a user to create a customized representation of the project-component module related information in the project database.
10. A project management system, comprising: a project database, comprising a relational database, associated with a network, that stores information associated with at least one project, the at least one project being carried out by at least a
first entity having at least one sub-entity, wherein the first entity comprises a business organization of one or more persons and the at least one sub-entity comprises a business organization of one or more persons and is associated with the first
entity in a business relationship; a project management tool including: a project information module to manage information associated with the at least one project and one or more related sub-projects in a relational project hierarchy, at least one
project-component module to manage at least sub-entity specific project information, in cooperation with the project information module, wherein the at least one project-component module allows the at least one sub-entity to produce at least one report
comprising at least one of a consolidated report and a individualized sub-entity report, and wherein further the project-component module allows a user to create a customized representation of the project-component module related information in the
project database; and at least one user system connected to the network to access the project management tool over the network, based on an access level associated with the user, wherein the access level associated with the user is determined at least
in part by input information regarding the access level received from the user, wherein the access level associated with the user is verified by the project management system and the access level comprises at least one of (1) reader access, (2) editor
access, (3) coordinator level access and (4) administrator access; wherein the reader access includes reader access function comprising access to one or more documents and information based on one or more projects to which the user has access; wherein
the editor access includes editor access function comprising the reader access function and an additional editor function of creating one or more records associated with one or more of programs, projects and sub-projects; wherein the coordinator access
includes coordinator access function comprising the editor access function and an additional coordinator function of editing and creating one or more of programs, projects and sub-project records; wherein the administrator access includes administrator
access function comprising the coordinator access function and an additional administrator function of determining access for one or more programs and projects. Description
FIELD OF THE INVENTION
The present invention relates to the field of project management, and more particularly to network-enabled project management for coordinating different levels of an organization.
BACKGROUND OF THE INVENTION
When an entity, such as a business, academic, government or other organization undertakes a large project, it is desirable to have a system to manage information about the project. For example, it may be desirable to accumulate schedules, costs,
and other information related to the project and to produce reports from the project-related information.
Although some project management systems are available, existing packages are limited in scope and flexibility. For example, the databases storing the project information often have limited storage or other capacities, so that the reports that
may be generated using the project management systems are correspondingly limited.
Further, operationally speaking, each department, line of business or other unit of an organization may employ its own project management system. The project management system used by one unit may not be compatible with the project management
system of another unit or a general project management system used by the business, or by suppliers and other vendors. Sharing data, such as schedules or lists of personnel, between levels of the company or other organization may therefore be difficult. Setting a consistent security policy across all levels of the company or other organization may also be difficult or impossible. Other problems exist.
SUMMARY OF THE INVENTION
The invention overcoming these and other problems in the art relates in one regard to a system and method for managing project information over a network. The inventive system may include a project information database associated with the
network, and a project information management tool. The project information database may store information associated with a project being carried out by a corporate or other organization having at least one sub-entity, such as a subsidiary, division,
foreign unit or other unit. The project information management tool may include a project information module to manage the information associated with the project, and share information using a set of collaborative management tools. These tools may
include at least one cross-entity module and other elements that manage entity-specific information, database access and other resources, and coordinate those resources in the overall database of the information associated with the project.
BRIEF
DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram illustrating a system including a project information system according to an embodiment of the present invention;
FIG. 2 is a blocked diagram illustrating one embodiment of a database shown in FIG. 1;
FIG. 3 is a flow diagram illustrating one embodiment of a method for providing access to a user by a project information system;
FIG. 4 is a block diagram illustrating one embodiment of the project information system of FIG. 1;
FIG. 5 is a block diagram illustrating a section module of a project information system according to the present invention;
FIG. 6 is a screen shot of a sample home page display generated by the home page module of FIG. 4;
FIG. 7 is a screen shot illustrating one embodiment of a project information record generated by a project information module;
FIG. 8 is a screen shot illustrating one embodiment of an initiative information record generated by the project information module;
FIG. 9 is a block diagram illustrating the organization of project information records;
FIG. 10 is a screen shot illustrating one embodiment of a milestone record generated by a milestone module of FIG. 4;
FIG. 11 is a screen shot illustrating one embodiment of an issue record generated by an issue module of FIG. 4;
FIG. 12 is a screen shot illustrating one embodiment of a change control record generated by the change control module of FIG. 4;
FIG. 13 is a screen shot illustrating one embodiment of a document record generated by a documents module of FIG. 4;
FIG. 14 is a screen shot of one embodiment of a project status report generated by a project status report module of FIG. 4;
FIG. 15 is a screen shot illustrating one embodiment of a delivery process status section generated by a project status reports module of FIG. 4;
FIG. 16 is a screen shot illustrating one embodiment of a team member status report generated by a team member status module of FIG. 4;
FIG. 17 is a screen shot illustrating a contact record generated by a contact module of FIG. 4;
FIG. 18 is a screen shot illustrating one embodiment of a management decision record generated by a management decisions module of FIG. 4; FIG. 19 is a screen shot illustrating one embodiment of a meeting record generated by a meetings module of
FIG. 4;
FIG. 20 is a screen shot illustrating one embodiment of an action item record generated by an action items module of FIG. 4;
FIG. 21 is a screen shot illustrating one embodiment of a financial record generated by a financials module of FIG. 4;
FIG. 22 is a flow diagram illustrating one embodiment of a method for managing a project.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
FIG. 1 is a block diagram illustrating one embodiment of an overall system including a project information system, according to an embodiment of the invention. System 1 may include a project information system ("PIS") 10, network 5 and users 2
and 3. PIS 10 may include a server 4 and database 6.
The server 4 may be or include, for instance, a workstation running the Microsoft Windows.TM. NT.TM., Windows.TM. 2000, Unix, Linux, Xenix, IBM AIX.TM., Hewlett-Packard UX.TM., Novell Netware.TM., Sun Microsystems Solaris.TM., OS/2.TM.,
BeOS.TM., Mach, Apache, OpenStep.TM. or other operating system or platform.
Although the database 6 is shown to be located outside project information system ("PIS") 10, database 6 may reside within PIS 10 in other embodiments. The database 6 may be, include or interface to, for example, the Oracle.TM. relational
database sold commercially by Oracle Corp. Other databases, such as Informix.TM., DB2 (Database 2), Sybase or other data storage or query formats, platforms or resources such as OLAP (On Line Analytical Processing), SQL (Standard Query Language), a
storage area network (SAN), Microsoft Access.TM. or others may also be used, incorporated or accessed in the invention.
PIS 10 and users 2 and 3 may communicate to each other through network 5. In one embodiment, PIS 10 may reside on one or both of a user system 2, 3. Although only two user systems are shown, in practice as many systems as needed or desired
maybe used.
In one embodiment, when a user 2, 3 accesses project information system 10, the functions, displays and records to which the user 2, 3 has access may be determined by the status of the user using user system 2, 3.
The communications link 5 may be, include or interface to any one or more of, for instance, the Internet, an intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network) or a MAN (Metropolitan Area Network), a
storage area network (SAN), a frame relay connection, an Advanced Intelligent Network (AIN) connection, a synchronous optical network (SONET) connection, a digital T1, T3, E1 or E3 line, Digital Data Service (DDS) connection, DSL (Digital Subscriber
Line) connection, an Ethernet connection, an ISDN (Integrated Services Digital Network) line, a dial-up port such as a V.90, V.34 or V.34bis analog modem connection, a cable modem, an ATM (Asynchronous Transfer Mode) connection, or an FDDI (Fiber
Distributed Data Interface) or CDDI (Copper Distributed Data Interface) connection. Communications link 5 may furthermore be, include or interface to any one or more of a WAP (Wireless Application Protocol) link, a GPRS (General Packet Radio Service)
link, a GSM (Global System for Mobile Communication) link, a CDMA (Code Division Multiple Access) or TDMA (Time Division Multiple Access) link such as a cellular phone channel, a GPS (Global Positioning System) link, CDPD (cellular digital packet data),
a RIM (Research in Motion, Limited) duplex paging type device, a Bluetooth radio link, or an IEEE 802.11-based radio frequency link. Communications link 5 may yet further be, include or interface to any one or more of an RS-232 serial connection, an
IEEE-1394 (Firewire) connection, a Fibre Channel connection, an IrDA (infrared) port, a SCSI (Small Computer Systems Interface) connection, a USB (Universal Serial Bus) connection or other wired or wireless, digital or analog interface or connection.
Users 1, 2 may communicate to PIS 10 through client systems. The client systems may be or include, for instance, a personal computer running the Microsoft Windows.TM. 95, 98, Millenium.TM., NT.TM., or 2000, Windows.TM.CE.TM., PalmOS.TM., Unix,
Linux, Solaris.TM., OS/2.TM., BeOS.TM., MacOS.TM. or other operating system or platform. The client systems may include a microprocessor such as an Intel x86-based device, a Motorola 68K or PowerPC.TM. device, a MIPS, Hewlett-Packard Precision.TM., or
Digital Equipment Corp. Alpha.TM. RISC processor, a microcontroller or other general or special purpose device operating under programmed control. The client systems may furthermore include electronic memory such as RAM (random access memory) or EPROM
(electronically programmable read only memory), storage such as a hard drive, CDROM or rewritable CDROM or other magnetic, optical or other media, and other associated components connected over an electronic bus, as will be appreciated by persons skilled
in the art. The client systems may also be or include a network-enabled appliance such as a WebTV.TM. unit, radio-enabled Palm.TM. Pilot or similar unit, a set-top box, a networkable game-playing console such as Sony Playstation.TM. or Sega
Dreamcast.TM., a browser-equipped cellular telephone, or other TCP/IP client or other device.
The client systems and PIS 10 may communicate with each other using network-enabled code. Network enabled code may be, include or interface to, for example, Hyper text Markup Language (HTML), Dynamic HTML, Extensible Markup Language (XML),
Extensible Stylesheet Language (XSL), Document Style Semantics and Specification Language (DSSSL), Cascading Style Sheets (CSS), Synchronized Multimedia Integration Language (SMIL), Wireless Markup Language (WML), Java.TM., Java.TM. Beans, Enterprise
Java.TM. Beans, Jini.TM., C, C++, Perl, UNIX Shell, Visual Basic or Visual Basic Script, Virtual Reality Markup Language (VRML), ColdFusion.TM. or other compilers, assemblers, interpreters or other computer languages or platforms.
FIG. 2 is a blocked diagram illustrating an embodiment of the database of FIG. 1. Projects in the PIS 10 may be classified and organized according to larger programs to which the projects belong. In one embodiment, database 206 may include at
least program file, such as program A 220 and program B 240. Each of program A 220 and program B 240 may include projects, such as 222, 232, 242. Each of the projects 222, 232, 242 may further include sub-projects such as sub-projects 224, 226, 234 in
a relational project hierarchy.
In the example shown, program A includes projects 222 and 232 and program B 240 includes project 242. Project 222 may be further sub-divided into sub-projects 224 and 226. In one embodiment, a project may include only one sub-project. For
example, project 232 may include only sub-project 234. Although only two programs 220 and 240, are shown, database 206 may include any number of programs. The database 206 may include as many programs as required or desired. The projects 222, 232, 242
and sub-projects 224, 226, 234 are shown for illustrative purposes only. In practice, programs 220, 240 may include any number of projects and sub-projects.
In one embodiment, each project 222, 232, 242 may include records 225, 227, 235, 245. If a project has sub-projects, the records may be a part of the sub-project or alternatively may be part of the project or program outside of the sub-project.
For example, the record 225 is a part of sub-project 224 of project 222 of program A. Record 227 is a part of sub-project 226 and record 235 is a part of sub-project 234. If the project such as 242 does not include a sub-project, the record maybe part
of the project. For example, record 245 would be considered to be a part of project 242.
FIG. 3 is a flow diagram illustrating one embodiment of a method providing a user with access to the PIS 10. At step 301, a user may input information indicating the user's status or access level. At step 302, PIS 10 may check the access level
of the user based on the users input 301. If the user's input indicates that the user does not authorize to that level of access, the PIS 10 may return a message indicating that the user does not have access or show the user a generic screen that does
not allow the user to access any restricted or confidential information regarding a program 220, 240 or project 222, 232, 242.
If the user input 301 indicates that the user has a reader level access, the PIS 10 will allow the user to access the reader level functionality, displays and records. Reader level functionality may include the ability to perform searches, save
searches, access policies and procedures documents, access section-specific PIS 10 help and open online displays.
The policies and procedures and documents for each program may be stored at the program level. The document may be accessed from any area of the PIS 10 hierarchy, however.
The reader-accessed 304 functionality may include the ability to open a record in read mode, open attachments, identify attachments with an icon such as one indicating a spreadsheet or text file, and export records to outside applications. For
example, a user having a reader level access may export a document to a Microsoft Excel.TM. document or other spreadsheet document.
The user having the reader level access may display only those projects to which the user has excess. For example, at step 302, the PIS 10 may also check to see to which projects the user has access. Thus, the user will only have reader
functionality for the projects to which the user has been given access. In one embodiment, the user having a reader level access status may also have the ability to select and save limited number of projects the user wants to display.
In viewing records, the user having a reader-level access status may access records, see previous record, see next records, print records and mail records. In one embodiment, a uniform resource locator ("URL") link to a PIS 10 record may be
included with an email. The user having record level access status may send a record copy with attachments as well as the URL link so that the user may access the original document in PIS 10.
The user may also have access to record-specific PIS 10 help. The user may also be able to expand sections and collapse section. In one embodiment, each record may have an edit history at the bottom of each record. The edit history may be
entitled "edit history" or "edit trail" or any other appropriate heading. The edit history or trail section may include a column called "type". The type column will reflect the type of change being made in the document. List of type of change may
include name change, deleted records, archive records, moved records and modified records. Name changes may include name changes to the program, the project, or a sub-project name and the affected related records 225, 227, 235, 245.
If the user access level is an editor access, PIS 10 may provide the user with editor access at step 305. Editor access may include all of the functionality of reader access, and form a superset thereof. With regard to on line displays, editor
access may include creating a record based on a program, project, or sub-project. The editor may create a record in any section in the PIS 10 except the archive section or project information section or project information section. The editor may also
open a record in edit mode (except in the archive section), move record(s) to the archive section, and remove record(s) from a section to mark the record(s) for deletion (except in the archive section). With regard to records, the editor may modify
previously record(s). The editor may not be able to edit records in the archive section or modify project name or participating line of business/sub-unit fields in the project information records described below. The editor may not be able to edit
fields in the tracking information section. The editor may also save modified records.
If the user has a coordinator-level access, at step 306, the PIS 10 will present the user with coordinator level access. The coordinator will have the same functionality as reader and editor. The coordinator may also be allowed to edit fields
in the tracking information section, as described below, and create program, project, and sub-project records.
If the user-access level is an administrator access level, at step 307 PIS 10 will present the user with administrator level access at step 307. Administrator-level access may include all of the functionality of reader level access 304,
editor-level access 305 and coordinator-level access 306. Additional administrator-level access privileges will be described below.
FIG. 4 is a block diagram illustrating one embodiment of the project information system of FIG. 1. Project information system 410 may include a plurality of components 411-428 for managing a project. Project information system 410 may include a
home page 411 and a project information section 412. The PIS 410 may also include a milestone module 413, and issues module 414, a change control module 415, a documents module 416, a project status report module 417, team member status report module
418, contact module 419, management decisions module 420, meetings module 421, and action items module 422. The PIS 410 may also include financials module 423, a "what's new" module 424, search module 425, archive module 426, PIS coordinator module 427
and central PIS administrator module. The modules will be described in more detail below with reference to FIGS. 6-21. Each module may include the ability to generate online displays and records related to the module, among other functions.
FIG. 5 is a block diagram illustrating a section module of the PIS of FIG. 1. FIG. 5 illustrates a PIS 510 including project information database system 532 and a project information management tool 534. Information regarding a project may be
input through input block 530 into project information database system 532. Input of information at block 530 may include information input by a sub unit of an entity, such as a line of business or other sub units of a corporation. The input may also
be from any other authorized user of the PIS 510.
Project information data base system 532 may store and/or organize the information input at input block 530. The information in project information data base 532 may be organized according to component, such as components 411-428 of FIG. 4.
Each of the components of 411-428 may be a part of project information management tool 534.
A component 536 is shown to be a part of project information management tool 534. Component 536 is representative of a component 411-428 of the PIS 410, 510. Component 536 includes an online display component 541 and a record component 542.
Online display component 541 may be used to easily find documents and display quick online reports. The online display component 541 may also be used to print formatted reports quickly. Records component 542 may include documents created to capture
different kind of information.
The user accessing a component 536 may be presented with online displays 541 and access to other online displays 541 as well as access to records 542. When a user accesses an online display, project information management tool 534 will retrieve
the information from project information database system 532. In one embodiment, the online displays 541 and records 542 may be pre-formatted and stored in project information database system 532. In another embodiment, the online displays 541 and
record 542 may be dynamically generated based on input from a user at a user system 2, 3. Thus, online displays 541 and records 542 may be customized based on user requirements or desires.
FIG. 6 is a screen shot of a sample home page display generated by the home page module 411 of FIG. 4. As shown in FIG. 6, the home page module may display a home page 600 including a header 601, links-board 602 and navigator 603. Links-board
602 may include links to the intra-net home page of the network 5, a phone book link, an exit link and a PIS coordinator link. The PIS coordinator link may allow users with a coordinator level access status or above to access functionality available
only to coordinators and central administrators.
Navigator 603 may include links to the project information system home page, a link to create a new program, a link to create/view/update project by a project, a link to create/view/update project records by a section, a link to the archive
module 426, a link to a search records module 425, a link to a reporting section, a link to help section, a link to a site map, and a link to the what's new module 424. The body of the home page 604 may display whatever is selected from the navigator
603. The items of navigator 603 may be used to bring up additional menus or drop down boxes to further define the users request. The navigator 603 may remain on screen regardless of where the user is in the project information system 410.
The functionality available in the home page module 411 may be defined in terms of access status. Users with a reader access status may access an intranet phone book, the delivery process guide, a service request management application, a change
management application, a project information system help section, the what's new module 422, search module 425, archive module 426 and any of the report modules. In one embodiment, the reader may also be given access to financials module 423.
The reader functionality may also include access to project documents. A reader may access project documents by selecting a link. For example, as shown in FIG. 6, a reader may access project documents by selecting either "create/view/update
project record by project" or by selecting "create/view/update project records by section". The project records by project selection will allow the user to choose one or multiple program(s), project(s), or sub-project(s) and display all project records
under their appropriate hierarchy. The selection of project records by section will allow the user to choose one or multiple section(s) 411-423 for one or more project(s) 222, 232, 242 to display records by section.
A user with PIS coordinator access status may access PIS coordinator functions available through the PIS coordinator link of links board 602. A user with central administrator status may access the PIS coordinator functions linked to see central
administrator functions as well as PIS coordinator functions. All functionality that is exclusive to central administrators may be hidden from PIS coordinators when the PIS coordinator link is selected by a user with a PIS coordinator status. The
central administrator may be able to modify the body of the home page including modifying the welcome message, who to call for support, who to call for access and the editor's guide. In one embodiment, the editor's guide may be an attachment to or
embedded (OLE or otherwise) document in the home page.
FIG. 7 is a screen shot illustrating one embodiment of a project information record generated by a project information module 412. Project information record 700 may include a general project information section 702, a tracking information
section 704, and a line of business or subunit specific section 706. Although only one line of business/business subunit section 706 is illustrated, there may be a plurality of line of business subunit sections 706, depending on the number of the line
of business of sub units involved in a project.
A user having a coordinator status may have the functionality to create programs, create projects associated with the programs, create sub projects associated with a project and realign project hierarchy. Realigning project hierarchy may include
moving all documents as one unit. Creating a program may include assigning editors as well as other PIS 10 coordinators at the program level. The coordinator may also be able to move project information records to the archive section 426 after all
related project records are archived. The coordinator may further archive selected project(s) with all related project records at any level or delete selected project(s) with all related project records at a new level.
The coordinator may further create initiative information records. The central administrator may maintain a list of initiatives and assign access to create the initiative information record, described in more detail below with reference to FIG.
8.
With reference to records 542 of the project information module 412, an editor may have the additional functionality of posting and editing delivery process dates and risks in grids that are displayed in the project information record. The
editor may select a phase name in a delivery process grid to bring up fields for the editor to complete. The fields the brought up may include dates and risks. In one embodiment, once the date is saved, the data may be displayed in delivery process and
risk grids in the project information record. Phase date and risk may be similarly edited. The editor may also hide or show individual phases within the delivery process and risks grid.
A user having coordinator status may complete all fields required to be completed for the creation of a program, project or sub-project. The fields to be completed may include required fields of the general information section 702 and optional
fields of line of business/sub unit section 706. In the general information section, the coordinator may complete the fields of program name, project name or sub project name, executive sponsor, program manager, overall project manager, participating
line of businesses or sub unit(s) and project objective/description.
The fields of the LOB/SU section 706 may vary with the LOB/SU. For example if one of the LOBs is retail information technology ("IT"), the fields the coordinator may fill out may include initiative, objective and business unit. For a retail
line of business, the field that a coordinator may include is "business unit". In one embodiment, if the entity performing the project is a financial surfaces entity or another entity having corporate administrative services as a supporting unit, the
project information record 700 may include, for example, a corporate administrative services (a LOB) information section 708. The coordinator may have the functionality to complete the fields in the CAS information section 708. These fields may include
project name, project manager, business unit, project objective/description, start date and cost center.
In one embodiment, the product information record may include, for example, a national enterprise operations ("NEO") information section as a supporting unit section 706. The coordinator may have the functionality to complete the fields of
project status, schedule start date and schedule end date in the NEO information section. Coordinator may have the functionality to select sections to be displayed in each program project, or sub project that are available within PIS 10. The
coordinator may choose to show or hide the selectable sections. The coordinator may further modify all editable fields and rename programs, projects or sub projects.
The coordinator may determine access for a program or project. This access will establish default access created for all documents created under the program or project. If a coordinator removes access at the program or project levels, access
for all records created for the program or project, respectively, will also be removed.
The coordinator may add a section in the general project information section 702. The added section may include the fields of initiative, program, project, sub project and participating (LOB/SU). The initiative may be chosen by the coordinator
at the program level. The field may be editable at the program level and viewable at all other levels. The initiative field may be left blank as a default selection. The initiative field may be created so that users may generate initiative level
status reports as well as other initiative level reports.
The coordinator may type in the name of the program at the program level, the name of the project at the project level and the name of the sub project at the sub project level. The program name may be editable at the program level and viewable
at all other levels. The project name may be editable at the project level and viewable at the program and sub project level. The administrator may establish a master list of participating LOB(s)/SU(s) and enter this list into the participating LOB/SU
field.
The values may inherit from the program level to the project and from the project to sub project levels. The coordinator may adjust the values in each level below program according to what is needed. The coordinator may have the authority to
remove but not add values in each level where the coordinator adjusts the values of the participating LOB/SU field. LOBs may be added only at the program level.
The coordinator may also add an ebusiness ("Ebiz") field for an Enterprise Project Delivery (EPD) report. The Ebiz field may be hard coded and optional.
Each time a project information record is created and saved, a financials record may be automatically created for that project.
The coordinator may also complete an initiative record as shown in FIG. 8. FIG. 8 is a screen shot illustrating one embodiment of an initiative record. The coordinator may complete the general information field 802 of the initiative information
record 800. The required fields of the general information section 802 may include initiative name and LOB/SU owner. The initiative name may be selected from a drop down list. The coordinator may also select a single value from a drop down list for
the LOB/SU owner.
The coordinator may complete text fields in the general information section 802 which may include description, benefit and strategy. The description field may describe the initiative. The benefit field may describe the benefit of completing the
initiative. The strategy field may describe the high-level of strategy for completing the initiative.
A user having a central administrator status may maintain values for initiative indicator key words fields and create additional LOB specific sections as needed. A central administrator may add new sections. The new sections may include the
fields of project manager, business unit, size or status.
FIG. 9 is a block diagram illustrating the organization of the project information record of FIG. 7. The project information record 900 may include a plurality of sub records including a general information sub record at 901 and other sub
records 902-918 representing a line of business or supporting unit.
The project information record of FIG. 9 illustrates an example of a project information record which may be used by a financial services entity. The financial services entities project information record 900 includes a general information
record 901, retail IT 903, national enterprise operations 904, CAS information 906, central IT 907, commercial information 908, corporate investment 909, corporate program office 910, corporate real estate 911, investment management group 913, retail
line of business 914, retail IT 915, risk information 917, delivery process 919 and delivery process risk 920. The project information record also includes line of business sub records 905, 912, and 918. The general information section 901 of the
project information record may include an executive sponsor field and program manager field established at the program level. Each LOB section may also include a business unit field tied to an associated LOB/SU so that a business unit may be selected if
the associated LOB/SU has been selected. Removing a LOB/SU may also remove all associated business units. Business units of the project and sub project levels may be removed but not added.
A project may inherit fields from the program level and a sub project may inherit fields from the project level. All inherited fields may be editable. In one embodiment, the project and sub project may inherit the fields of executive sponsor,
program manager, over all project manager, technical officer, business owner, finance owner, technology owner, participating LOB/SU start date, revised start date, end date, revised end date, project objective/description and benefit. Modification of
the inherited fields however may not cause re-inheritance except for the participating LOB/SU field. When a coordinator creates a project record, the LOB/SU information may cascade from the program record to the newly created project record and from the
project record to the sub project record. If a coordinator edits a program record to add or delete a LOB/SU, the pick list of LOB/SU values will update for the lower levels but will not automatically change the LOB/SU field in the project or sub project
record. The coordinator may edit the project or sub project record to change the field.
The key word fields in the general information section may include any chosen field such as, for example, participating LOB/SU, initiative, executive sponsor, program manager, overall program manager, technical officer, business owner, finance
owner, technology owner, overall status and e-business. The key word field may also include "on time?" and "uses DP framework?".
Some or all of the key word fields may include hard-coded radio buttons. In one embodiment, the key word fields may include hard-coded radio buttons having the values yes or no. Other key word fields may include drop-down lists. In one
embodiment, some or all of the drop-down list may be maintained by central administrator. The e-business field may also include hard coded radio buttons including yes or no values to indicate whether the project is an electronic business project. In
one embodiment if no is selected in the "on time?" field, a required text field labeled "if no, then comment" may be displayed for the user to complete.
The fields in the other sub records 903-920 may be inherited or selected as described with reference to the general information subrecord 901. The central administrator or other authorized user may determine which fields are inherited and which
fields are selectable. In one embodiment, some of the fields may be designed to be editable even if inherited. Each record 700, 800 of the project information system 10 may include a record access and edit history 820. The record access and edit
history section may include a field for name of user, date/time and type of change made in the document.
FIG. 10 is a screen shot illustrating one embodiment of a milestones record 1000 generated by the milestones module 413. Milestones module 413 may be used to track milestones. Milestone record 1000 may include sub records such as, for example,
reporting information 1002, dates 1004, tracking information 1006 and status information 1008.
The online displays may provide the reader with the functionality of displaying default columns. The default columns may include milestone name or sort, risk, status, percent complete, start date, end date and owner. The start date and end date
may pull either the original or revised date. For an editor, the functionality may include creating a milestone based on a program, project or sub project. The editor may also complete required fields of the record 1000. The required fields may
include milestone name, status and risk.
In the dates sub records 1004, the original date and end date may not be editable after the first entry and save. In one embodiment, the original end date may be a required field. In the reporting information 1002, the phase field may include a
drop-down box of all phases in which the user may choose the appropriate phase. The percent complete fields under status information 1008 may automatically update to 100% once the status is marked complete. The key word fields of the milestones record
413 may include the fields of phase, status, risk, milestone type, owner and team owner. The key word fields may include drop down lists or hard coded radio buttons. The drop down list may be maintained by central administrator.
FIG. 11 is a screen shot illustrating one embodiment of an issue record generated by issue module 414. Issue record 1100 may include reporting information sub record 1102, issue description sub record 1104, status and severity sub record 1106,
impacts sub record 1108 and resolution sub record 1110. The reader functionality in online displays of the issue modules 414 may include viewing a default display including issue number, issue title, status, severity, risk, target date and who the issue
is assigned to. Editor functionality for online displays may include creating issues based on a program, project or sub project, creating a risk matrix and problem solving matrix, generating a issue log and modifying predetermined editor modifiable
fields for an issue. The predetermined editor modifiable fields may include status, severity, risk, problem solving step.
The editor functionality may further include completing required fields of the issue record. The required fields may include, issue number, issue date, issue description, issue title, status, severity and risk. The key word fields in the issue
record may include issue category, phase, raised by, status, severity, risk, problem solving step, project teams impacted, impacts, assigned to and assigned team. These fields may be populated by a selection of a value from a drop down list or hard
coded radio buttons. A drop down lists may be maintained by the coordinator for each program hierarchy or central administrator.
The issue number may pre-populate with a sequential number within a program, project or sub project. The issue number field may begin with 1 and increase in increments of one within each program, project or sub project. The issue date may
pre-populate with the current date. The issue date may also be editable. If status is marked closed, the actual date may appear as a required field. The actual date may pre-populate with current date, but may be editable.
The resolution field may have the ability to capture name and date of each author each time a new entry is made in the resolution field for each issue. The resolution field may be required when the status is marked closed. An issues update
field 1112 may be used to record the name and date of each author each time a new comment is made on an issue. An impacts field in the impacts section 1108 may include a list of categories that may be check as being impacted. The list of categories may
include issue, scope, schedule, resources, financial and other.
The issue record 1100 may have the ability to reference the phase of the project which is impacted by the issue, as shown in issue description field 1104. An automatic e-mail may be sent to the person assigned to the issue after the first save
of an issue or after the "assigned to" field has been changed.
FIG. 12 is a screen shot illustrating one embodiment of a change control record generated by change control module 415. The change control record 1200 may include a reporting information section 1202, an identification section 1204, impact
section 1206, and action taken action 1208.
The reader functionality for online displays for the change controls module 415 may include viewing a default display. The default display may include change control number, change control name, action taken and priority. The editor
functionality for the online displays may include creating change control based on program, project, or sub-project, open change control record and edit mode.
The editor functionality for records may include completing required fields for the change control record. The required fields may include change control number, submitted by, change control name, date submitted. The change control number may
pre-populate with a sequential number within a program, project, or sub-project. The number may begin with 1 and increase in increments of one within each program, project or sub-project. The change control number may not be editable.
The key word fields in the change control records may include submitted by, project manager, related request, priority, impact assessment conducted by, action taken. The key word fields may include drop down name lists or hard coded radio
buttons. If a key word field is populated by drop down name list, multiple values may be allowed for that field. The drop down list may be administered by coordinator, editor or central administrator as determined by the central administrator or other
authorized user.
The submitted name field may pre-populate with the name of the person creating the change control. The dates submitted field may be pre-populated with the current date. The action taken sub record may have additional fields that appear that are
appropriate to the selection made. For example, if the in progress field of the action taken sub record is selected, "name of creator" and "in progress as of" fields may appear. If the accept field is selected, "name of approver" and "date accepted"
fields will appear. If the defer field is selected, the "name of approver" and "reason deferred" fields will appear. If the reject field is selected, the "name of approver" and "reject reason" fields will appear. If the implemented field is selected,
an "implementation date" field will appear.
FIG. 13 is a screen shot illustrating one embodiment of a document record 1300 generated by documents module 416. The document record may include a reporting information section 1302 and a document information section 1304. The reader
functionality for the online display module 416 may include viewing a default display. The default display may include type, category, title and status of the document. The reader functionality may also include viewing a display capturing all records
from the documents section as well as attachments stored in the PIS 10. The editor functionality for the online display may include creating a document based on a program, project, or a sub-project.
The editors record functionality may include completing the required fields of the document record 1300. The required field may include category and title.
The key word fields for the document record may include type, type [category], phase, created by, team, assigned to, status and purpose. The type field may be a drop down list maintained by central administrator. The type [category] field may
include a drop down list maintain by a coordinator for each program hierarchy. Other fields may include drop down lists maintain either by central administrator or the coordinator form each program hierarchy. In some fields, multiple values may be
allowed. Some fields may include hard coded radio buttons.
The created by fields under document information sub-record 1304 may be pre-populated with the name of the person creating the record. The created by field may also be editable. A "created on" field may pre-populate with the current date yet
also be editable. The user may populate the phase field based on a drop down box listing all phases. The current status list in the document sub-record 1304 may default to "in progress". The "assigned to" field may list the person to whom the document
is assigned to be completed. The "assigned to" field may access names listed in the contacts module 419.
The purpose field may allow users to record the reason for the document. Each program may have the ability to determine its own lists of purposes. A code field added in the document information 1304 may allow the user to determine what kind of
record the document is. For example, the document may be a deliverable, a template, other, etc. The comments fields may allow the user to add additional comments.
FIG. 14 is a screen shot of one embodiment of a project status report record generated by the project status report module 417. The project status report 1400 contains three illustrative sub-records. In practice, the project status report may
include a plurality of sub-records 1404 similar to the sub-records 1402, 1404 shown.
The project status report 1400 includes a general sub-record 1402, a line of business information sub-record 1404 and a status summary record 1406. The reader functionality for online displays may include linking into a central location to
cross-program status report display by line of business. The reader may also link to pre-define reports by the line of business, export online displays to Microsoft Excel.TM. or other spreadsheet application, access print preview mode prior to
printing, print online displays and view a default display. The default display may include a report date, status, overall risk, LOB/SU and business unit. The default display fields of LOB/SU and business units may include only those LOB/SU and
business units identified in the report.
The editor functionality for online display may include creating status reports based on initiative indicator, creating status reports based on a program, project or sub-project, creating a line of business status report and creating a business
unit status report. The line of business status report may report on consolidated effort of all or a selection of line of businesses involved. In another embodiment, line of business status report would report on the consolidated effort of all or a
selection of business units involved. The business unit status report may report on business unit component only. Any level in the PIS 10 hierarchy should be able to create a consolidated LOB, independent LOB or business unit status unit.
Based on the LOB creating the status report, each LOB including the LOB business units, may have their own status report template that would be called up when they create a status report. One template may be available per LOB per level within
the PIS 10 hierarchy. When a consolidated status report is generated, the report creator may have the ability to edit the title of the report. When a consolidated status report is generated, each line of business and/or business unit involved should be
identified.
The editor may have the ability to copy, to paste, and to update existing status report(s) including initiative status reports. The editor may also have the functionality to generate a new status report(s) or provide a button to import all
fields from previous status reports. The new status report(s) would start a new record history. The editor may also have the functionality to open the status report record in edit mode, move records to the archive module 426 and remove records from the
project status report section to mark them for deletion.
In the records section of the project status report section 417, a user with reader status may have the functionality to access print preview mode prior to printing, print a record, mail a record to any type of mail package and export a record to
a word processing application. The mail packages to which the record may be mailed may include an Internet mail package, such as, for example, Notes.TM. mail, Outlook.TM., etc. The word processing program may include Microsoft ("MS") Word.TM. or any
other appropriate word processing program. The report header for each sub record may include the fields of line of business, project name, initiative, program, project or subproject status report, "consolidated for", for period ending, and status. The
"consolidated for" field may be followed by the business unit.
Each of the general project information field and the line of business/supporting unit field may include a header listing the section name, the audience type, the type of status report, and the functionality of the report. The functionality may
include boxes indicating view project information and import project information. In the body of the subrecord, fields may be imported from the project information record for the program, project or subproject. For the general project information
record 1402, the non-editable imported fields may include executive sponsor, program manager, overall project manager, start date, end date, participating LOBs and service request number. The start dates and end date may be pulled from revised date
first. If the revised date is not available, then the original date may be used. The general project information subrecord may also import the editable field of project description. Subrecord 1402 is an illustration of general project information
section for an audience of line of business 1. The non-editable fields and editable fields imported may vary with the audience and the desires of the user creating the report.
Subrecord 1406 is an illustration of a status summary report. The status summary subrecord 1406 is a manual table including category, risks, trend, and comments. Common status summary categories across all LOBs include overall assessment,
issues, scope, schedules, resources, and financial. Other LOB defined categories may be defined. The central administrator may modify the defined categories for each LOB at each level. When performing cross LOB reports, only common categories listed
above may be globally reported. The status summary risk may be manually entered at all levels. The PIS 10 may not combine status/risk data automatically. In one embodiment, the risk fields may be color coded according to risk level. For example, the
risk fields may be color coded such that green status indicates no significant issues exist, yellow signifies that issues have arisen that are considered manageable, and red may indicate the significant issues have risen that put the project in jeopardy.
FIG. 15 is a screen shot illustrating one embodiment of a delivery process status section generated by the project status reports module 417. The delivery process report 1500 includes a delivery process status report 1502 and a delivery process
risk status report 1504. The delivery process status report 1502 may include the functionality to hide the section, show section, view phase information and import phase dates. The delivery process phase dates may be imported as documented in the phase
records.
Delivery process risk record 1504 may include the functionalities of hide section, show section, view phase information, and import phase dates. The delivery process risk record 1504 may import delivery process phase risk records. The table may
contain columns listing overall risks, check point date, overall comments, additional risks, check point dates and comments for each LOB identified on the status report.
The delivery process status report 1502 may include the columns of original start date, revised start date, actual start date, original end date, revised end date and actual end date. The project status report module 417 may similarly generate
tables for reports based on the other PIS 10 component modules such as project information module 412, milestone module 413, issues module 414, change control module 415, financials module 423, etc. Tables may be generated for other factors such as
problem solving and other customizable sections. Initiative status reports may also be generated for viewing initiative information and importing initiative information.
FIG. 16 is a screen shot illustrating one embodiment of a team member status report. Team member status report 1600 may include a reporting information section 1602. The team member status report 1600 may be generated by team member status
reports module 418. The online displays functionality for a user having reader status may include viewing a default display, exporting online display to a Microsoft Excel.TM. document, accessing print preview prior to printing and printing online
displays. The default display may include document author, date, status and recipients ("to" field).
The editor functionality for online displays may include creating a team status report based on a program, a project or a sub-project. The editor functionality may further include copying, pasting and editing an existing team status report to
generate a new team status report or provide a button to import all fields from a previous report. The new team status report would start a new record history.
In the records section of the team member status reports module 418, the reader may have the functionalities of printing the record, mailing a record to any type of mail package, accessing print preview prior to printing and exporting the record
to MS Word.TM. or other word processing program. The editor functionality for the records section may include creating comments.
The key word fields in the team member status report may include the fields "to", team and status. The "to" and the team fields may include drop down lists allowing multiple values. The team drop down list may be maintained by the coordinator
for each program hierarchy. The status field may include hard coded radio buttons. The "from" field of the reporting information section 1602 may not be editable and may be prepopulated with the name of the person creating the status report. The date
field may be prepopulated with a current date and may also be editable. The subject field may be prepopulated with the current month and year followed by status report, but may also be editable. Attachments may be entered or linked from a library.
The project type and project name associated with the team member status report may be prepopulated in the team member status report. A "for period ending" field may be added that prepopulates with the current date and is also editable. The
status field may be prepopulated with the "completed" circle selected. A coordinator may add text fields but the content in the text fields may not be automatically pushed or pulled to other levels in the hierarchy.
FIG. 17 is a screen shot illustrating a contact record generated by contact module 419. The contact record 1700 may include reporting information section 1702, a name of contact section 1704, a general information section 1706 and other contact
information section 1708.
The reader functionality for the online displays in the contact module 419 may include viewing a default display. The default display may include name, team, phone, mail code, pager, personal identification number ("PIN") and fax. The editor
functionality for the online displays may include creating contacts based on a program, project or subproject.
The editor functionality for the record section may include completing required fields such as name and employee type. The key word fields may include employee type, manager, alternate name, administrative assistant name, LOB represented,
project(s), team, subteam and team role. The key word fields may include drop down lists, some of which may allow multiple values. The drop down lists may be maintained by a central administrator or coordinator, depending on design. The employee type
fields may include hard coded radio buttons. In one embodiment, if a user populates a name field using the name of a employee of the entity and the address of an entity, the office phone field may also populate automatically. The contact records may
come from the entities address book. The fax number may also populate if available on the user's record.
FIG. 18 is a screen shot illustrating one embodiment of a management decision record. Management decision record 1800 may include a reporting information section 1802, a decision information section 1804, and an impact information section 1806.
Management decision record 1800 may be generated by management decision module 420.
Reader functionality for the management decision module 420 may include viewing a default display including title and date. The editor functionality for the online display may include creating management decisions based on a program, project or
subproject.
The records functionality for the editor may include completing required fields such as decision title, decision description, decision date and person responsible in decision information section 1804. The key word fields of the management
decision record 1800 may include person responsible, type, impacted project and impacted team. The key word fields may include drop down lists maintained by the coordinator, administrator or other authorized user, depending on design. Some key word
fields may allow multiple values.
FIG. 19 is a screen shot illustrating one embodiment of a meeting record. Meeting record 1900 may be generated by meetings module 421. Meeting record 1900 may include a reporting information section 1902, meeting information section 1904 and
meeting results section 1906. In particular, meeting results section 1906 may present information related to phase, participants, attachments, minutes and next steps.
Reader functionality for online displays for the meeting module 421 may include viewing a default display. The default display may include date, purpose, location, start time, end time, time zone, conference number and access code. The editor
functionality for the record section of the meetings module 421 may include creating a meeting based on a program, project or subproject. The editor functionality may further include completing required fields in the meeting record. The required fields
may include purpose, date, start time, end time, contact name and contact phone.
The key word fields for the meeting record may include purpose, time zone, project, team, primary location, other locations, contact name, phase and participants. The key word fields may include drop down lists maintained by coordinator,
administrator or other authorized user. Some of the key word fields may allow multiple values. Some key word fields may include radio buttons.
In the meeting information section 1904, the start time and end time and other preselected fields may be designed to be prepopulated. For example, the start time may be prepopulated with an 8 a.m. time, the end time may prepopulate with a 9
a.m. time and the time zone field may be prepopulated with the current time zone for the user creating the record. Depending on the design, the start time and end time may be editable but the time zone may not be editable. In another embodiment, time
zone may default to an eastern time zone but may be editable with a drop down list of available time zones. A contact phone field of the meeting information section 1904 may capture the phone number of the contact name from the contact record.
FIG. 20 is a screen shot illustrating one embodiment of an action item record generated by action items module 422. The action item record 2000 may include reporting information section 2002, source of action item subrecord 2004 and action item
information subrecord 2006.
The online display functionality for a reader may include viewing a default display. The default display may include due date, source, action item number, description, assigned to, status and priority. The editor functionality for online
displays may include creating action items based on a program, project, subproject in a module 412-423. The available modules for creation of action items may include project information module 412, milestones module 413, issues module 414, change
controls module 415, documents module 416, project status reports module 417, team member status reports module 418, management decisions module 420, meetings module 421 and financials module 423.
The editor functionality in the records section of the action items module 422 may include completing required fields in the action item record such as "assign to" and "action record description".
The key word fields in the action item record may include "assign to", team, priority and status. The assign to and team fields may be drop down lists. The team field drop down list may be maintained by a coordinator for each program hierarchy. The priority and status key word fields may include hard coded radio buttons.
The date logged field may be prepopulated with the current date and may be editable. The priority field values may include "high", "medium" and "low". The default priority value may be set to "low". The status options for the status field may
include open, closed or hold. The action item number field may be prepopulated with a sequential number within a program, project or subproject. The number may begin with 1 and increase in increments of 1 within each program, project or subproject.
This feature of the present invention assists users understand new enhancements or production fixes that have occurred recently. The action item number may not be editable. The reporting information section 2002 in action item record 2000 may be used
to track the associated program, project and subproject information along with the associated LOB and business unit information which is imported from the project information record module 412.
The section field may prepopulate based on the section where the action item is created. The phase field may pull in the phase that is listed on the source document.
FIG. 21 is a screen shot illustrating one embodiment of a financial record generated by financials module 423. Financials record 2100 may include a reporting information section 2102, an overall subrecord 2104, a tracking information subrecord
2106 and at least one line of business or supporting unit subrecord 2108.
Financial record 2100 may be generated by financials module 423. The reader functionality for the online displays for the financials module 423 may include viewing a default display. The default display may include LOB/SU, business units and at
budget (overall).
The coordinator functionality for the record section of the financials module 423 may include generating a finance record each time the coordinator creates and saves a project information record in project information module 412. The LOB and
support units selected on the project information record may determine the sections available on the finance record 2100. The following functionality rules for creating a financial record 2100 apply. If only one LOB or SU is chosen on the project
information record 700, the financial record may display a reporting information, tracking information and selected LOB or SU. If two or more LOBs or SUs are chosen, then the finance record may display reporting information, overall information 2104,
tracking information 2106 and selected LOB or SU 2108. The finance record may inherit LOB and SU selection changes from project information record 700.
In one embodiment, all LOB sections may include two parts, LOB and IT. The coordinator may have the ability to hide or show sections. If all sections are hidden, a tag line may appear indicating that all sections have been suppressed. The
overall section 2104 should appear for every LOB and SU section. The overall section may include at budget and budget. The "at budget" field may be an indicator field requiring a yes or no answer. If no is chosen, the user may be required to fill out
a field "if no, then comment."
The budget field may be a numeric field populated with the dollar amount (or other currency amount) of budget for the project. Other fields of overall section 2104 may include planned head count number, planned contractor head count, actual head
count, actual contractor head count, planning estimate, planning launch date, commitment estimate, commitment launch date, current estimate and current launch date. Tracking information section 2106 may include major project code, subproject code,
billing LOB, billing business unit, primary service request, other service requests, cost center number, cost center name, Contact Resource Request (CRR) number, Capital Expenditure Request Package (CERP) and change management number, and other
information.
For each LOB or supporting unit financial record or sub record 2108, the fields available or selected may vary with the LOB/supporting unit or type of LOB/supporting unit.
The what's new module 424 may identify what is new in PIS 410. The online display reader functionality for the "what's new" module 424 may include, opening a record in read mode and identifying attachments with a paper clip icon. The editor
functionality for the online display of the what's new module 424 may include opening a record in edit mode and removing records from the section to mark for deletion.
The reader functionality in the records mode of the what's new module 424 includes access to a URL linked to a PIS 10 record with an email. Editor functionality in the record mode of what's new module 424 may include modifying previously created
records, determining record access and saving modified records.
The search module 425 enables searches in PIS 10. A user having reader status would have the same functionality in the search module 425 as the reader status functionality described with reference to FIG. 3.
The search module 425 may allow a user having editor status to delete selected searches. The editor may also complete required fields including Excel.TM. export type and record type. The editor complete optional fields such as, for example,
participating LOB/SU. The participating LOB/SU field may be designated to be a required field for project search selection. Search module 425 may allow searches of other modules 412-423. Choice of record type in the search module 425 may provide users
with customized search criteria depending on the module being searched. The advanced searched criteria may be edited and customized by an administrator, coordinator or other authorized user.
In one embodiment, two field name and search value areas may be displayed, depending upon which record type is selected. These fields may be able to search fields that are used globally as well as fields specific to a line of business. A search
summary section may be displayed with information such as date search, last run, records found and lapse time. The search results may be exported to a predefined Excel.TM. template for searches of change control module 415, issues module 414,
milestones module 413, project information module 412, and action items module 422. Search results may be exported to user defined Excel.TM. spreadsheets for all search types.
The archive module 426 may be used to store archived records. The coordinator may have the functionality to restore records from archives in the online display section of the archive module 426.
The coordinator module 427 provides additional functionality for the coordinator. The coordinator has the functionality to edit the policies and procedures module.
For online displays, the coordinator may create local [project hierarchy] keyword record, modify a local [project hierarchy] keyword record, delete records marked for deletion, return marked records for deletion to PIS 10 and send entire
projects, including all associated records, to the archive 426.
In the record section, the coordinator may complete required fields in keyword records such as keyword name. The keyword records include the information in the "drop-down" lists in all of the modules. A keyword record contains two parts: (1)
the category (field name from a module); and (2) the value (what the user sees in a list). Coordinators or administrators maintain these keyword lists by maintaining keyword records The coordinator may also modify previously created records.
For security access, the coordinator may assign user access to a program. Once a user has been given the role of coordinator by the central administrator, the coordinator may create as many programs as needed. The coordinators may grant access
rights to users. The access rights that may be assigned include no access, reader access, and editor access. The coordinators may also assign other coordinators as coordinators for their program. A coordinator may not assign as an other coordinator
for a program someone who does not have a coordinator role assigned to him/her already. Thus, a coordinator may not bypass the system to establish editors or other users as coordinators.
The central administrator module 428 provides functionality to central administrators. Functionality available to central administrators includes access to global keyword database, updates of database profile, access to PIS specific help, and
assigning coordinator access at the PIS program level. The central administrator may also add or modify LOB groups. Central administrators may add LOBs at any time. Each time a new LOB is added, a LOB specific project information section is generated
and a default status report header is also generated. The central administrator may also maintain online help.
For online displays, the central administrator may create database [global and LOB] keyword records, modify database [global and LOB] keyword records, and delete database [global and LOB] keyword records.
The central administrator may modify previously created database keyword records, save modified database keyword records, and modify database profiles. Types of modification may include name change for a program, project or subproject, deleted
records, archived records, moved records, and modified records. The central administrator may also maintain and edit the homepage.
Line of business fields in the database profile record may determine default templates to use for project information record. The LOB fields in the database profile record may also determine default LOB names to populate in participating LOB
fields in the project information record 700 under the general information section.
Subproject section for project information record 700 will determine the sections that appear in the project information record 700 anytime a coordinator creates a new subproject. Project status report guidelines include storing and modifying
LOB status are use for LOB and business unit status reports. One LOB template may be used per level in the hierarchy. Application links may be available to other applications outside of PIS.
A program status report section may determine the sections that appear in the program Status Report. Title and descriptions may be added by the administrator or other authorized user for customized sections and status summary values allow status
summary tables to be defined for all program status reports for the PIS 10. A project status report section and a sub-project status report section may be provided to determine the sections that appear in the project status report and a sub-project
status report. The central administrators may define and show customizable fields at program level. The fields available may include table look-ups and text fields.
FIG. 22 is a flow diagram illustrating one embodiment of a method for managing a project using the PIS 10. The method includes storing project information at step 2201, generating a project related record at step 2202 and generating a project
component display at step 2203.
Storing the project information may include storing project information, for a first project, with associations to at least one project component so that all of the project information related to each project component is accessible by a user on
a network when the project component is retrieved. In one embodiment, the project information may be received from user 1, 2 system connected to the network 5.
The project information may include project information related to at least one sub-unit of the entity performing the project. For example, the entity may be a corporation and the sub-entity may be a line of business, a business unit or other
sub-entity. The project component may include at least one of the modules 411-428 of the PIS 10 shown in FIG. 4.
The step 2202 of generating the project related record may include generating at least one project component record based on the associations to the at least one project component 411-423. The project related record 542 may be used to track and
manage the project. The project related record may be any record generated by modules 411-423, such as, for example, project related record 542 described with reference to FIG. 5.
In one embodiment, the project related record 542 may be created automatically when a link representing the project related record is selected by a user 2, 3. In another embodiment, the project related record 542 may be created based on user
input. For example, the user may fill out fields of an on-line form and the values in the fields may be used to generate the project related record 542.
The step 2203 of generating the project component display may include generating a project component display customized to a project component 411-423. The project component display may include any display generated by modules 411-423 such as,
for example, the on-line display 541 described with reference to FIG. 5. The project component display 541 may be based on at least one project component record and generated when the project component 411-423 is accessed by a user. The project
component display 541 may include links to project component related documents and project component related reports.
The project component display 541 would be available to at least one user system 2, 3 over the network 5. In one embodiment, the project component display 541 may include a web page related to the project component 411-423.
In one embodiment, the project related record 542 and the project component display 541 may depend on the status of the user as described above with reference to FIG. 3.
In one embodiment, the method of FIG. 22 may further include generating a project related report as described with reference to FIGS. 7, 8 and 10-21 above. In one embodiment, each project related report may be automatically generated when a link
representing the project related report is selected by a user.
The invention is related in one regard to the use of a computer system for managing project related information, using computer, network and other resources. According to one embodiment of the invention, the project information management system
is provided via the computer system in response to the processor executing one or more sequences of one or more instructions contained in main memory.
Such instructions may be read into main memory from another computer-readable medium, such as the storage device. Execution of the sequences of instructions contained in main memory causes the processor to perform the process steps described
herein. One or more processors in a multi-processing arrangement may also be employed to execute the sequences of instructions contained in main memory. In alternative embodiments, hard wired circuitry may be used in place of or in combination with
software instructions to implement the invention. Thus, embodiments of the invention are not limited to specific combination of hardware circuitry and software.
The term "computer-readable medium" as used herein refers to any medium that participates in providing instructions to the processor for execution. Such a medium may take many forms, including but not limited to non-volatile media, volatile
media, and transmission media. Non-volatile media include dynamic memory, such as main memory. Transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise the bus. Transmission media can also take the
form of acoustic or light waves, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other
magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave, or any other medium from
which a computer can read.
While the foregoing description includes many details and specificities, it is to be understood that these have been included for purposes of explanation only, and are not to be interpreted as limitations of the present invention. The present
invention has been generally described in relation to a network-based project information system. Nonetheless, the characteristics and parameters pertaining to the system and method of the invention may be applicable to other types of project management
systems, as well as to other types of network-enabled platforms. Other modifications to the embodiments described above can be made without departing from the spirit and scope of the invention, as is intended to be encompassed by the following claims
and their legal equivalents.
* * * * *