US8504412B1 - Audit automation with survey and test plan - Google Patents
Audit automation with survey and test plan Download PDFInfo
- Publication number
- US8504412B1 US8504412B1 US13/472,153 US201213472153A US8504412B1 US 8504412 B1 US8504412 B1 US 8504412B1 US 201213472153 A US201213472153 A US 201213472153A US 8504412 B1 US8504412 B1 US 8504412B1
- Authority
- US
- United States
- Prior art keywords
- audit
- task
- template
- surveys
- survey
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
Definitions
- Audits are common activities in an organization, such as a business enterprise. Audits cover a broad range of practices in the organization, including financial audits, operational systems audits, manufacturing audits, compliance audits, information systems audits, and so on. There are many goals of an audit: add credibility to the financial health of an organization, assure customers of the quality of the goods or services provided by an organization, assure governmental and other regulatory agencies that the organization is in compliance and applicable laws and regulations, and so on. Accordingly, it is important that the quality and reliability of an audit is high.
- Auditors need to perform several tasks during execution of an audit. Among these tasks, auditors need to send out surveys and control test plans to ensure compliance with rules and regulations that are applicable to the business. Results and responses from the surveys and test plans need to be collected, organized, and then analyzed. In a large organization having many employees and many groups, and having many applicable rules and regulations, the auditing effort can be tremendous. Errors may occur in the distribution of surveys and test plans, and in the collection of results from those surveys and test plans.
- FIG. 1 is a system level diagram of a system in accordance with the present disclosure.
- FIG. 2 is a process flow for designing an audits for an organization in accordance with the present disclosure.
- FIG. 3 is a process flow for executing audits.
- FIG. 4 is a high level system diagram of an audit server in accordance with the present disclosure.
- FIG. 1 shows an audit management system 100 for an organization according to principles of the present disclosure.
- the audit management system 100 may include an audit server 102 and several data stores 104 , 106 , 108 , and 110 to support the audit server.
- the data stores 104 - 110 may be implemented as one or more physical storage systems.
- the data stores 106 and 108 may be collectively referred to as a repository of audit surveys (hereinafter “surveys”) and audit test plans (hereinafter “test plans”).
- An audit templates data store 104 may store “audit templates” and their constituent “audit tasks”. As will be explained below, audit templates can automate and facilitate the organization's audit processing activities.
- a survey data store 106 may contain audit surveys (e.g., 106 a , 106 b , 106 c ) that can be used to collect data from people and/or departments within the organization in connection with the organization's audit processing activities.
- a test plan data store 108 may contain control test plans (e.g., 108 a , 108 b ) to be performed by people and/or departments in connection with the organization's audit processing activities.
- An audit issues data store 110 may be provided to store issues identified during an audit. The audit management system 100 may resolve audit issues identified during an audit.
- an audit template 122 comprises one or more audit tasks 124 .
- Each audit task 124 is associated with one or more surveys from the survey database 106 and/or one or more test plans from the test plan database 108 .
- an audit may be performed when an executer accesses a suitable audit template 122 and provides instantiating information to the audit template.
- the instantiating information comprises specific information (e.g., timelines, schedules, places, people, etc.) for an audit template and its audit tasks, thus creating an instance of an audit 122 ′ to be performed.
- Instances of audit tasks 124 ′ may be created by the instantiating information related to the audit tasks and retrieving surveys ( 106 a - 106 c ) and test plans ( 108 a - 108 b ) from the respective data stores 106 and 108 .
- the designer and the executer may be the same person, and in other embodiments may be different people.
- the audit server 102 may provide services that allow a designer, in a step 202 , to develop audit surveys and develop control test plans for assessing conformance to rules and regulations applicable to the organization.
- Audit surveys created by the designer may be stored in a data store (e.g., 106 ) containing a plurality of previously defined audit surveys and, likewise, test plans developed by the designer may be stored in a data store (e.g., 108 ) containing a plurality of previously defined test plans.
- Audit surveys may be used to gather information from people in the organization pertaining to the organization's audit processing activities.
- a survey may be formulated as a questionnaire, or a multiple choice questionnaire, fill in the blanks, short answers, and so on.
- a survey may be completed by a single person, or may be completed by a group of people.
- Test plans typically specify some sequence of activities to be performed by an individual or a group in connection with establishing conformance with applicable rules and regulations.
- a test plan may be modeled as a workflow, comprising different parts that can be sent to different people or groups to perform different activities.
- a test plan may set forth multiple test steps that need to be performed. There may be instructions that explain how to perform a given step.
- the test plan may specify data samples that need to be collected; e.g., measurements of carbon dioxide emissions from a processing station, or pollutant levels at a discharge pump in a recycling center, and so on.
- the surveys and test plans may be catalogued in their respective data stores 106 , 108 in any of several ways in order to facilitate identifying and accessing surveys and test plans for a given audit situation. For example, suppose a survey or test plan is designed to assess conformance to some rule or regulation. The survey or test plan may therefore be indexed according to its applicable rule or regulation. Of course, it will be appreciated that the survey or test plan may be indexed or otherwise catalogued according to any other suitable criteria. In this way, the designer has at their disposal a library of predefined surveys and test plans that they can search to facilitate their effort in designing an audit template. If a suitable survey or test plan has already been designed and developed, then the designer can use it.
- the designer may modify an existing survey or test plan, thus creating a new survey or test plan that can be added to the data store 106 (surveys) or data store 108 (test plans). Or, the designer may create a completely new survey or test plan that can be added to the data store 106 (surveys) or data store 108 (test plans). And so on.
- the audit server 102 may facilitate the design of an audit.
- a designer e.g., FIG. 1
- the designer may develop an “audit template” (e.g., 122 ).
- the audit template represents a general process for performing the particular audit, but omits the specifics.
- the audit template for a given audit may designate that the department manager is the contact person for the audit proceeding, but will omit the manager's name.
- the audit template may generally designate people, times, and places, information about specific people, times, and places may be left un-specified.
- the designer may build an audit template from scratch, or the designer may search the audit template data store 104 to obtain a predefined audit template and modify or otherwise customize the predefined audit template for their specific auditing needs.
- the developed audit template may then be stored to the audit template data store 104 , thus increasing the repository of predefined audit templates that are available to the organization, allowing for the re-use of audit templates.
- the audit templates stored in the audit template data store 104 may be indexed based the rules or regulations they are intended to assess the organization's conformance for, in order to facilitate searching the audit template data store. More generally, the stored audit templates may be indexed or otherwise catalogued based on any other criteria that may be helpful to identify relevant audits.
- An audit proceeding can be a complex process. Accordingly, the designer may break down the audit proceeding into manageable pieces referred to as “audit tasks.” The designer may define each audit task to be an independent unit, so that it can be performed independently of other audit tasks of the audit. The designer may define one or more audit tasks (e.g., 124 ) which comprise the audit template. The audit tasks in an audit template may contain certain information that is left un-specified such as specific participants, completion dates, and so on.
- the audit template data store 104 may also include a repository of predefined audit tasks as building blocks for designing audit templates. Audit tasks designed for one audit template may be re-usable in another audit template. Accordingly, the designer may develop their own audit tasks when building an audit template, or they may search the audit template data store 104 of predefined audit tasks to incorporate into their audit template. Any newly created audit tasks may be stored in the audit template data store 104 to increase the repository of predefined audit tasks that designers may choose when designing new audit templates.
- the designer may associate one or more surveys or test plans with each audit task of the audit template. For example, the designer may search or otherwise browse the repository of surveys and repository of test plans in order to identify suitable surveys or test plans for the given audit task.
- the audit task may simply store references or links to identified surveys or test plans, rather than storing copies of the actual documents corresponding to the surveys or test plans. If the designer does not find a suitable survey or test plan, they may need to design a new survey or test plan. Accordingly, as indicated in the process flow, there may be some iteration between steps 206 and the survey and test plan design step 202 .
- the audit server 102 coordinates activities relating to the execution of an audit proceeding.
- the audit template facilitates the automated initiation and execution of an audit proceeding.
- FIG. 3 illustrates a process flow for automated handling of an audit proceeding in accordance with principles of the present disclosure.
- An executer e.g., FIG. 1
- the executer may instantiate (steps 302 and 304 ) an audit to be performed.
- the executer may begin the process by selecting an audit template (e.g., 122 , FIG. 1 ) from the audit template data store 104 that is suitable for the audit proceeding.
- the audit templates may be indexed or other catalogued in order to facilitate searching for a suitable audit template.
- the audit server 102 may provide a suitable interface and/or search engine that the executer can use to search the audit template data store 104 .
- the audit server 102 may automatically process each audit task comprising the selected audit template including retrieving the surveys or test plans identified in the audit tasks. As explained above, each audit task identifies the surveys or test plans needed to perform the specific task. In step 302 , the audit server 102 may retrieve copies of the actual documents that correspond to the surveys or test plans associated with each audit task, thus creating from the audit template a specific instance of the audit (e.g., 122 ′, FIG. 1 ) to be performed.
- a specific instance of the audit e.g., 122 ′, FIG. 1
- the executer may identify specific people, times, and places called for in the audit template and fill in the un-specified details in the audit template to further instantiate the audit to be performed. For example, the executer may identify recipients of the surveys and test plans associated with the audit tasks that comprise the audit.
- the processing of step 304 may be largely automated by the audit server 102 .
- the audit server 102 may identify the needed information using the audit template and providing that information to instantiate the audit.
- the audit template may include or otherwise be associated with metadata that the audit server 102 can read.
- the metadata may identify various actors in the audit by their roles in the organization. For example, there may be metadata in the audit template that indicates “Manager of Manufacturing”.
- the audit server 102 may read in that metadata and can identify the manager, for example, by accessing the organization's personnel database. It can be understood therefore that the metadata may be used to guide the audit server 102 in generating the specific information needed to instantiate the audit.
- the results produced by the audit server 102 may be subject to review by the executer or other actual person, for example, for to verify the accuracy and propriety of the choices made by the audit server.
- the executer may initiate automated execution of the audit process by the audit server 102 .
- the audit server 102 may conduct the audit proceeding by sending out the survey documents and test plan documents to the recipients identified in step 304 .
- the audit server 102 may send emails to the recipients and include the documents as attachments in the emails.
- the audit server 102 may deliver the surveys and test plans to respective recipients in any suitable manner such as by mailing the surveys or test plans to the recipient, signaling people in the Office Services department to deliver the materials, and so on.
- the surveys and test plans in an instantiated audit task may be sent to one or more recipients.
- an audit task instance 124 ′ comprising survey S 1 and survey S 2 is handled by two recipients, A and B.
- the audit task instance comprising survey S 3 and test plan TP 1 is handle by a single recipient C.
- the audit task instance comprising only test plan TP 2 is also handled by a single recipient D. It can be appreciated of course that other combinations of audit tasks/recipients are possible.
- the audit server 102 may monitor the progress of the audit proceeding.
- responses to the surveys and test plans may be communicated to the audit server 102 .
- Surveys typically require responses from the recipients.
- Responses may be written down or otherwise indicated on the survey documents themselves.
- Recipients may scan the responses (e.g., into a PDF document) and email the responses as an attachment to an email address that the audit server 102 monitors.
- Recipients may simply return the physical documents (e.g., by interoffice mail), where a processing person may then scan it into the audit server 102 .
- Responses to a test plan may include the recording of information obtained during the processing of the test plan. If no data is gathered, a signature or some form or express indication that the test plan was performed may be provided by the recipient of the test plan, their manager, etc., indicating that the test plan was executed.
- the audit tasks comprising an audit may be conducted independently of each other.
- the audit server 102 may track the progress of each audit task as results from completed surveys and test plans are received. When all the surveys and test plans for a given audit task have been received, the audit server 102 may indicate the given audit task as having been completed. In some embodiments, if a completed survey or test plan for an audit task has not been received after a given period of time, the audit server 102 may make note of the fact and designate the missing survey or test plan as having been “constructively” received for the purpose of tracking when the completion status of the audit task. Similarly, the audit server 102 may receive an partially completed survey or test plan.
- the audit server 102 may then allow for a certain period of time to during which to receive the remaining portion of the survey or test plan. After passage of that certain period of time, the audit management system may consider the partially completed survey or test plan to be complete for the purpose of tracking the completion status of the audit task.
- the audit server 102 may analyze the results of the audit. For example, the responses given to the surveys and test plans may be reviewed.
- audit issues may be identified among the responses.
- various remediation workflows may be triggered based on the audit issues identified in step 312 .
- the remediation workflows may be assigned to be performed by appropriate people in the organization. Results from the remediation workflow may be reviewed and the process may continue until the audit issues have been resolved. In some embodiments, these steps may be automated by the audit server 102 .
- a system for automated processing of an audit proceeding is disclosed in commonly owned U.S. Application No. 13/453,187, filed Apr. 23, 2012, entitled “P ATTERN B ASED A UDIT I SSUE R EPORTING” . It will be appreciated of course that any other audit issue handling methodology or system may be used.
- FIG. 4 A particular embodiment of the audit server 102 in accordance with the present disclosure is illustrated in FIG. 4 , showing a high level block diagram of a computer system 402 configured to operate in accordance with the present disclosure.
- the computer system 402 may include a central processing unit (CPU) or other similar data processing component.
- the computer system 402 may include various memory components.
- the memory components may include a volatile memory 414 (e.g., random access memory, RAM) and a data storage device 416 .
- a communication interface 418 may be provided to allow the computer system 402 to communicate over a communication network 422 , such as a local area network (LAN), the Internet, and so on.
- An internal bus 420 may interconnect the components comprising the computer system 402 .
- the data storage device 416 may comprise a non-transitory computer readable medium having stored thereon computer executable program code 432 .
- the computer executable program code 432 may be executed by the CPU 412 to cause the CPU to perform steps of the present disclosure, for example the steps set forth in FIGS. 2 and 3 .
- the data storage device 416 may store data structures 434 such as object instance data, runtime objects, and any other data described herein.
- the data structures 434 may include audit templates, audit tasks, surveys, test plans, and so on.
- a user may interact with the computer system 402 using suitable user interface devices 442 .
- They may include, for example, input devices such as a keyboard, a keypad, a mouse or other pointing device, and output devices such as a display.
- All systems and processes discussed herein may be embodied in program code stored on one or more non-transitory computer-readable media.
- Such media may include, for example, a floppy disk, a CD-ROM, a DVD-ROM, a Flash drive, magnetic tape, and solid state Random Access Memory (RAM) or Read Only Memory (ROM) storage units. It will be appreciated that embodiments are not limited to any specific combination of hardware and software.
- Elements described herein as communicating with one another are directly or indirectly capable of communicating over any number of different systems for transferring data, including but not limited to shared memory communication, a local area network, a wide area network, a telephone network, a cellular network, a fiber-optic network, a satellite network, an infrared network, a radio frequency network, and any other type of network that may be used to transmit information between devices.
- communication between systems may proceed over any one or more transmission protocols that are or become known, such as Asynchronous Transfer Mode (ATM), Internet Protocol (IP), Hypertext Transfer Protocol (HTTP) and Wireless Application Protocol (WAP).
- ATM Asynchronous Transfer Mode
- IP Internet Protocol
- HTTP Hypertext Transfer Protocol
- WAP Wireless Application Protocol
- the foregoing has disclosed an automatic execution of surveys and control test plans during for an audit proceeding, and to consolidate the results for audit issue creation. Users can re-use the surveys and control test plans defined by internal control departments within the organization. Audit tasks may be mapped to surveys and test plan data. Audit templates support automated audit execution at runtime. Audit issue detection and issue remediation workflow are facilitated. Embodiments in accordance with the present disclosure can greatly simplify the tasks auditors need to perform during an audit execution and reduce the manual efforts for auditors. Embodiments can greatly improve the accuracy and the quality of the audit process.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/472,153 US8504412B1 (en) | 2012-05-15 | 2012-05-15 | Audit automation with survey and test plan |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/472,153 US8504412B1 (en) | 2012-05-15 | 2012-05-15 | Audit automation with survey and test plan |
Publications (1)
Publication Number | Publication Date |
---|---|
US8504412B1 true US8504412B1 (en) | 2013-08-06 |
Family
ID=48876468
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/472,153 Active US8504412B1 (en) | 2012-05-15 | 2012-05-15 | Audit automation with survey and test plan |
Country Status (1)
Country | Link |
---|---|
US (1) | US8504412B1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109408326A (en) * | 2018-09-30 | 2019-03-01 | 福建星瑞格软件有限公司 | The method and system of monitoring data library security audit product treatment SQL message efficiency |
US10963796B1 (en) * | 2016-10-07 | 2021-03-30 | Jpmorgan Chase Bank, N.A. | System and method for implementing an assessment tool |
JP2022115543A (en) * | 2021-01-28 | 2022-08-09 | 社会保険労務士法人みらいコンサルティング | Monitoring support device and monitoring support method |
CN116112196A (en) * | 2022-10-31 | 2023-05-12 | 支付宝(杭州)信息技术有限公司 | Professional identity authentication method, device, electronic equipment, medium and program product |
Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050131781A1 (en) * | 2003-12-10 | 2005-06-16 | Ford Motor Company | System and method for auditing |
US20050131784A1 (en) * | 2000-10-13 | 2005-06-16 | Jeffrey Mamorsky | Audit system and method |
US6912502B1 (en) * | 1999-12-30 | 2005-06-28 | Genworth Financial, Inc., | System and method for compliance management |
US20060089861A1 (en) * | 2004-10-22 | 2006-04-27 | Oracle International Corporation | Survey based risk assessment for processes, entities and enterprise |
US20060106686A1 (en) * | 2004-11-12 | 2006-05-18 | Oracle International Corporation | Audit procedures and audit steps |
US20060241991A1 (en) * | 2005-04-25 | 2006-10-26 | Orcale International Corporation | Internal audit operations for sarbanes oxley compliance |
US20060242261A1 (en) * | 2005-04-21 | 2006-10-26 | Piot Jon C | System and method for information technology assessment |
US20060282276A1 (en) * | 2005-06-09 | 2006-12-14 | Venzon Laurie A | Method and system for determining effectiveness of a compliance program |
US20070156495A1 (en) * | 2006-01-05 | 2007-07-05 | Oracle International Corporation | Audit planning |
US20070180490A1 (en) * | 2004-05-20 | 2007-08-02 | Renzi Silvio J | System and method for policy management |
US20080195436A1 (en) * | 2006-12-21 | 2008-08-14 | Stephen Joseph Whyte | Automated supplier self audit questionnaire system |
US7818192B2 (en) * | 2003-02-28 | 2010-10-19 | Omnex Systems L.L.C. | Quality information management system |
US20110251930A1 (en) * | 2010-04-07 | 2011-10-13 | Sap Ag | Data management for top-down risk based audit approach |
US20120016802A1 (en) * | 2010-07-16 | 2012-01-19 | Sap Ag | Automatic event management for regulation compliance |
US20120254048A1 (en) * | 2011-03-30 | 2012-10-04 | Chemsecure Llc | System and method for regulatory security compliance management |
US20120310850A1 (en) * | 2010-07-16 | 2012-12-06 | Sap Ag | Method and System for Evaluating Events |
-
2012
- 2012-05-15 US US13/472,153 patent/US8504412B1/en active Active
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6912502B1 (en) * | 1999-12-30 | 2005-06-28 | Genworth Financial, Inc., | System and method for compliance management |
US20050131784A1 (en) * | 2000-10-13 | 2005-06-16 | Jeffrey Mamorsky | Audit system and method |
US7818192B2 (en) * | 2003-02-28 | 2010-10-19 | Omnex Systems L.L.C. | Quality information management system |
US20050131781A1 (en) * | 2003-12-10 | 2005-06-16 | Ford Motor Company | System and method for auditing |
US20070180490A1 (en) * | 2004-05-20 | 2007-08-02 | Renzi Silvio J | System and method for policy management |
US20060089861A1 (en) * | 2004-10-22 | 2006-04-27 | Oracle International Corporation | Survey based risk assessment for processes, entities and enterprise |
US20060106686A1 (en) * | 2004-11-12 | 2006-05-18 | Oracle International Corporation | Audit procedures and audit steps |
US20060242261A1 (en) * | 2005-04-21 | 2006-10-26 | Piot Jon C | System and method for information technology assessment |
US20060241991A1 (en) * | 2005-04-25 | 2006-10-26 | Orcale International Corporation | Internal audit operations for sarbanes oxley compliance |
US20060282276A1 (en) * | 2005-06-09 | 2006-12-14 | Venzon Laurie A | Method and system for determining effectiveness of a compliance program |
US20070156495A1 (en) * | 2006-01-05 | 2007-07-05 | Oracle International Corporation | Audit planning |
US20080195436A1 (en) * | 2006-12-21 | 2008-08-14 | Stephen Joseph Whyte | Automated supplier self audit questionnaire system |
US20110251930A1 (en) * | 2010-04-07 | 2011-10-13 | Sap Ag | Data management for top-down risk based audit approach |
US20120016802A1 (en) * | 2010-07-16 | 2012-01-19 | Sap Ag | Automatic event management for regulation compliance |
US20120310850A1 (en) * | 2010-07-16 | 2012-12-06 | Sap Ag | Method and System for Evaluating Events |
US20120254048A1 (en) * | 2011-03-30 | 2012-10-04 | Chemsecure Llc | System and method for regulatory security compliance management |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10963796B1 (en) * | 2016-10-07 | 2021-03-30 | Jpmorgan Chase Bank, N.A. | System and method for implementing an assessment tool |
US11823071B2 (en) | 2016-10-07 | 2023-11-21 | Jpmorgan Chase Bank, N.A. | System and method for implementing an assessment tool for converting a regulation into a series of questions |
CN109408326A (en) * | 2018-09-30 | 2019-03-01 | 福建星瑞格软件有限公司 | The method and system of monitoring data library security audit product treatment SQL message efficiency |
JP2022115543A (en) * | 2021-01-28 | 2022-08-09 | 社会保険労務士法人みらいコンサルティング | Monitoring support device and monitoring support method |
JP7127166B2 (en) | 2021-01-28 | 2022-08-29 | 社会保険労務士法人みらいコンサルティング | Audit support device and audit support method |
CN116112196A (en) * | 2022-10-31 | 2023-05-12 | 支付宝(杭州)信息技术有限公司 | Professional identity authentication method, device, electronic equipment, medium and program product |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11341439B2 (en) | Artificial intelligence and machine learning based product development | |
US20170213169A1 (en) | Social networking system for organization management | |
US8499300B2 (en) | System and method for task management of rule based tasks | |
Baškarada et al. | A critical success factor framework for information quality management | |
US20170316080A1 (en) | Automatically generated employee profiles | |
Fikri Mohamed et al. | Potential for improving site management practices through knowledge management | |
Talla et al. | An implementation of ITIL guidelines for IT support process in a service organization | |
US8645180B1 (en) | Automated impact assessment and updates of compliance response plans pursuant to policy changes | |
Lock et al. | Modelling and analysis of socio-technical system of systems | |
Montgomery et al. | What do support analysts know about their customers? on the study and prediction of support ticket escalations in large software organizations | |
US20230195759A1 (en) | Data processing systems and methods for automatically detecting and documenting privacy-related aspects of computer software | |
US8504412B1 (en) | Audit automation with survey and test plan | |
Montgomery et al. | Customer support ticket escalation prediction using feature engineering | |
Valverde et al. | ITIL-based IT service support process reengineering | |
US20200401977A1 (en) | System and method for evaluation | |
da Fonseca Lage et al. | Usability technical debt in software projects: A multi-case study | |
Almomani et al. | Software process improvement initiatives in small and medium firms: a systematic review | |
Outmazgin | Exploring workaround situations in business processes | |
US20160092807A1 (en) | Automatic Detection and Resolution of Pain Points within an Enterprise | |
Agustiono | Academic business intelligence: can a small and medium-sized University Afford to build and deploy it within limited resources | |
Van der Aalst et al. | Emailanalyzer: an e-mail mining plug-in for the prom framework | |
US20230316197A1 (en) | Collaborative, multi-user platform for data integration and digital content sharing | |
Bosu et al. | Evaluation of IT Service Desk: A Case Study | |
Ionita et al. | Arguesecure: out-of-the-box security risk assessment | |
Kadenic | Compliance of Data Lake Enterprise Architecture Model with the General Data Protection Regulation (GDPR) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SAP AG, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ZENG, YING;REEL/FRAME:028318/0365 Effective date: 20120514 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: SAP SE, GERMANY Free format text: CHANGE OF NAME;ASSIGNOR:SAP AG;REEL/FRAME:033625/0334 Effective date: 20140707 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |