Method, framework and system for organizing, aligning and managing organizations

• US 20030110070A1
• Filed: 10/25/2002
• Published: 06/12/2003
• Est. Priority Date: 02/05/2001
• Status: Abandoned Application

• Current Assignee: Marc Alexander De Goeij
• Original Assignee: Marc Alexander De Goeij
• Inventors: De Goeij, Marc Alexander
• Application Number:
  US10/258,691
• Publication Number:
  US 20030110070A1
• Time in Patent Office: Days
• US Class Current: 705/8
• CPC Class Codes: G06Q 10/063114 Status monitoring or status determination for a person or group
• CPC Class Codes: G06Q 10/06312 Adjustment or analysis of established resource schedule, e.g. resource or task levelling, or dynamic rescheduling
• CPC Class Codes: G06Q 10/0633 Workflow analysis
• CPC Class Codes: G06Q 10/0635 Risk analysis of enterprise or organisation activities
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change
• CPC Class Codes: G06Q 10/06393 Score-carding, benchmarking or key performance indicator [KPI] analysis
• CPC Class Codes: G06Q 30/0201 Market modelling; Market analysis; Collecting market data
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass

Abstract

A concept and method for organizing and aligning processes, functions, roles and tasks within organizations and across organizations by dividing these into Front Offices covering all processes, functions, roles and tasks whereby only the interaciton with any outside party, including Customers, is involved and Back Offices covering all processes, functions, roles and tasks whereby only the execution of a service or the production of a product is involved. Between the Front Offices and the Back Offices a Mid-Office is introduced covering all processes, functions, roles and tasks related to the coordination and management of all processes, functions, roles and tasks within or across organizations over all relevant Front Offices and Back Offices.

Claims

1. A concept and method for organizing and aligning processes, functions, roles and tasks within organizations and across organizations by dividing these into:

Front Offices covering all processes, functions, roles and tasks whereby only the interaction with any outside party, including Customers, is involved,

Back Offices covering all processes, functions, roles and tasks whereby only the execution of a service or the production of a product is involved,

characterized in that

between the Front Offices and the Back Offices a Mid-Office is introduced covering all processes, functions, roles and tasks related to the coordination and management of all processes, functions, roles and tasks within or across organizations over all relevant Front Offices and Back Offices as well as centrally storing and/or managing all relevant data and information about organizational internal and organizational external objects and occurrences necessary for effective management and proper performance of said organization processes, functions, roles and tasks,

for the main purposes of reducing complexity of relationships—

and therefore reducing management complexity—

and increasing flexibility for change.

2. A framework and method for implementing the concept and method defined in claim 1, said framework consisting of the following four architecture layers or blueprints:

a first architecture layer or blueprint describing the processes, functions, roles and tasks within or across organizations, aligned with the objectives of these organizations,

a second architecture layer or blueprint describing the information flows and data elements necessary to support the above mentioned processes, functions, roles and tasks,

a third architecture layer or blueprint describing the applications and/or software systems/components necessary to support the above mentioned processes, functions, roles and tasks and supporting information flows and data elements,

a fourth architecture layer or blueprint describing the hardware systems, operating systems and networks necessary for the aforementioned applications and software systems to run on,

characterized in that each of the above-mentioned four architecture layers is constructed according to the concept and method defined in claim 1.

3. The framework and method of claim 2, whereby the four architecture layers or blueprints form one set with each other such that the corresponding areas of the concept and method as defined in claim I are aligned:

Front Offices to Front Offices, Mid-Office to Mid-Office and Back Offices to Back Offices, for the main purposes of creating a consistent framework to support organization improvement and change and/or in order to implement the concept as defined in claim 1 within or across organizations.

4. The framework and method of claim 2 and 3 whereby all four architecture layers or blueprints are still to be seen independent of each other to obtain and maintain maximum flexibility to change any of the components in any of the architectures without substantially affecting the other components in any of the architecture layers or blueprints, or any of the architecture layers or blueprints themselves.

5. A system being the materialization and operationalization of the Mid-Office part of the framework defined in claim 2 through 4 and therefore covering all Mid-Office components on the third and fourth physical layers of the framework, designed for the purpose of implementing in an automated environment the concept and method defined in claim 1 as well as the framework defined in claim 2 through 4, said system comprising an integrated software/hardware platform together performing the various coordination, management, data and information management processes, functions, roles and tasks assigned to the Mid-Office, which system does not contain any Front Offices and Back Offices other than for its own management, maintenance and development and therefore is generic and applicable to any organizational environment.

6. The system of claim 5 comprising of various software components of which the key components are:

