Page Comparison

...

...

• 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).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 Program
• 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

...

• customer continuously iterating executable use cases weekly to drive requirements, usage, design, quality

• working with customers, define the use cases, process requirements in scope for a releasewith customers, define the use cases, process requirements in scope for a release
• client needs ( not products ) drive the solution engineering process
• often CDD - Capability Driven Design methods focus on the translation of potential needs, requirements into capabilities that can map to product offerings

RDD - Responsibility Driven Design for Requirements Definitions

...

• requirements are defined as executable use cases for a solution
• responsibilities are best defined as executable use cases as well
• all requirements should be testable as an executable use case
• if there isn't an XUC, don't build the solution or service that fulfills the requirement
• ideally, there is an E2M2 - Executable Enterprise MetaModel that XUCs are added to 
• the XUC approach automates SDP from requirements through QA ETE

CDD -

...

Capability Driven Design - Customer Centric Focus

• CDD supports a customer-centric solution focus
  • based on matching client use cases to requirements and related capabilities
  • this contrasts with a product-oriented process where the client has to do more work to map their needs to solutions

• given the RDD object model, define capabilities required from the RDD definitions and related NFRs ( Non Functional Requirements )

• provides a part of the SWT Value Chain Solution Engineering life cycle 
• what are the needs, priorities, problems, opportunities to solve? deliver? avoid?
  focus not on products but solution engineering
• CDD will enhance the actors and also add lower level services to implement many of the CDDs as needed
• CDD complements portfolio driven IT asset and product management
• mapping: actors may be mapped to existing objects fully or partially where that applies using the object service catalog for existing systems to reduce "reinventing the wheel" where feasible for the NFRs

...

• 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

...

• data should manage itself for operations, change management
• drive automation with metadata management for data and the environment
• SDM services fit data needs for:  volume, volatility, value, variety, variance, veracity, velocity, visualization
• variety includes: structured, unstructured documents and media
• SDM should support application needs for immutability, retention, reliability, replay, reuse

• the more intelligent the data, the less work for applications

• engineer intelligent data services that answer higher level questions

• expand process modeling to include decision modeling for each stage

• create agents that offer answers to the decisions at each stageagents that offer answers to the decisions at each stage

The Data Vs >> volume, velocity, variance, variety, validity, verifications, versions, value, visualizations

SDD - sprint driven delivery

• SDD practiced inside the SDP process
• before you run and manage sprints, you need to prepare - Sprint 0 - the preparation sprint is task-based, not time-based and critical to success
• all work for product releases, not just development, can be tracked in sprints
• the only exception is normally ongoing support for bug fixes etc

• break down deliverables into executable units of work that can be validated, ideally by users

• work sprint phases clearly EACH sprint – plan, deliver, test, review

• users involved at the start, end and testing of every sprint

• balance resource, deliverables and time in a sprint

• goals down, plans up

• daily standups

• sprint review reports

• sprint reviews

m Consulting Process#FortheSDP(SolutionDeliveryProcess)%2CAnalyticsMethodstouseforVCEsolutions

i Lean Agile#KeyConcepts

CDP - continuous incremental delivery process

...

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 >> Modern Platform ODP supports VCE , DANVCE > 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
  • s Blockchain Opportunity Assessment - BOA
• See Tokenomics for the models to incentivize network behaviors based on roles
  • m Token Economy Examples: Tokenomics

...

• 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?"

...

1. Creation
   1. Datablox can be created automatically or manually from definitions ( metadata )
   2. create request can be defined by data gap: an output format for specific data sources 
   3. the datablox registry shows defined datablox definitions
   4. datablox can be: named, created as temporary or permanent, shared or dedicated by default

STS - Smart Trust Services Concepts

GEMS - Global Event Management Services

...

flexible metadata definitions with shared, distributed repository

dynamic discovery, assessments, registrations, services catalogs, IAMs

supports prioritizations, logging levels

...

for each of the capabilities listed below, how can your current solution design leverage these concepts?

#NFRs defined by ascrum

ascrum NFRs - a set of capabilities that identify the value of different solution aspects - not related to solution functional requirements

• 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

Image Added

Architecture Design Concepts for Solution Engineering

DATES - Decisions & Data, Automations, Trusts, Events, Services

...