{"component": "clause", "props": {"groups": [{"samples": [{"hash": "3F3WytzOgPW", "uri": "/contracts/3F3WytzOgPW#system-setup", "label": "Commercial Agreement", "score": 32.7853831336, "published": true}, {"hash": "9NNC8AIpLjn", "uri": "/contracts/9NNC8AIpLjn#system-setup", "label": "Commercial Agreement", "score": 24.7932922656, "published": true}, {"hash": "bAvdOsf3UPR", "uri": "/contracts/bAvdOsf3UPR#system-setup", "label": "Commercial Agreement", "score": 24.6824093087, "published": true}], "size": 3, "snippet_links": [{"key": "relating-to", "type": "definition", "offset": [15, 26]}, {"key": "installation-of-products", "type": "clause", "offset": [109, 133]}, {"key": "account-manager", "type": "clause", "offset": [364, 379]}, {"key": "to-discuss", "type": "definition", "offset": [401, 411]}, {"key": "consulting-services", "type": "definition", "offset": [412, 431]}, {"key": "project-engagement", "type": "clause", "offset": [503, 521]}], "snippet": "7.2.1.1 Issues relating to current PA projects, system setup, business flow process, or the configuration or installation of products. Different products have different levels of configuration. Configuration includes the parameters, data and logic that a consultant adds to an installed product to deliver a solution. These issues will be escalated to your Inside Account Manager who will contact you to discuss Consulting Services assistance. Note: Current PA project issues are managed as part of the project engagement.", "hash": "ea7e9fa89bf00992fca4577598580d75", "id": 1}, {"samples": [{"hash": "2ANZ6hDnDeT", "uri": "/contracts/2ANZ6hDnDeT#system-setup", "label": "End User Agreement", "score": 25.7967145791, "published": true}, {"hash": "bqGzYRtp11f", "uri": "/contracts/bqGzYRtp11f#system-setup", "label": "End User Agreement", "score": 25.5379876797, "published": true}], "size": 2, "snippet_links": [], "snippet": "A schematic representation of the different gas/liquid systems are depicted in Fig.", "hash": "68c7ee4605b367970b37f516bfdb3231", "id": 2}, {"samples": [{"hash": "iLlIXLzOg68", "uri": "/contracts/iLlIXLzOg68#system-setup", "label": "License Agreement", "score": 24.7508555784, "published": true}, {"hash": "4n3dqS9fC0", "uri": "/contracts/4n3dqS9fC0#system-setup", "label": "License Agreement", "score": 24.485284052, "published": true}], "size": 2, "snippet_links": [{"key": "technical-specification", "type": "clause", "offset": [63, 86]}, {"key": "the-system", "type": "definition", "offset": [91, 101]}, {"key": "requirements-for", "type": "clause", "offset": [165, 181]}, {"key": "for-example", "type": "definition", "offset": [204, 215]}, {"key": "the-governing-body", "type": "definition", "offset": [246, 264]}, {"key": "the-process", "type": "clause", "offset": [306, 317]}, {"key": "security-requirements", "type": "clause", "offset": [407, 428]}, {"key": "to-host", "type": "definition", "offset": [458, 465]}, {"key": "creation-of-the", "type": "clause", "offset": [488, 503]}, {"key": "roles-and-responsibilities", "type": "definition", "offset": [601, 627]}, {"key": "revocation-of-such", "type": "clause", "offset": [675, 693]}], "snippet": "The tasks in system setup include designing and finalizing the technical specification for the system, defining the processes used in the system, and specifying any requirements for operating the system. For example, a blockchain governing body (the Governing Body in the present document) needs to define the process for incorporating a new consensus node operator. Or, the governing body needs to set the security requirements an entity must meet in order to host a consensus node. The creation of the present document can be viewed as a system setup task. Other setup tasks include defining system roles and responsibilities as well as the mechanism for authorization and revocation of such roles and responsibilities.", "hash": "21a801c3a7d1760e1823fbab5b1a516c", "id": 3}, {"samples": [{"hash": "65UN5GU7g2S", "uri": "/contracts/65UN5GU7g2S#system-setup", "label": "Authenticated Group Key Agreement Protocol", "score": 19.0, "published": true}], "size": 1, "snippet_links": [], "snippet": "KGC chooses a random number", "hash": "e2395e0984dbf63ad085db35cd30167f", "id": 4}, {"samples": [{"hash": "8sTrqF24yPq", "uri": "/contracts/8sTrqF24yPq#system-setup", "label": "Key Agreement Scheme", "score": 17.0, "published": true}], "size": 1, "snippet_links": [{"key": "system-parameters", "type": "clause", "offset": [283, 300]}, {"key": "cryptographic-hash", "type": "definition", "offset": [399, 417]}, {"key": "a-member", "type": "clause", "offset": [447, 455]}, {"key": "key-generation", "type": "definition", "offset": [703, 717]}, {"key": "our-scheme", "type": "definition", "offset": [801, 811]}, {"key": "figure-4", "type": "definition", "offset": [1073, 1081]}, {"key": "an-example", "type": "clause", "offset": [1088, 1098]}, {"key": "private-key", "type": "definition", "offset": [1196, 1207]}], "snippet": "Given security parameter 1k, the KGCs generates two groups G1, G2, and an admissible bilinear map e\u02c6 : G1 \u00d7 G1 \u2212\u2192 G2, where G1 denotes a cyclic additive group of prime order q and G2 is a multiplicative group of the same order. The KGCs chooses a generator P of G1 and publishes the system parameters params = {G1, G2, e\u02c6, P, H1, H2, H3}, here H1 : {0, 1}\u2217 \u2192 Z\u2217, H2 : G2 \u2192 Z\u2217, H3 : Z\u2217 \u00d7 Z\u2217 \u2192 Z\u2217 are cryptographic hash own subgroup key. Thus, when a member joins or leaves functions. the communication group, it joins or leaves only its lo- cal subgroup. As a result, only the local subgroup com- munication key needs to be refreshed and the scalability problem is greatly mitigated. We use a \u2019group\u2019 of key generation centers (KGCs) to share the overall key gener- ation and distribution workload. In our scheme the task The basic idea of our scheme is the usage of an iden- tity tree, where each node in the tree has an identity. The leaf node\u2019s identity is corresponding to a user\u2019s iden- tity and the interior node\u2019s identity is generated from it\u2019s children\u2019s identity. Figure 4 shows an example of identity tree. A node in the identity tree is also associate with a sv)\u22121P and the node N 1\u2019s private key P 1 = (Q1 +s\u03c9)\u22121P", "hash": "ee0cb270c17c9d72684bea344af0e454", "id": 5}, {"samples": [{"hash": "c5cGlF8BZxu", "uri": "/contracts/c5cGlF8BZxu#system-setup", "label": "Highway Construction Contract", "score": 19.5118877375, "published": true}], "size": 1, "snippet_links": [{"key": "the-project", "type": "clause", "offset": [42, 53]}, {"key": "the-system", "type": "definition", "offset": [159, 169]}, {"key": "traffic-signal", "type": "clause", "offset": [234, 248]}, {"key": "communication-failure", "type": "clause", "offset": [297, 318]}, {"key": "additional-events", "type": "clause", "offset": [376, 393]}, {"key": "requested-by", "type": "definition", "offset": [394, 406]}, {"key": "the-software", "type": "clause", "offset": [465, 477]}], "snippet": "Input/Modify all data that is specific to the project\u2019s intersections, with all available graphics. Create intersection diagrams to facilitate optimization of the system. Program system to report the following events, at a minimum: \u2022 Traffic Signal Flash (Conflict or Manual) \u2022 Detector Failure \u2022 Communication Failure \u2022 Cabinet Door Open (if equipped with door switch) \u2022 Any additional events requested by the municipalities or PennDOT that can be accommodated by the software", "hash": "e947f4df712baecfeec0ae2dc0a0c6fd", "id": 6}, {"samples": [{"hash": "4wjdDhl2VwA", "uri": "/contracts/4wjdDhl2VwA#system-setup", "label": "Agreement for Intelligent Transit Signal Priority Project", "score": 30.35733809, "published": true}], "size": 1, "snippet_links": [{"key": "tracking-devices", "type": "clause", "offset": [22, 38]}, {"key": "cloud-platform", "type": "clause", "offset": [129, 143]}, {"key": "bus-location", "type": "clause", "offset": [187, 199]}, {"key": "location-information", "type": "definition", "offset": [264, 284]}, {"key": "machine-learning", "type": "clause", "offset": [325, 341]}, {"key": "capable-of", "type": "definition", "offset": [349, 359]}, {"key": "traffic-signals", "type": "definition", "offset": [408, 423]}, {"key": "city-of", "type": "clause", "offset": [429, 436]}, {"key": "palo-alto", "type": "clause", "offset": [442, 451]}, {"key": "will-provide", "type": "clause", "offset": [452, 464]}, {"key": "according-to", "type": "definition", "offset": [504, 516]}, {"key": "will-work", "type": "clause", "offset": [556, 565]}, {"key": "secure-communication", "type": "clause", "offset": [588, 608]}, {"key": "figure-6", "type": "definition", "offset": [667, 675]}, {"key": "architecture-diagram", "type": "clause", "offset": [695, 715]}, {"key": "web-portal", "type": "clause", "offset": [742, 752]}, {"key": "for-epa", "type": "clause", "offset": [753, 760]}, {"key": "transit-system", "type": "definition", "offset": [812, 826]}, {"key": "one-time-password", "type": "definition", "offset": [930, 947]}, {"key": "transit-vehicle", "type": "definition", "offset": [1041, 1056]}, {"key": "performance-metrics", "type": "clause", "offset": [1130, 1149]}, {"key": "number-of", "type": "clause", "offset": [1263, 1272]}, {"key": "not-limited", "type": "clause", "offset": [1382, 1393]}, {"key": "setup-and-installation", "type": "clause", "offset": [1400, 1422]}, {"key": "network-performance", "type": "clause", "offset": [1479, 1498]}, {"key": "comprehensive-report", "type": "clause", "offset": [1569, 1589]}, {"key": "and-documentation", "type": "clause", "offset": [1646, 1663]}, {"key": "the-security", "type": "clause", "offset": [1670, 1682]}, {"key": "communication-network", "type": "clause", "offset": [1719, 1740]}, {"key": "the-project", "type": "clause", "offset": [1839, 1850]}, {"key": "next-steps", "type": "clause", "offset": [1883, 1893]}, {"key": "evaluation-elements", "type": "clause", "offset": [1927, 1946]}, {"key": "the-report", "type": "clause", "offset": [1952, 1962]}, {"key": "related-data", "type": "definition", "offset": [1977, 1989]}, {"key": "based-on", "type": "clause", "offset": [2030, 2038]}, {"key": "for-approval", "type": "definition", "offset": [2136, 2148]}, {"key": "prior-to", "type": "definition", "offset": [2149, 2157]}, {"key": "report-to", "type": "definition", "offset": [2216, 2225]}, {"key": "the-partners", "type": "clause", "offset": [2230, 2242]}, {"key": "final-project-report", "type": "clause", "offset": [2318, 2338]}, {"key": "tasks-and-deliverables", "type": "clause", "offset": [2370, 2392]}, {"key": "schedule-1", "type": "definition", "offset": [2405, 2415]}, {"key": "to-verify", "type": "definition", "offset": [2433, 2442]}, {"key": "wireless-connection", "type": "definition", "offset": [2631, 2650]}, {"key": "kick-off-meeting", "type": "definition", "offset": [2727, 2743]}, {"key": "to-acquire", "type": "definition", "offset": [2765, 2775]}, {"key": "required-number", "type": "definition", "offset": [2776, 2791]}, {"key": "the-selected", "type": "clause", "offset": [2872, 2884]}, {"key": "tracking-units", "type": "definition", "offset": [3016, 3030]}, {"key": "to-provide", "type": "definition", "offset": [3078, 3088]}, {"key": "firmware-version", "type": "definition", "offset": [3269, 3285]}, {"key": "pdf-format", "type": "definition", "offset": [3334, 3344]}, {"key": "digital-system", "type": "definition", "offset": [3620, 3634]}, {"key": "communication-connection", "type": "definition", "offset": [3702, 3726]}, {"key": "to-validate", "type": "definition", "offset": [3819, 3830]}, {"key": "field-observations", "type": "clause", "offset": [3984, 4002]}, {"key": "pilot-operation", "type": "clause", "offset": [4101, 4116]}, {"key": "live-operation", "type": "definition", "offset": [4153, 4167]}, {"key": "completion-date", "type": "clause", "offset": [4168, 4183]}, {"key": "external-communication", "type": "clause", "offset": [4301, 4323]}, {"key": "final-report", "type": "definition", "offset": [4443, 4455]}, {"key": "board-of-directors", "type": "definition", "offset": [4517, 4535]}, {"key": "project-findings", "type": "clause", "offset": [4539, 4555]}, {"key": "project-stakeholders", "type": "definition", "offset": [4627, 4647]}, {"key": "access-to-the", "type": "clause", "offset": [4673, 4686]}, {"key": "as-needed", "type": "clause", "offset": [4728, 4737]}, {"key": "advice-and-guidance", "type": "clause", "offset": [4746, 4765]}, {"key": "project-management-responsibilities", "type": "clause", "offset": [4793, 4828]}, {"key": "project-plan", "type": "clause", "offset": [4853, 4865]}, {"key": "weekly-calls", "type": "clause", "offset": [4876, 4888]}, {"key": "meeting-agendas", "type": "clause", "offset": [4955, 4970]}, {"key": "action-items", "type": "clause", "offset": [5005, 5017]}, {"key": "project-progress", "type": "clause", "offset": [5027, 5043]}, {"key": "monthly-invoices", "type": "definition", "offset": [5129, 5145]}, {"key": "progress-reports", "type": "clause", "offset": [5151, 5167]}, {"key": "work-completed", "type": "clause", "offset": [5180, 5194]}, {"key": "billing-period", "type": "definition", "offset": [5203, 5217]}, {"key": "success-criteria", "type": "clause", "offset": [5227, 5243]}, {"key": "removal-of", "type": "definition", "offset": [5509, 5519]}, {"key": "on-schedule", "type": "definition", "offset": [5534, 5545]}, {"key": "approved-by", "type": "definition", "offset": [5546, 5557]}, {"key": "to-develop", "type": "definition", "offset": [5596, 5606]}, {"key": "evaluation-criteria", "type": "definition", "offset": [5607, 5626]}, {"key": "data-for-evaluation", "type": "clause", "offset": [5667, 5686]}, {"key": "analyze-data", "type": "clause", "offset": [5719, 5731]}, {"key": "transit-routes", "type": "clause", "offset": [5787, 5801]}, {"key": "bus-stops", "type": "clause", "offset": [5806, 5815]}, {"key": "route-schedule", "type": "clause", "offset": [5829, 5843]}, {"key": "signalized-intersections", "type": "clause", "offset": [5924, 5948]}, {"key": "it-department", "type": "definition", "offset": [6000, 6013]}, {"key": "communication-requirements", "type": "definition", "offset": [6027, 6053]}, {"key": "internet-connection", "type": "definition", "offset": [6068, 6087]}, {"key": "it-guidelines", "type": "definition", "offset": [6157, 6170]}, {"key": "software-updates", "type": "definition", "offset": [6316, 6332]}, {"key": "vehicle-data", "type": "definition", "offset": [6339, 6351]}, {"key": "engineering-principles", "type": "definition", "offset": [6364, 6386]}, {"key": "direct-cost", "type": "clause", "offset": [6549, 6560]}, {"key": "participate-in", "type": "definition", "offset": [6571, 6585]}, {"key": "communication-access", "type": "clause", "offset": [6610, 6630]}, {"key": "city-network", "type": "definition", "offset": [6654, 6666]}, {"key": "working-with", "type": "definition", "offset": [6765, 6777]}, {"key": "firmware-updates", "type": "clause", "offset": [6845, 6861]}, {"key": "the-vendor", "type": "clause", "offset": [6867, 6877]}, {"key": "issues-or-concerns", "type": "clause", "offset": [6972, 6990]}, {"key": "agree-to", "type": "clause", "offset": [6993, 7001]}, {"key": "vehicle-information", "type": "clause", "offset": [7081, 7100]}, {"key": "allow-access", "type": "clause", "offset": [7136, 7148]}, {"key": "weekly-meetings", "type": "clause", "offset": [7363, 7378]}, {"key": "evaluation-metrics", "type": "clause", "offset": [7395, 7413]}, {"key": "sensor-data", "type": "definition", "offset": [7572, 7583]}, {"key": "within-the-city", "type": "definition", "offset": [7772, 7787]}, {"key": "installation-of", "type": "clause", "offset": [7816, 7831]}, {"key": "as-a-service", "type": "definition", "offset": [7883, 7895]}, {"key": "service-infrastructure", "type": "definition", "offset": [7924, 7946]}, {"key": "communications-equipment", "type": "definition", "offset": [8014, 8038]}, {"key": "secure-connection", "type": "definition", "offset": [8043, 8060]}, {"key": "to-city", "type": "definition", "offset": [8061, 8068]}, {"key": "to-host", "type": "definition", "offset": [8209, 8216]}, {"key": "status-meetings", "type": "clause", "offset": [8225, 8240]}, {"key": "project-partners", "type": "definition", "offset": [8268, 8284]}, {"key": "hardware-and-software", "type": "clause", "offset": [8323, 8344]}, {"key": "completion-of", "type": "clause", "offset": [8350, 8363]}], "snippet": "The temporary vehicle tracking devices attached to the SamTrans sub-fleet will be configured to send location updates to the LYT cloud platform. Software will collect and process transit bus location updates in real-time. Once approximately 5 weeks of transit bus location information has been saved, LYT will begin training machine learning models capable of predicting the buses arrive time to the piloted traffic signals. The City of East Palo Alto will provide LYT with traffic signal phase diagrams according to the NEMA standard. EPA and Cal-West IT will work with LYT to implement secure communication between traffic signals, Maestro, and the cloud platform. Figure 6: LYT.speed Network Architecture Diagram The LYT system includes a web portal for EPA, C/CAG and transit staff to login and view how the transit system is performing at each of the piloted traffic signals. Features include: \u2022 Secure login with additional One Time Password (OTP) at each login \u2022 View entire city, multiple cities, a particular signal or a particular transit vehicle \u2022 Troubleshoot issues in real-time at the intersection level with signal performance metrics \u2022 Review charts of daily priority calls and their impact on transit performance Summarized in the table below, a number of significant metrics will be collected during the pilot time to evaluate the level of success, including, but not limited to: \u2022 Setup and installation time \u2022 Traffic light delay \u2022 Bus speed \u2022 Traffic signal network performance Using this information SSV and LYT will provide to all stakeholders a comprehensive report which will include, but is not limited to, the analysis and documentation of: \u2022 The security & reliability of the traffic signal communication network \u2022 The before and after effects of traffic light delay on average bus speed \u2022 Report will document the project challenges \u2022 Recommendations on next steps \u2022 Potential to add other project evaluation elements into the report Other project-related data and metrics may be added to the report, based on evolving requests from stakeholders and participants. SSV shall submit a report outline to C/CAG for approval prior to drafting the report. SSV will also submit a draft project report to all the partners for comments. With comments from the stakeholders, SSV will then prepare a final project report for submittal to C/CAG. ITEM # TASKS AND DELIVERABLES ANTICIPATED SCHEDULE 1 LYT and Cal-West to verify traffic signal interconnect possible using 4G wireless modem connections. SSV and LYT to identify a temporary bus tracking unit (1st unit purchased and tested) Note: LYT has tested an all-wireless connection solution utilizing 4G cellular modems which we\u2019ll use in this pilot. Done 2 Kick off meeting Target 5/20/21 3 SSV to acquire required number of specified 4G cellular modems to support pilot. LYT and Cal-West to configure the selected traffic controllers with 4G cellular modems to enable LYT.speed\u2019s communication with EPA traffic signals. SSV to acquire temporary tracking units for SamTrans subfleet. 5/17/21 \u2013 6/04/21 4 EPA to provide LYT with intersection diagrams, NEMA phase and ring configuration, EVP controller channel configuration, phase overlap configurations, list of traffic signal controller types with firmware version numbers, and traffic signal controller manuals (PDF format). 5/17/21-6/04/21 5 SamTrans to provide LYT with GeoJSON shape files of routes, schedules, and bus stop GeoJSON file consisting of stop coordinates and IDs. 6/11/21 6 LYT to review and verify traffic agency intersection documents, SamTrans route and stop files, and complete digital system mappings on LYT's platform 6/18/21 7 LYT and SSV to coordinate the communication connection between LYT\u2019s cloud (CloudConductor) and SamTrans Buses (Tracker One devices) 6/23/21 8 LYT to validate communications with selected EPA traffic signals. 6/23/21 9 LYT to validate that transit signal priority is functioning along the corridor by supervised field observations. 6/25/21 10 Begin training Maestro AI component against live TSP data 6/28/21-7/30/21 11 Live TSP Pilot Operation in East Palo Alto 8/01/21-2/4/22 12 Live Operation Completion Date 2/4/22 ITEM # TASKS AND DELIVERABLES ANTICIPATED SCHEDULE 13 SSV and LYT will remove Maestro, provided firewall, and external communication connection from EPA signal controllers SSV will remove tracking devices from SamTrans buses 2/7/22 14 SSV will develop final Report to C/CAG. SSV will make presentation to C/CAG Committees and Board of Directors on project findings. SSV will develop slide presentation with revisions by C/CAG staff and project stakeholders. 2/25/22 \u2022 Grant limited access to the Safe and Smart Corridor to SSV and LYT \u2022 As needed provide advice and guidance to the pilot \u2022 Perform all project management responsibilities o Build, manage overall project plan o Host bi-weekly calls with C/CAG, SamTrans, East Palo Alto, and LYT o Develop bi-weekly meeting agendas, facilitate meetings and document action items o Review project progress and discuss upcoming needs and deliverables o Communicate with stakeholders o Submit monthly invoices with progress reports summarizing work completed in each billing period o Define success criteria, prepare and deliver final report \u2022 Manage sub-contractors and stakeholders \u2022 Define project and convene stakeholders, partners o C/CAG o SamTrans o City of East Palo Alto o LYT \u2022 Purchase temporary bus trackers, 4G/LTE modems; coordinate and fund installation and removal of devices based on schedule approved by SamTrans \u2022 Work with all stakeholders to develop evaluation criteria \u2022 Work with all stakeholders to collect data for evaluation \u2022 Work with all stakeholders to analyze data \u2022 Receive from SamTrans a shapefile or GeoJSON file of transit routes and bus stops; receive bus route schedule files \u2022 Digitally map bus route and bus stops into CloudConnect \u2022 Digitally Map Signalized intersections (match phase to lane) and validate \u2022 Provide EPA\u2019s IT department LYT\u2019s secure communication requirements (firewall and Internet connection and/or 4G/LTE modems) \u2022 Provide 1 Maestro to EPA configured to their IT guidelines \u2022 Confirm Maestro is successfully pulling signal status at 1 Hz from all authorized traffic signals \u2022 Confirm city connection to AWS for Maestro software updates \u2022 Use vehicle data and traffic engineering principles to configure signal controller priority settings \u2022 Grant stakeholders access to LYT\u2019s web portal \u2022 Attend bi-weekly calls with C/CAG, SamTrans, EPA, and SSV \u2022 No direct cost to EPA to participate in the pilot \u2022 Provide LYT communication access to traffic signals via city network or 4G cell modems \u2022 Provide LYT with traffic signal phase-to-lane documentation \u2022 Help facilitate working with traffic contractor Cal-West Lighting \u2022 Traffic signals may require firmware updates from the vendor \u2022 Attend Bi-weekly meeting with SamTrans, C/CAG, SSV, and LYT \u2022 Communicate to LYT any system issues or concerns \u2022 Agree to participate \u2022 No direct cost to SamTrans to participate in the pilot \u2022 Provide vehicle information and specs for temporary trackers \u2022 Allow access to buses for installation and removal of temporary trackers o Approximately 45 buses would need the trackers installed; this would include all vehicles that could be assigned to Routes 296 and 280 \u2022 Participate in weekly meetings \u2022 Contribute to evaluation metrics development \u2022 Allow for removal of trackers at end of TSP operation \u2022 Share data \u2022 Maestro, LYT\u2019s data gateway is able to consume real-time traffic light and sensor data, can communicate with traffic lights and is accessible through the East Palo Alto city network and/or supplied 4G cellular modems \u2022 SamTrans will provide sufficient buses to be dispatched within the City of East Palo Alto and allow installation of temporary GPS location devices \u2022 LYT will provide, as a service, all necessary software and service infrastructure to perform the following activities. \u2022 SSV will purchase necessary communications equipment for secure connection to City of East Palo Alto network and/or traffic controllers, up to 8 traffic lights along University Avenue and other selected intersections \u2022 SSV to host monthly status meetings among all of the principal project partners \u2022 SSV and LYT to remove all installed hardware and software upon completion of pilot", "hash": "ade7fc8c380b6b8bf9ff17001deafeb4", "id": 7}, {"samples": [{"hash": "8IVzaXqcaJs", "uri": "/contracts/8IVzaXqcaJs#system-setup", "label": "Master License Agreement (Bank of Commerce Holdings)", "score": 21.0, "published": true}], "size": 1, "snippet_links": [{"key": "to-maintain", "type": "clause", "offset": [16, 27]}, {"key": "adequate-staff", "type": "definition", "offset": [31, 45]}, {"key": "the-systems", "type": "clause", "offset": [84, 95]}, {"key": "by-customer", "type": "clause", "offset": [111, 122]}, {"key": "reasonable-requests", "type": "clause", "offset": [192, 211]}, {"key": "complete-the", "type": "clause", "offset": [237, 249]}, {"key": "will-provide", "type": "clause", "offset": [319, 331]}, {"key": "equipment-specifications", "type": "clause", "offset": [361, 385]}, {"key": "operation-of-the-software", "type": "clause", "offset": [397, 422]}, {"key": "responsible-for", "type": "clause", "offset": [436, 451]}, {"key": "in-accordance-with", "type": "definition", "offset": [503, 521]}, {"key": "use-of-the-software", "type": "clause", "offset": [676, 695]}, {"key": "access-to-the-software", "type": "clause", "offset": [714, 736]}, {"key": "by-cardinal", "type": "clause", "offset": [737, 748]}, {"key": "performance-of-maintenance-services", "type": "clause", "offset": [764, 799]}], "snippet": "Customer agrees to maintain an adequate staff of persons who are knowledgeable with the systems currently used by Customer to process data. Customer further agrees to cooperate fully with any reasonable requests of Cardinal necessary to complete the deployment and conversion in a timely and efficient manner. Cardinal will provide Customer written network and equipment specifications for proper operation of the Software. Customer is responsible for procuring and installing the appropriate equipment in accordance with Cardinal\u2019s specifications, including cabling and any configuration or telecommunications changes required for communications, to enable Customer\u2019s proper use of the Software as well as remote access to the Software by Cardinal for the remote performance of Maintenance Services.", "hash": "5e5c5cad0cd62fd72ee2e4ea55b47b40", "id": 8}, {"samples": [{"hash": "gEoCl0Z6QDR", "uri": "/contracts/gEoCl0Z6QDR#system-setup", "label": "Authentication and Key Agreement Protocol", "score": 28.9841952659, "published": true}], "size": 1, "snippet_links": [{"key": "the-security", "type": "clause", "offset": [5, 17]}, {"key": "trust-participant", "type": "clause", "offset": [44, 61]}, {"key": "cloud-server", "type": "definition", "offset": [62, 74]}, {"key": "private-key", "type": "definition", "offset": [202, 213]}, {"key": "the-system", "type": "definition", "offset": [220, 230]}, {"key": "public-key", "type": "definition", "offset": [231, 241]}, {"key": "hash-functions", "type": "clause", "offset": [275, 289]}], "snippet": "Take the security parameter \ud835\udf05 as input, the trust participant cloud server (\ud835\udc36\ud835\udc46) generates a multiplicative cyclic group \ud835\udc3a of \ud835\udc5e order with a generator \ud835\udc54. Next, \ud835\udc36\ud835\udc46 chooses a random number \ud835\udc65 as the master private key, sets the system public key \ud835\udc54\ud835\udc43\ud835\udc62\ud835\udc4f = \ud835\udc54\ud835\udc65. And then chooses five hash functions \ud835\udc5e \ud835\udc3b1 , \ud835\udc3b2 , \ud835\udc3b3 , \ud835\udc3b4 and \ud835\udc3b5 , where \ud835\udc3b1 :{0,1}\u2217 \u2192 \ud835\udc4d\u2217 , \ud835\udc3b2 :\ud835\udc3a \u2192 \ud835\udc46\ud835\udc3e\ud835\udc48\ud835\udc56 to the \ud835\udc48\ud835\udc56 through a secure channel.", "hash": "1d17584fc8c53b7acb7e3093edc3e0a1", "id": 9}, {"samples": [{"hash": "9pVOA754eRo", "uri": "/contracts/9pVOA754eRo#system-setup", "label": "Warranty Agreement", "score": 19.0, "published": true}], "size": 1, "snippet_links": [{"key": "a-unit", "type": "clause", "offset": [48, 54]}, {"key": "the-unit", "type": "clause", "offset": [80, 88]}, {"key": "current-unit", "type": "clause", "offset": [113, 125]}, {"key": "to-enter", "type": "definition", "offset": [335, 343]}, {"key": "new-unit", "type": "definition", "offset": [346, 354]}, {"key": "communications-module", "type": "definition", "offset": [448, 469]}, {"key": "return-to", "type": "definition", "offset": [889, 898]}, {"key": "system-settings", "type": "definition", "offset": [903, 918]}, {"key": "function-keys", "type": "definition", "offset": [1066, 1079]}, {"key": "change-to", "type": "definition", "offset": [1278, 1287]}], "snippet": "A. UNIT ID NUMBER\nI. Every PDR-2000 is assigned a Unit ID number whether or not the Unit ID feature is used. The current Unit ID number assigned to the unit can be found in the top left corner of the Default display. It is important that no unit be assigned number 00. The unit will not operate correctly with a Unit ID number 00.\nII. To enter a new Unit ID number, enter a two digit number from 01 to 99 (01 to 03 for units equipped with an Audio Communications module) and press F1 (OK). To exit without changing the number, press F4 (Exit).\nIII. To turn the Unit ID feature On/Off press 1 then F1 (OK) to enter the Unit ID menu again. The * will show if the Unit ID is currently On or Off. To change this setting press 1 then F1 (OK). The next menu offers the On/Off choice. Again the * shows the current setting. Press 1 for On and 2 for Off then press F1 (OK).\nIV. Press F4 (Exit) to return to the System Settings menu.\nB. PASSWORD\nI. Press 2 and F1 (OK) to enter the Password menu.\nII. The current password is displayed. Enter a new 4 digit number (do not use Function keys) for the password and press F1 (OK) to change the password. Repeat the number to confirm and press F1 (OK). Press F3 (Clr) to erase an entry on the display. Press F4 (Exit) to exit without making a change to the password.", "hash": "6781cf02352d85eeffda340cb16edc22", "id": 10}], "next_curs": "ClUST2oVc35sYXdpbnNpZGVyY29udHJhY3RzcjELEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhVzeXN0ZW0tc2V0dXAjMDAwMDAwMGEMogECZW4YACAA", "clause": {"title": "System Setup", "size": 23, "children": [["network-time-setup", "Network Time Setup"], ["general-setup", "General Setup"], ["packet-forwarding", "PACKET FORWARDING"], ["", ""], ["choose-invert-clock-on", "Choose Invert Clock On"]], "parents": [["appendices", "Appendices"], ["requirements-and-recommendations", "Requirements and Recommendations"], ["blockchain-transactions", "Blockchain Transactions"], ["governance-domains", "Governance Domains"], ["price-adjustment-criteria-and-conditions", "Price Adjustment Criteria and Conditions"]], "id": "system-setup", "related": [["system-logging", "System Logging", "System Logging"], ["system-access", "System Access", "System Access"], ["system-use", "System Use", "System Use"], ["system-upgrades", "System Upgrades", "System Upgrades"], ["setup", "Setup", "Setup"]], "related_snippets": [], "updated": "2025-07-07T12:37:48+00:00", "also_ask": [], "drafting_tip": null, "explanation": "The System Setup clause defines the responsibilities and procedures for installing, configuring, and making operational any hardware, software, or systems provided under the agreement. Typically, it outlines which party is responsible for performing the setup, the timeline for completion, and any requirements for site readiness or technical support. This clause ensures that both parties understand their roles in the initial deployment phase, minimizing delays and misunderstandings related to system implementation."}, "json": true, "cursor": ""}}