58 results about "Enterprise architecture" patented technology

A selected scenario of a design ICD document for an integrated enterprise is validated by examining each IDL call of each sequence diagram forming part of the selected scenario. A list of data attributes contained in one or more of the IDL calls are generated and each IDL call associated therewith is generated. A physical location to which each such IDL call is mapped is then associated with the IDL call. By analyzing the IDL calls and associated physical locations on a data attribute-by-data attribute basis, inconsistencies in the physical mapping of the data attributes to the databases forming an IIS for the integrated enterprise may be identified and subsequently corrected.

A device for modeling an integrated enterprise includes a first tool for constructing a model of the integrated enterprise and a second tool which validates compliance of documents constructed by the first tool with a set of standards. The documents which may be constructed by the first tool include an analysis interface control document (“ICD”) and a design ICD document. The second tool may then be used to selectively compare either the analysis ICD or the design ICD with selected ICD standards and generate an analysis ICD document standards exception report and a design ICD document standards exception report, respectively, which lists each variation of the analysis and design ICD documents from the selected ICD standards. The analysis and/or design ICD standards exception reports may subsequently be used as guides to correct errors in the analysis and/or design ICD documents causing the exceptions.

A device for modeling an integrated enterprise includes a first tool for constructing a model of the integrated enterprise and a second tool for analyzing calls, contained in the constructed model, between applications of the integrated enterprise and a database shared thereby. The call analysis tool identifies data attribute imbalances in calls between the applications of the integrated enterprise and the shared database. Data attribute imbalances result if the calls attempt to consume data which was never produced or if the calls produce data which is never consumed. The call analysis tool also generates producer/consumer maps of the data attributes used in the model, producer exception reports which identify data attributes which are consumed but never produced and consumer exception reports which identify data attributes which are produced but never consumed.

A device by which RFID data can pass from the RFID reader, or from the plant floor PLC and reader, to business applications at the enterprise level. The RFID tag date is easily integrated into a PLC for integration with other equipment. The security of the overall system is maintained by only allowing tag information to be available to authenticated users by means of active or passive tags and the use of certificates and encryption during the data transmission. Multiple RFID reader device drivers can be customized to support any number of readers available in the marketplace, with each RFID reader including its own data structure, protocol and handshaking methodology for communication. Additionally, a set of run time and configuration tools is provided which allow for an easier integration of RFID tag data into the enterprise architecture for use by other business applications.

A method for maintaining a dynamic reference repository within an enterprise architecture domain, comprises discovering pertinent input(s) to the dynamic reference repository. These newly discovered pertinent inputs are then retrieved to the dynamic reference repository. After retrieval, the pertinent input(s) to the dynamic reference repository are managed and distributed within the enterprise architecture domain.

A method and system for calculating the return-on-investments (ROI) for an enterprise architecture. The present invention discloses a unique set of metrics which provides improved accuracy for the economic and architecture for the construction of future systems. A preferred embodiment of the present invention focuses on developing process improvement assumptions associated with estimating the impact of the proposed capabilities. It includes the following components: an understanding of the client's strategic drivers, an understanding of the key business process areas, an identification of the business capabilities that a solution can offer the client, an estimation of the business processes improvements, and an estimation of the financial impact the proposed solution will have on the client. The value framework and ROI model of the present invention incorporates a client's strategic position and key processes before the benefits of a proposed solution or initiative can be estimated.

Systems and methods for determining the impact of an asset on an enterprise architecture using a data model are disclosed. These systems and methods may determine the impact of a particular asset on the enterprise architecture represented by the data model, where determination of the impact of any particular asset takes into account not only assets that depend directly on that particular asset, but assets that depend indirectly on that asset as well. Using the data model of the enterprise architecture, dependency chains for one or more components of the data model can be discovered and a dependency map created. Using impact ratings associated with relationships between components in the dependency chains of a particular component, the impact of that particular component both on another individual component, and aggregately on an environment, can be determined. These systems and methods may also allow the determination of the risk of a particular component.

An exemplary embodiment of the invention relates to a method, system, and storage medium for creating and maintaining an enterprise architecture over a network. The system comprises at least one client system; a server operably coupled to the client system via the network; a plurality of business applications executable via the server; a data storage device in communication with the server via the network; an enterprise architecture assessment model executing on the system; and a maturity model map generated via the enterprise architecture assessment model. The maturity model map comprises a process component, an organization component, a business component, and a technology component. The maturity model map is generated using information stored in the data storage device. Other embodiments of the invention include a method and storage medium for implementing enterprise architecture assessment model.

The present invention is a distributed system comprising client- and server-side components that, together, allow XML schemas or the like to be managed in a collaborative way across an enterprise environment. The server-side component, or server, is used to assemble a collection of one or more schemas. The server exposes the collection of schemas to one or more client components that connect to the server. Such connections may be made over a computer network. The client component preferably exports a display interface through which a user can visualize dependencies between schemas, e.g., by dragging them into a workspace and viewing all related schemas and how they are connected, as well as what elements and other components they define. In this way, the client component provides a high-level view of a larger (e.g., enterprise-wide) information architecture.

