Proposed Architecture Sample Clauses

Proposed Architecture. This section briefly describes the architecture being proposed for the implementation of [***]*. a. Design Philosophy The [***]* will be implemented using the TTG OM2000 Product. It will be designed to allow the external interfaces to be modified easily as the needs of the customer change, and standardized interfaces are developed. The core functionality will be shielded from the external interfaces via strictly defined and maintained APIs, and interaction between functional sections of the system is also structured so that enhancements to one feature or function will have predictable and limited impact to all other areas of the system. The NE specific functions and databases will be isolated from the main system and be easy to test and configure to minimize maintenance over the product lifetime.
Sample 1
AutoNDA by SimpleDocs
Proposed Architecture. Based on requirements acquired from section 2 and in terms of multi-layered architecture, the PROPHESY – AR consists of a set of components placed in the application – presentation layer. In terms of PROPHESY architecture, the PROPHESY-AR is a crosscutting layer which crosses PROPHESY-CPS and PROPHESY PdM. Figure 3-1:PROPHESY – AR components 3.2.1 Components of PROPHESY-AR This component in CPS level is interfacing with the following components: • CPS Message bus: with this interface, data visualization retrieves data come from CPS assets (such as sensors, machinery) and local machine learning algorithms (PROPHESY-ML -HF/ML). All these data are presented as topics in the CPS message bus. In PdM level data visualization interfaces with the following components: • PdM message bus: with this interface, data visualization retrieves data come from connected CPS to PdM platform central machine learning algorithms (PROPHESY-XX -XX/ML). All these data are presented as topics in the PdM message bus. • Platform repository: With this interface data visualization retrieves data come from legacy systems (Pdfs, csv, files etc.).
Sample 1
Proposed Architecture. The proposed issue Fault tolerance is one of the most crucial issue which is faced by the cloud users and cloud service providers. If poorly handled, it can lead to increased waiting time, increased job turnaround time and in worst case increased job failures. Strict fault tolerance policies provide a static fault tolerance but induce additional overhead. Considering this we to have propose an adaptive fault tolerant job scheduling method which should vary the degree of Fault tolerance as per the user requirements. The cloud users have been classified into various classes based on the application requirements along with the job classification. [1] X. Xxxxx, X. Xxx, and A. K. Xxx, “A novel high adaptive fault tolerance model in real time cloud computing,” in 2014 5th International Conference - Confluence The Next Generation Information Technology Summit (Confluence), 2014, pp. 138–143. [2] X. Xxxxx and X. Xxxxxxx, “A Migration Approach for Fault Tolerance in Cloud Computing,” Int.
Sample 1
Proposed Architecture. Required or recommended process updates
Sample 1
Proposed Architecture. We have proposed a mashup that will be base on ReST with web or data sources. Data may be transmitted in XML format. This mashup will use a combination of both server and client side logic for data aggregation. We have also designed the client web browser views on the basis of our information requirements analysis of quay allocation and planning process. Figure 6-2: Proposed Information Architecture Model of Information Exchange For Vestbase 6.3.1 API / Contents We are proposing that supply chain member should develop API’s to expose their contents to the partners. We are not very sure either the current information systems applications have capabilities to expose their contents though API’s or not. If not it should be done. Screen scraping is an alternative way to aggregate data in the absence of API’s. But we will not recommend this due to lack of sophisticated, re-usable screen-scraping toolkit software. By developing standard API’s for sharing contents it will easy to accommodate new members in the mashup. 6.3.2 ReST Representational State Transfer (ReST) technique will be use to communicate on web. It is platform independent protocol for communicating with remote services. It is very simple and using XML as a data format and communicates over HTTP. Every object has a unique URI. By using GET operation of ReST we can get contents of that object. Then we can modify that object by using POST, DELETE and PUT operations. It is very easy to build, no toolkit required. It produces human readable results. Design methodology of ReST is very simple. 1- Identify resources to be exposed as service (e.g. quay status, ship trips and planning data etc.) 2- Define ”Nice” URL’s to address them 3- Distinguish between read-only (GET) from modifiable resources (POST, PUT, DELETE) 4- Identify relationships between resources correspond to hyperlinks that can be followed to get more details 5- Implement and deploy to web server It emphasis on pieces of information called resources. ReST is useful while integrating resources. Because Vestbase is collecting information in bits and pieces from different sources, we think ReST is a good option for our enterprise mashup. SOAP is an alternative option for communicating with remote services. But as compared to ReST it is complex in design methodology. It’s a framework to deliver the necessary interoperability between message-based middleware tools across the entire industry. SOAP focus more on integrating design of distributed app...
Sample 1
Proposed Architecture. The architecture for Smart Grid infrastructure is proposed to have bi-directional communication having 5 layers wherein the Field Devices - Energy Meter/ Sub-Stations shall communicate via suitable field communication devices like DCUs/ RTUs and chosen Publically Available Communication Mode to the AMI System/ SCADA System. For visualization, GIS shall be on top of the Layer where all data from AMI and SCADA system shall be visible. The Layout has been designed as per the flow of Communication from field devices to Visualisation engine which is the GIS System. SCADA system shall be supervised by the Data Management System (DMS) and Outage Management System (OMS) which will have all the logics of controlling the Distribution Network. Similarly, the AMI will be supervised by the Meter Data Management (MDM) which will have all the logics and control. The Consumer and the Network data for analysis and effective visualization will be available in the GIS System in the Control Centre. The Control Centre will have a remote disaster data back up at a remote location suitably in Bhubaneswar.
Sample 1

