Functional Architecture Sample Clauses
The Functional Architecture clause defines the overall structure and organization of a system's components and their interactions. It typically outlines how different modules, subsystems, or services are arranged and how they communicate to achieve the system's objectives. For example, it may specify the division between front-end and back-end components, data flow, and integration points. This clause ensures that all parties have a clear understanding of the system's design, facilitating coordination, reducing misunderstandings, and providing a reference for development and maintenance.
Functional Architecture. The SoftFIRE Middleware is based on a microservice-oriented architecture where the EM plays the central role dispatching incoming requests and events to several managers in charge of handling different types of resources (see Figure 1).
Functional Architecture. This section presents the functional architecture of the connectivity required to outsourcers. US.54162848.01 The SIP to outsourcer Architecture will include numerous components which will be used for redundancy/route-advance purposes to insure proper termination of the call.
Functional Architecture. End user🚹 Download results & report Download input data Upload fresh input data Specify a batch Upload historical data and results The scheme hereunder shows the logical Simulation Facility components and its external interactions. Internal interactions are shown for clarity purpose, but as they require a technical analysis of the requirements, their design will be specified in a later stage. f s s s ) ) s
Functional Architecture. The SEGRID functional architecture is based on the functional interoperability layer in the SGAM. In this, the functional architecture focuses on the information flow required to implement the desired functionality, including as assets the data source, communication channels, and data recipient. All assets described in this view are also assigned to the corresponding market roles, i.e.,
Functional Architecture. In consideration of the payment of the license fees set forth in the Contract, Lucent will deliver ATP Release 4.0 in accordance with the milestones in SECTION 11.4, "Deployment Milestones" of this SOW. The features of the CONNECTVU-ATP product (Release 4.0) listed in the following table are included in the pricing in the Contract unless explicitly noted otherwise. --------------- -------------------------------------------------- -------------------------------------------------- REF. NO. FUNCTION COMMENTS --------------- -------------------------------------------------- -------------------------------------------------- ATP1.1 Support for 5ESS generic 5E12 and DMS100 generic ATP Release 4.0 NA007. --------------- -------------------------------------------------- -------------------------------------------------- ATP1.2 Support of mechanized switch provisioning for A complete list of views/tables will be Infrastructure Recent Change/Verify. delivered under a separate cover. --------------- -------------------------------------------------- -------------------------------------------------- ATP1.3 Support of mechanized switch provisioning for A complete list of views/tables will be --------------- -------------------------------------------------- -------------------------------------------------- LUCENT TECHNOLOGIES INC. AND ALLEGIANCE TELECOM, INC. PROPRIETARY 74 --------------- -------------------------------------------------- -------------------------------------------------- REF. NO. FUNCTION COMMENTS --------------- -------------------------------------------------- -------------------------------------------------- Line-Side Recent Change/Verify. delivered under a separate cover. --------------- -------------------------------------------------- -------------------------------------------------- ATP1.4 Switch coupler to create and maintain an mirror ALLEGIANCE must purchase appropriate time updates to the ATP shadow database whenever Echo-Back image of the switch database by changes are made to the switch database. providing real feature support from NORTEL. --------------- -------------------------------------------------- -------------------------------------------------- ATP1.5 Real time provisioning of switch Recent Change/Verify. --------------- -------------------------------------------------- -------------------------------------------------- ATP1.6 Power tools for rapid creation of multiple Recent Change/Verify across switch network. ---...
Functional Architecture. The functional architecture maps the business functions to application functions and identifies the services that are needed to support these functions. The orchestration of these services to execute a business process and the identification of common services are also defined. Application standards, the technology standard, and usage of products and tools will also be defined under the functional architecture. The integration of applications and services and the usage of tools to streamline the integration will also be defined. Workgroups will be created to work with the business stakeholders and IT system owners to develop the functional architecture.
Functional Architecture. This section presents the functional architecture of the connectivity required to outsourcers.
Functional Architecture. In general, the distributed system architecture of the fleet is designed around functional layers: 1▇▇▇▇://▇▇▇.▇▇▇.▇▇▇ At the bottom, an ability level encapsulates the basic robot functionalities like localisation, individual reactive navigation behaviours, pick and place operations, etc, running on the processing units of the individual robots in the fleet. This facilitates low-latency, closed-loop control of individual lower-level abilities of the robots, and is based entirely on ROS components, deployed locally to the robots in the fleet. In the functional architecture, on top of the ability level, we designed a shared knowledge and consolidation layer that encompasses the information fusion and sharing abilities of the robotic fleet, like mapping, perception consolidation, and data sharing. These comprise services that run on cloud or site-local computing platforms, following a Soft- ware as a Service (SaaS) paradigm to facilitate dissemination and exploitation through accessible APIs of the generic implementations. In the first implementation of the layer, communication is mainly facilitated via ROS services, but in the course of the project these can be more and more opened up to publicly accessible web services where appropriate. At the top of this conceptual architecture, the distributed aspects of fleet management (WP5) will be implemented. This layer comprises fleet-level planning and scheduling, consulting warehouse operations-level systems and expertise for selecting tasks to be accomplished, and coordinates the fleet given constraints provided from the shared knowledge level.