Issues for Business Motivation Model 1.1 Revision Task Force

To comment on any of these issues, send email to bmm-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 10113: Section: 7, 8, 9
Issue 10586: Section: 8.5 pages 48 - 50
Issue 11510: Restore Primary Reading to "Formulated Based On" Fact Type
Issue 11695: class diagram issue
Issue 12955: BMM section 7.3.6 - clarification needed
Issue 13059: Category of Category
Issue 13060: Internal and External Influencers

Issue 10113: Section: 7, 8, 9 (bmm-rtf)

Click here for this issue's archive.
Source: Rule ML Initiative (Mr. John Hall, john.hall(at)modelsystems.co.uk)
Nature: Revision
Severity: Significant
Summary:
In response to some SBVR FTF issues, changes have been made to SBVR that affect business rule (adopted from SBVR by BMM) and business policy (adopted from BMM by SBVR). A minor update of BMM is needed to keep it consistent with SBVR Summary of relevant SBVR changes: The resolution of SBVR Issue 9477 caused the verb concept (unary fact type) 'directive is actionable' to be replaced by two verb concepts with narrower definitions: • 'element of guidance is practicable': this is concerned with ensuring that business rules are sufficiently well-defined and precise that they can be put directly into practice. • 'element of governance is directly enforceable': this is concerned with ensuring that violations of operative business rules can be detected and corrected. This separation of concerns is relevant to BMM. If desired results for an enterprise are not being achieved, there could be two causes related to business rules: 1 The enterprise does not have the right business rules. 2 The enterprise and, particularly, the people in the enterprise are not applying the rules correctly. Before challenging whether the business rules are the right ones, it would be important to establish that the rules were being applied as they were intended to be. To establish this, the rules must be enforceable. A resolution of this issue has been drafted, and will be distributed to the BMM FTF when the relevant SBVR changes have been finalized

Resolution: The resolution is: · To align BMM definitions of 'directive' and 'business rule' with corresponding definitions in SBVR, using "practicable" and "directly enforceable" instead of "actionable". · Not to adopt additional structure from SBVR into BMM, but to add some explanatory notes. The rationale is that 'business rule' in BMM is a placeholder (like 'business process' and 'organization unit'). In an enterprise's BMM an instance of 'business rule' would be a reference to a business rule that is defined in a model of the operational business. In an integrated set of OMG business models, the operational model for business rules would be SBVR-based. Business rules would be connected to the fact types they are based on, the representations owned by speech communities, etc. But businesses can use BMM without having to use SBVR. Operational models do not have to be SBVR-based. This "loose coupling" is one of BMM's strengths, and it can be adequately supported by a 'business rule' placeholder. It does not need additional concepts (see discussion below), such as 'element of governance', 'operative business rule' and 'structural business rule' to be adopted into BMM from SBVR.
Revised Text: In 8.2.10, first paragraph (page 35) Replace: A Business Policy is a non-actionable Directive whose purpose … With A Business Policy is a Directive that is not directly enforceable whose purpose … Add a footnote, referenced after "directly enforceable": "Not directly enforceable" means that some interpretation of the directive (e.g. in business rules) is needed in order to detect violations In 8.2.7 first paragraph (page 32) Replace: A Business Rule has an enforcement level. With: A Business Rule that guides behavior has an enforcement level. Add a footnote, referenced after "enforcement level" Only business rules that guide behavior (SBVR 'operative business rule') require enforcement. Definitional business rules (SBVR 'structural business rule') are "true by definition" In 9.1, under 'business policy' (page 60) Replace: Definition directive that is not actionable With: Definition directive that is concerned with directly controlling, influencing, or regulating the actions of an enterprise and the people in it and that is not directly enforceable Replace: Note: 'Actionable' means that a person who understands a Directive could observe a relevant situation (including his or her own behavior) and decide directly whether or not the business was complying with that Directive. In contrast to Business Rules, Business Policies are not actionable in that sense. With: Note: 'Not directly enforceable' means that some interpretation of the directive (e.g. in business rules) is needed in order to detect violations. In 9.1 under 'business rule' (page 61) Replace: Definition directive that is actionable With: Definition directive that is practicable Replace: Note: 'Actionable' means that a person who understands a directive could observe a relevant situation (including his or her own behavior) and decide directly whether or not the business was complying with that directive. In contrast to business rules, business policies are not actionable in that sense. With: Note: 'Practicable' means that a person who understands a directive could observe a relevant situation (including his or her own behavior) and recognize directly whether or not the business was complying with that directive. For rules that govern activity (SBVR 'operative business rule') this recognition is about the behavior of people and what form compliant behavior takes. For example: "each rental must be guaranteed by a valid credit card held by the renter of the rental" For definitional rules (SBVR 'structural business rule') this recognition is about evaluation of the criteria vested in the rule to produce consistent outcomes for decisions or calculations. For example: "a car model requested for a rental must be a car model of the car group specified for the rental". In 9.1, under 'directive' (page 63), add Synonym: element of guidance [Source: SBVR] In 9.1 under 'tactic effects enforcement level of business rule', add Note: Only business rules that guide behavior (SBVR 'operative business rule') require enforcement. Definitional business rules (SBVR 'structural business rule') are "true by definition".
Actions taken:
August 21, 2006: received issue
July 23, 2009: closed issue

