Claims
- 1. A system comprising:
a portal connected to user interface (UI) components; application logic linking the UI components to a repository layer and connectivity layer through an object access layer; and source systems linked to the repository layer and the connectivity layer.
- 2. The system of claim 1 further comprising input/output (I/O) devices linked to the portal.
- 3. The system of claim 2 in which the I/O devices are web devices that communicate with the portal using Wireless Application Protocol (WAP) and Wireless Markup Language (WML).
- 4. The system of claim 2 in which the I/O devices are Internet browsers that communicate with the portal using Hypertext Transfer Protocol (HTTP) and Extended Markup Language (XML).
- 5. The system of claim 1 in which the portal is a common interface that receives requests from clients and generates information views (iViews) in response.
- 6. The system of claim 5 in which the iViews are web pages.
- 7. The system of claim 1 in which the UI components comprise:
application navigation components; application integration components; and information views.
- 8. The system of claim 5 in which the client requests are coupled to the portal by a proxy server.
- 9. The system of claim 1 in which the repository layer comprises:
a data object model; and databases including metadata and data, the data including templates.
- 10. The system of claim 9 in which the metadata comprises data pertaining to roles, work sets and personalization information.
- 11. The system of claim 9 in which the metadata interacts with the object access layer, the connectivity layer and the application logic.
- 12. The system of claim 9 in which the metadata interacts with the templates, the templates providing a format of information according to preset conditions.
- 13. The system of claim 12 in which the templates interact with Web application server (WAS) processes and core restructuring processes.
- 14. The system of claim 9 in which the databases interact with the source systems through base systems connectors using a markup language.
- 15. The system of claim 9 in which the databases interact with the source systems through base systems connectors using web services.
- 16. The system of claim 9 in which the databases interact with the source systems through base systems connectors using transmission control protocol/Internet protocol (TCP/IP).
- 17. The system of claim 1 in which source systems communicate with each other through a firewall.
- 18. An architecture comprising:
a network linked to a portal, the portal generating information views and an interface to an enterprise management system; and enterprise base systems linked to the enterprise management system, the enterprise base systems including application services and multiple types of base system data.
- 19. The architecture of claim 18 further comprising client systems linked to the network.
- 20. The architecture of claim 19 further comprising a proxy server linking the client systems to the network.
- 21. The architecture of claim 18 in which the portal provides a common interface through user interface (UI) components.
- 22. The architecture of claim 18 in which enterprise management system includes integrated application services to manage business objects and business processes in a business enterprise.
- 23. The architecture of claim 22 in which business objects and business processes comprise personnel resources, development project resources, business program resources, inventory resources, accounts, business products and business services.
- 24. The architecture of claim 18 in which the application services comprise human resource management systems, customer relationships management systems, financial management systems, project management systems, knowledge management systems, business warehouse systems, time management systems, electronic file systems and mail systems.
- 25. The architecture of claim 18 in which the enterprise management system includes a process to consolidate and integrate base system data into a single management tool.
- 26. The architecture of claim 25 in which the single management tool comprises systems and methods to facilitate generation of cross-functional applications that draw on resources of the enterprise base systems.
- 27. The architecture of claim 18 in which the enterprise base systems reside in servers connected to a public network.
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Application entitled “ENTERPRISE CHANGE PLANNING AND EXECUTION,” filed on Mar. 14, 2003, application Ser. No. 60/455,087.
Provisional Applications (1)
|
Number |
Date |
Country |
|
60455087 |
Mar 2003 |
US |