Read Aloud the Text Content

This audio was created by Woord's Text to Speech service by content creators from all around the world.

Text Content or SSML code:

Hello Everyone, SSDs are Standard Supporting document. These are additional documents that aid in the execution of specific process steps. for example, Templates/ Tracker, Letters templates, Guides, Policy or Job Aids or Work Instructions and Watchouts. Process to Identify Standard Supporting documents. Chapter 3 consist of Process Inputs which are Static Input, Variable Input and System Access. Static Input: • All the SSDs pertaining to the entire process are housed here along with their description. • Mention all the SSDs in collapsible and expandable pattern under the respective Country/ Region or Cluster. • Static Inputs can be a Form, Tracker, Matrix, Template, Guidelines, Checklist, or watchout etc. • Static Inputs mentioned here, should also be mentioned in the applicable steps under - “Summary of SSDs for the Step(s):”. Variable Inputs: • All variable inputs before/during the process should be captured (ServiceNOW Ticket, Signatures, approvals or request received through various medium like email/Fax/ Call, etc.). • Inputs captured in the Process map which trigger the start of the process shall also be mentioned here. System Access: • All the systems involved in the process should be mentioned here along with their Job Aids. Example: Case Management tool Guideline, Workday Guidelines or Job Aids. • Training document related to the system should be linked in this section. Policies: Policies are captured in Chapter 10 of the S.O.P. • Policies and Rules provides guidance in the execution of the process step uniformly. • Mondelez Record Retention Policy and Mondelez Corporate Policy is a Global document, and it is a mandatory policy which is required to be linked in all the S.O.P. • Required Policies should also be linked in the applicable steps under, “Summary of SSDs for the Step(s):”. Raacaaf: Raacaaf is a Risk and Controls Framework. • It is captured in the Chapter 2 of the S.O.P and provides access to the process specific RaaCaaF document for a detailed understanding of all control points and control point accountabilities. • It captures all the Risk like Operational or Financial Risk which are identified in the specific process. • All control points are called out as part of the process step where they require review. • Process Controls signify the mitigation actions that need to be taken to keep the process functioning by addressing risks for process steps. Process Performance parameters – SLA/ KPI: • Chapter 5 of the S.O.P provides access to the specific SLAs and KPIs, important for the performance of this process. • Very high level Key Performance Indicators or Business Outcome Indicators at Level 1 by which the performance of the Process is determined. • SLA’s are agreements with internal or external customers that set the expected delivery norms for the particular process step. • It is a Global document and Process Owner cannot make changes to these documents. Contact Information for systems/ applications, process, and escalation: • Chapter 6 of the S.O.P provides access to important contacts in case there are issues with the process or system/ application. • These are Global document and necessary approval is required for making any changes in the document. Definitions and Appendix: • Chapter 7 of the S.O.P provides additional information on definitions and acronyms used. • Ensure that link in this chapter has been updated with additional information on definitions and acronyms. Record Retention: • Chapter 8 of the S.O.P consist of Mondelez Global Record Retention Policy. It is mandatory document which is required to linked in all the S.O.P. File naming Conventions: This will help you in naming S.O.P, SSD and PM correctly as per the naming Convention. Process to Identify – Standard Supporting Documents: 1. Referring and tracking of information: • Refer process maps and Process collation template to have complete understanding of related information or documents that are required. • Save all documents in personal folder. • If the documents are not ready or work in progress, still you may go ahead and mark the document name in Red as placeholder in the S.O.P, this could be replaced once documents are finalized. 2. Update document Tracker: • Create a ‘final list’ of all applicable documents/info in the document tracker. • Rename the files as per convention (use “Column G” of auto naming within Documents tracker). • Update the document tracker as new documents are getting discovered and rename files. 3. Upload / reload of documents: • To upload new document or replace existing document with the updated one, raise an Oreo Change Request • Once the requested document is approved and uploaded in the Knowledge base, document should be linked in the S.O.P • Once the work in progress SSD is finalized, raise an Oreo request for the same and make sure that the respective SSDs linked in the S.O.P (Marked in red as placeholder) Points to Remember: • Naming convention of the document must be checked while raising an Oreo request. • The naming convention helps in navigating to the correct folder in SharePoint. • If the document is uploaded to the wrong folder, the document link in the S.O.P will break. • Name of the document should be preferably in English so that it is easier to understand. • Naming convention for SSD should be “SSD_L2 process_Process Name_Region/ Country/ Cluster”. • Version numbers and dates should not be written in the naming convention. • If you receive word document is in.xml format, it should be converted to dot D O C X. • Subfolders increase the risk of the same document being duplicated in multiple subfolders; therefore, subfolders should not be created.