Download
1 / 17
180 likes | 201 Views
TMF Information Framework. Chip Srull. Integrated Models and Frameworks. Frameworks provide containment and structure Different models, each developed for a domain/perspective Integrated within framework for alignment and containment Models for each viewpoint, perspective, domain, etc.
E N D
TMF Information Framework Chip Srull
Integrated Models and Frameworks • Frameworks provide containment and structure • Different models, each developed for a domain/perspective • Integrated within framework for alignment and containment • Models for each viewpoint, perspective, domain, etc. • Enterprise architecture & business process models • Conceptual, logical and physical data models • Application architecture and UML models • Integrate domains and transform between perspectives • Data and process and applications align • Context, concept, logic and implementation views sync’d
Integrated Models with Frameworx • Frameworx defines a comprehensive enterprise IT and process architecture that also embraces major IT industry standards such as ITIL and TOGAF. • Business Process Framework (eTOM) is the industry's common process architecture for both business and functional processes • Business and functional processes for telecommunication • Full scope and interactions defined • Information Framework (SID) provides a common reference model to describe management information: • Common model: standardization and reduce complexity • Consistent data use: service providers and business partners • Conceptual Data Models • UML class (domain) diagrams • Application Framework (TAM) provides a common language to describe systems and their functions: • Represents applications aligned to business functions • Provides mapping between eTOM and SID • Integration Framework provides a service oriented integration approach with standardized interfaces and support tools
TMF Frameworx • Frameworx • Is the industry’s most comprehensive business architecture • Provides the flexibility of a vendor and technology-independent blueprint • Allows Service Providers to realize ITIL-compliant implementations • Is fully supported by a range of commercial products • SOA compatible • TM Forum’s Frameworx Integrated Business Architecture provides an industry agreed, service oriented approach for rationalizing operational IT, processes, and systems that enables Service Providers to significantly reduce their operational costs and improve business agility. • Frameworx uses standard, reusable, generic blocks—Platforms and Business Services—that can be assembled in unique ways to gain the advantages of standardization while still allowing customization where necessary.
Information Framework (SID) • Focuses on business entitiesand associated attribute definitions. • Business Entity -- “a thing of interest to the business, such as customer, product, service, or network. Its attributes are facts that describe the entity.” (sound familiar?) • Is fundamentally an Information Model. • Information Model-- “a representation of business concepts, their characteristics and relationships, described in an implementation independent manner.” (sound familiar?) • Entities and models are packaged in a series of documents and modeled in UML. • Provides: • an information/data reference model and a common information/data vocabulary, from a business entity perspective. • the definition of the “things” that are to be affected by the business processes defined in the eTOM. • the model that represents business concepts and their characteristics and relationships, described in an implementation-independent manner. • Designed as a layered framework that partitions the shared information and data into eight high level domains.
Information Framework (SID) • Uses the concepts of domains and ABEs (i.e. sub-domains) to categorize business entities • Developed by the application of data affinity concepts to a telecom enterprise’s processes and data. • High degree of cohesion between entities • Loose coupling between different domains • Top domains are broadly aligned with the eTOM
SAM – SID Mapping • Accounting • Activities and Events • Contact Point • Contracts • Document Management • Geography • People and Organizations • Physical Assets • Roles
SID Common Categories • To ensure consistency, each ABE is aligned with a categorization pattern • Management Entity ABE • Interaction • Configuration • Performance • Test • Trouble Price • Usage • Managed Entity ABE • Strategy and Plan • Managed Entity • Managed Entity Specification
What, Where, Why, When, Who GB922 Addendum 1P, V9.6, p. 6 GB922 Addendum 1L, V3.4, p. 22 GB922 Addendum 1T, V1.4, p. 15 GB922 Addendum 3, V9.5, p. 21
Conceptual Model - Entities • Identity / Party (who) • Individuals & Organizations • Customer (actual or potential) • Supplier • User • Time & Time Period (when) • Calendar • Places / Locations (where) • Locations & Sites • Addresses • Motivation (why) • Business Planning • Work (how) • Plan & Project • Process • Policy (how) • The Business (what) • Agreement & Contract • Product • Service • Resource • Event (when) • Financials (what)
Information Framework (SID) • The top layer (Layer 1) contains domains which are aligned with eTOMlevel 0 concepts • Domain – collection of ABEs associated with a specific mgmt area. • ABE – well-defined set of info and ops that characterize a highly cohesive, loosely coupled set of business entities.
SID – Level 2 • Within each domain are multiple “Aggregate Business Entities” (ABEs) Service Domain
Architectural Patterns • As with the Party entity, roles can be used to simplify the modeling of different types of Resources and to make the model inherently more extensible. [GB922 Addendum 5LR, v.9.5, p.38] • Party and Party Role • Resource and ResourceRole • Service and ServiceRole • Device and DeviceRole • Other architectural patterns • Specification • Abstract Superclass (e.g. Party) • Composite (assemble objects into trees; e.g. Party) • Role Entity • Temporal State Entity • Self Relationship
