External management entities can be a legacy OSS/BSS, management and orchestration entities [b- MANO], cloud management entities, or other management functionality which can be defined in the future. (...) Its main functionality includes abstraction of SDN management information for the exchange and request/reply of management operations with external management entities. (...) A.5.2 Management information abstraction functional element The management information abstraction functional element provides abstraction of SDN management information for the exchange with external management entities for inter-domain management information hiding purpose.
Language:English
Score: 342724.7
-
https://www.itu.int/en/publica.../files/basic-html/page316.html
Data Source: un
Fire management resources
English
Français
Español
FAO Home
Forestry
Fire management resources
Project Reports
Global assessments
Legal Framework and International Agreements
Working papers
Handbook for Trainers
Community Based Fire Management
Other FAO publications
Fire management resources
send by email
Working papers
Fire Management Working Papers report on issues and activities for decisionmakers, planners, managers, practitioners, researchers and academics.
(...) D.Johnson & A.P.Vuorinen 2009, EN
Forest Fire Management Working Paper - 023 Fire management needs and actions in the Southeast Asian region 2009, EN , 40pp
Forest Fire Management Working Paper - 022 Fire management voluntary guidelines: Preparation for action - country level methodology A.P. (...) Vuorinen 2008, EN
Forest Fire Management Working Paper - 019 Fire management voluntary guidelines: Preparation for action - country and regional level methodology A.P.
Language:English
Score: 342703.17
-
https://www.fao.org/forestry/92117/en/
Data Source: un
Page 475 - Cloud computing: From paradigm to operation
Basic HTML Version
Table of Contents
View Full Version
Page 475 - Cloud computing: From paradigm to operation
P. 475
Cloud Computing management 2 In a cloud-aware telecommunication management system, the general requirements include: – it is required that service management provides service catalogue and service inventory management functionality for telecommunication service, cloud service and TC-hybrid service; – it is required that service management supports the on-demand and automated service provisioning modification and termination for telecommunication service, cloud service and TC-hybrid service; – it is recommended that service management supports the E2E quality assurance of telecommunication service, cloud service and TC-hybrid service, and provide high levels of reliability and availability according to the service level agreement (SLA); – it is recommended that service management supports charging for telecommunication service, cloud service and TC-hybrid service, according to use time, bandwidth, resource usage and any combination of these; – it is recommended that service management supports monitoring, auditing and reporting for telecommunication service, cloud service and TC-hybrid service, for the purpose of service quality evaluation and assurance. All of the requirements listed above are suitable for services provided by single CSP as well as inter-cloud service provider. 8 Functional framework for service management in cloud-aware telecommunication management system The high-level organization of service management functionalities in a cloud-aware telecommunication management system is composed of service catalogue management, service inventory management, service test management, service order management, service problem management, service quality management, service performance management and service rating/discounting management. Figure 8-1 depicts the functional framework for service management in a cloud-aware telecommunication management system: Figure 8-1 – Functional framework for service management in cloud-aware telecommunication management system The functions are as follows: – service catalogue management: Provides capabilities for creating and designing new services, mapping service definitions, managing complex rules, supporting componentization of services and managing their relationships and dependencies; – service inventory management: Provides capabilities for storing and managing service instances and their attributes.
Language:English
Score: 342686.43
-
https://www.itu.int/en/publica.../files/basic-html/page475.html
Data Source: un
Information and Knowledge Management
Information and KnowledgeInformation and Knowledge ManagementManagement
A Risk ManagerA Risk Manager’’s Perspectives Perspective Dr Barbara CarbyDr Barbara Carby
The Cayman IslandsThe Cayman Islands AtAt
CTO Conference, JamaicaCTO Conference, Jamaica September 2006September 2006
Barbara.Carby@gov.kyBarbara.Carby@gov.ky
Information and KnowledgeInformation and Knowledge A Risk ManagerA Risk Manager’’s Perspectives Perspective
WHAT IS KNOWLEDGE MANAGEMENT?WHAT IS KNOWLEDGE MANAGEMENT?
Information and KnowledgeInformation and Knowledge A Risk ManagerA Risk Manager’’s Perspectives Perspective
WHAT IS KNOWLEDGE MANAGEMENT? (...) managed?
Information and KnowledgeInformation and Knowledge A Risk ManagerA Risk Manager’’s Perspectives Perspective
Disaster/Risk Managers must Disaster/Risk Managers must ensure that the public isensure that the public is aware, alerted.
Language:English
Score: 342642.46
-
https://www.itu.int/en/ITU-D/E...20-%20Dr%20Barbara%20Carby.pdf
Data Source: un
In the assurance process, the service test is responsible for service trouble/problem distinguishing; – service order management: Provides the capabilities for managing the E2E lifecycle of a service request. (...) This should include a real-time E2E view to ensure that each service is functioning correctly as well as a historical view; – service rating/discounting management: Provides the capabilities for ensuring that the customer receives an invoice that is reflective of all the billable events delivered by the service provider dictated by their business relationship. 9 Functional requirements for service management in cloud-aware telecommunication management system This clause provides functional requirements for service management in a cloud-aware telecommunication management system. 9.1 Service catalogue management In a cloud-aware telecommunication management system, the service catalogue management requirements include: – it is required that service catalogue management provides functions to manage cloud service information. It is required that service catalogue management provides functions to manage information of TC-hybrid services. 9.2 Service inventory management In a cloud-aware telecommunication management system, the service inventory management requirements include: – it is required that service inventory management provides functions to manage the attributes of cloud service; – it is required that service inventory management provides functions to trace the relationship between the cloud service or TC-hybrid service and resource. 9.3 Service order management In a cloud-aware telecommunication management system, the service order management requirements include: – it is required that the service order management provides functions to validate cloud service availability as well as the cloud service order request; – it is required that the service order management provides functions to manage service and or product order decomposition which contain cloud service; 468
471 472 473 474 475 476 477 478 479 480 481
Language:English
Score: 342609.18
-
https://www.itu.int/en/publica.../files/basic-html/page476.html
Data Source: un
S4_P1_Sidor
International Telecommunication Union
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
ITUITU--T Overview of T Overview of NGN ManagementNGN Management
Dave Sidor Chairman, ITU-T SG 4
Chair, NGNMFG Nortel Networks
2 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Agenda
o ITU-T SG 4 o NGN Management Focus Group
(NGNMFG) o NGNMFG candidate management
specifications o Key issue o Backup charts
3 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
NGN Management Architecture (M.3060)
Management Functional Architecture
Management Functional Architecture
Management Information Architecture
Management Information Architecture
Management Physical Architecture
Management Physical Architecture
B us
in es
s P ro
ce ss
A rc
hi te
ct ur
e B
us in
es s P
ro ce
ss A
rc hi
te ct
ur e
B us
in es
s P ro
ce ss
A rc
hi te
ct ur
e
Se cu
ri ty
C on
sid er
at io
ns
4 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Business Process Architecture (M.3050 series = TMF eTOM)
Enterprise Management
Strategy, Infrastructure & Product Operations
Fulfillment Assurance BillingProduct Lifecycle Management
Infrastructure Lifecycle Management
Operations Support & Readiness
Customer Relationship Management
Service Management & Operations
Resource Management & Operations
Supplier/Partner Relationship Management
Strategic & Enterprise Planning
Financial & Asset Management
Stakeholder & External Relations Management
Strategy & Commit
Marketing & Offer Management
Service Development & Management
Resource Development & Management
Supply Chain Development & Management
Human Resources Management
(Application, Computing and Network)(Application, Computing and Network)
Enterprise Risk Management
Enterprise Effectiveness Management
Knowledge & Research Management
Customer
5 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
NGN Management Logical Layered Architecture (M.3060)
Market, Product & Customer (Customer Facing) OSFs
NGN Service Management (Resource Facing) OSFs
NGN Service Resource Management OSFs
NGN Transport Resource Management OSFs
NGN Service Customer (Wholesale and Retail)
NGN Service Stratum NGN Transport Stratum
Service Management Layer
Network Management Layer
OSF Human User
Supplier Partner Management OSFs
Supplier Partner Management OSFs
Imported Resources
NGN Service Element Management OSFs NGN Transport Element
Management OSFs
q
x
q
q
q
Element Management Layer
Network Element Layer
f
Enterprise Management OSFs x
Service Element Function Transport Element Function
q q
Business Management Layer
LLA Layers
6 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Security of the Management Plane (M.3016 series)
o M.3016.0: Overview o M.3016.1: Requirements o M.3016.2: Services o M.3016.3: Mechanisms o M.3016.4: Profile proforma
7 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
NGN Management Focus Group (NGNMFG)
o Established by ITU-T SG 4 in Sept 2004 at FGNGN request to support NGN Release 1
o Based on collaboration with SDOs, forums, and consortia (initially 8)
o Focused on the following (FCAPS) management interfaces: • NE-OS, OS-OS, and NE/OS-WS interfaces
FCAPS - Fault, Configuration, Accounting, Performance, and Security Management
8 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
NGNMFG Scope: FCAPS Management Interfaces
Network Element Layer
Element Management Layer
Network Management Layer
Service Management Layer
Network Element Layer
Element Management Layer
Network Management Layer
Service Management Layer
NML-NML interface
NML-EML interface
transmission interface
NML-EML interface
SML-SML interface
EML-EML interface
SML-NML interface SML-NML interface
EML-NEL interface EML-NEL interface
• Excludes transmission interfaces • But also includes Human-Machine Interfaces (HMI)
Business Management Layer
BML-SML interface
Business Management Layer
BML-SML interface
9 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
NGN Management FG – Objectives - 1
General goal: To provide the management interface capabilities to support the FGNGN objectives for Release 1.
o To agree with the high level management requirements in Y.2001, Y.2011, and the FGNGN FRA.
o To determine from them, the functional and physical entities to be managed for Release 1.
10 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
NGN Management FG – Objectives – 2
o To produce a NGN Management Roadmap focused on Release 1 which identifies • Requirements • Framework, principles, and architecture • Interface specifications, both protocol-neutral
and protocol-specific o To emphasize reuse of partner organizations’
specifications o To identify gaps and best organization(s) to fill
the gaps o As a last resort, to produce specifications
deemed to be necessary but unavailable from any source.
11 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Candidate Specifications for NGN Management - 1
o ITU-T SG 4 •M.3016 series (security of the management plane)
•M.3050 series (Enhanced Telecom Operations Map)
•M.3060 (NGN principles and architecture) •M.3341 (QoS/SLA management service requirements)
•M.3350 (Emergency telecommunication service management requirements)
o ITU-T SG 15 •G.7718, G.7718.1 (ASON control plane management)
12 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Candidate Specifications for NGN Management – 2
o ETSI TISPAN WG8 •DTS 08004 (OSS interface requirements for NGN) •DTS 08006 (Vision for NGN OSS) •DTS 08007 (NGN OSS archtitecture for R1) •DTS 08008 (NGN OSS services for R1)
o TeleManagement Forum •Enhanced Telecom Operations Map (eTOM, =M.3050)
•Multi-technology Network Management (MTNM)
13 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Candidate Specifications for NGN Management – 3
o 3GPP SA5 •32.101/32.102 (principles and architecture) •32.150 series (IRP methodology) •32.111 series (alarm IRP) •32.200 series (subset for IMS charging and billing) •32.300 common management series (name convention, IRPs for notification, generic, test, notification log, file transfer)
•32.400 performance management series (requirements, PM IRP)
14 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Candidate Specifications for NGN Management – 4
o 3GPP SA5 (cont.) •32.600 series (requirements; interface IRPs for basic CM, bulk CM, kernel CM; NRM IRPs for generic, core, UTRAN, GERAN, network transport, signalling transport; data definition IRPs for state management)
o 3GPP2 TSG S WG5 •Most of 3GPP specs above •S.S0028 series (NRM IRPs for generic, core, radio access)
15 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Candidate Specifications for NGN Management – 5
o OASIS • WSDM-MUWS (Web services distributed
management) o IETF
• RFC 3444 (On the difference between information models and data models)
• RFC 3535 (Overview of the 2002 IAB network management workshop)
Note: Some of the above specifications are in draft form.
16 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Issues Regarding Functional and Physical Entities to be Managed
o Identification of NEs still very abstract in FGNGN FRA • Essential for identifying relevant IETF standards
which are focused on NE interfaces. o Service Stratum
• What 3GPP/2 OAM standards are essential for IMS? (...) o Transport Stratum • Transport NEs most unclear
17 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Backup Charts
18 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
NGN Management Focus Group o Leadership
• Chair: Dave Sidor (Nortel Networks) • Vice Chair: Leen Mak (Lucent Technologies)
o Participation • Open; individuals from founding organizations
encouraged • Registration required: see http://www.itu.int/ITU-T/studygroups/com04/ngn-
mfg/index.html o Time schedule
• Initial results reported to SG 4: Feb. 2005 • Final recommendations to SG 4: Sept. 2005
o Working methods • Decision-making via consensus • Electronic meetings, but f2 f meetings allowed • Any specifications produced are candidates to be SG 4
Recommendations
19 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Template for Specification Candidates
Short Name o Title: o Status: approved, draft (due date) o Organization (group): o Organization leader (group leader): o Type: architecture (functional, physical), functional
requirements, information model (protocol-neutral, protocol-specific), protocol, conformance
o Role: generic, technology-specific, NGN-specific o Release 1 application: o Traceability: o Location of text: either URL or NGNMFG ID number o Remarks:
20 dates
ITU-T
ITU-T Workshop on NGN (jointly organized with IETF) Geneva, 1-2 May 2005
Acronyms o ASON – Automatic switching optical network o BML – Business management layer o EML – Element management layer o eTOM – Enhanced Telecom Operations Map (RM) o FCAPS – Fault, configuration, accounting, performance, and security management
(combination of FM, CM, AM, PM, and SM) o FRA – Functional requirements and architecture o GERAN – GSM edge radio access network o HMI – Human machine interface o IMS – IP multimedia subsystem o IRP – Integration reference point o LLA – Logical layered architecture o MTNM – Multi-technology network management o NE(L) – Network element (layer) o NRM – Network resource model o OS(F) – Operation system (function) o OSS – Operations support system (specialization of an OS) o SLA – Service level agreement o SML – Service management layer o UTRAN – UMTS radio access network o WS - Workstation
Language:English
Score: 342595.97
-
https://www.itu.int/ITU-T/work...505/presentations/s4-sidor.pdf
Data Source: un
CHAPTER 4
ENSURING TELECOMMUNICATIONS SUCCESS AROUND THE WORLD
Telecommunications Management Group, Inc.
Current Trends on Spectrum Management
Daniel Leza Telecommunications Management Group, Inc.
(...) Contents
• General background • Defining spectrum management • National spectrum management • International coordination • Spectrum management paradigm shift • Steps for regulators
3Vientiane, Lao P.D.R. 26-27 October, 2007
Current Trends on Spectrum Management
Telecommunications Management Group, Inc.
(...) Thank You
Daniel Leza Legal and Regulatory Advisor
Telecommunications Management Group, Inc. 1600 Wilson Boulevards, Suite 700
Arlington, VA 22209 USA +1.703.224.1501
www.tmgtelecom.com
Current Trends on Spectrum Management
Contents
General Background
Defining Spectrum Management
Spectrum Management
International Coordination
International Coordination Process
Spectrum Management Paradigm Shift
Spectrum Management Paradigm Shift
Spectrum Management Paradigm Shift
Licensing in a Converging Environment
Impact of Convergence on Spectrum Management
Steps for Regulators
Thank You
Language:English
Score: 342565.65
-
https://www.itu.int/ITU-D/treg...rends__Spectrum_Management.pdf
Data Source: un
Process Management System;
Corporate Knowledge Management System;
Corporate Records Management System;
HR Management System.
ISO 9001:2000 – 4.1, 4.2.3,4.2.4,6.2.2, 6.3,6.4
ISO 27001:2005
To make business transparent
Process Management System;
Corporate Knowledge Management System;
Corporate Reports Management System;
HR Management System;
Supply Management System;
The System of Process Monitoring and Measurement;
ISO 9001:2000 – 4.1, 4.2.3,4.2.4, 5.5, 7.4, 8.2.3
Systematic Risk Management
Corrective Action Management System;
Preventive Action Management System;
Procedures of Information Security Risks Management.
(...) Customer Relationship Management System (7.2 ISO 9001:2000);
8. Supply Management System.
Language:English
Score: 342544.7
-
https://unece.org/fileadmin/DA...uments/2006/8d_nikonov_eng.doc
Data Source: un
Approve requests for leave absence work instructions.fm
1/18Department of Management Office of Human Resources Management
21 March 2015
Approve requests for leave absence by Time Manager Quick Reference
Purpose
Use this procedure to by the Time Manager (primary and secondary) to approve/endorse leave absence requests submitted by a staff member.
(...) Approver Work Center
7/18Department of Management Office of Human Resources Management
21 March 2015
Approve requests for leave absence by Time Manager Quick Reference
5. (...) Approver Work Center
11/18Department of Management Office of Human Resources Management
21 March 2015
Approve requests for leave absence by Time Manager Quick Reference
12.
Language:English
Score: 342540.7
-
https://umoja.un.org/sites/umo...bsence_work_instructions_0.pdf
Data Source: un
Approve requests for leave absence work instructions.fm
1/18Department of Management Office of Human Resources Management
21 March 2015
Approve requests for leave absence by Time Manager Quick Reference
Purpose
Use this procedure to by the Time Manager (primary and secondary) to approve/endorse leave absence requests submitted by a staff member.
(...) Approver Work Center
7/18Department of Management Office of Human Resources Management
21 March 2015
Approve requests for leave absence by Time Manager Quick Reference
5. (...) Approver Work Center
11/18Department of Management Office of Human Resources Management
21 March 2015
Approve requests for leave absence by Time Manager Quick Reference
12.
Language:English
Score: 342540.7
-
https://umoja.un.org/sites/umo...absence_by_time_manager__0.pdf
Data Source: un