Solution Architecture Sample Clauses

Solution Architecture. During the Solution Architecture phase, the detailed solution design is finalized based on confirmed requirements. During this phase, the team analyzes the current systems, operations, and operational procedures, identifies the human factors needs, considers implementation options, and with the CUSTOMER, commits the detailed solution design and implementation schedule. Stakeholder participation to identify processes and standard operating impact is critical in this process to support a successful integration of the new system. Current procedures, connectivity, and routing policies are examined so that the appropriate practices are carried forward to the new system environment. Examples of important areas considered include load balancing philosophies and default routing rules. Initial planning for connectivity from the telephone service providers to the Points of Interconnection (“POI”) also begins in the architecture phase. Key solution architecture planning activities include: • Detailed solution design and schematics (onsite, site to site, site to West, firewalls, routers, etc.) • IP specifications • Telephone service provider connectivity specifications • Physical requirements (e.g., equipment room design, floor loading) • Call transfer requirementsTraining plan and schedule • Refined project plan and timeline During the Solution Integration phase, the components of the solution, including processes, applications, servers, network components, and data flow, are ordered, engineered and readied for deployment. All network, regional, data center, and CUSTOMER premises components are delivered, and the equipment rooms and other facilities are readied. Coordination with wireline, wireless, and VoIP telephone service providers is an essential part of this stage to plan for the Service management transition. Telephone service providers receive all necessary information and detail to obtain connectivity to the West systems and the service provider’s connectivity to the POIs is engineered and ordered. Working closely with the CUSTOMER and stakeholder groups, the project team designs customized provisioning plans (including incoming trunk route plans, bridge lists, and dialing plans). Additionally, the documentation and training developers customize the user and process documents and various training courseware, if needed, to meet the needs of the CUSTOMER. During the Solution Deployment phase, all network components and equipment connectivity is validated an...
AutoNDA by SimpleDocs
Solution Architecture. Contractor shall provide a document that outlines requirements, use cases, and a solution framework in an effort to address items defined in the scope statement. The Solution Architecture shall be reviewed by the PAC and submitted for approval or rejection by the CA. This document shall include: a. Identification of requirements that address the subproject requirement b. Defined list of use cases for Test Plan c. Defined list of Acceptance Criteria-the acceptance criteria will be defined for the entire subproject (excluding the Delivery task) and are measured during the Demonstration Milestone. d. Proposed high-level solution that addresses the subproject requirements
Solution Architecture. Elections Voter Registration These principal areas of focus are implemented within an architectural environment shown below. Application Service Xxxx Data Warehouse External Electronic Input Specialty Reporting Web Services Records Archive Clerk Assessor Recorder Central Imaging Workflow Manager The diagram shows the core software applications for the recorder, assessor, voter registration and the central imaging application. With the implementation of XXXX’x eRegistry solution for voter registration, XXXX’x election solution communicates directly with eRegistry. There may be additional data flow to the election solution that is identified through the business process analysis such as death certificates from the Clerk. The additional logical blocks include: (a) Web services – interface and management of intra-COUNTY data flows, including enterprise-wide GIS, (b) Workflow manager – management of data flows between CARE business units, (c) Clerk/Recorder – the highest priority information flows will be supported through a combination of the new recorder application, workflows and central imaging outputs, (d) Data warehouse – a repository for data used for large transactions or reports as determined by the business process analysis, (e) Records archive – historically a storage and retrieval function, its relationship within the CARE-FREE solution is to be determined. (f) Electronic input – the growth of electronic input requires definition of the information entry point into the CARE-FREE solution is required and is shown as a conceptual block.
Solution Architecture. The Supplier shall provide a description on how their solution will comply with the different aspects of the architecture requirements listed under this chapter. The purpose of the architecture requirements is to ensure that the new solution will support NRKs needs. 6.2.1 HIGH AVAILABILITY (HA) AND RESILIENCE‌ Very high service availability is imperative for NRK. Ref. table Mezzanine Sources in 6.1.2, the table column “Category” refers to the terms found in the glossary (section 1.5 ). Primary channels should have redundancy level at 1:1 in both in network layer and related to encoder resources. For secondary channels the Customer expects a pool of minimum 2 extra encoders to be available as spares in case of encoder outage for a given secondary channel. The same applies to infrastructure such as network resources. These requirements should be applied for the production environment for all the different geolocation setups. As for a staging environment, these redundancy requirements do not apply. Keeping in mind the different SLA and availability requirements for the primary channels and the streaming channels specified in chapter 6.1.2, please suggest, and discuss the following: • The systems’ resilience strategies • What type of outage, failure and emergency situations are mitigated with the different possible configurations (1:1, N:2, etc.)? • Is there any added value or additional benefits in running all channels with same resilience/redundancy strategy. • Site-redundancy for the origin service, where each channel is in sync between sites • How non-planned maintenance and / or operational disruptions won’t impact Customers audience

Related to Solution Architecture

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Solution The Supplier’s contractually committed technical approach for solving an information technology business objective and associated Requirements as defined and authorized by the scope of the Contract or any order or Statement of Work issued under the Contract. Solution means all Supplier and Supplier’s third-party providers’ components making up the Solution, including but not limited to Software, Product, configuration design, implementation, Supplier-developed interfaces, Services and Work Product.

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Industry Troubleshooter Where a difference arises between the parties relating to the dismissal, discipline, or suspension of an employee, or to the interpretation, application, operation, or alleged violation of this Agreement, including any question as to whether a matter is arbitrable, during the term of the Collective Agreement, Xxxxx XxXxxxxxxx, Xxxx Xxxxxx, Xxxxx Xxxxxxxx, or a substitute agreed to by the parties, shall at the request of either party:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • 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.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!