{"component": "clause", "props": {"groups": [{"samples": [{"hash": "ahigoPfU3hr", "uri": "/contracts/ahigoPfU3hr#process-management", "label": "Network of Excellence Agreement", "score": 21.0, "published": true}, {"hash": "8q0Y9CEh15c", "uri": "/contracts/8q0Y9CEh15c#process-management", "label": "Network of Excellence Agreement", "score": 21.0, "published": true}, {"hash": "4xh9pgpcpJa", "uri": "/contracts/4xh9pgpcpJa#process-management", "label": "Network of Excellence Agreement", "score": 21.0, "published": true}], "snippet_links": [{"key": "the-process", "type": "clause", "offset": [0, 11]}, {"key": "describe-in-detail", "type": "definition", "offset": [28, 46]}, {"key": "a-formal", "type": "clause", "offset": [73, 81]}, {"key": "figure-2", "type": "clause", "offset": [94, 102]}, {"key": "the-organisation", "type": "clause", "offset": [172, 188]}, {"key": "the-services", "type": "clause", "offset": [218, 230]}, {"key": "based-on", "type": "definition", "offset": [296, 304]}, {"key": "workflow-management", "type": "definition", "offset": [305, 324]}, {"key": "common-use", "type": "definition", "offset": [378, 388]}, {"key": "research-program", "type": "clause", "offset": [429, 445]}, {"key": "staff-mobility", "type": "clause", "offset": [492, 506]}, {"key": "knowledge-dissemination", "type": "clause", "offset": [510, 533]}, {"key": "other-processes", "type": "clause", "offset": [535, 550]}, {"key": "related-to", "type": "clause", "offset": [551, 561]}, {"key": "the-\u2587", "type": "clause", "offset": [586, 591]}, {"key": "budget-allocation", "type": "clause", "offset": [612, 629]}, {"key": "committee-selection", "type": "clause", "offset": [641, 660]}, {"key": "private-sector", "type": "clause", "offset": [708, 722]}], "snippet": "The process management must describe in detail how operations operate in a formal manner (see Figure 2). This formalisation is generally conducted through a description of the organisation and its processes supporting the services to their stakeholders. EuroFIR will include such process support based on workflow management. The main processes assisting the integration are: \u2022 Common use of infrastructure; \u2022 Joint execution of research program; \u2022 Co-programming; \u2022 Resources relocations; \u2022 Staff mobility; \u2022 Knowledge dissemination. Other processes related to the internal working of the \u2587\u2587\u2587 will be included: budget allocation, auditing, committee selection and various communications to the researchers, private sector, professions, consumer, policy makers and other NGOs.", "size": 4, "hash": "5c63d52f12c988bf17b9c0a11dd54428", "id": 1}, {"samples": [{"hash": "lHImY6jnzne", "uri": "/contracts/lHImY6jnzne#process-management", "label": "Master Services Agreement (Bionano Genomics, Inc.)", "score": 35.5982208252, "published": true}, {"hash": "5AqZ31zjdCI", "uri": "/contracts/5AqZ31zjdCI#process-management", "label": "Master Services Agreement (BioNano Genomics, Inc)", "score": 29.4873371124, "published": true}, {"hash": "fQGsAFAj7kU", "uri": "/contracts/fQGsAFAj7kU#process-management", "label": "Master Services Agreement (BioNano Genomics, Inc)", "score": 29.3641338348, "published": true}], "snippet_links": [{"key": "exercise-day", "type": "definition", "offset": [15, 27]}, {"key": "managerial-authority", "type": "clause", "offset": [35, 55]}, {"key": "wafer-fabrication", "type": "clause", "offset": [79, 96]}, {"key": "allocation-of-activities", "type": "clause", "offset": [155, 179]}, {"key": "the-operation", "type": "clause", "offset": [199, 212]}, {"key": "development-and-planning", "type": "clause", "offset": [214, 238]}, {"key": "provisions-of-this-agreement", "type": "clause", "offset": [272, 300]}, {"key": "customer-shall", "type": "clause", "offset": [306, 320]}, {"key": "employees-with", "type": "clause", "offset": [329, 343]}, {"key": "authority-to", "type": "definition", "offset": [360, 372]}, {"key": "an-operating", "type": "clause", "offset": [373, 385]}, {"key": "committee-shall", "type": "definition", "offset": [453, 468]}, {"key": "in-person", "type": "clause", "offset": [474, 483]}, {"key": "time-to-review", "type": "clause", "offset": [546, 560]}, {"key": "operational-matters", "type": "definition", "offset": [600, 619]}, {"key": "changes-to-the", "type": "definition", "offset": [631, 645]}, {"key": "operating-procedures", "type": "definition", "offset": [651, 671]}, {"key": "to-customer", "type": "clause", "offset": [683, 694]}, {"key": "provided-however", "type": "clause", "offset": [696, 712]}, {"key": "ultimate-control", "type": "clause", "offset": [737, 753]}, {"key": "attempt-to-resolve", "type": "definition", "offset": [843, 861]}, {"key": "good-faith-negotiations", "type": "definition", "offset": [865, 888]}, {"key": "with-respect-to", "type": "clause", "offset": [923, 938]}, {"key": "other-disputes", "type": "definition", "offset": [956, 970]}, {"key": "arising-under-this-agreement", "type": "definition", "offset": [971, 999]}, {"key": "except-as-specifically", "type": "clause", "offset": [1001, 1023]}, {"key": "operations-meeting", "type": "clause", "offset": [1074, 1092]}, {"key": "daily-activities", "type": "clause", "offset": [1106, 1122]}, {"key": "on-the-line", "type": "definition", "offset": [1123, 1134]}, {"key": "customer-representative", "type": "definition", "offset": [1174, 1197]}, {"key": "to-attend", "type": "clause", "offset": [1210, 1219]}, {"key": "prior-written-approval", "type": "definition", "offset": [1275, 1297]}, {"key": "a-list", "type": "definition", "offset": [1342, 1348]}, {"key": "proposed-operations", "type": "clause", "offset": [1356, 1375]}, {"key": "all-equipment", "type": "clause", "offset": [1387, 1400]}, {"key": "failure-to", "type": "clause", "offset": [1422, 1432]}, {"key": "adhere-to", "type": "clause", "offset": [1433, 1442]}, {"key": "approved-list", "type": "clause", "offset": [1447, 1460]}, {"key": "grounds-for-termination", "type": "clause", "offset": [1479, 1502]}, {"key": "section-123", "type": "clause", "offset": [1518, 1530]}, {"key": "master-services-agreement", "type": "clause", "offset": [1538, 1563]}, {"key": "no-liability", "type": "definition", "offset": [1585, 1597]}, {"key": "responsible-for", "type": "clause", "offset": [1605, 1620]}, {"key": "arising-out-of", "type": "definition", "offset": [1642, 1656]}, {"key": "related-to", "type": "clause", "offset": [1660, 1670]}, {"key": "the-work", "type": "definition", "offset": [1671, 1679]}, {"key": "customer-personnel", "type": "clause", "offset": [1683, 1701]}, {"key": "not-limited", "type": "clause", "offset": [1716, 1727]}, {"key": "by-customer", "type": "clause", "offset": [1764, 1775]}], "snippet": "3.1 SVTC shall exercise day-to-day managerial authority over the semiconductor wafer fabrication facilities, referred to as the \u201cLine,\u201d including over the allocation of Activities and all aspects of the operation, development and planning of the Line, consistent with the provisions of this Agreement.\n3.2 Customer shall appoint employees with decision-making authority to an operating committee (\u201cOperating Committee\u201d) to work with SVTC. The Operating Committee shall meet in person or telephonically once every [\u2026***\u2026] at a regularly scheduled time to review operational results and approve future operational matters, including changes to the Line operating procedures applicable to Customer; provided however, that SVTC shall retain ultimate control over any changes to the Line and its operating procedures. The Operating Committee shall attempt to resolve by good faith negotiations any operating disputes that arise with respect to the Line, or any other disputes arising under this Agreement, except as specifically set forth herein.\n3.3 SVTC will hold a daily Line operations meeting in which the daily Activities on the Line are reviewed, discussed and planned; a Customer representative is expected to attend all operations meetings.\n3.4 Customer shall submit for prior written approval to the Operating Committee or its designee, a list of all proposed operations, including all equipment intended to be used. Failure to adhere to the approved list may be considered grounds for termination as provided in Section 12.3 of the Master Services Agreement.\n3.5 SVTC shall have no liability nor be responsible for any costs or damages arising out of or related to the work of Customer Personnel including but not limited to results other than those desired by Customer in the wafers processed on the Line solely by Customer Personnel.", "size": 3, "hash": "a7a207febe95a7e211323179a498ed96", "id": 2}, {"samples": [{"hash": "ahigoPfU3hr", "uri": "/contracts/ahigoPfU3hr#process-management", "label": "Network of Excellence Agreement", "score": 21.0, "published": true}, {"hash": "4xh9pgpcpJa", "uri": "/contracts/4xh9pgpcpJa#process-management", "label": "Network of Excellence Agreement", "score": 21.0, "published": true}], "snippet_links": [{"key": "the-process", "type": "clause", "offset": [0, 11]}, {"key": "describe-in-detail", "type": "definition", "offset": [28, 46]}, {"key": "a-formal", "type": "clause", "offset": [73, 81]}, {"key": "figure-2", "type": "clause", "offset": [94, 102]}, {"key": "the-organisation", "type": "clause", "offset": [172, 188]}, {"key": "the-services", "type": "clause", "offset": [218, 230]}, {"key": "based-on", "type": "definition", "offset": [296, 304]}, {"key": "workflow-management", "type": "definition", "offset": [305, 324]}, {"key": "common-use", "type": "definition", "offset": [378, 388]}, {"key": "research-program", "type": "clause", "offset": [429, 445]}, {"key": "staff-mobility", "type": "clause", "offset": [492, 506]}, {"key": "knowledge-dissemination", "type": "clause", "offset": [510, 533]}, {"key": "other-processes", "type": "clause", "offset": [535, 550]}, {"key": "related-to", "type": "clause", "offset": [551, 561]}, {"key": "the-\u2587", "type": "clause", "offset": [586, 591]}, {"key": "budget-allocation", "type": "clause", "offset": [612, 629]}, {"key": "committee-selection", "type": "clause", "offset": [641, 660]}, {"key": "private-sector", "type": "clause", "offset": [708, 722]}, {"key": "communication-management", "type": "clause", "offset": [779, 803]}, {"key": "software-platform", "type": "definition", "offset": [868, 885]}, {"key": "the-network", "type": "clause", "offset": [891, 902]}, {"key": "key-activity", "type": "definition", "offset": [908, 920]}, {"key": "commencement-of-the-project", "type": "definition", "offset": [975, 1002]}, {"key": "operating-system", "type": "definition", "offset": [1015, 1031]}, {"key": "the-database", "type": "definition", "offset": [1033, 1045]}, {"key": "communication-system", "type": "definition", "offset": [1054, 1074]}, {"key": "system-architecture", "type": "clause", "offset": [1119, 1138]}, {"key": "underpinned-by", "type": "definition", "offset": [1156, 1170]}, {"key": "community-software", "type": "definition", "offset": [1213, 1231]}, {"key": "provide-a", "type": "definition", "offset": [1261, 1270]}, {"key": "the-partners", "type": "definition", "offset": [1391, 1403]}, {"key": "the-software", "type": "definition", "offset": [1429, 1441]}, {"key": "communication-networks", "type": "clause", "offset": [1488, 1510]}, {"key": "networking-activities", "type": "clause", "offset": [1641, 1662]}, {"key": "external-to-the", "type": "definition", "offset": [1700, 1715]}, {"key": "in-addition", "type": "clause", "offset": [1725, 1736]}, {"key": "the-researcher", "type": "clause", "offset": [1834, 1848]}, {"key": "research-and-information", "type": "clause", "offset": [1986, 2010]}, {"key": "site-content", "type": "clause", "offset": [2136, 2148]}, {"key": "generic-applications", "type": "clause", "offset": [2201, 2221]}, {"key": "knowledge-management", "type": "definition", "offset": [2223, 2243]}, {"key": "document-management", "type": "definition", "offset": [2250, 2269]}, {"key": "reports-and-publications", "type": "clause", "offset": [2320, 2344]}, {"key": "inventory-management", "type": "definition", "offset": [2383, 2403]}, {"key": "database-management", "type": "definition", "offset": [2435, 2454]}, {"key": "other-tools", "type": "clause", "offset": [2463, 2474]}, {"key": "the-provision-of-services", "type": "clause", "offset": [2586, 2611]}, {"key": "wide-range", "type": "definition", "offset": [2617, 2627]}, {"key": "the-proposed", "type": "clause", "offset": [2702, 2714]}, {"key": "accuracy-of-the-information", "type": "clause", "offset": [2960, 2987]}, {"key": "general-public", "type": "definition", "offset": [3009, 3023]}, {"key": "access-to-information", "type": "clause", "offset": [3034, 3055]}, {"key": "development-of", "type": "clause", "offset": [3111, 3125]}, {"key": "the-documents", "type": "clause", "offset": [3170, 3183]}, {"key": "quality-criteria", "type": "definition", "offset": [3198, 3214]}, {"key": "health-related", "type": "clause", "offset": [3219, 3233]}, {"key": "issued-by", "type": "definition", "offset": [3244, 3253]}, {"key": "the-european-commission", "type": "clause", "offset": [3254, 3277]}, {"key": "research-community", "type": "definition", "offset": [3306, 3324]}, {"key": "management-systems", "type": "definition", "offset": [3440, 3458]}, {"key": "restricted-access", "type": "clause", "offset": [3540, 3557]}, {"key": "the-system", "type": "clause", "offset": [3575, 3585]}, {"key": "a-limited", "type": "clause", "offset": [3672, 3681]}, {"key": "selection-of", "type": "definition", "offset": [3682, 3694]}, {"key": "training-procedures", "type": "clause", "offset": [3912, 3931]}, {"key": "academic-community", "type": "definition", "offset": [4004, 4022]}, {"key": "and-health", "type": "clause", "offset": [4034, 4044]}, {"key": "regulatory-authorities", "type": "definition", "offset": [4093, 4115]}, {"key": "video-conferencing-system", "type": "definition", "offset": [4136, 4161]}, {"key": "establishment-of", "type": "clause", "offset": [4228, 4244]}, {"key": "an-open", "type": "clause", "offset": [4245, 4252]}, {"key": "in-order-to-ensure", "type": "clause", "offset": [4409, 4427]}, {"key": "training-activities", "type": "clause", "offset": [4500, 4519]}, {"key": "the-facilities", "type": "clause", "offset": [4624, 4638]}, {"key": "six-months", "type": "definition", "offset": [4719, 4729]}, {"key": "common-features", "type": "clause", "offset": [4764, 4779]}, {"key": "new-research", "type": "clause", "offset": [5053, 5065]}, {"key": "additional-funding", "type": "definition", "offset": [5172, 5190]}, {"key": "research-work", "type": "definition", "offset": [5213, 5226]}, {"key": "additional-income", "type": "clause", "offset": [5303, 5320]}, {"key": "core-training", "type": "clause", "offset": [5378, 5391]}, {"key": "cooperation-with", "type": "clause", "offset": [5440, 5456]}, {"key": "key-stakeholders", "type": "clause", "offset": [5531, 5547]}, {"key": "outside-europe", "type": "definition", "offset": [5592, 5606]}, {"key": "the-design", "type": "clause", "offset": [5608, 5618]}, {"key": "periodic-reports", "type": "clause", "offset": [5859, 5875]}, {"key": "each-year", "type": "definition", "offset": [5930, 5939]}, {"key": "to-assist", "type": "clause", "offset": [6060, 6069]}, {"key": "the-commission", "type": "clause", "offset": [6162, 6176]}, {"key": "to-establish", "type": "clause", "offset": [6200, 6212]}, {"key": "best-practice", "type": "definition", "offset": [6213, 6226]}, {"key": "following-the", "type": "definition", "offset": [6228, 6241]}, {"key": "new-partners", "type": "clause", "offset": [6257, 6269]}, {"key": "year-1", "type": "clause", "offset": [6273, 6279]}, {"key": "see-appendix", "type": "clause", "offset": [6378, 6390]}, {"key": "agreement-for", "type": "clause", "offset": [6410, 6423]}, {"key": "further-details", "type": "clause", "offset": [6424, 6439]}, {"key": "will-work", "type": "clause", "offset": [6452, 6461]}, {"key": "information-flow", "type": "clause", "offset": [6597, 6613]}, {"key": "joint-research-activities", "type": "clause", "offset": [6618, 6643]}, {"key": "duration-and", "type": "clause", "offset": [6710, 6722]}], "snippet": "The process management must describe in detail how operations operate in a formal manner (see Figure 2). This formalisation is generally conducted through a description of the organisation and its processes supporting the services to their stakeholders. EuroFIR will include such process support based on workflow management. The main processes assisting the integration are: \u2022 Common use of infrastructure; \u2022 Joint execution of research program; \u2022 Co-programming; \u2022 Resources relocations; \u2022 Staff mobility; \u2022 Knowledge dissemination. Other processes related to the internal working of the \u2587\u2587\u2587 will be included: budget allocation, auditing, committee selection and various communications to the researchers, private sector, professions, consumer, policy makers and other NGOs. \u2022 Communication management and internet technology The integration of the IT communication software platform into the network is a key activity that will take place within the first 3 months of the commencement of the project. Around the operating system, the database and the communication system are the essential components of the EuroFIR system architecture. EuroFIR will be underpinned by a robust and well-established web-based e-community software platform. This software will provide a common shared platform, which will facilitate the co-ordination and implementation of the programming and adaptation of the partners\u2019 activities. Critically, the software will reinforce the electronic information and communication networks to support interactive working between the teams involved and in the spreading of excellence via dissemination, communication and networking activities both within the network and to teams external to the network. In addition, the software will support the mobility of researchers within the network by alerting members of the researcher positions open within the network organisations. Furthermore, it will enable members to connect with existing relevant pan-European food research and information networks. An online newsletter will be included, being updated regularly (monthly) to highlight additions and changes to the site content. The network\u2019s IT operating system will support the generic applications: Knowledge Management (KM), Document Management (including publications and methods repositories, reports and publications; DM); Centres Skills & Infrastructure Inventory Management (CSM) and the Food Composition Database Management (FCDM). Other tools such as video conferencing and e-learning applications will also be available. The network will be central for the provision of services to a wide range of users and therefore needs interconnection with other FP6 IPs and NOEs. The proposed integrating activities will allow for the reinforcement of electronic information and communication networks to support interactive working between the various centres and teams and this will be carefully monitored to assess confidentiality and accuracy of the information. They include: o The general public will have access to information about EuroFIR through a website (\u2587\u2587\u2587.\u2587\u2587\u2587\u2587\u2587\u2587\u2587.\u2587\u2587\u2587). The development of this website will follow recommendations of the documents \u201cEurope 2002: Quality Criteria for Health related Websites\u201d issued by the European Commission COM (2002) 667 final. o The research community constituted by all the EuroFIR members will have access to their data and applications; Knowledge, Document & Data Management Systems; the Nutrient and Bioactive Databank, and other integrating activities. However, restricted access to some parts of the system will be foreseen in order to protect IPR. This will be accessible with an Intranet. o A limited selection of organisations beyond the EuroFIR members (policy makers, industry, professionals and other NGOs) will have access to EuroFIR knowledge and applications via an Extranet. o E-learning tools will provide educational and training procedures for disseminating knowledge both within the EuroFIR \u2587\u2587\u2587 and towards the academic community (e.g. food and health scientists), agro-food industry, retail sector, regulatory authorities, and consumers. o A video conferencing system will be established through the EuroFIR Co-ordinating Centre. The establishment of an open platform for the JPA is essential for the network in order to achieve the integration of the research goals. The CO and SMB will oversee the four platforms in order to ensure cross-platform, and within-platform, coordination of joint research and training activities and co-programming of projects. The co-ordinator and the WP-Ls will closely in order to ensure that all the facilities of the network are effectively used and these activities will be reviewed every six months. The facilities will include some common features of the network including common databases; skills inventory; publications, reports and newsletters; methods repositories and the nutrient and bioactive compound databank systems. They will also provide search facilities and network knowledge in order to identify potential new research partners for all the network platforms. In addition, an important aspect of this activity will be to seek additional funding initiatives for joint research work linked to the JPA. This will be reviewed every 6 months and targets set for additional income for the various research activities. The updating of the core training directory will be undertaken regularly in close cooperation with WP3.1 and work closely with RA2.1 to identify and build partnerships with key stakeholders and international compilers both within and outside Europe. The design of an information and communication system where the specific indicators given below (see pages 76-77) can be captured, stored and monitored will be undertaken within this activity. The information will be collected annually as part of the Periodic Reports and used to produce an overall integration status for each year. It will be possible to identify those areas and partners that need to integrate more, and strategies will be developed to assist this process. Close collaboration with other NoEs (especially NuGO, CASCADE & Harmony), and the Commission, is envisaged in order to establish best practice. Following the first call for new partners in Year 1, future annual calls for new national compilers from non-EuroFIR countries may also be organised (see Appendix A.4 and Consortium Agreement for further details). This task will work closely with RA2.1 & 2.2 to identify key stakeholders and compilers from both within and outside Europe. IA1.7: Integrating knowledge, information flow and joint research activities Responsible: IFR, DTU/DFI, UHEL, AUA, UCC, UiO, BNF, UL & Baigent Duration and Tasks: M18-60", "size": 3, "hash": "ce5232541fae3086a469f424825cc73c", "id": 3}, {"samples": [{"hash": "5MRlAJ41b30", "uri": "/contracts/5MRlAJ41b30#process-management", "label": "Construction Manager Agreement", "score": 26.2632522583, "published": true}, {"hash": "bVCKrMcHMm", "uri": "/contracts/bVCKrMcHMm#process-management", "label": "Construction Manager Agreement", "score": 26.2440910339, "published": true}], "snippet_links": [{"key": "will-work", "type": "clause", "offset": [36, 45]}, {"key": "design-team", "type": "definition", "offset": [55, 66]}, {"key": "site-visits", "type": "definition", "offset": [120, 131]}, {"key": "trade-contractor", "type": "clause", "offset": [166, 182]}, {"key": "receipt-of-bids", "type": "clause", "offset": [194, 209]}, {"key": "to-verify", "type": "definition", "offset": [240, 249]}, {"key": "bid-analysis", "type": "clause", "offset": [332, 344]}, {"key": "the-architect", "type": "clause", "offset": [427, 440]}, {"key": "prior-to", "type": "definition", "offset": [441, 449]}, {"key": "award-of-trade-contracts", "type": "clause", "offset": [450, 474]}, {"key": "purchase-orders", "type": "clause", "offset": [478, 493]}], "snippet": "During the GMP preparations, the CM will work with the Design team to notify bidders, conduct pre-bid meetings, conduct site visits and/or walk-throughs, and receive trade contractor bids. Upon receipt of bids, the CM will analyze all bids to verify that bids are complete and that no unacceptable qualifications are made. The CM\u2019s bid analysis, together with the CM\u2019s recommendation for award, shall be reviewed with PCMC and the architect prior to award of trade contracts or purchase orders.", "size": 2, "hash": "3dbad16ef31ff75ffb7f6c86b22991ff", "id": 4}, {"samples": [{"hash": "j02BIbKN2V6", "uri": "/contracts/j02BIbKN2V6#process-management", "label": "Contact Center Services Agreement (Contax Holding CO)", "score": 18.0, "published": true}, {"hash": "b7zVBUCBiFV", "uri": "/contracts/b7zVBUCBiFV#process-management", "label": "Contact Center Services Agreement (Contax Holding CO)", "score": 18.0, "published": true}], "snippet_links": [{"key": "types-of", "type": "clause", "offset": [27, 35]}, {"key": "to-the-service", "type": "clause", "offset": [49, 63]}, {"key": "the-operations", "type": "clause", "offset": [182, 196]}, {"key": "modifications-to-the", "type": "clause", "offset": [267, 287]}, {"key": "requirements-specification", "type": "clause", "offset": [335, 361]}, {"key": "associated-risks", "type": "clause", "offset": [386, 402]}], "snippet": "Identify and implement all types of improvements to the Service in a reactive and/or proactive manner, such as: Implement front-end modifications (Attendance application used during the operations); Introduce alterations to the Audible Response Unit (ARU); Introduce modifications to the Attendance model; Draw up the Orbitall Clients requirements specification (analysis of impact and associated risks).", "size": 2, "hash": "7be7b81cc4ce396393c4aa0e9d409b25", "id": 5}, {"samples": [{"hash": "8RjLTA0Inyn", "uri": "/contracts/8RjLTA0Inyn#process-management", "label": "Bilateral Development Services Agreement (Maxeon Solar Technologies, Ltd.)", "score": 33.3264884949, "published": true}, {"hash": "aZKfQAyEFKr", "uri": "/contracts/aZKfQAyEFKr#process-management", "label": "Bilateral Development Services Agreement (Maxeon Solar Technologies, Ltd.)", "score": 33.0718688965, "published": true}], "snippet_links": [{"key": "both-parties", "type": "clause", "offset": [0, 12]}, {"key": "research-and-development-activities", "type": "definition", "offset": [35, 70]}, {"key": "scope-of-this", "type": "clause", "offset": [92, 105]}, {"key": "adherence-to-the", "type": "definition", "offset": [163, 179]}, {"key": "the-parties-shall", "type": "clause", "offset": [232, 249]}, {"key": "to-ensure", "type": "clause", "offset": [294, 303]}, {"key": "maintenance-of-the", "type": "clause", "offset": [356, 374]}], "snippet": "Both Parties shall ensure that all research and development activities conducted within the scope of this Collaboration are managed, documented, and maintained in adherence to the prevailing industry-leading standards. To this end, the Parties shall implement and maintain appropriate measures to ensure effective and timely management, documentation, and maintenance of the following: (a)", "size": 2, "hash": "c747b306d3054df8e2bfd4809439cfea", "id": 6}, {"samples": [{"hash": "htxqAnBpyAz", "uri": "/contracts/htxqAnBpyAz#process-management", "label": "D4science System High Level Design", "score": 19.0, "published": true}, {"hash": "bN2XDBhZ2hu", "uri": "/contracts/bN2XDBhZ2hu#process-management", "label": "D4science System High Level Design", "score": 19.0, "published": true}], "snippet_links": [{"key": "the-process", "type": "clause", "offset": [0, 11]}, {"key": "class-of-services", "type": "definition", "offset": [23, 40]}, {"key": "management-of", "type": "clause", "offset": [61, 74]}, {"key": "an-appropriate", "type": "clause", "offset": [180, 194]}, {"key": "workflow-management", "type": "definition", "offset": [195, 214]}, {"key": "family-cover", "type": "definition", "offset": [248, 260]}, {"key": "in-particular", "type": "clause", "offset": [299, 312]}, {"key": "user-interface", "type": "definition", "offset": [351, 365]}, {"key": "activities-related-to", "type": "clause", "offset": [404, 425]}, {"key": "services-and", "type": "clause", "offset": [491, 503]}, {"key": "the-execution", "type": "clause", "offset": [528, 541]}], "snippet": "The Process Management class of services is dedicated to the management of gCube Compound Services (CS), i.e. complex services obtained by composing other simpler services through an appropriate workflow management language. The components in this family cover all aspects related to CS management. In particular, they allow to design via a dedicated user interface the CS and perform various validation activities related to CS design, to manage CS definitions, to execute instances of the services and control in various ways the execution. Finally, a component in this family allows managing gLite jobs as \u201cservices\u201d in a CS.", "size": 2, "hash": "09f522aef1c4087b8dbb0ac9062cbfc2", "id": 7}, {"samples": [{"hash": "6UBzfPQqa1L", "uri": "/contracts/6UBzfPQqa1L#process-management", "label": "Technical Support and Spare Supply Agreement", "score": 23.6988372803, "published": true}], "snippet_links": [{"key": "major-component", "type": "definition", "offset": [10, 25]}, {"key": "phase-of", "type": "clause", "offset": [86, 94]}, {"key": "responsible-for", "type": "clause", "offset": [124, 139]}, {"key": "management-plans", "type": "clause", "offset": [210, 226]}, {"key": "to-establish", "type": "clause", "offset": [227, 239]}, {"key": "successful-execution", "type": "definition", "offset": [244, 264]}, {"key": "the-duration-of-the-contract", "type": "clause", "offset": [282, 310]}, {"key": "the-process", "type": "clause", "offset": [312, 323]}, {"key": "building-blocks", "type": "clause", "offset": [369, 384]}, {"key": "maintenance-plan", "type": "definition", "offset": [494, 510]}, {"key": "order-handling", "type": "clause", "offset": [542, 556]}, {"key": "resource-management", "type": "definition", "offset": [558, 577]}, {"key": "investment-management", "type": "clause", "offset": [590, 611]}, {"key": "the-contractor-shall", "type": "clause", "offset": [613, 633]}, {"key": "required-to-work", "type": "clause", "offset": [637, 653]}, {"key": "to-ensure", "type": "clause", "offset": [685, 694]}, {"key": "maintenance-activities", "type": "clause", "offset": [704, 726]}, {"key": "maintenance-and", "type": "clause", "offset": [763, 778]}, {"key": "reliability-and-availability", "type": "clause", "offset": [788, 816]}, {"key": "without-affecting", "type": "clause", "offset": [817, 834]}, {"key": "revenue-service", "type": "definition", "offset": [845, 860]}, {"key": "comprehensive-maintenance", "type": "definition", "offset": [905, 930]}, {"key": "by-the-agency", "type": "clause", "offset": [1006, 1019]}, {"key": "the-maintenance", "type": "clause", "offset": [1021, 1036]}, {"key": "by-the-contractor", "type": "clause", "offset": [1109, 1126]}, {"key": "regulatory-agencies", "type": "definition", "offset": [1128, 1147]}, {"key": "to-maintain", "type": "clause", "offset": [1164, 1175]}, {"key": "design-life", "type": "clause", "offset": [1254, 1265]}, {"key": "the-equipment", "type": "clause", "offset": [1269, 1282]}, {"key": "annual-basis", "type": "clause", "offset": [1478, 1490]}, {"key": "the-performance", "type": "clause", "offset": [1499, 1514]}, {"key": "frequency-and-duration", "type": "clause", "offset": [1572, 1594]}, {"key": "provide-a", "type": "definition", "offset": [1625, 1634]}, {"key": "life-of-the-project", "type": "definition", "offset": [1718, 1737]}, {"key": "the-requirements", "type": "clause", "offset": [1786, 1802]}], "snippet": "The first major component of any TSSSA is Process Management. During the mobilization phase of the TSSSA, the contractor is responsible for developing necessary implementation, staffing, material controls, and management plans to establish the successful execution of the TSSSA for the duration of the contract. The process management component represents the critical building blocks for a successful TSSSA. The process management component of a TSSSA may include any or all of the following: Maintenance Plan, Joint Fleet Planning, Service Order Handling, Resource Management and Depot & Investment Management. The contractor shall be required to work in conjunction with the agency to ensure that all maintenance activities are forecasted in a way to optimize maintenance and increase reliability and availability without affecting scheduled revenue service. The contractor shall develop and propose a comprehensive maintenance plan which shall be updated and submitted annually for review and approval by the agency. The maintenance plan shall include all activities, schedules and documentation required by the contractor, regulatory agencies, and the agency to maintain, inspect, and restore equipment to maintain intended design function over the design life of the equipment. The maintenance plan shall be a detailed documented process describing all maintenance activities that are required for the equipment throughout its life and must be reviewed and approved on an annual basis against the performance of the equipment. The maintenance plan shall include the frequency and duration of each activity required and provide a scheduling tool to demonstrate how the equipment will be maintained throughout the life of the project. Ultimately, the maintenance plan shall fulfill the requirements of 49 CFR 238.107.", "size": 2, "hash": "81700ffc68b5bd7c475762962df51dc1", "id": 8}, {"samples": [{"hash": "93h5FMCaqF7", "uri": "/contracts/93h5FMCaqF7#process-management", "label": "Premier Support Agreement (Medibuy Com Inc)", "score": 18.0, "published": true}], "snippet_links": [{"key": "dynamic-pricing", "type": "definition", "offset": [75, 90]}, {"key": "back-office", "type": "definition", "offset": [91, 102]}, {"key": "the-process", "type": "clause", "offset": [113, 124]}, {"key": "services-include", "type": "clause", "offset": [136, 152]}, {"key": "buyers-and-sellers", "type": "clause", "offset": [162, 180]}, {"key": "the-value", "type": "clause", "offset": [222, 231]}, {"key": "to-buyers", "type": "clause", "offset": [392, 401]}], "snippet": "Premier's Services shall also include process management that includes the dynamic pricing back office function. The process management services include engaging buyers and sellers through various events meant to maximize the value dynamic pricing delivers to participants. This service also includes activities such as receiving incoming requests, identifying buyers, communicating requests to buyers, returning quotes to participants and members, facilitating transactions and all follow-up between events.", "size": 1, "hash": "45f54b8c834f67fe20c1dfe8798dcfdb", "id": 9}, {"samples": [{"hash": "6YorCaUnQJp", "uri": "/contracts/6YorCaUnQJp#process-management", "label": "Grant Agreement", "score": 23.7099933624, "published": true}], "snippet_links": [{"key": "process-improvement", "type": "definition", "offset": [53, 72]}, {"key": "user-groups", "type": "clause", "offset": [383, 394]}, {"key": "of-the-standard", "type": "clause", "offset": [395, 410]}, {"key": "annual-conference", "type": "clause", "offset": [435, 452]}, {"key": "reference-model", "type": "clause", "offset": [469, 484]}, {"key": "consist-of", "type": "clause", "offset": [510, 520]}, {"key": "capability-levels", "type": "clause", "offset": [521, 538]}, {"key": "the-process", "type": "clause", "offset": [555, 566]}, {"key": "conducting-assessment", "type": "clause", "offset": [793, 814]}], "snippet": "\u200c This sections analyses generic maturity models for process improvement. In theory, these models can be used to improve processes independently of the domain and context of those processes.\nA.5.1 ISO/ IEC 15504\u200c Description: The ISO/IEC 15504 [39] was born as the \u201cSoftware Process Improvement and Capability Evaluation\u201d (SPICE) [38] in 1993. The acronym is still used today by the user groups of the standard and in the title of the annual conference. ISO 15504 is a reference model for maturity models that consist of capability levels that consist of the process attributes and further consist of generic practices. The standard is divided into nine components or parts which are, (1) Concepts and introductory guide; (2) A model for process management; (3) Rating processes; (4) Guide to conducting assessment;", "size": 1, "hash": "cbf4b40135917592abdac28a5babb45e", "id": 10}], "next_curs": "ClsSVWoVc35sYXdpbnNpZGVyY29udHJhY3RzcjcLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2Ihtwcm9jZXNzLW1hbmFnZW1lbnQjMDAwMDAwMGEMogECZW4YACAA", "clause": {"size": 30, "children": [["functions", "Functions"], ["", ""], ["csvalidator-service", "CSValidator Service"], ["reference-architecture", "Reference Architecture"], ["cs-engine-service", "CS Engine Service"]], "parents": [["integrated-organisation-of-knowledge-and-information-flow-ia1", "Integrated Organisation of Knowledge and Information Flow Ia1"], ["miscellaneous", "Miscellaneous"], ["assignment", "Assignment"], ["integrating-activities-ia", "Integrating Activities Ia"], ["prices-structure", "PRICES STRUCTURE"]], "title": "Process Management", "id": "process-management", "related": [["access-management", "Access Management", "Access Management"], ["virus-management", "Virus Management", "Virus Management"], ["configuration-management", "Configuration Management", "Configuration Management"], ["service-management", "Service Management", "Service Management"], ["patch-management", "Patch Management", "Patch Management"]], "related_snippets": [], "updated": "2025-09-21T06:08:45+00:00", "also_ask": ["What are the essential elements to include in a robust Process Management clause?", "How can this clause be leveraged to allocate or limit liability strategically?", "What are the most common pitfalls or ambiguities that undermine enforceability?", "How does this clause compare to industry standards or similar provisions in competitor contracts?", "What factors do courts consider when determining if a Process Management clause is enforceable?"], "drafting_tip": "Specify roles and responsibilities to prevent confusion, outline procedures clearly to ensure consistency, and set timelines to promote accountability.", "explanation": "The Process Management clause establishes the procedures and responsibilities for overseeing and coordinating the various tasks and workflows within a project or agreement. It typically outlines how processes will be documented, monitored, and improved, and may specify roles such as process owners or managers who are accountable for ensuring compliance. By clearly defining how processes are managed, this clause helps ensure efficiency, consistency, and accountability, reducing the risk of miscommunication or operational delays."}, "json": true, "cursor": ""}}