jump to navigation

An introduction in Quality March 25, 2008

Posted by rettema in Research Problem.
add a comment

LSS = Lean Six Sigma ; EE = Enterprise Engineering

In the line of reasoning of the business problem we noted that the professionals in both disciplines work isolated from each other. Combine this with the fact that both have their own fundamental theories we find ourselves in a situation of segregated concepts. So an useful concept within LSS does not necessarily lead to a meaningful concept for EE. So if we strive towards a merger of Lean Six Sigma and Enterprise Engineering we need a fundamental research to explore the conceptual areas of segregation.

Overseeing fundamental research we observed a research pattern. Researchers explore in many cases the meaning of a concept by placing them in a meta-model. This creates a situation and opportunity to reason its meaning from the meta model perspective and its position within. For example if a concept is positioned in an upper ontology we are capable to reason its meaning in the realm of the philosophical existence. As enterprise ontology is the cornerstone for enterprise engineering the concepts within are scientifically well defined.

Lean Six Sigma is different. Recently in 2007, Henk de Koning a researcher of IBIS UVA (section 2.1) delivered a scientifically grounding for LSS based upon a rational reconstruction (Koning, 2007). In this report Six Sigma is seen as quality improvement strategy (Koning, 2007 p. 21) which is in line with our introduction of LSS in section 2.2.3. The statement implicit expresses the importance of quality for LSS therefore a definition of Quality was reconstructed from publications of thought leaders.

Definitions: (Koning, 2007 p. 22)

Product Quality: product quality refers to product characteristics and the extent to which they meet customer (meaning: end-user) demands. Product characteristics that together make up product quality are: performance, features, reliability, conformance, durability, serviceability, aesthetics and perceived quality.

Process Quality: process quality reflects the demands of internal customers, and comes down to effectiveness (the extent to which a process provides required features) and efficiency (being effective at low cost). Dimensions of process quality include defect rates, but as well cycle time, yield and production costs not related to defects.

Understanding these definitions from a semiotic triangle perspective (Dietz, 2006 pp. 36, fig 4.1) these definitions are concepts, reconstructed from the mental pictures of LSS publicists. Within these definitions we can identify process and product characteristics which are other concepts from which the six sigma level of quality is reasoned. For reasoning purpose we marked them red in the next figure.

Figure 11 Rational reconstruction of Six Sigma’s business context.

These process characteristics are important concepts because they bind the LSS concerns with the business transaction oriented way of modeling of DEMO. If we strive towards an integrated methodology we need to understand their ontology and their relationship with the enterprise ontology. In practical terms, concepts like ‘Yield’, ‘cycle times’, ‘defects rates’ need to be studied in the context of the ontological parallelogram (Dietz, 2006 pp. 39, fig 4.2).

Currently there is a lack of knowledge how these process characteristics fit into the enterprise  ontology . As result of this, it is not only difficult to strive further to one integrated methodology but what is more severe is our missing understanding of quality (incl process characteristics) in the realm of enterprise ontology.

Dietz, Jan. 2006. Enterprise Ontology, ISBN: 3540291695. Delft : Springer Verlag, 2006.

Koning, Henk de. 2007. Scientific Grounding of Lean Six Sigma’s Methodology. Amsterdam : UVA, 2007. 978-90-6464-176-3.

The ontological notion of behaviour March 20, 2008

Posted by rettema in Free Thoughts, Research Problem.
Tags:
add a comment

In the last post I presented the “Mass Production” (MP) and “One Piece Flow” (OPF) video. My statement that both have the same ontology was made from the DEMO perspective. Independent if a composite business act is implemented in either OPF or MP the representation of the situation with DEMO is the same. My statement doesn’t mean there is no notion of behavior in ontology.

In the publication The behavior of a technical Artifact researchers delivered an ontological definition of behavior for an artifact. The added value for my research is that behavior is reasoned from the Upper Ontology
DOLCE. This ‘Upper Ontology’ is , part of the wonderweb project that finished in 2004.

Idea: A future publication for my research is to define performance, waste and variation from the upper ontology to create a viable introduction of these concepts as an interoperability bridge between DEMO and Lean Six Sigma.

Has a composite act implemented in either “mass production” or “one piece flow” the same ontology ? March 15, 2008

Posted by rettema in Free Thoughts.
2 comments

Enterprise ontology is about capturing those elements of an enterprise that determines the existence of the enterprise as a whole. In the theory of Enterprise Engineering the set of business acts including rules and information defines the enterprises structure and therefore its architecture. A representation of this information in for example DEMO, reflects an enterprises ontology and is completely disconnected from its implementation. However if we like to optimize enterprises for example with Lean Six Sigma we need to know how the business acts within behave.

Take for example the behavior of an composite act “creation of a bicycle”. In ontology we speak of a composite act because other ‘nested’ business acts are necessary to realize its creation. However the behavior ‘performance’ of the composite differs when these sub acts are conducted as a sequence or as parallel. Is the behavioral dimension then part of the enterprises ontology ? When not can it be considered as a dimension between ontology and implementation ?. In the next video of Ron Pereira we observe a simple experiment of two implementations of a business act (P-Fact). As result we will see a performance difference between the traditional “mass production” manufacturing technique against the lean “one piece flow” approach.

From an ontological perspective the business act (including P-Fact) is the same. From the composite axiom for both situations the business act has the same composition.

Question: Is the ontology of both the same or is it necessary to introduce a behavioral dimension as part of the ontology ?

The Things (Arnaldo Antunes, 1993) : The things have weight, mass, volume, size, time, shape, color, position, texture, duration, density, smell, value, consistency, depth, boundaries, temperature, function, appearance, price, fate, age, significance. The things have no peace.

Can Enterprise Architecture be Expressed as a Set of Partial Differential Equations ? March 11, 2008

Posted by rettema in Free Thoughts.
add a comment

All complexities can be studied by applying simple Axioms, such that the laws of nature governing the system as a whole explains the EA behavior.

EnterpriseArchitecture = f (Process Architecture) +f (Performance) + f(Cost) +f(Architecture decisions) + f (Degree of Problem Complexity)+ f ( Process ofCreation) + f (Operations) + f (Market) …..etc

Change in any of the variable impacts the EA behavior, the concern is in understanding that a change happens and how this can be aligned with the desired objective. Remember, increasing ‘Degree of Complexity’ reduces the ‘Degree of Freedom’, from Goldratt’s Theory Of Constraint ; i.e, ‘Complexity’ and ‘Freedom of  Operation’ are inversely proportional.

ProcessArch = f(Business Arch) +f(Information Arch) + f(Solution Arch) + f (TechnologyArch) + f (Degree of Solution Complexity) + …etc

Processes= f (Function) +f (Business Ontology) + f (Degree of Business Abstraction) + f(Aggregated Cost)

Function=f (Activities) + f (physical resources) + f (information) + f (abstraction –businessrules) + f (actual cost) + ……etc

Source: ingine