US7020697B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Architectures for netcentric computing systems
Assignee: Accenture Global Services Ltd
•
Filing: 2000-11-03
•
Granted: 2006-03-28
•
Expires: 2020-11-03
Abstract
Abstract An execution architecture, a development architecture and an operations architecture for a netcentric computing system. The execution architecture contains common, run-time services required when an application executes in the netcentric computing system. The development architecture is the production environment for one or several systems development projects as well as for maintenance efforts. The purpose of the development environment is to support the tasks involved in the analysis, design, construction, and maintenance of business systems, as well as the associated management processes. It is important to note that the environment should adequately support all the development tasks, not just the code/compile/test/debug cycle. The operations architecture is a combination of tools and support services required to keep a production system up and running efficiently.
Inventors
- 👤 Marina Goodman
- 👤 Tor Mesoy
- 👤 Stanton J. Taylor
- 👤 Scott R. Reiter
- 👤 Michael T. Bowen
- 👤 Ralph Auriemma
- 👤 Tamara D. Alairys
- 👤 Christopher M. Degiorgio
- 👤 Lizbeth Johnson Coleman
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-31 07:42
CPC Classifications
G; G06; G06Q; G06Q10/00; G06Q10/06; G06Q10/10; G06F; G06F11/00; G06F11/30; G06F11/34; G06F11/3409
Claims Analysis
Total Claims: 21
Claim 1
Independent Claim
277 words
A netcentric computing system having an operations architecture stored on a computer readable medium, comprising: a operations integration architecture component executable to provide for the integration of other operations architecture components; a network/systems management component executable to survey a status of network devices for event faults and health information, to integrate into an overall management platform and to provide monitoring redundancy; a solution availability component executable to ensure availability of information technology systems through back-up or redundancy strategies by coordination of data across a plurality of network devices and by enablement of the netcentric computer system to recover from man-made and natural disasters that result in interruptions to service; a service management component executable to assist an information technology organization in providing quality information technology service and to support and to provide a central point of contact to route all reported incidents from users to support teams; a configuration management component executable to remotely administer changes to network components and to allow network management tools to remotely install or configure firmware or software on the network; a physical site management component executable to ensure that the physical environment is managed and protected against unplanned outages; an operations data architecture executable to support an overall service level agreement by defining how operations data is stored, accessed, used and distributed, and how an operations component interfaces to data generated by a different component; an operations execution architecture executable to provide the run-time services for execution of the operations architecture; and an operations development architecture, wherein the components provide specific functionality for the operations architecture, while the architectures represent the environments in which the components are developed, deployed, and operated.
Claim 2
Dependent Claim
277 words
A netcentric computing system having an operations architecture stored on a computer readable medium, comprising: a operations integration architecture component executable to provide for the integration of other operations architecture components; a network/systems management component executable to survey a status of network devices for event faults and health information, to integrate into an overall management platform and to provide monitoring redundancy; a solution availability component executable to ensure availability of information technology systems through back-up or redundancy strategies by coordination of data across a plurality of network devices and by enablement of the netcentric computer system to recover from man-made and natural disasters that result in interruptions to service; a service management component executable to assist an information technology organization in providing quality information technology service and to support and to provide a central point of contact to route all reported incidents from users to support teams; a configuration management component executable to remotely administer changes to network components and to allow network management tools to remotely install or configure firmware or software on the network; a physical site management component executable to ensure that the physical environment is managed and protected against unplanned outages; an operations data architecture executable to support an overall service level agreement by defining how operations data is stored, accessed, used and distributed, and how an operations component interfaces to data generated by a different component; an operations execution architecture executable to provide the run-time services for execution of the operations architecture; and an operations development architecture, wherein the components provide specific functionality for the operations architecture, while the architectures represent the environments in which the components are developed, deployed, and operated.
Claim 3
Dependent Claim
20 words
The operations architecture of claim 1 , wherein said operations integration architecture comprises an integration framework and a monitoring component.
Claim 4
Dependent Claim
22 words
The operations architecture of claim 2 , wherein said integration framework further comprises an applications program interface and an enterprise management console.
Claim 5
Dependent Claim
44 words
The operations architecture of claim 1 , wherein said network/systems management component is selected from the group consisting of a network management tool, a database management tool, an application management tool, a production scheduling tool, an output/input management tool and a security management tool.
Claim 6
Dependent Claim
29 words
The operations architecture of claim 4 , wherein said network management tool is selected from the group consisting of a network monitoring component and a network configuration management component.
Claim 7
Dependent Claim
28 words
The operations architecture of claim 4 , wherein database management component is selected from the group consisting of a database performance monitoring service and a backup preparation service.
Claim 8
Dependent Claim
30 words
The operations architecture of claim 4 , wherein said output/input management tool is selected from the group consisting of an output job and queue manager, and a physical device manager.
Claim 9
Dependent Claim
28 words
The operations architecture of claim 1 , wherein said solutions availability component is selected from the group consisting of a backup/storage/recovery management component and a failover management component.
Claim 10
Dependent Claim
20 words
The operations architecture of claim 8 , further comprising a monitor for viewing application performance in a client server application.
Claim 11
Dependent Claim
37 words
The operations architecture of claim 1 , wherein said service management component is selected from the group consisting of a service desk component, a capacity planning component, a user administration component and a service level management component.
Claim 12
Dependent Claim
32 words
The operations architecture of claim 10 , wherein said service desk component includes a workflow automation service, a service desk database, an incident querying capability service and a service desk reporting service.
Claim 13
Dependent Claim
26 words
The operations architecture of claim 10 , wherein said capacity planning, component includes a data collection agent, a scenario modeling agent and a data capture agent.
Claim 14
Dependent Claim
42 words
The operations architecture of claim 1 , wherein said configuration management components is selected from the group consisting of a software distribution/file transfer component, an asset management component, a change control component, a migration control component and a systems configuration management component.
Claim 15
Dependent Claim
20 words
The operations architecture of claim 13 , wherein said asset management component includes inventory management tools and license management tools.
Claim 16
Dependent Claim
29 words
The operations architecture of claim 13 , wherein said change control component includes a change control workflow automation application, a change control database and a change control reporting service.
Claim 17
Dependent Claim
36 words
The operations architecture of claim 1 , wherein said physical site management component includes a UPS/generator component, a raised floor, a fire suppression and climate control system, a plurality of wiring/cabling and a disaster recovery component.
Claim 18
Dependent Claim
25 words
The operations architecture of claim 1 , wherein the network configuration management component identifies, controls or monitors a plurality of managed objects in the network.
Claim 19
Dependent Claim
17 words
The operations architecture of claim 17 , wherein the managed objects are hardware objects or software objects.
Claim 20
Dependent Claim
40 words
The operations architecture of claim 1 , wherein said operations integration architecture addresses integration of operations architecture components and decides on common standards, interfaces, message formats, monitoring responsibilities, and file logging formats used by other components of the operation architecture.
Claim 21
Dependent Claim
33 words
The operations architecture of claim 2 , wherein said integration framework provides a foundation for standardizing the way system events are communicated, addressed, and managed throughout an environment of the netcentric computing system.
References Cited (Backward Citations)
US4809170A
Cited
US5495610A
Cited
US5590270A
Cited
WO1992020022A1
Cited
EP0520923A2
Cited
US5535388A
Cited
US5619716A
Cited
US5602997A
Cited
US5860012A
Cited
WO1995023373A1
Cited
EP0697691A2
Cited
EP0697655A2
Cited
US5859969A
Cited
US5745753A
Cited
US5933582A
Cited
US5742829A
Cited
WO1997012311A2
Cited
US5758150A
Cited
EP0769739A2
Cited
US5737533A
Cited
US5956479A
Cited
US5799297A
Cited
US5710915A
Cited
US6012071A
Cited
US5805785A
Cited
US6029192A
Cited
EP0810520A1
Cited
US5781732A
Cited
GB2315891A
Cited
US5956400A
Cited
US5761071A
Cited
US5911071A
Cited
EP0829808A2
Cited
US6067577A
Cited
US5835090A
Cited
US5930512A
Cited
US6385655B1
Cited
EP0841616A2
Cited
US6023698A
Cited
US6061695A
Cited
US5892905A
Cited
US5877759A
Cited
WO1998052121A2
Cited
WO1998053396A1
Cited
US6038560A
Cited
WO1998054660A8
Cited
WO1998057260A1
Cited
US5905868A
Cited
US6006171A
Cited
US6112304A
Cited
US6615258B1
Cited
US5924096A
Cited
EP0915422A1
Cited
US6457066B1
Cited
WO1999038079A1
Cited
US6401097B1
Cited
US6366912B1
Cited
US6185573B1
Cited
US6144975A
Cited
US6321263B1
Cited
US6598046B1
Cited
US6584466B1
Cited
US6721713B1
Cited
US6556659B1
Cited
US6542593B1
Cited
US6704303B1
Cited
US6707812B1
Cited
US6195697B1
Cited
US6449588B1
Cited
US6081518A
Cited
US6147975A
Cited
US20020133328A1
Cited
US6426948B1
Cited
US6442547B1
Cited
US6122630A
Cited
US6418430B1
Cited
US6523027B1
Cited
US6289382B1
Cited
US6345239B1
Cited
US6742015B1
Cited
US6438594B1
Cited
US6434628B1
Cited
US6434568B1
Cited
US6477580B1
Cited
US6477665B1
Cited
US6496850B1
Cited
US6502213B1
Cited
US6427132B1
Cited
US6529909B1
Cited
US6529948B1
Cited
US6539396B1
Cited
US20030058277A1
Cited
US6405364B1
Cited
US6549949B1
Cited
US6550057B1
Cited
US6370573B1
Cited
US6571282B1
Cited
US6578068B1
Cited
US6442748B1
Cited
US6339832B1
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2009-03-27 | 2009-09-26 | 2010-03-28 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2013-03-27 | 2013-09-26 | 2014-03-28 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2017-03-27 | 2017-09-26 | 2018-03-28 | $7700.00 | Window Closed / Lapsed |