A BKPMNPackage is mechanism for packaging and distributing a set of BPM+ models (i.e., the knowledge). A BKPMNPackage references separate, but connected BPM+ models (BPMN Processes, CMMN Cases, and DMN Decision Services). It should be noted that BKPMN is focused solely on the BMI behavioral standards. A BKPMNPackage also contains a Data Item library for the data that will be used by the BPM+ models (the proposed standard SDMN defines the elements of the Data Item library). This is a list of the BKPMNVocabularies that are included in the BKPMNModel. This is a subset of the list of SCEVocabularies. This is a list of the BKPMNDefinitions that are included in the BKPMNModel. This is a list of the BKPMNInstances that are included in the BKPMNModel. The Manifest is a list of files that contain the components of the BKPMNModel. This includes the files that contains the BPM+ models. The purpose element provides another classification mechanism for the BKPMNPackage. This classification could be used as part of a search for a particular BKPMNPackage, for example. A BKPMNPackage is mechanism for packaging and distributing a set of BPM+ models (i.e., the knowledge). A BKPMNPackage references separate, but connected BPM+ models (BPMN Processes, CMMN Cases, and DMN Decision Services). It should be noted that BKPMN is focused solely on the BMI behavioral standards. A BKPMNPackage also contains a Data Item library for the data that will be used by the BPM+ models (the proposed standard SDMN defines the elements of the Data Item library). The knowledgeElement association ... The BKPMNInstances element is one of the two main containers for the contents of a BPM+ Knowledge Package. It contains a set of PackageElements. The BKPMNInstances element is contained within a BKPMNModel package. The Purpose Enumeration provides a list of options for the purpose attribute of a BKPMNPackage. This list of literals can be extended. A model that can be presented with a visual representation of the breadth and scope of a BKPMNDefinitions in terms of the BPM+ models it contains. It is contained within a BKPMNDefinitions. This is a list of the BKPMNDiagramElements (BKPMNPackageRefs, CaseRefs, ChoreographyRefs, CollaborationRefs, DecisionServiceRefs, and ProcessRefs) that are within the BKPMNDiagram. This is a list of the Connectors that are within the BPMPlusKnowledgeModel. A diagram that provides a visual representation of the breadth and scope of a BKPMNPackage in terms of the BPM+ models it contains. This class is included in the metamodel to serve as a mechanism to group seven other classes and provide a single association for the BKPMNDiagram class. This represents one of the Cases that is part of the BKPMNPackage. In the BKPMN model, it is a reference to a Case within a CMMN file. Element role: startTrigger This identifies the Event that triggers the start of the overall Knowledge Package. This represents the Choreography model that is part of the BKPMNPackage. In the BKPMN model, it is a reference to a Choreography within a BPMN file that can be used in multiple BKPMNPackages. There should be only one Choreography model for a given BKPMNPackage. This represents a Collaboration model that is part of the BKPMNPackage. In the BKPMN model, it is a reference to a Collaboration within a BPMN file that can be used in multiple BKPMNPackages. A Collaboration will be linked to one or more Process elements in a BKPMNPackage. This represents one of the Decision Services that is part of the BKPMNPackage. In the BKPMN model, it is a reference to a Decision Service within a DMN file that can be used in multiple BKPMNPackages. Many BKPMNPackages (particularly in healthcare) will contain the details of the methodology that was used to create the BKPMNPackage. This type of information is also captured in the Pedigree of business elements. We still need to reconcile this… Element role: operationalDocumentRef The implementationType of the referenced OperationalDocumentRef MUST NOT be of the types that are listed as the specializations of the OperationalDocumentRef element, such as BPMN and CMMN, etc. This identifies the URI of the element that the concrete OperationalModelRef represents. The URI will be found in the appropriate model definition file referenced in the Manifest. -- Changed to anyURI after initial submission -- Discuss URI vs QName -- Element role: startTrigger This identifies the Event that triggers the start of the overall Knowledge Package. The Undefined Behavior element is used as a placeholder for one of the other behavioral elements. It is mainly used early in the development of a BKPMNPackage. A specific behavior is known to be part of the pathway, but it is not clear at that point whether the behavior is a Process or a Case. This allows the inclusion of the behavior in the overall context before the modeler is ready to set its type. The Group object is a ModelArtifact that provides a visual mechanism to informally group elements of a diagram. Groups are often used to highlight certain sections of a diagram without adding additional constraints or semantics. The highlighted (grouped) section of the diagram can be separated for reporting and analysis purposes. BKPMN extends the SCE Group element by adding an association to a ParticipantRef. This allows provides the capability for Groups in a BKPMNDiagram to separate the behavioral elements into groups related to a particular participant of the BKPMNPackage behaviors. Element role: participantRef This identifies the Participant within the BKPMNPackagethat is associated with the Group. The GeneralModelRef and BKPMNModelRef elements that are contained within the graphical boundaries of the Group should also be associated with the same ParticipantRef. This identifies the KnowledgeModel element that is at the source end of the ModelElementConnector. This attribute redefines the sourceRef attribute of SCE ElementRelationshipType. This identifies the KnowledgeModel element that is at the target end of the ModelElementConnector. The arrowhead will be at the end of the ModelElementConnector attached to this element. This attribute redefines the targetRef attribute of SCE ElementRelationshipType. Expected element: RelationshipConnector This attribute identifies the outgoing Relationship Connector of the BKPMNPackage. Expected element: RelationshipConnector This attribute identifies the incoming Relationship Connector of the BKPMNPackage. Element role: policyRef This identifies any policies that are related to the BPMPlusModelElement. This identifies the URI of the element that the concrete BPMPlusModelElement represents. The URI will be found in the appropriate model definition file referenced in the Manifest. -- Changed to anyURI after initial submission -- Discuss URI vs QName -- This attribute sets the written language used for the BKPMNPackageSummary. If this attribute is not set, then the setting from the BKPMNPackage element will be used. A Contributor is a person that assisted in the development of the BKPMNPackage. There are different types of Contributors, such as editors, reviewers, etc. This attribute sets the type of contribution provided by the Contributor. See the section below for the information on the ContributorType element. A Participant is distinguished from a Performer. Performers are those resources, often Human, that are responsible for performing activities within a Process or a Case. In a healthcare setting… Element role: policyDocumentRef This identifies the Policy Document (through the PolicyDocumentRef) that contains the Policy element. This document MUST be identified. Note: the publisher will also be found in the Pedigree of the BKPMNPackage, if the Pedigree is being tracked. A LifecycleEvent is a significant circumstance or event, as identified by the BKPMNPackage developer, that occurs during the development of the BKPMNPackage. LifecycleEvent is contained within a BKPMNPackage and can be referenced by a Recommendation. Note: lifecycle events will also be found in the Pedigree of the BKPMNPackage, if the Pedigree is being tracked. Element role: eventRef This relates the BPMN elements, such as Start Evenrts, that are associated with the LifecycleEvent. It is possible that multiple Process Events, across the Processes of the BKPMNPackage, may be associated with the LifecycleEvent. Both EventRefs and MilestoneRefs may be associated with a LifecycleEvent. Element role: milestoneRef This relates the CMMN elements, such as Milestones, that are associated with the LifecycleEvent. It is possible that multiple Case elements, across the Cases of the BKPMNPackage, may be associated with the LifecycleEvent. Both EventRefs and MilestoneRefs may be associated with a LifecycleEvent. An Input represents a key DataItem that is necessary to be present at the start of a performance of a BKPMNPackage. This attribute is optional since a BKPMNPackage can be developed before all the information is available. However, before a BKPMNPackage is considered complete, the DataItemRef for the BKPMNPackageInput should be set (e.g., there should be a Situational Data Model within the BKPMNPackage that contains the referenced Data Item). A BKPMNPackageOutput represents a key Data Item that is a product at the end of a performance of a BKPMNPackage. This attribute is optional since a BKPMNPackage can be developed before all the information is available. However, before a BKPMNPackage is considered complete, the DataItemRef for the BKPMNPackageOutput should be set (e.g., there should be a Situational Data Model within the BKPMNPackage that contains the referenced Data Item). An Effect is some change to the environment or data that may occur when the behaviors of BPM+ Knowledge Package is performed. In the healthcare domain, for example, a reduction in blood pressure may be the effect of the application of a medication. Each BKPMNPackage can contain a list of Effects, which are contained within a BKPMNPackage. This allows the BKPMNPackage modeler to associate various BPMN events or CMMN milestones to the Effect. These events can be used to define a type of lifecycle for the Effect. This identifies any Measures that are defined to determine whether or not the Effect occurs. This element indicates the type of impact that the Effect will have when the behaviors of the BKPMNPackage or Recommendation are executed. An optional text description of the Effect. This is a probability rating that defines how likely the Effect will occur when the behaviors of the owning BKPMNPackage or Recommendation are performed. This identifies the DMN expression that is used to evaluate the Measure. The expression will be contained within a DMN model as part of a Decision or Business Knowledge Model. The MeasureType element provides a connection to an ontology that will define the types of measures that are used in the context of the BPM+ Knowledge Package. includes: quality, process, perception, performance, input Indicates the impact and probability of loss. A RiskFactor can be expressed through an expression (e.g., “Age > 75 years”). The actual expression will be contained within a DMN model as part of a Decision or Business Knowledge Model. This defines the type of risk that is being defined. This provides a description of the RiskFactor. Additional discussion or documentation can be included in the Documentation element. This defines the type of risk that is being defined. Examples of risk types include: fraction-of-incidences hazard-ratio increases-in-incidences relative This references the DecisionServiceRef that will execution the criteria that determines if the current context should be excluded. This references the DecisionServiceRef that will execution the criteria. This is a brief summary of what constitutes the applicability for the BKPMNPackage. Additional description of the applicability can be provided by the Documentation element. This is a brief summary of what constitutes the applicability for the BKPMNPackage. Additional description of the applicability can be provided by the Documentation element. If true, this specifies that this Applicability definition applies to the overall BKPMNPackage rather than a Recommendation. The Manifest lists zero or more BPMN Documents, which are XML documents, usually with the file extension “.bpmn.” Within a single BPMN Document there can be multiple Processes, Choreographies, and/or Collaborations. A BPMNDocumentRef element references the XML document, thus including the BPMN Document in the Manifest. = This provides the list of the BPMN elements that are referenced within the BKPMNPackage. There must be at least one element referenced otherwise the BPMNDocumentRef does not need to be included in the Manifest. The Manifest lists zero or more CMMN Documents, which are XML documents, usually with the file extension “.cmmn.” Within a single CMMN Document there can be multiple Cases. A CMMNDocumentRef element references the XML document, thus including the CMMN Document in the Manifest. This provides the list of the CMMN elements that are referenced within the BKPMNPackage. There must be at least one element referenced otherwise the CMMNDocumentRef does not need to be included in the Manifest. The Manifest lists zero or more DMN Documents, which are XML documents, usually with the file extension “.dmn.” Within a single DMN Document there can be multiple Decision Services. A DMNDocumentRef element references the XML document, thus including the DMN Document in the Manifest. Element role: dmnElementRef This provides the list of the DMN elements that are referenced within the BKPMNPackage. There must be at least one element referenced otherwise the DMNDocumentRef does not need to be included in the Manifest. The Manifest lists zero or more BKPMN Documents, which are XML documents, usually with the file extension “.bkpmn.” Within a single BKPMN Document there will be one BKPMNPackage. A BKPMNDocumentRef element references the XML document, thus including the BKPMN Document in the Manifest. This provides the list of the BKPMN elements that are referenced within the BKPMNPackage. There must be at least one element referenced otherwise the BKPMNDocumentRef does not need to be included in the Manifest. The Manifest lists zero or more MDMI Documents, which are XML documents, usually with the file extension “.mdmi.” Within a single MDMI Document there will be multiple MDMI models. A MDMIDocumentRef element references the XML document, thus including the PPMN Document in the Manifest. Element Role: mdmiElementRef This provides the list of the MDMI elements that are referenced within the BKPMNPackage. There must be at least one element referenced otherwise the MDMIDocumentRef does not need to be included in the Manifest. There are currently 3 classes that are specializations of the DMNElementRef element. Those classes are: DecisionServiceRef, DecisionRef, and ExpressionRef. The Manifest lists zero or more PPMN Documents, which are XML documents, usually with the file extension “.ppmn.” Within a single BKPMN Document there will be one BKPMNPackage. A PPMNDocumentRef element references the XML document, thus including the PPMN Document in the Manifest. Element Role: ppmnElementRef This provides the list of the PPMN elements that are referenced within the BKPMNPackage. There must be at least one element referenced otherwise the PPMNDocumentRef does not need to be included in the Manifest. ResourceRoles are contained within a BPMN Process. ResourceRoles are contained within a BPMN Process. This association provides the list of documents containing BPM+ models or other types of operational models that are part of the BKPMNPackage. This association provides the list of documents containing documents that are used a resource information that help in the understanding and purpose of the BKPMNPackage. It is contained within a Manifest. This association provides the list of BPM+ and other standards that are being used by documents that are part of the Manifest. It is contained within a Profile. The name of the modeling language listed in the Profile. The name must be consistent with the language identified by the languageURI property. The version of the modeling language listed in the Profile. The version must be consistent with the language identified by the languageURI property. The URI to the definition of the ModelingLanguage. The Manifest lists zero or more SDMN Documents, which are XML documents, usually with the file extension “.sdmn.” Within a single SDMN Document there will be one Situational Data Model. A SDMNDocumentRef element references the XML document, thus including the SDMN Document in the Manifest. There should be at least one Situational Data Model in the SDMN document. Otherwise, there is no need for the SDMN document to be in the Manifest. As type of element, OperationslDocumentRefs are not graphically shown on a BKPMNDiagram. The URI where the Operational Document is located. The documentLocation SHALL be specified in a URI format. The implementation kind could be derived from the extension of the target file. E.g., a file with an extension of ".bpmn" would be listed as a BPMN implementation. The specializations of OperationalDocumentRef will derive the implementationKind from the document in the documentLocation. There are currently 6 classes that are specializations of the BPMNElementRef element. Those classes are: ProcessRef, EventRef, CollaborationRef, ChoreographyRef, ResourceRoleRef, and ParticipantRef. These 6 types of BPMN elements have been identified as being relevant for the definition of the BKPMNPackage. The RootElement of BPMN is used in this context to provide the flexibility to extend BKPMN with references BPMN elements that are not on this list. This identifies the BPMN Document (through the BPMNDocumentRef) that contains the BPMN element referenced by the concrete sub-class of this BPMPlusModelElementRef. This document MUST be identified. It is contained within a BKPMNPackage. ResourceRoles are contained within a BPMN Process. There are currently 4 classes that are specializations of the CMMNElementRef element. Those classes are: CaseRef, MilestoneRef, ExitCriterionRef, and CaseRoleRef. Element role: cmmnDocumentRef This identifies the CMMN Document (through the CMMNDocumentRef) that contains the CMMN element referenced by the concrete sub-class of this BPMPlusModelElementRef. This document MUST be identified. There are currently 3 classes that are specializations of the DMNElementRef element. Those classes are: DecisionServiceRef, DecisionRef, and ExpressionRef. These 3 types of DMN elements have been identified as being relevant for the definition of the BKPMNPackage. The DMNElement of DMN is used in this context to provide the flexibility to extend BKPMN with references DMN elements that are not on this list. Element role: dmnDocumentRef This identifies the DMN Document (through the DMNDocumentRef) that contains the DMN element referenced by the concrete sub-class of this BPMPlusModelElement. This document MUST be identified. BKPMN does not directly support the definition of executable expressions. If a BKPMNPackage developer requires an executable expression, then the capabilities of DMN should be used. The BKPMN Expression can then be linked to a DMN Expression that is part of the BKPMNPackage. The expression will be contained within a DMN model as part of a Decision or Business Knowledge Model. The KnowledgeElement abstract class is one of two intermediary classes to help with the organization of multiple elements that are contained within a BKPMNPackage (the other being PackageElement). Instead of creating separate containment associations to BKPMNPackage, there is one containment association from KnowledgeElement to BKPMNPackage and then there are a set of concrete subclasses to KnowledgeElement (which can be seen in the figure below). The class is named KnowledgeElement to indicate that its subclasses are elements that can be categorized as reflecting some aspect of the knowledge that is contained in the BKPMNPackage. The PackageElement abstract class is one of two intermediary classes to help with the organization of multiple elements that are contained within a BKPMNPackage (the other being KnowledgeElement). Instead of creating separate containment associations to BKPMNPackage, there is one containment association from PackageElement to BKPMNPackage and then there are a set of concrete subclasses to PackageElement (which can be seen in the figure below). The class is named PackageElement to indicate that its subclasses are elements that can be categorized as reflecting some aspect of the package itself that may help in the understanding or discovery of the BKPMNPackage. There is currently 1 class that are specializations of the BKPMNElementRef element. That class is: BKPMNPackageRef. This identifies the BKPMN Document (through the BKPMNDocumentRef) that contains the BKPMN element referenced by the concrete sub-class of this BPMPlusModelElementRef. This document MUST be identified. There are currently 2 classes that are specializations of the SDMNNamedElementRef element. Those classes are: DataItemRef, and SituationalDataModelRef.The SDMNElement of SDMN is used in this context to provide the flexibility to extend BKPMN with references SDMN elements that are not on this list. Element role: sdmnDocumentRef This identifies the SDMN Document (through the SDMNDocumentRef) that contains the SDMN element referenced by the concrete sub-class of this BPMPlusModelElementRef. This document MUST be identified. The applicability of a BKPMNPackage is a statement of the conditions that must be met, after a BKPMNPackageStartTrigger occurs, in order for the BKPMNPackage to be applied. This is a list of the key Data Items that are necessary to be present at the start of a performance of a BKPMNPackage. This is a list of the key Data Items that are a product at the end of a performance of a BKPMNPackage. The Effects of a BKPMNPackage are statements as to a change in condition or a result that occurs due to enacting of the behaviors of the BKPMNPackage. These are the significant circumstances or events, as identified by the BKPMNPackage developer, that occur during the enactment of the BKPMNPackage. This identifies BPM+ model elements (e.g., a Process) that is related to the Recommendation. Element role: relatedRecommendation This identifies another Recommendation that is related to this Recommendation. The RecommendationStatus defines how the Recommendation is related to Recommendations the of previous versions of the BKPMPackage. The RecommendationStrength is an evaluation of the confidence that the Recommendation developers have regarding how the Recommendation should be applied.  This is the written narrative of the Recommendation. It will often include “We recommend…” Additional discussion or documentation can be included in the Documentation element. An optional text description of the RecommendationBehavior. The RecommendationStatus defines how the Recommendation is related to Recommendations the of previous versions of the Definitions. Custom enumeration sets can be defined, however, a common list includes: amended; deleted; new-added; new-replaced; not-changed. The RecommendationStrength is an evaluation of the confidence that the Recommendation developers have regarding how the Recommendation should be applied. Custom enumeration sets can be defined, however, a common list includes: strong-against; strong-for; weak-against; weak-for. Narratives are text or video documents that provide supporting information to help understand the behaviors of a BKPMNPackage. They add supporting descriptions that would help someone navigate the models or understand why they are structured the way that they are. As type of element, ResourceDocumentRefs are not graphically shown on a BKPMNDiagram. The URI where the RelatedResourceRef is located. The documentLocation SHALL be specified in a URI format.