Discussion:
The relevant part of SBVR is illustrated in the following diagram from the SBVR specification:
The part of this SBVR fragment that is specifically relevant to BMM is illustrated below. 






Correspondence between SBVR and BMM:
Directive
Since directive in BMM and element of guidance in SBVR have the same definition, they are synonyms: 
Definition	means that guides, defines, or constrains some aspect of an enterprise.
Business Policy
In BMM 1.0, business policy is a specialization of directive
business policy
Concept Type:	directive that is not actionable
Note:	'Actionable' means that a person who understands a Directive could observe a relevant situation (including his or her own behavior) and decide directly whether or not the business was complying with that Directive. In contrast to Business Rules, Business Policies are not actionable in that sense.
In SBVR 1.0, business policy is a specialization of element of governance, which is a specialization of element of guidance.
business policy
Definition	element of governance that is not directly enforceable whose purpose is to guide an enterprise
Note:	'Directly enforceable' means that a person who knows about the element of governance could observe relevant business activity (including his or her own behavior) and decide directly whether or not the business was complying with the element of governance.
element of governance
Definition	element of guidance that is concerned with directly controlling, influencing, or regulating the actions of an enterprise and the people in it
The definition of BMM business policy can be aligned with that of SBVR business policy:
Start with the SBVR definition of business policy: 
Definition	element of governance that is not directly enforceable whose purpose is to guide an enterprise
Replace the term 'element of governance' with its definition:
Definition	element of guidance that is concerned with directly controlling, influencing, or regulating the actions of an enterprise and the people in it and that is not directly enforceable whose purpose is to guide an enterprise
Replace the term 'element of guidance' with its BMM synonym 'directive':
Definition	directive that is concerned with directly controlling, influencing, or regulating the actions of an enterprise and the people in it and that is not directly enforceable whose purpose is to guide an enterprise
Delete the final phrase ("whose purpose …"), because it is covered by the embedded definition of element of governance:
Definition	directive that is concerned with directly controlling, influencing, or regulating the actions of an enterprise and the people in it and that is not directly enforceable 
Business Rule 
In BMM, Business Rule has two definitions, one of which is adopted from SBVR.
business rule
Definition	directive that is actionable
Definition	SBVR: rule that is under business jurisdiction 

SBVR includes the following:
structural business rule
Definition	structural rule that is a business rule
Necessity:	Each structural business rule is practicable.
operative business rule
Definition	business rule that is a claim of obligation
Definition	element of governance that is directly enforceable
(under element of governance is directly enforceable):
Necessity:	Each element of governance that is directly enforceable is practicable.
So, in SBVR, both types of business rule are practicable. The BMM definition of business rule can be updated to:
business rule
Definition	directive that is practicable
and the note on 'actionable' replaced by an equivalent note on 'practicable'.
BMM Fact Type
Also, BMM includes a fact type:
tactic effects enforcement level of business rule
Synonymous Form:	business rule has enforcement level effected by tactic
In SBVR, only operative business rules can be enforced, so only they have enforcement levels. A note explaining this is needed. 
 


