Purpose The purpose of the Telecom Reference Model (TRM) Team is to develop a reference model for business architecture in multi-national Communication Service Providers (CSPs) operating in regulated markets to give these organizations a coherent starting point for their adoption of business architecture.  Scope 1. A multinational CSP in the context of the TRM covers any Enterprise which provides communication services. This includes voice, data, and media services together with network and device provisioning. 2. The TRM will cover the creation and administration of CSP related products and services utilized by customers, both individual consumers as well as businesses. 3. The scope of the TRM includes ecosystems in which a multinational CSP operates. This includes providing the services themselves or working with suppliers to, for example, physically lay cables and fiber, provide communication infrastructure, devices, and customer equipment, or deliver broadcast media content, broadband, and mobile services. 4. The scope of the TRM will support all CSP business environments; single nation / market to multinational / multi-market and single product / multi-product. 5. Create mappings of capabilities, value streams, organization, and stakeholders sufficient to provide a baseline or starting point for organizations to launch or mature their business architecture efforts. 6. Identify approaches that organizations can take when adopting the model, including likely permutations or customizations. 7. Focus on multi-national CSP specific business architecture reference model content while engaging with and incorporating cross-industry reference model content form the Common Reference Model.  Goals 1. Expedite multi-national CSP adoption and proliferation of business architecture through an industry reference model. 2. Enhance the utility of and conformance to the BIZBOK® Guide 3. Publish readily consumable reference model content that can be adapted and customized by members and scaled to support the transition between various CSP business environments, including, but not limited to, single nation / market to multinational / multi-market, single product / service to multi-product / multi-service, and vice-versa. 4. Extend the core capabilities of the business architecture practitioner by adding the ability to consume, integrate and leverage the reference business architecture model to create organization-specific models. 5. Develop and foster a business architecture community of experts to enable and enhance best practices in multi-national CSPs. 6. Engage and inform Business Architecture Guild members on the topic of business architecture for multinational CSPs.  Deliverables 1. The team Charter 2. Annual roadmap of deliverables 3. Scope definition refinements of the initial TRM 4. Upon acceptance of the scope proposition, define deliverables to include: a. Roadmap and timeline of deliverables and milestones b. Formal reference model packaged for member use including: * Capability map * Value streams * Information map * Stakeholder map * Organization map * Cross-mappings * Extended domain mappings: Product map * Policy map 1. New or updated BIZBOK® Guide section in Part 8 2. Agenda and materials for Guild Workshops (based on need and Guild scheduling) 3. Webinar deck and presentation for Business Architecture Guild monthly webinars (to be scheduled with the team)  Qualifications This team assumes that a team member has two categories of qualifications for membership. 1. Team members have a background in the vertical industry or are currently employed within this industry. This means that the team member brings industry-specific expertise and/or a vested interest in establishing a reference model for in-house use. 2. Team members will have experience in formal value stream, capability, and other business architecture domain mapping categories, or, the team member has minimally read BIZBOK® Guide sections 1, 2.2, 2.4, and other sections as may apply to the work underway, and has viewed the latest value stream mapping and capability mapping webinars on the Guild site.  In summary, a team member will have experience or be working in the CSP vertical industry, and have experience in or has familiarized themselves with basic mapping principles, guidelines, and best practices as defined by the Guild.  Expectations The expectations for team members are as follows: 1. Team members will participate in virtual team meetings as appropriate to team needs and scheduling commitments where missing meetings on a continuing, extended basis will result in being removed from the team 2. Team members will contribute content to various deliverables as determined by the team and the team leadership 3. As appropriate to the prior expectations, team members will be able to dedicate a minimum of 2 hours per week (or more as need and timing determines)  Duration Indefinite period of time but foreseen to be on a continuing basis.