| Table of Contents |
|---|
...
ensures continuous improvement in operational performance across the organization unit and outside parties
- background at BWC West - 1984
before LSS - Six Sigma existed, in 1984 BWC West, defined the CIP process - the ERP implementation team had designed many business process improvements while implementing MANMAN ERP
- after the system was running successfully in production, the team of mid-level operations staff continued to meet every 2 weeks to focus on the next items they could improve as a business or operations priority based on their own assessments of impact, value, risk as well as top management goals
- when significant funding or business approvals were required for a change, they submitted the business decision to senior management
- the business results from the BWC West CIP were clear and we took that process and starting using it in other business units
much later came the branding of CIP with Six Sigma and LSS - LSS can reduce your costs and help you retain and even gain more customers. LSS prescribes an improvement process known as DMAIC (Define—Measure—Analyze—Improve—Control). For new processes - see DMADV ( Define - Measure - Analyze - Design - Verify ) – see POT, POC, POV
- BWI: Barry Wright BEP - Business Excellence ProcessProgram
- i Project Mgt#LeanSixSigma-ProcessImprovement,WasteReduction-DMAIC
- i Project Mgt#LeanSixSigma-ProcessImprovement%2CWasteReduction
- https://www.purdue.edu/leansixsigmaonline/blog/dmaic-vs-dmadv/
- PDCA is another approach to CIP
- PDCA refers to a repetitive model that includes four stages – Plan, Do, Check, and Act. It is used to achieve continuous improvement in business process management. The concept was introduced by Dr. Edward Deming in 1950
- PDCA is normally for smaller changes in process or systems in scope - today the MAKER / CHECKER pattern is used for independent verification that proposed changes actually solve a problem without side effects
- CIP overview
- CIP - Continuous Improvement Process - a business operations model focused on continuous improvement on business goals and operating plan was the driver for the best run company I was part of. It was always driving operations excellence while driving improvement in services, operations across all departments ( an integrated version of Agile iterative improvement ). With its focus on metrics, it was always looking to find the right data and improve data quality. With its focus on process integration across departments, clients and vendors it was a prototype for todays blockchain consortiums that re-engineer and optimize business processes across communities and roles. It fit well in the "goals down, plans up" model driving operation change from the operations level. With both corporate strategic and tactical planning cycles driving goals down, it delivered consistently good results.
EOS - enterprise open-source
...
all phases driven by a library of executable test cases with matching masked data scenarios and automation
tests are executable use case scenarios to implement and drive the entire delivery cycle.
SOS - Smart Object Services - defined with SOE - service oriented engineering
- why SOS vs SOE? Because EVERYTHING has a context explicit or implicit
soa is a dream, soe is reality – it’s what got built and runs . it’s what matters. Not a paper design.
soe delivers what soa promises
- multiple approaches to SOE design
...
VCE - Value Chain Economies - Networks to optimize network value, efficiency, lower costs, risks
VCE is a micro economy oeprating in a VCC ( Value Chain Community )
for more, see >> VCE > Value Chain Economies are virtual economic communities#VCE-ValueChainEconomiesareVirtualDigitalCommunities
...
- does not need to be a DLT network but DLT networks often focus on VCN outcomes
- Supports multiple parties in multiple roles on a network
- key design method for any DLT network
- See Solutions VCRS to decide how to realize
- See FACTUR3DFACTUR3DT.IO analysis for before and after impacts
- See Tokenomics for the models to incentivize network behaviors based on roles
...
- Rotation on environments resources assets where planned or needed
- Recovery Design: BCP, RTO, RPO
- Reliability Design: What can't fill ( by design ) will >> Design Test for Failure, Performance vs Requirements
- Rerun: support transaction reprocess where needed across the VCN
- Replay: replay data transactions where needed
- Review: monitoring and alerting of events where needed
- Redesign: when the business requirements change or the technology operations capabilities change, consider redesign
- Re-engineer: where the business requirements haven't changed significantly but operations characteristics are no longer meeting needs
STS - Smart Trust Services Concepts
SGS = Smart Governance Services >>. GOV = GTO > Governance, Trust, Outcomes
Better Governance = Better Trust = Better Outcomes
Proof of Governance is key
CBTP - Confidence Needs Understood, Belief the Right Resources Available, Trust in Delivery Priority for a Purpose in service provider relations
Basis for agreements, contracts for value & services
RME - Risk Management Engineering - Answer? - Consensus reached on "What's it take to do it right?"
...
- Creation
- Datablox can be created automatically or manually from definitions ( metadata )
- create request can be defined by data gap: an output format for specific data sources
- the datablox registry shows defined datablox definitions
- datablox can be: named, created as temporary or permanent, shared or dedicated by default
...
GEMS - Global Event Management Services
...
flexible metadata definitions with shared, distributed repository
dynamic discovery, assessments, registrations, services catalogs, IAMs
supports prioritizations, logging levels
...
- adaptable, automated, auditable, asynchronous
- secure, standards, supportable, serviceable, simple, smart, subscribeable, solid design principles
- cost-effective, configurable, collaborative
- reliable, reusable, recoverable, risk-efficient, resource-efficient, reactive, resilient, replays
- usable, useful
- modular, maintainable, manageable, monitorable, migrateable
NFR Definitions best practices
Solution criticality, usage, risks, threats will drive NFR engineering depth
Architecture Design Concepts for Solution Engineering
...