Issue 10586: Section: 8.5 pages 48 - 50 (bmm-rtf)

Click
here for this issue's archive.
Source: Rule ML Initiative (Mr. John Hall, john.hall(at)modelsystems.co.uk)
Nature: Revision
Severity: Significant
Summary:
The placeholder descriptions of "Organization Unit" and "Business Process" need to be updated to be consistent with the latest submissions for OSM and BPDM

Resolution: Create a holding position for business process and organization unit placeholders: · Change the reference for business process to BPMN, instead of BPDM. · Remove Figure F-2 · Update the comments about the current status of BPDM and OSM in Annex F Create a new issue for business process and organization unit placeholders, to be resolved in a future RTF or RFP, after BPDM, BPMN and OSM are stabilized.
Revised Text: In 1.2, 2nd bullet point (page 1) Replace: the submissions for BPDM2 With: the submissions for BPMN2 Replace footnote 2 with: OMG Adopted Specification "Business Process Modeling and Notation" In 1.6.2 (page 4) In first sentence, replace: …. standards and models based on the OMG's specifications for BPDM, SBVR, and OSM. With: …. standards and models based on the OMG's specifications for BPMN, SBVR, and OSM. In 2nd numbered point, replace: Eventually specifications such as BPDM, SBVR … With: Eventually specifications such as BPMN, SBVR … In 5 (page 5), add BPMN Business Process Modeling Notation OMG Specification In 7.3.7 first paragraph (page 14) Replace: The BRG anticipated that the best sources for the required external standards would be the OMG's specifications for the Organization Structure Metamodel (OSM), Business Process Definition Metamodel (BPDM), and Semantics of Business Vocabulary and Business Rules (SBVR). With: The BRG anticipated that the best sources for the required external standards would be OMG specifications such as Organization Structure Metamodel (OSM), Business Process Modeling and Notation (BPMN), and Semantics of Business Vocabulary and Business Rules (SBVR). in 7.3.11, last paragraph (page 16) Replace: However, when the OMG specifications for BPDM, SBVR … With: However, when the OMG specifications for BPMN, SBVR … In 8.5 second paragraph (page 52) In the 2nd paragraph, replace: … Business Process Definition Metamodel (BPDM), With: … Business Process Modeling and Notation (BPMN), In the 3rd paragraph, replace: ... are placeholders for association with concepts in OSM and BPDM respectively. With ... are placeholders for association with concepts in OSM and BPMN respectively. In 8.5.2 second paragraph (page 55) Replace: 'Business Process' in the Model is a placeholder for a concept to be adopted from an external standard. As a placeholder, an informal description is: "A unit of work to accomplish a transformation of information or resources contributing to the business objective of a conventional or orchestrated process." [BPDM 'Activity']10 With: 'Business Process' in the Model is a placeholder for a concept to be adopted from an external standard, such as BPMN. Delete: Footnote 10 In 9.1 (page 61) replace the entry for 'business process' with business process General Concept: motivation element Note: The concept 'business process' is adopted from the OMG's Business Process Modeling and Notation (BPMN) specification. The placeholder definition is given below. Definition a set of activities that are performed within an organization or across organizations Note: A Business Process may contain more than one separate Process. Each Process may have its own Sub-Processes. Individual Processes would be independent in terms of sequence flow, but could have message flows connecting them. Note: An activity is work that is performed within a business process. An activity can be atomic or non-atomic (compound). The types of activity that are a part of a Business Process are: Process, Sub-Process, and Task. In D.3 after bullet points (page 82) Replace: 'Business Process' in the Model is a placeholder for a concept to be adopted from an external standard. The placeholder definition adopted into BMM is: "A unit of work to accomplish a transformation of information or resources contributing to the business objective of a conventional or orchestrated process." With: 'Business Process' in the Model is a placeholder for a concept adopted from the OMG's Business Process Modeling and Notation (BPMN) specification. Delete: Footnote 3 In F.1 (page 91) In 1st bullet point set, 1st bullet, replace: Business Process Definition Metamodel (BPDM) With: Business Process Modeling and Notation (BPMN) In 2nd bullet point set, 2nd bullet, replace: Business Process Definition Metamodel (BPDM) With: Business Process Modeling and Notation (BPMN) In F.2 (page 91) Replace heading: Business Process Definition Metamodel (BPDM) With: Business Process Modeling and Notation (BPMN) In F.2 (pages 92 - 94) Replace: All of F.2 after figure F.1 (i.e. starting from "The corresponding fragment …") With: The concepts in BPMN that correspond to Business Process in the BMM are: · Process (Clause 8.6) A Process is an activity performed within or across companies or organizations. In BPMN a Process is depicted as a graph of Flow Objects, which are a set of other activities and the controls that sequence them. The concept of process is intrinsically hierarchical. Processes may be defined at any level from enterprise-wide processes to processes performed by a single person. Low-level processes may be grouped together to achieve a common business goal. Note that BPMN defines the term Process fairly specifically and defines a Business Process more generically as a set of activities that are performed within an organization or across organizations. Thus a Business Process, as shown in a Business Process Diagram, may contain more than one separate Process. Each Process may have its own Sub-Processes ... The individual Processes would be independent in terms of Sequence Flow, but could have Message Flow connecting them. · Activity (Clause 9.4) An activity is work that is performed within a business process. An activity can be atomic or non-atomic (compound). The types of activities that are a part of a Business Process Diagram are: Process, Sub-Process, and Task. · Task (Clause 9.4.3) A Task is an atomic activity that is included within a Process. A Task is used when the work in the Process is not broken down to a finer level of Process Model detail. Generally, an end-user and/or an application are used to perform the Task when it is executed. Note: as at November 2008 responses to an OMG RFP for BPMN 2.0 had been submitted. It is expected that the outcome will not affect the nature of the correspondence between 'business process' concepts in BMM and BPMN. Add a footnote, referenced from 'BPMN' in the first line: Business Process Modeling Notation, V1.2 (Beta 3) OMG Available Specification (08-02-07.pdf) In F.4 (page 95) Replace: The corresponding part of the SBVR Specification (OMG document formal/2008-01-02) is: With: The corresponding part of the SBVR Specification is: Add a footnote, referenced from 'SBVR Specification': Semantics of Business Vocabulary and Business Rules (SBVR), v1.0 OMG Available Specification (08-01-02.pdf) Renumber Figure F.4 as F.3 In F.5 (page 96) Renumber Figure F.5 as F.4 Replace: Currently, there are 3 submissions for OSM (OMG documents bei/04-12-01, bei/05-01-03, bei/05-01-04). The submission teams are collaborating to produce a single submission. However, across all three there are several concepts that define organization units of various types, and in two of the submissions they are associated with processes. So, it is not anticipated that mapping of concepts will be difficult, but suggestions for reconciliation of the OSM model with the Business Motivation Model will be deferred until a draft of the joint submission is available. With: Three responses to the OSM RFP were submitted. In September 2008, the RFP was opened for further letters of intent (LOI), and some additional LOIs have been received. New submissions will be made early in 2009. Given the terms of the RFP and the content of submissions received so far, it is not anticipated that mapping of concepts will be difficult, but suggestions for reconciliation of the OSM model with the Business Motivation Model will be deferred until: · Either, a draft of a single joint submission is available · Or, a single submission has been accepted by the OMG In Annex H (page 103) Replace: BPDM Business Process Definition Metamodel, OMG RFP and responses, available (to OMG members) from www.omg.org With: BPDM Business Process Definition Metamodel, OMG specification, available from www.omg.org After BPDM, add: BPMN Business Process Modeling and Notation, OMG specification, available from www.omg.org End of changes Actions Taken: 9 January 2007: received issue 13 November 2008: agreed to create spin-off issues for resolution when BPMN 2.0 and OSM are available.
Actions taken:
January 9, 2007: received issue
July 23, 2009: closed issue