A device for modeling an integrated enterprise includes a first tool for constructing a model of the integrated enterprise and a second tool for analyzing calls, contained in the constructed model, between applications of the integrated enterprise and a database shared thereby. The call analysis tool identifies data attribute imbalances in calls between the applications of the integrated enterprise and the shared database. Data attribute imbalances result if the calls attempt to consume data which was never produced or if the calls produce data which is never consumed. The call analysis tool also generates producer/consumer maps of the data attributes used in the model, producer exception reports which identify data attributes which are consumed but never produced and consumer exception reports which identify data attributes which are produced but never consumed.

A distributed architecture for an enterprise portal involves a network of connected, department-sized portal servers working together as a group of federated portals, including a union of independent entities working together to provide specific functions. An enterprise portal architecture includes a number of user systems connected, over a network, to at least two portals, a plurality of data sources coupled over a network to the portals, where each of the portals include a knowledge framework unit. The knowledge framework units, which are interconnected, each include a digital business identity and a knowledge broker, wherein the digital business identity includes a user directory configured to store information unique to a subset of said plurality of users, and wherein the knowledge broker includes a meta-data directory.

Systems and methods for a reference model for the representation of an arbitrarily complex enterprise architecture are disclosed. These systems and methods provide a reference model composed of component types and relationship types useful in modeling an enterprise architecture. The reference model may be constructed according to a set of domains. A set of component types associated with each of these domains may be defined and relationship types defined for these component types. A data model of a particular enterprise architecture may then be instantiated using this reference model.

Under the present invention, components of an enterprise architecture are first identified. This process not only involves hardware, software and topographic identification, but also includes developing and documenting an understanding of the business processes occurring within the enterprise architecture. Based on this analysis, an enterprise architecture profile is developed. Thereafter, transactions that occur within the enterprise architecture are identified, and data related thereto is collected for different geographic regions. In general, a transaction involves a set (e.g., one or more) of steps (e.g., “clicks”) within an application of the enterprise architecture. For each such step, data is collected. Based on the data collection one or more transaction class profiles are developed. Using these profile(s) and the enterprise architecture profile, transaction response time(s) can be estimated.

The present invention discloses an enterprise network architecture based on a bill of product materials and a constructing method therefor. The enterprise network architecture comprises: a data collecting module, which is used to acquire unique identifier data of an enterprise, attribute data of a product produced by the enterprise and bill of materials (BOM) data of a purchased component; a server, which is used to construct a public product tree structure that stores the foregoing obtained data; a data processing module, which is connected with the server and is used for traversing the public product tree structure, obtaining a product supply relationship, a homogeneity relationship, and a potential supply relationship according to a relationship between the attribute data of the product produced by the enterprise and the BOM data of the purchased component that are stored in the public product tree structure, and mapping the product supply relationship, the homogeneity relationship, and the potential supply relationship to a supply chain table, a homogeneity chain table and a potential supply chain table to form a product relationship network, and according to the formed product relationship network, finally obtaining the enterprise network architecture corresponding to the product.

A system for measuring performance of an enterprise architecture includes an enterprise collaborative recommender engine that provides recommendations for an account within the enterprise architecture based upon enterprise assessments; a health control process engine that triggers rebuilding of the heat map topology view that provides recommendations for updating the enterprise architecture towards increased maturity in response to recommendations from the enterprise collaborative recommender engine; and an enterprise heat map generator that presents a heat map providing maturity information of the enterprise architecture for each domain.

Analyzing technical solutions for supporting desired business capabilities includes constructing a plurality of alternative technical solutions, wherein each alternative technical solution comprises a respective set of technology components, wherein each technology component provides support for a respective requirement associated with fulfilling a respective one of a plurality of desired business capabilities. Then an implementation roadmap can be generated comprising any technology component that is a member of more than one of the respective sets of technology components; and this implementation roadmap can then be provided as output.

Modeling an enterprise architecture includes associating a plurality of desired business capabilities with a plurality of requirements and associating each of a plurality of technology components with one or more of the plurality of requirements, based on a respective technology supporting the one or more requirements. Then a model may be constructed that includes linking each of the technology components with one or more of the desired business capabilities based on the associating of the plurality of desired business capabilities with the plurality of requirements and the associating of each of the plurality of technology components with one or more of the plurality of requirements.

A process for developing Enterprise Architectures that results in a dramatic reduction in the complexity of the architecture and, therefore, in the cost of developing, implementing, and maintaining that architecture. The process is novel in that it is based on a mathematical model for complexity and how complexity can be reduced. The process for constructing enterprise architectures can also validate the architecture before it is implemented. The process begins by partitioning the Enterprise Architecture into autonomous subunits using the equivalence relation synergistic. It then uses type relations between these autonomous subunits to identify redundancies which can be simplified through consolidation. Once these autonomous subunits have been simplified as much as possible through consolidation, outsourcing, or functionality reduction, they are prioritized through risk/value analysis pictorially represented as Risk/Value Graphs.