<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="part2stratml.xsl"?>
<PerformancePlanOrReport xmlns="urn:ISO:std:iso:17469:tech:xsd:PerformancePlanOrReport" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

 xsi:schemaLocation="urn:ISO:std:iso:17469:tech:xsd:PerformancePlanOrReport http://stratml.us/references/PerformancePlanOrReport20160216.xsd" Type="Strategic_Plan"><Name>Business Centric Methodology (BCM) Creating practical tools for business integration</Name><Description>The BCM Foundation -- Starting from a perspective of semantic relationships, BCM aims to enable business collaboration with a set of tools that help business groups to work together for mutual benefit. The aim is to provide a foundation for well-defined interaction among groups that may be accustomed to differing business vocabularies and patterns of behavior. </Description><OtherInformation>The BCM approach has developed its own version of a layered architecture ... which also defines a process for moving from fundamental business concepts to the implementation of business and technical interoperability requirements.
This builds on a long tradition of efforts to integrate business strategies and needs with management of the changing information technology infrastructure. The emphasis here, however, is on requirements for interchange among Communities of Interest. </OtherInformation><StrategicPlanCore><Organization><Name>Organization for the Advancement of Structured Information Standards</Name><Acronym>OASIS</Acronym><Identifier>_81300f81-424c-472b-bae9-f7f70b7420b4</Identifier><Description/><Stakeholder StakeholderTypeType="Generic_Group"><Name>Business Centric Methodology Technical Committee</Name><Description> </Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Mike Lubash</Name><Description>Co-Chair</Description></Stakeholder><Stakeholder StakeholderTypeType="Person"><Name>Bruce Peat</Name><Description>Co-Chair</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Business Groups</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Businesses</Name><Description>Business Impact -- 
* Reduced time-to-market - rapid response changing business requirements.
* Reduced cost of adaptation to changing market and technical conditions.
* Ease of negotiation for business and technical coordination.
* Reuse of knowledge, people, capital assets across business units and
processes.
* Visibility of business capabilities to stakeholders.
* Integration of performance measures with change management and investment strategies.
* Ability to prioritize investment and management attention based on
business impact.
* Reduced cost and complexity through elimination of redundant business
processes and technical assets.</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Technicians</Name><Description>Technical Impact -- 
* Low-cost adaptation to new technologies.
* Implementation of metadata management and semantic mapping capabilities.
* Ability to redistribute services among business and technical communities.</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Customers</Name><Description>Customer Impact -- 
* Customer empowerment – BCM enables customer to be both consumer of business services and expert creator of business services.
* Ability for business services to adapt to real-time customer requirements. </Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Communities of Interest</Name><Description>The BCM approach builds on a number of core concepts. Among the most important is that of Community of Interest. This concept follows from the recognition (validated by formal network theory) that interacting entities, whether they be people, organizations or technical systems, tend to coalesce in groups with common characteristics, such as purpose, vocabulary and behavior. In a business environment, the communities may be defined by formal or informal organizational structures.
The unique features that define one community, however, may also act as barriers to interaction with other communities. The BCM approach addresses these inhibitors to interaction from an integrated business perspective. Working from a formal understanding of the “ontologies” that characterize the communities, the BCM approach enables the definition of collaborative business patterns, which support contracts, the vehicle for formal interaction among the interacting communities. </Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Large Organizations</Name><Description>BCM in Practice -- The BCM approach can have its greatest impact in organizations that are composed or multiple business units or which must operate across an extended business network.
Complexity in the structure of the business relationships is the rule not the exception. The need for improved integration across business boundaries is widespread in both the public and private sectors.
A few examples:</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Financial Services</Name><Description>More often than not, financial services companies have grown through mergers and acquisitions. They often consist of multiple service organizations with overlapping and duplicative functions and services. The financial services company has typically invested a great deal in its ability to collaborate with sister financial institutions like banks, regulatory agencies and other service organizations. To reduce time-to-market for new services and create more flexible  interactions with customers, many of these companies are struggling to create workable mechanisms for interoperability and more effective delivery of services to customers.
BCM offers a path to meeting those objectives. </Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Public Sector</Name><Description>Like financial services, information systems within public sector organizations have grown as stove-piped operations within isolated business units.</Description></Stakeholder><Stakeholder StakeholderTypeType="Organization"><Name>Office of Management and Budget</Name><Description>Programs such as the federal enterprise architecture effort under the Office of Management and Budget (OMB) and parallel initiatives within the Defense Department have established broad goals for interoperability and reuse of business services, data, and technology components. The challenge is to create the business framework to focus investment on feasible initiatives within limited budgets. The BCM offers one means to meet those objectives.</Description></Stakeholder><Stakeholder StakeholderTypeType="Organization"><Name>Defense Department</Name><Description/></Stakeholder><Stakeholder StakeholderTypeType="Organization"><Name>IRS</Name><Description>As one example of a mechanism that implements semantic transformation and mediation, the IRS has a business relationship with millions of customers it hardly knows. It imposes highly complex business rules on customers of varying business skills. That relationship is mediated through the common language of tax preparation software (and the accounting community). The best of that breed transforms the complex language and business rules of the IRS into a form that is meaningful to a broad set of customers.</Description></Stakeholder><Stakeholder StakeholderTypeType="Organization"><Name>Norway</Name><Description>There are other examples of application of BCM principles, such as the pilot of government service delivery under the Electronic Process program (EPR) in Norway.
The program addresses service delivery requirements in diverse domains such as construction and healthcare and provides integrated mechanisms for information access and collaboration.</Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>U.S. Federal Sector</Name><Description>The EPR effort represents a model of how to combine practical implementation with standards development that enables replication of that experience in multiple environments. Similar initiatives are being undertaken in the U.S. federal sector. </Description></Stakeholder><Stakeholder StakeholderTypeType="Generic_Group"><Name>Pharmaceutical Industry</Name><Description>Pharmaceutical Research -- The pharmaceutical industry faces a challenge of reducing time-to-market through more efficient clinical trials. But the culture of the research and IT communities is distinct from the clinics in which the trials are carried out. The industry is also faced with a highly diverse set of communities of interest, each research specialty characterized by its own set of jargon, ways of doing business, and set of professional practices. Getting drugs to market faster is worth billions of dollars to the industry. That goal is impeded by challenges of semantic transformation and other issues of business interoperability. The BCM approach and complementary tools offer a path out of that quagmire.</Description></Stakeholder></Organization><Vision><Description>Business groups to work together for mutual benefit</Description><Identifier>_6b2c06ca-aa65-11ea-9885-42f42983ea00</Identifier></Vision><Mission><Description>To enable business collaboration</Description><Identifier>_6b2c0990-aa65-11ea-9885-42f42983ea00</Identifier></Mission><Value><Name>Coordination</Name><Description>Benefits of BCM -- Organizations that follow the BCM process will experience a number of benefits, some of which overlap with the effects of other enterprise architecture approaches and some of which are unique to BCM. In general terms, the BCM methods aim to implement conditions that smooth business operations among multiple communities. 
These conditions include: </Description></Value><Value><Name>Strategic Alignment</Name><Description>Alignment of priorities and interests among multiple business units or communities.</Description></Value><Value><Name>Priorities</Name><Description/></Value><Value><Name>Interests</Name><Description/></Value><Value><Name>Visibility</Name><Description>Visibility and understandability of technical and business requirements.</Description></Value><Value><Name>Understandability</Name><Description/></Value><Value><Name>Predictability</Name><Description>Predictable and effective orchestration of business and technical relationships among business parties. </Description></Value><Value><Name>Orchestration</Name><Description/></Value><Value><Name>Relationships</Name><Description/></Value><Value><Name>Interoperability</Name><Description>Alignment of business and technical strategies for interoperability.</Description></Value><Value><Name>Negotiation</Name><Description>Support for negotiation mechanisms and contract monitoring among business parties.</Description></Value><Value><Name>Monitoring</Name><Description/></Value><Value><Name>Flexibility</Name><Description>Loose coupling between business capabilities and technical implementation.</Description></Value><Value><Name>Adaptability</Name><Description>Rapid adaptation to evolving business and technical integration standards.</Description></Value><Value><Name>Standardization</Name><Description>BCM and the Standards Process -- A primary guiding principle of the BCM
approach is the use of open, transparent
communication and standards.</Description></Value><Value><Name>Openness</Name><Description/></Value><Value><Name>Transparency</Name><Description/></Value><Value><Name>Communication</Name><Description/></Value><Value><Name>Interaction</Name><Description>The BCM products have evolved though interaction with a number of other technical committees and continue to profit from contributions within and beyond the standards development communities. In particular, there is ongoing collaboration with work on registries, ebXML, e-government and other efforts to implement standards, technologies, and practices that promote interoperable business operations. </Description></Value><Goal><Name>Concepts</Name><Description>Understand the semantics of the business.</Description><Identifier>_6b2c0ab2-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>The Conceptual layer improves the understanding of the semantics by aligning the terminology of the business and uncovers the operational meaning of the business vocabulary. In this layer, the business managers determine the solution requirements and use BCM templates to acquire information regarding business collaboration needs. The relevant data includes information on business goals, project boundaries, the participants, the Community of Interest, use cases, and business events.</OtherInformation><Objective><Name>Goals</Name><Description>Determine the business goals.</Description><Identifier>_6b2c0b98-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Boundaries</Name><Description>Establish the project boundaries.</Description><Identifier>_6b2c0c6a-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>1.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Participants</Name><Description>Identify the project participants.</Description><Identifier>_6b2c0d32-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>1.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>COIs</Name><Description>Identify the Community of Interest.</Description><Identifier>_6b2c0e40-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>1.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Use Cases</Name><Description>Document the use cases.</Description><Identifier>_6b2c0f4e-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>1.5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Events</Name><Description>Document the relevant business events.</Description><Identifier>_6b2c102a-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>1.6</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Goals</Name><Description>Understand the business goals.</Description><Identifier>_6b2c1106-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>The Business Layer develops an understanding of the core business goals that the “preferred” business objects must accomplish and constrains them according to defined business processes and patterns. This layer captures formal business rules and identifies opportunities for reuse of process components and related business domain knowledge.</OtherInformation><Objective><Name>Business Rules</Name><Description>Capture business rules.</Description><Identifier>_6b2c11d8-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>2.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Processes</Name><Description>Identify opportunities for reuse of process components.</Description><Identifier>_6b2c12aa-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>2.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Knowledge</Name><Description>Identify opportunities for reuse of business domain knowledge.</Description><Identifier>_6b2c1390-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>2.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Implementation</Name><Description>Define potential implementation options.</Description><Identifier>_6b2c1462-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>The Extension Layer defines potential implementation options and provides the view needed for mapping the required interoperability requirements to industry practices, organizations, standard bodies, and internal legacy system formats.</OtherInformation><Objective><Name>Practices</Name><Description>Map interoperability requirements to industry practices.</Description><Identifier>_6b2c1534-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Organizations</Name><Description>Map interoperability requirements to organizations.</Description><Identifier>_6b2c1674-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Standards Bodies</Name><Description>Map interoperability requirements to standard bodies.</Description><Identifier>_6b2c1750-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.3</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>Standards Bodies</Name><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Formats</Name><Description>Map interoperability requirements to internal legacy system formats.</Description><Identifier>_6b2c182c-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.4</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Templates</Name><Description>Capture information in a way that can be reused over time and among participating organizations.</Description><Identifier>_6b2c191c-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name>BCM Community</Name><Description/></Stakeholder><OtherInformation>How to use BCM BCM Implementation Process and Supporting Tools -- The BCM approach is designed to be more than a vision for inter-enterprise operations. It aims to become a repository of methods and tools for implementing the envisioned world of interoperability. The BCM community is actively developing tools that assist with the achievement of the BCM implementation framework by working closely with selected industry initiatives. A growing set of templates for captures critical information in a way that can be reused over time and among participating organizations. The templates are designed to create a consistent body of information for all layers of the business architecture, from business ontology to contractual relationships among individuals and communities. The templates work with familiar desktop tools and do not require specialized software.
These templates include:</OtherInformation></Objective><Objective><Name>Strategies</Name><Description>Implement strategies for interoperability.</Description><Identifier>_6b2c19f8-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.1</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>A defined process for moving from conceptual semantic and business foundations to implementation of strategies for interoperability.</OtherInformation></Objective><Objective><Name>Capabilities</Name><Description>Analyze and reuse business and technical capabilities.</Description><Identifier>_6b2c1ade-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.2</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>A modular approach to analysis and reuse of business and technical capabilities.</OtherInformation></Objective><Objective><Name>Patterns</Name><Description>Capture replicable knowledge.</Description><Identifier>_6b2c1bd8-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.3</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Use of patterns to capture replicable knowledge.</OtherInformation></Objective><Objective><Name>Metadata</Name><Description>Manage metadata.</Description><Identifier>_6b2c1cbe-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.4</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Implementation of metadata management.</OtherInformation></Objective><Objective><Name>Standards</Name><Description>Apply standards for interoperability and contracts.</Description><Identifier>_6b2c1da4-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.5</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Interoperability standards / contracts.</OtherInformation></Objective><Objective><Name>Negotiations</Name><Description>Negotiate among COIs.</Description><Identifier>_6b2c1e9e-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.6</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Inter-community negotiation mechanisms.</OtherInformation></Objective><Objective><Name>Performance</Name><Description>Monitor and manage performance.</Description><Identifier>_6b2c206a-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.7</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Performance monitoring and management tools.</OtherInformation></Objective><Objective><Name>Artifacts</Name><Description>Manage artifacts.</Description><Identifier>_6b2c216e-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.8</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Artifact management for semantic interoperability.</OtherInformation></Objective><Objective><Name>Registry</Name><Description>Use a standard registry.</Description><Identifier>_6b2c2272-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.9</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Use of a standard registry to enable access to processes and other business and technical artifacts.</OtherInformation></Objective><Objective><Name>Other Artifacts</Name><Description>Use other artifacts.</Description><Identifier>_6b2c236c-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.10</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Specific data dictionaries, lexicons, taxonomies, thesauri, topic maps and ontologies.</OtherInformation></Objective><Objective><Name>Data Dictionaries</Name><Description>Use data dictionaries.</Description><Identifier>_6b2c245c-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.10.1</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Lexicons</Name><Description>Use lexicons.</Description><Identifier>_6b2c256a-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.10.2</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Taxonomies</Name><Description>Use taxonomies.</Description><Identifier>_6b2c2664-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.10.3</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Thesauri</Name><Description>Use thesauri.</Description><Identifier>_6b2c275e-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.10.4</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Topic Maps</Name><Description>Use topic maps.</Description><Identifier>_6b2c286c-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.10.5</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Ontologies</Name><Description>Use ontologies.</Description><Identifier>_6b2c2970-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>3.5.10.6</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Interactions</Name><Description>Support business interactions.</Description><Identifier>_6b2c2a6a-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>The Implementation Layer provides the specific mechanisms that support business interactions among communities. The implementation will follow from templates based on existing standards, proven technology and reusable business components. </OtherInformation><Objective><Name>Standards</Name><Description>Use existing standards.</Description><Identifier>_6b2c2b82-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>4.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Technology</Name><Description>Use proven technology.</Description><Identifier>_6b2c2d80-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>4.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Components</Name><Description>Reuse available business components.</Description><Identifier>_6b2c2e8e-aa65-11ea-9885-42f42983ea00</Identifier><SequenceIndicator>4.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate/><EndDate/><PublicationDate>2020-06-09</PublicationDate><Source>https://www.oasis-open.org/committees/download.php/5809/BCM%20brochure%20V1.pdf</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></PerformancePlanOrReport>