Discussion:
BPDM (08-05-07.pdf) has been recast as the common infrastructure for business process definition. It now does not explicitly define 'process' or mention 'activity', which in BMM 1.0 was taken as the BPDM concept that most closely matched the BMM concept of business process (see BMM figure F.2). 
An enterprise that uses the OMG family of business process modeling specifications will probably model its business processes in BPMN. In its BMM, referenced business processes will be in BPMN models. So the BMM specification should be referring to BPMN rather than BPDM. 
As of 10 November 2008, there are two contending submissions for BPMN 2.0, with BPDM providing the metamodel for one of them. BMM needs a neutral reference to 'business process' until this situation is resolved. 
The definition proposed is from the BPMN Version 1.2 Beta 3 specification (08-02-07.pdf), which  is publicly available from the OMG web site. The definition is taken from the first two paragraphs of clause 8.6 (Process) rather than the glossary entries for 'business process' and 'process', which are diagram-oriented and quite sparse. 
OSM has been reopened for LOI, and new submissions will be invited. BMM needs a neutral reference to 'organization unit' until OSM submissions are further developed.


Issue 11510: Restore Primary Reading to "Formulated Based On" Fact Type (bmm-rtf)

Click
here for this issue's archive.
Source: Business Rule Solutions, LLC (Ms. Keri Anderson Healy, keri_ah(at)mac.com)
Nature: Uncategorized Issue
Severity:
Summary:
Source: BRG
Keri Anderson Healy, Ronald G. Ross
Summary:
The 07-08-06 version of BMM now reflects a 'forward' (primary) reading of a fact type that differs from business intent of this association, as expressed in both the BRG BMM and the prose for this assocation (see 8.2.6 Directive, first paragraph on p. 30 (PDF p. 40)).
It is also possible for the Courses of Action to be formulated based on Directives. For example, the Tactics 'Comply with manufacturer's maintenance schedules' and 'Equalize use of cars across rentals so that mileage is similar for cars of the same car group and age' are both formulated based on the Business Policy 'Depreciation of cars must be minimized'. The Directive thereby serves as the source of the Course of Action.
Given an understanding of how the BRG developed the prose reading of a model, it is clear which reading of this fact type is the intended primary reading.  Here is the mechanistic process that was generally applied:
·	Express the fact type in a prose sentence that states the forward-reading's first concept as the subject, the primary reading phrase as the verb, and the forward-reading's second concept as the object of the sentence.
·	Give example(s).
·	Optionally, state the secondary reading.  (Note:  when the secondary reading is simply the passive form, omit.)
From this, it is evident that the intended forward (primary) reading of this fact type is:
course of action is formulated based on directive
Indeed, this is the way the entry appeared in an early version of Clause 9 (e.g., dated Aug. 22, 2006).
Changing the reading of this fact type to have 'directive' be the subject loses an important part of the business message of what is going on in this part of the model.  There are two potential relationships between a course of action and a directive, each with a different 'subject', to yield a kind of back-and-forth synergy between the concepts.  Depicting the same subject for both fact types loses this part of the message.
Resolution:
Restore the original designation of which reading is "primary" so that both the Concepts Catalog entry and the UML derivitaves are correct and consistent with the prose and the business intent of this fact type.
Revised Text:
In 9.1, p. 59 (PDF p. 69), change the entry that currently reads:
directive is source of course of action
	Synonymous Form course of action is formulated based on directive 
