Traceability and Provenance Sample Clauses

Traceability and Provenance. How to make use of the traceability and provenance features of the tool chain using examples from the line-follower pilot study. References
AutoNDA by SimpleDocs
Traceability and Provenance. ‌ The Deploy 18 project presents an approach to traceability from informal requirements to a formal model in the Event-B notation [Pro12]. In contrast to INTO-CPS, Deploy concentrate on traceability from complete requirements to only state-based models, rather than the flexible tracing of system engineering model elements. As with the INTO-CPS project, Deploy see tool support as critical for traceability, and produce an integration of the ProR platform for requirements engineering and the Rodin platform for Event- B modelling. The ADVANCE 19 project continued this development. In addition, in collaboration with the VERDE project, a traceability solution was developed between Eclipse-based tools such as ProR and Topcased20 for SysML. This uses a concept of Tracepoints to link to Eclipse model elements [GJ11]. In the OPENCOSS 21 project traceability is used for evidence management and impact analysis of requirement through to safety cases [vdBLK+15]. Several traceability rela- tionships are defined linking ‘artefacts’. The traceability links are then used as part of impact analysis using the Evidence Management tool support produced in the project. Using SVN repositories, a user must manually add artefacts, linked to resources in a SVN repository and record the necessary traces. This is in contrast to INTO-CPS which aims to have a central traceability and management tool which will be integrated with the INTO-CPS tool chain, and a greater number of traceability links covering a modelling and simulation. In the COMPASS 22 project, requirements were modelled and there was support for trace- ability between models. Explicit traceability mechanisms supporting forwards and back- wards tracing were not a focus of the project, however a traceability pattern was produced 15xxxxx://xxx.xxxxxxxx.xxx/ 16xxxx://xxx.xxxxxx-xxxxxxx.xx/‌‌ 17xxxxx://xxx.xxxxxxxx.xxx/external-projects/modrio 18xxxx://xxx.xxxxxx-xxxxxxx.xx‌ 00xxx.xxxxxxx-xxx.xx/ 20xxxxx://xxx.xxxxxxxx.xxx/topcased 21xxxx://xxx.xxxxxxxx-xxxxxxx.xx 22xxxx://xxxxxxx-xxxxxxxx.xx‌‌ for SysML SoS engineering [PHP+14]. It would appear that provenance metadata could be captured within the existing framework, but this was not a subject of study in the project. In common with INTO-CPS, the SPRINT 23 project uses OSLC to link models form various tools, from requirements in DOORS through to architectural models using IBM Rhapsody and Simulink and Modelica system models. Although not explicitly used for traceability or mo...

