{ "nodes": [ { "id": "6", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Implement key performance indicators (KPIs) to monitor financial performance against the plan.This is a continuous iteration which ensures that the financial planning remains adaptive to changing circumstances. Integrate compliance considerations and risk management into the financial planning process. Ensure that plans adhere to regulatory requirements and address potential financial risks. ", "Process_Group": "Financial Planning and Budgeting", "Scope": "This involves regular review and assessment of actual results compared to forecasts and budgets and using feedback from stakeholders to refine and improve the financial planning process.", "Outcome": "Actual financial performance is monitored against planned financial performance.", "GUID": "b799627c-99e4-11ee-3781-0201b014c5b2", "name": "Conduct performance monitoring", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.0, "y": -2.0, "z": 0.0 }, "color": "#66CCFF", "size": 1.0 }, { "id": "7", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Conduct periodic audits and assurance checks to validate the accuracy and reliability of financial planning data and processes.", "Process_Group": "Financial Planning and Budgeting", "Scope": "The processes and data used during the financial planning are examined to identify areas of improvement and mitigate risk. For efficient auditing, all the activities, and results from the planning process should be properly documented and made available to the audit team. Additionally, audit findings should be documented and shared with the relevant stakeholders.", "Outcome": "Financial planning process is audited.", "GUID": "b7996281-99e4-11ee-3781-0201b014c5b2", "name": "Conduct financial planning audits", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9999591495320046, "y": -1.9966777408637875, "z": 0.0156557062827583 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Financial goals must align with the overall strategic business objectives. This ensures the efficient allocation of financial resources to support the organizations strategic objectives.", "Process_Group": "Financial Planning and Budgeting", "Scope": "Based on the strategic objectives, determine the key financial drivers such as capital allocation and cost management that directly help to achieve the strategic objectives. Additionally, KPIs that measure both aspects should be defined and reported periodically. Financial processes and strategic processes should also be integrated to ensure prioritization of operational activities. ", "Outcome": "Financial goals are aligned with strategic goals.", "GUID": "b7996276-99e4-11ee-3781-0201b014c5b2", "name": "Align financial planning with strategic planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9997821323207003, "y": -1.9933554817275747, "z": 0.0417479816047524 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is to predict the expected future income and expenses of the organization based on the data collected. It also provides a benchmark against which financial performance is monitored.", "Process_Group": "Financial Planning and Budgeting", "Scope": "With the help of statistical models, expected future income and expenses can be predicted. It involves the use of both historical and current quantitative and qualitative data. Financial forecasts tend to change over time due to changes in internal and external conditions, therefore, it is important to document, monitor, and review forecast results for a more accurate prediction. ", "Outcome": "Expected future earnings and expenditure are predicted and monitored.", "GUID": "b799626e-99e4-11ee-3781-0201b014c5b2", "name": "Perform financial forecasting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.999387254105089, "y": -1.9900332225913622, "z": 0.07827568902012848 }, "color": "#66CCFF", "size": 1.0 }, { "id": "10", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Gather relevant financial data from various sources across the organization. Integrate data from departments such as sales, marketing, operations, and HR to create a holistic financial picture", "Process_Group": "Financial Planning and Budgeting", "Scope": "A comprehensive dataset that incorporates information like sales forecasts, budgeting figures, expense reports, market trends, and other relevant financial metrics is created. The collected data is merged in a coherent manner. By consolidating and integrating this data, financial planners can gain a holistic view of the companys financial situation, enabling better analysis, forecasting, and decision-making. It helps in creating more accurate financial models and plans that take into account multiple factors affecting the organizations performance.", "Outcome": "Dataset is standardized. ", "GUID": "b7996267-99e4-11ee-3781-0201b014c5b2", "name": "Perform data collection and integration", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.9986928295239474, "y": -1.9867109634551494, "z": 0.12523712316235644 }, "color": "#66CCFF", "size": 1.0 }, { "id": "11", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Foster collaboration among different departments and teams involved in the financial planning process. Effective communication is crucial to ensuring that all stakeholders are aligned and informed.", "Process_Group": "Financial Planning and Budgeting", "Scope": "Roles and responsibilities of each stakeholder are clearly defined after which an efficient communication channel for regular updates and discussions is set up.", "Outcome": "All stakeholders are aligned on the scope and expectations of the process.", "GUID": "b7996279-99e4-11ee-3781-0201b014c5b2", "name": "Ensure communication and collaboration", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9993191959496073, "y": -1.9833887043189369, "z": 0.05218000294572144 }, "color": "#66CCFF", "size": 1.0 }, { "id": "12", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Perform scenario analysis to assess the impact of various factors on financial outcomes. This helps in identifying potential risks and opportunities, allowing for better decision-making. ", "Process_Group": "Financial Planning and Budgeting", "Scope": "This process typically involves creating and analyzing multiple scenarios based on varying factors like market conditions, economic changes, industry trends, or specific events. By assessing how different scenarios might play out, planners can anticipate potential risks, opportunities, and challenges. It aids in devising strategies to mitigate risks or capitalize on favorable conditions, thereby enhancing the overall financial plans resilience and adaptability to different circumstances.", "Outcome": "Impact of potential changes in forecast results on financial performance is assessed and risk management plans are determined.", "GUID": "b7996272-99e4-11ee-3781-0201b014c5b2", "name": "Conduct scenario analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9985294999620216, "y": -1.9800664451827243, "z": 0.09391931567844575 }, "color": "#66CCFF", "size": 1.0 }, { "id": "13", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Clearly articulate the financial planning objectives and scope. This could include budgeting, forecasting, strategic planning, and performance analysis", "Process_Group": "Financial Planning and Budgeting", "Scope": "The scope of financial planning should align with the strategic objectives. The strategic objectives should be well defined and measurable.The scope of financial planning can encompass cash flow management, investment planning, and any other areas based on the strategic objectives of the company.", "Outcome": "Scope of financial planning is defined.", "GUID": "b7996263-99e4-11ee-3781-0201b014c5b2", "name": "Define financial planning objectives and Scope", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9973313934809576, "y": -1.9767441860465116, "z": 0.14608809223063535 }, "color": "#66CCFF", "size": 1.0 }, { "id": "14", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Generate regular financial reports to communicate the outcomes of the planning process to stakeholders, including executives, managers, and investors.", "Process_Group": "Financial Planning and Budgeting", "Scope": "This involves the use of actual financial data to gain insights into the financial performance of the organization. Based on management needs, the report should be well structured and provide the relevant information suitable for management decision making.", "Outcome": "Results from financial planning process are communicated and shared with all stakeholders.", "GUID": "b799627f-99e4-11ee-3781-0201b014c5b2", "name": "Report on outcomes of planning process", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.995643239717227, "y": -1.973421926910299, "z": 0.20868306464006528 }, "color": "#66CCFF", "size": 1.0 }, { "id": "18", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review,\n approve and monitor spending request,\n Perform periodic variance analysis,\n Perform budget adjustments,\n Generate income and expense reports", "Type": "Business Process", "Description": "The goal of this process is to ensure that the company is not operating beyong approved budgetary levels.It is necessary for the comparison of actual performance with the provisions and estimates of the budget.", "Process_Group": "Financial Planning and Budgeting", "hasAssignment": true, "Scope": "It involves monitoring the budget implementation,performing variance analysis, managing financial performance and exercising cost management activities.Cost management is about deciding which expenses should or can be avoided in order to optimise revenue.", "Outcome": "Resources are efficiently allocated in order to optimise the performance of the budget.", "GUID": "052ff017-a505-11ec-4ad5-0201b014c5b2", "name": "Perform budgetary controls", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.993383425608483, "y": -1.9700996677740863, "z": 0.28170039694952104 }, "color": "#66CCFF", "size": 1.0 }, { "id": "20", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Set periodic spending limit,\n Distribute budget within periodic spending limits", "Type": "Business Process", "Description": "This process is about putting the budget into practical use and keeping within designated forecasting parameters.", "hasAssignment": true, "Process_Group": "Financial Planning and Budgeting", "Scope": "In this process all potential challenges to the successful implementation of the budget are also identified and addressed.", "Outcome": "The budget is being executed.", "GUID": "052ff014-a505-11ec-4ad5-0201b014c5b2", "name": "Release and implement budget", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9972772472925846, "y": -1.9667774086378738, "z": 0.10432448153408794 }, "color": "#66CCFF", "size": 1.0 }, { "id": "22", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Request budget submission,\n Obtain complete budget submission,\n Provide budget assumptions,\n Adjust functional budget with budget assumptions,\n Create budget for each functional line,\n Combine functional budgets,\n Adjust financial forecast results", "Type": "Business Process", "Description": "The purpose of this process is to ensure that results from the financial forecasts are put into a flexible financial plan. A flexible plan ensures the budget is subject to adjustments.", "hasAssignment": true, "Process_Group": "Financial Planning and Budgeting", "Scope": "It involves preparing a detailed plan for revenues and expenditures in a comprehensive, realistic and transparent manner.Creating the budget must address its functions such as sales, cost of production, or a project.", "Outcome": "The planned income to be generated and expenditures to be incurred are prepared.", "GUID": "052fa1f0-a505-11ec-4ad5-0201b014c5b2", "name": "Create periodic budget", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.995058439363243, "y": -1.9634551495016612, "z": 0.17211898442360923 }, "color": "#66CCFF", "size": 1.0 }, { "id": "24", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Send draft to management for approval,\n Perform budget adjustments,\n Resubmit completed budget draft for approval,\n Approve budget", "Type": "Business Process", "Description": "This process describes a thorough review of the prepared budget and its underlying assumptions before it is approved.", "hasAssignment": true, "Process_Group": "Financial Planning and Budgeting", "Scope": "Management must approve before the budget is released and implemented.", "Outcome": "The budget becomes the financial operating guide for the company.", "GUID": "052ff011-a505-11ec-4ad5-0201b014c5b2", "name": "Review and approve budget", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.992159255237771, "y": -1.9601328903654485, "z": 0.25032874549161355 }, "color": "#66CCFF", "size": 1.0 }, { "id": "29", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This periodic process ensures the fair and accurate allocation of shared or indirect costs across various organizational units. ", "Process_Group": "Overhead Cost Controlling", "Scope": "This process involves systematically distributing costs from sender cost objects, such as cost centers or internal orders, to designated receiver cost objects based on predefined allocation rules. Key steps include defining allocation rules, identifying sender and receiver objects, executing the allocation run and analyzing results for accuracy", "Outcome": "Indirect costs are distributed to correct cost centers or profit centers.", "GUID": "8da3c075-9d8e-11ee-3781-0201b014c5b2", "name": "Run allocation cycles", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.988498171177448, "y": -1.956810631229236, "z": 0.3389483679843468 }, "color": "#66CCFF", "size": 1.0 }, { "id": "30", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "It describes full eliminations of all intragroup transactions. Adjustments are made for transactions that occur between the reporting date of the financial statement and the date of investment in a subsidiary. ", "Scope": "It covers adjustments made for tax effects, goodwill, capital reserves, intragroup transactions and balances, non-controlling interests and cost of equity investments of the parent in each subsidiary.", "Process_Group": "Intercompany", "Outcome": "Consolidated Financial statement data shows profit or loss and equity position at group level considering all intragroup eliminations.", "GUID": "18962e21-4be9-11ea-0cfc-001bc641ce4f", "name": "Conduct intercompany eliminations", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.98399370198131, "y": -1.9534883720930232, "z": 0.4379718879654452 }, "color": "#66CCFF", "size": 1.0 }, { "id": "31", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that sub-ledgers are reconciled with the general ledger. This includes reconciling accounts payable, accounts receivable, and other relevant modules.", "Process_Group": "General Ledger", "Scope": "Reconcile of the following sub-ledgers with the general ledger: -Accounts Receivable sub-ledger -Accounts Payable sub-ledger -Inventory sub-ledger -Fixed Assets sub-ledger -Cash sub-ledger -Project sub-ledger -Expense subledger: -Payroll Subledger -Revenue Subledge", "Outcome": "Discrepancies in accounting records between each sub-ledger and GL are identified and cleared.", "GUID": "8da3c06c-9d8e-11ee-3781-0201b014c5b2", "name": "Reconcile sub-ledgers with general ledger", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9938755441958478, "y": -1.9501661129568106, "z": 0.1563979355928709 }, "color": "#66CCFF", "size": 1.0 }, { "id": "32", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This refers to the process of gathering, preparing and presenting information about the companys revenue, expenses, and costs to determine whether it made a net profit or loss during an accounting period such as month, quarter, or year.", "Process_Group": "Finance Reporting and Analytics", "Scope": "After period end closing is completed, all revenues, costs, income, and expenses for the accounting period are combined. The P&L report typically shows the gross profit, operating profit and net profit or net loss positions. The figures are validated and published in the reporting system", "Outcome": "Net Profit or net loss figures are released", "GUID": "c510d0f1-5b7c-11ee-3781-0201b014c5b2", "name": "Generate Profit & Loss statement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9895483308477835, "y": -1.946843853820598, "z": 0.2502014738670276 }, "color": "#66CCFF", "size": 1.0 }, { "id": "33", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Periodic settlements serve to accurately allocate and distribute costs among different cost objects, such as cost centers, internal orders, and production processes. These settlements are crucial for tracking and controlling expenses, ensuring that costs are appropriately assigned to specific activities or projects.", "Process_Group": "Overhead Cost Controlling", "Scope": "This process covers settlements to transfer costs from internal orders, projects, or other cost objects to cost centers or other target objects. The process facilitates the creation of settlement documents that provide a transparent record of the cost flows, supporting effective cost management and financial reporting. Additionally, periodic settlements contribute to the closing of temporary accounts, preparing the system for the next accounting period. ", "Outcome": "Accurate allocation and distribution of costs among different cost objects for a given period. ", "GUID": "8da3c077-9d8e-11ee-3781-0201b014c5b2", "name": "Perform periodic settlements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9842692388038063, "y": -1.9435215946843853, "z": 0.3543989739287314 }, "color": "#66CCFF", "size": 1.0 }, { "id": "34", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of the foreign currency revaluation process is to adjust the values of foreign currency transactions and balances to reflect changes in exchange rates. This process is particularly relevant for businesses that conduct transactions in multiple currencies.", "Process_Group": "General Ledger", "Scope": "First, identify foreign currency transactions and balances. Next, determine the appropriate exchange rates for revaluation, considering factors such as spot rates, forward rates, and historical rates. Calculate the gain or loss resulting from changes in exchange rates by comparing the revalued balances to their original values. Record the foreign exchange gains or losses in the financial records.", "Outcome": "Adjustment of the values of foreign currency-denominated transactions and balances to reflect changes in exchange rates. This adjustment leads to the recognition of foreign exchange gains or losses in the financial statements.", "GUID": "d3f52a9c-47d5-11ee-3781-0201b014c5b2", "name": "Perform foreign currency revaluation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.977956912877356, "y": -1.9401993355481728, "z": 0.46898291390683056 }, "color": "#66CCFF", "size": 1.0 }, { "id": "35", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of the post-closing entries process is to officially close temporary accounts and prepare the accounting records for the start of a new accounting period. Post-closing entries ensure that the balances in these accounts are transferred to permanent accounts, such as retained earnings. This process not only facilitates accurate financial reporting by separating different periods but also helps maintain a clear and organized financial structure, supporting transparency and compliance with accounting principles. ", "Process_Group": "General Ledger", "Scope": "After financial statements have been prepared and reviewed, certain accounts, known as temporary or nominal accounts (e.g., revenue, expenses, and dividends), need to be reset to zero in order to begin accumulating transactions for the next period.", "Outcome": "Formal closure of temporary or nominal accounts in the general ledger, which include revenue, expense, and dividend accounts. ", "GUID": "08f11d49-9da8-11ee-3781-0201b014c5b2", "name": "Post closing entries", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.970530051204303, "y": -1.93687707641196, "z": 0.5939452059460842 }, "color": "#66CCFF", "size": 1.0 }, { "id": "36", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is used by businesses to set aside funds to cover specific anticipated future expenses or other financial impacts. ", "Process_Group": "General Ledger", "Scope": "Provisions are recorded according to accounting principles, depending on the expected future costs. The level of provisions will depend on the point in time that the provisions are setup. Moreover, the provisions must be need adjusted periodically.", "Outcome": "All provisions are posted to correct period.", "GUID": "61b92dc3-a3b4-11ed-3781-0201b014c5b2", "name": "Capture provisions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9891164025526438, "y": -1.9335548172757475, "z": 0.20836491330362922 }, "color": "#66CCFF", "size": 1.0 }, { "id": "37", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves collecting financial data, classifying it into relevant categories (operations, investments, and finance), and performing calculations to present a coherent picture of cash inflows and outflows. ", "Process_Group": "Finance Reporting and Analytics", "Scope": "After validation and approval, the finalized statement is included in financial reports for both internal and external audiences.", "Outcome": "Cash flow statement is released.", "GUID": "6016034b-53b7-11ee-3781-0201b014c5b2", "name": "Generate cash flow statement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9820029257198377, "y": -1.930232558139535, "z": 0.32811362513362313 }, "color": "#66CCFF", "size": 1.0 }, { "id": "38", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Upload figures to consolidation system,\n Execute period end closing report (Cash book),\n Execute period end closing report (general ledger),\n Execute period end closing report (trial balance),\n Report P&L figures,\n Report balance sheet figures,\n Report accounts payable and accounts receivable,\n Report work in progress (WIP),\n Report accrued and deferred sales", "Type": "Business Process", "Description": "This process is about collecting, consolidating and generating the total value of the companys assets, liabilities, and capital at the end of an accounting period. ", "Process_Group": "Finance Reporting and Analytics", "hasAssignment": true, "Scope": "After period end closing is completed, reporting relevant figures for the balance sheet are submitted, validated and published in the reporting system.", "Outcome": "Balance sheet figures are released.", "GUID": "26c56e2c-7ca1-11e5-0a66-001bc640cd9b", "name": "Generate balance sheet", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9736667157342094, "y": -1.9269102990033222, "z": 0.4582279261089435 }, "color": "#66CCFF", "size": 1.0 }, { "id": "40", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Perform manual posting of primary costs ,\n Transfer time sheet entries to CO,\n Edit costing run ,\n Post standard price ,\n Perform service and repair order settlement ,\n Perform actual overhead calculation ,\n Perform variance calculation ,\n Perform actual settlement ,\n Execute COPA actual assessment ,\n Calculate WIP", "Type": "Business Process", "Description": "Profitability Analysis (COPA) reports in organizations serve the purpose of offering detailed insights into the profitability of different dimensions such as products, customers, market segments, and geographical regions. These reports aid in understanding the contribution margin, customer value, and overall impact on the bottom line.", "Process_Group": "Finance Reporting and Analytics", "hasAssignment": true, "Scope": "Profitability Analysis (COPA) reports include: - Operating Concern Reports - Profitability Analysis Line Items - Profit Center Reports.", "Outcome": "The organization has a comprehensive and detailed analysis of the financial performance of various dimensions, such as products, customers, and market segments, providing actionable insights to optimize profitability and support strategic decision-making.", "GUID": "2b3cd26c-9734-11e8-2ddf-001bc640cd9b", "name": "Generate profitability analysis reports", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.964026641348297, "y": -1.9235880398671097, "z": 0.5986981743619616 }, "color": "#66CCFF", "size": 1.0 }, { "id": "42", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Execute planned depreciation run,\n Maintain relevant company code,\n Maintain relevant posting period,\n Execute test depreciation run,\n Execute unplanned depreciation postings,\n Verify the results from the test depreciation run,\n Execute depreciation run", "Type": "Business Process", "Description": "This process reflects the application of the depreciation policy to all fixed assets which fall within the companys asset register.", "hasAssignment": true, "Process_Group": "Asset Accounting", "Scope": "Conduct periodic asset depreciation in accordance with the depreciation policy given in the applicable financial reporting standards (e.g. IFRS). At period-end depreciation may be reposted, recalculated, or posted anew. After posting depreciation, the asset history sheet is checked to ensure the complete and accurate asset transactions for the period are posted.", "Outcome": "Perform periodic asset depreciation is complete.", "GUID": "d4cc2764-6966-11e8-2ddf-001bc640cd9b", "name": "Perform periodic asset depreciation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.953001639385446, "y": -1.920265780730897, "z": 0.749514163624804 }, "color": "#66CCFF", "size": 1.0 }, { "id": "44", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check reason for blocked invoices,\n Align with the requester,\n Get approval to release blocked invoice,\n Release blocked invoices ,\n Trigger dispute management case with vendor", "Type": "Business Process", "Description": "This process ensures that all Accounts Payable invoices posted (including recurring entries) so that they are considered for the accounting period.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "Post AP invoices and where applicable review and release blocked incoming invoices so that they can be applied to the appropriate accounting period in accordance with the matching concept.", "Outcome": "All AP invoices are posted (including recurring entries).", "GUID": "68f6e4eb-9732-11e8-2ddf-001bc640cd9b", "name": "Post AP invoices", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9830030624058794, "y": -1.9169435215946844, "z": 0.26019003533745066 }, "color": "#66CCFF", "size": 1.0 }, { "id": "46", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review payroll results ,\n Analyse wage type details,\n Reconcile payroll postings,\n Generate payroll reports", "Type": "Business Process", "Description": "Process to ensure that closing operations are closed in payroll.", "hasAssignment": true, "Process_Group": "General Ledger", "Scope": "Review payroll results and wage type details, as well as reconcile payroll postings. When applicable, execute quarterly reports and year-end activities.", "Outcome": "Closing in payroll complete", "GUID": "adc123f1-d629-11e9-0cfc-001bc641ce4f", "name": "Perform closing in payroll", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9724273609217797, "y": -1.9136212624584719, "z": 0.40580239531523865 }, "color": "#66CCFF", "size": 1.0 }, { "id": "48", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Post accruals or deferrals to account for expenses or revenues that need to be recognized in the current period. This are typical period-end closing activities because the amount of the necessary accruals or deferrals is usually unknown until the end of a given period.", "Process_Group": "General Ledger", "Scope": "Accrual postings are typical period-end closing activities because the amount of the necessary accruals is usually unknown until the end of a given period. Committed amounts are accrued to post expenses in the fiscal periods in which they occur.", "Outcome": "All accruals and deferrals posted to correct period.", "GUID": "61b92dc5-a3b4-11ed-3781-0201b014c5b2", "name": "Record accruals and deferrals", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9603589042696297, "y": -1.910299003322259, "z": 0.5617449148610576 }, "color": "#66CCFF", "size": 1.0 }, { "id": "49", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Release billing to accounts receivable,\n Select billing documents for release,\n Align with sales on reason for billing block,\n Align with credit management,\n Align with Risk Management,\n Align with hazardous substances and dangerous goods management,\n Trigger credit limit management handling ,\n Trigger risk management handling,\n Trigger hazardous substances and dangerous goods handling", "Type": "Business Process", "Description": "This process ensures that all sales invoices are posted to accounts receivable accounting in a timely manner for period end closing.", "hasAssignment": true, "Process_Group": "Accounts Receivable", "Scope": "The post-sales invoices to accounting process is initiated by sales order processing, followed by delivery processing and goods issue confirmation. Billing documents are generated, and revenue is recognized based on delivery. The sales invoice is posted to the Accounts Receivable subledger, updating customer balances, and corresponding entries are made in the general ledger, considering tax calculations. ", "Outcome": "All sales invocies are posted to accounts payable.", "GUID": "68f6e4f1-9732-11e8-2ddf-001bc640cd9b", "name": "Post sales invoices to accounting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.946716840375551, "y": -1.9069767441860466, "z": 0.7280058386750243 }, "color": "#66CCFF", "size": 1.0 }, { "id": "53", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The goal of this process is to validate the consistency and accuracy of financial data based on defined rules. Data validation ensures that financial consolidation occurs in a timely and seamless manner, avoiding data inconsistencies.", "Process_Group": "General Ledger", "Scope": "Data validation covers all the activities done in the system before posting entries for consolidation. All potential errors resulting from validation are investigated and resolved.", "Outcome": "The financial statement data is valid and unbiased.", "GUID": "c7087264-bd00-11e9-0cfc-001bc641ce4f", "name": "Conduct reporting data validation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.931420399938501, "y": -1.9036544850498338, "z": 0.9045728490251015 }, "color": "#66CCFF", "size": 1.0 }, { "id": "54", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Consolidation can only take place when financial statement data of the subsidiary(ies) have been collected and captured in the groups standardised format. When these requirements are met, the captured data is approved and can be used for financial consolidation.", "Process_Group": "General Ledger", "Scope": "Each subsidiarys data is captured separately but with uniform accounting policies for the same reporting date. It covers all activities from capturing to approval.", "Outcome": "Subsidiary(ies) financial statement data is ready for group consolidation.", "GUID": "db2aa62c-b79b-11e9-0cfc-001bc641ce4f", "name": "Approve and import financial statements data for consolidation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9755396857422882, "y": -1.9003322259136213, "z": 0.3118380189413426 }, "color": "#66CCFF", "size": 1.0 }, { "id": "55", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The goal of this process is to verify the consistency and accuracy of the adjustments. It is important in order to ensure that all consolidation adjustments have been properly accounted for.", "Process_Group": "General Ledger", "Scope": "Data verification after adjustments covers all the activities done before generating the consolidated statement. All potential errors are investigated and resolved.", "Outcome": "The adjusted financial statements data is accurate and can now be reported.", "GUID": "c7087280-bd00-11e9-0cfc-001bc641ce4f", "name": "Perform final verifications at group level", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.960828155536908, "y": -1.8970099667774087, "z": 0.48321489358246456 }, "color": "#66CCFF", "size": 1.0 }, { "id": "56", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The balance sheet and P&L statements data are prepared to show the overall financial position of the parent company for the same given period of the subsidiary. The P&L shows the net profit or loss while the balance sheet represents its net worth at the given period without including data from the subsidiary(ies).", "Process_Group": "General Ledger", "Scope": "It involves using data from the trial balance. The trial balance is extracted from the general ledger, which is a complete record of all individual accounts. Accounting policies and data format in preparing financial statements must match on group level.", "Outcome": "Realized profit or loss and financial strength of the parent company are revealed without inter-company eliminations.", "GUID": "c7087261-bd00-11e9-0cfc-001bc641ce4f", "name": "Capture financial statements data of parent company for consolidation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.944354864422015, "y": -1.893687707641196, "z": 0.6648794653998469 }, "color": "#66CCFF", "size": 1.0 }, { "id": "57", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose is to report the consolidated data in a single currency provided there are different functional currencies among the companies. The single currency is the groups currency.", "Process_Group": "General Ledger", "Scope": "Translate all local currencies into group currency by using the appropriate translation method for a particular group item.Translation methods are based on either spot or historical exchange rates. For example, an asset acquired at an earlier date must be converted using the exchange rate (historical) as at the date of acquisition.", "Outcome": "All financial data for parent company and subsidiaries are available in one single currency", "GUID": "c7087272-bd00-11e9-0cfc-001bc641ce4f", "name": "Perform foreign currency translation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.926039294541732, "y": -1.8903654485049834, "z": 0.8568178736644076 }, "color": "#66CCFF", "size": 1.0 }, { "id": "58", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The consolidated balance sheet provides true and fair net worth or value of both the parent company and the subsidiary(ies) as a single entity. It shows the value of what the group owes and owns as at a particular reporting date.", "Process_Group": "Finance Reporting and Analytics", "Scope": "The consolidated balance sheet is generated by combining balance sheet data of the parent company and its subsidiary(ies) on a line by line basis. Like items of assets, liabilities and equities are consolidated after intragroup eliminations and adjustments have been accounted for.", "Outcome": "The aggregated value of the groups assets, liabilities and equity is computed. There are no distinctions on which items belong to a specific legal entities within the group.", "GUID": "c7087283-bd00-11e9-0cfc-001bc641ce4f", "name": "Generate consolidated balance sheet", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.905801025458697, "y": -1.8870431893687707, "z": 1.0590156975659073 }, "color": "#66CCFF", "size": 1.0 }, { "id": "59", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose is to provide true and fair value of either a net profit or loss of both the parent company and the subsidiary(ies) as a single entity. It gives the general breakdown of consolidated revenue, income and expenses that have been accounted for the reporting date.", "Process_Group": "Finance Reporting and Analytics", "Scope": "The consolidated P&L statement is generated by combining on a line by line basis the revenue, income, and expenses on the parent company and its subsidiary(ies) respective P&L statements after intragroup eliminations and adjustments have been accounted for. A reconciliation of profit share for the group and non-controlling interests are included in the consolidated P&L statement.", "Outcome": "The aggregated value of net profit or loss for the reporting period is computed with an indication of the profit share attributable to the group and the individual subsidiaries.", "GUID": "c7087287-bd00-11e9-0cfc-001bc641ce4f", "name": "Generate consolidated Profit & Loss statement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9667313536589321, "y": -1.8837209302325582, "z": 0.3632737019588729 }, "color": "#66CCFF", "size": 1.0 }, { "id": "60", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Data harmonization describes the process of merging parent companys and subsidiaries data to create a standardised and comparable data for group reporting. ", "Process_Group": "General Ledger", "Scope": "Data is harmonised into one common format appropriate for reporting at group level.", "Outcome": "Parent company and subsidiary data have been harmonized.", "GUID": "18962e27-4be9-11ea-0cfc-001bc641ce4f", "name": "Harmonize and aggregate data for consolidation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.94721320635123, "y": -1.8803986710963456, "z": 0.5602984171929296 }, "color": "#66CCFF", "size": 1.0 }, { "id": "61", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that financial statements data of subsidiaries meet the requirements for group level consolidation. Typically, the parent company provides subsidiaries with a consolidation package for capturing the financial statements data used for consolidation. ", "Process_Group": "General Ledger", "Scope": "Ensure that business transactions involving several companies within the group are correctly maintained and up to date. Reporting data from individual financial statements of subsidiary must be adapted so that it easily links to the consolidation system used by the parent company. ", "Outcome": "Financial statement data of subsidiary is ready for approval by group controller", "GUID": "db2aa629-b79b-11e9-0cfc-001bc641ce4f", "name": "Prepare financial statements data for consolidation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9256654918065164, "y": -1.8770764119601329, "z": 0.767561363305569 }, "color": "#66CCFF", "size": 1.0 }, { "id": "67", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Perform primary cost planning ,\n Perform overhead cost planning ,\n Perform allocation to production cost center,\n Select applicable controlling area for planning,\n Define and update cost elements and activity inputs as required,\n Determine overhead absorption rates,\n Perform activity rate planning", "Type": "Business Process", "Description": "Cost center planning forms part of the overall business planning process. It enables to perform detailed planning below the cost element level.", "hasAssignment": true, "Process_Group": "Overhead Cost Controlling", "Scope": "Cost center planning involves entering planned figures for costs, activities, prices or statistical key figures for a particular cost center and a particular planning period.", "Outcome": "Cost center planning figure is available for planning period.", "GUID": "b4b3673c-9562-11e8-2ddf-001bc640cd9b", "name": "Perform cost center planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.902008081203795, "y": -1.8737541528239203, "z": 0.9850465835749513 }, "color": "#66CCFF", "size": 1.0 }, { "id": "69", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Execute capacity planning,\n Define production line shift schedules,\n Define activity type and rate,\n Define normal production capacity,\n Perform routing master data maintenance,\n Maintain routing using standard values,\n Maintain parameters for planned production orders,\n Execute parameters for planned production orders ", "Type": "Business Process", "Description": "In addition to the activity rate calculations, cost centers must also be budgeted.", "Process_Group": "Overhead Cost Controlling", "hasAssignment": true, "Scope": "This process involves the budgeting for estimated labour hours, machine hours or any other relevant activity type that will be a required resource for the achievement of periodic goals and targets (production targets etc. )", "Outcome": "Capacity planning figures available for each production cost center.", "GUID": "c7c0ffd9-9565-11e8-2ddf-001bc640cd9b", "name": "Perform capacity planning on the production cost center", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.8761609577199465, "y": -1.8704318936877076, "z": 1.2127375639303808 }, "color": "#66CCFF", "size": 1.0 }, { "id": "71", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify that costs are correctly maintained in Controlling,\n Distribute costs to production related cost centers,\n Allocate costs to production related cost centers,\n Allocate cost via appropriate cost element", "Type": "Business Process", "Description": "This represents an allocation, distribution and application of settlement rules for production or project related costs which have been incurred for a given period to the correct production cost center.", "Process_Group": "Overhead Cost Controlling", "hasAssignment": true, "Scope": "Once the budgetary planning has taken place, this must subsequently be allocated to the various cost centers within the company code or group organisational structure.", "Outcome": "Cost center planning figures allocation to cost centers is correct and completed.", "GUID": "c7c0ffd7-9565-11e8-2ddf-001bc640cd9b", "name": "Distribute and allocate costs to production related cost centers", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.956584062903971, "y": -1.867109634551495, "z": 0.41446206676870845 }, "color": "#66CCFF", "size": 1.0 }, { "id": "75", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Analyse incomplete production orders ,\n Transfer to finished inventory,\n Transfer to semi-finished inventory ,\n Calculate work in progress", "Type": "Business Process", "Description": "WIP refers to the raw materials, labor, and overhead costs incurred for products that are at various stages of the production process. WIP is a component of the inventory asset account on the balance sheet. These costs are subsequently transferred to the finished goods account and eventually to cost of sales.", "Process_Group": "Product Cost Controlling", "hasAssignment": true, "Scope": "When production orders have not been completed in the accounting time period when it was generated, there needs to be a calculation to accurately reflect the companys balance sheet position at that point in time.", "Outcome": "WIP calculations are reflected at the line item level of the balance sheet.", "GUID": "768b35d6-d4a1-11eb-2c3e-001bc641ce4f", "name": "Calculate work in progress (WIP)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9315917824772977, "y": -1.8637873754152823, "z": 0.6370004873715409 }, "color": "#66CCFF", "size": 1.0 }, { "id": "77", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Match planned orders against actual production orders ,\n Execute variance analysis,\n Analyze planned production orders,\n Generate report on variances to be settled,\n Perform analysis on production orders with variances,\n Investigate the cause of the variance,\n Prepare production order variances for settlement", "Type": "Business Process", "Description": "Variance calculation provides the difference between Actual Costs and Target Costs posted on order.", "Process_Group": "Product Cost Controlling", "hasAssignment": true, "Scope": "This process covers the analysis of price variances stemming from the manufacturing process which can include: ***Total Variance ***Variance ***Planning Variance", "Outcome": "Product price variances determined and follow up actions initiated.", "GUID": "b4b36753-9562-11e8-2ddf-001bc640cd9b", "name": "Conduct variance analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9043035102237087, "y": -1.8604651162790697, "z": 0.8697207023262279 }, "color": "#66CCFF", "size": 1.0 }, { "id": "79", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Settle variances to finance and COPA,\n Perform settlement to controlling objects,\n Perform manual settlement to controlling objects", "Type": "Business Process", "Description": "During production, product cost collectors and manufacturing orders are debited with actual costs. Each time goods are received into inventory, ERP systems evaluate the goods receipt and credit it to the defined product cost collector or production order accordingly.", "hasAssignment": true, "Process_Group": "Product Cost Controlling", "Scope": "The actual costs posted to an order can be higher or lower than the value of the initial production order which was credited when the goods receipt was posted. This must be settled by the difference between the debit and credit of the order which is subsequently transferred to Financial Accounting.", "Outcome": "All differences are settled.", "GUID": "b4b36755-9562-11e8-2ddf-001bc640cd9b", "name": "Settle differences via product cost collectors", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.874639560909118, "y": -1.8571428571428572, "z": 1.112604669781572 }, "color": "#66CCFF", "size": 1.0 }, { "id": "81", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Select materials for costing run ,\n Execute BOM for costing run ,\n Execute costing run ,\n Perform analysis of costing run ,\n Perform update of prices ", "Type": "Business Process", "Description": "This process involves the periodic costing of a sizeable number of products/ materials (for example all materials of one plant).", "Process_Group": "Product Cost Controlling", "hasAssignment": true, "Scope": "With help of the costing run, the high-performing costing of a great number of materials per collective processing is possible (often at plant level).", "Outcome": "A standard price is derived for the product and release to the material master.", "name": "Execute product costing run", "GUID": "b4b3674e-9562-11e8-2ddf-001bc640cd9b", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.842520375800422, "y": -1.8538205980066444, "z": 1.3656337936492675 }, "color": "#66CCFF", "size": 1.0 }, { "id": "83", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain link between activity type,\n cost and work center ,\n Execute quantity structure via costing run,\n Maintain existing costing variant for material,\n Select the applicable entity or plant for costing,\n Establish BOM and routing prioritization,\n Define and maintain costing variant for material ", "Type": "Business Process", "Description": "The cost estimate with quantity structure enables you to calculate the non-order-related cost of goods manufactured and the cost of goods sold for products, based on the BOMs and routings (PP).", "Process_Group": "Product Cost Controlling", "hasAssignment": true, "Scope": "Quantity structure to be established on planned production orders with the relevant BOM and routing master data maintained.", "Outcome": "The quantity structure is maintained and correctly connected to planned production orders.", "GUID": "b4b36749-9562-11e8-2ddf-001bc640cd9b", "name": "Establish quantity structure based on BOM and routing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9451047217940511, "y": -1.850498338870432, "z": 0.4653682641247537 }, "color": "#66CCFF", "size": 1.0 }, { "id": "85", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Plan cost center allocations ,\n Execute plan cost center splitting ,\n Calculate activity type rates ,\n Execute activity type rate calculation ,\n Select applicable controlling area,\n Select applicable activity type for processing,\n Apply activity type allocation rules as per planning,\n Plan individual activity type to cost center allocations,\n Perform collective processing of activity rates,\n Perform individual processing of activity rates", "Type": "Business Process", "Description": "Activity Rates define or rather calculate the cost of performing an activity type.", "hasAssignment": true, "Process_Group": "Overhead Cost Controlling", "Scope": "Perform activity rate calculation in order to calculate plan activity rates for activities in each production cost center.", "Outcome": "Plan activity rates are available for each activity in each cost center in a plant.", "GUID": "b4b36743-9562-11e8-2ddf-001bc640cd9b", "name": "Perform activity rate calculation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.913974519043757, "y": -1.8471760797342194, "z": 0.7132688850382477 }, "color": "#66CCFF", "size": 1.0 }, { "id": "89", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Define settlement receiver(s),\n Define settlement cycle,\n Check posting rule for internal order,\n Determine allocation structure,\n Complete actual cost postings,\n Close internal order,\n Settle costs of internal order", "Type": "Business Process", "Description": "Settlement of costs posted in internal orders refers to the process of allocating actual costs to the respective cost receivers at the end of a period. Only real internal orders are settled. ", "Process_Group": "Overhead Cost Controlling", "hasAssignment": true, "Scope": "Includes the steps for: - Completion confirmation - Technical completion - Settlement of costs - Business completion", "Outcome": "All costs are correctly settled to cost objects", "GUID": "f5d9ad6b-b096-11ed-3781-0201b014c5b2", "name": "Settle actual costs to cost receivers", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.8802834629971787, "y": -1.8438538205980066, "z": 0.9712879319700327 }, "color": "#66CCFF", "size": 1.0 }, { "id": "91", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check posting rule for internal order,\n Post actual cost to internal order,\n Verify source documents (invoices,\n time sheets,\n expense reports),\n Post actual cost to cost receiver,\n Request complete documents", "Type": "Business Process", "Description": "The process tracks and ensures that the actual costs incurred from the project or activities are correctly captured in the internal order.", "hasAssignment": true, "Process_Group": "Overhead Cost Controlling", "Scope": "The system uses this cost element category to post actual costs when they are incurred. ", "Outcome": "Actual costs are posted to cost objects", "GUID": "f5d9ad68-b096-11ed-3781-0201b014c5b2", "name": "Perform actual cost posting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.843952366257169, "y": -1.840531561461794, "z": 1.2394052902225194 }, "color": "#66CCFF", "size": 1.0 }, { "id": "93", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Define cost elements for WBS,\n Assign cost elements to cost center,\n Develop cost estimate for cost elements,\n Approve cost budget,\n Capture cost budget in internal order,\n Create cost budget,\n Revise cost budget,\n Prepare work breakdown structure (WBS)", "Type": "Business Process", "Description": "This process allows planning of costs by total costs and as well as by corresponding total consumption. ", "hasAssignment": true, "Process_Group": "Overhead Cost Controlling", "Scope": "Typically, detailed cost planning occurs annually and covers cost-element-based planning using primary costs, revenues, and order costs. ", "Outcome": "Cost element planning figures are available for use.", "GUID": "f5d9ad62-b096-11ed-3781-0201b014c5b2", "name": "Perform cost element planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.804902182344551, "y": -1.8372093023255813, "z": 1.5176002943500844 }, "color": "#66CCFF", "size": 1.0 }, { "id": "95", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Define order type,\n Maintain company code,\n Define controlling area,\n Assign responsible cost center,\n Determine validity period,\n Define business area,\n Define posting rules", "Type": "Business Process", "Description": "Before costs for internal jobs can be pooled and analyzed, it is necessary to create and maintain the type of internal order in the system. Type of internal order includes overhead cost orders, accrual orders, investment orders, and orders with revenue. ", "Process_Group": "Overhead Cost Controlling", "hasAssignment": true, "Scope": "In creating the internal order, posting rules and controlling area must be defined and maintained. Posting rules are necessary because an internal order can be either real or statistical. ", "Outcome": "Internal order is created and saved in the system.", "GUID": "f5d9ad60-b096-11ed-3781-0201b014c5b2", "name": "Create internal order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.932301145511096, "y": -1.8338870431893688, "z": 0.5159576368816586 }, "color": "#66CCFF", "size": 1.0 }, { "id": "99", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is used to finalize and allocate the costs associated with a specific production order to appropriate cost centers or accounts.", "Process_Group": "Product Cost Controlling", "Scope": "This begins with capturing costs like raw materials and labor, calculating the total cost for a production order, and then distributing these costs according to accounting rules.", "Outcome": "All costs related to production orders are settled to the respective receiving accounts.", "GUID": "9345f148-56c3-11ee-3781-0201b014c5b2", "name": "Settle production orders", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.8943734099549108, "y": -1.830564784053156, "z": 0.7890516863590014 }, "color": "#66CCFF", "size": 1.0 }, { "id": "100", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Apply settlement rules,\n Settle variances to finance and COPA,\n Settle production cost center variances ,\n Match planned orders against actual production orders ,\n Execute variance analysis,\n Analyze planned production orders,\n Generate report on variances to be settled,\n Perform analysis on production orders with variances,\n Investigate the cause of the variance,\n Prepare production order variances for settlement", "Type": "Business Process", "Description": "Once the difference between planned and actual production/ process orders have been calculated, it is required that there is an accompanying settling of the differences which according to the allocation rules defined must be settled through a cost collector, controlling object or a cost center.", "hasAssignment": true, "Process_Group": "Product Cost Controlling", "Scope": "Once the difference between planned and actual production/ process orders have been calculated, it is required that there is an accompanying settling of the differences which according to the allocation rules defined must be settled through a cost collector, controlling object or a cost center.", "Outcome": "All cost differences from production are settled.", "GUID": "c7c0ffc2-9565-11e8-2ddf-001bc640cd9b", "name": "Perform and settle variances", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.8536217030723687, "y": -1.8272425249169435, "z": 1.0721939048556548 }, "color": "#66CCFF", "size": 1.0 }, { "id": "102", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Define valuation methods (WIP),\n Define valuation variant for WIP and scrap,\n Apply cost elements for WIP calculation ,\n Apply posting rules for the settlement of WIP,\n Analyze technically incomplete production orders,\n Calculate work in progress per entity,\n Calculate work in progress per production order,\n Material consumption posting", "Type": "Business Process", "Description": "The WIP calculation function evaluates the unfinished products (work in process) in an accounting period.", "Process_Group": "Product Cost Controlling", "hasAssignment": true, "Scope": "In the Product Cost by Order component, the work in process is evaluated at actual cost. Work in progress is the difference between the debit and credit of a production or process order that has not been fully completed. WIP can be calculated at actual costs for the following objects: ***Production orders ***Process orders", "Outcome": "WIP values from production/ process orders are posted.", "GUID": "c7c0ffb9-9565-11e8-2ddf-001bc640cd9b", "name": "Post work in progress (WIP) values", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.809967389214364, "y": -1.823920265780731, "z": 1.365362118521805 }, "color": "#66CCFF", "size": 1.0 }, { "id": "104", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Settle production order against controlling objects,\n Transfer values to profitability analysis,\n Adjust the assignment to correct settlement rule (manually),\n Apply settlement rules to appropriate controlling object", "Type": "Business Process", "Description": "The production order is commercially closed when all the costs have been booked completely.", "hasAssignment": true, "Process_Group": "Product Cost Controlling", "Scope": "The production order is set to status closed. With this - no more costs can be posted to the order, that is, confirmations and goods movements are no longer permitted for the order and the order can no longer be changed.", "Outcome": "Production order is closed commercially.", "GUID": "c7c0ffc4-9565-11e8-2ddf-001bc640cd9b", "name": "Close production order commercially", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.763331987970807, "y": -1.8205980066445182, "z": 1.668533606623631 }, "color": "#66CCFF", "size": 1.0 }, { "id": "109", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check existing contra entries,\n Check existing goods receipt/ invoice receipt for differences,\n Settle goods receipt/ invoice receipt differences,\n Post cleared invoice", "Type": "Business Process", "Description": "Conduct clearing AP refers to the offsetting of outgoing vendor payments against outstanding amounts owed to creditors.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "Open items on vendors account are cleared when the vendor is paid. This can be manually or automatically performed. Clearing open items on vendors account decreases the total amount owed to the vendor", "Outcome": "Vendor account is cleared.", "GUID": "981573d8-9499-11e8-2ddf-001bc640cd9b", "name": "Conduct clearing AP", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.918182050781699, "y": -1.8172757475083057, "z": 0.5661957435895436 }, "color": "#66CCFF", "size": 1.0 }, { "id": "111", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check goods receipt against invoice receipt ,\n Post verified invoice to ERP system", "Type": "Business Process", "Description": "After verification the invoiced amount must be posted accordingly.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "Confirmation is given that the invoiced amounts correspond with the inbound delivery and has a corresponding goods receipt posting which also matches with the invoiced quantities and amounts.", "Outcome": "Posting of invoice complete and correct.", "GUID": "981573d6-9499-11e8-2ddf-001bc640cd9b", "name": "Post verified invoice", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.872801799725218, "y": -1.8139534883720931, "z": 0.8642972980957128 }, "color": "#66CCFF", "size": 1.0 }, { "id": "113", "text": "Process", "data": { "Advisory_Notes": "The methods of payment must be established taking into account country specific factors.", "KeyActivities": "Maintain general parameters,\n Check if manual payment or payment run is required,\n Post outgoing payment manually,\n Import and post electronic bank statement,\n Select required open items,\n Generate proposal list for payment run,\n Approve proposal list for payment run,\n Execute payment program,\n Generate and forward DME file to bank,\n Collect all cheques for the day and sent them to the post,\n Approve and release all cheques in batches", "Type": "Business Process", "Description": "This process ensures that a payment to a vendor is captured, executed, and documented accordingly.", "hasAssignment": true, "Process_Group": "Accounts Payable", "Scope": "Manage outgoing payment involves making a payment to a vendor and posting the payment to the relevant vendor account.", "Outcome": "The outgoing payment is executed and the account vendor debited.", "GUID": "a717a132-d4a8-11eb-2c3e-001bc641ce4f", "name": "Manage outgoing vendor payment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.824336381883426, "y": -1.8106312292358804, "z": 1.1723699237880447 }, "color": "#66CCFF", "size": 1.0 }, { "id": "117", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This indicates the intention of the seller to pass credit or debit to customer.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "Information about material, price, quantity and reason for requesting credit or debit memo is defined. The request can be created with reference to either sales order or billing document.", "Outcome": "Credit or debit memo request related to Accounts Receivable created.", "GUID": "d38e824a-8d31-11ee-3781-0201b014c5b2", "name": "Create customer credit / debit memo request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.772707766890726, "y": -1.8073089700996678, "z": 1.490389402760549 }, "color": "#66CCFF", "size": 1.0 }, { "id": "118", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Once the credit or debit memo request is created it has to be approved before the billing block can be removed.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "Based on a workflow that defines different values to be approved by responsible roles, the request to process credit or debit memo is approved or rejected. If the request is rejected, the reason for rejection should be provided.", "Outcome": "Credit or debit memo request related to Accounts Receivable approved.", "GUID": "d38e824c-8d31-11ee-3781-0201b014c5b2", "name": "Approve customer credit /debit memo request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.717838093835896, "y": -1.803986710963455, "z": 1.8183309744595717 }, "color": "#66CCFF", "size": 1.0 }, { "id": "119", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Once the request is approved, the billing block is removed making it possible for the credit or debit memo document to be created.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "If the request is accepted, the system automatically removes the billing block but if the request is rejected the billing block is not removed.", "Outcome": "Billing block removed.", "GUID": "d38e824e-8d31-11ee-3781-0201b014c5b2", "name": "Remove billing block", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9027570499427389, "y": -1.8006644518272426, "z": 0.6160483819418777 }, "color": "#66CCFF", "size": 1.0 }, { "id": "120", "text": "Process", "data": { "Advisory_Notes": "Especially in global projects different variants of payments have to be considered but their use should often be limited to a group of countries rather than being made available to all.", "KeyActivities": "Post incoming down payment,\n Post incoming payment,\n Check incoming payment,\n Forward DME to bank,\n Create data medium exchange (DME) file,\n Assign payment to open customer items and clear payment,\n Execute payment program", "Type": "Business Process", "Description": "Manage incoming payment process ensures that the payment from a customer is captured and documented appropriately.", "hasAssignment": true, "Process_Group": "Accounts Receivable", "Scope": "Manage incoming payment involves receiving a payment from a customer and entering the information in accounting. The incoming payment is mapped to the customer invoice and customer account.", "Outcome": "Incoming payment is recorded and the customer account is credited.", "GUID": "768b35e0-d4a1-11eb-2c3e-001bc641ce4f", "name": "Manage incoming customer payments", "Business_Rules": "The methods of payment must be established taking into account country specific factors related to the business and customer. For instance: The bill of exchange (BoE) payment method is used in some countries only. Typical methods of payment are: ***Check ***Direct debits ***Credit cards ***Bank transfers", "Prerequisite": "Prerequisite: currency exchange and hedging processes" }, "position": { "x": 2.849274374394297, "y": -1.7973421926910298, "z": 0.938954492731137 }, "color": "#66CCFF", "size": 1.0 }, { "id": "122", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Receive request for pay out,\n Analyse refund claim,\n Decide on settlement of refund,\n Settle customer account,\n Release refund payment to customer,\n Maintain customer account", "Type": "Business Process", "Description": "This refers to the accompanying process step which is triggered by a warranty claim or a customer return which will be honored and refunded.", "hasAssignment": true, "Process_Group": "Accounts Receivable", "Scope": "An assessment is conducted whether a payment should be given to the customer based on a warranty claim or customer return.", "Outcome": "The warranty claim decision is made with the decision to issue a refund or credit note to the customer.", "GUID": "e7fef697-5db5-11e8-2ddf-001bc640cd9b", "name": "Manage outgoing customer payments", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.792447436995633, "y": -1.7940199335548173, "z": 1.2717477885277615 }, "color": "#66CCFF", "size": 1.0 }, { "id": "124", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create credit or debit memo,\n Send credit or debit memo to customer,\n Create accounting document,\n Execute account determination,\n Determine and check corresponding business partners,\n Accounts receivable posting (credit memo),\n Accounts receivable posting (debit memo)", "Type": "Business Process", "Description": "Credit or debit memo is created based on credit or debit memo requests. Credit or debit memo can be quantity related or value related.", "Process_Group": "Billing, Rebates and Commissions", "hasAssignment": true, "Scope": "Once the decision is made to compensate a customer or request additional payment from a customer, the credit or debit memo is created. The appropriate sales tax is also calculated along with any shipping charges that are being credited or debited to the customer based on the date of the original sales transaction. In case multiple credit or debit memos are to be created, this can be done using a batch job.", "Outcome": "Credit or debit memo is created and sent to the customer.", "GUID": "d38e8257-8d31-11ee-3781-0201b014c5b2", "name": "Create customer credit / debit memo", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.732198865788046, "y": -1.7906976744186047, "z": 1.6144020238572312 }, "color": "#66CCFF", "size": 1.0 }, { "id": "128", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare and sort incoming invoices,\n Scan and interpret invoices,\n Verify invoices,\n Approve invoice ,\n Transfer to ERP system", "Type": "Business Process", "Description": "This process covers the scanning of a Purchase Order based invoice or an Expense Invoice (no PO reference).", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "After the invoice is received, it is scanned and the data is captured. The data is then stored in a database for digital use and then transferred to for verification.", "Outcome": "Received invoice information is transferred for verification.", "GUID": "981573d2-9499-11e8-2ddf-001bc640cd9b", "name": "Scan incoming invoice", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.66845147236721, "y": -1.787375415282392, "z": 1.9668904152031463 }, "color": "#66CCFF", "size": 1.0 }, { "id": "130", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create manual invoice entry in ERP system,\n Verify receipt of product or service,\n Assign invoice to cost center responsible,\n Post invoice to ERP system,\n Block invoice from payment,\n Trigger alignment with vendor", "Type": "Business Process", "Description": "Processing of an Expense Invoice from a vendor, in order to trigger the outgoing payment process. Such invoices have no reference to a Purchase Order.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "After the FI invoice has been transferred (from the scanning tool), verification involves checking for formal compliance and whether it is consistent with goods delivered or services provided.", "Outcome": "FI invoice is verified and ready for posting.", "GUID": "be50c2f0-9556-11e8-2ddf-001bc640cd9b", "name": "Process incoming invoice without reference to PO", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8860366443972647, "y": -1.7840531561461794, "z": 0.6654816120605479 }, "color": "#66CCFF", "size": 1.0 }, { "id": "134", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check against existing contra entries ,\n Check the debtors aging report,\n Perform clearing for invoiced amounts", "Type": "Business Process", "Description": "Conduct clearing AR refers to the offsetting of incoming customer payments against outstanding amounts owed by debtors. This clearing process results in a decrease in the total accounts receivable which will be reported in the balance as at that given point in time.", "Process_Group": "Accounts Receivable", "hasAssignment": true, "Scope": "This involves the clearing of open items on customers account by matching payments to the right open items. This can be a manual or automatic process.", "Outcome": "The amounts owed are cleared with no differences outstanding against the initial customer order.", "GUID": "e7fef685-5db5-11e8-2ddf-001bc640cd9b", "name": "Conduct clearing AR (Accounts Receivable)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.8238071515286087, "y": -1.780730897009967, "z": 1.0129724433447755 }, "color": "#66CCFF", "size": 1.0 }, { "id": "138", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Once the credit or debit memo request is created it has to be approved.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "Based on a workflow that defines different values to be approved by responsible roles, the request to process credit or debit memo is approved or rejected. If the request is rejected, the reason for rejection should be provided.", "Outcome": "Credit or debit memo request related to Accounts Payable approved.", "GUID": "6a80cb44-8d36-11ee-3781-0201b014c5b2", "name": "Approve credit /debit memo request AP", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.757976578531833, "y": -1.7774086378737541, "z": 1.3702598422219707 }, "color": "#66CCFF", "size": 1.0 }, { "id": "139", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create credit or debit memo,\n Send credit or debit memo to vendor,\n Create accounting document,\n Execute account determination,\n Determine and check corresponding business partners,\n Accounts payable posting (credit memo),\n Accounts payable posting (debit memo)", "Type": "Business Process", "Description": "Credit or debit memo is created based on credit or debit memo requests. Credit or debit memo can be quantity related or value related.", "Process_Group": "Billing, Rebates and Commissions", "hasAssignment": true, "Scope": "Once the decision is made to demand credit or make additional payments credit or debit memo is created. It can be created with reference to purchase order or invoice.", "Outcome": "Credit or debit memo is created and sent to vendor.", "GUID": "6a80cb46-8d36-11ee-3781-0201b014c5b2", "name": "Create credit / debit memo AP", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.688468264530276, "y": -1.7740863787375416, "z": 1.7373155535171092 }, "color": "#66CCFF", "size": 1.0 }, { "id": "141", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This indicates the intention of the company to request for credit or debit from the vendor.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "Information about material, price, quantity and reason for requesting credit or debit memo is defined. The request can be created with reference to either purchase order or billing document.", "Outcome": "Credit or debit memo request related to Accounts Payable created.", "GUID": "6a80cb42-8d36-11ee-3781-0201b014c5b2", "name": "Create vendor credit / debit memo request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.615205746176684, "y": -1.7707641196013288, "z": 2.114110788985372 }, "color": "#66CCFF", "size": 1.0 }, { "id": "142", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When purchased goods are returned to a vendor or the company is not satisfied with the quality of service rendered by the vendor, the vendor may compensate the company by refunding some amount depending on the agreement. In this case the payment details from the vendor is correctly captured and documented.", "Process_Group": "Accounts Payable", "Scope": "Manage incoming vendor payment involves receiving a payment from a vendor and entering the information in accounting. The incoming payment is mapped to the vendor account.", "Outcome": "The incoming payment is documented and the AP account is debited.", "GUID": "6a80cb48-8d36-11ee-3781-0201b014c5b2", "name": "Manage incoming vendor payment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.868032217465096, "y": -1.7674418604651163, "z": 0.7144617796022655 }, "color": "#66CCFF", "size": 1.0 }, { "id": "145", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Post invoice in accounts receivable,\n Capture invoice data in FI,\n Post invoice in accounts payable", "Type": "Business Process", "Description": "When a sales transaction occurs between two entities from the same parent company, invoices generated from such transaction must be processed to reflect receivable in the selling entity and payable in the purchasing entity.", "Process_Group": "Billing, Rebates and Commissions", "hasAssignment": true, "Scope": "The intercompany invoice must be captured and documented accordingly in the accounting system. The invoice is mapped to business transactions performed in purchasing and sales.", "Outcome": "Incoming intercompany invoice is posted.", "GUID": "837a78be-7eff-11e5-0a66-001bc640cd9b", "name": "Manage intercompany invoice", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.796417469316632, "y": -1.7641196013289036, "z": 1.086300758216049 }, "color": "#66CCFF", "size": 1.0 }, { "id": "147", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify open liabilities from intercompany transactions,\n Reconcile open balances,\n Clear open liabilities", "Type": "Business Process", "Description": "When transactions occur between two related legal entities in an intercompany organization or between two groups in the same legal entity, the resulting balances from these transactions must be eliminated or appropriately adjusted during the preparation of the organizations consolidated financial statements. In such cases only the open balances are settled with actual payments. It must be ensured that open items in both legal entities are closed in the same way.", "hasAssignment": true, "Scope": "Any open liabilities arising from intercompany transactions between two related legal entities are cleared and resulting open balances balances reconciled and settled by making actual payments.", "Process_Group": "Intercompany", "Outcome": "Intercompany balances are cleared and recorded in accounting.", "GUID": "a99fac28-7e52-11e5-0a66-001bc640cd9b", "name": "Clear intercompany balance", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.720947274392087, "y": -1.760797342192691, "z": 1.467839017465505 }, "color": "#66CCFF", "size": 1.0 }, { "id": "152", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Compare failed IDOCs with PDFs ,\n Report findings for further analysis", "Type": "Business Process", "Description": "Once the failed IDOC invoices are identified, they must be compared with a PDF version of the invoice.", "hasAssignment": true, "Process_Group": "Accounts Receivable", "Scope": "As a second quality check the accounts receivable clerk will compare the failed IDOC against the automatically generated pdf file which was created at invoice creation.", "Outcome": "Comparison of incoming IDOC with PDF has been executed.", "GUID": "fccd2e76-9569-11e8-2ddf-001bc640cd9b", "name": "Compare incoming IDOCs with PDFs", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.641545735087877, "y": -1.7574750830564785, "z": 1.8590463117113423 }, "color": "#66CCFF", "size": 1.0 }, { "id": "154", "text": "Process", "data": { "Advisory_Notes": "Typically there are special calculation rules to determine the profit margin in intercompany transactions.", "KeyActivities": "Generate customer invoice based on billing plan,\n Maintain billing sales area,\n Select item to be billed and post the invoice,\n Print invoice,\n Post invoice via EDI,\n Display billing due list,\n Post corrected invoice via EDI,\n Accounts receivable posting,\n Revenue posting,\n Accounts payable posting", "Type": "Business Process", "Description": "The creation of an intercompany invoice initiates the payment process for a transaction between two entities from the same corporate group.", "Process_Group": "Billing, Rebates and Commissions", "hasAssignment": true, "Scope": "The intercompany invoice, with which the supplier entity bills the selling or receiving entity, is created. In the case of a direct delivery to a customer, this happens automatically at the same time when the customer invoice is created. The required accounting entries are created using information from this invoice.", "Outcome": "Intercompany invoice is created and issued.", "GUID": "53da3f54-e8c9-11e4-0a66-001bc640cd9b", "name": "Create intercompany invoice", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.558137165170373, "y": -1.7541528239202657, "z": 2.2598918675794772 }, "color": "#66CCFF", "size": 1.0 }, { "id": "156", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Reference accounts payable line item to vendor,\n Block invoice from payment,\n Post open item accounts payable,\n Review changes on vendor line item balances,\n Trigger alignment with vendor", "Type": "Business Process", "Description": "After receiving the accounts payable open item, the person responsible for processing accounts payable must process the outgoing payment.", "hasAssignment": true, "Process_Group": "Accounts Payable", "Scope": "Once there are open items to be paid the Accounts receivable department ensures that the invoice has been applied to the correct reconciliation account.", "Outcome": "A task list is generated to be utilised during invoice verification.", "GUID": "80843c13-9567-11e8-2ddf-001bc640cd9b", "name": "Process open items accounts payable", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8487560266330132, "y": -1.7508305647840532, "z": 0.7629555386705792 }, "color": "#66CCFF", "size": 1.0 }, { "id": "158", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Confirm IDOCs received,\n Track failed IDOCS", "Type": "Business Process", "Description": "This process involves the tracking of failed IDOCS and the generation of reports for the failed IDOCs.", "Process_Group": "Accounts Receivable", "hasAssignment": true, "Scope": "Conduct timely checks to ensures that all failed Inter-company IDOC invoices are identified for analysis.", "Outcome": "List of failed IDOC invoices are ready for analysis.", "GUID": "fccd2e74-9569-11e8-2ddf-001bc640cd9b", "name": "Monitor IDOCS", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.767123974764956, "y": -1.7475083056478407, "z": 1.1588895151311844 }, "color": "#66CCFF", "size": 1.0 }, { "id": "160", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Reference accounts payable line item to vendor,\n Automatic posting of accounts payable open items", "Type": "Business Process", "Description": "Once the adjusted IDOCS are generated, the system automatically posts the contra entry open item from the selling entitys perspective.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "This particularly useful for: ***Intercompany Replenishment ***Sales via Intercompany", "Outcome": "There is the automatic change in the vendor line items or the amounts owed on the vendors account as a result of the incoming IDOC.", "GUID": "80843c1e-9567-11e8-2ddf-001bc640cd9b", "name": "Post accounts payable open items automatically", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.6813847342766377, "y": -1.744186046511628, "z": 1.5644188819606242 }, "color": "#66CCFF", "size": 1.0 }, { "id": "162", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Analyse IDOC errors,\n Detail required corrections,\n Adjust IDOC segment with errors ", "Type": "Business Process", "Description": "With this process, an analysis is done of all errors generated in the failed IDOC report.", "hasAssignment": true, "Process_Group": "Accounts Receivable", "Scope": "The causes of IDOC errors are identified at this point.All errors are then corrected and the segment type is adjusted.", "Outcome": "The IDOC segment type is adjusted.", "GUID": "fccd2e78-9569-11e8-2ddf-001bc640cd9b", "name": "Analyse IDOC errors and adjust segment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.591463222508946, "y": -1.7408637873754154, "z": 1.979511423646695 }, "color": "#66CCFF", "size": 1.0 }, { "id": "164", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create IC IDOC invoice,\n Generate accompanying PDF file for IDOC", "Type": "Business Process", "Description": "Required re-process the generation and transfer of intercompany invoices via EDI", "Process_Group": "Accounts Receivable", "hasAssignment": true, "Scope": "After adjustments have been made a corrected IDOC is generated with an accompanying PDF file.", "Outcome": "IC invoice transferred EDI.", "GUID": "fccd2e7c-9569-11e8-2ddf-001bc640cd9b", "name": "Re-process IDOCS", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.4972845818693745, "y": -1.7375415282392026, "z": 2.4041344026366853 }, "color": "#66CCFF", "size": 1.0 }, { "id": "170", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review project plan and resource assignments ,\n Release project,\n Release project phase", "Type": "Business Process", "Description": "When all requirements are met, the project is approved, released and communicated to the stakeholders.", "hasAssignment": true, "Process_Group": "Project Management", "Scope": "Project deliverables, plan and resources assignments are reviewed. If all requirements are fulfilled the project is released for execution. It is possible to release the whole project or only a phase of the project.", "Outcome": "The entire project or a project phase is released for execution.", "GUID": "1cdd808a-7ca3-11e5-0a66-001bc640cd9b", "name": "Approve and release project", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8282211952098106, "y": -1.73421926910299, "z": 0.8109298745178966 }, "color": "#66CCFF", "size": 1.0 }, { "id": "172", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Assign personnel resources to project,\n Release WBS element", "Type": "Business Process", "Description": "In a project environment, several personnel resources may be assigned to a work center. In case capacity planning is performed on work center level, and not assigned to a single person a detailed and meaningful reporting will not be possible. Therefore, assigning personnel resources enables capacity planning on personnel level to avoid overwork or to assign personnel with relevant qualification.", "Process_Group": "Project Management", "hasAssignment": true, "Scope": "Once the customer order is created, activities are assigned to personnel resources. To ensure the advanced procurement, the status of a Work Breakdown Structure (WBS) element has to have the status Released.", "Outcome": "Required personnel resources are assigned to project activities.", "GUID": "768b35ba-d4a1-11eb-2c3e-001bc641ce4f", "name": "Assign personnel resources to project", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.735946611003321, "y": -1.7308970099667773, "z": 1.230689295370461 }, "color": "#66CCFF", "size": 1.0 }, { "id": "174", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain resource requirements,\n Maintain material requirements,\n Assign staff to activities,\n Calculate estimated project costs,\n Save project schedule,\n Schedule project,\n ?", "Type": "Business Process", "Description": "In order to ensure execution of the project in a timely manner and the controlling of costs, planning and scheduling of the project must be performed.", "Process_Group": "Project Management", "hasAssignment": true, "Scope": "Scheduling is carried out according to project timelines, milestones and deliverables. The cost of materials and planned labour comes from the project template. This information is incorporated into the project plan.", "Outcome": "Project plan is created and project activities are scheduled.", "GUID": "1cdd8084-7ca3-11e5-0a66-001bc640cd9b", "name": "Plan and schedule project", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.6393158925230393, "y": -1.7275747508305648, "z": 1.6599336837443937 }, "color": "#66CCFF", "size": 1.0 }, { "id": "176", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Structure and document product request data ,\n Forward product request data to R&D engineer,\n Receive and evaluate product request,\n Exchange information with requester,\n Reject request and inform requester", "Type": "Business Process", "Description": "When the internal marketing department sends a request for a new product, the information is recorded and stored. This forms the basis for defining product specifications.", "hasAssignment": true, "Process_Group": "Product Development", "Scope": "Once the marketing department sends the request for a new product, the data is documented, stored and forwarded to the product development department.", "Outcome": "All relevant details regarding the requested product are documented.", "GUID": "1cdd8081-7ca3-11e5-0a66-001bc640cd9b", "name": "Receive and process product request", "Business_Rules": "It is necessary to define how the information will be recorded and forwarded for further evaluation by the product development department.", "Prerequisite": "" }, "position": { "x": 4.538254823170903, "y": -1.7242524916943522, "z": 2.0986288761870306 }, "color": "#66CCFF", "size": 1.0 }, { "id": "178", "text": "Process", "data": { "Advisory_Notes": "For Capital Investment Projects (CAPEX) the Asset master has to be maintained and the relevant asset related information updated on the settlement rule for the project. This is to enable costs to be settled to the asset when settlement is run after technical completion.", "KeyActivities": "Complete project technically", "Type": "Business Process", "Description": "A project is technically complete when the project work is finished but costs are still expected to be incurred. The last activities in the technical project closure are the project evaluation, preparation of the final report, handover and acceptance of the project, discharge of the project members. Within the project handover, a briefing of the employees can be carried out as required.", "Process_Group": "Project Management", "hasAssignment": true, "Scope": "Once all project related activities have been performed and confirmed, the project is completed by setting the project status to technically complete. This prevents further changes to the project.", "Outcome": "The project is technically complete.", "GUID": "1f40c4ed-7ca3-11e5-0a66-001bc640cd9b", "name": "Complete project technically", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.4326894249588795, "y": -1.7209302325581395, "z": 2.54674019325489 }, "color": "#66CCFF", "size": 1.0 }, { "id": "180", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Close portfolio item,\n Complete project commercially", "Type": "Business Process", "Description": "With the commercial completion of the project, no more costs can be allocated to the project. This marks the completion of the project from an accounting/ controlling perspective.", "Process_Group": "Project Accounting", "hasAssignment": true, "Scope": "After all the project activities have been completed and costs are settled, the project is completed commercially and the project portfolio item is closed. Completion of a project will usually be linked to a quality control gate.", "Outcome": "Project is completed.", "GUID": "54e6bc6c-e7fc-11e4-0a66-001bc640cd9b", "name": "Complete project commercially", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8064417033918958, "y": -1.717607973421927, "z": 0.8583521260220576 }, "color": "#66CCFF", "size": 1.0 }, { "id": "182", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain project structure,\n Generate settlement rule,\n Create project for internal use", "Type": "Business Process", "Description": "The project maps the work structure and is the object for collecting costs incurred for the internal work.This allows the capturing of times and expenses incurred on project tasks.", "Process_Group": "Project Management", "hasAssignment": true, "Scope": "The project is created from a standard template. The settlement rule is generated, forming the basis for capturing project related costs.", "Outcome": "Project is created and related costs can be allocated.", "GUID": "400b3f50-9627-11e8-2ddf-001bc640cd9b", "name": "Create internal project", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.7029066037072575, "y": -1.7142857142857144, "z": 1.3016512173526744 }, "color": "#66CCFF", "size": 1.0 }, { "id": "184", "text": "Process", "data": { "Advisory_Notes": "Further implications of a new product introduction should be considered especially from a planning perspective. Cannibalism might reduce demand for similar existing products and demand on component level might change.", "Type": "Business Process", "Description": "After a new product has been successfully developed, it needs to be handed over to the regular operations units.", "Process_Group": "Product Development", "Scope": "The scope of the handover typically includes the knowledge transfer and provision of master data and documentation materials for production and sales. Depending on the type of product it might also include EHS, logistics and warehousing, service and other technical departments.", "Outcome": "Hand-over of responsibility to operational departments", "GUID": "70914ab0-09c8-11e9-2ddf-001bc640cd9b", "name": "Roll out new product", "Business_Rules": "Clear guidelines and sometimes system supported status schema should be defined when various actions such as planning and forecasting, purchasing, price lists, quotations and sales orders, production for new products should be allowed.", "Prerequisite": "" }, "position": { "x": 3.5947693897691533, "y": -1.7109634551495017, "z": 1.754318395952887 }, "color": "#66CCFF", "size": 1.0 }, { "id": "185", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review product specification,\n Forward production request,\n Determine quantity of test product needed", "Type": "Business Process", "Description": "For internal product development, it is necessary to carry out test production based on the product prototype. Information must be passed on to the manufacturing department regarding what needs to be produced and in what quantity.", "hasAssignment": true, "Process_Group": "Product Development", "Scope": "Based on the product specifications, the production department is engaged to manufacture a specific quantity of the new product. The production order is assigned to the project.", "Outcome": "Test production of new product can begin.", "GUID": "1cdd807b-7ca3-11e5-0a66-001bc640cd9b", "name": "Initiate small scale test production", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.48195676156753, "y": -1.707641196013289, "z": 2.2163175736881877 }, "color": "#66CCFF", "size": 1.0 }, { "id": "187", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update CAD document using EasyDM,\n Change material BOM,\n Activate change number,\n Lock engineering change master,\n Assign revision level to header material of new product,\n Change engineering change master (ECM),\n Create standard cost estimate", "Type": "Business Process", "Description": "The product master data offers a single point of reference for information regarding a product. Maintaining the data ensures that all relevant information is available and up-to-date.", "Process_Group": "Material and Product Master Data", "hasAssignment": true, "Scope": "Once designing and prototyping is complete, the new material master and material BOM are created in the backend system. Later, the production scheduling department creates routing as a basis for production and calculation of the product price. To check the price level specified by the marketing department, the product cost controller calculates material costs using the BOM and routing. In case, the estimated price exceeds the specified price limit, a component of the new product BOM is exchanged for a less expensive component using change management. The design department issues an engineering change master to collect and document all changes according the specification document. Following a second costing run (cost estimate), the price meets the budget and the development status of the new product can be fixed by assigning a revision level.", "Outcome": "Cost calculation is complete and product master data updated.", "GUID": "1cdd80a5-7ca3-11e5-0a66-001bc640cd9b", "name": "Maintain product master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.364395671083347, "y": -1.7043189368770764, "z": 2.68761215283423 }, "color": "#66CCFF", "size": 1.0 }, { "id": "189", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check CAD drawings into DMS,\n Create prototype of product with change,\n Create design of product with CAD", "Type": "Business Process", "Description": "Designing and creating a prototype of the product are essential early steps in product development that provide the blueprint from which the final product is derived.", "hasAssignment": true, "Process_Group": "Product Development", "Scope": "The design process is carried out in a CAD system which can be fully integrated into the SAP system. SAP CAD Desktop is used as the central user interface by the design engineer. By linking the CAD system and the CAD Desktop in the SAP system all components designed in the CAD system can be managed. With full CAD integration, the CAD drawings are checked into the document management system (DMS). A document BOM is available in the system. CAD Desktop allows the easy creation of the necessary material masters and material BOM.", "Outcome": "Product is design complete and documented.", "GUID": "1f40c4c4-7ca3-11e5-0a66-001bc640cd9b", "name": "Design and prototype product", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7834323787455135, "y": -1.7009966777408638, "z": 0.9051900079221596 }, "color": "#66CCFF", "size": 1.0 }, { "id": "191", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Maintaining engineering master data provides detailed information about the components, materials, and specifications used in designing the product. ", "Process_Group": "Material and Product Master Data", "Scope": "The engineering master data is created or changed and then activated in relevant destination systems. In addition relevant production and sales teams are informed.", "Outcome": "Engineering master data maintained.", "GUID": "4f7ac66c-4d51-11ee-3781-0201b014c5b2", "name": "Maintain engineering master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.668026446647557, "y": -1.697674418604651, "z": 1.3717269699139154 }, "color": "#66CCFF", "size": 1.0 }, { "id": "194", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Evaluate plan of measures,\n Create and distribute implementation assignments,\n Apply measures,\n Report implementation status", "Type": "Business Process", "Description": "With regard to the prevention of the repeated occurrence of the error, a corrective action is required to eliminate the cause of the error. This should be carried out appropriately to the extent of the error that has occurred. ", "Process_Group": "Quality Management", "hasAssignment": true, "Scope": "The designated action controller of a process/business unit is responsible for recording all actions identified for the processes in the central action plan, evaluating them and assigning their implementation to the respective process owner (who can delegate within his process). The corresponding status update and completion message is sent to the measure controller by the process owner or the delegate.", "Outcome": "Updated plan of measures", "GUID": "255a51c2-9bb7-11ed-3781-0201b014c5b2", "name": "Implement corrective measures", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.5477755534544846, "y": -1.6943521594684385, "z": 1.8475087610917373 }, "color": "#66CCFF", "size": 1.0 }, { "id": "196", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Start work according to new process,\n Report on work performed,\n Analyze current status of change implementation,\n Complete change implementation,\n Create technical information for user documentation,\n Document changes and product data ,\n Confirm completion of change implementation", "Type": "Business Process", "Description": "The development result and the specifications are to be compared. If the result and the specifications do not match, the product development process restarts.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "Work is performed according to the new process. The work done is reported, analyzed before completion of change implementation is confirmed.", "Outcome": "Process change completed.", "GUID": "35a36f71-09d8-11e9-2ddf-001bc640cd9b", "name": "Implement manufacturing process change", "Business_Rules": "Test are done by R&D, AE (application engineering) and customer. Approved by project manager and gate review by EPSC. Documentation mainly done in QSYS. Follow up concerning time line driven by EPSC and project manager.", "Prerequisite": "" }, "position": { "x": 4.422607365647199, "y": -1.691029900332226, "z": 2.3324973932082207 }, "color": "#66CCFF", "size": 1.0 }, { "id": "198", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Approve process request,\n Create process order,\n Evaluate process request,\n Stop process change activities", "Type": "Business Process", "Description": "Approval of the request initiates the planning of required tasks to fulfil process change procedures.", "Process_Group": "Product Development", "hasAssignment": true, "Scope": "Based on impact analysis, process request is evaluated, and approved before process order is created. If approval is not granted, the process change activities are stopped. the ", "Outcome": "Process order created or change request stopped. ", "GUID": "8c36f737-9414-11e9-0cfc-001bc641ce4f", "name": "Approve manufacturing process request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.292449814907033, "y": -1.6877076411960132, "z": 2.826654375174035 }, "color": "#66CCFF", "size": 1.0 }, { "id": "200", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes creation of a formal change request. Usually, an organizations template is used for change request.", "Process_Group": "Strategic Management", "Scope": "Reviewing organizations template for change requests, gathering relevant information, filling in change request template, checking for completeness and submitting change request.", "Outcome": "Change request submitted.", "GUID": "167e351b-9350-11ed-3781-0201b014c5b2", "name": "Create change request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7592088861120798, "y": -1.6843853820598007, "z": 0.9514116327984934 }, "color": "#66CCFF", "size": 1.0 }, { "id": "201", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter status and completion message (plan of measures),\n Verify completion status,\n Conduct effectiveness check,\n Update plan of measures,\n Define new measure", "Type": "Business Process", "Description": "If a measure is reported as completed, the responsible management carries out an effectiveness check. ", "Process_Group": "Quality Management", "hasAssignment": true, "Scope": "Effectiveness reviews can take the form of process/product evaluations, performance measurements, or audits. If the effectiveness is confirmed, the measure can be closed, otherwise a new measure must be defined by the measure controller. The results of the effectiveness test are documented.", "Outcome": "Confirmation of effectiveness, the results are incorporated into the management review.", "GUID": "9bbdebdb-e2e7-11eb-2c3e-001bc641ce4f", "name": "Follow up on measures", "Business_Rules": "", "Prerequisite": "* Status and completion message" }, "position": { "x": 2.631329886376424, "y": -1.6810631229235882, "z": 1.4408688451980067 }, "color": "#66CCFF", "size": 1.0 }, { "id": "203", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review change request for new manufacturing process,\n Release process change request", "Type": "Business Process", "Description": "Approval of planned activities is given with the release of the process change request.This initiates execution of all activities related to the process change request.", "Process_Group": "Product Development", "hasAssignment": true, "Scope": "Before change request is released, the change request for new manufacturing process is reviewed.", "Outcome": "Change request released.", "GUID": "0cb0b796-09d6-11e9-2ddf-001bc640cd9b", "name": "Release process change request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.49836637717314, "y": -1.6777408637873754, "z": 1.9394413347829005 }, "color": "#66CCFF", "size": 1.0 }, { "id": "205", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Define corrective measures,\n Set up action plan,\n Trigger corrective measures implementation", "Type": "Business Process", "Description": "Based on the results of the analysis, suitable corrective actions are defined and triggered. ", "Process_Group": "Quality Management", "hasAssignment": true, "Scope": "An action plan is created that defines the goal, scope, and activities for improvement, as well as the designation of responsibilities, deadlines, and required resources. There is also an alignment with all responsible departments such as procurement, sales and production.", "Outcome": "Action plan created.", "GUID": "83b25a9c-ac6d-11ed-3781-0201b014c5b2", "name": "Determine and initiate corrective measures", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.360247040719038, "y": -1.6744186046511627, "z": 2.4470892390554275 }, "color": "#66CCFF", "size": 1.0 }, { "id": "207", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Adopt actions for implementation monitoring ,\n Perform control of planned vs. implemented actions,\n Document actual status of implementation,\n Define follow up actions", "Type": "Business Process", "Description": "The implementation of corrective measures are monitored. The respective measure controller receives the reports on the status of a measure and documents them promptly in the central measure plan.", "Process_Group": "Quality Management", "hasAssignment": true, "Scope": "Each defined corrective action is monitored with regard to timely implementation and result. The implementation of the measures is tracked and documented in regular meetings with the responsible person. Deviations from planned deadlines can be tracked. The actual status of the activities is known and the quality notification is completed after the defined activities have been carried out.", "Outcome": "Status and completion message", "GUID": "83b25aa0-ac6d-11ed-3781-0201b014c5b2", "name": "Monitor corrective measures", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.21690083746023, "y": -1.6710963455149501, "z": 2.9637721997661615 }, "color": "#66CCFF", "size": 1.0 }, { "id": "209", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Record and store change data,\n Observe reason for process change,\n Decide on following steps,\n Recommend change to R&D team,\n Stop change activity", "Type": "Business Process", "Description": "The request must be evaluated to determine whether a process change is actually required.", "hasAssignment": true, "Process_Group": "Product Development", "Scope": "When the change is released the change data is stored and made available for decision making.", "Outcome": "Change information is forwarded.", "GUID": "51963d8b-09d7-11e9-2ddf-001bc640cd9b", "name": "Evaluate change impact of manufacturing process", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7337877169434943, "y": -1.6677740863787376, "z": 0.9969855327816273 }, "color": "#66CCFF", "size": 1.0 }, { "id": "211", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review information from quality inspection,\n Assess possible root cause,\n Document root cause,\n Assess extent of quality issue,\n Define suitable internal investigations,\n Perform further internal investigations", "Type": "Business Process", "Description": "Based on the information from the problem definition, appropriate investigations are determined and conducted. Typically, at least the extent of nonconformity and possible causes are evaluated and analyzed. All results are documented.", "hasAssignment": true, "Process_Group": "Quality Management", "Scope": "The root causes of the problem are identified and assessed by the team. Methods and tools can be used to identify the root causes, such as Ishikawa diagram (representation of cause-effect relationships), on-site visit (Gemba), 5 Why method and the W-question technique. The assessment should consider frequency and impact of problem issues for prioritization.", "Outcome": "The extent and the cause of the problem/non-conformity are defined and documented.", "GUID": "83b25a9a-ac6d-11ed-3781-0201b014c5b2", "name": "Evaluate and analyze nonconformity", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.592841906060727, "y": -1.6644518272425248, "z": 1.509029771136202 }, "color": "#66CCFF", "size": 1.0 }, { "id": "213", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The non-conformity or problem is described and documented in detail. Essential contents are: Type (What?), Time (When?), Location (Where?), Scope (How many?), Frequency (How often?). ", "Process_Group": "Quality Management", "Scope": "As a rule, corrective actions are triggered by reporting results, quality control measures, audits and customer feedback. The resulting non-conforming results provide information for further processing.", "Outcome": "Documented non-conformity", "GUID": "83b25a8f-ac6d-11ed-3781-0201b014c5b2", "name": "Identify and describe nonconformity", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.4465754988924586, "y": -1.6611295681063123, "z": 2.0300535289578447 }, "color": "#66CCFF", "size": 1.0 }, { "id": "214", "text": "Process", "data": { "Advisory_Notes": "***Depending on the request it might be necessary to involve further departments, e.g. HSE for dangerous goods specifications", "KeyActivities": "Assign request to responsible department,\n Update product information,\n Update MRP information,\n Update purchasing information in material master,\n Update standard price,\n Review material master and inform requester", "Type": "Business Process", "Description": "This process describes changing material master of materials either produced in-house or procured externally.", "Process_Group": "Material and Product Master Data", "hasAssignment": true, "Scope": "After requesting a change to an existing material master the related different views of material master is updated.", "Outcome": "Material master has been changed.", "GUID": "37205d75-8d0d-11e9-0cfc-001bc641ce4f", "name": "Change material master", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.294918241944844, "y": -1.6578073089700998, "z": 2.5600150966370134 }, "color": "#66CCFF", "size": 1.0 }, { "id": "216", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Exchange information with requester,\n Reject request and inform requester,\n Receive and evaluate process request,\n Structure and document process request data,\n Forward process request data to R&D engineer", "Type": "Business Process", "Description": "When an request for process change is sent, the information is recorded and stored.", "hasAssignment": true, "Process_Group": "Product Development", "Scope": "Once the request for a process change for a product is sent, the data is documented, stored and forwarded.", "Outcome": "Process change request documented.", "GUID": "0cb0b781-09d6-11e9-2ddf-001bc640cd9b", "name": "Receive manufacturing process change request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.137800172792787, "y": -1.654485049833887, "z": 3.0988722762402467 }, "color": "#66CCFF", "size": 1.0 }, { "id": "220", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The scope of changes required may vary depending on the extent or type of nonconformity. By grouping the nonconformity, the change impact and requirements are better understood providing the basis for appropriate corrective actions and responsibles to be taken. ", "Process_Group": "Quality Management", "Scope": "This involves grouping the necessary modifications or improvements required into specific categories based on the types and extent of nonconformity identified.", "Outcome": "Nonconformities are classified and evaluated according to company specific risk management.", "GUID": "7d9d5ff6-c016-11e9-0cfc-001bc641ce4f", "name": "Classify product change", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7071861780746929, "y": -1.6511627906976745, "z": 1.0418806809758605 }, "color": "#66CCFF", "size": 1.0 }, { "id": "221", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To successfully amend the product due to complaints, all complaints related to the product are received and properly recorded.", "Process_Group": "Customer Returns", "Scope": "The product number, batch number, best before date are recorded and the complaints are recorded in detail. In some industries such as the chemical and food industries, provisioning of physical sample is required.", "Outcome": "Complaints related to the product are documented.", "GUID": "7d9d5ff0-c016-11e9-0cfc-001bc641ce4f", "name": "Process product change problem notification", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.5525887084733556, "y": -1.647840531561462, "z": 1.576163343494045 }, "color": "#66CCFF", "size": 1.0 }, { "id": "222", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When complaints are resolved and new changes are applied, customers are informed about the changes. This enhances customer satisfaction, as it demonstrates a commitment to improving products to meet their expectations.", "Process_Group": "Customer Relationship Mgmt", "Scope": "Take updated product documentation, analyse affected customers and send out product amendment information to affected customers.", "Outcome": "Product changes communicated to customers.", "GUID": "7d9d600a-c016-11e9-0cfc-001bc641ce4f", "name": "Inform customers about product amendment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.3924381780521475, "y": -1.6445182724252492, "z": 2.1192836544677602 }, "color": "#66CCFF", "size": 1.0 }, { "id": "223", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Determine relevant stakeholder for change order,\n Forward change order,\n Confirm receipt of change order", "Type": "Business Process", "Description": "A change order is work that is added to or deleted from the original scope of product development.", "Process_Group": "Product Development", "hasAssignment": true, "Scope": "Issuing of a change order initiate the development process, and can result in a a new project to handle significant changes to the current project.", "Outcome": "Change order forwarded to relevant parties.", "GUID": "c5c21af8-9bd2-11e8-2ddf-001bc640cd9b", "name": "Issue change order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.226665445435428, "y": -1.6411960132890364, "z": 2.671198085571742 }, "color": "#66CCFF", "size": 1.0 }, { "id": "225", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Closing complaint is the final step in the dispute management process and occurs when all matters related to the dispute have been settled. .", "Process_Group": "Complaint Management", "Scope": "Once the issuing of a credit/debit memo or replacement, or a return by the customer/to the vendor has occurred, all information related to the dispute settlement is recorded, stored and sent to the relevant stakeholders. This marks the end of the dispute.", "Outcome": "Complaint is closed", "GUID": "a717a13a-d4a8-11eb-2c3e-001bc641ce4f", "name": "Close complaint", "Business_Rules": "It is important to decide: ***Who is responsible for closing what customer complaint ***Whether and how confirmation of the closure needs to be confirmed by the customer? ", "Prerequisite": "" }, "position": { "x": 5.055201672957599, "y": -1.6378737541528239, "z": 3.2318626279170166 }, "color": "#66CCFF", "size": 1.0 }, { "id": "226", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Accept product for use,\n Trigger corrective action,\n Review inspection results,\n Compare inspection results with specifications", "Type": "Business Process", "Description": "The corrective actions process provides information about the further processing of the record results.", "hasAssignment": true, "Process_Group": "Complaint Management", "Scope": "In case, the assessed quality parameters are not within the required range, a decision on corrective actions takes place to bring the production back in quality or on the initiation of rework if no other options are possible.", "Outcome": "Based on the inspection results, a decision regarding necessary corrective actions is made and required actions are triggered.", "GUID": "7d364531-7e45-11e5-0a66-001bc640cd9b", "name": "Initiate corrective actions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6794223799410837, "y": -1.6345514950166113, "z": 1.0860665125824598 }, "color": "#66CCFF", "size": 1.0 }, { "id": "230", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The changed version of the product is released and made available to users. The release can be done in a phase manner to ensure the smooth transition from older versions to newer versions of the product. It can also be done in a controlled environment to identify and address all issues.", "Process_Group": "Product Development", "Scope": "This involves informing relevant customers, production and sales about new product specification.", "Outcome": "Changed product version is released.", "GUID": "9c41f070-09d2-11e9-2ddf-001bc640cd9b", "name": "Roll out changed product version", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.5105976981542693, "y": -1.6312292358803986, "z": 1.642223857463557 }, "color": "#66CCFF", "size": 1.0 }, { "id": "231", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Start work according to prototype,\n Report on work performed,\n Analyze current status of change implementation,\n Complete change implementation,\n Create technical information for user documentation,\n Document changes and product data ,\n Confirm completion of change implementation", "Type": "Business Process", "Description": "Implement changes according to prototype so that all changes are executed as specified in the change order.", "Process_Group": "Product Development", "hasAssignment": true, "Scope": "Based on the change specifications, the responsible parties are engaged to manufacture a specific quantity of the new product with the new raw material/components.The production order is assigned to the project.", "Outcome": "Changes implemented.", "GUID": "c5c21b0f-9bd2-11e8-2ddf-001bc640cd9b", "name": "Implement change", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.3359912715595117, "y": -1.627906976744186, "z": 2.2070709630817835 }, "color": "#66CCFF", "size": 1.0 }, { "id": "233", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review specifications for development,\n Determine quantity needed,\n Forward request for prototype creation", "Type": "Business Process", "Description": "Based on the engineering change order, the development process is initiated.", "Process_Group": "Product Development", "hasAssignment": true, "Scope": "Initiate development process sets out a series of stages that new or change products typically go through, including creation of a prototype and the implementation of the change.", "Outcome": "Prototyping can start.", "GUID": "c5c21b0b-9bd2-11e8-2ddf-001bc640cd9b", "name": "Initiate development", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.155535117971104, "y": -1.6245847176079735, "z": 2.780562512030413 }, "color": "#66CCFF", "size": 1.0 }, { "id": "235", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check if supplier documents are complete,\n Review change request for material/ component,\n Request supplier documents,\n Receive required supplier documents,\n Approve change request for material/ component,\n Reject change request for material/ components", "Type": "Business Process", "Description": "When all requirements are met, the change request is approved, released and communicated to the stakeholders.", "Process_Group": "Product Development", "hasAssignment": true, "Scope": "Once all the tasks in a change request are approved, it is released.At this point, there are records of all items that should be changed and the parties involved.", "Outcome": "Change request is approved.", "GUID": "c5c21af5-9bd2-11e8-2ddf-001bc640cd9b", "name": "Release change request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.969161571347911, "y": -1.6212624584717608, "z": 3.3626527144263894 }, "color": "#66CCFF", "size": 1.0 }, { "id": "240", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review material master data,\n Confirm correctness of data,\n Update validity of material,\n Set material phase out status ", "Type": "Business Process", "Description": "The validity of a material must be updated in the system by setting the appropriate phase out status.", "hasAssignment": true, "Process_Group": "Phase Out", "Scope": "The time at which the material will no longer be valid for use in production is maintained in the system.", "Outcome": "Data regarding the product phase out are maintained in the system.", "GUID": "686d861b-94c0-11e8-2ddf-001bc640cd9b", "name": "Update phase out status of master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6505152242488907, "y": -1.6179401993355482, "z": 1.1295129457082969 }, "color": "#66CCFF", "size": 1.0 }, { "id": "242", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Gather change data,\n Post information for production", "Type": "Business Process", "Description": "Production needs to be notified about materials that have been discontinued to make the necessary adjustments to the production process and also avoid unwanted production costs by consuming materials that are no longer needed.", "Process_Group": "Phase Out", "hasAssignment": true, "Scope": "Change data is gathered and provided to production.", "Outcome": "Production informed about material phase out.", "GUID": "de706d8d-9408-11e9-0cfc-001bc641ce4f", "name": "Inform production about phase out", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.466897462753373, "y": -1.6146179401993355, "z": 1.7071663387792564 }, "color": "#66CCFF", "size": 1.0 }, { "id": "244", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When an request for phase out is sent, the information is recorded and stored. From todays point of view there are manual processes only.", "Process_Group": "Phase Out", "Scope": "Once the request for phase out for a material is sent, the data is documented, stored and forwarded.", "Outcome": "Phase out information stored.", "GUID": "7d9d6019-c016-11e9-0cfc-001bc641ce4f", "name": "Receive phase out request and conduct impact analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.2772732086971237, "y": -1.611295681063123, "z": 2.2933556888446365 }, "color": "#66CCFF", "size": 1.0 }, { "id": "245", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review phase out information,\n Approve phase-out,\n Reject phase-out", "Type": "Business Process", "Description": "With a careful consideration of the impact analysis, the request to phase out material needs to be reviewed and authorized.", "Process_Group": "Phase Out", "hasAssignment": true, "Scope": "Once phase out request is documented, the information is reviewed and a decision to accept or decline the phase out request is made.", "Outcome": "Phase out request accepted or declined.", "GUID": "de706d8a-9408-11e9-0cfc-001bc641ce4f", "name": "Approve phase out", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.081575685366918, "y": -1.6079734219269102, "z": 2.8880339202685237 }, "color": "#66CCFF", "size": 1.0 }, { "id": "249", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review relevant documentation on product phase out,\n Determine end of service time for product,\n Forward product end of service time details to customer", "Type": "Business Process", "Description": "During phase out, the continued time for service needs to be defined and communicated to the customer. This includes not only repair, service onsite but also stockholding of spare parts. Purchasing or production of spare parts must be ensured until end of repair/service time.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Consider sold units, warranty times, service quota and used spare parts.", "Outcome": "End of service defined with all relevant details. Communicated to all relevant parties.", "GUID": "686d8614-94c0-11e8-2ddf-001bc640cd9b", "name": "Define end of service time", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.879738444413392, "y": -1.6046511627906976, "z": 3.4911534933477166 }, "color": "#66CCFF", "size": 1.0 }, { "id": "251", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Specify follow-up activities,\n Inform sales,\n Initiate production adjustment order creation,\n Trigger scrapping", "Type": "Business Process", "Description": "Observe the reason for phase out and decide which following steps are needed. From todays point of view these are manual processes only.", "Process_Group": "Phase Out", "hasAssignment": true, "Scope": "Sold units and warehouse stock has to be considered to calculate follow-up costs.", "Outcome": "Classified request for product phase out.", "GUID": "686d8610-94c0-11e8-2ddf-001bc640cd9b", "name": "Classify request for phase out", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6204843911067943, "y": -1.601328903654485, "z": 1.172190401845725 }, "color": "#66CCFF", "size": 1.0 }, { "id": "253", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Evaluate request for phase out,\n Exchange information with requester,\n Generate product request,\n Verify if follow-up material is required,\n Structure and document request data ", "Type": "Business Process", "Description": "When an request for phase out is sent, the information is recorded and stored. From todays point of view there are manual processes only.", "Process_Group": "Phase Out", "hasAssignment": true, "Scope": "Once the request for phase out for a product is sent, the data is documented, stored and forwarded.", "Outcome": "Phase out information stored.", "GUID": "686d860e-94c0-11e8-2ddf-001bc640cd9b", "name": "Receive request for phase out", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.421517753567931, "y": -1.5980066445182723, "z": 1.7709465743368207 }, "color": "#66CCFF", "size": 1.0 }, { "id": "255", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify goods receipt options for quality inspection,\n Verify materials and routing operations,\n Assign batch number,\n Maintain material,\n production plant,\n order type,\n quantity into header,\n Verify scheduling type and production start date,\n Create production order", "Type": "Business Process", "Description": "When rework is to be done a production order for rework needs to be created. The nature of reworking processes require the selection of required operations and components either selected from standard routings and standard BOMs or captured manually. A process order can also be used in the process industry.", "hasAssignment": true, "Process_Group": "Production Scheduling", "Scope": "A rework order is created with its own product as component. Within the order the required operations and additionally required components are defined and batches will be assigned if applicable.", "Outcome": "The rework order with the required operations and components is created.", "GUID": "5a5e62f7-7f29-11e5-0a66-001bc640cd9b", "name": "Create production order for rework", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.216323964960012, "y": -1.5946843853820598, "z": 2.378079088765533 }, "color": "#66CCFF", "size": 1.0 }, { "id": "257", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Initiate depreciation for specified goods,\n Move goods,\n Set status to not-active", "Type": "Business Process", "Description": "If the good cannot be sold, re-worked or recycled, it needs to be scrapped.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "After the decision was made to scrap the good, it has to be depreciated and scrapped as defined for this specific good. The batch needs to be flagged as not active for sales.", "Outcome": "The good is ready for scrapping.", "GUID": "f4e1fe2a-7e46-11e5-0a66-001bc640cd9b", "name": "Initiate scrapping", "Business_Rules": "Decisions are needed for: ***internal vs. external scrapping ***good specific scrapping regulations to be determined ***official specifications/laws to be determined ***special health and/or environmental protection needs", "Prerequisite": "" }, "position": { "x": 4.004837499504149, "y": -1.5913621262458473, "z": 2.9935391433160436 }, "color": "#66CCFF", "size": 1.0 }, { "id": "259", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Specify customers to be informed,\n Provide data to key account manager ,\n Inform customer regarding last option to buy,\n Collect feedback from customer", "Type": "Business Process", "Description": "Within a reasonable time before a planned product phase out the customers have to be informed. This is necessary to give customers the chance to place replacement orders or to fill their stocks. In case a follow-up-product will be set up, this information has to be given to the customers too.", "Process_Group": "Customer Relationship Mgmt", "hasAssignment": true, "Scope": "Customers need to be informed in case products are being discontinued as follows: ***date of phase-out (last production date at vendor ***last acceptance date for PO from customers ***successor material ***timeline of availability of spare parts if applicable ***timeline of service being provided All information given is prior to availability!", "Outcome": "Customer informed and prepped for upcoming product phase out", "GUID": "686d8612-94c0-11e8-2ddf-001bc640cd9b", "name": "Inform customer about last option to buy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.786993171781061, "y": -1.5880398671096345, "z": 3.6172774808302304 }, "color": "#66CCFF", "size": 1.0 }, { "id": "265", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Procurement data contains information about the vendors that supply an enterprise and general purchasing data. Vendor information is stored in individual vendor records and contains the vendors name and address, as well as data such as currency used for ordering from vendor, terms of payments, etc. Purchasing is also supported in its work, in addition to vendor data, by other data such as: source list, quota arrangement, conditions, purchasing info records, etc. When creating vendor both type of data described above need to be maintained.", "Process_Group": "Business Partner Master Data", "Scope": "Business partner is created in organization, as the next step vendor data to be maintained: -vendors name and address -currency used for ordering from vendor -terms of payments -source list -quota arrangement -conditions -purchasing info records -vendor evaluation", "Outcome": "Procurement data is created or changed for the business partner.", "GUID": "b6f15ca3-d6d6-11ed-3781-0201b014c5b2", "name": "Maintain procurement data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5893503256276345, "y": -1.584717607973422, "z": 1.214069826009745 }, "color": "#66CCFF", "size": 1.0 }, { "id": "266", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Financial data have to be maintained for all business partners types. Following mandatory financial data to be entered are: -company code -terms of payment for customer -reconciliation account -dunning procedure -account group Mandatory financial data can differ based on the business policy.", "Process_Group": "Business Partner Master Data", "Scope": "All mandatory financial data for vendor or customer to be maintained", "Outcome": "Financial data is created or changed for the business partner.", "GUID": "b6f15ca5-d6d6-11ed-3781-0201b014c5b2", "name": "Maintain financial data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.3744894652877626, "y": -1.5813953488372092, "z": 1.8335211422935478 }, "color": "#66CCFF", "size": 1.0 }, { "id": "267", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Sales document needs to be maintained for all customers and the data for one customer can also differ for each sales area. The sales area is a combination of sales organization, distribution channel and division. Therefore where maintaining sales document, it is necessary to assign a sales group. If you edit a customer master record, you must enter the customer number and the sales area in order to access screens containing sales and distribution data.", "Process_Group": "Business Partner Master Data", "Scope": "Data in sales document to be maintained: - Assign sales area - data includes pricing data, delivery priority, shipping condition - Shipping information - Billing information", "Outcome": "Sales data is created or changed for the business partner.", "GUID": "b6f15ca1-d6d6-11ed-3781-0201b014c5b2", "name": "Maintain sales data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.1531850348401798, "y": -1.5780730897009967, "z": 2.4611834828106445 }, "color": "#66CCFF", "size": 1.0 }, { "id": "268", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Creation of general business partner is triggered by creation of new lead or vendor.", "Process_Group": "Business Partner Master Data", "Scope": "Create general business partner data by maintaining basic following information -Title and name - Street address - Postal code/country/city - Communication language - Further information in the tabs Address Overview, Identification, Control, Payment Transactions", "Outcome": "General business partner created.", "GUID": "b6f15c9f-d6d6-11ed-3781-0201b014c5b2", "name": "Create general business partner data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9253728040505544, "y": -1.574750830564784, "z": 3.0970063527897858 }, "color": "#66CCFF", "size": 1.0 }, { "id": "272", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the creation of and change to G/L account in a chart of accounts context. The information is applicable to all companies using the G/L account.", "Process_Group": "FICO Master Data", "Scope": "The chart of account segment of a general ledger account contains the following information: 1. Account name 2. Account type 3. Account number 4. Account group 5. Group account number (if the account is required for group consolidation)", "Outcome": "Chart of account segment of the GL account is created", "GUID": "b9028fb0-d6de-11ed-3781-0201b014c5b2", "name": "Maintain General Ledger account (chart of account)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.690988894808179, "y": -1.5714285714285714, "z": 3.740938811152401 }, "color": "#66CCFF", "size": 1.0 }, { "id": "273", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the maintenance of cost elements and cost element groups.", "Process_Group": "FICO Master Data", "Scope": "Primary cost element are created to compare the G/L accounts of profit and loss statements. These are used to transfer costs from FI to CO.", "Outcome": "The required primary cost elements are created or changed.", "GUID": "b902b6c1-d6de-11ed-3781-0201b014c5b2", "name": "Maintain primary cost elements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5571342240092945, "y": -1.5681063122923589, "z": 1.255122706518758 }, "color": "#66CCFF", "size": 1.0 }, { "id": "274", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the creation of and change to the financial reporting structure.", "Process_Group": "FICO Master Data", "Scope": "Financial statement version (FSV) is by setting the attributes: - FSV ID and description - Chart of Accounts: - Valid from and valid to date", "Outcome": "Financial statement version is created or changed in the system.", "GUID": "b902b6c3-d6de-11ed-3781-0201b014c5b2", "name": "Maintain financial statement version", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.325844614962011, "y": -1.564784053156146, "z": 1.8948474416301209 }, "color": "#66CCFF", "size": 1.0 }, { "id": "275", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the creation of and change to G/L account in a company code context.", "Process_Group": "FICO Master Data", "Scope": "The link between company code and chart of account is established through assignment. Once the chart of account is created, a company code must be assigned.", "Outcome": "Company code is assigned to chart of accounts.", "GUID": "b902b6c5-d6de-11ed-3781-0201b014c5b2", "name": "Maintain General Ledger account (in company code)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.0878994035769916, "y": -1.5614617940199336, "z": 2.5426122931718984 }, "color": "#66CCFF", "size": 1.0 }, { "id": "279", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process orchestrates the creation, maintenance and/or notification activities to further maintain material master data dependant objects, required to make the material fit for purpose.", "Process_Group": "Material and Product Master Data", "Scope": "After all the local material master data has been maintained, the depended material master data objects must be captured in the system.", "Outcome": "Depended material master data objects are created or changed.", "GUID": "be8adeb4-d6da-11ed-3781-0201b014c5b2", "name": "Monitor maintenance of master data dependent master data objects", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.84323569889266, "y": -1.558139534883721, "z": 3.1983651077944564 }, "color": "#66CCFF", "size": 1.0 }, { "id": "280", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the central exit point after the creation and maintenance of material master data.", "Process_Group": "Material and Product Master Data", "Scope": "Ensure that all depended material master data objects are maintained and the material is activated and fit for purpose.", "Outcome": "The material is fit for purpose.", "GUID": "be8adeb6-d6da-11ed-3781-0201b014c5b2", "name": "Activate material master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.591790973595365, "y": -1.5548172757475083, "z": 3.8620532951796678 }, "color": "#66CCFF", "size": 1.0 }, { "id": "281", "text": "Process", "data": { "Advisory_Notes": "Usually following basic information needs to be recorded: ***Material type ***Base unit of measures ***Material description***Material group***Model code***Net weight***Weight unit***Basic data text Specific product information might be: ***Product hierarchy***Commodity code***Cross plant material status***Country of origin***Serial number***Tax classification***Batch management indicator*** Dangerous goods indicator profile MRP information usually is: ***MRP group***Type*** Lot size***Planning and scheduling data. Purchasing information includes: ***Purchasing group***Purchasing values Price information includes: ***Price conditions***Standard price ***Intercompany price", "KeyActivities": "Create request for new material,\n Specify basic material information,\n Specify product specific specifications,\n Complete MRP information,\n Enter purchasing information in material master,\n Add price lists for customers and intercompany business,\n Review the material and inform requester", "Type": "Business Process", "Description": "This process describes the creation of a new material that is either produced in-house or is externally procured. It also applicable for creating variant configuration material master.", "hasAssignment": true, "Process_Group": "Material and Product Master Data", "Scope": "After the new material master has been requested, basic information and product specifications are maintained. In addition information on MRP parameters and purchasing are entered. Finally price information for customers and intercompany business are added.", "Outcome": "A new material master has been created and is ready for use for example in sales, procurement or production.", "GUID": "37205d71-8d0d-11e9-0cfc-001bc641ce4f", "name": "Create material master", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5238580191042437, "y": -1.5514950166112957, "z": 1.2953210944054336 }, "color": "#66CCFF", "size": 1.0 }, { "id": "283", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process orchestrates the creation, maintenance and/or notification activities to further maintain article master data dependant objects, required to make the material fit for purpose.", "Process_Group": "Material and Product Master Data", "Scope": "After the article master data is maintained and activated in relevant destination systems, all article dependent master data must be maintained.", "Outcome": "All article dependent master data activated in relevant destination systems.", "GUID": "be8adeae-d6da-11ed-3781-0201b014c5b2", "name": "Monitor maintenance of article dependent master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.27561632020181, "y": -1.548172757475083, "z": 1.9548837211535561 }, "color": "#66CCFF", "size": 1.0 }, { "id": "284", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the maintenance of an article object.", "Process_Group": "Material and Product Master Data", "Scope": "The article master data is created or changed and then activated in relevant destination systems.", "Outcome": "Article activated in relevant destination systems.", "GUID": "be8adeac-d6da-11ed-3781-0201b014c5b2", "name": "Maintain article master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.0205115178926425, "y": -1.5448504983388704, "z": 2.6223100827853836 }, "color": "#66CCFF", "size": 1.0 }, { "id": "285", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the creation of and changes to global material master data.", "Process_Group": "Material and Product Master Data", "Scope": "When the maintenance of global material master data is needed, all the required data is captured and activated in relevant destination systems.", "Outcome": "Global material master data activated in relevant destination systems.", "GUID": "be8adeb0-d6da-11ed-3781-0201b014c5b2", "name": "Maintain global material master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.7584821033043476, "y": -1.5415282392026577, "z": 3.297546402879106 }, "color": "#66CCFF", "size": 1.0 }, { "id": "286", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the creation of and changes to local material master data.", "Process_Group": "Material and Product Master Data", "Scope": "All required local master data is created or changed and then activated in relevant destination systems.", "Outcome": "Local material master data activated in relevant destination systems.", "GUID": "be8adeb2-d6da-11ed-3781-0201b014c5b2", "name": "Maintain local material master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.48946694248917, "y": -1.5382059800664452, "z": 3.980538477680744 }, "color": "#66CCFF", "size": 1.0 }, { "id": "291", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify material per order item line,\n Identify relevant transport type,\n Identify net weight of material,\n Permit order,\n Identify UN (United Nations) number,\n Block order and report issue to sales,\n Identify UN code of material packaging", "Type": "Business Process", "Description": "The purpose of this process is to prevent shipping of dangerous goods which will harm dangerous goods regulation.", "Process_Group": "Healthy, Safety and Environment", "hasAssignment": true, "Scope": "The dangerous goods check verifies whether the shipment of dangerous goods contains transport regulatory data derived from UN-numbers, dangerous good classes, packaging codes etc.", "Outcome": "The product complies with the EH+S related requirements and the sales order is permitted by EH+S.", "GUID": "e4547700-d32a-11eb-2c3e-001bc641ce4f", "name": "Perform dangerous goods check", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.489544365487564, "y": -1.5348837209302326, "z": 1.3346376224444787 }, "color": "#66CCFF", "size": 1.0 }, { "id": "293", "text": "Process", "data": { "Advisory_Notes": "It is necessary to define what happens after the availability is confirmed. Typically the requested product quantity is reserved (excluded from available stock). It should be defined how undelivered sales orders are handled and when a reservation for a sales order will be canceled. Business rules that need to be defined are: ***What are the main and alternative supply points for regions/customers (ship-to) ***Which future goods receipts should be considered ***Which future goods issues should be considered ***Are allocations required to reserve quantities for specific customers, customer groups, markets/sales channels, regions ***If allocations are used are those valid for the whole sales period or will those be deactivated after a certain time (example: monthly allocations are only valid until mid of the month any remaining quantities will be made generally available afterwards). Sometimes other constraints like transportation capacity or handling capacity need to be integrated into the ATP check.", "KeyActivities": "Perform ATP,\n Confirm date and quantities to order ,\n Calculate alternative delivery date,\n Inform customer about alternative date,\n Receive response to alternative delivery date", "Type": "Business Process", "Description": "The Available-to-Promise (ATP) check against stock verifies whether the required quantity of finished goods can be sold to the customer at the requested date. The check is carried out against actual or projected finished goods inventory.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "After the customer order data is captured, it must be checked if the order can be fulfilled (the requested products are available in the requested quantity and on the desired date). It is also necessary to determine the storage location the goods will be delivered from. During the check, it is also possible to run simulations to know how changes in demand or supply conditions will affect the ATP results. ", "Outcome": "ATP check is performed.", "GUID": "768b35c8-d4a1-11eb-2c3e-001bc641ce4f", "name": "Check availability to promise at sales order entry", "Business_Rules": "For setting-up the check it must be defined which sources, i.e. inventory, are to be considered. Typical business cases are: ***Check against plan or inventory ***Inventory in local warehouse ***Inventory in global organisation ***Inventory in local warehouse + placed purchase orders/released production orders Allocations might be used in short markets to manage the distribution of stock to particular markets, customer segments, or individual customers. The workflow in case of different partial availability situations should be defined: ***Proposal of alternate dates ***Proposal of substitute products ***Proposal of substitute plants ***Proposal of partial shipments ***Backorder processing", "Prerequisite": "" }, "position": { "x": 2.223838776633676, "y": -1.5315614617940199, "z": 2.0135891079215833 }, "color": "#66CCFF", "size": 1.0 }, { "id": "295", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Remove billing block,\n Create down payment request,\n Send down payment request to customer", "Type": "Business Process", "Description": "This process describes the steps after the sales order was confirmed. The customer is required to pay the down payment. In order to do that, the billing block of the sales order needs to be removed first and a down payment request sent to the customer.", "Process_Group": "Billing, Rebates and Commissions", "hasAssignment": true, "Scope": "Remove billing block, create down payment request", "Outcome": "Down payment request created and sent to customer.", "GUID": "ad546818-7e58-11e5-0a66-001bc640cd9b", "name": "Process down payment request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.951067255732655, "y": -1.5282392026578073, "z": 2.7002225930731223 }, "color": "#66CCFF", "size": 1.0 }, { "id": "297", "text": "Process", "data": { "Advisory_Notes": "In addition to the pricing itself, the workflows and required approvals have to be defined. Consider all types of sales (priced samples, free of charge samples etc.) and possible promotions and rebates. In case a quotation has been placed, the conditions between both should be aligned or at least an interaction with the customer has to take place in case of any deviation.", "KeyActivities": "Refer to standard price,\n Refer to quotation (If referenced),\n Refer to contract,\n Refer to special price agreements / promotions,\n Refer to intercompany pricing (If relevant),\n Calculate pricing schema,\n Release price,\n Trigger price finding,\n Trigger quotation renewal,\n Act on policy for VAT exceptions,\n Adjust price to zero manually,\n Determine value added tax", "Type": "Business Process", "Description": "Once the confirmation is provided that the customer order can be fulfilled, the product price must be calculated (or extracted from the system) taking into account relevant conditions (e.g. rebates, shipping condition, customer price groups).", "Process_Group": "Pre-order Management", "hasAssignment": true, "Scope": "Pricing takes into account all conditions related to the product and customer.", "Outcome": "Pricing and conditions related to the order are generated, documented and agreed with customer.", "GUID": "768b35d0-d4a1-11eb-2c3e-001bc641ce4f", "name": "Determine product price and conditions", "Business_Rules": "Pricing schemas are typically defined upfront. It must be defined who (and with which limitations) has the rights to adjust prices and conditions within the sales process. The price and trading conditions of the product must be based on a set of guidelines that take into account: ***Cost of product ***Market value of product ***Customers perceived value of product ***Relationship with customer (rebates etc.) ***Defined profit margin expectations", "Prerequisite": "" }, "position": { "x": 3.6711697178767757, "y": -1.5249169435215948, "z": 3.3944827150163186 }, "color": "#66CCFF", "size": 1.0 }, { "id": "299", "text": "Process", "data": { "Advisory_Notes": "Down payments have to be considered in the credit check.", "KeyActivities": "Block customer billing ,\n Monitor the billing due list,\n Perform down payment request clearing", "Type": "Business Process", "Description": "When a customer is requested to make down payment before the sales order is fulfilled, the request remains as an open item until the customer makes the down payment. When the customer makes the down payment, and it is posted to the customer account, it clears the down payment request. ", "Process_Group": "Accounts Receivable", "hasAssignment": true, "Scope": "Post the down payment received from the customer. The posting is made in reference to the sales order with down payment request. Both automatic and manual postings are possible. The down payment request gets cleared.", "Outcome": "Down payment request cleared.", "GUID": "768b35d8-d4a1-11eb-2c3e-001bc641ce4f", "name": "Clear down payment request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.384086464104426, "y": -1.521594684385382, "z": 4.096313693463472 }, "color": "#66CCFF", "size": 1.0 }, { "id": "301", "text": "Process", "data": { "Advisory_Notes": "Many corporations start looking at credit management from a group perspective. This requires some collaboration across companies and business units, which might not be established. Hierarchical credit limits might help to hinder a single business unit from already consuming the entire credit limit of a customer. Any kind of guarantees such as letter of credit or bank guarantees and advanced payments need to be considered in this process. Credit management for consignment fill-ups - despite goods remaining in sellers property, it is common to perform credit check, since control over goods is lost and the goods issue is typically retrospective.", "KeyActivities": "Review blocking reason,\n Make??additional checks and analysis,\n Check blocking reason ,\n Check customer credit data in credit management info system,\n Start approval workflow according to group policy,\n Release sales document,\n Check credit management data,\n Inform Sales about bad payment behaviour,\n Inform Sales about critcal parmeters,\n Inform Sales about critical level of dunning", "Type": "Business Process", "Description": "Credit management helps to control the companys exposure to credit risk. Credit management must be aligned taking into account the customers liquidity and payment history (credit limit/insurance) and outstanding receivables.", "Process_Group": "Credit Management", "hasAssignment": true, "Scope": "The customers ability to pay for the product or service is evaluated based on their liquidity and payment history and a decision is made on whether the sale is allowed or not.", "Outcome": "The decision is made on whether to proceed with sale or not.", "GUID": "768b35dc-d4a1-11eb-2c3e-001bc641ce4f", "name": "Execute credit management", "Business_Rules": "It is necessary to define the information necessary to execute the credit management process. A framework must be put in place for: ***Calculating the rating value of customers ***Determining Credit Limit ***Setting rules for Credit Check", "Prerequisite": "" }, "position": { "x": 1.4542166240336203, "y": -1.5182724252491695, "z": 1.3730455237843575 }, "color": "#66CCFF", "size": 1.0 }, { "id": "303", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify country of importer,\n Communicate with vendor and identify real substance of material ,\n Check quantity of already imported / produced chemical component,\n Permit order,\n Identify destination country,\n Identify real substance of material,\n Block order and report issue to sales,\n Check quantity limit to import / produce", "Type": "Business Process", "Description": "Country specific regulations state that, above a certain quantity of chemicals and other hazardous substances, it is required to register with the authorities the maximum quantities of these substances that is planned to be purchased, imported, produced, sold, or exported within a certain period. By comparing the recorded quantities with the limit values, the system signals that a limit value is close to be exceeded if a limit value is exceeded, the system can also block the respective business process.", "Process_Group": "Healthy, Safety and Environment", "hasAssignment": true, "Scope": "Identify required Checks ***Check if Registration Status is positive or negative ***Check quantity limit to import / produce ***Block order and report issue ***Permit Order", "Outcome": "The product complies with the chemical compliance related requirements and sales order processing is permitted.", "GUID": "96e72960-eaa6-11e4-0a66-001bc640cd9b", "name": "Perform chemical compliance check", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.170547234618989, "y": -1.5149501661129567, "z": 2.0709236350691107 }, "color": "#66CCFF", "size": 1.0 }, { "id": "305", "text": "Process", "data": { "Advisory_Notes": "The check itself is typically done automatically by the ERP system. The actual process discussion should focus on the maintenance of the relevant GTS data (including the integration of external data sources) and the handling of sales orders failing to pass the checks.", "KeyActivities": "Update compliance documents,\n Check compliance documents for completeness,\n Communicate trade compliance check results to Sales,\n Perform license control check,\n Evaluate results of trade compliance checks,\n Verify documents required for compliance check ,\n Perform sanctioned party list screening,\n Perform embargo check for transportation route,\n Block order and report issue to sales", "Type": "Business Process", "Description": "Global trade compliance ensures due diligence with trade regulatory programs and cross-border customs requirements. Global trade checks are required for all business operations.", "hasAssignment": true, "Process_Group": "Global Trade Compliance", "Scope": "Global trade checks verify conformance with regulations of the countries from/to which the trade is being conducted. In this respect both involved business partners and products being sold or related services are subject to checks.", "Outcome": "The sales order complies with the applicable trade regulations and the product can be shipped.", "GUID": "a717a138-d4a8-11eb-2c3e-001bc641ce4f", "name": "Perform global trade check for sales", "Business_Rules": "It needs to be ensured that information (sanctioned party lists, embargo lists, dual use products) used for screening is comprehensive and up to date. Customer data must be up to date. Rules and procedures how to handle sales orders which failed the compliance checks have to be in place.", "Prerequisite": "" }, "position": { "x": 2.8796138950319836, "y": -1.5116279069767442, "z": 2.776296780882535 }, "color": "#66CCFF", "size": 1.0 }, { "id": "307", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create standard sales order ,\n Create sales order for dropshipment,\n Create sales order with scheduling agreement,\n Create sales order for free of charge,\n Enter sales order header data,\n Enter item data and quantity,\n Save sales order,\n Trigger credit block management,\n Trigger back order processing,\n Trigger dangerous goods check compliance,\n Trigger resolution of global trade block,\n Perform global trade check for sales,\n Create sales order for consignment sales,\n Capture down payment data", "Type": "Business Process", "Description": "Receiving the customer order and capturing it in a format necessary for further processing are the key first steps to all sales processes. A billing plan is maintained and the initial down payment to be paid by the customer captured.", "hasAssignment": true, "Process_Group": "Sales Order Management", "Scope": "Once the customer order is placed, the data must be amended, stored and forwarded for further processing. This might include transferring or copying data from other documents such as quotations or frame contracts.", "Outcome": "All relevant information regarding the customers order is documented. The information captured provides the basis for determining whether the order can be fulfilled.", "GUID": "ad54682d-7e58-11e5-0a66-001bc640cd9b", "name": "Create sales order with down payment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.5813579852355955, "y": -1.5083056478405314, "z": 3.48910804957216 }, "color": "#66CCFF", "size": 1.0 }, { "id": "309", "text": "Process", "data": { "Advisory_Notes": "Circumstances such as required documents for customs clearance or advance payments might have an impact on the timing when an invoice needs to be created during the sales process. In a case of self-billing, instead of sending invoices to the customer, the supplier receives self-billing information from the customer, including a reference document number, received quantity, and the value to be credited to the supplier.", "KeyActivities": "Run billing due list,\n Create and post customer invoice,\n Send invoice to customer,\n Execute account determination,\n Verify if open item referenced to down payment,\n Analyse customer open items,\n Create manual reference to down payment at line item level,\n Accounts receivable posting,\n Revenue posting", "Type": "Business Process", "Description": "The creation of a customer invoice provides documentation of the financial obligation related to a customer order. The customer invoice is created from a sales order.", "hasAssignment": true, "Process_Group": "Billing, Rebates and Commissions", "Scope": "After the customer order has been fulfilled, the invoice is created. It provides the customer with information required to settle the payment related to their order.", "Outcome": "Invoice is created and sent to the customer.", "GUID": "75ff0dfc-e8bd-11e4-0a66-001bc640cd9b", "name": "Create customer invoice", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.275721281897647, "y": -1.504983388704319, "z": 4.20930012229201 }, "color": "#66CCFF", "size": 1.0 }, { "id": "311", "text": "Process", "data": { "Advisory_Notes": "The effectiveness of the approval-workflows often is overestimated. Sales managers will receive many approval requests daily. The data to be checked should be limited to the essentials. Everything that can be checked automatically by rules should be implemented in the system. The result of the automatic checks should be obvious to the reviewer.", "KeyActivities": "Save sales order,\n Review sales order,\n Approve sales order,\n Inform responsible about necessary changes", "Type": "Business Process", "Description": "Approval of the sales order is given through the confirmation and represents a commitment to fulfil the order.", "hasAssignment": true, "Process_Group": "Sales Order Management", "Scope": "After all checks related to the order have been performed the final decision is made regarding execution of the order. A commitment to the customer is made. This triggers the outbound logistics, production process or service process.", "Outcome": "A decision is made to fulfil the customers order. This triggers the outbound logistics/production process. The customer is informed about the decision.", "GUID": "a98a286c-7e52-11e5-0a66-001bc640cd9b", "name": "Save and approve sales order", "Business_Rules": "Rules must be established for allocating authorization for sales order approval to users. The format of the confirmation (electronic, paper) and communication channel must be defined.", "Prerequisite": "" }, "position": { "x": 1.4178988460118864, "y": -1.5016611295681064, "z": 1.4105186501702702 }, "color": "#66CCFF", "size": 1.0 }, { "id": "313", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Monitor delivery due date,\n Monitor invoicing due date,\n Monitor incomplete data,\n Monitor and corroborate unconfirmed quantities,\n Monitor and corroborate credit blocks,\n Resolve delivery blocks and other delivery issues,\n Collaborate shipping blocks in deliveries,\n Monitor and resolve billing blocks,\n Monitor sales order status,\n Corroborate issues independent service orders,\n Corroborate issues independent manufacturing orders,\n Corroborate issues independent purchase orders,\n Maintain obsolete open order items", "Type": "Business Process", "Description": "After capturing and confirming a sales order, the order fulfillment needs to be monitored. Changes in availability, confirmation dates and priorities have to be considered and reflected in the sales order. The customer needs to be informed accordingly.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "From a time perspective, this process spans from the saving of the sales order to the creation, release of the delivery and invoicing.", "Outcome": "Any changes are reflected in the sales order, communication and escalation procedures are triggered if necessary.", "GUID": "397b5453-d3a1-11e9-0cfc-001bc641ce4f", "name": "Monitor order fulfillment", "Business_Rules": "Clear guidelines need to be defined how to handle shortages, deviations from already given commitments to the customer, priority conflicts as well as rules need to be agreed on how and when, and under which sircumstances the customer can request changes to the order.", "Prerequisite": "" }, "position": { "x": 2.115777975255406, "y": -1.4983388704318936, "z": 2.126848269017829 }, "color": "#66CCFF", "size": 1.0 }, { "id": "317", "text": "Process", "data": { "Advisory_Notes": "The documentation may be delivered together with the goods receipt or independently from it. The documentation may be delivered as hard copy or as an electronic version.", "KeyActivities": "Compile documentation,\n Trigger creation of documentation,\n Create documentation,\n Prepare documentation for shipment to customer", "Type": "Business Process", "Description": "The process describes the creation of customer specific documentation that may be requested by our customers.", "Process_Group": "Customer Relationship Mgmt", "hasAssignment": true, "Scope": "After the request for creating customer specific documentation has been received, the documentation is created and prepared for a shipment to the customer.", "Outcome": "The customer receives specific documentation as requested.", "GUID": "56165656-7169-11e9-2ddf-001bc640cd9b", "name": "Prepare customer specific documentation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.8062000815280075, "y": -1.495016611295681, "z": 2.8504808545984317 }, "color": "#66CCFF", "size": 1.0 }, { "id": "319", "text": "Process", "data": { "Advisory_Notes": "If assembly orders are used for final filling or packaging, typically sales BOMs are used to specify the components (product and packaging material). Sometimes, assembly orders are used for processes like blending and mixing. In such cases, either a configuration logic is established or the BOM is specified for each order specifically. Even more complex configurations are typically handled using configurable products.", "KeyActivities": "Enter components in sales order,\n Determine required components", "Type": "Business Process", "Description": "An assembly is either done based on a simple sales BOM (bill of material) or on a more complex configuration logic. The outcome of this process serves as input for determining the price and conditions of the assembly order as well as for the actual assembly work.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "Once the sales order data for assembly production has been captured, the next step is to define how the product will be assembled and what components will be used for production.", "Outcome": "The product configuration and required components are defined based on the sales order.", "GUID": "768b35bc-d4a1-11eb-2c3e-001bc641ce4f", "name": "Configure product (Assembly)", "Business_Rules": "Depending on the product and type of assembly, rules to limit options might be required.", "Prerequisite": "" }, "position": { "x": 3.48910804957216, "y": -1.4916943521594686, "z": 3.581357985235595 }, "color": "#66CCFF", "size": 1.0 }, { "id": "321", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create standard sales order ,\n Create sales order for dropshipment,\n Create sales order with scheduling agreement,\n Create sales order for free of charge,\n Enter sales order header data,\n Enter item data and quantity,\n Save sales order,\n Trigger credit block management,\n Trigger back order processing,\n Trigger dangerous goods check compliance,\n Trigger resolution of global trade block,\n Create sales order for consignment sales", "Type": "Business Process", "Description": "Receiving an assembly order and capturing it in a standard format necessary for further processing are the key first steps for the assembly sales scenario.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Once the customer order is placed, the data must be amended, stored and forwarded for further processing. This might include transferring or copying data from other documents such as quotations or frame contracts.", "Outcome": "All relevant information regarding the customers order is documented. The information captured provides the basis for determining whether the order can be fulfilled.", "GUID": "7263da23-7e53-11e5-0a66-001bc640cd9b", "name": "Receive assembly order and capture sales order data", "Business_Rules": "", "Prerequisite": "Prerequisite: set-up of communication channels to be used." }, "position": { "x": 4.164445171323803, "y": -1.4883720930232558, "z": 4.319420842547975 }, "color": "#66CCFF", "size": 1.0 }, { "id": "328", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create standard sales order ,\n Create sales order for dropshipment,\n Create sales order with scheduling agreement,\n Create sales order for free of charge,\n Enter sales order header data,\n Enter item data and quantity,\n Create sales order for consignment sales,\n Enter data from quotation to sales order,\n Trigger credit block management,\n Trigger back order processing,\n Trigger dangerous goods check compliance,\n Trigger resolution of global trade block,\n Save sales order,\n Perform global trade check for sales", "Type": "Business Process", "Description": "For customer orders related to a quotation, information from the quotation is transferred to the sales order when the customer order is received. This differs from sales processes where the source of incoming information is only the customer order itself.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Once the customer order is placed, information from the quotation is transferred to the sales order, updated and enriched if necessary.", "Outcome": "Sales order with reference to the quotation is created.", "GUID": "7c55366c-7e54-11e5-0a66-001bc640cd9b", "name": "Receive customer order and transfer quotation to sales order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.3806157567127404, "y": -1.485049833887043, "z": 1.4470314897459926 }, "color": "#66CCFF", "size": 1.0 }, { "id": "330", "text": "Process", "data": { "Advisory_Notes": "For inquiries from and quotations for new potential customers, a dummy customer master might be used. Latest with the order entry, a real customer master gets created and the sales order will be captured with reference to it.", "KeyActivities": "Enter inquiry information into system,\n Assign relevant sales department,\n Assign business partner to inquiry,\n Evaluate request and maintain in system ,\n Request additonal inquiry information,\n Request additonal information,\n Resolve ambiguous business partner assignment,\n Resolve ambiguous sales department assignment,\n Trigger quotation for new customer,\n Trigger quotation for existing customer", "Type": "Business Process", "Description": "Process describes the initial capturing and checking of an inquiry. In comparison to a lead an inquiry contains an explicit request for a quotation. Receiving the customer inquiry and capturing it in a format necessary for further processing and initiating pre-sales business processes.", "hasAssignment": true, "Process_Group": "Pre-order Management", "Scope": "Once a customer inquires about a certain product, the data must be recorded, stored and forwarded for further processing.", "Outcome": "All relevant information regarding the customers inquiry is documented. The information captured provides the basis for preparing a quotation or reservation of goods.", "GUID": "f80615ee-7e50-11e5-0a66-001bc640cd9b", "name": "Receive and capture customer inquiry", "Business_Rules": "Rules should determine in which cases inquiries have to be documented. There are several aspects why inquiries should be captured in the system: ***Avoidance of duplicated capturing of data ***Considering the information in planning ***Internal compliance and approval guidelines ***Using the information for reporting and identifying reasons for lost sales", "Prerequisite": "" }, "position": { "x": 2.0595682856765363, "y": -1.4817275747508307, "z": 2.18132493605043 }, "color": "#66CCFF", "size": 1.0 }, { "id": "332", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Approve quotation,\n Check quotation,\n Send out quotation,\n Change quotation", "Type": "Business Process", "Description": "Quotation is a binding commitment and can deal with significant product quantities and monetary values. Therefore, it must be ensured that information included into quotation is correct and corresponds to companys interests, which is ensured through an approval process.", "Process_Group": "Pre-order Management", "hasAssignment": true, "Scope": "After passing all checks related to the quotation, the commercial aspects of the quotation are approved and quotation is sent to the customer.", "Outcome": "Quotation is sent to customer.", "GUID": "f806160f-7e50-11e5-0a66-001bc640cd9b", "name": "Approve and send out quotation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.730875795642315, "y": -1.478405315614618, "z": 2.9227243094029505 }, "color": "#66CCFF", "size": 1.0 }, { "id": "334", "text": "Process", "data": { "Advisory_Notes": "In case standard agreements exist, the check with the supplier might be replaced by an internal check against standard lead times documented in the respective master data.", "KeyActivities": "Copy data from inquiry to quotation,\n Calculate pricing,\n Change proposed sales price,\n Create quotation", "Type": "Business Process", "Description": "In order to quote a price and conditions to the customer, the quotation must be created and processed. Depending on the business model this may include collecting different information and processing various checks. Base for the creation of a quotation are customer details and information from the customer inquiry.", "hasAssignment": true, "Process_Group": "Pre-order Management", "Scope": "A quotation document is prepared based on information captured in the inquiry. The sales price is calculated and conditions determined (e.g. rebates, shipping conditions, pre-payment requirements etc.). The availability, and potentially also conditions and price are checked with the supplier.", "Outcome": "A quotation is prepared and can be formally processed.", "GUID": "5fbf8d47-82c7-11e5-0a66-001bc640cd9b", "name": "Create quotation for trading goods", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.3944827150163186, "y": -1.4750830564784052, "z": 3.6711697178767757 }, "color": "#66CCFF", "size": 1.0 }, { "id": "336", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "After the customer inquiry or information regarding internal product request is received, technical feasibility to produce requested products must be assessed before a quotation can be issued to the customer. ", "Process_Group": "Product Development", "Scope": "In make to order scenarios, the customer inquiry may contain very specific requirements or even request a product that has never been produced before in the specific configuration. Technical feasibility to meet these requirements must be assessed in order to prepare a quotation for the customer. Depending on complexity of the inquiry, the assessment may range from checking if existing products meet specified requirements and changes to product design to complete development of a new product prototype in a R&D project (engineer to order). During the assessment, the components and production steps required for manufacturing are defined, building a foundation for further pricing proposals.", "Outcome": "Technical feasibility to meet requirements contained in customer inquiry is assessed. Manufacturing information for product pricing is available", "GUID": "1cdd809c-7ca3-11e5-0a66-001bc640cd9b", "name": "Gather and document product specifications", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.050333889609684, "y": -1.4717607973421927, "z": 4.426600883598982 }, "color": "#66CCFF", "size": 1.0 }, { "id": "340", "text": "Process", "data": { "Advisory_Notes": "MTO can use either already finally specified material masters (including routing and BOM), or need to be configured. Latter is often done using special routings with criteria for determining whether a production step is required or not and Super BOMs. In differentiation to this case by case configuration a material variant is a material that can be kept in stock and that arises from an individual configuration of a configurable product.", "KeyActivities": "Enter components in sales order,\n Determine required components", "Type": "Business Process", "Description": "Based on received customer order the configuration of the product to be manufactured is captured. The outcome of this process serves as input for the actual manufacturing work.", "hasAssignment": true, "Process_Group": "Sales Order Management", "Scope": "Once the sales order data has been captured, the next step is to define how the product will be configured, what components will be used for production and what production tasks must be carried out. In make to order scenario it is possible that no BOM (bill of material) or routing exist and must be created in this process.", "Outcome": "The product configuration and required components are defined based on the sales order.", "GUID": "7c553669-7e54-11e5-0a66-001bc640cd9b", "name": "Configure product (MTO)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.3423927386143886, "y": -1.4684385382059801, "z": 1.4825591844224506 }, "color": "#66CCFF", "size": 1.0 }, { "id": "342", "text": "Process", "data": { "Advisory_Notes": "Depending on the product structure it must be decided how many production stages are considered during the CTP check and how stock levels of intermediates are factored in. Even more complex rules can be required in case other intermediates can be used as substitutes.", "KeyActivities": "Determine material availability date,\n Calculate ATP quantities and dates,\n Execute ATP check,\n Transfer requirements to detailed scheduling,\n Transfer results to order,\n Reserve temporary planned orders,\n Determine checking method and rule,\n Schedule temporary planned orders,\n Transfer requirements from order", "Type": "Business Process", "Description": "Capable to Promise (CTP) verifies whether a customers order can be fulfilled by production within a given time frame.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "After the customer order data is captured for a make to order production, it must be checked whether the order can be fulfilled. It is verified whether capacity is available to manufacture the finished product in the requested quantity and for the desired delivery date. In doing so, it must be ensured that the order can be placed and fits into the production plan. Components might be checked directly or their availability is considered as given based on the production plan. During the check, it is also possible to run simulations to know how changes in demand or supply conditions will affect the CTP results.", "Outcome": "CTP check is performed.", "GUID": "bf26ba8a-eaa4-11e4-0a66-001bc640cd9b", "name": "Check capability to promise", "Business_Rules": "It must be defined what capacity is checked and reserved: ***Capacity at local manufacturing unit ***Capacity at all manufacturing units owned by the global organisation ***Capacity of external contractors It is necessary to define what consumes capacity and therefore reduces the available capacity. The decision should be made whether capacity can be adjusted due to consumer demand. A production campaign for a certain type of product can be extended/increased.", "Prerequisite": "" }, "position": { "x": 2.0019564336667184, "y": -1.4651162790697674, "z": 2.2343165482313454 }, "color": "#66CCFF", "size": 1.0 }, { "id": "344", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Run resource capacity check,\n Check components to be purchased/manufactured,\n Evaluate results of capability to promise checks,\n Reserve resources and machines,\n Inform customer about alternative date,\n Calculate alternative delivery date,\n Receive response to alternative delivery date,\n Execute MRP,\n Analyze planning situation,\n Inform sales about available date", "Type": "Business Process", "Description": "Capable to Promise (CTP) for quotation verifies whether products related to a quotation can be fulfilled by production within a given time frame.", "Process_Group": "Pre-order Management", "hasAssignment": true, "Scope": "Based on the quotation, It is verified whether capacity is available to manufacture the finished product in the requested quantity and for the desired delivery date. ", "Outcome": "CTP check for quotation is performed.", "GUID": "768b35ce-d4a1-11eb-2c3e-001bc641ce4f", "name": "Check capability to promise for quotation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.65369231845383, "y": -1.4617940199335548, "z": 2.992977961659447 }, "color": "#66CCFF", "size": 1.0 }, { "id": "346", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Copy data from inquiry to quotation,\n Calculate pricing,\n Change proposed sales price,\n Create quotation", "Type": "Business Process", "Description": "In order to quote a price and conditions to the customer, the quotation must be created and processed. Depending on the business model this may include collecting different information and processing various checks. Base for the creation of a quotation are customer details and information from the customer inquiry.", "Process_Group": "Pre-order Management", "hasAssignment": true, "Scope": "A quotation document is prepared based on information captured in the inquiry. The sales price is calculated and conditions determined (e.g. rebates, shipping conditions, pre-payment requirements etc.). The requested quantity and delivery data is checked against production capabilities and/or production plans.A quotation document is prepared based on information captured in the inquiry. A sales price is calculated and conditions determined (e.g. rebates, shipping conditions, pre-payment requirements etc.). The requested quantity and delivery data is checked against production capabilities and/or production plans.", "Outcome": "A quotation is prepared and can be formally processed.", "GUID": "7c55365a-7e54-11e5-0a66-001bc640cd9b", "name": "Create quotation for MTO", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.297546402879106, "y": -1.4584717607973423, "z": 3.758482103304347 }, "color": "#66CCFF", "size": 1.0 }, { "id": "350", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create standard sales order ,\n Create sales order for dropshipment,\n Create sales order with scheduling agreement,\n Create sales order for free of charge,\n Enter sales order header data,\n Enter item data and quantity,\n Create sales order for service,\n Trigger credit block management,\n Trigger back order processing,\n Trigger dangerous goods check compliance,\n Trigger resolution of global trade block,\n Save sales order,\n Perform global trade check for sales", "Type": "Business Process", "Description": "Receiving the customer order and capturing it in a format necessary for further processing are the key first steps to all sales processes.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Once the customer order is placed, the data must be amended, stored and forwarded for further processing. This might include transferring or copying data from other documents such as quotations or frame contracts.", "Outcome": "All relevant information regarding the customers order is documented. The information captured provides the basis for determining whether the order can be fulfilled.", "GUID": "4cb51061-7e56-11e5-0a66-001bc640cd9b", "name": "Receive customer order and capture sales order data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9334651241780754, "y": -1.4551495016611296, "z": 4.530767276838963 }, "color": "#66CCFF", "size": 1.0 }, { "id": "352", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Analyse ATP situation,\n Reschedule sales order confirmations,\n Evaluate supplier options with production planners and purchasing ,\n Communicate results to all affected entities", "Type": "Business Process", "Description": "Back order processing must be performed in case the ATP check did not provide a satisfying result, or an unplanned change to the supply situation requires a reconsideration/ recalculation of already confirmed quantities and dates. The process might affect other sales orders, stock transfer orders, and confirmed documents such as material reservations, production or repair orders, which compete with the respective sales documents for the available quantity of the requested material. The resolution of a shortage situation includes the alignment (and consequent adjustment) of the supply situation as well as a reallocation of already confirmed and allocated ATP quantities. All affected parties must be involved or informed accordingly.", "hasAssignment": true, "Process_Group": "Pre-order Management", "Scope": "After the ATP situation has been analysed, a solution is elaborated by e.g. rescheduling the order confirmation or evaluating other supplier options. Finally the solution is communicated with all relevant parties.", "Outcome": "Aligned supply situation and communicated with all affected parties", "GUID": "3e124dd1-602a-11e8-2ddf-001bc640cd9b", "name": "Perform back order processing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.3032558141023707, "y": -1.4518272425249168, "z": 1.5170775468012065 }, "color": "#66CCFF", "size": 1.0 }, { "id": "354", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review ATP results for sales orders,\n Reconfirm order to customer,\n Contact MRP planner", "Type": "Business Process", "Description": "The results of the final ATP check need to be reviewed and the order confirmation to the customer is sent out. If the ATP check has not already been (re-)performed, this needs to be done now out of the individual sales document to consider the newly available ATP quantities and to adjust confirmation dates.", "hasAssignment": true, "Process_Group": "Pre-order Management", "Scope": "After reviewing the results of the ATP, the customer needs to be informed via order confirmation or the supply situation must be clarified with the MRP planner.", "Outcome": "Reviewed ATP and communicated order confirmation", "GUID": "3e124dd3-602a-11e8-2ddf-001bc640cd9b", "name": "Review ATP and reconfirm order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9429816416081507, "y": -1.4485049833887045, "z": 2.2857870286563653 }, "color": "#66CCFF", "size": 1.0 }, { "id": "358", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Assign source of supply,\n Determine source of supply,\n Assign source of supply according to quota arrangement", "Type": "Business Process", "Description": "Determine supply source and conditions aims at finding the external source from which a customer order will be fulfilled, as well as agreeing on the related conditions. The Determine supply source and conditions process is required for third party sales and sales via subcontracting, as well as in certain constellations of intercompany processes. In case of the latter, external source may also refer to other entities of the group.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "After the customer order data is captured, the external source (external vendor) used to fulfil the order and related conditions must be determined.", "Outcome": "Source of supply and conditions related to the order are defined and documented.", "GUID": "768b35b6-d4a1-11eb-2c3e-001bc641ce4f", "name": "Determine supply source and conditions- Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.5747021967864456, "y": -1.4451827242524917, "z": 3.0611939823969094 }, "color": "#66CCFF", "size": 1.0 }, { "id": "360", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create standard sales order ,\n Create sales order for dropshipment,\n Create sales order with scheduling agreement,\n Create sales order for free of charge,\n Enter sales order header data,\n Enter item data and quantity,\n Create sales order for consignment sales,\n Trigger credit block management,\n Trigger back order processing,\n Trigger dangerous goods check compliance,\n Trigger resolution of global trade block,\n Save sales order,\n Perform global trade check for sales", "Type": "Business Process", "Description": "In the sales via subcontracting scenario, once the selling entity has accepted a customer order, a purchase order is issued to the subcontractor. Receipt of this order and capturing it in a format necessary for further processing are the key first steps required for fulfillment of the subcontracting service.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Once a purchase order is received, its data must be amended, stored and forwarded for further processing.", "Outcome": "All relevant information regarding the received purchase order are documented. The information captured provides the basis for determining whether the order can be fulfilled.", "GUID": "e7ceea7f-7e57-11e5-0a66-001bc640cd9b", "name": "Receive subcontracting order and capture sales order data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.1983651077944564, "y": -1.441860465116279, "z": 3.84323569889266 }, "color": "#66CCFF", "size": 1.0 }, { "id": "364", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Upon the commercial completion of the solution, all costs have been allocated. Respective documents (cost objects) are marked as commercially completed. This signifies the conclusion of the solution from an accounting and controlling perspective.", "Process_Group": "Project Accounting", "Scope": "After all solution activities have been completed, the actual costs of individual solution items (physical goods, services, projects, etc.) are determined, and remaining commitments and accruals are removed. The completion of a solution is typically associated with a quality control gate.", "Outcome": "Solution commercially completed.", "GUID": "023b0c61-9b2a-11ee-3781-0201b014c5b2", "name": "Complete solution commercially", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.813918439757848, "y": -1.4385382059800664, "z": 4.631849105365487 }, "color": "#66CCFF", "size": 1.0 }, { "id": "365", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the approval of the solution order that represents a commitment to fulfill the order.", "Process_Group": "Sales Order Management", "Scope": "After all checks related to the solution order and all its items (physical goods, services, projects, and subscriptions) have been performed, the final decision is made regarding execution of the order. A commitment to the customer is made.", "Outcome": "Solution order approved.", "GUID": "b8ae1f93-9b1d-11ee-3781-0201b014c5b2", "name": "Approve solution order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.263231627753414, "y": -1.435215946843854, "z": 1.5505630766413407 }, "color": "#66CCFF", "size": 1.0 }, { "id": "366", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Transfer billing milestones to sales order,\n Generate customer invoice based on billing plan,\n Send invoice to customer,\n Accounts receivable posting,\n Revenue posting,\n Event-based revenue recognition posting", "Type": "Business Process", "Description": "This process involves activities required to create a billing document that is sent to the customer for payment.", "hasAssignment": true, "Process_Group": "Billing, Rebates and Commissions", "Scope": "The milestones set in the project are transferred to the sales order and a billing document is created.", "Outcome": "Billing document is created and can be sent to the customer.", "GUID": "ca0ea8e9-7eef-11e5-0a66-001bc640cd9b", "name": "Perform milestone billing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8826840597781374, "y": -1.4318936877076411, "z": 2.3357013360139414 }, "color": "#66CCFF", "size": 1.0 }, { "id": "368", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the creation of solution order, which serves as a central document to the customer, combining sales items, service and service contract items, subscriptions and project items for the specific solution offering. Typically, the solution order is created with the reference to a customer quotation.", "Process_Group": "Sales Order Management", "Scope": "Once the clarification and negotiation with the customer concludes in an order, the data must be captured for further processing. This might include transferring or copying data from other documents such as quotations or frame contracts to create the solution order.", "Outcome": "Solution order created.", "GUID": "b8ae1f80-9b1d-11ee-3781-0201b014c5b2", "name": "Create solution order with reference to quotation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.4939592074349344, "y": -1.4285714285714286, "z": 3.127325929872119 }, "color": "#66CCFF", "size": 1.0 }, { "id": "369", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "A solution achieves technical completion when all individual solution items (physical goods, services, projects, etc.) are finished, even though costs are still anticipated. The final activities in the technical solution closure encompass solution evaluation, the preparation of the final report, and the handover and acceptance of the solution. During the solution handover, a briefing of employees can be conducted as needed.", "Process_Group": "Production Operations", "Scope": "Once all solution-related activities have been performed and confirmed, those documents requiring status updates to document technical completion are set accordingly.", "Outcome": "Solution technically completed.", "GUID": "b8ae1faf-9b1d-11ee-3781-0201b014c5b2", "name": "Complete solution technically", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.0970063527897858, "y": -1.425249169435216, "z": 3.9253728040505544 }, "color": "#66CCFF", "size": 1.0 }, { "id": "370", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Start R&D work,\n Perform report on R&D work,\n Analyze R&D work results,\n Complete R&D work,\n Confirm completion of R&D work,\n Track project milestone,\n Report on R&D project progress ,\n Trigger service procurement,\n Trigger material procurement,\n Request rework of R&D task (s)", "Type": "Business Process", "Description": "In a project environment, it is necessary to perform required R&D work, track the process and confirm upon completion.", "Process_Group": "Product Development", "hasAssignment": true, "Scope": "Required R&D work is performed as specified in the project plan. Milestones are tracked, and the status of the project is reported.", "Outcome": "Completion of R&D work is confirmed", "GUID": "19efab1a-7ef6-11e5-0a66-001bc640cd9b", "name": "Execute R&D work", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.6917752242159674, "y": -1.4219269102990033, "z": 4.72977755226027 }, "color": "#66CCFF", "size": 1.0 }, { "id": "372", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process encompasses activities associated with fulfilling individual solution items, including procurement, production, service provision, and project delivery. If physical goods constitute a part of the overall solution, outbound delivery is also integral to this orchestration. Furthermore, the process entails monitoring the overall solution execution, encompassing activities like tracking changes in availability, confirmation dates, and priorities. In the event of such changes, it is imperative to inform the customer promptly. More details can be derived from the individual processes related to the fulfillment of order items of the respective specialized E2E scenarios.", "Process_Group": "Production Operations", "Scope": "Depending on the solution items, materials or services are being procured, physical goods are produced, services are provided, projects are delivered etc. All these activities are closely monitored and exceptions are handled accordingly.", "Outcome": "Solution delivered to the customer.", "GUID": "b8ae1fa5-9b1d-11ee-3781-0201b014c5b2", "name": "Orchestrate and monitor solution execution", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.2223474281956985, "y": -1.4186046511627906, "z": 1.5829929768585083 }, "color": "#66CCFF", "size": 1.0 }, { "id": "378", "text": "Process", "data": { "Advisory_Notes": "The design and the quality of this process is essential to avoid any changes to the sales order later in the sales and delivery process. All relevant and necessary data should be captured in order to allow an uninterrupted order processing.", "KeyActivities": "Create sales order for dropshipment,\n Enter sales order header data,\n Enter item data and quantity,\n Trigger credit block management,\n Trigger back order processing,\n Trigger dangerous goods check compliance,\n Trigger resolution of global trade block,\n Save sales order,\n Perform global trade check for sales", "Type": "Business Process", "Description": "Receiving the customer order and capturing it in a format necessary for further processing are the key first steps to all sales processes.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Once the customer order is placed, the data must be amended, stored and forwarded for further processing. This might include transferring or copying data from other documents such as quotations or frame contracts.", "Outcome": "All relevant information regarding the customers order is documented. The information captured provides the basis for determining whether the order can be fulfilled.", "GUID": "2a215fa6-7eec-11e5-0a66-001bc640cd9b", "name": "Receive customer order and capture 3rd party sales order data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8211047390146173, "y": -1.415282392026578, "z": 2.3840254884414516 }, "color": "#66CCFF", "size": 1.0 }, { "id": "388", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Report on project progress,\n Report on assembly work ,\n Analyze assembly work results,\n Complete assembly work,\n Track project milestone,\n Trigger service procurement,\n Trigger material procurement,\n Request rework of assembly,\n Start assembly work", "Type": "Business Process", "Description": "In a project assembly situation it is necessary to perform assembly work at the customers location. For this purpose, work performed must be tracked and confirmed upon completion.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "Once the WBS element is released, assembly work can begin with execution of all the required tasks. At each stage of the assembly, completion of activities is followed by confirmation and reporting to the responsible project lead on-site at the customer location.", "Outcome": "Assembly work is complete and confirmed", "GUID": "8172e291-7ef7-11e5-0a66-001bc640cd9b", "name": "Execute assembly work", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.4115183205534874, "y": -1.4119601328903655, "z": 3.1913287811873734 }, "color": "#66CCFF", "size": 1.0 }, { "id": "390", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create sales order based on quotation data,\n Enter sales order header data,\n Enter item data and quantity,\n Trigger credit block management,\n Trigger back order processing,\n Trigger dangerous goods check compliance,\n Trigger resolution of global trade block,\n Save sales order", "Type": "Business Process", "Description": "For customer projects, a sales order must be created with reference to the quotation sent to the customer.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "After sending the customer quotation, a customer order is created with reference to the quotation. The project baseline is adjusted based on sales order and technical documents are assigned to project related activities.", "Outcome": "Customer order is created with reference to quotation.", "GUID": "ca0ea8e0-7eef-11e5-0a66-001bc640cd9b", "name": "Create sales order with reference to quotation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9935391433160436, "y": -1.4086378737541527, "z": 4.004837499504149 }, "color": "#66CCFF", "size": 1.0 }, { "id": "397", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create return delivery order", "Type": "Business Process", "Description": "A delivery is the central object of the goods receipt process containing all the data required for triggering and monitoring it, starting from goods receipt in the yard and ending with transferral of the goods to the final putaway. In a customer return (as well as consignment pick-up) process, a return delivery document is used for this purpose.", "Process_Group": "Customer Returns", "hasAssignment": true, "Scope": "After the return order (consignment pick-up order for consignment process) is created, a return delivery is created with reference to it.", "Outcome": "Return delivery is created and goods receipt process can be initiated.", "GUID": "3712628c-e9bd-11e4-0a66-001bc640cd9b", "name": "Create return delivery", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.5671186331483, "y": -1.4053156146179402, "z": 4.824485947440017 }, "color": "#66CCFF", "size": 1.0 }, { "id": "399", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain quantity of the returnable packaging to the sales order,\n Maintain value of the returnable packaging to the sales order,\n Assign plant for customer return ", "Type": "Business Process", "Description": "The assignment of returnable packaging to a sales order ensures that the cost and quantity of the materials are mapped to the customer order.", "Process_Group": "Returnable Packaging Management", "hasAssignment": true, "Scope": "Information about the quantity and value of the returnable packaging, as well as the plant to which the materials are to be returned is linked to the customer order and documented accordingly.", "Outcome": "Returnable packaging information is recorded with the sales order data.", "GUID": "605f699d-7e4f-11e5-0a66-001bc640cd9b", "name": "Assign returnable packaging to sales order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1806310495578807, "y": -1.4019933554817277, "z": 1.6143451690452872 }, "color": "#66CCFF", "size": 1.0 }, { "id": "403", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes steps to process deposit request for returnable packaging. Deposits are used especially in relation to returnable packaging to ensure that in case the packaging is not returned by customer, costs of the packaging is covered by deposit payment from customer.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "Determining deposit amount, creating and releasing deposit request to customer.", "Outcome": "Deposit request sent to customer.", "GUID": "4f186adf-95ba-11ee-3781-0201b014c5b2", "name": "Process deposit request for returnable packaging", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7582856027685871, "y": -1.398671096345515, "z": 2.4307265866601915 }, "color": "#66CCFF", "size": 1.0 }, { "id": "407", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create final settlement,\n Release agreement for settlement,\n Create partial settlement,\n Create normal rebate payment,\n Verify accruals,\n Generate credit memo,\n Accounts receivable posting (credit memo)", "Type": "Business Process", "Description": "At the end of validity period of a rebate agreement the transactions under the terms of the agreement are evaluated and mutual liabilities arising form the agreement are settled. During the validity of the rebate agreement, partial settlements can take place.", "hasAssignment": true, "Process_Group": "Billing, Rebates and Commissions", "Scope": "The customer invoices are evaluated and accrued. Rebates are calculated and a credit note request gets created. At the end of the rebate agreement, the final settlement is executed to close the agreement.", "Outcome": "Rebates are calculated in accordance to the agreement and credit note requests are created.", "GUID": "7093bfdb-7e51-11e5-0a66-001bc640cd9b", "name": "Settle rebate agreement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.327435662231812, "y": -1.3953488372093024, "z": 3.253158962942261 }, "color": "#66CCFF", "size": 1.0 }, { "id": "409", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter conditions,\n Enter accruals and scales,\n Enter rebate header data,\n Enter validity period", "Type": "Business Process", "Description": "After rebate agreement terms have been negotiated with the customer, a rebate agreement is created in the system containing the agreement details. The agreement will be further used for tracking of customer commitment fulfillment.", "hasAssignment": true, "Process_Group": "Billing, Rebates and Commissions", "Scope": "A rebate agreement is created in the system after general negotiation with customer. The agreement contains details necessary for tracking of customer commitment fulfillment and calculation of applied rebates during settlement - rebate validity period, value/volume of goods customer commits to, items, for which rebates are relevant, rebate amounts/percentages, payment methods etc.", "Outcome": "Rebate agreement is created and applied rebates can be tracked.", "GUID": "7093bfe7-7e51-11e5-0a66-001bc640cd9b", "name": "Capture rebate agreement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.8880339202685237, "y": -1.3920265780730898, "z": 4.081575685366918 }, "color": "#66CCFF", "size": 1.0 }, { "id": "413", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Save scheduling agreement,\n Trigger credit block management,\n Trigger back order processing,\n Trigger dangerous goods check compliance,\n Trigger resolution of global trade block,\n Perform global trade check for sales,\n Outline time period,\n Enter scheduling agreement header data,\n Enter item and requested quantity,\n Create schedule lines", "Type": "Business Process", "Description": "After an outline agreement with the customer regarding items, prices, delivery quantities and dates is negotiated, a scheduling agreement is created in the system containing the agreement details (individual deliveries form schedule lines) and serve as base for further performing of actual deliveries.", "hasAssignment": true, "Process_Group": "Customer Contracts", "Scope": "A scheduling agreement is created in the system. Schedule lines for individual deliveries can be entered either at creation of the scheduling agreement or later. Similar to a standard sales order, dangerous goods, global trade, availability and credit management checks are performed, when the scheduling agreement is created. Because of the nature and often long lead times of such agreements, the result of an ATP check and credit check might only be for information purposes.", "Outcome": "Scheduling agreement is created and individual deliveries can be carried out.", "GUID": "4021aa79-7e5b-11e5-0a66-001bc640cd9b", "name": "Capture scheduling agreement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.4400335332669556, "y": -1.388704318936877, "z": 4.915909813045685 }, "color": "#66CCFF", "size": 1.0 }, { "id": "418", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Save consignment pickup order ,\n Confirm consignment pickup order,\n Approve consignment pick up order,\n Inform sales person of consignment pickup order to be changed,\n Change consignment pick up order", "Type": "Business Process", "Description": "Approval of consignment pickup order is required to ensure that customer request to return not consumed by the customer back to the warehouse in accordance with company rules.", "hasAssignment": true, "Process_Group": "Sales Order Management", "Scope": "A consignment pickup allows a customer to return goods and materials, which were not consumed. Once such a request is received and recorded in form of a consignment pickup order, its validity is checked. In case it is in accordance with company rules, the pickup is confirmed and can be processed. A consignment pickup allows a customer to return goods and materials, which were not consumed.", "Outcome": "Once a pick-up request is received and recorded in form of a consignment pickup order, its validity is checked. In case it is in accordance with company rules, the pickup is confirmed and can be processed.", "GUID": "6bcd18ca-624c-11e8-2ddf-001bc640cd9b", "name": "Confirm consignment pick up order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1381108925195043, "y": -1.3853820598006643, "z": 1.6445983085022486 }, "color": "#66CCFF", "size": 1.0 }, { "id": "420", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter order type,\n Create return sales order with reference,\n Enter consignment pick-up order header data,\n Enter requested pick-up date,\n Copy data from consignment fill-up order ,\n Enter sales order item and requested quantity,\n Create return sales order without reference,\n Contact customer and request missing data,\n Enter missing consignment pick up data,\n Check availability of consignment stock,\n Save consignment pick up order", "Type": "Business Process", "Description": "With the creation of a consignment pick-up order, goods returned by the customer are recorded in the warehouse of the seller i.e. the company that actually owns the goods. This precedes the transportation of the goods from the customers storage location back to the supplying company.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "When the customer no longer requires goods given to them on consignment, the creation of a consignment pick-up order triggers a return delivery to the seller.", "Outcome": "Order for consignment pick-up is created.", "GUID": "5abd47b1-7e47-11e5-0a66-001bc640cd9b", "name": "Receive customer notification and create consignment pick-up order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.694269418562445, "y": -1.3820598006644518, "z": 2.475772836373336 }, "color": "#66CCFF", "size": 1.0 }, { "id": "424", "text": "Process", "data": { "Advisory_Notes": "Even though, the consignment goods are still owned by the selling company, prices get determined at this stage and later copied to the consignment issue order. The price will be necessary for any pro forma invoice as well as will be used in case of excise tax procedures apply.", "KeyActivities": "Enter sales order header data,\n Enter item data and quantity,\n Create sales order for consignment sales,\n Trigger credit block management,\n Trigger back order processing,\n Trigger dangerous goods check compliance,\n Trigger resolution of global trade block,\n Save sales order,\n Perform global trade check for sales", "Type": "Business Process", "Description": "The consignment scenario is initiated with a fill-up order, which triggers the transfer of consignment goods to the customer. Depending on the agreement with the customer, the planning and respectively the request for a new fill-up can be either done by the customer or by the seller.", "hasAssignment": true, "Process_Group": "Sales Order Management", "Scope": "Once the consignment order has been placed, the data must be amended, stored and forwarded for further processing.", "Outcome": "All relevant information regarding the consignment order is documented. The information captured provides the basis for determining whether the consignment order can be fulfilled.", "GUID": "6581198b-7e49-11e5-0a66-001bc640cd9b", "name": "Capture consignment fill-up order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.24176847628426, "y": -1.3787375415282392, "z": 3.3127743808986065 }, "color": "#66CCFF", "size": 1.0 }, { "id": "426", "text": "Process", "data": { "Advisory_Notes": "Most of the data will be copied from the consignment fill-up order including price. However, there might be scenarios where price determination is affected by the date of consumption and therefore price determination runs again. Customer notification can be part of self invoicing. In this case payment will be settled with issuing the invoice.", "KeyActivities": "Create consignment issue order,\n Check availability of consignment stock,\n Receive consumption list,\n Save consignment issue order,\n Enter usage per product and batch ", "Type": "Business Process", "Description": "This process includes the customer notification that goods provided on consignment have been consumed captured by an consignment issue order. From the sellers perspective this happens when the goods are sold.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Once the customer provides information that goods on consignment have been consumed, the data is amended, stored and forwarded for further processing.", "Outcome": "A sales order for consignment issue is created.", "GUID": "7f93241f-7e49-11e5-0a66-001bc640cd9b", "name": "Capture and issue consignment consumption", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.780562512030413, "y": -1.3754152823920265, "z": 4.155535117971104 }, "color": "#66CCFF", "size": 1.0 }, { "id": "428", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create non physical outbound delivery ,\n Post goods issue of consignment stock,\n Inventory reduction posting (consignment issue),\n COGS posting", "Type": "Business Process", "Description": "When the goods provided on consignment have been sold, the ownership of the goods must be transferred to the customer. Since the goods are already being stored at the customers location, the movement is non-physical and represents only a change of ownership. Nevertheless an outbound delivery needs to be created to record the goods issue from consignment stock.", "Process_Group": "Outbound Delivery Management", "hasAssignment": true, "Scope": "Once the customer provides notification that the goods have been sold, the outbound delivery is created and goods issue posted, allocating the goods as a property of the customer.", "Outcome": "Goods provided on consignment become property of the customer. This triggers the invoicing process.", "GUID": "7f932416-7e49-11e5-0a66-001bc640cd9b", "name": "Simulate outbound delivery and post goods issue", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.310606444622676, "y": -1.372093023255814, "z": 5.003986907339268 }, "color": "#66CCFF", "size": 1.0 }, { "id": "433", "text": "Process", "data": { "Advisory_Notes": "There is no direct link between the different sales orders and stock movements throughout the consignment scenarios except for the fill-up and issue. Thus, it is possible to post a consignment return with higher quantities or for other batches than actually posted in the issue.", "KeyActivities": "Send consignment return confirmation,\n Confirm consignment return order ", "Type": "Business Process", "Description": "Approval of consignment return order is required to ensure that customer request to returned previously consumed goods/materials is in accordance with company rules.", "hasAssignment": true, "Process_Group": "Sales Order Management", "Scope": "A consignment return allows customer to give company back goods/materials, which were previously reported as consumed and request refund of made payment (if applicable). Once such request is received and recorded in form of a consignment return order, its validity is checked and if request is considered justified and in accordance with company rules, the return is confirmed and can be processed.", "Outcome": "Consignment return order validity is checked and confirmed, order can be processed.", "GUID": "aa8c61ab-7e48-11e5-0a66-001bc640cd9b", "name": "Confirm consignment return order", "Business_Rules": "Rules must be established for evaluating, when customer returns can be considered justified.", "Prerequisite": "" }, "position": { "x": 1.0948159049757047, "y": -1.3687707641196014, "z": 1.6737317987695126 }, "color": "#66CCFF", "size": 1.0 }, { "id": "435", "text": "Process", "data": { "Advisory_Notes": "The return is usually posted with the same batch number the issue has been posted from except the company policies require issuing a new batch number in case of returns.", "KeyActivities": "Create return sales order with reference,\n Create return sales order without reference,\n Copy data from consignment fill-up order ,\n Enter consignment return order header data,\n Enter consignment return order item and quantity,\n Enter order type,\n Create consignment return order", "Type": "Business Process", "Description": "When the customer provides notification that goods sold through consignment issue are being returned to consignment stock, it is necessary to create a consignment return order to initiate the change of ownership of the goods.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Once the customer provides notification to return consignment goods, a consignment return order is created. In this case the consignor must take back ownership of the goods.", "Outcome": "The consignment return order is created, triggering the non-physical goods receipt for consignment returns process.", "GUID": "aa8c61b1-7e48-11e5-0a66-001bc640cd9b", "name": "Receive customer notification and create consignment return order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6290997688736892, "y": -1.3654485049833887, "z": 2.519133569911626 }, "color": "#66CCFF", "size": 1.0 }, { "id": "437", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Inventory increase (return delivery) posting,\n Create non physical outbound delivery ,\n Post goods receipt of consignment return", "Type": "Business Process", "Description": "Non-physical goods receipt is required to record the change of ownership of goods from an external entity to the organization. Physically, the goods are still located at customer premises. Return delivery is required to record goods receipt into consignment stock.", "Process_Group": "Customer Returns", "hasAssignment": true, "Scope": "Once the consignment return order has been created, the return delivery is created and non-physical goods receipt posted. This documents the fact that goods have been returned by the customer and are now owned by the organization. However, the goods are still at the customers location physically.", "Outcome": "Non-physical goods receipt is recorded, goods become property of the organization and consignment stock has increased.", "GUID": "1577b599-7e48-11e5-0a66-001bc640cd9b", "name": "Simulate return delivery and post goods receipt", "Business_Rules": "Rules must be established regarding: ***How to deal with consignment returns i.e. if they are added to regular customer consignment stock or tracked separately.", "Prerequisite": "" }, "position": { "x": 2.1545750852780117, "y": -1.3621262458471761, "z": 3.3701344486383995 }, "color": "#66CCFF", "size": 1.0 }, { "id": "442", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Save sample order,\n Review sample order,\n Approve sample order,\n Inform responsible about necessary changes", "Type": "Business Process", "Description": "Approval of the sample order is provided through the confirmation and represents a commitment to deliver the sample goods to the customer on the agreed date.", "hasAssignment": true, "Process_Group": "Sales Order Management", "Scope": "After all checks related to the sample order have been performed the final decision is made regarding execution of the order. A commitment to the customer is made, triggering the outbound logistics process.", "Outcome": "A decision is made to deliver the samples to customer.", "GUID": "5ae11e01-7e59-11e5-0a66-001bc640cd9b", "name": "Save and approve sample order", "Business_Rules": "It is essential to define how sample order confirmation is linked to inventory management and production processes. Rules must be established for allocating authorization for sample order approval. The format of the confirmation (electronic, paper) and communication channel must be defined.", "Prerequisite": "" }, "position": { "x": 2.6711980855717425, "y": -1.3588039867109636, "z": 4.226665445435427 }, "color": "#66CCFF", "size": 1.0 }, { "id": "444", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create reservation for a specific batch of product,\n Transfer reservation into the warehouse,\n Define duration of the reservation", "Type": "Business Process", "Description": "Goods reservation ensures that products related to the customer inquiry will be available when the customer wants to buy them.", "Process_Group": "Inventory Management", "hasAssignment": true, "Scope": "Based on the customer inquiry, a reservation is created for a specific batch of product. This information needs to be transferred to the warehouse in order to ensure that the reserved batch is not shipped out to fulfil another customer order.", "Outcome": "A batch of goods is reserved.", "GUID": "5acb9a3c-7e59-11e5-0a66-001bc640cd9b", "name": "Reserve goods on batch level", "Business_Rules": "The duration of the reservation, means of securing that the batch is not shipped out, and the means of locating the batch and matching it to a sample must be established.", "Prerequisite": "" }, "position": { "x": 3.178925481701641, "y": -1.3554817275747508, "z": 5.08865726707822 }, "color": "#66CCFF", "size": 1.0 }, { "id": "446", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Run billing due list,\n Execute account determination,\n Verify if open item referenced to down payment,\n Analyse customer open items,\n Create manual reference to down payment at line item level,\n Create delivery related billing document,\n Reference billing to outbound delivery document,\n Generate ProForma invoice ,\n Attach ProForma invoice to export related documents", "Type": "Business Process", "Description": "The pro-forma invoice provides the customer with documentation regarding the goods delivered. As opposed to a customer invoice, the pro-forma invoice is not a request for payment.", "hasAssignment": true, "Process_Group": "Billing, Rebates and Commissions", "Scope": "After the samples have been delivered to the customer, a pro-forma invoice is create with information on the quantity (value of samples if required). This concludes the sample handling process.", "Outcome": "Pro-forma invoice is created and sent to the customer.", "GUID": "5acb9a33-7e59-11e5-0a66-001bc640cd9b", "name": "Create pro forma invoice", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.0507755623293635, "y": -1.352159468438538, "z": 1.7017258056489035 }, "color": "#66CCFF", "size": 1.0 }, { "id": "448", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create sample order,\n Determine batch based on the inquiry ,\n Reserve goods in sample", "Type": "Business Process", "Description": "Once customer inquiry is received, a sample order must be created to enable further processing of the customer request.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Data from customer inquiry is amended, stored and forwarded for further processing.", "Outcome": "All relevant information regarding the customers inquiry is documented. The information captured provides the basis for determining batch, from which sample will be drawn and reserving goods in this sample.", "GUID": "5acb9a51-7e59-11e5-0a66-001bc640cd9b", "name": "Create batch sample order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5628210214637908, "y": -1.3488372093023255, "z": 2.5607792671120393 }, "color": "#66CCFF", "size": 1.0 }, { "id": "454", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Change quotation according to customers needs,\n Update components and duration of activities,\n Recalculate project costs,\n Update quotation with new pricing information,\n Reschedule project,\n Approve quotation", "Type": "Business Process", "Description": "Upon revision of the quotation by the customer, changes may be required. Given this, the data must be updated according to the new information.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Based on the requested changes of the customer, the quotation is populated with the new information and sent back to the customer.", "Outcome": "The quotation is updated and sent to the customer", "GUID": "768b35c6-d4a1-11eb-2c3e-001bc641ce4f", "name": "Change quotation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.0659148508268315, "y": -1.345514950166113, "z": 3.4252001151951914 }, "color": "#66CCFF", "size": 1.0 }, { "id": "456", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check tender requirements", "Type": "Business Process", "Description": "The budget is the approved cost structure for a project. It is used by management to approve the expected development of order costs over a given timeframe. Availability control enables the control of costs actively by issuing warnings and error messages when costs are incurred.", "Process_Group": "Project Management", "hasAssignment": true, "Scope": "The original budget is allocated to the WBS elements. After a specified point in time, the budget can only be corrected using budget updates.", "Outcome": "The budget is allocated to the WBS elements.", "GUID": "ab66384d-7e4e-11e5-0a66-001bc640cd9b", "name": "Perform budget planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.560015096637014, "y": -1.3421926910299002, "z": 4.294918241944843 }, "color": "#66CCFF", "size": 1.0 }, { "id": "458", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create inquiry,\n Enter inquiry header data,\n Enter project requirement", "Type": "Business Process", "Description": "When a prospective customer sends an request for a project, the information must be captured and stored for further processing in form of an inquiry.", "hasAssignment": true, "Process_Group": "Pre-order Management", "Scope": "An inquiry of a customer that would require a project for implementation is recorded. A respective project number is then assigned to the inquiry.", "Outcome": "Customer inquiry for a project is created.", "GUID": "ab66382c-7e4e-11e5-0a66-001bc640cd9b", "name": "Create inquiry for customer project", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.045080293436767, "y": -1.3388704318936877, "z": 5.169863248338688 }, "color": "#66CCFF", "size": 1.0 }, { "id": "460", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Send to customer,\n Receive customers response to quotation,\n Update quotation and trigger approval", "Type": "Business Process", "Description": "The quotation is a binding commitment and can deal with significant product quantities and monetary values. Therefore, it must be ensured that the information included in the quotation is correct and corresponds to the companys interests, which is ensured through the approval process.", "Process_Group": "Pre-order Management", "hasAssignment": true, "Scope": "After the quotation is created, it needs to be send to customer and receive feedback. Based on customer response, a quotation is updated, rejected or accepted.", "Outcome": "After passing all checks related to the quotation, the commercial aspects of the quotation are approved and the quotation is sent to the customer.", "GUID": "e22cbe01-e8c2-11e4-0a66-001bc640cd9b", "name": "Send quotation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.0060198474241349, "y": -1.3355481727574752, "z": 1.728561270707151 }, "color": "#66CCFF", "size": 1.0 }, { "id": "462", "text": "Process", "data": { "Advisory_Notes": "The relationship between advance procurement and project budgeting is that when creating a PR for an advance procurement, there needs to be a check whether budget is available. If it is available, the budget is reserved while approving the PR. If the budget is not available, the PR will not be approved.", "KeyActivities": "Identify long lead time components for advance procurement,\n Release long lead time components for procurement", "Type": "Business Process", "Description": "Advance procurement due to long lead times is triggered before the order is confirmed or a certain stage of a project typically required to approve the purchase, is reached. Although whenever possible ordering project-specific materials beforehand is avoided. However, in some situations it is required.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "The data for needed materials with long lead time and feasibility of meeting planned demand is checked. With the release of this activity, the purchase requisition is created and approved. Typically, a budget block is triggered simultaneously. That leads to the creation of purchase order for indirect materials with long lead time. ", "Outcome": "A purchase order is created for the procurement of the required materials.", "GUID": "ab66384a-7e4e-11e5-0a66-001bc640cd9b", "name": "Perform advance procurement of indirect materials", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.4954782991724407, "y": -1.3322259136212624, "z": 2.600681575415242 }, "color": "#66CCFF", "size": 1.0 }, { "id": "464", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain project structure,\n Create customer project", "Type": "Business Process", "Description": "A project is created in order to add further details to the inquiry (for example, scheduling, payment processing). This ensures calculation of the cost as the basis for determining the gross price in the quotation.", "Process_Group": "Project Management", "hasAssignment": true, "Scope": "The project is created with activities, components, and milestones in a complex structure.", "Outcome": "Project is created, and timeline, costs, etc. can now be assigned.", "GUID": "768b35be-d4a1-11eb-2c3e-001bc641ce4f", "name": "Create customer project", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9758481331774413, "y": -1.3289036544850499, "z": 3.477933891640153 }, "color": "#66CCFF", "size": 1.0 }, { "id": "466", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Calculate pricing,\n Change proposed sales price,\n Approve quotation,\n Transfer milestones,\n Create project version,\n Enter quotation header data,\n Copy data from inquiry to quotation", "Type": "Business Process", "Description": "This process ensures the creation of a quotation based on the information in the inquiry. The quotation is subsequently sent to the prospective customer.", "Process_Group": "Pre-order Management", "hasAssignment": true, "Scope": "The inquiry is first copied into the quotation. After maintaining all the details for the labour and materials used in the project, the pricing information is added to the quotation. Project milestones are transferred to the quotation. By means of a project version a snapshot of the project is created before sending out the quotation.", "Outcome": "The quotation is forwarded to the customer", "GUID": "ab663832-7e4e-11e5-0a66-001bc640cd9b", "name": "Create quotation with ref. to customer inquiry", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.447089239055428, "y": -1.3255813953488373, "z": 4.360247040719038 }, "color": "#66CCFF", "size": 1.0 }, { "id": "468", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create work breakdown structure (WBS) for project,\n Create cost estimates,\n Establish costing structure,\n Establish project work list,\n Establish planning forms as variants in work list,\n Assign planning forms to WBS elements", "Type": "Business Process", "Description": "Easy cost planning enables the planning of costs at WBS level based on quantities and characteristics. It is used to create quantity structures for the cost calculation, starting from the project structure.", "hasAssignment": true, "Process_Group": "Project Accounting", "Scope": "Easy cost planning is performed to create a first rough calculation of the project cost.", "Outcome": "Initial estimate of project cost is available", "GUID": "135cff11-e998-11e4-0a66-001bc640cd9b", "name": "Perform easy cost planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9091620021743507, "y": -1.3222591362126246, "z": 5.24754956575971 }, "color": "#66CCFF", "size": 1.0 }, { "id": "473", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review and provide management approval,\n Assess and update purchase order data,\n Issue purchase order,\n Trigger follow up action in procurement", "Type": "Business Process", "Description": "Once issued to vendor the purchase order represents a firm commitment. Therefore, it must be approved before the issue and then transferred to vendor.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "Before committing to the actual purchase of materials or services, an authorised person does a final check if the purchase order is correct and approves it. The PO will then be sent to the vendor.", "Outcome": "The purchase order is issued.", "GUID": "de59c972-7efd-11e5-0a66-001bc640cd9b", "name": "Approve and issue purchase order", "Business_Rules": "Approval rules and limits have to be defined.", "Prerequisite": "" }, "position": { "x": 0.9605792301320043, "y": -1.3189368770764118, "z": 1.7542199242509493 }, "color": "#66CCFF", "size": 1.0 }, { "id": "475", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check EDI Entry,\n Build up document header/ items for FI posting,\n Start Posting FI vendor invoice,\n Change IDOC status to ERROR,\n Check if manual interference necessary,\n Correct error,\n Post vendor invoice to Accounts payable", "Type": "Business Process", "Description": "For intercompany transactions, this process ensures that billing information is received by the delivering entity and the financial obligation related to the transaction is settled.", "hasAssignment": true, "Process_Group": "Accounts Payable", "Scope": "After the goods have been delivered and invoice received, payment is made to the delivering entity and recording in accounting.", "Outcome": "Amount in the intercompany invoice is paid and documented accordingly.", "GUID": "6166270a-7e56-11e5-0a66-001bc640cd9b", "name": "Receive intercompany invoice", "Business_Rules": "It is necessary to define: - General payment terms and condition for intercompany invoicing, - Relations between the selling and shipping operating units in view of intercompany transaction flows.", "Prerequisite": "" }, "position": { "x": 1.4271174491977399, "y": -1.3156146179401993, "z": 2.63881332916812 }, "color": "#66CCFF", "size": 1.0 }, { "id": "477", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter sales order header data,\n Enter item data and quantity,\n Trigger credit block management,\n Trigger back order processing,\n Trigger dangerous goods check compliance,\n Trigger resolution of global trade block,\n Save sales order,\n Create sales order", "Type": "Business Process", "Description": "Receiving the purchase order and capturing it in a format necessary for further processing are the key first steps to all sales processes.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Once the purchase order is placed, the data must be amended, stored and forwarded for further processing. This might include transferring or copying data from other documents such as quotations or frame contracts.", "Outcome": "All relevant information regarding the purchase order is documented. The information captured provides the basis for determining whether the order can be fulfilled.", "GUID": "05042ad3-9404-11e9-0cfc-001bc641ce4f", "name": "Create sales order for intercompany purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8844362501160234, "y": -1.3122923588039868, "z": 3.5282998766046885 }, "color": "#66CCFF", "size": 1.0 }, { "id": "479", "text": "Process", "data": { "Advisory_Notes": "***set-up of possible conversions must be defined. Conversion options are single, multiple or partial ***purchasing strategies for vendors need to be considered (e.g. fair share, contingents) ***special agreements with vendors need to be considered (e.g. FTL/FCL only, min/max quantities, multiple products to be bundled)", "KeyActivities": "Convert purchase requisition into purchase order,\n Copy price into purchase order,\n Save purchase order,\n Update information for purchase order", "Type": "Business Process", "Description": "An official purchase order (PO) has to be created from a purchase requisition (PR) to be able to order materials and services.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "The PO is created with reference to a specific PR. Additional data not provided within the PR has to be maintained.", "Outcome": "A PO is generated.", "GUID": "de59c987-7efd-11e5-0a66-001bc640cd9b", "name": "Convert purchase requisition for direct materials to purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.3324973932082207, "y": -1.308970099667774, "z": 4.422607365647199 }, "color": "#66CCFF", "size": 1.0 }, { "id": "481", "text": "Process", "data": { "Advisory_Notes": "Purchasing products directly for a sales order is used in a variety of business models. It can be a one time opportunity, a frequently applied model, or even a type of outsourced inventory in a JIT-like set-up. Therefore, the interaction between the sales department, the purchasing department, and the vendor in order to clarify availability and delivery dates might differ. In a opportunity sale, it might even be required to identify a source of supply before any commitment to the customer is given.", "KeyActivities": "Determine source of supply,\n Create purchase requisition", "Type": "Business Process", "Description": "A purchase requisition (PR) is created after a sales order has been confirmed. The purchasing department must check which vendor can supply the goods. The goods are delivered directly to the customer, therefore it is necessary to clarify the terms of delivery with the vendor.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "If not already specified by master data, the purchasing department checks vendors to determine which one can supply the products required to fulfil the order.", "Outcome": "The PR is created.", "GUID": "78ced096-7f02-11e5-0a66-001bc640cd9b", "name": "Process purchase requisition for sales orders", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.771263141637606, "y": -1.3056478405315615, "z": 5.321663330181726 }, "color": "#66CCFF", "size": 1.0 }, { "id": "483", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create dispatch advice / ASN,\n Transfer dispatch advice / ASN electronically", "Type": "Business Process", "Description": "A dispatch advice is automatically transferred to the requesting IC entity.", "hasAssignment": true, "Process_Group": "Outbound Delivery Management", "Scope": "A dispatch advice typically refers to a document or notification sent to inform the IC recipient about the dispatch or shipment of goods. It includes details such as item descriptions, quantities, and shipment dates.", "Outcome": "Dispatch advice created and transferred.", "GUID": "6f734268-9406-11e9-0cfc-001bc641ce4f", "name": "Transfer dispatch advice", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9144846466092772, "y": -1.302325581395349, "z": 1.7786842977650377 }, "color": "#66CCFF", "size": 1.0 }, { "id": "485", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Post goods receipt,\n Event-based revenue recognition posting", "Type": "Business Process", "Description": "In a third party sales scenario there is no physical inbound movement of goods or materials. Nevertheless it is necessary to acknowledge change of ownership of goods from supplier to selling entity to be able to further record the sale to the customer.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "Once advanced shipping notification is received, a non-physical goods receipt is recorded, documenting assumption of the title of ownership for the goods or materials by the selling entity. The non-physical goods receipt does not initiate any changes in inventory levels.", "Outcome": "Change of goods ownership is recorded.", "GUID": "2bb46437-7f03-11e5-0a66-001bc640cd9b", "name": "Perform non-physical goods receipt", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.3577850118832395, "y": -1.2990033222591362, "z": 2.6751485681182703 }, "color": "#66CCFF", "size": 1.0 }, { "id": "487", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain product price using pricing scheme,\n Apply product price using pricing scheme", "Type": "Business Process", "Description": "In an intercompany situation, product price may vary from those offers to external customers. In such cases, it is necessary to determine the price offered to the IC buyer. Pricing will be performed, using SD-functionality.", "Process_Group": "Pre-order Management", "hasAssignment": true, "Scope": "Transfer product price is determined based on corporate guidelines and corporate tax regulations.", "Outcome": "Transfer product price is determined.", "GUID": "80843c23-9567-11e8-2ddf-001bc640cd9b", "name": "Determine transfer product price for IC", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7917414352228205, "y": -1.2956810631229236, "z": 3.5762637807222313 }, "color": "#66CCFF", "size": 1.0 }, { "id": "495", "text": "Process", "data": { "Advisory_Notes": "Not all vendor contracts need to be captured in SAP. Often, only details such as prices or rebates will be reflected in the purchasing master data. Only if special treatment of contracts within SAP is required, the contracts have to be captured as such in SAP. This is basically the case for scheduling agreements and for more complex rebate agreements.", "KeyActivities": "Scan signed documents,\n File scanned documents", "Type": "Business Process", "Description": "Receiving information about a supplier contract and capturing it for further processing are key first steps in purchasing processes which are based on the contractual agreement with a supplier.", "hasAssignment": true, "Process_Group": "Sourcing Direct", "Scope": "Details regarding contracts with a supplier are recorded, stored and forwarded for further processing. The information can include the type of products, the quantity and the agreed price, as well as other terms and condition related the purchase.", "Outcome": "All relevant information regarding the contract with the supplier is stored.", "GUID": "ec357bcb-7e11-11e5-0a66-001bc640cd9b", "name": "Capture vendor contract- Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.216317573688188, "y": -1.292358803986711, "z": 4.48195676156753 }, "color": "#66CCFF", "size": 1.0 }, { "id": "497", "text": "Process", "data": { "Advisory_Notes": "The monitoring scope and necessary details must be defined depending on material market availability and importance for the supply chain (e.g. monitoring for deficit components might be stricter then for widely available materials). Rules for sending reminders to vendor (timing etc.) must be defined", "KeyActivities": "Monitor import status and documents,\n Monitor receipt of order acknowledgement,\n Maintain import data,\n Maintain order acknowledgement in purchase order,\n Contact vendor for update,\n Check and follow-up on overdue deliveries,\n Monitor documentation receipt", "Type": "Business Process", "Description": "Monitoring purchase order (PO) process ensures - through communication with the vendor - that the correct material is sent and can be/is delivered on time, and in full quantity.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "After the PO has been sent to the vendor, it needs to be tracked. The vendor hereby sends an order acknowledgement to confirm the receipt of the PO. Furthermore, the delivery date is tracked and, in case of imported material, the estimated time of arrival (ETA) as well as the estimated time of sailing is provided by the vendor. In addition, the timely provision of quality certificate is monitored. In case of delays or missing information on the vendors side, reminders and dunning letters can be issued.", "Outcome": "Purchase order status and delivery of goods, documents and additional information has been monitored.", "GUID": "dfa9a1e2-7efd-11e5-0a66-001bc640cd9b", "name": "Monitor purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.631477593929331, "y": -1.2890365448504983, "z": 5.392154084653729 }, "color": "#66CCFF", "size": 1.0 }, { "id": "499", "text": "Process", "data": { "Advisory_Notes": " *** In SAP environments typically the MRP run is used as functionality to calculate the final requirements per material and create the corresponding purchase requisitions. ***Often (not always!) you will find separate MRP calculation setups for externally sourced materials compared to the own produced materials. Difference can be found for example in frequency of the calculation and also in the scope of demand elements taken into account. ***If requirements for externally source materials are calculated with a different logic it is still absolutely essential to consider the overall sequence of MRP calculations in combination with calculations of own-produced materials and those of across other plants in the supply network.", "Type": "Business Process", "Description": "Requirements for externally source materials are evaluated considering all relevant demand elements.", "Process_Group": "Procurement Planning", "Scope": "In order to evaluate the material requirements the demands from production (esp. components), from customer orders or intercompany replenishments (esp. trading goods), as well as stock replenishments and planned procurment quantities need to be considered and combined. Based on this comprehensive information the purchase requisitions are created.", "Outcome": "Purchase requisitions for externally sourced materials have been created according to the overall demand situation.", "GUID": "279a79cf-99bb-11e9-0cfc-001bc641ce4f", "name": "Evaluate material requirements for procurement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.8677674782351164, "y": -1.2857142857142856, "z": 1.8019377358048383 }, "color": "#66CCFF", "size": 1.0 }, { "id": "500", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align scope of services from RFP/RFQ with vendor,\n Negotiate contract terms ,\n Align scope of services with vendor", "Type": "Business Process", "Description": "In this process supplier and customer negotiate and agree the terms and conditions of their anticipated relationship. The negotiation can be based on the previous exchange of RFP/RFQ and the related responses.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "Align and agree scope of services, negotiate and agree contract terms.", "Outcome": "Agreement ready for contracting.", "GUID": "ec357bad-7e11-11e5-0a66-001bc640cd9b", "name": "Perform vendor negotiations- Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.287528189033086, "y": -1.282392026578073, "z": 2.709662555087844 }, "color": "#66CCFF", "size": 1.0 }, { "id": "502", "text": "Process", "data": { "Advisory_Notes": "As one of the most prominent examples of Segregation of Duty (SoD), invoice verification has to be done from a department independent from the department responsible for the purchasing. Typically, invoice verification is a department reporting to finance. Needs to be implemented. ***In addition tolerances need to be defined in order to avoid clearing efforts for small deviations. ***Further more rules need to be defined on how to handle invoices for partial deliveries. These rules could either effect internal procedures or external ones (e.g. allow supplier to increase quantity of next delivery to compensate for missing quantities). ***The sequence of processing invoices compared to the goods receipt might differ from case to case. Especially for purchasing of services both sequences are common (e.g. service entry sheet).", "KeyActivities": "Receive PO based invoice,\n Validate invoice data,\n Review and edit invoice data,\n Assign invoice to PO manually ,\n Perform quantity and price deviation analysis ,\n Post verified invoice to ERP system,\n Block invoice from payment,\n Trigger alignment with vendor", "Type": "Business Process", "Description": "Processing of a Purchase Order based invoice from a vendor, in order to trigger the outgoing payment process.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "After the invoice has been transferred (from a scanning tool), invoice verification supports the checking for formal compliance, and whether it is consistent with the purchase order and the actually provided goods or services.", "Outcome": "The invoice is posted, triggering the outgoing payment process.", "GUID": "981573d4-9499-11e8-2ddf-001bc640cd9b", "name": "Process incoming invoice (with PO)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6978267955032609, "y": -1.2790697674418605, "z": 3.621792949972586 }, "color": "#66CCFF", "size": 1.0 }, { "id": "504", "text": "Process", "data": { "Advisory_Notes": "Typically at the end of the negotiations the vendor master data and other master data is initiated if required.", "KeyActivities": "Receive contract,\n Create contract based on vendor negotiation ,\n Send contract to supplier for signing,\n Send contract for approval,\n Sign contract,\n Correct contract details", "Type": "Business Process", "Description": "Before purchasing goods under a contractual agreement with the supplier, it is necessary to define the conditions and set the terms under which the goods will be provided. The purchasing department must understand exactly what products (e.g. goods or services) need to be purchased and in what quantity, as well as select the supplier and prepare the contracting details with the supplier.", "hasAssignment": true, "Process_Group": "Sourcing Direct", "Scope": "Based on the products and quantity that needs to be purchased, a suitable supplier is selected. Specific terms and conditions related to the purchase are negotiated and a contract document prepared.", "Outcome": "The contract with the supplier is approved.", "GUID": "ec357bb3-7e11-11e5-0a66-001bc640cd9b", "name": "Perform contracting- Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.098628876187031, "y": -1.2757475083056478, "z": 4.538254823170902 }, "color": "#66CCFF", "size": 1.0 }, { "id": "506", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Convert purchase requisition into purchase order,\n Save purchase order,\n Update information for purchase order,\n Add supplier master data to purchase order", "Type": "Business Process", "Description": "An approved purchase requisition (PR) is automatically converted into a purchase order (PO). For purchases based on a contractual agreement with the supplier, the agreed terms, conditions and prices stated in the supplier contract are applied to the order.", "Process_Group": "Purchasing Direct", "Scope": "The PO is created with information from the purchase requisition as well as details regarding the terms and conditions specified in the supplier contract. The PO is then forwarded for approval.", "hasAssignment": true, "Outcome": "The PO is ready for further processing.", "GUID": "2164f397-7f0b-11e5-0a66-001bc640cd9b", "name": "Convert purchase requisition for contract into purchase order- Direct", "Business_Rules": "The set-up of possible conversions must be defined. Conversion options are: ***single ***multiple ***partial", "Prerequisite": "" }, "position": { "x": 2.4899005256165907, "y": -1.2724252491694352, "z": 5.4589738387845586 }, "color": "#66CCFF", "size": 1.0 }, { "id": "508", "text": "Process", "data": { "Advisory_Notes": "Settling the contract may lead to a debit or credit note. Follow-up contracts might be negotiated.", "KeyActivities": " Generate settlement items due for settlement,\n Determine difference between target and actual billing,\n Conduct contract setllement,\n Initiate debit memo processing with vendor,\n Request credit memo from vendor", "Type": "Business Process", "Description": "This process ensures that any obligation from both parties are met and financially settled. This is executed periodically or at expiration of the contract.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "Actual business transactions are evaluated against the contractually agreed conditions. Financial obligations are documented and settled.", "Outcome": "Contract settled.", "GUID": "31d74f14-7f0b-11e5-0a66-001bc640cd9b", "name": "Settle contract- Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.8204595302469739, "y": -1.2691029900332227, "z": 1.8239644073355474 }, "color": "#66CCFF", "size": 1.0 }, { "id": "510", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check purchases and delivery against agreed contractual terms,\n Check actual purchase against agreed volumes", "Type": "Business Process", "Description": "Monitoring the vendor contract ensures that the supplier is meeting the performance criteria stated in the contractual agreement. It involves measuring, analysing and managing the suppliers ability to comply with the contractual obligations as well as keeping track of own commitments.", "hasAssignment": true, "Process_Group": "Sourcing Direct", "Scope": "Consulting the order, it is checked whether the supplier is compliant with the contract. This includes confirming on timely delivery of goods that conform to specifications, as well as measuring performance against other contract requirements over time.", "Outcome": "Up-to-date information regarding the suppliers performance is available.", "GUID": "2164f38b-7f0b-11e5-0a66-001bc640cd9b", "name": "Monitor vendor contract- Direct", "Business_Rules": "It is necessary to define: ***What will be measured ***Criteria for measuring performance e.g. service levels and quality, written down in the contract", "Prerequisite": "" }, "position": { "x": 1.2163948117768446, "y": -1.26578073089701, "z": 2.742331792814716 }, "color": "#66CCFF", "size": 1.0 }, { "id": "512", "text": "Process", "data": { "Advisory_Notes": "The GTS check itself is in most cases just an automated check against tables.", "KeyActivities": "Perform embargo check for transportation route,\n Perform sanctioned party list screening,\n Verify documents required for compliance check ,\n Evaluate results of trade compliance checks,\n Update compliance documents,\n Check compliance documents for completeness,\n Block purchase order,\n Communicate trade compliance check results to procurement ,\n Perform control check for material", "Type": "Business Process", "Description": "Global trade checks ensure compliance with trade regulatory programs and cross-border customs requirements. Compliance must be ensured in all international business operations.", "Process_Group": "Global Trade Compliance", "hasAssignment": true, "Scope": "Global trade checks verify conformance with regulations of the countries from/to which the trade is being conducted. In this respect both the vendor and products being purchased are subject to checks.", "Outcome": "The purchase order complies with the applicable trade regulations and the goods can be purchased and imported.", "GUID": "fb9de07b-7f05-11e5-0a66-001bc640cd9b", "name": "Perform global trade checks for purchasing", "Business_Rules": "It needs to be ensured that information (sanctioned party lists, embargo lists) used for screening is comprehensive and up to date. Vendor data must be up to date. Rules and procedures how to handle purchase orders which failed the compliance checks have to be in place.", "Prerequisite": "" }, "position": { "x": 1.6027562684244574, "y": -1.2624584717607974, "z": 3.6648563879129163 }, "color": "#66CCFF", "size": 1.0 }, { "id": "514", "text": "Process", "data": { "Advisory_Notes": "Even if APO is used for supply chain planning, quite often the ERP MRP run will finally generate the PRs on a local (=plant) level. However, PRs can also be generated and transferred to the ERP by the APO.", "KeyActivities": "Inform requester,\n Check and maintain delivery schedules,\n Maintain source of supply,\n Check missing source,\n Assign purchase requisition to source of supply,\n Create and send request for quotation,\n Check open purchase requisitions,\n Trigger missing master data creation,\n Check delivery conditions,\n Check payment methods", "Type": "Business Process", "Description": "A purchase requisition (PR) acts as the trigger for the purchasing department to perform the required purchase of direct materials. Therefore, the purchasing department needs to check who can deliver the material and if the supplier can meet the necessary purchasing conditions. Often the supply network for continuously required direct materials is defined and already considered by the planning tool. Thus, the processing can be automated.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "Processing the PR checks if the purchase order can be fulfilled. Delivery conditions, payment methods, and potential suppliers who can deliver the material, are checked. Once the purchasing department has all relevant information, the conversion of the PR into a purchase order (PO) can be triggered.", "Outcome": "The PR is ready to be converted to a PO.", "GUID": "26aa6cf5-7f07-11e5-0a66-001bc640cd9b", "name": "Process purchase requisition for direct materials", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9795114236466955, "y": -1.2591362126245849, "z": 4.591463222508946 }, "color": "#66CCFF", "size": 1.0 }, { "id": "519", "text": "Process", "data": { "Advisory_Notes": "RFQs are typically used as supporting documentation for sealed bids (either single-round or multi-round) and may be a logical pre-cursor to an electronic reverse auction.", "KeyActivities": "Create RFQ ,\n Issue RfQ to vendors,\n Choose potential vendors for RFQ,\n Receive response to RFQ", "Type": "Business Process", "Description": "Requests For Quotation (RFQ) are suited for goods or services that are as standardized as possible. A formal request for proposal (RFQ) is sent to potential suppliers. It contains a description of all relevant parameters of the intended purchase, such as: ***Part or service descriptions/specifications ***Quantities/Volumes ***Description or drawings ***Quality levels or personnel skills, training level or competencies ***Delivery requirements ***Term of contract ***Terms and conditions ***Other value added requirements or terms ***Draft contract As the request is centered around a standard offering the most important dimension for ranking suppliers will be the price per item or per unit of service, with other dimensions playing a secondary role.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "An RfQ is created and issued to potential vendors. The vendor responses to the RfQ are collected.", "Outcome": "Vendor responses to RfQ is available.", "GUID": "915d6e90-7f0d-11e5-0a66-001bc640cd9b", "name": "Request quotation from vendors- Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.346628322940936, "y": -1.255813953488372, "z": 5.522077101414957 }, "color": "#66CCFF", "size": 1.0 }, { "id": "521", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Gather requirements from all parties,\n Collect and store product or service requirements", "Type": "Business Process", "Description": "Gathering information regarding products and services required by the organization is a key first step of the purchasing process. Through this, details on the specific product and service needs of the various department within the organization are communicated and documented accordingly.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "Before a potential supplier can be identified, details regarding the specific products or services needed are collected and recorded. The information is captured in a reliant format for further processing.", "Outcome": "Comprehensive information on products and services required by the various departments is available.", "GUID": "915d6e8a-7f0d-11e5-0a66-001bc640cd9b", "name": "Gather product/service information- Direct", "Business_Rules": "It is necessary to define: ***What information is required on the products and services ***How the information is collected and stored", "Prerequisite": "" }, "position": { "x": 0.7725930100874562, "y": -1.2524916943521593, "z": 1.8447493165099706 }, "color": "#66CCFF", "size": 1.0 }, { "id": "523", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create source list- Direct", "Type": "Business Process", "Description": "After identification of suitable vendors it is possible to maintain the vendor in a source list to determine through which vendor a certain material/service is to be purchased at one specific time.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "The supplier is identified as a source. It is captured and that the supplier delivers certain materials/services for the organization within a pre-defined period.", "Outcome": "Source list created.", "GUID": "768b35b4-d4a1-11eb-2c3e-001bc641ce4f", "name": "Create source list", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.144433308005869, "y": -1.2491694352159468, "z": 2.7731340399495195 }, "color": "#66CCFF", "size": 1.0 }, { "id": "525", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Assign source of supply as per quota arrangement,\n Initiate preparation and issue of request for quotation,\n Assign source of supply,\n Check existence of source list,\n Determine source of supply", "Type": "Business Process", "Description": "Possible suppliers are evaluated regarding aspects that are important for a well-set and cordial working co-operation. These can include: ***company profile ***management ***quality ***compliance ***reputation ***location", "hasAssignment": true, "Process_Group": "Sourcing Direct", "Scope": "Depending on the purchasing requirements, possible suppliers are sorted and evaluated in order to determine who is most suited. Based on the assessment, a quotation or proposal is requested from the selected suppliers.", "Outcome": "Suppliers, who will be involved in further sourcing process, are selected.", "GUID": "9d60b014-7f0d-11e5-0a66-001bc640cd9b", "name": "Evaluate source of supply- Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5065945783863184, "y": -1.2458471760797343, "z": 3.705424776780248 }, "color": "#66CCFF", "size": 1.0 }, { "id": "527", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Evaluate and compare prices,\n Mantain vendor details in system,\n Evaluate previous performance,\n Propose vendors for negotiation,\n Send vendor evaluation questionnaire to vendor categories,\n Receive vendor responses,\n Display vendor scorecards", "Type": "Business Process", "Description": "Through evaluation, the organization can qualify suppliers to ensure that their capabilities have been verified. The result of the evaluation forms the basis for the negotiation process with the supplier. It is possible to assign different weights to the individual criterias. The vendors overall score is calculated taking into account the weighted scores awarded for each of the main criteria.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "The data, statements, records, operations and performances of a supplier are maintained in the system and examined in order to verify the suppliers validity and support the decision on whether or not to enter into a business relation with the supplier. The audit can include criteria such as: ***checking that the supplier is capable of producing the product or providing the service with adequate quality standards ***verifying that the supplier is conforming to required environmental regulations and international standards ***checking if the information available about the supplier is comprehensive enough to begin the negotiation process", "Outcome": "Negotiations with identified supplier can begin.", "GUID": "915d6e93-7f0d-11e5-0a66-001bc640cd9b", "name": "Gather and evaluate vendor responses", "Business_Rules": "It is necessary to establish a framework for the audit i.e. ***What information will be used? ***How will the audit be operationalised? ***Who will perform the audit? ***How will the results be communicated and used in the selection of suppliers?", "Prerequisite": "" }, "position": { "x": 1.8590463117113432, "y": -1.2425249169435215, "z": 4.641545735087876 }, "color": "#66CCFF", "size": 1.0 }, { "id": "529", "text": "Process", "data": { "Advisory_Notes": "Material master data might be already captured.", "KeyActivities": "Define and classify product or service definition", "Type": "Business Process", "Description": "Information on products or services requested by the various departments must be amended in order to ensure that all the necessary details are available to begin the search for suppliers.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "The purchasing department uses the initial information gathered concerning products and services needed by the various departments as the basis for documenting the specifics of the requests. Additional information is sourced in order to complete the definition of requested product or services.", "Outcome": "Requested product or service is defined.", "GUID": "915d6ea8-7f0d-11e5-0a66-001bc640cd9b", "name": "Complete definition of requested product or services- Direct", "Business_Rules": "It must be defined: ***Where additional information will be taken from e.g. asking the various departments to provide the missing details ***Whether approval is required once the products or services have been defined and if yes, through whom it will be defined", "Prerequisite": "" }, "position": { "x": 2.201758526198258, "y": -1.239202657807309, "z": 5.58142091158813 }, "color": "#66CCFF", "size": 1.0 }, { "id": "531", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Analyze product or service negotiations,\n Select and inform supplier on decision", "Type": "Business Process", "Description": "The final decision regarding which supplier will provide the organization with the requested products or services has to be made in order to initiate collaboration with the supplier and confirm the new source of products or services.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "Based upon the negotiations with potential suppliers, an assessment is carried out to determine which one is most suitable to fulfill the requests for products or services. A supplier is selected and informed about the decision.", "Outcome": "The supplier that will provide a specified product or service is chosen and the contracting process can begin.", "GUID": "915d6eb7-7f0d-11e5-0a66-001bc640cd9b", "name": "Evaluate vendors and make final decision- Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.7242005054773663, "y": -1.2358803986710964, "z": 1.8642783128777547 }, "color": "#66CCFF", "size": 1.0 }, { "id": "533", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Profile suppliers ,\n Profiling products and services ,\n Analyze market trends ,\n Specify market for analysis,\n Determine criteria for cost evaluation,\n Conduct cost structures assessment ,\n Evaluate distribution channels with market,\n Conduct key success factor analysis,\n Collect required data for market evaluation,\n Review success details from factor analysis,\n Store and communicate market evaluation results", "Type": "Business Process", "Description": "Evaluating the market enables the purchasing department to know what products and services are currently offered in relation to the defined products and services requested by the various departments within the organization.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "Once the requested products or services have been clearly defined, the purchasing department performs market research in order to get a clear picture of the products and services being offered by various suppliers on the market. The evaluation can include: ***profiling of suppliers ***profiling of products and services ***analysis of market trends ***assessment of cost structures ***gaining insight on distribution channels ***assessment of key success factors and review of success details", "Outcome": "All relevant information on the market is available for further processing.", "GUID": "915d6e75-7f0d-11e5-0a66-001bc640cd9b", "name": "Evaluate market- Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.0716926694033986, "y": -1.2325581395348837, "z": 2.802048326197644 }, "color": "#66CCFF", "size": 1.0 }, { "id": "541", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create and transfer purchase requisition data to ERP,\n Send stock and sales data to vendor,\n Release purchase requisition,\n Create purchase requisition from external system", "Type": "Business Process", "Description": "With procurement via vendor-managed inventory, the vendor is responsible for creating and maintaining the inventory plan, as well as monitoring stock levels and making replenishment decisions for products owned by the organization which purchases the goods. Extensive information sharing is required so that the vendor can maintain a high degree of visibility. This must be ensured either by giving the vendor access to the organizations system or providing consistent and regular information sharing with the vendor about stock levels and planned consumption.", "Process_Group": "Procurement Planning", "hasAssignment": true, "Scope": "Based on information regarding stock levels and planned consumption, the vendor plans and initiates replenishment by scheduling its production/distribution. The creation of the purchase order is triggered by notification of future replenishment from the vendor.", "Outcome": "Replenishment of stock is initiated and the purchasing process is triggered", "GUID": "fcf412ed-7f0b-11e5-0a66-001bc640cd9b", "name": "Exchange, monitor stock levels and plan replenishment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.4094071926569145, "y": -1.229235880398671, "z": 3.7434704974511224 }, "color": "#66CCFF", "size": 1.0 }, { "id": "543", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create purchase order,\n Save purchase order,\n Change purchase order,\n Send PO number to vendor for reference in sales order", "Type": "Business Process", "Description": "The purchase order (PO) for VMI stock is created with information received from the vendor regarding replenishment. This PO is a formal request to the vendor for the products and initiates the official purchasing process. Information from the vendor notification is incorporated into the PO.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "Once the vendor notifies that a specified quantity of stock is needed, the PO is created based on the information provided. The PO is issued to the vendor, who then ships out the goods.", "Outcome": "The PO for VMI stock is sent to the vendor.", "GUID": "fcf412ef-7f0b-11e5-0a66-001bc640cd9b", "name": "Create and issue purchase order for VMI stock", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7373155535171096, "y": -1.2259136212624586, "z": 4.688468264530276 }, "color": "#66CCFF", "size": 1.0 }, { "id": "547", "text": "Process", "data": { "Advisory_Notes": "***the allocation of actually consumed qty to the different existing PO needs to be considered. It needs to be defined if vendor is defining the split or receives it as part of the consumption information. *** the invoicing scheme needs to be aligned with the vendor (e.g. per consumption, weekly, monthly).", "KeyActivities": "Record consumption of vendor consignment inventory,\n Inform vendor about goods consumption of vendor owned stock,\n Inventory increase posting (consignment consumption)", "Type": "Business Process", "Description": "Consumption of vendor consigned inventory is recorded triggering reporting to the vendor.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "After the vendor owned inventory is used up, the vendor will be informed.", "Outcome": "Vendor informed about goods consumption", "GUID": "1b7433e8-9fd9-11e8-2ddf-001bc640cd9b", "name": "Perform consumption of vendor consignment stock", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.0553897633329568, "y": -1.2225913621262459, "z": 5.636964867797749 }, "color": "#66CCFF", "size": 1.0 }, { "id": "549", "text": "Process", "data": { "Advisory_Notes": "Material requirements planning (MRP) requires bills of materials and material lead times to be defined and correctly maintained. The MRP schedule must be defined regularly. There are many different MRP strategies available for planning driven and consumption driven material approaches. The identified materials requirement can be the triggering event for this process. Other triggering events can be: ***Production order created ***Independent demand revised and updated ***Rework production order created ***Refilling/Re-packaging process order created ***Campaign scheduling completed ***Dependent demand revised and updated", "KeyActivities": "Evaluate results,\n Change receipt elements,\n Execute MRP automatically ,\n Execute MRP", "Type": "Business Process", "Description": "Material requirements planning (MRP) helps to ensure the availability of all materials (raw materials, semifinished goods) required for production or other use in the right quantity and on time.", "Process_Group": "Master Planning", "hasAssignment": true, "Scope": "In stepwise production scheduling procedure after defining finished product demand for the planning period, material requirements planning must be performed to compare demand with current stocks and planned manufacturing, identify final products to be manufactured, analyze, what materials, in what quantity and when are required for the manufacturing and propose production and purchasing schedule (material requirements planning assumes infinite production capacity).", "Outcome": "As a result of material requirements planning, the recommended production schedule is created together with planned orders. In parallel, a recommended purchasing schedule for materials required for production but not available on stock is needed.", "GUID": "817029ee-7eff-11e5-0a66-001bc640cd9b", "name": "Perform and evaluate material requirements planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.6753149622298505, "y": -1.219269102990033, "z": 1.8825381010190725 }, "color": "#66CCFF", "size": 1.0 }, { "id": "551", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create purchase order,\n Save purchase order,\n Change purchase order,\n Send PO number to vendor for reference in sales order", "Type": "Business Process", "Description": "The purchase order (PO) for VOI (Vendor owned inventory) stock is created with information received from the vendor regarding replenishment. This PO is a formal request to the vendor for the products and initiates the official purchasing process. Information from the vendor notification is incorporated into the PO.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "Once the purchaser notifies that a specified quantity of stock is needed, the PO is created based on the information provided. The PO is issued to the vendor, who then ships out the goods.", "Outcome": "The purchase order complies with the applicable trade regulations and the goods can be purchased and imported.", "GUID": "1b7433ce-9fd9-11e8-2ddf-001bc640cd9b", "name": "Create and issue purchase order for VOI", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9982224180908219, "y": -1.2159468438538206, "z": 2.829054966595897 }, "color": "#66CCFF", "size": 1.0 }, { "id": "556", "text": "Process", "data": { "Advisory_Notes": "Subcontracting stock underlies the regular inventory procedures.", "KeyActivities": "Check current status of subcontracting stock,\n Post goods receipt in subcontracting stock,\n Receive GR info from subcontractor,\n Material transfer posting", "Type": "Business Process", "Description": "This process is required in order to track components delivered to the subcontractor. The components still belong to the organization, but are held in storage at the subcontractor. That way the subcontractor is able to fulfill his service to manufacture a product with components from the requesting organization.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "When components are delivered to the subcontractor, they must be recorded as stock that is stored at an external location (not at an internal storage location).", "Outcome": "Information regarding components consumption and subcontracting progress is available.", "GUID": "dfb588c6-7efd-11e5-0a66-001bc640cd9b", "name": "Confirm components delivery and monitor subcontracting stock", "Business_Rules": "The level of system integration with the subcontractor as well as external vendors of components must be defined. It is necessary to define how tracking and reporting will be done.", "Prerequisite": "" }, "position": { "x": 1.3112602768020971, "y": -1.212624584717608, "z": 3.778967648244807 }, "color": "#66CCFF", "size": 1.0 }, { "id": "558", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Receive information from subcontractor about real components consumption,\n Post subsequent component adjustments,\n Forward information to warehouse management,\n Escalate consumption deviation for approval,\n Production material variance posting", "Type": "Business Process", "Description": "Subsequent adjustments of components stock is required in order to reflect the actual consumption related to the goods receipt from the subcontractor. With this, the actual quantity of components used to fulfill a subcontracting order is recorded.", "Process_Group": "Inventory Management", "hasAssignment": true, "Scope": "When the subcontractor gives notice that a larger or smaller quantity of the subcontracting components was actually consumed than planned, a subsequent adjustment to correct the component consumption must to be done.", "Outcome": "The actual components consumption is recorded.", "GUID": "dfb588d2-7efd-11e5-0a66-001bc640cd9b", "name": "Perform subsequent goods issue and adjustments of components", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6144020238572314, "y": -1.2093023255813953, "z": 4.732198865788046 }, "color": "#66CCFF", "size": 1.0 }, { "id": "560", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Pick up semi-finished product (External),\n Perform manufacturing service (External),\n Deliver semi-finished product (External),\n Receive semi-finished product,\n Post goods receipt for manufacturing service,\n Post confirmation of operation ", "Type": "Business Process", "Description": "The subcontractor must fulfil the order by manufacturing the products stated in the purchase order (PO) under the agreed conditions. After the manufacturing the products can be sent to the contractor.", "hasAssignment": true, "Process_Group": "Receipt Handling Direct", "Scope": "Upon reception of the components, the subcontractor manufactures the products with the specifications stipulated in the PO. Manufacturing is performed exclusively by the subcontractor, who provides notification and delivers the finished products.", "Outcome": "Products are manufactured and ready to be sent out by the subcontractor.", "GUID": "de59c969-7efd-11e5-0a66-001bc640cd9b", "name": "Perform subcontracting manufacturing", "Business_Rules": "It must be defined: ***How/whether the manufacturing process will be monitored by the contracting organization. ***How/whether manufacturing practices of the subcontractor will be aligned with the contracting organization.", "Prerequisite": "" }, "position": { "x": 1.9076216827916426, "y": -1.2059800664451827, "z": 5.6886711554934495 }, "color": "#66CCFF", "size": 1.0 }, { "id": "562", "text": "Process", "data": { "Advisory_Notes": "The quantities of components delivered to a subcontractor do not have to match exactly the required quantities from the purchase order. It is possible to keep stock of components at the subcontractor. Before sending components to the subcontractor the availability of these for own production should be checked. Especially if own produced orders have already been confirmed towards customers this check avoids reliability breaches.", "KeyActivities": "Create delivery for components to be provided,\n Set planning status in shipment,\n Create stock transfer order,\n Block shipment", "Type": "Business Process", "Description": "In order to provide the subcontractor with the components required for manufacturing, it is necessary to determine where the components will be taken from and approve the components delivery. It is also essential to verify and confirm that the correct components are being sent to the correct subcontractor.", "Process_Group": "Outbound Delivery Management", "hasAssignment": true, "Scope": "After the purchase order (PO) has been issued and acknowledgement is communicated by the subcontractor, the required components are located. The delivery of the stated quantity to the designated subcontractor, who will fulfil the order, is initiated. Releasing the components delivery triggers the outbound logistics process.", "Outcome": "Components are released and can be sent to the subcontractor.", "GUID": "de59c975-7efd-11e5-0a66-001bc640cd9b", "name": "Initiate and release components delivery to subcontractor", "Business_Rules": "***Rules must be established for allocating authorization for components release. ***It must be clarified how information regarding the release will be communicated across the organization (e.g. to storage locations, to outbound logistics). ***It must be defined who has authorization to approve the delivery and to what amount.", "Prerequisite": "" }, "position": { "x": 0.625969661820758, "y": -1.2026578073089702, "z": 1.8995162495961981 }, "color": "#66CCFF", "size": 1.0 }, { "id": "564", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Determine and assign subcontractor,\n Create subcontracting purchase requisition", "Type": "Business Process", "Description": "When purchasing subcontracting services, a requisition must be sent to the purchasing department that checks to see which subcontractor can manufacture the required products under the corresponding purchasing conditions.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "Potential subcontractors that can manufacture the required products under desired conditions are checked. Once the purchasing department confirms that all relevant information is available for the fulfilment of the order, the purchase requisition (PR) is ready to be converted to a purchase order (PO).", "Outcome": "The PR is ready to be converted to a PO.", "GUID": "de59c96c-7efd-11e5-0a66-001bc640cd9b", "name": "Process subcontracting purchase requisition", "Business_Rules": "Rules must be defined regarding how materials can be provided to fulfil a specific order.", "Prerequisite": "Pre-requisites: - There must be predefined contracts with subcontractors. - A list of subcontractors and the specific services they provide must be available" }, "position": { "x": 0.9240725729128163, "y": -1.1993355481727574, "z": 2.854135574914108 }, "color": "#66CCFF", "size": 1.0 }, { "id": "569", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Document inventory transfer,\n Confirm stock transport order,\n Create stock transport order manually,\n Create stock transfer order automatically", "Type": "Business Process", "Description": "In a cross-company replenishment scenario, no purchase orders are used. Instead a stock transport order (STO) is used to depict the fact that goods delivery is expected from another legal entity of the group.", "Process_Group": "Intercompany Supply Chain Operations", "hasAssignment": true, "Scope": "An STO is created (converted from an STR), which documents the fact that materials will be received from a cross-company vendor. The kind and quantity of materials to be transferred and received are specified in the transport order, as well as the specified storage location and the point in time for planned goods receipt. Pricing follows the same logic as for purchasing from external vendors.", "Outcome": "An STO is created triggering and documenting the expected inventory transfer.", "GUID": "fbef921c-e8d4-11e4-0a66-001bc640cd9b", "name": "Create stock transport order", "Business_Rules": "Approval requirements for stock transfer orders need to be defined.", "Prerequisite": "" }, "position": { "x": 1.2122206496397148, "y": -1.1960132890365447, "z": 3.811892062557263 }, "color": "#66CCFF", "size": 1.0 }, { "id": "571", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review stock transport requsition,\n Approve stock transport requsition,\n Reject stock transport requsition,\n Record material quantity required,\n Record source of supply ", "Type": "Business Process", "Description": "Replenishment scenarios are based on a set of agreements between the individual legal entities of a group, which are reflected in the supply chain set-up and related master data. The processing of the stock requisition (STR) for replenishment involves taking information on material requirements and mapping them to a predefined supplying entity. This forms the basis for delivery scheduling.", "Process_Group": "Intercompany Supply Chain Operations", "hasAssignment": true, "Scope": "When the PR is received, the purchasing department records the required amount of materials based on planning data and records which predefined group vendor will supply the materials. The STR is then reviewed and approved accordingly.", "Outcome": "The STR is approved and forwarded for further processing.", "GUID": "81702a09-7eff-11e5-0a66-001bc640cd9b", "name": "Process stock transport requisition", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.490389402760549, "y": -1.1926910299003324, "z": 4.772707766890726 }, "color": "#66CCFF", "size": 1.0 }, { "id": "573", "text": "Process", "data": { "Advisory_Notes": "In order to verify the material availability for replenishments across plants, a global availability check has to be established.", "KeyActivities": "Inform supplying entity about alternative date,\n Receive response to alternative delivery date,\n Reserve resources and machines,\n Reserve goods,\n Calculate alternative delivery date,\n Check requested goods and quantity", "Type": "Business Process", "Description": "The Available-to-Promise (ATP) check verifies, whether the required quantity of material will be available at the required date.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "After the stock transport order is created, it must be checked if the order can be fulfilled (requested material is available in the requested quantity and on the desired date). During the check, it is also possible to run simulations to know how changes in demand or supply conditions can affect the ATP results.", "Outcome": "ATP check is performed.", "GUID": "817029f4-7eff-11e5-0a66-001bc640cd9b", "name": "Check availability to promise for stock transfer", "Business_Rules": "Rules how to manage and distribute available materials to different requesting plants and legal entities have to be defined.", "Prerequisite": "" }, "position": { "x": 1.7585548856820683, "y": -1.1893687707641196, "z": 5.7365045728251385 }, "color": "#66CCFF", "size": 1.0 }, { "id": "585", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes creation of the pipeline material info record. This info record serves as a central reference point for managing and tracking the purchase details associated with a specific pipeline material, streamlining the procurement process and contributing to efficient supply chain management.", "Process_Group": "Purchasing Direct", "Scope": "Collecting relevant data, initiating creation of pipeline material info record, defining source of pipeline materials, setting procurement parameters, and confirming creation of pipeline material info record.", "Outcome": "Pipeline material info record created.", "GUID": "6fb5b5a0-8e88-11ee-3781-0201b014c5b2", "name": "Create pipeline material info record", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.5761981987304754, "y": -1.1860465116279069, "z": 1.915201199816812 }, "color": "#66CCFF", "size": 1.0 }, { "id": "586", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes tracking and documenting the actual usage of materials that flow directly into the production process.", "Process_Group": "Receipt Handling Direct", "Scope": "Initiating creation of goods issue from pipeline to record the consumption of pipeline material, and monitoring pipeline material balances.", "Outcome": "Consumption of pipeline material recorded.", "GUID": "6fb5dcb3-8e88-11ee-3781-0201b014c5b2", "name": "Record consumption of pipeline material", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.8492936153843156, "y": -1.1827242524916943, "z": 2.877273076172548 }, "color": "#66CCFF", "size": 1.0 }, { "id": "589", "text": "Process", "data": { "Advisory_Notes": "For asset acquisition, one of the key topics is determining the values that should be capitalized. This is dependent on the accounting principle(s) for which the company needs to prepare financial statement. It is always advisable to capitalize asset values based on line transaction items.", "KeyActivities": "Trigger manual depreciation posting to asset,\n Capitalize asset with historical values for IFRS,\n Settle asset to appropriate cost center", "Type": "Business Process", "Description": "This process ensures that the value of the final asset is recorded in the corresponding asset balance sheet account.", "Process_Group": "Asset Accounting", "hasAssignment": true, "Scope": "Assets can be acquired via settlement of values from asset under construction or via posting of vendor invoice. This depends on whether asset under construction (AUC) is involved or a final asset is procured. In AUC, asset values are initially posted to assets under construction and finally transferred to final asset after construction is completed but when final assets are procured the value of asset is derived from the vendor invoice.", "Outcome": "Asset value is reflecting in asset master records and asset balance sheet account.", "name": "Perform asset acquisition", "GUID": "d4cc2762-6966-11e8-2ddf-001bc640cd9b", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1123557377490874, "y": -1.1794019933554818, "z": 3.8422213253138717 }, "color": "#66CCFF", "size": 1.0 }, { "id": "591", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create purchase requisition,\n Attach reference document", "Type": "Business Process", "Description": "A purchase requisition (PR) has to be created with detailed information about the asset to be purchased.", "Process_Group": "Purchasing Indirect", "hasAssignment": true, "Scope": "The PR can be derived from an individual demand and includes basic information of the type of asset and which quantity is needed. This could be: ***material ***quantity ***delivery date ***estimated price ***vendor (if known) ***procurement type (e.g. K for cost center) ***information about the related cost object.", "Outcome": "PR has been created for an asset and can be handed over for approval.", "GUID": "22f82391-94bc-11e8-2ddf-001bc640cd9b", "name": "Create purchase requisition for asset", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.3653621185218063, "y": -1.176079734219269, "z": 4.809967389214364 }, "color": "#66CCFF", "size": 1.0 }, { "id": "593", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check reason for denial,\n Delete purchase requisition and inform requester,\n Send purchase requisition back to requester,\n Approve purchase requestion", "Type": "Business Process", "Description": "Before the created purchase requisition (PR) can be processed further, it needs to pass an approval workflow to ensure, that no un-necessary purchases are made.", "hasAssignment": true, "Process_Group": "Purchasing Indirect", "Scope": "Typically approval of a purchase requisition involves two stages - budget approval and content approval. Budget approval confirms, that there are sufficient funds for the intended purchase and lies within responsibility of the budget owner for the requesting department. Content approval confirms the necessity of the purchase and is performed by subject matter expert (e.g. IT manager for IT related spending).", "Outcome": "Purchase requisition has been approved and can be further processed by purchasing department.", "GUID": "f34356d0-d49e-11eb-2c3e-001bc641ce4f", "name": "Approve purchase requisition", "Business_Rules": "To eliminate possibility of maverick spending, rules must be established regulating approvals requirements (e.g. spending exceeding set amount require a higher instance approval). To reduce unnecessary approval workload rules must be established on when which approvals are required (e.g. only spending exceeding predefined amounts require extra approval).", "Prerequisite": "" }, "position": { "x": 1.6082908572834829, "y": -1.1727574750830565, "z": 5.780432554608552 }, "color": "#66CCFF", "size": 1.0 }, { "id": "595", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Assign asset number automatically,\n Identify asset number of existing asset,\n Create new asset sub-number ,\n Determine asset class,\n Maintain main/sub-number,\n Maintain depreciation and valuation information ,\n Maintain relevant master record information ,\n Maintain asset class,\n Maintain company code", "Type": "Business Process", "Description": "When an asset is aquired or a CAPEX project is released, it is necessary to create the relevant asset in the system. This is used for managing and supervising assets in Financial Accounting.", "Process_Group": "Asset Accounting", "hasAssignment": true, "Scope": "It is possible to create an entirely new asset or add the asset to an already existing one. When creating a new asset, the correct asset class must be determined and then entered into the initial screen of the master data transaction along with the company code. When adding an asset to an already existing one, the asset main number of the existing asset must first be identified. This is followed by the creation of a new asset sub-number for the asset being added. Once the asset number is assigned, relevant master record information is maintained along with depreciation and valuation information for each depreciation area.", "Outcome": "Asset is created/added and saved in the system.", "GUID": "44a5e5bf-7eed-11e5-0a66-001bc640cd9b", "name": "Create asset", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.5260344575726676, "y": -1.169435215946844, "z": 1.9295822733032737 }, "color": "#66CCFF", "size": 1.0 }, { "id": "599", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Send reminder to vendor,\n Maintain available import data,\n Monitor import status and documents,\n Monitor receipt of order acknowledgement,\n Maintain order acknowledgement in purchase order,\n Check and follow-up on overdue deliveries,\n Monitor documentation receipt", "Type": "Business Process", "Description": "Monitoring purchase order (PO) for indirect materials ensures - through communication with the vendor - that the correct material is sent and can be/is delivered on time, and in full quantity.", "Process_Group": "Purchasing Indirect", "hasAssignment": true, "Scope": "After the PO has been sent to the vendor, it needs to be tracked. The vendor hereby sends an order acknowledgement to confirm the receipt of the PO. Furthermore, the delivery date is tracked and, in case of imported material, the estimated time of arrival (ETA) as well as the estimated time of sailing is provided by the vendor. In comparison to monitoring PO for indirect materials the timely receipt of purchased materials by consumable procurement is less strictly monitored by the purchasing department, therefore overdue deliveries are possible. In this case information regarding the delays needs to be received from vendor and delivery information updated.", "Outcome": "Order acknowledgement and details on import status, delivery date and confirmed quantity.", "GUID": "bdc1eaff-7f03-11e5-0a66-001bc640cd9b", "name": "Monitor purchase order for indirect materials", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.7739364553224881, "y": -1.1661129568106312, "z": 2.898451718266644 }, "color": "#66CCFF", "size": 1.0 }, { "id": "601", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Evaluate material movement history and/or planned requirements,\n Update material requirement parameters if needed,\n Check validity of material requirement parameters", "Type": "Business Process", "Description": "In inventory managed consumables procurement scenario, the procurement process is triggered by planning instead of acting on an actual, individual request. Parameters used in the material requirement planning (MRP) and resulting in purchase requisitions must be reviewed regularly to ensure their relevance to current situation and avoid unnecessary purchases.", "Process_Group": "Master Planning", "hasAssignment": true, "Scope": "Parameters used in MRP for calculating purchasing requirements are reviewed and updated. Such parameters could include minimal stock levels, replenishment time, minimal order size. Review should also answer the question if consumables under question are still required and their planned purchasing should be continued.", "Outcome": "Parameters used in MRP are up-to-date.", "GUID": "dac2e2bc-7f04-11e5-0a66-001bc640cd9b", "name": "Review material requirement parameters", "Business_Rules": "In order to ensure consistency of all relevant planning parameters and logistics data, it is recommended to define standardized types of materials/products and to set rules how to classify and periodically verify those.", "Prerequisite": "" }, "position": { "x": 1.0117335295667227, "y": -1.1627906976744184, "z": 3.8699347882297013 }, "color": "#66CCFF", "size": 1.0 }, { "id": "605", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create purchase requisition,\n Attach reference document", "Type": "Business Process", "Description": "A purchase requisition (PR) has to be created from the purchase request with additional information of the purchase.", "Process_Group": "Purchasing Indirect", "hasAssignment": true, "Scope": "The PR can be derived from an individual demand and includes basic information of the type of indirect materials and which quantity is needed. This could be: ***material ***quantity ***delivery date ***estimated price ***vendor (if known) ***procurement type (e.g. K for cost center)", "Outcome": "A PR with the necessary details is created and ready for the approval workflow through the purchasing department.", "GUID": "564ad661-7f04-11e5-0a66-001bc640cd9b", "name": "Create purchase requisition for indirect materials", "Business_Rules": "It needs to be ensured that the information on the PR is complete and up to date. This includes for example: ***When the PR was created ***Why the PR is required", "Prerequisite": "" }, "position": { "x": 1.2394052902225199, "y": -1.1594684385382061, "z": 4.843952366257169 }, "color": "#66CCFF", "size": 1.0 }, { "id": "607", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify and confirm receipt of materials,\n Inform procurement about rejection,\n Communicate quality deviations to procurement,\n Check materials,\n Transfer materials to requester,\n Document deviations,\n Post goods receipt to cost object,\n Consumable expense posting,\n Accounts payable posting", "Type": "Business Process", "Description": "Since directly consumable materials are not stock-managed, upon receipt they are forwarded to the cost center or receiver which is responsible for the original request.", "hasAssignment": true, "Process_Group": "Inbound Delivery Management", "Scope": "Once the directly consumable materials are delivered to the requesting department, the goods are verified and confirmed regarding correct product, correct quantity, and correct cost allocation. They are then posted to consumption accounts.", "Outcome": "GR posted to cost object.", "GUID": "bdcb60d1-7f03-11e5-0a66-001bc640cd9b", "name": "Manage goods receipt for directly consumed materials", "Business_Rules": "Rules and procedures should be established in order to avoid unnecessary delays which might affect timely payment and the entitlement of cash discounts.", "Prerequisite": "" }, "position": { "x": 1.4569318979550494, "y": -1.1561461794019934, "z": 5.820425194495768 }, "color": "#66CCFF", "size": 1.0 }, { "id": "609", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Issue purchase order,\n Send purchase order to requester for modification,\n Check existing trade compliance blocks", "Type": "Business Process", "Description": "A purchase order is an external document and issued by a procuring organization to a supplier indicating types, quantities, and agreed prices for products or services. In procurement via catalogue scenario all items available for purchasing and included into catalogue are controlled by procurement. Therefore no separate approval of purchase order at a later stage is required. Nevertheless purchase order must be checked before the issue on absence of trade compliance blocks.", "Process_Group": "Purchasing Indirect", "hasAssignment": true, "Scope": "After global trade checks have been performed for a particular purchase order, it is checked if any blocks have been set and the purchase order is issued to vendor.", "Outcome": "Purchase order is issued.", "GUID": "7d8dc859-e8c6-11e4-0a66-001bc640cd9b", "name": "Issue purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.47551259002549845, "y": -1.1528239202657806, "z": 1.9426496793625048 }, "color": "#66CCFF", "size": 1.0 }, { "id": "616", "text": "Process", "data": { "Advisory_Notes": "The following questions need to be answered: ***Who receives the shipping information? ***How are the documents received (EDI, Email etc.)? ***What information is required? ***Who communicates with the vendor? ***Who must be made aware of the processed ASN internally?", "KeyActivities": "Verify ASN against information on purchase order,\n Update purchase order,\n Assess impact,\n Trigger escalation handling,\n Inform customer,\n Create inbound delivery", "Type": "Business Process", "Description": "The advanced shipping notification (ASN) issued by the vendor provides information about the carrier, the amount of material, the mode of transport, and the company which executes the shipping. It also provides information about the delivery date. Based on this information, an inbound delivery can be created to steer the further processing and allow for more accurate planning of goods receipt activities and material availability. In cases with short lead time, the order confirmation instead the ASN might suffice.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "The shipping notification is received from the vendor and forwarded to all business units involved in goods receipt e.g. warehouse management and quality management. Typically the inbound delivery, which is created based on the confirmed quantities and dates, acts as the system document of further processing. The ASN includes information on shipment of goods and additional information related to the shipment, such as order information, product description, physical characteristics, type of packaging, markings, carrier information, and configuration of goods within the transportation equipment.", "Outcome": "Advanced shipping notification is received and distributed to involved business units and inbound delivery has been created.", "GUID": "8cc43a30-92dd-11eb-7ba3-001bc641ce4f", "name": "Process advanced shipping notification and inbound delivery", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.6980523961871303, "y": -1.149501661129568, "z": 2.9176570826910773 }, "color": "#66CCFF", "size": 1.0 }, { "id": "621", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The inspection lot is created, completed and the underlying inspection plan are defined.", "Process_Group": "Quality Inspections", "Scope": "All necessary information for an inspection is stored in the inspection lot. When creating the inspection lot, information from the corresponding material master, inspection plan and sampling procedure is evaluated.", "Outcome": "Outcome of the completed inspection lot is documentation which enables making usage decision about specific material.", "GUID": "b27a547f-90b2-11e8-2ddf-001bc640cd9b", "name": "Complete inspection lot", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9104225290995112, "y": -1.1461794019933556, "z": 3.8950135838669486 }, "color": "#66CCFF", "size": 1.0 }, { "id": "622", "text": "Process", "data": { "Advisory_Notes": "The reverse flow does not have to always follow the original path, e.g. a customer returns material to the selling entity, which will then be sent back to the originally shipping entity. Even though the original path was the direct shipment from the shipping entity to the customer (as a drop shipment).", "Type": "Business Process", "Description": "An intercompany (IC) stock returns transfer order is a process flow used to return materials from one entity back to the intercompany source entity. It is initiated when there is a need to return goods due to issues such as defects, damage, expiration, or overstock situations. The transfer order contains information on the quantity of the material to be moved and requirements for warehouse operations. It requires an IC scenario such as IC replenishment or IC drop-shipment as the original business case, which is basically fully or partially reversed.", "Process_Group": "Intercompany Supply Chain Operations", "Scope": "Creating IC stock returns transfer order either manually or automatically, and maintaining material picking and putaway data.", "Outcome": "IC stock transfer order created representing a reverse flow of the original supply chain.", "GUID": "82cfedb8-9829-11ee-3781-0201b014c5b2", "name": "Create intercompany stock returns transfer order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1126046697815721, "y": -1.1428571428571428, "z": 4.874639560909118 }, "color": "#66CCFF", "size": 1.0 }, { "id": "623", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Given all global trade checks meet predefined criteria, the intercompany (IC) stock return order is approved and consequently issued.", "Process_Group": "Intercompany Supply Chain Operations", "Scope": "Before conducting the actual stock returns, an authorized person does a final check if the stock returns order is correct and approves it. The stock transfer order will then be issued.", "Outcome": "IC stock transfer order issued.", "GUID": "82cfedbf-9829-11ee-3781-0201b014c5b2", "name": "Approve and issue intercompany returns stock transfer order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.3045810534893418, "y": -1.1395348837209303, "z": 5.856455265335563 }, "color": "#66CCFF", "size": 1.0 }, { "id": "624", "text": "Process", "data": { "Advisory_Notes": "The usage decision for an inspection lot confirms that all physical samples have been evaluated and the inspection has been completed. Usage decisions: ***unrestricted usage sale/production ***destruction of goods ***recycling ***re-work ***return ***restricted usage (sale/production under certain circumstances - lower quality) Approval requirements for usage decisions must be defined. The matrix between quality properties and actions should be defined to always ensure the same usage of goods. Even in case of purchased goods, a new quality certificate might be generated if the goods are intended for sale. If Laboratory Information Management System (LIMS) is used, the basis of the usage decision can be the recommendation transferred from the LIMS to the ERP.", "KeyActivities": "Review inspection record,\n Accept product for usage,\n Trigger other follow up actions for usage decisions,\n Document usage decision,\n Accept for restricted usage,\n Block for rework,\n Block for return,\n Block for scrap,\n Block for adjustment,\n Block for recycling,\n Post goods receipt into unrestricted stock,\n Post goods receipt into restricted stock", "Type": "Business Process", "Description": "Based on the documented results of the quality inspection, a decision on usage and final quality is made by an authorized and qualified person. It specifies whether the goods in the inspection lot have been accepted for use or rejected.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "The results of the quality inspection get reviewed and the completeness of the quality report is checked. Usage decisions can be made with the help of a predefined catalogue which includes all allowed codes for usage decisions. After the usage decision is made, the stock posting of material for stock-relevant inspection lots is carried out. The usage decision is communicated and documented, as well as a certificate of quality is generated and signed.", "Outcome": "The decision on usage of goods is evaluated, documented and communicated. A quality certificate is generated if required.", "GUID": "f072b296-7e45-11e5-0a66-001bc640cd9b", "name": "Make usage decision", "Business_Rules": "In order to make usage decision, the following conditions must be met: ***The Inspection Lot is released ***Expiration date has been assigned (if required ) ***Inspection results have been recorded for required characteristics, they are valuated and closed. In case that an interface from SAP to LIMS and from LIMS to SAP (results transferring) are in place, this process takes place.", "Prerequisite": "" }, "position": { "x": 0.4246669915810276, "y": -1.1362126245847177, "z": 1.9543945216515317 }, "color": "#66CCFF", "size": 1.0 }, { "id": "626", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Monitor return delivery to vendor,\n Update status of vendor return,\n Check location of goods,\n Clarify with logistics party about delay in goods delivery", "Type": "Business Process", "Description": "The purchase department checks the status of the goods return delivery.", "Process_Group": "Vendor Returns", "hasAssignment": true, "Scope": "Status of return delivery is verify, and all relevant details are recorded.", "Outcome": "Status of vendor return is available and up to date.", "GUID": "01d98350-a15e-11e8-2ddf-001bc640cd9b", "name": "Monitor vendor return", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.6216931001530629, "y": -1.132890365448505, "z": 2.9348760943559564 }, "color": "#66CCFF", "size": 1.0 }, { "id": "628", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create inspection lot automatically,\n Trigger creation of inspection lot manually", "Type": "Business Process", "Description": "Quality inspections are processes on the basis of inspection lots. If a specific quantity of a material is inspected, an inspection lot must be created in the system.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Triggered by the event that an inspection is required an inspection plan has to be assigned. Inspection plan together with information derived from the triggering business object (production order, purchase order) and material master basically specify the content of the inspection lot: ***what shall be inspected? ***by whom? ***when? ***in what way? ***how often? Once the inspection lot is defined, the source of the lot needs to be noted within the quality system. All necessary information for an inspection is stored in the inspection lot. When creating the inspection lot, information from the corresponding material master, inspection plan and sampling procedure is evaluated.", "Outcome": "The inspection lot is created and the underlying inspection plan is defined.", "GUID": "17fae614-e864-11e4-0a66-001bc640cd9b", "name": "Create inspection lot", "Business_Rules": "Whenever an inspection has to be carried out, an Inspection lot must be created. The specific LIMS integration needs to be checked. It is possible to transmit created inspection lots from SAP to LIMS, to perform the sampling calculation there.", "Prerequisite": "" }, "position": { "x": 0.8084917092869208, "y": -1.1295681063122922, "z": 3.9174406384799645 }, "color": "#66CCFF", "size": 1.0 }, { "id": "630", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "An outbound delivery is the central object of the goods issue process - all shipping activities including picking, packing, transportation and goods issue are initiated based on the outbound delivery. In the intercompany (IC) context, the IC outbound delivery triggers an automatic creation of an inbound delivery for the receiving entity.", "Process_Group": "Intercompany Supply Chain Operations", "Scope": "The stock return outbound delivery is created with reference to the intercompany stock transfer order.", "Outcome": "IC outbound delivery for stock returns created.", "GUID": "f44660a3-982c-11ee-3781-0201b014c5b2", "name": "Create intercompany outbound delivery", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9850465835749525, "y": -1.12624584717608, "z": 4.902008081203795 }, "color": "#66CCFF", "size": 1.0 }, { "id": "633", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Request for returnable packaging pick-up,\n Receive returnable packaging pick-up information,\n Prepare packaging for pick-up", "Type": "Business Process", "Description": "Before returnable packaging can be sent back to the vendor, the vendor must provide confirmation that the materials will be picked-up upon delivery on a specified date. The information is captured and processed to update the existing data pertaining to the return.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "After information has been sent to the vendor regarding the return of the packaging units, the vendor acknowledges the return and confirms when and where the packaging materials will be picked-up. The information from the vendor updates the existing data on the return of the specified packaging units. This triggers the logistics process.", "Outcome": "All relevant information regarding the pick-up is available and the returnable packaging can be sent to the vendor", "GUID": "9595686f-7f0c-11e5-0a66-001bc640cd9b", "name": "Receive and process returnable packaging pick-up information", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1513420449583545, "y": -1.1229235880398671, "z": 5.888498237709774 }, "color": "#66CCFF", "size": 1.0 }, { "id": "635", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Display RTP stock overview ", "Type": "Business Process", "Description": "When returnable packaging material sent by a vendor is at the storage location of the purchasing entity, it is necessary to track the packaging units in order to: ***know when the packaging must be sent back to the vendor, ***know what units are at which storage location, ***record when packaging was received and when it was sent out.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "After the receipt of packaging units has been captured, all relevant information concerning the packaging is collected and recorded. With this information the movement of the packaging is tracked until it is sent back to the vendor.", "Outcome": "Returnable distribution packaging is being tracked and can be located if needed.", "GUID": "95956860-7f0c-11e5-0a66-001bc640cd9b", "name": "Track packaging units", "Business_Rules": "***The decision must be made regarding what information is required for tracking. ***It is necessary to define what movements of the packaging will be tracked e.g. only movement to/from vendor, movement between storage locations owned by the purchasing entity.", "Prerequisite": "" }, "position": { "x": 0.3735322781286199, "y": -1.1196013289036544, "z": 1.9648088042341534 }, "color": "#66CCFF", "size": 1.0 }, { "id": "637", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Record storage location,\n Post returnable packaging units in RTP stock,\n Enter packaging material ", "Type": "Business Process", "Description": "Regarding the receipt of returnable packaging materials, it is necessary to capture the fact that the packaging units received come from a specific vendor and are now at a specific storage location of the purchasing entity.", "Process_Group": "Vendor Returns", "hasAssignment": true, "Scope": "Once the packaging material is received along with the products, details regarding what packaging has been received and where it is, is kept documented. Furthermore the packaging material is stored in an unvalued special stock. The information is forwarded for further processing.", "Outcome": "Details regarding returnable packaging at the storage location is recorded.", "GUID": "ba511821-7f0c-11e5-0a66-001bc640cd9b", "name": "Capture receipt of packaging units", "Business_Rules": "It is necessary to define how and which data will be captured and stored.", "Prerequisite": "" }, "position": { "x": 0.5449105529383095, "y": -1.1162790697674418, "z": 2.950097030488398 }, "color": "#66CCFF", "size": 1.0 }, { "id": "639", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Add return conditions of returnable packaging,\n Add quantity and value of returnable packaging to PO", "Type": "Business Process", "Description": "Processing the purchase order with returnable packaging information ensures that the cost, quantity and other conditions related to the returnable packaging material are recorded in the purchase order (PO).", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "When returnable packaging is received from a vendor along with products, information about the quantity and value of the returnable packaging, as well as return conditions and the vendor to which the packaging is to be returned must be captured in the PO and forwarded for further processing.", "Outcome": "Returnable packaging information is recorded in the PO.", "GUID": "ba511803-7f0c-11e5-0a66-001bc640cd9b", "name": "Process purchase order for direct materials with returnable packaging", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.7060104650439382, "y": -1.1129568106312293, "z": 3.9372006836391313 }, "color": "#66CCFF", "size": 1.0 }, { "id": "641", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review details on return items and date,\n Prepare return documents,\n Confirm quantity to be returned,\n Inform vendor about return of packaging units ", "Type": "Business Process", "Description": "Before packaging materials can be sent back to the vendor, it is necessary to provide the vendor with information regarding the return. This includes the specific packaging units and quantity being returned as well as other conditions related to the delivery of the packaging materials.", "hasAssignment": true, "Process_Group": "Vendor Returns", "Scope": "A document to initiate the return of packing units is compiled, specifying the quantity being returned and the proposed delivery date. The information is then sent to the vendor.", "Outcome": "The vendor receives information about the return of the packaging units.", "GUID": "ba511800-7f0c-11e5-0a66-001bc640cd9b", "name": "Provide information on return of packaging units to vendor", "Business_Rules": "It is necessary to define: ***What information will be documented and sent to the vendor. ***How the information will be communicated to the vendor.", "Prerequisite": "" }, "position": { "x": 0.8568178736644084, "y": -1.1096345514950166, "z": 4.926039294541732 }, "color": "#66CCFF", "size": 1.0 }, { "id": "645", "text": "Process", "data": { "Advisory_Notes": "***All related materials need to be considered. This includes finished products that might have already been produced using the same raw materials/components. In case products have already been delivered to customer the customer return process also needs to be triggered from within this process. ***In chemical industry it is a common case that material with quality issues is not returned to the vendor but used in a different way (e.g. concentration) to adjust to the quality deviation. The re-imbursement is then handled independently from the vendor return process.", "KeyActivities": "Review documented data ,\n Assess and evaluate risks,\n Verify implemented actions effectiveness,\n Release product,\n Rework product,\n Scrap product,\n Document decision for each related material,\n Return to vendor,\n Determine use of material(s)", "Type": "Business Process", "Description": "For all materials related to the quality issue the decision on further usage is taken.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Based on results of investigations and corrective measures it is determined if the material can be released, released only with a certain restriction on usage, should be reworked, scrapped or returned to the vendor.", "Outcome": "Decision is taken for each related material.", "GUID": "c38779e9-659c-11e9-2ddf-001bc640cd9b", "name": "Take decision on further use of material(s)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9973191980997709, "y": -1.106312292358804, "z": 5.916532296633022 }, "color": "#66CCFF", "size": 1.0 }, { "id": "647", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Adopt actions for implementation monitoring ,\n Perform control of planned vs. implemented actions,\n Document actual status of implementation,\n Define follow up actions", "Type": "Business Process", "Description": "Conduction of investigation and implementation of corrective actions are monitored.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Each defined investigation task and corrective action is monitored with regards to timely performance and result. Deviations from planned timelines can be followed up on. The quality notification is closed once all defined activities have been conducted.", "Outcome": "Actual status of activities is known and quality notification is closed after conduction of defined activities.", "GUID": "bdf94770-6761-11e9-2ddf-001bc640cd9b", "name": "Monitor investigations and corrective actions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.3221432623883098, "y": -1.1029900332225915, "z": 1.9738854370246053 }, "color": "#66CCFF", "size": 1.0 }, { "id": "649", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create return delivery for purchase orders", "Type": "Business Process", "Description": "A delivery is the central object of the goods issue process - all shipping activities including picking, packing, transportation and goods issue are initiated based on the delivery. For the return to vendor scenario creation of a return delivery is required (similar to an outbound delivery in sales scenarios). .", "hasAssignment": true, "Process_Group": "Vendor Returns", "Scope": "A return delivery is created with reference to the return purchase order. A delivery can be created only for purchase orders, which are due to delivery (material availability date or the transportation scheduling date is reached).", "Outcome": "Return delivery document is created and shipping activities can be initiated.", "GUID": "7b1559a0-7f0c-11e5-0a66-001bc640cd9b", "name": "Create return delivery for vendor returns", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.46775702841201394, "y": -1.0996677740863787, "z": 2.9633095286134323 }, "color": "#66CCFF", "size": 1.0 }, { "id": "651", "text": "Process", "data": { "Advisory_Notes": "***It needs to be determined whether corrective actions need to taken also for other products/plants ***Corrective actions will vary depending on the specific case and are therefore not specified in more detail. One could think of a wide range from adjusting the quality control mechanisms or certain parameters in production process, over rework of product or adjusted usage of the material, down to stop buying materials from the vendor.", "KeyActivities": "Define corrective measures,\n Set up action plan,\n Trigger corrective measures implementation", "Type": "Business Process", "Description": "Suitable corrective actions are defined and triggered.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Based on the investigation results suitable corrective measures are identified. An action plan is set up including determination of responsible people and clear timelines.", "Outcome": "Corrective actions are defined and implementation is triggered.", "GUID": "1c7ed417-7553-11e9-2ddf-001bc640cd9b", "name": "Define and trigger corrective actions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.603048566016734, "y": -1.096345514950166, "z": 3.9542802666256676 }, "color": "#66CCFF", "size": 1.0 }, { "id": "653", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Request return material authorization (RMA),\n Receive complaint confirmation by vendor", "Type": "Business Process", "Description": "Receiving notification from the relevant department about a product related complaint to a vendor and processing the information initiates the return-to-vendor process.", "Process_Group": "Vendor Returns", "hasAssignment": true, "Scope": "This process includes receiving the complaint from a relevant department, assessing and updating it with the necessary information (e.g. PO number, warranty terms), identifying the responsible vendor and requesting a return material authorization (RMA). After the vendor has confirmed the complaint, the return purchase order can be created.", "Outcome": "The complaint contains all necessary information. The vendor has approved the return and the product can be returned to the vendor.", "GUID": "7b15599a-7f0c-11e5-0a66-001bc640cd9b", "name": "Process complaint to vendor", "Business_Rules": "It must be defined: ***How the validity of the complaint will be assessed and what parties (departments) will be involved. ***Who will have authorization to approve which type of complaints. ***What information is required to ensure that the vendor accepts the complaint. ***What the timeframe for processing of complaints is.", "Prerequisite": "" }, "position": { "x": 0.7280058386750249, "y": -1.0930232558139537, "z": 4.946716840375551 }, "color": "#66CCFF", "size": 1.0 }, { "id": "655", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review information from quality inspection,\n Assess possible root cause,\n Document root cause,\n Assess extent of quality issue,\n Define suitable internal investigations,\n Perform further internal investigations", "Type": "Business Process", "Description": "Internal investigations are conducted to evaluate the quality issue.", "hasAssignment": true, "Process_Group": "Quality Inspections", "Scope": "Based on the information from the quality inspection further suitable investigations are defined and conducted. Typically at least the extent of the quality issue and potential root causes are assessed. Sometimes more detailed quality analyses are conducted in order to support this investigation.", "Outcome": "Extent and internal root cause of quality issue has been determined.", "GUID": "1c7ed413-7553-11e9-2ddf-001bc640cd9b", "name": "Perform internal investigation", "Business_Rules": "***when using quality notification the investigative activities can be managed with workflows and also monitored regarding status and results. ***depending on the relationship with the vendor the internal results might be shared with the vendor in order to support the investigations conducted by the vendor. ***The exact procedure of reporting complaints need to be defined together with the vendor and should be part of contract negotiation. This could also include determination who runs the quality measurements/controls in case of complaints.", "Prerequisite": "" }, "position": { "x": 0.8426173722915866, "y": -1.089700996677741, "z": 5.940538356404445 }, "color": "#66CCFF", "size": 1.0 }, { "id": "657", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain required purchase order data (material code,\n quantity,\n etc.),\n Set return flag,\n Change return purchase order,\n Determine purchase prices and conditions", "Type": "Business Process", "Description": "The creation of a return purchase order is required to initiate the return of products to the vendor. The return can result from a valid complaint or the over-delivery of products, part of which needs to be returned to vendor.", "Process_Group": "Vendor Returns", "hasAssignment": true, "Scope": "After the notification is given that products must be sent back to the vendor, a return purchase order is created and forwarded for further processing.", "Outcome": "All relevant information regarding the return is documented in the return purchase order.", "GUID": "768b35b2-d4a1-11eb-2c3e-001bc641ce4f", "name": "Create return purchase order", "Business_Rules": "***The format of the order (electronic, paper) and communication channel must be defined. ***It is necessary to define who covers the transportation and other related costs.", "Prerequisite": "" }, "position": { "x": 0.2705349302101591, "y": -1.0863787375415281, "z": 1.9816182406145197 }, "color": "#66CCFF", "size": 1.0 }, { "id": "659", "text": "Process", "data": { "Advisory_Notes": "The exact procedure of reporting complaints need to be defined together with the vendor and should be part of contract negotiation. This could also include determination who runs the quality measurements/controls in case of complaints.", "KeyActivities": "Review information from quality inspection,\n Assess extent of quality issue,\n Assess possible root cause,\n Document new findings,\n Identify new findings,\n Share information with vendor,\n Align with vendor on further investigations,\n Assess investigation results from vendor", "Type": "Business Process", "Description": "Investigations are conducted in cooperation with the vendor to evaluate the quality issue.", "hasAssignment": true, "Process_Group": "Quality Inspections", "Scope": "Based on the information from the quality inspection further suitable investigations are defined and conducted. Typically at least the extent of the quality issue and potential root causes are assessed. Sometimes more detailed quality analyses are conducted in order to support this investigation. The activities are done either in cooperation with the vendor or by the vendor.", "Outcome": "Extent and external root cause of quality issue has been determined.", "GUID": "1c7ed415-7553-11e9-2ddf-001bc640cd9b", "name": "Perform investigation with vendor", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.39028505300617644, "y": -1.0830564784053156, "z": 2.974504593608819 }, "color": "#66CCFF", "size": 1.0 }, { "id": "664", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Escalate issue,\n Maintain order acknowledgement ,\n Send reminder to service provider,\n Receive updates from service provider,\n Update purchase order,\n Assess impact of update information,\n Monitor receipt of order acknowledgement", "Type": "Business Process", "Description": "Monitoring purchase order (PO) for services ensures - through communication with the vendor - that the correct service will be performed on time and in agreed quality.", "hasAssignment": true, "Process_Group": "Receipt Handling Indirect", "Scope": "After the PO has been sent to the vendor, it needs to be tracked. The vendor hereby sends an order acknowledgement to confirm the receipt of the PO. The service provider may provide additional data or inform about changes at any time.", "Outcome": "Order acknowledgement received.", "name": "Monitor purchase order for services", "GUID": "94eda4a0-83f0-11e5-0a66-001bc640cd9b", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.4996761090832031, "y": -1.079734219269103, "z": 3.9686677595902973 }, "color": "#66CCFF", "size": 1.0 }, { "id": "666", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check budget and approve purchase requisition,\n Delete purchase requisition,\n Modify purchase requisition,\n Check reason for denial,\n Create purchase requisition", "Type": "Business Process", "Description": "The purchase requisition (PR) for standard services is a notification that informs the approver (i.e., category manager) about standard services that are required. Often, a PR for standard indirect services is automatically approved. In some cases, it can be sent for a header or item level approval.", "Process_Group": "Purchasing Indirect", "hasAssignment": true, "Scope": "A standard service typically consists of predefined tasks that need to be provided. The purchase requisition (PR) might contain a detailed specification of the tasks or might only include an electronic document or a reference to such. The requisition is triggered by the receiving department. The PR for standard services must contain the relevant cost object the costs for the service are posted against. The object quite often might be relevant for determining the right approvers.", "Outcome": "Purchase requisition is sent for approval.", "GUID": "529c6282-7f06-11e5-0a66-001bc640cd9b", "name": "Create purchase requisition for standard services", "Business_Rules": "The reasons, stating why purchasing a service is necessary to achieve a certain task, must be clearly defined. ***How are the services purchased e.g. via a bidders platform? ***What if the price of the service exceeds the budget e.g. of a project? ***How is the internal hiring process started? ***How is the bid procedure performed? ***How were the quotations compared?", "Prerequisite": "" }, "position": { "x": 0.5986981743619617, "y": -1.0764119601328903, "z": 4.964026641348297 }, "color": "#66CCFF", "size": 1.0 }, { "id": "668", "text": "Process", "data": { "Advisory_Notes": "Depending on the nature of the service and the organizational set-up different variations who actually captures the service delivery via the service entry sheet and who confirms it finally can be established.", "KeyActivities": "Confirm receipt of service,\n Create service entry sheet,\n Inform vendor about service confirmation,\n Escalate issue with vendor,\n Receive confirmation of service performed by vendor,\n Service consumption posting,\n Accounts payable posting", "Type": "Business Process", "Description": "Receipt confirmation takes place after service has been performed and is used to record the service performance fact and initiate billing process on vendor side and payment process on service recipient side.", "hasAssignment": true, "Scope": "Vendor provides a confirmation once the service has been performed. This serves as a trigger for recording the service fulfillment, which is done via service entry sheet. Once service fulfillment is recorded, it must be confirmed by the requestor, if the service has actually been performed, as well as if it complies with agreed requirements on time, cost and quality. If requestor confirms the service, billing and payment process can be initiated.", "Process_Group": "Receipt Handling Indirect", "Outcome": "Service is confirmed, billing and payment can be initiated.", "GUID": "529c6284-7f06-11e5-0a66-001bc640cd9b", "name": "Confirm standard service receipt", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.6873418891634164, "y": -1.0730897009966778, "z": 5.960500073601313 }, "color": "#66CCFF", "size": 1.0 }, { "id": "672", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create purchase requisition for one-time service ,\n Attach reference document", "Type": "Business Process", "Description": "A purchase requisition (PR) is required to trigger the formal approval of one-time services. The PR for one-time services is a notification that informs the approver (i.e., category manager) that one-time services are required. ", "Process_Group": "Purchasing Indirect", "hasAssignment": true, "Scope": "Since the one-time service is not regularly purchased, the PR must contain reference to a statement of work, previously negotiated vendor proposal or other documents stating content and terms of the service. The PR for one-time services must contain the relevant cost object the costs for the service are posted against. The object quite often might be relevant for determining the right approvers.", "Outcome": "Purchase requisition is sent for approval.", "GUID": "fbfd3e93-7f05-11e5-0a66-001bc640cd9b", "name": "Create purchase requisition for one-time services", "Business_Rules": "", "Prerequisite": "Pre-requisites: request for proposal process has been performed if required, vendor proposal has been received, its terms negotiated and approved by purchasing department." }, "position": { "x": 0.21874241675574904, "y": -1.0697674418604652, "z": 1.9880019504798918 }, "color": "#66CCFF", "size": 1.0 }, { "id": "674", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check purchase requisition for formal correctness,\n Delete purchase requisition and inform requester,\n Send purchase requisition back to requester,\n Check reason for denial,\n Inform requester about modification,\n Approve purchase requestion for one-time service", "Type": "Business Process", "Description": "The approval process for purchase requisition (PR) for one-time services confirms that the specific service can be purchased by the requester and performed by the identified service provider. Moreover, the duration of the service to be performed and other related terms and conditions are verified. The operational expenses related to this service have to be approved by the budget owner of the respective cost object. Typically, a PR is sent for a header or item level approval to the specific approvers (e.g., category manager, budget owner).", "Process_Group": "Purchasing Indirect", "hasAssignment": true, "Scope": "The approvers verify that the service can be purchased, budget is covered, and that all necessary information regarding the service is recorded.", "Outcome": "The PR for one-time services is ready to be converted into a purchase order (PO).", "GUID": "fbfd3e95-7f05-11e5-0a66-001bc640cd9b", "name": "Approve purchase requisition for one-time services", "Business_Rules": "It needs to be clarified what will happen if the PR is not converted into a PO because: ***the price for the service exceeds the budget ***the purchase of services is not required It is necessary to define what services a department is allowed to purchase.", "Prerequisite": "" }, "position": { "x": 0.312547369955444, "y": -1.0664451827242525, "z": 2.9836746038289657 }, "color": "#66CCFF", "size": 1.0 }, { "id": "676", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Escalate issue with vendor,\n Inform vendor about service confirmation,\n Receive confirmation of service performed by vendor,\n Post goods receipt to cost object,\n Record service fulfillment via goods receipt slip,\n Service consumption posting,\n Accounts payable posting", "Type": "Business Process", "Description": "Receipt confirmation takes place after service has been performed and is used to record the service performance fact and initiate billing process on vendor side and payment process on service recipient side.", "Process_Group": "Receipt Handling Indirect", "hasAssignment": true, "Scope": "Vendor provides a confirmation, once the service has been performed. This serves as trigger for recording the service fulfillment by procurement. For one-time services the recording typically is done by using the goods receipt functionality of ERP system. Once service fulfillment is recorded, it must be confirmed by the requestor, if the service has actually been performed, as well as if it complies with agreed requirements on time, cost and quality. If requestor confirms the service, billing and payment process can be initiated.", "Outcome": "Service is confirmed, billing and payment can be initiated.", "name": "Confirm one-time service receipt", "GUID": "fbfd3e97-7f05-11e5-0a66-001bc640cd9b", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.39596347063072296, "y": -1.0631229235880397, "z": 3.9803533674695357 }, "color": "#66CCFF", "size": 1.0 }, { "id": "681", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update PO with confirmation data,\n Update PO with ASN", "Type": "Business Process", "Description": "By using the SAP Business Network all documents required are exchanged electronically. These documents can be: ***Purchase requisition ***Purchase order ***Order confirmation ***Advanced shipping notification ***Goods receipt ***Invoice", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "After the supplier receives the PO via the SAP Business Network, the order confirmation can be created, if required. The confirmation data is transferred to the procuring organization and the PO is updated. To inform the procuring organization about a pending delivery and details on e.g. the schedule and physical characteristics of the shipment, the supplier creates an Advanced Shipping Notification (ASN). Also the ASN details are exchanged via the SAP Business Network and the the PO is updated accordingly. At any time, the procuring company is able to monitor the suppliers updates via the the network.", "Outcome": "PO is enriched with order confirmation data and ASN details.", "GUID": "a30b1b18-972c-11e9-0cfc-001bc641ce4f", "name": "Exchange electronic documents via SAP Business Network - Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.46898291390683033, "y": -1.0598006644518272, "z": 4.977956912877356 }, "color": "#66CCFF", "size": 1.0 }, { "id": "683", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create purchase requisition,\n Submit purchase requisition for approval,\n Approve purchase requisition,\n Transfer purchase requisition", "Type": "Business Process", "Description": "After a demand for materials is identified, a purchase requisition (PR) is created to capture the details of the demand. The PR is an internal document and its details include e.g. the quantity and timeframe for the required material. The approved PR then is the trigger for the procurement department to perform the purchase of the required goods.", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "The creation of a PR takes place in SAP Ariba. After submitting the the PR for approval, an automated transfer of the document will be send to SAP S4/HANA and therefore be created also in the ERP system with status In Release. Simultaneously, the approver can check if all relevant information is included in the PR and approve the document in SAP Ariba. In S4/HANA, all information and progress of the PR can be monitored at any point in time.", "Outcome": "The approved PR is ready to be converted into a PO.", "GUID": "31aa9d57-b9cd-11e9-0cfc-001bc641ce4f", "name": "Create and approve purchase requisition for direct materials (Ariba)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.5315984608930978, "y": -1.0564784053156147, "z": 5.9764038582057095 }, "color": "#66CCFF", "size": 1.0 }, { "id": "685", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Receive supplier invoice,\n Check invoice,\n Release blocked invoice", "Type": "Business Process", "Description": "The invoice issued by the supplier gets processed and posted. If goods-receipt-based invoice verification has been defined for a purchase order item, the system compares the supplier invoice data with the related goods receipt data. If the deviation is outside defined tolerances, the invoice is posted, but the invoice is automatically blocked for payment. Blocked invoices can be released and therefore enable the payment process.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "The supplier invoice is transferred via the Ariba network. The invoice includes the S4/HANA PO reference. If required, a check of the invoice and release of blocked invoices can be performed.", "Outcome": "The invoice is posted, triggering the outgoing payment process.", "GUID": "4dc445b3-b9d2-11e9-0cfc-001bc641ce4f", "name": "Process supplier invoice (Ariba)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.1668009825780186, "y": -1.053156146179402, "z": 1.993032220565189 }, "color": "#66CCFF", "size": 1.0 }, { "id": "687", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Transfer purchase order,\n Create purchase order from approved purchase requisition,\n Receive purchase order number,\n Issue purchase order", "Type": "Business Process", "Description": "An official purchase order (PO) has to be created from a purchase requisition (PR) to be able to order materials. It is a formal request or instruction from a purchasing organization to a vendor to supply or provide a certain quantity of materials at or by a certain point in time", "Process_Group": "Purchasing Direct", "hasAssignment": true, "Scope": "Upon approval of a PR, a PO is created based on it. An automated notification on the creation of the PO in SAP Ariba is then sent to the S4/HANA system. Based on this message the PO is also created in the ERP system and a PO number is generated. This information is sent back to Ariba where the PO number is added to the document in Ariba. The updated PO is ready to be issued to the supplier via the Ariba network.", "Outcome": "The PO is issued.", "GUID": "31aa9d59-b9cd-11e9-0cfc-001bc641ce4f", "name": "Create purchase order (Ariba)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.2345969033893064, "y": -1.0498338870431894, "z": 2.990813316293772 }, "color": "#66CCFF", "size": 1.0 }, { "id": "691", "text": "Process", "data": { "Advisory_Notes": "Self-billing agreements usually last for 12 months. At the end of this period it is necessary to review the agreement to ensure existence of a proof that the agreement is still in force. It is important not to self-bill a supplier without their written agreement to do so. It is necessary to enter into a separate agreement with each vendor.", "KeyActivities": "Perform evaluated receipt settlement,\n Create self invoice ,\n Send self invoice to vendor,\n Post self invoice,\n Accounts payable posting", "Type": "Business Process", "Description": "With self invoicing an agreement is reached with a supplier, that he does not create invoices for delivered goods/provided services. Instead the customer himself creates an invoice for the received goods and provides it to vendor.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "After receiving ordered goods, a self invoice is automatically created in customers system based on data in the purchase orders and goods receipts. The self invoice is posted and sent to vendor. This allows closer control over correctness of the invoices and speeds the recognition of the liability.", "Outcome": "Self invoice is created, posted and issued, liability for received goods is recorded.", "GUID": "bdcb60c8-7f03-11e5-0a66-001bc640cd9b", "name": "Manage self invoice", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.29198125864362995, "y": -1.0465116279069768, "z": 3.9893291346542066 }, "color": "#66CCFF", "size": 1.0 }, { "id": "693", "text": "Process", "data": { "Advisory_Notes": "***Items need to be included into catalogue and controlled by procurement, which means, they contain all information necessary to make the purchase (vendor information, product information etc.). ***Purchase request can be directly converted to a purchase requisition in the ERP system without any manual intervention only if catalogue content is maintained correctly.", "KeyActivities": "Convert purchase request to purchase requisition,\n Receive data from catalog/vendor portal,\n Check for existence of materials in ERP,\n Inform procurement department to maintain materials in ERP", "Type": "Business Process", "Description": "Purchase requisition (PR) is created in the ERP based on data from the purchase request within the catalogue system or vendor portal.", "Process_Group": "Purchasing Indirect", "hasAssignment": true, "Scope": "Information from the purchase request in the catalogue system or vendor portal is transferred to the ERP system in order to create a corresponding purchase requisition (PR) there. During this process the existence of the requested materials within the ERP is checked.", "Outcome": "Purchase requisition is created and can be processed in ERP.", "GUID": "768b35b0-d4a1-11eb-2c3e-001bc641ce4f", "name": "Convert purchase request to purchase requisition", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.3389483679843463, "y": -1.043189368770764, "z": 4.988498171177448 }, "color": "#66CCFF", "size": 1.0 }, { "id": "695", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Approve purchase request,\n Delete purchase request,\n Modify purchase request,\n Check reason for denial,\n Create purchase request,\n Check catalogue for required material", "Type": "Business Process", "Description": "In this process the requestor uses an electronic catalogue system/vendor portal for placing purchasing requests. The same tool is used also for approving the placed requests.", "Process_Group": "Purchasing Indirect", "hasAssignment": true, "Scope": "Requestor places purchase request in an electronic catalogue system/vendor portal, which is not part of ERP. The materials included into the catalogue/vendor portal are previously defined by procurement, their terms agreed with vendors and rules control, which items are available for choice for a particular requestor. Required approval workflow is also managed through the catalogue system/vendor portal.", "Outcome": "Purchase request is placed in the catalogue/vendor portal and approved.", "GUID": "bdc1eaf3-7f03-11e5-0a66-001bc640cd9b", "name": "Create and approve purchase request via catalogue-vendor portal", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.3754931182374207, "y": -1.0398671096345515, "z": 5.988238882856656 }, "color": "#66CCFF", "size": 1.0 }, { "id": "702", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check audit location and functional area,\n Check external audit needs,\n Request external audit plan,\n Receive external Audit Plan,\n Call up process change report,\n Create audit questionnaire,\n Assemble audit team,\n Carry out scheduling of audits,\n Create audit plan", "Type": "Business Process", "Description": "As soon as the necessity of an audit has been determined, the IMS representative must initiate the planning of the audit. In the course of this, the dates, locations and internal audit teams (according to technical background knowledge but cross-functional) are to be determined. The necessity of an external audit has to be checked and the external planning has to be harmonized with the internal planning in terms of content, time and staff. The process changes, findings, deviations, measures since/from the last audit are evaluated and a question catalog (random questions for processes to be audited) is created for the upcoming audit.", "Process_Group": "Audit Management", "hasAssignment": true, "Scope": "During planning, the audit type (internal and/or external) and scope of the audit as well as auditors, locations and dates are determined. The results of the last audit must be taken into account accordingly to ensure a targeted and seamless exchange of information with the external certifiers and to harmonize internal audit planning with external audit planning.", "Outcome": "* Audit questionnaire * Audit schedule * Audit plan", "GUID": "53a84350-d28d-11eb-2c3e-001bc641ce4f", "name": "Plan audit", "Business_Rules": "", "Prerequisite": "* Plan of measures* Audit reports * Standards * Laws (legal register) * Process change report * Audit schedule * External audit plan * Audit team plan" }, "position": { "x": 0.11474598961573952, "y": -1.036544850498339, "z": 1.996705626242162 }, "color": "#66CCFF", "size": 1.0 }, { "id": "704", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The audit process and the audit program, like all other processes in the IMS, are subject to Continuous Improvement. The audit process is of great importance for the overall functioning and improvement of the management systems. Therefore, at planned intervals (min. once a year), it should be analyzed and evaluated whether the overall implementation of the audit program has achieved the planned objectives.", "Process_Group": "Audit Management", "Scope": "Compliance with the audit program, ongoing auditor professional development, audit program records, confidentiality, and information security related to the audit program are reviewed. ", "Outcome": "Lessons learned from the review should be used as inputs for program improvement.", "GUID": "182f247d-9cc0-11ed-3781-0201b014c5b2", "name": "Review and improve audit program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.15648672230113178, "y": -1.0332225913621262, "z": 2.9959158709388767 }, "color": "#66CCFF", "size": 1.0 }, { "id": "705", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Determines and assesses risks and opportunities that may affect an audit program. Risks may be related to audit planning, resources for conducting audits, auditor selection, coordination of audits, and communication channels.", "Process_Group": "Audit Management", "Scope": "An audit program may involve risks and opportunities related to the auditees environment that may affect the achievement of objectives. The person managing the audit program should identify and present to the audit client the risks and opportunities that were considered in developing the audit program and resource requirements so that they can be adequately addressed.", "Outcome": "The risks and opportunities of the audit program are taken into account with appropriate measures when defining the audit program.", "GUID": "182f2475-9cc0-11ed-3781-0201b014c5b2", "name": "Determine and assess audit program risks and opportunities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.18780026463301452, "y": -1.0299003322259135, "z": 3.9955889504056556 }, "color": "#66CCFF", "size": 1.0 }, { "id": "706", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Audit program objectives are created to guide the planning and execution of audits and should ensure that the audit program is implemented effectively. ", "Process_Group": "Audit Management", "Scope": "Objectives should be based on: Stakeholder requirements, process, product, service and project requirements, management systems and opportunities for improvement.", "Outcome": "Objectives of the audit program", "GUID": "182f2473-9cc0-11ed-3781-0201b014c5b2", "name": "Set audit programme objectives", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.2086830646400656, "y": -1.026578073089701, "z": 4.995643239717227 }, "color": "#66CCFF", "size": 1.0 }, { "id": "707", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The implementation of the audit program should be continuously monitored with regard to the achievement of its objectives. The audit program should also be reviewed to identify any need for correction or potential for improvement.", "Process_Group": "Audit Management", "Scope": "It monitors whether schedules are adhered to, the performance of the auditors, the suitability of the audit team to implement the audit plans and the adequacy of the audit documentation.", "Outcome": "Audit program oversight ensures that audit planning and execution are managed and that the audit program is implemented.", "GUID": "182f247b-9cc0-11ed-3781-0201b014c5b2", "name": "Monitor audit program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.21913213834595444, "y": -1.0232558139534884, "z": 5.995997090221437 }, "color": "#66CCFF", "size": 1.0 }, { "id": "708", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The audit program includes all planned audits in a defined period (usually for one year). ", "Process_Group": "Audit Management", "Scope": "For each audit listed, the scope, duration, audit type, audit location, auditor(s) and time period are defined. ", "Outcome": "Audit program established", "GUID": "182f2477-9cc0-11ed-3781-0201b014c5b2", "name": "Set up audit program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.0626128771189642, "y": -1.0199335548172757, "z": 1.9990196666413478 }, "color": "#66CCFF", "size": 1.0 }, { "id": "709", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Conduct introductory interview,\n Perform audit according to questionnaire,\n Check implementation of measures taken,\n Conduct final interview,\n Define measures to be taken,\n Create audit report", "Type": "Business Process", "Description": "At the beginning of the audit, the auditor conducts an introductory meeting with the area/site to be audited and then begins to work through his Audit questionnaire. The status and further processing of the results of the last audit are reviewed. In the final meeting, all results are discussed and possible new measures are defined. The audit performance is concluded with the final report.", "Process_Group": "Audit Management", "hasAssignment": true, "Scope": "The planned audits are carried out. In the event of deviations, associated measures are defined. In addition, advice and recommendations for improvements are given (CIP).", "Outcome": "* completed Audit questionnaire * reviewed documents * updated plan of measures * audit report", "GUID": "53a84352-d28d-11eb-2c3e-001bc641ce4f", "name": "Perform audit", "Business_Rules": "", "Prerequisite": "* Audit plan * Audit questionnaire * Role descriptions * Process descriptions * Plan of measures" }, "position": { "x": 0.07827000441858253, "y": -1.0166112956810631, "z": 2.998978793924411 }, "color": "#66CCFF", "size": 1.0 }, { "id": "711", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The audit report provides a complete, accurate, concise and clear record of the audit results, including the audit conclusion. ", "Process_Group": "Compliance and Audits Reporting", "Scope": "The audit report is distributed within an agreed period of time to the persons specified in the audit program or audit plan.", "Outcome": "Audit report", "GUID": "182f2485-9cc0-11ed-3781-0201b014c5b2", "name": "Create and distribute the audit report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.08349141544157122, "y": -1.0132890365448506, "z": 3.999128553015965 }, "color": "#66CCFF", "size": 1.0 }, { "id": "712", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "At least two weeks before the scheduled date of an audit, the corresponding audit is arranged. ", "Process_Group": "Audit Management", "Scope": "The representatives of the respective areas to be audited are contacted to agree on the details of the audit. The audit date must be fixed, communication channels defined, implementation confirmed and site-specific precautions regarding access, confidentiality, health, safety and occupational health agreed for the upcoming audit.", "Outcome": "Details of the audit plan are coordinated with the area to be audited.", "GUID": "182f247f-9cc0-11ed-3781-0201b014c5b2", "name": "Initiate audit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.07827568902012852, "y": -1.0099667774086378, "z": 4.999387254105089 }, "color": "#66CCFF", "size": 1.0 }, { "id": "715", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain settlement rule for project,\n Provide asset related specification,\n Stop future bookings on completed project phase,\n Post capitalization", "Type": "Business Process", "Description": "During the month end closing process, costs incurred from the project phase of a capital investment project must be capitalized according to accounting rules.", "hasAssignment": true, "Process_Group": "Asset Accounting", "Scope": "For project costs to be capitalized, all necessary information relevant for the posting and depreciation of an asset is provided, e.g. cost center, useful life, asset class, location / plant, etc. With this information, the settlement rule for the project is maintained.", "Outcome": "Project costs are capitalized and can be incorporated in month end closing figures.", "GUID": "44b6ae88-7eed-11e5-0a66-001bc640cd9b", "name": "Capitalize asset from project phase", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.06262197240712963, "y": -1.0066445182724253, "z": 5.999673198481051 }, "color": "#66CCFF", "size": 1.0 }, { "id": "717", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Trigger service procurement,\n Trigger material procurement,\n Collect materials after goods issue to project,\n Perform project related activities,\n Monitor project activities,\n Collect and document project progress,\n Complete project work,\n Confirm completion of project work,\n Report on project progress ,\n Track project working hours,\n Request rework of project task (s)", "Type": "Business Process", "Description": "Project execution phase involves fulfilment of planned activities, collecting and reporting on project progress, as well as tracking of time, cost, and deliverables.", "Process_Group": "Project Management", "hasAssignment": true, "Scope": "Once the project has been released, it is executed in accordance with the project plan. Depending on the project status, it is possible to assign purchase requisitions and purchase orders, perform goods receipt / issue and book of invoices, time confirmations and other allocations to project elements. During project execution, all actual costs are considered during the individual month end closing activities (e.g. settlement).", "Outcome": "Project related activities are executed and tracked.", "GUID": "44b6ae91-7eed-11e5-0a66-001bc640cd9b", "name": "Execute project", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.0104371375218391, "y": -1.0033222591362128, "z": 1.9999727663546696 }, "color": "#66CCFF", "size": 1.0 }, { "id": "721", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process aims to systematically monitor and evaluate the organizations activities to ensure ongoing adherence to compliance policies, procedures, and relevant regulations. ", "Process_Group": "Risk and compliance Management", "Scope": "This process includes implementing monitoring mechanisms, conducting regular audits, and analyzing data to assess compliance levels. It may involve collaboration with internal audit teams, compliance officers, and external experts to ensure a robust monitoring process.", "Outcome": "A comprehensive compliance monitoring report highlighting areas of compliance strength and potential weaknesses. The organization gains insights into its overall compliance status, allowing for timely corrective actions, continuous improvement, and risk mitigation.", "GUID": "baf954fb-9b52-11ee-3781-0201b014c5b2", "name": "Execute compliance monitoring", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8369701987210297e-16, "y": -1.0, "z": 3.0 }, "color": "#66CCFF", "size": 1.0 }, { "id": "722", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of conducting regulatory mapping and assessment is to systematically identify and analyze applicable laws, regulations, and industry standards that impact an organization. This process ensures a comprehensive understanding of regulatory requirements relevant to its operations. ", "Process_Group": "Risk and compliance Management", "Scope": "This process involves researching and mapping relevant regulations, assessing their impact on organizational activities, and identifying areas of compliance concern. The assessment may extend to evaluating the organizations current compliance status and potential risks associated with non-compliance.", "Outcome": "A documented regulatory map and assessment report, providing insights into the regulatory landscape, potential compliance challenges, and a foundation for developing effective compliance strategies.", "GUID": "baf954f1-9b52-11ee-3781-0201b014c5b2", "name": "Conduct regulatory mapping and assessment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.020874275043676824, "y": -0.9966777408637875, "z": 3.9999455327093396 }, "color": "#66CCFF", "size": 1.0 }, { "id": "723", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to disseminate knowledge and awareness of compliance policies and procedures among employees. It ensures that all relevant personnel understand their roles in maintaining compliance and are equipped to adhere to established standards. ", "Process_Group": "Risk and compliance Management", "Scope": "This process covers designing training programs, communication strategies, and outreach efforts to educate employees about compliance requirements. This may include conducting training sessions, creating informative materials, and establishing communication channels for inquiries.", "Outcome": "An informed and trained workforce with a clear understanding of compliance policies and procedures. Employees are aware of their responsibilities, potential risks, and the importance of maintaining compliance in their day-to-day activities.", "GUID": "baf95500-9b52-11ee-3781-0201b014c5b2", "name": "Train and communicate compliance policies & procedures", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.052184977005940755, "y": -0.9933554817275747, "z": 4.999727665400876 }, "color": "#66CCFF", "size": 1.0 }, { "id": "724", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to establish clear and comprehensive compliance policies and procedures that guide employees on how to adhere to relevant laws, regulations, and internal standards. This process aims to create a framework for compliance management within the organization. Compliance policies & procedures serve as a reference for employees, outlining expectations, responsibilities, and guidelines for maintaining compliance across various aspects of the organization.", "Process_Group": "Risk and compliance Management", "Scope": "The scope of the process includes drafting, reviewing, and finalizing compliance policies and procedures. It involves collaboration with legal experts, subject matter specialists, and key stakeholders to ensure that the documents accurately reflect regulatory requirements and organizational needs.", "Outcome": "A set of well-defined and documented compliance policies and procedures.", "GUID": "baf954f3-9b52-11ee-3781-0201b014c5b2", "name": "Develop compliance policies & procedures", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.09393082682415349, "y": -0.9900332225913622, "z": 5.999264704926107 }, "color": "#66CCFF", "size": 1.0 }, { "id": "725", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of preparing a document that provides insights into whether a companys operations or processes comply with regulatory standards. This process enables a company to avoid legal penalties because non-compliance issues are detected and resolved early. By so doing the company enhances its market reputation and competitiveness.", "Process_Group": "Compliance and Audits Reporting", "Scope": "By identifying the relevant regulatory requirements, current operations are compared to the regulatory requirements to identify gaps. Once the gaps are identified and documented, appropriate corrective actions are implemented. ", "Outcome": "Compliance with regulatory standards assessed.", "GUID": "47644cba-5b9e-11ee-3781-0201b014c5b2", "name": "Generate regulatory compliance report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.041745707720785806, "y": -0.9867109634551494, "z": 1.9995642765079824 }, "color": "#66CCFF", "size": 1.0 }, { "id": "728", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect data for Management Review,\n Analyze data for Management Review", "Type": "Business Process", "Description": "The IMS Representative collects all available and necessary data from the relevant reports and assessments for the management review currently being prepared and evaluates this data. The basis for conducting the management review is thus created.", "Process_Group": "Quality Management", "hasAssignment": true, "Scope": "Gathering the available and necessary data in order to be able to perform the Management Review.", "Outcome": "* Data evaluation for Management Review", "GUID": "975f5203-e2fa-11eb-2c3e-001bc641ce4f", "name": "Collect and analyze data", "Business_Rules": "", "Prerequisite": "* Status report product testing * Previous Management Review evaluations * Status report Health & Safety * Status report Energy Management System(s)* Status report Quality Management System(s) * Status report Environmental Management System(s) * Supplier evaluation * Reports / evaluations on customer satisfaction * Status report Business Process Management (BPM)" }, "position": { "x": -0.07827000441858215, "y": -0.9833887043189369, "z": 2.998978793924411 }, "color": "#66CCFF", "size": 1.0 }, { "id": "730", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Evaluate data for Management Review,\n Create Management Review report,\n Create plan of measures from Management Review", "Type": "Business Process", "Description": "Top management evaluates the information and results from the management review with regard to target achievement. The overall result of the assessment and the identified necessary measures for improvement are documented in the management review report.", "Process_Group": "Project Management", "hasAssignment": true, "Scope": "Evaluate data and derive actions for conducting management review with top management.", "Outcome": "* Plan of measures * Management Review report", "GUID": "975f5205-e2fa-11eb-2c3e-001bc641ce4f", "name": "Conduct management review", "Business_Rules": "", "Prerequisite": "* Data evaluation for Management Review" }, "position": { "x": -0.125225754237927, "y": -0.9800664451827243, "z": 3.9980393332826956 }, "color": "#66CCFF", "size": 1.0 }, { "id": "737", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of analyzing processes is to systematically examine and evaluate the various elements and stages involved in a specific business process. This analysis aims to understand the efficiency, effectiveness, and overall performance of the process. The ultimate goal is to identify areas for improvement, enhance operational efficiency, and align the process with organizational objectives.", "Process_Group": "Process Management", "Scope": "The scope of process analysis encompasses the entire lifecycle of a business process, from initiation to completion. It involves examining inputs, outputs, tasks, roles, technologies, and interactions within the process. The scope may also extend to external factors such as regulations, customer requirements, and market dynamics. Process analysis can be applied to diverse business functions, ranging from manufacturing and service delivery to administrative and support processes.", "Outcome": "A comprehensive understanding of the strengths, weaknesses, and dynamics of a particular business process. ", "GUID": "09ebd491-9315-11ed-3781-0201b014c5b2", "name": "Analyze processes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.18261011528829474, "y": -0.9767441860465116, "z": 4.996664241851197 }, "color": "#66CCFF", "size": 1.0 }, { "id": "738", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "- The flow of the target process is modeled and coordinated with the process participants and presented in a flow chart or concretized in the form of step descriptions. - The entire target process, including all necessary accompanying documents, is released by the process owner following coordination in the process control group.", "Process_Group": "Process Management", "Scope": "Structured communication of process flows requires the visualization of processes in a descriptive form of representation and is based on the purpose of the representation. The representation should be clear and understandable. The following representation variants of processes are most commonly used: Value chain chart/ flowchart / BPMN / event-driven process chain (EPC) / swim lanes (cross functional flowchart) / staircase representation (diagonal matrix).", "Outcome": "Creation of clear and structured representations that provide a detailed understanding of how specific activities or workflows are executed within an organization.", "GUID": "41fe8308-957e-11ed-3781-0201b014c5b2", "name": "Model and document processes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.250419677568078, "y": -0.973421926910299, "z": 5.994771887660672 }, "color": "#66CCFF", "size": 1.0 }, { "id": "739", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To scope processes in the organization, the initial situation must be analyzed. For this purpose, the existing activities of process-oriented work are to be systematically surveyed and analyzed for their relevance. ", "Process_Group": "Process Management", "Scope": "- Identification (recording of the relevant business processes) and location of the processes, based on a delimitation and context analysis. - Representation of the processes in the process map.", "Outcome": "The process map provides an overview of the central activities of the organization and maps the interactions.", "GUID": "41fe8304-957e-11ed-3781-0201b014c5b2", "name": "Scope processes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.09390013231650701, "y": -0.9700996677740863, "z": 1.9977944752028278 }, "color": "#66CCFF", "size": 1.0 }, { "id": "740", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of processes release and publishing is to systematically coordinate and manage the deployment of content to a productive environment, ensuring a controlled and efficient transition from development to live operational use. This involves making new features, updates, or content available to end-users while minimizing disruptions and maintaining the integrity of the overall system.", "Process_Group": "Process Management", "Scope": "This process includes planning and executing the release strategy, coordinating with development and operations teams, conducting necessary testing, and managing the deployment of content. It encompasses the entire lifecycle of the release, from planning and preparation to actual deployment and post-release monitoring.", "Outcome": "The successful deployment and availability of new process content in the live environment.", "GUID": "d9129890-a263-11ed-3781-0201b014c5b2", "name": "Release and publish processes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.15648672230113142, "y": -0.9667774086378738, "z": 2.9959158709388767 }, "color": "#66CCFF", "size": 1.0 }, { "id": "743", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Document control and monitoring must ensure that documents are available and adequately protected.", "Process_Group": "Document Management", "Scope": "Document control includes: - Automatic distribution to interested parties (departments, teams, posts and specific employees). - Setting permissions e.g. set read or print permissions. - Requiring active read confirmation (acknowledgement) logging - Enable version comparison - Automatic withdrawal of documents that are no longer valid and notification", "Outcome": "steered documents", "GUID": "167e34fb-9350-11ed-3781-0201b014c5b2", "name": "Control and monitor documents", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.22949197923147854, "y": -0.9634551495016612, "z": 3.993411252484324 }, "color": "#66CCFF", "size": 1.0 }, { "id": "744", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Document management supports the central storage of all relevant information in the company and controls the filing of all digital and analog documents, as well as the distribution of documents in the company to the right people and a valid and traceable process for changes and approvals of documents. The regulations include in detail: - Provision of information - keeping all important and valid (current version) documents centrally and always accessible. - Clear responsibility and permission hierarchy for creating, revising and retrieving documents - Automatic distribution of information to all (authorized) employees and departments including receipt and read confirmation - Maintenance of the information flow within the company - Standard-compliant and audit-proof documentation and archiving - Guaranteed traceability - Support for quality management and the continuous improvement process", "Process_Group": "Document Management", "Scope": "Creation and definition of guidelines, documentation requirements, responsibilities, filing and document structures, Development of data security and data protection concepts", "Outcome": "Documentation Manual", "GUID": "2faa432f-a6f1-11ed-3781-0201b014c5b2", "name": "Define documentation requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.3129109318645167, "y": -0.9601328903654485, "z": 4.990199069047214 }, "color": "#66CCFF", "size": 1.0 }, { "id": "745", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "A new document must first be reviewed and approved by a responsible party to become an applicable and governed document. In the four-eyes principle, the document is checked for suitability, appropriateness, content, compliance with the established conventions.", "Process_Group": "Document Management", "Scope": "The approval process (workflow): In order for a document to be considered managed, it must inevitably go through various review and approval steps before it is marked as valid and distributed to the appropriate employees. This is referred to as three processing stages (processing, checking, release). However, there are several variants of these processing steps. In most cases, several steps take place in one stage or additional steps are inserted: Unmanaged document: 1-stage document (processing only) Guided document: 2-step document (editing, review and release) 3-step document (editing, checking, release) 4-level document (editing, content check, formal check, release)", "Outcome": "Release of the document", "GUID": "167e34f9-9350-11ed-3781-0201b014c5b2", "name": "Check and release documents", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.4067380415812148, "y": -0.9568106312292359, "z": 5.986197805412938 }, "color": "#66CCFF", "size": 1.0 }, { "id": "746", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Documents are created in accordance with the standardized regulations in the organization. It is important to note that documents (e.g. manuals, process descriptions, regulations, etc.) are changeable and their actuality must be marked, and records (e.g. proofs, protocols, reports, etc.) are not changeable and a retention period must be taken into account.", "Process_Group": "Document Management", "Scope": "It must be ensured that the history of a document can be traced from its creation to its distribution (and, if necessary, its withdrawal). The automatic marking and description of the documents (e.g. title, file name, author, reference number), by assignment of version numbers, valid-to, valid-from, transaction number and the automatic recording of the author and the date make this possible.", "Outcome": "documented information", "GUID": "167e34f7-9350-11ed-3781-0201b014c5b2", "name": "Generate documents", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.14599062932181517, "y": -0.9534883720930232, "z": 1.9946645673271033 }, "color": "#66CCFF", "size": 1.0 }, { "id": "749", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The documentation of risks is also necessary from a legal perspective. In this way, the company and the responsible management provide evidence of what they have initiated or undertaken in detail as part of risk management. Risk reporting involves the ongoing reporting of identified and assessed risks as well as the measures initiated to address risks to the relevant stakeholders. The risk reporting system must ensure that the findings of risk control are communicated at an early stage and in a comprehensible, meaningful form.", "Process_Group": "Risk and compliance Management", "Scope": "The reporting system includes the presentation and assessment of the risk situation and, if necessary, proposals for action to improve the risk position. It thus ensures appropriate communication within the company and enables decisions to be made on necessary measures for risk management. In addition, the risk reporting system covers accountability functions (evidence of dutiful conduct), assurance functions (error-preventing measures) and auditability functions (basis for review by the Supervisory Board, internal audit, etc.). The documentation and reports should contain all further information explaining and substantiating the significance, consequences and options for action for the individual risk. These can be compiled in a risk catalog or risk manual. It is important to make changes visible on a regular basis. In doing so, the information can be divided according to the companys business areas.", "Outcome": "Risk report, risk catalog or risk manual", "GUID": "9eb01170-9ca1-11ed-3781-0201b014c5b2", "name": "Record and report results", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.23459690338930606, "y": -0.9501661129568106, "z": 2.990813316293772 }, "color": "#66CCFF", "size": 1.0 }, { "id": "750", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose assess and evaluate risks process is to systematically identify, analyze, and evaluate potential risks that could impact the achievement of organizational objectives. It aims to understand the likelihood and impact of each identified risk. The evaluation of risks assists in prioritizing risks based on their significance, enabling the organization to focus on mitigating or managing the most critical risks.", "Process_Group": "Risk and compliance Management", "Scope": "The process involves conducting a comprehensive risk assessment across various aspects of the organization, including projects, operations, and strategic initiatives. The assessment may cover financial risks, operational risks, compliance risks, and other relevant categories. The scope also includes identifying risk triggers and potential scenarios.", "Outcome": "A detailed risk assessment that outlines identified risks, their potential impact, and the likelihood of occurrence.", "GUID": "c844d02d-67e7-11e9-2ddf-001bc640cd9b", "name": "Assess and evaluate risks", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.3336019651560358, "y": -0.9468438538205981, "z": 3.986064441130378 }, "color": "#66CCFF", "size": 1.0 }, { "id": "751", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Define risk controls process aims to develop strategies and measures to mitigate or manage identified risks. It involves creating a proactive plan to address risks, reduce their impact, or take advantage of potential opportunities. The defined risk controls provide a roadmap for managing risks throughout the organization and contribute to a more resilient and proactive approach to risk management.", "Process_Group": "Risk and compliance Management", "Scope": "The scope includes developing risk mitigation strategies, implementing control measures, and establishing contingency plans. It may involve collaboration with relevant stakeholders to ensure that risk controls align with organizational objectives and are feasible to implement. The scope also covers monitoring and updating risk controls as needed.", "Outcome": "A set of documented risk controls and mitigation plans. This includes specific actions to be taken, responsibilities assigned, and resources allocated to address identified risks.", "GUID": "fdc640d2-9a9f-11ee-3781-0201b014c5b2", "name": "Define risk controls", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.44299871741091423, "y": -0.9435215946843853, "z": 4.9803365485047575 }, "color": "#66CCFF", "size": 1.0 }, { "id": "752", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of defining the risk management scope is to establish the boundaries and objectives of the risk management process within an organization. It outlines the areas, activities, and assets that will be considered in the risk management process. It provides clarity on the focus areas, helping in the efficient allocation of resources and ensuring that the risk management process aligns with organizational objectives.", "Process_Group": "Risk and compliance Management", "Scope": "The process involves clearly defining what aspects of the organizations operations, projects, or processes will be included in the risk management efforts. This may include identifying specific projects, departments, or types of risks that need to be addressed. The scope also outlines the goals and desired outcomes of the risk management process.", "Outcome": "A documented and well-defined scope statement that serves as a foundation for the organizations risk management efforts.", "GUID": "fdc640e8-9a9f-11ee-3781-0201b014c5b2", "name": "Define risk management scope", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.5627794966881958, "y": -0.9401993355481728, "z": 5.973548295452828 }, "color": "#66CCFF", "size": 1.0 }, { "id": "753", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Risk monitoring involves checking at regular, predefined intervals whether the measures taken have brought about any changes in the risks, and if so, which ones. ", "Process_Group": "Risk and compliance Management", "Scope": "On the basis of this review, potential improvements can be identified and implemented. It is also possible to determine whether any new risks have come to light.", "Outcome": "Identification of improvement potentials", "GUID": "9eb0116e-9ca1-11ed-3781-0201b014c5b2", "name": "Monitor and review risk", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.19798173531536167, "y": -0.93687707641196, "z": 1.9901766837347679 }, "color": "#66CCFF", "size": 1.0 }, { "id": "758", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The results of the customer satisfaction survey are analyzed and evaluated in order to derive measures for improvement. ", "Process_Group": "Quality Management", "Scope": "The customer satisfaction results are relevant inputs for the management review.", "Outcome": "Measures for improvement", "GUID": "e98d522c-9c90-11ed-3781-0201b014c5b2", "name": "Evaluate customer satisfaction analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.3125473699554437, "y": -0.9335548172757475, "z": 2.9836746038289657 }, "color": "#66CCFF", "size": 1.0 }, { "id": "759", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The organization must monitor the customers perception of the degree of fulfillment of their requirements and expectations. Suitable methods are selected and determined for this purpose, such as customer surveys and feedback by the customer on products supplied or services rendered. ", "Process_Group": "Quality Management", "Scope": "Additional indicators of customer satisfaction can be complaint rates and analysis of market shares. The planning of the customer satisfaction analysis also includes the determination of the regular intervals of the survey, criteria, scope, customer groups, responsibilities, evaluation systems including key figures and method-dependent resources.", "Outcome": "internal guideline for the survey of customer satisfaction", "GUID": "e98d5228-9c90-11ed-3781-0201b014c5b2", "name": "Plan customer satisfaction analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.43748483351149675, "y": -0.930232558139535, "z": 3.9760039009597836 }, "color": "#66CCFF", "size": 1.0 }, { "id": "760", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Customer surveys or other defined methods are used to survey customer satisfaction. ", "Process_Group": "Quality Management", "Scope": "The results are collected and documented.", "Outcome": "Customer satisfaction feedback", "GUID": "e98d522a-9c90-11ed-3781-0201b014c5b2", "name": "Perform customer satisfaction analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.5727849076361797, "y": -0.9269102990033222, "z": 4.967083394667762 }, "color": "#66CCFF", "size": 1.0 }, { "id": "763", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Immediately after becoming aware of a problem, immediate measures shall be taken to limit the the effects of the problem, with the aim of ensuring that the customer does not continue to receive, use or deliver defective products are received, used or delivered.", "Process_Group": "Quality Management", "Scope": "The effectiveness of the immediate measures introduced must be ensured until suitable corrective measures have been introduced. In addition, it must be ensured that information about the problem is passed on within the affected area (e.g. downstream shift) as well as to potentially affected areas (e.g. other production lines/plants) are forwarded. Suitable immediate measures can be replacement deliveries, repair, credit notes, the sorting out of material suspected of being faulty with subsequent 100% inspection or even the temporary halt of production. Immediate actions shall be documented along with the associated results. If no immediate measures are possible, this must be justified and documented. ", "Outcome": "Immediate measures implemented incl. documentation and information.", "GUID": "1d2993e0-ad01-11ed-3781-0201b014c5b2", "name": "Implement immediate measure", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7184378092343533, "y": -0.9235880398671097, "z": 5.956831969617957 }, "color": "#66CCFF", "size": 1.0 }, { "id": "764", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "After successful verification of the effectiveness of the corrective measures introduced, the immediate measure taken is cancelled. ", "Process_Group": "Quality Management", "Scope": "For a later or earlier cancellation of the immediate measures, the reasons must be documented.", "Outcome": "Cancellation of the immediate measures (if necessary, after approval by the customer).", "GUID": "6da3e762-ad15-11ed-3781-0201b014c5b2", "name": "Repeal immediate measure", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.2498380545416013, "y": -0.9202657807308969, "z": 1.9843338797951489 }, "color": "#66CCFF", "size": 1.0 }, { "id": "765", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "A correction is the elimination of an error or non-conformity that has occurred and is carried out by the responsible department. QM accompanies the correction. ", "Process_Group": "Quality Management", "Scope": "Within a correction, only the symptom is eliminated. The correction can represent an adjustment, rework, repair, return, special release, reclassification or recall action. A correction can be made before, in connection with or after a corrective action.", "Outcome": "Elimination of the occurred error or non-conformity", "GUID": "53338c23-abb9-11ed-3781-0201b014c5b2", "name": "Implement accompanying correction", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.3902850530061761, "y": -0.9169435215946844, "z": 2.974504593608819 }, "color": "#66CCFF", "size": 1.0 }, { "id": "768", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To eliminate the causes, suitable solutions or improvement measures must be found to prevent recurrence.", "Process_Group": "Quality Management", "Scope": "Procedure: - Define the desired state after the problem has been solved. - Definition of the necessary tasks for solving the problem with objective metrics such as costs, technical performance data, etc. as far as possible.", "Outcome": "Proposal for an improvement measure", "GUID": "993cc53f-a230-11ed-3781-0201b014c5b2", "name": "Find solution to eliminate the causes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.5410698604203177, "y": -0.9136212624584719, "z": 3.9632364812290395 }, "color": "#66CCFF", "size": 1.0 }, { "id": "769", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The improvement measure is implemented according to the measure plan.", "Process_Group": "Quality Management", "Scope": "The designated measure controller of a process / a business area is responsible for recording and evaluating all measures being identified for the processes in the central measure plan and for assigning the implementation to the respective process owner (who can delegate within his process). The corresponding status update and the completion message is sent by the process owner or the person to whom the task has been delegated to the measure controller.", "Outcome": "* Updated plan of measures", "GUID": "f61d9766-a79a-11ed-3781-0201b014c5b2", "name": "Perform improvement measures", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7021811435763216, "y": -0.9102990033222591, "z": 4.950448630337037 }, "color": "#66CCFF", "size": 1.0 }, { "id": "770", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The performance of investigations and the implementation of improvement measures are monitored. The respective measure controller receives the reports on the status of a measure and documents it in the central plan of measures as up to date as possible.", "Process_Group": "Quality Management", "Scope": "Each defined improvement measure is monitored with regard to timely implementation and result. The implementation of the measures is tracked and documented in regular meetings with the responsible person. Deviations from planned deadlines can be tracked. The quality notification is completed when all defined activities have been carried out.", "Outcome": "Status and completion message", "GUID": "83b25aa4-ac6d-11ed-3781-0201b014c5b2", "name": "Monitor improvement measures", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8736070064100276, "y": -0.9069767441860466, "z": 5.9360602084506615 }, "color": "#66CCFF", "size": 1.0 }, { "id": "771", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter status and completion message (plan of measures),\n Verify completion status,\n Conduct effectiveness check,\n Update plan of measures,\n Define new measure", "Type": "Business Process", "Description": "If a measure is reported as completed, the responsible management carries out an effectiveness check. ", "hasAssignment": true, "Process_Group": "Quality Management", "Scope": "Effectiveness reviews can take the form of process/product evaluations, performance measurements, or audits. If the effectiveness is confirmed, the measure can be closed, otherwise a new measure must be defined by the measure controller. The results of the effectiveness test are documented.", "Outcome": "Confirmation of effectiveness, the results are incorporated into the management review.", "GUID": "f61d9769-a79a-11ed-3781-0201b014c5b2", "name": "Execute follow up measures", "Business_Rules": "", "Prerequisite": "* Status and completion message" }, "position": { "x": -0.3015242830083672, "y": -0.9036544850498338, "z": 1.9771401333128338 }, "color": "#66CCFF", "size": 1.0 }, { "id": "773", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Potential for improvement can typically be identified from a variety of sources, e.g.: - Audits - Company suggestion scheme (BVW) - reviews - Working groups or meetings - Other assessments (e.g. internal audit or auditing) - tax consultants - benchmarks - complaints - Suppliers and partners", "Process_Group": "Quality Management", "Scope": "The identified improvement potentials are to be consolidated without losing sight of the sources of the suggestions. Subsequently, improvement potentials are prioritized. The criteria according to which the prioritization is to be carried out can be manifold. Typically, the following criteria are used: - Feasibility (Can we do it at all?) - Effort/cost - Benefit/effect - Noticeable for customers - Noticeable for employees - Strengthens competitiveness - Supports strategy - Necessary for compliance with laws The focus within the evaluation should be on the benefits for the company. Excellent companies measure the monetary added value of the measures and relate it to the effort and expense of the measures.", "Outcome": "Achieve maximum benefit from the identified improvement potentials.", "GUID": "993cc53b-a230-11ed-3781-0201b014c5b2", "name": "Identify potential for improvement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.4677570284120135, "y": -0.9003322259136213, "z": 2.9633095286134323 }, "color": "#66CCFF", "size": 1.0 }, { "id": "774", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The responsible person with decision-making authority reviews the proposed solutions and gives the go-ahead to implement the improvement measure, with naming of a responsible person or project manager.", "Process_Group": "Quality Management", "Scope": "The developed solution proposal for an improvement measure is reviewed in terms of appropriateness, feasibility, time and cost.", "Outcome": "Release for implementation of the improvement measure.", "GUID": "993cc541-a230-11ed-3781-0201b014c5b2", "name": "Take implementation decision", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.6442865247766183, "y": -0.8970099667774087, "z": 3.9477708740492106 }, "color": "#66CCFF", "size": 1.0 }, { "id": "775", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To generate effective improvements, it is necessary to explore the problem and find the root causes. Root cause analysis is a structured approach and includes all root cause identification, assessment and prioritization activities.", "Process_Group": "Quality Management", "Scope": "The root causes of the problem are identified and assessed by the team. Methods and tools can be used to identify the root causes, such as Ishikawa diagram (representation of cause-effect relationships), on-site visit (Gemba), 5 Why method and the W-question technique. The assessment should consider frequency and impact of problem issues for prioritization.", "Outcome": "Effective troubleshooting can only be done on the basis of identifying the root cause of the problem. If causes are not eliminated, only the symptom is treated and the problem may continue to occur.", "GUID": "993cc53d-a230-11ed-3781-0201b014c5b2", "name": "Analyze causes of problem", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8310993317498084, "y": -0.893687707641196, "z": 4.930443580527519 }, "color": "#66CCFF", "size": 1.0 }, { "id": "776", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The content of the action plan is checked and approved.", "Process_Group": "Quality Management", "Scope": "In terms of content, the check is: who does what, when and how in what period of time - again based on objective benchmarks such as deadlines, costs and resources.", "Outcome": "Confirmation and approval of the action plan", "GUID": "5bccfaba-a210-11ed-3781-0201b014c5b2", "name": "Check and release action plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.0281814483972882, "y": -0.8903654485049834, "z": 5.911247153450079 }, "color": "#66CCFF", "size": 1.0 }, { "id": "777", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "After the release of the improvement measures, an implementation plan must be prepared by the responsible person, which contains a description of the measures to be carried out.", "Process_Group": "Quality Management", "Scope": "In the action plan, the goal, scope and activities for improvement are defined with the designation of responsibilities, deadline and required resources.", "Outcome": "Action plan", "GUID": "993cc543-a230-11ed-3781-0201b014c5b2", "name": "Create action plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.35300523252196925, "y": -0.8870431893687707, "z": 1.9686003418195657 }, "color": "#66CCFF", "size": 1.0 }, { "id": "782", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify local labour market specifics,\n Analyze local labour market specifics,\n Update EVP to fit local market specifics,\n Request approval for localized EVP,\n Share localized EVP with stakeholders ,\n Review feedback on localized EVP", "Type": "Business Process", "Description": "The process si concerned with localizing an employee value proposition to fit the specific labour market.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Identifying and analyzing specifics of local labour market, and updating EVP in order to improve candidate experience taking into account factors specific to talent segments and markets where the organization operates.", "Outcome": "Employer value proposition localized.", "GUID": "c4b8d26f-f56c-11e8-2ddf-001bc640cd9b", "name": "Localize employer value proposition and core messages", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.544910552938309, "y": -0.8837209302325582, "z": 2.9500970304883984 }, "color": "#66CCFF", "size": 1.0 }, { "id": "784", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review employer branding strategy,\n Identify employer branding activities,\n Align with stakeholders on employer branding activities,\n Request approval for employer branding activities,\n Plan employer branding activities,\n Review feedback on employer branding activities,\n Update employer branding activities,\n Share employer branding plan with stakeholders,\n Develop employer branding material", "Type": "Business Process", "Description": "Based on employer branding strategy, employer branding activities are planned and prepared.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Reviewing employer branding strategy, identifying and planning branding activities,and developing branding material.", "Outcome": "Employer branding activities planned and prepared.", "GUID": "f783a632-d579-11e9-0cfc-001bc641ce4f", "name": "Plan and prepare employer branding activities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7470645562572384, "y": -0.8803986710963456, "z": 3.9296176084683068 }, "color": "#66CCFF", "size": 1.0 }, { "id": "786", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Evaluate existing perception of employer brand,\n Determine employer value proposition (EVP) ,\n Test EVP with group of existing employees,\n Receive feedback on EVP,\n Evaluate feedback on EVP,\n Improve EVP,\n Test improved EVP with group of externals,\n Share EVP with stakeholders,\n Request approval of EVP,\n Review feedback on EVP,\n Define evaluation method for testing EVP", "Type": "Business Process", "Description": "The process describes developing employer value proposition (EVP) that will be used for branding strategy. The purpose of EVP is to communicate companys competitive advantage in the labour market. However, it should not be about compensation, but rather about companys deeper purpose.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Evaluate existing perception of the organization. Develop EVP and test it with a group of existing employees. Then test EVP on a sample group of externals. Make adjustments where required and finalise the EVP. ", "Outcome": "Employee value proposition approved.", "GUID": "c4b8d26d-f56c-11e8-2ddf-001bc640cd9b", "name": "Develop employer value proposition (EVP)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.9594517041319615, "y": -0.8770764119601329, "z": 4.907081864758145 }, "color": "#66CCFF", "size": 1.0 }, { "id": "788", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review employer branding activities status,\n Analyze impact of employer branding,\n Report results of employer branding impact,\n Continue in planned employer branding activities,\n Review required changes,\n Update employer branding plan & activities,\n Share updated employer branding plan and activities", "Type": "Business Process", "Description": "The process of monitoring employer branding activities is ongoing to ensure relevance of employer branding activities.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Review past, ongoing and planned employer branding activities, analyze impact of employer branding, align with stakeholders on results of the analysis, and update employer branding plan if needed.", "Outcome": "Employer branding activities monitored.", "GUID": "3103c804-35dd-11ee-3781-0201b014c5b2", "name": "Monitor employer branding activities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.182055900289941, "y": -0.8737541528239203, "z": 5.8824096974445546 }, "color": "#66CCFF", "size": 1.0 }, { "id": "790", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review employer value proposition,\n Develop organizations brand vision,\n Develop organizations brand mission,\n Develop organizations brand story,\n Develop employer branding strategy,\n Request approval for employer branding strategy,\n Share employer branding strategy with stakeholders,\n Review feedback on employer branding strategy,\n Update employer branding strategy", "Type": "Business Process", "Description": "Based on the branding needs and employee value proposition, a branding strategy is developed.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Reviewing EVP, developing the organizations brand vision, brand mission, and brand story, taking into account all target groups, and developing and approving branding strategy.", "Outcome": "Employer branding strategy approved.", "GUID": "7d720701-f56f-11e8-2ddf-001bc640cd9b", "name": "Develop employer branding strategy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.4042458546434606, "y": -0.8704318936877076, "z": 1.9587203192399822 }, "color": "#66CCFF", "size": 1.0 }, { "id": "792", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify employees to engage in employer branding,\n Align with employees on engagement in employer branding,\n Engage employees in employer branding", "Type": "Business Process", "Description": "To support the impact of the employer branding strategy, engage existing employees in employer branding activities. By engaging existing employees, companys employer branding will gain more credibility.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Identifying suitable employees for employer branding activities, aligning with identified employees on their engagement in employer branding, and engaging employees in employer branding activities.", "Outcome": "Employees engaged in employer branding.", "GUID": "3103a0f0-35dd-11ee-3781-0201b014c5b2", "name": "Engage existing employees in employer branding activities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.6216931001530626, "y": -0.867109634551495, "z": 2.9348760943559564 }, "color": "#66CCFF", "size": 1.0 }, { "id": "794", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Initiate employer brand audit,\n Review companys mission,\n vision,\n values and culture,\n Prepare internal employer brand research,\n Conduct internal employer brand research,\n Prepare external employer brand research,\n Approve internal employer brand research,\n Approve external employer brand research,\n Conduct external employer brand research,\n Analyze data from internal and external employer brand research,\n Identify target groups for employer branding,\n Evaluate target groups for employer branding,\n Consolidate findings,\n Prepare report from employer brand audit,\n Share report with stakeholders", "Type": "Business Process", "Description": "This process enables the organisation to assess its branding needs in order to derive strategies that improve its reputation internally and externally. ", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Review companys mission, vision, values and culture. Conduct internal and external research (surveys, career market monitoring, social media search etc.) to understand aspects of your employer brand. Conduct critical analysis of the organizations strengths and weaknesses. Evaluate target groups for employer branding initiatives. ", "Outcome": "Employer branding audit completed.", "GUID": "c4b8d26b-f56c-11e8-2ddf-001bc640cd9b", "name": "Conduct employer brand audit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8493339831620539, "y": -0.8637873754152825, "z": 3.908789043303064 }, "color": "#66CCFF", "size": 1.0 }, { "id": "798", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Capture job description for all employees job assignments,\n Maintain job descriptions in HR system,\n Review interdependencies between job assignments,\n Adjust job descriptions", "Type": "Business Process", "Description": "Process for capturing job descriptions related to an employees assignments.", "Process_Group": "Employee Data Management", "hasAssignment": true, "Scope": "For all employee assignments capture the job description and any interdependencies between assignments.", "Outcome": "Job descriptions for assignments are maintained in HR management system.", "GUID": "d36579ed-6809-11ec-2c3e-001bc641ce4f", "name": "Maintain job descriptions of assignments", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.087150877907784, "y": -0.8604651162790697, "z": 4.8803793877796355 }, "color": "#66CCFF", "size": 1.0 }, { "id": "800", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Capture employee information for payroll,\n Share payroll information with payroll accountant,\n Check information correctness,\n Request additional information from employee,\n Receive additional information from employee,\n Register employee with tax authority,\n Register employee for social insurance,\n Register employee for health insurance", "Type": "Business Process", "Description": "Process to ensure that new employees details are captured in payroll.", "Process_Group": "Employee Data Management", "hasAssignment": true, "Scope": "In this process, all the banking institutional data are maintained to ensure that the employes wages and salaries can be transferred when they are due.", "Outcome": "Employee payroll set up.", "GUID": "5dad9938-6cb1-11e9-2ddf-001bc640cd9b", "name": "Conduct employee payroll setup", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.335125603737886, "y": -0.8571428571428572, "z": 5.849567473090942 }, "color": "#66CCFF", "size": 1.0 }, { "id": "802", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect employees biographical information,\n Document employees biographical information,\n Complete completeness of employees biographical information", "Type": "Business Process", "Description": "In a concurrent employment set-up, this process ensures that there is a single source of truth for employee biographical data. ", "Process_Group": "Employee Data Management", "hasAssignment": true, "Scope": "Collect and document all employee biographical data including address information, personal Information, contact Information and ID. ", "Outcome": "Employee biographical information is available and can be mapped to job assignments. ", "GUID": "d36579e3-6809-11ec-2c3e-001bc641ce4f", "name": "Capture employee biographical information", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.4552112645497558, "y": -0.8538205980066444, "z": 1.947506791933474 }, "color": "#66CCFF", "size": 1.0 }, { "id": "804", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect information on employee benefits,\n Enroll employee in benefits,\n Inform stakeholders about employees ineligibility,\n Check employees eligibility for benefits,\n Change benefits selection", "Type": "Business Process", "Description": "Employees who fulfill eligibility criteria will be enrolled in new benefits plans. This can happen manually or via automatic (e.g. SAP ERP) enrollment.", "Process_Group": "Employee Data Management", "hasAssignment": true, "Scope": "Collecting information on employees benefits plan (i.e., health, insurance, savings, credit etc.) and other benefits, checking employees eligibility for such a plan and enrolling employee in this plan.", "Outcome": "Employee benefits set up.", "GUID": "5dad993a-6cb1-11e9-2ddf-001bc640cd9b", "name": "Conduct employee benefits set up", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.69805239618713, "y": -0.8504983388704319, "z": 2.9176570826910773 }, "color": "#66CCFF", "size": 1.0 }, { "id": "806", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create concurrent job assignments in HR system,\n Link employees information with all job assignments,\n Check for completeness,\n Fill in missing information", "Type": "Business Process", "Description": "In a concurrent employment set-up, this process ensures sync between employee biographical information and their job assignments.", "Process_Group": "Employee Data Management", "hasAssignment": true, "Scope": "HR management system contains employee biographical information which is linked to multiple employment information entities, each with a corresponding job information, compensation information and payment Information.", "Outcome": "HR management system contain employee information with all related job assignments.", "GUID": "d36579e8-6809-11ec-2c3e-001bc641ce4f", "name": "Link employee information with assignments", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.9510251800509956, "y": -0.8471760797342194, "z": 3.8852993587250095 }, "color": "#66CCFF", "size": 1.0 }, { "id": "810", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with stakeholders,\n Conduct cost-benefit analysis,\n Collect relevant information,\n Create cost plan,\n Determine planning approach", "Type": "Business Process", "Description": "The purpose of creating a cost plan is to provide an efficient estimate of the actual cost to be incurred in filling or closing the identified jobs or positions.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "The cost plan must be prepared within the organizations annual budget. It involves a cost-benefit analysis. Additionally, the cost plan depends on the chosen planning approach. For instance, if the organization intends to terminate roles, it must take into consideration the present value of all future benefit packages that must be paid out to the affected employees.", "Outcome": "Cost plan created.", "GUID": "d932a660-1e22-11ed-3781-0201b014c5b2", "name": "Create cost plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2141099149625405, "y": -0.8438538205980066, "z": 4.850354328746473 }, "color": "#66CCFF", "size": 1.0 }, { "id": "812", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with stakeholders on required resources,\n Review business strategy,\n Create short-term outlook of required resources ,\n Determine required resources ,\n Prepare report of required resources", "Type": "Business Process", "Description": "The process involves identifying the tasks or positions to be filled or closed in the short term typically within a twelve month period.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "HR aligns with different organisational units to determine the right tasks or positions to be filled or closed", "Outcome": "Total number of tasks or positions to be filled or closed is determined.", "GUID": "d932a652-1e22-11ed-3781-0201b014c5b2", "name": "Determine required resources", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.487286348267022, "y": -0.8405315614617941, "z": 5.812742839508604 }, "color": "#66CCFF", "size": 1.0 }, { "id": "814", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify available workforce,\n Analyze KSAOs of available workforce,\n Compare available against required resources,\n Analyze salaries of available workforce,\n Consider succession planning,\n Report results", "Type": "Business Process", "Description": "This process involves determining if the organization has the right number of people with the right skills in the right positions and if salaries have to be adjusted accordingly. ", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Identify the total number of employees in each organizational unit, their respective positions, Knowledge, Skills, Abilities, and Other characteristics (KSAOs), experience, salaries, and all other relevant employee data that affect headcount.", "Outcome": "Analysis of the current workforce is completed to determine the appropriate headcount planning approach.", "GUID": "e7a51a82-c21d-11ec-4ad5-0201b014c5b2", "name": "Conduct headcount and salary review", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.5058667647833616, "y": -0.8372093023255813, "z": 1.9349673941148504 }, "color": "#66CCFF", "size": 1.0 }, { "id": "816", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Communicate headcount plan to stakeholders,\n Supervise implementing headcount plan,\n Set up headcount plan in HR system,\n Identify need for employee hiring,\n Identify need for employee termination", "Type": "Business Process", "Description": "This process describes implementing the headcount plan resulting in identifying need for employee hiring.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Setting up headcount plan in HR system, communicating headcount plan with stakeholders, supervising execution of the plan and tracking progress.", "Outcome": "Headcount plan implemented.", "GUID": "d932a668-1e22-11ed-3781-0201b014c5b2", "name": "Implement headcount plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7739364553224877, "y": -0.8338870431893688, "z": 2.8984517182666445 }, "color": "#66CCFF", "size": 1.0 }, { "id": "818", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with stakeholders,\n Prepare plan for employee hiring,\n Prepare plan for employee terminations,\n Prepare plan for employee transfers,\n Consolidate operational headcount plans", "Type": "Business Process", "Description": "This process involves deciding when and how the jobs and positions are to be filled or closed (in cases of termination) and who is responsible for executing a particular task in the plan.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Plan for hires, terminations, transfers or consolidations based on the headcount review and business objectives.", "Outcome": "Draft plan for filling or closing the identified jobs or positions is prepared for approval.", "GUID": "d932a65d-1e22-11ed-3781-0201b014c5b2", "name": "Determine headcount planning approach", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.0520689151453357, "y": -0.830564784053156, "z": 3.859164546606547 }, "color": "#66CCFF", "size": 1.0 }, { "id": "820", "text": "Process", "data": { "Advisory_Notes": "Cost plan approved.", "KeyActivities": "Request approval for cost plan,\n Inform stakeholders about approved cost plan,\n Review feedback on cost plan,\n Adjust cost plan based on feedback", "Type": "Business Process", "Description": "This is a thorough review of the cost efficient planning approach by considering how it helps the organization to achieve its short term goals and how it supports the overall strategic workforce planning in the long term.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Management must approve both the planning approach and the cost plan before implementation.", "Outcome": "The plan becomes the operational guide for determining the right tasks or positions to be filled or closed within the short term.", "GUID": "d932a665-1e22-11ed-3781-0201b014c5b2", "name": "Approve cost plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.3402423810695685, "y": -0.8272425249169435, "z": 4.817027128840461 }, "color": "#66CCFF", "size": 1.0 }, { "id": "824", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Request work permit from candidate,\n Check work permit,\n Create confirmation letter of received work permit ,\n Issue confirmation letter to candidate,\n Decide on extending period for receiving work permit,\n Reject candidate in HR system,\n Inform stakeholders about rejecting candidate,\n Inform candidate about rejection", "Type": "Business Process", "Description": "When hiring immigrants, candidates must receive work permit to be eligible to work in the country. Receiving work permit is usually candidate-driven while the future employer is only supporting candidate. Once work permit is issued to the candidate, they must present it to the employer. ", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Requesting and receiving work permit from the candidate, checking the work permit and issuing confirmation letter of received work permit.", "Outcome": "Work permit received.", "GUID": "45c68140-464c-11ee-3781-0201b014c5b2", "name": "Receive work permit from candidate", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6384345422261655, "y": -0.823920265780731, "z": 5.7719608670572375 }, "color": "#66CCFF", "size": 1.0 }, { "id": "826", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with hiring manager,\n Select candidate(s) for further assessment,\n Reject candidate in HR system,\n Prepare relevant candidate information for selection,\n Update candidates status in HR system,\n Inform candidate about rejection", "Type": "Business Process", "Description": "This process covers selecting candidates for further assessment (test, interview, assessment center etc.) based on the information from candidates resume, pre-screening interview and other previous assessments.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Aligning with hiring manager and selecting candidates for further assessment.", "Outcome": "Candidates for further assessment selected.", "GUID": "5fdb3343-3db5-11ee-3781-0201b014c5b2", "name": "Select candidates for further assessment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.5561778688745439, "y": -0.8205980066445182, "z": 1.9211106626569356 }, "color": "#66CCFF", "size": 1.0 }, { "id": "828", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review job description,\n Request information for job requisition,\n Gather relevant information for job requisition,\n Create job requisition in HR system,\n Route job requisition for approval,\n Inform stakeholders about job requisition rejection", "Type": "Business Process", "Description": "This process is concerned with creating and approving job requisitions.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Reviewing job description, requesting and gathering all required information, creating job requisition in HR system and routing the job requisition for approval.", "Outcome": "Job requisition approved.", "GUID": "c4b8d258-f56c-11e8-2ddf-001bc640cd9b", "name": "Create and approve job requisition", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8492936153843152, "y": -0.8172757475083057, "z": 2.8772730761725485 }, "color": "#66CCFF", "size": 1.0 }, { "id": "830", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review remaining candidates (on hold) in HR system,\n Transfer candidate to other job requisition,\n Reject candidate in HR system,\n Withdraw job posting from career website,\n social media etc.", "Type": "Business Process", "Description": "This process is concerned with activities that must be undertaken to settle the job requisition before the new hire start date.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Reviewing remaining candidates and transferring them other job requisitions or directly rejecting them, and withdrawing the job posting from company career page, social media, job boards etc.", "Outcome": "Job requisition settled.", "GUID": "2cbb1f1d-4258-11ee-3781-0201b014c5b2", "name": "Settle remaining candidates and job postings", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.1523963974609504, "y": -0.8139534883720929, "z": 3.830402399633624 }, "color": "#66CCFF", "size": 1.0 }, { "id": "832", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Schedule job interview,\n Decide on interviewer(s),\n Prepare questions for job interview,\n Conduct job interview,\n Send meeting link to candidate,\n Book meeting room,\n Book parking spot (optional),\n Notify receptionist,\n Conduct debriefing with interviewer(s),\n Share results information with hiring manager", "Type": "Business Process", "Description": "Candidates must undergo interviews to determine if the candidate fits the profile which is intended for the job as per job description.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Scheduling job interview, preparing questions, and conducting job interview and debriefing meeting with interviewer.", "Outcome": "Job interview conducted.", "GUID": "53fa79c0-f56b-11e8-2ddf-001bc640cd9b", "name": "Conduct job interview", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.4654624047350564, "y": -0.8106312292358804, "z": 4.780420477354283 }, "color": "#66CCFF", "size": 1.0 }, { "id": "834", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Determine test assessment type,\n Prepare test assessment,\n Send test assessment to candidate,\n Evaluate test assessment results,\n Reject candidate in HR system,\n Share test results with hiring manager", "Type": "Business Process", "Description": "Candidates might be asked to complete a test assessment (i.e., language tests, psychometric tests, ability tests, personality questionnaires, situational judgemental tests etc.) that will help the employer better evaluate qualifications and / or skills of a candidate.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Determining what test assessment a candidate should take, preparing test assessment, sending test assessment to a candidate, receiving and evaluating results of the test assessment.", "Outcome": "Test assessment completed.", "GUID": "5fdb334a-3db5-11ee-3781-0201b014c5b2", "name": "Conduct test assessment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7884672833126583, "y": -0.8073089700996678, "z": 5.727249320268871 }, "color": "#66CCFF", "size": 1.0 }, { "id": "836", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Agree on assessment center organization,\n Decide on assessors and facilitator,\n Align with assessors and facilitator and divide roles,\n Invite candidates for assessment center,\n Prepare assessment center,\n Conduct assessment center,\n Conduct debriefing with assessors,\n Share assessment center results with hiring manager", "Type": "Business Process", "Description": "Assessment center as a selection method is characterized by a series of assessment methods that are conducted over a period of one or more days. The purpose of this method is to assess candidates multiple times on multiple traits at once. Usually, a group of candidates participate in one assessment centers at once.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Aligning with hiring team on assessment center organization, deciding on assessors, inviting candidates for assessment center, technical preparation (i.e., room booking, organizing catering, checking equipment etc.), conducting assessment center an debriefing meeting with hiring team.", "Outcome": "Assessment center organized.", "GUID": "c3dcd115-40de-11ee-3781-0201b014c5b2", "name": "Organize and execute assessment center", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.6061103248198572, "y": -0.8039867109634551, "z": 1.9059460312786318 }, "color": "#66CCFF", "size": 1.0 }, { "id": "838", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Schedule pre-screening interview,\n Prepare questions for pre-screening interview,\n Conduct pre-screening interview with candidate,\n Summarize information from pre-screening interview,\n Share pre-screening summary with hiring manager", "Type": "Business Process", "Description": "Candidate pre-screening interview is usually conducted over a phone with a purpose to check candidates qualification stated in resume, expected salary and availability to start. Additionally, another candidate checks might be required (i.e., eligibility to work in the country, background check, criminal check, etc.).", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Scheduling and conducting pre-screening interview, summarizing information from the pre-screening interview and sharing it with hiring manager.", "Outcome": "Pre-screening interview completed.", "GUID": "5fdb0c30-3db5-11ee-3781-0201b014c5b2", "name": "Conduct candidate pre-screening interview", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.9240725729128159, "y": -0.8006644518272426, "z": 2.8541355749141086 }, "color": "#66CCFF", "size": 1.0 }, { "id": "840", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review job requisition,\n Prepare hiring strategy proposal,\n Organize strategic alignment with hiring manager,\n Document hiring strategy,\n Share hiring strategy with stakeholders,\n Decide on hiring strategy", "Type": "Business Process", "Description": "This process describes strategic alignment with hiring manager (HM) and the hiring team. The purpose of this meeting is to decide on recruitment strategy for the job requisition (i.e., candidate attraction and selection, communication infrastructure between HM and the hiring team etc.).", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Reviewing job requisition, preparing suggested hiring strategy, organizing strategic alignment and sharing agreed hiring strategy with stakeholders.", "Outcome": "Hiring strategy developed.", "GUID": "639863b9-f56a-11e8-2ddf-001bc640cd9b", "name": "Conduct strategic alignment meeting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2519393236415164, "y": -0.7973421926910298, "z": 3.799032499192396 }, "color": "#66CCFF", "size": 1.0 }, { "id": "842", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create employment contract,\n Review job offer,\n Get companys signature of employment contract,\n Send employment contract to candidate,\n Receive signed employment contract,\n Copy signed contract,\n Upload signed contract to HR system,\n Store signed contract physically", "Type": "Business Process", "Description": "An employment contract is an agreement between the employer and employee setting out the employees employment rights, responsibilities and duties. It forms the legal relationship between the employer and employee.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Creating employment contract, requesting HR managers signature or other legally eligible person, and sending the contract to the employee.", "Outcome": "Employment contract signed.", "GUID": "98840da3-c4d5-11e9-0cfc-001bc641ce4f", "name": "Create and sign employment contract", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5896847356597017, "y": -0.7940199335548173, "z": 4.740559296244542 }, "color": "#66CCFF", "size": 1.0 }, { "id": "844", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review candidates profiles,\n Align with hiring manager,\n Update candidate status in HR system,\n Keep candidate on hold in case selected candidate reject job offer", "Type": "Business Process", "Description": "This process is concerned with final selection of a candidate for the job offer based on the results of all previous selection methods.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Reviewing candidates profiles and results from selection methods, aligning with hiring manager, selecting a candidate for job offer.", "Outcome": "Candidate for job offer selected.", "GUID": "6ef9bb10-4249-11ee-3781-0201b014c5b2", "name": "Select candidate for job offer", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9372824286286758, "y": -0.7906976744186047, "z": 5.678638638945657 }, "color": "#66CCFF", "size": 1.0 }, { "id": "846", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check status of all candidates in HR system,\n Confirm all candidates are in final status in HR system,\n Close job requisition ,\n Update candidate status in HR system", "Type": "Business Process", "Description": "This process describes closing the job requisition after it is filled. There are also other reasons why a job requisition can be closed, such as incapability of finding a suitable candidate, position no longer needed etc.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Checking that all candidates are disposed and closing the job requisition in HR system.", "Outcome": "Job requisition closed.", "GUID": "2cbb1f29-4258-11ee-3781-0201b014c5b2", "name": "Close job requisition", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.6556301384010488, "y": -0.787375415282392, "z": 1.8894838241224035 }, "color": "#66CCFF", "size": 1.0 }, { "id": "848", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review list of existing job descriptions,\n Align with hiring manager,\n Create job description draft,\n Request feedback on job description draft from hiring manager,\n Review feedback on job description,\n Update job description", "Type": "Business Process", "Description": "This process is concerned with creating formal job description that will consist of job title, job purpose, roles and responsibilities, required and preferred qualifications, and working conditions.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Reviewing a list of existing job descriptions, aligning with hiring manager to create a job description, and creating the job description.", "Outcome": "Job description created.", "GUID": "639863b7-f56a-11e8-2ddf-001bc640cd9b", "name": "Create job description", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.9982224180908215, "y": -0.7840531561461794, "z": 2.8290549665958973 }, "color": "#66CCFF", "size": 1.0 }, { "id": "850", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check candidate resumes against criteria,\n Determine eligibility criteria to be considered for pre-screening,\n Update candidate status in HR system,\n Reject candidate in HR system,\n Inform candidate about rejection", "Type": "Business Process", "Description": "Candidates are shortlisted based on predetermined criteria and a profile which must fit the job description.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Screening resumes based on minimum qualifications, screening resumes based on preferred qualifications and creating shortlist.", "Outcome": "Candidates for pre-screening selected.", "GUID": "639863c6-f56a-11e8-2ddf-001bc640cd9b", "name": "Select candidates for pre-screening interview", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.3506299244597015, "y": -0.7807308970099667, "z": 3.765076202038145 }, "color": "#66CCFF", "size": 1.0 }, { "id": "852", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review approved job offer in HR system,\n Prepare formal job offer letter,\n Send job offer letter to candidate,\n Update candidate status in HR system,\n Inform hiring manager about job offer rejection,\n Reject candidate in HR system,\n Inform hiring manager about job offer acceptance,\n Inform candidate about rejection", "Type": "Business Process", "Description": "Based on the approved job offer in HR system, a formal job offer letter is prepared and send to the candidate. Job offer letter typically includes job title, salary, start date, benefits etc.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Reviewing approved job offer in HR system, preparing formal job offer letter, sending it to the candidate and receiving response from the candidate. ", "Outcome": "Job offer accepted.", "GUID": "53fa79c2-f56b-11e8-2ddf-001bc640cd9b", "name": "Offer job to candidate", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7128248027774635, "y": -0.7774086378737541, "z": 4.697470723164791 }, "color": "#66CCFF", "size": 1.0 }, { "id": "854", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review job description,\n Determine search criteria,\n Decide on search tool (i.e.,\n LinkedIn),\n Initiate candidate search,\n Contact potential candidates,\n Get candidate apply for job requisition,\n Mark candidate disinterest in job requisition", "Type": "Business Process", "Description": "This process describes the search, identifying and contacting potential candidates for the job requisition. Candidate sourcing is usually conducted via search engine or social media based on pre-defined search criteria.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Reviewing job description, determining search criteria, searching and contacting potential candidates.", "Outcome": "Candidates identified.", "GUID": "b8af5675-f569-11e8-2ddf-001bc640cd9b", "name": "Source candidates", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.0847786642205297, "y": -0.7740863787375416, "z": 5.626161917436332 }, "color": "#66CCFF", "size": 1.0 }, { "id": "856", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Determine employee start date,\n Create job offer in HR system,\n Gather employee compensation information,\n Determine job offer approver(s),\n Gather information on probation period,\n Gather information on special working conditions,\n Route job offer for approval,\n Review feedback on rejected job offer,\n Update job offer", "Type": "Business Process", "Description": "After selecting a candidate for hiring, a job offer must be created in HR system and approved before sending it out to the candidate.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Capturing relevant information (i.e., start date, compensation, special working conditions, probation period, approvers etc.) for job offer, creating job offer in HR system, routing the job offer for approval, and receiving job offer approval.", "Outcome": "Job offer approved.", "GUID": "2cbb1f04-4258-11ee-3781-0201b014c5b2", "name": "Request and receive job offer approval", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7047035963284574, "y": -0.7707641196013288, "z": 1.8717352487255612 }, "color": "#66CCFF", "size": 1.0 }, { "id": "858", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Generate employee ID and email account,\n Request and prepare employee equipment,\n Assign buddy to new hire,\n Plan onboarding training sessions,\n Organize welcome day for new hire,\n Prepare other documents for new hires signature", "Type": "Business Process", "Description": "Pre-onboarding covers all activities that are necessary to undertake before the start day of the new hire.", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Generating employee ID and email account, preparing employee equipment (laptop, mobile phone, badge etc.), assigning buddy to new hire, planning onboarding training sessions (code of conduct, cyber security, health and safety etc.), organizing welcome day for new hire and preparing other relevant documents for employee signature.", "Outcome": "Pre-onboarding completed.", "GUID": "2cbb1f23-4258-11ee-3781-0201b014c5b2", "name": "Conduct pre-onboarding", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.0716926694033981, "y": -0.7674418604651163, "z": 2.802048326197644 }, "color": "#66CCFF", "size": 1.0 }, { "id": "860", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review hiring strategy,\n Decide on where to post the job,\n Post to company career website,\n Prepare post for commercial job advertising,\n Post job to social media,\n Post job to job boards,\n Post job to internal career site,\n Check job posting,\n Share job opportunity with colleagues", "Type": "Business Process", "Description": "This process describes posting the job requisition both internally and externally (i.e., company career website, external job boards, social media etc.).", "Process_Group": "Recruiting, Sourcing and Selection", "hasAssignment": true, "Scope": "Reviewing job hiring strategy, posting job requisition internally and / or externally, and checking job requisition posting.", "Outcome": "Job requisition posted.", "GUID": "4a819370-3da8-11ee-3781-0201b014c5b2", "name": "Post job requisition", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.448401010954733, "y": -0.7641196013289036, "z": 3.728556625755509 }, "color": "#66CCFF", "size": 1.0 }, { "id": "864", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review workforce gap risks,\n Review workforce gap risk responses,\n Identify cost drivers,\n Evaluate costs of risk responses,\n Calculate cost impact of risk responses,\n Share results with stakeholders", "Type": "Business Process", "Description": "This process is concerned with cost analysis of risk responses to workforce gaps to determine the impact of such responses on the company.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Reviewing workforce gap risks and risk responses, identifying cost drivers, evaluating costs of risk responses, and calculating cost impact of risk responses.", "Outcome": "Cost impact of risk responses calculated.", "GUID": "4dea1b7d-3819-11ee-3781-0201b014c5b2", "name": "Calculate cost impact of risk responses to workforce gaps", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8347987718318812, "y": -0.760797342192691, "z": 4.651184092990109 }, "color": "#66CCFF", "size": 1.0 }, { "id": "866", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Monitor workforce gap,\n Update risk responses,\n Calculate cost impact of new risk responses,\n Evaluate cost impact of contemporary risk responses,\n Inform stakeholders about workforce gap progress,\n Update cost impact of risk responses", "Type": "Business Process", "Description": "This process is concerned with monitoring workforce gap and related risk responses.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Monitoring workforce gap, updating risk responses and cost impact of risk responses.", "Outcome": "Strategic workforce plan monitored.", "GUID": "6ee05f10-383e-11ee-3781-0201b014c5b2", "name": "Monitor strategic workforce plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.23085557405361, "y": -0.7574750830564785, "z": 5.569854882105451 }, "color": "#66CCFF", "size": 1.0 }, { "id": "868", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with stakeholders,\n Define strategic workforce objectives,\n Request approval for strategic workforce objectives,\n Share strategic workforce objectives with stakeholders,\n Review feedback on strategic workforce objectives,\n Update strategic workforce objectives", "Type": "Business Process", "Description": "This process is concerned with definition of strategic workforce objectives based on business strategy.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Aligning with stakeholders to define strategic workforce objectives, defining and approving strategic workforce objectives, and communicating strategic workforce objectives to relevant stakeholders.", "Outcome": "Strategic workforce objectives defined.", "GUID": "4dea1b73-3819-11ee-3781-0201b014c5b2", "name": "Define strategic workforce objectives", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.753297289193159, "y": -0.7541528239202657, "z": 1.8527123883901242 }, "color": "#66CCFF", "size": 1.0 }, { "id": "870", "text": "Process", "data": { "Advisory_Notes": "The human resource department should work with various unit heads to determine the right responses. ", "KeyActivities": "Review workforce gap,\n Determine risk responses to close workforce gap,\n Request approval for risk responses,\n Review feedback,\n Update risk responses,\n Share risk responses with stakeholders", "Type": "Business Process", "Description": "This process refers to the development of strategies that help to mitigate the identified risks and close the workforce gaps.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "To close the workforce gaps, determine the cost effective strategic approaches (i.e., risk responses). The approaches may include external and internal recruitments of FTEs or contingent staff, organising training programs or conducting employee transfers. The approaches selected should depend on whether the organization will need to expand, contract or restructure.", "Outcome": "Risk responses determined.", "GUID": "25142d70-1890-11ed-4ad5-0201b014c5b2", "name": "Determine risk responses for workforce gaps", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.1444333080058688, "y": -0.7508305647840532, "z": 2.77313403994952 }, "color": "#66CCFF", "size": 1.0 }, { "id": "872", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review strategic workforce objectives,\n Define required competencies,\n Define required positions,\n Define need timeframe of positions and competencies,\n Define size of workforce needed,\n Derive cost impact of planned workforce demand,\n Consolidate workforce demand plan,\n Request approval of workforce demand plan,\n Share workforce demand plan with stakeholders,\n Review feedback on workforce demand plan,\n Update workforce demand plan", "Type": "Business Process", "Description": "This process is to determine the quality and size of the workforce composition needed to achieve future objectives. Demand planning can be along different dimensions such as organizational unit, location, position and job classification. ", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Based on the strategic workforce objectives, define required skills, positions, the timeframe, and the size of workforce needed. Derive the cost impact, and take into account regulatory, labour, and economic market conditions.", "Outcome": "Workforce demand planned.", "GUID": "d0e939f2-b58b-11ec-4ad5-0201b014c5b2", "name": "Perform workforce demand planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5451860201749128, "y": -0.7475083056478404, "z": 3.6894986330199413 }, "color": "#66CCFF", "size": 1.0 }, { "id": "874", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review strategic workforce objectives,\n Analyze organizational structure,\n Analyze positions,\n Analyze talent profiles,\n Analyze workloads,\n Analyze employee attrition rate,\n Analyze employees view on job security,\n Analyze employee job satisfaction,\n Analyze contractual differences,\n Analyze demographic differences,\n Consolidate results,\n Prepare report,\n Share report with stakeholders", "Type": "Business Process", "Description": "The goal of this process is to determine if the organization currently has the right people with the right skills in the right roles to help achieve the strategic workforce and business objectives.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Assess the structure of the organization by gathering and analysing employees data such as talent profiles, workloads, attrition rates, health, employees views on job security, satisfaction, and intention to leave, contractual differences or even demographic characteristics. ", "Outcome": "Current workforce analyzed.", "GUID": "d0e939f4-b58b-11ec-4ad5-0201b014c5b2", "name": "Analyze current workforce supply", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9555236024507794, "y": -0.7441860465116279, "z": 4.6017309178457975 }, "color": "#66CCFF", "size": 1.0 }, { "id": "876", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Compare demand plan and current workforce analysis,\n Identify workforce demand-supply gap,\n Identify workforce gap risks,\n Evaluate workforce gap risks,\n Prepare report,\n Share report with relevant stakeholders", "Type": "Business Process", "Description": "The purpose of this process is to determine if the organization has a workforce surplus or shortage.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Compare the results from demand planning and current workforce analysis to identify possible risks and workforce surplus or shortages.", "Outcome": "Workforce gap and risks analyzed.", "GUID": "d0e939f7-b58b-11ec-4ad5-0201b014c5b2", "name": "Conduct workforce gap analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.3754137083760325, "y": -0.7408637873754154, "z": 5.509755867010735 }, "color": "#66CCFF", "size": 1.0 }, { "id": "878", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with business leaders on business goals and strategy,\n Identify mid-term business challenges,\n Identify short-term business challenges,\n Analyze challenges,\n Evaluate challenges in relation to current workforce,\n Prepare report", "Type": "Business Process", "Description": "From the HR perspective, reviewing business goals and strategy represents the first step in majority of HR activities. It is a necessary step that must be taken to ensure critical alignment between business and HR.", "Process_Group": "HR Planning, Policies and Strategies", "hasAssignment": true, "Scope": "Aligning with business leaders on business goals and strategy, identifying current and future challenges related to human resources (mid-term and short-term), analyzing challenges and preparing report.", "Outcome": "Business goals and strategy reviewed.", "GUID": "79ad46b0-329c-11ee-3781-0201b014c5b2", "name": "Review business goals and strategy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8013781342122285, "y": -0.7375415282392026, "z": 1.8324281939564582 }, "color": "#66CCFF", "size": 1.0 }, { "id": "883", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare list of candidates for employee promotion,\n Review essential employee promotion criteria,\n Compare candidates against essential criteria,\n Select candidate(s) meeting essential criteria,\n Reject candidates employee promotion request,\n Inform candidate about request rejection", "Type": "Business Process", "Description": "This process describes selecting relevant candidate(s), from the pool of potential candidates, to be evaluated for employee promotion.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Reviewing pre-defined criteria and selecting relevant candidate(s) meeting the essential criteria for employee promotion.", "Outcome": "Relevant candidate(s) for employee promotion selected.", "GUID": "d015e4dc-1712-11ee-3781-0201b014c5b2", "name": "Select relevant candidates for employee promotion", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2163948117768442, "y": -0.7342192691029901, "z": 2.742331792814716 }, "color": "#66CCFF", "size": 1.0 }, { "id": "885", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Send employee promotion proposal to candidate,\n Get candidate acceptance of employee promotion proposal,\n Report employee refusal of promotion proposal,\n Update employee promotion proposal,\n Review candidate feedback on promotion proposal,\n Analyze requested changes,\n Inform candidate about rejection of requested changes,\n Review other evaluated candidate(s)", "Type": "Business Process", "Description": "This process describes informing stakeholders about decision on employee promotion and related administrative activities.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Informing candidate(s) about the decision, getting candidates acceptance of the positive decision, informing relevant stakeholders and updating relevant systems and documents.", "Outcome": "Employee promotion completed.", "GUID": "d015e4e0-1712-11ee-3781-0201b014c5b2", "name": "Implement employee promotion decision", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6409190604939483, "y": -0.7308970099667773, "z": 3.647928814671095 }, "color": "#66CCFF", "size": 1.0 }, { "id": "887", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect application(s) for employee promotion ,\n Check application(s) for completeness,\n Store application(s) for employee promotion,\n Request additional information for application,\n Close application period for employee promotion,\n Receive additional information for application,\n Dismiss application for incompleteness,\n Inform candidate about application dismissal", "Type": "Business Process", "Description": "This process describes collecting employee application(s) for employee promotion opportunity that has been announced to the company.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Collecting, checking and storing employee application(s) for employee promotion.", "Outcome": "Application period for employee promotion closed.", "GUID": "967c53ab-208a-11ee-3781-0201b014c5b2", "name": "Collect applications for employee promotion", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.074917104680492, "y": -0.7275747508305648, "z": 4.549144865653799 }, "color": "#66CCFF", "size": 1.0 }, { "id": "889", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Receive employee promotion request,\n Assess relevance of employee promotion request,\n Approve relevance of employee promotion request,\n Reject relevance of employee promotion request,\n Inform candidate about request rejection", "Type": "Business Process", "Description": "The process is concerned with assessing the relevance of the employee promotion request.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Assessing the relevance of employee promotion request and approving/rejecting it.", "Outcome": "Relevance of employee promotion request approved/rejected.", "GUID": "d015e4d5-1712-11ee-3781-0201b014c5b2", "name": "Assess employee promotion request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.5183546514244366, "y": -0.7242524916943522, "z": 5.445905787805083 }, "color": "#66CCFF", "size": 1.0 }, { "id": "891", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect relevant information and documents,\n Write employee promotion request letter,\n Submit employee promotion request", "Type": "Business Process", "Description": "This process involves employees or their managers requesting employee promotion.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Collecting relevant information/documents, writing promotion request letter, and submitting promotion request.", "Outcome": "Employee promotion requested.", "GUID": "d01596b0-1712-11ee-3781-0201b014c5b2", "name": "Request employee promotion", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8489133977516299, "y": -0.7209302325581395, "z": 1.8108964749862935 }, "color": "#66CCFF", "size": 1.0 }, { "id": "893", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Compare candidates for employee promotion,\n Identify suitable candidate(s) to be promoted,\n Define conditions for employee promotion,\n Approve employee promotion proposal,\n Report justification for not identifying suitable candidate(s),\n Inform candidate about request rejection,\n Create employee promotion proposal,\n Review and adjust employee promotion proposal,\n Identify need for employee hiring", "Type": "Business Process", "Description": "This decision-making process describes which candidate(s) for employee promotion will be promoted.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Analyzing information from candidate(s) evaluation process and making decision on whom to promote.", "Outcome": "Employee promotion proposal approved.", "GUID": "d015e4de-1712-11ee-3781-0201b014c5b2", "name": "Decide on employee promotion", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2875281890330854, "y": -0.717607973421927, "z": 2.709662555087844 }, "color": "#66CCFF", "size": 1.0 }, { "id": "895", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review job specification of requested position,\n Determine essential and additional criteria for promotion,\n Determine method(s) for employee promotion evaluation,\n Approve criteria and method(s)", "Type": "Business Process", "Description": "This process describes determining essential (i.e., seniority, education etc.) and additional (i.e., performance, motivation, skills etc.) criteria against which candidate(s) for employee promotion will be judged, as well as determining appropriate evaluation method(s) to ensure that the most suitable candidate(s) for promotion is/are chosen. ", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Based on job analysis, determine essential and additional criteria and appropriate method(s) for evaluating candidate(s) for employee promotion.", "Outcome": "Employee promotion criteria and evaluation method(s) approved.", "GUID": "d015e4d7-1712-11ee-3781-0201b014c5b2", "name": "Determine employee promotion criteria and method(s)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7355349564702323, "y": -0.7142857142857142, "z": 3.6038754716096766 }, "color": "#66CCFF", "size": 1.0 }, { "id": "897", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Plan employee promotion opportunity announcement,\n Provide announcement plan to stakeholders,\n Prepare key information for announcement,\n Get relevant information for announcement planning,\n Vizualize information for announcement,\n Approve final announcement material ,\n Approve announcement plan,\n Release employee promotion opportunity announcement,\n Set up requesting procedure,\n tools etc.,\n Review and adjust announcement plan", "Type": "Business Process", "Description": "This process describes informing employees about an employee promotion opportunity (if the promotion is driven by organizational need to fill a job vacancy). The purpose of this process is to get relevant candidate(s) for employee promotion.", "Process_Group": "Employee communication", "hasAssignment": true, "Scope": "Planning employee promotion opportunity announcement, preparation and release of the announcement. ", "Outcome": "Employee promotion opportunity announced.", "GUID": "d015e4da-1712-11ee-3781-0201b014c5b2", "name": "Announce employee promotion opportunity", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.192897994941108, "y": -0.7109634551495017, "z": 4.493461737211442 }, "color": "#66CCFF", "size": 1.0 }, { "id": "899", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Plan evaluation interview with candidate,\n Execute evaluation interview with candidate,\n Review candidates employee promotion request,\n Review candidates performance appraisal data,\n Create candidate evaluation report,\n Evaluate candidate for employee promotion", "Type": "Business Process", "Description": "This process is concerned with evaluating candidate(s) for employee promotion. The evaluation is based on employee seniority, performance appraisal, 360 degree feedback etc.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Executing interview with candidate(s) for employee promotion and analyzing the data obtained from performance appraisal, 360 degree feedback and other sources.", "Outcome": "Candidate(s) for employee promotion evaluated.", "GUID": "d015e4d2-1712-11ee-3781-0201b014c5b2", "name": "Evaluate relevant candidates for employee promotion", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.659581088425823, "y": -0.7076411960132891, "z": 5.378348113881038 }, "color": "#66CCFF", "size": 1.0 }, { "id": "903", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with successors on their succession plan,\n Share employee succession plan with other stakeholders,\n Initiate employee development,\n Initiate executive mentoring", "Type": "Business Process", "Description": "This process ensures that all stakeholder are informed about the employee succession plan and required follow-up actions are triggered.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Aligning with successors on their succession plan, informing relevant stakeholders about employee succession plan, and implementing employee succession plan or initiating learning and development activities and executive mentoring (if needed).", "Outcome": "Employee learning initiated. / Executive mentoring initiated. / Employee transition initiated.", "GUID": "51da3430-b8ef-11e9-0cfc-001bc641ce4f", "name": "Communicate and implement succession plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8958707176114097, "y": -0.7043189368770764, "z": 1.7881318903611159 }, "color": "#66CCFF", "size": 1.0 }, { "id": "905", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Analyze competencies of high potential employees,\n Analyze competencies needed for succession ,\n Define preparation period to gain competencies for succession,\n Compile succession plan,\n Prepare employee development plan,\n Prepare executive mentoring plan", "Type": "Business Process", "Description": "This process is concerned with preparation of succession plan that describes when successors should be prepared for succession and what preparation activities (i.e., learning and development and executive coaching) are needed.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Analyzing current competencies of successors and required competencies of critical positions they are planned to fill in the future, defining preparation period needed for successors to be prepared for succession, preparing learning and development (L&D) and executive mentoring plan for successors.", "Outcome": "Employee succession plan prepared.", "GUID": "51da342e-b8ef-11e9-0cfc-001bc641ce4f", "name": "Prepare succession plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.3577850118832386, "y": -0.7009966777408638, "z": 2.6751485681182707 }, "color": "#66CCFF", "size": 1.0 }, { "id": "907", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify critical positions for business strategy,\n Analyze impact of critical positions on business strategy,\n Categorize critical positions based on impact,\n Create list of critical positions in HR system", "Type": "Business Process", "Description": "This process is concerned with identifying positions that have the greatest impact on companys future business goals, company performance, and what roles are also the most difficult to replace.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Identifying critical positions that will help the company achieve the business strategy, analyzing impact of critical positions on companys business goals, and creating a list of critical positions in HR system.", "Outcome": "Critical positions identified.", "GUID": "51da3432-b8ef-11e9-0cfc-001bc641ce4f", "name": "Identify critical positions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.828969293218554, "y": -0.6976744186046511, "z": 3.557368595530076 }, "color": "#66CCFF", "size": 1.0 }, { "id": "909", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review progress of succession plan,\n Update succession plan,\n Approve updated succession plan,\n Report succession plan progress", "Type": "Business Process", "Description": "This process is concerned with monitoring succession plan to ensure that successors have been developed according to the plan. Additionally, if any changes in succession plan are needed, the process is concerned with making sure they are implemented.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Reviewing progress of succession plan, identifying deviations and implementing changes needed.", "Outcome": "Succession plan monitored.", "GUID": "742ab898-32aa-11ee-3781-0201b014c5b2", "name": "Monitor succession plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.309385951364671, "y": -0.6943521594684385, "z": 4.434719441818106 }, "color": "#66CCFF", "size": 1.0 }, { "id": "911", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review list of critical positions and respective competencies,\n Align with HRBPs to identify high potential employees,\n Review performance appraisal of identified employees,\n Set high potential employees as successors in HR system,\n Report inability to identify high potential employees,\n Identify need for employee hiring", "Type": "Business Process", "Description": "This process is concerned with identifying employees who have potential to replace current employees occupying critical positions. ", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Aligning with HR Business Partners (HRBPs) on identifying high potential employees, reviewing employees performance appraisal, identifying high potential employees, setting up high potential employees as successors in HR system.", "Outcome": "High potential employees identified.", "GUID": "79ad6dc9-329c-11ee-3781-0201b014c5b2", "name": "Identify high potential employees", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.798996871849863, "y": -0.691029900332226, "z": 5.30712883877664 }, "color": "#66CCFF", "size": 1.0 }, { "id": "913", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review list of critical positions,\n Analyze job specification of critical positions,\n Analyze job description of critical positions,\n Identify critical competencies for critical positions,\n Update competencies for critical positions in HR system", "Type": "Business Process", "Description": "After critical positions have been identified, it is necessary to identify competencies (i.e., knowledge, skills, abilities and other characteristics) of these critical positions. Such competencies represent critical success factors for each position.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Reviewing list of critical positions, analyzing job description and specification of critical positions, identifying critical competencies for critical positions.", "Outcome": "Competencies for critical positions identified.", "GUID": "79ad6dc4-329c-11ee-3781-0201b014c5b2", "name": "Identify competencies for critical positions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.9422181250580115, "y": -0.6877076411960132, "z": 1.7641499383023445 }, "color": "#66CCFF", "size": 1.0 }, { "id": "917", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Gather required information,\n Prepare job (re)evaluation request,\n Submit job (re)evaluation request", "Type": "Business Process", "Description": "The process deals with requesting job (re)evaluation for a particular position with the aim of increasing pay rate or redistribution in tasks/duties/accountability. ", "hasAssignment": true, "Scope": "Submit the job (re)evaluation request for a specific position, enter reason and suggest a potential outcome (change in pay rate, redistribution of tasks/duties/accountability etc.).", "Process_Group": "Employee Relations", "Outcome": "Job (re)evaluation requested.", "GUID": "593dff40-13f3-11ee-3781-0201b014c5b2", "name": "Request job (re)evaluation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.4271174491977394, "y": -0.6843853820598007, "z": 2.63881332916812 }, "color": "#66CCFF", "size": 1.0 }, { "id": "919", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review job (re)evaluation request,\n Approve to proceed with job (re)evaluation,\n Reject to proceed with job (re)evaluation,\n Inform stakeholders about job (re)evaluation termination", "Type": "Business Process", "Description": "The process is concerned with assessing the necessity of job (re)evaluation request for a particular position.", "Process_Group": "Employee Relations", "hasAssignment": true, "Scope": "Assessing the relevance and necessity of job (re)evaluation for a particular position and approving/rejecting it.", "Outcome": "Job (re)evaluation process is initiated/terminated.", "GUID": "593e2652-13f3-11ee-3781-0201b014c5b2", "name": "Assess job (re)evaluation request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.921158460264009, "y": -0.681063122923588, "z": 3.508439848501898 }, "color": "#66CCFF", "size": 1.0 }, { "id": "921", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect documentation/information,\n Execute job (re)evaluation interview,\n Decide on job (re)evaluation,\n Inform stakeholders about no change in grade,\n Inform stakeholders about change in grade,\n Update data in relevant documents and systems,\n Get employee signature on updated documents,\n Inform stakeholders about rejection of change in grade", "Type": "Business Process", "Description": "The process covers execution of the job (re)evaluation process from collecting relevant information/documentation, through evaluation, to implementation of final decision.", "hasAssignment": true, "Scope": "Collecting and analyzing relevant information, proposing and implementing solution (change in pay rate, tasks, duties, accountability etc.).", "Process_Group": "Employee Relations", "Outcome": "Change of grade implemented/rejected.", "GUID": "593e2654-13f3-11ee-3781-0201b014c5b2", "name": "Perform job (re)evaluation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.424301668478625, "y": -0.6777408637873754, "z": 4.372957971466425 }, "color": "#66CCFF", "size": 1.0 }, { "id": "925", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check candidates availability for global assignment,\n Check candidates conditions for global assignment,\n Review interview report,\n Determine conditions for global assignment,\n Create candidate proposal for global assignment,\n Send proposal for global assignment for approval,\n Report inability to select suitable candidate(s),\n Identify need for employee hiring,\n Receive feedback on rejection of proposal,\n Incorporate desired changes in proposal", "Type": "Business Process", "Description": "To ensure the goals of global assignment are met, the most suitable candidate for global assignment must be selected.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Reviewing candidate profiles and conditions for global assignment, selecting the most suitable candidate and approving the selection.", "Outcome": "Candidate for global assignment selected.", "GUID": "5dbbe489-2609-11ee-3781-0201b014c5b2", "name": "Select candidate and approve proposal for global assignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9365070868665115, "y": -0.6744186046511629, "z": 5.232296448862846 }, "color": "#66CCFF", "size": 1.0 }, { "id": "927", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Schedule pre-assignment briefing meeting with employee,\n Conduct pre-assignment briefing meeting with employee,\n Prepare pre-assignment training for employee,\n Inform Corporate Security,\n Arrange security training,\n Arrange cross-cultural training,\n Arrange language training,\n Arrange further training", "Type": "Business Process", "Description": "Global assignments usually require some training (cross-cultural, language etc.,) that should help the employee to prepare for global assignment and ensure smooth adaptation process.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Conducting pre-assignment briefing meeting, conducting relevant trainings and related activities.", "Outcome": "Employee prepared for global assignment.", "GUID": "6cd53725-279f-11ee-3781-0201b014c5b2", "name": "Initiate employee preparation for global assignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.9879240665887206, "y": -0.6710963455149501, "z": 1.7389669458200767 }, "color": "#66CCFF", "size": 1.0 }, { "id": "929", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update global assignment information in HR system,\n Update organizational structure,\n Review and maintain Home Country employment data,\n Review and maintain Host Country employment data,\n Manage master data for payroll,\n Arrange travel to Host Country,\n Create employee profile in Host Country,\n Set employee status as \"Dormant\" in Home Country,\n Set employee status as \"Active\" in Host Country,\n Start employee global assignment", "Type": "Business Process", "Description": "This process refers to administrative processing of employees global assignment from both the Home Country and Host Country perspective right before the global assignment starts. ", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Updating global assignment and related information to HR system, updating organizational structure, managing travel to Host Country, managing payroll data and creating another profile for employee in the Host Country and suspending the profile in Home Country.", "Outcome": "Global assignment started.", "GUID": "c0d8a917-2614-11ee-3781-0201b014c5b2", "name": "Start global assignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.4954782991724405, "y": -0.6677740863787376, "z": 2.600681575415242 }, "color": "#66CCFF", "size": 1.0 }, { "id": "931", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Inform line manager about expected end date of global assignment,\n Discuss end of global assignment,\n Schedule regular meetings with expatriate employee,\n Conduct regular meetings with expatriate employee,\n Update assignment-specific data", "Type": "Business Process", "Description": "This process involves administrative monitoring of global assignment after it has started. ", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Meeting with expatriate employee regularly, updating assignment-specific data, informing expatriate employee and their manager about the scheduled end of global assignment, discussing potential extension of global assignment or terminating global assignment.", "Outcome": "Extension of global assignment desired/End of global assignment initiated.", "GUID": "fa423123-1223-11ec-2c3e-001bc641ce4f", "name": "Monitor global assignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.01203969484827, "y": -0.6644518272425248, "z": 3.457122541414302 }, "color": "#66CCFF", "size": 1.0 }, { "id": "933", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Request candidate suggestion from HRBPs and managers,\n Review potential candidates for global assignment,\n Identify eligible candidates,\n Report inability to identify potential candidates,\n Identify need for employee hiring", "Type": "Business Process", "Description": "Once the need for global assignment is identified and approved, suitable candidates must be identified. ", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Requesting recommendations for global assignment candidates from Human Resource Business Partners (HRBP) and/or managers, reviewing recommendations and identifying suitable candidate(s).", "Outcome": "Candidate(s) for global assignment identified/need for employee hiring identified.", "GUID": "5dbbe478-2609-11ee-3781-0201b014c5b2", "name": "Identify candidates for global assignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.537566911197305, "y": -0.6611295681063123, "z": 4.308219373615573 }, "color": "#66CCFF", "size": 1.0 }, { "id": "935", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Inform stakeholders about end of global assignment,\n Prepare end of global assignment form,\n Check end of global assignment form,\n Process end of global assignment in HR system,\n Schedule debriefing meeting with expatriate employee,\n Conduct debriefing meeting with expatriate employee,\n Organize end of global assignment logistics,\n Arrange travel to Home Country,\n Calculate/pay allowances if applicable,\n Update organizational structure,\n Set employee status to \"Terminated\" in Host Country,\n Set employee status to \"Active\" in Home Country,\n Provide employee support to adapt to Home Country,\n Create global assignment report,\n Share global assignment report with stakeholder", "Type": "Business Process", "Description": "This process covers administrative activities related to the end of global assignment.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Arranging employee return to Home Country, debriefing with employee, reporting and closing global assignment in an HR system.", "Outcome": "Global assignment ended.", "GUID": "c5cc7902-2638-11ee-3781-0201b014c5b2", "name": "End global assignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.072018115964415, "y": -0.6578073089700998, "z": 5.153901890333813 }, "color": "#66CCFF", "size": 1.0 }, { "id": "937", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Initiate request for immigration application,\n Prepare documents for immigration application,\n Receive documents from Home / Sending Country,\n Receive documents from Host / Receiving Country,\n Process immigration application,\n End global assignment / employee transfer procedure,\n Inform all relevant stakeholders,\n Upload work permit in HR system", "Type": "Business Process", "Description": "This process describes the efforts needed to receive employee work permit in Host/Receiving Country.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Initiating immigration application request, processing immigration application and receiving work permit.", "Outcome": "Work permit received. Global mobility dismissed.", "GUID": "fa42311c-1223-11ec-2c3e-001bc641ce4f", "name": "Receive work permit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.0329574254134155, "y": -0.654485049833887, "z": 1.7126000575975957 }, "color": "#66CCFF", "size": 1.0 }, { "id": "939", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Inform on intention to extend global assignment,\n Advice on feasibility and possibility,\n Prepare global assignment extension form,\n Request global assignment extension approval,\n Inform about denied extension of global assignment,\n Inform about approved extension of global assignment,\n Process extension of global assignment in HR system,\n Process extension of global assignment with DSP ", "Type": "Business Process", "Description": "If requested, employee is asked to extend their global assignment.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Informing employee about the intention to extend the global assignment, analyzing the feasibility of extension, approving and processing global assignment extension.", "Outcome": "Global assignment extended/Extension of global assignment rejected.", "GUID": "c5cc7900-2638-11ee-3781-0201b014c5b2", "name": "Extend global assignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5628210214637908, "y": -0.6511627906976745, "z": 2.5607792671120397 }, "color": "#66CCFF", "size": 1.0 }, { "id": "941", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Schedule interview with suitable candidate(s),\n Prepare interview questions,\n Conduct interview with suitable candidate(s),\n Prepare interview report,\n Share report with relevant stakeholders", "Type": "Business Process", "Description": "This process is concerned with interviewing candidates for global assignment to understand their availability and conditions for global assignment.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Scheduling interview, conducting interview and preparing report from interview.", "Outcome": "Interview with candidate(s) for global assignment conducted.", "GUID": "5dbbe47a-2609-11ee-3781-0201b014c5b2", "name": "Conduct interview with candidate(s) for global assignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.1015511246587275, "y": -0.6478405315614617, "z": 3.4034516112978066 }, "color": "#66CCFF", "size": 1.0 }, { "id": "943", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Send global assignment proposal to candidate,\n Review candidate feedback on proposal,\n Analyze requested changes,\n Update global assignment proposal,\n Get candidate acceptance of global assignment proposal,\n Inform candidate about rejection of changes requested,\n Report candidate refusal of global assignment,\n Assign employee global assignment in HR system", "Type": "Business Process", "Description": "After a candidate for global assignment is selected, they must accept the global assignment conditions. ", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Sending global assignment proposal to a candidate and getting their acceptance of the proposal. Sometimes proposal changes might be required.", "Outcome": "Global assignment proposal accepted/refused.", "GUID": "c0d88200-2614-11ee-3781-0201b014c5b2", "name": "Offer global assignment to candidate", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.649104568084701, "y": -0.6445182724252492, "z": 4.240547722565184 }, "color": "#66CCFF", "size": 1.0 }, { "id": "945", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Initiate relocation at Destination Services Provider (DSP),\n Create and send quotation for services,\n Sign quote and submit PO,\n Provide DSP with necessary information,\n Execute DSP services,\n Initiate shipping of household goods,\n Initiate shipping of personal effects,\n Initiate tax briefings,\n Initiate assignment to social security,\n Initiate assignment to tax provider,\n Initiate school search,\n Initiate home search,\n Initiate pet moving,\n Process immigration application for family members", "Type": "Business Process", "Description": "This process is concerned with activities that are related to employee relocation, such as housing, school search, assignment to social security and tax etc. Usually some Destination Services provider (DSP) is involved to support the relocation.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Initiating relocation services, creating quotation, sending Purchase Order (PO), providing information and initiating DSP services.", "Outcome": "Employee relocation services completed.", "GUID": "6cd53727-279f-11ee-3781-0201b014c5b2", "name": "Initiate employee relocation services", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.2054377026860896, "y": -0.6411960132890366, "z": 5.071998534522514 }, "color": "#66CCFF", "size": 1.0 }, { "id": "947", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Discuss idea for global assignment with HRBP,\n Identify need for global assignment,\n Gather data for feasibility analysis,\n Analyze (financial) feasibility of global assignment,\n Fill formal request for global assignment,\n Send global assignment request for approval,\n Prepare relevant documents for formal request,\n Reject global assignment request,\n Inform stakeholders about global assignment approval,\n Inform stakeholders about global assignment rejection", "Type": "Business Process", "Description": "In a globalized economy, it is sometimes required to send employees across international borders. Usually to fill immediate business needs or to generate and transfer knowledge.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Identify the need for global assignment, prepare relevant documents, analyze feasibility and approve global assignment. ", "Outcome": "Global assignment approved/rejected.", "GUID": "fa423101-1223-11ec-2c3e-001bc641ce4f", "name": "Identify and approve need for global assignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.077287542639006, "y": -0.6378737541528239, "z": 1.6850672243191998 }, "color": "#66CCFF", "size": 1.0 }, { "id": "951", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "After employee transfer is requested, employees hiring manager should provide feedback on employees request or request from another manager for employee transfer.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Sending employee transfer request letter to hiring manager, requesting and receiving managers feedback on employee transfer request, and assessing the feedback.", "Outcome": "Employee transfer justified/dismissed.", "GUID": "d233bc36-253e-11ee-3781-0201b014c5b2", "name": "Receive manager's feedback on employee transfer request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6290997688736892, "y": -0.6345514950166113, "z": 2.519133569911626 }, "color": "#66CCFF", "size": 1.0 }, { "id": "953", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with employee on transfer offer,\n Prepare employee transfer offer draft,\n Send employee transfer offer for approval,\n Send transfer offer to employee,\n Review requested changed in transfer offer,\n Update employee transfer offer,\n Inform stakeholders about offer rejection,\n Inform stakeholders about offer acceptance,\n Update HR system", "Type": "Business Process", "Description": "This process is to negotiate with the employee the terms and conditions of employee transfer to Receiving Country. Both parties must agree on the remuneration package, duration of the contract and all conditions provided in employee transfer offer.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Aligning with employee on employee transfer offer to Receiving Country, preparing and approving employee transfer offer.", "Outcome": "Employee transfer offer accepted/rejected.", "GUID": "44f60dd9-442b-11ea-0cfc-001bc641ce4f", "name": "Negotiate employee transfer offer conditions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.1896318099514103, "y": -0.6312292358803986, "z": 3.347463597539025 }, "color": "#66CCFF", "size": 1.0 }, { "id": "955", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Schedule meeting with employee and Receiving Country HR,\n Conduct meeting with employee and Receiving Country HR,\n Prepare employee transfer report with all details,\n Share employee transfer report with relevant stakeholders", "Type": "Business Process", "Description": "After employee transfer offer is accepted, employee must be familiarized with the next steps.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Schedule a meeting with the employee to inform them about the transfer process. Prepare a report which specifies all relevant information such as new company address, new manager, new role and contact person.", "Outcome": "The employee is informed about the transfer process.", "GUID": "44f60dd7-442b-11ea-0cfc-001bc641ce4f", "name": "Inform employee about transfer process", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.7588387038522297, "y": -0.627906976744186, "z": 4.169989089449389 }, "color": "#66CCFF", "size": 1.0 }, { "id": "957", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect documents for employee transfer request,\n Write employee transfer request letter,\n Submit employee transfer request", "Type": "Business Process", "Description": "This process involves employees themselves or managers requesting employee transfer across departments or locations.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Collecting relevant information/documents, writing employee transfer request letter, and submitting the request.", "Outcome": "Employee transfer requested.", "GUID": "c0bc3ef0-2539-11ee-3781-0201b014c5b2", "name": "Request employee transfer", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.3366750144364947, "y": -0.6245847176079735, "z": 4.9866421415653255 }, "color": "#66CCFF", "size": 1.0 }, { "id": "959", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update employee transfer information in HR system,\n Update organizational structure,\n Release employee separation request,\n Inform stakeholders about employee transfer", "Type": "Business Process", "Description": "When an employee is to be transferred to another location or entity, this must be managed centrally within the organisational hierarchy and communicated across the organization.", "Process_Group": "Employee communication", "hasAssignment": true, "Scope": "Update employee transfer information, inform stakeholders about employee transfer and release separation request.", "Outcome": "Employee separation request received.", "GUID": "44f60dde-442b-11ea-0cfc-001bc641ce4f", "name": "Inform stakeholders about employee transfer", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.1208842381421302, "y": -0.6212624584717608, "z": 1.6563871904493033 }, "color": "#66CCFF", "size": 1.0 }, { "id": "961", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with Receiving Country on employee transfer ,\n Analyze feasibility of employee transfer,\n Inform stakeholders about approval of employee transfer,\n Inform stakeholders about rejection of employee transfer,\n Request approval of employee transfer", "Type": "Business Process", "Description": "This process is concerned with approving employee transfer based on the agreement with the legal entity in Receiving Country and feasibility analysis.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Aligning with the legal entity in Receiving Country on employee transfer, analyzing the feasibility of the transfer and approving employee international transfer.", "Outcome": "Employee transfer approved/rejected.", "GUID": "c0bc6601-2539-11ee-3781-0201b014c5b2", "name": "Approve employee transfer", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6942694185624454, "y": -0.6179401993355482, "z": 2.475772836373336 }, "color": "#66CCFF", "size": 1.0 }, { "id": "963", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Arrange initial interview with employee about transfer,\n Conduct initial interview with employee about transfer,\n Analyze employee transfer possibility,\n Inform stakeholders about inability to identify vacancy", "Type": "Business Process", "Description": "This process involves finding a match between the request and a vacant position in the Receiving Country.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Conducting initial employee interview with HR regarding their transfer location and finding a match between the request and a vacant position in the Receiving Country.", "Outcome": "Employee transfer request matched with vacancy.", "GUID": "d233bc38-253e-11ee-3781-0201b014c5b2", "name": "Match employee transfer request with a vacancy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.276221785039008, "y": -0.6146179401993355, "z": 3.2891966170044977 }, "color": "#66CCFF", "size": 1.0 }, { "id": "968", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Decide on online platform (e.g. Linkedin),\n Create alumni page,\n Create and distribute electronic newsletter,\n Establish online alumni community,\n Define the objective of the alumni network,\n Set up rules & regulations,\n Redefine alumni network objective", "Type": "Business Process", "Description": "The establishment of an online alumni network opens up a communication channel with past employees and interns who want to stay connected to the organization. Additionally, this provides a platform to exchange value with a significant group of individuals with similar goals and objectives.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Define objective of alumni network, Decide on online platform, Create alumni page, Set up rules & regulations, Establish online alumni community, Create and distribute electronic newsletter.", "Outcome": "Online alumni community created (e.g.LinkedIn, Facebook)", "GUID": "46ac2b7c-ec09-11e9-0cfc-001bc641ce4f", "name": "Establish online alumni network", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.866694611055797, "y": -0.6112956810631229, "z": 4.096591510871404 }, "color": "#66CCFF", "size": 1.0 }, { "id": "970", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Invite keynote speaker,\n Post event invitation to alumni page,\n Align on event type (virtual or in-person),\n Conduct alumni event,\n Create after action report (AAR),\n Plan event (budget,\n theme,\n schedule,\n etc)", "Type": "Business Process", "Description": "Host alumni events and mixers as well as career workshops and other learning and development opportunities.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Plan event, Choose event location (virtual or in person), Invite key executives for interactive sessions with community, Invite alumni community to event, Conduct alumni event. Create after action report (AAR)", "Outcome": "Alumni events conducted", "GUID": "46ac2b82-ec09-11e9-0cfc-001bc641ce4f", "name": "Plan and coordinate alumni events", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.4656407043222277, "y": -0.6079734219269104, "z": 4.897890822440301 }, "color": "#66CCFF", "size": 1.0 }, { "id": "972", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Filter & approve member request routinely,\n Monitor community engagement regarding rules & regulations,\n Track & monitor community stats,\n Analyze and document results,\n Enforce community rules and guidelines", "Type": "Business Process", "Description": "Describes the maintenance of chosen platform, and administrative tasks required to monitor and regulate platform activities.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Filter & approve member requests, Monitor community engagement regarding rules & regulations, Track community stats.", "Outcome": "Community governance conducted", "GUID": "46ac2b7a-ec09-11e9-0cfc-001bc641ce4f", "name": "Monitor alumni network", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.1637178311159053, "y": -0.6046511627906976, "z": 1.626579481471131 }, "color": "#66CCFF", "size": 1.0 }, { "id": "974", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check alumni retention rate in online community,\n Check attendance rate of in person event,\n Create and post feedback survey survey,\n Analyze survey results,\n Document survey results", "Type": "Business Process", "Description": "This process is conducted to analyze the impact of online alumni community against set Key Performance Indicators and the overall objective of the alumni network. Impact measurement can be conducted intermittently (monthly, quarterly, bi-annually or annually).", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Check alumni retention rate in online community, Check attendance rate of in-person event, Create and post feedback survey, Analyze survey results, Document results.", "Outcome": "Impact of alumni network determined", "GUID": "46ac2b80-ec09-11e9-0cfc-001bc641ce4f", "name": "Measure impact of alumni network", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7582856027685865, "y": -0.6013289036544851, "z": 2.4307265866601924 }, "color": "#66CCFF", "size": 1.0 }, { "id": "976", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Post regular update about company activities,\n Share relevant information (industry updates,\n job postings),\n Build engagement via online polls & other relevant activities,\n Request regular community feedback,\n Document feedback result", "Type": "Business Process", "Description": "Describes the engagement in regular discussions, sharing interesting topics and keeping alumni informed on new relevant updates on potential job offerings and the overall process of maintaining a productive relationship with the network.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Post regular updates about company activities, Share relevant information (industry news, job posts) Build engagement via polls, Request regular community feedback", "Outcome": "Regular interaction with alumni network established", "GUID": "46ac2b7e-ec09-11e9-0cfc-001bc641ce4f", "name": "Connect and maintain relationship with network", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.361262099115761, "y": -0.5980066445182723, "z": 3.228690338090575 }, "color": "#66CCFF", "size": 1.0 }, { "id": "980", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Notify employee about duty to return company assets,\n Maintain confidentiality of passwords/trade secrets,\n Distribute separation forms and documents,\n Align with employee on return of equipment (Date & time),\n Check condition of returned equipment and assets,\n Check completeness of returned items and forms,\n Update HR system,\n Inform employee on unaccetable status of returned equipment,\n Align with management team on next stems", "Type": "Business Process", "Description": "All administrative forms associated with the termination need to be completed together with a due diligence checklist which ensures that all material and assets that belong to the company is returned. All company-issued equipment or asset must be returned before the employee leaves.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Notify employee about duty to return items, Maintain confidentiality of passwords/trade secrets. Distribute separation forms and documents. Align on return of equipment (Date & time), Check condition of returned equipment and assets, Check completeness of returned items and forms. Return equipment.", "Outcome": "Company equipment, assets and termination forms returned", "GUID": "5dad9928-6cb1-11e9-2ddf-001bc640cd9b", "name": "Conduct employee exit procedure", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.972598860956916, "y": -0.5946843853820598, "z": 4.020404956200015 }, "color": "#66CCFF", "size": 1.0 }, { "id": "982", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create note for departments and pertinent clients on employee exit,\n Distribute note via appropriate channels,\n Archive termination note", "Type": "Business Process", "Description": "The purpose of this process is to ensure that the communication flow and channels are not disrupted as a result of the departure of the employee. Assuming the employee was client-facing, a plan of action must be created to notify the clients about the departure and potential replacement.", "hasAssignment": true, "Process_Group": "Employee communication", "Scope": "Create note for departments and pertinent clients on employee exit, Distribute note via appropriate channels, Archive termination note. ", "Outcome": "All relevant entities notified.", "GUID": "5dad9926-6cb1-11e9-2ddf-001bc640cd9b", "name": "Notify all relevant departments of termination", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.5922469719792502, "y": -0.5913621262458473, "z": 4.805804999404981 }, "color": "#66CCFF", "size": 1.0 }, { "id": "984", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Schedule meeting with employee and Receiving Country HR,\n Conduct meeting with employee,\n Advise management team on meeting outcome and next steps,\n Schedule exit interview,\n Commence separation process", "Type": "Business Process", "Description": "This commences the employee offboarding process. This is necessary to promote and ensure seamless succession planning and the transitioning of work related tasks which will require a hand-over. This helps companies mitigate security risks (reclaiming company asset, etc), manage legal issues such as compensation and contract dispute, as well as navigating the logistical challenges of the transitioning employee.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Schedule meeting with employee, Conduct meeting with employee, Inform management on meeting outcome, Schedule exit interview with employee and commence seperation process.", "Outcome": "Exit interview scheduled", "GUID": "5dad9920-6cb1-11e9-2ddf-001bc640cd9b", "name": "Meet with employee to manage exit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2057591602767435, "y": -0.5880398671096345, "z": 1.5956643905936871 }, "color": "#66CCFF", "size": 1.0 }, { "id": "986", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with senior management on separation request,\n Decide on separation request", "Type": "Business Process", "Description": "This process is triggered by a concensus of all pertinent parties (Human Resources, Senior Management Team) on the need to end a professional relationship with an employee through dismissal, mutual retirement agreement or layoff.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Receive employee separation request, Align with senior manager on separation request, Decide on separation request. ", "Outcome": "Employment termination notification captured", "GUID": "ac724000-24a0-11ee-3781-0201b014c5b2", "name": "Process separation request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8211047390146167, "y": -0.584717607973422, "z": 2.384025488441452 }, "color": "#66CCFF", "size": 1.0 }, { "id": "988", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Conduct exit interview discussing reasons for exit,\n Get feedback from employee regarding experience with company,\n Discuss future aspirations,\n Advise employee on next steps,\n Document outcome of employee exit interview", "Type": "Business Process", "Description": "This interview represents an open discussion between the employee and their direct superior where both the individuals provide retroactive insights as well as feedback on the way forward on both sides of their employment relationship.This interview provides key insight into an employees experience within the organization. In cases of behaviour related exits an official letter is drafted highlighting the documented infringements committed by the employee, usually based on a warning system.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Conduct exit interview discussing reasons for exit. Get input from employee on exit and future career aspirations, Align with employee on next steps", "Outcome": "Agreement on exit terms", "GUID": "5dad9924-6cb1-11e9-2ddf-001bc640cd9b", "name": "Conduct exit interview with employee", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.444694856391397, "y": -0.5813953488372092, "z": 3.1659859537170165 }, "color": "#66CCFF", "size": 1.0 }, { "id": "990", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Confirm termination of employee access with IT,\n Revoke access to company databases,\n Ensure termination of employee access to client databases", "Type": "Business Process", "Description": "The official termination request is made to have the employee information and data removed from the companys servers. Employee access to company files and databases is revoked as part of security measures.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Confirm termination of employees online accounts, Revoke access to sensitive company and client database, Remove employee file from database. ", "Outcome": "Accounts disabled", "GUID": "5dad992c-6cb1-11e9-2ddf-001bc640cd9b", "name": "Revoke employee database access & online accounts", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.076479353513305, "y": -0.5780730897009967, "z": 3.9414812935502255 }, "color": "#66CCFF", "size": 1.0 }, { "id": "992", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update employee exit and separation documents on HR system,\n Store crucial data employee worked with (client lists,\n e.t.c.),\n Confirm employee exit in HR system,\n Determine employee eligibility for alumni network,\n Add employee to alumni network", "Type": "Business Process", "Description": "This represents a retroactive control to ensure that all of the companys assets have been returned together with the processing of all statutory/ social / tax related contributions are processed for the exiting employee.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Document employee exit on HR system, Store critical employee information, Confirm employee exit. Determine employee eligibility for alumni network", "Outcome": "Employee seperation completed", "GUID": "5dad992a-6cb1-11e9-2ddf-001bc640cd9b", "name": "Complete employee separation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.7164076233477408, "y": -0.5747508305647842, "z": 4.710447364860666 }, "color": "#66CCFF", "size": 1.0 }, { "id": "994", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Back up electronic correspondence data,\n Save electronic correspondence on company servers", "Type": "Business Process", "Description": "It is common practice to have the employee emails and electronic correspondence archived to ensure that a clear audit trail exists when it is deemed necessary. It is common practice to have the employee emails and electronic correspondence archived to ensure that a clear audit trail exists when it is deemed necessary. It also helps ensure regulatory compliance (e.g. Freedom of Information Act), and prevents the accidental deletion of crucial company and customer data.", "Process_Group": "Employee Redeployment and Retiring", "hasAssignment": true, "Scope": "Backup and save data", "Outcome": "Electronic correspondence archived", "GUID": "5dad992e-6cb1-11e9-2ddf-001bc640cd9b", "name": "Archive employee electronic correspondence", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.246979603717467, "y": -0.5714285714285714, "z": 1.5636629649360598 }, "color": "#66CCFF", "size": 1.0 }, { "id": "999", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Set up payout percentage in HR application,\n Validate HR application set-up,\n Launch APP in HR application,\n Adjust APP set-up in HR application,\n Close APP process in HR application,\n Add APP information on employee profile,\n Check APP and send gross amount to HR for net calculation,\n Calculate net amount,\n Provide payroll instruction to host HR,\n Inform employee per e-mail on gross/net amounts,\n Run APP report,\n Send data for payout", "Type": "Business Process", "Description": "This process comprises of the application the defined and calculated payout through the use of the pertinent HR Application (eg SAP SuccessFactor, HR Connect APP, Workday) that automates benefits dissemination.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Set up payout percentage in HR Application,Validate HR Application set-up, Launch APP in HR Application, Align employee information, Align with all pertinent entities,Run APP report, Send data for payout. ", "Outcome": "Applied Payout Percentage (APP) received", "GUID": "02fd56fd-0e94-11ee-3781-0201b014c5b2", "name": "Apply payout factor", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8826840597781367, "y": -0.5681063122923589, "z": 2.3357013360139423 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1001", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare input for balanced scorecard,\n Finalize balanced scorecard,\n Alignment with HR P&P,\n Request approval from authorizing committee,\n Create and send target letters for SLT & MDs", "Type": "Business Process", "Description": "This process outlines the target definition phase in accordance with organizational goals & objectives by maintaining a balanced scorecard. The balanced scorecard is particularly significant in this scenario because it is a management system tool that translates organizational goals into a set of key performance metrics, while simultaneously focusing on strategy and improving performance. ", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Create & finalize balanced scorecard, alignment with Human Resources Policies & Procedures, T&C Committee and Senior Leadership Teams to finalize target letter. ", "Outcome": "Target letter finalized", "GUID": "572bf234-0b6e-11ee-3781-0201b014c5b2", "name": "Define target", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.526463255506828, "y": -0.5647840531561461, "z": 3.1011261532826815 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1003", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Compile results on organizational goals,\n Calculate company payout factor,\n Check payout factor and advise,\n Adjust payout factor,\n Inform all relevant stakeholders of approved payout factor,\n Inform HR P&A of payout factor to be set up", "Type": "Business Process", "Description": "This process describes the procedure of calculating the payout factor which is largely dependent on the outcomes of predefined organizational targets and performance metrics. Payout factor indicates a proportion of target earnings determined by appropriate entities, that is payable to employees based on performance.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Compile results on organizational goals, calculate company payout factor, alignment with all relevant stakeholders and HR Personnel & Administration", "Outcome": "Payout factor calculated", "GUID": "572bf236-0b6e-11ee-3781-0201b014c5b2", "name": "Calculate payout factor", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.1782653664648732, "y": -0.5614617940199336, "z": 3.859874254471239 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1007", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Analyze payroll report for accuracy,\n Check payroll schedule,\n Advise accounting department on error,\n Inform employee on error and further action,\n Document payroll results", "Type": "Business Process", "Description": "After running the payroll it is necessary to check the results for completeness and correctness. ", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Check payroll report, Compare report with schedule. ", "Outcome": "Validity of payroll results confirmed.", "GUID": "2db0a716-6d94-11e9-2ddf-001bc640cd9b", "name": "Validate payroll results", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.8380381293533463, "y": -0.558139534883721, "z": 4.611882838671193 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1009", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Cluster relevant payroll results information,\n Create summary of payroll results,\n Post to accounting", "Type": "Business Process", "Description": "This process ensures that all information from payroll results are reflected in accounting components.", "Process_Group": "General Ledger", "hasAssignment": true, "Scope": "Group relevant information from payroll results together, create summarized documents, and perform the relevant postings in accounting components. ", "Outcome": "Payroll results are reflected in accounting.", "GUID": "2db0a718-6d94-11e9-2ddf-001bc640cd9b", "name": "Post payroll results to Accounting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2873510983932226, "y": -0.5548172757475083, "z": 1.530596991198455 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1011", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Input schedule data in payroll software,\n Check accuracy of data,\n Make necessary adjustments,\n Save payroll information,\n Align with benefits & compensation,\n Maintain employee status for pay period", "Type": "Business Process", "Description": "This process involves the collection of and entry of all relevant information in the payroll software for calculation. Furthermore, accuracy of information maintained on the payroll system is crucial.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Enter payroll information in payroll software for calculations. Check employees status for pay period (e.g on paid or unpaid vacation) Check accuracy of information, Save payroll information.", "Outcome": "Payroll information is ready for payroll run.", "GUID": "2db0a712-6d94-11e9-2ddf-001bc640cd9b", "name": "Prepare payroll run", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9429816416081502, "y": -0.5514950166112957, "z": 2.285787028656366 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1013", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Execute payment to employees,\n Align with finance department,\n Make required adjustments", "Type": "Business Process", "Description": "This process executes the payroll based on the provided payroll schedule data.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Align with finance department, Approve payroll, Execute payment to employees. ", "Outcome": "Payroll run completed successfully.", "GUID": "2db0a714-6d94-11e9-2ddf-001bc640cd9b", "name": "Run Payroll", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.606511628204742, "y": -0.548172757475083, "z": 3.034155093602413 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1015", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Define payroll schedule,\n Assign schedule to each employee,\n Input relevant tax information,\n Make required adjustments,\n Approve payroll schedule", "Type": "Business Process", "Description": "The payroll schedule determines the re-occurring pay period of employees which could be weekly, bi-weekly or monthly semi-monthly.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Define one or multiple payroll schedules e.g. a bi-weekly or monthly, Assign schedule to each employee, Input relevant tax information. ", "Outcome": "Payroll schedule created", "GUID": "2db0a710-6d94-11e9-2ddf-001bc640cd9b", "name": "Create payroll schedule", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.277887603481729, "y": -0.5448504983388704, "z": 3.7756393973658033 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1019", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Research industry standards in employee benefits,\n Evaluate employees needs and preferences of benefits,\n Select benefit plans,\n Review budget for employee benefits,\n Request approval for benefit plans,\n Inform stakeholders about approved benefit plans,\n Review feedback on employee benefit plans,\n Select different employee benefit plans,\n Determine enrollment type for benefit plans,\n Request approval for enrollment types,\n Inform stakeholders about enrollment types,\n Review feedback on enrollment types,\n Determine different enrollment types", "Type": "Business Process", "Description": "This process aims to provide employees with valuable benefits while aligning with the companys financial resources and strategic objectives. It requires careful consideration of employee preferences, legal requirements, and cost factors to create a well-rounded benefits package.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Researching industry standards in terms of employee benefits, evaluating the needs and preferences of employees for employee benefits, selecting specific benefits based on objectives, needs assessment and budget constraints, and determining enrollment types.", "Outcome": "Employee benefits plans and enrollment types selected.", "GUID": "44f60dcd-442b-11ea-0cfc-001bc641ce4f", "name": "Select employee benefits plans and enrollment types", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.957055683454927, "y": -0.5415282392026579, "z": 4.510178523965217 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1021", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Track employee enrollment in benefit plans,\n Update employee enrollment in benefit plans,\n Create documents,\n Receive signed documents from organization,\n Receive signed document from employee,\n Monitor financial aspects of benefit plans,\n Perform compliance check,\n Analyze vendor performance,\n Analyze employee satisfaction with benefits,\n Gather feedback on employee satisfaction with benefits,\n Report benefits status to stakeholders,\n Align with stakeholders on desired change of benefit plans", "Type": "Business Process", "Description": "This process describes ongoing oversight and evaluation of the organizations benefit programs to ensure they remain effective, compliant, and aligned with the needs of employees and the organization. Monitoring employee benefit plans is a dynamic and essential process that helps organizations adapt their benefits programs to evolving needs, maintain compliance with regulations, and ensure that employees receive valuable and competitive benefits. Regular assessment and adjustment are key to achieving the goals of employee satisfaction, retention, and overall well-being.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Tracking and updating employees enrollment in benefit plans based on changes and life events (e.g. marriage or job change), monitoring financial aspects of benefit plans, compliance checks, analyzing employee satisfaction with benefits, analyzing vendor performance and modifying benefit plans if necessary.", "Outcome": "Employee benefit plans monitored.", "GUID": "6fac0ffa-673c-11ee-3781-0201b014c5b2", "name": "Monitor employee benefit plans", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.326846159226915, "y": -0.5382059800664452, "z": 1.4964889808297235 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1023", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare communication materials,\n Prepare training materials,\n Request approval for communication and training materials,\n Select communication channels,\n Review feedback on communication and training materials,\n Adjust communication and training materials,\n Inform employees about benefit plans and enrollment,\n Share training materials for enrollment", "Type": "Business Process", "Description": "This process describes effective communication of the details of available employee benefit programs and the enrollment process to the workforce. Effectively informing employees about benefit plans and enrollment is essential for ensuring that they make informed choices, understand the value of their benefits, and can take advantage of the offerings that best suit their needs and preferences. Clear and accessible communication can also lead to higher employee satisfaction and engagement with the organizations benefits programs.", "Process_Group": "Employee communication", "hasAssignment": true, "Scope": "Preparing and approving communication and training materials, selecting communication channels, informing employees about benefit plans and enrollment, and providing training material for enrollment. ", "Outcome": "Employees informed about employee benefit plans and enrollment.", "GUID": "6fac0ff6-673c-11ee-3781-0201b014c5b2", "name": "Inform employees about benefit plans and enrollment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.001956433666718, "y": -0.5348837209302326, "z": 2.234316548231346 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1025", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with stakeholders,\n Identify objectives of employee benefit program,\n Determine budget for employee benefit program,\n Request approval for employee benefit budget ,\n Inform stakeholders about approved budget,\n Review feedback on employee benefits budget,\n Adjust employee benefits budget,\n Inform stakeholder about rejected budget,\n Request approval for employee benefit program,\n Review feedback on program objectives,\n Adjust program objectives,\n Share program objectives with stakeholders", "Type": "Business Process", "Description": "This process describes setting clear goals and financial allocations for the organizations employee benefit programs. This process is crucial to ensure that the organizations benefits package aligns with its strategic goals, meets the needs of employees, and remains financially sustainable. It requires careful planning, analysis, and ongoing evaluation to make informed decisions about benefit offerings.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Identifying objectives and goals of the employee benefit program, determining and approving the budget available for employee benefits.", "Outcome": "Objectives and budget for employee benefit program approved.", "GUID": "6fabc1d0-673c-11ee-3781-0201b014c5b2", "name": "Determine objectives & budget for employee benefit program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.684785477228778, "y": -0.5315614617940199, "z": 2.9651183688449003 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1027", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Activate employee benefits in HR system,\n Inform benefit receiver about activated benefits,\n Create documents,\n Receive signed documents from organization,\n Receive signed document from employee", "Type": "Business Process", "Description": "After employees have been enrolled in the right benefits plan activation is needed in the system.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Confirming enrollment by activating in system, and informing benefit receiver of enrollment and handover relevant documents (if applicable).", "Outcome": "Employee benefits activated.", "GUID": "44f60dd1-442b-11ea-0cfc-001bc641ce4f", "name": "Activate employee benefit plans", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.3752782413414026, "y": -0.5282392026578073, "z": 3.6888340696658184 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1029", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Configure HR system to set up benefit plans,\n Set up employee benefit plans in HR system,\n Establish procedures for employee enrollment in benefit plans ", "Type": "Business Process", "Description": "This process involves configuring and implementing benefit programs within the HR software or system. It is a critical step in ensuring that benefits are efficiently managed and accurately administered. It requires careful attention to detail, compliance with regulations, and seamless integration with other HR processes to provide employees with access to the benefits they need and deserve.", "Process_Group": "Employee Data Management", "hasAssignment": true, "Scope": "Configuring HR system to set up employee benefit plans, establishing procedures for employee enrollment in benefit plans, setting up employee benefit plans.", "Outcome": "Employee benefit plans set up in HR system.", "GUID": "44f60dcf-442b-11ea-0cfc-001bc641ce4f", "name": "Set up employee benefit plans in HR system", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.073379258019582, "y": -0.5249169435215948, "z": 4.405403661452131 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1033", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Monitor job application of referred candidate,\n Review job application status of referred candidate,\n Communicate job application status to referee", "Type": "Business Process", "Description": "This process describes monitoring and recording the progress and status of employee referrals throughout the recruitment and hiring process. Tracking referrals helps ensure transparency, accountability, and effective management of the employee referral program, allowing organizations to assess its success and make informed decisions regarding incentives and program improvements.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Monitoring candidates job application, reviewing candidates job application status, communicating the application status to referee.", "Outcome": "Employee referrals monitored.", "GUID": "b6f93ee8-628e-11ee-3781-0201b014c5b2", "name": "Monitor employee referrals", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.3654378978211574, "y": -0.521594684385382, "z": 1.4613621547014752 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1035", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with stakeholders,\n Define programs objectives,\n Develop referral bonus structure,\n Request approval for employee referral bonus program,\n Define eligibility criteria,\n Develop communication strategy,\n Review feedback on the program,\n Estimate costs,\n Inform stakeholders about rejection of the program,\n Implement changes into the program design", "Type": "Business Process", "Description": "This process describes creating and gaining approval for a structured program within an organization that incentivizes employees to refer potential candidates for job openings.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Defining the programs objectives, bonus structure, eligibility criteria, and communication strategy, and seeking approval from relevant stakeholders, such as HR, management, and finance.", "Outcome": "Employee referral bonus program approved.", "GUID": "b6f93ed1-628e-11ee-3781-0201b014c5b2", "name": "Design and approve employee referral bonus program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.0595682856765363, "y": -0.5182724252491695, "z": 2.1813249360504305 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1037", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare communication materials,\n Request approval for communication materials ,\n Inform employees about the program,\n Review feedback on communication materials,\n Adjust communication materials,\n Clarify program benefits,\n Clarify eligibility criteria,\n Clarify submission process,\n Clarify reward structures", "Type": "Business Process", "Description": "This process describes communicating details of the referral program to the workforce. It aims to ensure that all employees are aware of the programs existence and how it works, encouraging them to participate in referring potential candidates for job openings within the organization. Effective communication is key to the success of the referral program.", "Process_Group": "Employee communication", "hasAssignment": true, "Scope": "Preparing and approving communication materials, and sharing information about program benefits, eligibility criteria, referral submission procedures, and reward structures.", "Outcome": "Employees informed about employee referral bonus program.", "GUID": "b6f93ed5-628e-11ee-3781-0201b014c5b2", "name": "Inform employees about employee referral bonus program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.7612315134254817, "y": -0.5149501661129567, "z": 2.8940629794919848 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1039", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Assess referral bonus eligibility criteria,\n Inform referee about not meeting criteria,\n Inform referee about meeting criteria,\n Determine bonus amount based on predefined rules ,\n Ensure accurate and timely bonus distribution", "Type": "Business Process", "Description": "This process describes determining the amount of and distributing monetary or non-monetary rewards earned by employees who have successfully referred candidates that were subsequently hired by the organization.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Assessing whether the referred candidate met the programs eligibility criteria, determining the bonus amount based on predefined rules, and ensuring accurate and timely distribution of rewards to the referring employees.", "Outcome": "Employee bonus distributed.", "GUID": "b6f93eed-628e-11ee-3781-0201b014c5b2", "name": "Calculate and distribute employee referral bonus", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.47037097610317, "y": -0.5116279069767442, "z": 3.599517368789979 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1041", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with stakeholders on key positions for referral bonus,\n Identify job positions for referral bonus,\n Consider financial implications of referral bonus for positions,\n Request approval of referral bonus for identified positions,\n Inform employees about job positions with referral bonus ,\n Review feedback on referral bonus for identified positions,\n Adjust list of job positions with referral bonus", "Type": "Business Process", "Description": "This process describes identifying and specifying which job positions or openings within the organization will be included in the referral program. This selection is typically based on the organizations strategic hiring needs, job roles that benefit from referrals, and budget considerations. By determining which positions are eligible, the organization focuses its efforts on incentivizing employees to refer candidates for roles that align with its priorities and goals.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Identifying job positions for referral bonus, considering financial implications, approving job positions for referral bonus, and informing employees about the eligible job positions for employee referral bonus.", "Outcome": "Job positions selected for employee referral bonus.", "GUID": "b6f93eda-628e-11ee-3781-0201b014c5b2", "name": "Select job positions eligible for employee referral bonus program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.186929659486591, "y": -0.5083056478405317, "z": 4.297629582282714 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1046", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review travel request,\n Evaluate travel request,\n Request additional information and/or documents,\n Receive additional information and/or documents,\n Approve travel request in Travel Management system,\n Reject travel request in Travel Management system,\n Inform stakeholders about approved travel request,\n Inform stakeholders about rejected travel request", "Type": "Business Process", "Description": "This process describes steps leading to approving submitted travel request.", "Process_Group": "Travel Management Activities", "hasAssignment": true, "Scope": "Evaluating travel necessity and conditions, approving or rejecting travel request.", "Outcome": "Travel request approved/rejected.", "GUID": "393bd876-ba89-11e9-0cfc-001bc641ce4f", "name": "Approve travel request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.403100040764004, "y": -0.5049833887043189, "z": 1.4252404272992156 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1048", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare travel schedule,\n Register travel in Travel Management system,\n Plan travel,\n Select travel-related services,\n Request approval for travel-related services,\n Make required adjustments,\n Send confirmation to procurement", "Type": "Business Process", "Description": "This process describes planning the trip and selecting travel-related services to be purchased.", "Process_Group": "Travel Management Activities", "hasAssignment": true, "Scope": "Planning trip agenda, selecting travel-related services (transportation, accommodation, etc.) and approving them.", "Outcome": "Confirmation sent to procurement.", "GUID": "393bd872-ba89-11e9-0cfc-001bc641ce4f", "name": "Plan travel", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.1157779752554053, "y": -0.5016611295681064, "z": 2.1268482690178296 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1050", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review travel expense report,\n Analyze travel expenses,\n Evaluate travel expenses,\n Request clarification on travel expenses,\n Deduct unjustified travel expenses from reimbursement,\n Approve travel expenses,\n Inform traveler about approved expenses,\n Travel cost posting", "Type": "Business Process", "Description": "Describes the evaluation of entered data about trip, checking of receipts, project times, and final approval before posting expenses.", "hasAssignment": true, "Process_Group": "Travel Management Activities", "Scope": "Choosing trip, handling documents and receipts according to travel guidelines, approve/reject travel expenses and if clarification needed contact person who entered the trip. ", "Outcome": "Travel expense ready for payout.", "GUID": "393bd88a-ba89-11e9-0cfc-001bc641ce4f", "name": "Evaluate and approve travel expense", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.835797692023772, "y": -0.4983388704318936, "z": 2.821037300340541 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1052", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create posting run,\n Check posting run,\n Create trip transfer documents for Accounting,\n Post posting run", "Type": "Business Process", "Description": "This process describes transfer of travel expense results to Travel Management Accounting.", "hasAssignment": true, "Process_Group": "Travel Management Activities", "Scope": "Creating trip transfer documents for Accounting, creating and checking posting run, and posting posting run.", "Outcome": "Travel settlement results transferred to Travel Management Accounting.", "GUID": "393bd88d-ba89-11e9-0cfc-001bc641ce4f", "name": "Post travel expense", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.5631010682480384, "y": -0.4950166112956811, "z": 3.5077501019100104 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1054", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Determine reimbursement amount,\n Determine method of travel expense reimbursement,\n Settle trip in Travel Management system,\n Prepare travel expense statement for traveler,\n Send travel expense statement to traveler,\n Calculate taxation in HR Payroll", "Type": "Business Process", "Description": "Describes the settlement of travel expenses to employee or third party.", "Process_Group": "Travel Management Activities", "hasAssignment": true, "Scope": "Settling trip in Travel Management system, determining reimbursement amount and taxation, preparing travel expense statement for travel.", "Outcome": "Travel reimbursement settled.", "GUID": "393bd890-ba89-11e9-0cfc-001bc641ce4f", "name": "Reimburse travel expense", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.297629582282713, "y": -0.49169435215946833, "z": 4.186929659486592 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1056", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect all travel-related documents (receipts etc.),\n Create travel expense report,\n Check travel expense report for completeness,\n Forward travel expense report to approver,\n Request additional input,\n Receive additional input ", "Type": "Business Process", "Description": "After a trip has been done, the traveler has to complete a travel expense report. On the basis of the trip provisions set for the relevant traveler, the system determines the travel expense results, especially the amount for reimbursement. To determine the reimbursement amount, you can choose between per diem/flat rate reimbursement and reimbursement according to individual receipts for meals, accommodations and travel costs for all other categories, reimbursement on the basis of individual receipts must be used", "hasAssignment": true, "Process_Group": "Travel Management Activities", "Scope": "Completing travel expense report including all necessary data and documents, checking travel expense report and receipts and forwarding report to responsible.", "Outcome": "Travel expense report created.", "GUID": "393bd880-ba89-11e9-0cfc-001bc641ce4f", "name": "Create travel expense report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.4398069475159914, "y": -0.4883720930232558, "z": 1.3881483904412681 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1058", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify business need for travel,\n Review travel request form,\n Collect relevant information and documents,\n Create travel request in Travel Management system,\n Submit travel request in Travel Management system,\n Align with employees supervisor on travel request", "Type": "Business Process", "Description": "This process represents the first action in organizing employees travel. It describes identifying business need for travel and submitting formal request for such a travel.", "Process_Group": "Travel Management Activities", "hasAssignment": true, "Scope": "Identifying business need for travel, collecting relevant information and documents, creating and submitting formal travel request in HR system.", "Outcome": "Travel request submitted.", "GUID": "2ba5ac98-73ca-11ee-3781-0201b014c5b2", "name": "Create travel request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.1705472346189882, "y": -0.48504983388704326, "z": 2.0709236350691116 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1062", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain employees general information,\n Maintain employees membership information,\n Maintain employees administrative information,\n Maintain employees personal information,\n Maintain employees financial information,\n Maintain attachments,\n Review existing employee master data,\n Check employee master data for completeness,\n Complete employee master data,\n Save adjusted employee master data", "Type": "Business Process", "Description": "This process describes systematically updating and managing essential information about employees within an organization. The information include general information about employee (i.e., name, position, position number, department etc.), membership (i.e., role, teams and team roles), administrative information (i.e., absence, education, previous employment etc.), personal information, financial information (i.e., salary, bank account, employee costs etc.), attachments etc.", "hasAssignment": true, "Process_Group": "Employee Data Management", "Scope": "Identify need for employee master data maintenance, review existing employee master data, adjust relevant employee master data, check the data for completeness, save employee master data.", "Outcome": "Employee master data maintained. ", "GUID": "dc3af550-7704-11ee-3781-0201b014c5b2", "name": "Maintain employee master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.90843324806724, "y": -0.4817275747508305, "z": 2.7460910475687155 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1064", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review current positions database,\n Identify missing or outdated positions,\n Collect information on missing positions,\n Create new positions,\n Check if outdated positions are to be deleted,\n Delete outdated positions,\n Keep outdated positions,\n Report status of positions database", "Type": "Business Process", "Description": "This process describes maintenance and control of positions within an organization. It helps organizations manage their workforce more efficiently and effectively.", "hasAssignment": true, "Process_Group": "Employee Data Management", "Scope": "Reviewing current database of positions, identifying and correcting gaps (if applicable), collecting information on new positions, creating new positions and/or deleting outdated positions, and reporting.", "Outcome": "HR Management system is up to date with employees job position.", "GUID": "46fc8358-1220-11ec-2c3e-001bc641ce4f", "name": "Maintain positions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.6534053867536875, "y": -0.47840531561461797, "z": 3.4135947445528947 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1066", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect information on new company structure,\n Adjust company structure in HR system,\n Update onboarding and other documentation,\n Prepare communication materials,\n Share new company structure with employees,\n Check if company structure is to be updated", "Type": "Business Process", "Description": "This process ensures the recording of relationships between employees and the organizational units to which they belong. It also allows a comprehensive view of the entire company structure.", "hasAssignment": true, "Scope": "Capture/update company structure as required. This can be a result of restructuring the entire organization, or changes in reporting lines.", "Process_Group": "Employee Data Management", "Outcome": "Visualization of the company structure with employees and their reporting lines. ", "GUID": "46fc8354-1220-11ec-2c3e-001bc641ce4f", "name": "Maintain company structure", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.40540366145213, "y": -0.4750830564784052, "z": 4.073379258019583 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1070", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review absence reasons,\n Prepare proposal for change of working schedule,\n Send proposal to approver,\n Receive approval for change proposal,\n Change employees working schedule in HR system,\n Inform stakeholders about change in working schedule", "Type": "Business Process", "Description": "This process describes the change of a working schedule due to for instance, reduced working times during parental leave.", "Process_Group": "Employee Data Management", "hasAssignment": true, "Scope": "Requesting and approving change of working schedule based on absence reasons, specifying new work schedule including working days per week, and setting minimum/maximum working hours per day.", "Outcome": "Work schedule changed/kept.", "GUID": "51da3440-b8ef-11e9-0cfc-001bc641ce4f", "name": "Change working schedule", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.4755336278663271, "y": -0.4717607973421927, "z": 1.3501112965365616 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1072", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create absence request in HR system,\n Collect all documents and information regarding absence,\n Review required documents for absence request,\n Submit absence request,\n Categorize absence,\n Select respective absence request form", "Type": "Business Process", "Description": "The employee must request for HR planning an application for absence.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Submit date of leave of absent request, categorize request, enter reason and request end date.", "Outcome": "Absence request routed to appropriate manager", "GUID": "8cc35ea6-6d86-11e9-2ddf-001bc640cd9b", "name": "Request employee absence", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.223838776633675, "y": -0.46843853820598014, "z": 2.0135891079215837 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1074", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review date of leave,\n Record absence in HR system,\n Review absence reason and category,\n Review expected end date of absence,\n Inform HR Payroll and other relevant departments,\n Collect relevant documents and information on absence", "Type": "Business Process", "Description": "Employee absences are maintained in the HR records to reflect the planned period of absence for the employee.", "hasAssignment": true, "Process_Group": "Employee Data Management", "Scope": "Update date of leave of absent request, update request category, update reason and request end date.", "Outcome": "Absence maintained.", "GUID": "8cc35e9c-6d86-11e9-2ddf-001bc640cd9b", "name": "Maintain employee absence in HR system", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9790887309751275, "y": -0.4651162790697674, "z": 2.669275244888958 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1076", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review absence request,\n Check required documents and information for completeness,\n Request missing documents and/or information,\n Receive missing documents and/or information,\n Evaluate request,\n Approve request,\n Reject request,\n Inform requestor about approval,\n Inform requestor about rejection", "Type": "Business Process", "Description": "This process ensures that employee leave requests are reviewed and managed in a way that balances the needs of the organization with the well-being of its employees. Proper communication and documentation are essential to maintain transparency and compliance with company policies and legal regulations.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Reviewing absence request, checking all required documents, requesting additional documents if necessary, evaluating absence request and approving/rejecting the request.", "Outcome": "Absence request approved.", "GUID": "c2f6aaf2-74a7-11ee-3781-0201b014c5b2", "name": "Approve absence", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.7412224520743083, "y": -0.46179401993355484, "z": 3.317115398067288 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1078", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check if additional documents from employee are required,\n Request additional documents,\n Receive additional documents,\n Check if authorities must be informed about absence,\n Collect required information and/or documents,\n Inform authorities about employee absence,\n Determine the nature of absence (paid or unpaid)", "Type": "Business Process", "Description": "The request for absence is processed according to requirements of the undertaking e.g. sickness, vacation, and other absences. For instance, in case of a sick leave, a doctors note must subsequently be submitted to the health insurance companies.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Recording absence in HR system, Informing relevant authorities about absence (if required), receiving additional documents from employee regarding the absence (i.e., doctors note), determining whether the absence is paid or unpaid, and informing salary department and other relevant departments.", "Outcome": "Employee absence processed.", "GUID": "8cc35eaa-6d86-11e9-2ddf-001bc640cd9b", "name": "Process employee absence", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.510178523965216, "y": -0.4584717607973421, "z": 3.9570556834549278 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1082", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check timesheet data for Controlling,\n Transfer timesheet data to Controlling,\n Complete timesheet data for Controlling,\n Service activity posting", "Type": "Business Process", "Description": "This process describes sending recorded timesheet information, including work hours and related data, to the Controlling module for analysis and tracking of labor costs and project expenses.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Checking timesheets for completeness and transferring timesheet data to Controlling.", "Outcome": "Timesheet data transferred to Controlling.", "GUID": "d04c948a-83ab-11ee-3781-0201b014c5b2", "name": "Transfer timesheet data to Controlling", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.510255758946321, "y": -0.45514950166112955, "z": 1.311155041392692 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1084", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes approval procedure of employees timesheet. It involves collaboration between employees and management, alternatively project leads, with the goal of accurately reflecting worked hours and activities.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Checking timesheet for completeness, forwarding timesheet for managers approval, requesting potential corrections, receiving managers approval of employees timesheet.", "Outcome": "Timesheet approved.", "GUID": "1b4afaf5-730a-11ee-3781-0201b014c5b2", "name": "Receive approval of employee's timesheet", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.2756163202018094, "y": -0.451827242524917, "z": 1.9548837211535566 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1086", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check timesheet data for Payroll,\n Transfer timesheet data to Payroll,\n Complete timesheet data for Payroll", "Type": "Business Process", "Description": "This process describes submitting the recorded timesheet data and relevant details, to the payroll system for accurate calculation and processing of employee compensation.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Checking timesheets for completeness and transferring timesheet data to Payroll.", "Outcome": "Timesheet data transferred to Payroll.", "GUID": "d04c9480-83ab-11ee-3781-0201b014c5b2", "name": "Transfer timesheet data to Payroll", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.0477160382084874, "y": -0.44850498338870426, "z": 2.5906421888108673 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1088", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check timesheet settings,\n Change timesheet settings,\n Record working times,\n Submit working times", "Type": "Business Process", "Description": "This process describes the recording of working times. Where applicable, working times are assigned to projects and orders. Employees working on projects or services have to record the hours spend for it. This can be done using Cross-Application Time Sheet (CATS). CATS is a tool for recording working times and tasks.", "Process_Group": "Employee Reward and Retention", "hasAssignment": true, "Scope": "Set up timesheet based on employee profiles. Record working times on a defined bases (e.g. daily, weekly, monthly)", "Outcome": "Working times recorded and filled time sheet can be generated.", "GUID": "51da3442-b8ef-11e9-0cfc-001bc641ce4f", "name": "Record working time", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.826492477996137, "y": -0.4451827242524917, "z": 3.218377745983058 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1092", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Select tool for storing and sharing knowledge,\n Request approval for the tool,\n Select different tool,\n Assess knowledge types,\n Create inventory of existing knowledge and its source,\n Develop a categorization system to organize knowledge,\n Approve categorization system,\n Develop naming conventions,\n Document naming conventions,\n Store categorized knowledge in selected tool,\n Categorize knowledge", "Type": "Business Process", "Description": "This process describes an ongoing effort that requires collaboration among various stakeholders in an organization. When executed effectively, it can significantly enhance productivity, problem-solving, and innovation by making critical information readily available to those who need it.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Selecting knowledge management system, assessing knowledge types, creating inventory of existing knowledge and its sources, developing a categorization system to classify knowledge into logical groups, developing and documenting naming conventions and formatting, storing and categorizing knowledge in dedicated knowledge management platform or Content Management System (CMS).", "Outcome": "Knowledge organized.", "GUID": "1b4afafe-730a-11ee-3781-0201b014c5b2", "name": "Organize knowledge", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.6118828386711925, "y": -0.44186046511627897, "z": 3.8380381293533468 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1094", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with source of knowledge,\n Document tacit knowledge,\n Document explicit knowledge,\n Acquire knowledge from source of knowledge,\n Check documented knowledge for completeness,\n Request additional information,\n Receive additional information,\n Share progress with stakeholders", "Type": "Business Process", "Description": "The process by which knowledge is converted from tacit to explicit forms.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Acquire and document tacit knowledge internally/externally, checking for completeness.", "Outcome": "Successful capture of needed knowledge.", "GUID": "c8a1e91d-b758-11e9-0cfc-001bc641ce4f", "name": "Capture knowledge", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5439497017884956, "y": -0.43853820598006643, "z": 1.2713061465859494 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1096", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review knowledge repository,\n Validate knowledge repository,\n Conduct corrective actions,\n Ensure knowledge consistency,\n Approve knowledge correctness and relevance", "Type": "Business Process", "Description": "This process ensures that the knowledge available to employees is reliable and conducive to informed decision-making and problem-solving. It also contributes to a culture of continuous improvement and learning within the organization.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Reviewing and validating the knowledge repository addressing issues such as incorrect or outdated information, redundancy, incomplete data, and knowledge gaps ensuring knowledge consistency, approving knowledge correctness and relevance.", "Outcome": "Knowledge correctness and relevance approved.", "GUID": "1b4afb02-730a-11ee-3781-0201b014c5b2", "name": "Review and validate knowledge repository", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.3258446149620107, "y": -0.4352159468438539, "z": 1.8948474416301215 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1098", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review knowledge repository,\n Validate relevance of stored knowledge,\n Update knowledge,\n Share status of knowledge repository with stakeholders", "Type": "Business Process", "Description": "This process describes the maintenance of knowledge data and availability.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Reviewing knowledge repository and its content, validating relevance of knowledge, investigating any concerns, and taking corrective actions.", "Outcome": "Knowledge repository monitored and updated.", "GUID": "c8a1e922-b758-11e9-0cfc-001bc641ce4f", "name": "Monitor and update knowledge repository", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.114268448018589, "y": -0.43189368770764114, "z": 2.510245413037516 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1100", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare communication materials,\n Share knowledge,\n Determine knowledge sharing approach,\n Approve knowledge sharing approach,\n Communicate knowledge management approach,\n Prepare training materials,\n Share training materials with employees", "Type": "Business Process", "Description": "This describes the process by which new information from different sources are shared and eventually can drive the creation of new knowledge.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Preparing communication materials to communicate knowledge sharing approach, preparing training materials and providing them to employees, and sharing knowledge via e.g. communities, self learning or via IT systems.", "Outcome": "Knowledge shared.", "GUID": "c8a1e927-b758-11e9-0cfc-001bc641ce4f", "name": "Share knowledge", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9091574123401482, "y": -0.4285714285714286, "z": 3.1174490092936677 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1102", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify source of knowledge,\n Discover knowledge,\n Align with stakeholders to identify source of knowledge,\n Create a list of discovered knowledge,\n Add source of knowledge to the list of discovered knowledge", "Type": "Business Process", "Description": "This describes the identification stage of HR relevant material that should be integrated into the HR knowledge base.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Identify sources of knowledge, increase the ability of individuals within the organization to share relevant knowledge with others.", "Outcome": "Source of knowledge and responsible persons identified.", "GUID": "c8a1e911-b758-11e9-0cfc-001bc641ce4f", "name": "Discover knowledge", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.7104473648606655, "y": -0.42524916943521585, "z": 3.7164076233477417 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1107", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review individual training needs,\n Select appropriate training program for employee,\n Assign training program to employee in LMS,\n Monitor training progress,\n Discuss delay with employee,\n Support employee if necessary", "Type": "Business Process", "Description": "This process describes assigning training programs to employees based on their individual training needs.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Reviewing individual training needs, selecting appropriate training program, assigning the training program to an employee and monitoring progress.", "Outcome": "Training program deployed.", "GUID": "04cded2a-baa7-11e9-0cfc-001bc641ce4f", "name": "Deploy training program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5765925174200899, "y": -0.4219269102990033, "z": 1.2305917414053222 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1109", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify general trainee characteristics,\n Identify general characteristics of work environment,\n Select training method(s),\n Decide on sequencing of training sessions,\n Request approval for general training design,\n Develop training content draft,\n Request approval for training content draft,\n Implement training content in LMS system,\n Review feedback on general training design,\n Adjust training design based on feedback,\n Review feedback on training content draft,\n Adjust training content draft", "Type": "Business Process", "Description": "This process is concerned with designing training programs based on training needs assessment and criteria for training success. In training design the following aspects must be considered: trainee characteristics, work environment, training methods (i.e., audiovisual instruction, conference, lecture, role play, simulation, microlearning etc.), sequencing of training sessions (i.e., one long or several short training sessions, breaking training topic into components or training topic as a whole) etc.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Identify general trainee characteristics and aspects of work environment influencing training design, select training methods, decide on sequencing of training sessions, develop training content, approve training program.", "Outcome": "Training program developed.", "GUID": "51da343c-b8ef-11e9-0cfc-001bc641ce4f", "name": "Design and develop training programs", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.374489465287762, "y": -0.4186046511627908, "z": 1.8335211422935482 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1111", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify purpose of evaluation,\n Select evaluation method,\n Request approval for evaluation method,\n Design evaluation tools,\n Collect data,\n Analyze data,\n Report evaluation results,\n Decide on follow-up actions,\n Review feedback on evaluation method,\n Select different evaluation method,\n Request approval for evaluation tools design,\n Review feedback on evaluation tools design,\n Adjust evaluation tools based on feedback,\n Improve program,\n Dismiss program,\n Maintain program", "Type": "Business Process", "Description": "This process is concerned with evaluation of training results based on the predefined training criteria to. Training evaluation can be done for various purposes, such as to determine whether training objectives were met, to see learned knowledge and skills are applied in practice, to assess results and business impact of training program, to assess effectiveness of training impact, etc. There are various training evaluation methods, such as Kirkpatricks Levels of Evaluation summative vs formative evaluation Context, Input, Process, and Product Evaluation Model etc. ", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Identify purpose of evaluation, select evaluation method, design evaluation tools, collect data, analyze and report results, and decide on follow-up actions (training maintenance, improvement, or dismissal) .", "Outcome": "Training program evaluated.", "GUID": "04cded2e-baa7-11e9-0cfc-001bc641ce4f", "name": "Evaluate program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.178700651255269, "y": -0.415282392026578, "z": 2.4281396520194893 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1113", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review training needs,\n Decide on criteria type,\n Define training criteria,\n Request approval for training criteria,\n Set training criteria in LMS,\n Review feedback on training criteria,\n Adjust training criteria based on feedback", "Type": "Business Process", "Description": "This process is concerned with defining criteria for training success. Criteria for training success will then serve as the basis for training design and as standards against which training results will be evaluated.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Review training needs, define and approve criteria for training success, and set training criteria in Learning Management System (LMS).", "Outcome": "Criteria for training success defined.", "GUID": "826b9620-520f-11ee-3781-0201b014c5b2", "name": "Define criteria for training success", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.989160976484217, "y": -0.4119601328903655, "z": 3.014397900691859 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1115", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review business goals for performance management ,\n Review job descriptions,\n Discuss training needs with HRBPs,\n Identify required KSAOs for job category,\n Review current status of employees KSAOs in job category,\n Define training needs for job category,\n Develop training plan for job category,\n Request approval of training plan,\n Review feedback on training plan,\n Update training plan,\n Set training plan in LMS", "Type": "Business Process", "Description": "This process is concerned with determining training needs and plan for job categories. In general, training needs should be assessed on the organizational, job and person level. This process is concerned with assessing organisational and job-level needs. Organizational training needs assessment covers organizations business objectives and their reflection in employees performance. Job-level training needs assessment is concerned with the nature of tasks conduced on the job. Person-level training needs assessment is concerned with employees required knowledge, skills, abilities and other characteristics. Training plan is a document that includes general information about the training programs such as objectives, target audience, high level schedule, strategies for creating curriculums, resources required, etc.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Review business goals for performance management, review job descriptions, discuss training needs with HRBPs, identify required Knowledge, Skills, Abilities and Other characteristics (KSAOs), review current status of employees KSAOs, identify training needs, and set training program in Learning Management System (LMS).", "Outcome": "Training needs and plan determined.", "GUID": "51da3436-b8ef-11e9-0cfc-001bc641ce4f", "name": "Determine training needs and training plan for job categories", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.80580499940498, "y": -0.4086378737541527, "z": 3.592246971979251 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1117", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review employees performance results,\n Review KSAOs needed for current role,\n Review KSAOs needed for the new role,\n Review KSAOs needed for future role,\n Identify individual training needs", "Type": "Business Process", "Description": "This process is concerned with person-level analysis of training needs that aims to identify a gap between desired and actual Knowledge, Skills, Abilities and Other characteristics (KSAOs) of the individual. ", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Reviewing employees performance assessment results, KSAOs of the new job role for promoted employee, or KSAOs of the employees future job role (in terms of succession planning), and identifying training needs.", "Outcome": "Individual training needs identified.", "GUID": "f60b6a33-c31a-11e9-0cfc-001bc641ce4f", "name": "Identify individual training needs", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.608161982480006, "y": -0.4053156146179402, "z": 1.1890395443827666 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1121", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Let new hire sign all relevant documents,\n Collect signed documents,\n Organize introductory presentation about the company,\n Pick up new hires equipment,\n Assist new hire set up the equipment,\n Facilitate new hires onboarding training,\n Receive confirmation of completed training,\n Hand new hire over to hiring manager,\n Update new hires status in HR system,\n Update new joiners report", "Type": "Business Process", "Description": "This process is concerned with new hires first day at the company that is usually referred to as welcome day. New hire usually spends most of the first day with HR department.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Signing all relevant documents, introducing organizations vision, mission, values, culture, structure,etc., setting up employees laptop and other equipment, conducting initial onboarding training, handing employee over to hiring manager, and updating employees status in HR system and report of new joiners.", "Outcome": "Employee started.", "GUID": "edb69060-4729-11ee-3781-0201b014c5b2", "name": "Conduct employee welcome day", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.421517753567931, "y": -0.40199335548172765, "z": 1.7709465743368211 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1123", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Schedule regular alignment meeting with new hire,\n Conduct regular alignment meeting with new hire,\n Check new hires progress in onboarding activities,\n Inform hiring manager about new hires delay,\n Ensure new hires progress,\n Check new hires job satisfaction,\n Discuss employees job dissatisfaction with hiring manager,\n Take appropriate actions,\n Check hiring managers satisfaction with new hire,\n Discuss managers dissatisfaction with new hire", "Type": "Business Process", "Description": "Employee onboarding can take up to one year (usually 1 month). Thus, HR must monitor that employees have fulfilled required onboarding activities on time.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Aligning with new hire, checking progress on onboarding activities and employee satisfaction.", "Outcome": "Employee onboarding process monitored.", "GUID": "edb6b779-4729-11ee-3781-0201b014c5b2", "name": "Monitor employee onboarding process", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.240968782213589, "y": -0.3986710963455149, "z": 2.344380803691449 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1125", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check employee data capture,\n Confirm employee data capture,\n Complete employee data capture,\n Check HR system setup,\n Complete HR system setup,\n Confirm HR system setup,\n Check completion of onboarding training,\n Confirm completion of onboarding training,\n Remind employee to complete onboarding training ,\n Change new hire status in HR system", "Type": "Business Process", "Description": "This process is concerned with procedures related to completing employee onboarding. Mostly, employee onboarding ends when new hire has finished all onboarding training sessions and all necessary information are captured and systems are updated. Usually it takes one month after employees first day at the company.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Checking and confirming all employee information were captured, all HR systems were properly set up (payroll, benefits etc.) and all onboarding training sessions were completed by the employee.", "Outcome": "Employee onboarding completed.", "GUID": "b0c70b50-4d49-11ee-3781-0201b014c5b2", "name": "Complete employee onboarding", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.0664487036778265, "y": -0.39534883720930236, "z": 2.9092945777897636 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1127", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect new hires personal information,\n Collect new hires social information,\n Collect new hires tax information,\n Collect other relevant information,\n Validate collected information,\n Store information in HR system,\n Store information physically", "Type": "Business Process", "Description": "This process ensures the collection and storage of employee information in the human resources central database.", "hasAssignment": true, "Process_Group": "Employee Data Management", "Scope": "This process covers collection of all employee-related information (i.e., personal, social, tax etc.). Once the information has been collected, it must be validated and stored accordingly.", "Outcome": "Employees information stored.", "GUID": "5dad9936-6cb1-11e9-2ddf-001bc640cd9b", "name": "Perform employee information data capture", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.897890822440301, "y": -0.3920265780730896, "z": 3.4656407043222286 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1131", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Decide on mentor and mentee enrollment,\n Communicate opportunity to enroll in mentoring program,\n Get input on potential mentors and mentees from HRBPs,\n Receive applications to mentoring program,\n Contact potential mentors and mentees,\n Gather information on potential mentors and mentees,\n Evaluate if candidates meet criteria for participation,\n Approve candidates participation in mentoring program,\n Screen potential candidates for mentoring program,\n Inform candidate about approved participation,\n Reject candidates participation in mentoring program,\n Inform candidate about rejected participation", "Type": "Business Process", "Description": "Based on the program design, choose the right mentors. The mentor should have the right set of skills, knowledge, experience, and personality to respond to the mentees needs. ", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Contact and inform potential mentors, gather information that meet the participation criteria, screen, select and approve their participation. ", "Outcome": "Mentors and mentees for the program selected.", "GUID": "1063c7fb-c089-11ec-4ad5-0201b014c5b2", "name": "Select and approve mentors and mentees", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6386366043485616, "y": -0.38870431893687707, "z": 1.146677844422319 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1133", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Organize formal closing of mentoring program,\n Close mentoring relationships,\n Provide guidance on transition out from mentoring,\n Encourage mentees to continue in their personal development,\n Close mentoring program in HR or LMS system", "Type": "Business Process", "Description": "Closing a mentoring program should be a thoughtful and deliberate process to ensure that both mentors and mentees derive maximum value from their experience.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Organizing formal closing of mentoring program, concluding the mentoring relationship, providing guidance on transition out of the formal mentoring relationship, encouraging mentees to continue in their personal development.", "Outcome": "Mentoring program closed.", "GUID": "cde39837-60eb-11ee-3781-0201b014c5b2", "name": "Close mentoring program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.466897462753373, "y": -0.38538205980066453, "z": 1.7071663387792564 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1135", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Plan mentoring program orientation,\n Prepare for mentoring program orientation,\n Schedule mentoring program orientation,\n Conduct mentoring program orientation,\n Decide on format of mentoring program orientation,\n Initiate mentoring program", "Type": "Business Process", "Description": "This process is concerned with giving mentors and mentees orientation in how the mentoring program is organised, how their relationship should look etc.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Introduce all aspects of the program including expectations to mentors and mentees. Orientation can be conducted in any preferred format such as formal session, online learning and email communication. ", "Outcome": "Mentoring program initiated.", "GUID": "1063c808-c089-11ec-4ad5-0201b014c5b2", "name": "Conduct mentoring program orientation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.301030448497781, "y": -0.3820598006644518, "z": 2.259025891416594 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1137", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Define scope of the program,\n Define selection process and criteria,\n Define program objectives,\n Define program timeline,\n Define program structure,\n Prepare program plan and documentation,\n Request approval for mentoring program plan,\n Share mentoring program plan with stakeholders,\n Review feedback on mentoring program plan,\n Adjust mentoring program plan,\n Set up mentoring program in HR or LMS system", "Type": "Business Process", "Description": "Mentoring program design is a framework for how the program will be managed, implemented and monitored. ", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Define scope, selection process and criteria, program timeline, objectives, and structure. Consider the plan of action that covers all aspects of the program. Management must approve the mentoring program plan before it is implemented. Lastly, mentoring program must be set up in some HR or LMS system.", "Outcome": "Mentoring program set up.", "GUID": "1063c800-c089-11ec-4ad5-0201b014c5b2", "name": "Design and set up mentoring program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.140967976123258, "y": -0.37873754152823924, "z": 2.802210595355326 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1139", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Organize feedback sessions with mentors and mentees,\n Gather feedback on mentoring program,\n Decide on the form of feedback gathering,\n Develop a feedback form,\n Intervene to manage issues,\n Terminate affected mentoring relationship,\n Report mentoring program status", "Type": "Business Process", "Description": "As mentors and mentees make progress in their relationship, check in regularly to ensure the program objectives are met. ", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Get and document feedback from both mentors and mentees, keep track of all relationships, provide support and take corrective actions.", "Outcome": "Mentoring program monitored.", "GUID": "1063c80a-c089-11ec-4ad5-0201b014c5b2", "name": "Monitor mentoring program", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.986642141565325, "y": -0.3754152823920265, "z": 3.336675014436496 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1141", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review information about mentors and mentees,\n Match mentors to mentees,\n Document matched pairs,\n Inform mentors and mentees about respective match,\n Inform unmatched mentors and mentees", "Type": "Business Process", "Description": "This process ensures the right mentor is matched to the menee.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Use information gathered from the selection phase to determine who mentors a mentee. Document all matches and inform each mentor and mentee about their respective matches.", "Outcome": "Mentors and mentees matched.", "GUID": "1063c806-c089-11ec-4ad5-0201b014c5b2", "name": "Match mentors to mentees", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6679956357797556, "y": -0.37209302325581395, "z": 1.1035354815408922 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1145", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Notify employees to set individual goals with managers,\n Assist employee with goal setting,\n Check progress of individual goals,\n Remind employees to set individual goals", "Type": "Business Process", "Description": "This process is concerned with facilitating determination of individual performance goals. The individual goals should be determined by an employee and their people manager based on the business goals for performance management.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Notify people managers to meet with employees to set up their individual performance goals, assist people managers when necessary, check progress of individual goals determination.", "Outcome": "Individual performance goals determined.", "GUID": "826bbd4e-520f-11ee-3781-0201b014c5b2", "name": "Facilitate determination of individual performance goals", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.5105976981542684, "y": -0.3687707641196014, "z": 1.6422238574635584 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1147", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Arrange performance review between employee and manager,\n Check completion status of performance examination,\n Update performance form status,\n Facilitate performance review between employee and manager,\n Remind employee and people manager to finalize form,\n Ensure employee performance form is finalized", "Type": "Business Process", "Description": "This process is concerned with facilitating conversation between managers and employee regarding employees performance assessment.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Informing managers to schedule employee performance assessment meeting with employee, facilitating conversations between managers and employees, receiving finalized employee performance form.", "Outcome": "Finalized employee performance form received.", "GUID": "6b488ab9-4d51-11ee-3781-0201b014c5b2", "name": "Facilitate performance feedback meeting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.3588447598821674, "y": -0.36544850498338866, "z": 2.1721330251649196 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1149", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare performance assessment feedback forms,\n Request approval for feedback forms,\n Review feedback on on feedback forms,\n Adjust feedback forms", "Type": "Business Process", "Description": "This process covers preparation of feedback form for 360-degree feedback. During 360-degree feedback, employees are assessed by themselves, their manager, closest colleagues etc.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Reviewing business and individual performance goals and metrics, preparing 360-degree feedback form and receiving approval for the form.", "Outcome": "360-degree feedback form approved.", "GUID": "1f54eb1c-52f8-11ee-3781-0201b014c5b2", "name": "Prepare 360-degree feedback form", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.2126680607979985, "y": -0.3621262458471761, "z": 2.6932188565975155 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1151", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare plan for notifying employees about assessment,\n Request approval for the plan,\n Prepare guidelines for performance assessment form,\n Adjust plan,\n Review feedback,\n Notify people managers about performance assessment,\n Notify remaining employees about assessment", "Type": "Business Process", "Description": "This process is concerned with notifying employees about upcoming performance assessment with guidelines on how to proceed.", "Process_Group": "Employee communication", "hasAssignment": true, "Scope": "Preparing communication plan and guidelines to employee performance assessment form, sharing information about upcoming performance assessment with people managers and then employees themselves.", "Outcome": "Employees notified about performance assessment.", "GUID": "fa230d26-4e2d-11ee-3781-0201b014c5b2", "name": "Notify employees about upcoming performance assessment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.071998534522513, "y": -0.35880398671096336, "z": 3.2054377026860905 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1153", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review business performance goals,\n Select performance metrics,\n Request approval for performance metrics,\n Set up performance metrics in HR system,\n Review feedback on performance metrics,\n Update performance metrics", "Type": "Business Process", "Description": "This process describes how performance metrics are set up. Performance metrics can be either objective (such as attendance, accidents, lateness, productivity), or subjective (such as behavior-focused rating forms where rater chooses behaviour that is closest to the performance of person in question).", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Review performance goals, select performance metrics, set up and approve performance metrics.", "Outcome": "Performance metrics set up.", "GUID": "826bbd52-520f-11ee-3781-0201b014c5b2", "name": "Set up performance metrics", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6962190890260735, "y": -0.3554817275747508, "z": 1.0596418272338806 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1155", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review finalized employee performance form,\n Propose follow-up actions,\n Request approval for follow-up actions,\n Initiate performance assessment follow-up actions,\n Review feedback on proposed follow-up actions,\n Adjust proposal for follow-up actions", "Type": "Business Process", "Description": "Define measures to give an employee with performance deficiencies the opportunity to succeed, or suggest a talented high-performer for promotion, or identify a potential successor.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Reviewing finalized employee performance results, and suggesting potential follow-up actions (development, promotion, succession or no action).", "Outcome": "Employee performance assessment completed.", "GUID": "c8a1e937-b758-11e9-0cfc-001bc641ce4f", "name": "Define performance assessment follow-up actions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.5525887084733547, "y": -0.3521594684385383, "z": 1.5761633434940463 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1157", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Send feedback forms to assessors,\n Monitor completion status,\n Remind assessors to fill feedback form,\n Ensure feedback form is completed,\n Select assessors", "Type": "Business Process", "Description": "This process is concerned with preparing and receiving 360-degree performance feedback form to gather information regarding employees performance.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Selecting assessors, releasing performance assessment form, and receiving filled performance assessment form.", "Outcome": "360-degree feedback form completed.", "GUID": "44f60dc8-442b-11ea-0cfc-001bc641ce4f", "name": "Receive filled 360-degree feedback form", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.4143723561493857, "y": -0.34883720930232553, "z": 2.0837613619517215 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1159", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare business goals proposal for performance management,\n Request approval for proposed business goals,\n Adjust proposed business goals,\n Add proposed business goals in HR system", "Type": "Business Process", "Description": "This process is concerned with setting up business goals in HR system for performance management purposes. Firstly, the corporate business goals should be defined, so that individual performance goals can be determined.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Adding proposal for business goals in HR system, reviewing and adjusting proposed business goals in HR system.", "Outcome": "Business goals for performance management set up.", "GUID": "8a143f4b-4d4c-11ee-3781-0201b014c5b2", "name": "Set up business goals for performance management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.281500143993989, "y": -0.345514950166113, "z": 2.58239356353354 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1165", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain credit limit,\n Review and approve credit limit,\n Release credit limit", "Type": "Business Process", "Description": "This process includes the required activities to set and release the credit limit for a business partner.", "Process_Group": "Credit Management", "hasAssignment": true, "Scope": "Review credit limit for specific business partner, approve and release.", "Outcome": "Released credit limit", "GUID": "ba2c9099-6a54-11e8-2ddf-001bc640cd9b", "name": "Approve and release credit limit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.153901890333812, "y": -0.34219269102990024, "z": 3.0720181159644158 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1167", "text": "Process", "data": { "Advisory_Notes": "For inquiries from and quotations for new potential customers, a dummy customer master might be used. Latest with the order entry, a real customer master is created and the sales order will be captured with reference to it.", "KeyActivities": "Copy data from inquiry to quotation,\n Calculate pricing,\n Change proposed sales price,\n Create quotation", "Type": "Business Process", "Description": "In order to quote a price and conditions to the customer, the quotation must be created and processed. Depending on the business model this may include collecting different information and processing various checks. Base for the creation of a quotation are customer details and information from the customer inquiry.", "Process_Group": "Pre-order Management", "hasAssignment": true, "Scope": "A quotation document is prepared based on information captured in the inquiry. The sales price is calculated and conditions determined (e.g. rebates, shipping conditions, pre-payment requirements etc.). The requested delivery data is checked against availability.", "Outcome": "Quotation is prepared and can be formally processed.", "GUID": "f80615e2-7e50-11e5-0a66-001bc640cd9b", "name": "Create quotation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7232877494462293, "y": -0.3388704318936877, "z": 1.0150267644789226 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1171", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Assess and update sales contract data,\n Send sales contract to business partner,\n Review and provide management approval,\n Trigger resolution of contract issue", "Type": "Business Process", "Description": "A simple approval of the sales contract is performed prior to sending out to the business partner.", "Process_Group": "Customer Contracts", "hasAssignment": true, "Scope": "Request approval of sales contract and issue released sales contract to customer.", "Outcome": "Released sales contract", "GUID": "1de237b6-6a51-11e8-2ddf-001bc640cd9b", "name": "Approve and issue sales contract", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.592841906060726, "y": -0.33554817275747517, "z": 1.5090297711362028 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1173", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify business partner,\n Check for existing contracts,\n Create new contract,\n Trigger creation or update of business partner,\n Maintain basic contract data,\n Trigger contract negotiation,\n Update contract", "Type": "Business Process", "Description": "This process describes the initial creation of a sales contract. Prerequisite is the existence of a business partner. Typically, if a contract already exists it may solely need a renewal or update.", "Process_Group": "Customer Contracts", "hasAssignment": true, "Scope": "Creation of sales contract", "Outcome": "Sales contract", "GUID": "1de237a4-6a51-11e8-2ddf-001bc640cd9b", "name": "Create sales contract", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.4675754338869886, "y": -0.3322259136212624, "z": 1.9939710655632545 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1175", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Monitor import status and documents,\n Monitor receipt of contract acknowledgement,\n Monitor contract validity date ,\n Update contract validity,\n Receive updates from the business partner,\n Assess impact of update information,\n Update sales contract,\n Escalate issue,\n Maintain import data,\n Maintain contract acknowledgement in sales contract,\n Request renewal of contract,\n Monitor contracted volumes,\n Inform sales department,\n Request import data,\n Request contract acknowledgment", "Type": "Business Process", "Description": "Process to reflect reporting requirements on monitoring sales contracts. This can be on volumes agreed upon or the realization of cash discounts.", "Process_Group": "Customer Contracts", "hasAssignment": true, "Scope": "Monitor fulfillment of contractual obligations", "Outcome": "Sales contract report", "GUID": "1de237c2-6a51-11e8-2ddf-001bc640cd9b", "name": "Monitor sales contracts", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.347417364550191, "y": -0.3289036544850499, "z": 2.469810166471802 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1177", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Conduct negotiation,\n Update contract with negotiation results,\n Send to business partner and request confirmation,\n Align on contract issues,\n Align on negotiation issues,\n Trigger credit management", "Type": "Business Process", "Description": "This process describes the formalization of negotiation results within a sales contract. The actual sequence and amount of negotiations will vary according to the subject matter and business relation. This is not reflected in the process.", "Process_Group": "Customer Contracts", "hasAssignment": true, "Scope": "Negotiate and maintain sales contract conditions", "Outcome": "Sales contract with maintained conditions", "GUID": "1de237ae-6a51-11e8-2ddf-001bc640cd9b", "name": "Negotiate and maintain sales and contract conditions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.232296448862846, "y": -0.3255813953488371, "z": 2.936507086866513 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1179", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check contract type and trigger activities,\n Inform supply chain to setup consignment warehouse,\n Update forecast on demand,\n Create demand (sales orders)", "Type": "Business Process", "Description": "This process reflects follow up activities that may be required in order to fulfill certain sales contracts. One example could be the creation of consignment warehouses adaption of stock levels in order to fulfill service levels.", "Process_Group": "Customer Contracts", "hasAssignment": true, "Scope": "Trigger activities according to contract type", "Outcome": "Contract follow-up activities defined and documented", "GUID": "1de237b9-6a51-11e8-2ddf-001bc640cd9b", "name": "Perform contract follow-up activities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7491831885865698, "y": -0.3222591362126246, "z": 0.9697206673914505 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1183", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check tender requirements,\n Trigger definition and approval of legal terms ,\n Trigger provision of certifications,\n Trigger provision of product specifications", "Type": "Business Process", "Description": "Depending on the nature of a tender the activities required to be performed in order to reply sufficiently may vary strongly. These can include (non-exhaustive): ***Product ***Development/ technologies ***Service levels ***Supply Chain ***Legal", "Process_Group": "Customer Contracts", "hasAssignment": true, "Scope": "Trigger definition of legal terms, provision of certifications and product specifications.", "Outcome": "All documents required for tender", "GUID": "3eda628e-9fd5-11e8-2ddf-001bc640cd9b", "name": "Perform tender management activities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.6313298863764234, "y": -0.31893687707641205, "z": 1.4408688451980072 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1187", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Inform requester on result,\n Check feasability of product request", "Type": "Business Process", "Description": "An inquiry including requirements which arent apparently covered by an existing standard product needs to be evaluated by product management. The result can be a reference to a standard product, a solution based on the adaption / configuration of an existing product or the solution based on a new product. In latter case the result needs to be further specified and developed.", "Process_Group": "Customer Relationship Mgmt", "hasAssignment": true, "Scope": "The scope of the feasibility check varies and depends on the extend to which the request deviates from the standard products and the level of customization required.", "Outcome": "Product or solution to customer inquiry", "GUID": "5a61ffcf-9f1d-11e8-2ddf-001bc640cd9b", "name": "Evaluate feasibility of request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.5184177722241596, "y": -0.3156146179401993, "z": 1.9028232655969866 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1192", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Execute campaign,\n Prepare campaign,\n Trigger procurement of external services,\n Trigger procurement of marketing material ", "Type": "Business Process", "Description": "Based on a marketing campaign plan the process execute marketing campaign requires different activities to be initiated and coordinated. Depending on the character of the marketing campaign (event, fair, email, advertising, telephone campaign) these activities can vary and involve the purchasing of services and material.", "hasAssignment": true, "Process_Group": "Customer Relationship Mgmt", "Scope": "Execution and monitoring of defined marketing activities, initiate and participate in purchasing of marketing materials and services.", "Outcome": "Marketing campaign plan is executed.", "GUID": "55508473-a053-11e8-2ddf-001bc640cd9b", "name": "Execute marketing campaign", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.410374845755861, "y": -0.31229235880398676, "z": 2.3555453126450296 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1194", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain campaign structure,\n Create campaign,\n Plan campaign activities,\n Plan campaign ressources,\n Plan external services,\n Plan required marketing material,\n Plan campaign budget ,\n Trigger approval of additional budget,\n Review campaign budget", "Type": "Business Process", "Description": "Plan marketing campaign is a process which defines in detail the activities, required resources and budget for a marketing campaign. The main input of objective and target group is typically predefined in the annual marketing plan.", "hasAssignment": true, "Process_Group": "Customer Relationship Mgmt", "Scope": "Planning of the timely sequence and dependency of required marketing activities. Define required marketing material and services.", "Outcome": "Marketing campaign plan is executable.", "GUID": "55508471-a053-11e8-2ddf-001bc640cd9b", "name": "Plan marketing campaign", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.307128838776639, "y": -0.308970099667774, "z": 2.798996871849864 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1196", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Close campaign,\n Create and store campaign report,\n Evaluate report,\n Follow up on results of campaign", "Type": "Business Process", "Description": "After executing marketing campaign activities the results of the campaign are evaluated in the process Close marketing campaign and documented in a campaign report. This includes checking if all activities were executed, budgets exceeded, services provided in time and an evaluation in how far the objectives were achieved (if tangible, i.e. amount of leads).", "Process_Group": "Customer Relationship Mgmt", "hasAssignment": true, "Scope": "Evaluation of campaign and creation of campaign report", "Outcome": "Campaign report", "GUID": "55508475-a053-11e8-2ddf-001bc640cd9b", "name": "Close marketing campaign", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7738877767272423, "y": -0.30564784053156147, "z": 0.9237543805458687 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1200", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter contact information into system,\n Assign relevant sales department,\n Request additonal lead information,\n Request additonal information,\n Resolve ambiguous sales department assignment,\n Trigger customer qualification ", "Type": "Business Process", "Description": "This process covers the activities required to register a lead in a system and identify and trigger the responsibilities for follow up activities.", "Process_Group": "Customer Relationship Mgmt", "hasAssignment": true, "Scope": "Typical activities are: ***register lead ***evaluate existing business relationship ***identify and assign responsible sales department ***trigger follow up activities", "Outcome": "Registered lead", "GUID": "5a1ed1dc-6a4f-11e8-2ddf-001bc640cd9b", "name": "Register and evaluate lead", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.6680264466475565, "y": -0.30232558139534893, "z": 1.371726969913916 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1202", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Select requested marketing material,\n Post marketing material,\n Trigger follow up actions,\n Trigger marketing material replacement", "Type": "Business Process", "Description": "This process describes the activities in case a lead requirements can be fulfilled by sending standard marketing material or small samples.", "hasAssignment": true, "Process_Group": "Customer Relationship Mgmt", "Scope": "After a selection of material has been made, it is sent out. In the system it is registered which material has been sent out to whom and when.", "Outcome": "Potential customer provided with marketing material and provision documented", "GUID": "5a1ed1e8-6a4f-11e8-2ddf-001bc640cd9b", "name": "Send marketing material", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.566864757491027, "y": -0.2990033222591362, "z": 1.8103800158443188 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1204", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Contact lead and qualify,\n Close lead,\n Define follow up tasks,\n Trigger quotation processing,\n Convert lead into customer ", "Type": "Business Process", "Description": "Qualify lead describes the activities required in order to qualify a lead initiated by a potential new customer for whom no prior business relationship existed and no corresponding business partner exists in the system.", "hasAssignment": true, "Process_Group": "Customer Relationship Mgmt", "Scope": "Typical activities are:***qualify lead ***trigger business partner creation ***initiate follow up activities", "Outcome": "Qualified lead", "GUID": "5a1ed1e5-6a4f-11e8-2ddf-001bc640cd9b", "name": "Qualify lead", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.470329725902789, "y": -0.29568106312292364, "z": 2.239676794028525 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1210", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Record inspection results,\n Close inspection lot,\n Perform ad-hoc inspection,\n Inspection activity posting", "Type": "Business Process", "Description": "Samples (sample may refer also to a 100% inspection) get inspected for each inspection characteristic. The results are recorded. Depending on the trigger for the ad-hoc inspection results document the quality of the inspected product and provide the basis for taking usage decisions and updating or revoking quality certificates OR provides the basis for decisions on corrective actions and follow-up activities.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Once the inspection lot was extracted, the defined inspection takes place. The inspection encompasses quality inspections based on predefined quality characteristics, as well as additional characteristics which will be added during the inspection as necessary.", "Outcome": "Quality characteristics have been assessed and documented.", "GUID": "03110b80-7e45-11e5-0a66-001bc640cd9b", "name": "Inspect and record results of ad-hoc inspection", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.378348113881037, "y": -0.2923588039867109, "z": 2.6595810884258233 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1212", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Post goods receipt into restricted stock,\n Identify and flag batch,\n Physically separate materials ", "Type": "Business Process", "Description": "If an ad-hoc inspection is required, the material/goods need to be blocked until the end of the inspection. In case the material for an ad-hoc inspection could influence the quality of other goods, the batch has to be flagged and physically separated.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "The batch needs to be flagged. In addition, in case of influencing the quality of other goods, it needs to be physically separated. This decision needs to be communicated.", "Outcome": "The relevant batch is flagged and cannot be sold or used for production before a usage decision has been made", "GUID": "07ddae90-7e45-11e5-0a66-001bc640cd9b", "name": "Block material for usage for ad-hoc inspection", "Business_Rules": "It must be defined per material: ***quarantine requirement (yes, no) ***marking conditions (specific signs) ***storage conditions (cooling, humidity)", "Prerequisite": "" }, "position": { "x": -1.7973846948845766, "y": -0.28903654485049834, "z": 0.8771591979764435 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1214", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create inspection lot manually", "Type": "Business Process", "Description": "Quality inspections are processes on the basis of inspection lots. If a specific quantity of a material is inspected, an inspection lot must be created in the system.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "The ad-hoc process is not planned and scheduled by quality management (QM). It must be triggered by an external department. In case of a trigger event, the respective department must inform QM which takes the decision if an ad-hoc inspection must be triggered. The inspection plan for the relevant inspection trigger can differ from the standard inspection plan of the relevant material. Ad-hoc inspection plans include at least the information by whom the inspection will be done and the inspection characteristics. Once the relevant inspection lot is defined, the source of the inspection lot needs to be noted within the quality system. All necessary information for an inspection is stored in the inspection lot. When creating the inspection lot, information from the corresponding material master, standard inspection plan and sampling procedure is evaluated. The inspection itself typically is minimized for the respective inspection trigger.", "Outcome": "The inspection lot and the inspection plan are defined and set up.", "GUID": "03110b7d-7e45-11e5-0a66-001bc640cd9b", "name": "Create inspection lot for ad-hoc inspection", "Business_Rules": "The trigger for the ad-hoc inspection needs to be defined: ***customer (return consignment) ***vendor audit ***production (retention samples) ***storage control ***after relocation of goods ***after adverse events (e.g. non-cooling, water, high temperatures) ***before repackaging The quantity control should be defined: ***single inspection lots ***full volume In case of an inspection of all products, no handling of samples is needed.", "Prerequisite": "" }, "position": { "x": -2.702906603707257, "y": -0.2857142857142858, "z": 1.3016512173526746 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1216", "text": "Process", "data": { "Advisory_Notes": "The storage of the samples, the amount of samples needed and sampling techniques need to be defined. Sample handling might not be necessary in case a 100% control is performed. In this case, the sample comprises of the total quantity.", "KeyActivities": "Draw samples,\n Print sample labels and drawing instructions,\n Record sample drawing activities,\n Trigger sample inspection,\n Identify and label retention samples,\n Store retention samples,\n Update storage location of retention samples,\n Perform sample posting", "Type": "Business Process", "Description": "Handle samples process provides information on the collection and extraction of samples.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Once the inspection lot is generated, the samples can be extracted in the correct way, correct amount and with a dedicated sampling technique. The storage conditions shall not have any influence on the quality of the sample.", "Outcome": "The samples are ready for the inspection.", "GUID": "07ddae9c-7e45-11e5-0a66-001bc640cd9b", "name": "Handle samples", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.612883406783792, "y": -0.28239202657807305, "z": 1.7167042520441145 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1218", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review inspection record,\n Accept product for usage,\n Trigger other follow up actions for usage decisions,\n Document usage decision,\n Accept for restricted usage,\n Block for rework,\n Block for return,\n Block for scrap,\n Block for adjustment,\n Block for recycling,\n Post goods receipt into unrestricted stock,\n Post goods receipt into restricted stock", "Type": "Business Process", "Description": "Based on the quality inspection information, a decision on usage and quality is made. It specifies whether the goods in the inspection lot have been accepted for use or rejected.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Decisions can be made during inspection lot completion with the help of a predefined catalogue, which includes all allowed codes for usage decisions. After the usage decision is made, the stock posting of material for stock-relevant inspection lots is carried out. The usage decision as well as the quality degree are communicated and documented.", "Outcome": "The decisions on usage and quality degree of goods are evaluated, documented and communicated.", "GUID": "07ddae81-7e45-11e5-0a66-001bc640cd9b", "name": "Make usage decision for ad-hoc inspected materials or goods", "Business_Rules": "The usage decision for an inspection lot confirms that all samples have been evaluated and the inspection has been completed. The usage of already produced goods and intermediate goods should be defined: ***approval for sale ***destruction of goods ***recycling ***re-work ***sale (lower quality) Approval requirements for usage decisions must be defined. The matrix between quality properties and actions should be defined to ensure always the same usage of goods. Communication channels for the usage decision need to be defined.", "Prerequisite": "" }, "position": { "x": -4.527241187465733, "y": -0.2790697674418605, "z": 2.1222834943790754 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1223", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check material shelf-life information ,\n Foward batch details for quality inspection,\n Identify relevant batches for quality inspection", "Type": "Business Process", "Description": "The identification of end-of-shelf-life material batches process covers monitoring of manufactured goods, raw and semifinished materials ,and its shelf-life information to ensure product quality.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "The process is triggered by the end-of-shelf life of products or materials with limited storage time.", "Outcome": "The relevant batches for the quality check are defined.", "GUID": "f38ca74f-7e46-11e5-0a66-001bc640cd9b", "name": "Identify end-of-shelf-life material batches", "Business_Rules": "The inspection is triggered within a specified automated or manual report before the batch expiry date. This period needs to be defined per material and monitored per batch. It must be defined per material: ***if an extension is allowed ***quality properties and allowed ranges under which an extension is possible ***if a physical separation is required", "Prerequisite": "" }, "position": { "x": -5.445905787805083, "y": -0.27574750830564776, "z": 2.5183546514244375 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1225", "text": "Process", "data": { "Advisory_Notes": "Inspections follow a clear and predefined inspection plan. The inspection characteristics define what has to be inspected. The inspection method states how the characteristic has to be assessed. The quality parameters define for the inspected product/good the values range within the result are considered as within specification.", "KeyActivities": "Perform inspection of batches,\n Record inspection results for batches,\n Inspection activity posting", "Type": "Business Process", "Description": "Samples (sample may refer also to a 100% inspection) get inspected for each inspection characteristic. The results are recorded. The inspection plan for end-of-shelf-life batches can differ from the original inspection plan used at the time of receiving the product from production or an external vendor.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Once the inspection lot was extracted, the defined inspection takes place. The inspection comprises quality inspections based on predefined quality characteristics.", "Outcome": "Quality characteristics have been assessed and documented.", "GUID": "f38ca755-7e46-11e5-0a66-001bc640cd9b", "name": "Inspect and record results for end-of-shelf-life batches", "Business_Rules": "Clear guidelines and procedures have to be established to comply with any regulatory requirement for extending shelf-life, if allowed at all.", "Prerequisite": "" }, "position": { "x": -1.8196579462615194, "y": -0.2724252491694352, "z": 0.8299668418721975 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1227", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain and communicate new shelf-life date ,\n Review inspection record,\n Accept product for usage,\n Trigger other follow up actions for usage decisions,\n Document usage decision,\n Accept for restricted usage,\n Block for rework,\n Block for return,\n Block for scrap,\n Block for adjustment,\n Block for recycling", "Type": "Business Process", "Description": "Based on the quality inspection information, a decision on usage and quality is made. Based on the inspection result, a new shelf-life date can be determined.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Decisions can be made during the inspection lot completion with the help of a predefined catalogue which includes all allowed codes for usage decisions. After the usage decision is made, the stock posting of material for stock-relevant inspection lots is carried out and a new shelf-life date can be set. The usage decision is communicated and documented as well as a certificate of quality is generated and signed.", "Outcome": "The decision on usage of goods is evaluated, documented and communicated. If the shelf-life of the batch will be extended, a new shelf-life date is set and communicated.", "GUID": "f38ca758-7e46-11e5-0a66-001bc640cd9b", "name": "Make usage decision for end-of-shelf-life batches", "Business_Rules": "The usage decision for an inspection lot confirms that all physical samples have been evaluated and the inspection has been completed. The usage of already produced goods and intermediate goods should be defined: ***approval for sale ***destruction of goods ***recycling ***re-work ***sale (lower quality) Approval requirements for usage decisions must be defined. The matrix between quality properties and actions should be defined to always ensure the same usage of goods. Communication channels for the usage decision need to be defined. New shelf-life date", "Prerequisite": "" }, "position": { "x": -2.735946611003321, "y": -0.2691029900332227, "z": 1.2306892953704611 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1229", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Store batch,\n record and communicate location,\n Block batch,\n Physically separate batch", "Type": "Business Process", "Description": "Expired material is posted to the quality inspection stock and blocked against usage.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Material is posted to the quality stock. In case the batch could influence the quality of other goods in the stock, the batch has to be flagged and physically separated.", "Outcome": "Material is blocked against usage.", "GUID": "f38ca743-7e46-11e5-0a66-001bc640cd9b", "name": "Block material for usage", "Business_Rules": "It must be defined per material: ***quarantine requirement (yes, no) ***marking conditions (specific signs) ***storage conditions (cooling, humidity)", "Prerequisite": "" }, "position": { "x": -3.656442390419621, "y": -0.26578073089700993, "z": 1.6218597490357936 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1234", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Record inspection results,\n Perform inspection of goods for delivery,\n Close inspection lot,\n Inspection activity posting", "Type": "Business Process", "Description": "Samples (sample may refer also to a 100% inspection) get inspected for each inspection characteristic. The results are recorded. The recorded inspection results document the quality of the inspected products and provide the basis for taking usage decisions and creating quality certificates", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "After the samples have been extracted, the defined inspection takes place. The inspection encompasses quality inspections based on predefined quality characteristics. The inspection can also include measurements done directly on the product without taking a specific sample for the inspection", "Outcome": "Quality characteristics have been assessed and documented.", "GUID": "75a44376-82f2-11ee-3781-0201b014c5b2", "name": "Perform inspection for goods to be delivered", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.5810704848911445, "y": -0.2624584717607974, "z": 2.0034453355305732 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1239", "text": "Process", "data": { "Advisory_Notes": "Inspections follow a clear and predefined inspection plan. The inspection characteristics define what has to be inspected. The inspection method states how the characteristic has to be assessed. The quality parameters define for the inspected product/good the values range within the result are considered as within specification.", "KeyActivities": "Record inspection results,\n Perform inspection of samples,\n Review internal specifications,\n Review vendor specifications,\n Close inspection lot,\n Review relevant documentation,\n Inspection activity posting", "Type": "Business Process", "Description": "Samples (sample may refer also to a 100% inspection) get inspected for each inspection characteristic. The results are recorded. Basis for the inspection are the internal goods specification and the vendor goods specification. The recorded inspection results document the quality of the inspected product, which might include quality related documents and certificates provided by the vendor.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Once the inspection lot was extracted, the defined inspection takes place. The inspection comprises quality inspections based on predefined quality characteristics. The inspection can also include measurements done directly on the product, without taking a specific sample for the inspection.", "Outcome": "Quality characteristics have been assessed and documented. Any required documents and certificates have been checked.", "GUID": "f072b287-7e45-11e5-0a66-001bc640cd9b", "name": "Inspect and record results for purchased materials or goods", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.509755867010735, "y": -0.25913621262458464, "z": 2.3754137083760347 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1241", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Reject change request,\n Create change request for vendor record,\n Approve change request,\n Update quality information in vendor record", "Type": "Business Process", "Description": "After quality results of all inbound goods are defined and tracked, the information regarding the vendor shall be updated to ensure a constant quality for the delivered products or goods.", "Process_Group": "Sourcing Direct", "hasAssignment": true, "Scope": "The process is triggered by the final decision of the usage of the delivered goods. The result shall have an influence on sourcing considerations and any further negotiations with the supplier, as well as should be used to commonly further develop the vendors quality management system.", "Outcome": "A track record on quality related data and KPIs is established.", "GUID": "768b35b8-d4a1-11eb-2c3e-001bc641ce4f", "name": "Update quality information in vendor record", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8406923671383186, "y": -0.2558139534883721, "z": 0.7822094409803125 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1245", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Based on the quality inspection information, a decision on usage and quality is. It specifies whether the goods in the inspection lot have been accepted for use or rejected.", "Process_Group": "Quality Inspections", "Scope": "Decisions can be made during the inspection lot completion with the help of a predefined catalogue which includes all allowed codes for usage decisions. After the usage decision is made, the stock posting of material for stock-relevant inspection lots is carried out. The usage decision as well as the quality degree are communicated and documented.", "Outcome": "The decisions on usage and quality degree of goods are evaluated, documented and communicated. ", "GUID": "f200ccc1-7e45-11e5-0a66-001bc640cd9b", "name": "Make lean usage decision for purchased materials or goods", "Business_Rules": "The usage decision for an inspection lot confirms that all relevant quality certificates, specifications and shipment documents have been evaluated and the inspection has been completed. The usage of already produced goods and intermediate goods should be defined: ***approval for sale/use ***return to vendor ***sale (lower quality) Approval requirements for usage decisions must be defined. The matrix between quality properties and actions should be defined to always ensure the same usage of goods. Communication channels for the usage decision need to be defined.", "Prerequisite": "" }, "position": { "x": -2.767123974764955, "y": -0.25249169435215957, "z": 1.1588895151311855 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1246", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The create inspection lot for lean inbound inspection process covers the creation of the inspection lot and the collation of handed over quality certificates, as well as shipment documentations.", "Process_Group": "Quality Inspections", "Scope": "The process is triggered by the inspection plan that includes: ***What shall be inspected? ***By whom? ***When? ***In what way? ***How often? Once the inspection lot is defined, the source of the lot needs to be noted within the quality system. All necessary information for an inspection is stored in the inspection lot. When creating the inspection lot, information from the corresponding material master and inspection plan is evaluated.", "Outcome": "The inspection lot and the inspection plan are defined and set up.", "GUID": "4c0e8a71-7e46-11e5-0a66-001bc640cd9b", "name": "Create inspection lot for lean inbound inspection", "Business_Rules": "The required documents need to be defined: ***quality certificates of goods / materials ***specification (vendor) ***specification (internal) ***shipment documentation In some cases the inspection lot might only consist of checking a quality certificate. For defined vendor and materials/goods, a lean inspection is allowed for.", "Prerequisite": "" }, "position": { "x": -3.697512053266026, "y": -0.2491694352159468, "z": 1.525911077341159 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1247", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The Inspect and record results of lean inspection process describes the inspection and the results record for each inspection characteristic of an inspection plan which is assigned to the inspection lot. Basis for the inspection are the vendor goods quality certificates as well as goods specifications, the internal goods specification and the shipment documentation. The recorded inspection results document the quality of the inspected product and provide the basis for taking usage decision.", "Process_Group": "Quality Inspections", "Scope": "Once the inspection lot was created, the defined inspection takes place. The inspection encompasses quality inspections based on predefined quality characteristics.", "Outcome": "Based on the quality inspection information, a decision on usage and quality can take place.", "GUID": "4c0e8a6b-7e46-11e5-0a66-001bc640cd9b", "name": "Inspect and record results of lean inbound inspection", "Business_Rules": "The inspection method (master data of inspection plan) of goods and the shipment needs to be defined. The quality parameters (master data of inspection plan) and the allowed ranges should be defined for the specific production phase and the intermediate goods: ***weight ***temperatures ***color, etc.", "Prerequisite": "" }, "position": { "x": -4.631780970975309, "y": -0.24584717607973428, "z": 1.8832432229828995 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1251", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create quality notification for inspection lot,\n Describe defect/issue,\n Identify affected objects,\n Identify relevant skakeholders,\n Maintain workflow settings", "Type": "Business Process", "Description": "The quality notification is created in order to document the investigation and the definition and implementation of corrective actions as well as further follow-up activities.", "hasAssignment": true, "Process_Group": "Quality Inspections", "Scope": "Based on a certain inspection lot the quality notification is created. The problem is described, affected objects are identified (e.g. material, batch, equipment, supplier), involved people are named and workflow settings can be maintained.", "Outcome": "The quality notification has been created in is ready to use for managing the quality issue.", "GUID": "00bed5b1-601f-11e9-2ddf-001bc640cd9b", "name": "Create quality notification", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.569854882105451, "y": -0.24252491694352152, "z": 2.230855574053611 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1256", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Receive data from measuring execution system,\n Update quality parameters in inspection lot,\n Close inspection lot", "Type": "Business Process", "Description": "Quality parameters from MES are received.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "The quality parameters are received from the MES and save to the inspection lot. The capturing of data from the MES can be done for multiple different parameters at different stages of production. It might be done multiple times during the production or by receiving a summary of parameters from the MES at the end of production.The inspection lot is closed once all parameters have been received and saved to the inspection lot.", "Outcome": "Quality parameters from MES are saved to inspection lot.", "GUID": "76d66f00-6750-11e9-2ddf-001bc640cd9b", "name": "Receive quality parameters from manufacturing execution system", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8604736371960433, "y": -0.23920265780730898, "z": 0.7339195087327528 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1260", "text": "Process", "data": { "Advisory_Notes": "Inspections follow a clear and predefined inspection plan. The inspection characteristics define what has to be inspected. The inspection method states how the characteristic has to be assessed. The quality parameters define for the inspected product/good the values range within the result are considered as within specification.", "KeyActivities": "Record inspection results,\n Perform inspection of goods for delivery,\n Close inspection lot,\n Inspection activity posting", "Type": "Business Process", "Description": "Samples (sample may refer also to a 100% inspection) get inspected for each inspection characteristic. The results are recorded. The recorded inspection results document the quality of the inspected products and provide the basis for taking usage decisions and creating quality certificates.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "After the samples have been extracted, the defined inspection takes place. The inspection encompasses quality inspections based on predefined quality characteristics. The inspection can also include measurements done directly on the product without taking a specific sample for the inspection, or can be done directly by using the integrated measurement devices of the production line.", "Outcome": "Quality characteristics have been assessed and documented.", "GUID": "72b8f001-59dc-11e8-2ddf-001bc640cd9b", "name": "Perform inspection and record results for finished goods", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.7964174693166317, "y": -0.23588039867109645, "z": 1.0863007582160502 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1264", "text": "Process", "data": { "Advisory_Notes": "Inspections follow a clear and predefined inspection plan. The inspection characteristics define what has to be inspected. The inspection method states how the characteristic has to be assessed. The quality parameters define for the inspected product/good the values range within the result are considered as within specification.", "KeyActivities": "Record inspection results,\n Perform inspection of samples,\n Close inspection lot,\n Inspection activity posting", "Type": "Business Process", "Description": "Samples (sample may refer also to a 100% inspection) get inspected for each inspection characteristic. The results are recorded. The recorded inspection results document the quality of the inspected products and provide the basis for taking usage decisions and creating quality certificates.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "After the samples have been extracted, the defined inspection takes place. The inspection encompasses quality inspections based on predefined quality characteristics. The inspection can also include measurements done directly on the product without taking a specific sample for the inspection, or can be done directly by using the integrated measurement devices of the production line.", "Outcome": "Quality characteristics have been assessed and documented.", "GUID": "09bfdc2e-7e45-11e5-0a66-001bc640cd9b", "name": "Perform inspection and record results for goods in production", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.7360644349301917, "y": -0.2325581395348837, "z": 1.4289235592045315 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1268", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Register retention sample,\n Store retention sample,\n Deliver retention sample to lab,\n Identify and pick retention sample,\n Conduct analysis,\n Bring back to stock,\n Pick sample,\n De-register sample,\n Destroy sample,\n Keep retention sample", "Type": "Business Process", "Description": "Process reflects the lifecycle of the retention sample including additional analyses and later scrapping.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "After the samples are taken, rentention sample is created, analysed and stored.", "Outcome": "Retention sample is kept on stock.", "GUID": "6e792144-99a0-11e9-0cfc-001bc641ce4f", "name": "Manage retention samples in LIMS", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.6793381218139025, "y": -0.22923588039867115, "z": 1.7617589908211446 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1270", "text": "Process", "data": { "Advisory_Notes": " ", "KeyActivities": "Review inspection quality results,\n Check completeness of quality report,\n Document usage recommendation,\n Send usage recommendation to ERP", "Type": "Business Process", "Description": "Based on the inspection data documented in LIMS the usage decision is prepared by documenting a recommendation.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "The results of the quality inspection get reviewed and the completeness of the quality report is checked.Usage recommendation can be made with the help of a predefined catalogue which includes all allowed codes for usage decisions.After the usage recommendation is made in LIMS, the information is sent to ERP.", "Outcome": "A recommendation for the actual usage decision has been documented in LIMS and transferred to ERP.", "GUID": "64e5d47a-8055-11e9-0cfc-001bc641ce4f", "name": "Document usage recommendation in LIMS", "Business_Rules": " ", "Prerequisite": "" }, "position": { "x": -5.626161917436332, "y": -0.2259136212624584, "z": 2.0847786642205306 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1272", "text": "Process", "data": { "Advisory_Notes": "Inspections follow a clear and predefined inspection plan. The inspection characteristics define what has to be inspected. The inspection method states how the characteristic has to be assessed. The quality parameters define for the inspected product/good the values range within the result are considered as within specification. The inspection data transferred from LIMS to ERP depends on the specific use case.", "KeyActivities": "Initiate inspection,\n Perform analysis of results,\n Record analytical time,\n Send inspection data to ERP,\n Maintain inspection data in LIMS,\n Record results in LIMS,\n Inspection activity posting", "Type": "Business Process", "Description": "Samples get inspected for each inspection characteristic and the results are recorded in LIMS.", "hasAssignment": true, "Process_Group": "Quality Inspections", "Scope": "After the samples have been distributed to labs, the defined inspection is initiated. Typically the results are captured in LIMS often by using automated interfacing to laboratory equipment. In addition the efforts might be captured. Finally, inspection data is maintained in LIMS and transferred to ERP.", "Outcome": "Inspection results have been recorded in LIMS and inspection data has been sent to ERP.", "GUID": "a25729e1-38dd-11e9-2ddf-001bc640cd9b", "name": "Inspect and record results in LIMS", "Business_Rules": "An interface from LIMS to SAP (results transferring) takes place as the usage decision is made in SAP.", "Prerequisite": "" }, "position": { "x": -1.8789882892659162, "y": -0.22259136212624586, "z": 0.6851299211109857 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1276", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The process of making a usage decision for in-process inspected materials or goods refers to evaluating the quality, compliance, and suitability of the products at a specific stage of production. Its purpose is to determine whether these materials or products meet predefined standards and can proceed further in the manufacturing process or if they require corrective action or rejection.", "Process_Group": "Quality Inspections", "Scope": "This process begins with setting explicit quality standards, followed by establishing protocols for systematic inspections across production stages. Criteria for evaluating materials against these standards are defined, alongside the creation of a structured decision-making framework to categorize materials based on inspection outcomes. Procedures for addressing non-conformities, whether through rework or disposal, are outlined, and a robust documentation and reporting system is established for traceability and analysis purposes.", "Outcome": "Materials or products are categorized as either acceptable for continued processing, in need of rework, or unfit for use.", "GUID": "75a44378-82f2-11ee-3781-0201b014c5b2", "name": "Make usage decision for in process inspected materials or goods", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.8238071515286083, "y": -0.21926910299003333, "z": 1.0129724433447767 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1277", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Display open inspection lots for the operation,\n Perform inspection,\n Record inspection results according to parameters in routing,\n Valuate inspection points,\n Confirm quality operation,\n Inspection activity posting", "Type": "Business Process", "Description": "Inspection is performed and results are recorded to decide if the production can proceed to the next operation in the production order.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "When production reaches a specific operation where inspection has to be performed the defined inspection takes place. Sampling procedures and Master inspection characteristics are maintained in Routing for the operation. The inspection is performed and the results are recorded in the operation post which the operation can be confirmed. The results are then valuated using a control chart. The valuation can happen manually or automatically through activation of control chart.", "Outcome": "Quality inspection is completed with results documents and confirmed in production order.", "GUID": "ca21ce98-82ec-11ee-3781-0201b014c5b2", "name": "Perform inspection and record results for quality operation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.7720732887945294, "y": -0.21594684385382057, "z": 1.330963224121096 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1281", "text": "Process", "data": { "Advisory_Notes": "***There can be multiple inspection points for one inspection lot. ***Production does not stop during this inspection and there is no sample drawn. ***Capturing of results is typically done by using PI sheets or directly reading data from test equipment (e.g. sensor data), which is interfaced either to the shop floor integration systems or the ERP system.", "KeyActivities": "Valuation of inspection point is triggered,\n Conduct valuation of inspection point,\n Capture valuation results ", "Type": "Business Process", "Description": "The inspection point is valuated and the results are captured.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "Once production reaches the predefined criteria the valuation of instruction point is triggered and conducted. The valuation results is captured for later review.", "Outcome": "Inspection is conducted and result is captured.", "GUID": "27e79566-7551-11e9-2ddf-001bc640cd9b", "name": "Valuate inspection point", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.723709560306008, "y": -0.21262458471760803, "z": 1.6390753460026228 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1283", "text": "Process", "data": { "Advisory_Notes": "***When using sophisticated shop floor integration there might be cases where an ad-hoc adjustment of process parameters (e.g. temperature, machine speed) is possible based on automatically measured and captured inspection points. However this would then need to be considered rather a automated process control instead of quality inspection. ***It is possible that inspection points are dynamically created based on the results of the valuation of the current inspection point. However, such logic is more likely provided by specific expert systems. In such cases, the interface from those systems to ERP triggers the creation of a new inspection point.", "KeyActivities": "Valuate repeated deviations or trends,\n Trigger corrective measure,\n Review valuation of inspection point ", "Type": "Business Process", "Description": "Inspection point valuations are reviewed and follow up actions are triggered.", "hasAssignment": true, "Process_Group": "Quality Inspections", "Scope": "On a recurring basis or ad-hoc the valuation of inspection points are reviewed. Valuations are checked for repeating deviations or trends, might be combined with post-production inspection results and even put into relation to customer complaint cases. Based on this review or analysis corrective measure could be triggered (e.g. re-adjustment of certain machine settings or processing times in the recipe). In severe cases even an ad-hoc quality inspection for certain batches might be initiated in order to block the stock and conduct detailed quality inspections.", "Outcome": "Follow-up actions trigerred.", "GUID": "1c7ed402-7553-11e9-2ddf-001bc640cd9b", "name": "Review results of inspection point valuation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.678638638945657, "y": -0.20930232558139528, "z": 1.9372824286286767 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1290", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Scan product label,\n Post goods receipt,\n Inventory increase (production) posting,\n Cost change posting", "Type": "Business Process", "Description": "This process describes the goods receipt process for products manufactured in production. After goods receipt, the system increases the stock of the goods at the relevant storage location.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "Goods or semi-finished goods that have been produced have to be posted on stock with a goods receipt.", "Outcome": "Goods receipt posted (in many cases in a special stock as long as quality inspection is still ongoing).", "GUID": "1c4d66cd-7ca9-11e5-0a66-001bc640cd9b", "name": "Perform goods receipt from production", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8962237184978166, "y": -0.20598006644518274, "z": 0.635873894263881 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1292", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Scan storage bin ID,\n Scan labels,\n Print putaway form,\n Print labels,\n Move goods to warehouse (Interim storage),\n Apply labels (Individual and packages),\n Move goods to putaway location,\n Confirm transfer order", "Type": "Business Process", "Description": "The putaway process includes putting goods away in storage bins in the warehouse. There are putaway strategies in the Warehouse Management (WM) system that simplify the search for appropriate storage bins.", "Process_Group": "Warehouse Operations", "hasAssignment": true, "Scope": "After transfer order is created based on an goods receipt for an inbound delivery, the putaway of goods is executed within the actual warehouse.", "Outcome": "Goods are stored in the warehouse and storage location has been confirmed.", "GUID": "1c4d66ca-7ca9-11e5-0a66-001bc640cd9b", "name": "Perform putaway", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.8492743743942968, "y": -0.2026578073089702, "z": 0.9389544927311377 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1294", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create transfer order manually,\n Create transfer order automatically based on transfer requirements,\n Maintain material picking data ,\n Maintain material putaway data", "Type": "Business Process", "Description": "A transfer order is used as an instruction to move materials from a source storage location to a destination storage location at a specified time. The transfer order contains information on the quantity of the material to be moved and requirements throughout a warehouse.", "Process_Group": "Warehouse Operations", "hasAssignment": true, "Scope": "The transfer order contains all the information required to execute the physical transfer of materials into the warehouse, out of the warehouse, or from one storage bin to another storage bin within the warehouse.", "Outcome": "Transfer order created.", "GUID": "768b35c2-d4a1-11eb-2c3e-001bc641ce4f", "name": "Create transfer order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.8055140998854777, "y": -0.19933554817275745, "z": 1.2320967638837552 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1299", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Send transportation request information,\n Consolidate transportation requests", "Type": "Business Process", "Description": "In case of outsourced transportation planning the 4PL need information about transportation requirements as early as possible to update their planning. The preliminary plans will be updated later when more solid information becomes available.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Send transportation request information, e.g. sales order and stock transfer order, to 4PL Transport Management System (TMS) to enable the 4PL TMS to perform transportation planning.", "Outcome": "Preliminary orders (sales order, purchase order, transfer order) or deliveries transmitted to 4PL for processing.", "GUID": "abe34416-7e11-11e5-0a66-001bc640cd9b", "name": "Provide transportation outlook to 4PL", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.764865078196579, "y": -0.1960132890365449, "z": 1.5152758120496437 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1301", "text": "Process", "data": { "Advisory_Notes": "Order information needs to be sent directly to the 4PL. The following questions need to be answered: ***Who receives the order information? ***How are the documents transmitted (EDI, Email etc.)? ***What information is required? ***Who communicates with the 4PL?", "KeyActivities": "Receive booking confirmation from carrier,\n Execute booking with 4PL", "Type": "Business Process", "Description": "Firm planning and booking transportation capacities and services by a 4PL is based on actual orders or deliveries provided by the shipper, as would be the case for internal operations.", "hasAssignment": true, "Process_Group": "Transportation Management", "Scope": "Transmission of firm transportation demands (e.g. deliveries from O2C) to 4PL for actual booking.", "Outcome": "Definite orders (sales order, purchase order, transfer order) or deliveries transmitted to 4PL for processing.", "GUID": "abe3442e-7e11-11e5-0a66-001bc640cd9b", "name": "Send transportation demands to 4PL", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.727249320268871, "y": -0.19269102990033216, "z": 1.788467283312658 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1303", "text": "Process", "data": { "Advisory_Notes": "Transport information needs to be exchanged directly with the warehouse. The following questions need to be answered: ***Who receives the transport information? ***How are the documents transmitted (system workflow, EDI, Email etc.)? ***What information is required? ***Who communicates with the warehouse?", "KeyActivities": "Confirm receipt of transportation information,\n Forward transportation information to Warehouse Management,\n Receive WMs confirmation of transportation information", "Type": "Business Process", "Description": "This process assures that the warehouse receives the delivery and pickup information (e.g. times, carrier, transportation requirements) provided by the 4PL.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Provide transportation information to warehouse and confirm receipt.", "Outcome": "Transportation information communicated to warehouse.", "GUID": "abe34419-7e11-11e5-0a66-001bc640cd9b", "name": "Communicate transportation information to warehouse", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.912168190941713, "y": -0.18936877076411962, "z": 0.5861849618940225 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1305", "text": "Process", "data": { "Advisory_Notes": "Order information needs to be received directly from the 4PL. The following questions need to be answered: ***Who receives the shipping information? ***How are the documents transmitted (EDI, Email etc.)? ***What information is required? ***Who communicates with the 4PL?", "KeyActivities": "Receive shipment information from 4PL,\n Update deliveries", "Type": "Business Process", "Description": "Receive consolidated and planned outbound shipment message from 4PL to trigger internal shipment creation.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Process shipment information from 4PL and update deliveries in own system.", "Outcome": "Deliveries updated.", "GUID": "f123cd4c-7e10-11e5-0a66-001bc640cd9b", "name": "Receive transportation information from 4PL", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.8728017997252175, "y": -0.18604651162790709, "z": 0.8642972980957133 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1309", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Reserve transportation capacities with carrier,\n Receive reservation confirmation from carrier,\n Update freight booking", "Type": "Business Process", "Description": "Pre-booking of freight space at a carrier is done based on freight bookings. This is important for complex transports, e.g. involving sea freight or time critical transports. The booking must be confirmed at a later point in any case.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Reserve transportation capacity (freight space) with carrier.", "Outcome": "Carrier freight space assured.", "GUID": "106a8136-7e10-11e5-0a66-001bc640cd9b", "name": "Perform carrier pre-booking", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.836364101563398, "y": -0.18272425249169433, "z": 1.1323914871790868 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1311", "text": "Process", "data": { "Advisory_Notes": "Rules must be defined which means of tracking (GPS, regular update calls, stage related postings, etc.) are applied to which kind of transport (value based, customer based, product class based, etc.).", "KeyActivities": "Trigger corrective actions,\n Record actual status,\n Send alert,\n Monitor expected events and timelines,\n Receive unexpected events", "Type": "Business Process", "Description": "This process describes the monitoring of transportation of goods to the recipient and initiation of a response in case of deviations.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Monitoring of transportation status updates compared to plan. Issuing and tracking of corrective actions in case of deviations, and recording of updates.", "Outcome": "Current transport status is recorded in the system.", "GUID": "8a80f575-7e0d-11e5-0a66-001bc640cd9b", "name": "Monitor transportation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.802776656642339, "y": -0.1794019933554818, "z": 1.3904446721863595 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1313", "text": "Process", "data": { "Advisory_Notes": "Rules must be defined guiding the selection of carriers. These may consider load size, destination, route and means of transportation, transportation time, transport conditions (e.g. cold chain), compatibility of goods. Existing framework contracts may also be a criterion.", "KeyActivities": "Select and assign carrier ", "Type": "Business Process", "Description": "This process covers the assignment of transportation tasks to a suitable carrier and freight orders or shipments under consideration of case-specific constraints and costs.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Selection and assignment of carriers based on a set of rules.", "Outcome": "Carrier is selected and assigned.", "GUID": "348c88f8-7e10-11e5-0a66-001bc640cd9b", "name": "Select carrier", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.7719608670572375, "y": -0.17607973421926904, "z": 1.6384345422261655 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1315", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect drop-shipment transportation requests,\n Create freight order / freight booking,\n Simulate pack goods & build freight units ,\n Optimize loads & routing", "Type": "Business Process", "Description": "This process consolidates demands for drop shipments based on sales- and stock transfer orders, into shipments and freight orders for subsequently tendering carriers.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Creation of freight units and subsequent load optimization for definition of shipments and freight orders.", "Outcome": "Freight orders created.", "GUID": "106a8142-7e10-11e5-0a66-001bc640cd9b", "name": "Receive and process drop shipment transportation demand", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9268108515361844, "y": -0.1727574750830565, "z": 0.5360969524278273 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1317", "text": "Process", "data": { "Advisory_Notes": "Shipment order needs to be sent directly to the carrier in order for freight booking and confirmation must be received. The following questions need to be answered: ***Who receives the order information on shipper and carrier side? ***How are the documents received (EDI, Email etc.)? ***What information is required? ***Who communicates with the carrier?", "KeyActivities": "Dispatch freight order / freight booking,\n Receive booking confirmation from carrier,\n Update freight booking,\n Enter location of pick-up and time of pick-up,\n Calculate transportation charges,\n Transportation cost posting", "Type": "Business Process", "Description": "This process is required for the actual booking of a transport and recording of the confirmation by the carrier.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "This process includes the booking of a transport with required information like pick-up location and time and receiving the booking confirmation from the carrier.", "Outcome": "Booking of carrier and receipt of confirmation.", "GUID": "106a8148-7e10-11e5-0a66-001bc640cd9b", "name": "Book and confirm carrier", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.8943734099549103, "y": -0.16943521594684396, "z": 0.7890516863590018 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1321", "text": "Process", "data": { "Advisory_Notes": "Minimum Shipping documentation: ***Truck: Bill of Lading (BOL), Master Bill of Lading (MBOL) ***Air: Airway Bill (AWB), House Way Bill (HWB) ***Sea: Bill of Lading (BOL) ***Parcel: Carrier compliant parcel labels", "KeyActivities": "Communicate shipping documents to involved parties,\n Process customs clearance,\n Receive shipping document,\n Update shipping document", "Type": "Business Process", "Description": "This process describes the handling of shipping documents and related customs interactions in case of international trade.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Alignment of shipping documents with carrier, submission to customs for clearance.", "Outcome": "Shipment is customs cleared and ready for pickup.", "GUID": "94126c6a-7e10-11e5-0a66-001bc640cd9b", "name": "Prepare and communicate transportation documents", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.864602291022192, "y": -0.1661129568106312, "z": 1.0319152737633184 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1323", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Simulate pack goods & build freight units ,\n Optimize loads & routing,\n Create freight order / freight booking", "Type": "Business Process", "Description": "This process consolidates demands for transportation, sales- and stock transfer orders, into shipments and freight orders, or freight bookings for subsequently tendering carriers. Freight orders capture all information required for transportation planning by the shipper (sender) and transportation execution.They are a combination of shipments, which can be assigned to specific legs of the transport and/or carriers. The combination is based on transportation planning or transportation charges calculation. Freight orders can be created directly or as part of transportation order based or delivery based planning. Freight bookings, in contrast, are used to book freight space in advance, for example, with a shipping company. Transportation execution can then happen on the same documents. Freight orders and freight bookings also form the basis for track & trace activities, event management and reporting.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Creation of freight units and subsequent load optimization for definition of shipments and freight orders/freight bookings.", "Outcome": "Freight order/freight booking created.", "GUID": "94126c64-7e10-11e5-0a66-001bc640cd9b", "name": "Receive and process transportation demand", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.837418485287126, "y": -0.16279069767441867, "z": 1.264666911958404 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1328", "text": "Process", "data": { "Advisory_Notes": "***it needs to be defined which events will trigger the adjustment of schedule or even feedback to production planning.", "KeyActivities": "Monitor status and milestones of productions,\n Identify issues and deviations from schedule,\n Trigger resolution on shopfloor,\n Involve scheduling in resolution,\n Ensure timely completion posting", "Type": "Business Process", "Description": "The actual production progress is monitored.", "hasAssignment": true, "Process_Group": "Production Operations", "Scope": "After orders have been released to production the actual progress needs to be monitored. In case of any special events or deviations follow-up activities as well as counter-measures need to be triggered. Most important is the update of the production schedule and information/feedback to production planning in case of need.", "Outcome": "Actual production progress is monitored and appropriate reactions are triggered.", "GUID": "0f289faf-974c-11e9-0cfc-001bc641ce4f", "name": "Monitor production progress", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.812742839508603, "y": -0.15946843853820591, "z": 1.4872863482670244 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1330", "text": "Process", "data": { "Advisory_Notes": "The supply demand references a specific scheduling agreement for specific components. The following questions need to be answered: ***Who is the recipient for the demand information? ***How are the documents submitted (EDI, Email etc.)? ***What information is required? ***Who communicates with the vendor?", "KeyActivities": "Identify materials on bill of materials (BOM),\n Send materials for staging to vendor", "Type": "Business Process", "Description": "When a request for materials is received from production, relevant information must be forwarded to a designated vendor. This ensures that the required material is available in the stated quantity and on the specified date.", "Process_Group": "Procurement Planning", "hasAssignment": true, "Scope": "Material is requested from a vendor with specified quantities and dates and reference to a scheduling agreement.", "Outcome": "The supply demand is received by the vendor.", "GUID": "8df4fb95-7e0f-11e5-0a66-001bc640cd9b", "name": "Receive production supply demand and provide to vendor", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9401417314985892, "y": -0.15614617940199338, "z": 0.485643965985017 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1332", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Perform goods receipt from vendor,\n Trigger action for missing pick items,\n Confirm staging completion,\n Material consumption posting", "Type": "Business Process", "Description": "The vendor provided goods are delivered directly to the staging area without prior warehousing. Goods receipt is posted against a production storage location or directly against a production order. Unloading and transfer to staging may be facilitated by carrier or warehouse staff and may involve quality management (QM) procedures. Typically, QM will have been performed by the supplier in this integrated scenario.", "Process_Group": "Internal Logistics", "hasAssignment": true, "Scope": "Transfer of unloaded goods to production staging, goods receipt and goods issue.", "Outcome": "Material is available for production.", "GUID": "8df4fb9e-7e0f-11e5-0a66-001bc640cd9b", "name": "Execute production staging directly from vendor", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.913974519043757, "y": -0.15282392026578062, "z": 0.7132688850382478 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1334", "text": "Process", "data": { "Advisory_Notes": "It must be defined which checks and additional tasks (e.g. cleaning) shall be performed for which kind of vehicles and goods, and what data shall be recorded.", "KeyActivities": "Check out truck from companys premises,\n Check drivers identification details,\n Perform exit checks,\n Check proof of delivery paperwork from WM", "Type": "Business Process", "Description": "In this process the truck about to leave the site and its driver are checked. This includes the de-registering procedure (e.g. capturing drivers name and license plate, check of loading documents, load securing and seals, or if truck must be empty).", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Check of driver and vehicle identity against transport documentation.", "Outcome": "Vehicle and persons leaving the site have been de-registered. Authorisation for moving goods off the site has been checked.", "GUID": "8b5b772a-7caa-11e5-0a66-001bc640cd9b", "name": "Check-out delivery truck", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.8902094435881023, "y": -0.1495016611295681, "z": 0.9307365282495083 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1336", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Bundle inbound delivery relevant documents", "Type": "Business Process", "Description": "This process contains the planning of inbound warehouse activities related to either vendor deliveries or customer returns.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "The inbound receipt schedule includes information on shipment of goods and additional information related to the shipment, such as order information, product description, physical characteristics, type of packaging, markings, carrier information, and configuration of goods within the transportation equipment.", "Outcome": "Inbound receipt schedule is current and comprehensive.", "GUID": "8710390a-7caa-11e5-0a66-001bc640cd9b", "name": "Update inbound receipt schedule", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.868766979833684, "y": -0.14617940199335555, "z": 1.1380281613743914 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1338", "text": "Process", "data": { "Advisory_Notes": "The forecast delivery schedule must be submitted to the vendor in regular intervals defined by a scheduling agreement for specific components. The following questions need to be answered: ***Who is the recipient for the forecast information? ***How are the documents submitted (EDI, Email etc.)? ***What information is required? ***Who communicates with the vendor?", "KeyActivities": "Update delivery quantities,\n Update delivery dates,\n Create forecast delivery,\n Load vendor forecast delivery schedule", "Type": "Business Process", "Description": "The process describes the maintenance of the forecast delivery schedule containing requirements concerning delivery quantities and dates for regularly purchased material from a vendor. The forecast is transmitted to the vendor for incorporation into their planning.", "Process_Group": "Procurement Planning", "hasAssignment": true, "Scope": "Create forecast delivery schedule and transmit to vendor.", "Outcome": "The current forecast delivery schedule is submitted to the vendor.", "GUID": "59938f35-7e0f-11e5-0a66-001bc640cd9b", "name": "Create forecast delivery schedule and provide to vendor", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.849567473090942, "y": -0.1428571428571428, "z": 1.335125603737887 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1340", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Assign truck to shipment,\n Register driver and vehicle,\n Assign yard and door,\n Check daily inbound delivery,\n Set check in status,\n Check detailed daily dispatch,\n Perform site entry checks", "Type": "Business Process", "Description": "In this process a truck about to enter the site and its driver are checked for suitability, e.g. purpose for entering the site, state of the vehicle. This includes the registering procedure (e.g. capturing drivers name and license plate).", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Alignment of transportation planning and actual vehicle movements in addition to site entry controls for trucks.", "Outcome": "Vehicle and persons entering the site have been registered and considered suitable to fulfill their pick-up or delivery task. Driving route and unloading/pick-up location have been communicated and the recipient at the (un-) loading location has been informed.", "GUID": "057b285c-7caa-11e5-0a66-001bc640cd9b", "name": "Check-in truck", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9521517551118541, "y": -0.13953488372093026, "z": 0.4348603511631145 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1342", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Perform visual check,\n Select inbound delivery,\n Grant permission to unload,\n Check bill of lading paperwork,\n Unload goods,\n Maintain batch,\n Determine required exception handling,\n Trigger action in procurement,\n Trigger action in quality,\n Create inbound delivery", "Type": "Business Process", "Description": "During unloading, a first verification of goods is supported by label scanners or radio frequency scanners. Labels are agreed between the supplier and the receiving party before shipment. A paper-based variant of the process must be possible for exceptional cases.", "Process_Group": "Internal Logistics", "hasAssignment": true, "Scope": "Goods are unloaded and compared against the shipping documents. A first visual check is performed.", "Outcome": "Goods are unloaded and available for goods receipt.", "GUID": "768b35c4-d4a1-11eb-2c3e-001bc641ce4f", "name": "Unload goods", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9315917824772977, "y": -0.1362126245847175, "z": 0.6370004873715409 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1348", "text": "Process", "data": { "Advisory_Notes": "The segregation of staging for production and actual posting of the GI of the components can differ depending on the physical and organizational set-up as well as on the required transparency on the material flow.", "KeyActivities": "Post goods issue for components used in production,\n Material consumption posting", "Type": "Business Process", "Description": "Goods issue for materials and components used within the production process have to be posted after delivery and when they are moved from the warehouse for further processing.", "hasAssignment": true, "Process_Group": "Outbound Delivery Management", "Scope": "Goods issues are performed for materials and components retrieved from stock used in the respective production step. Some stock materials might be exempt and later be posted in the cause of a backflushing process.", "Outcome": "Goods issue is posted.", "GUID": "baf08434-7f1a-11e5-0a66-001bc640cd9b", "name": "Perform goods issue of components for production", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.913168125807942, "y": -0.13289036544850497, "z": 0.8289241335374175 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1350", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Place material in destined storage location,\n Save & confirm transfer order", "Type": "Business Process", "Description": "The transfer order is a document used in the warehouse management (WM) system that contains all the information needed to carry out the physical movement of material into the warehouse, out of the warehouse or from one storage place to another within the warehouse. Transfer can also occur to a production staging area or loading bay. Confirmation can happen manually, automatically, or by scanning.", "hasAssignment": true, "Process_Group": "Warehouse Operations", "Scope": "Verification of materials at storage location, confirmation of transfer order in system.", "Outcome": "Transfer order has been confirmed. Material is available at the recorded storage location.", "GUID": "d9267281-e82f-11e4-0a66-001bc640cd9b", "name": "Save and confirm transfer order", "Business_Rules": "It must be defined which stock movements shall require confirmation.", "Prerequisite": "" }, "position": { "x": -4.896800798099956, "y": -0.12956810631229243, "z": 1.0106146366086524 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1352", "text": "Process", "data": { "Advisory_Notes": "Picking items can be sorted to optimize the picking distance / resources Deviations from picking quantities require adaptations in the delivery item. It is possible to cover pick and pack combined in an automated procedure.", "KeyActivities": "Pick material,\n Confirm picking completion,\n Scan storage bin ID,\n Print/ generate picking list,\n Scan label and capture quantity,\n Trigger action for missing pick items,\n Outbound activities posting", "Type": "Business Process", "Description": "The process describes picking of goods from a warehouse for delivery to a staging area of production workstation.", "Process_Group": "Warehouse Operations", "hasAssignment": true, "Scope": "The process includes the creation of transfer order, picking and confirmation of picked items.", "Outcome": "Items for delivery have been picked.", "GUID": "7e8a0fc2-7e0d-11e5-0a66-001bc640cd9b", "name": "Perform pick for production staging", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.8824096974445546, "y": -0.12624584717607967, "z": 1.182055900289942 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1354", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create transfer requirement,\n Convert transfer requirement into transfer order", "Type": "Business Process", "Description": "Production staging makes warehouse managed materials available within a supply area close to the consuming production workstation. This happens with reference to a production order. Goods issue posting to the process order typically is done when the materials are taken from the staging area to be consumed during production. In cases when the consumed quantity is known only after production goods issue posting is possible after confirming the process order.", "Process_Group": "Internal Logistics", "hasAssignment": true, "Scope": "Creation of transfer requirement based on production order(s), transformation into transfer order, movement of materials from warehouse to staging area.", "Outcome": "Transfer order for picking is created.", "GUID": "05d0f3bb-7e0e-11e5-0a66-001bc640cd9b", "name": "Initiate production staging and create transfer order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.962832745903258, "y": -0.12292358803986714, "z": 0.38378068165278495 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1359", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Assign transportation carrier,\n Assign transportation method,\n Assign shipping lanes,\n Record transportation rates and conditions", "Type": "Business Process", "Description": "Transportation lanes are used for planning distribution and procurement between different locations. This simplifies transportation planning of recurring complex or high volume transportation requirements. Awarding lanes complements the remaining vendor negotiations.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Once the carrier and method of transportation have been documented, transportation lanes are awarded to selected carriers. Subsequently, the rates and conditions of transportation are recorded.", "Outcome": "Transportation lane awarded to carrier.", "GUID": "ec357bb0-7e11-11e5-0a66-001bc640cd9b", "name": "Award lanes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.94721320635123, "y": -0.11960132890365438, "z": 0.5602984171929293 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1361", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Submit requirements to vendors for quotation", "Type": "Business Process", "Description": "Requests For Quotation (RFQ) is sent to potential transportation suppliers, i.e. carriers. It contains a description of all relevant parameters of the required transportation services, such as: ***Transportation lanes ***Quantities/Volumes ***Delivery requirements (e.g. cold chain, hazardous goods) ***Other value added requirements or terms ***Term (duration) of contract ***Terms and conditions", "hasAssignment": true, "Process_Group": "Transportation Management", "Scope": "The RFQ is created and submitted to potential vendors.", "Outcome": "Defined requirement submitted to vendors.", "GUID": "ec357bc2-7e11-11e5-0a66-001bc640cd9b", "name": "Request quote for transport sourcing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9334627073178643, "y": -0.11627906976744184, "z": 0.7265474039177462 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1363", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create and update order-/delivery based transportation requirements,\n Convert transportation requirements into freight orders", "Type": "Business Process", "Description": "Transportation requirements are deduced from different orders in the ERP system (e.g. sales orders, purchase orders, and stock transport orders, as well as the corresponding returns orders for each order type). Depending on the time scale considered either actual, planned or projected transportation requirements can be formulated. Data summarized include: materials, volumes, dates, pick-up locations and recipients, transport routes and conditions, etc.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "This process includes the assessment of orders and translation into transportation requirements.", "Outcome": "Transportation requirements defined.", "GUID": "ec357baa-7e11-11e5-0a66-001bc640cd9b", "name": "Gather transportation requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.921500854548913, "y": -0.11295681063122931, "z": 0.8825130813049241 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1365", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Analyze current proposals,\n Compare past transportation performance,\n Trigger transportation negotiations", "Type": "Business Process", "Description": "Based on the available information (e.g. proposal, past performance, market intelligence) and binding price quote from several carriers a preliminary assignment of suppliers to specific lanes is made and optimized. Individual carrier may only be awarded particular subset of lanes covered within a bidding and selection process. Subsequent negotiations are based on these prices and lane assignments.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Analyze current proposals and quotes against past performance and provisionally assign transportation lanes.", "Outcome": "Carrier proposed for negotiations.", "GUID": "abfff400-7e11-11e5-0a66-001bc640cd9b", "name": "Evaluate carrier responses", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.911247153450079, "y": -0.10963455149501655, "z": 1.028181448397289 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1367", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Plan inbound deliveries,\n Plan warehouse resources", "Type": "Business Process", "Description": "The shipping schedule outlines the overall expected quantity of the material(s) to be shipped over a specific period of time. It is used to plan activities in the warehouse and as a reference point for site access controls.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "The shipping schedule specifies the carriers and associated lanes with the expected transportation volumes and shipping days, pick-up window, laycan, etc.", "Outcome": "Shipping schedules updated.", "GUID": "ec357bc8-7e11-11e5-0a66-001bc640cd9b", "name": "Update shipping schedules", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9721774322110075, "y": -0.10631229235880402, "z": 0.3324397326999237 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1372", "text": "Process", "data": { "Advisory_Notes": "This scenario does not apply when Transportation Management is used.", "KeyActivities": "Create shipment cost document,\n Calculate shipment cost,\n Add shipment cost manually,\n Determine ??shipment cost account,\n Set status transfer,\n Allocate shipment cost,\n Trigger follow up action with carrier", "Type": "Business Process", "Description": "In this process the shipment costs will be captured based on incoming carrier-provided information and subject to proof of delivery. G/L account determination takes place during the cost determination of the respective service order representing shipment cost. Actual costs will be settled for each creditor included in the shipment cost document on item level.", "Process_Group": "Overhead Cost Controlling", "hasAssignment": true, "Scope": "Creation of shipment cost document, cost calculation and allocation.", "Outcome": "Shipment cost document has been updated.", "GUID": "3cd87de3-e831-11e4-0a66-001bc640cd9b", "name": "Settle freight cost", "Business_Rules": "Cost allocation rules must be maintained.", "Prerequisite": "" }, "position": { "x": -2.960828155536908, "y": -0.10299003322259126, "z": 0.4832148935824642 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1374", "text": "Process", "data": { "Advisory_Notes": "Proof of delivery is exclusively an instrument for confirmation of external customers deliveries.", "KeyActivities": "Receive proof of delivery from ship-to-party", "Type": "Business Process", "Description": "Proof of delivery (POD) is the confirmation sent by the Ship to party upon the receipt of goods. The ship-to party transfers the proof of delivery in the System via IDoc. This way, quantities are confirmed once for the entire delivery.", "Process_Group": "Outbound Delivery Management", "hasAssignment": true, "Scope": "Receipt of POD from ship-to party, processing of discrepancies as required, confirmation of POD to goods recipient.", "Outcome": "POD confirmed.", "GUID": "f4301854-7e0f-11e5-0a66-001bc640cd9b", "name": "Receive and process proof of delivery", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9510793714845764, "y": -0.09966777408637872, "z": 0.6236760378826854 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1378", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The external service provider conducts freight settlement services and forwards information about distribution of transportation costs. Freight cost settlement allows the assignment and forwarding of the shipment costs to FI and cost accounting.", "Process_Group": "Transportation Management", "Scope": "The freight costs are calculated based on freight agreements with predefined rates and tariffs and scales for inhouse calculation. Furthermore G/L account determination takes place during the cost determination and the transfer to FICO will be triggered by a transfer procedure with Service PO and service entry sheet creation for each creditor which will be included in the freight charge document on item level. ", "Outcome": "Service provider provides freight cost distribution data.", "GUID": "a703ec87-94af-11e8-2ddf-001bc640cd9b", "name": "Conduct freight settlement services", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.942850333282085, "y": -0.09634551495016619, "z": 0.7538107075209188 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1382", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Monitor waste disposal,\n Dispose waste,\n Record external disposal operations ,\n Compile waste disposal documents ", "Type": "Business Process", "Description": "Disposal is executed according to legal guidelines and waste management requirements.", "Process_Group": "Healthy, Safety and Environment", "hasAssignment": true, "Scope": "Record the necessary external disposal operations and put together the legally required waste disposal documents such as waste manifests, dock receipts on the basis of the internal disposal documents. Execute the disposal and confirm completion.", "Outcome": "Disposal of waste is confirmed.", "GUID": "ff0fe25a-7ef0-11e5-0a66-001bc640cd9b", "name": "Execute waste disposal", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.9360602084506615, "y": -0.09302325581395343, "z": 0.8736070064100289 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1384", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check for overdue disposal documents,\n Send out reminders for waste disposal documents,\n Adjust permitted waste quantities based on waste approvals,\n Block waste approvals if permitted quantity is reached.", "Type": "Business Process", "Description": "This process ensures receipt of the return copies of disposal documents within the set periods.", "Process_Group": "Healthy, Safety and Environment", "hasAssignment": true, "Scope": "Generate list of the disposal documents whose return within period is soon to expire. For example, as soon as the disposer has sent the return copies and informed of the waste quantity disposed. Adjust the waste quantity that can still be disposed of with the corresponding waste approval. Lock waste approvals which have reached their permitted quantity.", "Outcome": "Waste disposal documents returned and up to date.", "GUID": "12bafa91-7ef1-11e5-0a66-001bc640cd9b", "name": "Monitor disposal and document return", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9801794521348148, "y": -0.0897009966777409, "z": 0.28087245743052897 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1386", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review and document physical (chemical) properties of waste,\n Specify safety and transport information,\n Specify required waste disposal documents,\n Capture legal data for waste,\n Evaluate waste management requirements", "Type": "Business Process", "Description": "In waste management, it is necessary to comply with and implement numerous national and international laws and regulations. This business process makes the classification of waste possible and the evaluation of waste management requirements.", "Process_Group": "Healthy, Safety and Environment", "hasAssignment": true, "Scope": "Including the waste specifications, the requirements for handling, disposal, approval and documentation of waste is specified.This includes physical-chemical properties, safety and transport information and legal data for waste.", "Outcome": "Waste classification and requirements evaluation are complete.", "GUID": "12bafa97-7ef1-11e5-0a66-001bc640cd9b", "name": "Classify waste and evaluate waste management requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9724273609217797, "y": -0.08637873754152814, "z": 0.4058023953152382 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1388", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create master data for waste management,\n Plan resources for waste disposal,\n Capture waste material and quantity,\n Assign to plant,\n cost center or storage location,\n Trigger service procurement for waste disposal,\n Inform EHS about waste disposal", "Type": "Business Process", "Description": "This process covers the creation of the master data required for waste management, including waste generators, points of generation, waste disposers, disposal facilities, waste transporters, authorities and waste. In cases where waste disposal is to be executed by a service provided, preparation of waste disposal will trigger the procurement process for disposal services.", "hasAssignment": true, "Process_Group": "Compliance Master Data", "Scope": "To describe the waste, waste materials can be created in the system with the logistic properties of the waste and waste specifications with the properties of ingredients, catalog numbers and process codes. The waste may be assigned to plant, cost centers, storage locations or the vendor.", "Outcome": "Waste master data is created and the waste execution is triggered.", "GUID": "12bafa9a-7ef1-11e5-0a66-001bc640cd9b", "name": "Create waste master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.966006124811759, "y": -0.0830564784053156, "z": 0.5203800706749013 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1392", "text": "Process", "data": { "Advisory_Notes": "The goods issue posting can be reflected in a simplified warehouse management setup or purely on inventory management level.", "Type": "Business Process", "Description": "After the goods issue has been recorded in the third-party Warehouse Management System (WMS), the data gets transferred and posted to reflect the inventory movement in the own system.", "Process_Group": "Outbound Delivery Management", "Scope": "Goods issue posting at the company level.", "Outcome": "Goods issue is posted at the company level.", "GUID": "82cfedad-9829-11ee-3781-0201b014c5b2", "name": "Transfer goods issue posting from third-party logistics provider", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.960834699487871, "y": -0.07973421926910307, "z": 0.6245951363540041 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1393", "text": "Process", "data": { "Advisory_Notes": "Dealing with delivery creation the legal requirements in the country of operations must be considered - some countries do not permit a sales order to be broken up into more than one delivery, and likewise they may not permit more than one sales document to be combined into one delivery. When creating an outbound delivery without reference, the ship-to-party and the material information must be entered manually. This is typically only used if the orders are processed by another system and ideally they are not created manually but rather via an interface.", "KeyActivities": "Trigger follow-up action with sales,\n Determine batch,\n Create outbound delivery document,\n Check availability to promise for delivery", "Type": "Business Process", "Description": "An outbound delivery is usually created with reference to another document (sales order, purchase order, stock transport order). Outbound deliveries can only be created for orders, which are due to delivery (material availability date or the transportation scheduling date is reached) - e.g. delivery is created 3 days before planned ship-out. Deliveries can not be created for orders, which are blocked e.g. sales order blocked due to exceeded credit limit.", "hasAssignment": true, "Process_Group": "Outbound Delivery Management", "Scope": "An outbound delivery is the central object of the goods issue process - all shipping activities including picking, packing, transportation and goods issue are initiated based on the outbound delivery.", "Outcome": "Outbound delivery document is created and shipping activities can be initiated.", "GUID": "768b35c0-d4a1-11eb-2c3e-001bc641ce4f", "name": "Create outbound delivery", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.956831969617957, "y": -0.07641196013289031, "z": 0.7184378092343531 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1395", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "After physically delivering goods to the customer or intercompany entity, the outbound delivery confirmation is received from the third-party logistics provider.", "Process_Group": "Outbound Delivery Management", "Scope": "Receiving outbound delivery confirmation.", "Outcome": "Outbound delivery confirmed.", "GUID": "82cfedb2-9829-11ee-3781-0201b014c5b2", "name": "Receive outbound delivery confirmation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9868333578671047, "y": -0.07308970099667778, "z": 0.2291139630544718 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1396", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The process covers picking of goods from a warehouse operated by a third-party for delivery to a customer or intercompany entity.", "Process_Group": "Warehouse Operations", "Scope": "The picking is typically recorded in the Warehouse Management System (WMS) of the third party.", "Outcome": "Goods are picked.", "GUID": "82cfeda0-9829-11ee-3781-0201b014c5b2", "name": "Perform pick in third-party WMS (External)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9820029257198377, "y": -0.06976744186046502, "z": 0.3281136251336224 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1397", "text": "Process", "data": { "Advisory_Notes": "The information necessary for labelling needs to be available in the third-party system.", "Type": "Business Process", "Description": "The process covers packing of goods. This whole process takes place in a warehouse operated by the third-party logistics provider.", "Process_Group": "Warehouse Operations", "Scope": "Physical packing of goods, and creation and labelling of handling units.", "Outcome": "Goods ready to be loaded.", "GUID": "82cfeda5-9829-11ee-3781-0201b014c5b2", "name": "Perform pack in third-party WMS (External)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9782328051052875, "y": -0.06644518272425248, "z": 0.4167298266072581 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1398", "text": "Process", "data": { "Advisory_Notes": "An availability check for delivery generation is recommended to determine whether the material situation has changed since the availability check was made for the sales order.", "Type": "Business Process", "Description": "Availability to promise check (ATP check) for delivery verifies whether goods included in the outbound delivery document are available on stock on the delivery date (or necessary ship-out date) and can be delivered.", "Process_Group": "Sales Order Management", "Scope": "Before sending the outbound delivery to warehouse for picking and initiating transportation it must be checked whether goods included in this outbound delivery are available on stock at picking date. If there are not enough goods, delivery is not sent to warehouse for fulfillment. Unlike other ATP checks, the check for delivery is typically performed only against physical stock on hand.", "Outcome": "Products required for delivery are available and outbound logistics can be initiated.", "GUID": "768b35ca-d4a1-11eb-2c3e-001bc641ce4f", "name": "Check availability to promise for delivery", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.97544170933692, "y": -0.06312292358803995, "z": 0.49495433828840407 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1401", "text": "Process", "data": { "Advisory_Notes": "The channel for providing the MSDS ist not legally defined. Best practice is to make MSDS available for download though a customer portal.", "KeyActivities": "Identify materials per position,\n Identify country and language of MSDS recipient,\n Create MSDS shipping request per material,\n Select MSDS for material,\n Trigger creation of MSDS,\n Bundle created MSDS,\n Provide MSDS to customer", "Type": "Business Process", "Description": "Provision of the Material Safety Data Sheet is a legal requirement in the context of risk communication for hazardous material. The distributor of hazardous material is obliged to inform the customer about the safety related data of a product. Carriers will require provision of a MSDS for transporting hazardous goods. The documents can be provided either as paper, e.g. as part of the shipment, or as an internet download.", "Process_Group": "Healthy, Safety and Environment", "hasAssignment": true, "Scope": "Determine country-language specific safety data sheet and check availability. Send safety data sheet to customer.", "Outcome": "Material safety data sheet has been provided to customer.", "GUID": "8a80f57e-7e0d-11e5-0a66-001bc640cd9b", "name": "Provide material safety data sheet (MSDS)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.973548295452828, "y": -0.05980066445182719, "z": 0.5627794966881982 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1403", "text": "Process", "data": { "Advisory_Notes": "The requirement and channel for ASN must be specified per recipient.", "KeyActivities": "Receive proof of delivery,\n Create advanced shipping notification,\n Send advanced shipping notification to customer", "Type": "Business Process", "Description": "This process describes the transport execution from leaving the enterprise grounds to receiving the eventual proof of delivery signed by the receiver which acts as service confirmation between sender and carrier.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Dispatching the shipment and delivery of goods to recipient. After associating the vehicle details with the delivery an Advance Shipping Notice is sent to the recipient.", "Outcome": "Recipient has been provided with Advance Shipping Note. Forwarder has received proof of delivery from recipient.", "GUID": "8a80f581-7e0d-11e5-0a66-001bc640cd9b", "name": "Execute shipment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9921346194019032, "y": -0.056478405315614655, "z": 0.1771994869643656 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1405", "text": "Process", "data": { "Advisory_Notes": "The Shipment loading process is optional and can be executed paper based or with a RF Scenario", "KeyActivities": "Set loading start status,\n Load truck,\n Set loading end status,\n Weigh loaded truck,\n Update delivery with actual weight,\n Confirm load", "Type": "Business Process", "Description": "The process describes the loading procedure for a shipment to ensure that all packages of a delivery are shipped to the Customer. This process also can be supported with RF technology.", "Process_Group": "Internal Logistics", "hasAssignment": true, "Scope": "Loading of vehicle and loading confirmation.", "Outcome": "Goods are loaded onto a shipment and are ready for goods issue.", "GUID": "7bf5a968-7e0d-11e5-0a66-001bc640cd9b", "name": "Load goods", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9895483308477835, "y": -0.0531561461794019, "z": 0.25020147386702807 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1407", "text": "Process", "data": { "Advisory_Notes": "It is possible to cover pick and pack combined in an automated procedure.", "KeyActivities": "Perform physical pack of materials,\n Print carton labels and pack list,\n Apply labels,\n Identify and prepare packaging materials,\n Record packing activities,\n Outbound activities posting", "Type": "Business Process", "Description": "Materials together with packing materials are packed into handling units suitable for loading and transport. Handling units can be nested (e.g. carton, pallet, container).", "Process_Group": "Warehouse Operations", "hasAssignment": true, "Scope": "In this process the physical packing of materials, creation of handling units and labelling of the packages is invovled.", "Outcome": "Goods ready to be loaded.", "GUID": "7bf5a959-7e0d-11e5-0a66-001bc640cd9b", "name": "Perform pack", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9877510883916956, "y": -0.04983388704318936, "z": 0.31279587118574304 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1409", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes a non-physical movement of sold stock to valuated stock in transit to retain the ownership of goods until the goods are delivered to the customer. This will decrease the quantity of the unrestricted inventory, but the total inventory value remains unchanged. Goods that are transferred to the valuated stock in transit cannot be used for other purposes.", "Process_Group": "Outbound Delivery Management", "Scope": "Non-physical stock transfer from unrestricted stock to valuated stock in transit is executed.", "Outcome": "Sold goods transferred from physical stock to valuated stock in transit.", "GUID": "5bdd3986-94cf-11ee-3781-0201b014c5b2", "name": "Perform stock transfer from physical stock to valuated stock in transit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.986661418317758, "y": -0.04651162790697683, "z": 0.36497657330454003 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1410", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When goods in transit are physically delivered to the customer, the goods issue must be posted in the system to reflect the change of ownership from the company to the customer. This reduces the total value of inventory owned by the company.", "Process_Group": "Outbound Delivery Management", "Scope": "This is a stock movement from valuated stock in transit to goods issue, while acknowledging the physical movement of the goods to customer.", "Outcome": "Goods issue posted.", "GUID": "5bdd3990-94cf-11ee-3781-0201b014c5b2", "name": "Post goods issue from valuated stock in transit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.986197805412938, "y": -0.04318936877076407, "z": 0.4067380415812173 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1411", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Pick material,\n Create transfer order (TO),\n Transfer data to delivery,\n Confirm picking completion,\n Scan storage bin ID,\n Print/ generate picking list,\n Scan label and capture quantity,\n Trigger action for missing pick items,\n Outbound activities posting", "Type": "Business Process", "Description": "The process describes picking of goods from a warehouse for delivery to a customer or intercompany.", "hasAssignment": true, "Process_Group": "Warehouse Operations", "Scope": "A picking list which is created in this process is enriched with additional information, e.g. the ID of the storage bin, quantity, etc. and will be transfered to delivery.", "Outcome": "Material is picked and ready for delivery.", "GUID": "e50fe5ce-6e30-11e8-2ddf-001bc640cd9b", "name": "Perform pick for outbound logistics", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9960796276188855, "y": -0.039867109634551534, "z": 0.1251643727458075 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1415", "text": "Process", "data": { "Advisory_Notes": "The goods issue posting does not necessarily require prior creation of shipment and loading.", "KeyActivities": "Print customs documents,\n Print transport documents,\n Post goods issue for samples,\n Post goods issue for stock items,\n COGS posting,\n Inventory reduction posting,\n Sample related cost posting,\n Event-based revenue recognition posting", "Type": "Business Process", "Description": "In this process the shipment documents are prepared and the goods issue gets posted. In some cases shipment documents may have to be printed in advance to be included in the packaging.", "Process_Group": "Outbound Delivery Management", "hasAssignment": true, "Scope": "Goods issue posting and printing of transport documents are invovled in this process.", "Outcome": "Goods issue posted and shipment ready for dispatch.", "GUID": "7e8a0fce-7e0d-11e5-0a66-001bc640cd9b", "name": "Perform goods issue from stock", "Business_Rules": "For event-based revenue recognition, when a goods issue is posted for sale from stock, revenue is automatically calculated based on the quantity delivered, accrued revenue is posted, and costs of goods sold are matched with revenues.", "Prerequisite": "" }, "position": { "x": -2.995058439363243, "y": -0.03654485049833878, "z": 0.17211898442360946 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1420", "text": "Process", "data": { "Advisory_Notes": "SAP Ariba integration: once the purchased materials are delivered to the requesting department a GR is created in Ariba and a notification on it is sent to the supplier and also to the own ERP system. After verification and check of the materials for correct type/product, correct quantity, and correct cost allocation and triggering any necessary put-away actions, the GR is confirmed. The confirmation is then transferred back to Ariba. Procedures for the visual check of received goods must be established including guidelines for exception handling of damaged or missing items or excess items. Verification of goods for goods receipt is supported by label scanners or radio frequency scanners. Labels must be agreed between the supplier and the receiving party before shipment. A paper-based variant of the process must be possible for exceptional cases.", "KeyActivities": "Check goods,\n Determine required exception handling,\n Trigger action in procurement,\n Trigger action in quality,\n Post goods receipt,\n Store goods in warehouse,\n Post stock differences,\n Accounts payable posting,\n Inventory increase (procurement) posting,\n Goods receipt/ invoice receipt clearing account posting", "Type": "Business Process", "Description": "In this process goods are checked to ensure quantity, quality, and items match. After checking goods, the goods receipt posting is performed thus triggering an update in inventory levels and accounts payable postings. Finally, the goods are stored in an interim storage location and final putaway is triggered.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "Goods receipt for received goods is posted and paper documentation is created as required.", "Outcome": "Goods receipt material document created, as required in addition goods receipt slip.", "GUID": "871038f8-7caa-11e5-0a66-001bc640cd9b", "name": "Perform goods receipt of stock items", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9945544945851688, "y": -0.03322259136212624, "z": 0.20864896306817682 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1424", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is triggered by process order for mixing. It describes the physical blending of new and original batches within a specified main tank.", "Process_Group": "Production Operations", "Scope": "This process involves preparation of the main tank and new batch for mixing, performing the actual mixing of the batches and executing process order for mixing.", "Outcome": "Original and new batches mixed resulting in a new blended batch.", "GUID": "df10d3e0-8d0c-11ee-3781-0201b014c5b2", "name": "Perform mixing of original batch and new batch into main tank", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.99448618800707, "y": -0.029900332225913706, "z": 0.23475033079126958 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1425", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Once it is confirmed that the new batch meets the quality standards, it is prepared for transfer to the main tank. Typically, there are some residuals in the tank, which require mixing of the new batch with the original one. This requires creating a process order for mixing to blend the batches.", "Process_Group": "Production Scheduling", "Scope": "This process involves creating a process order for mixing the two batches of the day tank and the main tank.", "Outcome": "Process order for mixing created.", "GUID": "df10d3dc-8d0c-11ee-3781-0201b014c5b2", "name": "Create process order for mixing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.994771887660672, "y": -0.02657807308970095, "z": 0.25041967756807915 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1426", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the goods receipt posting of newly delivered batch of tank material. To enable storing a new batch in a main tank, it must be first assigned to a virtual day tank to ensure quality inspections and further mixing with the residual batch.", "Process_Group": "Inbound Delivery Management", "Scope": "The process covers assigning the new batch to a virtual day tank to enable quality inspection prior to mixing of the new batch with residuals of an existing batch. By assigning the new batch to the virtual day tank, goods receipt is posted.", "Outcome": "Goods receipt posted into a virtual day tank.", "GUID": "df10d3d7-8d0c-11ee-3781-0201b014c5b2", "name": "Post goods receipt of new batch into a day tank", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9986656967404788, "y": -0.023255813953488413, "z": 0.07304404611531826 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1429", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Plan incoming deliveries,\n Evaluate cross-docking options,\n Confirm cross-docking operations", "Type": "Business Process", "Description": "This process describes the planning of cross-docking elements including planning of incoming shipments and outgoing shipping requirements. This procedure can reduce material handling costs, labour and time. Furthermore this process enables the warehouse to map inbound delivery documents to outbound deliveries which results in the reduction of storing in the warehouse.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "For cross-docking logistics, it is required to plan and align incoming supply with outgoing demand requirements.", "Outcome": "Incoming and outgoing transfers and deliveries planned.", "GUID": "7eaea9a9-9ee7-11e8-2ddf-001bc640cd9b", "name": "Plan cross-docking", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9985294999620216, "y": -0.019933554817275656, "z": 0.09391931567844582 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1431", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Pick material,\n Confirm picking completion,\n Print/ generate picking list,\n Scan label and capture quantity,\n Trigger action for missing pick items,\n Scan picking storage location,\n Outbound activities posting", "Type": "Business Process", "Description": "The cross-docking picking process involves taking goods for cross docking staging at the right quantity.", "hasAssignment": true, "Process_Group": "Warehouse Operations", "Scope": "For cross-docking transfer of materials, it is necessary to specify which materials to pick and the storage location where to find the materials.", "Outcome": "Goods picked from inbound picking location.", "GUID": "7eaea9c0-9ee7-11e8-2ddf-001bc640cd9b", "name": "Pick goods for cross-docking", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9986383918992146, "y": -0.01661129568106312, "z": 0.1043600058914436 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1433", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Print customs documents,\n Print transport documents,\n Post goods issue for cross-docking,\n COGS posting,\n Inventory reduction posting", "Type": "Business Process", "Description": "This process describes issuing the goods to an outbound delivery for cross-docking. In some cases shipment documents may have to be printed in advance to be included in the packaging.", "Process_Group": "Outbound Delivery Management", "hasAssignment": true, "Scope": "The goods issue posting is performed including printing of transport documents.", "Outcome": "Goods issue for cross-docking posted.", "GUID": "e5a63124-9eea-11e8-2ddf-001bc640cd9b", "name": "Perform goods issue for cross-docking", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.998910691269956, "y": -0.013289036544850585, "z": 0.10436426930196543 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1435", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Scan material / package label,\n Post goods receipt for cross-docking,\n Inventory increase (procurement) posting", "Type": "Business Process", "Description": "This process describes the goods receipt from inbound deliveries needing to be directly processed via cross-docking to outbound deliveries.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "Materials, goods or finished goods that are arriving at an inbound dock and directly needing to be shipped outbound.", "Outcome": "Goods receipt is performed and transfer order can be created.", "GUID": "7eaea9b3-9ee7-11e8-2ddf-001bc640cd9b", "name": "Perform goods receipt to inbound delivery for cross-docking", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.999264704926107, "y": -0.009966777408637828, "z": 0.0939308268241546 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1439", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes transmission of data on incoming shipments to an external warehouse management system (WMS). This process is crucial for preparation of warehouse operations ensuring timely and accurate handling of goods within the warehouse or automation of process steps.", "Process_Group": "Inbound Delivery Management", "Scope": "The ?scope ?ranges ?from ?minimal ?information ?on ?inbound ?delivery ?data ?to ?extensive ?logistics ?data, ?necessary ?for ?this ?efficient ?organizing ?of ?inbound. ?", "Outcome": "Inbound data transferred to third party WMS.", "GUID": "7dee7aa0-8792-11ee-3781-0201b014c5b2", "name": "Transfer expected inbound data to third-party WMS", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9998910661603502, "y": -0.006644518272425293, "z": 0.02087399080237667 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1440", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes recording and updating the arrival of goods within an external warehouse management system (WMS). By accurately documenting the incoming goods in the third-party WMS, organizations can maintain real-time visibility of their inventory, optimize storage space, and facilitate efficient order fulfillment processes.", "Process_Group": "Inbound Delivery Management", "Scope": "This process includes tasks such as verifying the received items against the purchase orders, updating inventory levels, and assigning storage locations within the warehouse.", "Outcome": "Incoming goods processed and documented in third-party WMS.", "GUID": "7deea1b1-8792-11ee-3781-0201b014c5b2", "name": "Receive goods in third-party WMS", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9999591495320046, "y": -0.0033222591362125353, "z": 0.01565570628275817 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1443", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When goods in transit are physically received into the plant, the physical goods receipt must be acknowledged in the system. This ensures that the goods are moved from the valuated stock in transit to physical stock. While this does not impact the inventory value, the inventory quantity is updated.", "Process_Group": "Inbound Delivery Management", "Scope": "Create and execute a non-physical stock transfer from valuated stock in transit to physical stock in inventory.", "Outcome": "Inventory value and inventory quantity matched.", "GUID": "57851757-943d-11ee-3781-0201b014c5b2", "name": "Perform stock transfer from valuated stock in transit to physical stock", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.0, "y": 0.0, "z": 4.898587196589413e-16 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1444", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes acknowledging the ownership of purchased goods in inventory even though the goods have not yet been physically received. This will update the inventory value, but the inventory will not be updated in terms of quantity until the goods are physically received. Goods that are received in valuated stock in transit cannot be used.", "Process_Group": "Inbound Delivery Management", "Scope": "Goods receipt to valuated stock in transit is posted and the corresponding material and accounting documents are generated.", "Outcome": "Goods receipt posted.", "GUID": "5785174b-943d-11ee-3781-0201b014c5b2", "name": "Perform goods receipt to valuated stock in transit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.999931915886674, "y": 0.0033222591362127574, "z": -0.02609284380459795 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1449", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Settle stock differences commercially,\n Adjustments to inventory posting,\n Valuation variances of inventory posting", "Type": "Business Process", "Description": "Purpose of this process is the commercial adjustment of stock postings in order to reflect differences in physical inventory.", "hasAssignment": true, "Process_Group": "Inventory Management", "Scope": "Once the inventory differences have been adjusted by the Warehouse management, there needs to be an accompanying settlement of this difference commercially.This commercial settlement is reflected by the settlement to the inventory differences clearing account which will subsequently be written off as an expense within the Trading, Profit and Loss account to the value of the amount settled.", "Outcome": "Stock is adjusted commercially to reflect actual inventory.", "GUID": "f86b2ab1-8e54-11e8-2ddf-001bc640cd9b", "name": "Adjust stock postings commercially", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.999673198481051, "y": 0.006644518272425071, "z": -0.06262197240712587 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1451", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update storage location for physical inventory", "Type": "Business Process", "Description": "This process refers to the operational adjustment of the differences in physical inventory as compared to what has been previously recorded by Inventory Management. This reflects a manual adjustment which triggers postings to the inventory differences account which will be received by Controlling.", "Process_Group": "Inventory Management", "hasAssignment": true, "Scope": "The process includes clearance of all the differences in physical inventory and results in an update of the storage location of the inventory.", "Outcome": "The storage location for physical inventory is updated and differences are cleared.", "GUID": "f86b2aaf-8e54-11e8-2ddf-001bc640cd9b", "name": "Clear differences in physical inventory", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9997549016420357, "y": 0.009966777408637828, "z": -0.03131027560805104 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1455", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Generate count document,\n Print count document,\n Maintain inventory to be counted", "Type": "Business Process", "Description": "This process describes the first requirement of generating and printing an inventory count document. The document describes what should be counted and at what locations the items can be found.", "Process_Group": "Inventory Management", "hasAssignment": true, "Scope": "The count document includes materials for inventory count and the storage bins/locations where the items can be found.", "Outcome": "Count document generated and printed.", "GUID": "f86b2a99-8e54-11e8-2ddf-001bc640cd9b", "name": "Create count document", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9993464147619737, "y": 0.013289036544850585, "z": -0.06261856158117854 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1457", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Perform physical count of goods", "Type": "Business Process", "Description": "This process describes the physical count of the goods against the count document. The purpose ist to determine exactly the inventory quantities and to identify differences. The physical inventory, system and physical stock levels should be aligned.", "Process_Group": "Inventory Management", "hasAssignment": true, "Scope": "This count includes all items included in the created count list.", "Outcome": "Physical inventory is determined.", "GUID": "f86b2a9b-8e54-11e8-2ddf-001bc640cd9b", "name": "Count goods physically", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9986383918992146, "y": 0.016611295681063343, "z": -0.10436000589144441 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1459", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain physical count in system,\n Display count differences,\n Trigger re-count,\n Trigger inventory adjustment", "Type": "Business Process", "Description": "Following the physical count, this process describes maintaining the count in the system. In the case of a mismatch, a re-count is triggered and the inventory is adjusted.", "Process_Group": "Inventory Management", "hasAssignment": true, "Scope": "This maintenance includes the documentation of the count in the system and identification of count differences.", "Outcome": "Inventory count maintained in the system.", "GUID": "f86b2a9d-8e54-11e8-2ddf-001bc640cd9b", "name": "Maintain count in system", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.99754916660337, "y": 0.019933554817275656, "z": -0.15653219279740843 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1465", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify business partner,\n Record and store customer complaint,\n Evaluate customer complaint,\n Feedback to customer about further processing,\n Decide further processing steps,\n Close complaint", "Type": "Business Process", "Description": "Receiving the customer complaint and capturing it in a format necessary for further processing helps to ensure the effective and efficient handling of customer disputes.", "Process_Group": "Complaint Management", "hasAssignment": true, "Scope": "Once the customer places a complaint, the data is recorded, stored and forwarded for further processing.", "Outcome": "All relevant information regarding the customers complaint is documented.", "GUID": "1f6c491c-7e4d-11e5-0a66-001bc640cd9b", "name": "Document and assess customer complaint", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.995997090221437, "y": 0.023255813953488413, "z": -0.2191321383459533 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1467", "text": "Process", "data": { "Advisory_Notes": "Guidelines must be established regarding the categorization and prioritization of complaints and how this information should be used in steering the handling (response time) of the customer dispute. It is required to set-up the information flow and monitoring of received customer complaints between all involved parties involved in complaint handling (e.g. Quality Management).", "KeyActivities": " Create return sales order with reference,\n Enter requested delivery date,\n Enter return sales order header data,\n Save return sales order,\n Enter item and requested quantity,\n Copy data from reference document,\n Create return sales order without reference", "Type": "Business Process", "Description": "It is necessary to determine the validity of each complaint received and the decision made regarding the settlement of the customer dispute.", "Process_Group": "Customer Returns", "hasAssignment": true, "Scope": "The information regarding the customer complaint is assessed to determine the validity of the claims made. The decision is made on the steps necessary to resolve the customer dispute. The required steps must then be initiated.", "Outcome": "The decision is made on: ***Whether to take the goods back from the customer ***If possible/appropriate, how to compensate the customer.", "GUID": "1f6c4931-7e4d-11e5-0a66-001bc640cd9b", "name": "Create return sales order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9982572958868907, "y": 0.02657807308970117, "z": -0.08347322585602676 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1477", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Costs are collected in projects only temporarily using cost collectors such as WBS elements or cost centres. Periodically costs incurred in executing a project are allocated in whole or part to one or more receivers such as WBS elements, GL accounts, or profitability segment. This helps to measure the profitability of the project.", "Process_Group": "Project Management", "Scope": "The costs are initially collected on the order, and when the order is technically completed, the costs are transferred to the settlement receiver specified in the settlement rule.", "Outcome": "All costs related to the project order are settled.", "GUID": "d04ec4a3-a658-11ee-3781-0201b014c5b2", "name": "Settle orders for projects", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9966917128042416, "y": 0.029900332225913484, "z": -0.14085019847475966 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1481", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Capture and document provided service,\n Print service order,\n Perform service operation,\n Spare part consumption posting,\n Service activity posting,\n Travel cost posting", "Type": "Business Process", "Description": "The service must be executed according to the specifications provided in the service order.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Once the service team has been dispatched, required activities are carried out to perform the service. After service execution, it is required to document the provided service.", "Outcome": "Service operations are fulfilled.", "GUID": "49b377d4-7e50-11e5-0a66-001bc640cd9b", "name": "Perform service", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.994554494585169, "y": 0.03322259136212624, "z": -0.20864896306817585 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1483", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter service order number,\n Capture resource-related expenses", "Type": "Business Process", "Description": "The process describes materials/spare parts/working hours used for the execution of the service and its confirmation with reference to the service order.", "Process_Group": "Billing, Rebates and Commissions", "hasAssignment": true, "Scope": "Capturing of resource-related expenses.", "Outcome": "Billing request created.", "GUID": "f56c62e3-7e51-11e5-0a66-001bc640cd9b", "name": "Create billing request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.991764065605405, "y": 0.036544850498339, "z": -0.2868649740393501 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1485", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Settle service order ,\n Complete service order,\n Settlement posting", "Type": "Business Process", "Description": "Before the commercial completion of the service order, the service order is settled, which is the posting of all costs and revenues related to the service order and its transfer to the profitability analysis. Commercial completion ensures no more costs can be allocated to the service. The service order is completed from an accounting/controlling perspective.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Post costs and revenues related to the service order and transfer to the profitability analysis via settlement, complete service order.", "Outcome": "All costs and revenues settled to service order and service order is closed from a business perspective.", "GUID": "499e1b10-7e50-11e5-0a66-001bc640cd9b", "name": "Settle and complete service order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.988238882856656, "y": 0.03986710963455131, "z": -0.3754931182374183 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1487", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Select billing request and save,\n Call up sales price determination,\n Unblock billing request,\n Correct price for service to zero due to goodswill/guarantee", "Type": "Business Process", "Description": "After the service execution the billing request needs to be created. Due to the previous decision that the customer will not be invoiced due to action of goodwill the pricing within the billing request needs to be corrected to 0. Once the billing has been adjusted and saved the system automatically blocks the billing request, which needs to be removed from it.", "hasAssignment": true, "Process_Group": "Billing, Rebates and Commissions", "Scope": "Correct price for service 0, unblock billing request.", "Outcome": "Billing request created.", "GUID": "35d8dd0b-7eea-11e5-0a66-001bc640cd9b", "name": "Create billing request (with goodwill)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9953992684709794, "y": 0.04318936877076407, "z": -0.1355793471937386 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1489", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Confirm material consumption,\n Spare part consumption posting", "Type": "Business Process", "Description": "Spare parts have been reserved from the service order in the stock for the repair. Spare part consumption takes place during the service process and must be recorded. Stock level in the system must be lowered accordingly.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Confirmation of material consumption, goods issue adjusts inventory and the spare parts are accounted to the service order as costs.", "Outcome": "Material consumption captured and goods issue posted.", "GUID": "499e1b3d-7e50-11e5-0a66-001bc640cd9b", "name": "Confirm consumption of spare parts", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.991996850990655, "y": 0.04651162790697683, "z": -0.21898594398272325 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1491", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Register completion of service,\n Event-based revenue recognition posting", "Type": "Business Process", "Description": "Once all service order activities are complete and completion confirmations are posted, the status of the service order can be set to technically complete.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "The status of the service order is set to technically complete.", "Outcome": "Service is technically complete.", "GUID": "49b377d1-7e50-11e5-0a66-001bc640cd9b", "name": "Technically complete service order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9877510883916956, "y": 0.049833887043189584, "z": -0.31279587118574204 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1493", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain repair service as non-billable,\n Confirm and save service order", "Type": "Business Process", "Description": "The service department decides to perform the repair service free of charge (goodwill).", "hasAssignment": true, "Process_Group": "Field Services", "Scope": "Maintain repair service as free of charge and confirm.", "Outcome": "Service order confirmed and ready for execution.", "GUID": "31be9a19-7eea-11e5-0a66-001bc640cd9b", "name": "Confirm service order for service execution (with goodwill)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.982580551412973, "y": 0.0531561461794019, "z": -0.4170024564450455 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1495", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Copy master record data into notification,\n Enter short description of notification,\n Create service order from service notification,\n Enter basic data", "Type": "Business Process", "Description": "This process describes the receipt of a service request of a customer for an equipment. From a service notification, a service order is directly created.", "hasAssignment": true, "Process_Group": "Field Services", "Scope": "A service notification with reference to an equipment master record is captured. The related service order is generated automatically.", "Outcome": "Service notification and service order created.", "GUID": "35d8dd17-7eea-11e5-0a66-001bc640cd9b", "name": "Create service notification and service order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.9764038582057095, "y": 0.056478405315614655, "z": -0.5315984608930954 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1497", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Calculate planned costs of required material and work hours,\n Maintain required material from structure list into service order,\n Call up structure list,\n Call up service order,\n Check description of defect equipment,\n Enter work hours for repair", "Type": "Business Process", "Description": "This process describes the planning of the service execution. Based on the description of the service order this can include the planned working hours and the required material/spare parts used for the repair process. A first repair cost calculation is calculated.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Capture estimates on work hours and required material/spare parts, and calculate the costs for the repair.", "Outcome": "Costs are calculated for the service order.", "GUID": "35d8dd2f-7eea-11e5-0a66-001bc640cd9b", "name": "Process service order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9911827651509424, "y": 0.05980066445182741, "z": -0.18759316556273223 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1501", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update existing contract,\n Check for existing contract,\n Create new contract,\n Trigger contract negotiation,\n Maintain basic contract data,\n Identify business partner", "Type": "Business Process", "Description": "This process describes the creation of a service contract.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Creation of customer contract based on the contract data.", "Outcome": "Service contract has been created.", "GUID": "84843a40-7e5b-11e5-0a66-001bc640cd9b", "name": "Create service contract", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9852650256021516, "y": 0.06312292358803973, "z": -0.2969726029730417 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1503", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Execute service order release ,\n Maintain data of required spare part for repairs ,\n Enter service order header data,\n Reserve spare parts in the stock for repairs,\n Reserve available spare parts in the stock for repairs,\n Create purchase requisition", "Type": "Business Process", "Description": "After noting down the customers problem in a service notification, the service manager creates a service order with reference to the notification. A service order is required prior to service execution. The service order can include the requirement of spare parts.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Creation of service order, reservation of required spare parts, release of service order.", "Outcome": "Service order created.", "GUID": "81351d3c-e9bd-11e4-0a66-001bc640cd9b", "name": "Create service order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9782328051052875, "y": 0.06644518272425248, "z": -0.4167298266072571 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1505", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update service notification,\n Contact customer for additional details", "Type": "Business Process", "Description": "It is sometimes required to maintain additional information to the customer notification based on new input internally, or from the customer.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Maintain additional information and update service notification.", "Outcome": "Service notification updated.", "GUID": "84843a2b-7e5b-11e5-0a66-001bc640cd9b", "name": "Change service notification", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.970004876199729, "y": 0.06976744186046524, "z": -0.5468560418893718 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1507", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Link invoice to service order,\n Maintain spare parts to be invoiced,\n Accounts receivable posting,\n Revenue posting", "Type": "Business Process", "Description": "Spare parts that were required for executing the service will be added to the customer invoice.", "Process_Group": "Billing, Rebates and Commissions", "hasAssignment": true, "Scope": "Price capturing of spare part/material, invoice will be linked to the customer invoice.", "Outcome": "Invoice added to final customer invoice.", "GUID": "768b35de-d4a1-11eb-2c3e-001bc641ce4f", "name": "Maintain spare parts for invoicing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.960500073601314, "y": 0.07308970099667755, "z": -0.687341889163414 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1509", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Copy master record data into notification,\n Enter short description of notification,\n Enter basic data", "Type": "Business Process", "Description": "This process describes the receipt of a service request of a customer and how to proceed with the request.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Create and maintain the service notification based on the customers request for a service.", "Outcome": "Service notification created.", "GUID": "499e1b19-7e50-11e5-0a66-001bc640cd9b", "name": "Create service notification", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9856106565393188, "y": 0.07641196013289031, "z": -0.2394792697447839 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1513", "text": "Process", "data": { "Advisory_Notes": "Services can be represented by a material number with service type and/or service item category. The service item category controls whether a delivery is required or not.", "KeyActivities": "Block sales order,\n Check credit limit and overdue payments,\n Enter requested service date,\n Enter service order header data,\n Execute credit management check", "Type": "Business Process", "Description": "This process describes the receipt of a customer request for services.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Create sales order and maintain basic order data for service and the performance of a credit check.", "Outcome": "Sales order for services is created.", "GUID": "4f887808-82c5-11e5-0a66-001bc640cd9b", "name": "Receive service request and create sales order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.976500819692723, "y": 0.07973421926910307, "z": -0.37475708181240175 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1517", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter repair order number,\n Confirm repair order and trigger repair,\n Create service order", "Type": "Business Process", "Description": "A service order is required prior to service execution. In this case the service order is automatically created once the repair order is confirmed for repair execution.", "hasAssignment": true, "Process_Group": "Repairs", "Scope": "Select repair order and confirm repair order.", "Outcome": "Repair order confirmed and service order automatically created.", "GUID": "499e1b22-7e50-11e5-0a66-001bc640cd9b", "name": "Process repair order and create service order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.966006124811759, "y": 0.08305647840531583, "z": -0.5203800706749021 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1519", "text": "Process", "data": { "Advisory_Notes": "Service products (material master record) are used to represent a service and to manage inventory of the customers returned equipment/product (unit of measure is piece)", "KeyActivities": "Contact customer for additional details,\n Update service notification,\n Call up outstanding notificications,\n Create repair order,\n Contact customer about service request processing", "Type": "Business Process", "Description": "The service notification is reopened for adding more details to it. Additional details can be added by calling back the customer. Based on the information of the customer, the service employee decides if the service request is further processed. If the service notification can be further processed, the service employee captures what material and quantity is requested for the repair of the equipment. The repair order is generated from the service notification.", "Process_Group": "Repairs", "hasAssignment": true, "Scope": "Add details to service notification, create repair order.", "Outcome": "Repair order created.", "GUID": "a9cc68f6-7e4f-11e5-0a66-001bc640cd9b", "name": "Process service notification and create repair order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.9540456015363, "y": 0.08637873754152814, "z": -0.6763373255253957 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1521", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Capture valid warranty status,\n Capture status no valid warranty for equipment,\n Check warranty of equipment", "Type": "Business Process", "Description": "Based on the equipment number, the service employee can perform a warranty check. If the equipment has a valid warranty which covers the kind of damage a sales order free of charge (potentially with returns delivery) is created. If the warranty does not apply, the customer is invoiced for the repair.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Check customer warranty.", "Outcome": "Warranty status determined.", "GUID": "499e1b34-7e50-11e5-0a66-001bc640cd9b", "name": "Determine warranty status", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.940538356404446, "y": 0.0897009966777409, "z": -0.8426173722915855 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1523", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Select with order reference,\n Perform goods receipt,\n Receive equipment,\n Enter shipping information,\n Create return delivery order", "Type": "Business Process", "Description": "The customers equipment is delivered for repair to the companys premises. The equipment delivered for repair needs to be posted into the companys stock with reference to the repair order.", "Process_Group": "Customer Returns", "hasAssignment": true, "Scope": "Once a repair order has been placed, a return delivery is initiated with all relevant shipping information. On arrival of the equipment, the goods receipt is posted.", "Outcome": "Goods receipt of equipment to be repaired posted", "GUID": "499e1b1f-7e50-11e5-0a66-001bc640cd9b", "name": "Create return delivery w. ref. to repair order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9786867361502203, "y": 0.09302325581395365, "z": -0.29120233547001 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1525", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Capture required spare parts ,\n Capture required working hours", "Type": "Business Process", "Description": "Prior to the service execution the planned working hours have to be maintained and if required also spare parts.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Prior to the repair process the planned working hours and required spare parts are maintained in the system.", "Outcome": "Working hours maintained, spare parts maintained.", "GUID": "019b08e2-83f2-11e5-0a66-001bc640cd9b", "name": "Maintain planned working hours", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.965710199969251, "y": 0.09634551495016597, "z": -0.4522864245125493 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1529", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter service notification ,\n Create spare part order", "Type": "Business Process", "Description": "The customer requests a spare part. A spare part order is created.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Create notification and spare part order.", "Outcome": "Spare part order created.", "GUID": "d46a2a9b-7eeb-11e5-0a66-001bc640cd9b", "name": "Enter service notification and create spare parts order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9510793714845764, "y": 0.09966777408637872, "z": -0.6236760378826844 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1533", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update service notification,\n Contact customer about service request processing,\n Contact customer for additional details,\n Call up outstanding notificications,\n Create service order", "Type": "Business Process", "Description": "The service employee calls up the outstanding notification. The service employee defines further actions that have to be taken e.g. creation of service order. Optionally, the service order employee requests more information from the customer prior to deciding if the service notification is further processed. The customer can now be informed that his service request is further processed.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Call up notification, call back customer and create service order.", "Outcome": "Service order created.", "GUID": "f56c6304-7e51-11e5-0a66-001bc640cd9b", "name": "Process service notification and create service order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.934713592561513, "y": 0.10299003322259148, "z": -0.8053581559707746 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1535", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Print customs documents,\n Print transport documents,\n Post goods issue of unvaluated stock", "Type": "Business Process", "Description": "In this process the shipment documents are prepared and the goods issue gets posted. In some cases shipment documents may have to be printed in advance to be included in the packaging.", "Process_Group": "Outbound Delivery Management", "hasAssignment": true, "Scope": "Goods issue posting and printing of transport and customs documents are involved in this process.", "Outcome": "Goods issue posted and shipment ready for dispatch.", "GUID": "41a28422-3c0a-11e9-2ddf-001bc640cd9b", "name": "Perform goods issue for customer-owned material", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.916532296633023, "y": 0.1063122923588038, "z": -0.9973191980997671 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1537", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Store goods in warehouse,\n Post goods receipt for customer-owned unvaluated stock", "Type": "Business Process", "Description": "In this process goods receipt posting is performed thus triggering an update in inventory levels. As the material remains property of the customer no postings and accounting are required.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "Goods receipt for received goods is posted and paper documentation is created as required.", "Outcome": "Goods receipt material document created, as required in addition goods receipt slip.", "GUID": "41a28420-3c0a-11e9-2ddf-001bc640cd9b", "name": "Perform goods receipt for customer-owned material", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9704157178166928, "y": 0.10963455149501655, "z": -0.3427271494657626 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1539", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Execute service order release ,\n Reserve spare parts in the stock for repairs", "Type": "Business Process", "Description": "After the quotation acceptance of the customer the release of the service order is triggered. Furthermore, spare parts that are required to execute the service are reserved.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Release service order and reserve spare parts.", "Outcome": "Service order released and spare parts reserved.", "GUID": "768b35d4-d4a1-11eb-2c3e-001bc641ce4f", "name": "Release service order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9529005127293484, "y": 0.11295681063122931, "z": -0.5295078487829536 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1547", "text": "Process", "data": { "Advisory_Notes": " ***The alignment of Production Planning and Procurement Planning during preparation of Master Planning and S&OP alignment is quite common. Especially if raw material availability is a mentionable restriction and/or subcontracting is a standard solution to resolve internal capacity issues. ***If interdependencies are strong it might make sense to combine Production Planning and Procurement Planning and sometimes also Distribution Planning to one central Supply Planning.", "Type": "Business Process", "Description": "Purpose of this process is to resolve production capacity shortages by plant specific means.", "Process_Group": "Sourcing Direct", "Scope": "For each identified capacity issue a suitable solution needs to be defined and documented. In order to resolve issues different suppliers but also other planning disciplines (e.g. Production Planning) might need to be involved.", "Outcome": "Supply issues have been resolved.", "GUID": "e7888668-61e5-11e9-2ddf-001bc640cd9b", "name": "Clarify capacity issues with suppliers", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9334627073178643, "y": 0.11627906976744207, "z": -0.726547403917747 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1548", "text": "Process", "data": { "Advisory_Notes": "***At this point in time there can be more then one source of supply for each procurement requirement. The selection of the source of supply will typically be done during actual Procurement activity based on rules, that need to be defined in a later stage of Procurement Planning scenario.", "Type": "Business Process", "Description": "Purpose of this process is to identify the most suitable source of supply for each procurement requirement.", "Process_Group": "Procurement Planning", "Scope": "Structured procurement requirements are matched with known sources of supply. Missing sources of supply are identified and escalated to Purchasing. ", "Outcome": "Procurement requirements are matched with sources of supply.", "GUID": "1afd612e-61ec-11e9-2ddf-001bc640cd9b", "name": "Match requirements with sources of supply", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.912022010585384, "y": 0.11960132890365438, "z": -0.9338306953215478 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1549", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to escalate procurement requirements back to Master Planning for which procurement planning cant provide a suitable supply.", "Process_Group": "Procurement Planning", "Scope": "A summary of all procurement issues is provided to Master Planning. Partially this is meant as information on already resolved issues (e.g. additional storage location to cover certain peaks). More importantly the not yet resolved issues (e.g. suppliers cant delivery sufficient material) need to be escalated in order to be aligned with the other planning disciplines during Master Planning. Typically Production Planning is the most closely related supply chain planning discipline. Alignment with Production Planning needs to be ensured especially when escalating issues to Master Planning and when adjusting procurement plans.", "Outcome": "Procurement issues that need to be resolved mutually with other planning disciplines are escalated to Master Planning.", "GUID": "e788866e-61e5-11e9-2ddf-001bc640cd9b", "name": "Escalate infeasible procurement requirements to Master Planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.888498237709775, "y": 0.12292358803986714, "z": -1.1513420449583534 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1550", "text": "Process", "data": { "Advisory_Notes": " ***It is necessary to align with Master Planning on the structure and format of the procurement requirements provided to Procurement Planning.", "Type": "Business Process", "Description": "Purpose of this process is to analyze procurement requirements and brake these down to certain categories and suppliers.", "Process_Group": "Procurement Planning", "Scope": "After receiving procurement requirements from Master Planning these are analyzed and structured according to categories and suppliers. ", "Outcome": "Procurement requirements from Master Planning have been structured in order to prepare procurement planning.", "GUID": "e788866b-61e5-11e9-2ddf-001bc640cd9b", "name": "Analyze procurement requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.960803232481518, "y": 0.1262458471760799, "z": -0.3940186334299811 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1551", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to adjust the initial procurement plan according to the results/decisions coming from Master Planning as a result of the S&OP alignment meetings.", "Process_Group": "Procurement Planning", "Scope": "After receiving input from Master Planning the procurement plan needs to be adjusted accordingly and issue resolution needs to be incorporated. The resulting Production Planning after S&OP alignment should be considered as input for procurement planning since it will provide additional details on required raw material, components and subcontracted materials. ", "Outcome": "Procurement plan is aligned with mutually agreed on S&OP plan.", "GUID": "e7888671-61e5-11e9-2ddf-001bc640cd9b", "name": "Adjust procurement plan to S&OP alignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9380804788599737, "y": 0.1295681063122922, "z": -0.6063687819651894 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1552", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to make the planned procurement activities known to the operative Procurement team.", "Process_Group": "Procurement Planning", "Scope": "Different responsible Procurement teams are informed about the planned procurement activities with focus on important upcoming changes (e.g. certain new rules for source of supply determination) and most critical situation in the mid-term horizon (e.g. special peak demands that need tight monitoring).", "Outcome": "Procurement requirements and plan are known to Procurement.", "GUID": "1afd6127-61ec-11e9-2ddf-001bc640cd9b", "name": "Provide procurement plan to Procurement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.913168125807942, "y": 0.13289036544850497, "z": -0.8289241335374166 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1553", "text": "Process", "data": { "Advisory_Notes": "Detail level and horizon of the procurement plan depend on the procurement lead times and the utilization level of storage facilities. In case of very tight storage capacities, the planning of inventories needs to be paid more attention and detail level might need to consider weekly or even daily buckets. ", "Type": "Business Process", "Description": "Purpose of this process is to create an initial procurement plan.", "Process_Group": "Procurement Planning", "Scope": "Transform procurement requirements into a comprehensive procurement plan showing when to procure which quantity from which source of supply. This includes the definition of rules in case of multiple source of supplies for the same material.", "Outcome": "Initial procurement plan is set up.", "GUID": "1afd6124-61ec-11e9-2ddf-001bc640cd9b", "name": "Create initial procurement plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.88598630412883, "y": 0.13621262458471772, "z": -1.061667478952569 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1554", "text": "Process", "data": { "Advisory_Notes": "* in a multi-plant setup it needs to be determined which plant is allowed to order raw materials at a supplier and which should order raw materials via intercompany replenishment setups.", "Type": "Business Process", "Description": "Purpose of this process is to define needed rules on how to choose the source of supply during actual procurement activities.", "Process_Group": "Sourcing Direct", "Scope": "For all cases with multiple possible suppliers the rules for choosing source of supply are defined. This includes consideration of existing contracts with suppliers, alignment with Purchasing on impacts to new contracts and results into source of supply settings in the system (e.g. favorite SoS, fair-share rules or certain quotas per supplier). In addition intercompany supply needs to be considered as possible option. Sometimes even externally sourced products might be supplied internally via intercompany in order to improve external supply set up by bundling the sourcing from a certain supplier to one of the plants.", "Outcome": "Determination rules for source of supply are defined.", "GUID": "1afd6134-61ec-11e9-2ddf-001bc640cd9b", "name": "Determine rules for source of supply decisions- Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.856455265335564, "y": 0.13953488372093004, "z": -1.3045810534893394 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1555", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to align available and needed supply capacities.", "Process_Group": "Procurement Planning", "Scope": "After receiving requirements from Master Planning these need to be aligned with actual available capacities of source of supplies. Discrepancies need to be identified for further processing.", "Outcome": "Needed and available supply capacities have been aligned and discrepancies have been identified.", "GUID": "1afd612a-61ec-11e9-2ddf-001bc640cd9b", "name": "Evaluate and align capacities of supply sources", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9498558243636472, "y": 0.1428571428571428, "z": -0.44504186791262856 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1556", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to transfer the distribution plan into the data needed for automated planning functionalities (esp. material requirements planning).", "Process_Group": "Distribution Planning", "Scope": "Stock parameters (such as target, minimum and maximum stock, as well as reorder levels and replenishment leadtimes) are determined for each material and storage location. Typically the parameters are maintained in material master data in order to facilitate material requirements planning functionalities.", "Outcome": "Stock parameters of related materials are up to date and reflect the aligned distribution plan.", "GUID": "e46c438c-765c-11e9-2ddf-001bc640cd9b", "name": "Maintain stock parameters in material master", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.921260187900211, "y": 0.14617940199335555, "z": -0.6828168968246341 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1560", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to adjust warehouse requirements and setup a stock allocation plan according to the results/decisions coming from Master Planning as a result of the S&OP alignment meetings.", "Process_Group": "Distribution Planning", "Scope": "After receiving input from Master Planning the warehouse requirements need to be adjusted accordingly and issue resolution needs to be incorporated. Based on this the stock allocation including projected stock levels are determined.", "Outcome": "Warehouse requirements including stock allocation are determined and aligned with mutually agreed on S&OP plan.", "GUID": "1cabcf50-764a-11e9-2ddf-001bc640cd9b", "name": "Adjust warehouse requirements and setup stock allocation plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.8902094435881023, "y": 0.1495016611295683, "z": -0.9307365282495074 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1561", "text": "Process", "data": { "Advisory_Notes": " ***in many industries distribution capacities are considered as infinite in this stage of planning and are resolved by operational functions during later execution.", "Type": "Business Process", "Description": "Purpose of this process is to align planned and existing transport capacities.", "Process_Group": "Distribution Planning", "Scope": "Based on planned distribution setup the implications on transport routes are determined. These planned transport requirements are compared to existing capacities. Most commonly the focus lies on expected transport cost increases (e.g. express freigt) and on customer service level violations (e.g. lead time requirements).", "Outcome": "Transport requirements are aligned with capacities and most critical issues have been identified.", "GUID": "1cabcf44-764a-11e9-2ddf-001bc640cd9b", "name": "Align transport requirements with capacities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.856624198406262, "y": 0.15282392026578062, "z": -1.1887814750637453 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1562", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to provide Transport Management with the derived transport plan.", "Process_Group": "Distribution Planning", "Scope": "Transport Management is provided with the transport plan and critical requirements and changes to the current setup are clarified. This also includes the documented guidelines to ensure compliance to the plan.", "Outcome": "Transport plan has been provided to Transport Management as basis for transport sourcing and execution processes.", "GUID": "e46c4382-765c-11e9-2ddf-001bc640cd9b", "name": "Provide transport plan to Transport Management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.820425194495768, "y": 0.15614617940199338, "z": -1.4569318979550496 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1563", "text": "Process", "data": { "Advisory_Notes": " ***Distribution Planning needs to have clear targets in order to be able to optimize the planned distribution setup. These targets need to reflect the overall strategy of the company or related business unit to allow resolution of conflicts between cost and service aspects. ***It needs to be defined to which extend Distribution Planning is allowed to adjust the distribution network. For example, if it is a valid option to plan an additional warehouse location in a certain market. This might be considered as strategic decision which should be taken in Strategic Network Planning with alignment further business functions.", "Type": "Business Process", "Description": "Purpose of this process is to optimize the distribution setup for planned distribution requirements.", "Process_Group": "Distribution Planning", "Scope": "The initial distribution plan is taken as a basis in order to compile different optimization options. Most commonly decisions on storage location versus transport lead time and costs (which warehouse to use) as well as transport lead time vs. cost (express freight or groupage) are reconsidered to improve overall setup. Each option is evaluated regarding different targets (e.g. customer service/lead time, transport cost, warehousing cost). Then an optimized distribution plan is derived.", "Outcome": "Distribution plan has been optimized with regards to various optimization targets.", "GUID": "1cabcf40-764a-11e9-2ddf-001bc640cd9b", "name": "Optimize distribution setup", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.937580946502868, "y": 0.15946843853820614, "z": -0.49576211608900767 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1564", "text": "Process", "data": { "Advisory_Notes": "***the scope of issue solving in Distribution Planning is most commonly restricted, since some important decisions (e.g. on new warehouses) typically do not fall under the responsibility of Distribution Planning but rather are considered as part of Strategic Network Planning (SNP). SNP is mostly involved after escalation to Master Planning and in alignment with other Supply Chain Planning functions and business functions like Sales and Corporate Strategy.", "Type": "Business Process", "Description": "Purpose of this process is to escalate distribution requirements back to Master Planning for which distribution planning cant provide a suitable solution.", "Process_Group": "Distribution Planning", "Scope": "A summary of critical distribution issues is provided to Master Planning. Partially this is meant as information on already resolved issues. More importantly the not yet resolved issues (e.g. customer lead time expectations can not be met) need to be escalated in order to be aligned with the other planning disciplines during Master Planning.", "Outcome": "Distribution issues that need to be resolved mutually with other planning disciplines are escalated to Master Planning.", "GUID": "1cabcf4c-764a-11e9-2ddf-001bc640cd9b", "name": "Escalate infeasible distribution requirements to Master Planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.902451091172276, "y": 0.16279069767441845, "z": -0.7588001471750415 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1565", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to adjust the transport requirement according to the results/decisions coming from Master Planning as a result of the S&OP alignment meetings.", "Process_Group": "Distribution Planning", "Scope": "After receiving input from Master Planning the transport requirements need to be adjusted accordingly and issue resolution needs to be incorporated. Based on these adjusted requirements a transport plan for each transport route is determined.", "Outcome": "Transport plan is aligned with mutually agreed on S&OP plan.", "GUID": "1cabcf54-764a-11e9-2ddf-001bc640cd9b", "name": "Adjust transport requirements and setup transport plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.864602291022192, "y": 0.1661129568106312, "z": -1.0319152737633175 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1566", "text": "Process", "data": { "Advisory_Notes": " ***It is necessary to align with Master Planning on the structure and format of the distribution requirements provided to Distribution Planning.", "Type": "Business Process", "Description": "Purpose of this process is to analyze distribution requirements and brake these down to different warehouse locations and transportation routes.", "Process_Group": "Distribution Planning", "Scope": "After receiving distribution requirements from Master Planning these are analyzed and structured according warehouse locations and transportation routes. In addition the warehousing requirements from Production Planning especially for semi- and finished goods (e.g. inventory development due to campaign production) need to be considered as input.", "Outcome": "Distribution requirements from Master Planning have been structured in order to prepare distribution planning.", "GUID": "54233eb9-6591-11e9-2ddf-001bc640cd9b", "name": "Analyze distribution requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.823955683258184, "y": 0.16943521594684396, "z": -1.3150861439316683 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1567", "text": "Process", "data": { "Advisory_Notes": " ***the determination of distribution setup needs to rely on results and guidelines provide by Strategic Network Planning. This includes for example distribution concepts such as local, regional or global hub-and-spoke systems and maybe fixed allocation of certain markets to certain distribution centers. ***in many industries logistics capacities are considered as infinite in this stage of planning. The contracting of additional capacities is often carried out by operative functions during logistics execution processes. ***additional data on customer requirements (e.g.expected lead times), supplier service conditions (e.g. only full trucks as direct shipments) and product specifics (e.g. thermo transport) need to be available in order to determine feasible distribution setups. ***it needs to be considered that decisions on stock allocation have an effect on the transport requirements due to related replenishments. ***in the definition of transport routes several parameters need to be considered. These are for example transport mode (e.g. road, sea, air, rail), transport service type (e.g. parcel, express, groupage, LTL, FTL, milk run), truck types (e.g. cooled or heated) and other influencing factors.", "Type": "Business Process", "Description": "Purpose of this process is to determine a first distribution setup considering the planned distribution requirements.", "Process_Group": "Distribution Planning", "Scope": "The already structured distribution requirements are matched to existing distribution resources. It is decided which warehouses and storage location should be used for which products/customers. In this way the planned warehouse requirements are specified. In addition first decisions are taken on the material flows through the distribution networks. Especially direct shipments, multi-stop and cross-docking options are considered. As a last step the resulting transport requirements are specified per transport route.", "Outcome": "A first distribution setup is determined and can be used for further distribution planning.", "GUID": "1cabcf3c-764a-11e9-2ddf-001bc640cd9b", "name": "Determine initial distribution setup", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.780432554608553, "y": 0.17275747508305628, "z": -1.6082908572834804 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1568", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to document guidelines for execution processes. This is needed in order to facilitate later compliance with the derived distribution plan.", "Process_Group": "Warehouse Operations", "Scope": "Decisions taken and assumptions made during creation of the distribution plan need to be documented. Of special importance in this field is the planned allocation of products, customers and warehouses (e.g. standard delivering plant) to facilitate the compliance with planned material flows.", "Outcome": "Critical decisions are documented in order to be considered during execution processes. ", "GUID": "e46c4390-765c-11e9-2ddf-001bc640cd9b", "name": "Document guidelines for distribution execution processes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9239869556857458, "y": 0.17607973421926904, "z": -0.5461448474087213 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1569", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to hand over the planning results to Warehouse Management.", "Process_Group": "Distribution Planning", "Scope": "The stock allocation plan is provided to Warehouse Management and critical topics are clarified. Focus lies on information needed to later coordinate needed warehousing resources (e.g. for pick&pack activities) or to organize interim warehouse capacities (e.g. at external warehouses to cover peaks). But there could also be insights from Planning alignments to be transferred to Warehouse Management (e.g. mid-term increase of full pallet movement).", "Outcome": "The requirements and plan have been provided and explained to Warehouse Management.", "GUID": "e46c4389-765c-11e9-2ddf-001bc640cd9b", "name": "Provide planned warehouse requirements to Warehouse Management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.8816659939854037, "y": 0.1794019933554818, "z": -0.834266803311815 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1570", "text": "Process", "data": { "Advisory_Notes": " ***the amount of documentation highly depends on the standardization of transport services and on the importance of transport for the company/business unit success. In environments where transport is not considered crucial part of customer service or has a very small impact on total cost, companies might rely on flexible execution processes instead of ensuring compliance to the transport plan.", "Type": "Business Process", "Description": "Purpose of this process is to document guidelines for transport management and execution processes. This is needed in order to facilitate later compliance with the derived transport plan. ", "Process_Group": "Transportation Management", "Scope": "Decisions taken and assumptions made during creation of the transport plan need to be documented for each transport route. This information will on the one hand be used for carrier negotiations but also during transport planning and carrier selection. Necessary service levels (e.g. number of departures per week, lead time) and carrier selection criteria could be part of these guidelines.", "Outcome": "Guidelines are documented and available for Transport Management and execution processes.", "GUID": "1cabcf62-764a-11e9-2ddf-001bc640cd9b", "name": "Document guidelines for transport management and execution processes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.8363641015633974, "y": 0.18272425249169455, "z": -1.1323914871790877 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1571", "text": "Process", "data": { "Advisory_Notes": " ***in many industries distribution capacities are considered as infinite in this stage of planning and are resolved by operational functions during later execution.", "Type": "Business Process", "Description": "Purpose of this process is to align planned and existing warehouse capacities.", "Process_Group": "Distribution Planning", "Scope": "Based on the planned distribution setup the implications on stock levels and warehouse operations (e.g. pick& pack, cross docking) are determined. These planned warehouse requirements are compared to existing capacities. Most commonly the focus lies on expected issues regarding customer service level violations.", "Outcome": "Warehouse requirements and capacities are aligned and most critical issues have been identified.", "GUID": "1cabcf58-764a-11e9-2ddf-001bc640cd9b", "name": "Align warehouse requirements with capacities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.78800299954203, "y": 0.18604651162790686, "z": -1.4404954968261854 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1575", "text": "Process", "data": { "Advisory_Notes": "The detailed sequence of alignment and the actual constitution of meetings highly depends on the business structures and supply chain setups. It is not possible to show a best practice as reference.", "Type": "Business Process", "Description": "Purpose of this process is summarize and distribute the aligned plan after decision taken during S&OP alignment meetings.", "Process_Group": "Master Planning", "Scope": "Different taken decisions need to be summarized including the impact on different planning disciplines. The mutual plan needs to be adjusted according to these decisions and then distributed to all planing disciplines as basis for operationalization.", "Outcome": "Mutual plan is distributed and available for all planning disciplines.", "GUID": "fa5b7820-5f7d-11e9-2ddf-001bc640cd9b", "name": "Distribute mutual plan to different planning disciplines", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.736504572825139, "y": 0.18936877076411962, "z": -1.758554885682066 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1576", "text": "Process", "data": { "Advisory_Notes": "A typical critical aspect which procurement planning could escalate towards master planning is a insufficient source of supply for certain raw materials.", "Type": "Business Process", "Description": "Purpose of this process is to receive feedback from Procurement Planning with regards to feasibility of forecasted requirements.", "Process_Group": "Master Planning", "Scope": "Procurement Planning provides feedback and planning details back to Master Planning with a special focus on critical aspects and/or impact on other planning disciplines.", "Outcome": "Procurement plan and critical aspects are known to Master Planning.", "GUID": "43d8c396-5f81-11e9-2ddf-001bc640cd9b", "name": "Receive feedback from procurement planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9090831067562901, "y": 0.19269102990033238, "z": -0.5961557611042198 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1577", "text": "Process", "data": { "Advisory_Notes": "*** The consolidation of different sales forecasts of different business units is especially relevant in case of mutually used resources either in sourcing (same raw material or suppliers), in production (same production lines) or in distribution (same warehouses or transportation means).", "Type": "Business Process", "Description": "Purpose of this process is consolidate sales forecasts of different business units into one sales forecast for the specific plant.", "Process_Group": "Demand Planning", "Scope": "After receiving the approved sales forecasts from all relevant business units the data needs to be consolidated in order to create one mutual sales forecast for the relevant plant.", "Outcome": "One consolidated business unit overarching sales forecast for the relevant plant has been set up.", "GUID": "629eacc5-5f71-11e9-2ddf-001bc640cd9b", "name": "Consolidate demand plans of different business units", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.858919046917948, "y": 0.1960132890365447, "z": -0.9091654872297843 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1578", "text": "Process", "data": { "Advisory_Notes": "*** The detailed sequence of alignment and the actual constitution of meetings highly depends on the business structures and supply chain setups. It is not possible to show a best practice as reference. It might be necessary to run cascaded meetings from global, regional to local level or vice-a-versa and maybe consider different meetings for different business units as well. *** In some cases it might even be necessary to review and adjust certain plans in between the alignment meetings and then align again afterwards.", "Type": "Business Process", "Description": "Purpose of this process is to conduct different Sales & Operations Planning alignment meetings.", "Process_Group": "Sales and Operations Planning", "Scope": "In order to create sound Sales & Operations Planning results different Supply Chain Planning disciplines need to come together, align and make adjustments to the different single plans in order to achieve an overall feasible mutual Sales & Operations Plan.", "Outcome": "Mutually agreed on and feasible Sales & Operations Plan has been defined and single Supply Chain discipline plans have been adjusted accordingly.", "GUID": "c4955b22-5f6c-11e9-2ddf-001bc640cd9b", "name": "Conduct Sales & Operations Planning alignment meetings", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.805514099885478, "y": 0.19933554817275745, "z": -1.2320967638837543 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1579", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to provide procurement requirements from sales forecast to Procurement Planning.", "Process_Group": "Master Planning", "Scope": "Requirements data is provided to the Procurement Planning and clarification needs are resolved to facilitate planning.", "Outcome": "Procurement requirements are known to Procurement Planning and available for further planning.", "GUID": "fa5b7807-5f7d-11e9-2ddf-001bc640cd9b", "name": "Consolidate production plan and procurement plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.748790623990495, "y": 0.2026578073089702, "z": -1.5649241545518953 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1580", "text": "Process", "data": { "Advisory_Notes": "*** The consolidation of different sales forecasts of different business units is especially relevant in case of mutually used resources either in sourcing (same raw material or suppliers), in production (same production lines) or in distribution (same warehouses or transportation means).", "Type": "Business Process", "Description": "Purpose of this process is to receive and understand sales forecasts of different business units.", "Process_Group": "Demand Planning", "Scope": "Receiving the approved sales forecasts from all relevant business units some of the data might need clarification in order to be interpreted the right way. Only after understanding the forecast data this can be used for master planning.", "Outcome": "Business specific sales forecasts have been received and clarification needs have been resolved.", "GUID": "73a83063-5f77-11e9-2ddf-001bc640cd9b", "name": "Review demand plan of different business units", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.688671155493451, "y": 0.20598006644518252, "z": -1.907621682791639 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1581", "text": "Process", "data": { "Advisory_Notes": "A typical critical aspect which production planning could escalate towards master planning is insufficient production capacity within specific production areas / concerning specific product groups (either personnel or equipment based).", "Type": "Business Process", "Description": "Purpose of this process is to receive feedback from Production Planning with regards to feasibility of forecasted requirements.", "Process_Group": "Master Planning", "Scope": "Production Planning provides feedback and planning details back to Master Planning with a special focus on critical aspects and/or impact on other planning disciplines.", "Outcome": "Production plan and critical aspects are known to Master Planning.", "GUID": "fa5b7815-5f7d-11e9-2ddf-001bc640cd9b", "name": "Receive feedback from production planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8928795463152188, "y": 0.20930232558139528, "z": -0.6457608095428918 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1582", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to provide procurement requirements from sales forecast to Procurement Planning.", "Process_Group": "Master Planning", "Scope": "Requirements data is provided to the Procurement Planning and clarification needs are resolved to facilitate planning.", "Outcome": "Procurement requirements are known to Procurement Planning and available for further planning.", "GUID": "73a83076-5f77-11e9-2ddf-001bc640cd9b", "name": "Provide and explain requirements to Procurement Planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.834225736183605, "y": 0.21262458471760803, "z": -0.983445207601573 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1583", "text": "Process", "data": { "Advisory_Notes": "*** Depending on the complexity of the Supply Chain and the amount and nature of issues mentioned by the different planning disciplines it might be necessary to run further cycles of alignment between Production, Procurement and Distribution before entering the alignment meetings. Sometimes it might even be necessary to involve more strategic planning areas (e.g. strategic network planning) in order to prepare solutions to critical aspects within the different plans.", "Type": "Business Process", "Description": "Purpose of this process is to prepare the Sales & Operations Planning alignment meetings.", "Process_Group": "Sales and Operations Planning", "Scope": "In order to prepare Sales & Operations Planning alignment meetings the plans of Sales, Production, Procurement and Distribution need to be consolidated. Furthermore invitations need to be prepared and participation of the different stakeholders need to be ensured. Decision points need to be prepared and shared upfront in order to facilitate decision making during the S&OP meetings.", "Outcome": "S&OP alignment meetings have been prepared.", "GUID": "fa5b781c-5f7d-11e9-2ddf-001bc640cd9b", "name": "Prepare Sales & Operations Planning alignment meetings", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.772073288794529, "y": 0.2159468438538208, "z": -1.3309632241210967 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1584", "text": "Process", "data": { "Advisory_Notes": "*** The brake down logic from sales forecast to procurement requirement depends on the actual structure of products (e.g. bill of material, potential substitution). *** The detail-level of procurement requirements should correspond to the detail-level of procurement planning. Both with regards to raw material structures (e.g. raw material classification) as well as accumulation level on a timeline (e.g. yearly, quarterly, monthly or weekly requirements) *** Necessity to de-consolidate depends on the overall procurement situation. For some materials a detailed procurement plan is not necessary (e.g. piped water). Details need to be aligned together with Procurement Planning.", "Type": "Business Process", "Description": "Purpose of this process is de-consolidate the forecast and prepare it for procurement planning.", "Process_Group": "Master Planning", "Scope": "Forecast data is broken down according to the structure of the products into requirements of procured material (e.g. raw materials).", "Outcome": "Procurement requirements are available for further planning.", "GUID": "73a8307c-5f77-11e9-2ddf-001bc640cd9b", "name": "Break down demand plan into procurement requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.706345252547682, "y": 0.2192691029900331, "z": -1.6882874055746244 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1585", "text": "Process", "data": { "Advisory_Notes": "A typical critical aspect which distribution planning could escalate towards master planning is a insufficient space in a certain warehouse.", "Type": "Business Process", "Description": "Purpose of this process is to receive feedback from Distribution Planning with regards to feasibility of forecasted requirements.", "Process_Group": "Master Planning", "Scope": "Distribution Planning provides feedback and planning details back to Master Planning with a special focus on critical aspects and/or impact on other planning disciplines.", "Outcome": "Distribution plan and critical aspects are known to Master Planning.", "GUID": "43d8c39c-5f81-11e9-2ddf-001bc640cd9b", "name": "Receive feedback from distribution planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.636964867797749, "y": 0.22259136212624586, "z": -2.055389763332956 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1586", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to provide procurement requirements from sales forecast to Procurement Planning.", "Process_Group": "Master Planning", "Scope": "Procurement requirements data is provided to the Procurement Planning and clarification needs are resolved to facilitate Procurement Planning.", "Outcome": "Procurement requirements are known to Procurement Planning and available for further planning.", "GUID": "fa5b7803-5f7d-11e9-2ddf-001bc640cd9b", "name": "Evaluate and decide on make or buy cases with Production and Procurement Planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8753873058121104, "y": 0.22591362126245862, "z": -0.6949262214068439 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1587", "text": "Process", "data": { "Advisory_Notes": "*** The brake down logic from sales forecast to capacity requirement depends on the actual structure of products, the production setup of the plant and of the different production lines/areas. *** The detail-level of capacity requirements should correspond to the detail-level of production planning. Both with regards to usage of resources and equipments including availability of details in master data (e.g. from work plans / recipes) as well as accumulation level on a timeline (e.g. yearly, quarterly, monthly or weekly capacities) *** Necessity to de-consolidate depends on the overall capacity utilization. In some cases it might be sufficient to focus on bottleneck areas only. This needs to be decided together with production planning.", "Type": "Business Process", "Description": "Purpose of this process is de-consolidate the forecast and prepare it for production planning.", "Process_Group": "Master Planning", "Scope": "Forecast data is broken down according to the structure of the products and the product specific production process in order to determine the capacity requirements.", "Outcome": "Production capacity requirements are available for further planning.", "GUID": "73a83067-5f77-11e9-2ddf-001bc640cd9b", "name": "Break down demand plan into production requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.807602873088342, "y": 0.22923588039867093, "z": -1.0570553944926848 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1588", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to provide requirements from sales forecast to Distribution Planning.", "Process_Group": "Master Planning", "Scope": "Requirements data is provided to the Distribution Planning and clarification needs are resolved to facilitate planning.", "Outcome": "Distribution requirements are known to Distribution Planning and available for further planning.", "GUID": "73a83086-5f77-11e9-2ddf-001bc640cd9b", "name": "Provide and explain requirements to Distribution Planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.736064434930192, "y": 0.2325581395348837, "z": -1.4289235592045306 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1589", "text": "Process", "data": { "Advisory_Notes": "*** The brake down logic from sales forecast to distribution requirements depends on the actual setup of production facilities (own production, sub contractors) on the distribution network setup (location of plants, warehouses, suppliers and customers) and special requirements either customer or product related (e.g. temperature based transport, storage of hazardous material) . *** The detail-level of distribution requirements should correspond to the detail-level of distribution planning. Both with regards to special requirements as well as accumulation level on a timeline (e.g. yearly, quarterly, monthly or weekly requirements) *** Necessity to de-consolidate depends on the overall distribution situation. For some customers a detailed procurement plan might not be necessary (e.g. EXW contracts). Details need to be aligned together with Distribution Planning.", "Type": "Business Process", "Description": "Purpose of this process is provide requirements data to distribution planning.", "Process_Group": "Master Planning", "Scope": "Forecast data is broken down according to warehousing and transportation structures into requirements for distribution. In addition information about make or buy decisions (e.g. own production vs. subcontracting) is being included.", "Outcome": "Distribution requirements are available for further planning.", "GUID": "73a83089-5f77-11e9-2ddf-001bc640cd9b", "name": "Break down demand plan and information from make or buy cases into distribution requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.660695782194387, "y": 0.23588039867109645, "z": -1.810501263693416 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1590", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to provide production requirements from sales forecast to Production Planning.", "Process_Group": "Master Planning", "Scope": "Requirements data is provided to the Production Planning and clarification needs are resolved to facilitate planning.", "Outcome": "Production capacity requirements are known to Production Planing and available for further planning.", "GUID": "73a8306b-5f77-11e9-2ddf-001bc640cd9b", "name": "Provide and explain requirements to Production Planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.581420911588132, "y": 0.23920265780730876, "z": -2.2017585261982546 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1594", "text": "Process", "data": { "Advisory_Notes": "***The capacity requirement information from mid-term production planning is most often used to trigger vacation planning and temporary workforce contracts.", "Type": "Business Process", "Description": "Purpose of this process is to make the needed capacities available to operations departments (e.g. production, quality control, on-site logistics, maintenance) in order for them to plan/organize resources accordingly.", "Process_Group": "Production Planning", "Scope": "Needed capacities for the different operations departments are extracted from the adjusted production plan and communicated. This includes information on decisions taken during Master Planning in order to resolve issues. ", "Outcome": "Needed capacities are known by the related departments.", "GUID": "7a091b50-6053-11e9-2ddf-001bc640cd9b", "name": "Provide capacity requirements to operations", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8566182940351508, "y": 0.24252491694352152, "z": -0.7436185246845366 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1595", "text": "Process", "data": { "Advisory_Notes": " ***The alignment of Production Planning and Procurement Planning during preparation of Master Planning and S&OP alignment is quite common. Especially if raw material availability is a mentionable restriction and/or subcontracting is a standard solution to resolve internal capacity issues. ***If interdependencies are strong it might make sense to combine Production Planning and Procurement Planning and sometimes also Distribution Planning to one central Supply Planning.", "Type": "Business Process", "Description": "Purpose of this process is to resolve production capacity shortages by plant specific means.", "Process_Group": "Production Planning", "Scope": "For each identified capacity issue a suitable solution needs to be defined and documented. In order to resolve issues different operations departments but also other planning disciplines (e.g. Procurement Planning) might need to be involved.", "Outcome": "Capacity issues have been resolved by plant specific means as far as possible.", "GUID": "43d8c3c0-5f81-11e9-2ddf-001bc640cd9b", "name": "Resolve capacity issues with plant specific means", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.779068582585186, "y": 0.24584717607973428, "z": -1.129945933789739 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1596", "text": "Process", "data": { "Advisory_Notes": "Some plant specific issue resolutions might have an impact on other planning disciplines as well (e.g. pre-ponement of production will lead to higher demand of warehouse capacities). Whether this kind of solutions can be aligned locally or need to be escalated via Master Planning and S&OP alignment meetings needs to be defined upfront.", "Type": "Business Process", "Description": "Purpose of this process is to escalate production requirements back to Master Planning for which plant specific production capacity is not sufficient.", "Process_Group": "Production Planning", "Scope": "A summary of all capacity issues is provided to Master Planning. Partially this is meant as information on already resolved issues. More importantly the not yet resolved issues need to be escalated in order to be aligned with the other planning disciplines during Master Planning.", "Outcome": "Capacity issues that need to be resolved mutually with other planning disciplines are escalated to Master Planning.", "GUID": "3d2f2526-5f90-11e9-2ddf-001bc640cd9b", "name": "Escalate infeasible production requirements to Master Planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.6975120532660255, "y": 0.24916943521594703, "z": -1.5259110773411597 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1597", "text": "Process", "data": { "Advisory_Notes": " ***Short-term production plan should already be available as planned production orders in the system and should not be impacted by changes to the PIR. ***The usage of planned independent requirements to document the production plan has the advantage to be able to use MRP logic for the BOM brake down to different production stages and even raw material requirements. Depending on the planning strategies used it might not be possible to use planned independent requirements. ***Using planned independent requirements implies the necessity to define suitable consumption rules for incoming orders/requirements. If these rules are not defined well or forecast accuracy is poor the consumption logic will in most cases lead to bad planning results.", "Type": "Business Process", "Description": "Purpose of this process is to make the most actual production plan available for MRP and capacity planning.", "Process_Group": "Production Planning", "Scope": "Most actual information is evaluated and adjustment needs are determined. Existing production requirements are checked (e.g. planned independent requirements). Also the planned production orders from short-term production plan are considered to determine the actual necessary adjustments to the mid-term plan. Production requirements are either adjusted or maintained in order to represent the aligned production plan.", "Outcome": "Adjusted production plan is available as independent demands in the system.", "GUID": "3d2f2530-5f90-11e9-2ddf-001bc640cd9b", "name": "Maintain production plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.611873291274927, "y": 0.25249169435215935, "z": -1.9314825252186396 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1598", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to adjust the initial production plan according to the results/decisions coming from Master Planning as a result of the S&OP alignment meetings.", "Process_Group": "Production Planning", "Scope": "After receiving input from Master Planning the production plan needs to be adjusted accordingly and issue resolution needs to be incorporated.", "Outcome": "Production plan is aligned with mutually agreed on S&OP plan.", "GUID": "3d2f252c-5f90-11e9-2ddf-001bc640cd9b", "name": "Adjust mid-term plant specific production plan to S&OP alignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.522077101414957, "y": 0.2558139534883721, "z": -2.346628322940936 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1599", "text": "Process", "data": { "Advisory_Notes": " ***It is necessary to align with Master Planning on the structure and format of the production requirements provided to Production Planning. If possible the structure used in master Planning is already usable for production planning but more often Master Planning is run on a less detailed granularity level in order to reduce complexity. ***The needed structure of data depends on production setup, production stages, product portfolio, planning horizons and many more aspects. Sometimes it might be plant specific.", "Type": "Business Process", "Description": "Purpose of this process is to analyze and brake down production requirements to the plant specific structures.", "Process_Group": "Production Planning", "Scope": "After receiving production requirements from Master Planning these need to be broken down to the actual production structures. ", "Outcome": "Production requirements from Master Planning have been structured in order to prepare mid-term production planning.", "GUID": "e9dd474e-60de-11e9-2ddf-001bc640cd9b", "name": "Analyze production requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.836585289003578, "y": 0.25913621262458486, "z": -0.7918045694586786 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1600", "text": "Process", "data": { "Advisory_Notes": "Depending on the used planning software, available capacities also need to be maintained in system.", "Type": "Business Process", "Description": "Purpose of this process is to identify available production capacities in a mid-term horizon.", "Process_Group": "Production Planning", "Scope": "Planned available capacities of different parts of operations need to be gathered, structured and aligned. This includes but is not limited to personnel and machine resources in production operations, quality control, warehouses, logistics as well as planned maintenance activities with impact on availability of resources.", "Outcome": "Planned available capacities are gathered from and aligned with different operations departments.", "GUID": "7a091b4b-6053-11e9-2ddf-001bc640cd9b", "name": "Determine planned available capacities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.748642290934688, "y": 0.2624584717607972, "z": -1.202067201318342 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1601", "text": "Process", "data": { "Advisory_Notes": "Detail level and horizon of the production plan depends on the duration of production process and volatility of business in general. In non-volatile and long-running production environments it might be sufficient to set up a production plan with monthly quantities. Other environments might need weekly or even daily quantities. Also the granularity might differ from production areas/lines down to single resources (e.g. bottleneck machines)", "Type": "Business Process", "Description": "Purpose of this process is to create an initial plant specific production plan.", "Process_Group": "Production Planning", "Scope": "Transform production requirements into a comprehensive production plan for all plant specific production resources.", "Outcome": "Plant specific production plan is created.", "GUID": "3d2f2522-5f90-11e9-2ddf-001bc640cd9b", "name": "Create initial mid-term plant specific production plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.6564423904196213, "y": 0.26578073089700993, "z": -1.6218597490357927 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1602", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to align available and needed production capacities.", "Process_Group": "Production Planning", "Scope": "After receiving production requirements from Master Planning these need to be aligned with actual available capacities within the plant. Discrepancies need to be identified for further processing.", "Outcome": "Needed and available capacities have been aligned and discrepancies have been identified.", "GUID": "43d8c3bc-5f81-11e9-2ddf-001bc640cd9b", "name": "Evaluate and align mid-term capacities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.55991101833887, "y": 0.2691029900332227, "z": -2.051148825617434 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1605", "text": "Process", "data": { "Advisory_Notes": " ***The quality of data on actually available capacities is a key driver for overall planning and scheduling accuracy. Especially when using advanced planning solutions the automatic planning functions and alert mechanisms are depending on this data. ***The granularity level of capacity evaluation highly depends on the time sensitivity and on the utilization of production. ***Within environments with clear bottlenecks, focussing on these areas is a common way to reduce complexity of planning.", "Type": "Business Process", "Description": "Purpose of this process is to obtain an overview of actually available capacities and to maintain these as basis for capacity leveling.", "Process_Group": "Production Planning", "Scope": "Available capacity for all relevant resources need to be clarified, aligned and maintained. This include production lines/ machines, special equipment but also personnel resources from different operations areas (e.g. production, quality control, warehouses, logistics).", "Outcome": "Actual available capacities are known to Production Planning and are maintained for capacity planning.", "GUID": "22a192b1-605d-11e9-2ddf-001bc640cd9b", "name": "Determine actual available capacities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.45897383878456, "y": 0.272425249169435, "z": -2.4899005256165885 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1606", "text": "Process", "data": { "Advisory_Notes": "Production capacity is often checked for bottleneck work centers or key work centers only. It should also be defined on which granularity capacity should be leveled. In less time sensitive environments, it might be sufficient to look at the weekly load not considering individual days of overload.", "KeyActivities": "Evaluate capacity,\n Level capacity and act on overloads", "Type": "Business Process", "Description": "Material requirements planning assumes infinite production capacity, therefore its outcome - recommended production schedule - is often unrealistic. Actual production capacity must be evaluated, to identify if the required capacity does not exceed work centers defined capacity limits in a given time period.", "hasAssignment": true, "Process_Group": "Production Planning", "Scope": "Recommended production schedule from MRP must be combined with information from routing sheets about work centers and working hours required to meet production plan, by taking into account also setup times. This allows to accurately determine the required capacity at each work center during each time period and to identify problem areas - overcommitment of resources.", "Outcome": "Recommended production schedule revised by taking into account actual capacity constraints, bottlenecks and overcommitment of resources identified.", "GUID": "712673d6-7f1e-11e5-0a66-001bc640cd9b", "name": "Evaluate and align capacity", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8153019292683612, "y": 0.27574750830564776, "z": -0.8394515504748121 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1608", "text": "Process", "data": { "Advisory_Notes": " *** Production Planning and Production Operations need to define clear rules on frozen horizons within which production orders are no longer subject to adjustments. Common practice is to use the creation of production orders from planned orders as cut-off point. From this point in time, planning is considered to be finalized and there should be no further changes to the production orders.", "Type": "Business Process", "Description": "Purpose of this process is to update existing and new planned production orders according to most actual MRP and capacity information. ", "Process_Group": "Production Planning", "Scope": "The planned production orders are updated with regards to for example quantity, date or production version.", "Outcome": "Planned production orders are up to date.", "GUID": "3d2f2549-5f90-11e9-2ddf-001bc640cd9b", "name": "Adjust planned production orders based on MRP and capacity planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.71634471247944, "y": 0.2790697674418605, "z": -1.2733700966274446 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1609", "text": "Process", "data": { "Advisory_Notes": "The basis for demand calculation must be defined. Typical setups are based on demand forecasts, actual demand, or a combination of both.", "KeyActivities": "Revise demand for finished products,\n Maintain planned independent requirements,\n Maintain production schedule", "Type": "Business Process", "Description": "Effective short term production planning must be based on the most accurate data available, this can be ensured by regularly revising and updating the independent demands from both sales forecasts as well as actual demands from customer orders.", "Process_Group": "Production Planning", "hasAssignment": true, "Scope": "Demand information from sales and operations planning, which is taken as initial base for detailed production scheduling is usually based on sales forecast and historical sales data. The demand for finished products must be revised at this stage, the actual demand (firm customer orders) considered and a final demand provided as input to enable analysis of material requirements and generation of detailed production schedules.", "Outcome": "Actual demand for finished products is considered and information for creation of detailed production schedules is updated.", "GUID": "eb3c00f1-7f1f-11e5-0a66-001bc640cd9b", "name": "Revise and update independent demands", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.6128834067837916, "y": 0.2823920265780733, "z": -1.7167042520441151 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1611", "text": "Process", "data": { "Advisory_Notes": " ***The logic and rules for handover of planned production orders to scheduling/production needs to be defined depending on the scheduling requirements and overall planning procedure. ***Often fixation or a certain frozen horizon is used to determine those planned elements ready for scheduling. Frozen horizon is many times related to the creation of production orders from planned orders. ***When defining the handover procedure from planning to scheduling one should also define the handover from scheduling to production. Also here a frozen horizon might make sense.", "Type": "Business Process", "Description": "Purpose of this process is to make (planned) production orders available to scheduling and declare the planning as finalized.", "Process_Group": "Production Planning", "Scope": "The planned production orders updated during MRP and capacity planning need to be released to scheduling. ", "Outcome": "Planned production orders are available for detailed scheduling and are no longer in the responsibility of planning.", "GUID": "22a192cc-605d-11e9-2ddf-001bc640cd9b", "name": "Hand-over production orders to scheduling", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.504844339512096, "y": 0.2857142857142856, "z": -2.16941869558779 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1612", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to evaluate and align impact of short-term changes to the production plan with impacted operations and related planning disciplines.", "Process_Group": "Production Planning", "Scope": "Changes to the production plan are evaluated with regards to potential impact on operations areas (e.g. production operations, procurement, warehouse operations, transport management, on-site logistics, maintenance). Changes and impact are aligned together and agreements are made in order to resolve potential issues. In case of need the related short-term to mid-term planning disciplines (e.g. procurement planning, distribution planning) are involved in order to check the impact on their plan.", "Outcome": "Impact of adjustments is evaluated and solutions have been aligned.", "GUID": "22a192d2-605d-11e9-2ddf-001bc640cd9b", "name": "Align adjustment needs with related planning disciplines and operations", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.392154084653731, "y": 0.28903654485049834, "z": -2.631477593929329 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1616", "text": "Process", "data": { "Advisory_Notes": "Insights from former forecasts need to be discussed and shared to ensure consideration in the next forecast cycle. This is especially important in case of manual forecasting.", "Type": "Business Process", "Description": "Purpose of reviewing the last forecast is to verify taken assumptions as well as information sources and to continuously improve the forecast accuracy. ", "Process_Group": "Demand Planning", "Scope": "Former forecasts are compared to actual figures. Depending on extend of deviation (forecast accuracy) root cause analyses might be conducted in order to optimize assumptions and inputs for the upcoming forecast cycles.", "Outcome": "Insights from former forecast cycles have been derived and shared.", "GUID": "ab363ebf-2632-11e9-2ddf-001bc640cd9b", "name": "Review former forecast cycles", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7927827046270122, "y": 0.2923588039867111, "z": -0.886527029475275 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1617", "text": "Process", "data": { "Advisory_Notes": "For manual forecasting it can be helpful to provide a statistical forecast based on historic data as a starting point. Sales department can use this as basis to adjust with information from further sources (e.g. knowledge about upcoming customer agreements or ending contracts). ", "Type": "Business Process", "Description": "Purpose of Initiate and monitor forecasting is to trigger and monitor the forecasting activities of the actual forecast cycle.", "Process_Group": "Demand Planning", "Scope": "***After running necessary preparations the conduction of the actual forecast cycle can be triggered by informing and instructing the different involved parties. ***The timely performance of forecasting activities as well as the provision of results needs to be closely monitored.", "Outcome": "outcome", "GUID": "ab363eb3-2632-11e9-2ddf-001bc640cd9b", "name": "Initiate and monitor forecasting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.6821978355416736, "y": 0.2956810631229234, "z": -1.3438060764171142 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1618", "text": "Process", "data": { "Advisory_Notes": "***It is important to document assumptions made in order to make use of this information during root-cause analyses within the review process. ***Also for manual forecast the aggregation/calculation logic needs to be carefully defined upfront in order to avoid blind spots or double counting during later consolidation of the individual forecast values. ***The aggregation level needs to be defined with care in order to allow for meaningful sales forecast without overly extensive efforts. Often sales forecasts are derived as monthly or quarterly figures on product type or group level per market or channel. ***The aggregation and consolidation rules and also the planning horizons need to be aligned with other planning disciplines. This task and the orchestration of the different planning disciplines is often considered as Sales & Operations Planning.", "Type": "Business Process", "Description": "Purpose of the manual Sales forecasting is to derive and maintain the actual forecast figures on the defined aggregation level.", "Process_Group": "Demand Planning", "Scope": "Based on available information (e.g. market intelligence, internal sources, specific customer information) and own experience the expected Sales figures are derived, validated Sales internally and maintained within the demand planning tool.", "Outcome": "Sales forecast has been derived, validated and provided to the demand planning.", "GUID": "ab363ebb-2632-11e9-2ddf-001bc640cd9b", "name": "Derive manual sales forecast", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.5668647574910275, "y": 0.2990033222591362, "z": -1.810380015844318 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1619", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of the alignment with the Service Organization is to consider impact of running or upcoming service and after sales activities on the sales figures within the forecasting horizon.", "Process_Group": "Demand Planning", "Scope": "The derived Sales forecast is presented and explained to the Service Organization. The Service Organization presents running or upcoming activities in order to identify potential impacts. Identified impacts are quantified together. The forecast is adjusted accordingly and reasons are documented.", "Outcome": "Impact of Service and After Sales activities has been considered in forecast", "GUID": "ab363ed4-2632-11e9-2ddf-001bc640cd9b", "name": "Align forecast with service organization", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.446710744412595, "y": 0.30232558139534893, "z": -2.2862116165231923 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1620", "text": "Process", "data": { "Advisory_Notes": "***The actual consolidation logic depends on the granularity level the forecast is being derived in and how it is going to be used during master planning. ***The aggregation and consolidation rules and also the planning horizons need to be aligned with other planning disciplines. This task and the orchestration of the different planning disciplines is often considered as Sales & Operations Planning.", "Type": "Business Process", "Description": "Purpose of the forecast consolidation for a specific business unit is to provide the overview on aggregated level and to prepare forecast information for the upcoming alignments.", "Process_Group": "Demand Planning", "Scope": "***Single forecast inputs are gathered and a first quality check is conducted. The validated inputs are combined in order to derive the consolidated overall forecast on business unit level. ***If needed documentation on assumptions is completed.", "Outcome": "All forecast data for the respective business unit has been consolidated to one central business unit sales forecast.", "GUID": "4d8735f4-2640-11e9-2ddf-001bc640cd9b", "name": "Consolidate sales forecast for business unit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.321663330181729, "y": 0.30564784053156124, "z": -2.7712631416376023 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1621", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of the alignment with Marketing is to consider impact of running or upcoming marketing activities such campaigns on the sales figures within the forecasting horizon.", "Process_Group": "Demand Planning", "Scope": "The derived Sales forecast is presented and explained to Marketing. Marketing presents running or upcoming activities in order to identify potential impacts. Identified impacts are quantified together. The forecast is adjusted accordingly and reasons are documented.", "Outcome": "Impact of Marketing activities has been considered in forecast.", "GUID": "ab363eca-2632-11e9-2ddf-001bc640cd9b", "name": "Align forecast with marketing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.76904294625888, "y": 0.308970099667774, "z": -0.9329989572832875 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1622", "text": "Process", "data": { "Advisory_Notes": "Consideration of M&A activities could also be part of this process.", "Type": "Business Process", "Description": "Purpose of the alignment with projects is to consider impact of running or upcoming projects on the sales figures within the forecasting horizon.", "Process_Group": "Demand Planning", "Scope": "The derived Sales forecast is presented and explained to the different Project Managements or the Project Portfolio Management in order to identify potential impacts. Identified impacts are quantified together. The forecast is adjusted accordingly and reasons are documented.", "Outcome": "Impact of projects has been considered in forecast.", "GUID": "ab363ed9-2632-11e9-2ddf-001bc640cd9b", "name": "Align forecast with projects", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.646224907453517, "y": 0.31229235880398676, "z": -1.413327187587017 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1623", "text": "Process", "data": { "Advisory_Notes": "***Some of the follow-up activities might be tasks for other planning disciplines and would then be considered again during master planning. Other identified deviations might lead to new sales, project, marketing, R&D or service activities. These should then also consider additional information from Master planning, since master planning might lead to adjusted forecast figures. ***The comparison of budget and forecast needs to be conducted with care. Deviation can not be avoided and the extend highly depends on the process how the budget is derived. It is strongly recommended to not misuse budget figures as forecast neglecting other more actual information sources. When forecast consists of budget data only you should rather not setup any demand planning processes at all.", "Type": "Business Process", "Description": "Purpose of the alignment with the Financial Planning is to identify deviation between forecast and budget and to be able to provide early feedback on budget fulfillment.", "Process_Group": "Demand Planning", "Scope": "The derived Sales forecast is compared to budget. In case of major deviations (especially but not limited to shortfalls) main drivers are identified. The documented assumptions of the forecast might be re-evaluated or follow-up activities might be defined in order to keep up with budget. Potentially the forecast data is adjusted to cover the impact of defined countermeasures to specific budget shortfalls.", "Outcome": "Deviation of forecast to budget has been identified. Potentially countermeasures have been defined or initiatives have been started to do so.", "GUID": "4d8735ea-2640-11e9-2ddf-001bc640cd9b", "name": "Align forecast with financial planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.5184177722241596, "y": 0.3156146179401995, "z": -1.9028232655969872 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1624", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to finalize the forecast and approve it for further usage in master planning.", "Process_Group": "Demand Planning", "Scope": "The previously aligned figures receive a last quality check. The approval process for sales forecast is run. After approval the forecast is provided to master planning.", "Outcome": "The sales forecast has been approved and is available for master planning.", "GUID": "ab363eb7-2632-11e9-2ddf-001bc640cd9b", "name": "Approve sales forecast", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.385549810627374, "y": 0.31893687707641183, "z": -2.4014480753300087 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1625", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to adjust the sales forecast according to insights from S&OP alignment meetings.", "Process_Group": "Demand Planning", "Scope": "The approved forecast is being adjusted according to decisions from mutual S&OP alignment meetings. The adjusted forecast is communicated to all related stakeholders.", "Outcome": "The sales forecast has been adjusted to fit the overall and mutually aligned Sales & Operations Plan.", "GUID": "629eacbd-5f71-11e9-2ddf-001bc640cd9b", "name": "Adjust sales forecast according to S&OP alignment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.24754956575971, "y": 0.3222591362126246, "z": -2.90916200217435 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1626", "text": "Process", "data": { "Advisory_Notes": "R&D impacts might be related to new product development (phase-in / phase-out), changes to existing products (incl. components, intermediates or raw materials) as well as major changes in production technology.", "Type": "Business Process", "Description": "Purpose of the alignment with Research & Development (R&D) is to consider impact of running or upcoming technological and product developments on the sales figures within the forecasting horizon.", "Process_Group": "Demand Planning", "Scope": "The derived Sales forecast is presented and explained to R&D. R&D presents running or upcoming activities in order to identify potential impacts. Identified impacts are quantified together. The forecast is adjusted accordingly and reasons are documented.", "Outcome": "Impact of R&D activities has been considered in forecast.", "GUID": "ab363ed0-2632-11e9-2ddf-001bc640cd9b", "name": "Align forecast with Research & Development", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7440988162876152, "y": 0.32558139534883734, "z": -0.9788356956221712 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1627", "text": "Process", "data": { "Advisory_Notes": "***Even if the final consolidated forecast will be input to Master Planning it is recommended to already consider information from Supply Chain in order to adjust assumptions and restrictions before starting to work on the Sales forecast itself. ***Master planning (and subsequent all other planning disciplines) is often involved in order to provide this information (e.g. major restrictions of capacities for a certain product range).", "Type": "Business Process", "Description": "Purpose of the clarification of Supply Chain assumptions is to be able to consider important restrictions in order to reduce later adjustment efforts.", "Process_Group": "Master Planning", "Scope": "Already known restrictions within the supply chain are retrieved and prepared as guidance for the later forecast conduction.", "Outcome": "Major restrictions coming from Supply Chain are known and can be considered during forecasting.", "GUID": "4d8735e4-2640-11e9-2ddf-001bc640cd9b", "name": "Clarify supply chain assumptions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.608450418730116, "y": 0.32890365448504966, "z": -1.4818860998830794 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1635", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Allocate internal resources to maintenance order,\n Request external resources for maintenance order", "Type": "Business Process", "Description": "This process ensures the allocation of resources required to perform plant maintenance.", "Process_Group": "Plant Maintenance Operations", "hasAssignment": true, "Scope": "It is necessary to determine the individual internal resources needed for specific maintenance activities, and when they are needed. Planning enables the availability of the resources at the time they are required.", "Outcome": "Resources are assigned to the maintenance order", "GUID": "e46f703c-e800-11e4-0a66-001bc640cd9b", "name": "Assign resources to maintenance order", "Business_Rules": "", "Prerequisite": "Internal resources allocated to maintenance order" }, "position": { "x": -3.4675754338869895, "y": 0.3322259136212624, "z": -1.9939710655632537 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1637", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Evaluate request for additional external resources,\n Specify alternative internal resource,\n Approve request for additional external resources,\n Plan additional external resource,\n Trigger planning or alternative internal resource,\n Trigger procurement of external resource", "Type": "Business Process", "Description": "Additional resources may be required to perform plant maintenance. In such cases it is necessary determine the individual resources needed for specific maintenance activities, and when they are needed. Planning enables the availability of the resources at the time they are required.", "Process_Group": "Plant Maintenance Operations", "hasAssignment": true, "Scope": "External resources are planned against the maintenance order. If an additional external service is required immediately, the maintenance planner will change the settings on the maintenance order so that a purchase requisition for the external service is generated immediately.", "Outcome": "Additional external resources are incorporated into the maintenance plan.", "GUID": "7bbc6aba-7eee-11e5-0a66-001bc640cd9b", "name": "Plan additional external resources", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.321403176767877, "y": 0.33554817275747517, "z": -2.515049618560337 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1639", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Maintain settlement rule in controlling,\n Verify correctness of cost allocated to maintenance,\n Adjust line items manually,\n Analyze activity related variances,\n Analyze material related variances,\n Settle variances,\n Settlement posting", "Type": "Business Process", "Description": "The costs that arise from processing an order (for example, costs for material, personnel, or external services) must be allocated to the correct cost object.", "hasAssignment": true, "Process_Group": "Overhead Cost Controlling", "Scope": "The costs are initially collected on the order, and when the order is technically completed, the costs are transferred to the settlement receiver specified in the settlement rule.", "Outcome": "All costs related to the maintenance order are settled.", "GUID": "18d52036-51b1-11e5-0a66-001bc640cd9b", "name": "Settle maintenance order", "Business_Rules": "", "Prerequisite": "An order can be settled if: It is released It has the status settlement rule created Costs collected for it have not yet been settled A business completion has not yet been performed for it" }, "position": { "x": -5.169863248338688, "y": 0.33887043189368793, "z": -3.0450802934367687 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1641", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Forward request for approval,\n Specify problem for corrective maintence,\n Define required maintenance activities", "Type": "Business Process", "Description": "When the need for corrective maintenance arises, the details must be recorded and made available for evaluation and approval. A corrective maintenance request is a targeted instruction to perform an activity in the manner described.", "Process_Group": "Plant Maintenance Asset Management", "hasAssignment": true, "Scope": "A corrective maintenance request is entered in the system by a maintenance requestor. The requestor maybe a maintenance technician who can create a corrective maintenance request from a mobile device whilst conducting preventive maintenance.", "Outcome": "Details regarding required corrective maintenance are recorded.", "GUID": "dd4a5383-e7ff-11e4-0a66-001bc640cd9b", "name": "Maintain corrective maintenance request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7179672967779376, "y": 0.34219269102990024, "z": -1.0240060386548049 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1643", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Execute plant maintenance work,\n Collect required materials,\n Record maintenance activities,\n Inform asset accounting,\n Inform EHS about harmful substances,\n Maintenance activity posting", "Type": "Business Process", "Description": "Plant maintenance must be executed as specified in the maintenance plan, with tracking of time and task completion. For dismantling, asset accounting is informed and EH&S is informed about harmful substances have to be transported when the asset is dismantled.", "hasAssignment": true, "Process_Group": "Plant Maintenance Operations", "Scope": "Having collected the required materials, the maintenance technician conducts the planned maintenance as described in the shop papers. All activities performed are tracked and documented accordingly.", "Outcome": "All activities related to the plant maintenance are performed", "GUID": "73e0f9e8-e802-11e4-0a66-001bc640cd9b", "name": "Perform plant maintenance", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.5689000863963933, "y": 0.345514950166113, "z": -1.5494361381201234 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1645", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Release plant maintenance order,\n Print shop papers,\n Prepare shop floor documentation,\n Inform shop floor staff and provide shop floor papers", "Type": "Business Process", "Description": "Approval of planned activities is given with the release of the maintenance order. This initiates execution of all activities related to the maintenance order.", "hasAssignment": true, "Process_Group": "Plant Maintenance Operations", "Scope": "Release of a maintenance order represents the approval of the planned activities, such as purchasing of services and materials, as well as the usage of planned materials from stock. After the maintenance order is released shop papers are printed. These are the maintenance instructions for the maintenance technician.", "Outcome": "Maintenance order is released and maintenance activities can be executed.", "GUID": "7bbc6ad8-7eee-11e5-0a66-001bc640cd9b", "name": "Release maintenance order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.4143723561493853, "y": 0.34883720930232576, "z": -2.083761361951722 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1647", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Set maintenance order status to technically completion,\n Check for open purchase orders,\n Remove reservations on maintenance order,\n Remove capacity requirements maintenance order,\n Investigate reason for open purchase order,\n Close purchase order,\n Align with vendor", "Type": "Business Process", "Description": "Technical completion of plant maintenance indicates that all planned activities of the order have been performed. This activity demonstrates that all existing reservations, open commitments and planned capacities are no longer needed.", "Process_Group": "Plant Maintenance Operations", "hasAssignment": true, "Scope": "Once the maintenance work planned in the order has been performed, results verified and accepted, the order is marked as complete for plant maintenance.", "Outcome": "The plant maintenance order obtains the status Technically completed.", "GUID": "7bbc6aa8-7eee-11e5-0a66-001bc640cd9b", "name": "Complete maintenance order technically", "Business_Rules": "A business rule should enforce timely setting of the status to release unused resources and avoid faulty recording of working hours or material consumptions.", "Prerequisite": "" }, "position": { "x": -4.25431451412226, "y": 0.35215946843853807, "z": -2.6269389058234074 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1649", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Assess components availability,\n Confirm maintenance plan,\n Create maintenance order,\n Create/update maintenance plan,\n Trigger components request for maintenance", "Type": "Business Process", "Description": "The maintenance plan demonstrates that tasks will be done on time, that the technical objects are available and that all required resources, such as internal and external resources and materials, are on hand. The maintenance tasks that are to be performed require detailed planning, in order to minimize the time that the object is not productive.", "Process_Group": "Plant Maintenance Operations", "hasAssignment": true, "Scope": "For preventative maintenance, the maintenance order is created based on planned tasks that are required when specific predefined circumstances are given. Those can be described by specific parameters , which are verified regularly, by measuring usage (discrete counter or running time), or by a period after which refurbishment is due. Subsequently the maintenance plan is compiled. For corrective maintenance (including refurbishment), planning is done after a maintenance request is approved (or planned order converted) and the maintenance order is created. In both cases, the maintenance plan provides a clear definition of tasks to be performed, roles and responsibilities, and dates.", "Outcome": "Maintenance plan is created.", "GUID": "7bbc6a9c-7eee-11e5-0a66-001bc640cd9b", "name": "Plan maintenance order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.088657267078221, "y": 0.3554817275747508, "z": -3.1789254817016404 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1651", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Approve maintenance request,\n Create corrective maintenance order,\n Evaluate maintenance request,\n Trigger disposal of equipment,\n Trigger recycling of equipment", "Type": "Business Process", "Description": "The request must be evaluated to determine whether corrective maintenance is actually required. Approval of the request initiates the planning of required tasks to fulfil corrective maintenance procedures.", "Process_Group": "Plant Maintenance Asset Management", "hasAssignment": true, "Scope": "Requests for maintenance are evaluated by the maintenance approver, who may either approve or reject the request. After the approval of a corrective maintenance request, a corrective maintenance order is created.", "Outcome": "A corrective maintenance order is created.", "GUID": "7bbc6acc-7eee-11e5-0a66-001bc640cd9b", "name": "Evaluate and approve maintenance request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6906661781741708, "y": 0.3588039867109636, "z": -1.0684792342286973 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1653", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Request material availability check,\n Review request for work clearance approval,\n Request work clearance approval,\n Evaluate work clearance approval requirement,\n Act on policy for work clearance denial", "Type": "Business Process", "Description": "Approvals are used to define certain rules or requirements that must be observed in Work Clearance Management.", "Process_Group": "Plant Maintenance Operations", "hasAssignment": true, "Scope": "The Maintenance Approver evaluates whether work clearance approval is required or not. In case work clearance approval is required, the maintenance planner requests work clearance approval and the maintenance approver either accepts or rejects the request.", "Outcome": "Decision is made whether work clearance is required or not.", "GUID": "7bbc6abd-7eee-11e5-0a66-001bc640cd9b", "name": "Evaluate work clearance approval", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.5276008364788005, "y": 0.3621262458471759, "z": -1.6159313139585079 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1655", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify cost settlement,\n Verify posting and clearance of payments,\n Set maintenance order status to commercially complete,\n Act on policy for maintenance order exceptions", "Type": "Business Process", "Description": "Commercial completion of the plant maintenance order indicates that all costs related to the order have been settled. This process pertains to the business completion of an order when no further costs are expected to be posted to the order.", "Process_Group": "Plant Maintenance Operations", "hasAssignment": true, "Scope": "Typically, maintenance orders are set to commercially complete by a batch process after a defined period of time.", "Outcome": "The order obtains the status Completed, which indicates full completion.", "GUID": "7bbc6aae-7eee-11e5-0a66-001bc640cd9b", "name": "Complete maintenance order commercially", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.358844759882168, "y": 0.36544850498338866, "z": -2.172133025164919 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1657", "text": "Process", "data": { "Advisory_Notes": "Pre-requisites: each material, whose availability is checked, must be assigned a checking group on the MRP detail screen in its material master. The checking group combines materials whose availability is checked at the same time. You can, for instance, group materials according to the material type or the MRP type.", "KeyActivities": "Confirm material availability,\n Determine date of material availability,\n Adapt maintenance plan to material availability,\n Check material availibility,\n Trigger material procurement", "Type": "Business Process", "Description": "Before the maintenance order can be released, it is necessary to check whether materials needed to conduct the maintenance are available.", "hasAssignment": true, "Process_Group": "Demand Planning", "Scope": "The system checks whether material components in networks are available on the required date. If the requirements are not covered, the system determines the date on which they can be covered. During the check, it is also possible to run simulations to know how changes in demand or supply conditions will affect the availability of material.", "Outcome": "Availability of required material is determined.", "GUID": "7d178dc7-7eee-11e5-0a66-001bc640cd9b", "name": "Check material availability", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.184329496923781, "y": 0.3687707641196014, "z": -2.737039762439263 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1659", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify results of maintenance,\n Confirm plant maintenance order,\n Reject completion of maintenance,\n Request rework,\n Perform rework of maintenace,\n Accept results of maintenance", "Type": "Business Process", "Description": "Completion of plant maintenance activities must be followed by confirmation and verification of results.", "Process_Group": "Plant Maintenance Operations", "hasAssignment": true, "Scope": "Once all planned activities have been performed, the Maintenance coordinator checks whether maintenance has been executed and documented as required. The Maintenance coordinator either: 1. Accepts the maintenance as successfully completed 2. Requests follow up maintenance and accepts the maintenance as having been completed 3. Rejects the completion of the maintenance, and asks for the maintenance to be completed.", "Outcome": "Completion of plant maintenance activities is verified.", "GUID": "7d178dc1-7eee-11e5-0a66-001bc640cd9b", "name": "Confirm plant maintenance order and verify results", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -5.003986907339268, "y": 0.37209302325581417, "z": -3.3106064446226755 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1661", "text": "Process", "data": { "Advisory_Notes": "For refurbishment orders, goods issue posting is performed using transaction MB1A (not MIGO).", "KeyActivities": "Post goods issue,\n Inform maintenance responsible to collect goods,\n Material consumption (maintenance) posting", "Type": "Business Process", "Description": "Parts designated for refurbishment must be taken from the plant to the area where the refurbishment is performed. This must be accompanied by the relevant goods issue posting.", "Process_Group": "Outbound Delivery Management", "hasAssignment": true, "Scope": "Goods issue is posted with reference to the maintenance order to inform the responsible that parts can be moved to the refurbishment site.", "Outcome": "Goods issue with reference to maintenance order posted.", "GUID": "2348f377-7efc-11e5-0a66-001bc640cd9b", "name": "Perform goods issue for maintenance order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.662214047188442, "y": 0.3754152823920265, "z": -1.112225004812165 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1665", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect reusable materials,\n Determine value of reusable material ,\n Post goods receipt of reusable material from scrapping,\n Inventory increase (plant maintenance) posting", "Type": "Business Process", "Description": "This process is used to record and store any reusable material derived from scrapping.", "Process_Group": "Warehouse Operations", "hasAssignment": true, "Scope": "After scrapping of asset is complete, components that can be reused are placed in a storage location with recording of the receipt into the warehouse.", "Outcome": "Goods receipt of material from strapping posted.", "GUID": "feff4062-7ef0-11e5-0a66-001bc640cd9b", "name": "Store reusable materials", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.484580785673955, "y": 0.37873754152823924, "z": -1.6813263572131953 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1667", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Evaluate condition of asset,\n Trigger sale of asset,\n Trigger scrapping of asset,\n Trigger disposal of asset", "Type": "Business Process", "Description": "When an asset can no longer be used, it is necessary to define further steps to finalize its phasing out.", "hasAssignment": true, "Process_Group": "Plant Maintenance Asset Management", "Scope": "The maintenance manager evaluates the asset to get a view of the asset condition. In doing this, a decision is made on whether to sell, scrap or dispose the asset.", "Outcome": "Decision is made whether to sell, scrap or dispose the asset.", "GUID": "21fda555-7ef0-11e5-0a66-001bc640cd9b", "name": "Analyze asset condition", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.3010304484977815, "y": 0.382059800664452, "z": -2.2590258914165933 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1669", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Align with cost center responsible for scrapped asset,\n Process proceeds from sale of scrapping components,\n Post profit on disposal of scrapping ,\n Post loss on disposal for scrapped asset,\n Settle net book value of asset in asset clearing account,\n Set deactivation date in asset master,\n Get approval for asset transfer,\n Transfer asset to receiving cost center,\n Get approval for recycling of asset components,\n Trigger recycling of asset components,\n Approve asset scrapping,\n Execute/ monitor asset scrapping,\n Trigger service procurement for asset scrapping", "Type": "Business Process", "Description": "This process covers the scrapping of a fixed asset within asset accounting.", "Process_Group": "Asset Accounting", "hasAssignment": true, "Scope": "When an asset is scrapped, the following activities must be performed: ***Post the net book value to expenses ***Set date of deactivation in asset master ***Return information to scrapping requestor", "Outcome": "Asset scrapping posted and requestor informed.", "GUID": "feff4065-7ef0-11e5-0a66-001bc640cd9b", "name": "Scrap asset", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.111495771255623, "y": 0.3853820598006643, "z": -2.84527723129876 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1671", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Determine asset with technical weak points,\n Determine high costs generating asset,\n Determine asset non-conform with safety standards,\n Determine asset non-conform with environmental standards,\n Set asset to inactive,\n Review outstanding order,\n Set maintenance plans to inactive ,\n Allocate outstanding order to other asset,\n Close outstanding orders,\n Archive asset master data,\n Create maintence order for asset dismantling", "Type": "Business Process", "Description": "If a technical asset is no longer fit to be used and it no longer makes sense, for economic or technical reasons, to continue using that asset as a resource, it must be removed from productive use.", "Process_Group": "Phase Out", "hasAssignment": true, "Scope": "The following activities are performed: ***Determine technical weak points ***Determine assets that generate very high costs ***Determine which assets no longer meets the required technical, business, safety, and environmental standards", "Outcome": "Asset phased out and no longer available for use", "GUID": "feff406b-7ef0-11e5-0a66-001bc640cd9b", "name": "Phase out asset", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.915909813045685, "y": 0.38870431893687707, "z": -3.4400335332669556 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1673", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Determine value of asset to be sold,\n Search potential buyers,\n Negotiate sale terms and conditions,\n Select buyer of asset", "Type": "Business Process", "Description": "After the decision has been taken to sell an asset, it is necessary to find a buyer and negotiate the terms of the sale.", "Process_Group": "Customer Relationship Mgmt", "hasAssignment": true, "Scope": "The remaining value of the asset is defined and based on that, negotiations are conducted with several potential buyers. The sale agreement is made with the buyer offering the best terms and conditions.", "Outcome": "Buyer found and sale terms and conditions defined.", "GUID": "feff4071-7ef0-11e5-0a66-001bc640cd9b", "name": "Negotiate sale and select buyer of asset", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6326302741467673, "y": 0.3920265780730898, "z": -1.1552135681074092 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1675", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Refer to asset sales condition,\n Verify receipt of down payment,\n Plan transportation of asset,\n Send reminder to buyer about down payment,\n Give asset to buyer,\n Trigger procurement of service for asset transport,\n Confirm hand over of asset to buyer,\n Monitor asset handover to buyer", "Type": "Business Process", "Description": "In handing over of physical possession of the asset to the buyer, it is necessary to define the means of transportation and who will cover the transportation cost, as well as record the sale.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "Once sale consideration or the down payment (as per negotiated terms of payment approved has been received, the possession of the asset is handed over to the buyer. If a portion of sale consideration is deferred, i.e. payable over a span of time, the rightful title of the asset can not be transferred to the purchaser. However, the buyer will take possession of the asset on depositing down payment and may be required to pay interest on the deferred part of sale.", "Outcome": "Asset is in possession of the buyer.", "GUID": "feff4074-7ef0-11e5-0a66-001bc640cd9b", "name": "Hand over asset to buyer", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.4398692222066964, "y": 0.39534883720930214, "z": -1.745576746673858 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1677", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create manual FI invoice for asset sale,\n Reference asset sale to approval document,\n Post asset sale to accounts receivable,\n Post asset retirement,\n Release asset from cost center,\n Remove asset from asset register,\n Accounts receivable posting,\n Revenue posting", "Type": "Business Process", "Description": "This reflects the sale of an asset which has been approved by management or the cost center responsible for scrapping and/ or sale.", "Process_Group": "Billing, Rebates and Commissions", "hasAssignment": true, "Scope": "The asset is sold upon negotiation of the selling price.There will be no sales order connected to this process and a manual invoice will be required.", "Outcome": "Asset sale is complete.", "GUID": "feff4098-7ef0-11e5-0a66-001bc640cd9b", "name": "Sell asset", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.24096878221359, "y": 0.3986710963455149, "z": -2.344380803691448 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1682", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Document end condition after refurbishment,\n Collect required materials,\n Execute Refurbishment work,\n Inform EHS about harmful substances", "Type": "Business Process", "Description": "Refurbishment involves the restoration of faulty repairable equipment. Related activities must be executed as specified in the maintenance plan, with tracking of time and task completion.", "hasAssignment": true, "Process_Group": "Plant Maintenance Operations", "Scope": "The repairable equipment is brought from an initial damaged condition to an end condition at which it can be used again. The maintenance technician performs the refurbishment of the equipment as described in the shop papers and provides confirmation upon completion.", "Outcome": "All activities related to refurbishment are performed.", "GUID": "1d89eb24-51b0-11e5-0a66-001bc640cd9b", "name": "Perform refurbishment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.0358629226132186, "y": 0.40199335548172765, "z": -2.951577623894701 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1684", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create refurbishment order,\n Enter number of repairable spares,\n Specify materials and utilities,\n Save refurbishment order,\n Enter plant and storage location,\n Specify time frame for the refurbishment,\n Specify necessary operations", "Type": "Business Process", "Description": "Repair/refurbishment can be triggered by an approved refurbishment maintenance request. In such cases, a refurbishment order is created from the request notification. A Refurbishment order is a special order, which is used for the refurbishment of repairable spares, and for which the order type must be specially selected in the system.", "Process_Group": "Plant Maintenance Operations", "hasAssignment": true, "Scope": "A refurbishment order is maintained in the system, which defines how many repairable spares managed in stock (if necessary, these can be identified uniquely by serial number) are to be refurbished for a particular material. The planner determines the time frame for the refurbishment and plans all the necessary operations, materials, utilities and so on.", "Outcome": "Refurbishment order is created", "GUID": "233ac2c4-7efc-11e5-0a66-001bc640cd9b", "name": "Create refurbishment maintenance order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.824485947440017, "y": 0.4053156146179404, "z": -3.567118633148301 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1686", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify if refurbishment is needed,\n Approve refurbishment request,\n Maintain refurbishment request,\n Forward refurbishment request for approval,\n Trigger disposal of equipment,\n Reject refurbishment request,\n Trigger recycling of equipment", "Type": "Business Process", "Description": "When a request for refurbishment is sent, all relevant details must be documented and then evaluated in order to determine whether to proceeded with creation of a refurbishment order.", "hasAssignment": true, "Process_Group": "Field Services", "Scope": "A refurbishment maintenance request is maintained in the system. It is then evaluated by the maintenance approver who may either approve or reject the request. If approved, the request notification forms the basis for creating the refurbishment order.", "Outcome": "Decision made whether to accept or reject the request.", "GUID": "233ac2a9-7efc-11e5-0a66-001bc640cd9b", "name": "Receive and process refurbishment request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6019349998016603, "y": 0.4086378737541527, "z": -1.1974156573264167 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1688", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify results,\n Confirm refurbishment,\n Send refurbished equipment to storage location ,\n Allocate refurbishment cost to cost collector,\n Capitalize refurbishment cost,\n Expense refurbishment cost to P&L,\n Trigger scrapping,\n Prepare transfer documentation", "Type": "Business Process", "Description": "Completion of Refurbishment activities must be followed by confirmation and verification of results, as well as entry of costs and settlement.", "Process_Group": "Plant Maintenance Operations", "hasAssignment": true, "Scope": "Once all refurbishment activities have been performed, the maintenance technician confirms work performed. The maintenance coordinator then checks whether refurbishment has been successful, whether follow-up work is required or whether a part needs to be scrapped. After this, related costs are either capitalized or expense according to accounting rules. Generally, If the refurbishment/repair is of a material nature i.e. a major overhaul or the repair of a major component of a machine, the amount is capitalized because the benefit is for more than the current period.", "Outcome": "Completion of Refurbishment is verified.", "GUID": "233ac2a3-7efc-11e5-0a66-001bc640cd9b", "name": "Confirm refurbishment and verify results", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.3934965858905306, "y": 0.4119601328903655, "z": -1.8086387404151147 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1690", "text": "Process", "data": { "Advisory_Notes": "MRP can be used to generate planned orders for refurbishment for rotable or repairable material types. Special settings in the material master are required to activate this process.", "KeyActivities": "Enter material to be converted,\n Convert planned order to refurbishment order,\n Save refurbishment order,\n Enter plant and storage location,\n Specify materials and utilities,\n Specify time frame for the refurbishment,\n Specify necessary operations", "Type": "Business Process", "Description": "Specific refurbishment are planned by creating planned orders in material requirements planning (MRP). When required, the planned order is converted into a refurbishment order to start the refurbishment process.", "Process_Group": "Production Scheduling", "hasAssignment": true, "Scope": "Refurbishment process is started by converting the planned order into a refurbishment order. The planned order provides the quantity and dates for the refurbishment order.", "Outcome": "Planned order converted into refurbishment order.", "GUID": "2359bc58-7efc-11e5-0a66-001bc640cd9b", "name": "Convert planned order into refurbishment order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.1787006512552685, "y": 0.41528239202657824, "z": -2.4281396520194902 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1698", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update documents,\n Dismantle and clean machinery or equipment,\n Execute assembly ,\n Label product,\n Package product", "Type": "Business Process", "Description": "After all preparations are carried out, the actually assembly work can be performed place. Besides the assembly of the products the process usually includes also labeling and packing.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "The work tasks for the assembly are performed. This includes setting-up and dismantling of machines and tools if necessary.", "Outcome": "The product is assembled, packaged, labelled and ready to be putaway.", "GUID": "baf08428-7f1a-11e5-0a66-001bc640cd9b", "name": "Assemble products", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.957482442146272, "y": 0.41860465116279055, "z": -3.055868570489244 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1700", "text": "Process", "data": { "Advisory_Notes": "Within the material master and BOM it must be defined whether back flushing or any other specific type of GI (e.g. pipeline) can and will be performed.", "KeyActivities": "Weigh material,\n Confirm time recordings,\n Record process parameters,\n Perform backflush of materials,\n Material consumption posting", "Type": "Business Process", "Description": "To reflect the actual stock situation, component consumption, which takes place during the manufacturing process must be recorded and stock level in the shop-floor papers lowered accordingly. In manufacturing this is often done via backflushing for components, which are not explicitly counted or weighed. Component consumption is recorded only after finishing the actual manufacturing operation calculated using the BOM or recipe and the actual recorded quantity of produced goods. Additionally or alternatively the consumption of material can be entered via scanner or manually in advance.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "The recording of material consumption for manufacturing process is carried out before, during, or after finishing manufacturing operation. The goods issue adjusts inventory and the value of the components is accounted to the order as actual costs.", "Outcome": "Goods issues are posted", "GUID": "baf083fe-7f1a-11e5-0a66-001bc640cd9b", "name": "Perform consumption for production", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.72977755226027, "y": 0.4219269102990033, "z": -3.691775224215966 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1702", "text": "Process", "data": { "Advisory_Notes": "Use a Sales BOM where there is a fixed combination of components and the customer needs confirmation of each item. The component items cannot be altered or removed from a sales order. Other items cannot be inserted between the parent and component items in the sales order. However, the quantities of the component items can be modified. Use the Assembly BOM when you would not expect the customer to check each component in the order.", "KeyActivities": "Create assembly order", "Type": "Business Process", "Description": "Assembly orders are used for highly standardized make to order products which typically have a short delivery time. In order to expedite the process an assembly order is automatically created after saving the sales order based on master data settings for BOM and routing.", "Process_Group": "Production Scheduling", "hasAssignment": true, "Scope": "Based on master data, a production order for assembly is generated.", "Outcome": "Assembly order created.", "GUID": "baf08422-7f1a-11e5-0a66-001bc640cd9b", "name": "Convert sales order demand to assembly order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5701491216202217, "y": 0.42524916943521607, "z": -1.2388025411159143 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1704", "text": "Process", "data": { "Advisory_Notes": "Capturing of working times and posting on the production order can be done automatically in case of electronic work sheets.", "KeyActivities": "Update capacity,\n Complete production order,\n Maintain serial number and batch number used in production,\n Maintain time postings,\n Production activity posting,\n Production material variance posting,\n Work in progress posting", "Type": "Business Process", "Description": "After the production is finished, the process order related to it must be confirmed. This represents the technical closure of the production.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "The production or process order confirmation takes place after the manufacturing process is finished. Confirmation can be performed for an order, for a completed manufacturing phase (milestone) or a single production step and is used to finally record and confirm produced quantity of goods, used resources and performed activities as well as actual order completion dates. Depending on set-up this process can have impact on production planning by reducing planned production quantities, reducing capacity load, making adjustments to dependent requirements for components etc.", "Outcome": "The confirmed production steps or the complete order is considered as technically closed. No further activities can be performed on it. However, commercial closure will be done later - typically in a month end procedure in controlling.", "GUID": "baf08401-7f1a-11e5-0a66-001bc640cd9b", "name": "Confirm production", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.3454944474040906, "y": 0.4285714285714284, "z": -1.8704694055761992 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1706", "text": "Process", "data": { "Advisory_Notes": "There are three options for production preparation: ***using PI Sheet (production instructions in electronic form) ***using shop floor papers (paper based solution) ***transfer production instructions to an external manufacturing control system. PI sheets (including electronic signatures) are often used in the pharmaceutical industry in order to comply with regulatory requirements concerning batch records.", "KeyActivities": "Trigger production supply,\n Set up machinery or equipment,\n Print shop floor papers", "Type": "Business Process", "Description": "After the production or after the process order is released shop-floor papers (alternative via electronic files) are generated and the supply of necessary materials to the production initiated.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "The production preparation process covers all activities required to start manufacturing based on the released process order or production order. Information about the actual manufacturing process and control parameters and instructions for the production operators must be transferred to the production control to be carried out (for this purpose control recipes are used). Shop-floor papers for the coordination of manufacturing tasks must be created and material supply to production initiated.", "Outcome": "All preparation steps for production are performed, physical manufacturing can start.", "GUID": "712673e8-7f1e-11e5-0a66-001bc640cd9b", "name": "Prepare production (Paper-based)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.1142684480185894, "y": 0.43189368770764114, "z": -2.5102454130375156 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1708", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review missing parts list,\n Assign batch,\n Trigger manufacturing rescheduling,\n Schedule assembly order,\n Set assembly order status to release", "Type": "Business Process", "Description": "Once an assembly order is created, the system copies the routing and BOM into the production order and performs the calculation of capacity and cost, and schedules the order.", "hasAssignment": true, "Process_Group": "Production Scheduling", "Scope": "Master data get copied into the order and timelines, requirements, and costs are calculated. Finally, the production order has to be released.", "Outcome": "Production order for assembly scheduled, costs and requirements (material and capacity) generated and order released.", "GUID": "b5e81079-7f1a-11e5-0a66-001bc640cd9b", "name": "Schedule and release assembly order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.876407691603352, "y": 0.4352159468438539, "z": -3.1580790693835348 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1712", "text": "Process", "data": { "Advisory_Notes": "Regardless whether a process order gets created directly or via converting a planned order material, recipe and BOM related data get retrieved again from respective master data. Possible conversion options must be defined: ***one planned order to one process order, ***several planned orders to one process order, ***partial conversion of planned orders.", "KeyActivities": "Verify material and quantity for production,\n Verify scheduling type and production start date,\n Verify goods receipt options for quality inspection,\n Save and create process order,\n Verify materials and routing operations,\n Assign batch number", "Type": "Business Process", "Description": "Planned orders created in material requirement planning or detailed scheduling are only planning elements, in order to trigger actual manufacturing in process industry they must be converted to process orders.", "Process_Group": "Production Scheduling", "hasAssignment": true, "Scope": "Within a defined horizon, planned orders get converted in process orders to become executable. The conversion typically includes the adding of production specific information. A process order describes the production of batches (materials) in a production run or the rendering of services. It is generated from the master recipe and contains all the information specified during process planning. You use a process order to plan the quantities, dates, and resources of the manufacturing process, to control process order execution, and to define rules for the account assignment and settlement of the costs incurred. A recipe version is selected, its operations and sequences are transferred to the process order. The bill of materials (BOM) is exploded and the items in the BOM are transferred to the order. Reservations are generated for bill of material items held in stock. The planned costs for the order are generated. The capacity requirements are generated for the work centers. Purchase requisitions are generated for non-stock items and externally-processed operations.", "Outcome": "Planned order is partly or completely converted to a process order.", "GUID": "88c21232-7f1c-11e5-0a66-001bc640cd9b", "name": "Convert planned order to process order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.631849105365486, "y": 0.43853820598006665, "z": -3.81391843975785 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1714", "text": "Process", "data": { "Advisory_Notes": "If weighing systems are used, they might be directly connected to the system and integrated in the user dialog.", "KeyActivities": "Weigh material,\n Post goods issue for components used in production,\n Material consumption posting", "Type": "Business Process", "Description": "Goods issue for materials and components used within the production process have to be posted after delivery and when they are moved from the warehouse for further processing.", "hasAssignment": true, "Process_Group": "Outbound Delivery Management", "Scope": "Goods issues are performed for materials and components retrieved from stock used in the respective production step. Prior to the goods issue it is possible that weighing of components required for the production needs to be executed first.Goods issues are performed for materials and components retrieved from stock used in the respective production step. Prior to the goods issue it is possible that weighing of components required for the production needs to be executed first.", "Outcome": "Goods issues are posted.", "GUID": "f9a05553-7f25-11e5-0a66-001bc640cd9b", "name": "Perform goods issue of components for process order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5372942795570645, "y": 0.44186046511627897, "z": -1.2793460431177819 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1716", "text": "Process", "data": { "Advisory_Notes": "Set-up of manufacturing quality inspection must be defined-when it should be carried out (during production, based on first manufactured products, at end of production) and how it is initiated (information flow from production). Production monitoring setup, exchange of production relevant information with external systems (e.g. process messages), production and downtime reporting requirements must be defined. Label use (manufacturing, shipping, receiving, scanning, customer specific, general in-house label use) must be defined and considered for product labeling.", "KeyActivities": "Update documents,\n Dismantle and clean machinery or equipment,\n Execute production steps,\n Label product,\n Package product", "Type": "Business Process", "Description": "After all preparations are carried out, the physical production can take place. Besides the manufacturing of products the process usually includes also their labeling and packing.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "Physical manufacturing of products is carried out and monitored by production control. Prior to the actual production of goods it is possible that machines need to be set up and after goods are produced, they must be packed and labeled. After labeling and packing production tools need to be dismantled.", "Outcome": "Goods have been produced.", "GUID": "712673e2-7f1e-11e5-0a66-001bc640cd9b", "name": "Manufacture products", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.2958954867976824, "y": 0.4451827242524917, "z": -1.9310266475898339 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1718", "text": "Process", "data": { "Advisory_Notes": "The release will also impact the status of the material reservations of the components. Latest at this point in time, the reservations should be treated as firm and no other planning or logistics process should no longer have access to the reserved quantities.", "KeyActivities": "Select process order for release,\n Set process order status to release,\n Review missing parts list,\n Assign batch,\n Trigger manufacturing rescheduling", "Type": "Business Process", "Description": "Process orders can be created in advance to the planned manufacturing start date and are not bound to the availability of required materials or capacity. The release process represents the final step to initiate the manufacturing process. Unless the order is released, no further processing is possible.", "Process_Group": "Production Scheduling", "hasAssignment": true, "Scope": "Created process orders must be released, before they can be processed by production. The release is done, when the release date has been reached and when the required materials and capacity are available. The availability of materials and capacity should be checked within the release process. The process order release may also include batch determination and assignments.", "Outcome": "Process order is released.", "GUID": "cf57b45a-e9c8-11e4-0a66-001bc640cd9b", "name": "Release process order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.047716038208487, "y": 0.4485049833887045, "z": -2.5906421888108677 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1720", "text": "Process", "data": { "Advisory_Notes": "***It needs to be decided how the schedule is going to be fixed. Often fixation of planned orders or the conversion to process orders is used to show, that scheduling has been conducted.In addition it is useful to discuss frozen horizons in order to keep production schedule stable. ***Typically in scheduling the following aspects are taken into consideration: detailed capacities, change-over cost, alternative production versions/recipes, lot size optimization, component availability for JIT components. *** Real-time status information from shop floor integration systems might be used in order to keep schedule up to date.", "KeyActivities": "Review current production progress,\n Review planned orders (production plan),\n Create / adjust schedule,\n Resolve capacity overloads,\n Optimize change-over cost,\n Fix planned order,\n Optimize used production version,\n Resolve material availability issues (e.g. JIT-components),\n Escalate to production planning", "Type": "Business Process", "Description": "Planned orders are scheduled in order to determine the actual production sequence per machine/workplace.", "Process_Group": "Production Scheduling", "hasAssignment": true, "Scope": "After receiving planned orders from production planning these need to be brought into sequence for actual production. During this scheduling detailed restrictions of the different needed machines/workplaces are considered. Furthermore change-over optimization is conducted in order to achieve a cost efficient production sequence.", "Outcome": "Planned orders scheduled.", "GUID": "0f289faa-974c-11e9-0cfc-001bc641ce4f", "name": "Schedule planned orders", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.792693867003018, "y": 0.4518272425249168, "z": -3.258139535255925 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1722", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Add unavailable components to missing part list,\n Check actual stock and reservations for components,\n Trigger action in procurement,\n Trigger rescheduling ,\n Trigger action in quality", "Type": "Business Process", "Description": "Although requirements planning will initially have planned the availability of raw materials and components it is important to check and re-check the availability for production to avoid that any change in the actual stock situation may cause an interruption of the scheduled production. This can be a undelivered raw material or a missing component due to a break-down", "hasAssignment": true, "Process_Group": "Production Scheduling", "Scope": "Availability of the required components will be checked.", "Outcome": "Availability confirmed or missing parts component list is generated.", "GUID": "88c21250-7f1c-11e5-0a66-001bc640cd9b", "name": "Check component availability", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.530767276838964, "y": 0.45514950166112955, "z": -3.933465124178075 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1726", "text": "Process", "data": { "Advisory_Notes": "Within the material master and BOM it must be defined whether back flushing or any other specific type of GI (e.g. pipeline) can and will be performed.", "KeyActivities": "Weigh material,\n Post goods issue,\n Confirm time recordings,\n Confirm quanitity used,\n Record process parameters,\n Material consumption posting", "Type": "Business Process", "Description": "To reflect the actual stock situation, component consumption, which takes place during the manufacturing process must be recorded and stock level in the process instruction sheet lowered accordingly. In manufacturing this is often done via backflushing for components, which are not explicitly counted or weighed. Component consumption is recorded only after finishing the actual manufacturing operation calculated using the BOM or recipe and the actual recorded quantity of produced goods. Additionally or alternatively the consumption of material can be entered via scanner or manually in advance.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "The recording of material consumption for manufacturing process is carried out before, during, or after finishing manufacturing operation. The goods issue adjusts inventory and the value of the components is accounted to the order as actual costs.", "Outcome": "Consumption postings have been conducted.", "GUID": "d5ab3667-689a-11e8-2ddf-001bc640cd9b", "name": "Perform consumption for production in POD", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5033928413217386, "y": 0.4584717607973423, "z": -1.3190185611516427 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1728", "text": "Process", "data": { "Advisory_Notes": "***With a higher degree of shopfloor integration it is possible to automate the capturing of data directly from the interfaces of available machine execution systems (MES). ***captured data can directly be used for postings (e.g. consumption postings) or gathered for later processing after completion of process order. ***Milestone confirmation data can be used for process analyses (e.g. throughput times or interruptions). But it is essential to keep in mind that this needs to be heavily supported by master data design (esp. structure of recipes) as well as the discipline on the shopfloor in case of manual capturing.", "KeyActivities": "Select production process,\n Start milestone,\n Read instruction,\n Enter data,\n Confirm data,\n Confirm milestone", "Type": "Business Process", "Description": "During production process data is documented through dedicated user interfaces or production operator dashboards (POD)", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "During production the shop floor operator receives step-by-step process instructions for the related process order in an user interface or production operator dashboards (POD). For some process steps the capturing of data is required (e.g. actually dosed quantities, process data as specified in inspection points, milestone confirmation). This process shows data entry and confirmation as well as milestone confirmation through POD", "Outcome": "Process data has been captured and confirmed and is available for further processing.", "GUID": "0e8d9651-7559-11e9-2ddf-001bc640cd9b", "name": "Capture process data in Production Operator Dashboards (POD)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.244733471244586, "y": 0.4617940199335546, "z": -1.990269238840371 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1730", "text": "Process", "data": { "Advisory_Notes": "There are three options for production preparation: ***using PI Sheet (production instructions in electronic form) ***using shop floor papers (paper based solution) ***transfer production instructions to an external manufacturing control system. In process industry PI sheet is the typical solution.", "KeyActivities": "Trigger production supply,\n Set up machinery or equipment,\n Generate shop floor order", "Type": "Business Process", "Description": "After the process order is released, the shop floor order is released in digital manufacturing cloud. The shop floor worker can view the order and initiate work through dedicated user interface.The supply of necessary materials to the production also gets initiated.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "The production preparation process covers all activities required to start manufacturing based on the released process order. Information about the actual manufacturing process and control parameters and instructions for the process operators must be transferred to the production control to be carried out (for this purpose control recipes are used). Shop-floor papers for the coordination of manufacturing tasks must be created and material supply to production initiated.", "Outcome": "All preparation steps for production are performed, physical manufacturing can start.", "GUID": "70fa5e73-e8f7-11e4-0a66-001bc640cd9b", "name": "Prepare production with Digital Manufacturing Cloud", "Business_Rules": "It must be defined: ***Which shop-floor papers are required (e.g. process order operations, goods issue slip), ***What information must be included into control recipe, to what destinations they must be sent as well as communication channels ***What checks are required before the release of control recipes and how they are set-up", "Prerequisite": "" }, "position": { "x": -2.979088730975128, "y": 0.4651162790697674, "z": -2.669275244888957 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1734", "text": "Process", "data": { "Advisory_Notes": "The release will also impact the status of the material reservations of the components. Latest at this point in time, the reservations should be treated as firm and no other planning or logistics process should have access to the reserved quantities anymore.", "KeyActivities": "Select production order(s) for release,\n Set production order status to release,\n Review missing parts list,\n Assign batch,\n Trigger manufacturing rescheduling,\n Release production orders", "Type": "Business Process", "Description": "Manufacturing orders can be created in advance to the planned manufacturing start date and are not bound to the availability of required materials or capacity. The release process represents the final step to initiate the manufacturing process. Unless the order is released, no further processing is possible.", "Process_Group": "Production Scheduling", "hasAssignment": true, "Scope": "Created manufacturing orders must be released, before they can be processed by production. The release is done, when the release date has been reached and when the required materials and capacity are available. The availability of materials and capacity should be checked within the release process.", "Outcome": "Production order is released.", "GUID": "024d6439-e8f7-11e4-0a66-001bc640cd9b", "name": "Release production order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.706397961056126, "y": 0.46843853820598014, "z": -3.355981846535972 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1736", "text": "Process", "data": { "Advisory_Notes": "Regardless whether a production order gets created directly or via converting a planned order material, routing and BOM related data get retrieved again from respective master data. Possible conversion options must be defined: ***one planned order to one production order, ***several planned orders to one production order, ***partial conversion of planned orders.", "KeyActivities": "Verify material and quantity for production,\n Verify scheduling type and production start date,\n Verify goods receipt options for quality inspection,\n Verify bill of materials and routing,\n Save and create production order,\n Assign batch number", "Type": "Business Process", "Description": "As a result of a planning procedure planned orders are created. Those need to be converted to production orders.", "Process_Group": "Production Scheduling", "hasAssignment": true, "Scope": "Within a defined horizon, planned production orders get converted in order to become executable production orders. The conversion typically includes the adding of production specific information. A production order describes the production of the specified product following the selected production version (combination of BOM alternative and version or routing). The production order is used to plan the quantities, dates, and resources of the manufacturing process, to control order execution, and to define rules for the account assignment and settlement of the costs incurred. A routing version is selected, its operations and sequences are transferred to the production order. The bill of materials (BOM) is exploded and the items in the BOM are transferred to the order. Reservations are generated for bill of material items held in stock. The planned costs for the order are generated. The capacity requirements are generated for the work centers. Purchase requisitions are generated for non-stock items and externally-processed operations.", "Outcome": "Planned order is partly or completely converted to a production order.", "GUID": "712673f1-7f1e-11e5-0a66-001bc640cd9b", "name": "Convert planned order to production order", "Business_Rules": "It must be defined, how production orders can be created - either by converting a planned order to a production order only, or also by creating it manually. Latter bypasses planning violating best practices principals, though.", "Prerequisite": "" }, "position": { "x": -4.426600883598981, "y": 0.4717607973421929, "z": -4.050333889609686 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1740", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Trigger production supply,\n Set up machinery or equipment,\n Load product in manufacturing execution system ", "Type": "Business Process", "Description": "After the production or process order is released shop-floor papers (or electronic files) are generated and the supply of necessary materials to the production initiated.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "The production preparation process covers all activities required to start manufacturing based on the released process order or production order.Information about the actual manufacturing process and control parameters and instructions for the production operators must be transferred to the production control to be carried out (for this purpose control recipes are used).Shop-floor papers for the coordination of manufacturing tasks must be created and material supply to production initiated.", "Outcome": "All preparation steps for production are performed, physical manufacturing can start.", "GUID": "ed92ae3d-9724-11e8-2ddf-001bc640cd9b", "name": "Prepare production with manufacturing execution system", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.4684678871507104, "y": 0.4750830564784052, "z": -1.357793086006527 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1742", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Gather demands,\n Schedule campaign production,\n Optimize production lot size for campaigns", "Type": "Business Process", "Description": "This process explains the collection of a family of demands and scheduling them for serial production.", "hasAssignment": true, "Process_Group": "Production Scheduling", "Scope": "For serial production, demands are placed for products to be produced within the same family. It must be planned that production lines are efficiently planned to maximize production lots.", "Outcome": "Campaign production scheduled.", "GUID": "88c21247-7f1c-11e5-0a66-001bc640cd9b", "name": "Schedule confirmed demands within campaign", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.192043232052213, "y": 0.47840531561461797, "z": -2.048156846731736 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1744", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Update documents,\n Dismantle and clean machinery or equipment,\n Execute production steps,\n Label product,\n Package product", "Type": "Business Process", "Description": "After all preparations are carried out, the physical production can take place. Besides the manufacturing of products the process usually includes also their labeling and packing.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "Physical manufacturing of products is carried out and monitored by production control. After goods are produced, they must be packed and labeled.", "Outcome": "Products are manufactured using MES and deviations are recorded in MES.", "GUID": "8a5dc0c7-7f1c-11e5-0a66-001bc640cd9b", "name": "Manufacture products using manufacturing execution system", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9084332480672397, "y": 0.4817275747508307, "z": -2.746091047568716 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1752", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Any errors in goods movement that might occur during backflushing are processed", "Process_Group": "Production Operations", "Scope": "Accurate records of all goods movement including errors should be documented. This helps to identify, analyze and resolve any errors that arise during goods movement.", "Outcome": "Accurate records of inventory management and production data is maintained.", "GUID": "f79c123a-992e-11ee-3781-0201b014c5b2", "name": "Post processing of error records", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.6175787243649826, "y": 0.48504983388704304, "z": -3.45153939178185 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1753", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is the systematic discontinuation or ceasing of repetitive manufacturing processes in a production environment. The purpose is to adapt and optimize production operations based on factors such as changes in market demand, product discontinuation, and evolving business needs or strategies. It allows organizations to reallocate resources, update technologies, or even transition to more efficient production models.", "Process_Group": "Production Operations", "Scope": "This involves a comprehensive evaluation of existing production lines, machinery, and associated workflows. It encompasses a detailed analysis of resource utilization, workforce requirements, technological dependencies, and the impact on downstream and upstream operations. Additionally, the financial implications, including cost analysis, budgetary adjustments, and potential investment redirection needs to be considered. This scope extends to developing a strategic plan outlining the phased approach to discontinue repetitive manufacturing, ensuring minimal disruption to ongoing operations while optimizing resources for future production needs. Coordination with stakeholders, including production teams, supply chain managers, and possibly external partners, is integral to manage the transition effectively.", "Outcome": "Repetitive manufacturing operations are discontinued.", "GUID": "94836c20-9ad0-11ee-3781-0201b014c5b2", "name": "Close repetitive manufacturing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.319420842547975, "y": 0.4883720930232558, "z": -4.164445171323803 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1754", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Confirmation of repetitive manufacturing is performed at pre defined reporting points. Backflush of components is carried based on confirmation.", "Process_Group": "Production Operations", "Scope": "Quantity of goods produced, materials consumed, time consumed and activities are confirmed at pre-defined reporting points in repetitive manufacturing. Once actual consumption is confirmed, backflush is carried out to reflect the actual stock situation. In the process, the system posts the actual costs to the product cost collector and reduces the planned orders.", "Outcome": "Accurate updating of production records and inventory levels.", "GUID": "f79c122b-992e-11ee-3781-0201b014c5b2", "name": "Perform confirmation and backflush for repetitive manufacturing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.4325431940942381, "y": 0.49169435215946855, "z": -1.3956432198288637 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1759", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Trigger subcontractor to ship units,\n Receive confirmation units are in transit,\n Trigger rescheduling", "Type": "Business Process", "Description": "In an active subcontracting process, the company must receive the components before providing the subcontracting services.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "In this process, the goods are received, which triggers production.", "Outcome": "Components received from sub-contractor.", "GUID": "1923a0ad-900d-11e8-2ddf-001bc640cd9b", "name": "Initiate and confirm components from subcontractor", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.1378606409488246, "y": 0.49501661129568086, "z": -2.1046500611460046 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1763", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check goods,\n Determine required exception handling,\n Trigger action in procurement,\n Trigger action in quality,\n Stage co-product for subcontracting,\n Post goods receipt of co-product,\n Inventory increase (production) posting,\n Work in progress posting", "Type": "Business Process", "Description": "This process describes subcontracting production.When a co-product is manufactured for sub-contracting, the semi-finished good is put onto stock as a co-product.Once the co-product is on stock, the subcontracting can be triggered.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "Semi-finished product produced internally and ready for subcontracting are staged for further processing.", "Outcome": "Co-products are checked and ready for subcontracting.", "GUID": "693c7fcf-94c9-11e8-2ddf-001bc640cd9b", "name": "Perform goods receipt of co-product for subcontracting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.835797692023773, "y": 0.4983388704318936, "z": -2.8210373003405405 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1765", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Post goods issue for components used in production,\n Material consumption posting", "Type": "Business Process", "Description": "After external subcontracting is complete, a goods issue of the externally subcontracted material is posted to the internal production order. The inventory of the components at the relevant storage location will be decreased.", "Process_Group": "Outbound Delivery Management", "hasAssignment": true, "Scope": "Before resuming production internally, a goods issue must be posted for the externally subcontracted materials.", "Outcome": "Goods issue posting of externally subcontracted material to internal production order.", "GUID": "693c7fe4-94c9-11e8-2ddf-001bc640cd9b", "name": "Perform goods issue of processed materials to subsequent internal production step", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.526296625425676, "y": 0.5016611295681064, "z": -3.5447471150297147 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1770", "text": "Process", "data": { "Advisory_Notes": "*** Re-labelling is often conducted in the warehouse whereas re-filling often needs to be done in production due to safety and environmental compliance (e.g. EX protection). ***Set-up of manufacturing quality inspection must be defined-when it should be carried out (during production, based on first manufactured products, at end of production) and how it is initiated (information flow from production). ***Production monitoring setup, exchange of production relevant information with external systems (e.g. process messages), production and downtime reporting requirements must be defined. ***Label use (manufacturing, shipping, receiving, scanning, customer specific, general in-house label use) must be defined and considered for product labeling. ***If products are serialized and new serial numbers are required, then the existing ones must be marked/written off as internal consumption for tracking purposes", "KeyActivities": "Update documents,\n Package product,\n Execute re-filling / re-labeling,\n Assign new serial number,\n Write off old serial number", "Type": "Business Process", "Description": "After all preparations are carried out, the physical production can take place. Besides the manufacturing of products the process usually includes also their labeling and packing.", "hasAssignment": true, "Process_Group": "Production Operations", "Scope": "Physical re-filling and re-labeling of products is carried out and monitored by production control.", "Outcome": "Product is refilled/relabelled and packed.", "GUID": "26d12177-7f27-11e5-0a66-001bc640cd9b", "name": "Process refilling or relabelling", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.20930012229201, "y": 0.5049833887043191, "z": -4.275721281897647 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1772", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify goods receipt options for quality inspection,\n Verify materials and routing operations,\n Assign batch number,\n Maintain material,\n production plant,\n order type,\n quantity into header,\n Maintain scheduling type and production start date,\n Create process order", "Type": "Business Process", "Description": "Manually create a process order in order to cater for the special circumstances of refilling or repacking. The situation that requires refilling or repacking of products can vary i.e. damaged packaging or just wrong labels. Depending on the necessary steps the process order requires manual selection and creation.", "hasAssignment": true, "Process_Group": "Production Scheduling", "Scope": "A process order needs to be created to trigger the refilling/repackaging process.", "Outcome": "A process order is created.", "GUID": "26d1217a-7f27-11e5-0a66-001bc640cd9b", "name": "Create process order for re-filling or re-packaging", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.3956432198288642, "y": 0.5083056478405314, "z": -1.4325431940942377 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1777", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Scan product label,\n Post goods receipt,\n Cost change posting,\n Inventory increase (rework order) posting", "Type": "Business Process", "Description": "This process describes the goods receipt process for products and by-products manufactured in production via re-working of a product normally due to quality issues.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "Re-worked goods that have been produced have to be posted on stock with a goods receipt.", "Outcome": "Goods receipt posted (in many cases in a special stock as long as quality inspection is still ongoing).", "GUID": "45c3aeb7-9c7c-11e8-2ddf-001bc640cd9b", "name": "Perform goods receipt from re-work", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.0822225856619023, "y": 0.5116279069767442, "z": -2.159710421273987 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1781", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify goods receipt options for quality inspection,\n Verify materials and routing operations,\n Assign batch number,\n Maintain material,\n production plant,\n order type,\n quantity into header,\n Verify scheduling type and production start date,\n Create production order", "Type": "Business Process", "Description": "A production order for recycling needs to be created for the breakdown and recycling of components. The nature of recycling processes require the selection of required operations and components either selected from standard routings and standard BOMs or captured manually.", "Process_Group": "Production Scheduling", "hasAssignment": true, "Scope": "A recycling order is created with its own product as component. Within the order the required operations and additionally required components are defined and batches will be assigned if applicable.", "Outcome": "The rework order with the required operations and components is created.", "GUID": "c3fb9beb-94b8-11e8-2ddf-001bc640cd9b", "name": "Create production order for recycling", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.761231513425481, "y": 0.514950166112957, "z": -2.894062979491985 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1783", "text": "Process", "data": { "Advisory_Notes": "Set-up of manufacturing quality inspection must be defined-when it should be carried out (during production, based on first manufactured products, at end of production) and how it is initiated (information flow from production). Production monitoring setup, exchange of production relevant information with external systems (e.g. process messages), production and downtime reporting requirements must be defined. Label use (manufacturing, shipping, receiving, scanning, customer specific, general in-house label use) must be defined and considered for product labeling.", "KeyActivities": "Update documents,\n Dismantle and clean machinery or equipment,\n Execute recycling", "Type": "Business Process", "Description": "After all preparations are carried out, the physical production can take place. Besides the manufacturing of products the process usually includes also their labeling and packing.", "Process_Group": "Production Operations", "hasAssignment": true, "Scope": "Physical recycling of products is carried out and monitored by production control.", "Outcome": "Goods have been recycled.", "GUID": "c3fb9c10-94b8-11e8-2ddf-001bc640cd9b", "name": "Perform recycling", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.432613809460896, "y": 0.5182724252491693, "z": -3.6355415600840484 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1788", "text": "Process", "data": { "Advisory_Notes": "The service order must be blocked until the customer accepts the quotation.", "KeyActivities": "Enter planned working time and costs,\n Generate quotation,\n Send quotation to customer,\n Enter required spare part", "Type": "Business Process", "Description": "In order to quote price and conditions to the customer, a quotation can be prepared in a predefined format. Depending on the business model quotation may include different information. The basis for the creation of quotation are the customer details and information from customer inquiry. The quotation is sent out to the customer.", "Process_Group": "Field Services", "hasAssignment": true, "Scope": "Quotation document is prepared based on information captured in inquiry. Sales price is calculated and conditions determined (e.g. service costs, margin tables, rebates, delivery terms).", "Outcome": "Quotation is created and sent to customer.", "GUID": "f56c62d4-7e51-11e5-0a66-001bc640cd9b", "name": "Create quotation for service request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -4.096313693463474, "y": 0.521594684385382, "z": -4.384086464104424 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1791", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Prior to the pick-up of returnable packaging sent to the customer, a document must be created that specifies related conditions and initiates the return.", "Process_Group": "Customer Returns", "Scope": "Compilation of the document to initiate the pick-up of returnable packing, specifying conditions related to the return of the materials. Information is provided on whether or not the customer will be charged for transportation.", "Outcome": "Document for pick-up of returnable packaging is created and the return process is triggered.", "GUID": "605f69a6-7e4f-11e5-0a66-001bc640cd9b", "name": "Create returnable packaging pick-up", "Business_Rules": "The information required in the document must be defined. The decision must be made on whether this process includes checks performed for standard sales order creation i.e. EH+S, GTS Check, etc.", "Prerequisite": "" }, "position": { "x": -1.3577930860065275, "y": 0.5249169435215948, "z": -1.4684678871507102 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1793", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The service must be executed based on the specifications provided in the service order and status needs to be maintained accordingly.", "Process_Group": "Repairs", "Scope": "Once the service has been dispatched, required activities are carried out to perform the service. After service execution, it is required to document the provided service and update the service order status.", "Outcome": "Service operations are fulfilled and status updated.", "GUID": "b27a548a-90b2-11e8-2ddf-001bc640cd9b", "name": "Perform service and update service order status", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.0251669448048433, "y": 0.5282392026578071, "z": -2.2133004417994897 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1794", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Employees working on repair or services have to record the hours spent on it. These hours need to be confirmed by the Head of repair.", "Process_Group": "Repairs", "Scope": "Working hours are recorded by employees and transferred to controlling.", "Outcome": "Working hours recorded.", "GUID": "b27a5490-90b2-11e8-2ddf-001bc640cd9b", "name": "Record confirmation of time", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.6847854772287785, "y": 0.5315614617940199, "z": -2.9651183688449 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1798", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify relevant communication case,\n Communicate necessary adjustments,\n Realize defined communication measures,\n Check improvement potential for communication,\n Define corrective and improving measures", "Type": "Business Process", "Description": "The communicator of the business area concerned checks the communication measures required for his area on the basis of the communication plan and implements them as described. If necessary, corrective and improvement measures are to be defined and forwarded to be added to the central action plan. The communication plan describes the communication measures in detail: who communicates with whom regarding which occasion (e.g. meeting, workshop, audit, incident, accident ...), when (e.g. periodically, weekly, daily, ad hoc ...) and in which form (e.g. minutes, mail, phone call, official letter...)", "Process_Group": "Quality Management", "hasAssignment": true, "Scope": "The communication plan is implemented in the business areas so that all stakeholders and parties involved are informed.", "Outcome": "* Meeting minutes * Shift handover protocol * Project progress report * Employee review form * Audit report * Updated plan of measures", "GUID": "b99b0a52-e47e-11eb-2c3e-001bc641ce4f", "name": "Implement communication plan", "Business_Rules": "", "Prerequisite": "* Communication plan " }, "position": { "x": -3.3365940561111973, "y": 0.5348837209302326, "z": -3.7238609137189087 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1800", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Communication must be managed internally and externally. In communication or information management, verbal and written communication including reporting is standardized.", "Process_Group": "Quality Management", "Scope": "For standardization, communication occasions, communication partners and topics as well as the type, scope and channels of internal and external communication are defined and specified. Documents such as: team meeting/meeting minutes, communication matrices, communication guidelines and reports are considered as evidence.", "Outcome": "* Meeting minutes * Shift handover protocol * Project progress report * Employee review form * Audit report * Updated plan of measures", "GUID": "66ad3312-ab9f-11ed-3781-0201b014c5b2", "name": "Control communication", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.9805384776807435, "y": 0.5382059800664454, "z": -4.489466942489171 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1801", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Defective products must be clearly identified and stored separately/isolated from nondefective products to prevent the use or delivery of defective products. ", "Process_Group": "Quality Management", "Scope": "The separation or isolation of defective products, can be achieved through the use of restricted areas, special markings or physical barriers. ", "Outcome": "blocked products", "GUID": "38026a50-9d6a-11ed-3781-0201b014c5b2", "name": "Marking and blocking of defective products", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.3190185611516432, "y": 0.5415282392026577, "z": -1.5033928413217381 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1802", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Customer satisfaction analysis is used for customer orientation and involves measuring customer satisfaction.", "Process_Group": "Quality Management", "Scope": "Customer satisfaction analysis can be carried out on the basis of the results of various methods used to determine customer satisfaction. The customer satisfaction analysis includes the observation of the customers, the analysis of the customer behavior but above all the questioning of the customers. The procedure for surveying customer satisfaction should include the following activities: - Determination of the customer group - Determination of the survey method - Designing the feedback form - Obtaining customer feedback - Evaluate results - Derive measures", "Outcome": "Measures for improvement", "GUID": "66ad332e-ab9f-11ed-3781-0201b014c5b2", "name": "Analyze customer satisfaction", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.966732562089038, "y": 0.5448504983388704, "z": -2.2653836384194816 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1803", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Evaluate plan of measures,\n Create and distribute implementation assignments,\n Apply measures,\n Report implementation status,\n Release of the solution for implementation,\n Create action plan", "Type": "Business Process", "Description": "Necessary corrective measures are discussed and approved by the process team. This can also be realized in the form of process optimization projects. The measures necessary for implementation are identified and the tools and resources required to carry out the process are adapted.", "Process_Group": "Quality Management", "hasAssignment": true, "Scope": "Workflow: - Problem definition - root cause analysis - solution finding - Solution decision - Create action plan", "Outcome": "Action plan for improvement", "GUID": "255a51bd-9bb7-11ed-3781-0201b014c5b2", "name": "Implement measures for improvement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.606511628204741, "y": 0.5481727574750832, "z": -3.0341550936024135 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1805", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Competence development is an elementary component of human resources management. It serves the further development and maintenance of knowledge, skills and abilities. ", "Process_Group": "Quality Management", "Scope": "The organization provides offers for the promotion, such as instructions, training courses, workshops. These offers are planned and documented in a (training) program (annually) with the respective topic, date period, duration, location and methods.", "Outcome": "Training program or support program for personnel development", "GUID": "0cb9a74e-9bdb-11ed-3781-0201b014c5b2", "name": "Planning competence development", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.2383027360135843, "y": 0.5514950166112955, "z": -3.8096450477606094 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1806", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Publish knowledge base,\n Check personal knowledge needs,\n Search knowledge base,\n Apply knowledge being found", "Type": "Business Process", "Description": "The knowledge manager publishes the documented knowledge in the organizations network (intranet, wiki ...). If the knowledge user has a need to enlarge his knowledge, he searches the collection and applies the knowledge gained.", "hasAssignment": true, "Process_Group": "Quality Management", "Scope": "By accessing a central knowledge collection, employees can use focused information and best practice recommendations in daily business. Shared knowledge saves time and facilitates quality in service and production.", "Outcome": "* Collection of knowledge (glossary, wiki, online training sessions ...)", "GUID": "3781fca2-e3ba-11eb-2c3e-001bc641ce4f", "name": "Distribute and apply knowledge", "Business_Rules": "", "Prerequisite": "* Knowledge base (glossary, wiki, online training sessions ...)" }, "position": { "x": -3.862053295179669, "y": 0.5548172757475083, "z": -4.591790973595364 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1808", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Quality assurance is an integral part of this process. It includes activities such as material inspections, incoming and outgoing goods inspections, process capability tests, in-process inspections and final inspections on products and services as well as returned goods.", "Process_Group": "Quality Management", "Scope": "Data and information obtained from quality assurance activities must be analyzed, evaluated, and documented. Methods of data analysis may include statistical procedures. The test and measurement equipment used must also be regularly checked for suitability and capability. A test equipment management system can provide support in this regard.", "Outcome": "Documented records of the test results", "GUID": "66ad3325-ab9f-11ed-3781-0201b014c5b2", "name": "Check and evaluate performance", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2793460431177832, "y": 0.558139534883721, "z": -1.5372942795570637 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1809", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The offerings planned in the (training) program to impart competencies are specified in detail in a (training) plan and documented in terms of content. ", "Process_Group": "Quality Management", "Scope": "The detailed contents include: Location, date, start/end, speaker/organizer, topic content, participants. Participation is confirmed with attendance documentation.", "Outcome": "Training schedule", "GUID": "0cb9a74c-9bdb-11ed-3781-0201b014c5b2", "name": "Train employees", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9069592198789254, "y": 0.5614617940199333, "z": -2.315924552682742 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1810", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Address communication amendment,\n Consolidate communication updates,\n Check update requirements,\n Update communication plan", "Type": "Business Process", "Description": "In case of new and / or changed communication causes, the process owner informs the IMS representative, who updates the communication plan accordingly.", "hasAssignment": true, "Process_Group": "Quality Management", "Scope": "Communication needs are defined so that the information in concern reaches the right internal and external addressees. For special situations and events (e.g. operational incident, operational accident, unannounced visit of financial authorities or customs) it is necessary to check for relevant communication and if required, to consider appropriate information channels and addressees.", "Outcome": "* Communication amendment * Updated communication plan.", "GUID": "b99b0a50-e47e-11eb-2c3e-001bc641ce4f", "name": "Determine communication needs", "Business_Rules": "", "Prerequisite": "* Communication update * Communication plan" }, "position": { "x": -2.52646325550683, "y": 0.5647840531561461, "z": -3.1011261532826797 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1812", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The existing competencies are measured and assessed as part of the competency needs assessment. The aim of competence measurement and assessment is to answer the question of which competences are already available and at what level, and which will need to be further developed or acquired completely from scratch in the future. Measurement instruments, measurement procedures and participants must be defined for the determination of competence requirements.", "Process_Group": "Quality Management", "Scope": "For competence development, the knowledge and skills must be analyzed and a profile of the employees strengths and weaknesses (departmental or personal, depending on the size of the company) must be drawn up. The assessment of the qualification can be done by the manager or the employee himself. A combination of self-assessment and assessment by others is recommended. The requirements analysis also includes: an activity and task analysis (requirements profile for a position) and a person or addressee analysis (suitability profile). The discrepancy between qualification and requirement reveals the need for learning fields, learning content and learning forms. Competences can be documented in a competence matrix.", "Outcome": "Competence assessment", "GUID": "0cb9a74a-9bdb-11ed-3781-0201b014c5b2", "name": "Determine competence needs", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.1378067662968956, "y": 0.5681063122923589, "z": -3.8928355600232356 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1813", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The management system must be evaluated at planned intervals to ensure that it is suitable, appropriate, effective, and consistent with the strategic direction of the organization.", "Process_Group": "", "Scope": "Inputs to the management review are: - Performance evaluation results (quality assurance, audits, and customer satisfaction analyses). - Impact of changes from the business environment - Adequacy of resources - Performance of external providers - Effectiveness of corrective and preventive actions (managing risks and opportunities) - Identification of opportunities for improvement", "Outcome": "Management-Review-Bericht", "GUID": "66ad332b-ab9f-11ed-3781-0201b014c5b2", "name": "Evaluate managementsystem", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.7409388111524016, "y": 0.5714285714285716, "z": -4.690988894808179 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1814", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Knowledge must be managed and protected as a strategic resource within the company. The knowledge manager collects the knowledge available in the organization from different sources and checks the available knowledge against the definition of the required knowledge. If the amount of knowledge is sufficient, it is prepared and stored accordingly. Otherwise, the necessary additional knowledge must be sourced externally and also prepared and stored. The use of knowledge management in conjunction with competence management is suitable for sifting through, describing, evaluating and deploying existing skills in the company, identifying and developing potential and thus supporting its maintenance.", "Process_Group": "Quality Management", "Scope": "The knowledge generated about customers and products as well as technical and methodological knowledge is stored, indexed and documented in order to make it accessible to all. The setup and use of a company wiki is beneficial, but not mandatory. Possible sources of knowledge: * Best practices from external events, seminars etc. * Successful measures from plan of measures * Results of supplier surveys * Results of customer surveys * Documentation of staff exit interviews * Best practice excerpts from meeting and workshop minutes * Lessons learned from project closure report * Results of employee surveys * Required depth of knowledge of the organization (from strategic planning)", "Outcome": "* Collection of knowledge (glossary, wiki, online training sessions ...)", "GUID": "5fb2a69e-ab8f-11ed-3781-0201b014c5b2", "name": "Maintain knowledge", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2388025411159147, "y": 0.5747508305647839, "z": -1.5701491216202212 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1815", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Collect knowledge of the organization,\n Check depth of knowledge,\n Acquire additional knowledge from external sources,\n Prepare and store knowledge of the organization", "Type": "Business Process", "Description": "The knowledge manager collects the knowledge available in the organization from different sources and checks the available knowledge against the definition of the required knowledge. If the amount of knowledge is sufficient, it is prepared and stored accordingly. Otherwise, the necessary additional knowledge must be sourced externally and also prepared and stored.", "hasAssignment": true, "Process_Group": "Quality Management", "Scope": "The knowledge generated about customers and products as well as technical and methodological knowledge is stored, indexed and documented in order to make it accessible to all. The setup and use of a company wiki is beneficial, but not mandatory.", "Outcome": "* Knowledge base (glossary, wiki, online training sessions ...)", "GUID": "3781fca0-e3ba-11eb-2c3e-001bc641ce4f", "name": "Document and save knowledge", "Business_Rules": "", "Prerequisite": "* Best practices from external events, seminars etc. * Successful measures from plan of measures * Results of supplier surveys * Results of customer surveys * Documentation of staff exit interviews * Best practice excerpts from meeting and workshop minutes * Lessons learned from project closure report * Results of employee surveys * Required depth of knowledge of the organization (from strategic planning)" }, "position": { "x": -1.8458876121079846, "y": 0.5780730897009967, "z": -2.364888776130134 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1817", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "CIP (Continuous Improvement Process) describes continuous improvement as a recurring activity to maintain the current level of performance, to respond to changes in internal and external conditions, to create new opportunities and to improve performance.", "Process_Group": "Quality Management", "Scope": "CIP should be systematic, following the Plan-Do-Check-Act cycle to specifically identify potential and improve the effectiveness of the management system. Systems, processes and products are continuously checked for possible optimization potential within the in-process monitoring activities (in Plan and Do) and performance evaluation (Check).", "Outcome": "Based on the use of available results for improvement, CIP is an ongoing process and leads to timely or immediate corrective and preventive actions.", "GUID": "66ad333f-ab9f-11ed-3781-0201b014c5b2", "name": "Apply CIP", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.4446948563913966, "y": 0.5813953488372094, "z": -3.165985953717017 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1818", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Customer orientation is the alignment of all activities to customer needs. ", "Process_Group": "Quality Management", "Scope": "To this end, customer wishes, needs and expectations are systematically recorded and analyzed. Products and services can thus be tailored to the individual customer. Customer-oriented companies have established processes that enable them to understand the needs, wishes and expectations of (potential) customers and to address these with their products, services and in their communications.", "Outcome": "to build long-term, stable, profitable customer relationships and to promote customer satisfaction.", "GUID": "5fb2a695-ab8f-11ed-3781-0201b014c5b2", "name": "Implement customer orientation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.0351745650243656, "y": 0.5847176079734218, "z": -3.973375814069083 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1819", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The personnel competences are documented and kept in consideration of the GDPR.", "Process_Group": "Quality Management", "Scope": "Records of existing and acquired competencies are documented, e.g. by confirmations of attendance, certificates of attendance, certificates, testimonials and CVs, and kept for reference.", "Outcome": "Demonstrable competencies of the employees", "GUID": "0cb9a750-9bdb-11ed-3781-0201b014c5b2", "name": "Document competences", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.6172774808302313, "y": 0.5880398671096345, "z": -4.78699317178106 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1821", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Gather information,\n Check legal register for relevance,\n Update legal register,\n Evaluate need for change of own documents and data,\n Apply changes to documents and data", "Type": "Business Process", "Description": "New and modified requirements are gathered by the process owner, reviewed for relevance for the legal register office, the need for changes to internal documents and data as well as the impact on the company. The identified need for change is recorded in the appropriate areas for subsequent publication. The change process is handled systemically from the submission of the request to the implementation of the change. This process might be supported by a workflow management application.", "hasAssignment": true, "Process_Group": "Document Management", "Scope": "Legal and internal requirements / changes are collected and checked for relevance and impact on internal processes and documents in order to stay up-to-date and avoid violations.", "Outcome": "* updated legal register * modified document * modified data * modified specifications", "GUID": "7715e2e5-e64f-11eb-2c3e-001bc641ce4f", "name": "Record and evaluate changes", "Business_Rules": "", "Prerequisite": "* Internal specifications & requirements * Internal documents * Internal data * External specifications & requirements * External documents * External data * Legal register * legal acts" }, "position": { "x": -1.1974156573264179, "y": 0.5913621262458473, "z": -1.6019349998016594 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1823", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Release changes of documents and data,\n Update list of valid documents and data,\n Update list of valid quality records,\n Mark invalid documents and data and remove them from circulation,\n Check for ARIS relevance,\n Assigning changes to processes and applicable documents in ARIS", "Type": "Business Process", "Description": "The process owner releases the changes and has previously checked the relevance of the updates. Depending on the scope of change and the level of detail, the corresponding documents must be adapted, republished and communicated accordingly. The quality management representative updates the lists of valid documents, data and quality records. This process can be supported by a workflow management application that also manages and processes the required lists electronically.", "Process_Group": "Document Management", "hasAssignment": true, "Scope": "Changes are approved and communicated to ensure process security and legal compliance.", "Outcome": "* Released documents * Released data * Released specifications * Updated list of valid documents and data * Updated list of valid quality records", "GUID": "7715e2e7-e64f-11eb-2c3e-001bc641ce4f", "name": "Release changes", "Business_Rules": "", "Prerequisite": "* Modified document * Modified data * Modified specifications * List of valid documents and data * List of valid quality records" }, "position": { "x": -1.7835593165741512, "y": 0.5946843853820596, "z": -2.4122429737200077 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1825", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The storage and archiving takes into account requirements for retention periods, audit security, and DSGVO compliance throughout the entire lifecycle of a document, until it is deleted or destroyed.", "Process_Group": "Document Management", "Scope": "Data protection and security aspects, such as encryption and data security, must also be taken into account as elementary components of storage and archiving.", "Outcome": "Audit-compliant archiving, as the document history is stored.", "GUID": "167e34fd-9350-11ed-3781-0201b014c5b2", "name": "Archive and delete documents", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.361262099115763, "y": 0.5980066445182723, "z": -3.228690338090573 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1828", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The pre-audit is used for conformity assessment according to the relevant regulations in order to check business readiness.", "Process_Group": "Audit Management", "Scope": "Optionally, a pre-audit can be conducted before the actual certification audit. Such a pre-audit serves as a dress rehearsal before a certification audit or is used as a site assessment if an implementation of a management system or an extension of the IMS to additional standards is planned. The selected auditor and the organization evaluate the implemented management system with the corresponding documentation to determine whether they have met the requirements of the corresponding set of regulations. Based on the auditors findings, the organization can focus on full implementation of the management system and implement improvement measures.", "Outcome": "Assessment of business maturity and identification of potential for improvement", "GUID": "3a9c9980-a92c-11ed-3781-0201b014c5b2", "name": "Perform pre-audit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.930476004614312, "y": 0.6013289036544851, "z": -4.051210977766987 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1830", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is to document and track activities, events, and every aspect of operations to ensure compliance with both internal and external policies. It helps maintain a record of activities that can be reviewed, audited, and used as evidence when necessary.", "Process_Group": "Compliance and Audits Reporting", "Scope": "Details of findings, actions taken, approvals, timestamps, and any supporting documentation which are relevant for specific compliance requirements are included.", "Outcome": "Audit trail report created.", "GUID": "47644cbc-5b9e-11ee-3781-0201b014c5b2", "name": "Create audit trail and compliance documentation report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.491153493347717, "y": 0.6046511627906979, "z": -4.879738444413392 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1833", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Product labels are generated based on a predefined layout in a specific language combination and master data released to the material.", "Process_Group": "Healthy, Safety and Environment", "Scope": "The system checks data completeness and whether the texts fits in the predefined text boxes. For regulated products the label has to be approved by product responsible persons.", "Outcome": "New label created and released for printing / ordering.", "GUID": "32dc8861-d7a6-11ed-3781-0201b014c5b2", "name": "Create and release label", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.1552135681074096, "y": 0.6079734219269102, "z": -1.6326302741467669 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1834", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of perform waste reporting processes is to systematically track, document, and analyze the generation, handling, and disposal of waste within an organization. This process helps businesses understand the types and quantities of waste they produce, identify opportunities for waste reduction and recycling, ensure compliance with environmental regulations, and contribute to sustainability goals. Waste reporting also aids in transparency and accountability, allowing stakeholders to assess environmental impacts and make informed decisions to minimize the ecological footprint of their operations.", "Process_Group": "Healthy, Safety and Environment", "Scope": "This process encompasses a thorough examination of the entire waste management lifecycle within an organization. This includes identifying and categorizing various types of waste generated across different operations, tracking the volume of waste at each stage, documenting disposal methods, and assessing recycling efforts. The waste reporting process may involve collaboration with various departments, suppliers, and stakeholders to gather comprehensive data, enabling a holistic understanding of the organizations waste footprint.", "Outcome": "Generation of comprehensive data and insights regarding an organizations waste management practices.", "GUID": "32dc887d-d7a6-11ed-3781-0201b014c5b2", "name": "Perform Waste reporting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7200167666334782, "y": 0.6112956810631229, "z": -2.457954906522842 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1835", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Companies have different requirements regarding labels, which means that different labels must be created depending on the business process or intended use.", "Process_Group": "Healthy, Safety and Environment", "Scope": "For hazardous chemicals, labels are required that contain hazard symbols and safety information. On transport packaging, you must also apply labels with dangerous goods data and danger labels and for Waste labels we need both information on one template. These requirements affect the report templates that are used for labels.", "Outcome": "New layout / language combination available for label generation.", "GUID": "32dc885f-d7a6-11ed-3781-0201b014c5b2", "name": "Manage label templates", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.2762217850390076, "y": 0.6146179401993357, "z": -3.289196617004498 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1836", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that requested information is available to support substance registration processes.", "Process_Group": "Healthy, Safety and Environment", "Scope": "Provide Substance Registration related reports like: - Chemical statistic survey - Poisonous and Deleterious substance report - Food additive track and trace report - Hazard Communication of Dangerous Materials", "Outcome": "Requested data provided in structured format.", "GUID": "32dc8853-d7a6-11ed-3781-0201b014c5b2", "name": "Provide Substance Registration Reports", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.8237823642707447, "y": 0.617940199335548, "z": -4.126288060622224 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1837", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes how risk assessment is conducted and reported on.", "Process_Group": "Healthy, Safety and Environment", "Scope": "Risks are identified, safety controls are initialised and reviewed and the effectiveness of safety controls is checked.", "Outcome": "Risk assessment performed and reports created.", "GUID": "32dc886d-d7a6-11ed-3781-0201b014c5b2", "name": "Perform risk assessment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.3626527144263894, "y": 0.6212624584717608, "z": -4.969161571347911 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1838", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Process to ensure that new waste materials are classified according to legal requirements.", "Process_Group": "Healthy, Safety and Environment", "Scope": "Declaration of a new unknown waste material. Clarify permits, Dangerous goods, disposer, container etc.", "Outcome": "Waste material classified to legal requirements.", "GUID": "32dc887f-d7a6-11ed-3781-0201b014c5b2", "name": "Perform characterization of new waste materials", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.1122250048121654, "y": 0.6245847176079735, "z": -1.6622140471884415 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1839", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the plant internal transport and storage of waste before disposal. Including stock transfer processes (place in and release from stock)", "Process_Group": "Healthy, Safety and Environment", "Scope": "When the storage of waste material is required, plant internal transportation and put away much be preformed according to legal requirements.", "Outcome": "Waste material is stored.", "GUID": "32fc6c60-d7a6-11ed-3781-0201b014c5b2", "name": "Perform Waste storage", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6553032223113386, "y": 0.6279069767441858, "z": -2.5019934536696335 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1840", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the distribution of the dangerous goods master data to other ERP systems.", "Process_Group": "Healthy, Safety and Environment", "Scope": "After the dangerous goods master data has been created it is provided to other ERP systems as required.", "Outcome": "Dangerous goods master data is distributed.", "GUID": "32dc8857-d7a6-11ed-3781-0201b014c5b2", "name": "Distribute dangerous goods master", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.189631809951411, "y": 0.6312292358803986, "z": -3.3474635975390243 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1841", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Near misses are unplanned events that did not result in injury, damage or illness or damage. However, they had the potential to do so. With near misses management, organizations can determine the root cause of the near-miss and take preventative action.", "Process_Group": "Healthy, Safety and Environment", "Scope": "This process comprises all steps to record initially and then review and complete near misses.", "Outcome": "Near misses recorded, reviewed and preventative action defined.", "GUID": "32dc886f-d7a6-11ed-3781-0201b014c5b2", "name": "Perform near misses management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.715166281456148, "y": 0.6345514950166113, "z": -4.19855594985271 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1842", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the provision of the final packing specification document in order to allow external access by the vendors to the document.", "Process_Group": "Healthy, Safety and Environment", "Scope": "Upon vendors request technical specification for packaging material are made available.", "Outcome": "Specification document released to vendor.", "GUID": "32dc8867-d7a6-11ed-3781-0201b014c5b2", "name": "Provide technical specification for packaging material", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.2318626279170166, "y": 0.6378737541528241, "z": -5.055201672957599 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1843", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Deals with the activities required when planning new safety observation.", "Process_Group": "Healthy, Safety and Environment", "Scope": "This process consist of all steps to record initially and then review complete safety observations.", "Outcome": "Safety observation performed and documented.", "GUID": "32dc8869-d7a6-11ed-3781-0201b014c5b2", "name": "Perform safety observation management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.068479234228697, "y": 0.6411960132890364, "z": -1.690666178174171 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1844", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Labels can be print labels via manually generated print requests. You can generate print requests a number of times for the labels determined. Before the print requests are generated in Label Printing, you can change the values that are printed on the labels. This process cover activities from label print request through to print exduction.", "Process_Group": "Healthy, Safety and Environment", "Scope": "After they have been generated, the print requests are displayed in the Print Information System of the Labeling Workbench, where you print them out. Before doing so, you can check whether the label is correct and change its values. Once the print request is approved the label is selected and printed.", "Outcome": "Label successfully printed.", "GUID": "32dc8863-d7a6-11ed-3781-0201b014c5b2", "name": "Perform label printing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5894627408508208, "y": 0.6445182724252492, "z": -2.54432863353911 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1845", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that the required analysis reports are generated and available for use.", "Process_Group": "Healthy, Safety and Environment", "Scope": "Analyze costs and quantities of the recycling process and prepare corresponding reports. Generate legal declarations and general reporting.", "Outcome": "Analyse reports created.", "GUID": "32dc8875-d7a6-11ed-3781-0201b014c5b2", "name": "Perform recycling reporting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.1015511246587253, "y": 0.6478405315614619, "z": -3.403451611297808 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1846", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Process to ensure accessibility of required dangerous good reports", "Process_Group": "Healthy, Safety and Environment", "Scope": "Request to provide data to support dangerous goods processes and the requested data is provided in structured format.", "Outcome": "Dangerous goods reports are available in required format.", "GUID": "32dc885d-d7a6-11ed-3781-0201b014c5b2", "name": "Provide Dangerous Goods Reports", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.604701702439654, "y": 0.6511627906976742, "z": -4.26796544518673 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1847", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the dangerous goods master filling. The dangerous goods master provides dangerous goods-specific data for logistic processes in the ERP system.", "Process_Group": "Healthy, Safety and Environment", "Scope": "Create or maintain dangerous goods master data sets.", "Outcome": "Dangerous goods master data set for material created.", "GUID": "32dc885b-d7a6-11ed-3781-0201b014c5b2", "name": "Fill dangerous goods master", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -3.098872276240246, "y": 0.654485049833887, "z": -5.137800172792788 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1848", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "In many countries, regulations state that, above a certain quantity of chemicals and other hazardous substances, you must register with the authorities the maximum quantities of these substances that you plan to purchase, import, produce, sell, or export.", "Process_Group": "Healthy, Safety and Environment", "Scope": "This process determines and controls information and quantities of produced or imported hazardous substances.", "Outcome": "Substance for each relevant legal entity is tracked.", "GUID": "32dc8851-d7a6-11ed-3781-0201b014c5b2", "name": "Perform substance volume tracking", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.0240060386548053, "y": 0.6578073089700998, "z": -1.7179672967779374 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1849", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves performing chemical approval process for new hazardous substances.", "Process_Group": "Healthy, Safety and Environment", "Scope": "Run work flow steps for users involved and integrate to processes for chemical data extraction and risk assessment. Get approval for new hazardous substances.", "Outcome": "Chemical is released for use.", "GUID": "32dc3a30-d7a6-11ed-3781-0201b014c5b2", "name": "Manage chemical approval", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.522540146718384, "y": 0.6611295681063121, "z": -2.584931624169344 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1850", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Process for planning and scheduling of exposure measurements.", "Process_Group": "Healthy, Safety and Environment", "Scope": "The process ensures the measurement of the cumulative exposure to occupational and safety risks over an specified timeframe.", "Outcome": "Measurement performed and documented.", "GUID": "32dc886b-d7a6-11ed-3781-0201b014c5b2", "name": "Manage exposure measurement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.0120396948482706, "y": 0.6644518272425248, "z": -3.4571225414143014 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1851", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the central process of recycling administration.", "Process_Group": "Healthy, Safety and Environment", "Scope": "Based on individual requirements. This process creates the legally required declarations for reporting incurred costs for a recycling partner with whom you work.", "Outcome": "Recycling declaration created.", "GUID": "32dc8873-d7a6-11ed-3781-0201b014c5b2", "name": "Perform recycling data collection and calculation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.4924638319540704, "y": 0.6677740863787376, "z": -4.334469292358735 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1853", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The definition of areas of responsibility must be defined and used consistently within an organization. ", "Process_Group": "Strategic Management", "Scope": "The basis for this is the organizational plan. For the distribution of responsibilities and roles, the corresponding areas of responsibility are first selected (e.g. department, project, process, sub-project).", "Outcome": "Organigramm", "GUID": "109d63f3-a14c-11ed-3781-0201b014c5b2", "name": "Select area of responsibility", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.9637721997661606, "y": 0.6710963455149503, "z": -5.21690083746023 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1854", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Once the mission statement has been anchored in the company, it is disseminated and communicated to internal (and external) stakeholders in a targeted manner.", "Process_Group": "Strategic Management", "Scope": "When publishing the mission statement, it should be made clear to each individual employee at this point at the latest why the mission statement was introduced and what importance is attached to the mission statement. Only if this prerequisite is met can the actions of each company employee be aligned with the mission statement. ", "Outcome": "Mission statement is published on the website", "GUID": "a6484b69-9317-11ed-3781-0201b014c5b2", "name": "Publish mission statement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.978835695622171, "y": 0.6744186046511627, "z": -1.7440988162876152 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1855", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The top management appoints a person responsible for the creation, implementation and updating of the mission statement.", "Process_Group": "Strategic Management", "Scope": "The person responsible for the mission statement manages the process of developing a mission statement as a bottom-up procedure: it should be clearly communicated that the mission statement is to be developed by parts of the companys own staff the entire bottom-up procedure should be transparent as a process. The development of a participation process can support the involvement of managers and employees in the bottom-up process.", "Outcome": "Distribution of responsibilities, roles and authorities", "GUID": "a6484b5f-9317-11ed-3781-0201b014c5b2", "name": "Mission statement Determine responsibility", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.4545810010871758, "y": 0.6777408637873754, "z": -2.6237747828798548 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1856", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Procedures and methods are defined for controlling and monitoring the requirements. ", "Process_Group": "Strategic Management", "Scope": "Systematic control for the realization and monitoring of requirements can be supported by risk management, change management, process management or quality management.", "Outcome": "Continuous compliance with the requirements", "GUID": "167e350b-9350-11ed-3781-0201b014c5b2", "name": "Implement and monitor requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.9211584602640097, "y": 0.6810631229235882, "z": -3.5084398485018977 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1857", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Objectives are defined for the scope, concerning the organization, business areas, systems, processes, products and resources. These must be in line with the mission statement, measurable and take into account the applicable requirements. ", "Process_Group": "Strategic Management", "Scope": "In order to define the scope, the relevant stakeholders and their requirements must be known. Based on the underlying strategies, goals are defined. The objectives should be broken down into sub-objectives and assigned to organizational units, processes and products.", "Outcome": "Strategy and target plans", "GUID": "b55d6955-932e-11ed-3781-0201b014c5b2", "name": "Establish application area, objectives and strategies", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.3785290819962355, "y": 0.6843853820598005, "z": -4.398022215280198 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1858", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The requirements and expectations of the identified stakeholders are identified and assessed. The assessment is carried out with the aim of classifying the requirements and expectations according to relevance.", "Process_Group": "Strategic Management", "Scope": "The analysis includes a classification of the relevant requirements and expectations. For this purpose, the requirements and expectations can be assigned to characteristic classes, e.g., basic, performance, and enthusiasm characteristics. A distinction is made between subconscious, conscious and subconscious requirements of the stakeholders.", "Outcome": "Requirements matrix", "GUID": "167e3503-9350-11ed-3781-0201b014c5b2", "name": "Determine and analyze requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.826654375174038, "y": 0.6877076411960132, "z": -5.292449814907031 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1859", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Necessary framework conditions are established for the suggestion scheme. ", "Process_Group": "Strategic Management", "Scope": "The framework includes at least: Principles (grounds for exclusion, what counts as a suggestion), responsibilities/committees, methods and form of submission, procedures, communication, reward scheme.", "Outcome": "Guideline for the company suggestion scheme", "GUID": "9eb01150-9ca1-11ed-3781-0201b014c5b2", "name": "Regulate company suggestion scheme", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.9329989572832881, "y": 0.691029900332226, "z": -1.7690429462588795 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1860", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The mission statement must be made known to all employees and employee identification with its contents must be promoted. A mission statement is very well suited to describe the central principles of your corporate culture. Embedded in a holistic process of organizational development, it offers the opportunity to support the desired behavior of employees and managers in the company.", "Process_Group": "Strategic Management", "Scope": "The mission statement content and the reasons for introducing a mission statement must be explained in detail to create understanding and acceptance. Key factors are specifically symbolic actions by management and highlighting the mission statement as the result of a company-wide, joint process. ", "Outcome": "Promoting identification with the mission statement", "GUID": "a6484b67-9317-11ed-3781-0201b014c5b2", "name": "Anchoring the mission statement in the company", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.3856315708188032, "y": 0.6943521594684388, "z": -2.660831665090863 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1861", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "A role definition is the bundling of tasks, competence and responsibility to describe jobs, activities and persons. This allows generalized profiles to be created that can be used for similar tasks. This reduces the effort of documentation and makes roles comparable across the board. Employees can be found and deployed more easily according to their roles. Duplication of work and unclear responsibilities can be identified. The contents of the role description are: the name of the role, objectives, responsibilities of the employee, core tasks, professional knowledge and competencies. ", "Process_Group": "Strategic Management", "Scope": "The role description is supplemented with authorizations and powers. These include, for example, substitution rules, signing authority, budget management, release authority, authority to issue directives.", "Outcome": "Job Description", "GUID": "109d63f9-a14c-11ed-3781-0201b014c5b2", "name": "Determine roles and authorities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.8289692932185548, "y": 0.6976744186046511, "z": -3.5573685955300753 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1862", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Stakeholders are individuals, groups and organizations that influence an organization directly or indirectly. In the internal and external corporate environment (context), the interested parties who place requirements or expectations on the organization are identified. The stakeholders are then categorized and evaluated and classified according to relevance.", "Process_Group": "Strategic Management", "Scope": "The PESTLE method (Political, Economic, Socio-Cultural, Technological, Legal, Environmental) is suitable for stakeholder identification. The relevance can then be assessed using a stakeholder portfolio. The identified relevant stakeholders should be documented in a stakeholder register.", "Outcome": "stakeholder register", "GUID": "488cd655-9d74-11ed-3781-0201b014c5b2", "name": "Stakeholder identification", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.262975019805401, "y": 0.7009966777408638, "z": -4.4585809468637825 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1863", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "In order to implement the proposal, the person responsible for a process / a business unit has the task of recording all measures identified for the processes in a central action plan and assigning the implementation to the respective process owner (who can delegate within his process).", "Process_Group": "Strategic Management", "Scope": "The corresponding status update and completion message is sent by the process owner or the delegate to the person responsible for the process / business unit.", "Outcome": "Action plan", "GUID": "9eb0115a-9ca1-11ed-3781-0201b014c5b2", "name": "Implement proposal", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.687612152834228, "y": 0.7043189368770766, "z": -5.364395671083348 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1864", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The responsibilities and accountabilities are assigned to the areas of responsibility with the respective responsibility characteristics. ", "Process_Group": "Strategic Management", "Scope": "These can be mapped in a RACI matrix, for example.", "Outcome": "RACI-Matrix ", "GUID": "109d63f7-a14c-11ed-3781-0201b014c5b2", "name": "Determine responsibilities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8865270294752763, "y": 0.7076411960132889, "z": -1.7927827046270115 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1865", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The aim of the evaluation is to determine whether the effort involved in implementation is worthwhile for the company. For this purpose, the evaluation of the purpose must be separated from the evaluation of the solution path. ", "Process_Group": "Strategic Management", "Scope": "The evaluation is based on evaluation criteria for data collection. An essential parameter in the evaluation of a proposal is the cost-benefit assessment. Furthermore, criteria such as safety, health, environmental concerns, and customer preferences are considered. To facilitate data collection and evaluation, checklists can be useful as memory aids to systematically and quickly review all parameters relevant to the evaluation. After a positive assessment, the proposal is released for implementation.", "Outcome": "Release of the improvement proposal for implementation", "GUID": "9eb01158-9ca1-11ed-3781-0201b014c5b2", "name": "Evaluate and release proposals", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.3157387969646654, "y": 0.7109634551495017, "z": -2.696077042326865 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1866", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The implementation plans or strategic plans, are implemented through the defined actions. The resulting activities can be divided into factual and behavioral tasks. ", "Process_Group": "Strategic Management", "Scope": "In the context of the factual tasks, the strategies are concretized and translated into operational plans with short- and medium-term measures. The relevant strategic success factors must be adjusted. In this context, particular importance is attached to the success factors of organizational structure - and processes, corporate culture, management systems and personnel, and executives. These must be aligned with the strategy as well as with each other.", "Outcome": "Implementation of the strategic plans", "GUID": "b55d695b-932e-11ed-3781-0201b014c5b2", "name": "Implement strategy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7355349564702331, "y": 0.7142857142857144, "z": -3.603875471609676 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1867", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Setting objectives for the organization, business units, systems, processes, products and resources. These must be consistent with the mission statement, measurable, and take into account applicable requirements. ", "Process_Group": "Strategic Management", "Scope": "In order to define the scope, the relevant stakeholders and their requirements must be known. Based on the underlying mission statement, strategies and goals are defined. The objectives should be broken down into sub-objectives and assigned to the organizational units, processes and products.", "Outcome": "Strategy and target plans", "GUID": "5fb27f80-ab8f-11ed-3781-0201b014c5b2", "name": "Define mission statement, goals and strategies", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.1458803150551455, "y": 0.7176079734219267, "z": -4.516104258479739 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1868", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The specified requirements are documented and made available to the application area for fulfillment. ", "Process_Group": "Strategic Management", "Scope": "Typical documents are: Specifications, requirements catalogs, regulations catalogs and requirement specifications.", "Outcome": "requirements catalog", "GUID": "167e3507-9350-11ed-3781-0201b014c5b2", "name": "Document requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.546740193254893, "y": 0.7209302325581395, "z": -5.432689424958879 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1869", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Responsibilities, roles and authorities are assigned to areas, activities (processes) and documented on the basis of competencies. Documents for this can be organizational charts, job descriptions and matrix diagrams.", "Process_Group": "Strategic Management", "Scope": "Workflow: - Select area of responsibility - Determine competencies - Determine responsibility - Determine roles and authorities", "Outcome": "Job descriptions, matrix charts", "GUID": "5fb2a69b-ab8f-11ed-3781-0201b014c5b2", "name": "Define roles and responsibilities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8394515504748119, "y": 0.7242524916943522, "z": -1.8153019292683612 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1870", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Top management, in cooperation with the person responsible for the mission statement, defines clear objectives for the mission statement. The mission statement helps to justify actions both internally and externally.", "Process_Group": "Strategic Management", "Scope": "A well-formulated mission statement, broken down into individual sub-areas and properly introduced to employees, can fulfill the following purposes/objectives, for example: - improve internal and external communication - strengthen customer loyalty - Basis for goals and strategies goals and measures must be measured against the mission statement, - decision support for leadership and delegation, - basis for corporate identity. From the mission statement goals, concrete measures are derived for the realization of the mobilization, implementation and stabilization phases. Even at this early stage, considerable attention must be paid to how the workforces willingness to change can be created and maintained. Translated with DeepL", "Outcome": "defined mission statement objectives for the creation of a mission statement", "GUID": "a6484b61-9317-11ed-3781-0201b014c5b2", "name": "Determine the goals of the mission statement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2449502628082953, "y": 0.727574750830565, "z": -2.7294869193922793 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1871", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The organization must define and document the scope or area of application for the management system. The scope can refer to sites, business units or departments. ", "Process_Group": "Strategic Management", "Scope": "The scope defines the area of application in which certain regulations/guidelines, processes or procedures must be considered. The scope must be defined and documented. To meet the requirements of internal and external topics, interested parties (stakeholders), as well as interfaces and dependencies, regulations and guidelines are defined in writing.", "Outcome": "defined and documented scope of application", "GUID": "5fb2a6a1-ab8f-11ed-3781-0201b014c5b2", "name": "Determine scope and regulations", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6409190604939483, "y": 0.7308970099667773, "z": -3.647928814671095 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1872", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "All proposals should be documented in a central recording system. ", "Process_Group": "Strategic Management", "Scope": "When a proposal has been entered, the applicant is informed of this with a notice of receipt. For ease of retrieval, proposals should be classified by topic. A review of previous proposals will easily identify duplicate proposals. If a proposal cannot be implemented due to clear knock-out criteria, it should also be recorded in the system (for statistical purposes). Obvious nonsense, on the other hand, should be filtered out and not recorded.", "Outcome": "Acknowledgement of receipt", "GUID": "9eb01156-9ca1-11ed-3781-0201b014c5b2", "name": "Enter suggestions and confirm receipt", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.0273246862947425, "y": 0.7342192691029901, "z": -4.570552988024526 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1873", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Strategic control reviews the strategic planning premises, the strategic planning and implementation process, and the strategic results.", "Process_Group": "Strategic Management", "Scope": "Strategy control and monitoring addresses the question of whether strategic objectives have been achieved and whether it is necessary to adjust the strategy.", "Outcome": "Strategy optimization", "GUID": "b55d695d-932e-11ed-3781-0201b014c5b2", "name": "Controlling the strategy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.404134402636683, "y": 0.7375415282392028, "z": -5.497284581869376 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1874", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The necessary competencies must be defined for the respective areas of responsibility.", "Process_Group": "Strategic Management", "Scope": "Identification of core, key and cross-cutting competencies, modeling of competency profiles", "Outcome": "Competence Matrix", "GUID": "0cb9a748-9bdb-11ed-3781-0201b014c5b2", "name": "Set competence requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7918045694586792, "y": 0.7408637873754151, "z": -1.8365852890035779 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1875", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Top management anchors the vision, mission, values and culture in a mission statement/policy for internal and external publication.", "Process_Group": "Strategic Management", "Scope": "The creation of the mission statement should be carried out by the top management in order to give sufficient importance to the topic. The development process should be designed as a bottom-up procedure: it should be clearly conveyed that the mission statement is to be created by parts of the companys own staff the entire bottom-up procedure should be transparent as a process. Finally, the need for and the development of a mission statement must be communicated and exemplified by the management - and the employees must be able to understand it.", "Outcome": "Mission Statement / Company Policy", "GUID": "a6484b65-9317-11ed-3781-0201b014c5b2", "name": "Create mission statement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.1733141614704679, "y": 0.7441860465116279, "z": -2.761038550707479 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1876", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Development of strategies and specific implementation and strategic plans.", "Process_Group": "Strategic Management", "Scope": "Strategies are developed to achieve the goals, with definition and designation of activities for the tactical and strategic approach, required systems to coordinate and control the activities, resources, responsibilities, deadlines and key figures to evaluate the results.", "Outcome": "Strategic plans", "GUID": "b55d6957-932e-11ed-3781-0201b014c5b2", "name": "Plan strategy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5451860201749128, "y": 0.7475083056478407, "z": -3.6894986330199413 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1877", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Recognized proposals can be awarded in various forms. ", "Process_Group": "Strategic Management", "Scope": "The most common are cash prizes, non-cash prizes (e.g. vouchers), special prizes (e.g. free time) or a points system in which ideas are awarded points that can be exchanged for cash, non-cash or special prizes in a kind of prize store.", "Outcome": "Proposal Award", "GUID": "9eb0115c-9ca1-11ed-3781-0201b014c5b2", "name": "Recognize proposals be awarded", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.907388846676449, "y": 0.750830564784053, "z": -4.621890066582532 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1878", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The organization defines its vision and its own values as part of the corporate identity to represent and publish the corporate philosophy.", "Process_Group": "Strategic Management", "Scope": "The vision is the result of the interaction of mission, strategy and values. The vision describes the aspirations of an organization and its orientation towards higher-level, long-term goals. The mission defines the corporate purpose, the values and culture are the DNA of the organization.", "Outcome": "Company Statement", "GUID": "a6484b63-9317-11ed-3781-0201b014c5b2", "name": "Identify visions, values", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.2598918675794795, "y": 0.7541528239202657, "z": -5.558137165170371 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1879", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The proposal request is forwarded to the responsible parties through the regulated submission process.", "Process_Group": "Strategic Management", "Scope": "To formulate proposals, the company should provide proposal forms whose text encourages not only the desired improvement, but also the problem of the existing condition, the solution path, and the purpose or benefit of the improvement.", "Outcome": "submitted suggestion for improvement", "GUID": "9eb01154-9ca1-11ed-3781-0201b014c5b2", "name": "Submit proposals", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7436185246845363, "y": 0.7574750830564785, "z": -1.8566182940351508 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1882", "text": "Process", "data": { "Advisory_Notes": " ***different forecasts might need a different consumption logic. ***especially critical is the question on whether and how to consider left-over forecast in the next period.", "Type": "Business Process", "Description": "Purpose of this process is to determine the logic for forecast consumption", "Process_Group": "Sales and Operations Planning", "Scope": "Forecast consumption is an essential logic to steer how forecast values are replaced by actual demands. It needs to be defined on how to react to deviations between forecasts and actuals.", "Outcome": "Forecast consumption logic is defined.", "GUID": "79f07d65-cee4-11e9-0cfc-001bc641ce4f", "name": "Determine forecast consumption logic", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.1008792630991282, "y": 0.7607973421926912, "z": -2.7907104557940654 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1883", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Purpose of this process is to define the overall planning procedure.", "Process_Group": "Sales and Operations Planning", "Scope": "Aspects such as frequency, horizon, scope, responsibilities and stakeholders as well as necessary cascades an an overall timetable for planning iterations need to be defined (aligned) to ensure efficient and successful planning.", "Outcome": "Planning procedure is defined.", "GUID": "79ee3370-cee4-11e9-0cfc-001bc641ce4f", "name": "Define Sales & Operations Planning procedure", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.448401010954732, "y": 0.7641196013289036, "z": -3.7285566257555094 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1884", "text": "Process", "data": { "Advisory_Notes": " ***Sales and Operations Planning function should coordinate and define the different approaches in order to ensure feasibility of usage of the different results. ***Furthermore logical breaches and contradictory assumptions need to be avoided.", "Type": "Business Process", "Description": "Purpose of this process is to define the different needed planning approaches.", "Process_Group": "Sales and Operations Planning", "Scope": "Different planning disciplines will need different approaches. This is about planning strategy, cascades within the discipline and detail levels but is not limited to these topics.", "Outcome": "Planning approaches for different planning disciplines are defined.", "GUID": "79f07d63-cee4-11e9-0cfc-001bc641ce4f", "name": "Define planning approach for different planning disciplines", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.7861544490056647, "y": 0.7674418604651163, "z": -4.670080543662739 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1885", "text": "Process", "data": { "Advisory_Notes": " ***forecast accuracy is the most common KPI for accuracy measurement, but also in other areas it is useful to have a look at deviations between plan and actuals.", "Type": "Business Process", "Description": "Purpose of this process is to monitor the planning accuracy.", "Process_Group": "Sales and Operations Planning", "Scope": "Planning accuracy is measured and monitored continuously. Deviation from plan to actual needs to be investigated in order to determine if planning procedure should be adjusted or optimization potentials in operations can be derived from the findings.", "Outcome": "Planning accuracy is monitored and follow-up activities have been initiated.", "GUID": "79f07d67-cee4-11e9-0cfc-001bc641ce4f", "name": "Monitor planning accuracy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -2.1141107889853736, "y": 0.7707641196013291, "z": -5.615205746176683 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1886", "text": "Process", "data": { "Advisory_Notes": " ***aggregation level is a key driver of effort during planning but is also crucial with regards to how meaningful planning results will be.", "Type": "Business Process", "Description": "Purpose of this process is to determine the aggregation levels for planning.", "Process_Group": "Sales and Operations Planning", "Scope": "In order to allow all planning disciplines to interact efficiently it is necessary to align on the aggregation levels of the different plans or at least of the interfaced/exchanged information.", "Outcome": "Aggregation levels for all planning disciplines are determined.", "GUID": "79f07d61-cee4-11e9-0cfc-001bc641ce4f", "name": "Determine aggregation levels", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.6949262214068445, "y": 0.7740863787375414, "z": -1.8753873058121102 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1894", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "After a demand for materials is identified, a purchase requisition (PR) is created to capture the details of the demand. The PR is an internal document and its details include e.g. the quantity and timeframe for the required material. The PR is then routed for an approval. Typically, a two-stage approval workflow is required, i.e., content and budget approval.", "Process_Group": "Purchasing Indirect", "Scope": "The creation of a PR takes place in SAP Ariba. After submitting the the PR for approval, an automated transfer of the document will be send to SAP S4/HANA and therefore be created also in the ERP system with status In Release. Simultaneously, the approver can check if all relevant information is included in the PR and approve the document in SAP Ariba. In S4/HANA, all information and progress of the PR can be monitored at any point in time.", "Outcome": "The approved PR is ready to be converted into a PO.", "GUID": "b62d71dd-68cd-11ee-3781-0201b014c5b2", "name": "Create and approve purchase requisition for indirect materials (Ariba)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.0276948816664775, "y": 0.7774086378737541, "z": -2.8184824338988745 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1895", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Advance procurement must be carried out at the very beginning of the project execution. In this process ProMan is used to control the activity. Sometimes long lead time procurement is triggered before the order is confirmed. Although whenever possible a supplier will avoid ordering project-specific materials beforehand, in some situations it is required.", "Process_Group": "Purchasing Indirect", "Scope": "The data for needed material (of long lead time material) is checked, and whether its planned demand will be met. With the release of this activity the demand for (long lead time) items are created for the MRP run.", "Outcome": "A purchase order is created for the procurement of the required materials.", "GUID": "b62d71e3-68cd-11ee-3781-0201b014c5b2", "name": "Perform advance procurement of indirect materials", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.3506299244597006, "y": 0.7807308970099669, "z": -3.765076202038145 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1896", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Processing the purchase order with returnable packaging information ensures that the cost, quantity and other conditions related to the returnable packaging material are recorded in the purchase order (PO).", "Process_Group": "Purchasing Indirect", "Scope": "When returnable packaging is received from a vendor along with products, information about the quantity and value of the returnable packaging, as well as return conditions and the vendor to which the packaging is to be returned must be captured in the PO and forwarded for further processing.", "Outcome": "Returnable packaging information is recorded in the PO.", "GUID": "b62d71ef-68cd-11ee-3781-0201b014c5b2", "name": "Process purchase order for indirect materials with returnable packaging", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6637040301513704, "y": 0.7840531561461792, "z": -4.715091610993162 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1897", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "An approved purchase requisition (PR) is automatically converted into a purchase order (PO). For purchases based on a contractual agreement with the supplier, the agreed terms, conditions and prices stated in the supplier contract are applied to the order.", "Process_Group": "Purchasing Indirect", "Scope": "The PO is created with information from the purchase requisition as well as details regarding the terms and conditions specified in the supplier contract.", "Outcome": "The PO is ready for further processing.", "GUID": "b62d71e0-68cd-11ee-3781-0201b014c5b2", "name": "Convert purchase requisition for contract into purchase order- Indirect", "Business_Rules": "The set-up of possible conversions must be defined. Conversion options are: ***single ***multiple ***partial", "Prerequisite": "" }, "position": { "x": -1.9668904152031477, "y": 0.787375415282392, "z": -5.6684514723672095 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1898", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Once terms for purchasing of one-time service have been agreed, a purchase requisition (PR) must be created to capture information about the procured service in the ERP system.", "Process_Group": "Purchasing Indirect", "Scope": "Since the purchased service is not regularly purchased, its details are not contained in the ERP system and cant be included into the PR. Therefore the purchase requisition must have reference to a statement of work, previously negotiated vendor proposal or other documents stating content and terms of the service.", "Outcome": "PR for services with necessary details is created and ready for the approval workflow.", "GUID": "b62d71ec-68cd-11ee-3781-0201b014c5b2", "name": "Create purchase requisition for one-time services- Indirect", "Business_Rules": "", "Prerequisite": "Pre-requisites: request for proposal process has been performed if required, vendor proposal has been received, its terms negotiated and approved by purchasing department." }, "position": { "x": -0.6457608095428933, "y": 0.7906976744186047, "z": -1.8928795463152184 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1899", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The approval process for purchase requisition (PR) for one-time services confirms that the specific service can be purchased by the requester and performed by the identified service provider. Moreover, the duration of the service to be performed and other related terms and conditions are verified.", "Process_Group": "Purchasing Indirect", "Scope": "The purchasing department verifies that the service can be purchased by the requester and that all necessary information regarding the service is recorded, including type and duration of service as well as vendor.", "Outcome": "The PR for one-time services is ready to be converted into a purchase order (PO).", "GUID": "b62d71f8-68cd-11ee-3781-0201b014c5b2", "name": "Approve purchase requisition for one-time services- Indirect", "Business_Rules": "It needs to be clarified what will happen if the PR is not converted into a PO because: ***the price for the service exceeds the budget ***the purchase of services is not required It is necessary to define what services a department is allowed to purchase.", "Prerequisite": "" }, "position": { "x": -0.9538108413958204, "y": 0.7940199335548175, "z": -2.844335577746725 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1900", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "By using the SAP Business Network all documents required are exchanged electronically. These documents can be: ***Purchase requisition ***Purchase order ***Order confirmation ***Goods receipt ***Invoice", "Process_Group": "Purchasing Indirect", "Scope": "After the supplier receives the PO via the SAP Business Network, the order confirmation can be created, if required. The confirmation data is transferred to the procuring organization and the PO is updated. At any time, the procuring company is able to monitor the suppliers updates via the the network.", "Outcome": "PO is enriched with order confirmation data.", "GUID": "b62d71f5-68cd-11ee-3781-0201b014c5b2", "name": "Exchange electronic documents via SAP Business Network - Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.251939323641519, "y": 0.7973421926910298, "z": -3.7990324991923954 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1901", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To ensure an accurate period end closing, all financial transactions related to procurement of services in a particular period must be reviewed and reconciled.", "Process_Group": "Purchasing Indirect", "Scope": "It involves checking open Purchase Orders (POs) for which Goods Receipts (GRs) have not yet been posted. Invoices must be validated and any discrepancies between the purchase order, goods receipt, and invoice must be resolved. In terms of services, all open purchase orders for which service entry sheets have not been confirmed and blocked invoices due to price variance between vendor invoice and service entry sheets are reviewed and resolved. Additionally, all open items related to service entry sheets should be reviewed to ensure there are no outstanding corresponding invoice postings. All accrued transactions must be recorded in the period in which the transactions occurred.", "Outcome": "Purchasing transactions posted in correct accounting period.", "GUID": "b62d71d4-68cd-11ee-3781-0201b014c5b2", "name": "Conduct period end closing purchasing - Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.5401209548546944, "y": 0.8006644518272426, "z": -4.756892624856847 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1902", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purchase requisition (PR) for services is a notification that informs the purchasing department that additional services, e.g. for a specific project, are required.", "Process_Group": "Purchasing Indirect", "Scope": "It must be determined where external resources are needed and what availability is required to perform the service. The requisition is triggered by the user department. The PR for services can contain a set of service specifications with details of the necessary service or group of services. It can also be very basic with a superficial provision for unplanned services. This can be the case for hiring external employees. In this case, the extent and the precise nature of the service are not fully determined yet.", "Outcome": "The PR includes all required information: ***specific value (max. price) ***services with certain skills ***time frame ***reason, stating why a service needs to be purchased", "GUID": "b62d71e9-68cd-11ee-3781-0201b014c5b2", "name": "Create purchase requisition for standard services- Indirect", "Business_Rules": "The reasons, stating why purchasing a service is necessary to achieve a certain task, must be clearly defined. ***How are the services purchased e.g. via a bidders platform? ***What if the price of the service exceeds the budget e.g. of a project? ***How is the internal hiring process started? ***How is the bid procedure performed? ***How were the quotations compared?", "Prerequisite": "" }, "position": { "x": -1.8183309744595728, "y": 0.8039867109634553, "z": -5.717838093835895 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1903", "text": "Process", "data": { "Advisory_Notes": "***set-up of possible conversions must be defined. Conversion options are single, multiple or partial ***purchasing strategies for vendors need to be considered (e.g. fair share, contingents) ***special agreements with vendors need to be considered (e.g. FTL/FCL only, min/max quantities, multiple products to be bundled)", "Type": "Business Process", "Description": "An official purchase order (PO) has to be created from a purchase requisition (PR) to be able to order indirect materials and services.", "Process_Group": "Purchasing Indirect", "Scope": "The PO is created with reference to a specific PR. Additional data not provided within the PR has to be maintained.", "Outcome": "A PO is generated.", "GUID": "b62d71fe-68cd-11ee-3781-0201b014c5b2", "name": "Convert purchase requisition for indirect materials to purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.5961557611042203, "y": 0.8073089700996676, "z": -1.90908310675629 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1905", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Monitoring purchase order (PO) for services ensures - through communication with the vendor - that the correct service will be performed on time.", "Process_Group": "Receipt Handling Indirect", "Scope": "After the PO has been sent to the vendor, it needs to be tracked. The vendor hereby sends an order acknowledgement to confirm the receipt of the PO. The service provider may provide additional data or inform about changes at any time.", "Outcome": "Order acknowledgement received.", "GUID": "a7e9c093-68ce-11ee-3781-0201b014c5b2", "name": "Monitor purchase order for services- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8792774428410353, "y": 0.8106312292358804, "z": -2.8682522864125692 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1906", "text": "Process", "data": { "Advisory_Notes": "Depending on the nature of the service and the organizational set-up different variations who actually captures the service delivery via the service entry sheet and who confirms it finally can be established.", "Type": "Business Process", "Description": "Receipt confirmation takes place after service has been performed and is used to record the service performance fact and initiate billing process on vendor side and payment process on service recipient side.", "Process_Group": "Receipt Handling Indirect", "Scope": "Vendor provides a confirmation once the service has been performed. This serves as a trigger for recording the service fulfillment, which is done via service entry sheet. Once service fulfillment is recorded, it must be confirmed by the requestor, if the service has actually been performed, as well as if it complies with agreed requirements on time, cost and quality. If requestor confirms the service, billing and payment process can be initiated.", "Outcome": "Service is confirmed, billing and payment can be initiated.", "GUID": "a7e9c096-68ce-11ee-3781-0201b014c5b2", "name": "Confirm service receipt- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.1523963974609495, "y": 0.8139534883720931, "z": -3.830402399633624 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1908", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "After identification of suitable vendors it is possible to maintain the vendor in a source list to determine through which vendor a certain material/service is to be purchased at one specific time.", "Process_Group": "Sourcing Indirect", "Scope": "The supplier is identified as a source. It is captured and that the supplier delivers certain materials/services for the organization within a pre-defined period.", "Outcome": "Source list created.", "GUID": "0e64c977-68cb-11ee-3781-0201b014c5b2", "name": "Create source list- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.415489358973863, "y": 0.8172757475083055, "z": -4.795455126954246 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1909", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Compared to contracting for direct materials and services, the process of capturing vendor contract is rather decentralised in a way that a requestor or a category manager captures contract-relevant information for further processing.", "Process_Group": "Sourcing Indirect", "Scope": "Gathering pertinent information concerning the contract, including details on product types, quantities, agreed prices, and associated terms and conditions for the purchase. Subsequently, delivering this comprehensive data to the authorised entity or person to validate the contract details.", "Outcome": "Contract created.", "GUID": "0e64c97a-68cb-11ee-3781-0201b014c5b2", "name": "Capture vendor contract- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.6685336066236318, "y": 0.8205980066445182, "z": -5.7633319879708065 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1910", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes requesting quotation (RFQ) for the indirect materials or services from identified potential suppliers. It can be as simple as providing prices or as complex as requesting proposal from multiple suppliers (RFI, RFS, RFP).", "Process_Group": "Sourcing Indirect", "Scope": "Creating and issuing RFQ, potentially RFI, RFS, RFP, and collecting vendors responses.", "Outcome": "Vendors responses to RFQ collected.", "GUID": "0e64c95c-68cb-11ee-3781-0201b014c5b2", "name": "Request quotation from vendors- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.5461448474087227, "y": 0.823920265780731, "z": -1.9239869556857456 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1911", "text": "Process", "data": { "Advisory_Notes": "Material master data might be already captured.", "Type": "Business Process", "Description": "Information on products or services requested by different departments needs refinement to ensure that comprehensive details are accessible for the initiation of supplier search processes. This involves specifying critical elements such as specifications, quantities, quality standards, and any other pertinent information. The purchasing department typically plays a crucial role in orchestrating and overseeing the demand management process across diverse departments. However, that can also be performed by specialized category managers from other departments.", "Process_Group": "Sourcing Indirect", "Scope": "Reviewing and consolidating the initial product or service information provided by each department. Additional information is sourced in order to complete the definition of requested product or services.", "Outcome": "Requested product or service is defined.", "GUID": "0e64c96e-68cb-11ee-3781-0201b014c5b2", "name": "Complete definition of requested product or services- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.80414542864174, "y": 0.8272425249169437, "z": -2.890216277304277 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1912", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Market evaluation empowers the requester with insights into the current landscape of products and services available on the market. Concurrently, potential suppliers undergo scrutiny against pre-established sourcing criteria, encompassing factors like price, technical specifications, quality, lead time, supplier ratings and CSR aspects. In certain scenarios, the market assessment may occur at the outset of the entire sourcing workflow. This proactive approach aids the requester in refining product or service details, especially when dealing with novel or innovative offerings.", "Process_Group": "Sourcing Indirect", "Scope": "Evaluating market for demanded products or services, sorting and assessing potential suppliers.", "Outcome": "Potential suppliers selected.", "GUID": "0e64c974-68cb-11ee-3781-0201b014c5b2", "name": "Evaluate market- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.0520689151453375, "y": 0.830564784053156, "z": -3.8591645466065465 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1913", "text": "Process", "data": { "Advisory_Notes": "Typically at the end of the negotiations the vendor master data and other master data is initiated if required.", "Type": "Business Process", "Description": "Before purchasing goods under a contractual agreement with the supplier, it is necessary to define the conditions and set the terms under which the goods will be provided. The purchasing department must understand exactly what products (e.g. goods or services) need to be purchased and in what quantity, as well as select the supplier and prepare the contracting details with the supplier.", "Process_Group": "Sourcing Indirect", "Scope": "Based on the products and quantity that needs to be purchased, a suitable supplier is selected. Specific terms and conditions related to the purchase are negotiated and a contract document prepared.", "Outcome": "The contract with the supplier is approved.", "GUID": "0e64c956-68cb-11ee-3781-0201b014c5b2", "name": "Perform contracting- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2898940922041464, "y": 0.8338870431893688, "z": -4.83075286377774 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1914", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Determine supply source and conditions aims at finding the external source from which a customer order will be fulfilled, as well as agreeing on the related conditions. The Determine supply source and conditions process is required for third party sales and sales via subcontracting, as well as in certain constellations of intercompany processes. In case of the latter, external source may also refer to other entities of the group.", "Process_Group": "Sourcing Indirect", "Scope": "After the customer order data is captured, the external source (external vendor) used to fulfil the order and related conditions must be determined.", "Outcome": "Source of supply and conditions related to the order are defined and documented.", "GUID": "60b9edd6-68d3-11ee-3781-0201b014c5b2", "name": "Determine supply source and conditions- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.517600294350085, "y": 0.8372093023255816, "z": -5.804902182344551 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1915", "text": "Process", "data": { "Advisory_Notes": "Choosing a supplier can result in diverse business scenarios, including supplier contracting, procurement through a catalog or vendor portal, or a direct purchase order without the need for additional contractual engagements.", "Type": "Business Process", "Description": "This process involves the assessment of vendor responses to RFQs, and possibly RFPs, focusing on negotiation aspects. The final decision is made based on predetermined sourcing criteria that encompass factors such as price, coverage of specified requirements, quality, lead time, supplier ratings and CSR.", "Process_Group": "Sourcing Indirect", "Scope": "Evaluating vendor responses based on predefined criteria and making the final decision, which vendor will supply the requested product or service. A supplier is selected and informed about the decision.", "Outcome": "The selected supplier is informed about the decision.", "GUID": "0e64c968-68cb-11ee-3781-0201b014c5b2", "name": "Evaluate vendors and make final decision- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.4957621160890083, "y": 0.8405315614617939, "z": -1.9375809465028677 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1916", "text": "Process", "data": { "Advisory_Notes": "* in a multi-plant setup it needs to be determined which plant is allowed to order raw materials at a supplier and which should order raw materials via intercompany replenishment setups.", "Type": "Business Process", "Description": "Purpose of this process is to define needed rules on how to choose the source of supply during actual procurement activities.", "Process_Group": "Sourcing Indirect", "Scope": "For all cases with multiple possible suppliers the rules for choosing source of supply are defined. This includes consideration of existing contracts with suppliers, alignment with Purchasing on impacts to new contracts and results into source of supply settings in the system (e.g. favorite SoS, fair-share rules or certain quotas per supplier). In addition intercompany supply needs to be considered as possible option. Sometimes even externally sourced products might be supplied internally via intercompany in order to improve external supply set up by bundling the sourcing from a certain supplier to one of the plants.", "Outcome": "Determination rules for source of supply are defined.", "GUID": "0e64c971-68cb-11ee-3781-0201b014c5b2", "name": "Determine rules for source of supply decisions- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7284659489775257, "y": 0.8438538205980066, "z": -2.9102125972478836 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1917", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "In terms of indirect materials and services, contract monitoring is typically decentralised. It involves the requestor or category manager to monitor the fulfilling of the contractual conditions and contract lifecycle.", "Process_Group": "Sourcing Indirect", "Scope": "Checking whether the supplier is compliant with the contract (i.e., service levels, specifications, and quality).", "Outcome": "Ensuring compliance of POs and provision of materials and services with the contract.", "GUID": "0e64c96b-68cb-11ee-3781-0201b014c5b2", "name": "Monitor vendor contract- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.9510251800509957, "y": 0.8471760797342194, "z": -3.8852993587250095 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1918", "text": "Process", "data": { "Advisory_Notes": "Settling the contract may lead to a debit or credit note. Follow-up contracts might be negotiated.", "Type": "Business Process", "Description": "This process ensures that any obligation from both parties are met and financially settled. This is executed periodically or at expiration of the contract. Typically, there is no difference in approval workflows and procedures for direct and indirect materials and services.", "Process_Group": "Sourcing Indirect", "Scope": "Scope is the same as in direct materials and services.", "Outcome": "Contract settled.", "GUID": "0e64c959-68cb-11ee-3781-0201b014c5b2", "name": "Settle contract- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.1634206603118877, "y": 0.8504983388704317, "z": -4.862761804485127 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1919", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Possible suppliers are evaluated regarding aspects that are important for a well-set and cordial working co-operation. These can include: ***company profile ***management ***quality ***compliance ***reputation ***location", "Process_Group": "Sourcing Indirect", "Scope": "Depending on the purchasing requirements, possible suppliers are sorted and evaluated in order to determine who is most suited. Based on the assessment, a quotation or proposal is requested from the selected suppliers.", "Outcome": "Suppliers, who will be involved in further sourcing process, are selected.", "GUID": "0e64c965-68cb-11ee-3781-0201b014c5b2", "name": "Evaluate source of supply- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.3656337936492675, "y": 0.8538205980066444, "z": -5.842520375800422 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1920", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When acquiring indirect materials and services, the process of gathering product or service information is more decentralized compared to direct sourcing. Information for a particular product or service may be collected either at a single instance for one-time demands or multiple times in response to evolving needs or sourcing criteria.", "Process_Group": "Sourcing Indirect", "Scope": "Defining product or service needs and gathering necessary information for sourcing. Typically, information is captured in a less standardized format.", "Outcome": "Product or service information captured.", "GUID": "0e64c962-68cb-11ee-3781-0201b014c5b2", "name": "Gather product/service information- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.4450418679126292, "y": 0.8571428571428572, "z": -1.9498558243636472 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1921", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "In this collaborative process, suppliers and customers engage in negotiations to establish and mutually agree upon the terms and conditions that will govern their anticipated relationship. This negotiation is often informed by the prior exchange of Request for Proposal (RFP) or Request for Quotation (RFQ) documents, along with the corresponding responses.", "Process_Group": "Sourcing Indirect", "Scope": "Align and agree scope of services, negotiate and agree contract or purchase order terms.", "Outcome": "Terms of purchase order to a contract negotiated.", "GUID": "0e64c95f-68cb-11ee-3781-0201b014c5b2", "name": "Perform vendor negotiations- Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.6522905267446694, "y": 0.86046511627907, "z": -2.928227632667782 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1925", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the creation of a document that presents detailed information of how effective and efficient each process or stage along the supply chain functions in satisfying customers demand. This information can be used to develop strategies, implement changes, and measure the impact of those actions on the overall performance of the supply chain.", "Process_Group": "Supply Chain Reporting and Analytics", "Scope": "Supply chain performance report covers several aspects such as lead times, inventory management, cost-efficiency, supplier performance, and quality management ", "Outcome": "Supply chain performance is assessed.", "GUID": "47644cbf-5b9e-11ee-3781-0201b014c5b2", "name": "Generate supply chain performance report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.8493339831620565, "y": 0.8637873754152823, "z": -3.908789043303063 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1926", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This refers to predicting future demand for products or services. This helps companies to align their production, inventory, and supply chain activities to meet customer demand effectively and efficiently.", "Process_Group": "Supply Chain Reporting and Analytics", "Scope": "It involves the use of predictive analysis techniques in analyzing historical data, market trends, and other relevant data to estimate the value of goods or services that customers will demand over a specific period of time.", "Outcome": "Information on demand forecast over a specific period is provided.", "GUID": "47644cc1-5b9e-11ee-3781-0201b014c5b2", "name": "Create demand forecasting report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.0361551669217701, "y": 0.867109634551495, "z": -4.891460157259928 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1931", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is to provide detailed information of all orders a company has placed with its suppliers. By reporting on purchase orders, a company is able to identify trends in its purchasing habits, monitor its inventory levels, and maintain accurate financial records of purchasing expenses. ", "Process_Group": "Procurement Reporting and Analytics", "Scope": "This report contains information about order details, order status and order tracking. ", "Outcome": "Detailed information about purchase order activity is provided.", "GUID": "47644ca1-5b9e-11ee-3781-0201b014c5b2", "name": "Generate purchase order report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.2127375639303806, "y": 0.8704318936877078, "z": -5.876160957719947 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1932", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes evaluation of vendor or supplier performance based on various criteria, such as timeliness of deliveries, quality of products and services, accuracy of orders, cost and pricing, communication and responsiveness etc.", "Process_Group": "Procurement Reporting and Analytics", "Scope": "Collecting data on vendor performance, selecting criteria for evaluation, analysis and reporting the results.", "Outcome": "Vendor performance report created.", "GUID": "47644ca3-5b9e-11ee-3781-0201b014c5b2", "name": "Create vendor performance report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.39401863342998084, "y": 0.8737541528239201, "z": -1.960803232481518 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1933", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To perform supplier collaboration analytics means a company analyzes and evaluates its interactions, transactions, and relationships with its suppliers to gain insights and make informed decisions. It enables a company to reduce costs and inefficiencies, and streamline ordering process.", "Process_Group": "Procurement Reporting and Analytics", "Scope": "This differs from traditional customer-supplier relationship which focuses more on transactional relationship. Instead, this process focuses on how effective a company considers its suppliers as strategic business partners who can be worked with to develop strategies aimed at improving the procurement of goods and services.", "Outcome": "Strategic relationship between a company and its supplier is analyzed.", "GUID": "47644ca9-5b9e-11ee-3781-0201b014c5b2", "name": "Perform supplier collaboration analytics", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.5756710224791776, "y": 0.8770764119601329, "z": -2.944249118854887 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1934", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of collecting and analyzing procurement data to make informed decisions about procurement processes. It helps a company in supplier contract management, supplier risk management, strategic sourcing, and inventory management.", "Process_Group": "Procurement Reporting and Analytics", "Scope": "Depending on the purpose of analysis, the type of data required will vary. However, procurement analytics is broadly made up of historical or predictive analysis. ", "Outcome": "Procurement data is analyzed.", "GUID": "47644ca5-5b9e-11ee-3781-0201b014c5b2", "name": "Perform procurement analytics", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7470645562572411, "y": 0.8803986710963456, "z": -3.9296176084683063 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1935", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Supplier performance and evaluation report is a document that enables a company to assess the performance of its suppliers against its defined criteria. It enables the company to determine if its suppliers are able to meet its objectives.", "Process_Group": "Procurement Reporting and Analytics", "Scope": "This involves definition of performance and evaluation criteria and supplier evaluation method, data collection and analysis.", "Outcome": "Quality of supplier performance is evaluated and reported", "GUID": "47644ca7-5b9e-11ee-3781-0201b014c5b2", "name": "Create supplier performance and evaluation report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.9081842548971852, "y": 0.8837209302325579, "z": -4.91682838414733 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1943", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When a change in the customer data is needed, the change can be requested in a particular area, as well as in all areas at the same time. The reason for change should be defined and approved. The data for one customer can also differ for each sales area, therefore it is possible to change data for one customer in only one sales area. The sales area is a combination of sales organization, distribution channel and division. Therefore, when maintaining sales document, it is necessary to assign a sales group. If you edit a customer master record, you must enter the customer number and the sales area in order to access screens containing sales and distribution data.", "Process_Group": "Customer Contracts", "Scope": "Customer view to be maintained.", "Outcome": "Request documented in specific system with required detail based on internal policy.", "GUID": "57c03164-9173-11e8-2ddf-001bc640cd9b", "name": "Maintain the customer and sales data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -1.0590156975659066, "y": 0.8870431893687707, "z": -5.905801025458697 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1945", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Monitor location of returnable packaging,\n Monitor timeframe of returnable packaging", "Type": "Business Process", "Description": "In a rental situation it is necessary to track returnable packaging in order to: ***Know how long the packaging will stay with the customer ***Know what units are with which customer ***Record when packaging were issued and when they are returned.", "Process_Group": "Returnable Packaging Management", "hasAssignment": true, "Scope": "Once returnable packaging have been sent out to the customer, all relevant information concerning the packaging is collected and recorded. With this information the movement of the packaging is tracked until returned to the storage facility of the organisation.", "Outcome": "Returnable packaging can be tracked after issuing them to the customer.", "GUID": "0182227a-7e4f-11e5-0a66-001bc640cd9b", "name": "Track returnable packaging", "Business_Rules": "The decision must be made regarding what information is required for tracking. It is necessary to define what movements of the packaging will be tracked e.g. only movement to/from internal storage facility to customer location, movement between external storage locations, etc.", "Prerequisite": "" }, "position": { "x": -0.34272714946576316, "y": 0.8903654485049834, "z": -1.9704157178166928 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1948", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Assign sales area,\n Mantain fields in the Order Tab,\n Save the customer data,\n Mantain shipping information,\n Maintain billing information", "Type": "Business Process", "Description": "Sales document needs to be maintained for all customers and the data for one customer can also differ for each sales area. The sales area is a combination of sales organization, distribution channel and division. Therefore where maintaining sales document, it is necessary to assign a sales group. If you edit a customer master record, you must enter the customer number and the sales area in order to access screens containing sales and distribution data.", "Process_Group": "Sales Order Management", "hasAssignment": true, "Scope": "Data in sales document to be maintained: ***Assign sales area - data includes pricing data, delivery priority, shipping condition ***Shipping information ***Billing information", "Outcome": "Sales document maintained.", "GUID": "ba2c9087-6a54-11e8-2ddf-001bc640cd9b", "name": "Maintain sales document", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.4986595990498858, "y": 0.8936877076411962, "z": -2.958266148316511 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1951", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Contact customer and qualify request,\n Convert customer into opportunity ,\n Close lead,\n Define follow up tasks,\n Trigger quotation processing", "Type": "Business Process", "Description": "This process is triggered on behalf of a lead in the context of an existing customer. The lead is typically qualified and based on the outcome an opportunity may be created.", "hasAssignment": true, "Process_Group": "Customer Relationship Mgmt", "Scope": "Qualify customer request and define follow up activities and create opportunity", "Outcome": "Opportunity created", "GUID": "5a1ed1e2-6a4f-11e8-2ddf-001bc640cd9b", "name": "Qualify customer request and create opportunity", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.644286524776621, "y": 0.8970099667774085, "z": -3.94777087404921 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1953", "text": "Process", "data": { "Advisory_Notes": "It is highly recommended to implement strict rules on who is allowed to adjust which business partner data.", "KeyActivities": "Review request for business partner change,\n Maintain sales data for business partner,\n Maintain purchasing data for business partner,\n Maintain ship-to address,\n Maintain financial data,\n Change and save business partner data", "Type": "Business Process", "Description": "This process describes changing the business partner data.", "hasAssignment": true, "Process_Group": "Customer Relationship Mgmt", "Scope": "The requested changes are conducted on the respective areas of business partner data.", "Outcome": "Business partner data has been changed.", "GUID": "37205d85-8d0d-11e9-0cfc-001bc641ce4f", "name": "Change business partner", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7795950473533593, "y": 0.9003322259136213, "z": -4.93884921435572 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1955", "text": "Process", "data": { "Advisory_Notes": "Business partners could be customers but also suppliers. Even focussing on sales only, there are multiple different business partner roles, such as sold-to and ship-to parties. General data needed to maintain might be: ***Title and name ***Street address ***Postal code/country/city ***Communication language ***Bank account details. Sales data is maintain per sales area, which is a combination of sales organization, distribution channel and division.The data includes: ***shipping address *** invoicing address ***different status data to block certain transactions. Procurement data typically includes: ***vendors name and address ***currency used for ordering from vendor ***terms of payments ***source list ***quota arrangement ***conditions ***purchasing info records ***vendor evaluation. Mandatory financial data might differ based on the business policy. It usually includes: ***company code ***terms of payment for customer ***reconciliation account ***dunning procedure ***account group. In addition to the above mentioned data a business partner profile might need to be maintained, which includes for example business partner specific documents or document layouts (this is represented in a separate process). If needed also the credit limit of a business partner could be maintained including the necessary approval (this is represented in a separate process).", "KeyActivities": "Create general business partner data,\n Maintain sales data for business partner,\n Maintain purchasing data for business partner,\n Maintain ship-to address,\n Maintain financial data,\n Save business partner data", "Type": "Business Process", "Description": "This process describes the creation of a new business partner.", "hasAssignment": true, "Process_Group": "Customer Relationship Mgmt", "Scope": "After entering the general data, additional information on sales, ship-to, procurement, finance is maintained.", "Outcome": "The business partner has been created.", "GUID": "37205d81-8d0d-11e9-0cfc-001bc641ce4f", "name": "Create business partner", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.9045728490251004, "y": 0.903654485049834, "z": -5.931420399938501 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1958", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "With the commercial completion of the service, no more costs can be allocated to the service. The service order is completed from an accounting/controlling perspective. This process describes the settling of the service order, which is the posting of all costs and revenues related to the service order and its transfer to the profitability analysis. ", "Process_Group": "Billing, Rebates and Commissions", "Scope": "Post costs and revenues related to the service order and transfer to the profitability analysis via settlement, complete service order.", "Outcome": "All costs and revenues settled to service order and service order is closed from a business perspective.", "GUID": "c12cdac1-90b6-11e8-2ddf-001bc640cd9b", "name": "Settle and complete service and sales order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.2912023354700115, "y": 0.9069767441860463, "z": -1.97868673615022 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1959", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create iDoc based invoice,\n Forward PDF of invoice to receiving entity ,\n Link the invoice to the outbound delivery,\n Trigger goods issue posting,\n Select appropriate output type for the invoice", "Type": "Business Process", "Description": "This process reflects the triggering of the output message type or labelling the invoicing medium as EDI related. This can usually be maintained during business partner creation.", "Process_Group": "Billing, Rebates and Commissions", "hasAssignment": true, "Scope": "This particularly useful for: ***Intercompany Replenishment ***Sales via Intercompany", "Outcome": "The invoice is generated without errors and the PDF is sent to the receiving entity.", "GUID": "80843c09-9567-11e8-2ddf-001bc640cd9b", "name": "Propagate IC invoice via EDI", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.4213086861457937, "y": 0.9102990033222591, "z": -2.9702691782022224 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1962", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "ATP check for quotation verifies whether goods related to a quotation will be available at the indicated date. The check performed is dependent on the underlying sales scenario, i.e. stocked products, assembly to order, make to order.", "Process_Group": "Pre-order Management", "Scope": "Based on the product and connected sales scenario, the check is performed against stock, production capability or component availability.", "Outcome": "ATP check is performed.", "GUID": "04bcb9d1-2c7f-11ee-3781-0201b014c5b2", "name": "Check availability to promise for quotation", "Business_Rules": "It must be defined: ***How the availability check will be done ***What type of actual stock or planned changes are considered for the availability check ***Whether and how to reserve material / capacity", "Prerequisite": "" }, "position": { "x": -0.5410698604203196, "y": 0.9136212624584719, "z": -3.963236481229039 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1964", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is aims at categorizing and analyzing customers based on various criteria such as demographics, purchasing behavior, or geographic location. The goal is to understand customer segments, tailor marketing strategies, and enhance customer relationship management. Customer segmentation and analysis report assists in tailoring marketing messages, improving customer experiences, and optimizing business strategies based on the identified segments.", "Process_Group": "Sales Reporting and Analytics", "Scope": "This process covers collecting and analyzing customer data to identify patterns and preferences. This may involve factors like purchase history, frequency of transactions, customer feedback, and demographics. The analysis aims to segment customers effectively for targeted marketing and improved customer satisfaction.", "Outcome": "A comprehensive report that outlines customer segments, their characteristics, and behaviors.", "GUID": "47644cb3-5b9e-11ee-3781-0201b014c5b2", "name": "Create customer segmentation and analysis report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.6504750883436292, "y": 0.9169435215946842, "z": -4.957507656014698 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1965", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to analyze the effectiveness of pricing and discount strategies. It aims to evaluate the impact of pricing decisions on sales, revenue, and customer satisfaction. Pricing and discount analysis report assists in making informed decisions about pricing adjustments, discounting policies, and overall revenue optimization.", "Process_Group": "Sales Reporting and Analytics", "Scope": "This process scope includes collecting data on pricing structures, discount levels, and their impact on sales and customer behavior. The analysis may involve comparing pricing strategies over time, assessing competitor pricing, and identifying optimal pricing points.", "Outcome": "A detailed report that provides insights into the performance of pricing and discount strategies.", "GUID": "c510d11c-5b7c-11ee-3781-0201b014c5b2", "name": "Create pricing and discount analysis report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.7495141636248079, "y": 0.9202657807308969, "z": -5.953001639385446 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1966", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is an analysis of all potential sales revenue-generating opportunities. It provides information on how many deals are in sales pipeline, the stage each deal is in, and the value of each deal. By tracking their progress, identifying trends, and making informed decisions it helps a company to optimize its sales processes.", "Process_Group": "Sales Reporting and Analytics", "Scope": "This process involves capturing and analyzing data related to the sales pipeline and ongoing opportunities within a business. This includes aggregating information on potential leads, current opportunities, and the progress of deals through various stages of the sales cycle. The process typically covers aspects such as deal value, probability of closure, key contacts, and expected timelines.", "Outcome": "Both promising and potentially risky sales deals yet to be closed are analyzed and reported.", "GUID": "47644cb1-5b9e-11ee-3781-0201b014c5b2", "name": "Generate sales pipeline and opportunity report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.2394792697447845, "y": 0.9235880398671097, "z": -1.9856106565393188 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1967", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process aims to provide a detailed overview of the sales orders received by a business during a specific timeframe. The primary goal is to analyze and quantify the demand for products or services, track sales performance, and facilitate informed decision-making in areas such as inventory management, production planning, and resource allocation.", "Process_Group": "Sales Reporting and Analytics", "Scope": "This process covers collecting and organizing data related to sales orders, including order numbers, quantities, customer details, and order dates. The scope may extend to analyzing sales order data by product categories, geographical regions, or customer segments, offering a comprehensive view of the businesss sales performance.", "Outcome": "A report that presents a comprehensive analysis of the sales orders received within the specified timeframe. The report contributes to improved sales forecasting, better resource planning, and enhanced responsiveness to customer demand.", "GUID": "60160361-53b7-11ee-3781-0201b014c5b2", "name": "Generate sales order intake report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.3436709445817079, "y": 0.9269102990033224, "z": -2.980250036800657 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1968", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to calculate and analyze the total net sales for a specified period. It provides a comprehensive overview of the revenue generated after deducting returns, discounts, and allowances. Derive total net sales report is crucial for financial analysis, performance evaluation, and strategic decision-making.", "Process_Group": "Sales Reporting and Analytics", "Scope": " This process includes collecting sales data, including gross sales, returns, and discounts. The analysis focuses on deriving the net sales figure, which represents the actual revenue generated by the business.", "Outcome": "A total net sales report that provides a clear and accurate representation of the revenue earned by the business.", "GUID": "6016035d-53b7-11ee-3781-0201b014c5b2", "name": "Derive total net sales report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.4374848335114986, "y": 0.9302325581395348, "z": -3.9760039009597836 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1969", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to analyze sales data related to both customers and products. It aims to understand the performance of different products among various customer segments, identify top-selling items, and optimize product offerings. Customer and product sales analysis report helps in optimizing product portfolios, pricing strategies, and marketing efforts.", "Process_Group": "Sales Reporting and Analytics", "Scope": "Customer and product sales analysis involves collecting and analyzing sales data, including customer purchase history, product sales volumes, and revenue generated by each product. The analysis may extend to identifying cross-selling or upselling opportunities and understanding customer preferences.", "Outcome": "A comprehensive report detailing the sales performance of products among different customer segments.", "GUID": "c510d11a-5b7c-11ee-3781-0201b014c5b2", "name": "Generate customer and product sales analysis report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.5209122832590751, "y": 0.9335548172757475, "z": -4.972791006381609 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1972", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Establish scope and governance,\n Develop budgeting procedures,\n Publish budgeting procedures,\n Monitor budgeting procedures", "Type": "Business Process", "Description": "This process serve as a guideline by developing a framework for rules and regulations regarding budgets. The budgeting process must align with the companys policies and procedures.", "Process_Group": "Financial Planning and Budgeting", "hasAssignment": true, "Scope": "It involves creating a step-by-step process to achieve financial goals and details who, when and how to prepare and implement the budget. The policy is prepared to align with the companys overall strategic objectives.", "Outcome": "A framework or guidelines for preparing budgets is available. It makes the budgeting process less cumbersome.", "GUID": "d563f9f1-a4f3-11ec-4ad5-0201b014c5b2", "name": "Develop and maintain budget policies and procedures", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.5939452059460826, "y": 0.9368770764119603, "z": -5.970530051204303 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1974", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Report audit findings,\n Implement corrective actions,\n Review budget policy,\n Review budgeting process,\n Evaluate execution of budget,\n Record and close audit report", "Type": "Business Process", "Description": "This purpose of this process is to check if allocated funds were or are misappropriated. It also ensures the budget was prepared and executed in line with the companys budget policy.", "Process_Group": "Financial Planning and Budgeting", "hasAssignment": true, "Scope": "Auditing and compliance can be performed by either an internal audit team or an external audit company depending on the companys policy and country-specific regulations. It involves evaluating and analyzing the budget transactions to detect possible anomalies.", "Outcome": "Discrepancies or anomalies are detected and raised for corrective actions to be taken.", "GUID": "052ff019-a505-11ec-4ad5-0201b014c5b2", "name": "Perform auditing and compliance checks", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.18759316556273373, "y": 0.9401993355481726, "z": -1.9911827651509424 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1976", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process focuses on the budgeting of specific controlling objects in an organization. It involves data collection, draft budget preparation, managerial review, and budget allocation, with periodic updates for alignment with organizational goals.", "Process_Group": "Financial Planning and Budgeting", "Scope": "The process involves forecasting expenses, setting budgets, and distributing funds to specific cost objects, to ensure effective utilization and alignment with organizational goals. ", "Outcome": "Planning and budgeting for individual cost objects performed. ", "GUID": "9345f144-56c3-11ee-3781-0201b014c5b2", "name": "Perform non-integrative planning & budgeting of controlling objects", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.26579923044654863, "y": 0.9435215946843853, "z": -2.9882019291028548 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1978", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process focuses on allocating and settling costs related to individual activities within a projects network structure. It starts by accumulating all costs tied to these activities, such as labor and materials. These costs are then allocated to specified receiving accounts like cost centers or internal orders, based on predefined rules. Accounting entries finalize this transfer of costs.", "Process_Group": "Project Accounting", "Scope": "This involves the accumulation, categorization, and allocation of various costs, such as labor, materials, and other expenses, related to the individual activities. Settlement is made to receiving objects such as cost centers or internal orders, based on established rules and criteria. This ensures accuracy and transparency in financial records related to the projects activities", "Outcome": "Costs and expenses incurred in project networks are correctly allocated and settled", "GUID": "9345f146-56c3-11ee-3781-0201b014c5b2", "name": "Settle networks", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.3336019651560376, "y": 0.9468438538205981, "z": -3.986064441130378 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1979", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is designed to accurately allocate costs to projects. It begins by recording all costs associated with specific WBS elements within a project. These costs are then assigned to specific receiving objects, such as cost centers or asset accounts, based on predefined rules. ", "Process_Group": "Project Accounting", "Scope": "At the end of the settlement cycle, settlement run is performed based on settlement and allocation rules to transfer and settle accumulated cost to the final receiving accounts.", "Outcome": "Project costs are settled to final receiving costs and WBS element cost objects are cleared.", "GUID": "9345f14c-56c3-11ee-3781-0201b014c5b2", "name": "Settle WBS elements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.39099483898217907, "y": 0.9501661129568104, "z": -4.984688860489619 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1980", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Define cost receiver,\n Define apportionment rule,\n Define additional settlement parameter,\n Forward cost allocation rules for approval,\n Review cost allocation rules,\n Approve cost allocation for project,\n Reject cost allocation for project", "Type": "Business Process", "Description": "The settlement rule is set up to post to costs. If the proofed requirement to activate the expenditure exists, it is possible to settle to assets under construction.", "Process_Group": "Project Accounting", "hasAssignment": true, "Scope": "Establish the rules for settling collected costs and revenues on a project to one or more receivers. Project revenues and costs are allocated according to settlement rules as part of period-end processing.", "Outcome": "All rules for settling of project revenues and costs are approved.", "GUID": "420f5791-6d90-11e8-2ddf-001bc640cd9b", "name": "Define and approve settlement rules for project", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.43797188796544834, "y": 0.9534883720930232, "z": -5.98399370198131 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1983", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of collecting and analyzing data related to the companys workforce to make data-driven decisions about human resource management and strategy.", "Process_Group": "HR Reporting and Analytics", "Scope": "HR analytics covers all aspects of workforce management such as recruitment, performance management, compensation and benefits, workforce planning, and workforce development.", "Outcome": "Actionable insights that enable organizations to optimize their HR processes and strategies generated.", "GUID": "df8f18e0-5ba6-11ee-3781-0201b014c5b2", "name": "Perform HR analytics", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.13557934719373832, "y": 0.9568106312292359, "z": -1.9953992684709794 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1984", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is gathering and analysing data that provides insights into employees job performance and attendance record. This enables HR management to assess employee productivity, identify areas of improvement, and make data-driven decisions regarding workforce management.", "Process_Group": "HR Reporting and Analytics", "Scope": "The report covers both performance metrics relevant to an employees role or job, the companys goals an attendance records such as working hours and days off", "Outcome": "A comprehensive report that provides insights into the productivity and attendance patterns of employees within a specified timeframe.", "GUID": "47644cd1-5b9e-11ee-3781-0201b014c5b2", "name": "Create employee performance and attendance report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.18774655911871008, "y": 0.9601328903654487, "z": -2.994119441428328 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1985", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is a summary that provides information about the companys payroll activities for a particular period. It is important for maintaining financial records and ensuring compliance with regulatory bodies. ", "Process_Group": "HR Reporting and Analytics", "Scope": "This report provides detailed financial and non financial records of all employees. The necessary data is gathered, calculated and presented in a clear format. ", "Outcome": "Payroll report is generated.", "GUID": "47644ccf-5b9e-11ee-3781-0201b014c5b2", "name": "Generate payroll report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.22949197923147951, "y": 0.963455149501661, "z": -3.993411252484324 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1987", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create dunning proposal,\n Decide about dunning,\n Block customer / item for dunning,\n Clarify delay with customer,\n Unblock customer for dunning,\n Excute dunning run,\n Archive dunning letter and dunning history,\n Create dunning letter,\n Review dunning letter,\n Send dunning letter,\n Close open item and unblock customer", "Type": "Business Process", "Description": "Dunning is performed on a regularly basis in case the customer has not paid on time. The process covers all dunning actions for all dunning levels.", "Process_Group": "Credit Management", "hasAssignment": true, "Scope": "When financial obligations have not been settled by the customer on time, a dunning run is started. Legal actions are taken if necessary. The whole process is closely reconciled with the responsible Sales Department.", "Outcome": "Customer is informed about outstanding payment and legal action is taken where required.", "GUID": "6d268280-723b-11ec-2c3e-001bc641ce4f", "name": "Perform dunning AR", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.26081120383522133, "y": 0.9667774086378738, "z": -4.993193118231461 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1990", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify the VAT code assignment,\n Correct incorrect VAT assignments,\n Apply VAT code assignment", "Type": "Business Process", "Description": "This is a required controlling step to ensure the correct VAT tax code has been applied to the sales order.", "Process_Group": "Tax Accounting", "hasAssignment": true, "Scope": "The process involves a thorough understanding of the jurisdictions VAT regulations applicable to the business operations. This is to determine the appropriate VAT rates to apply for each taxable business transaction. Different goods and services may be subject to different VAT rates, so it is essential to accurately identify the correct rate for each transaction using tax codes.", "Outcome": "VAT on sales order is correct.", "GUID": "5f7265f5-9bc7-11e8-2ddf-001bc640cd9b", "name": "Assign and review appropriate VAT conditions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.2817003969495185, "y": 0.9700996677740865, "z": -5.993383425608483 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1992", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Calculate income tax accrual monthly,\n Finalize annual financial statements,\n Audit financial statements,\n Submit tax reports to authorities,\n Resolve and resubmit tax report,\n Initiate and release payment or confirm tax return,\n Offset tax prepayments against actual tax liability monthly,\n Prepare income tax reports,\n Prepare trade tax reports ", "Type": "Business Process", "Description": "This process ensures the correct income tax amounts is paid to the tax authority for a given period. Income tax include corporate tax. ", "hasAssignment": true, "Process_Group": "Tax Accounting", "Scope": "For month-end closing, income tax accrual is calculated based on profit for the month. After year-end closing is completed, the final tax liability has to be calculated based on the annual reports and reported to the tax authorities.", "Outcome": "Correct income tax to be paid to the tax authority.", "GUID": "16b89b55-d752-11ec-4ad5-0201b014c5b2", "name": "Perform income and trade tax liability", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.08347322585602739, "y": 0.9734219269102988, "z": -1.9982572958868907 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1994", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Calculate withholding tax amount,\n Withhold claculated tax amount from payment,\n Generate withholding tax report,\n Report withholding tax to authorities,\n Pay withholding tax to authorities", "Type": "Business Process", "Description": "This process deals with tax that is charged at the beginning of payment flow but the party who is subjected to tax does not pay the withholding tax to the tax authorities by themselves. When a customer is authorized to deduct withholding taxes from vendors invoice amount, the customer reduces the payment amount by the value of withholding tax. Subsequently, the withheld taxi is transferred to the tax authority by the customer", "Process_Group": "Tax Accounting", "hasAssignment": true, "Scope": "Based on the applicable tax rate on the invoiced amount, the tax amount to be withheld is calculated and paid to the tax authority. A report is generated and filed for future reference.", "Outcome": "Withholding tax to be paid to tax authority declared", "GUID": "3d73b420-2484-11ee-3781-0201b014c5b2", "name": "Execute withholding tax declaration", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.10956606917297623, "y": 0.9767441860465116, "z": -2.9979985451107183 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1996", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Reconcile tax amounts by GL account,\n Revise reconciled transactions ,\n Update the tax reconciliation repository,\n Update compulsory deductions repository,\n Update tax liability record ,\n Update the tax subledger accounts", "Type": "Business Process", "Description": "This process is used for managing information relevant to taxes, for ease of record keeping throughout the year.", "Process_Group": "Tax Accounting", "hasAssignment": true, "Scope": "Tax ledger can include fields for income, deductions, depreciations, payments to tax agencies and other data that may be important for tax accounting.", "Outcome": "Tax ledger maintained and correct.", "GUID": "ad40fc92-6b16-11e8-2ddf-001bc640cd9b", "name": "Manage tax ledger", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.125225754237928, "y": 0.9800664451827243, "z": -3.9980393332826956 }, "color": "#66CCFF", "size": 1.0 }, { "id": "1998", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Specify attributes and parameters for the primary ledger,\n Assign subledgers to the primary ledger,\n Specify reporting guidelines for the subledgers,\n Assign reporting currencies to subledgers,\n Define local GAAP reporting guideline,\n Align and communicate reporting standard,\n Update local GAAP ledger ", "Type": "Business Process", "Description": "This process is used for managing information relevant to local tax accounting standards and regulations.", "Process_Group": "Tax Accounting", "hasAssignment": true, "Scope": "Local GAAP ledger for tax accounting includes fields for income, deductions, depreciations, payments to tax agencies and other data that are set forth by local tax authorities.", "Outcome": "Local tax ledger maintained and correct.", "GUID": "ad40fc94-6b16-11e8-2ddf-001bc640cd9b", "name": "Manage local GAAP ledger", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.13045000736430482, "y": 0.9833887043189367, "z": -4.998297989874018 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2001", "text": "Process", "data": { "Advisory_Notes": "The transfer is to be done using the asset clearing account.", "KeyActivities": "Determine current net book value of asset,\n Record asset retirement,\n Transfer asset value to inventory", "Type": "Business Process", "Description": "Transfer assets to inventory process covers cases where a fixed assets is transferred and managed as inventory.", "hasAssignment": true, "Process_Group": "Asset Accounting", "Scope": "The transfer of asset to inventory is done using the asset clearing account.", "Outcome": "Asset has been transferred to an inventory", "GUID": "d4cc2766-6966-11e8-2ddf-001bc640cd9b", "name": "Transfer asset to inventory", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.1252371231623589, "y": 0.9867109634551494, "z": -5.9986928295239474 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2004", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Analyze data from local payment activities,\n Compare financial transactions with operative payments,\n Calculate currency exposure,\n Collect data on local payment activities,\n Define and initiate further hedging activities,\n Monitor currency risk", "Type": "Business Process", "Description": "Currency risk management ensures effective analysis and hedging of foreign currency risks.", "Process_Group": "Treasury-Risk Management", "hasAssignment": true, "Scope": "Based on data from local payment activities, financial transactions are compared with operative payments. Remaining open items for each currency is calculated as currency exposure, forming the basis for further hedging activities.", "Outcome": "Currency risk is determined, forming the basis for hedging activities.", "GUID": "741518b2-87b8-11e5-0a66-001bc640cd9b", "name": "Manage currency risk", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.03131027560805077, "y": 0.9900332225913622, "z": -1.9997549016420357 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2006", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Determine extent of the loss in asset value due to risk,\n Compare financial transactions with operative payments,\n Take decision on asset,\n Evaluating probability of loss of asset value ,\n Record and communicate decision to keep in spite of risk,\n Initiate sale of asset,\n Initiate asset refurbishment,\n Initiate scrapping of asset", "Type": "Business Process", "Description": "By knowing the risk involved in acquiring or maintaining ownership of a fixed asset, investment strategy can be optimized.", "Process_Group": "Treasury-Risk Management", "hasAssignment": true, "Scope": "This process involves measuring risk stemming from a loss in the value of a fixed asset. By evaluating the probability and extent of the loss in asset value, the decision can be made on whether or not the asset should be kept as part of the organization`s portfolio. Reasons for a loss in asset value may include market conditions, political and environmental developments, accessibility and legal regulations, technological trends.", "Outcome": "Value at risk of a fixed asset is assessed and required actions taken to mitigate the impact.", "GUID": "741518b6-87b8-11e5-0a66-001bc640cd9b", "name": "Manage asset value risk", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.03131098620356386, "y": 0.9933554817275749, "z": -2.9998365992405254 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2008", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The adverse impact of changes in market prices of products and financial instruments on cash flows and net present value of financial instruments needs to be monitored and assessed.", "Process_Group": "Treasury-Risk Management", "Scope": "Based on data from operational and treasury transactions, an analysis is conducted using an appropriate market risk method to determine the potential loss arising from changes in market prices. The degree of potential loss influences the appropriate risk mitigation decisions needed. ", "Outcome": "Market risk is determined and mitigation strategies are implemented.", "GUID": "6fd31456-6f5d-11ee-3781-0201b014c5b2", "name": "Manage market risk", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -0.020874275043677806, "y": 0.9966777408637872, "z": -3.9999455327093396 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2009", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Calculate financial risk per transaction,\n Quantify default risk ,\n Assign risks to affected portfolio segments ,\n Set up and monitor limits for risks", "Type": "Business Process", "Description": "Credit risk management affords the measuring, analysis, and controls of default risks. Default risk implies the potential loss arising from a financial transaction when the business partner fails to fulfill their contractual obligations.", "Process_Group": "Treasury-Risk Management", "hasAssignment": true, "Scope": "Attributable amounts for each single transaction entered is calculated, showing the risk for the respective transaction. Credit and settlement risks are taken into account when quantifying default risk. Default risk is calculated based on counterparties (individual organizations and enterprises) and issuers. The calculated risks are assigned to affected portfolio segments. Risks can be controlled by setting up and monitoring limits.", "Outcome": "Controls for default risk are implemented.", "GUID": "741518b4-87b8-11e5-0a66-001bc640cd9b", "name": "Manage credit risk", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": -9.184850993605148e-16, "y": 1.0, "z": -5.0 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2011", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "In hedge accounting the entries to adjust the fair value of the hedge item which can be an asset, liability, or cash flow and its hedged instrument are treated as one to determine the overall net gain or loss position. The purpose of hedging is to minimize the losses arising from transactions or positions that expose a company to risks such as foreign exchange risk, interest rate risk, liquidity risk, and price risk.", "Process_Group": "Treasury-Risk Management", "Scope": "The hedge item and the hedge instrument must be specified after which the type of hedge is defined. The type of hedge could be fair value, cash flow, or net investment hedge. The type of hedge determines how gains or losses from the hedging relationship are recognised depending on the accounting standards. On an ongoing basis, the effectiveness of the hedging relationship is assessed to estimate the potential gain or loss. On settlement date, the net gain or loss position in the hedging relationship is recognised either in other comprehensive income (OCI) or P&L account.", "Outcome": "Net profit or loss position from hedging is recognised.", "GUID": "6fd3145a-6f5d-11ee-3781-0201b014c5b2", "name": "Perform hedge accounting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.0313114125655145, "y": 1.0033222591362128, "z": -5.999918299064009 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2012", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The adverse impact of changes in interest rates on liquidity and security positions in the financial market needs to be monitored and assessed. When interest rate rises, it can potentially reduce the value of securities portfolio and increase the cost of borrowing funds or debt servicing. Additionally, interest rate risk may arise from a mismatch between interest income and interest expense, it is therefore important that all sources of interest rate risks are identified and assessed.", "Process_Group": "Treasury-Risk Management", "Scope": "It involves identifying the various sources of interest rate risk for each transaction to determine the potential amount of losses. An appropriate mitigation technique such as hedging, portfolio diversification, and duration matching is then implemented to manage the risk. ", "Outcome": "Controls for interest rate risk are implemented.", "GUID": "6fd31458-6f5d-11ee-3781-0201b014c5b2", "name": "Manage interest rate risk", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.02087399080237517, "y": 1.006644518272425, "z": -1.9998910661603502 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2014", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review credit note request,\n Release credit note,\n Communicate with customer about refund ,\n Reject credit note", "Type": "Business Process", "Description": "Once sales has aligned with Accounts Receivable, the release takes place where accounts receivable collects the costs of this warranty claim against the applicable cost center responsible for dealing with quality claims.", "Process_Group": "Accounts Receivable", "hasAssignment": true, "Scope": "The accounts receivable department approves the refund to be given to the customer in the form of a credit note or a reversal of the initial payment. The initial customer order should be connected as a reference to the credit note.", "Outcome": "Credit note is released", "GUID": "bb4dabe1-5dba-11e8-2ddf-001bc640cd9b", "name": "Release credit memo to sales", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.04696541341207505, "y": 1.0099667774086378, "z": -2.9996323524630535 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2016", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Clear customer down payment,\n Reference incoming payment to sales document,\n Monitor that line items are cleared", "Type": "Business Process", "Description": "After final invoice has been issued to the customer the down payment can be cleared with the invoice.", "Process_Group": "Accounts Receivable", "hasAssignment": true, "Scope": "A customer pays an invoice for which a down payment was made. The down payment open item is clear to indicate the payment made.", "Outcome": "Down payment cleared.", "GUID": "ad54682a-7e58-11e5-0a66-001bc640cd9b", "name": "Clear down payment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.08349141544157113, "y": 1.0132890365448506, "z": -3.999128553015965 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2018", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify the dispute case number,\n Specify refunding method ,\n Forward credit note for approval", "Type": "Business Process", "Description": "This reflects a communication flow between Accounts receivable and Sales/ party responsible for issuing the credit note. This is to ensure that the terms and conditions of the warranty have been met before the amounts can be released by accounts receivable.", "Process_Group": "Accounts Receivable", "hasAssignment": true, "Scope": "This process applies to all instances where there is a communication flow between sales and corresponding departments.", "Outcome": "All parties involved are informed and aligned.", "GUID": "e7fef69f-5db5-11e8-2ddf-001bc640cd9b", "name": "Align customer returns with sales staff", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.13045000736430298, "y": 1.0166112956810633, "z": -4.998297989874018 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2021", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Request guarantee from the bank,\n Check formal requirements of guarantee received from the bank,\n Perform statistical guarantee posting,\n Contact bank and resolve anomalies in the guarantee contract,\n Send guarantee to vendor", "Type": "Business Process", "Description": "When a company buys a product, sometimes the seller will demand a guarantee from the company (buyer). Issued by the buyers bank, the bank promises to make full payment to the seller in the event that the company (buyer) defaults and the seller fulfills his or her part of the trade contract with the company. In this process, there are no payments involved.", "Process_Group": "Treasury-Bank Accounting", "hasAssignment": true, "Scope": "After the buyer and vendor have agreed that a guarantee is needed, the buyer requests for the guarantee from its bank. When the bank grants the request, the buyer reviews the bank guarantee for completeness and accuracy. The contract is captured and settled in the buyers system before it is sent to the vendor. ", "Outcome": "Bank guarantee is sent to vendor", "GUID": "3041a275-52da-11ee-3781-0201b014c5b2", "name": "Manage outgoing bank guarantee", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.1878386313568898, "y": 1.0199335548172757, "z": -5.997058999924043 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2023", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check formal requirements of LC,\n Perform statistical letter of credit posting,\n Reject and return LC to importer,\n Send trade documents to importer", "Type": "Business Process", "Description": "In international trade, before a company decides to sell goods to a buyer, sometimes it will demand a letter of credit (LC) from the importer. This secures the exporter against the importers payment default.", "hasAssignment": true, "Process_Group": "Treasury-Bank Accounting", "Scope": "After the exporters bank confirms receipt of the LC from the importers bank, the company must check for completeness in the LC before shipping the goods.", "Outcome": "Letter of credit provided by importer verified and goods are ready to be shipped to importer.", "GUID": "7c709ccb-78b6-11ee-3781-0201b014c5b2", "name": "Manage incoming letter of credit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.07304404611531676, "y": 1.0232558139534884, "z": -1.9986656967404788 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2025", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Request letter of credit from the bank,\n Review letter of credit provided by the bank,\n Perform statistical letter of credit posting,\n Contact bank and resolve anomalies in the letter of credit,\n Inform bank to forward LC to exporters bank", "Type": "Business Process", "Description": "In international trade, sometimes a company importing goods may be required to provide a letter of credit (LC) to the exporter. Issued by the importers bank (issuing bank) to the exporters bank (advising bank) this document guarantees that the importer will make payment on time based on the conditions in the letter of credit such as the exporter must submit all relevant trade documents required by the importer. While it provides financial security to the exporter, it also secures the company (importer) against sub-standard goods or illegal or incomplete custom documents.", "hasAssignment": true, "Process_Group": "Treasury-Bank Accounting", "Scope": "After the importer and exporter have agreed that an LC is needed, the importer requests for the LC from its bank. When the bank grants the request, the importer reviews the LC for completeness and accuracy before his or her bank sends the LC to the exporters bank.", "Outcome": "Letter of credit is sent to exporters bank.", "GUID": "868f3557-78b5-11ee-3781-0201b014c5b2", "name": "Manage outgoing letter of credit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.12520983878403996, "y": 1.0265780730897012, "z": -2.997385943830336 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2027", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Upload electronic bank statement file,\n Post processed bank statement,\n Post outgoing payment,\n Post incoming bank transfer to interim reconciliation account,\n Clear appropriate open item,\n Process the bank statement (L3 task)", "Type": "Business Process", "Description": "Process bank statement process describes the handling of bank statement files including the relevant postings.", "hasAssignment": true, "Process_Group": "Treasury-Bank Accounting", "Scope": "All incoming and outgoing payments are posted to the bank interim accounts and/or to the relevant sub ledger and balance sheet. If the nature of the payment can be defined by a rule, the postings and transactions are done automatically. As soon as all incoming and outgoing payments of the bank statement are posted, the matching items on the bank interim accounts are cleared (on a daily basis).", "Outcome": "All incoming and outgoing payments of the bank statement are posted.", "GUID": "a717a136-d4a8-11eb-2c3e-001bc641ce4f", "name": "Process bank statement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.1878002646330109, "y": 1.0299003322259135, "z": -3.995588950405656 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2029", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check formal requirements of guarantee ,\n Perform statistical guarantee posting,\n Reject and return document to buyer", "Type": "Business Process", "Description": "Before a company decides to sell products to a buyer, sometimes it will demand a guarantee from the buyer as proof that payment will be received from the buyer before shipping the products.", "hasAssignment": true, "Process_Group": "Treasury-Bank Accounting", "Scope": "After sellers bank informs the seller that a bank guarantee is received from the buyer, the seller reviews the contract for completeness and accuracy. If everything is fine with the guarantee, the seller settles the contract.", "Outcome": "Bank guarantee received from buyer is verified and settled.", "GUID": "7cc470d0-78b0-11ee-3781-0201b014c5b2", "name": "Manage incoming bank guarantee", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.2608112038352195, "y": 1.0332225913621262, "z": -4.993193118231462 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2031", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "A company needs to have an overview of the fees it is being charged by all its banks and regularly check if the agreed fees are charged by the banks and take necessary steps to reconcile any discrepancy in order to prevent unwanted financial losses or leakages. Bank fees refer to any fee that a company incurs for using financial services provided by its financial institution(s). These fees such as account maintenance fees, withdrawal and transfer fees, non-sufficient funds fees (NSF), late payment fees, may be one-time or recurring.", "Process_Group": "Treasury-Bank Accounting", "Scope": "All bank service charges stated on the bank statement are checked, reviewed and matched against internal records and agreed contracts to identify and resolve discrepancies.", "Outcome": "Bank fees are verified, reconciled, and settled to the bank.", "GUID": "6c797262-797f-11ee-3781-0201b014c5b2", "name": "Process bank fees", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.34423796884721714, "y": 1.036544850498339, "z": -5.990116878726486 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2033", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that all intercompany transactions related to services and special operations are accurately priced, allocated, and billed, thus offering a true picture of profitability both at the entity and group levels. The key features are: Transaction Oversight, Real-time Data Integration, Consistent Accounting Practices, Cost Allocation, Automated Billing and Reconciliation, Compliance and Auditing and Custom Reports.", "Process_Group": "Intercompany", "Scope": "This process involves creating and implementing standardized protocols and documentation for tracking, verifying, and processing services rendered or special operations conducted between different legal entities within the same corporate group. In addition, clear guidelines for billing, recording transactions, and reconciling accounts to prevent discrepancies should be defined for transparency and accuracy.", "Outcome": "Billing for IC transactions are defined and streamlined enabling efficient group financial reporting.", "GUID": "7b591e3f-56c8-11ee-3781-0201b014c5b2", "name": "Ensure accurate IC billing of services and special operations", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.125164372745806, "y": 1.0398671096345513, "z": -1.9960796276188857 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2034", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process determines the planned prices for materials purchased within the same group. The price is reviewed and adjusted based on factors such as market trends and internal costs. After management approval, the final planned price is integrated into the cost accounting system and serves as a benchmark for budgeting, internal transfer pricing and profitability analyses.", "Process_Group": "Intercompany", "Scope": "This involves establishing planned prices for materials purchased within the same group through the collection, analysis, adjustment, and integration of cost data.", "Outcome": "Planned price for IC purchasing transactions is determined.", "GUID": "9345f140-56c3-11ee-3781-0201b014c5b2", "name": "Determine planned price for material (IC purchased)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.2033690207906064, "y": 1.043189368770764, "z": -2.993098902706469 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2035", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "A process within intercompany relationships that involves the administration and oversight of financial accounts that exist within a single corporate entity to facilitate the movement of funds between various subsidiaries, divisions, or departments. ", "Process_Group": "Intercompany", "Scope": "Internal accounts for each currency is created and all relevant master data maintained. When this is done funds transferred to the respective entities can be easily tracked, monitored, and reported on.", "Outcome": "Funds allocated within corporate group are monitored and properly accounted for.", "GUID": "6fd3145c-6f5d-11ee-3781-0201b014c5b2", "name": "Manage internal bank accounts", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.2919812586436308, "y": 1.0465116279069768, "z": -3.9893291346542066 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2038", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Complete travel request application,\n Approve travel request,\n Perform travel planning and reservations,\n Capture and scan traveling receipts,\n Complete travelling expense report,\n Perform quality check and review,\n Transfer posting to integrated ERP system,\n Reimburse approved employee travel expenses", "Type": "Business Process", "Description": "This process describes the recording of travel activities that can occur when performing a service.", "hasAssignment": true, "Process_Group": "Travel Management Activities", "Scope": "Creation of trips including start and end date of trip, travel expenses, location, finalization of travel activities recording by setting the status to approved and settled, posting travel activities to financial accounting.", "Outcome": "Travel activities recorded and posted to accounting.", "GUID": "84843a3d-7e5b-11e5-0a66-001bc640cd9b", "name": "Record travel activities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.39099483898217724, "y": 1.0498338870431896, "z": -4.984688860489619 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2041", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Review IC purchase info records ,\n Align with supplying entity on price differences ,\n Post invoice to ERP system,\n Block invoice from payment,\n Trigger alignment with IC vendor", "Type": "Business Process", "Description": "This is a check to ensure that the correct pricing conditions have been applied in cases of no transfer to the final customer.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "In addition to verifying correctness of purchasing pricing conditions, the accounts payable clerk ensures that no Value Added Tax has been applied to the invoiced amount.", "Outcome": "All IC purchase price conditions are correct.", "GUID": "80843c11-9567-11e8-2ddf-001bc640cd9b", "name": "Review IC purchasing pricing conditions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.5004029477340542, "y": 1.053156146179402, "z": -5.979096661695567 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2043", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Check down payment invoice,\n Check whether guarantee is needed,\n Verify requirement of approval of down payment,\n Receive guarantee,\n Contact requestor to verify down payment invoice,\n Approve invoice,\n Release down payment request for payment,\n Post down payment", "Type": "Business Process", "Description": "The down payment process in Accounts Payable describes the handling, validation and execution of a down payment. In addition, guarantees from vendors are also taken into account.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "This process is triggered when a down payment invoice is received. It begins by reviewing the down payment invoice and determining whether a guarantee is required. This is followed by an approval and release of the down payment. Subsequently, the down payment is posted.", "Outcome": "Down payment request posted and ready for payment", "GUID": "0b62f540-457c-11ee-3781-0201b014c5b2", "name": "Conduct down payment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.177199486964365, "y": 1.0564784053156147, "z": -1.9921346194019032 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2045", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter parameters for dunning run,\n Create dunning proposal,\n Check open items,\n Determine appropriate level of dunning,\n Create dunning proposal list,\n Print dunning notice,\n Edit dunning proposal list,\n Send dunning notice to vendor", "Type": "Business Process", "Description": "Vendor dunning refers to the process of engaging the vendor on his/her outstanding reimbursement of funds or goods supply. It is the process whereby correspondence with a companys suppliers is made about suppliers open items, e.g., pending bills.", "Process_Group": "Accounts Payable", "hasAssignment": true, "Scope": "When credit memo obligations have not been settled by the vendor on time, a dunning run is started. Legal actions are taken if necessary. The whole process is closely reconciled with the responsible Purchasing Department.", "Outcome": "Vendor is informed about outstanding payment and legal action is taken where required.", "GUID": "373b5b10-dac6-11ed-3781-0201b014c5b2", "name": "Perform vendor dunning AP", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.2813897483440995, "y": 1.0598006644518274, "z": -2.986774147726414 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2047", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Confirm STO quantities,\n Analyse quantity differences between goods receipt/ invoice receipt,\n Confirm invoice against GR ,\n Block invoice from payment,\n Post verified IC invoice to ERP system,\n Trigger alignment with IC vendor ", "Type": "Business Process", "Description": "This process ensures that no quantity differences outside of the defined tolerance have occured which is often the prerequisite to ensure that all risks related to differences in physical inventory and transit stock have been identified and mitigated.", "hasAssignment": true, "Process_Group": "Accounts Payable", "Scope": "Inter-company invoices transferred via EDI are verified for consistency against the goods received.", "Outcome": "The goods receipt quantities and the amounts billed correspond or fall within an agreed tolerance limit.", "GUID": "80843c0f-9567-11e8-2ddf-001bc640cd9b", "name": "Execute IC invoice verification", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.39596347063072024, "y": 1.0631229235880397, "z": -3.980353367469536 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2050", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Generate GL account report,\n Verify account balances,\n Clarify discrepancies,\n Post discrepancies to P&L and balance sheet", "Type": "Business Process", "Description": "This process describes the reconciliation of GL accounts and the clarification of provisions, accruals and other accounts in order to establish a sound trading, profit and loss account and balance sheet.", "Process_Group": "General Ledger", "hasAssignment": true, "Scope": "In this process, the GL account report is created, account balances are checked and discrepancies are posted to P&L or balance sheet.", "Outcome": "Balance sheet and P&L are reconciled.", "GUID": "9b6dd8cd-63e8-11e8-2ddf-001bc640cd9b", "name": "Reconcile GL accounts", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.5209122832590733, "y": 1.0664451827242525, "z": -4.972791006381609 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2052", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Verify completeness of data,\n Access current exchange rates,\n Upload current exchange rates", "Type": "Business Process", "Description": "This process is used for managing currency rate information.", "Process_Group": "General Ledger", "hasAssignment": true, "Scope": "Current currency exchange rates are updated in the system on a daily/weekly/monthly basis Preferably it is established using interfaces with a bank.", "Outcome": "Current exchange rates are available and maybe used for P&L and further analysis to evaluate currency effects.", "GUID": "9b6dd8cb-63e8-11e8-2ddf-001bc640cd9b", "name": "Import current exchange rates", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.6562272502672457, "y": 1.0697674418604652, "z": -5.964005851439675 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2054", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Clear open item managed accounts,\n Analyze postings,\n Confirm matching of items,\n Change assignments ,\n Conduct manual postings", "Type": "Business Process", "Description": "Maintain open item managed accounts process covers the continuous clearing of open item managed accounts by clearing jobs as well as the follow up of items, which could not be cleared automatically.", "Process_Group": "General Ledger", "hasAssignment": true, "Scope": "Automatic clearing job is started for open item/managed accounts. In case items could not be cleared automatically, the accounts must be cleared manually. Conditions for automatic postings: ***balance in tolerance ***trading partner correct ***assignment correct Zero balance accounts and accounts with balance within tolerance will be cleared automatically.", "Outcome": "Open item managed accounts cleared.", "GUID": "9b6dd8c9-63e8-11e8-2ddf-001bc640cd9b", "name": "Maintain open item managed accounts", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.22911396305447118, "y": 1.0730897009966776, "z": -1.9868333578671047 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2056", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Enter cash journal entries,\n Save cash journal entries,\n Enter company code and cash journal number,\n Post cash journal entries,\n Display follow-on documents,\n Delete cash journal entries saved,\n Print cash journal entries,\n Print receipts,\n Display all deleted cash journal documents,\n Change cash journal", "Type": "Business Process", "Description": "This is the process of accurately recording, tracking, and reconciling all cash transactions recorded in the Cash journal. It ensures complete and accurate records of all cash receipt and cash payment transactions.", "Process_Group": "General Ledger", "hasAssignment": true, "Scope": "The cash book can be used independently of other posting transactions and amounts can be entered in different currencies. It calculates the cash balance of the company after each cash receipt or payment is posted and allows the user to print a cash journal document.", "Outcome": "Saved cash journal entries posted to G/L account (e.g., at the end of a working day). Printing of saved cash journal entries also possible.", "GUID": "373b5b12-dac6-11ed-3781-0201b014c5b2", "name": "Manage cash journal", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.35921890461717565, "y": 1.0764119601328903, "z": -2.9784159848089784 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2058", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Display accounts list,\n Enter journal code,\n Add description,\n Set appropriate approval dept,\n Enter all applicable lines,\n Set post date,\n Save balanced entry,\n Approve manual journal entry,\n Post manual journal entry,\n Rework manual posting", "Type": "Business Process", "Description": "Manual journal entries are used to enter corrections in the ledgers to add or correct data.", "Process_Group": "General Ledger", "hasAssignment": true, "Scope": "If a manual journal entry is required, the accounts list will be displayed first, then the journal code must be entered, a description must be added, a posting date and an appropriate approval dept must be specified. After all the applicable lines have been entered, the balanced entry must be saved and the manual journal entry approved. If the journal entry is approved, the manual journal entry can be posted. If it is not approved, the manual journal entry must be reworked, saved and approved.", "Outcome": "Manual posting approved and posted to G/L", "GUID": "373b5b14-dac6-11ed-3781-0201b014c5b2", "name": "Perform manual postings", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.49967610908320387, "y": 1.079734219269103, "z": -3.9686677595902973 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2061", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process aims to set product or service prices that cover all costs and ensure that no losses are incurred. The process involves reviewing all production costs to calculate a break-even price and then takes into account the targeted profit margins to arrive at a coverage price. This price is adjusted to market conditions and, once approved by management, is integrated into the cost accounting system for future financial planning and profitability analysis.", "Process_Group": "Product Cost Controlling", "Scope": "The scope of this process extends across the entire product cost structure, encompassing both variable and fixed costs. It involves a comprehensive examination of all cost elements associated with the production, distribution, and sale of a product. The analysis considers factors such as raw material costs, direct labor expenses, manufacturing overhead, and other associated operational costs.", "Outcome": "Pricing model that ensures financial viability is established.", "GUID": "9345f137-56c3-11ee-3781-0201b014c5b2", "name": "Determine loss-free or coverage prices", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.6504750883436273, "y": 1.0830564784053158, "z": -4.957507656014698 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2062", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Determine the market value ,\n Update material master data", "Type": "Business Process", "Description": "The goal of this process is to determine the evaluation method and market price required for conducting inventory valuation.", "Process_Group": "Product Cost Controlling", "hasAssignment": true, "Scope": "Identify the market value and update in material master data.", "Outcome": "Evaluation method for inventory valuation is determined", "GUID": "d30a0f10-e7c8-11ec-4ad5-0201b014c5b2", "name": "Determine evaluation method for inventory valuation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.8116047906304772, "y": 1.0863787375415281, "z": -5.9448547218435595 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2064", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process assesses the value of inventory by comparing its actual cost to the current market price. The lower value between the two is identified and recorded in the accounting system after managerial approval. This process ensures compliance with accounting standards and provides a conservative and accurate basis for financial reporting and analysis.", "Process_Group": "Product Cost Controlling", "Scope": "This process involves an analysis of various aspects such as purchase cost, current market value, potential obsolescence, damage, shifts in market demand, and any factors that could impact the value of the inventory. This evaluation considers external market conditions, internal inventory management practices, and regulatory requirements to ascertain the most accurate valuation for financial reporting purposes.", "Outcome": "Price required to perform inventory valuation is determined.", "GUID": "9345f139-56c3-11ee-3781-0201b014c5b2", "name": "Determine lower cost or market price", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.2808724574305284, "y": 1.089700996677741, "z": -1.980179452134815 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2065", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process deals with determination and allocation of tariffs and trade-related costs. It includes importing essential data such as trade laws and exchange rates, setting up tariff structures, and automatically validating compliance. The calculated tariffs are allocated to the appropriate cost centers or products.", "Process_Group": "Product Cost Controlling", "Scope": "This process typically covers analyzing international trade regulations, identifying applicable tariffs based on the products classification and origin, and integrating these costs into the products pricing structure.", "Outcome": "Additional costs related to domestic or international trade activities which impact production cost or sales cost are determined.", "GUID": "9345f153-56c3-11ee-3781-0201b014c5b2", "name": "Calculate tariffs", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.43680350320501615, "y": 1.0930232558139537, "z": -2.9680301042253303 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2066", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process for third-party purchases in cost accounting encompasses the collection of vendor and material data and the identification of various cost elements like purchase price and transportation costs to perform an initial cost calculation. This is refined by market trends and adjustment factors like discounts. After managerial review and approval, the final planned price is integrated into the cost accounting system for future financial planning, helping the organization make informed budgeting decisions and optimize profitability.", "Process_Group": "Product Cost Controlling", "Scope": "This process involves analyzing various factors, such as supplier quotes, market conditions, historical pricing data, and any relevant contractual agreements. In case new vendors are required, market analysis is required to identify reliable suppliers, negotiating prices, considering quality standards, and factoring in potential fluctuations in market rates. ", "Outcome": "Price for externally procured materials are predetermined.", "GUID": "9345f142-56c3-11ee-3781-0201b014c5b2", "name": "Determine planned price for material (third party purchased)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.6030485660167322, "y": 1.096345514950166, "z": -3.954280266625668 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2067", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Perform stock entry,\n Perform inventory valuation based on BOM and Routings ", "Type": "Business Process", "Description": "This purpose of this process is to revalue the inventory. Revaluation means determining the market value of the inventory item.", "hasAssignment": true, "Process_Group": "Product Cost Controlling", "Scope": "In this process the inventory items will be evaluated with the values required for different reporting purposes. For example, HGB, companies must report lower values while for IFRS companies report higher values between production and market.", "Outcome": "The value of the inventory has been recalculated in line with reporting requirements.", "GUID": "5dca9060-d74e-11ec-4ad5-0201b014c5b2", "name": "Conduct inventory valuation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.7795950473533575, "y": 1.0996677740863787, "z": -4.93884921435572 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2069", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves the collection and calculation of various cost components related to material production or procurement. Essential data such as raw materials, labor, and overhead is integrated into the system and a detailed cost calculation is carried out to create a comprehensive cost structure.", "Process_Group": "Product Cost Controlling", "Scope": "This process typically includes determining material prices, quantities needed, supplier costs, transportation fees, and any additional expenses related to material acquisition. For accurate material costing, factors like quality, quantity discounts, and potential fluctuations in prices need to be considered.", "Outcome": "Cost of direct materials are determined", "GUID": "9345f13b-56c3-11ee-3781-0201b014c5b2", "name": "Conduct material costing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9664297871649292, "y": 1.1029900332225915, "z": -5.921656311073816 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2071", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Gather employees feedback on implemented change,\n Analyze employees feedback on implemented change ,\n Identify issues,\n Select appropriate follow-up actions,\n Report change acceptance to stakeholders", "Type": "Business Process", "Description": "This process is concerned with monitoring employees acceptance of implemented change.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Gathering and evaluating employee feedback on implemented change, identifying issues, selecting appropriate follow-up actions and reporting.", "Outcome": "Change acceptance monitored.", "GUID": "59b1bf6a-61b5-11ee-3781-0201b014c5b2", "name": "Monitor change acceptance", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.33243973269992316, "y": 1.1063122923588038, "z": -1.9721774322110077 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2073", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Celebrate successes,\n Reinforce change,\n Transfer ownership of the change to operational managers,\n Share success stories from change implementation", "Type": "Business Process", "Description": "This step helps identifying and celebrating successes on the project. Use these celebrations and public acknowledgement to reinforce the change. Constantly seek evidence of major milestones and identify early successes even if small.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Clebrate successes and reinforce the change and transfer ownership of the change to operational managers.", "Outcome": "Success recognized and change reinforced.", "GUID": "81ef94d7-e10c-11e9-0cfc-001bc641ce4f", "name": "Recognize success and reinforce change", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.5140907241986437, "y": 1.1096345514950166, "z": -2.9556235767250394 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2075", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Prepare communication plan,\n Request approval for communication plan,\n Prepare communication materials,\n Review feedback on communication plan,\n Update communication plan,\n Communicate change vision and roadmap to employees,\n Clarify concerns ,\n Make sure employees properly understand the change vision", "Type": "Business Process", "Description": "This process describes conveying the details and significance of a planned organizational change to all employees effectively.", "Process_Group": "Employee communication", "hasAssignment": true, "Scope": "Preparing and approving communication plan, preparing communication material, communicating change vision and roadmap to customers in planned manner and clarifying any potential misunderstandings or concerns. ", "Outcome": "Change vision and roadmap communicated to employees.", "GUID": "59b17140-61b5-11ee-3781-0201b014c5b2", "name": "Communicate change vision and roadmap to employees", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.7060104650439363, "y": 1.1129568106312293, "z": -3.9372006836391313 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2077", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Identify need for employee transition,\n Review list of potential successors,\n Align with successor on employee transition,\n Request approval for employee transition,\n Report inability to identify suitable successor,\n Report rejection of employee transition,\n Identify need for employee hiring", "Type": "Business Process", "Description": "When employee succession is needed (employee on the position in question left the position of company), transition of the successor must be approved.", "Process_Group": "Human Resource Development", "hasAssignment": true, "Scope": "Identifying need for employee transition, reviewing successors for the critical position, identifying most suitable successor, approving transition of this successor, and aligning with employee on transition.", "Outcome": "Employee transition approved.", "GUID": "79ad6deb-329c-11ee-3781-0201b014c5b2", "name": "Request approval for employee transition", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9081842548971835, "y": 1.116279069767442, "z": -4.916828384147331 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2079", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that permission is given by the works council for hiring an employee. ", "Process_Group": "Employee communication", "Scope": "During the hiring process the works council must be informed, consulted or approve certain steps as provided for by law.", "Outcome": "Works council approves or rejects new employee hire.", "GUID": "b8af5678-f569-11e8-2ddf-001bc640cd9b", "name": "Conduct works council approval", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1205968343858594, "y": 1.1196013289036544, "z": -5.89442641270246 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2080", "text": "Process", "data": { "Advisory_Notes": "Choosing the appropriate time recording method depends on organizational needs, employee roles, and the level of detail required for tracking work-related time. Each method offers a unique perspective, enabling businesses to efficiently manage attendance, work deviations, and compensation based on their specific requirements.", "Type": "Business Process", "Description": "The process of determining a time recording method describes selecting the most suitable approach for capturing and managing employees work hours. Various methods, such as positive time recording (employees document all work aspects for a comprehensive overview), overtime recording (employees log extra hours for a specific analysis), negative time recording (employees note deviations for overall recorded time), and absences-only time recording (employees record only absences, useful for fixed compensation roles like executives, without tracking or compensating for overtime), offer different perspectives on tracking time-related activities. ", "Process_Group": "Employee Reward and Retention", "Scope": "Reviewing organizational needs and roles, assessing different time recording methods, selecting appropriate time recording methods for job roles.", "Outcome": "Time recording methods selected.", "GUID": "d04c6d60-83ab-11ee-3781-0201b014c5b2", "name": "Determine time recording method", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.38378068165278434, "y": 1.1229235880398671, "z": -1.9628327459032582 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2082", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Define criteria for selection,\n Determine options for treasury risk management,\n Evaluate financial instruments,\n Select financial instruments to manage treasury risk", "Type": "Business Process", "Description": "Financial instruments are contracts that give rise to a financial asset of one entity and a financial liability or equity instrument of another entity. The appropriate financial instrument must be selected, representing a legally binding agreement for fulfillment of an obligation arising from a transaction.", "hasAssignment": true, "Process_Group": "Treasury-Financial Instruments", "Scope": "Financial instruments are selected according to various criteria, taking underlying transactions (existing and future) into account. Financial instruments used for Treasury Risk Management can include: * Forward exchange transactions * Currency options * Bonds * Loans * Interest rate guarantees * Interest rate swaps * Futures * Bond options * Options on futures", "Outcome": "Financial instruments are selected.", "GUID": "741518ae-87b8-11e5-0a66-001bc640cd9b", "name": "Select financial instruments", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.5910279501449702, "y": 1.12624584717608, "z": -2.9412048487222773 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2084", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This involves monitoring and evaluating the companys net market position in the money market, capital market, or stock market to gain a clear understanding of its investments and borrowings in each market. This is important for effective asset and liability management and ensuring the company has sufficient funds to meet its financial obligations.", "Process_Group": "Treasury-Financial Instruments", "Scope": "By identifying the product types, transaction types and value types, the total value of investments is nett-off against the total value of borrowings to determine the net market exposure.", "Outcome": "Net position in each financial market is determined and made available for financial decisions. ", "GUID": "0b751490-539c-11ee-3781-0201b014c5b2", "name": "Manage securities position", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.8084917092869189, "y": 1.1295681063122922, "z": -3.917440638479965 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2085", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "At the end of each day, the closing account balance of each foreign currency held by the company should be recorded and posted to the relevant accounts. This is because its daily FX transactions and exchange rate volatilities have significant impact on its FX account balances and overall financial health. By recording the daily account balances, it enables the company to minimize risks, control costs by deciding whether to go long (buy) or short (sell) on each foreign currency.", "Process_Group": "Treasury-Financial Instruments", "Scope": "It involves the use of both quantitative and qualitative data. Quantitative data covers determining foreign currency exposure arising from both operational and treasury trading activities and revaluating FX account balances using current exchange rates while qualitative data covers economic, political, or behavioural factors that can impact exchange rate movements. ", "Outcome": "Long or short position of each foreign currency is determined.", "GUID": "09a9f990-7990-11ee-3781-0201b014c5b2", "name": "Manage foreign currency position", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.0361551669217681, "y": 1.132890365448505, "z": -4.891460157259928 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2086", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Every financial security traded in the money market, capital market, or stock market has its own characteristics. This includes the type, settlement date, interest day basis, timing of interest payments and dividend payments, and tax requirements. Each of the securities issued or bought needs to have its own account to ensure settlement and postings arising from either trading activities or holding securities until maturity are made to the right account.", "Process_Group": "Treasury-Financial Instruments", "Scope": "The security nomenclature is used to create the security account after which the right class, and all relevant parameters are assigned to the account. To ensure correctness, it is reviewed and authorized and finally it is closed when the security matures.", "Outcome": "Securities accounts maintained.", "GUID": "6fd31451-6f5d-11ee-3781-0201b014c5b2", "name": "Maintain securities accounts", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.2740009747430827, "y": 1.1362126245847177, "z": -5.863183564954595 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2087", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "After an agreement has been reached with the counterparty, the details of the trade is captured. This enables the treasury team to track, monitor, and manage the deal until it is settled including its impact on the companys liquidity.", "Process_Group": "Treasury-Financial Instruments", "Scope": "The trader in front office records the details of the trade. Details of the trade captures information such as counterparty, product type, transaction type which is either a purchase or sale, and settlement date. ", "Outcome": "Trade deal agreement is captured.", "GUID": "6c797264-797f-11ee-3781-0201b014c5b2", "name": "Create trade deal", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.43486035116311217, "y": 1.13953488372093, "z": -1.9521517551118548 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2089", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process captures and allocates costs related to sales and distribution orders. It compiles costs like materials, labor, and overhead, calculates the total for each order, and then distributes these costs to the relevant financial accounts.", "Process_Group": "Overhead Cost Controlling", "Scope": "Settling SD orders for the purpose of cost controlling involves reviewing, verifying, and reconciling costs incurred throughout the SD order lifecycle, ensuring accuracy and adherence to budgetary constraints or predetermined cost targets.", "Outcome": "All costs related sales and distribution are settled", "GUID": "9345f14a-56c3-11ee-3781-0201b014c5b2", "name": "Settle SD orders", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.6675628018689427, "y": 1.1428571428571428, "z": -2.924783736545471 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2090", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process deals with allocating and reporting on costs and revenues linked to customer service operations. ", "Process_Group": "Overhead Cost Controlling", "Scope": "Ctegorize expenditures like labor, materials, and overheads and assigns them to appropriate accounting structures.", "Outcome": "Service orders are settled to the correct in accounting period", "GUID": "60160342-53b7-11ee-3781-0201b014c5b2", "name": "Settle service orders", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9104225290995103, "y": 1.1461794019933556, "z": -3.8950135838669486 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2091", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The process is designed to allocate and finalize costs linked to a particular project, task, or activity within an organization.", "Process_Group": "Overhead Cost Controlling", "Scope": "The process begins by gathering all costs related to an internal order, such as labor and materials. These costs are then allocated to designated receiving accounts, like permanent cost centers or asset accounts, based on pre-established rules. Accounting entries are made to complete the transfer, effectively zeroing out the internal orders cost balance.", "Outcome": "Internal order is settled to correct cost object.", "GUID": "60160344-53b7-11ee-3781-0201b014c5b2", "name": "Settle internal order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.163420660311886, "y": 1.1495016611295683, "z": -4.862761804485128 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2093", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Record payment inflows,\n Record payment outflows,\n Determine payments due ,\n Determine current cash position", "Type": "Business Process", "Description": "Cash Management ensures that sufficient liquidity is available for making payments. Moreover, monitoring of payment flows affords an overview of cash positions and short-term liquidity on a group or/and individual legal entity level.", "Process_Group": "Treasury-Cash and Liquidity Management", "hasAssignment": true, "Scope": "Payment inflows and outflows of various accounts are recorded and monitored. Source of payments can include, Manual/electronic bank statement, Manual/electronic check deposit, and Bill of exchange. The core records of payment inflows and outflows are based on the concentration strategy defined in advance (e.g. cash pooling: combining credit and debit positions of various accounts into one account). The result of the cash concentration is output in form of payment orders. The payments due form the basis for determining the current cash position.", "Outcome": "Information is available regarding the current cash position of the organization.", "GUID": "741518a2-87b8-11e5-0a66-001bc640cd9b", "name": "Conduct cash management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.4265377700764914, "y": 1.1528239202657806, "z": -5.827949038087515 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2095", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Plan expected incoming cash flows,\n Plan expected outgoing cash flows,\n Specify cash required to fund future business operations ,\n Review business plan,\n Review incoming and outgoing postings from pervious periods,\n Report cash budget for given period", "Type": "Business Process", "Description": "The manage cash budget process has the goal of monitoring and securing liquidity in the medium to long term. This delivers the actual and target figures for reviewing plans, analyzing deviations and form the basis for future planning.", "Process_Group": "Treasury-Cash and Liquidity Management", "hasAssignment": true, "Scope": "Planning of expected incoming and outgoing flows (for exact periods /typically weeks or months) is conducted. The planned items indicate the source of incoming payments and purpose of outgoing payments, which results in the cash required to fund future business operations. The relevant data is derived from the business plan and postings from previous periods.", "Outcome": "The funds required for payment at the beginning and remaining expected cash at the end of a period are determined.", "GUID": "741518ac-87b8-11e5-0a66-001bc640cd9b", "name": "Manage cash budget", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.4856439659850164, "y": 1.1561461794019934, "z": -1.9401417314985894 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2097", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Capture debt and investment transactions,\n Ensure completeness and correctness of data,\n Forward relevant details to cash management,\n Forward relevant details to financial market risk management,\n Specify effect of debts and investments on liquidity,\n Define follow-up action to hedge loans risk", "Type": "Business Process", "Description": "The is the process of planning and monitoring both debt and investment transactions in order to reduce debt burden and optimize investment returns. This ensures adequate documentation and coordination of debt and investment transactions at all stages and it also takes into account lending/borrowing between entities of the same group to level uneven cash demands.", "Process_Group": "Treasury-Cash and Liquidity Management", "hasAssignment": true, "Scope": "Debt and investment transactions are executed based on standardized procedures, with timely accessing and processing of relevant information. Integration of debt and investment management with cash management and market risk management, allows transparency on the effect of respective transactions on liquidity, and the exposure to currency risks and interest rate risk.", "Outcome": "The effect of debt and investment transactions on liquidity is assessed and made available for liquidity planning", "GUID": "741518a8-87b8-11e5-0a66-001bc640cd9b", "name": "Execute debt and investment management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.7436431741335113, "y": 1.1594684385382061, "z": -2.906371419754302 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2099", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of creating a cash flow forecast for the short to medium term period to ensure the company has enough cash to meet its short-term obligations. ", "Process_Group": "Treasury-Cash and Liquidity Management", "Scope": "Based on expected cash outflows from accounts payable and cash inflow from accounts receivable, statistical forecast is performed to predict the future cash flows. After analyzing the forecast, if there is a potential liquidity shortfall, appropriate actions to secure additional funding are determined.", "Outcome": "Future cash flow is predicted and necessary actions are taken to cover liquidity shortfalls.", "GUID": "6fd2ed40-6f5d-11ee-3781-0201b014c5b2", "name": "Conduct liquidity planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.0117335295667218, "y": 1.1627906976744184, "z": -3.8699347882297013 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2100", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Capture financial transactions in treasury management system ,\n Analyze current liquidity ,\n Analyze risk situation,\n Decide future investments and borrowings,\n Communicate decision to stakeholder", "Type": "Business Process", "Description": "This process provides support for managing financial transactions and positions from the trading stage through to the transfer to Financial Accounting. Treasury management affords flexible reporting and evaluation structures for analyzing financial transactions, positions and portfolios of financial assets and fixed assets.", "Process_Group": "Treasury-Cash and Liquidity Management", "hasAssignment": true, "Scope": "Financial transactions are entered in treasury management. With analyses of the current liquidity and risk situation, decisions are made on future investments and borrowings.", "Outcome": "Records of financial transactions are available and analyzed for decision making on future investments and borrowings.", "GUID": "741518a6-87b8-11e5-0a66-001bc640cd9b", "name": "Perform treasury management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.2898940922041444, "y": 1.1661129568106312, "z": -4.830752863777741 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2103", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This refers to generating a financial report that provides detailed information about cost of asset maintenance and how efficiently assets are used to generate revenue or achieve specific goals. It helps management to make good capital investment decisions. ", "Process_Group": "Finance Reporting and Analytics", "Scope": "This report outlines all the activities, time, and cost associated with asset maintenance and actual utilization. It involves careful consideration of all factors that impact the actual utilization of an asset. Some of these factors are maintenance, repairs, rest periods, breakdowns, and changeovers.", "Outcome": "Asset utilization ratios and cost of asset maintenance are reported", "GUID": "47644caf-5b9e-11ee-3781-0201b014c5b2", "name": "Create asset maintenance and utilization report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5781033727180043, "y": 1.169435215946844, "z": -5.788746819909821 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2104", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process provides insights into all outstanding receivables from customers by providing information on the value and length of time payments from customers remain unpaid. Outstanding payments from customers can disrupt a companys cash flow, therefore it is important for a company to periodically review all outstanding payments from customers in order to take appropriate measures. This can also be an input for assessing the effectiveness of its credit management processes.", "Process_Group": "Finance Reporting and Analytics", "Scope": "The report is generated based on certain criteria that align with the business needs. Typically this includes the need to specify whether to group the report by customer or sales employee, aging date, interval, and currency conversions.", "Outcome": "Value of customer debts and the length of time the debts have remained unpaid are determined.", "GUID": "936e0cf0-903a-11ee-3781-0201b014c5b2", "name": "Generate accounts receivable aging report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.5360969524278258, "y": 1.1727574750830563, "z": -1.9268108515361848 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2105", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This refers to the process of creating a report that outlines the depreciation of a companys assets over a specific period. Asset depreciation is a non-cash expense that shows the gradual reduction in the value of assets over time. This report helps management and stakeholders to assess the impact of asset depreciation on the companys financial health", "Process_Group": "Finance Reporting and Analytics", "Scope": "This involves defining and using a depreciation method which specifies how depreciation expenses are calculated and allocated over the useful period of the asset. After the figures are validated and approved, they are reported in the expense section of P&L statement because it reduces the operating profit of the company. ", "Outcome": "The net book value of the asset is reported.", "GUID": "47644cad-5b9e-11ee-3781-0201b014c5b2", "name": "Generate asset depreciation report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.8192172711130831, "y": 1.176079734219269, "z": -2.8859804335286183 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2106", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process provides insight into how much a company owes its trade creditors and when payments are due or past due. ", "Process_Group": "Finance Reporting and Analytics", "Scope": "The report is generated based on certain criteria that align with the business needs. Typically this includes the need to specify whether to group the report by vendor, or company code, aging date, interval, and currency conversions.", "Outcome": "Value of vendor debts and the length of time the debts have remained unpaid are determined.", "GUID": "936e3401-903a-11ee-3781-0201b014c5b2", "name": "Generate accounts payable aging report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1123557377490865, "y": 1.1794019933554818, "z": -3.8422213253138717 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2107", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "In performing project cost and accountability reporting, costs, revenue and overall profitability of a project are tracked and analyzed. This process is important for ensuring that projects are financially viable and that resources are allocated efficiently.", "Process_Group": "Finance Reporting and Analytics", "Scope": "All costs and revenues associated with a project are recorded and allocated to the right cost / profit centers. The profitability is determined by comparing total revenue to total cost.", "Outcome": "Net profit or loss figures of a project are determined and reported.", "GUID": "47644cb5-5b9e-11ee-3781-0201b014c5b2", "name": "Perform project cost and profitability reporting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.4154893589738613, "y": 1.1827242524916945, "z": -4.795455126954246 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2108", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process gathers and analyzes data on internal cross-border transactions to evaluate profitability and tax implications, aiding in compliance and strategic planning.", "Process_Group": "Finance Reporting and Analytics", "Scope": "The transfer price report outlines the prices at which goods, services, or assets are transferred between different departments, divisions, or subsidiaries within a company, especially in a multi-entity organization.", "Outcome": "Transfer price report is available for analysis.", "GUID": "60160365-53b7-11ee-3781-0201b014c5b2", "name": "Create transfer price report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7285945961914222, "y": 1.1860465116279069, "z": -5.745603599450437 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2109", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Perform cost of sales analysis per line item ,\n Define scope of analysis", "Type": "Business Process", "Description": "Controlling process to evaluate the cost of sales on line items level.", "Process_Group": "Finance Reporting and Analytics", "hasAssignment": true, "Scope": "Line items within the Trading, Profit and Loss account in addition to Balance sheet line items can be assessed, analysed and evaluated by management so that potential corrective action can be triggered if necessary.", "Outcome": "Cost of sales figures available for a specified period.", "GUID": "fccd2e59-9569-11e8-2ddf-001bc640cd9b", "name": "Perform cost of sales analysis on line items", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.5861849618940228, "y": 1.1893687707641196, "z": -1.912168190941713 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2111", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Perform profit and loss analysis by strategic BU ,\n Perform profit and loss analysis by selling entity ,\n Perform profit and loss analysis by profit center ", "Type": "Business Process", "Description": "Process to assist management in understanding the qualitative reasoning behind variances so that corrective action can be triggered.", "Process_Group": "Finance Reporting and Analytics", "hasAssignment": true, "Scope": "Perform plan / actual variance analysis process evaluating the qualitative reasoning behind variances. This is often used as performance indicator in production, purchasing and overhead budgetary control. Based on the analysis corrective actions are triggered.", "Outcome": "Variances between planned and actual order determined and reasons for variances captured.", "GUID": "fccd2e5b-9569-11e8-2ddf-001bc640cd9b", "name": "Perform plan actual variance analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.8942336416563295, "y": 1.1926910299003324, "z": -2.8636246601344353 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2113", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The consolidated cash flow statement provides a summary of the cash inflows and outflows of the parent company and the subsidiary(ies) as a single entity as at a particular reporting date.", "Process_Group": "Finance Reporting and Analytics", "Scope": "It involves combining the cash flows of the parent company and its subsidiaries while accounting for intercompany or intragroup transactions and eliminating double counting.", "Outcome": "The aggregated value of cash flows for the reporting period is computed.", "GUID": "9d864d81-6824-11ee-3781-0201b014c5b2", "name": "Generate consolidated cash flow statement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.2122206496397139, "y": 1.1960132890365447, "z": -3.8118920625572636 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2114", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves collecting and analyzing organizational data to prepare comprehensive reports for board members and shareholders. ", "Process_Group": "Finance Reporting and Analytics", "Scope": "These reports are subject to rigorous reviews for accuracy and compliance before being presented and distributed, providing critical insights into the companys financial and operational standing.", "Outcome": "Board and shareholder report is released.", "GUID": "60160349-53b7-11ee-3781-0201b014c5b2", "name": "Create board and shareholder report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5401209548546926, "y": 1.1993355481727574, "z": -4.756892624856848 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2115", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Calculate cost of goods sold based on production and material costs,\n Update cost of goods sold in profitability analysis", "Type": "Business Process", "Description": "The purpose of this process is to determine the cost of goods sold for profitability analysis or IFRS/US-GAAP periodic reporting standards.", "hasAssignment": true, "Process_Group": "Finance Reporting and Analytics", "Scope": "Information about production cost of a material and the sold volume of this material are required to determine cost of goods sold.", "Outcome": "Cost of goods sold calculated", "GUID": "16b87440-d752-11ec-4ad5-0201b014c5b2", "name": "Determine cost of goods sold", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8779089854622764, "y": 1.2026578073089702, "z": -5.6985487487885935 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2117", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves gathering and analyzing data related to an organizations investments in capital assets. The resulting reports provide crucial insights that guide decision-making on future investments and financial planning.", "Process_Group": "Finance Reporting and Analytics", "Scope": " A capital expenditures report typically includes details about the amount spent, the purpose of the investments, and their expected benefits, helping stakeholders assess the companys commitment to infrastructure and growth.", "Outcome": "Create capital expenditures report is released.", "GUID": "6016034d-53b7-11ee-3781-0201b014c5b2", "name": "Create capital expenditures report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.6358738942638795, "y": 1.2059800664451825, "z": -1.896223718497817 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2118", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is concerned with calculating the profitability of specific products or services by deducting direct costs from revenues. The contribution margin report helps businesses evaluate the individual profitability of products or services and make informed pricing and production decisions.", "Process_Group": "Finance Reporting and Analytics", "Scope": "The Contribution Margin report outlines the profitability of a specific product or service by detailing the revenue generated from its sales minus its direct variable costs. The resulting CM metric is used in various strategic decisions, including pricing and production planning.", "Outcome": "Derive contribution margin figures are released.", "name": "Derive contribution margin report", "GUID": "60160351-53b7-11ee-3781-0201b014c5b2", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9686412143143388, "y": 1.2093023255813953, "z": -2.839319319472828 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2119", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Transfer cost center costs to controlling objects,\n Transfer process order costs to controlling objects,\n Execute overhead allocation in COPA,\n Perform direct activity allocation,\n Perform allocation cycles in COPA,\n Transfer production variances to COPA,\n Execute COPA analysis on line items,\n Perform indirect activity allocation", "Type": "Business Process", "Description": "This reflects the analysis, interpretation and evaluation of the financial performance of functional units, divisions or regions. This is commonly used by senior management as a control to ensure that operational targets at the business unit level are consistent with strategic goals.", "Process_Group": "Finance Reporting and Analytics", "hasAssignment": true, "Scope": "To ensure accuracy of analysis, the following must be done: ***Calculate work in process (WIP) of sales orders on the basis of planned and actual revenues and costs. ***Generate report of WIP calculations for sales orders. ***Settle sales orders to profitability analysis. This moves all revenues from the sales order to a controlling object for profitability analysis. ***Review and complete (post) any outstanding goods issues.", "Outcome": "Profitability analysis is closed.", "GUID": "fccd2e5d-9569-11e8-2ddf-001bc640cd9b", "name": "Perform profit and loss analysis by functional area and profit centers", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.3112602768020971, "y": 1.212624584717608, "z": -3.778967648244807 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2121", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Cost center report is a document that summarizes the expenses and costs incurred by a specific department or unit within an organization. It provides insights into how resources are allocated and spent within that department, helping management assess its efficiency and control costs. Cost center reports are valuable for budgeting, cost management, and performance evaluation within a company.", "Process_Group": "Finance Reporting and Analytics", "Scope": "This process involves collecting, analyzing, and reporting costs according to organizational units and cost types. The report aids in budget planning, resource allocation, and cost-cutting initiatives.", "Outcome": "Cost center/cost type report is released.", "GUID": "60160353-53b7-11ee-3781-0201b014c5b2", "name": "Generate cost center/cost type report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6637040301513686, "y": 1.2159468438538208, "z": -4.715091610993162 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2122", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves gathering financial data, calculating the Return on Net Assets ratio, analyzing trends and performance, and producing a detailed report to guide decision-making on asset management and profitability.", "Process_Group": "Finance Reporting and Analytics", "Scope": "A Return on Net Assets (RONA) provides insights into how efficiently a company utilizes its capital to generate earnings and is a key metric for assessing overall financial performance and asset management.", "Outcome": "Return on net assets is reported.", "GUID": "60160359-53b7-11ee-3781-0201b014c5b2", "name": "Report return on net assets (RONA)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.025944886689549, "y": 1.219269102990033, "z": -5.647614303057218 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2125", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create freight order with defined carrier,\n Maintain transportation data,\n Maintain scheduling and location data,\n Add freight units,\n Calculate transportation charges", "Type": "Business Process", "Description": "Freight orders capture all information required for transportation planning by the shipper (sender) and transportation execution.They are a combination of shipments, which can be assigned to specific legs of the transport and/or carriers. The combination is based on transportation planning or transportation charges calculation. Freight orders also form the basis for track & trace activities, event management and reporting. Freight orders can be created directly or as part of transportation order based or delivery based planning. Freight bookings, in contrast, are used to book freight space in advance, for example, with a shipping company. Transportation execution can then happen on the same documents.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "The process includes the creation and maintenance with all relevant transportation information, e.g. scheduling and location data, units, charges.", "Outcome": "Freight order has been created and transmitted to the carrier of the transport and/or carriers. The combination is based on transportation planning or transportation charges calculation.", "GUID": "106a8145-7e10-11e5-0a66-001bc640cd9b", "name": "Create freight order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.6851299211109843, "y": 1.2225913621262459, "z": -1.8789882892659169 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2127", "text": "Process", "data": { "Advisory_Notes": "There might be situations where you source transport on the spot market. In these cases the I2O Transportation sourcing scenario needs to be conducted for each single shipment.", "KeyActivities": "Create shipment,\n Choose deliveries,\n Assign deliveries to shipment,\n Set planning status,\n Assign documents relevant to shipment", "Type": "Business Process", "Description": "The process facilitates planning outbound shipments related to deliveries. In addition it supports carrier selection, call-off and booking activities.", "Process_Group": "Transportation Management", "hasAssignment": true, "Scope": "The creation of shipment with assigned deliveries and booking of carrier is performed.", "Outcome": "Shipment has been confirmed by a carrier and planning status has been maintained", "GUID": "7bf5a971-7e0d-11e5-0a66-001bc640cd9b", "name": "Plan shipment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.0423893321102657, "y": 1.2259136212624586, "z": -2.8130809587181655 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2134", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process aims at assess the efficiency and effectiveness of inventory management by calculating the rate at which stock is sold and replaced within a specific time period. Stock turnover or inventory turnover, is crucial for evaluating how quickly a companys inventory is sold and replenished.", "Process_Group": "Inventory Reporting and Analytics", "Scope": "This process involves collecting data on sales, average inventory levels, and possibly production rates within a given timeframe. This data is used to calculate the stock turnover ratio. Stock turnover reporting may extend to analyzing turnover for specific product categories, locations, or time periods, providing a more granular understanding of inventory dynamics.", "Outcome": "A quantitative measure of how efficiently a company is utilizing its inventory. ", "GUID": "c510d111-5b7c-11ee-3781-0201b014c5b2", "name": "Report stock turnover", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.4094071926569143, "y": 1.229235880398671, "z": -3.743470497451123 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2135", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "A Warehouse Activity Report provides a summary of activities and transactions that have occurred within a warehouse or storage facility. This report is crucial for monitoring and managing the efficiency and productivity of warehouse operations. ", "Process_Group": "Inventory Reporting and Analytics", "Scope": "A Warehouse Activity Report in SAP typically includes information such as the following: Inventory Movements: It lists details of items that have been received, shipped, or moved within the warehouse. This includes the date and time of each movement, the item codes, quantities, and the locations involved. Stock Levels: The report may display current stock levels for each item, helping warehouse managers track inventory levels and identify potential stockouts or overstock situations. Order Fulfillment: It provides insights into the progress of order fulfillment processes, indicating which orders have been picked, packed, and shipped, along with any outstanding orders. Storage Utilization: Warehouse Activity Reports can also show how storage space within the warehouse is being utilized, highlighting any areas of congestion or inefficiency. Productivity Metrics: Some reports may include key performance indicators (KPIs) related to warehouse operations, such as order processing times, pick accuracy, and resource utilization. Exception Handling: Exceptional events or discrepancies, such as damaged items or missing inventory, are often highlighted in the report for immediate attention and resolution. Historical Data: Depending on the configuration, historical data may be available, allowing for trend analysis and performance benchmarking.", "Outcome": "Generation of detailed and actionable insights into the activities within a warehouse.", "GUID": "c510d113-5b7c-11ee-3781-0201b014c5b2", "name": "Report warehouse activity", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7861544490056631, "y": 1.2325581395348837, "z": -4.67008054366274 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2136", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process collects and analyzes data on various inventory metrics. The resulting report provides valuable insights into inventory efficiency, aiding in better management and planning.", "Process_Group": "Inventory Reporting and Analytics", "Scope": "The is process involves compiling and presenting comprehensive information about the inventory within a business. This includes details on stock levels, item locations, turnover rates, and other relevant metrics. The scope extends to capturing data on both raw materials and finished goods, tracking movement throughout the supply chain, and providing insights into inventory valuation.", "Outcome": "Comprehensive and up-to-date overview of the current state of the inventory within a business.", "GUID": "60160357-53b7-11ee-3781-0201b014c5b2", "name": "Generate Inventory report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.172601516432096, "y": 1.2358803986710964, "z": -5.592834938633265 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2138", "text": "Process", "data": { "Advisory_Notes": "It is necessary to define how the actual physical storage will be performed. The procedure for informing the requester must be defined. ***In case a more sophisticated warehouse management is needed, refer to the processes of warehouse management within the domain I2O.", "KeyActivities": "Communicate quality deviations ,\n Inform procurement about rejection,\n Check goods,\n Record goods receipt of indirect materials,\n Document discrepancies,\n Store goods in warehouse,\n Confirm goods delivery with external carrier,\n Accounts payable posting,\n Inventory increase (procurement) posting", "Type": "Business Process", "Description": "When inventory-managed indirect materials are delivered, they need to be placed in the warehouse and their receipt must be documented.", "Process_Group": "Inbound Delivery Management", "hasAssignment": true, "Scope": "Upon delivery of inventory-managed indirect materials, it is confirmed and documented that the items are correct, in good condition and in accordance with requirements of the purchase order. These materials are inventory-managed on a quantity basis. The process covers simplified goods receipt without inbound delivery. Shown here as exemplary process, since it is assumed that consumable handling does not require sophisticated goods receipt process.", "Outcome": "Indirect materials are received and available for use.", "GUID": "dac2e2cd-7f04-11e5-0a66-001bc640cd9b", "name": "Perform goods receipt of indirect materials", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.7339195087327514, "y": 1.2392026578073088, "z": -1.860473637196044 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2142", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This Process describes the execution of the report, analysis of the data and the decision to inactivate materials that are not longer used", "Process_Group": "Business Partner Master Data", "Scope": "Create reports on business partner master data to check which master data entries are not longer needed and set them to inactivate.", "Outcome": "Annual portfolio check conducted, and where required materials are phased out.", "GUID": "ea16581b-d703-11ed-3781-0201b014c5b2", "name": "Execute annual business partner portfolio check", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1154277870268035, "y": 1.2425249169435215, "z": -2.7849274410527265 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2144", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": " This process is essential for effectively capturing, allocating, and analyzing costs associated with different departments or functions. It includes tasks such as setting up new cost centers, defining attributes like responsible departments or managers, and linking cost centers to relevant business units or profit centers.", "Process_Group": "FICO Master Data", "Scope": "This process involves the updating and management of cost center information within the financial framework of an organization.", "Outcome": "All needed cost centers are created or changed.", "GUID": "9345f15d-56c3-11ee-3781-0201b014c5b2", "name": "Maintain master data cost center", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5065945783863184, "y": 1.2458471760797343, "z": -3.705424776780248 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2145", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the creation, maintenance and approval of secondary cost elements. Secondary cost elements are mandatory for primary cost and secondary cost account types.", "Process_Group": "FICO Master Data", "Scope": "When a requestor submits a secondary cost elements request form, upon approval the secondary cost elements is created and all Stakeholders are informed.", "Outcome": "Secondary cost element are ready for posting.", "GUID": "ea165813-d703-11ed-3781-0201b014c5b2", "name": "Maintain secondary cost elements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9073888466764475, "y": 1.249169435215947, "z": -4.621890066582533 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2146", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": " This process ensures that all banking transactions, whether they relate to accounts payable, accounts receivable, or general ledger activities, are accurately mapped to the correct bank information.", "Process_Group": "FICO Master Data", "Scope": "This process involves the collection, validation, and secure storage of all bank master data including bank account details, routing numbers, and other relevant banking credentials.", "Outcome": "All needed bank master data is created or changed.", "GUID": "9345f155-56c3-11ee-3781-0201b014c5b2", "name": "Maintain bank master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.317779030262367, "y": 1.2524916943521593, "z": -5.534247949529913 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2147", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "These key figures serve as the foundation for distributing costs across various departments, cost centers, or projects, and can include metrics like labor hours, machine hours, or square footage.", "Process_Group": "FICO Master Data", "Scope": "This involves defining, updating, and managing statistical metrics that are essential for cost allocation and performance measurement.", "Outcome": "statistical key figures are available in ERP system.", "GUID": "7b591e33-56c8-11ee-3781-0201b014c5b2", "name": "Maintain statistical key figures", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.7822094409803111, "y": 1.255813953488372, "z": -1.8406923671383193 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2148", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is pivotal for tracking, reporting, and analyzing profitability on a segmented basis.", "Process_Group": "FICO Master Data", "Scope": "This process focuses on the configuration and upkeep of hierarchical structures that define profit center groups within the organization.", "Outcome": "Profit center groups are created or changed in ERP system.", "GUID": "7b58f728-56c8-11ee-3781-0201b014c5b2", "name": "Maintain master data profit center groups", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1877068541880178, "y": 1.2591362126245849, "z": -2.7548779335053672 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2149", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The process allows for accurate cost accounting and allocation, as it establishes the framework for charging costs from one department to another based on activity consumption.", "Process_Group": "FICO Master Data", "Scope": "This process focuses on categorizing and defining various activities that consume resources within an organization.", "Outcome": "Activity types are maintained in the ERP system.", "GUID": "9345f159-56c3-11ee-3781-0201b014c5b2", "name": "Maintain master data activity type", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.602756268424454, "y": 1.2624584717607972, "z": -3.6648563879129177 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2150", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This ensure the consistent updating and categorization of tax-related variables. These tax classifications are crucial for correct tax calculation and reporting, ensuring compliance with local, state, and federal tax laws.", "Process_Group": "FICO Master Data", "Scope": "This process involves defining and modifying tax indicators, such as tax rates, tax jurisdictions, and tax categories that are applicable to various transactions within the organization.", "Outcome": "Tax-related variables are updated and categorized.", "GUID": "7b591e35-56c8-11ee-3781-0201b014c5b2", "name": "Maintain tax classification indicators", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.0273246862947407, "y": 1.26578073089701, "z": -4.570552988024527 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2151", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "By clustering similar activities together, this process enhances the efficiency and accuracy of cost accounting practices, simplifies reporting, and aids in better resource allocation.", "Process_Group": "FICO Master Data", "Scope": "This process involves the categorization and grouping of related activity types.", "Outcome": "Activity type groups are maintained in the ERP system.", "GUID": "9345f15b-56c3-11ee-3781-0201b014c5b2", "name": "Maintain master data activity type groups", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.4613785907409205, "y": 1.2691029900332227, "z": -5.471893222006643 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2152", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the maintenance of cost center data and related cost center groups and hierarchies.", "Process_Group": "FICO Master Data", "Scope": "When a requestor submits a cost center request form, upon approval the cost center is created and all Stakeholders are informed.", "Outcome": "Cost centers are ready for posting.", "GUID": "ea165811-d703-11ed-3781-0201b014c5b2", "name": "Maintain cost center", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.829966841872196, "y": 1.272425249169435, "z": -1.81965794626152 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2153", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Profit centers are used to manage internal controlling. Dividing a company into profit centers allows delegation of responsibility to decentralized units and treat them as separate companies within a company.", "Process_Group": "FICO Master Data", "Scope": "Object owners needs to maintain profit center data and related profit center groups and hierarchies. In this process, profit center data and related profit center groups and hierarchies are created or changed.", "Outcome": "All needed profit centers are created or changed.", "GUID": "ea165815-d703-11ed-3781-0201b014c5b2", "name": "Maintain profit center", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.259177325712217, "y": 1.2757475083056478, "z": -2.722952893902542 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2154", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that the planned prices for externally purchased materials are current and accurate. ", "Process_Group": "FICO Master Data", "Scope": "This process involves collecting up-to-date pricing data, accounting for additional costs, and integrating this information into financial models for more reliable cost and profitability calculations.", "Outcome": "Material plan prices are up to date in ERP system.", "GUID": "7b591e31-56c8-11ee-3781-0201b014c5b2", "name": "Maintain material planned prices (third party purchased)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6978267955032609, "y": 1.2790697674418605, "z": -3.621792949972586 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2155", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process facilitates the organized handling of internal orders within an enterprise. Internal order groups make it easier to manage related orders collectively, thereby simplifying cost tracking, budgeting, and financial reporting.", "Process_Group": "FICO Master Data", "Scope": "The process involves the categorization and grouping of various internal orders according to specific criteria such as project type, department, or cost center.", "Outcome": "All needed internal order groups are created or changed.", "GUID": "7b58f724-56c8-11ee-3781-0201b014c5b2", "name": "Maintain master data internal order groups", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.1458803150551438, "y": 1.2823920265780733, "z": -4.516104258479739 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2156", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "By grouping statistical key figures, this process adds a layer of granularity that allows for more accurate and tailored financial reporting and decision-making.", "Process_Group": "FICO Master Data", "Scope": "This process specifically focuses on the categorization and handling of statistical key figures, which are essential for internal cost allocation, overhead calculations, and various other financial analytics.", "Outcome": "Statistical key figure groups are available in the ERP system.", "GUID": "7b58f72a-56c8-11ee-3781-0201b014c5b2", "name": "Maintain master data statistic key figures groups", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.6033024347053475, "y": 1.2857142857142856, "z": -5.405813207414516 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2157", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": " This process ensures that all controlling (CO) relevant variables such as labor rates, material costs, and overheads are accurately captured and reflected in the system. The data gathered serves as the basis for tariff calculations, internal cost allocations, and external financial reporting.", "Process_Group": "FICO Master Data", "Scope": "Collecting, updating, and maintaining the key information that influences tariff rates and financial reporting.", "Outcome": "CO relevant data for tariff determination & reporting ready for use.", "GUID": "9345f157-56c3-11ee-3781-0201b014c5b2", "name": "Maintain CO relevant data for tariff determination & reporting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.8771591979764429, "y": 1.2890365448504983, "z": -1.7973846948845769 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2158", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process allows for the structured setup and ongoing upkeep of profit centers. ", "Process_Group": "FICO Master Data", "Scope": "Capture and analyze revenue and costs in a segmented manner, facilitating more accurate financial reporting and strategic decision-making.", "Outcome": "Profit centers are created or changed in ERP system.", "GUID": "7b58f726-56c8-11ee-3781-0201b014c5b2", "name": "Maintain master data profit center", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.3297905442129134, "y": 1.292358803986711, "z": -2.689174056940518 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2159", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "These groups aggregate multiple cost centers for simplified reporting and analysis, facilitating efficient budget allocation and expenditure monitoring.", "Process_Group": "FICO Master Data", "Scope": "This process involves the creation and updating of cost center groups.", "Outcome": "All needed cost center groups are created or changed.", "GUID": "9345f15f-56c3-11ee-3781-0201b014c5b2", "name": "Maintain master data cost center groups", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7917414352228174, "y": 1.2956810631229234, "z": -3.576263780722233 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2160", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the creation, maintenance, change and activation of internal order.", "Process_Group": "FICO Master Data", "Scope": "A requester submits a internal order request form and the internal order is created made available for Stakeholders.", "Outcome": "Internal order is ready for posting.", "GUID": "ea16580f-d703-11ed-3781-0201b014c5b2", "name": "Maintain internal order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.262975019805399, "y": 1.2990033222591362, "z": -4.458580946863783 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2161", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is key for management accounting and reporting, as it helps segregate costs, revenues, and other financial parameters by different functional aspects like marketing, production, research, etc.", "Process_Group": "FICO Master Data", "Scope": "This process involves the configuration and updating of functional areas that are used to classify a companys various business operations.", "Outcome": "Functional areas are maintain in ERP system.", "GUID": "7b58f720-56c8-11ee-3781-0201b014c5b2", "name": "Maintain master data functional area", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.7434539398278304, "y": 1.302325581395349, "z": -5.336052893295114 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2162", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": " These internal orders serve as cost objects that capture expenses and revenues for specific, time-bound activities or projects.", "Process_Group": "FICO Master Data", "Scope": "This process focuses on setting up and updating internal orders for better cost tracking and internal project financing.", "Outcome": "Internal order master data is maintained in ERP system.", "GUID": "7b58f722-56c8-11ee-3781-0201b014c5b2", "name": "Maintain master data internal orders", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9237543805458681, "y": 1.3056478405315612, "z": -1.7738877767272425 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2164", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Create Service Material Master process is a key step in materials management, particularly in industries that offer services rather than physical products. This process ensures accurate record-keeping, facilitates pricing and billing for services, and helps in managing service-related inventory efficiently. It also applicable for creating variant configuration for service material master.", "Process_Group": "Material and Product Master Data", "Scope": "This process involves entering and maintaining detailed information about service materials in an organizations database. It typically includes data such as the service materials description, price, unit of measure, and other relevant attributes. ", "Outcome": "A new service material master has been created and is ready for use for example in sales or procurement.", "GUID": "4f7ac641-4d51-11ee-3781-0201b014c5b2", "name": "Create service material master", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.3994984359249312, "y": 1.308970099667774, "z": -2.65356441938832 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2165", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create new routing,\n Extend routing to an existing material", "Type": "Business Process", "Description": "This process shows the routing instructions used in production.", "Process_Group": "Material and Product Master Data", "hasAssignment": true, "Scope": "The routing is an ordered list of tasks required for a manufacturing process that is used for making a product.", "Outcome": "The routing is created.", "GUID": "3f96eb08-9569-11e8-2ddf-001bc640cd9b", "name": "Create routing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8844362501160241, "y": 1.3122923588039868, "z": -3.528299876604688 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2167", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that users are offered default data when creating or extending master record. This keeps time required to enter data to a minimum and makes it possible to copy changes from the reference data to dependent data records.", "Process_Group": "Material and Product Master Data", "Scope": "The default data comes from the references listed in generic reference data record Also indicated is the priority (1 = highest) with which the default data is used when you create an master record.", "Outcome": "All needed Reference data is available to use.", "GUID": "a779b7d0-d79e-11ed-3781-0201b014c5b2", "name": "Maintain generic reference data record", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.3785290819962337, "y": 1.3156146179401995, "z": -4.3980222152802 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2168", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process covers the activities to request and execute a change of BOM with engineering record.", "Process_Group": "Material and Product Master Data", "Scope": "The BOM list contains the object number of each component, together with the quantity and unit of measure. Changes to the BOM list are made in the system. Request engineering record for BOM change, send engineering record for approval. After all approvals, complete, status changes and change number is generated, then change BOM with change, number. ", "Outcome": "The BOM is changed and engineering record for deactivating the change number is closed.", "GUID": "ea16580b-d703-11ed-3781-0201b014c5b2", "name": "Change a bill of materials (BOM) with engineering record", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.881737690396013, "y": 1.3189368770764118, "z": -5.262659772752848 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2169", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes changing service material master of materials.", "Process_Group": "Material and Product Master Data", "Scope": "After requesting a change to an existing service material master the related different views of material master is updated.", "Outcome": "Service material master has been changed.", "GUID": "4f7ac643-4d51-11ee-3781-0201b014c5b2", "name": "Change service material master", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 0.9697206673914499, "y": 1.3222591362126246, "z": -1.7491831885865703 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2170", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Create bill of materials,\n Maintain material and plant for BOM,\n Maintain material,\n quantity and unit", "Type": "Business Process", "Description": "A bill of material is a complete, formally structured list of the components that make up a product or assembly. A BOM may possess different statuses.", "hasAssignment": true, "Process_Group": "Material and Product Master Data", "Scope": "The BOM list contains the object number of each component, together with the quantity and unit of measure.", "Outcome": "The BOM is created.", "GUID": "ea165807-d703-11ed-3781-0201b014c5b2", "name": "Create a bill of materials (BOM)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.4682535434332555, "y": 1.3255813953488373, "z": -2.6161482244314236 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2172", "text": "Process", "data": { "Advisory_Notes": "***The extension to plants is needed in order to make materials available in these plants for any activities. Typically there are strict rules on this extension in order to control portfolio, supply routes and price policies.", "KeyActivities": "Check request and assign to product expert,\n Fill in existing material number,\n Add requested plant for extension,\n Review material and inform requester", "Type": "Business Process", "Description": "This process describes how to extend the material master to another plant.", "Process_Group": "Material and Product Master Data", "hasAssignment": true, "Scope": "The extension request needs to be checked and approved before the material master is actually extended to the other plant.", "Outcome": "Material master has been extended to the other plant and is available for example to launch the product in the respective legal entity.", "GUID": "37205d79-8d0d-11e9-0cfc-001bc641ce4f", "name": "Extend material master to other plant", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9758481331774391, "y": 1.3289036544850497, "z": -3.4779338916401543 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2174", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process covers the activities to request and execute a change of recipe with engineering record.", "Process_Group": "Material and Product Master Data", "Scope": "Request engineering record for recipe change, send engineering record for approval, after all approvals complete, status changes automatically and change number is generated.", "Outcome": "Change recipe with the change number created.", "GUID": "ea16580d-d703-11ed-3781-0201b014c5b2", "name": "Change a recipe with an engineering record", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.4924638319540686, "y": 1.3322259136212624, "z": -4.334469292358736 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2175", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The information in the QM view of the Material Master controls the quality management processes throughout the logistics supply chain. QM-specific data in the Material Master: * enables the control of the quality inspection process * sets rules for sample calculation * helps define whether a Material is to be posted to inspection stock", "Process_Group": "Material and Product Master Data", "Scope": "The Material itself serves as the reference object for the quality inspection, quality certificates, and quality notifications. Master Data must be updated and maintained on a regular basis, in order for business processes to be performed in the system.", "Outcome": "Local fields of QM view of Material Master maintained.", "GUID": "ea16581d-d703-11ed-3781-0201b014c5b2", "name": "Maintain master data for quality management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.018059542272405, "y": 1.3355481727574752, "z": -5.185683812121453 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2176", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "A master recipe is used to describe the production sequence. All needed resources are assigned to operations. An operation is subdivided into one or more phases. A phase is an independent process step that contains the detailed description of a part of the entire manufacturing process.", "Process_Group": "Material and Product Master Data", "Scope": "The master recipe is created in the system. It contains standard values for activities in conjunction with a base quantity of the header material. Sequential, parallel or overlapping relationships between phases can be maintained to show constraints.", "Outcome": "The recipe is created.", "GUID": "ea165809-d703-11ed-3781-0201b014c5b2", "name": "Create a master recipe", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.0150267644789221, "y": 1.338870431893688, "z": -1.7232877494462295 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2177", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the maintenance of a product hierarchy record.", "Process_Group": "Material and Product Master Data", "Scope": "Create a product hierarchy and assign the respective products to the product hierarchies in the system. These product hierarchies are the alphanumeric character string used for grouping materials.", "Outcome": "All needed product hierarchy records ar available to use.", "GUID": "a77a05f1-d79e-11ed-3781-0201b014c5b2", "name": "Maintain product hierarchy record", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.536009057982207, "y": 1.3421926910299002, "z": -2.5769509451669066 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2178", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This Process describes the execution of the report, analysis of the data and the decision to inactivate business partners that are not longer used.", "Process_Group": "Material and Product Master Data", "Scope": "Create reports on business partner master data to check which master data entries are not longer needed and can get inactivated. Material status is switched to inactivated Status.", "Outcome": "Material status is switched to inactivated Status.", "GUID": "ea165819-d703-11ed-3781-0201b014c5b2", "name": "Execute annual material portfolio check", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.0659148508268292, "y": 1.345514950166113, "z": -3.4252001151951927 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2180", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes how to maintain a local material master data in the view Warehouse management 1 and 2, such as Stock removal indicator, stock placement indicator, storage section, bin type.", "Process_Group": "Operational Master Data", "Scope": "Define and maintain warehousing-specific data for all items used in Warehousing. Typically, master data for Storage and Warehouse management is required for all activities involved in warehouse processing.", "Outcome": "Warehousing-specific data is maintained for all items used in Warehousing.", "GUID": "ea165823-d703-11ed-3781-0201b014c5b2", "name": "Maintain master data for storage and warehouse management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.6047017024396526, "y": 1.3488372093023258, "z": -4.267965445186731 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2181", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Manufacturing operations are carried out at a work center. It can represent the following real work centers, for example: * machines, * machine groups, * production lines * assembly work centers, * employees and * groups of employees.", "Process_Group": "Operational Master Data", "Scope": "The plant where the work center is located and a key which identifies the work center is entered in the system. When creating a work center, the work center category must be maintained.", "Outcome": "Work center is created. ", "GUID": "a77a05f8-d79e-11ed-3781-0201b014c5b2", "name": "Create work center", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.152326686988086, "y": 1.352159468438538, "z": -5.105177416946713 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2182", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the information that can be maintained in the material master record, data that is relevant only for inventory management. Such information could be updated in case a business decision has been taken and which implies to update the material in order to change the behavior of the material in the location. ", "Process_Group": "Operational Master Data", "Scope": "To be able to update the material master record special user authorization is required, and this must be only for plant and storage location material views.", "Outcome": "Inventory management data update to date.", "GUID": "ea165821-d703-11ed-3781-0201b014c5b2", "name": "Maintain master data for inventory management", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.0596418272338801, "y": 1.3554817275747508, "z": -1.696219089026074 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2183", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that master data process are executed according to agree procedures and guidelines.", "Process_Group": "Operational Master Data", "Scope": "Create reports on master data process performance, conduct analysis and take corrective actions where applicable.", "Outcome": "Master data processes are evaluated and corrective action taken as required.", "GUID": "ea165817-d703-11ed-3781-0201b014c5b2", "name": "Monitor master data processes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6027188513430446, "y": 1.3588039867109636, "z": -2.535999267261257 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2184", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "A planning hierarchy represents the organizational levels and units relevant for planning.", "Process_Group": "Operational Master Data", "Scope": "The planning hierarchy can either be created automatically by the system or manually. To create a planning hierarchy manually: 1) Enter the name of the information structure on which the planning hierarchy is to be based 2) Enter values for the characteristics from the information structure (the units of the information structure on which you base your planning hierarchy must be defined in Customizing)", "Outcome": "Planning hierarchy is created.", "GUID": "a77a05fc-d79e-11ed-3781-0201b014c5b2", "name": "Create planning hierarchy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.15457508527801, "y": 1.362126245847176, "z": -3.3701344486384004 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2185", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Work centers can be grouped into a work center hierarchy. Apart from the top of the hierarchy - the hierarchy root - every work center in the hierarchy is subordinate to another work center. One work center can exist in several work center hierarchies. A work center hierarchy can include several plants.", "Process_Group": "Operational Master Data", "Scope": "When changing data of a work center that is assigned to an operation, only default values for which a reference indicator has been set, are changed in the operation.", "Outcome": "Work center hierarchy is changed.", "GUID": "a77a05fa-d79e-11ed-3781-0201b014c5b2", "name": "Change work center hierarchy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.715166281456147, "y": 1.3654485049833887, "z": -4.198555949852711 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2187", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes a standardised data gathering for packaging material.", "Process_Group": "Compliance Master Data", "Scope": "The process requires standardized phrases and text blocks for the generation of technical specifications.", "Outcome": "Master data for packaging specification is captured in designated systems.", "GUID": "ea165801-d703-11ed-3781-0201b014c5b2", "name": "Maintain packaging specification master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.284447714927115, "y": 1.3687707641196014, "z": -5.021195396308538 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2188", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process allows businesses to maintain a set of essential information and records to support their international trade and commerce activities.", "Process_Group": "Compliance Master Data", "Scope": "Global trade master data includes product descriptions, specifications, classifications, and compliance data, such as Harmonized System (HS) codes, which are used for customs and tariff purposes. Global trade master data may also include supplier contact details, certifications, and performance history, as well as Customer Data, country and regulatory Information.", "Outcome": "All required data are copied to the global trade master.", "GUID": "61babc20-5152-11ee-3781-0201b014c5b2", "name": "Global trade master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1035354815408918, "y": 1.3720930232558142, "z": -1.6679956357797558 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2189", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process cover the activities to maintain and manage waste master data.", "Process_Group": "Compliance Master Data", "Scope": "Maintain and if applicable concatenate: - Waste - Waste Code - Waste Catalog - Waste generators (points of generation) - Waste disposers - Waste transporters -Authorities and waste approvals", "Outcome": "Waste master data is maintained.", "GUID": "ea165805-d703-11ed-3781-0201b014c5b2", "name": "Maintain Waste master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6683375072182474, "y": 1.3754152823920265, "z": -2.4933210707826627 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2190", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process to create and maintain the dangerous goods master data.", "Process_Group": "Compliance Master Data", "Scope": "Typically, dangerous goods master master can be maintained manually or by using an automatic process. All legal data and related regulations with the transport are maintained in the UN listed substance and during filling process.", "Outcome": "All required data are copied to the dangerous goods master.", "GUID": "ea1630f0-d703-11ed-3781-0201b014c5b2", "name": "Maintain dangerous goods master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.2417684762842587, "y": 1.3787375415282392, "z": -3.312774380898608 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2191", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that master data related to recycling is correct, complete and available when required.", "Process_Group": "Compliance Master Data", "Scope": "Create and edit articles, packaging, electronic articles, Batteries etc., fractions, recycling partners Make sure to identify customers, allowed to send back packaging. Make sure that materials are marked that recycling is mandatory.", "Outcome": "Recycling master data is up to date.", "GUID": "ea165803-d703-11ed-3781-0201b014c5b2", "name": "Maintain recycling master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.8237823642707434, "y": 1.382059800664452, "z": -4.126288060622226 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2194", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The inspection equipment monitoring / measuring equipment monitoring aims to ensure and maintain the quality, reliability, operational capability and readiness of the inspection equipment in the organization.", "Process_Group": "Test Equipment Management", "Scope": "ISO 9001 prescribes regular calibration and, if necessary, adjustment of all test and measuring equipment in a company. The intervals of calibration depend on individual factors: Industry, type, design and sensitivity of the testing and measuring equipment and its relevance in the processes. The more important this testing and measuring equipment is for the quality of the products, the more value must be placed on the reliability and precision of the testing and measuring equipment. Monitoring and calibration of test equipment: ? When the monitoring date is reached, due test equipment shall be collected by the quality department in consultation with the departments using the respective test equipment. For their information and disposition, the test equipment is marked with stickers indicating the calibration date. ? If test equipment is damaged or if damage or a defect is suspected in the test equipment, it is also submitted for calibration. ? Test equipment is calibrated internally or externally using standards. If the measurement deviations determined (by internal or external bodies) are not greater than the specified limit value, the test equipment is OK. ? The decision is recorded in the calibration report, the next monitoring interval is specified and the test equipment is marked accordingly with the next calibration date. ? If the maximum measurement deviation is greater than the specified limit value, an evaluation of the last product tests performed with the test equipment is carried out. ? If the faulty test equipment can be adjusted, it is adjusted and then recalibrated. Non-adjustable faulty test equipment is reclassified or scrapped.", "Outcome": "Test equipment lists, test equipment plans Calibration records, calibration reports, marked test and measuring equipment", "GUID": "ac003fd8-9d52-11ed-3781-0201b014c5b2", "name": "Perform inspection equipment monitoring", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.4143326775585097, "y": 1.3853820598006643, "z": -4.933794925506748 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2195", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Test and measuring equipment must be checked for suitability or capability before use. For this purpose, measuring equipment is calibrated or methods such as capability or measuring system analyses are applied. Measurement system analysis or test equipment capability analysis is the analysis of measuring equipment and complete measurement systems in quality management.", "Process_Group": "Test Equipment Management", "Scope": "Five different categories of measurement deviations are distinguished: accuracy, repeatability, reproducibility, linearity and stability. Accuracy or trueness is determined by repeated measurement of one and the same test item. For this purpose, the mean value of the measured values is compared with the true characteristic value of the test specimen. The difference between the mean value and the true value is called the systematic measurement deviation. This difference is then used to make a statement about the accuracy (correctness, suitability) of the measuring device. To determine the comparative precision, measurements are carried out on the same test specimens according to a specified measuring procedure: - by different operators - at different locations or - with several devices of the same type Usually, there are two or three operators who measure the same parts several times in succession, or one and the same operator repeats the same measurement procedure at different locations or with different devices. However, only one of these three variables (operator, location, device) is ever changed within an examination.", "Outcome": "Calibration records, calibration reports", "GUID": "ac003fd4-9d52-11ed-3781-0201b014c5b2", "name": "Check the suitability of the test equipment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1466778444223185, "y": 1.388704318936877, "z": -1.6386366043485618 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2196", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The need for test equipment results from the product characteristics to be tested. This requirement is recorded by the test equipment management in order to develop test equipment planning, which forms the basis for the procurement of test equipment. The aim of test equipment planning is to find the optimum test equipment for each test characteristic. ", "Process_Group": "Test Equipment Management", "Scope": "The test equipment must be suitable for the measuring/testing task (area of application, no geometric restrictions, environmental conditions, requirements for the tester, reliability).", "Outcome": "Test equipment plan", "GUID": "ac003fd2-9d52-11ed-3781-0201b014c5b2", "name": "Plan test equipment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7328203521611139, "y": 1.3920265780730898, "z": -2.448945411220151 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2197", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The prerequisite of any test equipment management is an intelligent recording and maintenance of the test equipment master data. It is also necessary to record and track the typical movement processes and to create the basis for a usage decision.", "Process_Group": "Test Equipment Management", "Scope": "Test equipment management includes the labeling, deadline monitoring of test equipment (e.g., calibration deadline monitoring), test equipment release and approval, and the performance of calibration. This ensures that no test equipment is used whose calibration date has been exceeded.", "Outcome": "Test equipment lists and test equipment plans", "GUID": "ac003fda-9d52-11ed-3781-0201b014c5b2", "name": "Manage test tools", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.32743566223181, "y": 1.3953488372093021, "z": -3.2531589629422624 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2199", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process provides a comprehensive document detailing the identification, investigation, and resolution of issues or defects within a system, product, or process. Its purpose is to assess and document the nature, causes, and impacts of identified defects, aiming to improve quality, efficiency, and performance.", "Process_Group": "Quality Reporting and Analytics", "Scope": "Creating a defect analysis report typically involves an identification and logging of defects that occur through testing, user feedback, or quality control measures. Following this, a thorough analysis is conducted to understand the root causes, often involving data collection, hypothesis formulation, and investigation. Subsequently, the impact assessment on the system or product is evaluated to determine the severity and implications of the identified defects. Once analyzed, recommendations and corrective actions are devised, involving collaboration among stakeholders and subject matter experts. Finally, the report is compiled, documenting findings, resolutions, and preventive measures for future reference, ensuring a continuous improvement cycle within the system or product design.", "Outcome": "Detailed documentation of defects and their impact are provided", "GUID": "c510d120-5b7c-11ee-3781-0201b014c5b2", "name": "Create defect analysis report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9304760046143103, "y": 1.398671096345515, "z": -4.051210977766988 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2200", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Generating quality control and inspection report is providing a structured document designed to assess the quality of a product or service. Its purpose is to systematically review and evaluate various aspects of production, ensuring compliance with set standards, identifying defects or deviations, and recommending corrective actions. ", "Process_Group": "Quality Reporting and Analytics", "Scope": "To generate this report, establish clear quality criteria and standards and define what aspects require evaluation. Inspection protocols and methodologies are devised, outlining the procedures for examining raw materials, intermediate stages, and the final product. During the inspection phase, data is systematically collected and recorded, noting any deviations from the set standards. Following the inspection, analysis and interpretation of gathered data occur to identify trends, patterns, and areas requiring improvement. Finally, the comprehensive report is generated, encompassing findings, observations, recommendations for corrective actions, and, importantly, measures for preventing similar issues in the future.", "Outcome": "A comprehensive report detailing findings, highlighting areas of concern or improvement, and providing actionable insights to enhance product quality and consistency is provided.", "GUID": "c510d11e-5b7c-11ee-3781-0201b014c5b2", "name": "Generate quality control and inspection report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.5418931486736427, "y": 1.4019933554817277, "z": -4.843035507135861 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2201", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Generating a sustainability report in quality reporting is to provide a comprehensive document that outlines an organizations environmental, social, and governance (ESG) performance. The purpose of this report is to provide stakeholders with a clear understanding of the companys commitment to sustainable practices, including its environmental footprint, social responsibility initiatives, and governance structures.", "Process_Group": "Compliance and Audits Reporting", "Scope": "This process begins with scoping and data collection, where key performance indicators (KPIs) are identified, and relevant data on environmental, social, and governance aspects are gathered from across the organization. Following this, the data undergoes verification and validation to ensure accuracy and reliability. The next step involves analysis and interpretation of the collected information to identify trends, strengths, weaknesses, and areas for improvement. Drafting the report comes next, involving the compilation of findings, setting goals, and integrating narratives that align with the companys sustainability strategy. Finally, the report undergoes review, including input from stakeholders, before being published to share the organizations sustainability efforts and progress transparent", "Outcome": "Detailed information about the companys ESG performance is generated and made available to relevant stakeholders. ", "GUID": "6016035b-53b7-11ee-3781-0201b014c5b2", "name": "Generate sustainability report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.1890395443827668, "y": 1.4053156146179404, "z": -1.6081619824800057 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2204", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process allows recording of all costs incurred throughout the complaint handling and investigation process for further consideration in claims processing.", "Process_Group": "Complaint Management", "Scope": "Costs incurred at every step of complaint handling is recorded by the relevant stakeholders", "Outcome": "Costs related to complaint are recorded.", "GUID": "11473b13-9505-11ee-3781-0201b014c5b2", "name": "Record cost of complaint", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7961234859896258, "y": 1.4086378737541527, "z": -2.4029024997024897 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2205", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures the proper handling of complaints.", "Process_Group": "Complaint Management", "Scope": "The progress of the complaint is monitored and tracked. In case of delays reasons are investigated and escalated.", "Outcome": "Complaint monitored.", "GUID": "1f6c4922-7e4d-11e5-0a66-001bc640cd9b", "name": "Monitor complaint", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.4115183205534865, "y": 1.4119601328903655, "z": -3.1913287811873747 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2207", "text": "Process", "data": { "Advisory_Notes": "Inspections follow a clear and predefined inspection plan. The inspection characteristics define what has to be inspected. The inspection method states how the characteristic has to be assessed. The quality parameters define for the inspected product/good the values range within the result are considered as within specification.", "KeyActivities": "Record inspection results,\n Perform visual inspection", "Type": "Business Process", "Description": "Samples (sample may refer also to a 100% inspection) get inspected for each inspection characteristic. The results are recorded. This may also include the qualification of the production line itself and its integrated measurement devices. The recorded inspection results document the quality of the inspected in-process-material and provide the basis for making a decision regarding corrective actions.", "Process_Group": "Quality Inspections", "hasAssignment": true, "Scope": "After the samples have been extracted, the defined inspection takes place. The inspection encompasses quality inspections based on predefined quality characteristics. The inspection includes visual measurements done directly on the product without taking a specific sample for the inspection, or can be done directly by using the integrated measurement devices of the production line.", "Outcome": "Quality characteristics have been assessed and documented.", "GUID": "57143ecd-59d9-11e8-2ddf-001bc640cd9b", "name": "Perform visual inspection and record results", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.0351745650243647, "y": 1.4152823920265782, "z": -3.9733758140690845 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2211", "text": "Process", "data": { "Advisory_Notes": "", "KeyActivities": "Reserve batch and quantity,\n Display and identify valid batches,\n Determine batch strategy,\n Submit data to expert system,\n Receive determined batches,\n Allocate the batches and quantities,\n Execute batch strategy", "Type": "Business Process", "Description": "The assignment of component batches processes covers the determination of batch assignment and their strategy used in production. Normally, there are 3 types of determinations utilized: manual assignment, automatic assignment or via submission of date to the expert system.", "Process_Group": "Production Scheduling", "hasAssignment": true, "Scope": "The assignment can happen during production planning,production order release, or during the production staging goods issue.", "Outcome": "Component batches assigned.", "GUID": "cf57b44e-e9c8-11e4-0a66-001bc640cd9b", "name": "Assign component batches", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.667042284587093, "y": 1.4186046511627906, "z": -4.748978930575527 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2214", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the maintenance of functional location data, which represents the place a maintenance task has to be performed.", "Process_Group": "Plant Maintenance Asset Management", "Scope": "Creating, updating, and monitoring information related to functional locations, such as equipment, buildings, or specific areas within a facility", "Outcome": "Functional location maintained.", "GUID": "33ac6770-699e-11ee-3781-0201b014c5b2", "name": "Maintain functional location", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.2305917414053225, "y": 1.4219269102990033, "z": -1.5765925174200897 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2215", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the maintenance of plant maintenance plans and items.", "Process_Group": "Plant Maintenance Asset Management", "Scope": "Creating, updating, and managing scheduled maintenance activities for assets and equipment within an organization.", "Outcome": "Maintenance plans maintained.", "GUID": "33ac8e83-699e-11ee-3781-0201b014c5b2", "name": "Maintain maintenance plans", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.858203811673871, "y": 1.425249169435216, "z": -2.3552236824303323 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2216", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the maintenance of equipment master data. This can include production machines and tools in structures of various complexity.", "Process_Group": "Plant Maintenance Asset Management", "Scope": "Creating, updating, and managing information related to individual pieces of equipment within an organization.", "Outcome": "Equipment data maintained.", "GUID": "33ac8e81-699e-11ee-3781-0201b014c5b2", "name": "Maintain equipment data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.4939592074349335, "y": 1.4285714285714284, "z": -3.1273259298721197 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2219", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of generate Work-in-Progress (WIP) Report process in production is to provide a detailed overview of ongoing production activities that are in progress but not yet completed. This report is crucial for manufacturing organizations to monitor and manage the status of work on the production floor. It helps in tracking the progress of manufacturing orders, assessing resource utilization, identifying bottlenecks, and ensuring that production schedules are being adhered to.", "Process_Group": "Procurement Reporting and Analytics", "Scope": "The scope of this process includes collecting and analyzing data related to work in progress on the production line. This may involve information on manufacturing orders, production schedules, machine utilization, labor allocation, and any issues affecting the production process. The scope could extend to evaluating WIP across different production lines, shifts, or products, offering a comprehensive view of the manufacturing operations.", "Outcome": "A detailed report that provides insights into the current state of production activities. This report helps production managers and decision-makers make informed decisions about resource allocation, identify areas for process improvement, and ensure that production goals are met efficiently.", "GUID": "47644cc8-5b9e-11ee-3781-0201b014c5b2", "name": "Generate Work-in-progress (WIP) report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.137806766296894, "y": 1.4318936877076411, "z": -3.8928355600232374 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2220", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process aims at generating a comprehensive document that provides details about the production orders within a specified timeframe. This report aims to offer insights into the production activities, resource utilization, and overall efficiency of the manufacturing process. It facilitates monitoring and analysis of production order data for informed decision-making.", "Process_Group": "Procurement Reporting and Analytics", "Scope": "This process involves collecting and organizing data related to production orders, including order numbers, quantities, production timelines, resource usage, and any associated costs. The scope may extend to analyzing performance metrics, identifying bottlenecks, and assessing adherence to production schedules. ", "Outcome": "A detailed report that offers insights into the performance and efficiency of the production orders. ", "GUID": "47644cc6-5b9e-11ee-3781-0201b014c5b2", "name": "Create production order report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.789694883260243, "y": 1.435215946843854, "z": -4.6516892299240205 }, "color": "#66CCFF", "size": 1.0 }, { "id": "2221", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This aims to examine and evaluate the bill of materials associated with a product or a range of products. The primary goal is to ensure accuracy, efficiency, and optimization in the use of materials and resources during the manufacturing or assembly process. BOM analysis helps in identifying potential improvements, cost-saving opportunities, and streamlining production processes.", "Process_Group": "Procurement Reporting and Analytics", "Scope": "This process involves a detailed examination of the bill of materials for a product or a group of related products. This includes scrutinizing the components, materials, quantities, and the hierarchical structure of the BOM. The analysis may extend to assessing the availability of materials, identifying alternative materials or suppliers, and ensuring that the BOM aligns with the current production requirements and specifications.", "Outcome": "A comprehensive report or set of recommendations. This document provides insights into the efficiency of the current bill of materials, highlights areas for improvement, and suggests potential changes to enhance production processes or reduce costs.", "GUID": "47644cca-5b9e-11ee-3781-0201b014c5b2", "name": "Perform bill of material (BOM) analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.2713061465859496, "y": 1.4385382059800667, "z": -1.5439497017884953 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8483", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This purpose of this process is to plan the costs associated with producing a product or service.", "Process_Group": "Product Cost Controlling", "Scope": "Involves executing the product cost planning process using the configured settings and data.", "Outcome": "Detailed cost plans for products, including direct and indirect costs.", "GUID": "69f835b0-c431-11ee-3781-0201b014c5b2", "name": "Perform product cost planning", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9190190646766738, "y": 1.441860465116279, "z": -2.3059414193355963 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8484", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process defines how materials are valued in the system, considering factors like standard price or moving average price.", "Process_Group": "Product Cost Controlling", "Scope": "Involves specifying the material valuation method and related parameters", "Outcome": "Material valuation settings that influence how material costs are determined.", "GUID": "69f835ae-c431-11ee-3781-0201b014c5b2", "name": "Set material valuation parameters", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.574702196786445, "y": 1.4451827242524917, "z": -3.0611939823969103 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8485", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process establishes rates for allocating overhead costs to products or services based on the activity types and cost centers.", "Process_Group": "Product Cost Controlling", "Scope": "Involves determining the appropriate rates for overhead allocation, considering factors like machine hours, labor hours, or other relevant metrics.", "Outcome": "Defined overhead rates that will be applied during cost calculations.", "GUID": "69f835a6-c431-11ee-3781-0201b014c5b2", "name": "Specify overhead rates for overhead cost centers", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.238302736013583, "y": 1.4485049833887045, "z": -3.8096450477606103 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8486", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process aims at categorizing and defining various activities that contribute to the cost of a product or service.", "Process_Group": "Product Cost Controlling", "Scope": "Involves specifying different types of activities, such as machine hours or setup activities, and assigning appropriate cost drivers.", "Outcome": "A list of defined activity types that will be used in cost allocation and calculation.", "GUID": "69f835a4-c431-11ee-3781-0201b014c5b2", "name": "Define activity types", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.90976744230711, "y": 1.4518272425249168, "z": -4.551232640403621 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8487", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process aims to review and analyze the results of the product costing run.", "Process_Group": "Product Cost Controlling", "Scope": "Involves examining the detailed cost breakdown, identifying variances, cost drivers, and ensuring accuracy in cost calculations.", "Outcome": "Insights into the cost distribution and identification of areas for potential cost optimization.", "GUID": "69f835b5-c431-11ee-3781-0201b014c5b2", "name": "Analyse costing run results", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.311155041392691, "y": 1.4551495016611296, "z": -1.5102557589463221 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8488", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To finalize and transfer calculated costs to other modules or processes within the ERP system.", "Process_Group": "Product Cost Controlling", "Scope": "Involves releasing the calculated costs for further use in areas like inventory valuation, profitability analysis, and financial reporting.", "Outcome": "Transferred and available costs for use in downstream processes.", "GUID": "69f835b8-c431-11ee-3781-0201b014c5b2", "name": "Release and transfer costs", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.978527841727464, "y": 1.4584717607973423, "z": -2.255089261982608 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8489", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures configuring of the parameters and settings for product costing runs.", "Process_Group": "Product Cost Controlling", "Scope": "Involves defining the rules and conditions for the costing process, such as valuation methods and precision settings.", "Outcome": "Configured costing variants that guide the system in calculating costs based on defined criteria.", "GUID": "69f835a8-c431-11ee-3781-0201b014c5b2", "name": "Set up costing variants", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.6536923184538295, "y": 1.4617940199335546, "z": -2.9929779616594474 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8490", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to structure and define the components of the costs associated with a product or service.", "Process_Group": "Product Cost Controlling", "Scope": "This process involves setting up the cost components, such as material costs, labor costs, and overhead costs, to establish a comprehensive understanding of the cost structure.", "Outcome": "A defined cost component structure that forms the basis for cost analysis and planning.", "GUID": "69f835a2-c431-11ee-3781-0201b014c5b2", "name": "Define cost component structure", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.3365940561111964, "y": 1.4651162790697674, "z": -3.7238609137189105 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8493", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "A debit memo serves as the document for the intercompany invoice in the service world. It is typically triggered by the time recording process on a project that is owned by another (selling) legal entity and consequently the provided services are charged with an IC invoice. A markup might be applied", "Process_Group": "Intercompany", "Scope": "Debit memo is created based on the time recordings. The intercompany invoice, with which the affiliated entity bills the selling entity, is created. The required accounting entries are created using information referencing previously issued debit memo.", "Outcome": "Intercompany invoice with reference to debit memo is created and issued.", "GUID": "f4d8f88c-bea7-11ee-3781-0201b014c5b2", "name": "Create IC invoice with reference to debit memo", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.027178215843165, "y": 1.4684385382059801, "z": -4.447677553267353 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8494", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The primary purpose of reviewing allocated costs in is to validate and ensure the accuracy of the cost allocation process. By conducting a thorough review, organizations aim to verify that costs have been distributed in accordance with established rules, methods, and strategic objectives. This process serves as a critical checkpoint to identify discrepancies, errors, or areas for improvement, ultimately contributing to the reliability of financial reporting, informed decision-making, and compliance with regulatory standards.", "Process_Group": "Overhead Cost Controlling", "Scope": "The scope of reviewing allocated costs encompasses a comprehensive examination of costs distributed among various entities and cost center within the organization. This evaluation includes a scrutiny of the allocation methods, rules, and data used in the process. Furthermore, the scope extends to ensuring that the allocated costs align with the organizations strategic goals and adhere to accounting standards and internal policies.", "Outcome": "The validation and verification of the accuracy and appropriateness of allocated costs within an organization. Precise financial reporting which supports informed decision-making and compliance with regulatory standards.", "GUID": "22f2f320-dd55-11ee-3781-0201b014c5b2", "name": "Review allocated costs", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.3501112965365616, "y": 1.471760797342193, "z": -1.4755336278663271 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8495", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to allocate indirect costs incurred by various activities within the organization to specific cost objects. By doing so, it enables a more accurate understanding of the true cost associated with producing goods or providing services. This information is vital for managerial decision-making, cost control, and performance evaluation.", "Process_Group": "Overhead Cost Controlling", "Scope": "This process involves identifying relevant cost drivers or allocation bases, determining the appropriate allocation methodology (such as activity-based costing), and executing the allocation within the system. It may encompass activities across different functional areas within the organization, including production, marketing, distribution, and support functions. Moreover, the scope may extend to allocating costs to various types of cost objects, such as products, services, projects, or customers.", "Outcome": "A more accurate representation of product or service costs, reflecting both direct and indirect expenses associated with their production or delivery.", "GUID": "d72ccbba-fd8c-11ee-3781-0201b014c5b2", "name": "Perform activity allocation to cost objects", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.0366896290097896, "y": 1.4750830564784052, "z": -2.202701830726067 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8496", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of reviewing and updating statistical key figures is to ensure that the system accurately reflects the non-financial metrics and indicators relevant to the organizations operations. Statistical key figures often represent quantities, counts, or ratios that are essential for performance monitoring, cost allocation, and decision-making processes. By regularly reviewing and updating these key figures, organizations can enhance the accuracy of their reporting and analysis, leading to better-informed decisions and improved operational efficiency.", "Process_Group": "Overhead Cost Controlling", "Scope": "The scope of this process encompasses the identification, review, and maintenance of statistical key figures within the system. It involves collaborating with relevant stakeholders across different departments to determine the appropriate statistical indicators to track and analyze. Additionally, the scope may include updating existing key figures based on changes in business processes, organizational structures, or reporting requirements.", "Outcome": "Statistical key figures reflect current business realities.", "GUID": "d72ccbb8-fd8c-11ee-3781-0201b014c5b2", "name": "Review and update statistical key figures", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.730875795642315, "y": 1.478405315614618, "z": -2.922724309402951 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8497", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to establish a foundational link (in the system) between intercompany costs and specific service materials. This linkage is essential as it serves as a prerequisite for the invoicing process. By ensuring that costs are accurately assigned to service materials, organizations create a structured foundation for determining prices associated with the provided services. The ultimate goal is to streamline the billing cycle and invoicing processing.", "Process_Group": "Intercompany", "Scope": "Compile all the months intercompany cost transfer postings and allocated them to service materials. The service material includes quantities and price of the services rendered. ", "Outcome": "Establish the foundational prerequisite for precise invoicing. Additionally, price determination ensures that invoiced amounts align seamlessly with agreed-upon pricing structures, contributing to a streamlined and trustworthy invoicing process.", "GUID": "22f2f317-dd55-11ee-3781-0201b014c5b2", "name": "Transfer IC allocations to service order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.4326138094608933, "y": 1.4817275747508307, "z": -3.635541560084051 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8498", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that all primary costs are correctly posted. This provides clarity on the types of costs to be distributed through cost allocation. ", "Process_Group": "Overhead Cost Controlling", "Scope": "The scope of this process encompasses recording various types of costs, including but not limited to: - General administrative costs - Marketing costs - Personnel costs - Logistical processing costs - Research and development (R&D) costs These costs are typically posted in the ERP system throughout the month according to predefined posting rules. The process can involve collaboration across departments and entities to gather comprehensive cost data and ensure alignment with organizational objectives.", "Outcome": "The establishment of a clear and comprehensive understanding of the costs earmarked for cost allocation.", "GUID": "45a10940-e21b-11ee-3781-0201b014c5b2", "name": "Record and categorize costs for allocation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.14184727013822, "y": 1.485049833887043, "z": -4.34109446923798 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8499", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The primary purpose of allocations is to ensure a fair and transparent distribution of costs incurred in one cost center to other related cost centers. This process enables organizations to allocate shared expenses, such as those incurred by centralized services or resources, accurately and efficiently.", "Process_Group": "Overhead Cost Controlling", "Scope": "Run the cost allocation process within the system, which will distribute costs according to the predefined rules (Typically based on statistical key figures). This process may involve both direct and indirect cost allocations from a sender to a receiver cost centers. The sender cost center is credited while the receiver cost center is debited accordingly.", "Outcome": "Available accurate financial reports reflecting the true distribution of costs within the organization, enhanced visibility into cost breakdowns for better resource management, and improved efficiency in intercompany reconciliation processes. ", "GUID": "22f2f315-dd55-11ee-3781-0201b014c5b2", "name": "Perform cost allocations", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.388148390441267, "y": 1.4883720930232558, "z": -1.4398069475159925 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8503", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "After the decision has been taken to sell an asset, it is necessary to find a buyer and negotiate the terms of the sale.", "Process_Group": "Customer Relationship Mgmt", "Scope": "The remaining value of the asset is defined and based on that, negotiations are conducted with several potential buyers. The sale agreement is made with the buyer offering the best terms and conditions.", "Outcome": "Buyer found and sale terms and conditions defined.", "GUID": "24393967-c0f3-11ee-3781-0201b014c5b2", "name": "Negotiate and determine buyer of asset", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.0934648297432963, "y": 1.4916943521594686, "z": -2.1488147911413567 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8504", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When a fixed asset is sold to an external or internal customer, the revenue earned must be recognized while the asset is removed from the asset portfolio.", "Process_Group": "Asset Accounting", "Scope": "Specify the customer account, revenue account and the asset to be retired. The asset to be retired could have been capitalized in a previous year or the current year. ", "Outcome": "Revenue from asset sale and net gain or loss on retired asset is realized", "GUID": "d437c08e-c0f8-11ee-3781-0201b014c5b2", "name": "Retire assets with revenue", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.806200081528005, "y": 1.4950166112956809, "z": -2.850480854598434 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8505", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Performing goods receipt for recycled materials involves the physical and administrative process of receiving recycled materials into a designated storage or processing area within a facility. This process typically includes verification of quantities, quality checks, documentation, and updating inventory systems.", "Process_Group": "Inbound Delivery Management", "Scope": "The process covers simplified goods receipt without inbound delivery.", "Outcome": "Recycled materials are received and available for use.", "GUID": "402bd4df-c0fc-11ee-3781-0201b014c5b2", "name": "Post goods receipt for recycled materials", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.526296625425675, "y": 1.4983388704318936, "z": -3.544747115029716 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8506", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of physically disassembling the asset into distinct parts. The distinct parts can then be reused for other purposes.", "Process_Group": "Plant Maintenance Asset Management", "Scope": "This encompasses identifying, disassembling, and repurposing various components of assets to either extend their lifecycle or create new assets. Only the parts that can be reused are recycled.", "Outcome": "Asset is disassembled.", "GUID": "402bd4ef-c0fc-11ee-3781-0201b014c5b2", "name": "Perform asset recycling", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.253696538035658, "y": 1.5016611295681064, "z": -4.231555950510812 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8513", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The goal of this process is to estimate the net value of the idea and its return on investment. It also ensures identification and quantification of the risks and opportunities involved in implementing the idea.", "Process_Group": "Portfolio Management", "Scope": "This involves conducting a detailed investigation of the products potential profitability. Factors to consider include manufacturing and operational costs, pricing, expected sales volume, market penetration and growth rates, and other financial metrics. This step provides a clear picture of the potential ROI and financial viability of the product, based on which the decision for product development is made.", "Outcome": "Comprehensive report with insights into whether the idea has the potential to generate profits and contribute positively to the financial health of the organization.", "GUID": "711d537e-dbcd-11ee-3781-0201b014c5b2", "name": "Conduct idea profitability analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.4252404272992165, "y": 1.5049833887043191, "z": -1.403100040764003 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8514", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that product and service ideas are screened in order to filter out the ones that meets business objectives and customer expectations based on defined criteria.", "Process_Group": "Portfolio Management", "Scope": "Once a pool of ideas has been generated, the next step is to screen them to filter out the feasible ones. This stage involves a preliminary assessment of the ideas, where they are evaluated in terms of their alignment with the companys vision and mission, market potential, feasibility in terms of resources and technology, competition, and other relevant factors. Some ideas can be immediately discarded, while others move on to the next stage. The ideas are evaluated based on criteria such as market demand, strategic fit, feasibility, and alignment with business goals.", "Outcome": "Documented selection of promising ideas that align with the screening criteria for further development.", "GUID": "711d5376-dbcd-11ee-3781-0201b014c5b2", "name": "Perform idea screening", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.1488147911413558, "y": 1.5083056478405314, "z": -2.093464829743297 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8515", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The innovation process starts with the generation of new ideas. This might include brainstorming sessions, surveys and feedback from customers, identifying pain points in the market, or through technological advancements. Ideas can come from various sources such as employees, partners, competitors and customers. At this stage, no idea is considered unfeasible", "Process_Group": "Portfolio Management", "Scope": "This step involves ideation sessions, market research, trend analysis, customer feedback, and competitor analysis to generate innovative and viable product or service ideas. Compilation of potential product or service ideas along with initial concept description and rationale.", "Outcome": "Documented pool of product and services ideas.", "GUID": "711d5371-dbcd-11ee-3781-0201b014c5b2", "name": "Generate ideas", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.8796138950319836, "y": 1.5116279069767442, "z": -2.7762967808825354 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8516", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The goal of this process to test the feasibility of the product idea. In this stage, the selected ideas are developed into a product concept.", "Process_Group": "Portfolio Management", "Scope": "This step involves creating concept prototypes or mockups to test with target customers or focus groups to gather feedback, validate assumptions, and assess market acceptance. They are then tested by conducting market research to understand consumer response to the product. This includes understanding consumer acceptance of the idea, their willingness to buy, projected demand, etc. Based on the results, the product concept might go through iterations to better suit market needs.", "Outcome": "Refined concept prototypes validated by stakeholders feedback, ready for further development.", "GUID": "711d537a-dbcd-11ee-3781-0201b014c5b2", "name": "Test concept", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.6175787243649813, "y": 1.514950166112957, "z": -3.4515393917818518 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8520", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes an automatic generation of the Purchase Requisition (PR) for direct standard services. The PR for direct standard services can be automatically generated by the system out of a process order, plant maintenance order, WBS element, quality inspection lot, etc.", "Process_Group": "Purchasing Direct", "Scope": "The system automatically generates the PR for externally provided services.", "Outcome": "PR for direct standard services is automatically generated.", "GUID": "79531a64-cc0b-11ee-3781-0201b014c5b2", "name": "Generate purchase requisition for standard services", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.362649872100859, "y": 1.5182724252491693, "z": -4.119136571353073 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8522", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves ensuring that contractual agreements meet organizational standards and comply with business requirements.", "Process_Group": "Sourcing Direct", "Scope": "Verifying that the contract terms are accurate, and the pricing and conditions meet the agreed-upon terms between the organization and the vendor. Checking for compliance with legal and regulatory requirements, and initiating the approval workflow, which may involve routing the contract for review by relevant stakeholders or departments.", "Outcome": "Contract approved.", "GUID": "f8039719-c1aa-11ee-3781-0201b014c5b2", "name": "Approve vendor contract - Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.4613621547014748, "y": 1.521594684385382, "z": -1.3654378978211579 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8523", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the centralized storage, organization, and retrieval of contract documents with a focus on efficiency, fostering transparency, ensuring compliance, and facilitating effective contract lifecycle management. Besides creating a contract as a structured document, such as value and quantity contracts, scheduling and rebates agreements etc., also the actual electronic version of the signed document is stored for reference.", "Process_Group": "Sourcing Direct", "Scope": "Uploading and categorizing contract documents within a document management system. Typical categories encompass contract type, vendor name, contract start date, and other metadata aligned with the organizations document management strategy. If there are alterations to an original document, a version control check may be necessary. Additionally, documents are interconnected with the respective contract and/or Purchase Order (PO) and business partner.", "Outcome": "Contract documents stored.", "GUID": "f803971b-c1aa-11ee-3781-0201b014c5b2", "name": "Store contract documents - Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.202701830726066, "y": 1.5249169435215948, "z": -2.03668962900979 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8524", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves creating a centralized source of information about materials and suppliers, facilitating automated procurement processes. The purchasing info record serves as a master data record that combines information about a specific material from a specific supplier.", "Process_Group": "Sourcing Direct", "Scope": "Specifying the material for which the Purchasing Info Record is being created. Entering essential information, such as the purchasing organization, plant, and relevant data specific to the vendor, like price, terms of payment, supplier material numbers and delivery conditions.", "Outcome": "Purchasing info record created.", "GUID": "f8039711-c1aa-11ee-3781-0201b014c5b2", "name": "Create purchasing info record", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.951067255732653, "y": 1.528239202657807, "z": -2.7002225930731245 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8526", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The aim of this process is to capture (in the system) the delivery schedule to ensure timely and efficient delivery of goods or services as per the terms outlined in the scheduling agreement.", "Process_Group": "Purchasing Direct", "Scope": "It encompasses monitoring delivery dates, quantities, and any changes or deviations from the original agreement. Communication between the buyer and supplier is crucial for addressing any issues and maintaining alignment with the agreed-upon schedule. ", "Outcome": "A well-maintained delivery schedule that facilitates smooth procurement operations, minimizes disruptions in the supply chain, and ensures timely fulfilment of orders", "GUID": "cab4d1b9-06c0-11ef-3781-0201b014c5b2", "name": "Maintain delivery schedule", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.706397961056126, "y": 1.5315614617940199, "z": -3.355981846535972 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8527", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The negotiation process aims to establish mutually beneficial terms between the buyer and supplier for the procurement of goods or services over a specified period. This involves discussions on pricing, quantities, delivery schedules, and other contractual conditions.", "Process_Group": "Purchasing Direct", "Scope": "Negotiations cover the terms and conditions of the scheduling agreement, including pricing mechanisms, quality standards, delivery locations, and any special requirements", "Outcome": "Agreed-upon terms of the scheduling agreement that serves as the foundation for future procurement transactions between the buyer and supplier.", "GUID": "cab4d1b1-06c0-11ef-3781-0201b014c5b2", "name": "Negotiate scheduling agreement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.468633096462691, "y": 1.5348837209302326, "z": -4.003912867333438 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8528", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The creation and approval of the scheduling agreement formalize the agreed-upon terms into a contractual document. This process ensures that all parties involved have a clear understanding of their roles, responsibilities, and obligations.", "Process_Group": "Purchasing Direct", "Scope": "Involves creating the scheduling agreement document based on the negotiated terms and obtaining the necessary approvals from relevant stakeholders within the buyers organization", "Outcome": "The scheduling agreement is created, approved, and ready for execution, providing a framework for the procurement of goods or services according to the specified terms and conditions.", "GUID": "cab4d1b5-06c0-11ef-3781-0201b014c5b2", "name": "Create and approve scheduling agreement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.496488980829723, "y": 1.5382059800664454, "z": -1.3268461592269154 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8529", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Releasing the scheduling agreement signals the buyers intent to procure the specified goods or services from the supplier. It initiates the procurement process and triggers the supplier to fulfill the order according to the terms outlined in the agreement.", "Process_Group": "Purchasing Direct", "Scope": "This process involves formally releasing the scheduling agreement to the supplier, confirming the details of the procurement request, and initiating the necessary actions to fulfill the order.", "Outcome": "The commencement of procurement activities as per the agreed-upon terms, facilitating the timely delivery of goods or services and ensuring alignment with organizational requirements and objectives.", "GUID": "cab4d1be-06c0-11ef-3781-0201b014c5b2", "name": "Release scheduling agreement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.255089261982607, "y": 1.5415282392026577, "z": -1.9785278417274648 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8530", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Quota arrangement maintenance aims to allocate specific quantities of goods or services to different departments, locations, or cost centers within the buyers organization as per the terms of the scheduling agreement.", "Process_Group": "Purchasing Direct", "Scope": "It involves managing and updating quota allocations, ensuring that the agreed-upon quantities are distributed appropriately and in accordance with organizational requirements.", "Outcome": "The effective management of quota arrangements, ensuring equitable distribution of resources within the buyers organization and optimizing procurement processes to meet operational needs.", "GUID": "cab4d1c1-06c0-11ef-3781-0201b014c5b2", "name": "Maintain quota arrangement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.020511517892643, "y": 1.5448504983388704, "z": -2.6223100827853827 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8534", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the centralized storage, organization, and retrieval of contract documents with a focus on efficiency, fostering transparency, ensuring compliance, and facilitating effective contract lifecycle management. This process might be even applicable in cases when there is no need of creating a structured document, such as value and quantity contracts, and rebates agreements etc. Thus, the actual electronic version of the signed document is stored for reference.", "Process_Group": "Sourcing Indirect", "Scope": "Uploading and categorizing contract documents within a document management system. Typical categories encompass contract type, vendor name, contract start date, and other metadata aligned with the organizations document management strategy. If there are alterations to an original document, a version control check may be necessary. Additionally, documents are interconnected with the respective contract and/or Purchase Order (PO) and business partner.", "Outcome": "Contract documents stored.", "GUID": "f8039733-c1aa-11ee-3781-0201b014c5b2", "name": "Store contract documents - Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.7926938670030164, "y": 1.5481727574750832, "z": -3.258139535255926 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8535", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves ensuring that contractual agreements meet organizational standards and comply with business requirements. Typically, there is no difference in approval workflows and procedures for direct and indirect materials and services.", "Process_Group": "Sourcing Indirect", "Scope": "Scope is the same as in direct materials and services.", "Outcome": "Contract approved.", "GUID": "f8039731-c1aa-11ee-3781-0201b014c5b2", "name": "Approve vendor contract - Indirect", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.571574057312731, "y": 1.5514950166112955, "z": -3.8859632832163014 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8537", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes updating and managing internal product or service catalogs. Catalogs typically contain information such as product descriptions, pricing, specifications, and other relevant details. Catalog entries often go through an approval process before they are made available for use. In the context of a vendor portal, it involves managing access and / or integration (punch out) with the suppliers portal. Catalogue entries and related commercial data is typically restricted and adjusted to the defined scope.", "Process_Group": "Purchasing Indirect", "Scope": "Maintaining the catalog involves adding new items, updating existing ones, and ensuring that the information is accurate and up-to-date. Formal approval might be required.", "Outcome": "Internal catalogue or vendor-hosted catalogue updated.", "GUID": "03793be1-bf80-11ee-3781-0201b014c5b2", "name": "Maintain and approve internal catalogue/vendor portal", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5305969911984545, "y": 1.5548172757475083, "z": -1.287351098393223 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8538", "text": "Process", "data": { "Advisory_Notes": "In case of aggregated demand, purchasing demand might be involved to ensure complete consolidation of needs.", "Type": "Business Process", "Description": "Certain indirect materials or services may be required by multiple departments, e.g. translation services. In such instances, aggregating the demand is employed to enhance purchasing power and negotiating leverage, thereby optimizing procurement outcomes.", "Process_Group": "Sourcing Indirect", "Scope": "Validating the demand for a specific product or service across various departments and consolidating the corresponding requests.", "Outcome": "Aggregated demand for a particular product or service captured.", "GUID": "037914d0-bf80-11ee-3781-0201b014c5b2", "name": "Aggregate demand for product or services", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.3059414193355954, "y": 1.558139534883721, "z": -1.9190190646766747 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8539", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "After the Purchase Requisition (PR) approval, an official Purchase Order (PO) for standard services is created from the PR. Since the POs for standard services are used for recurring and repeatable purchases, they are more standardized compared to the POs for one-time services. The PO for standard services is typically described by service materials or several item lines specifying individual activities related to one or multiple service materials.", "Process_Group": "Purchasing Direct", "Scope": "The PO is created based on the PR including task specifications and/or any other reference to the service being procured. Any additional data not provided within the PR has to be maintained.", "Outcome": "PO for standard services is created.", "GUID": "79531a62-cc0b-11ee-3781-0201b014c5b2", "name": "Convert purchase requisition for standard services to purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.0878994035769898, "y": 1.5614617940199333, "z": -2.5426122931719006 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8540", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "One-time services purchase orders are created for services that are not part of regular or recurring procurement. These services are often unique, non-repetitive, and may not have well-defined specifications. The PO includes details related to the service to be performed, such as a description of the service, quantity or duration, unit of measure (if applicable), and pricing. Since services may vary and are not part of routine procurement, the process allows for flexibility in specifying the details for a particular service engagement.", "Process_Group": "Purchasing Indirect", "Scope": "The PO is created based on the PR including reference to a statement of work, previously negotiated vendor proposal or other documents stating content and terms of the service. Any additional data not provided within the PR has to be maintained.", "Outcome": "PO for one-time services is created.", "GUID": "79531a60-cc0b-11ee-3781-0201b014c5b2", "name": "Convert purchase requisition for one-time services to purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.8764076916033496, "y": 1.564784053156146, "z": -3.158079069383538 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8551", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process describes the goods receipt process for products and by-products manufactured in production. After goods receipt, the system increases the stock of the goods at the relevant storage location.", "Process_Group": "Inbound Delivery Management", "Scope": "Co-products could be intermediate compounds or substances with different properties than the final product. By-products could be waste and impurities.", "Outcome": "Goods receipt posted", "GUID": "5e66c9d0-bf69-11ee-3781-0201b014c5b2", "name": "Perform goods receipt for co- and by-product", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.671402672027883, "y": 1.5681063122923589, "z": -3.7653681195562747 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8552", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Collect relevant data sources needed to perform transportation forecasts, such as historical transportation data, sales forecasts, production schedules, inventory levels, customer orders.", "Process_Group": "Transportation Management", "Scope": "Choose the relevant forecasting model (Time Series Analysis, Regression Analysis, Exponential Smoothing, Machine Learning Algorithm, Simulation Models,...) and evaluate the results.", "Outcome": "A detailed forecast of transportation requirements over a specified time horizon. ", "GUID": "faa677d0-e2ac-11ee-3781-0201b014c5b2", "name": "Get forecast on transportation requirements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5636629649360594, "y": 1.5714285714285716, "z": -1.2469796037174674 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8553", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The goal of this process is to ensure the accuracy and relevance of master data for lanes, facilitating efficient logistics operations and informed decision-making.", "Process_Group": "Transportation Management", "Scope": "This process encompasses the review, validation, and modification of essential lane data, including but not limited to origin, destination, transit times, carrier preferences, and cost structures.", "Outcome": "An updated and synchronized master dataset for lanes, reflecting current market conditions, operational requirements, and strategic objectives. ", "GUID": "faa69ee8-e2ac-11ee-3781-0201b014c5b2", "name": "Update master data for lanes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.355223682430332, "y": 1.574750830564784, "z": -1.8582038116738724 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8554", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process refers to the steps involved in ensuring that waste materials are collected from a particular location or delivered to a designated destination. Its purpose is to efficiently and effectively manage waste transportation while adhering to regulatory requirements and environmental standards.", "Process_Group": "Outbound Delivery Management", "Scope": "It covers confirming the scheduled time and location for the pick-up or delivery, verifying the type and quantity of waste to be collected or delivered, coordinating logistics such as packaging materials, transportation and personnel, and confirming the completion of the pick-up or delivery.", "Outcome": "Waste picked up or delivered.", "GUID": "28455064-cfdc-11ee-3781-0201b014c5b2", "name": "Confirm waste pick up", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.1531850348401784, "y": 1.5780730897009967, "z": -2.4611834828106463 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8555", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to manage and account for inventory items that are considered unusable, damaged, obsolete, or otherwise not fit for sale or consumption. This process allows organizations to accurately reflect the value of their inventory by adjusting the inventory levels and accounting for the loss or disposal of unusable items. It helps maintain accurate records and supports financial reporting by reflecting the actual state of the inventory.", "hasAssignment": true, "Process_Group": "Inventory Management", "Scope": "This process includes identifying and processing items that need to be scrapped. This may involve the identification of damaged goods, obsolete products, or items that have reached the end of their shelf life. The process includes recording the relevant information in the system, initiating the necessary approvals, and updating inventory records to reflect the reduction in quantity and value due to the scrapped items.", "Outcome": "An accurate and up-to-date representation of the organizations inventory. This includes adjusted inventory levels, updated valuation, and proper accounting for any losses associated with scrapping items.", "GUID": "e5143de0-bab5-11ee-3781-0201b014c5b2", "name": "Perform material scrapping", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9574824421462713, "y": 1.5813953488372094, "z": -3.055868570489246 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8557", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of dealing with potential buyers to find the suitable buyer for the waste and agree on a price at which the waste will be sold.", "Process_Group": "Sales Order Management", "Scope": "Determine the market value of the sellable waste and assess the potential buyers by considering factors such as credit risk and their compliance to health and safety legal requirements. Negotiate and agree on relevant terms such as pricing, quantity, quality, and any legal considerations.", "Outcome": "Waste is sold.", "GUID": "28455051-cfdc-11ee-3781-0201b014c5b2", "name": "Initiate waste sale", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.7680509768829005, "y": 1.5847176079734218, "z": -3.6422094780292396 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8558", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of assessing the economic value of waste materials. It aims to quantify the potential value that can be derived from waste materials before they are sold.", "Scope": "Determine the composition, quantity, and type of waste generated. For each type of waste material, the value can be determined using the information available in the material master records.", "Process_Group": "", "Outcome": "Value of waste is determined.", "GUID": "28452940-cfdc-11ee-3781-0201b014c5b2", "name": "Perform waste valuation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.5956643905936867, "y": 1.5880398671096345, "z": -1.205759160276744 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8559", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose is to ensure the safe and legal transportation of waste from its point of origin to its designated disposal or treatment facility. These documents typically include important information such as the type and quantity of waste being transported, its origin, destination, handling instructions, and any associated hazards or special handling requirements. These documents are necessary for regulatory compliance, and internal audit.", "Process_Group": "", "Scope": "This document includes essential information such as the waste type, quantity, origin, destination, transportation mode, and any regulatory compliance requirements. They are printed and distributed to relevant stakeholders, including waste generators, transporters, and disposal facilities. It serves as a legal record of the waste transportation process.", "Outcome": "Waste transportation document prepared.", "GUID": "11a6316c-da05-11ee-3781-0201b014c5b2", "name": "Prepare waste transportation document", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.4029024997024893, "y": 1.5913621262458473, "z": -1.7961234859896271 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8560", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "For waste sales, a sales order is created. This could be with or without reference to a customer order.", "Process_Group": "Sales Order Management", "Scope": "In the sales order, data about customer, material, order quantity, wish delivery date, and item price are provided.", "Outcome": "Sales order for waste is created", "GUID": "28455058-cfdc-11ee-3781-0201b014c5b2", "name": "Create sales order for waste", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.2163239649600106, "y": 1.5946843853820596, "z": -2.378079088765535 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8566", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of analyzing service performance is to evaluate how well the service delivery process is meeting established standards and objectives. ", "Process_Group": "Field Services", "Scope": "Analysis of service performance data, considering metrics such as response times, resolution rates, and customer satisfaction scores.", "Outcome": "A understanding of the effectiveness and efficiency of the service delivery process. ", "GUID": "bbcc8106-bab6-11ee-3781-0201b014c5b2", "name": "Analyze service performance", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.035862922613217, "y": 1.5980066445182723, "z": -2.9515776238947042 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8567", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is designed to identify service orders that are overdue or incomplete and take appropriate actions to address them. It ensures that service commitments are met within the specified timeframes.", "Process_Group": "Field Services", "Scope": "The scope involves analyzing service orders to identify those that are past due or incomplete. It may include investigating the root causes of delays and initiating corrective actions.", "Outcome": "The outcome is the timely completion of service orders, meeting customer expectations, and maintaining a high level of service performance.", "GUID": "bbcc8102-bab6-11ee-3781-0201b014c5b2", "name": "Assess overdue and incomplete service orders", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.861453173320384, "y": 1.601328903654485, "z": -3.5165712055371743 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8568", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of reviewing service contracts is to ensure that service agreements and contracts with customers are up to date, accurate, and aligned with business requirements. It involves assessing contract terms, service level agreements (SLAs), pricing, and other relevant details to guarantee compliance and customer satisfaction.", "Process_Group": "Field Services", "Scope": "The examination of all existing service contracts within the system. This may involve checking contract durations, terms and conditions, billing information, and any special clauses.", "Outcome": "An updated and accurate understanding of the current state of service contracts. It ensures that the organization is well-informed about its contractual obligations and can proactively address any issues or opportunities related to service agreements.", "GUID": "bbcc80f9-bab6-11ee-3781-0201b014c5b2", "name": "Review service contracts", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6265794814711305, "y": 1.6046511627906979, "z": -1.1637178311159058 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8569", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process aims to identify and address potential issues or situations that may impact service delivery. It involves verifying data, monitoring key performance indicators (KPIs), and initiating appropriate actions to prevent or mitigate adverse situations.", "Process_Group": "Field Services", "Scope": "Monitoring real-time data and system alerts to identify situations that require attention. It may involve collaboration with relevant stakeholders to address emerging issues promptly.", "Outcome": "The timely handling of situations that could impact service quality or disrupt operations.", "GUID": "bbcc80fd-bab6-11ee-3781-0201b014c5b2", "name": "Verify and initiate situation handling", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.4489454112201505, "y": 1.6079734219269102, "z": -1.7328203521611147 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8570", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To ensure an accurate period end closing, all open items on the vendors accounts at the end of the period must be valid and without any outstanding open items.", "Process_Group": "Purchasing Indirect", "Scope": "It involves checking open Purchase Orders (POs) for which Goods Receipts (GRs) have not yet been posted. Invoices must be validated and any discrepancies between the purchase order, goods receipt, and invoice must be resolved. All accrued transactions must be recorded in the period in which the transactions occurred. Additionally, all open items on the vendors account must be validated.", "Outcome": "Purchasing transactions posted in correct accounting period.", "GUID": "53b68241-cc94-11ee-3781-0201b014c5b2", "name": "Conduct period end closing purchasing - Direct", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.277273208697123, "y": 1.611295681063123, "z": -2.2933556888446383 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8571", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When it has been established that customers are incapable of paying their debt owed to a company, the company must make provisions for such debts by writing them off. Writing off a bad debt means the amount owed by the customer is partially reduced or completely cancelled depending on the customers financial situation. Bad debts have a negative impact on a companys capital.", "Process_Group": "Accounts Receivable", "Scope": "Determine and maintain in the master records, the threshold for overdue days and corresponding applicable rate. Check and perform periodic reporting to ensure all provisions for a period are posted. If provisioning is performed at period-end the adjustment postings need to be reversed at the beginning of the new period to ensure accurate financial records for the new period", "Outcome": "Provisions made for bad debts.", "GUID": "ce7c00d0-dc58-11ee-3781-0201b014c5b2", "name": "Process doubtful receivables", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.111495771255623, "y": 1.6146179401993357, "z": -2.8452772312987595 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8572", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of creating guidelines and procedures for extending credit to other companies within the same corporate group or organization. It aims to establish clear criteria for evaluating creditworthiness, setting credit limits, terms of payment, and procedures for monitoring and managing credit risk. It also covers periodic reviews and updates to ensure it adapts to changing business conditions.", "Process_Group": "Intercompany", "Scope": "It involves identifying the types of intercompany transactions occurring within the organization, gathering relevant information such as financial statements of all entities, industry benchmarks, etc. Based on the gathered information, a draft credit policy is formulated. After review and approval sessions, the final policy is formulated. This is a cross-functional collaboration between executive management and other functions such as finance, legal, and credit to ensure the policy aligns with the companys financial objectives and also legal requirements. ", "Outcome": "Intercompany credit policy is established and communicated to all relevant stakeholders", "GUID": "0ba827e1-cc00-11ee-3781-0201b014c5b2", "name": "Develop and maintain intercompany credit policy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.951545672746669, "y": 1.617940199335548, "z": -3.3885388371248943 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8573", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "In this process, based on agreed loan contract, one legal entity provides credit facility to another legal entity who belongs to the same corporate group. This gives rise to interest income to the lending entity and interest expense to the borrowing entity. The loan is monitored until maturity when the loan accounts are closed and the balances are removed from the balance sheet with only the interest expense and interest income reported on the P&L accounts of the respective entities.", "Process_Group": "Intercompany", "Scope": "After the lender receives the loan application from the borrower, it performs credit checks to determine the right amount of loan, interest rate and tenor. After an agreement is reached, the final loan contract is created and posted in both systems. The principal is booked on the respective GL accounts. As repayment occurs, the outstanding loan balance reduces until the full amount (principal plus interest) is repaid.", "Outcome": "Loan amount is provided to intercompany borrower and loan monitoring is triggered. ", "GUID": "0ba827e3-cc00-11ee-3781-0201b014c5b2", "name": "Execute intercompany loan processing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6563871904493035, "y": 1.6212624584717608, "z": -1.12088423814213 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8574", "text": "Process", "data": { "Advisory_Notes": "Cross-border intercompany transactions must be reconciled in the transaction currency to avoid foreign currency differences. ", "Type": "Business Process", "Description": "This is the process of identifying, verifying, and matching financial transactions that occur between different entities within a corporate group to ensure the ledger balances in the entities are accurate and complete. It may lead to adjustment postings. Reconciling intercompany transactions is key to ensuring the integrity of a corporate groups financial statement by avoiding double entries across the entities. ", "Process_Group": "Intercompany", "Scope": "Intercompany reconciliation can be performed on all account types (GL accounts, intercompany customer, or intercompany vendor accounts). The process involves the identification of accounts or transactions to be reconciled, verification of source documents, rectification of discrepancies and finally review and approval to confirm accuracy of account balances.", "Outcome": "Balances on all intercompany accounts are accurate and complete.", "GUID": "0ba800d0-cc00-11ee-3781-0201b014c5b2", "name": "Reconcile intercompany transactions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.4933210707826623, "y": 1.6245847176079735, "z": -1.6683375072182485 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8575", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that product costs are seamlessly integrated with the group ledger, which is a key component of financial accounting.", "Process_Group": "Intercompany", "Scope": "This processes involves managing product costing in the context of parallel ledgers to allow handling of multiple accounting principles simultaneously by: - Conducting ledger-specific valuations in Asset Accounting, General Ledger, and Controlling - Execution of costing run to set standard costs in group view - Performing costing run to calculate actual costs in group view", "Outcome": "Product costs are integrated seamlessly with the group ledger ", "GUID": "6455e350-baa3-11ee-3781-0201b014c5b2", "name": "Perform actual costing for group ledger", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.335991271559511, "y": 1.6279069767441858, "z": -2.207070963081785 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8576", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of transferring funds from accounts held by subsidiaries to a central account. It enables companies to manage their cash positions and optimize the use of surplus funds. In some cases cash pooling can be used to facilitate intercompany lending and borrowing transactions. For example, if a company decides that all account balances of its subsidiaries as at the end of a day or a period should be transferred to a central account, those with deficit account balances can either borrow from other subsidiaries or the parent company. The parent company may choose to lend from the pooled funds.", "Process_Group": "Intercompany", "Scope": "First, the cash pool master data should be created. The cash pool is the master account where cash is centralised. After creating the cash pool master data, the relevant bank accounts are assigned to the cash pool in a hierarchical structure. Minimum and maximum account balances required for pooling cash are maintained for each bank account assigned to the cash pool. In cash pooling, funds move from the assigned bank accounts to the master account and vice versa depending on whether the assigned bank accounts are in surplus or deficit respectively.", "Outcome": "Funds are transferred from diverse accounts to a central account.", "GUID": "5cab75c0-d4d4-11ee-3781-0201b014c5b2", "name": "Perform cash pooling", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.18432949692378, "y": 1.6312292358803986, "z": -2.737039762439264 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8577", "text": "Process", "data": { "Advisory_Notes": "If the transaction is relevant for different accounting principles, the transaction is posted to multiple assigned ledgers with the use of parallel ledger accounting. In S/4Hana, parallel accounting enables the valuation of transactions based on specific principles such as local GAAP, US GAAP and IFRS.", "Type": "Business Process", "Description": "This is the trading of financial instruments such foreign exchange, money market, and capital market securities between legal entities within the same corporate group.", "Process_Group": "Intercompany", "Scope": "When the deal is agreed by both parties, one party creates the trade deal. If both parties are in the same system, this activity leads to the automatic creation of mirror transaction in the other partys system. The counterparty checks the mirror transaction for accuracy. On settlement date, the trade is settled after the deal has been confirmed by back office teams and postings are made to the relevant GL accounts. ", "Outcome": "Financial instruments are traded between entities within the same corporate group.", "GUID": "9193c220-cfc9-11ee-3781-0201b014c5b2", "name": "Execute intercompany exchange of financial instruments", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.038267139823252, "y": 1.6345514950166113, "z": -3.258199537747378 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8578", "text": "Process", "data": { "Advisory_Notes": "Since this can be a time consuming and costly process especially if it is done manually, it is advisable for companies to deploy machine learning technology to streamline the process. Machine learning technology is able to identify the root cause of mismatches existing in the GR/IR account, propose next steps, prioritize actions, and even propose the responsible department / person who needs to be contacted to resolve the difference.", "Type": "Business Process", "Description": "The process of reconciling open items on GR/IR account by matching goods receipt postings with their corresponding invoice receipt postings. Due to reasons such as Invoice or goods receipt is missing, amounts mismatch, creating purchase order with an outdated price list, and delivery costs were posted on the wrong GR/IR account, the GR/IR account will have some uncleared items.", "Process_Group": "General Ledger", "Scope": "Review all open items and liaise with the responsible units in procurement and accounts payable to resolve the open items. If the vendor has not yet provided invoice for goods received, the outstanding item should be treated as a liability in the balance sheet and if invoice has been received but goods are yet to be received from the vendor the outstanding item should be treated as an asset in the balance sheet.", "Outcome": "Open items on GR/IR account are cleared and unresolved items are carried forward", "GUID": "c0332081-fc0b-11ee-3781-0201b014c5b2", "name": "Reconcile GR/IR account", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.6850672243191998, "y": 1.637873754152824, "z": -1.0772875426390058 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8579", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of performing non-physical goods issue in the context of direct shipment from a vendor to a customer is to manage the logistical and administrative aspects of these transactions efficiently. This process ensures that when goods are shipped directly from a vendor to a customer without physically passing through the organizations inventory, proper documentation and controls are in place.", "Process_Group": "Outbound Delivery Management", "hasAssignment": true, "Scope": "This process entails recording the goods issue within the organizations systems when drop shipments occur from a vendor directly to a customer of the organization. It involves validating the transaction, updating inventory records, and coordinating with relevant stakeholders to ensure accurate documentation of the goods issue.", "Outcome": "The outcome of this process is the proper recording and documentation of goods issued within the organizations systems for drop shipments from vendors to customers.", "GUID": "1a947eae-f8c1-11ee-3781-0201b014c5b2", "name": "Perform non-physical goods issue", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.535999267261256, "y": 1.6411960132890364, "z": -1.6027188513430457 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8581", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to facilitate the efficient modification and adaptation of highly individualized materials (products) for sales, procurement and manufacturing. Leveraging advanced configurability features, this process streamlines the review and implementation of requested changes, ensuring accurate representation and management of product specifications and attributes. This enables businesses to maintain accurate and up-to-date representations of configurable materials, supporting continuous improvement and responsiveness to evolving customer requirements.", "Process_Group": "Material and Product Master Data", "Scope": "Change configurable material encompasses initiating and processing change requests for modifying and updating product specifications, attributes, and variants within the ERP system. This includes evaluating and implementing requested changes while adhering to established rules, dependencies, and constraints to ensure consistency and accuracy in product design. Collaboration across departments is facilitated to optimize the entire product lifecycle within the integrated master data framework, ensuring seamless adaptation to changing market demands.", "Outcome": "Successful implementation of approved changes to configurable material master data within the ERP system. ", "GUID": "45a13054-e21b-11ee-3781-0201b014c5b2", "name": "Change configurable material", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.392438178052147, "y": 1.6445182724252492, "z": -2.1192836544677616 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8582", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process enables businesses to efficiently define and introduce customizable service materials for sales, purchasing and manufacturing. Leveraging advanced configurability features, this process streamlines the initial request and creation of service materials, ensuring accurate representation and management of service specifications within the ERP system. ", "Process_Group": "Material and Product Master Data", "Scope": "The scope encompasses the initiation and management of requests for defining and configuring service specifications, attributes, and options. This includes capturing essential information such as service descriptions, pricing details, service level agreements (SLAs), and any other relevant metadata within the ERP system. ", "Outcome": "Available and up to date customizable service offerings within the ERP system.", "GUID": "45a13056-e21b-11ee-3781-0201b014c5b2", "name": "Create configurable service material", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.25431451412226, "y": 1.647840531561462, "z": -2.6269389058234074 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8583", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Change configurable service material process facilitates efficient modifications and adaptations of customizable service materials for sales, purchasing and manufacturing. Leveraging advanced configurability features, this process ensures streamlined review, approval, and implementation of requested changes to service specifications, attributes, and options. By maintaining accurate representation and management of modified service materials, this process enables businesses to adapt to evolving customer requirements while preserving operational efficiency and competitiveness.", "Process_Group": "Material and Product Master Data", "Scope": "The scope of the change configurable service material process encompasses initiating, reviewing, and processing change requests to modify and update existing configurable service material within the ERP system. ", "Outcome": "Successful implementation of approved changes to configurable service material master data within the ERP system. ", "GUID": "45a1305a-e21b-11ee-3781-0201b014c5b2", "name": "Change configurable service material", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.121558534224077, "y": 1.6511627906976742, "z": -3.125642042927585 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8584", "text": "Process", "data": { "Advisory_Notes": "Configurable materials creating can also be used in sales of kits scenario", "Type": "Business Process", "Description": "The purpose of this process is to facilitate the request and efficient creation of highly individualized materials (products) for sales, procurement and manufacturing. Leveraging advanced configurability features, this process streamlines the initial request, ensuring accurate representation and management of product specifications and attributes before creation within the system. This enables businesses to maintain accurate and up-to-date representations of configurable materials, supporting efficient product innovation, streamlined procurement, and enhanced customer satisfaction based on requests processed before material creation.", "Process_Group": "Material and Product Master Data", "Scope": "The scope encompasses initiating and processing requests for defining and configuring product specifications, attributes, and variants. This includes establishing rules, dependencies, and constraints to ensure consistency and accuracy in product design. Collaboration across departments is facilitated to optimize the entire product lifecycle within the integrated master data framework.", "Outcome": "Available and up to date customizable product offerings within the ERP system.", "GUID": "45a13052-e21b-11ee-3781-0201b014c5b2", "name": "Create configurable material", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.712600057597596, "y": 1.654485049833887, "z": -1.0329574254134153 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8616", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Reclassification of receivables and payables is necessary to ensure accurate financial reporting. It is important for providing transparency and clarity to stakeholders regarding the companys financial position and liquidity. Additionally, it ensures that financial statements accurately reflect the timing and nature of the companys obligations and assets.", "Process_Group": "General Ledger", "Scope": "This involves the review of current balances in both sub-ledgers to identify discrepancies, misclassifications, or accounts that need to be reallocated based on updated information such as payment terms, aging schedules, or changes in vendor/customer status. The team may analyze outstanding invoices, payment histories, or contractual agreements to determine which balances should be reclassified. Once the relevant accounts are identified, journal entries are created in the system to transfer the amounts from one account to another, ensuring the correct classification. These journal entries are reviewed for accuracy and compliance with accounting policies, and once approved, they are posted to the general ledger. The financial statements are then updated to reflect the changes. The reclassification process may be carried out manually, with the use of spreadsheets, or through automated system processes, depending on the organizations practices and the complexity of the reclassification needed. Finally, the updated balances are verified, and the financial reports are adjusted accordingly, ensuring that the companys financial position is accurately represented.", "Outcome": "Accounts receivable and accounts payable balances are accurately reported in the balance sheet.", "GUID": "e21333ee-9db7-11ef-3781-0201b014c5b2", "name": "Reclassify accounts receivable and accounts payable balances", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.576950945166906, "y": 1.6578073089700998, "z": -1.5360090579822083 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8625", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of identifying and matching financial transactions that occur between different legal entities within the corporate group to ensure that the financial records in all the involved legal entities are accurate and balanced.", "Process_Group": "Intercompany", "Scope": "This process usually involves using a centralized reconciliation tool or software that pulls in financial data from each entity to streamline the process. The matching step entails aligning the transactions to ensure that both sides of each intercompany relationship have recorded them consistently in terms of amount, currency, and timing. Any mismatches or differences are flagged and require investigation, often involving communication between the relevant entities to understand the cause of the discrepancies. Once all differences have been identified and investigated, adjustments or reclassifications are made as necessary to ensure the intercompany accounts match. Finally, after all discrepancies are resolved, the reconciled balances are confirmed, and these entries are ready for consolidation.", "Outcome": "Intercompany balances are reconciled.", "GUID": "0ee64a70-a03c-11ef-3781-0201b014c5b2", "name": "Conduct intercompany matching and reconciliation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.446575498892458, "y": 1.661129568106312, "z": -2.0300535289578456 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8628", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of determining the true and fair value of an asset. The purpose is to determine the value of the asset based on the specific purpose of valuation which could be for external reporting, commercial sales, or internal controlling.", "Process_Group": "Asset Accounting", "Scope": "This involves different valuation methods depending on the type of asset and accounting principles. It is important that the valuation method complies with international and local GAAP. ", "Outcome": "True and fair value of asset is determined", "GUID": "c5954615-8b9f-11ef-3781-0201b014c5b2", "name": "Perform asset valuation", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.321403176767876, "y": 1.6644518272425248, "z": -2.515049618560339 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8640", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This indicates the intention of the selling entity to issue a credit or debit memo to the buying entity", "Process_Group": "Billing, Rebates and Commissions", "Scope": "Information about material, price, quantity and reason for requesting credit or debit memo is defined. The request can be created with reference to either intercompany sales order or invoice.", "Outcome": "Intercompany credit or debit memo request created.", "GUID": "abe79147-9845-11ef-3781-0201b014c5b2", "name": "Create intercompany credit / debit memo request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.201363150830481, "y": 1.6677740863787376, "z": -2.990956598344885 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8643", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This involves the transfer of funds between entities within the same corporate group, typically when one subsidiary pays another for goods or services received.", "Process_Group": "Intercompany", "Scope": "After validating the intercompany billing document, the buying entity initiates the payment process. Once the payment is approved, it is executed through the companys banking system, transferring the funds to the receiving companys bank account. After the payment is completed, both entities update their accounting records to reflect the transaction, ensuring that intercompany accounts payable and accounts receivable are accurately recorded.", "Outcome": "Intercompany accounts payable balance reduced or updated.", "GUID": "6a98dee7-984a-11ef-3781-0201b014c5b2", "name": "Process intercompany outgoing payment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7389669458200767, "y": 1.6710963455149503, "z": -0.9879240665887202 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8656", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Once the request is approved, the billing block is removed making it possible for the credit or debit memo document to be created.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "If the request is accepted, the system automatically removes the billing block but if the request is rejected the billing block is not removed.", "Outcome": "Billing block removed.", "GUID": "abe7914f-9845-11ef-3781-0201b014c5b2", "name": "Remove billing block", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.6161482244314227, "y": 1.6744186046511627, "z": -1.4682535434332566 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8657", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves the receipt of payments from an intercompany entity, typically when one company within a corporate group provides goods or services to another company in the same group.", "Process_Group": "Intercompany", "Scope": "After the payment is received, it is essential to reconcile the payment against the outstanding billing document to ensure accurate financial records. This reconciliation process involves matching the incoming payment with the respective accounts receivable entry, verifying that the payment amount aligns with the billing document.", "Outcome": "Intercompany accounts payable balance reduced or updated.", "GUID": "6a98dee9-984a-11ef-3781-0201b014c5b2", "name": "Process intercompany incoming payment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.4983663771731397, "y": 1.6777408637873754, "z": -1.9394413347829014 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8658", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To ensure accurate records of intercompany transaction and facilitate intercompany matching and reconciliation process, the intercompany credit or debit memo is posted in the buying entitys books via a medium such as IDOC.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "Once a credit or debit memo is issued in the vendors (selling entitys) system, it triggers an automatic posting in the buying entitys system. This creates a debit adjustment to the accounts payable for the buying entity.", "Outcome": "Intercompany credit or debit memo received and posted.", "GUID": "6a98dee4-984a-11ef-3781-0201b014c5b2", "name": "Receive and post intercompany credit / debit memo", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.3855498106273725, "y": 1.6810631229235882, "z": -2.4014480753300123 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8659", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Once the credit or debit memo request is created it has to be approved before the billing block can be removed.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "Based on a workflow that defines different values to be approved by responsible roles, the request to process credit or debit memo is approved or rejected. If the request is rejected, the reason for rejection should be provided.", "Outcome": "Intercompany credit or debit memo request approved.", "GUID": "abe7914c-9845-11ef-3781-0201b014c5b2", "name": "Approve intercompany credit /debit memo request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.277626658336239, "y": 1.6843853820598005, "z": -2.854234898395483 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8660", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The intercompany credit or debit memo is created to confirm a reduction or increase in the intercompany accounts receivable balance.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "Once the decision is made to compensate or request additional payment from the the buying entity, the credit or debit memo is created. The appropriate sales tax is also calculated along with any shipping charges that are being credited or debited to the buying entity. In case multiple credit or debit memos are to be created, this can be done using a batch job.", "Outcome": "Credit or debit memo is created and sent to the buying entity.", "GUID": "6a98dee1-984a-11ef-3781-0201b014c5b2", "name": "Create and post intercompany credit / debit memo", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.7641499383023436, "y": 1.6877076411960132, "z": -0.9422181250580128 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8662", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of categorizing all the financial accounts based on their nature, such as assets, liabilities, equity, primary income, or expenses. By doing so, companies can produce meaningful financial statements and manage transactions effectively.", "Process_Group": "FICO Master Data", "Scope": "General ledger accounts are classified into any or all of the following types of accounts depending on the companys operations: 1. Reconciliation 2. Balance sheet 3. Primary cost or revenue 4. Secondary cost 5. Non-operating cost or income.", "Outcome": "GL account classification completed.", "GUID": "a4390f21-9de1-11ef-3781-0201b014c5b2", "name": "Maintain General Ledger account types", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.653564419388319, "y": 1.691029900332226, "z": -1.3994984359249323 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8663", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of grouping accounts for each type of account to facilitate financial reporting and analysis. This grouping allows similar accounts, such as foreign, domestic, one-time, and payroll accounts, to be organized under broader categories. This enhances the clarity and accuracy of financial reports, aiding in efficient data retrieval and consistent financial statement presentation.", "Process_Group": "FICO Master Data", "Scope": "The account group determines the length of account number assigned to a GL account and controls account data that need to be captured in the company code segment of the GL account. ", "Outcome": "GL accounts are grouped.", "GUID": "a4390f23-9de1-11ef-3781-0201b014c5b2", "name": "Maintain General Ledger account groups", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.547775553454484, "y": 1.6943521594684388, "z": -1.8475087610917378 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8664", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process determines the estimated rebates owed to customers based on the terms outlined in their rebate agreements. Once the accrual amount is calculated, it is posted in the financial accounting system as an accrued liability, which recognizes the companys obligation to pay out the rebate in the future. This posting is typically made at the end of an accounting period to ensure financial statements accurately reflect liabilities.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "The amount of rebate accrued, is determined based on the terms and conditions captured in the rebate agreement. The value of sales is multiplied by an accrual percentage as at the end of the accounting period to calculate the accrued rebate expense.", "Outcome": "Rebate accruals posted.", "GUID": "2fc20aba-9856-11ef-3781-0201b014c5b2", "name": "Calculate and post rebate accruals", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.446710744412593, "y": 1.697674418604651, "z": -2.286211616523194 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8665", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to enable the processing of goods receipt into the transit plant which is a virtual storage location.", "Process_Group": "Inbound Delivery Management", "Scope": "This type of inbound delivery can be created with reference to an outbound delivery with stock in transit in case of intercompany stock transfers or with reference to the external vendors advanced shipping notification. ", "Outcome": "Inbound delivery for valuated stock in transit is created.", "GUID": "1fb0f9de-8d65-11ef-3781-0201b014c5b2", "name": "Create inbound delivery for stock in transit", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.35029713623654, "y": 1.7009966777408638, "z": -2.7155700237664813 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8668", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to validate and authorize the return of goods to the supplier. The approval process ensures that returns are valid, appropriately documented, and compliant with company policies.", "Process_Group": "Vendor Returns", "Scope": "The return purchase order is reviewed by the responsible role to ensure all information is accurate, including product details, quantities, return reasons, and any applicable terms for returns. Approval workflow is normally used to streamline the approval process.", "Outcome": "Return purchase order approved and issued to supplier.", "GUID": "e34ca1b2-983a-11ef-3781-0201b014c5b2", "name": "Approve return purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.788131890361116, "y": 1.7043189368770766, "z": -0.8958707176114095 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8670", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to record costs associated with assets that are still under construction. It provides transparency on the costs associated with these type of assets and ensures the right cost of asset is finally capitalized.", "Process_Group": "Asset Accounting", "Scope": "After the project is released, asset under construction is automatically created.", "Outcome": "Asset under construction created.", "GUID": "ee965ee0-985c-11ef-3781-0201b014c5b2", "name": "Create asset under construction (AUC)", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.689174056940517, "y": 1.707641196013289, "z": -1.3297905442129145 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8671", "text": "Process", "data": { "Advisory_Notes": "In the case of statistical goods movement, this process enables the warehouse team to record results of material inspection performed by the vendor.", "Type": "Business Process", "Description": "Outbound delivery for returns purchase order is needed to process the return of goods to the vendor. This can be used to process both physical and statistical outbound goods movement.", "Process_Group": "Outbound Delivery Management", "Scope": "This process includes generating an outbound delivery document to formally track the physical or non-physical movement of the goods back to the supplier, ensuring proper documentation and inventory adjustments. The logistics team is involved in organizing and executing the transportation of the returned goods if physical goods movement is required.", "Outcome": "Outbound delivery for goods return is created and or statistical goods issue is posted.", "GUID": "612b4281-982d-11ef-3781-0201b014c5b2", "name": "Create outbound delivery for return purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.594769389769153, "y": 1.7109634551495017, "z": -1.7543183959528874 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8673", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is to manage and document returns between companies within a corporate group that operate as distinct entities. When goods are returned to the supplying company by the receiving company due to defects, overstock, or incorrect items, this process ensures that the return transaction is properly recorded. It facilitates transparency and accountability between the involved parties, aligning with inventory and financial tracking in a controlled and compliant manner.", "Process_Group": "Intercompany Supply Chain Operations", "Scope": "This covers the creation of a purchase order that records the return of goods to the intercompany supplier, coordinating with logistics to arrange for the return shipment. These information are captured when performing this process: 1. Intercompany vendor 2. Material 3. Quantity 4. Deliver date 5. Net price ", "Outcome": "Intercompany return purchase order is approved for further processing.", "GUID": "abe79125-9845-11ef-3781-0201b014c5b2", "name": "Create intercompany return purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.504844339512095, "y": 1.7142857142857144, "z": -2.1694186955877917 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8674", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process enables the reversal of goods or services sold by one legal entity to another in the same corporate group. This serves as an essential mechanism for reversing the original sales transaction, allowing the supplying company to accept the return, adjust inventory, and update financial records.", "Process_Group": "Intercompany Supply Chain Operations", "Scope": "This is often created after a return purchase order has been received from the buying company. This covers all activities required to handle the return of goods between affiliated entities within the same corporate structure. This includes identifying return reasons, creating the return order, which enables smooth coordination with logistics for the return shipment, and ensures accurate financial and inventory adjustments. ", "Outcome": "Intercompany return sales order is created triggering the inbound processes.", "GUID": "abe7912c-9845-11ef-3781-0201b014c5b2", "name": "Create intercompany return sales order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.419325110175686, "y": 1.7176079734219267, "z": -2.575056378066175 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8675", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of settling indirect taxes is to ensure accurate calculation and timely payment of indirect taxes to tax authorities. ", "Process_Group": "Tax Accounting", "Scope": "This involves gathering transaction data from sales, purchases, and other relevant financial records to determine the tax liabilities. Based on the data accurate calculation of tax amounts based on applicable rates and regulations is performed. The calculated amounts are verified to ensure compliance. Finally tax payment files are prepared and payments are scheduled to meet deadlines set by tax authorities.", "Outcome": "Indirect taxes paid.", "GUID": "a2750f35-a0da-11ef-3781-0201b014c5b2", "name": "Settle indirect taxes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8108964749862928, "y": 1.7209302325581395, "z": -0.8489133977516312 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8676", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of declaring indirect taxes is to ensure that the company complies with tax laws by accurately reporting on indirect taxes, thereby contributing to government revenue and maintaining fiscal stability.", "Process_Group": "Tax Accounting", "Scope": "This involves the declaration of all types of indirect tax reports such as VAT, Intrastat, EC Sales List (ESL), and other regional declarations via web portals and various applications. In other cases, submission of reimbursements in case of VAT refunds is also required.", "Outcome": "Indirect tax report submitted to tax authorities.", "GUID": "a2750f31-a0da-11ef-3781-0201b014c5b2", "name": "Declare indirect taxes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.7229528939025416, "y": 1.7242524916943522, "z": -1.259177325712218 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8678", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of recording the receipt of excess amount paid in taxes to the tax authority.", "Process_Group": "Tax Accounting", "Scope": "After filing a tax return, the tax authority issues a refund in case actual amount of tax paid exceeds the tax liability. The tax authority reviews the tax return for accuracy and compliance, sometimes requesting additional documentation. Once validated, the refund amount is calculated and then disbursed to the company (taxpayer), either via direct deposit or a mailed check, concluding the process.", "Outcome": "Tax expense account is credited.", "GUID": "a2750f33-a0da-11ef-3781-0201b014c5b2", "name": "Process tax refund", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.6393158925230393, "y": 1.727574750830565, "z": -1.6599336837443939 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8723", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process ensures that changes in tax amount arising from differences between book income and taxable income are properly accounted for as tax assets or tax liabilities. These differences arise because some items are recognized in different periods for financial accounting and tax purposes. With temporary difference, the difference between book income and taxable income will eventually reverse unlike with permanent difference.", "Process_Group": "Tax Accounting", "Scope": "Financial transactions such as depreciation, revenue recognition, and tax-exempt income that lead to timing differences should be identified. Then the difference between book income and taxable income is calculated and posted as temporary or permanent difference. If book income exceeds taxable income then deferred tax liability is posted and vice versa for deferred tax asset after validating the calculated difference. ", "Outcome": "Deferred tax asset or liability determined.", "GUID": "a274e820-a0da-11ef-3781-0201b014c5b2", "name": "Calculate permanent and temporary tax differences", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.559911018338868, "y": 1.7308970099667773, "z": -2.0511488256174357 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8724", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of calculating and capitalizing the right of use of the asset. The right of use asset represents the economic benefit the lessee enjoys while using the leased item during the lease period. Periodically the value is depreciated over the useful life of the leased asset.n asset in the balance sheet. The right of use asset represents the economic benefit the lessee enjoys while using the leased item during the lease period. Periodically the value is depreciated over the useful life of the leased asset.", "Process_Group": "Asset Accounting", "Scope": "This amount is calculated based on the present value of the future repayments during the lease period and other costs such as advanced payments before commencement date, incentives received or to be received, initial direct cost, and estimated costs to be incurred.", "Outcome": "Value of right of use of the leased item is capitalized.", "GUID": "1fb0f9c4-8d65-11ef-3781-0201b014c5b2", "name": "Capitalize right of use asset", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.4846635856294315, "y": 1.73421926910299, "z": -2.4327896235536914 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8725", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of capturing the agreement between the lessee (the party obtaining the asset) and the lessor (the party providing the asset) for the use of an asset over a specified period in exchange for payments. The lease contract is recorded and managed, with periodic reviews to ensure compliance with the agreed terms and to monitor for any required actions, such as payments or asset inspections.", "Process_Group": "Asset Accounting", "Scope": "Information such as leasee, lessor, asset to be leased, the duration of the lease, payment terms, and any conditions related to the assets use including provisions for maintenance, early termination, and renewal options are captured.", "Outcome": "Lease contract is created.", "GUID": "1fb0f9c2-8d65-11ef-3781-0201b014c5b2", "name": "Create asset lease contract", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8324281939564586, "y": 1.7375415282392028, "z": -0.8013781342122278 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8727", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The process of monitoring lease contract for assets involves maintaining accurate and up-to-date records of all transactions and correspondence related to the lease is crucial for effective monitoring and timely processing of financial obligations.", "Process_Group": "Asset Accounting", "Scope": "This includes tracking payment schedules, ensuring timely release payments, and checking for any adjustments or escalations specified in the contract. Additionally, any changes to the lease agreement, such as renewals, extensions, or terminations, should be documented and managed appropriately.", "Outcome": "Financial obligations are tracked and lease contract is reviewed or updated.", "GUID": "065144d0-a04d-11ef-3781-0201b014c5b2", "name": "Monitor asset lease contract", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.754877933505367, "y": 1.7408637873754151, "z": -1.187706854188019 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8728", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of calculating the total amount of liability to be repaid during the lease contract. This consists of the principal and interest. The purpose is to ensure that the right amount of liability is reported in the lessees balance sheet.", "Process_Group": "Asset Accounting", "Scope": "This amount is calculated based on the present value of the future repayments during the lease period. The calculation takes into account payment terms such as fixed payment, variable payment, or even activity based payments. Outcome: Total amount of lease liability is calculated.", "Outcome": "Total amount of lease liability is calculated.", "GUID": "1fb0f9c6-8d65-11ef-3781-0201b014c5b2", "name": "Determine lease liability", "Business_Rules": "It is important to consider the date when first repayment is made since it influences the calculation of the present value of future repayments. If the first payment is made on or before commencement date of the lease contract then, this is excluded from discounting future repayments.", "Prerequisite": "" }, "position": { "x": 3.6813847342766377, "y": 1.744186046511628, "z": -1.564418881960624 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8730", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is a self-initiated payment process initiated by the seller at agreed intervals without requiring the buyer to initiate payment. This is common in subscription based sales, where regular recurring payments are needed, as it helps ensure timely payment and reduces administrative effort for both parties.", "Process_Group": "Accounts Receivable", "Scope": "The mandate is first created and stored. The mandate can be created using the customer master records. This document grants the seller the authority to collect payment from the customers bank account. Once payments are confirmed by the sellers bank, postings are made on the customers account to clear the open items.", "Outcome": "Customer payments via direct debit processed.", "GUID": "647a6eb5-9d29-11ef-3781-0201b014c5b2", "name": "Manage direct debit payments", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.611873291274926, "y": 1.7475083056478407, "z": -1.9314825252186414 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8732", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process refers to the legal and administrative procedures that are initiated when a customer is unable to meet their financial obligations to creditors or sellers. The purpose is to resolve the customers financial distress in a manner that maximizes the returns to creditors while providing a structured means for the customer to address their financial difficulties.", "Process_Group": "Accounts Receivable", "Scope": "This process typically begins with the filing of an insolvency petition, followed by the appointment of an insolvency practitioner to oversee the case. The practitioners role includes assessing the debtors financial situation, managing the assets, and formulating a plan to distribute the assets to creditors. Throughout this process, efforts may be made to reorganize the debtors operations, negotiate settlements with creditors, or, if necessary, liquidate assets to repay debts. T", "Outcome": "Provision for bad debts are made and approved.", "GUID": "0ee698b0-a03c-11ef-3781-0201b014c5b2", "name": "Process customer insolvency", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.546268079899039, "y": 1.750830564784053, "z": -2.288866616011739 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8759", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When it has been identified that a customer is likely to default on payments, all necessary steps must be taken to ensure that payment is received from the customer. This includes processing of legal case against the customer. Bad debts have negative impact on the companys capital. The company may engage the services of an external agency to collect the outstanding payments.", "Process_Group": "Accounts Receivable", "Scope": "This follows dunning procedure. Outstanding debts retrieved are processed and customers open items are cleared while uncollectible amounts are identified, and appropriate steps are taken to mitigate their negative impact of the companys financial health.", "Outcome": "Customer outstanding payments received and decision on how to manage bad debts taken.", "GUID": "0ee698b2-a03c-11ef-3781-0201b014c5b2", "name": "Manage collections", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8527123883901238, "y": 1.7541528239202657, "z": -0.75329728919316 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8760", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The process of adjusting the transfer price for intercompany transactions by processing variance between planned and actual transfer price. The settlement ensures accurate reporting of intercompany transactions for both tax and financial reporting purpose.", "Process_Group": "Intercompany", "Scope": "The business team provides and updates the periodic forecasts. The responsible team then calculates the appropriate debit or credit notes in compliance with the companys transfer pricing manual. This is then approved to validate compliance and accuracy. Finally, once approved, the debit or credit note is issued and the business units are informed, completing the intercompany financial adjustment.", "Outcome": "Transfer price difference settled via credit or debit note.", "GUID": "06516be7-a04d-11ef-3781-0201b014c5b2", "name": "Perform transfer price settlement", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.784927441052726, "y": 1.7574750830564785, "z": -1.1154277870268046 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8762", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is automatically deducting funds from a companys bank account to pay its creditors. This enhances efficiency by reducing administrative tasks and minimizing the risk of late payments or human error, thereby maintaining good relationships with suppliers and optimizing cash flow management.", "Process_Group": "Accounts Payable", "Scope": "This process begins with the company authorizing its bank to pay specific amounts to designated vendors on agreed dates. The bank then processes these payments directly, ensuring timely settlement of invoices without manual intervention. The automatic payment run can be used to perform this process.", "Outcome": "Vendor payment processed.", "GUID": "0ee698ae-a03c-11ef-3781-0201b014c5b2", "name": "Execute direct debiting AP", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.720947274392087, "y": 1.7607973421926912, "z": -1.4678390174655045 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8764", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The process of journalizing recurring items involves identifying and recording financial transactions that occur on a regular basis, such as monthly rent payments, utility bills, or subscription fees. This simplifies routine accounting, reduces manual effort, and helps maintain an accurate and up-to-date general ledger.", "Process_Group": "General Ledger", "Scope": "This involves identifying transactions that recur periodically, defining a template for each entry within the accounting system, and setting parameters like accounts, amounts, and posting frequency. Accountants review these templates to ensure accuracy and relevance, making adjustments if necessary to reflect changes in amounts or conditions. Once set up, the system automates the posting of these entries at the designated intervals, requiring periodic verification to confirm alignment with actual financial activities. This automation minimizes manual input, enhances data consistency, and keeps the ledger current with minimal ongoing intervention", "Outcome": "Recurring entries processed.", "GUID": "06516be9-a04d-11ef-3781-0201b014c5b2", "name": "Journalize recurring entries", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.660695782194387, "y": 1.7641196013289036, "z": -1.8105012636934155 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8769", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of closing an accounting period. It ensures all accounting entries, adjustments, and reconciliations in the general ledger are finalized, allowing for accurate financial statements and compliance with accounting standards.", "Process_Group": "General Ledger", "Scope": "All GL accounts are are reconciled and sub-ledgers are reconciled with the general ledger. After all accounts are reconciled and balanced, the general ledger is closed and no postings are allowed to the closed period.", "Outcome": "General ledger closed.", "GUID": "06516be5-a04d-11ef-3781-0201b014c5b2", "name": "Perform general ledger closing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.604096652395287, "y": 1.7674418604651163, "z": -2.143385338806798 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8770", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Creating initial prototypes of the selected ideas to evaluate their practicality and performance. This includes design and engineering efforts to bring the ideas into a tangible form.", "Process_Group": "Portfolio Management", "Scope": "This task involves the R&D team, Design team, and customer representatives for feedback. It includes detailed design work, material selection, prototype manufacturing, and initial testing to ensure the prototype meets the intended design specifications.", "Outcome": "Functional prototypes with initial test results, documented with detailed specifications and feedback.", "GUID": "93c313b7-3910-11ef-3781-0201b014c5b2", "name": "Develop prototypes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.871735248725561, "y": 1.770764119601329, "z": -0.704703596328458 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8772", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of preparing for period end closing activities to ensure the timely execution of period end activities. It includes activities such as opening new periods, master data changes checks, and release of month close task list.", "Process_Group": "General Ledger", "Scope": "Period end closing activities are planned. This may involve the use of closing cockpit. Pre close activities such as master data changes checks, and reconciliation checks are performed by before start of close. Special posting periods are opened for adjustment postings, new periods are also opened and old periods are closed.", "Outcome": "Posting periods are opened.", "GUID": "06516be3-a04d-11ef-3781-0201b014c5b2", "name": "Prepare period end closing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.8130809587181655, "y": 1.7740863787375414, "z": -1.0423893321102669 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8774", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "When a customer is also a supplier, it is possible to clear open items in accounts receivable and accounts payable for this business partner by offsetting the account balances without processing any incoming or outgoing payment. This simplifies cash management and reduces the number of payment transactions needed to settle accounts.", "Process_Group": "General Ledger", "Scope": "Instead of making separate payments, receivables and payables are set-off against each other. This means that open items in accounts receivable can be offset against open items in accounts payable, reducing the balances accordingly.", "Outcome": "Open items in accounts receivable and accounts payable cleared.", "GUID": "647a6eb7-9d29-11ef-3781-0201b014c5b2", "name": "Conduct inter-account clearing", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.757976578531833, "y": 1.7774086378737541, "z": -1.37025984222197 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8776", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of confirming the deal with the counterparty to ensure that all details captured by the front office are accurate and complete. Before any deal is settled it is important that the back office team confirms the deal to prevent financial loss.", "Process_Group": "Treasury-Financial Instruments", "Scope": "Depending on the type of trade and counterparty confirmation can be automated using platforms such as SWIFT or manually confirmed via phone calls. During this process, the back office team checks the details provided by the counterparty against what has been captured in the system.", "Outcome": "Trade deal confirmed and ready to be settled.", "GUID": "e21333e3-9db7-11ef-3781-0201b014c5b2", "name": "Confirm trade deal", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.706345252547681, "y": 1.780730897009967, "z": -1.6882874055746262 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8778", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is a master data activity in treasury which describes the mechanism by which trade settlement is concluded between the company and its trade counterparties. It ensures consistent, accurate, and efficient transaction settlements, reducing the likelihood of settlement errors, speeding up the payment process, and enhancing operational efficiency by minimizing the manual input required for each transaction.", "Process_Group": "Treasury-Financial Instruments", "Scope": "In this process, the company captures settlement instructions provided by the counterparts. This includes account numbers, payment methods, currencies, and contact details.", "Outcome": "Standard settlement instructions for counterparty is created and updated.", "GUID": "e21333e5-9db7-11ef-3781-0201b014c5b2", "name": "Maintain standard settlement instructions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.658109933191794, "y": 1.7840531561461792, "z": -1.9964448361816447 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8780", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the exchange of financial instruments and funds following a trade agreement. It ensures actual transfer of ownership of securities.", "Process_Group": "Treasury-Financial Instruments", "Scope": "On settlement date, the trade is settled. Settlement can only take place after confirmation. The financial postings are posted to the relevant GL and security accounts.", "Outcome": "Ownership of financial securities transferred.", "GUID": "e212e5c0-9db7-11ef-3781-0201b014c5b2", "name": "Settle trade deal", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.8894838241224032, "y": 1.787375415282392, "z": -0.6556301384010493 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8784", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The process for executing funds transfer between in-house cash and non-in-house cash typically involves moving money between accounts within the same company (in-house) and external accounts or bank accounts outside the companys in-house cash pool. This is to manage liquidity efficiently across the organization by reallocating funds where they are needed by allowing the company to cover both internal and external payments, settle obligations, or fund specific projects. It optimizes cash flow, reduces the reliance on external borrowing, and minimizes transaction costs by efficiently using internal funds before resorting to external resources.", "Process_Group": "Treasury-Cash and Liquidity Management", "Scope": "It begins with the identification of the transfer need, such as paying internal or external vendors. The transfer request is then initiated within the financial system, where the transfer amount, currency, and accounts are specified. Approval workflows may be required, depending on the organizations policy. Once approved, the transfer is executed.", "Outcome": "Funds are moved between in-house cash account and non-inhouse cash account.", "GUID": "a2750f37-a0da-11ef-3781-0201b014c5b2", "name": "Execute funds transfer between in-house cash and non-inhouse cash", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.8393193194728275, "y": 1.7906976744186047, "z": -0.9686412143143401 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8786", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of documenting and communicating all financial transactions related to the companys treasury activities. The reporting is essential for ensuring transparency and compliance with regulatory standards, helping the company assess its risk exposure, liquidity, and financial position.", "Process_Group": "Finance Reporting and Analytics", "Scope": "This includes tracking and reporting on various trade transactions such as foreign exchange (FX) trades, interest rate swaps, commodities, and securities. It includes capturing the details of each transaction, such as trade date, settlement date, counterparties, amounts, and the financial instruments involved. This information is then compiled into reports that are presented to stakeholders, such as management, auditors, or regulatory bodies.", "Outcome": "Report on treasury operations for specific purpose generated.", "GUID": "10ecd273-9d13-11ef-3781-0201b014c5b2", "name": "Perform treasury trade reporting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.7924474369956336, "y": 1.7940199335548175, "z": -1.2717477885277608 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8791", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This refers to the process of calculating and reporting the average number of days it takes a company to collect payments from its customers after a sale has been made. This helps companies to assess how efficiently a company is managing its accounts receivable.", "Process_Group": "Finance Reporting and Analytics", "Scope": "To determine the days sales outstanding, the average accounts receivable during a given period is divided by the total value of credit sales during the same period, and then multiplied by the number of days in the period being measured. A high value suggests that a company is experiencing delays in receiving payments, which can result in a cash flow problem.", "Outcome": "Average number of days for receivables to be collected determined.", "GUID": "10ecd271-9d13-11ef-3781-0201b014c5b2", "name": "Generate days sales outstanding report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.748790623990494, "y": 1.7973421926910298, "z": -1.564924154551899 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8793", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This refers to the process of calculating and analyzing the average number of days it takes for a company to pay its suppliers. This helps businesses track their accounts payable performance and assess how efficiently they manage their payment cycle.", "Process_Group": "Finance Reporting and Analytics", "Scope": "This report involves collecting data on accounts payable balances, number of days, opening inventory balance, ending inventory balance, and purchases within the period. While higher values of days payable outstanding is beneficial since the company can retain funds for short term investments, it is not always desirable. This is because it can jeopardize its relationship with the suppliers and creditors.", "Outcome": "Average number of days taken to make payment to vendors determined.", "GUID": "10ec8450-9d13-11ef-3781-0201b014c5b2", "name": "Generate days payable outstanding report", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.708271149828216, "y": 1.8006644518272426, "z": -1.8481451458256335 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8794", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Assessing the technical viability of each idea in collaboration with suppliers. This includes evaluating technical specifications, compatibility with existing systems, and potential for integration.", "Process_Group": "Portfolio Management", "Scope": "This task involves detailed technical assessments by the R&D team in conjunction with supplier technical experts. It includes reviewing technical documentation, conducting compatibility tests, and holding technical review meetings to discuss feasibility.", "Outcome": "Technical evaluation report for each idea, highlighting feasibility, potential challenges, and required modifications.", "GUID": "93c313b5-3910-11ef-3781-0201b014c5b2", "name": "Review and assess supplier suggestions", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9059460312786316, "y": 1.8039867109634553, "z": -0.6061103248198577 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8795", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Engaging with suppliers to understand their latest innovations, technologies, and offerings. This involves regular meetings, reviewing supplier updates, and exploring potential new materials, components, or technologies that suppliers can provide.", "Process_Group": "Portfolio Management", "Scope": "This task involves collaboration between the Procurement team and Supplier Relations team. It includes scheduling and conducting meetings with suppliers, attending supplier presentations, reviewing supplier portfolios and innovation showcases, and maintaining an updated database of supplier capabilities.", "Outcome": "List of potential innovations and technologies from suppliers, documented with detailed descriptions and potential applications.", "GUID": "93c313b3-3910-11ef-3781-0201b014c5b2", "name": "Engage with key suppliers", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.863624660134435, "y": 1.8073089700996676, "z": -0.8942336416563306 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8799", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process assesses discrepancies between the recorded inventory levels in accounting records or inventory management systems and the actual physical stock on hand.This ensures inventory accuracy, ensure proper stock control, and support effective financial reporting by resolving inconsistencies between expected and actual inventory levels.", "Process_Group": "Inventory Management", "Scope": "This process starts with gathering detailed inventory data, including quantities, costs, and age of the stock. The next step is to compare the recorded values with current market values, considering factors such as obsolescence, damage, and market demand changes. Variance analysis is then performed to identify discrepancies between expected and actual values. These variances are categorized and analyzed to determine their causes and corrective actions.", "Outcome": "Corrective actions to address causes of inventory variance taken.", "GUID": "06516beb-a04d-11ef-3781-0201b014c5b2", "name": "Conduct inventory variance analysis", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.8243363818834255, "y": 1.8106312292358804, "z": -1.1723699237880472 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8801", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of analyzing current and projected demand, lead times, and inventory turnover rates to establish optimal stock levels that meet customer needs while minimizing holding costs. This process requires understanding the sales forecast, production schedules, and any seasonal or market-driven fluctuations that impact demand.", "Process_Group": "Inventory Management", "Scope": "This involves analysis of historical sales data, current demand forecasts, and expected lead times to project future stock requirements. This involves calculating optimal inventory levels that balance stock availability with storage costs, ensuring enough product is available to meet anticipated demand while minimizing excess. By assessing factors such as seasonal demand, market trends, and supply chain reliability, the company establishes reorder points and safety stock levels to prevent stockouts and overstock situations. The inventory plan is then reviewed and adjusted regularly to adapt to changes in market conditions, demand patterns, and supplier performance.", "Outcome": "Periodic optimal stock level is determined.", "GUID": "06516bed-a04d-11ef-3781-0201b014c5b2", "name": "Determine inventory plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.78800299954203, "y": 1.8139534883720931, "z": -1.4404954968261872 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8808", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the process of updating time dependent data related to an asset. This type of data can be changed per time during the asset lifecycle. Data such as cost center, plant or location are examples of time dependent data that can be changed or updated per time. Asset depreciation values are then posted to the new cost center", "Process_Group": "FICO Master Data", "Scope": "The asset master record serves as a central repository for managing the assets lifecycle, from acquisition to disposal. It is used to track key financial data, such as depreciation and impairment, and ensure compliance with accounting standards. Regular updates to asset master records are necessary to reflect changes like asset transfers, adjustments, or disposals, ensuring accurate reporting and effective asset management.", "Outcome": "Asset master records updated.", "GUID": "c2b0ccb7-9d17-11ef-3781-0201b014c5b2", "name": "Maintain asset master records", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.754546152345094, "y": 1.8172757475083055, "z": -1.698587230768636 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8825", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Conducting a market feasibility study to evaluate the potential of each idea. This includes assessing market demand, target audience, competitive landscape, and potential market entry strategies.", "Process_Group": "Portfolio Management", "Scope": "This task involves the Market Research team, Marketing team, and Business Development team. It includes conducting surveys, focus groups, market simulations, and competitive analysis.", "Outcome": "Market feasibility report for each idea, detailing market potential, target demographics, and competitive analysis.", "GUID": "93c313c5-3910-11ef-3781-0201b014c5b2", "name": "Conduct market feasibility study", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9211106626569356, "y": 1.8205980066445182, "z": -0.556177868874544 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8846", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Analyzing market trends and competitor activities to identify opportunities for new products or services. This involves monitoring industry reports, market research studies, competitor product launches, and global trends.", "Process_Group": "Portfolio Management", "Scope": "This task involves collaboration between the Marketing team, Market Research team, and Competitive Intelligence team. It includes gathering and analyzing data from various sources, attending industry conferences, and utilizing market analysis tools.", "Outcome": "Comprehensive market trend report highlighting opportunities and potential market gaps.", "GUID": "93c313c3-3910-11ef-3781-0201b014c5b2", "name": "Analyse market trends and competitors", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.8859804335286183, "y": 1.823920265780731, "z": -0.8192172711130843 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8857", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is the physical inspection of all assets to ensure the condition and functionality of the assets. All findings from the inspection activity are carefully documented and asset value adjustment postings are made depending on the inspection results.", "Process_Group": "Plant Maintenance Asset Management", "Scope": "For periodic inspection activities, an inspection plan is prepared. All resources required for the inspection activities are captured in the inspection plan. On the inspection date, physical inspection is carried out and the findings are documented in an inspection report. If maintenance activities are required then this is triggered following the inspection results.", "Outcome": "Asset inspection results documented.", "GUID": "06516be1-a04d-11ef-3781-0201b014c5b2", "name": "Perform asset inspection", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.853621703072369, "y": 1.8272425249169437, "z": -1.0721939048556535 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8866", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves evaluating the submitted ideas to determine their feasibility, alignment with business goals, and potential value. It typically includes initial screening, categorization, and a preliminary assessment of the ideas potential impact and resource requirements.", "Process_Group": "Portfolio Management", "Scope": "The scope encompasses gathering ideas from various sources, setting criteria for initial screening and categorization, conducting preliminary assessments with cross-functional input, providing feedback to idea submitters, and maintaining records of all reviewed ideas and their statuses.", "Outcome": "The outcome of this process is a refined list of ideas that meet the basic criteria for further consideration. These ideas are categorized and ranked based on predefined criteria such as strategic alignment, potential ROI, feasibility, and resource availability.", "GUID": "c81829c0-499b-11ef-3781-0201b014c5b2", "name": "Review ideas", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.823955683258183, "y": 1.830564784053156, "z": -1.3150861439316721 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8867", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process involves a deeper evaluation of the shortlisted ideas from the Review Ideas process. It includes a detailed analysis of each ideas feasibility, resource requirements, potential benefits, risks, and alignment with the strategic objectives. Based on this analysis, the process leads to the selection and formal approval of ideas to be developed further.", "Process_Group": "Portfolio Management", "Scope": "The scope includes conducting detailed feasibility studies, consulting with key stakeholders, developing business cases or proposals, facilitating decision-making meetings to finalize approvals, communicating decisions to relevant parties, and documenting the selection and approval process along with the criteria and rationale used.", "Outcome": "The outcome is a set of approved ideas that are ready to move into the development phase. These ideas are prioritized and have a clear plan for development, including assigned resources and timelines.", "GUID": "c81829c2-499b-11ef-3781-0201b014c5b2", "name": "Select and approve ideas for development", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.796903436533288, "y": 1.8338870431893688, "z": -1.5478729106449758 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8875", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Analyzing the collected customer feedback to identify unmet needs, desires, and pain points. This analysis helps to pinpoint areas where new products or improvements can be made to better serve the customer base.", "Process_Group": "Portfolio Management", "Scope": "This involves data analysis using statistical tools, thematic analysis, and collaboration between Market Research, Product Management, and Data Analytics teams. The task includes identifying patterns and trends in the feedback, segmenting customer needs by demographics, and prioritizing these needs based on frequency and impact.", "Outcome": "Detailed report outlining customer needs and desires, prioritized by importance and potential impact on the business.", "GUID": "93c313bd-3910-11ef-3781-0201b014c5b2", "name": "Identify customer needs", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9349673941148504, "y": 1.8372093023255816, "z": -0.5058667647833618 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8876", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Gathering feedback from customers through various channels such as surveys, interviews, focus groups, social media, and customer service interactions. The goal is to understand customer needs, pain points, preferences, and suggestions for improvement.", "Process_Group": "Portfolio Management", "Scope": "This task involves designing and distributing surveys, conducting interviews and focus groups, monitoring social media and customer service logs, and collecting data from all these sources. It requires collaboration between the Customer Relations team, Market Research team, and sometimes external consultants.", "Outcome": "Comprehensive data set of customer feedback, including qualitative and quantitative insights, categorized by themes and relevance.", "GUID": "93c313bb-3910-11ef-3781-0201b014c5b2", "name": "Gather customer feedback", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9063714197543016, "y": 1.8405315614617939, "z": -0.7436431741335126 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8890", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "In a firm that manages multiple projects for various customers, the process of billing for services rendered is crucial. However, each project may have different billing requirements depending on the contract type, such as Time and Materials, Fixed Price, or Milestone-based contracts. To streamline the billing process and ensure consistency, the firm decides to establish standardized billing plans. These billing plans are designed to cover the most common billing scenarios and contract types encountered by the firm.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "The scope of the Create Billing Plan process encompasses the development and implementation of standardized billing plan within a consulting firm that manages a diverse portfolio of projects. The process is relevant to all projects handled by the firm, covering various contract types such as Time and Materials, Fixed Price, and Milestone-based contracts. The process involves the finance and project management teams. This process aims to ensure that billing plans are consistently and efficiently applied across all projects, regardless of their specific requirements or client demands.", "Outcome": "The outcome of creating a billing plan for projects is a comprehensive and structured financial framework that details the billing schedule, payment terms, and milestone definitions, all formally agreed upon with the customer.", "GUID": "7c66e7f0-4f0e-11ef-3781-0201b014c5b2", "name": "Create billing plan", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.8802834629971783, "y": 1.8438538205980066, "z": -0.9712879319700345 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8892", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Essential to ensure the successful execution of an exhibition stall. In order to create a positive impact and experience for potential customers. It is important, to make everything run according to the plan.", "Process_Group": "Pre-order Management", "Scope": "This process talks about the event itself. Its about building up the stand, organizing it and participating at the exhibition. It also includes possible adjustment that you need to take according to problems that appeared on one of the first days of the exhibition. At the end it is also necessary to put down the stand.", "Outcome": "The outcome of this event is a successful time at the exhibition.", "GUID": "12a88131-1e98-11ef-3781-0201b014c5b2", "name": "Run fair and exhibition", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.856624198406262, "y": 1.8471760797342194, "z": -1.1887814750637449 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8896", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Participating at a stall or exhibition requires high logistical preparation, therefore it is important to plan the campaign and the strategy in advance to dont miss out on anything and have a smooth on sight event.", "Process_Group": "Pre-order Management", "Scope": "The teams will now work on their topic of the campaign planning and according to a schedule check in with each other.The planning involves to design a stall layout, showcase products/services, plan activities, train the staff that will be representing the company at the exhibition and develop a follow up plan (too nuture leads and capitalize on the connections made during the exhibition.", "Outcome": "At the end of this process you have a schedule with tasks and activities that is ready to follow along. Each team member knows their role in the following weeks/months until the exhibition.", "GUID": "12a83310-1e98-11ef-3781-0201b014c5b2", "name": "Plan fair and exhibition and strategy", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.835314165382153, "y": 1.8504983388704317, "z": -1.3961047923742658 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8913", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Committees serve as the backbone of efficient event planning. The division of labour and utilization of expertise and skill is crucial for a fluently running planning process.", "Process_Group": "Pre-order Management", "Scope": "In this process you will create a well-managed team. The size and type of teams depend on the size and kind of event you are planning. It includes assigning roles, creating management tasks and a schedule, defining workflow and communication. From the employees of your company you need to consider the best fitting members for the given tasks in the process of developing a successful exhibition stand. Those people need to be able to work together efficiently and be willing to commit to the given task.", "Outcome": "The process ends with concrete teams of experts, each knowing what tasks they are supposed to focus on.", "GUID": "cf2f0ae7-1e48-11ef-3781-0201b014c5b2", "name": "Set up event committees", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.947506791933474, "y": 1.8538205980066444, "z": -0.45521126454975597 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8918", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "It is important to set up event ROI-driven event goals to be able to measure the success of the event afterwards. These goals will form the foundation for the event strategy and planning. They need to be measurable and specific (include key benchmarks) .", "Process_Group": "Pre-order Management", "Scope": "Create objectives and goals for the exhibition that define what is supposed to be achieved with this exhibition. The goals should follow the SMART Rule.", "Outcome": "The outcome of this event are set goal.", "GUID": "cf2f0ae1-1e48-11ef-3781-0201b014c5b2", "name": "Set up ROI and goals", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9247837365454705, "y": 1.8571428571428572, "z": -0.6675628018689439 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8920", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Assessing the success through feedback is important to take it as a learning for further exhibitions.", "Process_Group": "Pre-order Management", "Scope": "Get feedback from customers that visited the exhibition stand and from the working teams to assess the success of the event. Collect figures and data to evaluate and measure the fulfillment of the goals (e.g. Lead creation, turnover rate,..).", "Outcome": "The outcome of this process is a data sheet that is easy to read to use it as a reference for the following exhibitions.", "GUID": "12a88133-1e98-11ef-3781-0201b014c5b2", "name": "Collect feedback", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.904303510223709, "y": 1.86046511627907, "z": -0.869720702326226 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8922", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is necessary so the people involved in the campaign planning know the financial means they have access to. It also specifies what the funds will be used for.", "Process_Group": "Pre-order Management", "Scope": "It involves collaboration between the marketing and finance departments to determine the available budget, assess revenue projections, and align campaign objectives with financial constraints. To not miss out on any financial data it is of importance to have close communication between the departments of the company. In this process you need to map out an initial plan or checklist that lists all of your event components. You than allocate the necessary resources and budget to the event components.", "Outcome": "The outcome of this event are a set budget, according to the financial means of the company.", "GUID": "cf2f0ae3-1e48-11ef-3781-0201b014c5b2", "name": "Set up event budget", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.885986304128829, "y": 1.8637873754152823, "z": -1.0616674789525709 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8928", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To make sure the goals are achievable with the now set budget, they might need to be adjusted. It is necessary to ensure the allocated resources to be utilized efficiently to achieve the desired outcome.", "Process_Group": "Pre-order Management", "Scope": "The scope includes the alignment of the planned campaign with the set budget. The goals of the campaign must be left as original as possible and adjustments should be held as small as possible. However, goals need to be prioritized based on their importance and potential impact to the success of the campaign. Afterwards, adjustments can be made to the less significant goals.", "Outcome": "The outcome of this event is a reworked frame of goals that matches the given budget.", "GUID": "cf2f0ae5-1e48-11ef-3781-0201b014c5b2", "name": "Align budget with goals", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.869752188711914, "y": 1.867109634551495, "z": -1.2433862003061242 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8929", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To make sure the goals are achievable with the now set budget, they might need to be adjusted. It is necessary to ensure the allocated resources to be utilized efficiently to achieve the desired outcome.", "Process_Group": "Pre-order Management", "Scope": "The scope includes the alignment of the planned campaign with the set budget. The goals of the campaign must be left as original as possible and adjustments should be held as small as possible. However, goals need to be prioritized based on their importance and potential impact to the success of the campaign. Afterwards, adjustments can be made to the less significant goals.", "Outcome": "The outcome of this event is a reworked version of the event goals aligned with the set budget.", "GUID": "e6e20213-1da7-11ef-3781-0201b014c5b2", "name": "Align goals with budget", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9587203192399822, "y": 1.8704318936877078, "z": -0.4042458546434603 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8931", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Campaign Measurements help the company to understand the impact of their marketing efforts and strategise accordingly. Setting up measurement tools is necessary to optimize future campaigns.", "Process_Group": "Pre-order Management", "Scope": "There are several measuring tools a company can use, therefore it firstly is necessary to find the proper tool that measures the success of the campaign goals. Afterwards, a reporting template (date base for collected data) needs to be set up and the data collection can begin. Common tools are the ROI, Cost/Win, Cost/Lead, Conversion Rate, Website Traffic. Traffic by Source.", "Outcome": "Measuring tools for campaign is selected and agreed upon with all stakeholders. The reporting template is set up.", "GUID": "e6e20215-1da7-11ef-3781-0201b014c5b2", "name": "Define campaign measurements", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9412048487222773, "y": 1.87375415282392, "z": -0.5910279501449714 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8950", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process is necessary so the people involved in the campaign planning know the financial means they have access to. It also specifies what the funds will be used for.", "Process_Group": "Pre-order Management", "Scope": "It involves collaboration between the marketing and finance departments to determine the available budget, assess revenue projections, and align campaign objectives with financial constraints. To not miss out on any financial data it is of importance to have close communication between the departments of the company. In this process you need to map out an initial plan or checklist that lists all of your event components. You than allocate the necessary resources and budget to the event components.", "Outcome": "The outcome of this process is a fixed budget aligned with the financial department of the company.", "GUID": "e6e20211-1da7-11ef-3781-0201b014c5b2", "name": "Set up campaign budget", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.925665491806516, "y": 1.8770764119601329, "z": -0.7675613633055703 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8954", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Advance planning enhances the effectiveness and efficiency of a campaign, leading to better outcomes and higher chances of success. It provides a structured approach, reduces uncertainties, and ensures that all elements of the campaign are well-coordinated to not face any surprises after the launch.", "Process_Group": "Pre-order Management", "Scope": "At first you need to identify the purpose, by looking at the campaign goals. You then define the audience. After agreeing upon a message/ theme and slogan (eg. Seasonal, new product,..) the key assets can be identified, meaning to choose the marketing channels the message will be send through. The final planning step is to create a schedule, creating distributions and deadlines, campaign ready to launch at the set date.", "Outcome": "The outcome of this process is a campaign ready to launch with a set schedule and responsibilities.", "GUID": "e6e20219-1da7-11ef-3781-0201b014c5b2", "name": "Plan campaign", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.912022010585383, "y": 1.8803986710963456, "z": -0.9338306953215516 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8961", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "It is important to set up ROI-driven event goals to be able to measure the success of the event afterwards. These goals will form the foundation for the event strategy and planning. They need to be measurable and specific (include key benchmarks).", "Process_Group": "Pre-order Management", "Scope": "Create objectives and goals for the campaign that define what is supposed to be achieved with this campaign. The goals should follow the SMART Rule.", "Outcome": "The outcome of this process are measurable and specific event goals.", "GUID": "e6e1b3f0-1da7-11ef-3781-0201b014c5b2", "name": "Define campaign goals", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.900194060976796, "y": 1.883720930232558, "z": -1.0898211058766227 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8983", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Assessing a campaign is essential for understanding its impact, making informed decisions, and driving continuous improvement. It provides valuable insights that help in refining strategies, optimizing resources, and ultimately achieving better results in future campaigns.", "Process_Group": "Pre-order Management", "Scope": "In this process it is necessary to evaluate the data received from the campaign measuring tools. It might also be taken into consideration to ask for customer feedback (e.g. Via email). Both will be analyzed and the data organized to create a data sheet.", "Outcome": "The outcome of this process is a data sheet that is easy to read to use it as a reference for the following campaigns.", "GUID": "e6e20217-1da7-11ef-3781-0201b014c5b2", "name": "Assess campaign success", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9686003418195657, "y": 1.8870431893687707, "z": -0.353005232521969 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8985", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "An appealing visual design is important, since the receiver will choose from the first sight - which is the appearance - whether to read the article or not.", "Process_Group": "Pre-order Management", "Scope": "Creation of a campaign layout/ design, with regard to its marketing. It must reflect the brands identity and convey the message effectively. It must be ensured to be user friendly on each laptop and mobile phone.", "Outcome": "The several emails of the email campaign are ready to send.", "GUID": "e6e2021f-1da7-11ef-3781-0201b014c5b2", "name": "Create template for email campaign", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9556235767250394, "y": 1.8903654485049834, "z": -0.514090724198645 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8986", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To improve any further campaigns it is necessary to collect the customers feedback, either through a feedback email link or after they purchased products. Furthermore, helpful information can be derived from the collected data from the monitoring.", "Process_Group": "Pre-order Management", "Scope": "In this process it is necessary to evaluate the data received from the campaign measuring tools. It might also be taken into consideration to ask for customer feedback (e.g. Via email - consider discount codes for giving a review). Both will be analyzed and the data organized to create a data sheet.", "Outcome": "The outcome of this process is a data sheet that is easy to read to use it as a reference for the following campaigns.", "GUID": "cf2ee3d0-1e48-11ef-3781-0201b014c5b2", "name": "Collect customer feedback and assess success", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.944354864422015, "y": 1.8936877076411962, "z": -0.664879465399848 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8987", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The more customers (and therefore data) you have, the more time consuming (and therefore money consuming) it is. Therefore, this process is necessary, since through it you spot inactive subscribers.", "Process_Group": "Pre-order Management", "Scope": "By looking at whether each individual subscriber becomes active through the campaign or not the company can select inactive subscribers. The company can as a first step send them a Welcome Back email. If they still not respond, eventually exclude them from the mailing list.", "Outcome": "The outcome of this process is a cleaned up mailing list, with customers that will potentially buy the companies products.", "GUID": "e6e20225-1da7-11ef-3781-0201b014c5b2", "name": "Follow up with inactive subscribers", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.934713592561513, "y": 1.8970099667774085, "z": -0.8053581559707766 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8988", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Maintaining a integer email list is crucial to send the right content to the right people that are interested in it.", "Process_Group": "Pre-order Management", "Scope": "It involves defining who to address with the planned campaign and additionally creating and growing an email list, that is tempting for people to sign-up to and take actions on the emails received. It is necessary to ensure compliance with relevant regulations, such as GDPR or CAN-Spam. This process also involves to segment your email audience into groups according to criteria that you determine. This might be the region, age or income class. The campaign must than be slightly adjusted to target each audience group individually.", "Outcome": "The outcome of this process are segmented campaign parts all including special adjustments for the certain audience group. The email list is maintained transparent and organized.", "GUID": "e6e2021d-1da7-11ef-3781-0201b014c5b2", "name": "Segment campaign audience", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.926619057226864, "y": 1.9003322259136213, "z": -0.9355140568240314 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8989", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Planning an email campaign in advance helps to prevent time pressure during the running time of the campaign, furthermore, potential issues might be fixed in advance. Therefore, the content of each piece of the campaign follows a logical flow.", "Process_Group": "Pre-order Management", "Scope": "At first the concrete content (aligned with the goals) must be chosen and outlined. Afterwards the content needs to be scheduled in an email campaign calender, that will be launched through automatic workflow.", "Outcome": "The launching dates of each part of the campaign are set, so that no further planning, adjusting, etc. needs to be done and the campaigns can simply be launched on the set date (without any complications).", "GUID": "e6e2021b-1da7-11ef-3781-0201b014c5b2", "name": "Plan and schedule email campaign", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9771401333128338, "y": 1.903654485049834, "z": -0.3015242830083669 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8990", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Campaign Measurements help the company to understand the impact of their marketing efforts and strategise accordingly. Setting up measurement tools is necessary to optimize future campaigns.", "Process_Group": "Pre-order Management", "Scope": "There are several measuring tools a company can use, therefore it firstly is necessary to find the proper tool that measures the success of the campaign goals. Afterwards, a reporting template (date base for collected data) needs to be set up and the data collection can begin. Common tools are the ROI, Cost/Win, Cost/Lead, Conversion Rate, Website Traffic, Traffic by Link.", "Outcome": "Measuring tools for campaign is selected and agreed upon with all stakeholders. The reporting template is set up.", "GUID": "e6e20223-1da7-11ef-3781-0201b014c5b2", "name": "Monitor success of campaign", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9680301042253303, "y": 1.9069767441860463, "z": -0.43680350320501743 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8993", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Develop a comprehensive tender proposal that addresses all the requirements and specifications outlined in the tender documents.", "Process_Group": "Pre-order Management", "Scope": "Cross-functional teams including sales, engineering, finance, and legal collaborate to gather necessary information, prepare technical and financial proposals, and compile all required documentation.", "Outcome": "A complete and well-prepared tender proposal that meets all the specifications and requirements of the tender.", "GUID": "b3708b8e-2d6c-11ef-3781-0201b014c5b2", "name": "Prepare tender", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9603589042696297, "y": 1.910299003322259, "z": -0.5617449148610585 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8995", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Identify and discover new tender opportunities that align with the companys expertise and business goals.", "Process_Group": "Pre-order Management", "Scope": "The business development team scans various sources such as government portals, industry publications, and networking events to find relevant tender opportunities.", "Outcome": "The business development team scans various sources such as government portals, industry publications, and networking events to find relevant tender opportunities.", "GUID": "b3708b8a-2d6c-11ef-3781-0201b014c5b2", "name": "Discover tender opportunities", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.954045601536299, "y": 1.9136212624584719, "z": -0.6763373255253997 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8996", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Review and approve the final tender proposal before submission.", "Process_Group": "Pre-order Management", "Scope": "Senior management and relevant stakeholders review the prepared tender proposal for accuracy, completeness, and strategic alignment. Necessary adjustments are made based on feedback.", "Outcome": "n approved tender proposal that has received all necessary internal endorsements, ensuring it is ready for submission.", "GUID": "b3708b92-2d6c-11ef-3781-0201b014c5b2", "name": "Approve tender", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.949009187217637, "y": 1.9169435215946842, "z": -0.7805701060123553 }, "color": "#66CCFF", "size": 1.0 }, { "id": "8998", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Analyze the competitive landscape to understand the strengths and weaknesses of potential competitors.", "Process_Group": "Pre-order Management", "Scope": "The market research team gathers intelligence on competitors capabilities, pricing strategies, past performance, and market positioning.", "Outcome": "A competitive analysis report that highlights key competitors and their potential strategies, helping to position the companys tender proposal effectively.", "GUID": "b3708b90-2d6c-11ef-3781-0201b014c5b2", "name": "Evaluate competition", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9843338797951486, "y": 1.920265780730897, "z": -0.24983805454160277 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9012", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Continuously track the status of the submitted tender and monitor any communications or updates from the issuing authority.", "Process_Group": "Pre-order Management", "Scope": "The tender management team follows up with the issuing authority, attends clarification meetings, and stays informed about the evaluation process and timelines.", "Outcome": "Up-to-date tracking information on the tender status, ensuring prompt responses to any queries or requests for additional information from the issuing authority, and preparing for the next steps based on the tender outcome.", "GUID": "b3708b88-2d6c-11ef-3781-0201b014c5b2", "name": "Track and monitor tender", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9784159848089784, "y": 1.9235880398671097, "z": -0.3592189046171769 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9026", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Assess the companys eligibility and capability to participate in the identified tender.", "Process_Group": "Pre-order Management", "Scope": "The qualification team reviews the tender requirements, including financial stability, technical expertise, past performance, and compliance with legal and regulatory standards.", "Outcome": "A qualified tender opportunity with a go/no-go decision based on the companys ability to meet the tender requirements.", "GUID": "b3708b8c-2d6c-11ef-3781-0201b014c5b2", "name": "Check qualification for tender", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.973666715734209, "y": 1.9269102990033224, "z": -0.4582279261089441 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9038", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Officially submit the tender proposal to the issuing authority or organization.", "Process_Group": "Pre-order Management", "Scope": "The tender submission team ensures that the proposal is submitted through the appropriate channels, adhering to all submission guidelines, formats, and deadlines.", "Outcome": "The tender proposal is successfully submitted, acknowledged by the issuing authority, and logged for tracking.", "GUID": "b3708b84-2d6c-11ef-3781-0201b014c5b2", "name": "Submit tender", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.970004876199729, "y": 1.9302325581395348, "z": -0.5468560418893735 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9061", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This is important, since satisfied customers are more likely to buy from the company again. Moreover, if you evaluate the reasons fr losing a lead, you can improve your next process.", "Process_Group": "Pre-order Management", "Scope": "The final negotiations on the deal happen and now the lead can either be lost or won. If it is lost, take the learnings from it and improve processes for further customers. If it is won, it is important to followup on the customer to check on their satisfaction.", "Outcome": "An evaluation of the reasons for losing the deal or information on the customer satisfaction.", "GUID": "b3708b78-2d6c-11ef-3781-0201b014c5b2", "name": "Follow up on lead", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.96734920765793, "y": 1.9335548172757475, "z": -0.6250947399108905 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9070", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Proposing an offering in the leads to opportunity process is crucial for effectively communicating value, aligning with customer needs, advancing the sales cycle, and ultimately converting leads into successful business opportunities. It helps in building relationships, setting clear expectations, and facilitating a smoother transition from interest to commitment", "Process_Group": "Pre-order Management", "Scope": "The sales proposal usually is a formal quote, including a range of prices options. The customer needs to get all the information to make a purchasing decision. Sometimes it is necessary to send along a proof of concept, demo or video for additional convincing. ", "Outcome": "A final offer proposed for the lead to agree or disagree on.", "GUID": "b3708b76-2d6c-11ef-3781-0201b014c5b2", "name": "Propose offering", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9901766837347679, "y": 1.9368770764119603, "z": -0.19798173531536098 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9078", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "It is necessary to engage the customer in order to move them closer. Understand customer needs, provide value and qualify/ prioritise leads. ", "Process_Group": "Pre-order Management", "Scope": "In this process you nurture your leads, by engaging with them and providing relevant content. Analysing the leads needs, helps to identify how your products address the leads needs and mapping out potential solutions. Furthermore, it is essential to continuously build the relationship with the lead and address concerns.", "Outcome": "At the end of this process you have a strong relationship with your leads. Their urgent questions are answered, so they have all the information to consider the following sales offer.", "GUID": "b3708b74-2d6c-11ef-3781-0201b014c5b2", "name": "Develop lead", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.986774147726414, "y": 1.9401993355481726, "z": -0.28138974834410074 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9086", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To determine whether a potential customer is a good fit for your product or service, ensuring that time and resources are invested in leads with the highest likelihood of converting into sales. By effectively qualifying leads, companies can ensure that their sales efforts are focused on the most promising opportunities, leading to better performance and higher success rates. ", "Process_Group": "Pre-order Management", "Scope": "This process has three stages. The organization-level qualification checks whether the lead meets the criteria of the buyer persona/ ideal customer profile. The oppurtunity-level qualification determines if the prospect could actually implement my companies offering/ if they benefit from it. And in the stakeholder-level the stakeholder, having the authority to make the final purchasing decision will be identified.", "Outcome": "The outcome of qualifying a lead is a streamlined and effective sales process that focuses on high-potential prospects, ultimately leading to better business results.", "GUID": "b3708b72-2d6c-11ef-3781-0201b014c5b2", "name": "Qualify lead", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9842692388038063, "y": 1.9435215946843853, "z": -0.3543989739287317 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9087", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "To address the lead on a more personal level,their information is necessary. An organized data base helps to be time and content efficient.", "Process_Group": "Pre-order Management", "Scope": " For each lead set up a data file, including all the information known about the person/ company leads personal details, contract history, project service information, stakeholder, legal and compliance information, historical data, miscellaneous, risk management. lead set up a data file, including all the information known about the person/ company leads personal details, contract history, project service information, stakeholder, legal and compliance information, historical data, miscellaneous, risk management.", "Outcome": "A data file for each lead that can through the further processes be filled out with more information.", "GUID": "b3708b70-2d6c-11ef-3781-0201b014c5b2", "name": "Create contact", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.982580551412973, "y": 1.946843853820598, "z": -0.4170024564450474 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9088", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Determining leads is important so the sales efforts are focused on the most promising potential customers to optimize resources and increase conversion rates.", "Process_Group": "Pre-order Management", "Scope": "Conduct market research to identify potential leads that fit the target market criteria. Utilize various channels such as marketing campaigns, events and networking.", "Outcome": "Filtered out consumers/ companies that potentially fit to the companys market offering.", "GUID": "b3703d50-2d6c-11ef-3781-0201b014c5b2", "name": "Determine lead", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.981626632587544, "y": 1.9501661129568104, "z": -0.4691938067786152 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9096", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Transform the active sales opportunity into a formal sales quote, providing the customer with detailed pricing and terms for the proposed products or services.", "Process_Group": "Pre-order Management", "Scope": "The sales team generates a sales quote based on the information captured in the opportunity, including all relevant details, pricing, terms, and conditions.", "Outcome": "A comprehensive sales quote is created and sent to the customer, marking the transition from opportunity to a formal offer, and setting the stage for potential order confirmation.", "GUID": "b3708b80-2d6c-11ef-3781-0201b014c5b2", "name": "Convert opportunity into sales quote", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9946645673271033, "y": 1.9534883720930232, "z": -0.14599062932181622 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9103", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Move the sales opportunity from a preliminary stage to an active status, indicating a higher likelihood of conversion into a sales quote.", "Process_Group": "Pre-order Management", "Scope": "The sales manager reviews the opportunity, evaluates its potential, and changes its status to active, signaling a commitment to pursuing it more aggressively.", "Outcome": "The sales opportunity is activated, prioritizing it for focused sales efforts and resource allocation.", "GUID": "b3708b82-2d6c-11ef-3781-0201b014c5b2", "name": "Activate opportunity", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.993098902706469, "y": 1.956810631229236, "z": -0.2033690207906077 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9110", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Continuously update the sales opportunity with new information as the sales team gathers more insights from customer interactions.", "Process_Group": "Pre-order Management", "Scope": "Sales representatives add details such as customer feedback, updated requirements, progress notes, and any changes in customer interest or circumstances.", "Outcome": "An up-to-date sales opportunity that reflects the current status and latest information, ensuring the sales team has a clear and accurate picture of the opportunity.", "GUID": "b3708b7c-2d6c-11ef-3781-0201b014c5b2", "name": "Update opportunity", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.992159255237771, "y": 1.9601328903654487, "z": -0.25032874549161366 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9122", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Initiate a sales opportunity when a potential customer expresses interest in the companys products or services.", "Process_Group": "Pre-order Management", "Scope": "The sales team captures the initial customer interest, documenting key details such as customer information, potential products or services of interest, and any relevant notes on the customers needs.", "Outcome": "A new sales opportunity is created and recorded in the CRM system, providing a foundation for further engagement and follow-up.", "GUID": "b3708b7a-2d6c-11ef-3781-0201b014c5b2", "name": "Create sales opportunity", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.991764065605405, "y": 1.963455149501661, "z": -0.2868649740393497 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9147", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of creating an intercompany maintenance request is to facilitate the seamless coordination and execution of maintenance activities between different plants within an organization. This ensures that equipment and facilities are maintained efficiently and effectively, leveraging resources, expertise, and services from various plants to prevent failures, optimize performance, and extend asset lifespan.", "Process_Group": "Plant Maintenance Asset Management", "Scope": "This process covers the identification and documentation of maintenance needs requiring collaboration between plants, coordination of resource allocation such as spare parts, specialized equipment, and skilled personnel.", "Outcome": "The successful initiation of maintenance activities by the requesting entity.", "GUID": "8ccb1117-481b-11ef-3781-0201b014c5b2", "name": "Create intercompany maintenance request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.991831741877753, "y": 1.9667774086378738, "z": -0.31297344460226595 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9164", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Evaluate and approve intercompany maintenance request process establishes a structured method for assessing and approving requests related to maintenance activities between different entities within the same corporate group. This process ensures that maintenance requests are evaluated thoroughly, approved efficiently, and executed effectively to maintain operational continuity and asset integrity across the organization.", "Process_Group": "Plant Maintenance Asset Management", "Scope": "The scope of this process includes all maintenance requests that involve interactions between different subsidiaries and divisions within the organization. It covers requests for maintenance services and repairs. The process covers roles, responsibilities, and procedures for submitting, evaluating, approving, and monitoring intercompany maintenance requests to ensure compliance with corporate standards and regulatory requirements.", "Outcome": "Effective and timely start of maintenance activities between different entities within the organization, ensuring operational continuity and resource optimization.", "GUID": "8ccb1121-481b-11ef-3781-0201b014c5b2", "name": "Evaluate and approve intercompany maintenance request", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9977944752028278, "y": 1.9700996677740865, "z": -0.09390013231650629 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9165", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of creating an intercompany purchase order is to formalize the procurement of goods or services between different plants or entities within the same organization, ensuring clear terms of purchase, transparent intercompany billing, and efficient allocation and delivery of resources needed for operational continuity and maintenance", "Process_Group": "Intercompany Supply Chain Operations", "Scope": "The scope of creating an intercompany purchase order includes identifying and documenting the required goods or services from one plant or entity to another within the same organization, specifying the purchase terms such as quantity, price, and delivery schedules, coordinating logistics for the issuance and receipt of goods, managing the approval workflow, and ensuring compliance with internal accounting, financial tracking, and regulatory standards for transparent intercompany billing.", "Outcome": "The generation of a formal purchase order document that accurately reflects the agreed terms between the purchasing and supplying entity.", "GUID": "8ccb1136-481b-11ef-3781-0201b014c5b2", "name": "Create intercompany purchase order", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.997385943830336, "y": 1.9734219269102988, "z": -0.12520983878404124 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9168", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "Report indirect taxes process ensures the accurate and timely reporting of indirect tax obligations, such as value-added tax (VAT), goods and services tax, sales tax, and other relevant indirect taxes. This process aims to maintain compliance with tax laws and regulations, facilitate proper tax remittance, and prevent legal and financial penalties.", "Process_Group": "Statutory Reporting", "Scope": "The scope of this process includes identifying applicable indirect tax laws and regulations, gathering and verifying all relevant transaction data required for tax reporting, and applying the correct tax rates, exemptions, and credits as per the regulatory framework. It also involves preparing detailed tax reports and documentation, coordinating with internal and external tax professionals for validation and review, ensuring timely submission of tax returns and payments to tax authorities, and updating tax reporting practices in response to changes in tax laws or business operations.", "Outcome": "Accurate reporting and remittance of the organizations indirect tax obligations, supported by comprehensive documentation and timely compliance with all tax filing and payment requirements.", "GUID": "fbfa36d6-49cc-11ef-3781-0201b014c5b2", "name": "Report indirect taxes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9973313934809576, "y": 1.9767441860465116, "z": -0.14608809223063524 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9169", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose execute custom declaration process is to ensure the accurate and timely submission of customs declarations for goods entering or leaving a country. This process aims to comply with international trade regulations, facilitate the smooth clearance of goods through customs, and prevent legal and financial penalties.", "Process_Group": "Statutory Reporting", "Scope": "The scope of this process includes identifying applicable customs regulations, gathering and verifying all relevant documentation and data related to the goods being imported or exported, and classifying goods according to the appropriate tariff codes. It also involves preparing detailed customs declarations, coordinating with customs brokers and internal stakeholders for validation and review, ensuring timely submission of declarations to customs authorities, and updating customs practices in response to changes in regulations or business operations. ", "Outcome": "Accurate and compliant submission of customs declarations, supported by comprehensive documentation and timely compliance with all customs filing and payment requirements.", "GUID": "fbfa36da-49cc-11ef-3781-0201b014c5b2", "name": "Execute custom declaration", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.99754916660337, "y": 1.9800664451827243, "z": -0.1565321927974103 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9170", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to ensure the accurate and timely collection and submission of trade data regarding the movement of goods between member states of the European Union (EU). This process aims to maintain compliance with EU regulations, facilitate the monitoring of intra-EU trade, and support the production of trade statistics.", "Process_Group": "Statutory Reporting", "Scope": "This process includes identifying applicable Intrastat reporting requirements, gathering and verifying all relevant transaction data related to the movement of goods within the EU, and classifying goods according to the Intrastat nomenclature. It also involves preparing detailed Intrastat reports and documentation, coordinating with internal and external stakeholders for data validation and review, ensuring timely submission of Intrastat declarations to the relevant statistical authorities, and updating reporting practices in response to changes in regulations or business operations.", "Outcome": "Accurate and comprehensive reporting of intra-EU trade data, supported by thorough documentation and timely compliance with all Intrastat filing requirements.", "GUID": "fbfa36d8-49cc-11ef-3781-0201b014c5b2", "name": "Perform Intrastat reporting", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 5.997957587848822, "y": 1.9833887043189367, "z": -0.15654000883716612 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9171", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The purpose of this process is to ensure the accurate and timely determination of direct tax liabilities, such as corporate income tax, personal income tax, and other relevant direct taxes. This process aims to maintain compliance with tax laws and regulations, optimize tax obligations, and prevent legal and financial penalties.", "Process_Group": "Tax Accounting", "Scope": "The scope of this process includes identifying applicable direct tax laws and regulations, gathering and verifying all relevant financial data required for tax calculations, and applying the correct tax rates, deductions, credits, and allowances as per the regulatory framework. It also involves preparing detailed tax calculation reports and documentation, coordinating with internal and external tax professionals for validation and review, ensuring timely submission of tax returns and payments to tax authorities, and updating tax calculations in response to changes in tax laws or business operations.", "Outcome": "Accurate determination of the organizations direct tax liabilities, supported by comprehensive documentation and timely compliance with all tax filing and payment requirements.", "GUID": "fbfa36d3-49cc-11ef-3781-0201b014c5b2", "name": "Apply calculation for direct taxes", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 1.9995642765079822, "y": 1.9867109634551494, "z": -0.041745707720786424 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9172", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "This process focuses on maintaining optimal inventory levels in warehouse picking areas through scheduled and automated replenishment within a warehouse.", "Process_Group": "Warehouse Operations", "Scope": "When stock falls below set thresholds, replenishment tasks are created to move stock from reserve to picking areas, ensuring efficient and continuous fulfillment operations.", "Outcome": "Stock in picking areas replenished.", "GUID": "1a2215c0-700a-11ef-3781-0201b014c5b2", "name": "Perform warehouse replenishment", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 2.9996323524630535, "y": 1.9900332225913622, "z": -0.04696541341207633 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9212", "text": "Process", "data": { "Advisory_Notes": "", "Type": "Business Process", "Description": "The primary purpose of performing internal commissions settlement for sales is to accurately calculate and distribute sales commissions to eligible employees or teams. This ensures that sales personnel are fairly rewarded for their contributions, thereby motivating them to achieve sales targets and improving overall business performance.", "Process_Group": "Billing, Rebates and Commissions", "Scope": "This process involves capturing relevant sales transaction data, defining and applying commission rules based on sales agreements or company policies, accurately calculating commissions using predefined methodologies, and managing the financial settlement within the organizations financial systems.", "Outcome": "Timely payout and precise settlement of commission payments to sales representatives as well as enhanced employee satisfaction and motivation, improved accuracy in financial records, and greater transparency in commission-related transactions.", "GUID": "307f29d4-438b-11ef-3781-0201b014c5b2", "name": "Perform internal commissions settlement for sales", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 3.9997821323207003, "y": 1.993355481727575, "z": -0.04174798160475205 }, "color": "#66CCFF", "size": 1.0 }, { "id": "9234", "text": "Process", "data": { "Advisory_Notes": "Consider that some chemical companies are actually developing new chemical substances, for that the whole process of registering and developing master data is much more complex and requires interactions with authorities.", "Type": "Business Process", "Description": "This process describes maintenance of chemical compliance master data ensuring the compliance assessment of chemical substances and their suppliers.", "Process_Group": "Compliance Master Data", "Scope": "It involves requesting compliance data from chemical suppliers, approving or blocking suppliers based on this data, maintaining supplier compliance data, and assessing whether the chemical substances meet the necessary requirements.", "Outcome": "Approved suppliers and chemicals are documented, with detailed chemical compliance master data.", "GUID": "46bcf430-74d1-11ef-3781-0201b014c5b2", "name": "Maintain chemical compliance master data", "Business_Rules": "", "Prerequisite": "" }, "position": { "x": 4.999931915886674, "y": 1.9966777408637872, "z": -0.02609284380459756 }, "color": "#66CCFF", "size": 1.0 } ], "links": [ { "id": "L0", "source": "6", "target": "1971", "type": "PROCESS_OF" }, { "id": "L1", "source": "6", "target": "4", "type": "PROCESS_OF" }, { "id": "L2", "source": "7", "target": "1971", "type": "PROCESS_OF" }, { "id": "L3", "source": "7", "target": "4", "type": "PROCESS_OF" }, { "id": "L4", "source": "8", "target": "1971", "type": "PROCESS_OF" }, { "id": "L5", "source": "8", "target": "4", "type": "PROCESS_OF" }, { "id": "L6", "source": "9", "target": "1971", "type": "PROCESS_OF" }, { "id": "L7", "source": "9", "target": "4", "type": "PROCESS_OF" }, { "id": "L8", "source": "10", "target": "1971", "type": "PROCESS_OF" }, { "id": "L9", "source": "10", "target": "4", "type": "PROCESS_OF" }, { "id": "L10", "source": "11", "target": "1971", "type": "PROCESS_OF" }, { "id": "L11", "source": "11", "target": "4", "type": "PROCESS_OF" }, { "id": "L12", "source": "12", "target": "1971", "type": "PROCESS_OF" }, { "id": "L13", "source": "12", "target": "4", "type": "PROCESS_OF" }, { "id": "L14", "source": "13", "target": "1971", "type": "PROCESS_OF" }, { "id": "L15", "source": "13", "target": "4", "type": "PROCESS_OF" }, { "id": "L16", "source": "14", "target": "1971", "type": "PROCESS_OF" }, { "id": "L17", "source": "14", "target": "4", "type": "PROCESS_OF" }, { "id": "L18", "source": "18", "target": "1971", "type": "PROCESS_OF" }, { "id": "L19", "source": "18", "target": "16", "type": "PROCESS_OF" }, { "id": "L20", "source": "20", "target": "1971", "type": "PROCESS_OF" }, { "id": "L21", "source": "20", "target": "16", "type": "PROCESS_OF" }, { "id": "L22", "source": "22", "target": "1971", "type": "PROCESS_OF" }, { "id": "L23", "source": "22", "target": "16", "type": "PROCESS_OF" }, { "id": "L24", "source": "24", "target": "1971", "type": "PROCESS_OF" }, { "id": "L25", "source": "24", "target": "16", "type": "PROCESS_OF" }, { "id": "L26", "source": "29", "target": "2088", "type": "PROCESS_OF" }, { "id": "L27", "source": "29", "target": "27", "type": "PROCESS_OF" }, { "id": "L28", "source": "30", "target": "2032", "type": "PROCESS_OF" }, { "id": "L29", "source": "30", "target": "2049", "type": "PROCESS_OF" }, { "id": "L30", "source": "30", "target": "51", "type": "PROCESS_OF" }, { "id": "L31", "source": "30", "target": "27", "type": "PROCESS_OF" }, { "id": "L32", "source": "31", "target": "27", "type": "PROCESS_OF" }, { "id": "L33", "source": "32", "target": "2102", "type": "PROCESS_OF" }, { "id": "L34", "source": "32", "target": "27", "type": "PROCESS_OF" }, { "id": "L35", "source": "33", "target": "2088", "type": "PROCESS_OF" }, { "id": "L36", "source": "33", "target": "27", "type": "PROCESS_OF" }, { "id": "L37", "source": "34", "target": "2049", "type": "PROCESS_OF" }, { "id": "L38", "source": "34", "target": "27", "type": "PROCESS_OF" }, { "id": "L39", "source": "35", "target": "2049", "type": "PROCESS_OF" }, { "id": "L40", "source": "35", "target": "27", "type": "PROCESS_OF" }, { "id": "L41", "source": "36", "target": "2049", "type": "PROCESS_OF" }, { "id": "L42", "source": "36", "target": "27", "type": "PROCESS_OF" }, { "id": "L43", "source": "37", "target": "2102", "type": "PROCESS_OF" }, { "id": "L44", "source": "37", "target": "27", "type": "PROCESS_OF" }, { "id": "L45", "source": "38", "target": "2102", "type": "PROCESS_OF" }, { "id": "L46", "source": "38", "target": "27", "type": "PROCESS_OF" }, { "id": "L47", "source": "40", "target": "2102", "type": "PROCESS_OF" }, { "id": "L48", "source": "40", "target": "27", "type": "PROCESS_OF" }, { "id": "L49", "source": "42", "target": "2000", "type": "PROCESS_OF" }, { "id": "L50", "source": "42", "target": "27", "type": "PROCESS_OF" }, { "id": "L51", "source": "44", "target": "2040", "type": "PROCESS_OF" }, { "id": "L52", "source": "44", "target": "27", "type": "PROCESS_OF" }, { "id": "L53", "source": "46", "target": "2049", "type": "PROCESS_OF" }, { "id": "L54", "source": "46", "target": "27", "type": "PROCESS_OF" }, { "id": "L55", "source": "48", "target": "2049", "type": "PROCESS_OF" }, { "id": "L56", "source": "48", "target": "27", "type": "PROCESS_OF" }, { "id": "L57", "source": "49", "target": "2013", "type": "PROCESS_OF" }, { "id": "L58", "source": "49", "target": "27", "type": "PROCESS_OF" }, { "id": "L59", "source": "53", "target": "2049", "type": "PROCESS_OF" }, { "id": "L60", "source": "53", "target": "51", "type": "PROCESS_OF" }, { "id": "L61", "source": "54", "target": "2049", "type": "PROCESS_OF" }, { "id": "L62", "source": "54", "target": "51", "type": "PROCESS_OF" }, { "id": "L63", "source": "55", "target": "2049", "type": "PROCESS_OF" }, { "id": "L64", "source": "55", "target": "51", "type": "PROCESS_OF" }, { "id": "L65", "source": "56", "target": "2049", "type": "PROCESS_OF" }, { "id": "L66", "source": "56", "target": "51", "type": "PROCESS_OF" }, { "id": "L67", "source": "57", "target": "2049", "type": "PROCESS_OF" }, { "id": "L68", "source": "57", "target": "51", "type": "PROCESS_OF" }, { "id": "L69", "source": "58", "target": "2102", "type": "PROCESS_OF" }, { "id": "L70", "source": "58", "target": "51", "type": "PROCESS_OF" }, { "id": "L71", "source": "59", "target": "2102", "type": "PROCESS_OF" }, { "id": "L72", "source": "59", "target": "51", "type": "PROCESS_OF" }, { "id": "L73", "source": "60", "target": "2049", "type": "PROCESS_OF" }, { "id": "L74", "source": "60", "target": "51", "type": "PROCESS_OF" }, { "id": "L75", "source": "61", "target": "2049", "type": "PROCESS_OF" }, { "id": "L76", "source": "61", "target": "51", "type": "PROCESS_OF" }, { "id": "L77", "source": "67", "target": "2088", "type": "PROCESS_OF" }, { "id": "L78", "source": "67", "target": "73", "type": "PROCESS_OF" }, { "id": "L79", "source": "67", "target": "65", "type": "PROCESS_OF" }, { "id": "L80", "source": "69", "target": "2088", "type": "PROCESS_OF" }, { "id": "L81", "source": "69", "target": "65", "type": "PROCESS_OF" }, { "id": "L82", "source": "71", "target": "2088", "type": "PROCESS_OF" }, { "id": "L83", "source": "71", "target": "65", "type": "PROCESS_OF" }, { "id": "L84", "source": "75", "target": "2060", "type": "PROCESS_OF" }, { "id": "L85", "source": "75", "target": "73", "type": "PROCESS_OF" }, { "id": "L86", "source": "77", "target": "2060", "type": "PROCESS_OF" }, { "id": "L87", "source": "77", "target": "73", "type": "PROCESS_OF" }, { "id": "L88", "source": "79", "target": "2060", "type": "PROCESS_OF" }, { "id": "L89", "source": "79", "target": "73", "type": "PROCESS_OF" }, { "id": "L90", "source": "81", "target": "2060", "type": "PROCESS_OF" }, { "id": "L91", "source": "81", "target": "73", "type": "PROCESS_OF" }, { "id": "L92", "source": "83", "target": "2060", "type": "PROCESS_OF" }, { "id": "L93", "source": "83", "target": "73", "type": "PROCESS_OF" }, { "id": "L94", "source": "85", "target": "2088", "type": "PROCESS_OF" }, { "id": "L95", "source": "85", "target": "73", "type": "PROCESS_OF" }, { "id": "L96", "source": "89", "target": "2088", "type": "PROCESS_OF" }, { "id": "L97", "source": "89", "target": "87", "type": "PROCESS_OF" }, { "id": "L98", "source": "91", "target": "2088", "type": "PROCESS_OF" }, { "id": "L99", "source": "91", "target": "87", "type": "PROCESS_OF" }, { "id": "L100", "source": "93", "target": "2088", "type": "PROCESS_OF" }, { "id": "L101", "source": "93", "target": "87", "type": "PROCESS_OF" }, { "id": "L102", "source": "95", "target": "2088", "type": "PROCESS_OF" }, { "id": "L103", "source": "95", "target": "87", "type": "PROCESS_OF" }, { "id": "L104", "source": "99", "target": "2060", "type": "PROCESS_OF" }, { "id": "L105", "source": "100", "target": "2060", "type": "PROCESS_OF" }, { "id": "L106", "source": "102", "target": "2060", "type": "PROCESS_OF" }, { "id": "L107", "source": "104", "target": "2060", "type": "PROCESS_OF" }, { "id": "L108", "source": "109", "target": "619", "type": "PROCESS_OF" }, { "id": "L109", "source": "109", "target": "2040", "type": "PROCESS_OF" }, { "id": "L110", "source": "109", "target": "126", "type": "PROCESS_OF" }, { "id": "L111", "source": "109", "target": "107", "type": "PROCESS_OF" }, { "id": "L112", "source": "111", "target": "2040", "type": "PROCESS_OF" }, { "id": "L113", "source": "111", "target": "126", "type": "PROCESS_OF" }, { "id": "L114", "source": "111", "target": "107", "type": "PROCESS_OF" }, { "id": "L115", "source": "113", "target": "1044", "type": "PROCESS_OF" }, { "id": "L116", "source": "113", "target": "689", "type": "PROCESS_OF" }, { "id": "L117", "source": "113", "target": "2040", "type": "PROCESS_OF" }, { "id": "L118", "source": "113", "target": "136", "type": "PROCESS_OF" }, { "id": "L119", "source": "113", "target": "126", "type": "PROCESS_OF" }, { "id": "L120", "source": "113", "target": "107", "type": "PROCESS_OF" }, { "id": "L121", "source": "117", "target": "1957", "type": "PROCESS_OF" }, { "id": "L122", "source": "117", "target": "115", "type": "PROCESS_OF" }, { "id": "L123", "source": "118", "target": "1957", "type": "PROCESS_OF" }, { "id": "L124", "source": "118", "target": "115", "type": "PROCESS_OF" }, { "id": "L125", "source": "119", "target": "8629", "type": "PROCESS_OF" }, { "id": "L126", "source": "119", "target": "1957", "type": "PROCESS_OF" }, { "id": "L127", "source": "119", "target": "115", "type": "PROCESS_OF" }, { "id": "L128", "source": "120", "target": "8563", "type": "PROCESS_OF" }, { "id": "L129", "source": "120", "target": "1380", "type": "PROCESS_OF" }, { "id": "L130", "source": "120", "target": "8501", "type": "PROCESS_OF" }, { "id": "L131", "source": "120", "target": "1663", "type": "PROCESS_OF" }, { "id": "L132", "source": "120", "target": "1475", "type": "PROCESS_OF" }, { "id": "L133", "source": "120", "target": "401", "type": "PROCESS_OF" }, { "id": "L134", "source": "120", "target": "2013", "type": "PROCESS_OF" }, { "id": "L135", "source": "120", "target": "289", "type": "PROCESS_OF" }, { "id": "L136", "source": "120", "target": "132", "type": "PROCESS_OF" }, { "id": "L137", "source": "120", "target": "115", "type": "PROCESS_OF" }, { "id": "L138", "source": "122", "target": "2013", "type": "PROCESS_OF" }, { "id": "L139", "source": "122", "target": "115", "type": "PROCESS_OF" }, { "id": "L140", "source": "124", "target": "1957", "type": "PROCESS_OF" }, { "id": "L141", "source": "124", "target": "115", "type": "PROCESS_OF" }, { "id": "L142", "source": "128", "target": "8531", "type": "PROCESS_OF" }, { "id": "L143", "source": "128", "target": "670", "type": "PROCESS_OF" }, { "id": "L144", "source": "128", "target": "662", "type": "PROCESS_OF" }, { "id": "L145", "source": "128", "target": "631", "type": "PROCESS_OF" }, { "id": "L146", "source": "128", "target": "614", "type": "PROCESS_OF" }, { "id": "L147", "source": "128", "target": "612", "type": "PROCESS_OF" }, { "id": "L148", "source": "128", "target": "603", "type": "PROCESS_OF" }, { "id": "L149", "source": "128", "target": "597", "type": "PROCESS_OF" }, { "id": "L150", "source": "128", "target": "587", "type": "PROCESS_OF" }, { "id": "L151", "source": "128", "target": "583", "type": "PROCESS_OF" }, { "id": "L152", "source": "128", "target": "580", "type": "PROCESS_OF" }, { "id": "L153", "source": "128", "target": "554", "type": "PROCESS_OF" }, { "id": "L154", "source": "128", "target": "545", "type": "PROCESS_OF" }, { "id": "L155", "source": "128", "target": "539", "type": "PROCESS_OF" }, { "id": "L156", "source": "128", "target": "493", "type": "PROCESS_OF" }, { "id": "L157", "source": "128", "target": "2040", "type": "PROCESS_OF" }, { "id": "L158", "source": "128", "target": "126", "type": "PROCESS_OF" }, { "id": "L159", "source": "130", "target": "2040", "type": "PROCESS_OF" }, { "id": "L160", "source": "130", "target": "126", "type": "PROCESS_OF" }, { "id": "L161", "source": "134", "target": "401", "type": "PROCESS_OF" }, { "id": "L162", "source": "134", "target": "2013", "type": "PROCESS_OF" }, { "id": "L163", "source": "134", "target": "132", "type": "PROCESS_OF" }, { "id": "L164", "source": "138", "target": "1957", "type": "PROCESS_OF" }, { "id": "L165", "source": "138", "target": "136", "type": "PROCESS_OF" }, { "id": "L166", "source": "139", "target": "1957", "type": "PROCESS_OF" }, { "id": "L167", "source": "139", "target": "136", "type": "PROCESS_OF" }, { "id": "L168", "source": "141", "target": "1957", "type": "PROCESS_OF" }, { "id": "L169", "source": "141", "target": "136", "type": "PROCESS_OF" }, { "id": "L170", "source": "142", "target": "619", "type": "PROCESS_OF" }, { "id": "L171", "source": "142", "target": "2040", "type": "PROCESS_OF" }, { "id": "L172", "source": "142", "target": "136", "type": "PROCESS_OF" }, { "id": "L173", "source": "145", "target": "1957", "type": "PROCESS_OF" }, { "id": "L174", "source": "145", "target": "143", "type": "PROCESS_OF" }, { "id": "L175", "source": "147", "target": "2032", "type": "PROCESS_OF" }, { "id": "L176", "source": "147", "target": "8629", "type": "PROCESS_OF" }, { "id": "L177", "source": "147", "target": "2013", "type": "PROCESS_OF" }, { "id": "L178", "source": "147", "target": "143", "type": "PROCESS_OF" }, { "id": "L179", "source": "152", "target": "2013", "type": "PROCESS_OF" }, { "id": "L180", "source": "152", "target": "150", "type": "PROCESS_OF" }, { "id": "L181", "source": "154", "target": "8666", "type": "PROCESS_OF" }, { "id": "L182", "source": "154", "target": "8500", "type": "PROCESS_OF" }, { "id": "L183", "source": "154", "target": "9125", "type": "PROCESS_OF" }, { "id": "L184", "source": "154", "target": "576", "type": "PROCESS_OF" }, { "id": "L185", "source": "154", "target": "489", "type": "PROCESS_OF" }, { "id": "L186", "source": "154", "target": "471", "type": "PROCESS_OF" }, { "id": "L187", "source": "154", "target": "1957", "type": "PROCESS_OF" }, { "id": "L188", "source": "154", "target": "150", "type": "PROCESS_OF" }, { "id": "L189", "source": "156", "target": "2040", "type": "PROCESS_OF" }, { "id": "L190", "source": "156", "target": "150", "type": "PROCESS_OF" }, { "id": "L191", "source": "158", "target": "2013", "type": "PROCESS_OF" }, { "id": "L192", "source": "158", "target": "150", "type": "PROCESS_OF" }, { "id": "L193", "source": "160", "target": "2040", "type": "PROCESS_OF" }, { "id": "L194", "source": "160", "target": "150", "type": "PROCESS_OF" }, { "id": "L195", "source": "162", "target": "2013", "type": "PROCESS_OF" }, { "id": "L196", "source": "162", "target": "150", "type": "PROCESS_OF" }, { "id": "L197", "source": "164", "target": "2013", "type": "PROCESS_OF" }, { "id": "L198", "source": "164", "target": "150", "type": "PROCESS_OF" }, { "id": "L199", "source": "170", "target": "8563", "type": "PROCESS_OF" }, { "id": "L200", "source": "170", "target": "1475", "type": "PROCESS_OF" }, { "id": "L201", "source": "170", "target": "732", "type": "PROCESS_OF" }, { "id": "L202", "source": "170", "target": "713", "type": "PROCESS_OF" }, { "id": "L203", "source": "170", "target": "392", "type": "PROCESS_OF" }, { "id": "L204", "source": "170", "target": "386", "type": "PROCESS_OF" }, { "id": "L205", "source": "170", "target": "1831", "type": "PROCESS_OF" }, { "id": "L206", "source": "170", "target": "168", "type": "PROCESS_OF" }, { "id": "L207", "source": "172", "target": "8563", "type": "PROCESS_OF" }, { "id": "L208", "source": "172", "target": "1475", "type": "PROCESS_OF" }, { "id": "L209", "source": "172", "target": "732", "type": "PROCESS_OF" }, { "id": "L210", "source": "172", "target": "713", "type": "PROCESS_OF" }, { "id": "L211", "source": "172", "target": "392", "type": "PROCESS_OF" }, { "id": "L212", "source": "172", "target": "386", "type": "PROCESS_OF" }, { "id": "L213", "source": "172", "target": "362", "type": "PROCESS_OF" }, { "id": "L214", "source": "172", "target": "1831", "type": "PROCESS_OF" }, { "id": "L215", "source": "172", "target": "168", "type": "PROCESS_OF" }, { "id": "L216", "source": "174", "target": "1475", "type": "PROCESS_OF" }, { "id": "L217", "source": "174", "target": "8563", "type": "PROCESS_OF" }, { "id": "L218", "source": "174", "target": "1181", "type": "PROCESS_OF" }, { "id": "L219", "source": "174", "target": "732", "type": "PROCESS_OF" }, { "id": "L220", "source": "174", "target": "713", "type": "PROCESS_OF" }, { "id": "L221", "source": "174", "target": "452", "type": "PROCESS_OF" }, { "id": "L222", "source": "174", "target": "1831", "type": "PROCESS_OF" }, { "id": "L223", "source": "174", "target": "168", "type": "PROCESS_OF" }, { "id": "L224", "source": "176", "target": "1940", "type": "PROCESS_OF" }, { "id": "L225", "source": "176", "target": "228", "type": "PROCESS_OF" }, { "id": "L226", "source": "176", "target": "168", "type": "PROCESS_OF" }, { "id": "L227", "source": "178", "target": "8563", "type": "PROCESS_OF" }, { "id": "L228", "source": "178", "target": "1475", "type": "PROCESS_OF" }, { "id": "L229", "source": "178", "target": "732", "type": "PROCESS_OF" }, { "id": "L230", "source": "178", "target": "713", "type": "PROCESS_OF" }, { "id": "L231", "source": "178", "target": "392", "type": "PROCESS_OF" }, { "id": "L232", "source": "178", "target": "386", "type": "PROCESS_OF" }, { "id": "L233", "source": "178", "target": "228", "type": "PROCESS_OF" }, { "id": "L234", "source": "178", "target": "1831", "type": "PROCESS_OF" }, { "id": "L235", "source": "178", "target": "168", "type": "PROCESS_OF" }, { "id": "L236", "source": "180", "target": "8563", "type": "PROCESS_OF" }, { "id": "L237", "source": "180", "target": "1475", "type": "PROCESS_OF" }, { "id": "L238", "source": "180", "target": "732", "type": "PROCESS_OF" }, { "id": "L239", "source": "180", "target": "713", "type": "PROCESS_OF" }, { "id": "L240", "source": "180", "target": "392", "type": "PROCESS_OF" }, { "id": "L241", "source": "180", "target": "386", "type": "PROCESS_OF" }, { "id": "L242", "source": "180", "target": "1977", "type": "PROCESS_OF" }, { "id": "L243", "source": "180", "target": "228", "type": "PROCESS_OF" }, { "id": "L244", "source": "180", "target": "168", "type": "PROCESS_OF" }, { "id": "L245", "source": "182", "target": "732", "type": "PROCESS_OF" }, { "id": "L246", "source": "182", "target": "713", "type": "PROCESS_OF" }, { "id": "L247", "source": "182", "target": "1831", "type": "PROCESS_OF" }, { "id": "L248", "source": "182", "target": "168", "type": "PROCESS_OF" }, { "id": "L249", "source": "184", "target": "1940", "type": "PROCESS_OF" }, { "id": "L250", "source": "184", "target": "168", "type": "PROCESS_OF" }, { "id": "L251", "source": "185", "target": "1940", "type": "PROCESS_OF" }, { "id": "L252", "source": "185", "target": "168", "type": "PROCESS_OF" }, { "id": "L253", "source": "187", "target": "2163", "type": "PROCESS_OF" }, { "id": "L254", "source": "187", "target": "228", "type": "PROCESS_OF" }, { "id": "L255", "source": "187", "target": "168", "type": "PROCESS_OF" }, { "id": "L256", "source": "189", "target": "1940", "type": "PROCESS_OF" }, { "id": "L257", "source": "189", "target": "228", "type": "PROCESS_OF" }, { "id": "L258", "source": "189", "target": "168", "type": "PROCESS_OF" }, { "id": "L259", "source": "191", "target": "2163", "type": "PROCESS_OF" }, { "id": "L260", "source": "191", "target": "168", "type": "PROCESS_OF" }, { "id": "L261", "source": "194", "target": "218", "type": "PROCESS_OF" }, { "id": "L262", "source": "194", "target": "1797", "type": "PROCESS_OF" }, { "id": "L263", "source": "194", "target": "192", "type": "PROCESS_OF" }, { "id": "L264", "source": "196", "target": "2217", "type": "PROCESS_OF" }, { "id": "L265", "source": "196", "target": "192", "type": "PROCESS_OF" }, { "id": "L266", "source": "198", "target": "1940", "type": "PROCESS_OF" }, { "id": "L267", "source": "198", "target": "192", "type": "PROCESS_OF" }, { "id": "L268", "source": "200", "target": "218", "type": "PROCESS_OF" }, { "id": "L269", "source": "200", "target": "192", "type": "PROCESS_OF" }, { "id": "L270", "source": "201", "target": "761", "type": "PROCESS_OF" }, { "id": "L271", "source": "201", "target": "1797", "type": "PROCESS_OF" }, { "id": "L272", "source": "201", "target": "218", "type": "PROCESS_OF" }, { "id": "L273", "source": "201", "target": "192", "type": "PROCESS_OF" }, { "id": "L274", "source": "203", "target": "1940", "type": "PROCESS_OF" }, { "id": "L275", "source": "203", "target": "192", "type": "PROCESS_OF" }, { "id": "L276", "source": "205", "target": "1797", "type": "PROCESS_OF" }, { "id": "L277", "source": "205", "target": "761", "type": "PROCESS_OF" }, { "id": "L278", "source": "205", "target": "218", "type": "PROCESS_OF" }, { "id": "L279", "source": "205", "target": "192", "type": "PROCESS_OF" }, { "id": "L280", "source": "207", "target": "218", "type": "PROCESS_OF" }, { "id": "L281", "source": "207", "target": "1797", "type": "PROCESS_OF" }, { "id": "L282", "source": "207", "target": "192", "type": "PROCESS_OF" }, { "id": "L283", "source": "209", "target": "1940", "type": "PROCESS_OF" }, { "id": "L284", "source": "209", "target": "192", "type": "PROCESS_OF" }, { "id": "L285", "source": "211", "target": "761", "type": "PROCESS_OF" }, { "id": "L286", "source": "211", "target": "1797", "type": "PROCESS_OF" }, { "id": "L287", "source": "211", "target": "218", "type": "PROCESS_OF" }, { "id": "L288", "source": "211", "target": "192", "type": "PROCESS_OF" }, { "id": "L289", "source": "213", "target": "1797", "type": "PROCESS_OF" }, { "id": "L290", "source": "213", "target": "218", "type": "PROCESS_OF" }, { "id": "L291", "source": "213", "target": "192", "type": "PROCESS_OF" }, { "id": "L292", "source": "214", "target": "2163", "type": "PROCESS_OF" }, { "id": "L293", "source": "214", "target": "218", "type": "PROCESS_OF" }, { "id": "L294", "source": "214", "target": "192", "type": "PROCESS_OF" }, { "id": "L295", "source": "216", "target": "1940", "type": "PROCESS_OF" }, { "id": "L296", "source": "216", "target": "192", "type": "PROCESS_OF" }, { "id": "L297", "source": "220", "target": "218", "type": "PROCESS_OF" }, { "id": "L298", "source": "221", "target": "1790", "type": "PROCESS_OF" }, { "id": "L299", "source": "221", "target": "218", "type": "PROCESS_OF" }, { "id": "L300", "source": "222", "target": "218", "type": "PROCESS_OF" }, { "id": "L301", "source": "223", "target": "1940", "type": "PROCESS_OF" }, { "id": "L302", "source": "223", "target": "228", "type": "PROCESS_OF" }, { "id": "L303", "source": "223", "target": "218", "type": "PROCESS_OF" }, { "id": "L304", "source": "225", "target": "1471", "type": "PROCESS_OF" }, { "id": "L305", "source": "225", "target": "2203", "type": "PROCESS_OF" }, { "id": "L306", "source": "225", "target": "218", "type": "PROCESS_OF" }, { "id": "L307", "source": "226", "target": "2203", "type": "PROCESS_OF" }, { "id": "L308", "source": "226", "target": "218", "type": "PROCESS_OF" }, { "id": "L309", "source": "230", "target": "1940", "type": "PROCESS_OF" }, { "id": "L310", "source": "230", "target": "228", "type": "PROCESS_OF" }, { "id": "L311", "source": "231", "target": "1940", "type": "PROCESS_OF" }, { "id": "L312", "source": "231", "target": "228", "type": "PROCESS_OF" }, { "id": "L313", "source": "233", "target": "1940", "type": "PROCESS_OF" }, { "id": "L314", "source": "233", "target": "228", "type": "PROCESS_OF" }, { "id": "L315", "source": "235", "target": "1940", "type": "PROCESS_OF" }, { "id": "L316", "source": "235", "target": "228", "type": "PROCESS_OF" }, { "id": "L317", "source": "240", "target": "1939", "type": "PROCESS_OF" }, { "id": "L318", "source": "240", "target": "247", "type": "PROCESS_OF" }, { "id": "L319", "source": "240", "target": "238", "type": "PROCESS_OF" }, { "id": "L320", "source": "242", "target": "1939", "type": "PROCESS_OF" }, { "id": "L321", "source": "242", "target": "238", "type": "PROCESS_OF" }, { "id": "L322", "source": "244", "target": "1939", "type": "PROCESS_OF" }, { "id": "L323", "source": "244", "target": "238", "type": "PROCESS_OF" }, { "id": "L324", "source": "245", "target": "1939", "type": "PROCESS_OF" }, { "id": "L325", "source": "245", "target": "238", "type": "PROCESS_OF" }, { "id": "L326", "source": "249", "target": "1787", "type": "PROCESS_OF" }, { "id": "L327", "source": "249", "target": "247", "type": "PROCESS_OF" }, { "id": "L328", "source": "251", "target": "1939", "type": "PROCESS_OF" }, { "id": "L329", "source": "251", "target": "247", "type": "PROCESS_OF" }, { "id": "L330", "source": "253", "target": "1939", "type": "PROCESS_OF" }, { "id": "L331", "source": "253", "target": "247", "type": "PROCESS_OF" }, { "id": "L332", "source": "255", "target": "1775", "type": "PROCESS_OF" }, { "id": "L333", "source": "255", "target": "2210", "type": "PROCESS_OF" }, { "id": "L334", "source": "255", "target": "247", "type": "PROCESS_OF" }, { "id": "L335", "source": "257", "target": "2206", "type": "PROCESS_OF" }, { "id": "L336", "source": "257", "target": "247", "type": "PROCESS_OF" }, { "id": "L337", "source": "259", "target": "1950", "type": "PROCESS_OF" }, { "id": "L338", "source": "259", "target": "247", "type": "PROCESS_OF" }, { "id": "L339", "source": "265", "target": "2141", "type": "PROCESS_OF" }, { "id": "L340", "source": "265", "target": "263", "type": "PROCESS_OF" }, { "id": "L341", "source": "266", "target": "2141", "type": "PROCESS_OF" }, { "id": "L342", "source": "266", "target": "263", "type": "PROCESS_OF" }, { "id": "L343", "source": "267", "target": "2141", "type": "PROCESS_OF" }, { "id": "L344", "source": "267", "target": "263", "type": "PROCESS_OF" }, { "id": "L345", "source": "268", "target": "2141", "type": "PROCESS_OF" }, { "id": "L346", "source": "268", "target": "263", "type": "PROCESS_OF" }, { "id": "L347", "source": "272", "target": "2143", "type": "PROCESS_OF" }, { "id": "L348", "source": "272", "target": "270", "type": "PROCESS_OF" }, { "id": "L349", "source": "273", "target": "2143", "type": "PROCESS_OF" }, { "id": "L350", "source": "273", "target": "270", "type": "PROCESS_OF" }, { "id": "L351", "source": "274", "target": "2143", "type": "PROCESS_OF" }, { "id": "L352", "source": "274", "target": "270", "type": "PROCESS_OF" }, { "id": "L353", "source": "275", "target": "2143", "type": "PROCESS_OF" }, { "id": "L354", "source": "275", "target": "270", "type": "PROCESS_OF" }, { "id": "L355", "source": "279", "target": "2163", "type": "PROCESS_OF" }, { "id": "L356", "source": "279", "target": "277", "type": "PROCESS_OF" }, { "id": "L357", "source": "280", "target": "2163", "type": "PROCESS_OF" }, { "id": "L358", "source": "280", "target": "277", "type": "PROCESS_OF" }, { "id": "L359", "source": "281", "target": "2163", "type": "PROCESS_OF" }, { "id": "L360", "source": "281", "target": "277", "type": "PROCESS_OF" }, { "id": "L361", "source": "283", "target": "2163", "type": "PROCESS_OF" }, { "id": "L362", "source": "283", "target": "277", "type": "PROCESS_OF" }, { "id": "L363", "source": "284", "target": "2163", "type": "PROCESS_OF" }, { "id": "L364", "source": "284", "target": "277", "type": "PROCESS_OF" }, { "id": "L365", "source": "285", "target": "2163", "type": "PROCESS_OF" }, { "id": "L366", "source": "285", "target": "277", "type": "PROCESS_OF" }, { "id": "L367", "source": "286", "target": "2163", "type": "PROCESS_OF" }, { "id": "L368", "source": "286", "target": "277", "type": "PROCESS_OF" }, { "id": "L369", "source": "291", "target": "1413", "type": "PROCESS_OF" }, { "id": "L370", "source": "291", "target": "1399", "type": "PROCESS_OF" }, { "id": "L371", "source": "291", "target": "1390", "type": "PROCESS_OF" }, { "id": "L372", "source": "291", "target": "489", "type": "PROCESS_OF" }, { "id": "L373", "source": "291", "target": "471", "type": "PROCESS_OF" }, { "id": "L374", "source": "291", "target": "450", "type": "PROCESS_OF" }, { "id": "L375", "source": "291", "target": "392", "type": "PROCESS_OF" }, { "id": "L376", "source": "291", "target": "386", "type": "PROCESS_OF" }, { "id": "L377", "source": "291", "target": "376", "type": "PROCESS_OF" }, { "id": "L378", "source": "291", "target": "362", "type": "PROCESS_OF" }, { "id": "L379", "source": "291", "target": "356", "type": "PROCESS_OF" }, { "id": "L380", "source": "291", "target": "348", "type": "PROCESS_OF" }, { "id": "L381", "source": "291", "target": "289", "type": "PROCESS_OF" }, { "id": "L382", "source": "291", "target": "1832", "type": "PROCESS_OF" }, { "id": "L383", "source": "293", "target": "489", "type": "PROCESS_OF" }, { "id": "L384", "source": "293", "target": "450", "type": "PROCESS_OF" }, { "id": "L385", "source": "293", "target": "422", "type": "PROCESS_OF" }, { "id": "L386", "source": "293", "target": "1947", "type": "PROCESS_OF" }, { "id": "L387", "source": "293", "target": "356", "type": "PROCESS_OF" }, { "id": "L388", "source": "293", "target": "348", "type": "PROCESS_OF" }, { "id": "L389", "source": "293", "target": "315", "type": "PROCESS_OF" }, { "id": "L390", "source": "293", "target": "289", "type": "PROCESS_OF" }, { "id": "L391", "source": "295", "target": "1957", "type": "PROCESS_OF" }, { "id": "L392", "source": "295", "target": "289", "type": "PROCESS_OF" }, { "id": "L393", "source": "297", "target": "1185", "type": "PROCESS_OF" }, { "id": "L394", "source": "297", "target": "1163", "type": "PROCESS_OF" }, { "id": "L395", "source": "297", "target": "489", "type": "PROCESS_OF" }, { "id": "L396", "source": "297", "target": "471", "type": "PROCESS_OF" }, { "id": "L397", "source": "297", "target": "450", "type": "PROCESS_OF" }, { "id": "L398", "source": "297", "target": "440", "type": "PROCESS_OF" }, { "id": "L399", "source": "297", "target": "422", "type": "PROCESS_OF" }, { "id": "L400", "source": "297", "target": "1961", "type": "PROCESS_OF" }, { "id": "L401", "source": "297", "target": "376", "type": "PROCESS_OF" }, { "id": "L402", "source": "297", "target": "356", "type": "PROCESS_OF" }, { "id": "L403", "source": "297", "target": "348", "type": "PROCESS_OF" }, { "id": "L404", "source": "297", "target": "338", "type": "PROCESS_OF" }, { "id": "L405", "source": "297", "target": "326", "type": "PROCESS_OF" }, { "id": "L406", "source": "297", "target": "315", "type": "PROCESS_OF" }, { "id": "L407", "source": "297", "target": "289", "type": "PROCESS_OF" }, { "id": "L408", "source": "299", "target": "2013", "type": "PROCESS_OF" }, { "id": "L409", "source": "299", "target": "289", "type": "PROCESS_OF" }, { "id": "L410", "source": "301", "target": "1757", "type": "PROCESS_OF" }, { "id": "L411", "source": "301", "target": "1511", "type": "PROCESS_OF" }, { "id": "L412", "source": "301", "target": "489", "type": "PROCESS_OF" }, { "id": "L413", "source": "301", "target": "471", "type": "PROCESS_OF" }, { "id": "L414", "source": "301", "target": "452", "type": "PROCESS_OF" }, { "id": "L415", "source": "301", "target": "450", "type": "PROCESS_OF" }, { "id": "L416", "source": "301", "target": "422", "type": "PROCESS_OF" }, { "id": "L417", "source": "301", "target": "392", "type": "PROCESS_OF" }, { "id": "L418", "source": "301", "target": "1986", "type": "PROCESS_OF" }, { "id": "L419", "source": "301", "target": "386", "type": "PROCESS_OF" }, { "id": "L420", "source": "301", "target": "376", "type": "PROCESS_OF" }, { "id": "L421", "source": "301", "target": "362", "type": "PROCESS_OF" }, { "id": "L422", "source": "301", "target": "356", "type": "PROCESS_OF" }, { "id": "L423", "source": "301", "target": "348", "type": "PROCESS_OF" }, { "id": "L424", "source": "301", "target": "338", "type": "PROCESS_OF" }, { "id": "L425", "source": "301", "target": "326", "type": "PROCESS_OF" }, { "id": "L426", "source": "301", "target": "315", "type": "PROCESS_OF" }, { "id": "L427", "source": "301", "target": "289", "type": "PROCESS_OF" }, { "id": "L428", "source": "303", "target": "489", "type": "PROCESS_OF" }, { "id": "L429", "source": "303", "target": "450", "type": "PROCESS_OF" }, { "id": "L430", "source": "303", "target": "440", "type": "PROCESS_OF" }, { "id": "L431", "source": "303", "target": "422", "type": "PROCESS_OF" }, { "id": "L432", "source": "303", "target": "392", "type": "PROCESS_OF" }, { "id": "L433", "source": "303", "target": "386", "type": "PROCESS_OF" }, { "id": "L434", "source": "303", "target": "376", "type": "PROCESS_OF" }, { "id": "L435", "source": "303", "target": "362", "type": "PROCESS_OF" }, { "id": "L436", "source": "303", "target": "356", "type": "PROCESS_OF" }, { "id": "L437", "source": "303", "target": "348", "type": "PROCESS_OF" }, { "id": "L438", "source": "303", "target": "338", "type": "PROCESS_OF" }, { "id": "L439", "source": "303", "target": "326", "type": "PROCESS_OF" }, { "id": "L440", "source": "303", "target": "315", "type": "PROCESS_OF" }, { "id": "L441", "source": "303", "target": "289", "type": "PROCESS_OF" }, { "id": "L442", "source": "303", "target": "1832", "type": "PROCESS_OF" }, { "id": "L443", "source": "305", "target": "1413", "type": "PROCESS_OF" }, { "id": "L444", "source": "305", "target": "1399", "type": "PROCESS_OF" }, { "id": "L445", "source": "305", "target": "1390", "type": "PROCESS_OF" }, { "id": "L446", "source": "305", "target": "1185", "type": "PROCESS_OF" }, { "id": "L447", "source": "305", "target": "1163", "type": "PROCESS_OF" }, { "id": "L448", "source": "305", "target": "2202", "type": "PROCESS_OF" }, { "id": "L449", "source": "305", "target": "489", "type": "PROCESS_OF" }, { "id": "L450", "source": "305", "target": "471", "type": "PROCESS_OF" }, { "id": "L451", "source": "305", "target": "452", "type": "PROCESS_OF" }, { "id": "L452", "source": "305", "target": "450", "type": "PROCESS_OF" }, { "id": "L453", "source": "305", "target": "392", "type": "PROCESS_OF" }, { "id": "L454", "source": "305", "target": "386", "type": "PROCESS_OF" }, { "id": "L455", "source": "305", "target": "376", "type": "PROCESS_OF" }, { "id": "L456", "source": "305", "target": "362", "type": "PROCESS_OF" }, { "id": "L457", "source": "305", "target": "356", "type": "PROCESS_OF" }, { "id": "L458", "source": "305", "target": "348", "type": "PROCESS_OF" }, { "id": "L459", "source": "305", "target": "338", "type": "PROCESS_OF" }, { "id": "L460", "source": "305", "target": "326", "type": "PROCESS_OF" }, { "id": "L461", "source": "305", "target": "289", "type": "PROCESS_OF" }, { "id": "L462", "source": "307", "target": "1947", "type": "PROCESS_OF" }, { "id": "L463", "source": "307", "target": "289", "type": "PROCESS_OF" }, { "id": "L464", "source": "309", "target": "1380", "type": "PROCESS_OF" }, { "id": "L465", "source": "309", "target": "1531", "type": "PROCESS_OF" }, { "id": "L466", "source": "309", "target": "1527", "type": "PROCESS_OF" }, { "id": "L467", "source": "309", "target": "1511", "type": "PROCESS_OF" }, { "id": "L468", "source": "309", "target": "1499", "type": "PROCESS_OF" }, { "id": "L469", "source": "309", "target": "1479", "type": "PROCESS_OF" }, { "id": "L470", "source": "309", "target": "489", "type": "PROCESS_OF" }, { "id": "L471", "source": "309", "target": "471", "type": "PROCESS_OF" }, { "id": "L472", "source": "309", "target": "422", "type": "PROCESS_OF" }, { "id": "L473", "source": "309", "target": "411", "type": "PROCESS_OF" }, { "id": "L474", "source": "309", "target": "395", "type": "PROCESS_OF" }, { "id": "L475", "source": "309", "target": "1957", "type": "PROCESS_OF" }, { "id": "L476", "source": "309", "target": "376", "type": "PROCESS_OF" }, { "id": "L477", "source": "309", "target": "356", "type": "PROCESS_OF" }, { "id": "L478", "source": "309", "target": "348", "type": "PROCESS_OF" }, { "id": "L479", "source": "309", "target": "338", "type": "PROCESS_OF" }, { "id": "L480", "source": "309", "target": "326", "type": "PROCESS_OF" }, { "id": "L481", "source": "309", "target": "315", "type": "PROCESS_OF" }, { "id": "L482", "source": "309", "target": "289", "type": "PROCESS_OF" }, { "id": "L483", "source": "311", "target": "8666", "type": "PROCESS_OF" }, { "id": "L484", "source": "311", "target": "1757", "type": "PROCESS_OF" }, { "id": "L485", "source": "311", "target": "1511", "type": "PROCESS_OF" }, { "id": "L486", "source": "311", "target": "489", "type": "PROCESS_OF" }, { "id": "L487", "source": "311", "target": "471", "type": "PROCESS_OF" }, { "id": "L488", "source": "311", "target": "450", "type": "PROCESS_OF" }, { "id": "L489", "source": "311", "target": "422", "type": "PROCESS_OF" }, { "id": "L490", "source": "311", "target": "1947", "type": "PROCESS_OF" }, { "id": "L491", "source": "311", "target": "376", "type": "PROCESS_OF" }, { "id": "L492", "source": "311", "target": "356", "type": "PROCESS_OF" }, { "id": "L493", "source": "311", "target": "348", "type": "PROCESS_OF" }, { "id": "L494", "source": "311", "target": "338", "type": "PROCESS_OF" }, { "id": "L495", "source": "311", "target": "326", "type": "PROCESS_OF" }, { "id": "L496", "source": "311", "target": "315", "type": "PROCESS_OF" }, { "id": "L497", "source": "311", "target": "289", "type": "PROCESS_OF" }, { "id": "L498", "source": "313", "target": "489", "type": "PROCESS_OF" }, { "id": "L499", "source": "313", "target": "471", "type": "PROCESS_OF" }, { "id": "L500", "source": "313", "target": "450", "type": "PROCESS_OF" }, { "id": "L501", "source": "313", "target": "440", "type": "PROCESS_OF" }, { "id": "L502", "source": "313", "target": "422", "type": "PROCESS_OF" }, { "id": "L503", "source": "313", "target": "411", "type": "PROCESS_OF" }, { "id": "L504", "source": "313", "target": "1947", "type": "PROCESS_OF" }, { "id": "L505", "source": "313", "target": "376", "type": "PROCESS_OF" }, { "id": "L506", "source": "313", "target": "356", "type": "PROCESS_OF" }, { "id": "L507", "source": "313", "target": "348", "type": "PROCESS_OF" }, { "id": "L508", "source": "313", "target": "338", "type": "PROCESS_OF" }, { "id": "L509", "source": "313", "target": "326", "type": "PROCESS_OF" }, { "id": "L510", "source": "313", "target": "315", "type": "PROCESS_OF" }, { "id": "L511", "source": "313", "target": "289", "type": "PROCESS_OF" }, { "id": "L512", "source": "317", "target": "489", "type": "PROCESS_OF" }, { "id": "L513", "source": "317", "target": "450", "type": "PROCESS_OF" }, { "id": "L514", "source": "317", "target": "440", "type": "PROCESS_OF" }, { "id": "L515", "source": "317", "target": "422", "type": "PROCESS_OF" }, { "id": "L516", "source": "317", "target": "1950", "type": "PROCESS_OF" }, { "id": "L517", "source": "317", "target": "376", "type": "PROCESS_OF" }, { "id": "L518", "source": "317", "target": "356", "type": "PROCESS_OF" }, { "id": "L519", "source": "317", "target": "348", "type": "PROCESS_OF" }, { "id": "L520", "source": "317", "target": "338", "type": "PROCESS_OF" }, { "id": "L521", "source": "317", "target": "326", "type": "PROCESS_OF" }, { "id": "L522", "source": "317", "target": "315", "type": "PROCESS_OF" }, { "id": "L523", "source": "319", "target": "2217", "type": "PROCESS_OF" }, { "id": "L524", "source": "319", "target": "315", "type": "PROCESS_OF" }, { "id": "L525", "source": "321", "target": "1947", "type": "PROCESS_OF" }, { "id": "L526", "source": "321", "target": "315", "type": "PROCESS_OF" }, { "id": "L527", "source": "328", "target": "1947", "type": "PROCESS_OF" }, { "id": "L528", "source": "328", "target": "338", "type": "PROCESS_OF" }, { "id": "L529", "source": "328", "target": "326", "type": "PROCESS_OF" }, { "id": "L530", "source": "330", "target": "1185", "type": "PROCESS_OF" }, { "id": "L531", "source": "330", "target": "1163", "type": "PROCESS_OF" }, { "id": "L532", "source": "330", "target": "440", "type": "PROCESS_OF" }, { "id": "L533", "source": "330", "target": "1961", "type": "PROCESS_OF" }, { "id": "L534", "source": "330", "target": "338", "type": "PROCESS_OF" }, { "id": "L535", "source": "330", "target": "326", "type": "PROCESS_OF" }, { "id": "L536", "source": "332", "target": "1185", "type": "PROCESS_OF" }, { "id": "L537", "source": "332", "target": "1163", "type": "PROCESS_OF" }, { "id": "L538", "source": "332", "target": "1961", "type": "PROCESS_OF" }, { "id": "L539", "source": "332", "target": "338", "type": "PROCESS_OF" }, { "id": "L540", "source": "332", "target": "326", "type": "PROCESS_OF" }, { "id": "L541", "source": "334", "target": "1961", "type": "PROCESS_OF" }, { "id": "L542", "source": "334", "target": "326", "type": "PROCESS_OF" }, { "id": "L543", "source": "336", "target": "1940", "type": "PROCESS_OF" }, { "id": "L544", "source": "336", "target": "326", "type": "PROCESS_OF" }, { "id": "L545", "source": "340", "target": "1947", "type": "PROCESS_OF" }, { "id": "L546", "source": "340", "target": "338", "type": "PROCESS_OF" }, { "id": "L547", "source": "342", "target": "1163", "type": "PROCESS_OF" }, { "id": "L548", "source": "342", "target": "1947", "type": "PROCESS_OF" }, { "id": "L549", "source": "342", "target": "338", "type": "PROCESS_OF" }, { "id": "L550", "source": "344", "target": "1185", "type": "PROCESS_OF" }, { "id": "L551", "source": "344", "target": "1961", "type": "PROCESS_OF" }, { "id": "L552", "source": "344", "target": "338", "type": "PROCESS_OF" }, { "id": "L553", "source": "346", "target": "1961", "type": "PROCESS_OF" }, { "id": "L554", "source": "346", "target": "338", "type": "PROCESS_OF" }, { "id": "L555", "source": "350", "target": "489", "type": "PROCESS_OF" }, { "id": "L556", "source": "350", "target": "471", "type": "PROCESS_OF" }, { "id": "L557", "source": "350", "target": "450", "type": "PROCESS_OF" }, { "id": "L558", "source": "350", "target": "1947", "type": "PROCESS_OF" }, { "id": "L559", "source": "350", "target": "348", "type": "PROCESS_OF" }, { "id": "L560", "source": "352", "target": "489", "type": "PROCESS_OF" }, { "id": "L561", "source": "352", "target": "450", "type": "PROCESS_OF" }, { "id": "L562", "source": "352", "target": "1961", "type": "PROCESS_OF" }, { "id": "L563", "source": "352", "target": "348", "type": "PROCESS_OF" }, { "id": "L564", "source": "354", "target": "489", "type": "PROCESS_OF" }, { "id": "L565", "source": "354", "target": "450", "type": "PROCESS_OF" }, { "id": "L566", "source": "354", "target": "1961", "type": "PROCESS_OF" }, { "id": "L567", "source": "354", "target": "348", "type": "PROCESS_OF" }, { "id": "L568", "source": "358", "target": "471", "type": "PROCESS_OF" }, { "id": "L569", "source": "358", "target": "1927", "type": "PROCESS_OF" }, { "id": "L570", "source": "358", "target": "376", "type": "PROCESS_OF" }, { "id": "L571", "source": "358", "target": "356", "type": "PROCESS_OF" }, { "id": "L572", "source": "360", "target": "1947", "type": "PROCESS_OF" }, { "id": "L573", "source": "360", "target": "356", "type": "PROCESS_OF" }, { "id": "L574", "source": "364", "target": "1977", "type": "PROCESS_OF" }, { "id": "L575", "source": "364", "target": "362", "type": "PROCESS_OF" }, { "id": "L576", "source": "365", "target": "1947", "type": "PROCESS_OF" }, { "id": "L577", "source": "365", "target": "362", "type": "PROCESS_OF" }, { "id": "L578", "source": "366", "target": "8563", "type": "PROCESS_OF" }, { "id": "L579", "source": "366", "target": "1475", "type": "PROCESS_OF" }, { "id": "L580", "source": "366", "target": "392", "type": "PROCESS_OF" }, { "id": "L581", "source": "366", "target": "1957", "type": "PROCESS_OF" }, { "id": "L582", "source": "366", "target": "386", "type": "PROCESS_OF" }, { "id": "L583", "source": "366", "target": "362", "type": "PROCESS_OF" }, { "id": "L584", "source": "368", "target": "1947", "type": "PROCESS_OF" }, { "id": "L585", "source": "368", "target": "362", "type": "PROCESS_OF" }, { "id": "L586", "source": "369", "target": "2217", "type": "PROCESS_OF" }, { "id": "L587", "source": "369", "target": "362", "type": "PROCESS_OF" }, { "id": "L588", "source": "370", "target": "392", "type": "PROCESS_OF" }, { "id": "L589", "source": "370", "target": "386", "type": "PROCESS_OF" }, { "id": "L590", "source": "370", "target": "1940", "type": "PROCESS_OF" }, { "id": "L591", "source": "370", "target": "362", "type": "PROCESS_OF" }, { "id": "L592", "source": "372", "target": "2217", "type": "PROCESS_OF" }, { "id": "L593", "source": "372", "target": "362", "type": "PROCESS_OF" }, { "id": "L594", "source": "378", "target": "1947", "type": "PROCESS_OF" }, { "id": "L595", "source": "378", "target": "376", "type": "PROCESS_OF" }, { "id": "L596", "source": "388", "target": "2217", "type": "PROCESS_OF" }, { "id": "L597", "source": "388", "target": "386", "type": "PROCESS_OF" }, { "id": "L598", "source": "390", "target": "8563", "type": "PROCESS_OF" }, { "id": "L599", "source": "390", "target": "1475", "type": "PROCESS_OF" }, { "id": "L600", "source": "390", "target": "392", "type": "PROCESS_OF" }, { "id": "L601", "source": "390", "target": "1947", "type": "PROCESS_OF" }, { "id": "L602", "source": "390", "target": "386", "type": "PROCESS_OF" }, { "id": "L603", "source": "397", "target": "8562", "type": "PROCESS_OF" }, { "id": "L604", "source": "397", "target": "1790", "type": "PROCESS_OF" }, { "id": "L605", "source": "397", "target": "1531", "type": "PROCESS_OF" }, { "id": "L606", "source": "397", "target": "1469", "type": "PROCESS_OF" }, { "id": "L607", "source": "397", "target": "1463", "type": "PROCESS_OF" }, { "id": "L608", "source": "397", "target": "416", "type": "PROCESS_OF" }, { "id": "L609", "source": "397", "target": "401", "type": "PROCESS_OF" }, { "id": "L610", "source": "397", "target": "395", "type": "PROCESS_OF" }, { "id": "L611", "source": "399", "target": "401", "type": "PROCESS_OF" }, { "id": "L612", "source": "399", "target": "395", "type": "PROCESS_OF" }, { "id": "L613", "source": "399", "target": "1944", "type": "PROCESS_OF" }, { "id": "L614", "source": "403", "target": "401", "type": "PROCESS_OF" }, { "id": "L615", "source": "403", "target": "1957", "type": "PROCESS_OF" }, { "id": "L616", "source": "407", "target": "405", "type": "PROCESS_OF" }, { "id": "L617", "source": "407", "target": "1957", "type": "PROCESS_OF" }, { "id": "L618", "source": "409", "target": "405", "type": "PROCESS_OF" }, { "id": "L619", "source": "409", "target": "1957", "type": "PROCESS_OF" }, { "id": "L620", "source": "413", "target": "411", "type": "PROCESS_OF" }, { "id": "L621", "source": "413", "target": "1942", "type": "PROCESS_OF" }, { "id": "L622", "source": "418", "target": "416", "type": "PROCESS_OF" }, { "id": "L623", "source": "418", "target": "1947", "type": "PROCESS_OF" }, { "id": "L624", "source": "420", "target": "416", "type": "PROCESS_OF" }, { "id": "L625", "source": "420", "target": "1947", "type": "PROCESS_OF" }, { "id": "L626", "source": "424", "target": "422", "type": "PROCESS_OF" }, { "id": "L627", "source": "424", "target": "1947", "type": "PROCESS_OF" }, { "id": "L628", "source": "426", "target": "422", "type": "PROCESS_OF" }, { "id": "L629", "source": "426", "target": "1947", "type": "PROCESS_OF" }, { "id": "L630", "source": "428", "target": "422", "type": "PROCESS_OF" }, { "id": "L631", "source": "428", "target": "2131", "type": "PROCESS_OF" }, { "id": "L632", "source": "433", "target": "431", "type": "PROCESS_OF" }, { "id": "L633", "source": "433", "target": "1947", "type": "PROCESS_OF" }, { "id": "L634", "source": "435", "target": "431", "type": "PROCESS_OF" }, { "id": "L635", "source": "435", "target": "1947", "type": "PROCESS_OF" }, { "id": "L636", "source": "437", "target": "1790", "type": "PROCESS_OF" }, { "id": "L637", "source": "437", "target": "431", "type": "PROCESS_OF" }, { "id": "L638", "source": "442", "target": "440", "type": "PROCESS_OF" }, { "id": "L639", "source": "442", "target": "1947", "type": "PROCESS_OF" }, { "id": "L640", "source": "444", "target": "440", "type": "PROCESS_OF" }, { "id": "L641", "source": "444", "target": "2132", "type": "PROCESS_OF" }, { "id": "L642", "source": "446", "target": "440", "type": "PROCESS_OF" }, { "id": "L643", "source": "446", "target": "1957", "type": "PROCESS_OF" }, { "id": "L644", "source": "448", "target": "440", "type": "PROCESS_OF" }, { "id": "L645", "source": "448", "target": "1947", "type": "PROCESS_OF" }, { "id": "L646", "source": "454", "target": "452", "type": "PROCESS_OF" }, { "id": "L647", "source": "454", "target": "1947", "type": "PROCESS_OF" }, { "id": "L648", "source": "456", "target": "452", "type": "PROCESS_OF" }, { "id": "L649", "source": "456", "target": "1831", "type": "PROCESS_OF" }, { "id": "L650", "source": "458", "target": "1181", "type": "PROCESS_OF" }, { "id": "L651", "source": "458", "target": "452", "type": "PROCESS_OF" }, { "id": "L652", "source": "458", "target": "1961", "type": "PROCESS_OF" }, { "id": "L653", "source": "460", "target": "452", "type": "PROCESS_OF" }, { "id": "L654", "source": "460", "target": "1961", "type": "PROCESS_OF" }, { "id": "L655", "source": "462", "target": "1893", "type": "PROCESS_OF" }, { "id": "L656", "source": "462", "target": "452", "type": "PROCESS_OF" }, { "id": "L657", "source": "462", "target": "1929", "type": "PROCESS_OF" }, { "id": "L658", "source": "464", "target": "1181", "type": "PROCESS_OF" }, { "id": "L659", "source": "464", "target": "452", "type": "PROCESS_OF" }, { "id": "L660", "source": "464", "target": "1831", "type": "PROCESS_OF" }, { "id": "L661", "source": "466", "target": "452", "type": "PROCESS_OF" }, { "id": "L662", "source": "466", "target": "1961", "type": "PROCESS_OF" }, { "id": "L663", "source": "468", "target": "1181", "type": "PROCESS_OF" }, { "id": "L664", "source": "468", "target": "452", "type": "PROCESS_OF" }, { "id": "L665", "source": "468", "target": "1977", "type": "PROCESS_OF" }, { "id": "L666", "source": "473", "target": "8666", "type": "PROCESS_OF" }, { "id": "L667", "source": "473", "target": "9125", "type": "PROCESS_OF" }, { "id": "L668", "source": "473", "target": "670", "type": "PROCESS_OF" }, { "id": "L669", "source": "473", "target": "662", "type": "PROCESS_OF" }, { "id": "L670", "source": "473", "target": "643", "type": "PROCESS_OF" }, { "id": "L671", "source": "473", "target": "614", "type": "PROCESS_OF" }, { "id": "L672", "source": "473", "target": "612", "type": "PROCESS_OF" }, { "id": "L673", "source": "473", "target": "597", "type": "PROCESS_OF" }, { "id": "L674", "source": "473", "target": "587", "type": "PROCESS_OF" }, { "id": "L675", "source": "473", "target": "580", "type": "PROCESS_OF" }, { "id": "L676", "source": "473", "target": "554", "type": "PROCESS_OF" }, { "id": "L677", "source": "473", "target": "493", "type": "PROCESS_OF" }, { "id": "L678", "source": "473", "target": "471", "type": "PROCESS_OF" }, { "id": "L679", "source": "473", "target": "1929", "type": "PROCESS_OF" }, { "id": "L680", "source": "475", "target": "8666", "type": "PROCESS_OF" }, { "id": "L681", "source": "475", "target": "9125", "type": "PROCESS_OF" }, { "id": "L682", "source": "475", "target": "8563", "type": "PROCESS_OF" }, { "id": "L683", "source": "475", "target": "8491", "type": "PROCESS_OF" }, { "id": "L684", "source": "475", "target": "576", "type": "PROCESS_OF" }, { "id": "L685", "source": "475", "target": "489", "type": "PROCESS_OF" }, { "id": "L686", "source": "475", "target": "471", "type": "PROCESS_OF" }, { "id": "L687", "source": "475", "target": "2040", "type": "PROCESS_OF" }, { "id": "L688", "source": "477", "target": "8666", "type": "PROCESS_OF" }, { "id": "L689", "source": "477", "target": "9125", "type": "PROCESS_OF" }, { "id": "L690", "source": "477", "target": "471", "type": "PROCESS_OF" }, { "id": "L691", "source": "477", "target": "1947", "type": "PROCESS_OF" }, { "id": "L692", "source": "479", "target": "8666", "type": "PROCESS_OF" }, { "id": "L693", "source": "479", "target": "689", "type": "PROCESS_OF" }, { "id": "L694", "source": "479", "target": "670", "type": "PROCESS_OF" }, { "id": "L695", "source": "479", "target": "662", "type": "PROCESS_OF" }, { "id": "L696", "source": "479", "target": "614", "type": "PROCESS_OF" }, { "id": "L697", "source": "479", "target": "612", "type": "PROCESS_OF" }, { "id": "L698", "source": "479", "target": "603", "type": "PROCESS_OF" }, { "id": "L699", "source": "479", "target": "597", "type": "PROCESS_OF" }, { "id": "L700", "source": "479", "target": "587", "type": "PROCESS_OF" }, { "id": "L701", "source": "479", "target": "580", "type": "PROCESS_OF" }, { "id": "L702", "source": "479", "target": "554", "type": "PROCESS_OF" }, { "id": "L703", "source": "479", "target": "471", "type": "PROCESS_OF" }, { "id": "L704", "source": "479", "target": "1929", "type": "PROCESS_OF" }, { "id": "L705", "source": "481", "target": "614", "type": "PROCESS_OF" }, { "id": "L706", "source": "481", "target": "612", "type": "PROCESS_OF" }, { "id": "L707", "source": "481", "target": "471", "type": "PROCESS_OF" }, { "id": "L708", "source": "481", "target": "1929", "type": "PROCESS_OF" }, { "id": "L709", "source": "483", "target": "471", "type": "PROCESS_OF" }, { "id": "L710", "source": "485", "target": "1469", "type": "PROCESS_OF" }, { "id": "L711", "source": "485", "target": "614", "type": "PROCESS_OF" }, { "id": "L712", "source": "485", "target": "471", "type": "PROCESS_OF" }, { "id": "L713", "source": "485", "target": "2137", "type": "PROCESS_OF" }, { "id": "L714", "source": "487", "target": "8666", "type": "PROCESS_OF" }, { "id": "L715", "source": "487", "target": "471", "type": "PROCESS_OF" }, { "id": "L716", "source": "487", "target": "1961", "type": "PROCESS_OF" }, { "id": "L717", "source": "495", "target": "516", "type": "PROCESS_OF" }, { "id": "L718", "source": "495", "target": "1357", "type": "PROCESS_OF" }, { "id": "L719", "source": "495", "target": "517", "type": "PROCESS_OF" }, { "id": "L720", "source": "495", "target": "493", "type": "PROCESS_OF" }, { "id": "L721", "source": "495", "target": "1927", "type": "PROCESS_OF" }, { "id": "L722", "source": "497", "target": "8666", "type": "PROCESS_OF" }, { "id": "L723", "source": "497", "target": "679", "type": "PROCESS_OF" }, { "id": "L724", "source": "497", "target": "614", "type": "PROCESS_OF" }, { "id": "L725", "source": "497", "target": "612", "type": "PROCESS_OF" }, { "id": "L726", "source": "497", "target": "587", "type": "PROCESS_OF" }, { "id": "L727", "source": "497", "target": "580", "type": "PROCESS_OF" }, { "id": "L728", "source": "497", "target": "554", "type": "PROCESS_OF" }, { "id": "L729", "source": "497", "target": "539", "type": "PROCESS_OF" }, { "id": "L730", "source": "497", "target": "493", "type": "PROCESS_OF" }, { "id": "L731", "source": "497", "target": "1929", "type": "PROCESS_OF" }, { "id": "L732", "source": "499", "target": "580", "type": "PROCESS_OF" }, { "id": "L733", "source": "499", "target": "493", "type": "PROCESS_OF" }, { "id": "L734", "source": "499", "target": "1890", "type": "PROCESS_OF" }, { "id": "L735", "source": "500", "target": "1357", "type": "PROCESS_OF" }, { "id": "L736", "source": "500", "target": "517", "type": "PROCESS_OF" }, { "id": "L737", "source": "500", "target": "493", "type": "PROCESS_OF" }, { "id": "L738", "source": "500", "target": "1927", "type": "PROCESS_OF" }, { "id": "L739", "source": "502", "target": "8531", "type": "PROCESS_OF" }, { "id": "L740", "source": "502", "target": "670", "type": "PROCESS_OF" }, { "id": "L741", "source": "502", "target": "662", "type": "PROCESS_OF" }, { "id": "L742", "source": "502", "target": "631", "type": "PROCESS_OF" }, { "id": "L743", "source": "502", "target": "614", "type": "PROCESS_OF" }, { "id": "L744", "source": "502", "target": "612", "type": "PROCESS_OF" }, { "id": "L745", "source": "502", "target": "603", "type": "PROCESS_OF" }, { "id": "L746", "source": "502", "target": "597", "type": "PROCESS_OF" }, { "id": "L747", "source": "502", "target": "587", "type": "PROCESS_OF" }, { "id": "L748", "source": "502", "target": "583", "type": "PROCESS_OF" }, { "id": "L749", "source": "502", "target": "580", "type": "PROCESS_OF" }, { "id": "L750", "source": "502", "target": "554", "type": "PROCESS_OF" }, { "id": "L751", "source": "502", "target": "545", "type": "PROCESS_OF" }, { "id": "L752", "source": "502", "target": "539", "type": "PROCESS_OF" }, { "id": "L753", "source": "502", "target": "493", "type": "PROCESS_OF" }, { "id": "L754", "source": "502", "target": "2040", "type": "PROCESS_OF" }, { "id": "L755", "source": "504", "target": "1357", "type": "PROCESS_OF" }, { "id": "L756", "source": "504", "target": "517", "type": "PROCESS_OF" }, { "id": "L757", "source": "504", "target": "493", "type": "PROCESS_OF" }, { "id": "L758", "source": "504", "target": "1927", "type": "PROCESS_OF" }, { "id": "L759", "source": "506", "target": "8531", "type": "PROCESS_OF" }, { "id": "L760", "source": "506", "target": "493", "type": "PROCESS_OF" }, { "id": "L761", "source": "506", "target": "1929", "type": "PROCESS_OF" }, { "id": "L762", "source": "508", "target": "516", "type": "PROCESS_OF" }, { "id": "L763", "source": "508", "target": "493", "type": "PROCESS_OF" }, { "id": "L764", "source": "508", "target": "1927", "type": "PROCESS_OF" }, { "id": "L765", "source": "510", "target": "516", "type": "PROCESS_OF" }, { "id": "L766", "source": "510", "target": "493", "type": "PROCESS_OF" }, { "id": "L767", "source": "510", "target": "1927", "type": "PROCESS_OF" }, { "id": "L768", "source": "512", "target": "8531", "type": "PROCESS_OF" }, { "id": "L769", "source": "512", "target": "689", "type": "PROCESS_OF" }, { "id": "L770", "source": "512", "target": "670", "type": "PROCESS_OF" }, { "id": "L771", "source": "512", "target": "662", "type": "PROCESS_OF" }, { "id": "L772", "source": "512", "target": "643", "type": "PROCESS_OF" }, { "id": "L773", "source": "512", "target": "619", "type": "PROCESS_OF" }, { "id": "L774", "source": "512", "target": "614", "type": "PROCESS_OF" }, { "id": "L775", "source": "512", "target": "603", "type": "PROCESS_OF" }, { "id": "L776", "source": "512", "target": "597", "type": "PROCESS_OF" }, { "id": "L777", "source": "512", "target": "587", "type": "PROCESS_OF" }, { "id": "L778", "source": "512", "target": "580", "type": "PROCESS_OF" }, { "id": "L779", "source": "512", "target": "554", "type": "PROCESS_OF" }, { "id": "L780", "source": "512", "target": "545", "type": "PROCESS_OF" }, { "id": "L781", "source": "512", "target": "2202", "type": "PROCESS_OF" }, { "id": "L782", "source": "512", "target": "539", "type": "PROCESS_OF" }, { "id": "L783", "source": "512", "target": "493", "type": "PROCESS_OF" }, { "id": "L784", "source": "514", "target": "580", "type": "PROCESS_OF" }, { "id": "L785", "source": "514", "target": "493", "type": "PROCESS_OF" }, { "id": "L786", "source": "514", "target": "1929", "type": "PROCESS_OF" }, { "id": "L787", "source": "519", "target": "517", "type": "PROCESS_OF" }, { "id": "L788", "source": "519", "target": "1927", "type": "PROCESS_OF" }, { "id": "L789", "source": "521", "target": "517", "type": "PROCESS_OF" }, { "id": "L790", "source": "521", "target": "1927", "type": "PROCESS_OF" }, { "id": "L791", "source": "523", "target": "517", "type": "PROCESS_OF" }, { "id": "L792", "source": "523", "target": "1927", "type": "PROCESS_OF" }, { "id": "L793", "source": "525", "target": "517", "type": "PROCESS_OF" }, { "id": "L794", "source": "525", "target": "1927", "type": "PROCESS_OF" }, { "id": "L795", "source": "527", "target": "1927", "type": "PROCESS_OF" }, { "id": "L796", "source": "527", "target": "517", "type": "PROCESS_OF" }, { "id": "L797", "source": "527", "target": "1936", "type": "PROCESS_OF" }, { "id": "L798", "source": "529", "target": "517", "type": "PROCESS_OF" }, { "id": "L799", "source": "529", "target": "1927", "type": "PROCESS_OF" }, { "id": "L800", "source": "531", "target": "517", "type": "PROCESS_OF" }, { "id": "L801", "source": "531", "target": "1927", "type": "PROCESS_OF" }, { "id": "L802", "source": "533", "target": "517", "type": "PROCESS_OF" }, { "id": "L803", "source": "533", "target": "1927", "type": "PROCESS_OF" }, { "id": "L804", "source": "541", "target": "539", "type": "PROCESS_OF" }, { "id": "L805", "source": "541", "target": "1890", "type": "PROCESS_OF" }, { "id": "L806", "source": "543", "target": "539", "type": "PROCESS_OF" }, { "id": "L807", "source": "543", "target": "1929", "type": "PROCESS_OF" }, { "id": "L808", "source": "547", "target": "545", "type": "PROCESS_OF" }, { "id": "L809", "source": "547", "target": "2137", "type": "PROCESS_OF" }, { "id": "L810", "source": "549", "target": "1779", "type": "PROCESS_OF" }, { "id": "L811", "source": "549", "target": "1775", "type": "PROCESS_OF" }, { "id": "L812", "source": "549", "target": "1768", "type": "PROCESS_OF" }, { "id": "L813", "source": "549", "target": "1603", "type": "PROCESS_OF" }, { "id": "L814", "source": "549", "target": "597", "type": "PROCESS_OF" }, { "id": "L815", "source": "549", "target": "576", "type": "PROCESS_OF" }, { "id": "L816", "source": "549", "target": "567", "type": "PROCESS_OF" }, { "id": "L817", "source": "549", "target": "545", "type": "PROCESS_OF" }, { "id": "L818", "source": "549", "target": "1889", "type": "PROCESS_OF" }, { "id": "L819", "source": "551", "target": "545", "type": "PROCESS_OF" }, { "id": "L820", "source": "551", "target": "1929", "type": "PROCESS_OF" }, { "id": "L821", "source": "556", "target": "554", "type": "PROCESS_OF" }, { "id": "L822", "source": "556", "target": "2137", "type": "PROCESS_OF" }, { "id": "L823", "source": "558", "target": "8666", "type": "PROCESS_OF" }, { "id": "L824", "source": "558", "target": "554", "type": "PROCESS_OF" }, { "id": "L825", "source": "558", "target": "2132", "type": "PROCESS_OF" }, { "id": "L826", "source": "560", "target": "554", "type": "PROCESS_OF" }, { "id": "L827", "source": "560", "target": "1922", "type": "PROCESS_OF" }, { "id": "L828", "source": "562", "target": "8666", "type": "PROCESS_OF" }, { "id": "L829", "source": "562", "target": "554", "type": "PROCESS_OF" }, { "id": "L830", "source": "562", "target": "2131", "type": "PROCESS_OF" }, { "id": "L831", "source": "564", "target": "8666", "type": "PROCESS_OF" }, { "id": "L832", "source": "564", "target": "554", "type": "PROCESS_OF" }, { "id": "L833", "source": "564", "target": "1929", "type": "PROCESS_OF" }, { "id": "L834", "source": "569", "target": "576", "type": "PROCESS_OF" }, { "id": "L835", "source": "569", "target": "567", "type": "PROCESS_OF" }, { "id": "L836", "source": "569", "target": "1928", "type": "PROCESS_OF" }, { "id": "L837", "source": "571", "target": "576", "type": "PROCESS_OF" }, { "id": "L838", "source": "571", "target": "567", "type": "PROCESS_OF" }, { "id": "L839", "source": "571", "target": "1928", "type": "PROCESS_OF" }, { "id": "L840", "source": "573", "target": "576", "type": "PROCESS_OF" }, { "id": "L841", "source": "573", "target": "567", "type": "PROCESS_OF" }, { "id": "L842", "source": "573", "target": "1947", "type": "PROCESS_OF" }, { "id": "L843", "source": "585", "target": "583", "type": "PROCESS_OF" }, { "id": "L844", "source": "585", "target": "1929", "type": "PROCESS_OF" }, { "id": "L845", "source": "586", "target": "583", "type": "PROCESS_OF" }, { "id": "L846", "source": "586", "target": "1922", "type": "PROCESS_OF" }, { "id": "L847", "source": "589", "target": "713", "type": "PROCESS_OF" }, { "id": "L848", "source": "589", "target": "8500", "type": "PROCESS_OF" }, { "id": "L849", "source": "589", "target": "587", "type": "PROCESS_OF" }, { "id": "L850", "source": "589", "target": "2000", "type": "PROCESS_OF" }, { "id": "L851", "source": "591", "target": "587", "type": "PROCESS_OF" }, { "id": "L852", "source": "591", "target": "1893", "type": "PROCESS_OF" }, { "id": "L853", "source": "593", "target": "8531", "type": "PROCESS_OF" }, { "id": "L854", "source": "593", "target": "603", "type": "PROCESS_OF" }, { "id": "L855", "source": "593", "target": "587", "type": "PROCESS_OF" }, { "id": "L856", "source": "593", "target": "1893", "type": "PROCESS_OF" }, { "id": "L857", "source": "595", "target": "8500", "type": "PROCESS_OF" }, { "id": "L858", "source": "595", "target": "713", "type": "PROCESS_OF" }, { "id": "L859", "source": "595", "target": "587", "type": "PROCESS_OF" }, { "id": "L860", "source": "595", "target": "2000", "type": "PROCESS_OF" }, { "id": "L861", "source": "599", "target": "587", "type": "PROCESS_OF" }, { "id": "L862", "source": "599", "target": "8531", "type": "PROCESS_OF" }, { "id": "L863", "source": "599", "target": "689", "type": "PROCESS_OF" }, { "id": "L864", "source": "599", "target": "603", "type": "PROCESS_OF" }, { "id": "L865", "source": "599", "target": "597", "type": "PROCESS_OF" }, { "id": "L866", "source": "599", "target": "1893", "type": "PROCESS_OF" }, { "id": "L867", "source": "601", "target": "597", "type": "PROCESS_OF" }, { "id": "L868", "source": "601", "target": "1889", "type": "PROCESS_OF" }, { "id": "L869", "source": "605", "target": "8531", "type": "PROCESS_OF" }, { "id": "L870", "source": "605", "target": "603", "type": "PROCESS_OF" }, { "id": "L871", "source": "605", "target": "1893", "type": "PROCESS_OF" }, { "id": "L872", "source": "607", "target": "689", "type": "PROCESS_OF" }, { "id": "L873", "source": "607", "target": "603", "type": "PROCESS_OF" }, { "id": "L874", "source": "607", "target": "2137", "type": "PROCESS_OF" }, { "id": "L875", "source": "609", "target": "670", "type": "PROCESS_OF" }, { "id": "L876", "source": "609", "target": "597", "type": "PROCESS_OF" }, { "id": "L877", "source": "609", "target": "587", "type": "PROCESS_OF" }, { "id": "L878", "source": "609", "target": "8531", "type": "PROCESS_OF" }, { "id": "L879", "source": "609", "target": "689", "type": "PROCESS_OF" }, { "id": "L880", "source": "609", "target": "603", "type": "PROCESS_OF" }, { "id": "L881", "source": "609", "target": "1893", "type": "PROCESS_OF" }, { "id": "L882", "source": "616", "target": "1441", "type": "PROCESS_OF" }, { "id": "L883", "source": "616", "target": "1437", "type": "PROCESS_OF" }, { "id": "L884", "source": "616", "target": "1427", "type": "PROCESS_OF" }, { "id": "L885", "source": "616", "target": "1422", "type": "PROCESS_OF" }, { "id": "L886", "source": "616", "target": "1418", "type": "PROCESS_OF" }, { "id": "L887", "source": "616", "target": "1326", "type": "PROCESS_OF" }, { "id": "L888", "source": "616", "target": "1307", "type": "PROCESS_OF" }, { "id": "L889", "source": "616", "target": "614", "type": "PROCESS_OF" }, { "id": "L890", "source": "616", "target": "2137", "type": "PROCESS_OF" }, { "id": "L891", "source": "621", "target": "1463", "type": "PROCESS_OF" }, { "id": "L892", "source": "621", "target": "619", "type": "PROCESS_OF" }, { "id": "L893", "source": "621", "target": "2206", "type": "PROCESS_OF" }, { "id": "L894", "source": "622", "target": "619", "type": "PROCESS_OF" }, { "id": "L895", "source": "622", "target": "1928", "type": "PROCESS_OF" }, { "id": "L896", "source": "623", "target": "619", "type": "PROCESS_OF" }, { "id": "L897", "source": "623", "target": "1928", "type": "PROCESS_OF" }, { "id": "L898", "source": "624", "target": "1463", "type": "PROCESS_OF" }, { "id": "L899", "source": "624", "target": "1266", "type": "PROCESS_OF" }, { "id": "L900", "source": "624", "target": "1262", "type": "PROCESS_OF" }, { "id": "L901", "source": "624", "target": "1258", "type": "PROCESS_OF" }, { "id": "L902", "source": "624", "target": "1254", "type": "PROCESS_OF" }, { "id": "L903", "source": "624", "target": "1237", "type": "PROCESS_OF" }, { "id": "L904", "source": "624", "target": "1232", "type": "PROCESS_OF" }, { "id": "L905", "source": "624", "target": "619", "type": "PROCESS_OF" }, { "id": "L906", "source": "624", "target": "2206", "type": "PROCESS_OF" }, { "id": "L907", "source": "626", "target": "8562", "type": "PROCESS_OF" }, { "id": "L908", "source": "626", "target": "1469", "type": "PROCESS_OF" }, { "id": "L909", "source": "626", "target": "643", "type": "PROCESS_OF" }, { "id": "L910", "source": "626", "target": "619", "type": "PROCESS_OF" }, { "id": "L911", "source": "626", "target": "1923", "type": "PROCESS_OF" }, { "id": "L912", "source": "628", "target": "1463", "type": "PROCESS_OF" }, { "id": "L913", "source": "628", "target": "1274", "type": "PROCESS_OF" }, { "id": "L914", "source": "628", "target": "1266", "type": "PROCESS_OF" }, { "id": "L915", "source": "628", "target": "1262", "type": "PROCESS_OF" }, { "id": "L916", "source": "628", "target": "1258", "type": "PROCESS_OF" }, { "id": "L917", "source": "628", "target": "1254", "type": "PROCESS_OF" }, { "id": "L918", "source": "628", "target": "1237", "type": "PROCESS_OF" }, { "id": "L919", "source": "628", "target": "1232", "type": "PROCESS_OF" }, { "id": "L920", "source": "628", "target": "1221", "type": "PROCESS_OF" }, { "id": "L921", "source": "628", "target": "619", "type": "PROCESS_OF" }, { "id": "L922", "source": "628", "target": "2206", "type": "PROCESS_OF" }, { "id": "L923", "source": "630", "target": "619", "type": "PROCESS_OF" }, { "id": "L924", "source": "630", "target": "1928", "type": "PROCESS_OF" }, { "id": "L925", "source": "633", "target": "631", "type": "PROCESS_OF" }, { "id": "L926", "source": "633", "target": "1929", "type": "PROCESS_OF" }, { "id": "L927", "source": "635", "target": "631", "type": "PROCESS_OF" }, { "id": "L928", "source": "635", "target": "1929", "type": "PROCESS_OF" }, { "id": "L929", "source": "637", "target": "631", "type": "PROCESS_OF" }, { "id": "L930", "source": "637", "target": "1923", "type": "PROCESS_OF" }, { "id": "L931", "source": "639", "target": "631", "type": "PROCESS_OF" }, { "id": "L932", "source": "639", "target": "1929", "type": "PROCESS_OF" }, { "id": "L933", "source": "641", "target": "631", "type": "PROCESS_OF" }, { "id": "L934", "source": "641", "target": "1923", "type": "PROCESS_OF" }, { "id": "L935", "source": "645", "target": "1249", "type": "PROCESS_OF" }, { "id": "L936", "source": "645", "target": "643", "type": "PROCESS_OF" }, { "id": "L937", "source": "645", "target": "2206", "type": "PROCESS_OF" }, { "id": "L938", "source": "647", "target": "1249", "type": "PROCESS_OF" }, { "id": "L939", "source": "647", "target": "643", "type": "PROCESS_OF" }, { "id": "L940", "source": "647", "target": "2206", "type": "PROCESS_OF" }, { "id": "L941", "source": "649", "target": "643", "type": "PROCESS_OF" }, { "id": "L942", "source": "649", "target": "1923", "type": "PROCESS_OF" }, { "id": "L943", "source": "651", "target": "1249", "type": "PROCESS_OF" }, { "id": "L944", "source": "651", "target": "643", "type": "PROCESS_OF" }, { "id": "L945", "source": "651", "target": "2206", "type": "PROCESS_OF" }, { "id": "L946", "source": "653", "target": "643", "type": "PROCESS_OF" }, { "id": "L947", "source": "653", "target": "1923", "type": "PROCESS_OF" }, { "id": "L948", "source": "655", "target": "1249", "type": "PROCESS_OF" }, { "id": "L949", "source": "655", "target": "761", "type": "PROCESS_OF" }, { "id": "L950", "source": "655", "target": "643", "type": "PROCESS_OF" }, { "id": "L951", "source": "655", "target": "2206", "type": "PROCESS_OF" }, { "id": "L952", "source": "657", "target": "1469", "type": "PROCESS_OF" }, { "id": "L953", "source": "657", "target": "643", "type": "PROCESS_OF" }, { "id": "L954", "source": "657", "target": "1923", "type": "PROCESS_OF" }, { "id": "L955", "source": "659", "target": "1249", "type": "PROCESS_OF" }, { "id": "L956", "source": "659", "target": "643", "type": "PROCESS_OF" }, { "id": "L957", "source": "659", "target": "2206", "type": "PROCESS_OF" }, { "id": "L958", "source": "664", "target": "1904", "type": "PROCESS_OF" }, { "id": "L959", "source": "664", "target": "670", "type": "PROCESS_OF" }, { "id": "L960", "source": "664", "target": "662", "type": "PROCESS_OF" }, { "id": "L961", "source": "664", "target": "1922", "type": "PROCESS_OF" }, { "id": "L962", "source": "666", "target": "1893", "type": "PROCESS_OF" }, { "id": "L963", "source": "666", "target": "662", "type": "PROCESS_OF" }, { "id": "L964", "source": "666", "target": "1929", "type": "PROCESS_OF" }, { "id": "L965", "source": "668", "target": "1904", "type": "PROCESS_OF" }, { "id": "L966", "source": "668", "target": "662", "type": "PROCESS_OF" }, { "id": "L967", "source": "668", "target": "1922", "type": "PROCESS_OF" }, { "id": "L968", "source": "672", "target": "1893", "type": "PROCESS_OF" }, { "id": "L969", "source": "672", "target": "670", "type": "PROCESS_OF" }, { "id": "L970", "source": "672", "target": "1929", "type": "PROCESS_OF" }, { "id": "L971", "source": "674", "target": "1893", "type": "PROCESS_OF" }, { "id": "L972", "source": "674", "target": "670", "type": "PROCESS_OF" }, { "id": "L973", "source": "674", "target": "1929", "type": "PROCESS_OF" }, { "id": "L974", "source": "676", "target": "670", "type": "PROCESS_OF" }, { "id": "L975", "source": "676", "target": "1904", "type": "PROCESS_OF" }, { "id": "L976", "source": "681", "target": "679", "type": "PROCESS_OF" }, { "id": "L977", "source": "681", "target": "1929", "type": "PROCESS_OF" }, { "id": "L978", "source": "683", "target": "679", "type": "PROCESS_OF" }, { "id": "L979", "source": "683", "target": "1929", "type": "PROCESS_OF" }, { "id": "L980", "source": "685", "target": "679", "type": "PROCESS_OF" }, { "id": "L981", "source": "685", "target": "2040", "type": "PROCESS_OF" }, { "id": "L982", "source": "687", "target": "679", "type": "PROCESS_OF" }, { "id": "L983", "source": "687", "target": "1929", "type": "PROCESS_OF" }, { "id": "L984", "source": "691", "target": "689", "type": "PROCESS_OF" }, { "id": "L985", "source": "691", "target": "2040", "type": "PROCESS_OF" }, { "id": "L986", "source": "693", "target": "689", "type": "PROCESS_OF" }, { "id": "L987", "source": "693", "target": "1893", "type": "PROCESS_OF" }, { "id": "L988", "source": "695", "target": "689", "type": "PROCESS_OF" }, { "id": "L989", "source": "695", "target": "1893", "type": "PROCESS_OF" }, { "id": "L990", "source": "702", "target": "700", "type": "PROCESS_OF" }, { "id": "L991", "source": "702", "target": "1827", "type": "PROCESS_OF" }, { "id": "L992", "source": "704", "target": "700", "type": "PROCESS_OF" }, { "id": "L993", "source": "704", "target": "1827", "type": "PROCESS_OF" }, { "id": "L994", "source": "705", "target": "700", "type": "PROCESS_OF" }, { "id": "L995", "source": "705", "target": "1827", "type": "PROCESS_OF" }, { "id": "L996", "source": "706", "target": "700", "type": "PROCESS_OF" }, { "id": "L997", "source": "706", "target": "1827", "type": "PROCESS_OF" }, { "id": "L998", "source": "707", "target": "700", "type": "PROCESS_OF" }, { "id": "L999", "source": "707", "target": "1827", "type": "PROCESS_OF" }, { "id": "L1000", "source": "708", "target": "700", "type": "PROCESS_OF" }, { "id": "L1001", "source": "708", "target": "1827", "type": "PROCESS_OF" }, { "id": "L1002", "source": "709", "target": "700", "type": "PROCESS_OF" }, { "id": "L1003", "source": "709", "target": "1827", "type": "PROCESS_OF" }, { "id": "L1004", "source": "711", "target": "700", "type": "PROCESS_OF" }, { "id": "L1005", "source": "711", "target": "1829", "type": "PROCESS_OF" }, { "id": "L1006", "source": "712", "target": "700", "type": "PROCESS_OF" }, { "id": "L1007", "source": "712", "target": "1827", "type": "PROCESS_OF" }, { "id": "L1008", "source": "715", "target": "713", "type": "PROCESS_OF" }, { "id": "L1009", "source": "715", "target": "2000", "type": "PROCESS_OF" }, { "id": "L1010", "source": "717", "target": "8563", "type": "PROCESS_OF" }, { "id": "L1011", "source": "717", "target": "1475", "type": "PROCESS_OF" }, { "id": "L1012", "source": "717", "target": "732", "type": "PROCESS_OF" }, { "id": "L1013", "source": "717", "target": "713", "type": "PROCESS_OF" }, { "id": "L1014", "source": "717", "target": "1831", "type": "PROCESS_OF" }, { "id": "L1015", "source": "721", "target": "719", "type": "PROCESS_OF" }, { "id": "L1016", "source": "721", "target": "1826", "type": "PROCESS_OF" }, { "id": "L1017", "source": "722", "target": "719", "type": "PROCESS_OF" }, { "id": "L1018", "source": "722", "target": "1826", "type": "PROCESS_OF" }, { "id": "L1019", "source": "723", "target": "719", "type": "PROCESS_OF" }, { "id": "L1020", "source": "723", "target": "1826", "type": "PROCESS_OF" }, { "id": "L1021", "source": "724", "target": "719", "type": "PROCESS_OF" }, { "id": "L1022", "source": "724", "target": "1826", "type": "PROCESS_OF" }, { "id": "L1023", "source": "725", "target": "719", "type": "PROCESS_OF" }, { "id": "L1024", "source": "725", "target": "1829", "type": "PROCESS_OF" }, { "id": "L1025", "source": "728", "target": "726", "type": "PROCESS_OF" }, { "id": "L1026", "source": "728", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1027", "source": "730", "target": "726", "type": "PROCESS_OF" }, { "id": "L1028", "source": "730", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1029", "source": "737", "target": "1796", "type": "PROCESS_OF" }, { "id": "L1030", "source": "737", "target": "735", "type": "PROCESS_OF" }, { "id": "L1031", "source": "738", "target": "1796", "type": "PROCESS_OF" }, { "id": "L1032", "source": "738", "target": "735", "type": "PROCESS_OF" }, { "id": "L1033", "source": "739", "target": "1796", "type": "PROCESS_OF" }, { "id": "L1034", "source": "739", "target": "735", "type": "PROCESS_OF" }, { "id": "L1035", "source": "740", "target": "1796", "type": "PROCESS_OF" }, { "id": "L1036", "source": "740", "target": "735", "type": "PROCESS_OF" }, { "id": "L1037", "source": "743", "target": "741", "type": "PROCESS_OF" }, { "id": "L1038", "source": "743", "target": "1820", "type": "PROCESS_OF" }, { "id": "L1039", "source": "744", "target": "741", "type": "PROCESS_OF" }, { "id": "L1040", "source": "744", "target": "1820", "type": "PROCESS_OF" }, { "id": "L1041", "source": "745", "target": "741", "type": "PROCESS_OF" }, { "id": "L1042", "source": "745", "target": "1820", "type": "PROCESS_OF" }, { "id": "L1043", "source": "746", "target": "741", "type": "PROCESS_OF" }, { "id": "L1044", "source": "746", "target": "1820", "type": "PROCESS_OF" }, { "id": "L1045", "source": "749", "target": "747", "type": "PROCESS_OF" }, { "id": "L1046", "source": "749", "target": "1826", "type": "PROCESS_OF" }, { "id": "L1047", "source": "750", "target": "747", "type": "PROCESS_OF" }, { "id": "L1048", "source": "750", "target": "1826", "type": "PROCESS_OF" }, { "id": "L1049", "source": "751", "target": "747", "type": "PROCESS_OF" }, { "id": "L1050", "source": "751", "target": "1826", "type": "PROCESS_OF" }, { "id": "L1051", "source": "752", "target": "747", "type": "PROCESS_OF" }, { "id": "L1052", "source": "752", "target": "1826", "type": "PROCESS_OF" }, { "id": "L1053", "source": "753", "target": "747", "type": "PROCESS_OF" }, { "id": "L1054", "source": "753", "target": "1826", "type": "PROCESS_OF" }, { "id": "L1055", "source": "758", "target": "756", "type": "PROCESS_OF" }, { "id": "L1056", "source": "758", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1057", "source": "759", "target": "756", "type": "PROCESS_OF" }, { "id": "L1058", "source": "759", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1059", "source": "760", "target": "756", "type": "PROCESS_OF" }, { "id": "L1060", "source": "760", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1061", "source": "763", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1062", "source": "763", "target": "761", "type": "PROCESS_OF" }, { "id": "L1063", "source": "764", "target": "761", "type": "PROCESS_OF" }, { "id": "L1064", "source": "764", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1065", "source": "765", "target": "761", "type": "PROCESS_OF" }, { "id": "L1066", "source": "765", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1067", "source": "768", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1068", "source": "768", "target": "766", "type": "PROCESS_OF" }, { "id": "L1069", "source": "769", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1070", "source": "769", "target": "766", "type": "PROCESS_OF" }, { "id": "L1071", "source": "770", "target": "766", "type": "PROCESS_OF" }, { "id": "L1072", "source": "770", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1073", "source": "771", "target": "766", "type": "PROCESS_OF" }, { "id": "L1074", "source": "771", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1075", "source": "773", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1076", "source": "773", "target": "766", "type": "PROCESS_OF" }, { "id": "L1077", "source": "774", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1078", "source": "774", "target": "766", "type": "PROCESS_OF" }, { "id": "L1079", "source": "775", "target": "766", "type": "PROCESS_OF" }, { "id": "L1080", "source": "775", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1081", "source": "776", "target": "766", "type": "PROCESS_OF" }, { "id": "L1082", "source": "776", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1083", "source": "777", "target": "766", "type": "PROCESS_OF" }, { "id": "L1084", "source": "777", "target": "1797", "type": "PROCESS_OF" }, { "id": "L1085", "source": "782", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1086", "source": "782", "target": "780", "type": "PROCESS_OF" }, { "id": "L1087", "source": "784", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1088", "source": "784", "target": "780", "type": "PROCESS_OF" }, { "id": "L1089", "source": "786", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1090", "source": "786", "target": "780", "type": "PROCESS_OF" }, { "id": "L1091", "source": "788", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1092", "source": "788", "target": "780", "type": "PROCESS_OF" }, { "id": "L1093", "source": "790", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1094", "source": "790", "target": "780", "type": "PROCESS_OF" }, { "id": "L1095", "source": "792", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1096", "source": "792", "target": "780", "type": "PROCESS_OF" }, { "id": "L1097", "source": "794", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1098", "source": "794", "target": "780", "type": "PROCESS_OF" }, { "id": "L1099", "source": "798", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1100", "source": "798", "target": "796", "type": "PROCESS_OF" }, { "id": "L1101", "source": "800", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1102", "source": "800", "target": "1119", "type": "PROCESS_OF" }, { "id": "L1103", "source": "800", "target": "796", "type": "PROCESS_OF" }, { "id": "L1104", "source": "802", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1105", "source": "802", "target": "796", "type": "PROCESS_OF" }, { "id": "L1106", "source": "804", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1107", "source": "804", "target": "1119", "type": "PROCESS_OF" }, { "id": "L1108", "source": "804", "target": "1017", "type": "PROCESS_OF" }, { "id": "L1109", "source": "804", "target": "796", "type": "PROCESS_OF" }, { "id": "L1110", "source": "806", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1111", "source": "806", "target": "796", "type": "PROCESS_OF" }, { "id": "L1112", "source": "810", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1113", "source": "810", "target": "808", "type": "PROCESS_OF" }, { "id": "L1114", "source": "812", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1115", "source": "812", "target": "808", "type": "PROCESS_OF" }, { "id": "L1116", "source": "814", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1117", "source": "814", "target": "808", "type": "PROCESS_OF" }, { "id": "L1118", "source": "816", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1119", "source": "816", "target": "808", "type": "PROCESS_OF" }, { "id": "L1120", "source": "818", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1121", "source": "818", "target": "808", "type": "PROCESS_OF" }, { "id": "L1122", "source": "820", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1123", "source": "820", "target": "808", "type": "PROCESS_OF" }, { "id": "L1124", "source": "824", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1125", "source": "824", "target": "822", "type": "PROCESS_OF" }, { "id": "L1126", "source": "826", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1127", "source": "826", "target": "822", "type": "PROCESS_OF" }, { "id": "L1128", "source": "828", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1129", "source": "828", "target": "822", "type": "PROCESS_OF" }, { "id": "L1130", "source": "830", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1131", "source": "830", "target": "822", "type": "PROCESS_OF" }, { "id": "L1132", "source": "832", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1133", "source": "832", "target": "822", "type": "PROCESS_OF" }, { "id": "L1134", "source": "834", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1135", "source": "834", "target": "822", "type": "PROCESS_OF" }, { "id": "L1136", "source": "836", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1137", "source": "836", "target": "822", "type": "PROCESS_OF" }, { "id": "L1138", "source": "838", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1139", "source": "838", "target": "822", "type": "PROCESS_OF" }, { "id": "L1140", "source": "840", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1141", "source": "840", "target": "822", "type": "PROCESS_OF" }, { "id": "L1142", "source": "842", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1143", "source": "842", "target": "822", "type": "PROCESS_OF" }, { "id": "L1144", "source": "844", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1145", "source": "844", "target": "822", "type": "PROCESS_OF" }, { "id": "L1146", "source": "846", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1147", "source": "846", "target": "822", "type": "PROCESS_OF" }, { "id": "L1148", "source": "848", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1149", "source": "848", "target": "822", "type": "PROCESS_OF" }, { "id": "L1150", "source": "850", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1151", "source": "850", "target": "822", "type": "PROCESS_OF" }, { "id": "L1152", "source": "852", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1153", "source": "852", "target": "822", "type": "PROCESS_OF" }, { "id": "L1154", "source": "854", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1155", "source": "854", "target": "822", "type": "PROCESS_OF" }, { "id": "L1156", "source": "856", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1157", "source": "856", "target": "822", "type": "PROCESS_OF" }, { "id": "L1158", "source": "858", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1159", "source": "858", "target": "822", "type": "PROCESS_OF" }, { "id": "L1160", "source": "860", "target": "9201", "type": "PROCESS_OF" }, { "id": "L1161", "source": "860", "target": "822", "type": "PROCESS_OF" }, { "id": "L1162", "source": "864", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1163", "source": "864", "target": "862", "type": "PROCESS_OF" }, { "id": "L1164", "source": "866", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1165", "source": "866", "target": "862", "type": "PROCESS_OF" }, { "id": "L1166", "source": "868", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1167", "source": "868", "target": "862", "type": "PROCESS_OF" }, { "id": "L1168", "source": "870", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1169", "source": "870", "target": "862", "type": "PROCESS_OF" }, { "id": "L1170", "source": "872", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1171", "source": "872", "target": "862", "type": "PROCESS_OF" }, { "id": "L1172", "source": "874", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1173", "source": "874", "target": "862", "type": "PROCESS_OF" }, { "id": "L1174", "source": "876", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1175", "source": "876", "target": "862", "type": "PROCESS_OF" }, { "id": "L1176", "source": "878", "target": "9181", "type": "PROCESS_OF" }, { "id": "L1177", "source": "878", "target": "1143", "type": "PROCESS_OF" }, { "id": "L1178", "source": "878", "target": "901", "type": "PROCESS_OF" }, { "id": "L1179", "source": "878", "target": "862", "type": "PROCESS_OF" }, { "id": "L1180", "source": "883", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1181", "source": "883", "target": "881", "type": "PROCESS_OF" }, { "id": "L1182", "source": "885", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1183", "source": "885", "target": "881", "type": "PROCESS_OF" }, { "id": "L1184", "source": "887", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1185", "source": "887", "target": "881", "type": "PROCESS_OF" }, { "id": "L1186", "source": "889", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1187", "source": "889", "target": "881", "type": "PROCESS_OF" }, { "id": "L1188", "source": "891", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1189", "source": "891", "target": "881", "type": "PROCESS_OF" }, { "id": "L1190", "source": "893", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1191", "source": "893", "target": "881", "type": "PROCESS_OF" }, { "id": "L1192", "source": "895", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1193", "source": "895", "target": "881", "type": "PROCESS_OF" }, { "id": "L1194", "source": "897", "target": "9176", "type": "PROCESS_OF" }, { "id": "L1195", "source": "897", "target": "881", "type": "PROCESS_OF" }, { "id": "L1196", "source": "899", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1197", "source": "899", "target": "881", "type": "PROCESS_OF" }, { "id": "L1198", "source": "903", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1199", "source": "903", "target": "901", "type": "PROCESS_OF" }, { "id": "L1200", "source": "905", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1201", "source": "905", "target": "901", "type": "PROCESS_OF" }, { "id": "L1202", "source": "907", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1203", "source": "907", "target": "901", "type": "PROCESS_OF" }, { "id": "L1204", "source": "909", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1205", "source": "909", "target": "901", "type": "PROCESS_OF" }, { "id": "L1206", "source": "911", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1207", "source": "911", "target": "901", "type": "PROCESS_OF" }, { "id": "L1208", "source": "913", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1209", "source": "913", "target": "901", "type": "PROCESS_OF" }, { "id": "L1210", "source": "917", "target": "9178", "type": "PROCESS_OF" }, { "id": "L1211", "source": "917", "target": "915", "type": "PROCESS_OF" }, { "id": "L1212", "source": "919", "target": "9178", "type": "PROCESS_OF" }, { "id": "L1213", "source": "919", "target": "915", "type": "PROCESS_OF" }, { "id": "L1214", "source": "921", "target": "9178", "type": "PROCESS_OF" }, { "id": "L1215", "source": "921", "target": "915", "type": "PROCESS_OF" }, { "id": "L1216", "source": "925", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1217", "source": "925", "target": "923", "type": "PROCESS_OF" }, { "id": "L1218", "source": "927", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1219", "source": "927", "target": "923", "type": "PROCESS_OF" }, { "id": "L1220", "source": "929", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1221", "source": "929", "target": "923", "type": "PROCESS_OF" }, { "id": "L1222", "source": "931", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1223", "source": "931", "target": "923", "type": "PROCESS_OF" }, { "id": "L1224", "source": "933", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1225", "source": "933", "target": "923", "type": "PROCESS_OF" }, { "id": "L1226", "source": "935", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1227", "source": "935", "target": "923", "type": "PROCESS_OF" }, { "id": "L1228", "source": "937", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1229", "source": "937", "target": "949", "type": "PROCESS_OF" }, { "id": "L1230", "source": "937", "target": "923", "type": "PROCESS_OF" }, { "id": "L1231", "source": "939", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1232", "source": "939", "target": "923", "type": "PROCESS_OF" }, { "id": "L1233", "source": "941", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1234", "source": "941", "target": "923", "type": "PROCESS_OF" }, { "id": "L1235", "source": "943", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1236", "source": "943", "target": "923", "type": "PROCESS_OF" }, { "id": "L1237", "source": "945", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1238", "source": "945", "target": "923", "type": "PROCESS_OF" }, { "id": "L1239", "source": "947", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1240", "source": "947", "target": "923", "type": "PROCESS_OF" }, { "id": "L1241", "source": "951", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1242", "source": "951", "target": "949", "type": "PROCESS_OF" }, { "id": "L1243", "source": "953", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1244", "source": "953", "target": "949", "type": "PROCESS_OF" }, { "id": "L1245", "source": "955", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1246", "source": "955", "target": "949", "type": "PROCESS_OF" }, { "id": "L1247", "source": "957", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1248", "source": "957", "target": "949", "type": "PROCESS_OF" }, { "id": "L1249", "source": "959", "target": "9176", "type": "PROCESS_OF" }, { "id": "L1250", "source": "959", "target": "949", "type": "PROCESS_OF" }, { "id": "L1251", "source": "961", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1252", "source": "961", "target": "949", "type": "PROCESS_OF" }, { "id": "L1253", "source": "963", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1254", "source": "963", "target": "949", "type": "PROCESS_OF" }, { "id": "L1255", "source": "968", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1256", "source": "968", "target": "966", "type": "PROCESS_OF" }, { "id": "L1257", "source": "970", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1258", "source": "970", "target": "966", "type": "PROCESS_OF" }, { "id": "L1259", "source": "972", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1260", "source": "972", "target": "966", "type": "PROCESS_OF" }, { "id": "L1261", "source": "974", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1262", "source": "974", "target": "966", "type": "PROCESS_OF" }, { "id": "L1263", "source": "976", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1264", "source": "976", "target": "966", "type": "PROCESS_OF" }, { "id": "L1265", "source": "980", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1266", "source": "980", "target": "978", "type": "PROCESS_OF" }, { "id": "L1267", "source": "982", "target": "9176", "type": "PROCESS_OF" }, { "id": "L1268", "source": "982", "target": "978", "type": "PROCESS_OF" }, { "id": "L1269", "source": "984", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1270", "source": "984", "target": "978", "type": "PROCESS_OF" }, { "id": "L1271", "source": "986", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1272", "source": "986", "target": "978", "type": "PROCESS_OF" }, { "id": "L1273", "source": "988", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1274", "source": "988", "target": "978", "type": "PROCESS_OF" }, { "id": "L1275", "source": "990", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1276", "source": "990", "target": "978", "type": "PROCESS_OF" }, { "id": "L1277", "source": "992", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1278", "source": "992", "target": "978", "type": "PROCESS_OF" }, { "id": "L1279", "source": "994", "target": "9180", "type": "PROCESS_OF" }, { "id": "L1280", "source": "994", "target": "978", "type": "PROCESS_OF" }, { "id": "L1281", "source": "999", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1282", "source": "999", "target": "997", "type": "PROCESS_OF" }, { "id": "L1283", "source": "1001", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1284", "source": "1001", "target": "997", "type": "PROCESS_OF" }, { "id": "L1285", "source": "1003", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1286", "source": "1003", "target": "997", "type": "PROCESS_OF" }, { "id": "L1287", "source": "1007", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1288", "source": "1007", "target": "1005", "type": "PROCESS_OF" }, { "id": "L1289", "source": "1009", "target": "1005", "type": "PROCESS_OF" }, { "id": "L1290", "source": "1009", "target": "2049", "type": "PROCESS_OF" }, { "id": "L1291", "source": "1011", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1292", "source": "1011", "target": "1005", "type": "PROCESS_OF" }, { "id": "L1293", "source": "1013", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1294", "source": "1013", "target": "1005", "type": "PROCESS_OF" }, { "id": "L1295", "source": "1015", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1296", "source": "1015", "target": "1005", "type": "PROCESS_OF" }, { "id": "L1297", "source": "1019", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1298", "source": "1019", "target": "1017", "type": "PROCESS_OF" }, { "id": "L1299", "source": "1021", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1300", "source": "1021", "target": "1017", "type": "PROCESS_OF" }, { "id": "L1301", "source": "1023", "target": "9176", "type": "PROCESS_OF" }, { "id": "L1302", "source": "1023", "target": "1017", "type": "PROCESS_OF" }, { "id": "L1303", "source": "1025", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1304", "source": "1025", "target": "1017", "type": "PROCESS_OF" }, { "id": "L1305", "source": "1027", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1306", "source": "1027", "target": "1017", "type": "PROCESS_OF" }, { "id": "L1307", "source": "1029", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1308", "source": "1029", "target": "1017", "type": "PROCESS_OF" }, { "id": "L1309", "source": "1033", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1310", "source": "1033", "target": "1031", "type": "PROCESS_OF" }, { "id": "L1311", "source": "1035", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1312", "source": "1035", "target": "1031", "type": "PROCESS_OF" }, { "id": "L1313", "source": "1037", "target": "9176", "type": "PROCESS_OF" }, { "id": "L1314", "source": "1037", "target": "1031", "type": "PROCESS_OF" }, { "id": "L1315", "source": "1039", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1316", "source": "1039", "target": "1031", "type": "PROCESS_OF" }, { "id": "L1317", "source": "1041", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1318", "source": "1041", "target": "1031", "type": "PROCESS_OF" }, { "id": "L1319", "source": "1046", "target": "2037", "type": "PROCESS_OF" }, { "id": "L1320", "source": "1046", "target": "1044", "type": "PROCESS_OF" }, { "id": "L1321", "source": "1048", "target": "2037", "type": "PROCESS_OF" }, { "id": "L1322", "source": "1048", "target": "1044", "type": "PROCESS_OF" }, { "id": "L1323", "source": "1050", "target": "1044", "type": "PROCESS_OF" }, { "id": "L1324", "source": "1050", "target": "2037", "type": "PROCESS_OF" }, { "id": "L1325", "source": "1052", "target": "1044", "type": "PROCESS_OF" }, { "id": "L1326", "source": "1052", "target": "2037", "type": "PROCESS_OF" }, { "id": "L1327", "source": "1054", "target": "1044", "type": "PROCESS_OF" }, { "id": "L1328", "source": "1054", "target": "2037", "type": "PROCESS_OF" }, { "id": "L1329", "source": "1056", "target": "1044", "type": "PROCESS_OF" }, { "id": "L1330", "source": "1056", "target": "2037", "type": "PROCESS_OF" }, { "id": "L1331", "source": "1058", "target": "2037", "type": "PROCESS_OF" }, { "id": "L1332", "source": "1058", "target": "1044", "type": "PROCESS_OF" }, { "id": "L1333", "source": "1062", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1334", "source": "1062", "target": "1060", "type": "PROCESS_OF" }, { "id": "L1335", "source": "1064", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1336", "source": "1064", "target": "1060", "type": "PROCESS_OF" }, { "id": "L1337", "source": "1066", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1338", "source": "1066", "target": "1060", "type": "PROCESS_OF" }, { "id": "L1339", "source": "1070", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1340", "source": "1070", "target": "1068", "type": "PROCESS_OF" }, { "id": "L1341", "source": "1072", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1342", "source": "1072", "target": "1068", "type": "PROCESS_OF" }, { "id": "L1343", "source": "1074", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1344", "source": "1074", "target": "1068", "type": "PROCESS_OF" }, { "id": "L1345", "source": "1076", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1346", "source": "1076", "target": "1068", "type": "PROCESS_OF" }, { "id": "L1347", "source": "1078", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1348", "source": "1078", "target": "1068", "type": "PROCESS_OF" }, { "id": "L1349", "source": "1082", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1350", "source": "1082", "target": "1080", "type": "PROCESS_OF" }, { "id": "L1351", "source": "1084", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1352", "source": "1084", "target": "1080", "type": "PROCESS_OF" }, { "id": "L1353", "source": "1086", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1354", "source": "1086", "target": "1080", "type": "PROCESS_OF" }, { "id": "L1355", "source": "1088", "target": "9205", "type": "PROCESS_OF" }, { "id": "L1356", "source": "1088", "target": "1080", "type": "PROCESS_OF" }, { "id": "L1357", "source": "1092", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1358", "source": "1092", "target": "1090", "type": "PROCESS_OF" }, { "id": "L1359", "source": "1094", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1360", "source": "1094", "target": "1090", "type": "PROCESS_OF" }, { "id": "L1361", "source": "1096", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1362", "source": "1096", "target": "1090", "type": "PROCESS_OF" }, { "id": "L1363", "source": "1098", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1364", "source": "1098", "target": "1090", "type": "PROCESS_OF" }, { "id": "L1365", "source": "1100", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1366", "source": "1100", "target": "1090", "type": "PROCESS_OF" }, { "id": "L1367", "source": "1102", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1368", "source": "1102", "target": "1090", "type": "PROCESS_OF" }, { "id": "L1369", "source": "1107", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1370", "source": "1107", "target": "1105", "type": "PROCESS_OF" }, { "id": "L1371", "source": "1109", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1372", "source": "1109", "target": "1105", "type": "PROCESS_OF" }, { "id": "L1373", "source": "1111", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1374", "source": "1111", "target": "1129", "type": "PROCESS_OF" }, { "id": "L1375", "source": "1111", "target": "1105", "type": "PROCESS_OF" }, { "id": "L1376", "source": "1113", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1377", "source": "1113", "target": "1105", "type": "PROCESS_OF" }, { "id": "L1378", "source": "1115", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1379", "source": "1115", "target": "1105", "type": "PROCESS_OF" }, { "id": "L1380", "source": "1117", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1381", "source": "1117", "target": "1105", "type": "PROCESS_OF" }, { "id": "L1382", "source": "1121", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1383", "source": "1121", "target": "1119", "type": "PROCESS_OF" }, { "id": "L1384", "source": "1123", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1385", "source": "1123", "target": "1119", "type": "PROCESS_OF" }, { "id": "L1386", "source": "1125", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1387", "source": "1125", "target": "1119", "type": "PROCESS_OF" }, { "id": "L1388", "source": "1127", "target": "9174", "type": "PROCESS_OF" }, { "id": "L1389", "source": "1127", "target": "1119", "type": "PROCESS_OF" }, { "id": "L1390", "source": "1131", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1391", "source": "1131", "target": "1129", "type": "PROCESS_OF" }, { "id": "L1392", "source": "1133", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1393", "source": "1133", "target": "1129", "type": "PROCESS_OF" }, { "id": "L1394", "source": "1135", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1395", "source": "1135", "target": "1129", "type": "PROCESS_OF" }, { "id": "L1396", "source": "1137", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1397", "source": "1137", "target": "1129", "type": "PROCESS_OF" }, { "id": "L1398", "source": "1139", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1399", "source": "1139", "target": "1129", "type": "PROCESS_OF" }, { "id": "L1400", "source": "1141", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1401", "source": "1141", "target": "1129", "type": "PROCESS_OF" }, { "id": "L1402", "source": "1145", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1403", "source": "1145", "target": "1143", "type": "PROCESS_OF" }, { "id": "L1404", "source": "1147", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1405", "source": "1147", "target": "1143", "type": "PROCESS_OF" }, { "id": "L1406", "source": "1149", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1407", "source": "1149", "target": "1143", "type": "PROCESS_OF" }, { "id": "L1408", "source": "1151", "target": "9176", "type": "PROCESS_OF" }, { "id": "L1409", "source": "1151", "target": "1143", "type": "PROCESS_OF" }, { "id": "L1410", "source": "1153", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1411", "source": "1153", "target": "1143", "type": "PROCESS_OF" }, { "id": "L1412", "source": "1155", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1413", "source": "1155", "target": "1143", "type": "PROCESS_OF" }, { "id": "L1414", "source": "1157", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1415", "source": "1157", "target": "1143", "type": "PROCESS_OF" }, { "id": "L1416", "source": "1159", "target": "9177", "type": "PROCESS_OF" }, { "id": "L1417", "source": "1159", "target": "1143", "type": "PROCESS_OF" }, { "id": "L1418", "source": "1165", "target": "1185", "type": "PROCESS_OF" }, { "id": "L1419", "source": "1165", "target": "1181", "type": "PROCESS_OF" }, { "id": "L1420", "source": "1165", "target": "1169", "type": "PROCESS_OF" }, { "id": "L1421", "source": "1165", "target": "1163", "type": "PROCESS_OF" }, { "id": "L1422", "source": "1165", "target": "1986", "type": "PROCESS_OF" }, { "id": "L1423", "source": "1167", "target": "1185", "type": "PROCESS_OF" }, { "id": "L1424", "source": "1167", "target": "1163", "type": "PROCESS_OF" }, { "id": "L1425", "source": "1167", "target": "1961", "type": "PROCESS_OF" }, { "id": "L1426", "source": "1171", "target": "1181", "type": "PROCESS_OF" }, { "id": "L1427", "source": "1171", "target": "1169", "type": "PROCESS_OF" }, { "id": "L1428", "source": "1171", "target": "1942", "type": "PROCESS_OF" }, { "id": "L1429", "source": "1173", "target": "1181", "type": "PROCESS_OF" }, { "id": "L1430", "source": "1173", "target": "1169", "type": "PROCESS_OF" }, { "id": "L1431", "source": "1173", "target": "1942", "type": "PROCESS_OF" }, { "id": "L1432", "source": "1175", "target": "1181", "type": "PROCESS_OF" }, { "id": "L1433", "source": "1175", "target": "1169", "type": "PROCESS_OF" }, { "id": "L1434", "source": "1175", "target": "1942", "type": "PROCESS_OF" }, { "id": "L1435", "source": "1177", "target": "1181", "type": "PROCESS_OF" }, { "id": "L1436", "source": "1177", "target": "1169", "type": "PROCESS_OF" }, { "id": "L1437", "source": "1177", "target": "1942", "type": "PROCESS_OF" }, { "id": "L1438", "source": "1179", "target": "1181", "type": "PROCESS_OF" }, { "id": "L1439", "source": "1179", "target": "1169", "type": "PROCESS_OF" }, { "id": "L1440", "source": "1179", "target": "1942", "type": "PROCESS_OF" }, { "id": "L1441", "source": "1183", "target": "1181", "type": "PROCESS_OF" }, { "id": "L1442", "source": "1183", "target": "1942", "type": "PROCESS_OF" }, { "id": "L1443", "source": "1187", "target": "1185", "type": "PROCESS_OF" }, { "id": "L1444", "source": "1187", "target": "1950", "type": "PROCESS_OF" }, { "id": "L1445", "source": "1192", "target": "1190", "type": "PROCESS_OF" }, { "id": "L1446", "source": "1192", "target": "1950", "type": "PROCESS_OF" }, { "id": "L1447", "source": "1194", "target": "1190", "type": "PROCESS_OF" }, { "id": "L1448", "source": "1194", "target": "1950", "type": "PROCESS_OF" }, { "id": "L1449", "source": "1196", "target": "1190", "type": "PROCESS_OF" }, { "id": "L1450", "source": "1196", "target": "1950", "type": "PROCESS_OF" }, { "id": "L1451", "source": "1200", "target": "1198", "type": "PROCESS_OF" }, { "id": "L1452", "source": "1200", "target": "1950", "type": "PROCESS_OF" }, { "id": "L1453", "source": "1202", "target": "1198", "type": "PROCESS_OF" }, { "id": "L1454", "source": "1202", "target": "1950", "type": "PROCESS_OF" }, { "id": "L1455", "source": "1204", "target": "1961", "type": "PROCESS_OF" }, { "id": "L1456", "source": "1204", "target": "8549", "type": "PROCESS_OF" }, { "id": "L1457", "source": "1204", "target": "1198", "type": "PROCESS_OF" }, { "id": "L1458", "source": "1204", "target": "1950", "type": "PROCESS_OF" }, { "id": "L1459", "source": "1210", "target": "1208", "type": "PROCESS_OF" }, { "id": "L1460", "source": "1210", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1461", "source": "1212", "target": "1208", "type": "PROCESS_OF" }, { "id": "L1462", "source": "1212", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1463", "source": "1214", "target": "1208", "type": "PROCESS_OF" }, { "id": "L1464", "source": "1214", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1465", "source": "1216", "target": "1266", "type": "PROCESS_OF" }, { "id": "L1466", "source": "1216", "target": "1262", "type": "PROCESS_OF" }, { "id": "L1467", "source": "1216", "target": "1258", "type": "PROCESS_OF" }, { "id": "L1468", "source": "1216", "target": "1237", "type": "PROCESS_OF" }, { "id": "L1469", "source": "1216", "target": "1232", "type": "PROCESS_OF" }, { "id": "L1470", "source": "1216", "target": "1221", "type": "PROCESS_OF" }, { "id": "L1471", "source": "1216", "target": "1208", "type": "PROCESS_OF" }, { "id": "L1472", "source": "1216", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1473", "source": "1218", "target": "1208", "type": "PROCESS_OF" }, { "id": "L1474", "source": "1218", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1475", "source": "1223", "target": "1221", "type": "PROCESS_OF" }, { "id": "L1476", "source": "1223", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1477", "source": "1225", "target": "1221", "type": "PROCESS_OF" }, { "id": "L1478", "source": "1225", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1479", "source": "1227", "target": "1221", "type": "PROCESS_OF" }, { "id": "L1480", "source": "1227", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1481", "source": "1229", "target": "1221", "type": "PROCESS_OF" }, { "id": "L1482", "source": "1229", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1483", "source": "1234", "target": "1232", "type": "PROCESS_OF" }, { "id": "L1484", "source": "1234", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1485", "source": "1239", "target": "1237", "type": "PROCESS_OF" }, { "id": "L1486", "source": "1239", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1487", "source": "1241", "target": "1927", "type": "PROCESS_OF" }, { "id": "L1488", "source": "1241", "target": "1243", "type": "PROCESS_OF" }, { "id": "L1489", "source": "1241", "target": "1237", "type": "PROCESS_OF" }, { "id": "L1490", "source": "1241", "target": "1936", "type": "PROCESS_OF" }, { "id": "L1491", "source": "1245", "target": "1243", "type": "PROCESS_OF" }, { "id": "L1492", "source": "1245", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1493", "source": "1246", "target": "1243", "type": "PROCESS_OF" }, { "id": "L1494", "source": "1246", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1495", "source": "1247", "target": "1243", "type": "PROCESS_OF" }, { "id": "L1496", "source": "1247", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1497", "source": "1251", "target": "1249", "type": "PROCESS_OF" }, { "id": "L1498", "source": "1251", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1499", "source": "1256", "target": "1254", "type": "PROCESS_OF" }, { "id": "L1500", "source": "1256", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1501", "source": "1260", "target": "1258", "type": "PROCESS_OF" }, { "id": "L1502", "source": "1260", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1503", "source": "1264", "target": "1262", "type": "PROCESS_OF" }, { "id": "L1504", "source": "1264", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1505", "source": "1268", "target": "1266", "type": "PROCESS_OF" }, { "id": "L1506", "source": "1268", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1507", "source": "1270", "target": "1266", "type": "PROCESS_OF" }, { "id": "L1508", "source": "1270", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1509", "source": "1272", "target": "1266", "type": "PROCESS_OF" }, { "id": "L1510", "source": "1272", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1511", "source": "1276", "target": "1274", "type": "PROCESS_OF" }, { "id": "L1512", "source": "1276", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1513", "source": "1277", "target": "1274", "type": "PROCESS_OF" }, { "id": "L1514", "source": "1277", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1515", "source": "1281", "target": "1279", "type": "PROCESS_OF" }, { "id": "L1516", "source": "1281", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1517", "source": "1283", "target": "1279", "type": "PROCESS_OF" }, { "id": "L1518", "source": "1283", "target": "2206", "type": "PROCESS_OF" }, { "id": "L1519", "source": "1290", "target": "1779", "type": "PROCESS_OF" }, { "id": "L1520", "source": "1290", "target": "1288", "type": "PROCESS_OF" }, { "id": "L1521", "source": "1290", "target": "2137", "type": "PROCESS_OF" }, { "id": "L1522", "source": "1292", "target": "1441", "type": "PROCESS_OF" }, { "id": "L1523", "source": "1292", "target": "1418", "type": "PROCESS_OF" }, { "id": "L1524", "source": "1292", "target": "1288", "type": "PROCESS_OF" }, { "id": "L1525", "source": "1292", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1526", "source": "1294", "target": "1427", "type": "PROCESS_OF" }, { "id": "L1527", "source": "1294", "target": "1346", "type": "PROCESS_OF" }, { "id": "L1528", "source": "1294", "target": "1288", "type": "PROCESS_OF" }, { "id": "L1529", "source": "1294", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1530", "source": "1299", "target": "1297", "type": "PROCESS_OF" }, { "id": "L1531", "source": "1299", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1532", "source": "1301", "target": "1297", "type": "PROCESS_OF" }, { "id": "L1533", "source": "1301", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1534", "source": "1303", "target": "1297", "type": "PROCESS_OF" }, { "id": "L1535", "source": "1303", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1536", "source": "1305", "target": "1297", "type": "PROCESS_OF" }, { "id": "L1537", "source": "1305", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1538", "source": "1309", "target": "1319", "type": "PROCESS_OF" }, { "id": "L1539", "source": "1309", "target": "1307", "type": "PROCESS_OF" }, { "id": "L1540", "source": "1309", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1541", "source": "1311", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1542", "source": "1311", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1543", "source": "1311", "target": "1307", "type": "PROCESS_OF" }, { "id": "L1544", "source": "1311", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1545", "source": "1313", "target": "1319", "type": "PROCESS_OF" }, { "id": "L1546", "source": "1313", "target": "1307", "type": "PROCESS_OF" }, { "id": "L1547", "source": "1313", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1548", "source": "1315", "target": "1307", "type": "PROCESS_OF" }, { "id": "L1549", "source": "1315", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1550", "source": "1317", "target": "1319", "type": "PROCESS_OF" }, { "id": "L1551", "source": "1317", "target": "1307", "type": "PROCESS_OF" }, { "id": "L1552", "source": "1317", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1553", "source": "1321", "target": "1319", "type": "PROCESS_OF" }, { "id": "L1554", "source": "1321", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1555", "source": "1323", "target": "1319", "type": "PROCESS_OF" }, { "id": "L1556", "source": "1323", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1557", "source": "1328", "target": "8666", "type": "PROCESS_OF" }, { "id": "L1558", "source": "1328", "target": "1757", "type": "PROCESS_OF" }, { "id": "L1559", "source": "1328", "target": "1750", "type": "PROCESS_OF" }, { "id": "L1560", "source": "1328", "target": "1748", "type": "PROCESS_OF" }, { "id": "L1561", "source": "1328", "target": "1746", "type": "PROCESS_OF" }, { "id": "L1562", "source": "1328", "target": "1738", "type": "PROCESS_OF" }, { "id": "L1563", "source": "1328", "target": "1732", "type": "PROCESS_OF" }, { "id": "L1564", "source": "1328", "target": "1724", "type": "PROCESS_OF" }, { "id": "L1565", "source": "1328", "target": "1710", "type": "PROCESS_OF" }, { "id": "L1566", "source": "1328", "target": "1326", "type": "PROCESS_OF" }, { "id": "L1567", "source": "1328", "target": "2217", "type": "PROCESS_OF" }, { "id": "L1568", "source": "1330", "target": "1326", "type": "PROCESS_OF" }, { "id": "L1569", "source": "1330", "target": "1890", "type": "PROCESS_OF" }, { "id": "L1570", "source": "1332", "target": "1326", "type": "PROCESS_OF" }, { "id": "L1571", "source": "1332", "target": "2129", "type": "PROCESS_OF" }, { "id": "L1572", "source": "1334", "target": "1441", "type": "PROCESS_OF" }, { "id": "L1573", "source": "1334", "target": "1422", "type": "PROCESS_OF" }, { "id": "L1574", "source": "1334", "target": "1418", "type": "PROCESS_OF" }, { "id": "L1575", "source": "1334", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1576", "source": "1334", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1577", "source": "1334", "target": "1326", "type": "PROCESS_OF" }, { "id": "L1578", "source": "1334", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1579", "source": "1336", "target": "1441", "type": "PROCESS_OF" }, { "id": "L1580", "source": "1336", "target": "1422", "type": "PROCESS_OF" }, { "id": "L1581", "source": "1336", "target": "1418", "type": "PROCESS_OF" }, { "id": "L1582", "source": "1336", "target": "1326", "type": "PROCESS_OF" }, { "id": "L1583", "source": "1336", "target": "2137", "type": "PROCESS_OF" }, { "id": "L1584", "source": "1338", "target": "1326", "type": "PROCESS_OF" }, { "id": "L1585", "source": "1338", "target": "1890", "type": "PROCESS_OF" }, { "id": "L1586", "source": "1340", "target": "1441", "type": "PROCESS_OF" }, { "id": "L1587", "source": "1340", "target": "1422", "type": "PROCESS_OF" }, { "id": "L1588", "source": "1340", "target": "1418", "type": "PROCESS_OF" }, { "id": "L1589", "source": "1340", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1590", "source": "1340", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1591", "source": "1340", "target": "1326", "type": "PROCESS_OF" }, { "id": "L1592", "source": "1340", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1593", "source": "1342", "target": "1441", "type": "PROCESS_OF" }, { "id": "L1594", "source": "1342", "target": "1422", "type": "PROCESS_OF" }, { "id": "L1595", "source": "1342", "target": "1418", "type": "PROCESS_OF" }, { "id": "L1596", "source": "1342", "target": "1326", "type": "PROCESS_OF" }, { "id": "L1597", "source": "1342", "target": "2129", "type": "PROCESS_OF" }, { "id": "L1598", "source": "1348", "target": "8666", "type": "PROCESS_OF" }, { "id": "L1599", "source": "1348", "target": "1761", "type": "PROCESS_OF" }, { "id": "L1600", "source": "1348", "target": "1757", "type": "PROCESS_OF" }, { "id": "L1601", "source": "1348", "target": "1746", "type": "PROCESS_OF" }, { "id": "L1602", "source": "1348", "target": "1738", "type": "PROCESS_OF" }, { "id": "L1603", "source": "1348", "target": "1732", "type": "PROCESS_OF" }, { "id": "L1604", "source": "1348", "target": "1696", "type": "PROCESS_OF" }, { "id": "L1605", "source": "1348", "target": "1346", "type": "PROCESS_OF" }, { "id": "L1606", "source": "1348", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1607", "source": "1350", "target": "1346", "type": "PROCESS_OF" }, { "id": "L1608", "source": "1350", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1609", "source": "1352", "target": "1346", "type": "PROCESS_OF" }, { "id": "L1610", "source": "1352", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1611", "source": "1354", "target": "1346", "type": "PROCESS_OF" }, { "id": "L1612", "source": "1354", "target": "2129", "type": "PROCESS_OF" }, { "id": "L1613", "source": "1359", "target": "1357", "type": "PROCESS_OF" }, { "id": "L1614", "source": "1359", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1615", "source": "1361", "target": "1357", "type": "PROCESS_OF" }, { "id": "L1616", "source": "1361", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1617", "source": "1363", "target": "1357", "type": "PROCESS_OF" }, { "id": "L1618", "source": "1363", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1619", "source": "1365", "target": "1357", "type": "PROCESS_OF" }, { "id": "L1620", "source": "1365", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1621", "source": "1367", "target": "1357", "type": "PROCESS_OF" }, { "id": "L1622", "source": "1367", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1623", "source": "1372", "target": "1370", "type": "PROCESS_OF" }, { "id": "L1624", "source": "1372", "target": "2088", "type": "PROCESS_OF" }, { "id": "L1625", "source": "1374", "target": "1376", "type": "PROCESS_OF" }, { "id": "L1626", "source": "1374", "target": "1370", "type": "PROCESS_OF" }, { "id": "L1627", "source": "1374", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1628", "source": "1378", "target": "1376", "type": "PROCESS_OF" }, { "id": "L1629", "source": "1378", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1630", "source": "1382", "target": "8501", "type": "PROCESS_OF" }, { "id": "L1631", "source": "1382", "target": "1380", "type": "PROCESS_OF" }, { "id": "L1632", "source": "1382", "target": "1832", "type": "PROCESS_OF" }, { "id": "L1633", "source": "1384", "target": "8501", "type": "PROCESS_OF" }, { "id": "L1634", "source": "1384", "target": "1380", "type": "PROCESS_OF" }, { "id": "L1635", "source": "1384", "target": "1832", "type": "PROCESS_OF" }, { "id": "L1636", "source": "1386", "target": "8501", "type": "PROCESS_OF" }, { "id": "L1637", "source": "1386", "target": "1380", "type": "PROCESS_OF" }, { "id": "L1638", "source": "1386", "target": "1832", "type": "PROCESS_OF" }, { "id": "L1639", "source": "1388", "target": "2186", "type": "PROCESS_OF" }, { "id": "L1640", "source": "1388", "target": "8501", "type": "PROCESS_OF" }, { "id": "L1641", "source": "1388", "target": "1380", "type": "PROCESS_OF" }, { "id": "L1642", "source": "1388", "target": "1832", "type": "PROCESS_OF" }, { "id": "L1643", "source": "1392", "target": "1390", "type": "PROCESS_OF" }, { "id": "L1644", "source": "1392", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1645", "source": "1393", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1646", "source": "1393", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1647", "source": "1393", "target": "1390", "type": "PROCESS_OF" }, { "id": "L1648", "source": "1393", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1649", "source": "1395", "target": "1390", "type": "PROCESS_OF" }, { "id": "L1650", "source": "1395", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1651", "source": "1396", "target": "1390", "type": "PROCESS_OF" }, { "id": "L1652", "source": "1396", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1653", "source": "1397", "target": "1390", "type": "PROCESS_OF" }, { "id": "L1654", "source": "1397", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1655", "source": "1398", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1656", "source": "1398", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1657", "source": "1398", "target": "1390", "type": "PROCESS_OF" }, { "id": "L1658", "source": "1398", "target": "1947", "type": "PROCESS_OF" }, { "id": "L1659", "source": "1401", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1660", "source": "1401", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1661", "source": "1401", "target": "1832", "type": "PROCESS_OF" }, { "id": "L1662", "source": "1403", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1663", "source": "1403", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1664", "source": "1403", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1665", "source": "1405", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1666", "source": "1405", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1667", "source": "1405", "target": "2129", "type": "PROCESS_OF" }, { "id": "L1668", "source": "1407", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1669", "source": "1407", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1670", "source": "1407", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1671", "source": "1409", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1672", "source": "1409", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1673", "source": "1410", "target": "471", "type": "PROCESS_OF" }, { "id": "L1674", "source": "1410", "target": "1441", "type": "PROCESS_OF" }, { "id": "L1675", "source": "1410", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1676", "source": "1410", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1677", "source": "1411", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1678", "source": "1411", "target": "1399", "type": "PROCESS_OF" }, { "id": "L1679", "source": "1411", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1680", "source": "1415", "target": "1413", "type": "PROCESS_OF" }, { "id": "L1681", "source": "1415", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1682", "source": "1420", "target": "1437", "type": "PROCESS_OF" }, { "id": "L1683", "source": "1420", "target": "1418", "type": "PROCESS_OF" }, { "id": "L1684", "source": "1420", "target": "2137", "type": "PROCESS_OF" }, { "id": "L1685", "source": "1424", "target": "1422", "type": "PROCESS_OF" }, { "id": "L1686", "source": "1424", "target": "2217", "type": "PROCESS_OF" }, { "id": "L1687", "source": "1425", "target": "1422", "type": "PROCESS_OF" }, { "id": "L1688", "source": "1425", "target": "2210", "type": "PROCESS_OF" }, { "id": "L1689", "source": "1426", "target": "1422", "type": "PROCESS_OF" }, { "id": "L1690", "source": "1426", "target": "2137", "type": "PROCESS_OF" }, { "id": "L1691", "source": "1429", "target": "1427", "type": "PROCESS_OF" }, { "id": "L1692", "source": "1429", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1693", "source": "1431", "target": "1427", "type": "PROCESS_OF" }, { "id": "L1694", "source": "1431", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1695", "source": "1433", "target": "1427", "type": "PROCESS_OF" }, { "id": "L1696", "source": "1433", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1697", "source": "1435", "target": "1427", "type": "PROCESS_OF" }, { "id": "L1698", "source": "1435", "target": "2137", "type": "PROCESS_OF" }, { "id": "L1699", "source": "1439", "target": "1437", "type": "PROCESS_OF" }, { "id": "L1700", "source": "1439", "target": "2137", "type": "PROCESS_OF" }, { "id": "L1701", "source": "1440", "target": "1437", "type": "PROCESS_OF" }, { "id": "L1702", "source": "1440", "target": "2137", "type": "PROCESS_OF" }, { "id": "L1703", "source": "1443", "target": "1441", "type": "PROCESS_OF" }, { "id": "L1704", "source": "1443", "target": "2137", "type": "PROCESS_OF" }, { "id": "L1705", "source": "1444", "target": "471", "type": "PROCESS_OF" }, { "id": "L1706", "source": "1444", "target": "1441", "type": "PROCESS_OF" }, { "id": "L1707", "source": "1444", "target": "2137", "type": "PROCESS_OF" }, { "id": "L1708", "source": "1449", "target": "1447", "type": "PROCESS_OF" }, { "id": "L1709", "source": "1449", "target": "2132", "type": "PROCESS_OF" }, { "id": "L1710", "source": "1451", "target": "1447", "type": "PROCESS_OF" }, { "id": "L1711", "source": "1451", "target": "2132", "type": "PROCESS_OF" }, { "id": "L1712", "source": "1455", "target": "1453", "type": "PROCESS_OF" }, { "id": "L1713", "source": "1455", "target": "2132", "type": "PROCESS_OF" }, { "id": "L1714", "source": "1457", "target": "1453", "type": "PROCESS_OF" }, { "id": "L1715", "source": "1457", "target": "2132", "type": "PROCESS_OF" }, { "id": "L1716", "source": "1459", "target": "1453", "type": "PROCESS_OF" }, { "id": "L1717", "source": "1459", "target": "2132", "type": "PROCESS_OF" }, { "id": "L1718", "source": "1465", "target": "8562", "type": "PROCESS_OF" }, { "id": "L1719", "source": "1465", "target": "1471", "type": "PROCESS_OF" }, { "id": "L1720", "source": "1465", "target": "1469", "type": "PROCESS_OF" }, { "id": "L1721", "source": "1465", "target": "1463", "type": "PROCESS_OF" }, { "id": "L1722", "source": "1465", "target": "2203", "type": "PROCESS_OF" }, { "id": "L1723", "source": "1467", "target": "8562", "type": "PROCESS_OF" }, { "id": "L1724", "source": "1467", "target": "1790", "type": "PROCESS_OF" }, { "id": "L1725", "source": "1467", "target": "1469", "type": "PROCESS_OF" }, { "id": "L1726", "source": "1467", "target": "1463", "type": "PROCESS_OF" }, { "id": "L1727", "source": "1477", "target": "8563", "type": "PROCESS_OF" }, { "id": "L1728", "source": "1477", "target": "1475", "type": "PROCESS_OF" }, { "id": "L1729", "source": "1477", "target": "1831", "type": "PROCESS_OF" }, { "id": "L1730", "source": "1481", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1731", "source": "1481", "target": "1531", "type": "PROCESS_OF" }, { "id": "L1732", "source": "1481", "target": "1515", "type": "PROCESS_OF" }, { "id": "L1733", "source": "1481", "target": "1511", "type": "PROCESS_OF" }, { "id": "L1734", "source": "1481", "target": "1499", "type": "PROCESS_OF" }, { "id": "L1735", "source": "1481", "target": "1479", "type": "PROCESS_OF" }, { "id": "L1736", "source": "1483", "target": "1479", "type": "PROCESS_OF" }, { "id": "L1737", "source": "1483", "target": "1957", "type": "PROCESS_OF" }, { "id": "L1738", "source": "1485", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1739", "source": "1485", "target": "1531", "type": "PROCESS_OF" }, { "id": "L1740", "source": "1485", "target": "1515", "type": "PROCESS_OF" }, { "id": "L1741", "source": "1485", "target": "1499", "type": "PROCESS_OF" }, { "id": "L1742", "source": "1485", "target": "1479", "type": "PROCESS_OF" }, { "id": "L1743", "source": "1487", "target": "1479", "type": "PROCESS_OF" }, { "id": "L1744", "source": "1487", "target": "1957", "type": "PROCESS_OF" }, { "id": "L1745", "source": "1489", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1746", "source": "1489", "target": "1531", "type": "PROCESS_OF" }, { "id": "L1747", "source": "1489", "target": "1515", "type": "PROCESS_OF" }, { "id": "L1748", "source": "1489", "target": "1499", "type": "PROCESS_OF" }, { "id": "L1749", "source": "1489", "target": "1479", "type": "PROCESS_OF" }, { "id": "L1750", "source": "1491", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1751", "source": "1491", "target": "1531", "type": "PROCESS_OF" }, { "id": "L1752", "source": "1491", "target": "1515", "type": "PROCESS_OF" }, { "id": "L1753", "source": "1491", "target": "1499", "type": "PROCESS_OF" }, { "id": "L1754", "source": "1491", "target": "1479", "type": "PROCESS_OF" }, { "id": "L1755", "source": "1493", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1756", "source": "1493", "target": "1479", "type": "PROCESS_OF" }, { "id": "L1757", "source": "1495", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1758", "source": "1495", "target": "1479", "type": "PROCESS_OF" }, { "id": "L1759", "source": "1497", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1760", "source": "1497", "target": "1479", "type": "PROCESS_OF" }, { "id": "L1761", "source": "1501", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1762", "source": "1501", "target": "1499", "type": "PROCESS_OF" }, { "id": "L1763", "source": "1503", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1764", "source": "1503", "target": "1499", "type": "PROCESS_OF" }, { "id": "L1765", "source": "1505", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1766", "source": "1505", "target": "1499", "type": "PROCESS_OF" }, { "id": "L1767", "source": "1507", "target": "1499", "type": "PROCESS_OF" }, { "id": "L1768", "source": "1507", "target": "1957", "type": "PROCESS_OF" }, { "id": "L1769", "source": "1509", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1770", "source": "1509", "target": "1531", "type": "PROCESS_OF" }, { "id": "L1771", "source": "1509", "target": "1515", "type": "PROCESS_OF" }, { "id": "L1772", "source": "1509", "target": "1499", "type": "PROCESS_OF" }, { "id": "L1773", "source": "1513", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1774", "source": "1513", "target": "1757", "type": "PROCESS_OF" }, { "id": "L1775", "source": "1513", "target": "1511", "type": "PROCESS_OF" }, { "id": "L1776", "source": "1517", "target": "1792", "type": "PROCESS_OF" }, { "id": "L1777", "source": "1517", "target": "1515", "type": "PROCESS_OF" }, { "id": "L1778", "source": "1519", "target": "1792", "type": "PROCESS_OF" }, { "id": "L1779", "source": "1519", "target": "1515", "type": "PROCESS_OF" }, { "id": "L1780", "source": "1521", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1781", "source": "1521", "target": "1531", "type": "PROCESS_OF" }, { "id": "L1782", "source": "1521", "target": "1515", "type": "PROCESS_OF" }, { "id": "L1783", "source": "1523", "target": "1790", "type": "PROCESS_OF" }, { "id": "L1784", "source": "1523", "target": "1515", "type": "PROCESS_OF" }, { "id": "L1785", "source": "1525", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1786", "source": "1525", "target": "1515", "type": "PROCESS_OF" }, { "id": "L1787", "source": "1529", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1788", "source": "1529", "target": "1527", "type": "PROCESS_OF" }, { "id": "L1789", "source": "1533", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1790", "source": "1533", "target": "1531", "type": "PROCESS_OF" }, { "id": "L1791", "source": "1535", "target": "1531", "type": "PROCESS_OF" }, { "id": "L1792", "source": "1535", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1793", "source": "1537", "target": "1531", "type": "PROCESS_OF" }, { "id": "L1794", "source": "1537", "target": "2137", "type": "PROCESS_OF" }, { "id": "L1795", "source": "1539", "target": "1787", "type": "PROCESS_OF" }, { "id": "L1796", "source": "1539", "target": "1531", "type": "PROCESS_OF" }, { "id": "L1797", "source": "1547", "target": "1545", "type": "PROCESS_OF" }, { "id": "L1798", "source": "1547", "target": "1927", "type": "PROCESS_OF" }, { "id": "L1799", "source": "1548", "target": "1545", "type": "PROCESS_OF" }, { "id": "L1800", "source": "1548", "target": "1890", "type": "PROCESS_OF" }, { "id": "L1801", "source": "1549", "target": "1545", "type": "PROCESS_OF" }, { "id": "L1802", "source": "1549", "target": "1890", "type": "PROCESS_OF" }, { "id": "L1803", "source": "1550", "target": "1545", "type": "PROCESS_OF" }, { "id": "L1804", "source": "1550", "target": "1890", "type": "PROCESS_OF" }, { "id": "L1805", "source": "1551", "target": "1545", "type": "PROCESS_OF" }, { "id": "L1806", "source": "1551", "target": "1890", "type": "PROCESS_OF" }, { "id": "L1807", "source": "1552", "target": "1545", "type": "PROCESS_OF" }, { "id": "L1808", "source": "1552", "target": "1890", "type": "PROCESS_OF" }, { "id": "L1809", "source": "1553", "target": "1545", "type": "PROCESS_OF" }, { "id": "L1810", "source": "1553", "target": "1890", "type": "PROCESS_OF" }, { "id": "L1811", "source": "1554", "target": "1545", "type": "PROCESS_OF" }, { "id": "L1812", "source": "1554", "target": "1927", "type": "PROCESS_OF" }, { "id": "L1813", "source": "1555", "target": "1545", "type": "PROCESS_OF" }, { "id": "L1814", "source": "1555", "target": "1890", "type": "PROCESS_OF" }, { "id": "L1815", "source": "1556", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1816", "source": "1556", "target": "1545", "type": "PROCESS_OF" }, { "id": "L1817", "source": "1556", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1818", "source": "1560", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1819", "source": "1560", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1820", "source": "1561", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1821", "source": "1561", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1822", "source": "1562", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1823", "source": "1562", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1824", "source": "1563", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1825", "source": "1563", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1826", "source": "1564", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1827", "source": "1564", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1828", "source": "1565", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1829", "source": "1565", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1830", "source": "1566", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1831", "source": "1566", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1832", "source": "1567", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1833", "source": "1567", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1834", "source": "1568", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1835", "source": "1568", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1836", "source": "1569", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1837", "source": "1569", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1838", "source": "1570", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1839", "source": "1570", "target": "2124", "type": "PROCESS_OF" }, { "id": "L1840", "source": "1571", "target": "1558", "type": "PROCESS_OF" }, { "id": "L1841", "source": "1571", "target": "1888", "type": "PROCESS_OF" }, { "id": "L1842", "source": "1575", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1843", "source": "1575", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1844", "source": "1576", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1845", "source": "1576", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1846", "source": "1577", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1847", "source": "1577", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1848", "source": "1578", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1849", "source": "1578", "target": "1881", "type": "PROCESS_OF" }, { "id": "L1850", "source": "1579", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1851", "source": "1579", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1852", "source": "1580", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1853", "source": "1580", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1854", "source": "1581", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1855", "source": "1581", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1856", "source": "1582", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1857", "source": "1582", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1858", "source": "1583", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1859", "source": "1583", "target": "1881", "type": "PROCESS_OF" }, { "id": "L1860", "source": "1584", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1861", "source": "1584", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1862", "source": "1585", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1863", "source": "1585", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1864", "source": "1586", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1865", "source": "1586", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1866", "source": "1587", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1867", "source": "1587", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1868", "source": "1588", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1869", "source": "1588", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1870", "source": "1589", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1871", "source": "1589", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1872", "source": "1590", "target": "1573", "type": "PROCESS_OF" }, { "id": "L1873", "source": "1590", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1874", "source": "1594", "target": "1592", "type": "PROCESS_OF" }, { "id": "L1875", "source": "1594", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1876", "source": "1595", "target": "1592", "type": "PROCESS_OF" }, { "id": "L1877", "source": "1595", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1878", "source": "1596", "target": "1592", "type": "PROCESS_OF" }, { "id": "L1879", "source": "1596", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1880", "source": "1597", "target": "1603", "type": "PROCESS_OF" }, { "id": "L1881", "source": "1597", "target": "1592", "type": "PROCESS_OF" }, { "id": "L1882", "source": "1597", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1883", "source": "1598", "target": "1592", "type": "PROCESS_OF" }, { "id": "L1884", "source": "1598", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1885", "source": "1599", "target": "1592", "type": "PROCESS_OF" }, { "id": "L1886", "source": "1599", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1887", "source": "1600", "target": "1592", "type": "PROCESS_OF" }, { "id": "L1888", "source": "1600", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1889", "source": "1601", "target": "1592", "type": "PROCESS_OF" }, { "id": "L1890", "source": "1601", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1891", "source": "1602", "target": "1592", "type": "PROCESS_OF" }, { "id": "L1892", "source": "1602", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1893", "source": "1605", "target": "1603", "type": "PROCESS_OF" }, { "id": "L1894", "source": "1605", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1895", "source": "1606", "target": "1779", "type": "PROCESS_OF" }, { "id": "L1896", "source": "1606", "target": "1775", "type": "PROCESS_OF" }, { "id": "L1897", "source": "1606", "target": "1768", "type": "PROCESS_OF" }, { "id": "L1898", "source": "1606", "target": "1603", "type": "PROCESS_OF" }, { "id": "L1899", "source": "1606", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1900", "source": "1608", "target": "1603", "type": "PROCESS_OF" }, { "id": "L1901", "source": "1608", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1902", "source": "1609", "target": "1603", "type": "PROCESS_OF" }, { "id": "L1903", "source": "1609", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1904", "source": "1611", "target": "1603", "type": "PROCESS_OF" }, { "id": "L1905", "source": "1611", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1906", "source": "1612", "target": "1603", "type": "PROCESS_OF" }, { "id": "L1907", "source": "1612", "target": "1887", "type": "PROCESS_OF" }, { "id": "L1908", "source": "1616", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1909", "source": "1616", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1910", "source": "1617", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1911", "source": "1617", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1912", "source": "1618", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1913", "source": "1618", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1914", "source": "1619", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1915", "source": "1619", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1916", "source": "1620", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1917", "source": "1620", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1918", "source": "1621", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1919", "source": "1621", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1920", "source": "1622", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1921", "source": "1622", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1922", "source": "1623", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1923", "source": "1623", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1924", "source": "1624", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1925", "source": "1624", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1926", "source": "1625", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1927", "source": "1625", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1928", "source": "1626", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1929", "source": "1626", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1930", "source": "1627", "target": "1614", "type": "PROCESS_OF" }, { "id": "L1931", "source": "1627", "target": "1889", "type": "PROCESS_OF" }, { "id": "L1932", "source": "1635", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1933", "source": "1635", "target": "1680", "type": "PROCESS_OF" }, { "id": "L1934", "source": "1635", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1935", "source": "1635", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1936", "source": "1635", "target": "2222", "type": "PROCESS_OF" }, { "id": "L1937", "source": "1637", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1938", "source": "1637", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1939", "source": "1637", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1940", "source": "1637", "target": "2222", "type": "PROCESS_OF" }, { "id": "L1941", "source": "1639", "target": "2088", "type": "PROCESS_OF" }, { "id": "L1942", "source": "1639", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1943", "source": "1639", "target": "1680", "type": "PROCESS_OF" }, { "id": "L1944", "source": "1639", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1945", "source": "1639", "target": "2222", "type": "PROCESS_OF" }, { "id": "L1946", "source": "1641", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1947", "source": "1641", "target": "2213", "type": "PROCESS_OF" }, { "id": "L1948", "source": "1643", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1949", "source": "1643", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1950", "source": "1643", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1951", "source": "1643", "target": "2222", "type": "PROCESS_OF" }, { "id": "L1952", "source": "1645", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1953", "source": "1645", "target": "1680", "type": "PROCESS_OF" }, { "id": "L1954", "source": "1645", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1955", "source": "1645", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1956", "source": "1645", "target": "2222", "type": "PROCESS_OF" }, { "id": "L1957", "source": "1647", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1958", "source": "1647", "target": "1680", "type": "PROCESS_OF" }, { "id": "L1959", "source": "1647", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1960", "source": "1647", "target": "2222", "type": "PROCESS_OF" }, { "id": "L1961", "source": "1649", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1962", "source": "1649", "target": "1680", "type": "PROCESS_OF" }, { "id": "L1963", "source": "1649", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1964", "source": "1649", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1965", "source": "1649", "target": "2222", "type": "PROCESS_OF" }, { "id": "L1966", "source": "1651", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1967", "source": "1651", "target": "2213", "type": "PROCESS_OF" }, { "id": "L1968", "source": "1653", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1969", "source": "1653", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1970", "source": "1653", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1971", "source": "1653", "target": "2222", "type": "PROCESS_OF" }, { "id": "L1972", "source": "1655", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1973", "source": "1655", "target": "1680", "type": "PROCESS_OF" }, { "id": "L1974", "source": "1655", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1975", "source": "1655", "target": "2222", "type": "PROCESS_OF" }, { "id": "L1976", "source": "1657", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1977", "source": "1657", "target": "1680", "type": "PROCESS_OF" }, { "id": "L1978", "source": "1657", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1979", "source": "1657", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1980", "source": "1657", "target": "1891", "type": "PROCESS_OF" }, { "id": "L1981", "source": "1659", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1982", "source": "1659", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1983", "source": "1659", "target": "2222", "type": "PROCESS_OF" }, { "id": "L1984", "source": "1661", "target": "1692", "type": "PROCESS_OF" }, { "id": "L1985", "source": "1661", "target": "1680", "type": "PROCESS_OF" }, { "id": "L1986", "source": "1661", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1987", "source": "1661", "target": "1633", "type": "PROCESS_OF" }, { "id": "L1988", "source": "1661", "target": "2131", "type": "PROCESS_OF" }, { "id": "L1989", "source": "1665", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1990", "source": "1665", "target": "2130", "type": "PROCESS_OF" }, { "id": "L1991", "source": "1667", "target": "8500", "type": "PROCESS_OF" }, { "id": "L1992", "source": "1667", "target": "8501", "type": "PROCESS_OF" }, { "id": "L1993", "source": "1667", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1994", "source": "1667", "target": "2213", "type": "PROCESS_OF" }, { "id": "L1995", "source": "1669", "target": "8501", "type": "PROCESS_OF" }, { "id": "L1996", "source": "1669", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1997", "source": "1669", "target": "2000", "type": "PROCESS_OF" }, { "id": "L1998", "source": "1671", "target": "1663", "type": "PROCESS_OF" }, { "id": "L1999", "source": "1671", "target": "1939", "type": "PROCESS_OF" }, { "id": "L2000", "source": "1673", "target": "1663", "type": "PROCESS_OF" }, { "id": "L2001", "source": "1673", "target": "1950", "type": "PROCESS_OF" }, { "id": "L2002", "source": "1675", "target": "8501", "type": "PROCESS_OF" }, { "id": "L2003", "source": "1675", "target": "1663", "type": "PROCESS_OF" }, { "id": "L2004", "source": "1675", "target": "2124", "type": "PROCESS_OF" }, { "id": "L2005", "source": "1677", "target": "8500", "type": "PROCESS_OF" }, { "id": "L2006", "source": "1677", "target": "8501", "type": "PROCESS_OF" }, { "id": "L2007", "source": "1677", "target": "1663", "type": "PROCESS_OF" }, { "id": "L2008", "source": "1677", "target": "1957", "type": "PROCESS_OF" }, { "id": "L2009", "source": "1682", "target": "1680", "type": "PROCESS_OF" }, { "id": "L2010", "source": "1682", "target": "2222", "type": "PROCESS_OF" }, { "id": "L2011", "source": "1684", "target": "1680", "type": "PROCESS_OF" }, { "id": "L2012", "source": "1684", "target": "2222", "type": "PROCESS_OF" }, { "id": "L2013", "source": "1686", "target": "1787", "type": "PROCESS_OF" }, { "id": "L2014", "source": "1686", "target": "1680", "type": "PROCESS_OF" }, { "id": "L2015", "source": "1688", "target": "1680", "type": "PROCESS_OF" }, { "id": "L2016", "source": "1688", "target": "2222", "type": "PROCESS_OF" }, { "id": "L2017", "source": "1690", "target": "1680", "type": "PROCESS_OF" }, { "id": "L2018", "source": "1690", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2019", "source": "1698", "target": "1696", "type": "PROCESS_OF" }, { "id": "L2020", "source": "1698", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2021", "source": "1700", "target": "8666", "type": "PROCESS_OF" }, { "id": "L2022", "source": "1700", "target": "1779", "type": "PROCESS_OF" }, { "id": "L2023", "source": "1700", "target": "1775", "type": "PROCESS_OF" }, { "id": "L2024", "source": "1700", "target": "1768", "type": "PROCESS_OF" }, { "id": "L2025", "source": "1700", "target": "1761", "type": "PROCESS_OF" }, { "id": "L2026", "source": "1700", "target": "1757", "type": "PROCESS_OF" }, { "id": "L2027", "source": "1700", "target": "1748", "type": "PROCESS_OF" }, { "id": "L2028", "source": "1700", "target": "1746", "type": "PROCESS_OF" }, { "id": "L2029", "source": "1700", "target": "1738", "type": "PROCESS_OF" }, { "id": "L2030", "source": "1700", "target": "1732", "type": "PROCESS_OF" }, { "id": "L2031", "source": "1700", "target": "1710", "type": "PROCESS_OF" }, { "id": "L2032", "source": "1700", "target": "1696", "type": "PROCESS_OF" }, { "id": "L2033", "source": "1700", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2034", "source": "1702", "target": "1696", "type": "PROCESS_OF" }, { "id": "L2035", "source": "1702", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2036", "source": "1704", "target": "8666", "type": "PROCESS_OF" }, { "id": "L2037", "source": "1704", "target": "1779", "type": "PROCESS_OF" }, { "id": "L2038", "source": "1704", "target": "1775", "type": "PROCESS_OF" }, { "id": "L2039", "source": "1704", "target": "1768", "type": "PROCESS_OF" }, { "id": "L2040", "source": "1704", "target": "1761", "type": "PROCESS_OF" }, { "id": "L2041", "source": "1704", "target": "1757", "type": "PROCESS_OF" }, { "id": "L2042", "source": "1704", "target": "1748", "type": "PROCESS_OF" }, { "id": "L2043", "source": "1704", "target": "1746", "type": "PROCESS_OF" }, { "id": "L2044", "source": "1704", "target": "1738", "type": "PROCESS_OF" }, { "id": "L2045", "source": "1704", "target": "1732", "type": "PROCESS_OF" }, { "id": "L2046", "source": "1704", "target": "1724", "type": "PROCESS_OF" }, { "id": "L2047", "source": "1704", "target": "1710", "type": "PROCESS_OF" }, { "id": "L2048", "source": "1704", "target": "1696", "type": "PROCESS_OF" }, { "id": "L2049", "source": "1704", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2050", "source": "1706", "target": "8666", "type": "PROCESS_OF" }, { "id": "L2051", "source": "1706", "target": "1779", "type": "PROCESS_OF" }, { "id": "L2052", "source": "1706", "target": "1775", "type": "PROCESS_OF" }, { "id": "L2053", "source": "1706", "target": "1768", "type": "PROCESS_OF" }, { "id": "L2054", "source": "1706", "target": "1761", "type": "PROCESS_OF" }, { "id": "L2055", "source": "1706", "target": "1757", "type": "PROCESS_OF" }, { "id": "L2056", "source": "1706", "target": "1748", "type": "PROCESS_OF" }, { "id": "L2057", "source": "1706", "target": "1746", "type": "PROCESS_OF" }, { "id": "L2058", "source": "1706", "target": "1732", "type": "PROCESS_OF" }, { "id": "L2059", "source": "1706", "target": "1710", "type": "PROCESS_OF" }, { "id": "L2060", "source": "1706", "target": "1696", "type": "PROCESS_OF" }, { "id": "L2061", "source": "1706", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2062", "source": "1708", "target": "1696", "type": "PROCESS_OF" }, { "id": "L2063", "source": "1708", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2064", "source": "1712", "target": "1748", "type": "PROCESS_OF" }, { "id": "L2065", "source": "1712", "target": "1738", "type": "PROCESS_OF" }, { "id": "L2066", "source": "1712", "target": "1724", "type": "PROCESS_OF" }, { "id": "L2067", "source": "1712", "target": "1710", "type": "PROCESS_OF" }, { "id": "L2068", "source": "1712", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2069", "source": "1714", "target": "1779", "type": "PROCESS_OF" }, { "id": "L2070", "source": "1714", "target": "1775", "type": "PROCESS_OF" }, { "id": "L2071", "source": "1714", "target": "1768", "type": "PROCESS_OF" }, { "id": "L2072", "source": "1714", "target": "1748", "type": "PROCESS_OF" }, { "id": "L2073", "source": "1714", "target": "1724", "type": "PROCESS_OF" }, { "id": "L2074", "source": "1714", "target": "1710", "type": "PROCESS_OF" }, { "id": "L2075", "source": "1714", "target": "2131", "type": "PROCESS_OF" }, { "id": "L2076", "source": "1716", "target": "8666", "type": "PROCESS_OF" }, { "id": "L2077", "source": "1716", "target": "1775", "type": "PROCESS_OF" }, { "id": "L2078", "source": "1716", "target": "1761", "type": "PROCESS_OF" }, { "id": "L2079", "source": "1716", "target": "1757", "type": "PROCESS_OF" }, { "id": "L2080", "source": "1716", "target": "1750", "type": "PROCESS_OF" }, { "id": "L2081", "source": "1716", "target": "1748", "type": "PROCESS_OF" }, { "id": "L2082", "source": "1716", "target": "1746", "type": "PROCESS_OF" }, { "id": "L2083", "source": "1716", "target": "1732", "type": "PROCESS_OF" }, { "id": "L2084", "source": "1716", "target": "1724", "type": "PROCESS_OF" }, { "id": "L2085", "source": "1716", "target": "1710", "type": "PROCESS_OF" }, { "id": "L2086", "source": "1716", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2087", "source": "1718", "target": "1779", "type": "PROCESS_OF" }, { "id": "L2088", "source": "1718", "target": "1768", "type": "PROCESS_OF" }, { "id": "L2089", "source": "1718", "target": "1748", "type": "PROCESS_OF" }, { "id": "L2090", "source": "1718", "target": "1738", "type": "PROCESS_OF" }, { "id": "L2091", "source": "1718", "target": "1724", "type": "PROCESS_OF" }, { "id": "L2092", "source": "1718", "target": "1710", "type": "PROCESS_OF" }, { "id": "L2093", "source": "1718", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2094", "source": "1720", "target": "8666", "type": "PROCESS_OF" }, { "id": "L2095", "source": "1720", "target": "1757", "type": "PROCESS_OF" }, { "id": "L2096", "source": "1720", "target": "1750", "type": "PROCESS_OF" }, { "id": "L2097", "source": "1720", "target": "1748", "type": "PROCESS_OF" }, { "id": "L2098", "source": "1720", "target": "1746", "type": "PROCESS_OF" }, { "id": "L2099", "source": "1720", "target": "1732", "type": "PROCESS_OF" }, { "id": "L2100", "source": "1720", "target": "1724", "type": "PROCESS_OF" }, { "id": "L2101", "source": "1720", "target": "1710", "type": "PROCESS_OF" }, { "id": "L2102", "source": "1720", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2103", "source": "1722", "target": "1779", "type": "PROCESS_OF" }, { "id": "L2104", "source": "1722", "target": "1775", "type": "PROCESS_OF" }, { "id": "L2105", "source": "1722", "target": "1768", "type": "PROCESS_OF" }, { "id": "L2106", "source": "1722", "target": "1757", "type": "PROCESS_OF" }, { "id": "L2107", "source": "1722", "target": "1750", "type": "PROCESS_OF" }, { "id": "L2108", "source": "1722", "target": "1748", "type": "PROCESS_OF" }, { "id": "L2109", "source": "1722", "target": "1746", "type": "PROCESS_OF" }, { "id": "L2110", "source": "1722", "target": "1738", "type": "PROCESS_OF" }, { "id": "L2111", "source": "1722", "target": "1732", "type": "PROCESS_OF" }, { "id": "L2112", "source": "1722", "target": "1724", "type": "PROCESS_OF" }, { "id": "L2113", "source": "1722", "target": "1710", "type": "PROCESS_OF" }, { "id": "L2114", "source": "1722", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2115", "source": "1726", "target": "1724", "type": "PROCESS_OF" }, { "id": "L2116", "source": "1726", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2117", "source": "1728", "target": "1724", "type": "PROCESS_OF" }, { "id": "L2118", "source": "1728", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2119", "source": "1730", "target": "1724", "type": "PROCESS_OF" }, { "id": "L2120", "source": "1730", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2121", "source": "1734", "target": "8666", "type": "PROCESS_OF" }, { "id": "L2122", "source": "1734", "target": "1775", "type": "PROCESS_OF" }, { "id": "L2123", "source": "1734", "target": "1757", "type": "PROCESS_OF" }, { "id": "L2124", "source": "1734", "target": "1746", "type": "PROCESS_OF" }, { "id": "L2125", "source": "1734", "target": "1732", "type": "PROCESS_OF" }, { "id": "L2126", "source": "1734", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2127", "source": "1736", "target": "8666", "type": "PROCESS_OF" }, { "id": "L2128", "source": "1736", "target": "1757", "type": "PROCESS_OF" }, { "id": "L2129", "source": "1736", "target": "1746", "type": "PROCESS_OF" }, { "id": "L2130", "source": "1736", "target": "1732", "type": "PROCESS_OF" }, { "id": "L2131", "source": "1736", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2132", "source": "1740", "target": "1738", "type": "PROCESS_OF" }, { "id": "L2133", "source": "1740", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2134", "source": "1742", "target": "1738", "type": "PROCESS_OF" }, { "id": "L2135", "source": "1742", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2136", "source": "1744", "target": "1738", "type": "PROCESS_OF" }, { "id": "L2137", "source": "1744", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2138", "source": "1752", "target": "1750", "type": "PROCESS_OF" }, { "id": "L2139", "source": "1752", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2140", "source": "1753", "target": "1750", "type": "PROCESS_OF" }, { "id": "L2141", "source": "1753", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2142", "source": "1754", "target": "1750", "type": "PROCESS_OF" }, { "id": "L2143", "source": "1754", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2144", "source": "1759", "target": "8666", "type": "PROCESS_OF" }, { "id": "L2145", "source": "1759", "target": "1757", "type": "PROCESS_OF" }, { "id": "L2146", "source": "1759", "target": "2137", "type": "PROCESS_OF" }, { "id": "L2147", "source": "1763", "target": "1761", "type": "PROCESS_OF" }, { "id": "L2148", "source": "1763", "target": "2137", "type": "PROCESS_OF" }, { "id": "L2149", "source": "1765", "target": "1761", "type": "PROCESS_OF" }, { "id": "L2150", "source": "1765", "target": "2131", "type": "PROCESS_OF" }, { "id": "L2151", "source": "1770", "target": "1768", "type": "PROCESS_OF" }, { "id": "L2152", "source": "1770", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2153", "source": "1772", "target": "1768", "type": "PROCESS_OF" }, { "id": "L2154", "source": "1772", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2155", "source": "1777", "target": "1775", "type": "PROCESS_OF" }, { "id": "L2156", "source": "1777", "target": "2137", "type": "PROCESS_OF" }, { "id": "L2157", "source": "1781", "target": "1779", "type": "PROCESS_OF" }, { "id": "L2158", "source": "1781", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2159", "source": "1783", "target": "1779", "type": "PROCESS_OF" }, { "id": "L2160", "source": "1783", "target": "2217", "type": "PROCESS_OF" }, { "id": "L2161", "source": "1788", "target": "1787", "type": "PROCESS_OF" }, { "id": "L2162", "source": "1791", "target": "1790", "type": "PROCESS_OF" }, { "id": "L2163", "source": "1793", "target": "1792", "type": "PROCESS_OF" }, { "id": "L2164", "source": "1794", "target": "1792", "type": "PROCESS_OF" }, { "id": "L2165", "source": "1798", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2166", "source": "1800", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2167", "source": "1801", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2168", "source": "1802", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2169", "source": "1803", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2170", "source": "1805", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2171", "source": "1806", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2172", "source": "1808", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2173", "source": "1809", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2174", "source": "1810", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2175", "source": "1812", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2176", "source": "1813", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2177", "source": "1814", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2178", "source": "1815", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2179", "source": "1817", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2180", "source": "1818", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2181", "source": "1819", "target": "1797", "type": "PROCESS_OF" }, { "id": "L2182", "source": "1821", "target": "1820", "type": "PROCESS_OF" }, { "id": "L2183", "source": "1823", "target": "1820", "type": "PROCESS_OF" }, { "id": "L2184", "source": "1825", "target": "1820", "type": "PROCESS_OF" }, { "id": "L2185", "source": "1828", "target": "1827", "type": "PROCESS_OF" }, { "id": "L2186", "source": "1830", "target": "1829", "type": "PROCESS_OF" }, { "id": "L2187", "source": "1833", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2188", "source": "1834", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2189", "source": "1835", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2190", "source": "1836", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2191", "source": "1837", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2192", "source": "1838", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2193", "source": "1839", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2194", "source": "1840", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2195", "source": "1841", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2196", "source": "1842", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2197", "source": "1843", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2198", "source": "1844", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2199", "source": "1845", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2200", "source": "1846", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2201", "source": "1847", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2202", "source": "1848", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2203", "source": "1849", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2204", "source": "1850", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2205", "source": "1851", "target": "1832", "type": "PROCESS_OF" }, { "id": "L2206", "source": "1853", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2207", "source": "1854", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2208", "source": "1855", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2209", "source": "1856", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2210", "source": "1857", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2211", "source": "1858", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2212", "source": "1859", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2213", "source": "1860", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2214", "source": "1861", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2215", "source": "1862", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2216", "source": "1863", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2217", "source": "1864", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2218", "source": "1865", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2219", "source": "1866", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2220", "source": "1867", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2221", "source": "1868", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2222", "source": "1869", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2223", "source": "1870", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2224", "source": "1871", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2225", "source": "1872", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2226", "source": "1873", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2227", "source": "1874", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2228", "source": "1875", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2229", "source": "1876", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2230", "source": "1877", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2231", "source": "1878", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2232", "source": "1879", "target": "1852", "type": "PROCESS_OF" }, { "id": "L2233", "source": "1882", "target": "1881", "type": "PROCESS_OF" }, { "id": "L2234", "source": "1883", "target": "1881", "type": "PROCESS_OF" }, { "id": "L2235", "source": "1884", "target": "1881", "type": "PROCESS_OF" }, { "id": "L2236", "source": "1885", "target": "1881", "type": "PROCESS_OF" }, { "id": "L2237", "source": "1886", "target": "1881", "type": "PROCESS_OF" }, { "id": "L2238", "source": "1894", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2239", "source": "1895", "target": "452", "type": "PROCESS_OF" }, { "id": "L2240", "source": "1895", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2241", "source": "1896", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2242", "source": "1897", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2243", "source": "1898", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2244", "source": "1899", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2245", "source": "1900", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2246", "source": "1901", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2247", "source": "1902", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2248", "source": "1903", "target": "603", "type": "PROCESS_OF" }, { "id": "L2249", "source": "1903", "target": "597", "type": "PROCESS_OF" }, { "id": "L2250", "source": "1903", "target": "587", "type": "PROCESS_OF" }, { "id": "L2251", "source": "1903", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2252", "source": "1905", "target": "1904", "type": "PROCESS_OF" }, { "id": "L2253", "source": "1906", "target": "1904", "type": "PROCESS_OF" }, { "id": "L2254", "source": "1908", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2255", "source": "1909", "target": "536", "type": "PROCESS_OF" }, { "id": "L2256", "source": "1909", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2257", "source": "1910", "target": "537", "type": "PROCESS_OF" }, { "id": "L2258", "source": "1910", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2259", "source": "1911", "target": "537", "type": "PROCESS_OF" }, { "id": "L2260", "source": "1911", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2261", "source": "1912", "target": "537", "type": "PROCESS_OF" }, { "id": "L2262", "source": "1912", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2263", "source": "1913", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2264", "source": "1914", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2265", "source": "1915", "target": "537", "type": "PROCESS_OF" }, { "id": "L2266", "source": "1915", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2267", "source": "1916", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2268", "source": "1917", "target": "536", "type": "PROCESS_OF" }, { "id": "L2269", "source": "1917", "target": "8531", "type": "PROCESS_OF" }, { "id": "L2270", "source": "1917", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2271", "source": "1918", "target": "536", "type": "PROCESS_OF" }, { "id": "L2272", "source": "1918", "target": "8531", "type": "PROCESS_OF" }, { "id": "L2273", "source": "1918", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2274", "source": "1919", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2275", "source": "1920", "target": "537", "type": "PROCESS_OF" }, { "id": "L2276", "source": "1920", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2277", "source": "1921", "target": "537", "type": "PROCESS_OF" }, { "id": "L2278", "source": "1921", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2279", "source": "1925", "target": "1924", "type": "PROCESS_OF" }, { "id": "L2280", "source": "1926", "target": "1924", "type": "PROCESS_OF" }, { "id": "L2281", "source": "1931", "target": "1930", "type": "PROCESS_OF" }, { "id": "L2282", "source": "1932", "target": "1930", "type": "PROCESS_OF" }, { "id": "L2283", "source": "1933", "target": "1930", "type": "PROCESS_OF" }, { "id": "L2284", "source": "1934", "target": "1930", "type": "PROCESS_OF" }, { "id": "L2285", "source": "1935", "target": "1930", "type": "PROCESS_OF" }, { "id": "L2286", "source": "1943", "target": "1942", "type": "PROCESS_OF" }, { "id": "L2287", "source": "1945", "target": "1944", "type": "PROCESS_OF" }, { "id": "L2288", "source": "1948", "target": "1947", "type": "PROCESS_OF" }, { "id": "L2289", "source": "1951", "target": "1950", "type": "PROCESS_OF" }, { "id": "L2290", "source": "1953", "target": "1950", "type": "PROCESS_OF" }, { "id": "L2291", "source": "1955", "target": "1950", "type": "PROCESS_OF" }, { "id": "L2292", "source": "1958", "target": "1957", "type": "PROCESS_OF" }, { "id": "L2293", "source": "1959", "target": "1957", "type": "PROCESS_OF" }, { "id": "L2294", "source": "1962", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2295", "source": "1964", "target": "1963", "type": "PROCESS_OF" }, { "id": "L2296", "source": "1965", "target": "1963", "type": "PROCESS_OF" }, { "id": "L2297", "source": "1966", "target": "1963", "type": "PROCESS_OF" }, { "id": "L2298", "source": "1967", "target": "1963", "type": "PROCESS_OF" }, { "id": "L2299", "source": "1968", "target": "1963", "type": "PROCESS_OF" }, { "id": "L2300", "source": "1969", "target": "1963", "type": "PROCESS_OF" }, { "id": "L2301", "source": "1972", "target": "1971", "type": "PROCESS_OF" }, { "id": "L2302", "source": "1974", "target": "1971", "type": "PROCESS_OF" }, { "id": "L2303", "source": "1976", "target": "1971", "type": "PROCESS_OF" }, { "id": "L2304", "source": "1978", "target": "1977", "type": "PROCESS_OF" }, { "id": "L2305", "source": "1979", "target": "1977", "type": "PROCESS_OF" }, { "id": "L2306", "source": "1980", "target": "1977", "type": "PROCESS_OF" }, { "id": "L2307", "source": "1983", "target": "1982", "type": "PROCESS_OF" }, { "id": "L2308", "source": "1984", "target": "1982", "type": "PROCESS_OF" }, { "id": "L2309", "source": "1985", "target": "1982", "type": "PROCESS_OF" }, { "id": "L2310", "source": "1987", "target": "1986", "type": "PROCESS_OF" }, { "id": "L2311", "source": "1990", "target": "1989", "type": "PROCESS_OF" }, { "id": "L2312", "source": "1992", "target": "1989", "type": "PROCESS_OF" }, { "id": "L2313", "source": "1994", "target": "1989", "type": "PROCESS_OF" }, { "id": "L2314", "source": "1996", "target": "1989", "type": "PROCESS_OF" }, { "id": "L2315", "source": "1998", "target": "1989", "type": "PROCESS_OF" }, { "id": "L2316", "source": "2001", "target": "2000", "type": "PROCESS_OF" }, { "id": "L2317", "source": "2004", "target": "2003", "type": "PROCESS_OF" }, { "id": "L2318", "source": "2006", "target": "2003", "type": "PROCESS_OF" }, { "id": "L2319", "source": "2008", "target": "2003", "type": "PROCESS_OF" }, { "id": "L2320", "source": "2009", "target": "2003", "type": "PROCESS_OF" }, { "id": "L2321", "source": "2011", "target": "2003", "type": "PROCESS_OF" }, { "id": "L2322", "source": "2012", "target": "2003", "type": "PROCESS_OF" }, { "id": "L2323", "source": "2014", "target": "2013", "type": "PROCESS_OF" }, { "id": "L2324", "source": "2016", "target": "2013", "type": "PROCESS_OF" }, { "id": "L2325", "source": "2018", "target": "2013", "type": "PROCESS_OF" }, { "id": "L2326", "source": "2021", "target": "2020", "type": "PROCESS_OF" }, { "id": "L2327", "source": "2023", "target": "2020", "type": "PROCESS_OF" }, { "id": "L2328", "source": "2025", "target": "2020", "type": "PROCESS_OF" }, { "id": "L2329", "source": "2027", "target": "2020", "type": "PROCESS_OF" }, { "id": "L2330", "source": "2029", "target": "2020", "type": "PROCESS_OF" }, { "id": "L2331", "source": "2031", "target": "2020", "type": "PROCESS_OF" }, { "id": "L2332", "source": "2033", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2333", "source": "2034", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2334", "source": "2035", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2335", "source": "2038", "target": "2037", "type": "PROCESS_OF" }, { "id": "L2336", "source": "2041", "target": "2040", "type": "PROCESS_OF" }, { "id": "L2337", "source": "2043", "target": "2040", "type": "PROCESS_OF" }, { "id": "L2338", "source": "2045", "target": "2040", "type": "PROCESS_OF" }, { "id": "L2339", "source": "2047", "target": "2040", "type": "PROCESS_OF" }, { "id": "L2340", "source": "2050", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2341", "source": "2052", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2342", "source": "2054", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2343", "source": "2056", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2344", "source": "2058", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2345", "source": "2061", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2346", "source": "2062", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2347", "source": "2064", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2348", "source": "2065", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2349", "source": "2066", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2350", "source": "2067", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2351", "source": "2069", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2352", "source": "2071", "target": "9177", "type": "PROCESS_OF" }, { "id": "L2353", "source": "2073", "target": "9177", "type": "PROCESS_OF" }, { "id": "L2354", "source": "2075", "target": "9176", "type": "PROCESS_OF" }, { "id": "L2355", "source": "2077", "target": "9177", "type": "PROCESS_OF" }, { "id": "L2356", "source": "2079", "target": "9176", "type": "PROCESS_OF" }, { "id": "L2357", "source": "2080", "target": "9205", "type": "PROCESS_OF" }, { "id": "L2358", "source": "2082", "target": "2081", "type": "PROCESS_OF" }, { "id": "L2359", "source": "2084", "target": "2081", "type": "PROCESS_OF" }, { "id": "L2360", "source": "2085", "target": "2081", "type": "PROCESS_OF" }, { "id": "L2361", "source": "2086", "target": "2081", "type": "PROCESS_OF" }, { "id": "L2362", "source": "2087", "target": "2081", "type": "PROCESS_OF" }, { "id": "L2363", "source": "2089", "target": "2088", "type": "PROCESS_OF" }, { "id": "L2364", "source": "2090", "target": "2088", "type": "PROCESS_OF" }, { "id": "L2365", "source": "2091", "target": "2088", "type": "PROCESS_OF" }, { "id": "L2366", "source": "2093", "target": "2092", "type": "PROCESS_OF" }, { "id": "L2367", "source": "2095", "target": "2092", "type": "PROCESS_OF" }, { "id": "L2368", "source": "2097", "target": "2092", "type": "PROCESS_OF" }, { "id": "L2369", "source": "2099", "target": "2092", "type": "PROCESS_OF" }, { "id": "L2370", "source": "2100", "target": "2092", "type": "PROCESS_OF" }, { "id": "L2371", "source": "2103", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2372", "source": "2104", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2373", "source": "2105", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2374", "source": "2106", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2375", "source": "2107", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2376", "source": "2108", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2377", "source": "2109", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2378", "source": "2111", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2379", "source": "2113", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2380", "source": "2114", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2381", "source": "2115", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2382", "source": "2117", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2383", "source": "2118", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2384", "source": "2119", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2385", "source": "2121", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2386", "source": "2122", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2387", "source": "2125", "target": "2124", "type": "PROCESS_OF" }, { "id": "L2388", "source": "2127", "target": "2124", "type": "PROCESS_OF" }, { "id": "L2389", "source": "2134", "target": "2133", "type": "PROCESS_OF" }, { "id": "L2390", "source": "2135", "target": "2133", "type": "PROCESS_OF" }, { "id": "L2391", "source": "2136", "target": "2133", "type": "PROCESS_OF" }, { "id": "L2392", "source": "2138", "target": "2137", "type": "PROCESS_OF" }, { "id": "L2393", "source": "2142", "target": "2141", "type": "PROCESS_OF" }, { "id": "L2394", "source": "2144", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2395", "source": "2145", "target": "270", "type": "PROCESS_OF" }, { "id": "L2396", "source": "2145", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2397", "source": "2146", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2398", "source": "2147", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2399", "source": "2148", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2400", "source": "2149", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2401", "source": "2150", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2402", "source": "2151", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2403", "source": "2152", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2404", "source": "2153", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2405", "source": "2154", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2406", "source": "2155", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2407", "source": "2156", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2408", "source": "2157", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2409", "source": "2158", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2410", "source": "2159", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2411", "source": "2160", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2412", "source": "2161", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2413", "source": "2162", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2414", "source": "2164", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2415", "source": "2165", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2416", "source": "2167", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2417", "source": "2168", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2418", "source": "2169", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2419", "source": "2170", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2420", "source": "2172", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2421", "source": "2174", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2422", "source": "2175", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2423", "source": "2176", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2424", "source": "2177", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2425", "source": "2178", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2426", "source": "2180", "target": "2179", "type": "PROCESS_OF" }, { "id": "L2427", "source": "2181", "target": "2179", "type": "PROCESS_OF" }, { "id": "L2428", "source": "2182", "target": "2179", "type": "PROCESS_OF" }, { "id": "L2429", "source": "2183", "target": "2179", "type": "PROCESS_OF" }, { "id": "L2430", "source": "2184", "target": "2179", "type": "PROCESS_OF" }, { "id": "L2431", "source": "2185", "target": "2179", "type": "PROCESS_OF" }, { "id": "L2432", "source": "2187", "target": "2186", "type": "PROCESS_OF" }, { "id": "L2433", "source": "2188", "target": "2186", "type": "PROCESS_OF" }, { "id": "L2434", "source": "2189", "target": "2186", "type": "PROCESS_OF" }, { "id": "L2435", "source": "2190", "target": "2186", "type": "PROCESS_OF" }, { "id": "L2436", "source": "2191", "target": "2186", "type": "PROCESS_OF" }, { "id": "L2437", "source": "2194", "target": "2193", "type": "PROCESS_OF" }, { "id": "L2438", "source": "2195", "target": "2193", "type": "PROCESS_OF" }, { "id": "L2439", "source": "2196", "target": "2193", "type": "PROCESS_OF" }, { "id": "L2440", "source": "2197", "target": "2193", "type": "PROCESS_OF" }, { "id": "L2441", "source": "2199", "target": "2198", "type": "PROCESS_OF" }, { "id": "L2442", "source": "2200", "target": "2198", "type": "PROCESS_OF" }, { "id": "L2443", "source": "2201", "target": "1829", "type": "PROCESS_OF" }, { "id": "L2444", "source": "2201", "target": "2198", "type": "PROCESS_OF" }, { "id": "L2445", "source": "2204", "target": "2203", "type": "PROCESS_OF" }, { "id": "L2446", "source": "2205", "target": "2203", "type": "PROCESS_OF" }, { "id": "L2447", "source": "2207", "target": "2206", "type": "PROCESS_OF" }, { "id": "L2448", "source": "2211", "target": "2210", "type": "PROCESS_OF" }, { "id": "L2449", "source": "2214", "target": "2213", "type": "PROCESS_OF" }, { "id": "L2450", "source": "2215", "target": "2213", "type": "PROCESS_OF" }, { "id": "L2451", "source": "2216", "target": "2213", "type": "PROCESS_OF" }, { "id": "L2452", "source": "2219", "target": "2218", "type": "PROCESS_OF" }, { "id": "L2453", "source": "2220", "target": "2218", "type": "PROCESS_OF" }, { "id": "L2454", "source": "2221", "target": "2218", "type": "PROCESS_OF" }, { "id": "L2455", "source": "8483", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2456", "source": "8483", "target": "73", "type": "PROCESS_OF" }, { "id": "L2457", "source": "8484", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2458", "source": "8484", "target": "73", "type": "PROCESS_OF" }, { "id": "L2459", "source": "8485", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2460", "source": "8485", "target": "73", "type": "PROCESS_OF" }, { "id": "L2461", "source": "8486", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2462", "source": "8486", "target": "73", "type": "PROCESS_OF" }, { "id": "L2463", "source": "8487", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2464", "source": "8487", "target": "73", "type": "PROCESS_OF" }, { "id": "L2465", "source": "8488", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2466", "source": "8488", "target": "73", "type": "PROCESS_OF" }, { "id": "L2467", "source": "8489", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2468", "source": "8489", "target": "73", "type": "PROCESS_OF" }, { "id": "L2469", "source": "8490", "target": "2060", "type": "PROCESS_OF" }, { "id": "L2470", "source": "8490", "target": "73", "type": "PROCESS_OF" }, { "id": "L2471", "source": "8493", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2472", "source": "8493", "target": "8563", "type": "PROCESS_OF" }, { "id": "L2473", "source": "8493", "target": "8491", "type": "PROCESS_OF" }, { "id": "L2474", "source": "8494", "target": "2088", "type": "PROCESS_OF" }, { "id": "L2475", "source": "8494", "target": "8491", "type": "PROCESS_OF" }, { "id": "L2476", "source": "8495", "target": "2088", "type": "PROCESS_OF" }, { "id": "L2477", "source": "8495", "target": "8491", "type": "PROCESS_OF" }, { "id": "L2478", "source": "8496", "target": "2088", "type": "PROCESS_OF" }, { "id": "L2479", "source": "8496", "target": "8491", "type": "PROCESS_OF" }, { "id": "L2480", "source": "8497", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2481", "source": "8497", "target": "8491", "type": "PROCESS_OF" }, { "id": "L2482", "source": "8498", "target": "2088", "type": "PROCESS_OF" }, { "id": "L2483", "source": "8498", "target": "8491", "type": "PROCESS_OF" }, { "id": "L2484", "source": "8499", "target": "2088", "type": "PROCESS_OF" }, { "id": "L2485", "source": "8499", "target": "8491", "type": "PROCESS_OF" }, { "id": "L2486", "source": "8503", "target": "1950", "type": "PROCESS_OF" }, { "id": "L2487", "source": "8503", "target": "8501", "type": "PROCESS_OF" }, { "id": "L2488", "source": "8504", "target": "2000", "type": "PROCESS_OF" }, { "id": "L2489", "source": "8504", "target": "8501", "type": "PROCESS_OF" }, { "id": "L2490", "source": "8505", "target": "2137", "type": "PROCESS_OF" }, { "id": "L2491", "source": "8505", "target": "8501", "type": "PROCESS_OF" }, { "id": "L2492", "source": "8506", "target": "2213", "type": "PROCESS_OF" }, { "id": "L2493", "source": "8506", "target": "8501", "type": "PROCESS_OF" }, { "id": "L2494", "source": "8513", "target": "8519", "type": "PROCESS_OF" }, { "id": "L2495", "source": "8513", "target": "8518", "type": "PROCESS_OF" }, { "id": "L2496", "source": "8513", "target": "8517", "type": "PROCESS_OF" }, { "id": "L2497", "source": "8513", "target": "1940", "type": "PROCESS_OF" }, { "id": "L2498", "source": "8513", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2499", "source": "8513", "target": "8511", "type": "PROCESS_OF" }, { "id": "L2500", "source": "8514", "target": "1940", "type": "PROCESS_OF" }, { "id": "L2501", "source": "8514", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2502", "source": "8514", "target": "8511", "type": "PROCESS_OF" }, { "id": "L2503", "source": "8515", "target": "8519", "type": "PROCESS_OF" }, { "id": "L2504", "source": "8515", "target": "8518", "type": "PROCESS_OF" }, { "id": "L2505", "source": "8515", "target": "8517", "type": "PROCESS_OF" }, { "id": "L2506", "source": "8515", "target": "1940", "type": "PROCESS_OF" }, { "id": "L2507", "source": "8515", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2508", "source": "8515", "target": "8511", "type": "PROCESS_OF" }, { "id": "L2509", "source": "8516", "target": "8519", "type": "PROCESS_OF" }, { "id": "L2510", "source": "8516", "target": "8518", "type": "PROCESS_OF" }, { "id": "L2511", "source": "8516", "target": "8517", "type": "PROCESS_OF" }, { "id": "L2512", "source": "8516", "target": "1940", "type": "PROCESS_OF" }, { "id": "L2513", "source": "8516", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2514", "source": "8516", "target": "8511", "type": "PROCESS_OF" }, { "id": "L2515", "source": "8520", "target": "1929", "type": "PROCESS_OF" }, { "id": "L2516", "source": "8520", "target": "662", "type": "PROCESS_OF" }, { "id": "L2517", "source": "8520", "target": "493", "type": "PROCESS_OF" }, { "id": "L2518", "source": "8522", "target": "1927", "type": "PROCESS_OF" }, { "id": "L2519", "source": "8522", "target": "516", "type": "PROCESS_OF" }, { "id": "L2520", "source": "8523", "target": "1927", "type": "PROCESS_OF" }, { "id": "L2521", "source": "8523", "target": "516", "type": "PROCESS_OF" }, { "id": "L2522", "source": "8524", "target": "1927", "type": "PROCESS_OF" }, { "id": "L2523", "source": "8524", "target": "517", "type": "PROCESS_OF" }, { "id": "L2524", "source": "8526", "target": "1929", "type": "PROCESS_OF" }, { "id": "L2525", "source": "8526", "target": "535", "type": "PROCESS_OF" }, { "id": "L2526", "source": "8527", "target": "1929", "type": "PROCESS_OF" }, { "id": "L2527", "source": "8527", "target": "535", "type": "PROCESS_OF" }, { "id": "L2528", "source": "8528", "target": "1929", "type": "PROCESS_OF" }, { "id": "L2529", "source": "8528", "target": "535", "type": "PROCESS_OF" }, { "id": "L2530", "source": "8529", "target": "1929", "type": "PROCESS_OF" }, { "id": "L2531", "source": "8529", "target": "535", "type": "PROCESS_OF" }, { "id": "L2532", "source": "8530", "target": "1929", "type": "PROCESS_OF" }, { "id": "L2533", "source": "8530", "target": "535", "type": "PROCESS_OF" }, { "id": "L2534", "source": "8534", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2535", "source": "8534", "target": "536", "type": "PROCESS_OF" }, { "id": "L2536", "source": "8535", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2537", "source": "8535", "target": "536", "type": "PROCESS_OF" }, { "id": "L2538", "source": "8537", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2539", "source": "8537", "target": "537", "type": "PROCESS_OF" }, { "id": "L2540", "source": "8538", "target": "1907", "type": "PROCESS_OF" }, { "id": "L2541", "source": "8538", "target": "537", "type": "PROCESS_OF" }, { "id": "L2542", "source": "8539", "target": "1929", "type": "PROCESS_OF" }, { "id": "L2543", "source": "8539", "target": "662", "type": "PROCESS_OF" }, { "id": "L2544", "source": "8540", "target": "1893", "type": "PROCESS_OF" }, { "id": "L2545", "source": "8540", "target": "670", "type": "PROCESS_OF" }, { "id": "L2546", "source": "8551", "target": "2137", "type": "PROCESS_OF" }, { "id": "L2547", "source": "8551", "target": "1288", "type": "PROCESS_OF" }, { "id": "L2548", "source": "8552", "target": "2124", "type": "PROCESS_OF" }, { "id": "L2549", "source": "8552", "target": "1357", "type": "PROCESS_OF" }, { "id": "L2550", "source": "8553", "target": "2124", "type": "PROCESS_OF" }, { "id": "L2551", "source": "8553", "target": "1357", "type": "PROCESS_OF" }, { "id": "L2552", "source": "8554", "target": "1380", "type": "PROCESS_OF" }, { "id": "L2553", "source": "8555", "target": "2132", "type": "PROCESS_OF" }, { "id": "L2554", "source": "8555", "target": "1380", "type": "PROCESS_OF" }, { "id": "L2555", "source": "8557", "target": "1380", "type": "PROCESS_OF" }, { "id": "L2556", "source": "8558", "target": "1380", "type": "PROCESS_OF" }, { "id": "L2557", "source": "8559", "target": "1380", "type": "PROCESS_OF" }, { "id": "L2558", "source": "8560", "target": "1380", "type": "PROCESS_OF" }, { "id": "L2559", "source": "8566", "target": "1787", "type": "PROCESS_OF" }, { "id": "L2560", "source": "8566", "target": "1542", "type": "PROCESS_OF" }, { "id": "L2561", "source": "8567", "target": "1787", "type": "PROCESS_OF" }, { "id": "L2562", "source": "8567", "target": "1542", "type": "PROCESS_OF" }, { "id": "L2563", "source": "8568", "target": "1787", "type": "PROCESS_OF" }, { "id": "L2564", "source": "8568", "target": "1542", "type": "PROCESS_OF" }, { "id": "L2565", "source": "8569", "target": "1787", "type": "PROCESS_OF" }, { "id": "L2566", "source": "8569", "target": "1542", "type": "PROCESS_OF" }, { "id": "L2567", "source": "8570", "target": "1929", "type": "PROCESS_OF" }, { "id": "L2568", "source": "8571", "target": "2013", "type": "PROCESS_OF" }, { "id": "L2569", "source": "8572", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2570", "source": "8573", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2571", "source": "8574", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2572", "source": "8575", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2573", "source": "8576", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2574", "source": "8577", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2575", "source": "8578", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2576", "source": "8579", "target": "1469", "type": "PROCESS_OF" }, { "id": "L2577", "source": "8579", "target": "2131", "type": "PROCESS_OF" }, { "id": "L2578", "source": "8581", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2579", "source": "8582", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2580", "source": "8583", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2581", "source": "8584", "target": "2163", "type": "PROCESS_OF" }, { "id": "L2582", "source": "8616", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2583", "source": "8616", "target": "27", "type": "PROCESS_OF" }, { "id": "L2584", "source": "8625", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2585", "source": "8625", "target": "51", "type": "PROCESS_OF" }, { "id": "L2586", "source": "8628", "target": "2000", "type": "PROCESS_OF" }, { "id": "L2587", "source": "8628", "target": "8500", "type": "PROCESS_OF" }, { "id": "L2588", "source": "8640", "target": "1957", "type": "PROCESS_OF" }, { "id": "L2589", "source": "8640", "target": "8629", "type": "PROCESS_OF" }, { "id": "L2590", "source": "8643", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2591", "source": "8643", "target": "8629", "type": "PROCESS_OF" }, { "id": "L2592", "source": "8656", "target": "1957", "type": "PROCESS_OF" }, { "id": "L2593", "source": "8656", "target": "8629", "type": "PROCESS_OF" }, { "id": "L2594", "source": "8657", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2595", "source": "8657", "target": "8629", "type": "PROCESS_OF" }, { "id": "L2596", "source": "8658", "target": "1957", "type": "PROCESS_OF" }, { "id": "L2597", "source": "8658", "target": "8629", "type": "PROCESS_OF" }, { "id": "L2598", "source": "8659", "target": "1957", "type": "PROCESS_OF" }, { "id": "L2599", "source": "8659", "target": "8629", "type": "PROCESS_OF" }, { "id": "L2600", "source": "8660", "target": "1957", "type": "PROCESS_OF" }, { "id": "L2601", "source": "8660", "target": "8629", "type": "PROCESS_OF" }, { "id": "L2602", "source": "8662", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2603", "source": "8662", "target": "270", "type": "PROCESS_OF" }, { "id": "L2604", "source": "8663", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2605", "source": "8663", "target": "270", "type": "PROCESS_OF" }, { "id": "L2606", "source": "8664", "target": "405", "type": "PROCESS_OF" }, { "id": "L2607", "source": "8665", "target": "2137", "type": "PROCESS_OF" }, { "id": "L2608", "source": "8665", "target": "471", "type": "PROCESS_OF" }, { "id": "L2609", "source": "8668", "target": "1923", "type": "PROCESS_OF" }, { "id": "L2610", "source": "8668", "target": "643", "type": "PROCESS_OF" }, { "id": "L2611", "source": "8670", "target": "2000", "type": "PROCESS_OF" }, { "id": "L2612", "source": "8670", "target": "713", "type": "PROCESS_OF" }, { "id": "L2613", "source": "8671", "target": "2131", "type": "PROCESS_OF" }, { "id": "L2614", "source": "8671", "target": "1469", "type": "PROCESS_OF" }, { "id": "L2615", "source": "8673", "target": "1928", "type": "PROCESS_OF" }, { "id": "L2616", "source": "8673", "target": "8562", "type": "PROCESS_OF" }, { "id": "L2617", "source": "8674", "target": "1928", "type": "PROCESS_OF" }, { "id": "L2618", "source": "8674", "target": "8562", "type": "PROCESS_OF" }, { "id": "L2619", "source": "8675", "target": "1989", "type": "PROCESS_OF" }, { "id": "L2620", "source": "8676", "target": "1989", "type": "PROCESS_OF" }, { "id": "L2621", "source": "8678", "target": "1989", "type": "PROCESS_OF" }, { "id": "L2622", "source": "8723", "target": "1989", "type": "PROCESS_OF" }, { "id": "L2623", "source": "8724", "target": "2000", "type": "PROCESS_OF" }, { "id": "L2624", "source": "8725", "target": "2000", "type": "PROCESS_OF" }, { "id": "L2625", "source": "8727", "target": "2000", "type": "PROCESS_OF" }, { "id": "L2626", "source": "8728", "target": "2000", "type": "PROCESS_OF" }, { "id": "L2627", "source": "8730", "target": "2013", "type": "PROCESS_OF" }, { "id": "L2628", "source": "8732", "target": "2013", "type": "PROCESS_OF" }, { "id": "L2629", "source": "8759", "target": "2013", "type": "PROCESS_OF" }, { "id": "L2630", "source": "8760", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2631", "source": "8762", "target": "2040", "type": "PROCESS_OF" }, { "id": "L2632", "source": "8764", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2633", "source": "8769", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2634", "source": "8770", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2635", "source": "8770", "target": "8519", "type": "PROCESS_OF" }, { "id": "L2636", "source": "8770", "target": "8518", "type": "PROCESS_OF" }, { "id": "L2637", "source": "8770", "target": "8517", "type": "PROCESS_OF" }, { "id": "L2638", "source": "8770", "target": "8511", "type": "PROCESS_OF" }, { "id": "L2639", "source": "8772", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2640", "source": "8774", "target": "2049", "type": "PROCESS_OF" }, { "id": "L2641", "source": "8776", "target": "2081", "type": "PROCESS_OF" }, { "id": "L2642", "source": "8778", "target": "2081", "type": "PROCESS_OF" }, { "id": "L2643", "source": "8780", "target": "2081", "type": "PROCESS_OF" }, { "id": "L2644", "source": "8784", "target": "2092", "type": "PROCESS_OF" }, { "id": "L2645", "source": "8786", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2646", "source": "8791", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2647", "source": "8793", "target": "2102", "type": "PROCESS_OF" }, { "id": "L2648", "source": "8794", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2649", "source": "8794", "target": "8517", "type": "PROCESS_OF" }, { "id": "L2650", "source": "8795", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2651", "source": "8795", "target": "8517", "type": "PROCESS_OF" }, { "id": "L2652", "source": "8799", "target": "2132", "type": "PROCESS_OF" }, { "id": "L2653", "source": "8801", "target": "2132", "type": "PROCESS_OF" }, { "id": "L2654", "source": "8808", "target": "2143", "type": "PROCESS_OF" }, { "id": "L2655", "source": "8825", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2656", "source": "8825", "target": "8518", "type": "PROCESS_OF" }, { "id": "L2657", "source": "8846", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2658", "source": "8846", "target": "8518", "type": "PROCESS_OF" }, { "id": "L2659", "source": "8857", "target": "2213", "type": "PROCESS_OF" }, { "id": "L2660", "source": "8866", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2661", "source": "8866", "target": "8853", "type": "PROCESS_OF" }, { "id": "L2662", "source": "8867", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2663", "source": "8867", "target": "8853", "type": "PROCESS_OF" }, { "id": "L2664", "source": "8875", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2665", "source": "8875", "target": "8519", "type": "PROCESS_OF" }, { "id": "L2666", "source": "8876", "target": "1938", "type": "PROCESS_OF" }, { "id": "L2667", "source": "8876", "target": "8519", "type": "PROCESS_OF" }, { "id": "L2668", "source": "8890", "target": "1957", "type": "PROCESS_OF" }, { "id": "L2669", "source": "8890", "target": "1475", "type": "PROCESS_OF" }, { "id": "L2670", "source": "8890", "target": "8563", "type": "PROCESS_OF" }, { "id": "L2671", "source": "8890", "target": "392", "type": "PROCESS_OF" }, { "id": "L2672", "source": "8890", "target": "386", "type": "PROCESS_OF" }, { "id": "L2673", "source": "8892", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2674", "source": "8892", "target": "8542", "type": "PROCESS_OF" }, { "id": "L2675", "source": "8896", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2676", "source": "8896", "target": "8542", "type": "PROCESS_OF" }, { "id": "L2677", "source": "8913", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2678", "source": "8913", "target": "8542", "type": "PROCESS_OF" }, { "id": "L2679", "source": "8918", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2680", "source": "8918", "target": "8542", "type": "PROCESS_OF" }, { "id": "L2681", "source": "8920", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2682", "source": "8920", "target": "8542", "type": "PROCESS_OF" }, { "id": "L2683", "source": "8922", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2684", "source": "8922", "target": "8542", "type": "PROCESS_OF" }, { "id": "L2685", "source": "8928", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2686", "source": "8928", "target": "8542", "type": "PROCESS_OF" }, { "id": "L2687", "source": "8929", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2688", "source": "8929", "target": "8543", "type": "PROCESS_OF" }, { "id": "L2689", "source": "8929", "target": "1190", "type": "PROCESS_OF" }, { "id": "L2690", "source": "8931", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2691", "source": "8931", "target": "1190", "type": "PROCESS_OF" }, { "id": "L2692", "source": "8950", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2693", "source": "8950", "target": "8543", "type": "PROCESS_OF" }, { "id": "L2694", "source": "8950", "target": "1190", "type": "PROCESS_OF" }, { "id": "L2695", "source": "8954", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2696", "source": "8954", "target": "1190", "type": "PROCESS_OF" }, { "id": "L2697", "source": "8961", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2698", "source": "8961", "target": "8543", "type": "PROCESS_OF" }, { "id": "L2699", "source": "8961", "target": "1190", "type": "PROCESS_OF" }, { "id": "L2700", "source": "8983", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2701", "source": "8983", "target": "1190", "type": "PROCESS_OF" }, { "id": "L2702", "source": "8985", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2703", "source": "8985", "target": "8543", "type": "PROCESS_OF" }, { "id": "L2704", "source": "8986", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2705", "source": "8986", "target": "8543", "type": "PROCESS_OF" }, { "id": "L2706", "source": "8987", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2707", "source": "8987", "target": "8543", "type": "PROCESS_OF" }, { "id": "L2708", "source": "8988", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2709", "source": "8988", "target": "8543", "type": "PROCESS_OF" }, { "id": "L2710", "source": "8989", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2711", "source": "8989", "target": "8543", "type": "PROCESS_OF" }, { "id": "L2712", "source": "8990", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2713", "source": "8990", "target": "8543", "type": "PROCESS_OF" }, { "id": "L2714", "source": "8993", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2715", "source": "8993", "target": "8548", "type": "PROCESS_OF" }, { "id": "L2716", "source": "8995", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2717", "source": "8995", "target": "8548", "type": "PROCESS_OF" }, { "id": "L2718", "source": "8996", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2719", "source": "8996", "target": "8548", "type": "PROCESS_OF" }, { "id": "L2720", "source": "8998", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2721", "source": "8998", "target": "8548", "type": "PROCESS_OF" }, { "id": "L2722", "source": "9012", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2723", "source": "9012", "target": "8548", "type": "PROCESS_OF" }, { "id": "L2724", "source": "9026", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2725", "source": "9026", "target": "8548", "type": "PROCESS_OF" }, { "id": "L2726", "source": "9038", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2727", "source": "9038", "target": "8548", "type": "PROCESS_OF" }, { "id": "L2728", "source": "9061", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2729", "source": "9061", "target": "8549", "type": "PROCESS_OF" }, { "id": "L2730", "source": "9070", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2731", "source": "9070", "target": "8549", "type": "PROCESS_OF" }, { "id": "L2732", "source": "9078", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2733", "source": "9078", "target": "8549", "type": "PROCESS_OF" }, { "id": "L2734", "source": "9086", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2735", "source": "9086", "target": "1950", "type": "PROCESS_OF" }, { "id": "L2736", "source": "9086", "target": "8549", "type": "PROCESS_OF" }, { "id": "L2737", "source": "9087", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2738", "source": "9087", "target": "8549", "type": "PROCESS_OF" }, { "id": "L2739", "source": "9088", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2740", "source": "9088", "target": "8549", "type": "PROCESS_OF" }, { "id": "L2741", "source": "9096", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2742", "source": "9096", "target": "8550", "type": "PROCESS_OF" }, { "id": "L2743", "source": "9103", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2744", "source": "9103", "target": "8550", "type": "PROCESS_OF" }, { "id": "L2745", "source": "9110", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2746", "source": "9110", "target": "8550", "type": "PROCESS_OF" }, { "id": "L2747", "source": "9122", "target": "1961", "type": "PROCESS_OF" }, { "id": "L2748", "source": "9122", "target": "8550", "type": "PROCESS_OF" }, { "id": "L2749", "source": "9147", "target": "9125", "type": "PROCESS_OF" }, { "id": "L2750", "source": "9164", "target": "2213", "type": "PROCESS_OF" }, { "id": "L2751", "source": "9164", "target": "9125", "type": "PROCESS_OF" }, { "id": "L2752", "source": "9165", "target": "1928", "type": "PROCESS_OF" }, { "id": "L2753", "source": "9165", "target": "2032", "type": "PROCESS_OF" }, { "id": "L2754", "source": "9165", "target": "9125", "type": "PROCESS_OF" }, { "id": "L2755", "source": "9168", "target": "9167", "type": "PROCESS_OF" }, { "id": "L2756", "source": "9169", "target": "9167", "type": "PROCESS_OF" }, { "id": "L2757", "source": "9170", "target": "9167", "type": "PROCESS_OF" }, { "id": "L2758", "source": "9171", "target": "1989", "type": "PROCESS_OF" }, { "id": "L2759", "source": "9172", "target": "2130", "type": "PROCESS_OF" }, { "id": "L2760", "source": "9212", "target": "1957", "type": "PROCESS_OF" }, { "id": "L2761", "source": "9234", "target": "2186", "type": "PROCESS_OF" } ] }