to read:
course of action is formulated based on directive
	Synonymous Form directive is source of course of action 
In 9.4, p. 67 (PDF, p. 77), change the line that currently reads:
directive is source of course of action 	DirectiveIsSourceOfCourseOfAction 
to read:
course of action is formulated based on directive 	CourseOfActionIsFormulatedBasedOnDirective 
In 9.5, p. 68 (PDF, p. 78), change the line that currently reads:
directive is source of course of action 	baseDirective 	derivedCourseOfAction  
to read:
course of action is formulated based on directive  	derivedCourseOfAction	baseDirective 

Resolution: Restore the original designation of which reading is "primary" so that both the Concepts Catalog entry and the UML derivatives are correct and consistent with the prose and the business intent of this fact type.
Revised Text: In 7.5 (page 18 of 08.08.02.pdf) Replace figure 7.1 with a new diagram in which the association name 'DirectiveIsSourceOfCourseOfAction' is replaced by 'CourseOfActionIsFormulatedBasedOnDirective' In 8.2.6 (page 31 of 08.08.02.pdf) Replace figure 8.8 with a new diagram in which the association name 'DirectiveIsSourceOfCourseOfAction' is replaced by 'CourseOfActionIsFormulatedBasedOnDirective' In 9.1 (page 63 of 08.08.02.pdf) Replace the entry that reads: directive is source of course of action Synonymous Form: course of action is formulated based on directive With: course of action is formulated based on directive Synonymous Form: directive is source of course of action [and move it to its correct alphabetic position] In 9.4 (page 70 of 08.08.02.pdf) Replace the entry that reads: directive is source of course of action DirectiveIsSourceOfCourseOfAction With: course of action is formulated based on directive CourseOfActionIsFormulatedBasedOnDirective [and move it to its correct alphabetic position] In 9.5 (page 70 of 08.08.02.pdf) Replace the entry that reads: directive is source of course of action baseDirective derivedCourseOfAction With: course of action is formulated based on directive derivedCourseOfAction baseDirective End of changes Actions Taken: Submitted as an urgent issue while the FTF report was being considered by the AB Deferred to RTF by the AB Notes: Because this was submitted after the FTF report, it appears in the issues log as an FTF issue, but does not appear in the FTF report.
Actions taken:
September 23, 2007: received issue
July 23, 2009: closed issue