Related to Traceability and Provenance

  • Traceability 11.1 Under the terms of this Agreement, Supplier shall have and operate a process to ensure that all Products, sub-assemblies and the components contained therein supplied to the Buyer are completely Traceable back to manufacturer by batch or lot or date code. 11.2 Further Supplier hereby agrees, unless directed otherwise by the Buyer, to procure components through franchised distributors or direct component Suppliers. Supplier agrees to indemnify and hold the Buyer harmless from and against all costs and expenses for the removal, repair or replacement and reinstallation of counterfeit components incorporated into a Product sold by Supplier to the Buyer where the counterfeit component was procured by Supplier from a person or entity other than a franchised distributor or direct component Supplier or other person or entity pre-approved by the Buyer in writing.

  • Review of legality and data minimisation (a) The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e). (b) The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request.

  • Compatibility 1. Any unresolved issue arising from a mutual agreement procedure case otherwise within the scope of the arbitration process provided for in this Article and Articles 25A to 25G shall not be submitted to arbitration if the issue falls within the scope of a case with respect to which an arbitration panel or similar body has previously been set up in accordance with a bilateral or multilateral convention that provides for mandatory binding arbitration of unresolved issues arising from a mutual agreement procedure case. 2. Nothing in this Article and Articles 25A to 25G shall affect the fulfilment of wider obligations with respect to the arbitration of unresolved issues arising in the context of a mutual agreement procedure resulting from other conventions to which the Contracting States are or will become parties.”.

  • Ordering and Provisioning 53.3.1 CenturyLink will provide necessary ordering and provisioning business process support as well as those technical and systems interfaces as may be required to enable CLEC to provide resale services, including the functions, features, and capabilities of such services, and Unbundled Network Elements. If CenturyLink deploys any enhanced electronic capability CenturyLink will notify CLEC of availability and CLEC shall use the processes for performing transaction(s) to the extent practicable and the use of any other interface or process will be discontinued. 53.3.2 The Parties agree that orders for services under this Agreement will not be submitted or accepted until thirty (30) Days after the completion of all account establishment activities, including but not limited to, the documents and information subscribed in Section 45.1, unless the Parties mutually agree upon a different date based on the specific circumstances of the Parties’ relationship. 53.3.3 Except as specifically provided otherwise in this Agreement, pre- ordering, ordering and provisioning of resold services shall be governed in accordance with CenturyLink’s Standard Practices. 53.3.4 CenturyLink will provide provisioning intervals and procedures for design and complex services on a nondiscriminatory basis. Complex Service Order charges pursuant to Tariff terms may apply. 53.3.5 Where Technically Feasible, the NEAC will coordinate support for all designed and/or complex services provided to CLEC. 53.3.6 To the extent required by Applicable Law, and upon request from CLEC, employing CenturyLink’s LSR, CenturyLink will provide blocking of 700, 900, and 976 services, or other services of similar type as may now exist or be developed in the future, and shall provide Billed Number Screening (BNS), including required LIDB updates, or equivalent service for blocking completion of bill-to-third party and collect calls, on a line, PBX, or individual service basis. Blocking shall be provided to the extent (a) it is an available option for the Telecommunications Service resold by CLEC, or (b) it is Technically Feasible when requested by CLEC as a function of Unbundled Network Elements. 53.3.7 When ordering a resale service via an LSR Service Order, CLEC may order separate interLATA and IintraLATA service providers (i.e., two PICs) on a line or trunk basis, and CLEC agrees to pay the applicable Service Order and PIC charges associated with such order. CenturyLink will accept PIC change orders for IntraLATA toll and long distance services through the service provisioning process. 53.3.8 The standard Service Order charges as listed in the Table 1 of this Agreement shall apply to all orders.

  • Quality of Materials and workmanship The Contractor shall ensure that the Construction, Materials and workmanship are in accordance with the requirements specified in this Agreement, Specifications and Standards and Good Industry Practice.

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

  • Data Return and Destruction of Data (a) Protecting PII from unauthorized access and disclosure is of the utmost importance to the EA, and Contractor agrees that it is prohibited from retaining PII or continued access to PII or any copy, summary or extract of PII, on any storage medium (including, without limitation, in secure data centers and/or cloud-based facilities) whatsoever beyond the period of providing Services to the EA, unless such retention is either expressly authorized for a prescribed period by the Service Agreement or other written agreement between the Parties, or expressly requested by the EA for purposes of facilitating the transfer of PII to the EA or expressly required by law. As applicable, upon expiration or termination of the Service Agreement, Contractor shall transfer PII, in a format agreed to by the Parties to the EA. (b) If applicable, once the transfer of PII has been accomplished in accordance with the EA’s written election to do so, Contractor agrees to return or destroy all PII when the purpose that necessitated its receipt by Contractor has been completed. Thereafter, with regard to all PII (including without limitation, all hard copies, archived copies, electronic versions, electronic imaging of hard copies) as well as any and all PII maintained on behalf of Contractor in a secure data center and/or cloud-based facilities that remain in the possession of Contractor or its Subcontractors, Contractor shall ensure that PII is securely deleted and/or destroyed in a manner that does not allow it to be retrieved or retrievable, read or reconstructed. Hard copy media must be shredded or destroyed such that PII cannot be read or otherwise reconstructed, and electronic media must be cleared, purged, or destroyed such that the PII cannot be retrieved. Only the destruction of paper PII, and not redaction, will satisfy the requirements for data destruction. Redaction is specifically excluded as a means of data destruction. (c) Contractor shall provide the EA with a written certification of the secure deletion and/or destruction of PII held by the Contractor or Subcontractors. (d) To the extent that Contractor and/or its subcontractors continue to be in possession of any de-identified data (i.e., data that has had all direct and indirect identifiers removed), they agree not to attempt to re-identify de-identified data and not to transfer de-identified data to any party.

  • Calibration The comparison of a measurement system or device of unverified accuracy with a measurement system of known and greater accuracy to detect deviation of the unverified measurement system from required performance specifications (of the unverified measurement system or device) and to quantify all measured values to applicable units of the international system of units.

  • Periodic Review of Costs of Environmental Compliance In the ordinary course of its business, the Company conducts a periodic review of the effect of Environmental Laws on the business, operations and properties of the Company and its subsidiaries, in the course of which it identifies and evaluates associated costs and liabilities (including, without limitation, any capital or operating expenditures required for clean-up, closure of properties or compliance with Environmental Laws or any permit, license or approval, any related constraints on operating activities and any potential liabilities to third parties). On the basis of such review and the amount of its established reserves, the Company has reasonably concluded that such associated costs and liabilities would not, individually or in the aggregate, result in a Material Adverse Change.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

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