Sequence Diagrams Sample Clauses

Sequence Diagrams. ‌ Before the system can enter normal operations, some setup will be necessary – mostly concerning components registering themselves with the Global Resource Directory, so their IPv6-addresses can be queried on demand. The following manual configuration setup steps will be necessary: 1) Any configuration that is required for legacy devices. 2) Install the maintenance app on the mobile phone and set up the user account. 3) Set the table of emergency contact SMS numbers at the maintenance tool. 4) Set up user accounts at the maintenance tool for remote access via a maintenance app. 5) Set up replacement instructions for (some) devices. 6) Register RFIDs of building automation devices with the STIS. 7) Set up the inventory management server to accept orders. In addition, all components will be required to register themselves with the Global Resource Directory upon start-up. The IoT6 Gateway should also register the legacy devices attached to it with the Global Resource Directory. Lastly, since the CMS will routinely have to access the IoT6 Gateway, it may make sense that it requests its address once and then caches it, so as to not issue too many requests to the Global Resource Directory.
Sample 1
AutoNDA by SimpleDocs
Sequence Diagrams. A.1.1 Selecting Wetlands Requirements A.1.2 Testing for Intersections Requirements A.1.3 Testing for Closest Stream (Proximity) Requirements A.1.4 Viewing an Analysis Report A.1.5 Annotating a Report
Sample 1
Sequence Diagrams. The timeline in UML is from the top to the bottom. Each arrow is method call. Each vertical line represents a class and its own life line. These diagrams illustrate the different method call available in the class MonitorDaemon and what this produces inside the other classes. LaunchCapture creates the CaptureController, launches the thread and then adds it to the data stored inside the class. Figure 18: Sequence Diagram 2 for the MonitorDaemon class StopCapture stops the thread, destroys the instance of CaptureController and then removes it from the data stored inside the class. Figure 19: Sequence Diagram 2 for the MonitorDaemon class
Sample 1
Sequence Diagrams. 2.1.1 Sender Intent Based Receiver Pull (notified pull) The sequence diagram below depicts the flow for the Sender Intent Based Receiver Pull (SIBR Pull) using OAuth 2.0 and HL7-FHIR, also known as "notified pull". The flow contains the following sections: • Invite the Receiver; • Cancellation by Sender (option), this block is only to be used when the Sender needs to withdraw the pull invitation, e.g., when the Sender invited a wrong Receiver; • Receiver performs pull interaction(s). Each section consists of several steps. The steps correspond to the numbers in the sequence diagram. Invite the Receiver 1 Optional reference to a request-Type resource that produced this event. If a workflow has been initiated, this should be referenced. 1 If the SIBR pull is part of a managed workflow involving both the Sender and the Receiver, and this workflow specifies the creation of a Task (W1) at the Sender, then the flow starts with a creation of this Task on the Sender EHR System. 2 The Sender creates a consent_token, which is used later to communicate a presumed consent for the exchange of patient information. The Receiver must treat the consent_token as opaque. The Receiver should not depend on any information contained in the consent_token. 3 The Sender creates an assertion, which can be used as an authorization grant when requesting an access_token in the next step.
Sample 1

Related to Sequence Diagrams

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

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

  • Outputs Analogue and digital outputs of protected content are allowed if they meet the requirements in this section and if they are not forbidden elsewhere in this Agreement..

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Residence Life or the Director’s designee.

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

  • Student Evaluations Student evaluations shall be completed by the end of the 12th week of the Fall semester.

  • Flexible Work Schedule A flexible work schedule is any schedule that is not a regular, alternate, 9/80, or 4/10 work schedule and where the employee is not scheduled to work more than 40 hours in the "workweek" as defined in Subsections F. and H., below.

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.50 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0150. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. The sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.

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