Issue 11695: class diagram issue (bmm-rtf)

Click
here for this issue's archive.
Nature: Revision
Severity: Significant
Summary:
Class diagrams in Business Motivation Model show association names where we expect role names as per UML specifications. This is misleading. Drawing Fig 8.2 on Star UML produced the following code: public class Vision { public Goal amplified_by; } public class Goal { public Vision amplifies; } 

Resolution:
Revised Text:
Actions taken:
November 29, 2007: received issue
July 23, 2009: closed issue

Discussion:
The conventions for association names and association end names in BMM were resolved in the FTF (Issues 10090, 11282) and included in the metamodel.
Disposition:	Closed without change


Issue 12955: BMM section 7.3.6 - clarification needed (bmm-rtf)

Click
here for this issue's archive.
Nature: Clarification
Severity:
Summary:
I am working on risk Assesment metamodel from "UML Profile for Modeling Quality of Service and Fault Tolerance Characteristics and Mechanisms v1.1" on the page 49 there is description of SWOT (chapter 11.1.2). It says that SWOT elements are directly connected to EnterpriseAsset metaclass. It looks that the we have the similar situation in BMM specification where OrganisationUnit makes assessment and on the other hand OrganizationUnit is responsible for asset. But there is not direct connection between Asset (EnterpriseAsset) and Assesment like in "UML Profile for Modeling Quality..."

Resolution:
Revised Text:
Actions taken:
October 13, 2008: received issue
July 23, 2009: closed issue

Discussion:
Discussion:
In BMM, Assessment is related to Asset, not directly, but via a Course of Action that deploys the Asset. 
Disposition:	Closed, no change


Issue 13059: Category of Category (bmm-rtf)

Click
here for this issue's archive. Click here for this issue's attachments.
Source: Rule ML Initiative (Mr. John Hall, john.hall(at)modelsystems.co.uk)
Nature: Enhancement
Severity: Minor
Summary:
Categorization (of Assessment, Influencer and Influencing Organization) would be much more flexible, with very limited impact on the metamodel,  if the BMM supported categories of categories.
Suggested by Ed Barkmeyer (NIST) and supported by John Hall (Inferware, Model Systems) and Andy Evans (Xactium)
 