a process management software component or a detailed workflow component that routes actions and/or transactions initiated outside the system (Customer or third party initiated) or inside the system (triggers such as time or another event) through the end-to-end process life-cycle for that action and/or transaction by means of translating the process steps into business rules and following the business rules in order to call the different Back Offices as steps in the whole process by giving them the desired input for processing and expecting the proper output after processing according to predefined service level agreements between the process management software component and the various Back Offices;

a rule base containing business rules that are the translation of the process steps of the processes that take place within or across the organizations in focus in order for the process management software component to function and to manage and coordinate the processes to be executed;

a data base and/or administration that contains the exact status of actions and or transactions flowing through the processes;

this data base and/or administration is capable of distracting, compiling and consolidating data and information in order to provide any relevant stock balance or total action and/or transaction status as well as optionally links to other Mid-Office external data bases in order to keep the transaction status data base in the Mid-Office in sync with all relevant Mid-Office external transaction status data bases by means of substitution, duplication, replication, remote access or any other means of keeping data bases synchronized on a when necessary basis;

a data base or a set of databases containing static data and/or all relevant organizational internal and organizational external data, including links to other Mid-Office external data bases and mechanisms in order to keep the static data base in the Mid-Office in sync with all relevant Mid-Office external data bases by means of substitution, duplication, replication, remote access or any other means of keeping data bases synchronized on a when necessary basis.

7. The system of claim 5 and 6, optionally with the extension of the relevant hardware components and operating systems necessary for the above software components, functions and databases to run on if not available in the organization where the system will be implemented.

8. The system of claim 5 and 6, optionally containing a software component carrying out system management tasks, including but not limited to exception handling, recovery and error recovery, time management, check pointing, load balancing, logging and restart capabilities for the whole mechanism, including Front Offices, Mid-Office and Back Offices.

9. The system of claim 5 and 6, optionally containing a middleware component connecting in a standard way all software components, functions, databases, operating systems and hardware and network components contained in the system, as well as supporting open connectivity from the system of claim 5 and 6 to any organization Front Office and/or Back Office for easy integration of the system in any organizational context or existing and/or future infrastructure.

10. The system of claim 5 and 6, optionally containing a data base that contains all historic, log and archived data about the system, its content, its configuration and its behavior at any given time.

11. The system of claim 5 and 6, optionally containing a software component carrying out technical channel management tasks in order to monitor, manage and report on channel behavior for the whole mechanism, i.e. all channels that connect all Front Offices, Mid-Office and Back Offices.

12. The system of claim 5 and 6, optionally containing a software component carrying out security tasks which are Front Office and Back Office independent, supporting the generic character of the Mid-Office, including but not limited to authentication, authorization, transaction security and encryption/decryption, with the purpose of allowing only authorized parties to do authorized actions as well as to manage integrity of all data, including safeguarding privacy and the proprietary nature of data and information.

13. The system of claim 5 and 6, optionally containing a software component carrying out Customer relationship management tasks, including monitoring, managing and reporting on Customer behavior, Customer profitability and Customer profiles.

14. The system of claim 5 and 6, optionally containing a software component carrying out human resources management tasks in order to monitor, manage and report on human resources behavior, including skills and experiences and mapping these to processes, functions, roles, tasks, jobs and responsibilities.

15. The system of claim 5 and 6, optionally containing a software component carrying out stakeholder relationship management tasks in order to monitor, manage and report on behavior, contracts, agreements, expectations, flows, statuses, performance measures and all other relevant data for all organization stakeholders, including but not limited to owners, suppliers, (strategic) partners, governments and other public or contextual bodies and communities.

16. The system of claim 5 and 6, optionally containing a software component carrying out administration and financial administration tasks in order to monitor, manage and report on stock balances, including financial balances, and translating all stock balances into financial balances as well as to support monitoring, managing and reporting on risks and exposures;

17. The system of claim 5 and 6, optionally containing a software component carrying out content management tasks in order to monitor, manage and report on information from various sources in various media and various formats.

18. The system of claim 5 and 6, optionally containing a software component carrying out management information and decision support tasks in order to monitor, manage and report on the nature and status of critical success factors (CSF'"'"'s), key performance indicators (KPI'"'"'s), performance targets and performance measures of the organization or organizations in focus and to support multi-level decision making by extracting, compiling, consolidating and arranging data.

19. The system of claim 5 and 6, optionally containing data warehouses and data marts to support the management information and decision support software component of claim 18 by rearranging data for security, response time and convenience purposes.

20. The system of claim 5 through 19, embedded in a development environment that allows for functional maintenance of the system, including but not limited to enhancements, change management, versioning, transition of versions and coexistence between versions.