Related to Proposed 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.

  • Architect/Engineer (A/E) means a person registered as an architect pursuant to Tex. Occ. Code Xxx., Chapter 1051, as a landscape architect pursuant to Tex. Occ. Code Xxx., Chapter 1052, a person licensed as a professional engineer pursuant to Tex. Occ. Code Xxx., Chapter 1001 and/or a firm employed by Owner or a design-build contractor to provide professional architectural or engineering services and to exercise overall responsibility for the design of a Project or a significant portion thereof, and to perform the contract administration responsibilities set forth in the Contract.

  • Approved Working Drawings The Final Working Drawings shall be approved by Landlord (the “Approved Working Drawings”) prior to the commencement of construction of the Premises by Tenant. After approval by Landlord of the Final Working Drawings, Tenant may submit the same to the appropriate municipal authorities for all applicable building permits. Tenant hereby agrees that neither Landlord nor Landlord’s consultants shall be responsible for obtaining any building permit or certificate of occupancy for the Premises and that obtaining the same shall be Tenant’s responsibility; provided, however, that Landlord shall cooperate with Tenant in executing permit applications and performing other ministerial acts reasonably necessary to enable Tenant to obtain any such permit or certificate of occupancy. No changes, modifications or alterations in the Approved Working Drawings may be made without the prior written consent of Landlord, which consent may not be unreasonably withheld.

  • Design Development An interim step in the design process. Design Development documents consist of plans, elevations, and other drawings and outline specifications. These documents will fix and illustrate the size and character of the entire project in its essentials as to kinds of materials, type of structure, grade elevations, sidewalks, utilities, roads, parking areas, mechanical and electrical systems, and such other work as may be required.

  • Architect Engineer shall provide assistance to Owner through the commissioning consultant/agent for the purpose of advising and counseling Owner’s personnel in the usage, operation and maintenance of the building mechanical, electrical, and plumbing systems.

  • Drawings and Specifications 9.1 A complete list of all Drawings that form a part of the Contract Documents are to be found as an index on the Drawings themselves, and/or may be provided to Developer and/or in the Table of Contents. 9.2 Materials or Work described in words that so applied have a well-known technical or trade meaning shall be deemed to refer to recognized standards, unless noted otherwise. 9.3 Trade Name or Trade Term It is not the intention of the Contract Documents to go into detailed descriptions of any materials and/or methods commonly known to the trade under “trade name” or “trade term.” The mere mention or notation of “trade name” or “trade term” shall be considered a sufficient notice to Developer that it will be required to complete the work so named, complete, finished, and operable, with all its appurtenances, according to the best practices of the trade. 9.4 The naming of any material and/or equipment shall mean furnishing and installing of same, including all incidental and accessory items thereto and/or labor therefor, as per best practices of the trade(s) involved, unless specifically noted otherwise. 9.5 Contract Documents are complementary, and what is called for by one shall be binding as if called for by all. As such, Drawings and Specifications are intended to be fully cooperative and to agree. However, if Developer observes that Drawings and Specifications are in conflict with the Contract Documents, Developer shall promptly notify District and Architect in writing, and any necessary changes shall be made as provided in the Contract Documents. 9.6 Figured dimensions shall be followed in preference to scaled dimensions, and Developer shall make all additional measurements necessary for the work and shall be responsible for their accuracy. Before ordering any material or doing any work, each Developer shall verify all measurements at the building and shall be responsible for the correctness of same. 9.7 Should any question arise concerning the intent or meaning of the Contract Documents, including the Plans and Specifications, the question shall be submitted to the District for interpretation. If a conflict exists in the Contract Documents, these Construction Provisions shall control over the Facilities Lease, which shall control over the Site Lease, which shall control over Division 1 Documents, which shall control over Division 2 through Division 49 documents, which shall control over figured dimensions, which shall control over large-scale drawings, which shall control over small-scale drawings. In no case shall a document calling for lower quality and/or quantity of material or workmanship control. However, in the case of discrepancy or ambiguity solely between and among the Drawings and Specifications, the discrepancy or ambiguity shall be resolved in favor of the interpretation that will provide District with the functionally complete and operable Project described in the Drawings and Specifications. 9.8 Drawings and Specifications are intended to comply with all laws, ordinances, rules, and regulations of constituted authorities having jurisdiction, and where referred to in the Contract Documents, the laws, ordinances, rules, and regulations shall be considered as a part of the Contract Documents within the limits specified. 9.9 As required by Section 4-317(c), Part 1, Title 24, CCR: “Should any existing conditions such as deterioration or non-complying construction be discovered which is not covered by the DSA-approved documents wherein the finished work will not comply with Title 24, California Code of Regulations, a construction change document, or a separate set of plans and specifications, detailing and specifying the required repair work shall be submitted to and approved by DSA before proceeding with the repair work.”

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

  • Construction Drawings After approving the Additional Programming Information, Landlord shall cause the Architect and the Engineers to prepare and deliver to Tenant Construction Drawings that conform to the approved Space Plan and the approved Additional Programming Information. Such preparation and delivery shall occur within 15 business days after the later of Landlord’s approval of the Additional Programming Information or the mutual execution and delivery of this Agreement. Tenant shall approve or disapprove the Construction Drawings by notice to Landlord. If Tenant disapproves the Construction Drawings, Tenant’s notice of disapproval shall specify any revisions Tenant desires in the Construction Drawings. After receiving such notice of disapproval, Landlord shall cause the Architect and/or the Engineers to revise the Construction Drawings, taking into account the reasons for Tenant’s disapproval (provided, however, that Landlord shall not be required to cause the Architect or the Engineers to make any revision to the Construction Drawings that is inconsistent with the Landlord Requirements or that Landlord otherwise reasonably disapproves), and resubmit the Construction Drawings to Tenant for its approval. Such revision and resubmission shall occur within five (5) business days after the later of Landlord’s receipt of Tenant’s notice of disapproval or the mutual execution and delivery of this Agreement if such revision is not material, and within such longer period of time as may be reasonably necessary (but not more than 15 business days after the later of such receipt or such mutual execution and delivery) if such revision is material. Such procedure shall be repeated as necessary until Tenant has approved the Construction Drawings. The Construction Drawings approved by Landlord and Tenant are referred to in this Work Letter as the “Approved Construction Drawings”.

  • Layout a. Estimate and quantity sheet (1) List of all bid items (2) Bid item quantities (3) Specification item number (4) Paid item description and unit of measure b. Basis of estimate sheet (list of materials) c. General notes and specification data. d. Condition diagram (1) Highway and intersection design features (2) Roadside development (3) Traffic control including illumination e. Plan sheet(s) (1) Existing traffic control that will remain (signs and markings) (2) Existing utilities (3) Proposed highway improvements (4) Proposed installation (5) Proposed additional traffic controls (6) Proposed illumination attached to signal poles. (7) Proposed power pole source f. Notes for plan layout g. Phase sequence diagram(s) (1) Signal locations (2) Signal indications (3) Phase diagram (4) Signal sequence table (5) Flashing operation (normal and emergency) (6) Preemption operation (when applicable) (7) Contact responsible Agency to obtain interval timing, cycle length and offset h. Construction detail sheets(s) (1) Poles (State standard sheets) (2) Detectors (3) Pull Box and conduit layout (4) Controller Foundation standard sheet (5) Electrical chart i. Marking details (when applicable)

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