Resolution:
Add the following associations
Association	Location	Page
Broader Organization Category categorizes Narrower Organization Category	figure 7.3figure 8.129.19.5	18446673
Also add text "Organization categories may themselves be categorized in broader categories; a narrower category may be included in more than one broader category"	8.4.3, following 3rd paragraph after figure 8.12	
Broader Influencer Category categorizes Narrower Influencer Category	figure 7.3figure 8.129.19.5	18446573
Also add text "Influencer Categories may themselves be categorized in broader categories; a narrower category may be included in more than one broader category"	8.4.2 following first sentence	39
Broader Assessment Category categorizes Narrower Assessment Category	figure 7.3figure 8.179.19.5	18476072
Also add text "Categories of assessment may themselves be categorized in broader categories; a narrower category may be included in more than one broader category"	8.4.6.2 following figure 8.17	47
Discussion:
No attempt has been made to optimize or generalize the 'category of category' pattern, since the semantics of the three occurrences are local, e.g. an Assessment Category can categorize other Assessment Categories, but not Influencer Categories or Organization Categories.  
Revised Text:

Resolution: Add the following associations to the BMM: Broader Organization Category categorizes Narrower Organization Category Broader Influencer Category categorizes Narrower Influencer Category Broader Assessment Category categorizes Narrower Assessment Category
Revised Text: In 7.5 (page 18) Replace figure 7.3 with a new one that includes the associations: Broader Organization Category categorizes Narrower Organization Category Broader Influencer Category categorizes Narrower Influencer Category Broader Assessment Category categorizes Narrower Assessment Category In 8.4.2 (page 39) After the first sentence add: Influencer Categories may themselves be categorized in broader categories; a narrower category may be included in more than one broader category In 8.4.3 (page 44) Following 3rd paragraph after figure 8.12 add Organization categories may themselves be categorized in broader categories; a narrower category may be included in more than one broader category Replace figure 8.12 with a new one that includes the associations: Broader Organization Category categorizes Narrower Organization Category Broader Influencer Category categorizes Narrower Influencer Category In 8.4.6.2 (page 47) Replace figure 8.17 with a new one that includes the association: Broader Assessment Category categorizes Narrower Assessment Category After figure 8.17, add: Categories of assessment may themselves be categorized in broader categories; a narrower category may be included in more than one broader category In 9.1 after "assessment category categorizes assessment" (page 60) add broader assessment category General Concept: assessment category Concept Type: role narrower assessment category General Concept: assessment category Concept Type: role broader assessment category categorizes narrower assessment category In 9.1 after "influencer category categorizes influence" (page 65) add broader influencer category General Concept: assessment category Concept Type: role narrower influencer category General Concept: assessment category Concept Type: role broader influencer category categorizes narrower influencer category In 9.1 after "organization category categorizes influencing organization" (page 66) add broader organization category General Concept: assessment category Concept Type: role narrower organization category General Concept: assessment category Concept Type: role broader organization category categorizes narrower organization category In 9.4 in the appropriate alphabetic positions, add broader assessment category categorizes narrower assessment category BroaderAssessmentCategoryCategorizesNarrowerAssessmentCategory broader influencer category categorizes narrower influencer category BroaderInfluencerCategoryCategorizesNarrowerInfluencerCategory broader orgnization category categorizes narrower organization category BroaderOrganizationCategoryCategorizesNarrowerOrganizationCategory In 9.5 in the appropriate alphabetic positions, add broader assessment category categorizes narrower assessment category broaderAssessmentCategory narrowerAssessmentCategory broader influencer category categorizes narrower influencer category broaderInfluencerCategory narrowerInfluencerCategory broader orgnization category categorizes narrower organization category broaderOrganizationCategory narrowerOrganizationCategory End of changes
Actions taken:
November 10, 2008: received issue
July 23, 2009: closed issue

