A reference architecture - from stakeholders perception to organize implicate and explicate order

Reference Architecture

The distinction between the implicate and explicate order.  Assume implicate serves as the foundation and represents the ideal state.

In a "real world" scenario what we expect or the foundation for the "fit for purpose".  In reality, the Real World expectations never turn up in our outcomes.  We expect nothing to be as we expected.

The trick is capturing the differences and having a transparent way to reveal the differences and allow others to contribute to the support or object in a respectful and meaningful way.    

Three Operating Models

Within each functional group, we have three types of workers.  

1. Operational and tactical workers who run the business
2. Leaders and People Managers who change the business
3. Transform and Grow the business with external market and international wisdom

Organizational Models 

Beyond the corporate organizational hierarchy, we use the same source for natural roll ups of information and workflow approvals.  Default to the hiring manager for all workers expenses and then adjust to higher levels in the same hierarchy based on the amount of a purchase and the authorization to approve amounts.  

Living Sustain-ably

Living Organizations and Living Enterprises both types serve people and planet. 

Human Rights and Equality 

• Women's Issues with - Security of persons and freedoms  

Information, Communication and Technology

• Information-the life blood of any organization.
• Information is derived from data
• All technology solutions off the shelve, out of the box and home grown custom coded applications whether merely an application created using business intelligence tools or one designed for the mainstream solutions we buy off the shelve.   Each has data structured in a form (web form) or digital document, once a user inputs their knowledge to a process, the processing performed by the application uses data, the output from the algorithm results in knowledge.  
• Once Validated by a designated user, during a close process for example we will have knowledge transformed into a record.  
• However, at each point in the before mentioned, we also have the same represented as "data" stored in a storage container.  
• We might copy the database where the data was collected or acquired for storage associated with the source application.  
• We might have a copy of the party, offer and financial tables from your ERP system stored to operate specifically for the application to use as reference data.  
• Each copy introduces the opportunity to change the reality or real world experience for the users in the operational applications.   
• The answer isn't to copy the information from an offline database to the source application, that's just trying to trick the systems and it's illegal when financial information exist.  
• The sole purpose of a customer, offer and associated items in the offer and financial account codes each have only one use in an organization.  
• A customer intends to generate a revenue transaction for a profit, ideally delighting your customer.  
• A supplier intends to purchase goods or services from a vendor for resale or administrative overhead and cost of running the business.   
• An item and offer are specifically created to buy or sell an offer.
• The financial account codes are used to associate the transactions with a reference in order to segment the results of the operational performance.  
• A record must be retained in its original format with associated system time stamps.  
• A physical record cannot be modified and thus the rationale for retention of the physical records over the digital records is smart and unfortunately required due to the lack of control in data processing.  
• An information architecture has three primary components
• Hierarchies
• Master Data 
• Metadata
• Operational Performance Measures 
• The financial transactions of expense and revenue used to consolidate and report the performance of a public and private sector organization. 
• The final reported numbers on an income statement, profit and loss report and anything reported to the Security Exchange Commission and industry analyst.  
• Records result from the validation process during the close procedures performed by accounting.  
• ERP is the system of record and most logical place to focus governance and controls.  
• ERP is the type of software application with zero down time and zero data loss in most sustainable organizations.  
• ERP transactions are never deleted and change control procedures exist for any change to a transaction or the details when entered into an ERP system.  
• All functional groups use ERP, directly or indirectly most users will use the application.  
• New hire request for headcount or on boarding a resource cost for the department.  
• Office Supplies
• Expense Reports and reimbursements 
• A major gap in most organizations or agencies exist with the lack of wisdom in what ERP is designed to do and why its so difficult to manipulate the system.  
• Integrity in the processing of financial transactions isn't optional its the law.  
• Regulations are getting more complex as the many ways people try to break the law, massage the numbers or whatever politically correct way your company has developed isn't in the gray area, its a symptom and cause for the economic crisis.  
• Its how companies fail to pay taxes or if you were not a private company you'd be accused of money laundering and fraud.   
• Organized crime is just as criminal in a board room as it is in the gambling casino or as Italian, Russian, Syrian, Mexican, Japanese or Chinese mobs.  
• Quality Management System is the outcome of the operational Business Management System. 
• Business Intelligence systems are not the same and not held to the same strict controls of the operations and performance systems.  
• In fact, the acquisition, storage and workflows include transformation which is an offline backend change to digital records.  
• Many sarbanes oxley laws and key controls are tightly managed in the source systems, although source systems are not the same in data warehouse and business intelligence systems.  
• A storage system
• An integration or ETL and ELT  system differs and doesn't typically meet the audit standards of general accounting acceptable practices.  
• Any near real time requirements you have in your organizations BI or EDW operations are typically suspect for deep quality assessments.  
• Data type changes in your EDW processing
• Nulls in your database - especially, in zip code or country code fields are a huge red flag.
• Decimal format errors - nearly always have a financial transaction impact and therefore, by default introduce an offline change by unauthorized users in most situations.  
• Date format errors - nearly always have a financial transaction dependency or by default may cause the erroneous application of an alternate source to trick the system into thinking no changes were made by the updates.  The date of update could not stamp and alternate response would default the original change date. 
• Without context "data is just data" or when acquired from a database storage container without the source application logic applied in the storage container, its a source system without the controls of the application. 
• In order to derive the context, we must acquire the context in the form of information from data organized and structured without breaking the application logic or referential key constraints.   
• Master Data and Implicate Order the match made in heaven, but also the Identity in a viable system model.  
• Transaction data derived from master data at a point in time. 

• Random Thoughts about digital and transformation