NOTE- This template is part of the paid Data Quality Package- the most comprehensive online data quality management tool-Kit. This page provides a sample view of the usage of this template. For Buying this template and the entire Data Quality Package, please Click Here

Purpose of Data Monitoring Request Form-

Data Monitoring Request form is like a typical change request form, but changed in the context of Data Monitoring. It is a formal request for the Business Systems Analyst and IT specialist to start working on the request.

When is Data Monitoring Request Form used?-

This form is used when a certain level of planning and analysis is done on 'what, why, when' part of data monitoring. This request form is essentially a request to IT to estimate, design, execute the same.

Who uses Data Monitoring Request Form?

This checklist is used by the IT specialist and business analyst linked with Data Monitoring. Occasionally it may also be also referred to by the Data Custodian and Data Steward.

Which are the linked work-tools to Data Monitoring Request Form?

• Data Monitoring Check-list**: This checklist is used to track the quality of DM process.
• Data Monitoring Planning Tool**: This tool is used to consciously plan for Data Monitoring. The output of this tool is used to create data monitoring request form.

HELP GUIDE

Back-Ground and Description

• Back-Ground: Provide the details on what is triggering this request. The reasons can be:
  • Data Quality Issues
  • Some recent major changes in the production systems.
  • Pro-active DM for critical financial data
  • Regulatory or compliance requirement
  • Response to Audit comments.
• Business Impact: This provides the business impact linked to data monitoring. It talks about-
  • The benefits, loss or risk to business if this DM is not done.
  • The importance of the data linked to data monitoring.
• Data to be monitored: List not only the data group to be monitored, but also what exactly we want to monitor. This includes:
  • System where the data resides.
  • Data Tables and the fields with in them to be monitored.
  • When the data needs to be monitored (for example after a certain batch has run or a certain interface file is uploaded into the system.
• Frequency of Monitoring: Daily, weekly, real-time

• Online v/s Offline: When we say offline, it means that monitoring can be done on the replica of production systems in the offline mode.

• Alerts Required: This asks for the details on what alerts at what kind of deviation.

• Data Monitoring Report Format: Attach the format if required

• Priority: High/Medium or Low Priority

Estimation and Impact Analysis

• Estimation of Effort: Small /Medium/Large

• Impact of Monitoring: System overload

• Cross-Function Impact Analysis: This is some level of analysis for DM request. For example, if DM request is for monitoring invoice data from raising an invoice to acceptance down to receiving the payment against the invoice, the results may need to be verified across the accounts payables, order-fulfillment and accounting function. Therefore, one may realize that one is talking about wider range of systems and people, who need to be involved.

• To be Included in Release: This states the release this DM will be included in. Sometime DM request may be executed on ad-hoc basis.

Approvals

Approved by BSA of function: The DM needs to be approved by the Business Systems Analyst of the requester function. Business systems analyst is the interface between Business and IT, and is typically a techno-business profile.

• Head of Technology: CIO or someone in his management team may sign-off.
• Head of requester function: The business function who has raised the request.