Functional Architecture Sample Clauses

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).
AutoNDA by SimpleDocs
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 general, the distributed system architecture of the fleet is designed around functional layers: 1xxxx://xxx.xxx.xxx Robot Abilities (on-board control) 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. Shared Knowledge Management 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. Fleet Management & Coordination 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.
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. This section presents the functional architecture of the connectivity required to outsourcers. Figure 1 – Functional Architecture with Ibone Edge Circuit 81 COMCAST CONFIDENTIAL US.54162848.01 Figure 2 – Functional Architecture with Commercial Services EDIA Circuit 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. This section presents the functional architecture of the connectivity required to outsourcers.
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.
AutoNDA by SimpleDocs

Related to Functional Architecture

  • Interfaces Bellcore’s GR-446-CORE defines the interface between the administration system and LIDB including specific message formats. (Bellcore’s TR-NWP-000029, Section 10)

  • Design At no cost to SCE, Seller shall be responsible for:

  • Project Management Project Management Institute (PMI) certified project manager executing any or all of the following: • Development of Project Charter • Development of project plan and schedule • Coordination and scheduling of project activities across customer and functional areas • Consultation on operational and infrastructure requirements, standards and configurations • Facilitate project status meetings • Timely project status reporting • Address project issues with functional areas and management • Escalation of significant issues to customers and executive management • Manage project scope and deliverable requirements • Document changes to project scope and schedule • Facilitate and document project closeout

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Programming (a) Pursuant to Section 624 of the Cable Act, the Licensee shall maintain the mix, quality and broad categories of Programming set forth in Exhibit 4, attached hereto and made a part hereof. Pursuant to applicable federal law, all Programming decisions, including the Programming listed in Exhibit 4, attached hereto, shall be at the sole discretion of the Licensee.

  • Contract Management To ensure full performance of the Contract and compliance with applicable law, the System Agency may take actions including:

  • Engineering Forest Service completed survey and design for Specified Roads prior to timber sale advertisement, unless otherwise shown in A8 or Purchaser survey and design are specified in A7. On those roads for which Forest Service completes the design during the contract, the design quantities shall be used as the basis for revising estimated costs stated in the Schedule of Items and adjusting Timber Sale Account. Forest Service engineering shall be completed according to the schedule in A8. Should Forest Service be unable to perform the designated survey and design by the completion date or other agreed to time, upon written agreement, Purchaser shall assume responsibility for such work. In such event, Contracting Officer shall revise:

  • Hosting 46.7.4.1 At CLEC’s request, SBC-SWBT and SBC-AMERITECH shall perform hosting responsibilities for the provision of billable message data and/or access usage data received from CLEC for distribution to the appropriate billing and/or processing location or for delivery to CLEC of such data via SBC-SWBT’s and SBC-AMERITECH’s internal network or the nationwide CMDS network pursuant to the applicable Appendix HOST, which is/are attached hereto and incorporated herein by reference.

Time is Money Join Law Insider Premium to draft better contracts faster.