Architectures for netcentric computing systems
First Claim
1. 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.
7 Assignments
0 Petitions
Accused Products
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.
1012 Citations
20 Claims
-
1. 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification