Business Process Framework (eTOM) - Revision history

User at 20:57, 5 January 2023

2023-01-05T20:57:00Z

User at 18:16, 7 September 2022

2022-09-07T18:16:42Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T14:17:11Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User: Created page with "'''The Business Process Framework (eTOM)''' is a critical component of the Open Digital Framework, TM Forum’s blueprint for enabling successful business transformation. It i..."

2020-05-19T15:57:43Z

Created page with "'''The Business Process Framework (eTOM)''' is a critical component of the Open Digital Framework, TM Forum’s blueprint for enabling successful business transformation. It i..."

New page

'''The Business Process Framework (eTOM)''' is a critical component of the Open Digital Framework, TM Forum’s blueprint for enabling successful business transformation. It is a comprehensive, industry-agreed, multi-layered view of the key [[Business Process|business processes]] required to run an efficient, effective and agile digital enterprise.<ref>Definition - What Does Business Process Framework (eTOM) Mean? [https://www.tmforum.org/business-process-framework/ TM Forum]</ref>

The development of the business process standardization for telecom service providers started with the founding of the TM Forum in 1988. The initial goal was to facilitate the creation of 'interoperable network management products'. The first approved standard was the 'OSI/NM Forum Protocol Specification,' an extension of OSI protocols developed since the late 1970s. The direct development towards the Business Process Framework (eTOM), as Brenner (2007) explained, was "the Telecom Operation Map (TOM) was first published in 2001. The goal of TOM was the creation of an industry-owned framework of business processes, including the definition of a common enterprise-independent terminology for service management. It was also supposed to serve as a basis for discussing the scope of information management necessary for the execution of the processes. The result of this latter effort has meanwhile spawned its own TMF document family, the Shared Information and Data Model (SID). The Telecom Operation Map (TOM) was extended in 2001 to eTOM, an acronym for Enhanced Telecom Operations Map. The process model eTOm was renamed "Enhanced Telecom Operations Map (eTOM)," and in 2013 to "Business Process Framework (eTOM)." There have been many versions of eTOM. Version 14 was published in May 2014. It also has been developed into a component of NGOSS, which has been renamed Frameworx.<ref>Historical Overview of Business Process Framework (eTOM) [https://en.wikipedia.org/wiki/Business_Process_Framework_(eTOM) Wikipedia]</ref>

@@ Line 1: / Line 1: @@
-'''The Business Process Framework (eTOM)''' is a critical component of the Open Digital Framework, TM Forum’s blueprint for enabling successful business transformation. It is a comprehensive, industry-agreed, multi-layered view of the key [[Business Process|business processes]] required to run an efficient, effective and agile digital enterprise.<ref>Definition - What Does Business Process Framework (eTOM) Mean? [https://www.tmforum.org/business-process-framework/ TM Forum]</ref>
+'''The Business Process Framework (eTOM)''' is a critical component of the Open Digital Framework, TM Forum’s blueprint for enabling successful [[Business Transformation|business transformation]]. It is a comprehensive, industry-agreed, multi-layered view of the key business processes required to run an efficient, effective, and agile digital enterprise.<ref>Definition - What Does Business Process Framework (eTOM) Mean? [https://www.tmforum.org/business-process-framework/ TM Forum]</ref>
-The development of the business process standardization for telecom service providers started with the founding of the TM Forum in 1988. The initial goal was to facilitate the creation of 'interoperable network management products'. The first approved standard was the 'OSI/NM Forum Protocol Specification,' an extension of OSI protocols developed since the late 1970s. The direct development towards the Business Process Framework (eTOM), as Brenner (2007) explained, was "the Telecom Operation Map (TOM) was first published in 2001. The goal of TOM was the creation of an industry-owned framework of business processes, including the definition of a common enterprise-independent terminology for service management. It was also supposed to serve as a basis for discussing the scope of information management necessary for the execution of the processes. The result of this latter effort has meanwhile spawned its own TMF document family, the Shared Information and Data Model (SID). The Telecom Operation Map (TOM) was extended in 2001 to eTOM, an acronym for Enhanced Telecom Operations Map. The process model eTOm was renamed "Enhanced Telecom Operations Map (eTOM)," and in 2013 to "Business Process Framework (eTOM)." There have been many versions of eTOM. Version 14 was published in May 2014. It also has been developed into a component of NGOSS, which has been renamed Frameworx.<ref>Historical Overview of Business Process Framework (eTOM) [https://en.wikipedia.org/wiki/Business_Process_Framework_(eTOM) Wikipedia]</ref>
+The development of business process standardization for telecom service providers started with the founding of the TM Forum in 1988. The initial goal was to facilitate the creation of 'interoperable network management products'. The first approved standard was the 'OSI/NM Forum Protocol Specification,' an extension of OSI protocols developed in the late 1970s. The direct development towards the Business Process Framework (eTOM), as Brenner (2007) explained, was "the Telecom Operation Map (TOM) was first published in 2001. The goal of TOM was the creation of an industry-owned framework of business processes, including the definition of common enterprise-independent terminology for service management. It was also supposed to serve as a basis for discussing the scope of information management necessary for the execution of the processes. The result of this latter effort has meanwhile spawned its own TMF document family, the Shared Information and Data Model (SID). The Telecom Operation Map (TOM) was extended in 2001 to eTOM, an acronym for Enhanced Telecom Operations Map. The process model eTOm was renamed "Enhanced Telecom Operations Map (eTOM)," and in 2013 to "Business Process Framework (eTOM)." There have been many versions of eTOM. Version 14 was published in May 2014. It also has been developed into a component of NGOSS, which has been renamed Frameworx.<ref>Historical Overview of Business Process Framework (eTOM) [https://en.wikipedia.org/wiki/Business_Process_Framework_(eTOM) Wikipedia]</ref>
 ==See Also==
 ===References===
 <references/>

← Older revision		Revision as of 18:16, 7 September 2022
Line 1:		Line 1:
−	'''The [[Business~~]] [[~~Process~~]] [[~~Framework]] ([[eTOM]])''' is a critical component of the Open Digital Framework, TM Forum’s [[blueprint]] for enabling successful business transformation. It is a comprehensive, [[industry]]-agreed, multi-layered view of the key [[Business Process\|business processes]] required to run an efficient, effective and agile digital enterprise.<ref>Definition - What Does [[Business Process]] Framework (eTOM) Mean? [https://www.tmforum.org/business-process-framework/ TM Forum]</ref>	+	'''The Business Process Framework (eTOM)''' is a critical component of the Open Digital Framework, TM Forum’s blueprint for enabling successful business transformation. It is a comprehensive, industry-agreed, multi-layered view of the key [[Business Process\|business processes]] required to run an efficient, effective and agile digital enterprise.<ref>Definition - What Does Business Process Framework (eTOM) Mean? [https://www.tmforum.org/business-process-framework/ TM Forum]</ref>

−	The development of the business process standardization for telecom [[service]] providers started with the founding of the TM Forum in 1988. The initial goal was to facilitate the creation of 'interoperable [[network~~]] [[~~management]] products'. The first approved [[standard]] was the 'OSI/NM Forum Protocol Specification,' an extension of OSI protocols developed since the late 1970s. The direct development towards the Business Process Framework (eTOM), as Brenner (2007) explained, was "the Telecom Operation Map (TOM) was first published in 2001. The goal of TOM was the creation of an industry-owned framework of business processes, including the definition of a common enterprise-independent terminology for service management. It was also supposed to serve as a basis for discussing the scope of information management necessary for the execution of the processes. The result of this latter effort has meanwhile spawned its own TMF document family, the Shared Information and [[Data~~]] [[~~Model]] (SID). The Telecom Operation Map (TOM) was extended in 2001 to eTOM, an acronym for Enhanced Telecom Operations Map. The process model eTOm was renamed "Enhanced Telecom Operations Map (eTOM)," and in 2013 to "Business Process Framework (eTOM)." There have been many versions of eTOM. Version 14 was published in May 2014. It also has been developed into a component of NGOSS, which has been renamed Frameworx.<ref>Historical Overview of Business Process Framework (eTOM) [https://en.wikipedia.org/wiki/Business_Process_Framework_(eTOM) Wikipedia]</ref>	+	The development of the business process standardization for telecom service providers started with the founding of the TM Forum in 1988. The initial goal was to facilitate the creation of 'interoperable network management products'. The first approved standard was the 'OSI/NM Forum Protocol Specification,' an extension of OSI protocols developed since the late 1970s. The direct development towards the Business Process Framework (eTOM), as Brenner (2007) explained, was "the Telecom Operation Map (TOM) was first published in 2001. The goal of TOM was the creation of an industry-owned framework of business processes, including the definition of a common enterprise-independent terminology for service management. It was also supposed to serve as a basis for discussing the scope of information management necessary for the execution of the processes. The result of this latter effort has meanwhile spawned its own TMF document family, the Shared Information and Data Model (SID). The Telecom Operation Map (TOM) was extended in 2001 to eTOM, an acronym for Enhanced Telecom Operations Map. The process model eTOm was renamed "Enhanced Telecom Operations Map (eTOM)," and in 2013 to "Business Process Framework (eTOM)." There have been many versions of eTOM. Version 14 was published in May 2014. It also has been developed into a component of NGOSS, which has been renamed Frameworx.<ref>Historical Overview of Business Process Framework (eTOM) [https://en.wikipedia.org/wiki/Business_Process_Framework_(eTOM) Wikipedia]</ref>
		+
		+
		+	==See Also==
		+	[[Business Process]]
		+	[[Business Process Engine (BPE)]]
		+	[[Business Process Automation]]
		+
		+
		+	===References===
		+	<references/>

← Older revision		Revision as of 14:17, 6 February 2021
Line 1:		Line 1:
−	'''The Business Process Framework (eTOM)''' is a critical component of the Open Digital Framework, TM Forum’s blueprint for enabling successful business transformation. It is a comprehensive, industry-agreed, multi-layered view of the key [[Business Process\|business processes]] required to run an efficient, effective and agile digital enterprise.<ref>Definition - What Does Business Process Framework (eTOM) Mean? [https://www.tmforum.org/business-process-framework/ TM Forum]</ref>	+	'''The [[Business]] [[Process]] [[Framework]] ([[eTOM]])''' is a critical component of the Open Digital Framework, TM Forum’s [[blueprint]] for enabling successful business transformation. It is a comprehensive, [[industry]]-agreed, multi-layered view of the key [[Business Process\|business processes]] required to run an efficient, effective and agile digital enterprise.<ref>Definition - What Does [[Business Process]] Framework (eTOM) Mean? [https://www.tmforum.org/business-process-framework/ TM Forum]</ref>

−	The development of the business process standardization for telecom service providers started with the founding of the TM Forum in 1988. The initial goal was to facilitate the creation of 'interoperable network management products'. The first approved standard was the 'OSI/NM Forum Protocol Specification,' an extension of OSI protocols developed since the late 1970s. The direct development towards the Business Process Framework (eTOM), as Brenner (2007) explained, was "the Telecom Operation Map (TOM) was first published in 2001. The goal of TOM was the creation of an industry-owned framework of business processes, including the definition of a common enterprise-independent terminology for service management. It was also supposed to serve as a basis for discussing the scope of information management necessary for the execution of the processes. The result of this latter effort has meanwhile spawned its own TMF document family, the Shared Information and Data Model (SID). The Telecom Operation Map (TOM) was extended in 2001 to eTOM, an acronym for Enhanced Telecom Operations Map. The process model eTOm was renamed "Enhanced Telecom Operations Map (eTOM)," and in 2013 to "Business Process Framework (eTOM)." There have been many versions of eTOM. Version 14 was published in May 2014. It also has been developed into a component of NGOSS, which has been renamed Frameworx.<ref>Historical Overview of Business Process Framework (eTOM) [https://en.wikipedia.org/wiki/Business_Process_Framework_(eTOM) Wikipedia]</ref>	+	The development of the business process standardization for telecom [[service]] providers started with the founding of the TM Forum in 1988. The initial goal was to facilitate the creation of 'interoperable [[network]] [[management]] products'. The first approved [[standard]] was the 'OSI/NM Forum Protocol Specification,' an extension of OSI protocols developed since the late 1970s. The direct development towards the Business Process Framework (eTOM), as Brenner (2007) explained, was "the Telecom Operation Map (TOM) was first published in 2001. The goal of TOM was the creation of an industry-owned framework of business processes, including the definition of a common enterprise-independent terminology for service management. It was also supposed to serve as a basis for discussing the scope of information management necessary for the execution of the processes. The result of this latter effort has meanwhile spawned its own TMF document family, the Shared Information and [[Data]] [[Model]] (SID). The Telecom Operation Map (TOM) was extended in 2001 to eTOM, an acronym for Enhanced Telecom Operations Map. The process model eTOm was renamed "Enhanced Telecom Operations Map (eTOM)," and in 2013 to "Business Process Framework (eTOM)." There have been many versions of eTOM. Version 14 was published in May 2014. It also has been developed into a component of NGOSS, which has been renamed Frameworx.<ref>Historical Overview of Business Process Framework (eTOM) [https://en.wikipedia.org/wiki/Business_Process_Framework_(eTOM) Wikipedia]</ref>