Architecture Instantiation Sample Clauses

Architecture Instantiation. ‌ Before we consider the relational and Circus model of FMUs, we instantiate the FMI architecture by assigning concrete values to the abstract constants in Fig. 9 (p. 33). As previously noted, this instantiation is also discussed in INTO-CPS Deliverable D2.3a, where it is serves to establish well-formedness of an architecture. In this deliverable, it is a key ingredient for defining the concrete behaviour of a master algorithm. We hence summarise it, focusing on aspects relevant to the work here. To instantiate the abstract type FMI2COMP, we make use of an Isabelle/HOL axiomatization that introduces concrete symbolic constants for each of the FMUs. In this case, we call them train1, train2, merger and interlocking. Fig. 17 includes the corresponding mechanisation fragment. We note that Isabelle axiomatizations can potentially cause logical inconsis- tencies in HOL theories. Here, however, the particular shape of the assump- tions, being that of an enumerated type, guarantees consistency. The INTO-SysML diagram (Fig. 14) is encoded by providing definitions for the seven constants: FMUs, parameters, initialValues, inputs, outputs, pdg and idd. We note that those definitions, unlike the previous one, are xxxxxx- vative — no user-level axioms are hence required to formulate them. As mentioned earlier on, FMUs is a sequence of all FMUs, hence we require its range to include all the values of the FMI2COMP type. Below we recapture its definition for the railways co-simulation system. We recall that simulation parameters are of type FMI2COMP VAR VAL. Con- crete parameters of the railways co-simulation are the routes of the trains and their maximum speed. Fig. 18 illustrates parameter instantiation in Is- abelle. The function InjU is used to construct a value of type VAL from some arbitrary HOL value; it is part of our universal value model [30] and allows us to encode arbitrary HOL values as elements of a universal type VAL. Our syntax for constructing variables is $name:{type}. The types fmi2Integer and fmi2Real are synonyms for the HOL types int and real, encoding inte- gers and real numbers, respectively. Indeed, we introduce such synonyms for all permissible FMI port types as per the FMI standard 2.0 [1]. Next, we consider the input and output ports of the control diagram in Fig. 14 on page 42. We recall that ports are modelled by pairs of type FMI2COMP VAR. An extract of the definition of inputs is recaptured below. For brevity, we only list the input ports o...
AutoNDA by SimpleDocs

Related to Architecture Instantiation

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

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

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

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

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Message Screening 7.4.4.4.1 BellSouth shall set message screening parameters so as to accept valid messages from MRC local or tandem switching systems destined to any signaling point within BellSouth’s SS7 network where the MRC switching system has a valid signaling relationship. 7.4.4.4.2 BellSouth shall set message screening parameters so as to pass valid messages from MRC local or tandem switching systems destined to any signaling point or network accessed through BellSouth’s SS7 network where the MRC switching system has a valid signaling relationship. 7.4.4.4.3 BellSouth shall set message screening parameters so as to accept and pass/send valid messages destined to and from MRC from any signaling point or network interconnected through BellSouth’s SS7 network where the MRC SCP has a valid signaling relationship.

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • Evaluation, Testing, and Monitoring 1. The System Agency may review, test, evaluate and monitor Grantee’s Products and services, as well as associated documentation and technical support for compliance with the Accessibility Standards. Review, testing, evaluation and monitoring may be conducted before and after the award of a contract. Testing and monitoring may include user acceptance testing. Neither the review, testing (including acceptance testing), evaluation or monitoring of any Product or service, nor the absence of review, testing, evaluation or monitoring, will result in a waiver of the State’s right to contest the Grantee’s assertion of compliance with the Accessibility Standards. 2. Grantee agrees to cooperate fully and provide the System Agency and its representatives timely access to Products, records, and other items and information needed to conduct such review, evaluation, testing, and monitoring.

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