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. Figure 18: Parameter definition of the railways instantiation. × × 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 in...
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.

  • Program Narrative All restricted xxxxxx courses which are taught for the purpose of qualifying an individual for restricted xxxxxx license to practice barbering shall consist of a minimum of 1200 hours of training to prepare each restricted xxxxxx to service their communities.

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

  • Medical Verification The Town may require medical verification of an employee’s absence if the Town perceives the employee is abusing sick leave or has used an excessive amount of sick leave. The Town may require medical verification of an employee’s absence to verify that the employee is able to return to work with or without restrictions.

  • Infrastructure Improvements The design, redevelopment and construction and completion of certain infrastructure improvements, including sewer, stormwater, electrical and water main improvements, along with other similar 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:

  • ODUF Testing 6.6.1 Upon request from TWTC, AT&T shall send ODUF test files to TWTC. The Parties agree to review and discuss the ODUF file content and/or format. For testing of usage results, AT&T shall request that TWTC set up a production (live) file. The live test may consist of TWTC’s employees making test calls for the types of services TWTC requests on ODUF. These test calls are logged by TWTC, and the logs are provided to AT&T. These logs will be used to verify the files. Testing will be completed within thirty (30) days from the date on which the initial test file was sent.

  • Installation, Maintenance, Testing and Repair Unless otherwise agreed in writing by the Parties, to the extent required by Applicable Law, Interconnection provided by a Party shall be equal in quality to that provided by such Party to itself, any subsidiary, affiliates or third party. If either Party is unable to fulfill its obligations under this Section 14.2, it shall notify the other Party of its inability to do so and will negotiate alternative intervals in good faith. The Parties agree that to the extent required by Applicable Law, the standards to be used by a Party for isolating and clearing any disconnections and/or other outages or troubles shall be at parity with standards used by such Party with respect to itself, any subsidiary, affiliate or third party.

  • Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.

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

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