{"component": "clause", "props": {"groups": [{"snippet_links": [{"key": "in-\u2587", "type": "clause", "offset": [0, 4]}, {"key": "payment-system", "type": "clause", "offset": [40, 54]}, {"key": "permissionless-blockchain", "type": "definition", "offset": [193, 218]}, {"key": "each-participant", "type": "clause", "offset": [252, 268]}, {"key": "cryptographic-key", "type": "definition", "offset": [343, 360]}, {"key": "private-key", "type": "definition", "offset": [395, 406]}, {"key": "number-of", "type": "clause", "offset": [432, 441]}, {"key": "in-principle", "type": "definition", "offset": [569, 581]}, {"key": "the-account", "type": "clause", "offset": [592, 603]}, {"key": "of-the-sender", "type": "definition", "offset": [604, 617]}, {"key": "signature-of-the", "type": "clause", "offset": [689, 705]}, {"key": "by-participants", "type": "clause", "offset": [737, 752]}, {"key": "other-participants", "type": "clause", "offset": [770, 788]}, {"key": "of-accounts", "type": "clause", "offset": [962, 973]}, {"key": "based-on", "type": "clause", "offset": [975, 983]}, {"key": "the-transactions", "type": "clause", "offset": [984, 1000]}, {"key": "the-blockchain", "type": "clause", "offset": [1133, 1147]}], "samples": [{"hash": "cIfHM7UMnrv", "uri": "/contracts/cIfHM7UMnrv#scenario-description", "label": "End User Agreement", "score": 23.0301163587, "published": true}, {"hash": "2ww4VsMg5r2", "uri": "/contracts/2ww4VsMg5r2#scenario-description", "label": "End User Agreement", "score": 23.0301163587, "published": true}], "size": 2, "snippet": "In \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2019\u2587 work [22] a decentralized payment system is envisioned. The essence is to have a consortium of unknown participants achieve consensus [26]. To achieve this, Bitcoin uses a public permissionless blockchain, allowing anyone to participate. Each participant owns one or more Bitcoin accounts. An account is identi- fied by a public cryptographic key, and managed by the corresponding private key. Each account may hold a number of tokens, which represent a value, and can be seen as \u2018coins\u2019. Coin ownership can be transferred by transactions. A transaction, in principle, contains the account of the sender, the account of the receiver, the number of coins transferred, and the signature of the sender. Trans- actions created by participants are collected by other participants called miners. These miners independently solve a moderately-hard cryptographic puzzle. The miner that solves the puzzle first, obtains the privilege to propose a new state of accounts, based on the transactions collected. A miner proposes a new state by presenting a sequence of transactions called a block. Note that only miners may write to the blockchain. Each block holds the hash of its previous block, linking all blocks into a block-chain.", "hash": "54f18d971fb09d4c128fd2b312f411a5", "id": 1}, {"snippet_links": [{"key": "scenario-a", "type": "clause", "offset": [14, 24]}, {"key": "by-ibm", "type": "clause", "offset": [82, 88]}, {"key": "supply-chain", "type": "definition", "offset": [143, 155]}, {"key": "south-africa", "type": "definition", "offset": [208, 220]}, {"key": "to-ensure", "type": "clause", "offset": [462, 471]}, {"key": "certification-process", "type": "clause", "offset": [482, 503]}, {"key": "the-certification-authority", "type": "clause", "offset": [579, 606]}, {"key": "the-blockchain", "type": "clause", "offset": [679, 693]}, {"key": "details-of-the", "type": "clause", "offset": [709, 723]}, {"key": "issued-by", "type": "definition", "offset": [903, 912]}, {"key": "for-example", "type": "definition", "offset": [942, 953]}, {"key": "discovery-of", "type": "clause", "offset": [965, 977]}, {"key": "the-production", "type": "clause", "offset": [1021, 1035]}, {"key": "sold-to", "type": "clause", "offset": [1269, 1276]}, {"key": "parties-involved", "type": "clause", "offset": [1419, 1435]}, {"key": "validity-of-the", "type": "clause", "offset": [1468, 1483]}, {"key": "change-of-ownership", "type": "clause", "offset": [1511, 1530]}, {"key": "audit-trail", "type": "definition", "offset": [1770, 1781]}], "samples": [{"hash": "cIfHM7UMnrv", "uri": "/contracts/cIfHM7UMnrv#scenario-description", "label": "End User Agreement", "score": 23.0301163587, "published": true}, {"hash": "2ww4VsMg5r2", "uri": "/contracts/2ww4VsMg5r2#scenario-description", "label": "End User Agreement", "score": 23.0301163587, "published": true}], "size": 2, "snippet": "In this third scenario a public permissioned blockchain called Hyperledger Fabric by IBM [5] is used. This blockchain tracks certificates in a supply chain of table grapes. In this scenario [11], a farmer in South Africa produces organic grapes, and presents such a claim to a certification authority. This authority issues a certificate to the farm, allowing the farm to certify its grapes. Grapes are stored in boxes, which are identified by a unique barcode. To ensure a correct certification process, certification authorities are accred- ited by an accreditation authority. The certification authority stores the certifi- cate it receives from an accreditation authority on the blockchain. Additionally, details of the certification authority are stored on the blockchain, so that anyone may see which party certified a farm. This entire process is audited. An audi- tor may revoke the certificate issued by the certification authority, for example, after the discovery of unauthorized pesticides [31] being used in the production of the fruits. An auditor also may revoke accreditations made by the accreditation authority. Here, both revocation types are recorded on the blockchain. The grape boxes are shipped to resellers in Europe, after which the grapes are sold to supermarkets, and eventually to customers. Since it is unknown who may purchase the grapes, public verifiability is required. This allows all parties involved to query the blockchain for the validity of the organic certificate. Also, change of ownership is recorded in the blockchain, and provenance of the labeled boxes can be determined. From this description we observe that there are mul- tiple, known writers. However, these writers are not trusted, as can be observed from the cascading audit trail from farmer to auditor.", "hash": "d7ba087929dc7ee58e62415740c687ba", "id": 2}, {"snippet_links": [{"key": "cloud-computing", "type": "definition", "offset": [71, 86]}, {"key": "software-system", "type": "definition", "offset": [131, 146]}, {"key": "in-the-presence-of", "type": "definition", "offset": [185, 203]}, {"key": "based-on", "type": "clause", "offset": [351, 359]}, {"key": "provide-a", "type": "definition", "offset": [417, 426]}, {"key": "cloud-platform", "type": "clause", "offset": [482, 496]}, {"key": "the-approach", "type": "clause", "offset": [599, 611]}, {"key": "figure-11", "type": "definition", "offset": [768, 777]}, {"key": "additional-hardware", "type": "clause", "offset": [937, 956]}, {"key": "security-levels", "type": "clause", "offset": [1031, 1046]}, {"key": "with-regard-to", "type": "clause", "offset": [1048, 1062]}, {"key": "the-applications", "type": "clause", "offset": [1063, 1079]}, {"key": "other-hardware", "type": "clause", "offset": [1210, 1224]}, {"key": "user-interface", "type": "clause", "offset": [1279, 1293]}, {"key": "in-the-case", "type": "clause", "offset": [1472, 1483]}, {"key": "a-general", "type": "clause", "offset": [1607, 1616]}, {"key": "other-scenarios", "type": "clause", "offset": [1707, 1722]}, {"key": "specific-aspects", "type": "clause", "offset": [1753, 1769]}, {"key": "to-distribute", "type": "definition", "offset": [1782, 1795]}, {"key": "response-times", "type": "definition", "offset": [1853, 1867]}, {"key": "an-appropriate", "type": "clause", "offset": [2056, 2070]}, {"key": "the-requirements", "type": "clause", "offset": [2109, 2125]}, {"key": "shut-down", "type": "definition", "offset": [2626, 2635]}, {"key": "for-research", "type": "clause", "offset": [2729, 2741]}, {"key": "cloud-infrastructure", "type": "definition", "offset": [2785, 2805]}, {"key": "need-to-know", "type": "clause", "offset": [2875, 2887]}, {"key": "adverse-conditions", "type": "clause", "offset": [2979, 2997]}, {"key": "these-conditions", "type": "clause", "offset": [3170, 3186]}, {"key": "the-code", "type": "clause", "offset": [3225, 3233]}, {"key": "in-principle", "type": "definition", "offset": [3250, 3262]}, {"key": "available-to", "type": "definition", "offset": [3267, 3279]}, {"key": "data-needs", "type": "clause", "offset": [3346, 3356]}, {"key": "data-storage", "type": "definition", "offset": [3474, 3486]}, {"key": "application-level", "type": "clause", "offset": [3584, 3601]}, {"key": "app-requirements", "type": "clause", "offset": [3657, 3673]}, {"key": "the-network", "type": "clause", "offset": [3701, 3712]}, {"key": "run-an", "type": "definition", "offset": [3731, 3737]}, {"key": "the-data", "type": "clause", "offset": [3806, 3814]}, {"key": "storage-level", "type": "definition", "offset": [3815, 3828]}, {"key": "running-instance", "type": "definition", "offset": [3943, 3959]}, {"key": "user-requests", "type": "clause", "offset": [4083, 4096]}, {"key": "the-requesting", "type": "clause", "offset": [4162, 4176]}, {"key": "section-33", "type": "clause", "offset": [4302, 4313]}], "samples": [{"hash": "lfTbCQiN9aM", "uri": "/contracts/lfTbCQiN9aM#scenario-description", "label": "Grant Agreement", "score": 20.4918653312, "published": true}], "size": 1, "snippet": "\u200c The idea behind the scenario we discuss here is that of an autonomic cloud computing platform; or, in other words, a distributed software system which is able to execute applications in the presence of certain difficulties such as leaving and joining nodes, fluctuating load, and different requirements of applications to be satisfied. The cloud is based on voluntary computing and using peer-to-peer technology to provide a platform- as-a-service. We call this cloud the Science Cloud Platform (SCP) since the cloud is intended to run in an academic environment (although this is not crucial for the approach). The interaction of these three topics mentioned is discussed in the next section. An illustrative picture of how such a cloud may be composed is shown in Figure 11. In our cloud scenario, we assume the following properties of nodes: Nodes have vastly different hardware, which includes CPU speed, available memory and also additional hardware like specialized graphics processing etc. Also, a node may have different security levels. With regard to the applications, we assume that: An application has requirements on hardware, i.e. where it can and wants to be run (CPU speed, available memory, other hardware) An application is not a batch task. Rather, it has a user interface which is directly used by clients in a request-based fashion. The main scenario of the science cloud is based on what the cloud is supposed to do, i.e. run, and continue running in the case of changing nodes and load, applications. The document [ASC12] has listed three smaller scenarios which we combine here to a general scenario which describes how the cloud manages adaptation. On top of this basic scenario, other scenarios may be imagined which improve specific aspects such as how to distribute load based on particular kinds of data or how to improve response times. The basic cloud scenario focuses on application resilience, load distribution and energy saving. In this scenario, we imagine apps being deployed in the cloud which need to be started on an appropriate node based on its SLA (requirements). The requirements may include things like CPU speed of the node to be run on, memory requirements, or similar things. Once the app is started, we can imagine that problems occur, such as that a node is no longer able to execute an app due to high load (in which case it must move the app somewhere else) or due to a complete node failure (in which case another node must realize this and take over). Also, a node may realize it is not used anymore and, if this ability is available due to the use of an IaaS solution, shut down. Finally, if an app is removed by a user, it must stop executing on the cloud. Opportunities for research exist on three different levels within the cloud infrastructure. Network Level: First of all, the nodes which form the science cloud need to know one another (at least partially), be able to route between themselves, and be stable under adverse conditions (i.e. nodes that are part of the science cloud leave, or new nodes are added). This means we need network resilience (self-healing), i.e. routing still needs to work under these conditions. Data level: When an app is deployed, the code needs (at least in principle) be available to all nodes which can possibly execute it; furthermore, application data needs to be stored in such a way that resuming an application, after a node which ran it failed, is possible. We thus need data storage with data redundancy, not only of immutable data (app code) but also of mutable data (app data). Application level: Finally, apps can only run on some machines (based on app requirements) so these must be found in the network and instructed to run an app (might be multiple nodes at once). The apps store their data on the data storage level. If apps need to coordinate, they can also do that via this level (i.e. a distributed database). If a node with a running instance goes down, it must be restarted (failover) on another, fitting node. We can call this application resilience. Furthermore, user requests to apps (request/response based, as in HTTP) must be routed from the requesting node (user node) to the app node (executing node). Different levels have been addressed by the ASCENS tools and methods (see section 3.3).", "hash": "d0a589ce1b693763529ecfe938bc57dc", "id": 3}, {"snippet_links": [{"key": "combination-of-both", "type": "clause", "offset": [57, 76]}, {"key": "management-rules", "type": "clause", "offset": [105, 121]}, {"key": "the-\u2587", "type": "clause", "offset": [453, 458]}, {"key": "irrigation-systems", "type": "definition", "offset": [587, 605]}, {"key": "cancellation-of-the", "type": "clause", "offset": [804, 823]}, {"key": "reduction-of", "type": "clause", "offset": [844, 856]}, {"key": "close-to", "type": "definition", "offset": [865, 873]}, {"key": "the-proposed", "type": "clause", "offset": [1023, 1035]}, {"key": "option-contract", "type": "definition", "offset": [1036, 1051]}], "samples": [{"hash": "5RfsKWCnR", "uri": "/contracts/5RfsKWCnR#scenario-description", "label": "Innovative Option Contract", "score": 22.523613963, "published": true}], "size": 1, "snippet": "The scenarios considered in our analysis result from the combination of both the traditional and new TST management rules and different water trading alternatives, resulting in 5 different scenarios: \uf0b7 Scenario 1a: traditional TST management rule without water trading; \uf0b7 Scenario 1b: traditional TST management rule with spot water purchases in drought periods; \uf0b7 Scenario 2a: new TST management rules without water trading; 1 The high water values in the \u2587\u2587\u2587\u2587\u2587\u2587 are, in part, due to the concentration of horticultural crops and greenhouses, and also to the widespread modernization of irrigation systems (Calatrava and \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587- \u2587\u2587\u2587\u2587\u2587\u2587\u2587\u2587 2012). The agricultural sector that depends on the transferred volumes from the Tagus basin generates 1268 \u20ac million to the GDP of the \u2587\u2587\u2587\u2587\u2587\u2587 basin (PwC 2013). The cancellation of the TST would lead to a reduction of the GDP close to 7.1% (\u2587\u2587\u2587\u2587\u2587\u2587 2008). \uf0b7 Scenario 2b: new TST management rule with spot water purchases in drought periods; \uf0b7 Scenario 2c: new TST management rule with the proposed option contract (different parameterizations).", "hash": "ab2d073fe0edb6d2b3e95653893e284c", "id": 4}, {"snippet_links": [{"key": "supply-chain", "type": "definition", "offset": [16, 28]}, {"key": "main-objective", "type": "clause", "offset": [34, 48]}, {"key": "the-supplier", "type": "clause", "offset": [127, 139]}, {"key": "monitoring-parameters", "type": "clause", "offset": [173, 194]}, {"key": "related-to", "type": "clause", "offset": [195, 205]}, {"key": "conditions-of-the", "type": "clause", "offset": [210, 227]}, {"key": "in-order-to", "type": "clause", "offset": [266, 277]}, {"key": "condition-of-the", "type": "clause", "offset": [372, 388]}, {"key": "first-round", "type": "clause", "offset": [661, 672]}, {"key": "second-round", "type": "definition", "offset": [764, 776]}, {"key": "other-data-sources", "type": "clause", "offset": [834, 852]}, {"key": "traffic-information", "type": "clause", "offset": [870, 889]}, {"key": "data-acquisition-system", "type": "clause", "offset": [991, 1014]}, {"key": "and-storage", "type": "clause", "offset": [1051, 1062]}, {"key": "in-motion", "type": "clause", "offset": [1106, 1115]}, {"key": "raw-data", "type": "clause", "offset": [1194, 1202]}, {"key": "the-field", "type": "definition", "offset": [1208, 1217]}, {"key": "data-collector", "type": "definition", "offset": [1257, 1271]}, {"key": "data-processing", "type": "definition", "offset": [1317, 1332]}, {"key": "data-at-rest", "type": "clause", "offset": [1370, 1382]}, {"key": "and-information", "type": "clause", "offset": [1419, 1434]}, {"key": "data-visualization", "type": "definition", "offset": [1593, 1611]}, {"key": "output-data", "type": "clause", "offset": [1630, 1641]}, {"key": "more-details", "type": "clause", "offset": [1762, 1774]}, {"key": "the-business", "type": "clause", "offset": [1786, 1798]}, {"key": "refer-to", "type": "definition", "offset": [1832, 1840]}, {"key": "background-and-foreground", "type": "clause", "offset": [1851, 1876]}, {"key": "table-4", "type": "definition", "offset": [1946, 1953]}], "samples": [{"hash": "kHI59ggBpl5", "uri": "/contracts/kHI59ggBpl5#scenario-description", "label": "Grant Agreement", "score": 26.1345956149, "published": true}], "size": 1, "snippet": "\u200c For the Smart Supply Chain, the main objective is the improvement of the efficiency of the transportation of components from the supplier plants to FCA production plants, monitoring parameters related to the conditions of the containers during the transportation, in order to be able to react to events than can happen during the travel, that can impact on the physical condition of the components or on the expected delivering date. To reach this goal, travelling containers conditions will be monitored using an HW product prototype called \u201cOutdoor LOGistic TrackER\u201d (OLOGER from now), developed by Cefriel, that will be integrated with MIDIH platform. The first round of experiment (end by M18) will be focused on logistic data coming from these devices. The second round of Experiment (M27), will extend data sources, including other data sources like weather and traffic information, and will require to use other FIWARE lane components of the MIDIH platform. In the first round, the data acquisition system, including transmission, management and storage of IoT industrial logistic data (DiM, Data in Motion), will rely on the MindShpere/FIWARE lane. - Data Ingestion: the ingestion of raw data from the field to FIWARE /MindSphere will leverage on Data Collector modules. MIDIH foreground component MASAI. - Data Processing: the analysis of logistic data (DaR, Data at Rest) in order to produce useful insight and information about the logistic process, will leverage on MindSphere components and ad-hoc logic. - Data Persistence: Mongo DB to manage the storage and loading of data - Data Visualization: visualization of output data will be done leveraging on a Production Logistic Optimization application developed within MIDIH by Cefriel (CC6). [For more details concerning the Business Scenarios and Objectives, please refer to D5.1] The background and foreground components in this scenario (first round) are shown in the following Table 4. MongoDB T4.2, T4.3, T4.4 FIWARE DONE BACKGROUND MASAI MindSphere T4.2 FIWARE DONE3 FOREGROUND", "hash": "0566d736697779a57dd83f078a1f8146", "id": 5}, {"snippet_links": [{"key": "for-the-purpose-of", "type": "definition", "offset": [29, 47]}, {"key": "these-clauses", "type": "clause", "offset": [65, 78]}, {"key": "in-practice", "type": "clause", "offset": [90, 101]}, {"key": "single-buyer", "type": "definition", "offset": [104, 116]}, {"key": "biodiversity-net-gain", "type": "clause", "offset": [191, 212]}, {"key": "the-buyer-is", "type": "definition", "offset": [225, 237]}, {"key": "restoration-project", "type": "definition", "offset": [293, 312]}, {"key": "the-tenant", "type": "clause", "offset": [430, 440]}, {"key": "landlord-and-tenant", "type": "clause", "offset": [481, 500]}, {"key": "the-benefits", "type": "clause", "offset": [513, 525]}, {"key": "responsibilities-of-the", "type": "clause", "offset": [530, 553]}, {"key": "a-long", "type": "clause", "offset": [585, 591]}, {"key": "restoration-site", "type": "definition", "offset": [695, 711]}, {"key": "project-name", "type": "definition", "offset": [726, 738]}, {"key": "supplier-name", "type": "definition", "offset": [756, 769]}, {"key": "supplier-address", "type": "definition", "offset": [802, 818]}, {"key": "buyer-name", "type": "definition", "offset": [845, 855]}, {"key": "effective-date-of-this-agreement", "type": "definition", "offset": [872, 904]}, {"key": "termination-date-of-this-agreement", "type": "clause", "offset": [906, 940]}, {"key": "signed-by-the", "type": "clause", "offset": [956, 969]}, {"key": "duly-authorised-representative", "type": "definition", "offset": [970, 1000]}, {"key": "of-landlord", "type": "clause", "offset": [1001, 1012]}, {"key": "representative-of-tenant", "type": "clause", "offset": [1044, 1068]}, {"key": "to-enter", "type": "definition", "offset": [1089, 1097]}, {"key": "of-buyer", "type": "clause", "offset": [1331, 1339]}, {"key": "planned-works", "type": "definition", "offset": [1475, 1488]}, {"key": "description-of-the-project", "type": "clause", "offset": [1515, 1541]}, {"key": "project-plan", "type": "clause", "offset": [1544, 1556]}, {"key": "the-landlord-will", "type": "clause", "offset": [1599, 1616]}, {"key": "agricultural-land", "type": "definition", "offset": [1806, 1823]}, {"key": "approved-by", "type": "definition", "offset": [1882, 1893]}, {"key": "ecosystem-services", "type": "definition", "offset": [1964, 1982]}, {"key": "location-of-the-project", "type": "clause", "offset": [2007, 2030]}, {"key": "subject-to-the", "type": "definition", "offset": [2198, 2212]}, {"key": "satisfaction-of-the-conditions", "type": "clause", "offset": [2213, 2243]}, {"key": "in-clause", "type": "clause", "offset": [2254, 2263]}, {"key": "the-supplier-shall", "type": "clause", "offset": [2277, 2295]}, {"key": "business-days", "type": "clause", "offset": [2320, 2333]}, {"key": "the-registry", "type": "clause", "offset": [2409, 2421]}, {"key": "buyer-and-the", "type": "clause", "offset": [2451, 2464]}, {"key": "net-price", "type": "clause", "offset": [2511, 2520]}, {"key": "confirmation-letter", "type": "definition", "offset": [2613, 2632]}, {"key": "the-buyer-shall", "type": "clause", "offset": [2650, 2665]}, {"key": "agree-to", "type": "clause", "offset": [2666, 2674]}, {"key": "of-the-buyer", "type": "clause", "offset": [2688, 2700]}, {"key": "by-the-buyer", "type": "clause", "offset": [2757, 2769]}, {"key": "to-the-supplier", "type": "clause", "offset": [2770, 2785]}, {"key": "receipt-of", "type": "clause", "offset": [2821, 2831]}, {"key": "provisions-of-this-agreement", "type": "clause", "offset": [2953, 2981]}, {"key": "verification-period", "type": "definition", "offset": [3027, 3046]}, {"key": "set-out", "type": "definition", "offset": [3238, 3245]}, {"key": "competent-authority", "type": "definition", "offset": [3468, 3487]}, {"key": "separate-clauses", "type": "clause", "offset": [4219, 4235]}, {"key": "and-payment-terms", "type": "clause", "offset": [4250, 4267]}, {"key": "biodiversity-units", "type": "definition", "offset": [4328, 4346]}, {"key": "verification-requirements", "type": "clause", "offset": [4381, 4406]}, {"key": "price-and-payments", "type": "clause", "offset": [4501, 4519]}, {"key": "the-price", "type": "clause", "offset": [4589, 4598]}, {"key": "for-the-buyer", "type": "clause", "offset": [4599, 4612]}, {"key": "obligation-to-purchase", "type": "clause", "offset": [4649, 4671]}, {"key": "having-been", "type": "clause", "offset": [4714, 4725]}, {"key": "a-qualified", "type": "clause", "offset": [4739, 4750]}, {"key": "verification-body", "type": "definition", "offset": [4766, 4783]}, {"key": "woodland-carbon-code", "type": "definition", "offset": [4794, 4814]}, {"key": "banking-day", "type": "definition", "offset": [5020, 5031]}, {"key": "signature-by-the", "type": "clause", "offset": [5042, 5058]}, {"key": "title-to-the", "type": "clause", "offset": [5103, 5115]}, {"key": "from-supplier", "type": "clause", "offset": [5136, 5149]}, {"key": "to-buyer", "type": "definition", "offset": [5150, 5158]}, {"key": "due-and-payable", "type": "clause", "offset": [5172, 5187]}, {"key": "the-bank-account", "type": "clause", "offset": [5240, 5256]}, {"key": "deemed-paid", "type": "definition", "offset": [5309, 5320]}, {"key": "an-invoice", "type": "clause", "offset": [5402, 5412]}, {"key": "in-writing", "type": "clause", "offset": [5413, 5423]}, {"key": "issuance-of-the", "type": "clause", "offset": [5475, 5490]}, {"key": "deemed-accepted", "type": "definition", "offset": [5521, 5536]}, {"key": "interest-on-overdue-amounts", "type": "clause", "offset": [5538, 5565]}, {"key": "rate-of", "type": "clause", "offset": [5596, 5603]}, {"key": "per-month", "type": "clause", "offset": [5643, 5652]}, {"key": "maximum-rate-permitted-by-law", "type": "clause", "offset": [5660, 5689]}, {"key": "buyer-payments", "type": "clause", "offset": [5712, 5726]}, {"key": "accrued-interest", "type": "clause", "offset": [5757, 5773]}, {"key": "principal-amount-outstanding", "type": "clause", "offset": [5821, 5849]}, {"key": "the-delivery", "type": "clause", "offset": [5904, 5916]}, {"key": "the-interest-rate", "type": "clause", "offset": [7181, 7198]}, {"key": "audit-purpose", "type": "clause", "offset": [7262, 7275]}, {"key": "the-process", "type": "clause", "offset": [7287, 7298]}, {"key": "payment-to", "type": "clause", "offset": [7414, 7424]}, {"key": "subject-to-clauses", "type": "clause", "offset": [7437, 7455]}, {"key": "cost-responsibilities", "type": "clause", "offset": [7471, 7492]}, {"key": "for-managing", "type": "clause", "offset": [7528, 7540]}, {"key": "costs-of-the-project", "type": "clause", "offset": [7575, 7595]}, {"key": "environmental-impact-assessments", "type": "clause", "offset": [7643, 7675]}, {"key": "stakeholder-consultations", "type": "clause", "offset": [7677, 7702]}, {"key": "feasibility-studies", "type": "clause", "offset": [7726, 7745]}, {"key": "the-technical", "type": "clause", "offset": [7766, 7779]}, {"key": "feasibility-of-the-project", "type": "clause", "offset": [7801, 7827]}, {"key": "associated-with", "type": "definition", "offset": [7834, 7849]}, {"key": "development-and-implementation", "type": "clause", "offset": [7854, 7884]}, {"key": "the-restoration-plan", "type": "clause", "offset": [7888, 7908]}, {"key": "preparation-of-the", "type": "clause", "offset": [7971, 7989]}, {"key": "validation-statement", "type": "definition", "offset": [7990, 8010]}, {"key": "the-fees", "type": "clause", "offset": [8049, 8057]}, {"key": "validation-body", "type": "definition", "offset": [8065, 8080]}, {"key": "other-costs", "type": "clause", "offset": [8103, 8114]}, {"key": "maintenance-of-the", "type": "clause", "offset": [8153, 8171]}, {"key": "registry-account", "type": "definition", "offset": [8172, 8188]}, {"key": "costs-and-expenses", "type": "definition", "offset": [8410, 8428]}, {"key": "due-diligence-costs", "type": "definition", "offset": [8444, 8463]}, {"key": "all-costs", "type": "definition", "offset": [8465, 8474]}, {"key": "required-authorisations", "type": "clause", "offset": [8501, 8524]}, {"key": "licenses-or-permits", "type": "clause", "offset": [8526, 8545]}, {"key": "participate-in", "type": "definition", "offset": [8563, 8577]}, {"key": "if-applicable", "type": "clause", "offset": [8621, 8634]}, {"key": "pay-to", "type": "definition", "offset": [8998, 9004]}, {"key": "delivery-of-the", "type": "clause", "offset": [9025, 9040]}, {"key": "audit-requirements", "type": "clause", "offset": [9094, 9112]}, {"key": "the-actions", "type": "clause", "offset": [9266, 9277]}, {"key": "the-risk", "type": "definition", "offset": [9311, 9319]}, {"key": "delivery-failures", "type": "clause", "offset": [9367, 9384]}, {"key": "dispute-resolution-processes", "type": "clause", "offset": [9435, 9463]}, {"key": "notify-the", "type": "clause", "offset": [9483, 9493]}, {"key": "delivery-shortfall", "type": "clause", "offset": [9530, 9548]}, {"key": "is-likely", "type": "definition", "offset": [9565, 9574]}, {"key": "shortfall-amount", "type": "definition", "offset": [9653, 9669]}, {"key": "duration-of-the", "type": "clause", "offset": [9812, 9827]}, {"key": "all-reasonable-endeavours", "type": "definition", "offset": [9903, 9928]}, {"key": "to-ensure", "type": "clause", "offset": [9929, 9938]}, {"key": "of-the-standard", "type": "clause", "offset": [10010, 10025]}, {"key": "other-projects", "type": "definition", "offset": [10047, 10061]}, {"key": "project-developer", "type": "definition", "offset": [10092, 10109]}, {"key": "in-order-to", "type": "clause", "offset": [10110, 10121]}, {"key": "to-provide", "type": "definition", "offset": [10263, 10273]}, {"key": "the-termination", "type": "clause", "offset": [10304, 10319]}, {"key": "proportional-amount", "type": "definition", "offset": [10373, 10392]}, {"key": "related-to", "type": "clause", "offset": [10406, 10416]}, {"key": "actually-paid", "type": "definition", "offset": [10499, 10512]}, {"key": "use-commercially-reasonable-efforts", "type": "clause", "offset": [10631, 10666]}, {"key": "acting-reasonably", "type": "clause", "offset": [10746, 10763]}, {"key": "the-participating", "type": "clause", "offset": [10901, 10918]}, {"key": "for-the-avoidance-of-doubt", "type": "clause", "offset": [10985, 11011]}, {"key": "restoration-activities", "type": "definition", "offset": [11066, 11088]}, {"key": "a-portion", "type": "definition", "offset": [11148, 11157]}, {"key": "emissions-reductions", "type": "clause", "offset": [11165, 11185]}, {"key": "in-accordance-with", "type": "definition", "offset": [11293, 11311]}, {"key": "reversal-of", "type": "clause", "offset": [11413, 11424]}, {"key": "default-under-this-agreement", "type": "clause", "offset": [11562, 11590]}, {"key": "caused-by", "type": "clause", "offset": [11613, 11622]}, {"key": "wilful-misconduct", "type": "definition", "offset": [11623, 11640]}, {"key": "breach-of-this-agreement", "type": "clause", "offset": [11656, 11680]}, {"key": "prior-to-the", "type": "clause", "offset": [11929, 11941]}, {"key": "from-the-effective-date", "type": "clause", "offset": [11963, 11986]}, {"key": "applicable-proportion", "type": "definition", "offset": [12053, 12074]}, {"key": "the-buyer-will", "type": "clause", "offset": [12092, 12106]}, {"key": "right-to-proceed", "type": "clause", "offset": [12116, 12132]}, {"key": "terminate-the-agreement", "type": "clause", "offset": [12163, 12186]}, {"key": "in-this-clause", "type": "clause", "offset": [12308, 12322]}], "samples": [{"hash": "lHcJioatRUi", "uri": "/contracts/lHcJioatRUi#scenario-description", "label": "Ecosystem Services Purchase Agreement", "score": 31.4829276931, "published": true}], "size": 1, "snippet": "We have developed a scenario for the purpose of illustrating how these clauses could work in practice A single buyer is purchasing 15,000 Woodland Carbon Pending Issuance Units (PIUs) and 10 Biodiversity Net Gain Units (BUs) The buyer is purchasing these credits from a single landholding The restoration project is a woodland creation project, being designed and implemented by a tenant farmer with the consent of their landlord The tenant is the only tenant on the land, and the landlord and tenant are sharing the benefits and responsibilities of the restoration project As this is a long-term project with commitments of 30+ years, the landlord is expected to be involved in the project The restoration site is in England Project Name/Number: Landlord Supplier Name: Tenant Supplier Name: Landlord Supplier Address: Tenant Supplier Address: Buyer Name: Buyer Address: Effective Date of this Agreement: Termination Date of this Agreement: Jurisdiction: Signed by the duly authorised Representative of Landlord: Signed by the duly authorised Representative of Tenant: Name: \u2026 Click here to enter text.\u0001 Name: \u2026 Click here to enter text.\u0001 Position: \u2026 Click here to enter text.\u0001 Position: Click here to enter text.\u0001 Date: Click here to enter a date.\u0001 Date: Click here to enter a date.\u0001 Signed by the duly authorised Representative of Buyer: Name: \u2026 Click here to enter text.\u0001 Position: \u2026 Click here to enter text.\u0001 Date: Click here to enter a date.\u0001 Clause Name: Overview of planned works Purpose: Provides a clear description of the project / project plan The Supplier (Tenant) with the consent of the Landlord will conduct a woodland creation project across X hectares of land, with expected works beginning [XX Date] and ending [XX Date]. The woodland will be mixed broadleaf and will replace intensive agricultural land used for dairy farming. The project has been reviewed and approved by [XX authorities]. Comments The authorities will vary dependent on the ecosystem services being generated and the location of the project. For Biodiversity Net Gain, permission will be required from the local council. Clause Name: Sales Purpose: Provides a clear overview of the exact services being sold Subject to the satisfaction of the conditions specified in clause [4.2] below, The Supplier shall, no later than ten (10) Business Days from the date 15,000 PIUs for the Project (\u201cBuyer PIUs\u201d) are registered on the Registry, offer the Buyer PIUs to the Buyer and the Buyer commits to purchase the Buyer PIUs at a net price of GBP 150,000.00; and. The Supplier shall offer the Buyer PIUs to the Buyer by sending the Confirmation Letter to the Buyer and the Buyer shall agree to the purchase of the Buyer PIUs by returning the Confirmation Letter duly executed by the Buyer to the Supplier within ten (10) Business Days from receipt of the Confirmation Letter from the Supplier. The Confirmation Letter constitutes part of, and is subject to, the terms and provisions of this Agreement. The Buyer PIUs shall be PIUs from the first Verification Period (also known as the first vintage) whereby the Buyer PIUs are intended to be converted to WCUs 5 years after post restoration Validation of the Project. An indicative Verification schedule is set out in Schedule D. Subject to the satisfaction of the conditions specified in clause [4.2] below, The Supplier shall, no later than ten (10) Business Days from the date 10 BUs for the Project (\u201cBuyer BUs\u201d) are verified by the competent authority, offer the Buyer BUs to the Buyer and the Buyer commits to purchase the Buyer BUs at a net price of GBP 200,000.00; and. The Supplier shall offer the Buyer BUs to the Buyer by sending the Confirmation Letter to the Buyer and the Buyer shall agree to the purchase of the Buyer BUs by returning the Confirmation Letter duly executed by the Buyer to the Supplier within ten (10) Business Days from receipt of the Confirmation Letter from the Supplier. The Confirmation Letter constitutes part of, and is subject to, the terms and provisions of this Agreement. The Buyer BUs shall be BUs upon verification by the competent authority Comments For ESPAs containing stacked ecosystem services, the ecosystem services should be split into separate clauses for the sales and payment terms. This is because the processes differ for each credit type. Biodiversity Units (BUs) are not subject to the same verification requirements as WCUs, and there is not currently a Biodiversity Net Gain registry in England. Clause Name: Price and Payments Purpose: Details the timeframes that the payments will take place in The Price for the Buyer PIUs is 150,000.00 GBP. The Buyer\u2019s obligation to purchase the Buyer PIUs is subject to: the Project having been Validated by a qualified Validation and Verification Body under the Woodland Carbon Code and; the Buyer PIUs having been registered on the Registry; the Validation and Verification referred to in clause [4.2.1] above not having expired. The Buyer shall pay the Price to the Supplier by the 5th Banking Day after the signature by the Buyer of the Confirmation Letter upon which title to the PIUs shall transfer from Supplier to Buyer. Any amounts due and payable under this Agreement shall be paid in pounds (\u00a3) to the bank account specified by the Supplier. Any amounts due shall be deemed paid when they are remitted to the Supplier\u2019s bank account. Unless the Buyer disputes an invoice in writing no later than on the 5th Banking Day following the issuance of the invoice, the invoice shall be deemed accepted. Interest on overdue amounts and invoices will accrue at a rate of one and one-half percent (1.5) percent per month or the maximum rate permitted by law (whichever is lower). Buyer payments will be first applied against accrued interest (if any), and thereafter credited to cover the principal amount outstanding. If payment is overdue, the Supplier may also suspend the delivery of Buyer PIUs. The Price for the Buyer BUs is 200,000.00 GBP. The Buyer\u2019s obligation to purchase the Buyer BUs is subject to: the Project having been Validated by a qualified Validation and Verification Body under the Biodiversity Code The Buyer shall pay the Price to the Supplier by the 5th Banking Day after the signature by the Buyer of the Confirmation Letter upon which title to the PIUs shall transfer from Supplier to Buyer. Any amounts due and payable under this Agreement shall be paid in pounds (\u00a3) to the bank account specified by the Supplier. Any amounts due shall be deemed paid when they are remitted to the Supplier\u2019s bank account. Unless the Buyer disputes an invoice in writing no later than on the 5th Banking Day following the issuance of the invoice, the invoice shall be deemed accepted. Interest on overdue amounts and invoices will accrue at a rate of one and one-half percent (1.5) percent per month or the maximum rate permitted by law (whichever is lower). Buyer payments will be first applied against accrued interest (if any), and thereafter credited to cover the principal amount outstanding. If payment is overdue, the Supplier may also suspend the delivery of Buyer BUs. Comments Specific dates and percentages can change, such as the interest rate for overdue amounts and invoices Clause Name: Verification and Audit Purpose: Describes the process for which the ecosystem services being sold will be/ have been verified. Describes the conditions required for the payment to be received Subject to clauses below on Buyer cost responsibilities, the Supplier shall be responsible for managing all Validation/Verification/Audit costs of the Project under the Standard including: the collation of environmental impact assessments, stakeholder consultations and the preparation of feasibility studies necessary to define the technical, financial and legal feasibility of the Project; fees associated with the development and implementation of the Restoration Plan; any fees associated with Validation and Verification and the preparation of the Validation Statement and Verification Statements including the fees of the Validation Body; any fees, charges or other costs associated with the establishment and maintenance of the Registry Account of the Supplier, and any fees, charges or other costs imposed on the BUs, PIUs and/or WCUs until delivery except for any fees for listing the PIUs on the Registry Account. The Buyer shall be responsible for the following costs and expenses all of its own due diligence costs; all costs involved in obtaining any required authorisations, licenses or permits for the Buyer to participate in the Project or purchase the BUs/PIUs/WCUs (if applicable); and any fees, charges or other costs associated with the establishment and maintenance of the Buyer\u2019s Registry Account, and any fees, charges or other costs imposed on the PIUs and/or WCUs following delivery as well as any fees for listing the PIUs and WCUs on the Registry Account, which if paid by the Supplier, the Supplier may recharge, and the Buyer shall pay to the Supplier on the delivery of the PIUs or WCUs. Comments Exact verification/validation/audit requirements will differ dependent on the ecosystem service being sold Clause Name: Delivery Failure Purpose: Provides a definition for \u2018delivery failure\u2019. Describes the actions to take place that will mitigate the risk of delivery failure. Describes the process for delivery failures and any contingencies. Provides an explanation of dispute resolution processes The Supplier shall notify the Buyer as soon as it is aware that a Delivery Shortfall has occurred or is likely to occur, specifying in reasonable detail: The actual or anticipated Delivery Shortfall amount; The reason for the Delivery Shortfall; The steps being taken by the Supplier (if any) to address the Delivery Shortfall; and The anticipated duration of the Delivery Shortfall. If a Delivery Shortfall occurs, the Supplier shall use all reasonable endeavours to ensure the issuance of additional WCUs and/or BUs, that meet the requirements of the Standard, from the Project or other projects for which the Supplier is the project developer in order to recoup the Delivery Shortfall. This shall, if possible, take place, during the following Verification Period. Shall the Supplier not be able to provide additional WCUs and/or BUs by the Termination Date, the Supplier shall reimburse the Buyer for the proportional amount of the Price related to the Delivery Shortfall up to a maximum of [XX]% of the Price (or any lower amount actually paid by the Buyer to the Supplier for the Buyer PIUs and/or Pending BUs) (a Delivery Shortfall Refund). The Supplier shall use commercially reasonable efforts to remedy any events which have resulted in or may, in the Supplier's opinion (acting reasonably), result in underperformance in the issuance of WCUs and/or BUs, and to actively enforce its rights under the respective agreements with the participating landholders. However, such commercially reasonable efforts shall, for the avoidance of doubt, not include the Supplier itself engaging directly in restoration activities The Supplier shall, as set out in the Standard, contribute a portion of net emissions reductions over the duration of each Project to the Standard Risk Buffer (if any). The Supplier shall, when possible, in accordance with the Standard, apply to the Standard to draw upon the Standard Risk Buffer in a case of unintentional reversal of post-restoration condition category. For the avoidance of doubt, a Delivery Shortfall under this clause shall not constitute an Event of Default under this Agreement unless it is directly caused by wilful misconduct or intentional breach of this Agreement by the Supplier. For the avoidance of doubt unintentional reversal events will not lead to any liability between Buyer and Supplier or to any Delivery Shortfall Refund. If fewer than 15,000 PIUs have been registered by the date that falls 3 months prior to the date falling 3 years from the Effective Date, the Supplier shall offer the available PIUs to the Buyer for the applicable proportion of the Price and the Buyer will have the right to proceed with the purchase or agree to terminate the Agreement. Comments The exact process in the instance of delivery failure should depend on the project itself, the process set out in this clause serves only as a guideline Clause Name: Alienation", "hash": "7bc46c6d33e7fa3309ac10e43c68343b", "id": 6}, {"snippet_links": [{"key": "proposed-solution", "type": "clause", "offset": [37, 54]}, {"key": "development-of-a", "type": "clause", "offset": [62, 78]}, {"key": "to-control", "type": "definition", "offset": [86, 96]}, {"key": "quality-control", "type": "clause", "offset": [113, 128]}, {"key": "control-data", "type": "clause", "offset": [141, 153]}, {"key": "to-provide", "type": "definition", "offset": [166, 176]}, {"key": "predictive-maintenance", "type": "clause", "offset": [211, 233]}, {"key": "production-line", "type": "clause", "offset": [241, 256]}, {"key": "provide-the", "type": "clause", "offset": [301, 312]}, {"key": "in-addition-to", "type": "clause", "offset": [424, 438]}, {"key": "control-module", "type": "definition", "offset": [490, 504]}, {"key": "data-collector", "type": "definition", "offset": [639, 653]}, {"key": "data-processing", "type": "definition", "offset": [823, 838]}, {"key": "data-visualization", "type": "definition", "offset": [1052, 1070]}, {"key": "the-data", "type": "clause", "offset": [1107, 1115]}, {"key": "background-and-foreground", "type": "clause", "offset": [1121, 1146]}, {"key": "table-5", "type": "definition", "offset": [1202, 1209]}], "samples": [{"hash": "kHI59ggBpl5", "uri": "/contracts/kHI59ggBpl5#scenario-description", "label": "Grant Agreement", "score": 26.1345956149, "published": true}], "size": 1, "snippet": "\u200c In the Smart Factory scenario, the proposed solution is the development of a system to control and analyse the quality control and process control data. The aim is to provide capabilities of visualization and predictive maintenance to the production line. For this, MIDIH will develop a solution to provide the blue-collar workers and plant supervisors with the capability to visualize and prevent the factory production. In addition to this quality control, a machine and tooling status control module will be developed. Smart Factory scenario background consists of a FIWARE and APACHE lanes with several components: \u2022 Data ingestion: Data Collector to enable physical level to FIWARE (i.e. OPC UA, non OPC UA, etc.). \u2022 Data bus: Orion Context Broker to manage context information or \u2587\u2587\u2587\u2587\u2587 to integrate data streams. \u2022 Data processing: CEP Siddhi, Logstash and TensorFlow to analyse events and create complex events or to elaborate files with information when services are executed. \u2022 Data persistence: Druid to manage which data must be loaded. \u2022 Data visualization: Ruby on Rails and Nginx to present the data. The background and foreground components in this scenario are shown in the following Table 5. Orion Context Broker (OCB) T4.2, T4.3, T4.4 FIWARE DONE BACKGROUND HADOOP T4.4 APACHE DONE HIVE T4.4 APACHE DONE IDAS T4.2, T4.3, T4.4 FIWARE DONE MIDIH Connectors T4.3 FIWARE DONE FOREGROUND", "hash": "0849bc0d1db07a2686f29a92a3396624", "id": 7}, {"snippet_links": [{"key": "the-safety", "type": "clause", "offset": [0, 10]}, {"key": "civil-engineering", "type": "clause", "offset": [20, 37]}, {"key": "structural-safety", "type": "clause", "offset": [124, 141]}, {"key": "safety-and-maintenance", "type": "clause", "offset": [186, 208]}, {"key": "emergency-planning", "type": "clause", "offset": [218, 236]}, {"key": "consequences-of-failure", "type": "clause", "offset": [246, 269]}, {"key": "loss-of-life", "type": "definition", "offset": [341, 353]}, {"key": "environmental-damage", "type": "clause", "offset": [427, 447]}, {"key": "property-damage", "type": "definition", "offset": [449, 464]}, {"key": "flood-plain", "type": "clause", "offset": [476, 487]}, {"key": "economic-impact", "type": "clause", "offset": [548, 563]}, {"key": "associated-with", "type": "definition", "offset": [589, 604]}, {"key": "number-of", "type": "clause", "offset": [643, 652]}, {"key": "preventive-measures", "type": "definition", "offset": [684, 703]}, {"key": "in-advance", "type": "clause", "offset": [734, 744]}, {"key": "the-execution", "type": "clause", "offset": [787, 800]}, {"key": "corrective-actions", "type": "definition", "offset": [804, 822]}, {"key": "in-time", "type": "definition", "offset": [823, 830]}, {"key": "structural-measures", "type": "clause", "offset": [836, 855]}, {"key": "related-to", "type": "clause", "offset": [867, 877]}, {"key": "physical-safety", "type": "clause", "offset": [882, 897]}, {"key": "the-non", "type": "clause", "offset": [923, 930]}, {"key": "operation-guidelines", "type": "clause", "offset": [997, 1017]}, {"key": "emergency-action-plans", "type": "clause", "offset": [1019, 1041]}, {"key": "alarm-systems", "type": "clause", "offset": [1043, 1056]}, {"key": "insurance-coverage", "type": "clause", "offset": [1058, 1076]}, {"key": "in-order-to", "type": "clause", "offset": [1083, 1094]}, {"key": "data-acquisition", "type": "clause", "offset": [1243, 1259]}, {"key": "able-to-perform", "type": "clause", "offset": [1268, 1283]}, {"key": "monitoring-systems", "type": "clause", "offset": [1406, 1424]}, {"key": "the-fact", "type": "clause", "offset": [1526, 1534]}, {"key": "figure-1", "type": "definition", "offset": [1675, 1683]}, {"key": "the-instruments", "type": "clause", "offset": [1712, 1727]}], "samples": [{"hash": "9U9piYzS4gT", "uri": "/contracts/9U9piYzS4gT#scenario-description", "label": "Grant Agreement", "score": 21.0201772741, "published": true}], "size": 1, "snippet": "The safety of large civil engineering structures like dams requires a comprehensive set of efforts, which must consider the structural safety, the structural monitoring, the operational safety and maintenance, and the emergency planning [1]. The consequences of failure of one of these structures may be catastrophic in many areas, such as: loss of life (minimizing human casualties is the top priority of emergency planning), environmental damage, property damage (e.g., dam flood plain), damage of other infrastructures, energy power loss, socio-economic impact, among others. The risks associated with these scenarios can be mitigated by a number of structural and non- structural preventive measures, essentially to try to detect in advance any signs of abnormal behaviour, allowing the execution of corrective actions in time. The structural measures are mainly related to the physical safety of the structures, while the non-structural measures can comprise a broad set of concerns, such as operation guidelines, emergency action plans, alarm systems, insurance coverage, etc. In order to improve the structural safety of large civil engineering structures, a substantial technical effort has been made to implement or improve automatic data acquisition systems able to perform real-time monitoring and trigger automatic alarms. This paradigm creates an imminent deluge of data captured by automatic monitoring systems (sensors), along with data generated by large mathematical simulations (theoretical models). Besides the fact that these monitoring systems can save lives and protect goods, they can also prevent costly repairs and help to save money in maintenance.\nFigure 1 Schematic representation of the instruments\u2019 location", "hash": "688b327cf065e7fd5f08ca5fc48d83b6", "id": 8}, {"snippet_links": [{"key": "structured-environment", "type": "definition", "offset": [38, 60]}, {"key": "the-environment", "type": "clause", "offset": [137, 152]}, {"key": "a-team", "type": "definition", "offset": [186, 192]}, {"key": "special-area", "type": "definition", "offset": [250, 262]}, {"key": "deployment-area", "type": "definition", "offset": [274, 289]}, {"key": "in-addition", "type": "clause", "offset": [549, 560]}, {"key": "a-portion", "type": "definition", "offset": [562, 571]}, {"key": "new-areas", "type": "definition", "offset": [941, 950]}, {"key": "the-value", "type": "clause", "offset": [1068, 1077]}, {"key": "scale-factor", "type": "definition", "offset": [1100, 1112]}, {"key": "a-number", "type": "definition", "offset": [1241, 1249]}, {"key": "characterized-by", "type": "definition", "offset": [1385, 1401]}, {"key": "over-time", "type": "clause", "offset": [1496, 1505]}, {"key": "number-of", "type": "clause", "offset": [1867, 1876]}, {"key": "must-take-into-account", "type": "definition", "offset": [1966, 1988]}, {"key": "energy-level", "type": "clause", "offset": [2044, 2056]}, {"key": "according-to", "type": "definition", "offset": [2067, 2079]}, {"key": "table-1", "type": "clause", "offset": [2197, 2204]}, {"key": "figure-1", "type": "definition", "offset": [2306, 2314]}, {"key": "the-picture", "type": "definition", "offset": [2447, 2458]}], "samples": [{"hash": "lfTbCQiN9aM", "uri": "/contracts/lfTbCQiN9aM#scenario-description", "label": "Grant Agreement", "score": 20.4918653312, "published": true}], "size": 1, "snippet": "\u200c The robotics scenario consists of a structured environment of width W and depth D, initially un- known to the robots. The structure of the environment mimics that of a building floor. A team of R robots called rescuers (Fig. 1(a)) is deployed in a special area called the deployment area within the environment. The size of the deployment area is always assumed sufficient to house all the robots. We imagine that some kind of disaster has happened, and the environment is occasionally ob- structed by debris (Fig. 1(b)) that the robots can move. In addition, a portion of the environment is dangerous for robot navigation due to the presence of radiation (Fig. 1(c)). We assume that prolonged exposition to radiation damages the robots. Short-term exposition increases a robot\u2019s sensory noise. Long-term damage eventually disables the robot completely. To avoid damage, the robots can use debris to build a protective wall, thus reaching new areas of the environment. Damage is simulated through a function dr(t) that increases with exposition time t from 1 to 10. The value of dr(t) is used as a scale factor for the natural sensory noise of a robot, until it reaches the value 10, which corresponds to a disabled robot. We imagine that a number V of victims (Fig. 1(d)) are trapped in the environment and must be rescued by the robots. Each victim is suffering a different injury characterized by a gravity Gv. The health hv(t; Gv) of each victim, initially in the range (0,1], deteriorates over time. When hv = 0, the victim is dead. The robots must calculate a suitable rescuing behavior that maximizes the number S of victims rescued. This can be seen as a problem of distributed consensus. A victim is considered rescued when it is deposited in the deployment area alive. In addition, each victim has a different mass Mv. The higher the mass, the larger the number of robots required to carry it to the deployment area. To perform its activities, a robot r must take into account that it has limited energy er. As the robot works, its energy level decreases according to a function er(t). If the energy reaches 0, the robot A reference of all the symbols and their meaning is reported in Table 1.\n2.4.1 and 2.4.2, we sketch two possible variants that focus on different behaviors.\n(a) (b) (c) (d) Figure 1: (a) A rescuer robot. (b) Debris is simulated with grippable cylinders. (c) Radiation is simulated with lights (the yellow blobs in the picture). (d) Victims are simulated with robots.", "hash": "06e1671834483466316538d2318eee6e", "id": 9}, {"snippet_links": [{"key": "technical-approach", "type": "definition", "offset": [6, 24]}, {"key": "reference-architecture", "type": "clause", "offset": [88, 110]}, {"key": "software-architecture", "type": "clause", "offset": [123, 144]}, {"key": "identity-provider", "type": "definition", "offset": [306, 323]}, {"key": "in-detail", "type": "clause", "offset": [353, 362]}, {"key": "for-the-customer", "type": "clause", "offset": [434, 450]}, {"key": "distribution-network", "type": "definition", "offset": [456, 476]}, {"key": "a-distribution", "type": "clause", "offset": [547, 561]}, {"key": "the-manufacturer", "type": "definition", "offset": [591, 607]}, {"key": "service-application", "type": "clause", "offset": [629, 648]}, {"key": "supply-chain", "type": "definition", "offset": [679, 691]}, {"key": "logistics-service-provider", "type": "definition", "offset": [748, 774]}, {"key": "transport-service", "type": "clause", "offset": [785, 802]}], "samples": [{"hash": "kHI59ggBpl5", "uri": "/contracts/kHI59ggBpl5#scenario-description", "label": "Grant Agreement", "score": 26.1345956149, "published": true}], "size": 1, "snippet": "\u200c The technical approach consists of the creation of a data space as defined in the IDS Reference Architecture Model4. The software architecture represents the reference architecture of the Industrial Data Space. The elements Connector and Broker from the Industrial Data Space are used as well as the IDS Identity Provider (mandatory and not described in detail as this is a standard component in the Reference Architecture Model5). For the customer, the distribution network organizes itself via apps in the Industrial Data Space. Within MIDIH, a distribution planning app is installed in the manufacturer's IDS connector. The Service Application transferring data through the Supply Chain partners, in this case between the manufacturer and the logistics service provider resp. the transport service provider. The scenario is described in detail in D.5.1 \u2587\u2587\u2587\u2587\u2587 T4.4 APACHE DONE BACKGROUND SPARK T4.4 APACHE DONE", "hash": "0ddd4b7fbcf6842bea1d78ca71dacb37", "id": 10}], "next_curs": "Cl0SV2oVc35sYXdpbnNpZGVyY29udHJhY3RzcjkLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2Ih1zY2VuYXJpby1kZXNjcmlwdGlvbiMwMDAwMDAwYQyiAQJlbhgAIAA=", "clause": {"parents": [["smart-supply-chain-integrated-architecture", "Smart Supply Chain Integrated Architecture"], ["smart-supply-chain-scenario-in-fca", "Smart Supply Chain Scenario in Fca"], ["application-for-inbound-logistics-tracking", "Application for Inbound Logistics Tracking"], ["smart-factory-scenario-in-neco", "Smart Factory Scenario in Neco"], ["application-for-smart-production-analysis", "Application for Smart Production Analysis"]], "size": 8, "title": "Scenario Description", "children": [["tagus-\u2587\u2587\u2587\u2587\u2587\u2587-transfer-management-rules", "Tagus-\u2587\u2587\u2587\u2587\u2587\u2587 Transfer management rules"]], "id": "scenario-description", "related": [["system-description", "System Description", "System Description"], ["task-description", "Task Description", "Task Description"], ["work-description", "Work Description", "Work Description"], ["project-description", "Project Description", "Project Description"], ["item-description", "ITEM DESCRIPTION", "ITEM DESCRIPTION"]], "related_snippets": [], "updated": "2025-07-07T12:36:13+00:00", "also_ask": [], "drafting_tip": null, "explanation": "The \"Scenario Description\" clause defines the specific circumstances or context under which the agreement or a particular provision applies. It typically outlines the relevant facts, background, or hypothetical situations that trigger the application of the contract terms. For example, it may describe a business transaction, a service to be provided, or a set of conditions that must be met. By clearly establishing the scenario, this clause ensures that all parties have a shared understanding of when and how the agreement's provisions are activated, thereby reducing ambiguity and potential disputes."}, "json": true, "cursor": ""}}