MBAers cần phải xây dựng mô hình kinh doanh mang lại giá trị cho xã hội
Các mô hình kinh doanh rất hay, nhưng khó áp dụng ở Việt Nam, bởi vì ở Việt Nam mục tiêu của người ta kinh doanh là vì kiếm tiền và làm giàu chứ không phải là đóng góp cho xã hội. Nhiều người thường có suy nghĩ rằng “Tôi giàu rồi sẽ đóng góp cho xã hội”, và kết quả là họ cũng chả giàu và chả đóng góp được gì cho xã hội. Tại sao lại không phải là “Tôi đóng góp cho xã hội và xã hội giúp tôi làm giàu”, clip này là một minh chứng.
Thêm nữa, những người được đào tạo MBA như chúng ta cần phải là những người tiên phong, sáng tạo ra những mô hình kinh doanh mới mang lại nhiều giá trị hơn cho xã hội chứ không chỉ gói gọn trong mục tiêu thăng tiến và lương bổng các bạn ạ!!!
The Proactive Outreach Manager Pluggable Data Connector ( POM PDC) is a Dialog Designer or Avaya Aura ® Orchestration Designer plug-in and extends the Dialog Designer or Avaya Aura ® Orchestration Designer application’s capability to interface and integrate with Proactive Outreach Manager (POM) using the core functionality of the PDC framework. It implements the functionality of seamless connectivity with POM for various type of data exchange, and establishes a connection between the VXML application and the POM server for information access and update. The PDC is similar to the Connection Technology Inc (CTI) connector and the IC connector. It extends the functionality of the Data node palette of Graphical Call flow editor in Dialog Designer or Avaya Aura ® Orchestration Designer, and provides following nodes to execute custom action for POM servers:
- Update disposition
- Add contact info
- Add contact to running job
- Get contact info
- Update contact attribute
- Get contact attribute
- Add to DNC List
- Remove from DNC List
Avaya Proactive Outreach Manager (POM) is a managed application of Avaya Aura ® Experience Portal, a new class of application, linking the capabilities within the platform more closely with the management infrastructure and services. POM provides a solution for unified, multichannel, inbound and outbound architecture with the capability to communicate through different channels of interaction like Short Message Service (SMS), or e-mail, or traditional voice and video.
AVAYA POM 3.1 – 12 FEATURES DESCRIPTIONS
- Campaign management
- Contact list management
- Attribute management
- Data sources
- Media channel management
- Campaign strategy management
- Campaign restrictions
- Pacing management
- Do Not Call list management
- Web service management
- Pluggable Data Connector nodes
1- CAMPAIGN MANAGEMENT
A campaign delivers a specific message to all customers in the database through selected channels such as e-mail, SMS, and voice.
POM provides a Web-based wizard to create campaigns. A campaign typically has a name, a campaign strategy, and one or more contact lists. You can have either a finite campaign or an infinite campaign. You can set filter criteria on the contact lists. If you specify a filter criterion, POM applies the criterion at the beginning of a campaign and selects only those customer records that meet the specified criterion. You can define and associate one or more custom completion codes with a campaign when you need some user input.
You can set criteria to terminate finite campaigns. For example:
- Goal-based campaign: A goal-based campaign terminates after receiving an expected number of responses from customers.
- Time-based campaign: A time-based campaign terminates after running for a specific time duration. For example, you can terminate a campaign after 12 hours.
- Completion code-based campaign: A completion code-based campaign terminates after achieving a specific completion code condition. For example, you can terminate a blood donation campaign after you receive 50 accepted responses.
- Natural finish: A natural finish campaign does not have specified finish criteria and terminates naturally after processing the customer records.
2 – CONTACT LIST MANAGEMENT
Campaigns need phone numbers for making phone calls and sending SMSs and email
addresses for sending email messages. A contact list is a logical collection of customer
records. You can set up any number of contact lists and associate one or more contact lists with a campaign. You can also use a single contact list in multiple campaigns. In a multitenant environment, you can associate a contact list with one or more tenants. Typically this customer data resides outside POM in a contact management system, and based on your campaign requirements, you must import relevant customer records into POM at regular time intervals.
You can set up any number of contact lists and define any number of attributes. Using POM, you can import customer records into a contact list from various external data sources such as flat files, external database and use various Web service methods to create, read, and update customer records. You can export all customer records into a comma-separated values (.csv) file.
3 – ATTRIBUTE MANAGEMENT
Attributes are properties of customer data.
Based on your campaign needs, you might need custom attributes such as Amount Due, Due Date, and BloodType. Using POM you can set up custom attributes, and import data to these attributes. A typical custom attribute has a name, data type, and privacy flag. The privacy flag helps you to define the visibility of this attribute in a multitenancy setup.
4 -DATA RESOURCE
With data sources, you can organize customer records into a contact list. You can define two types of data sources, file based and database based. With the file-based data source, you can import customer records from a .csv file into a contact list. The .csv file can either be on a local file system or the File Transfer Protocol (FTP) server. With the database-based data source, you can import customer records from an external database. You can run the data source to import data. You can also define recurring schedules to import data at a fixed interval from an external file or a database.
5 – MEDIA CHANNEL MANAGEMENT
POM uses various notification channels to run campaigns: SMS channel, email channel, and voice and video channel.
5 – PLUGGABLE DATA CONNECTOR (PDC)
ou can use the Pluggable Data Connector (PDC), a plug-in, to gain access to POM specific operations using Voice Portal or an Avaya Aura ® Orchestration Designer application.
14 CHỦ ĐỀ VỀ WOOCOMMER:
- Bài 1 – Giới thiệu Woocommerce
- Bài 2 – Cài đặt file Việt Hóa cho Woocommerce
- Bài 3 – Các thiết lập cần thiết sau khi cài plugin
- Bài 4 – Cách thêm một sản phẩm đơn giản
- Bài 5 – Đưa sản phẩm ra trang chủ
- Bài 6 – Thuộc tính sản phẩm
- Bài 7 – Thiết lập phí vận chuyển (Shipping Fee)
- Bài 8 – Thiết lập thuế
- Bài 9 – Tạo nhóm sản phẩm
- Bài 10 – Tạo mã giảm giá
- Bài 11 – Quản lý đơn hàng
- Bài 12 – Tự Việt hóa Woocommerce
- Bài 13 – Thêm sản phẩm kỹ thuật số vào Woocommerce
- Bài 14 – Cấu trúc giao diện của Woocommerce
BÀI 1 – GIỚI THIỆU WOO ECOMMERCE
BÀI 2 – VIỆT HÓA WOOCOMMERCE
BÀI 3 – THIẾT LẬP CƠ BẢN CHO WOO COMMERCE
BÀI 4 – THÊM MỘT SẢN PHẨM TRONG WOOCOMMERCE Continue reading Tổng hợp 14 bài về sử dụng WooCommerce Plugin trong WordPress Update 2015
[email protected] 08:04 PM /opt/Avaya/avpom/POManager/logs # su – postgres
Welcome to psql 8.3.10, the PostgreSQL interactive terminal.
Type: \\copyright for distribution terms
\\h for help with SQL commands
\\? for help with psql commands
\\g or terminate with semicolon to execute query
\\q to quit
postgres=# \\c VoicePortal
You are now connected to database “VoicePortal”.
pom=# select * from pim_job where job_id=’1150′;
job_id | campaign_id | schedule_id | status | start_time | end_time | last_allocated_id | f inish_reason | next_archival_time | abort_time | total_calls | total_emails | total_sms | total_contacts | successful_calls | nuisance_calls | customer_hangups
1150 | 1 | | 16 | 2011-03-02 12:41:42.188-07 | | -1 | | | | 0 | 0 | 0 | 0 | 0 | 0 | 0
pom=# delete from pim_job where job_id=’1150′;
Src: How to stop POM Campaign manually https://support.avaya.com/ext/index?page=content&id=SOLN147110&group=UG_ENTITLED_PARTNER
UNABLE START POM SERVER
[email protected] ~]# service POM restart
Stopping POM at Mon Oct 17 10:12:07 CEST 2011
Stopping individual components:
Stopping Campaign Manager…
Stopping Campaign Manager:
Warning: No CM process is running! Please restart CM [ OK ]
Stopping Campaign Director…
Stopping Campaign Director:
Warning: No CD process is running! Please restart CD [ OK ]
POM Shutdown Status: [ OK ]
Solution: From the Voice Portal (VP) web Administration page, remove and create back the POM server.
From the Voice Portal Web Administration page, access menu POM Configuration / POM servers
- Check the box in front of the POM server name and click the Delete button.
- Click the Add button to create back the POM server and fill the POM Server Name and POM Server IP Address fields.
Proactive Outreach Manager POM: Got only one ring on POM dialed contact
When running the campaign, the called contacts ring only once. In the POM report, the calls are identified as transferred however the calls have not been answered. The strategy has been developed to use the AvayaPOMAgent application which proceed with a Blind transfer.
On CM, access the administration and run:
change system-parameters special-applications.
Set to yes SA8874 as shown below:
(SA8874) – Call Status Messages for 7434ND IP Softphone? y
[[email protected] ~]# service POM status
POM Experience Portal Management System (EPMS) Plug-in
When POM is installed, the POM plug-in is installed on the Experience Portal. This plug-in incorporates the POM Web application and POM tools that look after licensing, logging, and alarming.
POM integrates with the EPM to provide common administration and management tasks like Single Sign On (SSO), user management, logs, alarms and license management. The POM plug-in is only installed on the primary EPM.
When the EPMS plug-in is installed, the plug-in registers POM as a managed application with Experience Portal, deploys the POM Web application on the Tomcat server and initializes POM related configurations.
The POM server consists of core POM components required to execute campaigns and communicate with the various POM Web services. The POM server can be installed on either the primary EPM or auxiliary EPM. When installed on more than one hardware server, the POM server supports high availability and failover capabilities.
Campaign Director is a Linux service responsible for triggering campaigns and data imports at scheduled date and time. Campaign Director is also responsible for pausing and resuming campaigns based on user action and terminating campaigns if their finish criteria are specified. When POM is installed in a multiple server configuration, only one Campaign Director is in the active state and others are in the dormant state. For a multiple server configuration, the Campaign Director is responsible for assigning the contacts to be processed for any campaign across POM servers. Campaign Director is also responsible for redistribution of load in case of failures.
POM Web services
Web services are installed as part of the POM server and are accessed from the external applications. POM Pluggable Data Connector (PDC) uses Web services to interface with POM. Web Services can be used to access various contact attributes to play personalized prompts or make certain decisions in the application flow.
POM Agent Manager (PAM) is a Linux service installed with the POM server and is a core module to manage and run agent-based and agent-less campaigns. The PAM is responsible for distributing licenses to all voice based campaigns. The high-level functions of PAM include:
- Manages agent allocation and state for campaigns
- Manage agents in a blended job. This module is only supported in Call Center Elite
- Update the POM database with current agent related information for reporting
- Distribute the preview and predictive agent licenses among running agent-based campaigns and distributing outbound ports to voice notification campaigns
- Support real time commands from POM Monitor like changing job-related parameters minimum agents, priority or agent based commands like Forced Logoff
POM Single Server Configuration
A single server deployment can be used for smaller capacity deployments (up to 75 Predictive agents).The illustration below depicts the single server configuration.
When using the single-server configuration, a separate server will be required for failover. The configuration includes a single server running the EPM, Media Processing Platform (MPP), POM software along with the database and application server. For single server installation, the POM server and EPM plug-in packages are installed on the primary EPM.
POM Multiple Server Configuration
The multiple-server configuration includes one or more POM servers installed on the primary EPM and auxiliary EPM. The EPMS plug-in resides only on the primary EPM and the rest of the POM servers reside on the auxiliary EPM systems. In this configuration, one of the designated POM servers controls the failover and load balancing when using the agent-less notifications. The following diagram shows a multiple-server configuration. For simplicity, the MPPs and App Servers/Speech Servers are excluded in this diagram.
For scalability, POM can be configured with multiple POM Servers and Auxiliary EPMs with multiple MPPs. They can all be served from the same external database server. The database server is used for the contact lists, campaigns, strategies, reports, and other critical data.
When executing campaigns in this configuration, the Campaign Director distributes the load across the POM Servers. When one of the Campaign Directors configured as the Master Campaign Director crashes, the Campaign Director on another POM Server that was initially in dormant state automatically becomes the Master. If a particular POM Server crashes, after a certain interval the Master Campaign Director reallocates the active campaign on the crashed POM Server to another POM Server. If multiple EPMs are available for a campaign, the POM Server uses all EPM Servers for load balancing and failover. POM uses the EPM outbound Web service to launch a call.