Discussion:
No attempt has been made to optimize or generalize the 'category of category' pattern, since the semantics of the three occurrences are local, e.g. an Assessment Category can categorize other Assessment Categories, but not Influencer Categories or Organization Categories.


Issue 13060: Internal and External Influencers (bmm-rtf)

Click
here for this issue's archive. Click here for this issue's attachments.
Source: Rule ML Initiative (Mr. John Hall, john.hall(at)modelsystems.co.uk)
Nature: Enhancement
Severity: Significant
Summary:
Description:
'Internal' and 'external' categories of 'influencer' are:
·	A fundamental categorization for business motivation, 
·	Relevant to all organizations
They should be brought back into the normative model. 
Suggested by Ed Barkmeyer (NIST). 
Resolution:
Add specializations 'internal influencer' and 'external influencer' of 'influencer' to figure 7.3 (page 18).
Replace "An enterprise can define whatever Influencer Categories it requires" at the beginning of 8.4.2 (page 39) with the following:
"Influencers impact an enterprise's employment of means or achievement of ends. There are two built-in categories:
·	External: an influencer that is outside the enterprise's organizational boundaries 
·	Internal: an influencer from within the enterprise. 
Beyond these, an enterprise can define whatever Influencer Categories it requires"
Add "(built into BMM)" after "Internal/External" in the second bullet point below figure G2 (page 98)
Move the definitions of internal influencer and external influence from Annex G (page 101) to Clause 9 (page 65) and replace them on page 101 with:
"The categories internal influencer and external influencer are built-in to BMM. 
Categories of external influencer include: competitor; customer; environment; partner; goal
Categories of internal influencer include: assumption; corporate value; habit; infrastructure; issue, management prerogative, resource"
Discussion:
This is simply a change of BMM scope, bringing back into scope two concepts that were excluded in the FTF.   

Resolution: Bring internal influencer and external influencer back into the normative model.
Revised Text: This is simply a change of BMM scope, bringing back into scope two concepts that were excluded in the FTF. Revised Text: In 7.5 (page 18) Replace figure 7.3 with a new one that includes internal influencer and external influencer as specializations of influencer. At the beginning of 8.4.2 (page 39) Replace: An enterprise can define whatever Influencer Categories it requires. Enterprises that do not have a preferred set of categories may choose to use the default set provided in Annex G, modifying and extending it as required. This default set is used for examples and discussion in this specification. It provides: · Two broad Influencer Categories: External Influencer and Internal Influencer · A set of general categories It suggests that each Influencer is categorized as (at least) one of the general categories and as either internal or external, as described in the following tables. With: Influencers impact an enterprise's employment of means or achievement of ends. There are two built-in categories of influencer: · External: an influencer that is outside the enterprise's organizational boundaries · Internal: an influencer from within the enterprise. Beyond these, an enterprise can define whatever Influencer Categories it requires. Enterprises that do not have a preferred set of categories may choose to use the default set provided in Annex G, modifying and extending it as required. This default set provides general categories that are used for examples and discussion in this specification. It is suggested that each Influencer is categorized as (at least) one of the general categories and as either internal or external, as described in the following tables. In the second bullet point below figure G2 (page 98) Add "(built into BMM)" after "Internal/External" In 9.1, after 'influencer' (page 64), add external influencer Definition influencer outside an enterprise's organizational boundaries that can impact its employment of means or achievement of ends Categories of external influencer might include: competitor; customer; environment; partner internal influencer Definition influencer from within an enterprise that can impact its employment of means or achievement of ends Categories of internal influencer might include: assumption; corporate value; habit; infrastructure; issue, management prerogative, resource In Annex G (page 101) replace the definitions of 'internal influencer' and 'external influencer' with: Categories internal influencer and external influencer are built into BMM. Categories of external influencer include: competitor; customer; environment; partner Categories of internal influencer include: assumption; corporate value; habit; infrastructure; issue, management prerogative, resource
Actions taken:
November 10, 2008: received issue
July 23, 2009: closed issue