当前位置:文档之家› Workflows in Dynamic Environments-- Can they be managed

Workflows in Dynamic Environments-- Can they be managed

Workflows in Dynamic Environments-- Can they be managed
Workflows in Dynamic Environments-- Can they be managed

Workflows in Dynamic Environments –

Can they be managed?

Shazia W. Sadiq

Computer Science and Electrical Engineering

The University of Queensland

QLD 4072 Australia

email:shazia@https://www.doczj.com/doc/8d9670022.html,.au

Abstract: Business environments have become exceedingly dynamic

and competitive in recent times. Workflow technology is currently one

of the most promising fields of research in business process automation.

However, workflow systems to date do not provide the flexibility

necessary to support the dynamic nature of business processes. In this

paper we primarily present the issues and challenges related to

managing workflows in dynamic environments, and provide feasibility

considerations for the automation of this process. We also present an

analysis of workflow modifications and potential solutions in this

regard.

1The Challenge

Recent technological advancements have made it possible for organizations to automate their business processes extensively. Specialized information systems have emerged, which are tailored to specific functional divisions of organizations. At the same time, there have been giant leaps in connectivity, owing to advancement in communication infrastructure and protocols. Organizations now seek to achieve higher goals by consolidating their specialized, but distributed and often disconnected resources. The introduction of the workflow paradigm, after considerable maturity of information systems, database management, and networking infrastructure, was the next logical step in business process automation.

A Workflow is defined as the automation of a business process, in whole or part, during which documents, information or tasks are passed from one participant to another for action, according to a set of procedural rules [WFM Coalition 1998]. Even though every business process will have some form of ‘flow of work’, there are of course, certain processes which are more suited for automation with workflow technology.

Workflows have been classified in many ways. The trade press classifies workflows into three categories: Ad-hoc, Production, Administrative, on the basis or repetitiveness, predictability and functionality. [Georgakopoulos et al., 1995]

classifies on the basis of processing entities: system-oriented and human oriented. [Mohan 1996] adds a further category to the trade press classification: Collaborative, and divides the classes on the basis of mission criticality and workflow complexity. Another important property of business processes is Rigidity. The degree of rigidity dictates the nature of the process, from production, assembly line type of processes for which the work required is exactly known and set before the process starts, to strategic, mission critical processes where the work required cannot be predicted or fixed. Processes that fall in the middle may very well be the ones most likely to be chosen for and to benefit from automation through workflow technology. These processes are defined prior to execution, but also allow for some flexibility. They are characterized by the phrase "This is the way we do things around here"[Burch & Grudnitski 1989]. Such processes may be of a similar nature, but can have different procedures in different organizations. However, due to the continually accelerating pace of technological advancements, changing requirements and regulations, and introduction of new methods, business processes are being constantly reviewed, improved and adapted to the changing environment. The stability of even those processes which, can be characterized as rigid, repetitive or predictable, is put in doubt.

Organizations seeking to employ workflow technology have to be prepared for a large undertaking. Setting up (process mapping, workflow model definition, resource allocations, constraint specification) of even the simplest business processes through workflow technology would incur significant investment of time, effort and resources, successful deployment is yet another issue. One has to question the appropriateness of processes that are ready to be changed as soon as they are set up. Whether workflows in dynamic environments, would actually deliver the superior management and monitoring the management aspires for, or it would convert the process to an inflexible structure, engaging the workforce in managing the support tool? The first question to be asked is the suitability of the business process for automation by workflow technology.

Assuming that organizations would endeavor to introduce workflows in dynamic environments, the next question is how best to capture the dynamism of the business process within the workflow model. One possible approach is to provide flexibility within the definition of the workflow, such that later modifications can be avoided as far as possible. These are slippery grounds since the distinction between ad-hoc and production workflows becomes fuzzy. If everything is kept flexible at build time, activity coordination and control at runtime cannot be satisfactorily provided. A workflow allowed to run freely, devoid of any control or constraints, will wipe out the very reason for which workflow technology was introduced. On the other hand, highly prescriptive models will impose a control that is too rigid for even the repetitive production workflows. Such inflexible structures can kill the individualism, dynamism and adaptability necessary for the organization to survive in a competitive environment. Finding the right balance between precise definition and flexible

definition is a hard issue for which generic solutions may not be workable.

We could also try to anticipate changes and/or exceptions to the process and attempt to build them into the process logic. However, specifying all exceptions within the process, if at all possible, would cause an enormous model to be built. And in spite of that, unanticipated ad-hoc deviations from the designed model may arrive later.

Thus the challenge remains, how do we manage workflows in dynamic environments? Even though the need for workflows reactive to dynamic environments is both apparent and pressing, the solution is neither apparent nor simple. In the following sections, we will advance the discussion further by trying to understand the scope and issues involved in the definition and enactment of such workflows. We will then discuss various approaches and potential solutions.

2The Scope

The workflow model or process model is a description of the tasks, ordering, data, resources, and other aspects of the process. Most, if not all, workflow models are represented as graphs [Casati et al., 1995], [Reichert &Dadam 1997], [Sadiq & Orlowska 1997], [Aalst et al., 1994] where nodes in the graph represent process activities or tasks, and edges depict the flow or ordering of the tasks involved in the process. For example, we can define an admission workflow that handles admission applications in a university. Ideally the workflow model is intended to completely achieve process goals with maximum efficiency.

Workflow instances are particular occurrences of the process, for example, a particular application for admission represents an instance of the admission workflow. Different instances of the same workflow may perform a different subset of workflow tasks, i.e. they may follow different paths in the workflow graph. An instance class is a set of instances that can be represented by the same sub-graph. An instance that represents a departure from the process model is an exception.

Although exception handling has been an active area of research in information systems [Saastomoinen & White 1995], [Strong & Miller 1995] only recently, the issue of exception handling in workflows has attracted interest in research groups, owing mostly perhaps to its necessity. Focus of research in this area has been quite diverse. Researchers have approached the problem from different perspectives. Workflow Evolution, Workflow Adaptation, Dynamic Workflows, Workflow Modification and Workflow Flexibility are but some of the terms used in the literature.

One of the earliest contributions came from [Eder & Liebhart 1995]. They divide exceptions that may occur during workflow execution into basic failures, which are failures at the system level, application failures, expected exceptions and unexpected exceptions. [Casati et al., 1996] present a notable taxonomy of workflow changes

referred to as Case Evolution Policies. They identify abort, flush and a set of progressive policies that allow case dependent evolution management of the workflow. In [Han &Sheth 1998], the authors classify workflow adaptation into process level adaptation, resource level adaptation and infrastructure level adaptation.

An important distinction in business changes affecting underlying workflows systems is whether modifications are to be made to the workflow model or instances. Changes made to the workflow model indicate a permanent change of the business process as a result of process improvement [Davenport 1993], process innovation or business process reengineering [Hammer & Champy 1993], or simply because of design errors. Changes that affect only particular or few instances represent unforeseen, presumably rare situations in the business process. Thus instances captured within the workflow model will eventually complete, that is, they can be guaranteed completion. An instance, which is unable to complete, identifies a process not specified by the workflow model, that is, an Exception. We explain this further; if any task in the instance fails to complete, it can do so for two reasons: System Failure: Recovery from system failure such as power cut, program abort, server down etc. are generally handled by the workflow activity which relies on the recovery capabilities of underlying (database) systems. The workflow may be temporarily suspended, but would resume execution when the local system recovers. Advanced issues like repeated system failure may require intervention, but we do not discuss this aspect of WFMS.

Semantic Failure: Semantic Failure occurs when an instance is unable to proceed according to the given workflow model. Thus the workflow model is unable to cater for the special requirements of this exceptional instance.

As a first step towards understanding the scope of workflow exceptions, we identify five related but distinct types of workflow changes. We view these changes as Modification Policies, which can be adopted by the workflow administrator (WFA). When business processes change, because of some event internal or external to the organization, the changes are generally planned, revised, approved and specified by high level managers or consultants, and then propagated to operational level. We see the role of the WFA, not different from a database administrator, who acts as a mediator between management's proposals and strategies, and the propagation of these proposals to the operational level. WFA thus has to be capable of translating process changes into workflow models, and making decisions regarding handling of active workflow instances. Modification Policies, which may be adopted by the WFA, are:

Flush

In flush situations all current instances are allowed to complete according to the old process model, but new instances are planned to follow new model. New instances may be put on hold, until all current instances have completed. However, the two

specifications could also be allowed exist simultaneously, and be treated as two different models. For example, immigration policies could be changed by new government regulations, effecting all applicants who apply after a certain date. However, ongoing applicants remain unaffected, i.e., their applications would be processed according to old rules, causing the two schemas to co-exist in the transition period.

Abort

Active workflow instances may be aborted when the process model is changed. Abort is most commonly used for adaptation of individual instances, for example canceling a reservation. However, it may also be a result of a radical change in the organization, for example, the management of a purchasing office may be changed because of bad planning and procedures practiced previously. To overcome the crisis, the new management may cancel all current purchasing orders, reallocate the budget, and introduce a new purchasing procedure. Cancellation of the purchasing orders would cause current instances of the workflow to abort, and then restart according to new procedures. This approach may incur losses to the organization, for example, the organization may be penalized for order cancellation in the form of fines, reputation etc. In some cases the losses may be unacceptable, for example in a manufacturing environment, an abort means that components assembled so far are either wasted, or have to be disassembled. In most cases, abort will require undoing, or compensating for the work accomplished so far.

Migrate

The change effects all current instances but it has to be introduced without allowing current instances to abort or flush. Current instances would normally be in different stages of process execution. The main problem arises when an instance is at a stage where tasks already accomplished have affected the process in such a way that subsequent tasks are unable to proceed in accordance with the new specification. Thus migration may involve undo or compensation of completed tasks, in order to bring the instance in compliance with the new specification. The worst case is when the complete process has to be rolled back to the start, that is all work is lost or undone. This special case is equivalent to Abort. Taking the example of immigration again, the new government may require all applicants, current and new, to sit for an English language test before the application is finally approved. Thus an additional task is introduced which has to be executed at an appropriate time for all current instances. When it is actually executed, will be dependent on the instance.

Adapt

Adapt includes cases of errors and exceptions, where the process model may not change permanently, but some instances have to be treated differently because of some exceptional and unforeseen circumstances. For example, in a university admission process there could be an applicant with a background in information systems and computer science, who is applying for a doctorate in management. Reviewers in the department of management sciences may refer the application for review by faculty of computer science, to determine the potential of the applicant. Such ad-hoc changes in otherwise repetitive and predictable workflows are bound to occur once in a while.

Build

Building of a new process is also a class of process change. The difference is that the starting point is not a detailed pre-existing model, but an elementary description, which captures only the basics, or even an empty process. A typical example can be where process activities are identified, but the order of execution is mostly unknown. The advantage of including build as a class of process change, is that it allows the inclusion of processes which cannot be fully predefined, into the domain of process change. Thus essentially the same mechanism can cater for dynamic definition (build) as well as dynamic modification (migrate, adapt etc.)

The differences in the policies are highlighted in the following table:

The common denominator in all of the above policies, with the possible exception of flush, is that they effect active instances of the given process model. Thus they dictate the scope of workflow modification and constitute dynamic modification, in contrast to static modification, which is merely a change in the workflow model, i.e. no currently active instances are involved.

3The Issues

Uncontrolled changes to either workflow model or workflow instances can lead to serious inconsistent and erroneous situations. However, the problem is more severe when currently active instances are involved, that is during dynamic modification.

The main challenge here is the handling of instances that were initiated for the old workflow model, but need to comply with the new, revised model. In the following section we will discuss some critical issues with regard to managing workflows in dynamic environments.

Workflow Meta-Model

The foundations of any framework to support dynamic modification will be laid in the underlying workflow model. How the workflow model is defined, and the extent of process semantics it captures, bears significantly on the modification process. The workflow model should be capable of capturing different aspects of the business process [Jablonski 1994], [WFM Coalition 1998], including structure, data, resources, transactional and temporal properties. Identifying a complete set of task properties that capture essential aspects of process logic is critical. Although this is an issue more closely related to conceptual modeling rather than dynamic modification, the capabilities of the modeling framework will have a direct impact on the quality of support that may be provided for dynamic modification. In turn, dynamic modification may identify potential weaknesses and deficiencies of the process meta-model. For example, defining an additional time constraint that process definition does not support, or assigning clients on the basis of roles in a model that only allows explicit client assignment. We observe a hierarchy of modifications. Modifications that affect process instances, as in adapt and abort. Modifications that also cause the process model to be changed, as in migrate, flush and build. And modifications that indicate inadequacy of the process meta-model. Solutions to the last problem requires an investigation into key questions as to what is the scope of support from workflow technology, organization’s purpose and motivation for using workflow technology, and the currently available products in the market.

Modification Language

An appropriate modification language is fundamental for supporting the process of dynamic modification of workflows. This language should consist of a set of complete and minimal operations, capable of specifying any modification. There are two challenges involved. First is to identify the complete and minimal operations, and second is to design the operations. In designing the operations, we observe an interesting trade-off between flexibility of specification and support for verification. Operations that are designed to ensure correctness compromise flexibility of specification. However, flexible operations do not necessarily compromise correctness. Recent research in this area has mostly focused on designing operations that guarantee the (structural) correctness of the new model [Casati et al., 1996], [Reichert &Dadam 1997]. Ideally subgraphs of the workflow graph should be changed, without having to perform each operation one by one, or in any specific

order. Since no instances are involved during the modification of the model, condition for correctness after each operation unnecessarily restricts the modifier. This degree of flexibility is possible if modification operations are encapsulated into transactions,and only begin and end of the transaction guarantees WF correctness. The ideal situation is where control over the granularity of the modification transaction is given to the ‘modifier’, and system verification of the model is imposed only after completely specifying the modifications to the workflow model.

In any case, end result of any modification process has to be a model that satisfies all correctness constraints. When the modification is put into effect, current instances are expected to comply with the revised model. If the model is allowed to be changed without control, we may end up with a drastically different model. It is necessary for the modification process to result in not only a correct workflow, but also to achieve it with minimum, designated operations. The target being to ensure that the effort required in conforming existing instances to the revised model is kept at a minimum

Compliance Criteria

As stated earlier, dynamic modification generally involves active instances. Switching these instances to the new model may not always be possible straight away. Instances represented by subgraphs which cannot be ‘traced’ in the new model are non-compliant to the new process. Defining and determining compliance is crucial to the process of dynamic modification. The most obvious way to determine compliance is to base it on the strict structural equivalence of subgraphs. However, various examples demonstrate that compliance can be found, even when strict structural equivalence cannot be established. Even though establishing graph equivalence is computationally hard, there is sufficient evidence that certain classes of equivalent structures can be identified for the specialized workflow graphs. These classes can then be used to bring the notion of compliance to a refined, more practical level.

(a) Change in Structure (b) Change in Task Properties

Fig. 1. Examples of Compliance

An example of such an equivalent structure with respect to compliance is given

in Figure 1 (a). Other structures remaining the same, an instance that is currently executing task 4, should remain compliant to the modified structure in either direction. That is serial tasks 2 and 3 to be executed in parallel, or vice versa.

Furthermore, instances may also remain compliant when certain properties of the tasks are changed, other things remaining the same. For example in Figure 1 (b), maximum allowed duration for task 2 may be reduced from 7 days to 3 days, which changes the specification of time constraints. Let task 9 represent the revised task 2. Even though, there is no structural equivalence, undoing task 2 for an instance where it has already completed is not sensible. On the other hand, underlying application for a task may be changed, which causes new or changed data to be generated. This data may cause successive tasks to be executed or performed differently. The work accomplished by these tasks may have to be undone to cater for the modification, indicating non-compliance of affected instances. A classification of task properties on the basis of effect on compliance is a first step towards refining the compliance criteria.

4Supporting Dynamic Modification of Workflows

There is substantial ongoing research in this area. Significant research has been done on the conceptual specification of workflow model and provision of change operations which guarantee the (structural) correctness of the changed model [Casati et al., 1996], [Reichert &Dadam 1997]. A mathematical formalism to model and analyze dynamic structural changes is introduced in [Ellis et al., 1995]. Using Petri-Nets to model Workflows, [Aalst 1997] present a set of transformation rules to construct and modify the workflow. Research on dynamic modification mostly concentrates on handling of exceptional instances, which is adapt policy. [Reichert & Dadam 1997] present the most notable framework. Similar work is also found in [Han et al., 1995], [Hermann 1995]. Related aspect of this area, where the workflow model cannot be built completely prior to execution and is dynamically defined at runtime, is also being investigated [Cichocki & Rusinkiewicz 1997].

We propose a simple yet effective framework to handle the modification policies identified in previous sections. The framework is based on a three-phase modification methodology that consists of defining, conforming to and effectuating the modification. We will briefly describe the three phases in the following sections. The formal specifications of the underlying workflow model and detailed procedures for the methodology can be found in [Sadiq & Orlowska 1998].

Defining the Modification

The modification process begins by defining the modification, which constitutes specifying the modification policy, specifying the affected instances in case of abort

or adapt, and specifying the changes to be made to the workflow model. We define M to be the Modification on the Workflow W, such that M: W k W k+1 where W k is Workflow Model Version k

M consists of a sequence of prescribed operations which when performed upon W k, will give W k+1. Our primary motivation in designing the operations was to provide complete flexibility of specification to the modifier. We allow subgraphs of the (graphical) workflow model to be changed within one modification transaction. The correctness of the model is verified by a verification engine at user specified intervals. The correctness properties and verification algorithms for the workflow model can be found in [Sadiq & Orlowska 1997]. These have been implemented in a prototype FlowMake. FlowMake is a graphical modeling tool supported by a verification engine that verifies the workflow graph by identifying structural conflicts.

Conforming to the Modification

After defining the modification, the next step is to bring the affected instances of W k in conformity with the specifications of W k+1. Instances must be grouped with respect to progress or stage, if automation is to be provided, else the process will reduce to individual handling of every affected instance. We have proposed a three level grouping scheme. At the first level, instances are grouped on the basis of Compliance. At the second level, the stage of the non-compliant instances is determined. It would be unrealistic to assume that there would never be a situation during the modification of active instances where external intervention will not be required. It is conceivable that instances may be at such a stage that trying to adjust the instances will be too difficult, or equivalent to abort. These instances may have to be handled externally. At second level, instances are grouped on this basis, i.e. whether compliance can be achieved within system, or externally. At the third level, the remaining non-compliant instances are grouped with respect to their class (same subgraph).

We have further proposed the concept of C ompliance Graphs for affected instances. The Compliance Graph CG i for instance i initialized under W k, defines a bridge between W k and W k+1. An instance i follows a unique path which consists partially of W k, the compliance graph, and partially of W k+1. The construction algorithm and properties of CG i are detailed in [Sadiq & Orlowska 1998]. Briefly, the algorithm identifies actions or compensations necessary to achieve compliance for instance i, and a suitable ‘plug’ point in W k+1. Compliance graphs thus provide revised schedules, which chart out the plan till completion for affected instances. Thus except for the (hopefully small) group of instances identified in level 2 grouping, the workflow management system can continue to provide full automated support for the changed business process.

Effectuating the Modification

The last phase in the modification procedure is that of effectuating the modification. This relates to the handling of workflow execution during the transition period. The transition period is signified by instances that started with the old model but are still executing. Instances may follow old model (e.g. in flush), or new model (for instances initialized after modification has been defined), or revised schedules based on compliance graphs. Instance execution, which may have been put on hold, will restart. When all instances following old model or revised schedules have completed, the new model becomes the current workflow model, and the modification process is over.

5Contributions

Deploying workflow technology for business process automation is hard, and in many cases the benefits may be debatable. Trying to handle the modification of such a system is consequently even harder. In this paper we have attempted to provide an insight into the challenges and issues involved in managing workflows in dynamic environments. Given the complexity involved in dynamic modification of workflows, that is changes in business processes which affect active instances of the workflow, it would be unrealistic to assume that workflow technology would always hold a promise of increased productivity and superior management. Suitability of the business environment and nature of the processes involved are key factors that cannot be ignored.

We have defined the scope of workflow modification through 5 modification policies of Flush, Abort, Migrate, Adapt and Build. The issue of compliance and the subsequent undoing and compensation effort that follows plays a significant role in almost all these policies. We further proposed a framework to support dynamic modification of workflows. The strength of the framework lies in its ability to uniformly support all classes of workflow modification. It is not limited to handling workflow schema change, or adaptation of individual instances. Provision for the different classes of workflow modification is essentially made in the second phase of the proposed methodology, where the construction of the compliance graph is driven by the specified modification policy.

References

Aalst W.M.P. van der (1997) Verification of Workflow Nets. In Application and Theory of Petri Nets, Editors P. Azema and G. Balbo, Volume 1248 of Lecture Notes in Computer Science

Aalst W.M.P. van der, Hee K.M. van, Houben G.J. (1994) Modeling and Analyzing Workflow using a Petri-net based approach, Proceedings of Second Workshop on Computer-supported Cooperative Work, Petri nets related formalisms, Pages 31-50, 1994. Editors G.

De Michelis, C. Ellis and G. Memmi, P.

Burch John G., Grudnitski Gary (1989) Information Systems Theory and Practice, 5th Edition,

John Wiley and Sons.

Casati F., Ceri S., Pernici B., Pozzi G. (1995) Conceptual Modeling of Workflows. Proceedings of 14th Object Oriented and Entity-Relationship Approach international Conference, Gold Coast, Australia, Springer Verlag Lecture Notes in Computer Science 341-35.

Casati F., Ceri S., Pernici B., Pozzi G. (1996) Workflow Evolution. In Proceedings of the 15th International Conference on Conceptual Modeling, ER’96, Cottbus, Germany. Springer Verlag, Lecture Notes in Computer Science.

Cichocki A., Rusinkiewicz M. (1997) Migrating Workflows. In A. Dogac et al., Advances in Workflow Management Systems and Interoperability, NATO Advanced Study Institute, pages 311 –326, NATO, Istanbul, Turkey.

Davenport Thomas (1993) Process Innovation – Reengineering work through Information Technology. Harvard Business School Press.

Eder J., Liebhart W. (1995) The workflow activity model WAMO. Proceedings of the 3rd international conference on Cooperative Information Systems (CoopIs), Vienna, Austria, May 1995.

.Ellis S., Keddara K., Rozenberg G. (1995) Dynamic Changes within Workflow Systems.

Proceedings of ACM Conference on Organizational Computing Systems (COOCS 95).

.Georgakopoulos D., Hornick M., Sheth A. (1995) An Overview of Workflow Management: From Process Modeling to Workflow Automation Infrastructure. Journal on Distributed and Parallel Databases, 3(2):119-153.

.Hammer Michael, Champy James (1993) Reengineering the Corporation- A Manifesto for Business Revolution, Nicholas Brealey Publishing, London.

.Hermann T., (1995) Workflow Management Systems: Ensuring Organizational Flexibility by Possibilities of Adaptation and Negotiation., Proceedings of ACM Conference on Organizational Computing Systems (COOCS 95).

.Han Y., Himminghofer J, Schaaf T., Wikarski D., (1995) Management of Workflow Resources to Support Runtime Adaptability and System Evaluation., Proceedings of PAKM'96 International Conference on Knowledge Engineering, Basel, Switzerland, Oct 1996. Han.Yanbo, Sheth Amit (1998) A Taxonomy of Adaptive Workflow Management, Towards Adaptive Workflow Systems, Workshop in Conference on Computer Supported Cooperative Work, Seattle, USA, Nov 1998.

.Jablonski Stefan (1994) MOBILE: A Modular Workflow Model and Architecture. Proceedings of 4th International Conference on Dynamic Modeling and Information Systems, Netherlands.

Mohan C. (1996) Tutorial: State of the Art in Workflow Management System Research and Products, 5th International Conference on Extending Database Technology, A vignon, France, March 1996.

Reichert Manfred, Dadam Peter (1997) ADEPTflex - Supporting Dynamic Changes of Workflow without loosing control. Journal of Intelligent Information Systems (JIIS), Special Issue on Workflow and Process Management

Strong Diane M., Miller Steven M. (1995) Exceptions and Exception Handling in Computerized Information Processes, ACM Transactions on Information Systems, Vol.

13, No 2, Pages 206-233, April 1995.

Saastomoinen Heikki, White George M. (1995) On Handling Exceptions, Proceedings of ACM Conference on Organizational Computing Systems (COOCS 95), Milpitas, CA. USA, Nov 1995.

Sadiq Wasim, Orlowska Maria E. (1997) On Correctness Issues in Conceptual Modeling of Workflows. In Proceedings of the 5th European Conference on Information Systems (ECIS ‘97), Cork, Ireland, June 19-21, 1997.

Sadiq Shazia Wasim, Orlowska Maria E. (1998) Dynamic Modification of Workflows.

Technical Report No. 442, University of Queensland, Brisbane, Australia, October 1998. Workflow Management Coalition (1998) Interface 1: Process Definition Interchange, Process Model, Document Number WfMC TC-1016-p.

前台新进员工带教手册(V11)

前台新进员工带教手册 目录 一、海友酒店介绍 1.1品牌故事 1.2产品特征 1.3目标客户群 二、海友酒店前台交接班制度 2.1 交接班准备 2.2 交接事项 2.3 填写交接班本 2.4 接班事项 2.5 交接班签名 三、海友酒店前台员工带教计划 3.1 带教目的 3.2 带教内容 一、海友酒店介绍: 1.1品牌故事 海友酒店是华住酒店集团(原汉庭酒店集团)旗下的风格经济型酒店连锁品牌,致力于为有预算要求 的客人提供“欢乐、超值”的住宿产品。 我们全情投入,与顾客真诚沟通,分享快乐,为客人提供愉快、舒适的住宿体验。一切从我们的“HI”开始。。。。。。 2005年初,华住在中国正式创立,同年8月,第1家门店开业,2006年底,旗下的汉庭酒店第34 家开业。2007年7月,华住以股权融资8500万美元创下中国服务行业首轮融资的新纪录,2007年底,汉庭酒店第74家开业。2008年初,汉庭在全国签约门店数达到180家,完成了全国主要城市的布局,并重 点在长三角、环渤海湾、珠三角和中西部发达城市形成了密布的酒店网络,成为国内成长最快的连锁酒店品牌之一。2008年4月,汉庭已开业酒店超过100家,出租率、经营业绩各项指标均在业内处于领先地位。 2008年2月,华住酒店集团正式成立,是国内第一家多品牌的酒店集团。华住致力于实现“中国服务”的理想,即打造世界级的中国服务品牌。华住的愿景是“成为世界住宿业领先品牌集团”,为此,我们将不断追求精细化的管理,实施标准化的体系和流程,更全面、更迅速地推进集团化发展。华住酒店集团旗下目前拥有禧玥酒店、星程酒店、汉庭酒店、全季酒店、海友酒店五个系列品牌,我们将坚持时尚现代、便捷舒适、高性价比的优势特点,塑造中国酒店的典范。

中华淘金网商业计划书--商业计划书

中华淘金网商业计划书--商业计划书 第一部分网页提案 目录 1、策略综述 2、意念的引入 3、站点基本描述 4、功能的实现以及费用的预算 5、项目进度安排 6、维护与升级 7、未来扩展项目 8、附录 1、意念的引入 在当前的网络社会中,由于技术上的原因,当前网民在网络中的自由受到诸多的限制。我们不妨将当前的网络世界比做人类社会发展史上的原始社会,当中的网民犹如原始社会中的原始人,在他们力所能及的网络空间内进行一系列的采集-狩猎活动。面对这些原始人,我们只能以非常简单的思维模式去考虑他们在网络空间的行为。 如何吸引他们到我们的网站进行采集--狩猎活动? 人类的需要是多元化的。按马斯洛对人类需要的分层,结合当前网络社会的特点分析上网的人,他们在现实世界已解决了最基本生理需要,包括避免饥饿,逃避危险等,在网上虚拟的空间他们所追求,将是较高层次的多元化需求,如获得爱与尊重,实现自我价值。 如何才能满足网民高层次多元化需求的满足呢? 一方面是简单的思维与行为模式,一方面是高层次多元化需求的满足。如何把这两方面有效的结合起来将是我们的网站成功的关键。 2、策略综述 利而诱之是我们的第一个策略。 综观当前的各类网站,主要为网民提供了各种各样的服务,包括提供各类的新闻、图片资讯;让网民注册,申请电子邮箱,免费主页空间,进行聊天;有的甚至提供物品的拍卖,网上购物服务,归根结底,他们就是要吸引网民的注意力,让他们在网站进行采集--狩猎活动。我们也将采取这一策略,但侧重于网络派钱的概念。 强调商业操作是我们的第二个策略

考察各种大众媒体工具(mass media)的发展史,我们可以看到每一种大众媒体工具(如广播,报纸,电视广播)的背后都有一套完善的商业操作,以及有效的资金来源支撑着。网络营运也必须找到它的资金来源。 在当今网络原始时代,众人都希望在网络营运中找到那只会下金蛋的母鸡。我们也不例外,一系列的商业操作(那只会下金蛋的母鸡)将是我们网站生存的关键。 倡导创意将是我们的第三个策略。 人是一种狡猾的动物,在原始本能驱动下所产生的动机,往往要堂而皇之地掩饰一番。为扩大我们网站的受众,提高我们网站的品位,倡导创意将是必不可少的。创意正是根源人类具有不安守本份的本能冲动。满足了人类这一本能冲动的网站将是成功的。 倡导多元化是我们的第四个策略 世界在网络的联结下变得越来越小,网络空间所聚集的人来自不同的国家地区,有着不同的需求。我们并不幻想以单一的网站满足网民的所有需要,但我们会以一系列网群的策划来实现多元化。 3、站点基本描述 A、站点结构概念 多面体两层结构:固定的STATION WEB SITE与流动的TOPIC WEB SITE,最大限度地网罗资讯与网民。我们所重视不是单一网站的概念,我们的视线亦将不再是局限于单一网站的建设,我们倡导网站群的概念,从整体上来规划一系列的网站。 我们这些单独网站之间的有机连接将形成一个以中华淘金网为首的网站群。 我们的网站群分为两类: 一类是两个固定的STATION WEB SITE,特点是长期存在,规模大,交互功能强,是进行BtoC、BtoB的服务界面。我们将设置一个主要的网站:面对网民和面对企业的的淘金网。 一类是一系列流动的TOPIC WEB SITE。特点是主题鲜明,内容简洁,规模小,极具娱乐性、艺术性与时效性,存在时间根据其主题以及赞助商来定,一般不超过一年。 固定的网站在一系列小型流动的网站包围下,互相进行功能的互补,分工是十分明确的。我们的设想是以淘金网为主导,通过淘金网进行一系列的市场营销活动以及市场调研活动,另一方面,淘金网又以有偿定向投稿的方式为一系列的流动主题网站提供源源不断的资讯更新。而流动主题网站则通过鲜明的主体吸引广大的网民进行浏览,以及引导网民进入我们的淘金网,负起扩大淘金网与外界联系的功能。

基于因子分析法的我国2012年各类型商业银行的经营业绩及排名

理学院课程项目 课程名称: 数据分析 题 目: 基于因子分析法的我国2012年各类型 商业银行的经营业绩及排名 班 级: 信科112 姓名学号: 冯力 11480010242 指导教师: 梁方楚 2014年5月30日

目录 摘要 (1) 1 问题的提出 (1) 2 研究背景 (1) 3 因子分析法的数学模型 (2) 3.1因子分析法的概念 (2) 3.2因子分析的计算步骤 (2) 4 样本的选择和指标体系的建立 (4) 4.1 样本的选择 (4) 4.2 我国上市银行经营绩效评价的指标选取 (4) 5 各类银行因子分析及其结果 (5) 5.1 数据查找 (5) 5.2数据处理 (5) 6 结论 (10) 7 参考文献 (11) 8 课程小结体会 (12) 附录 (13)

摘要 报告选取了中国银行,工商银行,建设银行,交通银行,中国农业银行,中信银行,中国民生银行,招商银行,中国兴业银行等16家具有代表性的国内上市商业银行作为此次研究的样本,这16家商业银行中包括5家国有控股商业银行,11家大中小型股份制商业银行,然后通过借鉴我国现行的商业银行业绩评价体系,最终确定了总资产收益率、人均利润、成本收入比、营业收入利润率、资本充足率、不良贷款率、拨备覆盖率、流动比率、存贷比率、存款增长率和非利息收入增长率为评价的11个指标,从各个方面对商业银行的经营业绩进行评价。 关键词:商业银行评价指标经营业绩因子分析

1 问题的提出 商业银行是经营货币资金、授受信用的特殊企业,是现代金融体系的重要组成部分。高效健全的银行体系能够为社会提供方便快捷的服务,安全稳健的银行经营对国民经济发展具有重要意义,同时经营绩效的高低不但会关系到银行本身能否良好运作,而且对整个国家宏观经济运行有着重大影响。 2 研究背景 随着我国银行业的全面开放,国内银行将面临更大的挑战和考验,在日益激烈的竞争环境中,商业银行提高经营绩效,增强竞争力势在必行。在这种背景下,按照现代商业银行经营绩效管理的要求,对我国的商业银行进行科学全面的评价,发现现阶段商业银行经营管理中存在的不足并提出应对方法,从而提高商业银行经营的绩效,就不仅是商业银行自身发展的客观需要,更是商业银行应对国际挑战和竞争的现实需要。

新员工带教流程

新员工带教流程 第一天: 熟悉公司的作息时间,了解公司基本状况,基本服务礼仪与动作规范,学习做迎宾。 1、上班时间:10:00---19:30 12:00----21:00 (转正前) 10:00--16:00 14:30---21:00(转正后) 备注:时间根据季节调整。 2、管理手册:P1、江明商贸简介(了解即可,店长须以解说的方式进行); 3、服务礼仪:1)仪容仪表标准; 2)服务动作规范(站姿、蹲姿、距离、手势、角度); 3)学习做迎宾(声音、表情、语调、迎宾位置); 4)电话礼仪; 第二天: 了解公司的考勤制度,产品的风格分类及陈列 1、相关制度的了解:《考勤制度及请假报批程序》《离职程序》; 2、产品风格分类(①以鞋来区分:男鞋、女鞋、童鞋②以季节来区分:春秋单鞋、夏季凉鞋、冬靴③以鞋头区分:尖头、圆头、方头④以鞋跟来区分:平跟3CM以下、中跟3.1CM--5CM、高跟5.1CM---8CM、特高跟8.1CM 以上⑤以鞋帮来区分:凉(拖)鞋、中空鞋、浅口鞋、满帮(低腰)鞋、短靴(筒高14CM以下)、中靴(筒高15--22CM)、长靴(筒高23--36CM);(以店铺现有货品实物讲解方式进行带教) 3、了解什么是陈列,为什么做陈列、陈列标准及陈列原则。 第三天: 掌握《会员卡》的办理及使用规范,相关票据的填写及操作流程,鞋类产品从哪六个方面进行描述。 1、“会员卡”的申办标准及使用细则; 2、相关票据:《销售单、销售退货单》《调拨单》《会员单》正确填写; 3、鞋类产品从:楦型、皮料、底材、高度、风格、线条六方面描述(以实物操作讲解带教为标准); 4、服务1--2步:细节重点的掌握及实操应用。 第四天: 了解鞋类基本皮料、材质的特性及打理保养方法,所属品牌货号含义,FABE\法则应用,服务三、 四步,轮流做迎宾。 1、皮料特征及打理方法、皮料的分类(牛、羊、猪、打蜡、漆皮、磨砂皮);(以店铺现有货品实物讲解方式进行带教) 2、了解所属品牌货号的含义; 3、服务技巧之FABE、含义理解及应用; 4、服务三、四步的细节重点的掌握及实操应用。 第五天: 学习掌握公司销售技巧及服务规范流程和语言表达标准、掌握做报表及相关单据技能,初步了解库存及货品摆放位置,服务五、六步、协助做销售。 1、销售技巧:USP/AIDA的含义及实操应用(以场景模拟带教实操为主) AIDA A:注意(Attention) 1)商品陈列 2)导购员的仪容、仪表 3)精神奕奕热忱的招呼(三声) 4)卖场气氛 I:兴趣(Interest) 1)接近顾客了解顾客购物动机 2)让顾客触摸商品 3)有效介绍货品的特性及卖点 4)为顾客做参谋 5)邀请试穿 D:欲望(Desire) 1)介绍FAB及USB 2)强调物超所值不可代替 3)化解顾客疑虑及异议 A:行动(Action) 1)把握时机完成交易 2)介绍打理知识 3)介绍其他配成产品 4)付款过程快速 USP(Unique selling piont)独特销售点: 质料、设计款式、手工、处理方法、色彩、价钱 2、开放式与封闭式的语言技巧:产品推荐:O O C 促成销售: C O C 3、初步了解库存及货品的摆放位置、辅助老员工做销售 4、掌握报表的正确填写、各项单据的电脑操作

0027~0030-旅游投资的商业模式研究――3L坐标分析法

旅游投资的商业模式研究――3L坐标分析法 2005年12月5日第3506期2005年12月12日第3509期 2005年12月19日第3512期2005年12月26日第3515期 杨光林峰 一、3L坐标分析法 民间投资商,已经成为旅游产业发展的主力军。这些旅游投资人,对于如何锁定风景及土地资源、如何确定项目的主题与市场定位、如何建设出具有吸引力的产品、如何实施有效的营销,最为重要的是如何获取盈利,都在反复思考,并感到不易把握。 投资商最关心的,就是如何获取利润。 旅游产业的综合行太强,投入大而获利周期长,因此盈利方式很难用简单的算数进行计算。对盈利方式中的盈利时序、盈利大小、盈利结构没有搞明白时,投资的决心是很难下定的。如果此时投资进入运作,往往会形成“摸着石头过河”的局面,走一步看一步。结果一般都是:效率低下,大走弯路。 旅游开发所涉的层面很多,开发运作环节复杂,交叉联动行业多。明晰的商业模式可以让投资者透过错综复杂的表象,看清具体项目的关键问题所在,项目的风险和利润所在,在具体的运作中能够从容以对。 因此,借助专业机构的经验与技术,进行旅游项目开发的商业模式设计,是投资商借脑中最重要的一个环节。 旅游商业模式设计――全面综合的研究旅游项目开发,系统解决锁定资源、定位主题与市场、设计并成型产品、制定营销战略,清晰建构盈利模式。 设计合理的商业模式需要实用有效的技术工具,通过该工具可以将投资过程中可能涉及到的各个层面和问题加以考虑,找出最适合项目的解决方案。 我们为此长期研究旅游产业经济及具体投资项目,并逐步建立了一套旅游投资商业模式专用分析工具――3L坐标分析法(或三链坐标分析法)。 通过持续的具体项目实践和理论研究,我们发现,由三个角度出发的链条(旅游业价值链、旅游开发运作链、旅游产业联动链)构成的坐标系(如下图所示)。在旅游产业中所有可能的商业模式,都能在该坐标系中找到位置;而任何旅游产业的项目,都可以运用3L坐标进行分析,从而发现盈利点、盈利结构,并由此形成商业模式的构架;对于旅游企业或正在经营中的旅游景区,运用3L坐标进行分析,可以对企业或景区进行诊断,发现其原有商业模式的缺陷,找到新的盈利增长点,寻找出可持续扩展的盈利新模式。

前台新进员工带教手册

一、海友酒店介绍 1.1 品牌故事 1.2 产品特征 1.3目标客户群 二、海友酒店前台交接班制度 交接班准备 交接事项 填写交接班本 接班事项 交接班签名 海友酒店前台员工带教计划带教目的 带教内容 海友酒店介绍:前台新进员工带教手册 目录

1.1 品牌故事 海友酒店是华住酒店集团(原汉庭酒店集团)旗下的风格经济型酒店连锁品牌,致力于为有预算要求的客人提供“欢乐、超值”的住宿产品。 我们全情投入,与顾客真诚沟通,分享快乐,为客人提供愉快、舒适的住宿体验。一切从我们的“HI”开始。。。。。。 2005 年初,华住在中国正式创立,同年8 月,第1 家门店开业,2006 年底,旗下的汉庭酒店第34 家开业。2007 年7 月,华住以股权融资8500 万美元创下中国服务行业首轮融资的新纪录,2007 年底,汉庭酒店第74 家开业。2008 年初,汉庭在全国签约门店数达到180 家,完成了全国主要城市的布局,并重点在长三角、环渤海湾、珠三角和中西部发达城市形成了密布的酒店网络,成为国内成长最快的连锁酒店品牌之一。2008 年4 月,汉庭已 开业酒店超过100 家,出租率、经营业绩各项指标均在业内处于领先地位。 2008 年2 月,华住酒店集团正式成立,是国内第一家多品牌的酒店集团。华住致力于实现“中国服务”的理想,即打造世界级的中国服务品牌。华住的愿景是“成为世界住宿业领先品牌集团”,为此,我们将不断追求精细化的管理,实施标准化的体系和流程,更全面、更迅速地推进集团化发展。华住酒店集团旗下目前拥有禧玥酒店、 星程酒店、汉庭酒店、全季酒店、海友酒店五个系列品牌,我们将坚持时尚现代、便捷舒适、高性价比的优势特点,塑造中国酒店的典范。 1.2 产品特征 装饰风格简约时尚 公共区域提供免费网吧 全酒店无线覆盖 独立淋浴、写字桌、电视机 提供大毛巾 自助理念 1.3 目标客户群 有预算要求的商务客人、家庭型散客、青年群体、长住客、背包客二、海友酒店前台交接班制度:交班前准备整理前台物品; 检查必备品和表格;

营销六步法

营销六步法 区域市场的运作是一个公司整体营销战略规划的一个有机组成部份;也是营销战略规划在执行中的具体体现。可以说,区域市场的操作成败在很大程度上决定着公司的整体营销业绩。根据个人的实践经验和书籍的查阅我认为,可以采取以下六个步骤来开展区域市场的营销工作: 一、划分区域市场,确定策略目标 首先,确定范围,定位类型,区域营销策略具体化。 通常来讲,市场与销售的开拓,总是存在一个逐步扩展的过程,很少有哪一家公司一开始就齐头并进地开发全国范围的市场。这就要求不同规模、实力的企业,不同产品结构的企业,必须确定大小不同的目标区域市场的空间范围。 在具体确定了区域范围后,必须对区域市场进行分类定位,划分出不同的区域类型,如大本营区域、根据地区域、运动区域、游击区域。不同类型的区域,推行不同的营销策略: 1、大本营区域是公司绝对占领(市场占有率在60%以上)的区域,对这类区域公司必须确保投入,将营销分支机构建立到县级甚至乡镇市场层面进行深度分销,牢固地占领终端网络对区域市场进行精耕细作; 2、根据地区域是公司绝对控制(市场占有率在40%以上)的区域,对这类区域公司应该重点投入,采取经销商与终端相结合的渠道策略(30%投入花在经销商身上70%投入花在终端上),有重点、针对性地与竞争对手开展竞争; 3、运动区域是公司没有相应的投入在短期内不容易占据主导地位的区域,

因此,最好避实就虚与对手开展竞争,在渠道上以零售终端带动经销商上量为主(70%投入花在经销商身上30%投入花在终端上),力争将市场占有率控制在20%左右; 4、游击区域是公司还没有客户基础的市场,对这类区域公司没有必要投入人财物力,采取现款现货的营销模式即可。 其次,进行区域细分,确定每个分区的具体业务拓展目标。 在确定了区域范围后,再综合考虑行政区划、人口数量、消费水平、交通条件、客户分布、政策投入等相关因素,将该区域进一步细分为若干个分区。并具体确定每个分区的市场开发和产品推广进度、目标任务(含销售数量和销售金额)、目标市场占有率、目标经销商和零售终端等分销客户的名称。如某医药生产企业将全国分为华中、华南、华北、华东等大区;再进一步又将华中分为河南、江西、安徽、湖南、重庆、湖北六个分区;其中湖北分区以"九州通""新龙"等经销商、以"中联""马应龙""同济堂""三九"等零售终端为目标客户,力争在2004年年底前实现销售额500万元,市场份额达到50%以上。 二、深入实际调查,建立客户档案 虽然确定了分区内的目标经销商和零售终端等分销客户的名称,但此时我们可能对它还一无所知或知有不尽,这就要求我们的业务人员必须进一步开展深入实际的调查工作,详细、真实地了解它们的相关情况。通常的做法是建立目标客户档案。客户建档工作有三点值得注意: 第一,档案信息必须全面详细。客户档案所反应的客户信息,是我们对该客户确定一对一的具体销售政策的重要依据。因此,档案的建立,除了客户名称、地址、联系人、电话这些最基本的信息之外,还应包括它的经营特色、行业地位

旅游投资的商业模式研究:3L坐标分析法-绿维创景

旅游投资的商业模式研究 ——3L坐标分析法旅游与文化规划设计专家旅游与文化导向的区域综合开发服务商 北京绿维创景规划设计院 New Dimension Planning & Design Institute Ltd. 旅游运营网https://www.doczj.com/doc/8d9670022.html,旅游景观设计网https://www.doczj.com/doc/8d9670022.html, 创意建筑设计网https://www.doczj.com/doc/8d9670022.html,旅游投融资网https://www.doczj.com/doc/8d9670022.html, 版权声明:该报告知识产权归北京绿维创景规划设计院所有,未经允许,不得擅自篡改、挪用、从事盈利性宣传活动,违者将追究法律责任。

旅游运营网 https://www.doczj.com/doc/8d9670022.html, 旅游投资的商业模式研究 ——3L 坐标分析法 北京绿维创景规划设计院 一、3L 坐标分析法 民间投资商,已经成为旅游产业发展的主力军。这些旅游投资人,对于如何锁定风景及土地资源、如何确定项目的主题与市场定位、如何建设出具有吸引力的产品、如何实施有效的营销,最为重要的是如何获取盈利,都在反复思考,并感到不易把握。 投资商最关心的,就是如何获取利润。 旅游产业的综合行太强,投入大而获利周期长,因此盈利方式很难用简单的算数进行计算。对盈利方式中的盈利时序、盈利大小、盈利结构没有搞明白时,投资的决心是很难下定的。如果此时投资进入运作,往往会形成“摸着石头过河”的局面,走一步看一步。结果一般都是:效率低下,大走弯路。 旅游开发所涉的层面很多,开发运作环节复杂,交叉联动行业多。明晰的商业模式可以让投资者透过错综复杂的表象,看清具体项目的关键问题所在,项目的风险和利润所在,在具体的运作中能够从容以对。 因此,借助专业机构的经验与技术,进行旅游项目开发的商业模式设计,是投资商借脑中最重要的一个环节。

商业项目招商的各种说法操作方法牢骚及案例

商业项目招商的各种说法操作方法牢骚及案例 Document serial number【UU89WT-UU98YT-UU8CB-UUUT-UUT108】

商业项目的各种说法、操作方法、牢骚及案例从本世纪初开始:许多做住宅产品好好的开发企业终于耐不住寂寞与诱惑一头扎进开发的汪洋大海之中,这其中有的开发商呛了多少盐水终于游到了彼岸,有的刚下水就不见身影,有的则还在波浪中垂死挣扎,有的早早举起求救的双手,只有少数开发商能一帆风顺…… 这是为什么呢笔者在担任上海文博堂不动产营销机构的首席策划的几年间,经历了数十个商业楼盘的,其中的酸甜苦辣和喜怒哀乐自然能就说几句闲话…… 一、成功与失败的原因在那里 成功者:根据笔者公司的分析:一定规模的成功商业楼盘大多集中地1—2线大都市:如北京的王府井边的东方新天地;上海的徐家汇商业区;无锡的崇安寺生活步行街区;南通的明都广场;苏州的左岸步行街等。我们发现上述商业楼盘只所以较为成功是因为:①大多在传统的商业街区。②大多开发商具备一定的实力,包括开发商一开始就有“放长线钓大鱼”的理念与目标③大多有合情合理的开发规模,合情合理的商业定位④大多有科学的规化,科学的、科学的售留比例。失败者:与上述相反:①大多规模过大,过多讲究所谓的后现代,在造这个城市10年后或若干年后的商业物业;②大多开发商以出售物业为终极手段与目的;③大多开发商盲目的在一些3—4线城市开发所谓“城市名片工程”;④大多开发商是先造建筑产品、先出售建筑产品,不讲究功能定位+先行+合理售留; ⑤最致命的是大多开发商不讲究合力打造,即专业的商业物业公司+良好心态与一定实力的开发商+一定支撑空壳的商户(商业品牌)

新员工带教方案V1.0

新员工带教方案 1、目的 (1)使新入职的员工尽快熟悉办公环境和公司员工,提高新员工对公司的满意度和认同度。(2)使新入职的员工初步了解工作内容和工作方式,尽快熟悉工作流程,更好的适应工作要求。 (3)评估新员工工作能力和工作态度,及时发现并解决工作中出现的问题。 2、方案周期 新员工带教方案分为两个阶段,总共六个月。第一个阶段:新入职到试用期结束的3个月;第二个阶段:新员工转正之后的三个月。 2.1第一阶段 第一个阶段主要是新员工的入职培训,使员工尽快适应工作环境和工作内容。具体实施如下: 2.1.1企业文化培训 新员工入职一周内,对新员工进行企业文化的带教,这个阶段主要由人力部门进行负责。主要涉及企业发展历史、企业文化、企业规章制度以及礼仪规范等,这个时期主要是提高新员工对公司的认知,增强员工对企业文化的认同度。在培训过程中,应与新员工建立一个友好的关系,让新员工以一种轻松的状态进入到公司环境中。 2.1.2岗位职责培训 在企业文化培训结束之后,新员工被安排到工作岗位上。从企业文化培训结束到实习期结束的这个时期,由部门主管,依据新员工的能力以及性格特点选择带教的人员,这个时期带教主要分为两个部分。 一是,对部门发展历史,工作内容,工作规范化以及工作流程的带教。帮助新员工更好了解工作流,尽快的适应新的工作内容,投入到工作中。具体流程如下: (1)制定带教计划 1)明确带教对象,针对带教对象的能力、性格等特点制定详细的带教工作计划 2)明确带教工作的内容,将工作内容分解到具体每日、每周以及每月,同时建立明确目标,考核标准以及激励奖惩办法。 (2)合理安排时间。避免出现见面就教的现状,合理利用不同时段进行教授与分享。(3)注重新员工的实践。俗话说:“授人以鱼不如授人以渔”。知识知道不等于能灵活运用,

商圈分析的内容和步骤

商圈分析的内容和步骤 在为店铺选址时,必须要明确商圈范围、了解商圈内人口因素、市场因素及一些非市场因素的有关资料,并由此评估经营效益,确定大致选址地点。经营者通过对商圈的调查分析,能够了解不同位置的商圈范围、构成及特点,并将之作为店铺选址的重要依据。 1、商圈形态 商业区:商业行为的集中区,其特色为商圈大,流动人口多、热闹、各种商店林立。其消费习性为快速、流行、娱乐、冲动购买及消费金额较高等。 住宅区:该区户数多,至少有1000户以上。住宅区的消费习性为消费者稳定,便利性、亲切感、家庭用品购买率高等。 文教区:该区附近有大、中、小学校等。文教区的消费习性为消费群以学生为多、消费金额普遍不高、休闲食品、文教用品购买率高等。 办公区:该区为办公大楼林立。办公区的消费习性为便利性、外食人口多、消费水准较高等。 混合区:住商混合、住教混合。混合区具备单一商圈形态的消费特色,属多元化的消费习性。 2、商圈的确定 对于一家尚未设立的连锁店铺而言,由于缺乏商圈统计的基本资料,当然更谈不上顾客的支持程度了。因此在从事商圈设定的考虑时,可以针对设店地区居民的生活形态及具有关联性的因素为出发点,并配合每天人口的流动情形,深入探讨该地区人口集中的原因,以及其流动的范围,以此作为基本资料来从事商圈的设定。 尤其是一家大规模的连锁经营企业,其商圈的设定并不像一般小型商店是徒步商店,可能顾客会利用各种交通工具前来,因此其商圈乃属于特性商圈,所以对于设店地区内工作、学习的人的流动性、购物者的流动性、城市规划、人口分布、公路建设、公共交通等均要加以观察,并配合各有关的调查资料,运用趋势分析以进行商圈设定。 3、商圈分析的内容与步骤 商圈分析主要包括以下九个部分内容组成: (1)人口规模及特征:人口总量和密度;年龄分布、平均教育水平;拥有住房的居民百分比;总的可支配收入;人均可支配收入;职业分布;人口变化趋势,以及到城市购买商品的近邻农村地区顾客数量和收入水平。 (2)劳动力保障:管理层的学历、工资水平;管理培训人员的学历、工资水平;普通员工的学历与工资水平。 (3)供货来源:运输成本;运输与供货时间;制造商和批发商数目;可获得性与可靠性。(4)促销:媒体的可获得性与传达频率;成本与经费情况。 (5)经济情况:主导产业;多角化程度;项目增长;免除经济和季节性波动的自由度。(6)竞争情况:现有竞争者的商业形式、位置、数量、规模、营业额、营业方针、经营风

六步搭建企业培训体系 课后测试

六步搭建企业培训体系课后测试 单选题 1、完备的培训制度的框架首先要设定()(10 分) ? A培训目标 B指导思想 C培训流程 D培训评估 正确答案:A 2、在培训效果评估中,对效果层最重要的衡量标准是什么(10 分)?A业绩提升与完成程度 B培训人员的满意度 C考试成绩 正确答案:A 多选题 1、建立企业培训制度重要的几个方面有(10 分) A制度是一系列培训活动的规则 B明确培训责任和操作程序 C明确培训工作规范化 D保证培训质量,提升培训效率 正确答案:A B C D

2、培训前,准备做需求调研,首先明确以下哪些内容(10 分)A培训的经费 B培训的目标、意义 C培训的内容 D培训的对象 正确答案:B C D 3、培训需求分析流程中包含哪些项目(10 分) A组织分析 B任务分析 C需求分析 D人员分析 正确答案:A B D 4、培训需求调研的方法有哪些(10 分) A问卷法 B访谈法 C绩效改进数据分析法 D行为观察法 E组织能力分析法 正确答案:A B C D E

5、完备的课程体系可以有效支撑企业战略发展,我们可以从哪几个维度考虑(10 分) A按照不同层级设计课程体系 B按照授课形式不同设计课程体系 C按照解决企业核心问题设计课程体系 正确答案:A B C 6、有效的线上课程体系建设方法有哪些(10 分) A线上课程按照企业不同业务部门模块化 B配套线上考试、测评 C每个业务部门模块化的知识,按照层级及知识点难易分类 D配套业务知识问答及在线专家解答 E配套工具表单 F内训师单独的功能模块 正确答案:A B C D E F 判断题 1、内训师是企业知识传承的重要纽带(10 分) ? A正确 B错误 正确答案:正确

商业模式分析步骤

商业模式设计分析步骤 关于商业模式构成,我们采用学者Ghosh(1997)提出的框架。具体步骤如下: 第一步价值主张 该步骤目的是为确定一家企业的产品或服务如何满足客户的需求。应分析: 1.企业满足了什么用户群体的什么需求; 2.用户为何选择在你这里购买,而非他处。 第二步盈利模式 该步骤主要描述企业如何获得收入、产生利润以及获得高额的投资回报。应分析: 1.企业收费对象; 2.企业向谁收费; 3.预期投入产出情况。 第三步市场机会 该步骤明确企业所预期的市场以及企业在该市场中有可能获得潜在财务收入的机会。应至少分析: 1.企业所服务的市场区域及市场的潜在规模如何。 第四步竞争环境 该阶段用于识别在同一市场中运作、销售相似产品的其它竞争对手。应至少分析: 1.企业的竞争对手是谁?应选出2-3家企业,从多个角度进行对比。这些企业可能是直接竞争对手、潜在进入对其有明显威胁者、上下游延伸企业等。 第五步竞争优势 该步骤用于找出企业能生产更好产品或比市场价格更低产品时获得的优势。应分析: 1.企业的竞争优势是什么?可从资源、能力方面阐述。第四步和第五步可结合,列表对比。第六步营销战略 该阶段主要阐述如何进入新市场、吸引新客户的详细计划。应至少: 1.可从产品、价格、渠道、促销方式等角度。 第七步组织发展 主要描述企业如何组织所要完成的工作。应至少分析: 1.对已有的知名企业而言,组织架构是否需要调整?如何调整; 2.对于创意或想法的实现,拟采用何种组织架构来配合商业模式的运行。 第八步管理团队 企业中负责商业模式运作的各类员工。应至少分析: 1.商业模式的具体操作方面,需要何种或拥有哪些专业背景或经验的人员; 注意: 1.要求有图、表以及数据,结合文字描述才有说服力。 2.所设计商业模式的对象可以为现有知名企业,也可以为创意或想法的拟实现。 3.若设计商业模式为现有企业,则需指出该企业现有商业模式存在的问题。 4.小四、固定值18磅,封面表明姓名、专业、班级以及商业计划名称。 5.无字数限制要求,以完整表达自身计划为准。

城市综合体(偏商办)操作模式全方位解析1天

城市综合体(偏商办)操作模式全方位解析 主要解决问题—— Q1:为什么大家都要开发城市综合体? Q2:城市综合体个物业类型操作逻辑是什么? Q3:城市综合体各物业类型如何落地操作? 第一章、城市综合体分类及意义 一、城市综合体概述及分类 1.综合体概念、特征 2.综合体分类——HM、ZL、YT、FL 综合体发展模式 3.开发综合体优劣势——拿地逻辑 4.ZL 集团城市综合体拿地过程——案例复盘 第二章、城市综合体各物业类型开发逻辑 二、各物业的开发逻辑 1.住宅开发逻辑——WK的逻辑、XHW的逻辑 2.商业开发逻辑——DYC的逻辑 3.写字楼开发逻辑——盈利模式 VS 产品配置 三、开发核心指标及高效工作流程 1. 极简的前期快速算账的工作体系 2. 各物业类型财务账决策指标 3. 里程碑开发计划 4. 项目监督管理运营机制

5. 城市地图工具手册 第三章、城市综合体整体定位 四、整体定位 1.综合体整体定位案例——大类业态指标确定 2.案例——青岛 DYC 整体定位案例 第四章、综合体各物业类型操作 五、商业MALL及商业操作 1、商业 MALL 持有型案例——西安 DYC 2、商业街销售案例——主题、运营、单铺面积、回报率等 3、杭州 DYC 悦街销售案例复盘 4、简述主要品牌品类产品硬件需求 六、住宅操作 1.市场解析——两大核心市场关键指标应用 2.产品定位——产品定位及户型定位步骤方法 3.营销解析 案场营销问题梳理 营销逻辑三步——RC 集团营销逻辑 逐条通病解决方法 七、写字楼操作 1.标准甲级写字楼产品硬件配置 2.写字楼盈利模式 盈利模式论证——持有\销售\租售并举模式分析 第2页共3页

新员工带教流程

新员工带教流程 -标准化文件发布号:(9456-EUATWK-MWUB-WUNN-INNUL-DDQTY-KII

新员工带教流程 第一天: 熟悉公司的作息时间,了解公司基本状况,基本服务礼仪与动作规范,学习做迎宾。 1、上班时间:10:00---19:30 12:00----21:00 (转正前) 10:00--16:00 14:30---21:00(转正后) 备注:时间根据季节调整。 2、管理手册:P1、江明商贸简介(了解即可,店长须以解说的方式进行); 3、服务礼仪:1)仪容仪表标准; 2)服务动作规范(站姿、蹲姿、距离、手势、角度); 3)学习做迎宾(声音、表情、语调、迎宾位置); 4)电话礼仪; 第二天: 了解公司的考勤制度,产品的风格分类及陈列 1、相关制度的了解:《考勤制度及请假报批程序》《离职程序》; 2、产品风格分类(①以鞋来区分:男鞋、女鞋、童鞋②以季节来区分:春秋单鞋、夏季凉鞋、冬靴③以鞋头区分:尖头、圆头、方头④以鞋跟来区分:平跟3CM以下、中跟3.1CM--5CM、高跟5.1CM---8CM、特高跟8.1CM 以上⑤以鞋帮来区分:凉(拖)鞋、中空鞋、浅口鞋、满帮(低腰)鞋、短靴(筒高14CM以下)、中靴(筒高15--22CM)、长靴(筒高23--36CM);(以店铺现有货品实物讲解方式进行带教) 3、了解什么是陈列,为什么做陈列、陈列标准及陈列原则。 第三天: 掌握《会员卡》的办理及使用规范,相关票据的填写及操作流程,鞋类产品从哪六个方面进行描述。 1、“会员卡”的申办标准及使用细则; 2、相关票据:《销售单、销售退货单》《调拨单》《会员单》正确填写; 3、鞋类产品从:楦型、皮料、底材、高度、风格、线条六方面描述(以实物操作讲解带教为标准); 4、服务1--2步:细节重点的掌握及实操应用。 第四天: 了解鞋类基本皮料、材质的特性及打理保养方法,所属品牌货号含义,FABE\法则应用,服务三、 四步,轮流做迎宾。 1、皮料特征及打理方法、皮料的分类(牛、羊、猪、打蜡、漆皮、磨砂皮);(以店铺现有货品实物讲解方式进行带教) 2、了解所属品牌货号的含义; 3、服务技巧之FABE、含义理解及应用; 4、服务三、四步的细节重点的掌握及实操应用。 第五天: 学习掌握公司销售技巧及服务规范流程和语言表达标准、掌握做报表及相关单据技能,初步了解库存及货品摆放位置,服务五、六步、协助做销售。 1、销售技巧:USP/AIDA的含义及实操应用(以场景模拟带教实操为主) AIDA A:注意(Attention) 1)商品陈列 2)导购员的仪容、仪表 3)精神奕奕热忱的招呼(三声) 4)卖场气氛 I:兴趣(Interest) 1)接近顾客了解顾客购物动机 2)让顾客触摸商品 3)有效介绍货品的特性及卖点 4)为顾客做参谋 5)邀请试穿 D:欲望(Desire) 1)介绍FAB及USB 2)强调物超所值不可代替 3)化解顾客疑虑及异议 A:行动(Action) 1)把握时机完成交易 2)介绍打理知识 3)介绍其他配成产品 4)付款过程快速 USP(Unique selling piont)独特销售点: 质料、设计款式、手工、处理方法、色彩、价钱 2、开放式与封闭式的语言技巧:产品推荐:O O C 促成销售: C O C 3、初步了解库存及货品的摆放位置、辅助老员工做销售 4、掌握报表的正确填写、各项单据的电脑操作

如何写商业方法手册(业务及前景 )

如何写商业计划书(业务及前景) 一般可以分为十一个部分,第一部分是概述,第二部分为,第三部分是经营管理,第四部分是拟用筹资,第五部分为风险控制(因素),第六部分是投资回报和退出,第七部分是营运及预测分析,第八部分是财务报表,第九部分是财务规划,第十部分是产品宣传:资料、小册子、报道和图片等,第十一部分为补充说明。 第二部分论及大量有助于投资者了解你的业务的关键话题。每一处都很重要,但总贯全局还要有一个综合概要,如果不是明确精细的话,尝试去展示你的业务是怎样的独特。向读者展示是什么使你的业务在世界上的业务中有独到之处。阅读这一章节时,投资者将尽力确定这个产业“成功的关键”。换句话说,他将尽力证明这两三件事是在你的业务情况下必须及时做好以达成功的。注意编号体系有一个单独的数字作为标题而副标题含有小数,比如 2.01。 2.01概要 开始的一段以这样的句子起头,“公司的注册地址为……”并列出公司办公地址、电话号码和需要接触的个人。 2.02业务的实质 在这一部分要给出你所从事的业务的纲要。举个例子,你可以说,“我公司设计、生产、销售、维修微机基础软件,这些软件控制用于监看门诊病人的医疗诊断设备”。用一个精练的句子阐述你公司是干什么的,这也许是最好的开头。接下来,你要以概括的语句来描述你的产品或是服务。你需要用尽可能少的话来让投资者了解你的产品或服务。 2.03业务的历史 你在这部分要说出公司何时组成,特别要说清楚第一件产品或服务始于何时,以及公司经历过的最重要的里程碑式的事情。报告的业务历史部分必须短小精要。如果报告多于一页,

或者最多,达到两页,你已经说了太多的历史了。要是公司有个特别精彩的经历,那也许可以作为一个特别的理由来囊括大段的历史,但无论如何都要简洁。 2.04业务的前景 说清楚公司的年次发展计划并指出其中的分界线。实际上,投资者需要了解你如何在五年内从现在所处的状况发展到你想要达到的状况。尽管计划书的这一部分必须要简洁,但在格式上有相当大的自由度。你可以简单地说明在接下来的五年里你打算继续生产你们的两种基本产品,到第三年的时候你将引入另一个类似的产品。依照这样的办法,你的业务的前景将会简洁而又切中要害。另外,如果你预料在达到稳定点前要经历许多变化,你应该指出会发生哪些变化。投资者需要准确地了解公司要获得成功必须做些什么。 2.05独特之处 给投资者的每份都应该有一些独特之处。管理层独特?产品或服务独特?生产过程独特?有独特的金融基础?所有的这些都可以囊括在内。重要的是要有一些东西使你的公司在和别的对投资者来说同样可得的投资机会的对比中凸现出来。投资者们不喜欢投资于“人云亦云”的公司。他们想要有独特的商业地位的公司。在一个像这样的单独的章节中,或是在整篇商业计划的各章节中,你要着重强调你公司的独特之处。如果你的业务里有一个新产品,一个生产的专利,或是别的特别不寻常的方面,那么应该像这样在单独一章里列出。除了要包括这部分之外,企业主还应在中间歇地突出公司。 2.06产品或服务 在这部分你要精确的描述你的产品或服务,要求是不给读者对于你所生产的或是计划生产的东西留下疑问。如果你有好几种产品或服务,用单独的段落来叙述其中的每一种。你应叙述产品的价格,价格如何确定以及毛利数目。企业主容易轻率地对待产品的定价。花足够的时间来考虑所有影响产品定价的因素,确信你能够用坦率而有逻辑的话来解释定价背后的道理。是因为竞争迫使价格趋向于那个方向吗?价格定得高是因为你能侥幸成功吗?你必须准备回答这些问题。

商业模式分析步骤

商业模式分析步骤 企业满足了什么用户群体的什么需求;2、用户为何选择在你这里购买,而非他处。第二步盈利模式该步骤主要描述企业如何获得收入、产生利润以及获得高额的投资回报。应分析:1、企业收费对象;2、企业向谁收费;3、预期投入产出情况。第三步市场机会该步骤明确企业所预期的市场以及企业在该市场中有可能获得潜在财务收入的机会。应分析:1、企业所服务的市场区域及市场的潜在规模如何。第四步竞争环境该阶段用于识别在同一市场中运作、销售相似产品的其它竞争对手。应分析:1、企业的竞争对手是谁?应选出2-3家企业。第五步竞争优势该步骤用于找出企业能生产更好产品或比市场价格更低产品时获得的优势。应分析:1、企业的竞争优势是什么?可从资源、能力方面阐述。第四步和第五步结合,列表对比。第六步营销战略该阶段主要阐述如何进入新市场、吸引新客户的详细计划。应分析:1、可从产品、价格、渠道、促销方式等角度。在渠道方面,线上渠道应着重阐述。第七步组织发展主要描述企业如何组织所要完成的工作。应分析:1、对已有的知名企业而言,组织架构是否需要调整?如何调整;2、对于创意或想法的实现,拟采用何种组织架构来配合商业模式的运行。第八步管理团队企业中负责商业模式运作的各类员工。应分析:1、商业模式的具体操作方面,需要何种或拥有哪些专业背景或经验的人员;注意:1、要求有图、表

以及数据,结合文字描述才有说服力。2、所设计商业模式的对象可以为现有知名企业,也可以为创意或想法的拟实现。3、若设计商业模式为现有企业,则需指出该企业现有商业模式存在的问题。4、商业计划以PPT呈现,并结合word,由班长打包发送给我。

新员工带教手册

新员工带教教程

第一天 一、团队融入(熟悉店铺、成员) 1、认识店铺成员、姓名、店铺各职能岗位成员介绍及主要负责工作阐述,如同事、店 长、大店长、主管等 2、店铺环境及商场环境简单介绍:高价值陈列区、闲杂物品摆放区、卫生间等。 3、靓妆上岗,妆容必须按公司规定执行,包括:粉底、眉毛、眼影、眼线、唇彩、指 甲、头发。 4、新员工的服装到店穿着规定服装,衣着干净整齐,无异味。 5、始终保持积极、热情的店铺氛围,主动和进入店的顾客及身边路过的人微笑招呼 二、品牌介绍(企业文化简介、品牌成长历程、品牌风格) 企业文化简介 企业愿景—— 成为书写文化的领导者。 企业使命—— 追求全体员工物质与精神两方面幸福的同时,传承书写文化。 企业价值观—— 第一:恪守正确的做人准则。 第二:付出不亚于任何人的努力。 品牌成长历程 三、店鋪运营店规店纪、仪容仪表、导购职责) 3-1店规店纪店(日常事务) 1. 工作纪律 1)员工自觉遵守公司及商场的规章制度 2)自觉遵守规定的上下班时间,不得迟到早退或擅自离岗,离岗时需填写《离岗登记表》 3)请假必须办理请假手续 4)店铺员工用餐时间为30分钟 5)工作时间不能闲坐聊天,要定位定岗 6)上班时应精神饱满不能打瞌睡、发呆 7)服从工作安排和调动,以及上级主管的合理工作指示,按时完成任务

8)公司的文件、资料要妥善保管,严守秘密 9)工作时间不得接访亲友、朋友,可在休息时间接待 10)店内工作中不得使用手机闲聊或阅览网页及游戏 11)未经主管同意不得私自调班,未经批准不得不参加公司会议 12)必须按规定将货款交至收银台,自行收银店铺必须在规定时间内将货款存入公司规定银行账号,不得用职务之便私扣营业款 13)不得私自占有顾客遗失物品或损坏顾客财务 14)不得在公司或店铺内吵闹、粗言秽语和打架 15)不得将公司设备、财务、货品挪为私用,更不得偷盗或占为己有 16)货物盘点时如发现货品不正常流失,应第一时间向上级汇报; 17)不得私自为顾客打折 18)未经主管同意不得擅自为顾客换货、挑货、退货 19)员工之间互相帮助,团结友爱,有团队合作精神 2.服务行为规定 1)店内接待客人时应充分展示自身形象,严格按照公司《服务标准》执行,向客人树立良好的公司形象 2)柜台迎宾站姿端正,销售人员面带微笑 3)客人到柜及喊宾时,身体微鞠躬示意,声音适中,用好礼貌用语,为顾客提供超一流的服务 4)销售人员应积极主动给予顾客提供帮助,用语言引导顾客。 5)接待顾客过程中,注意语言行为应用,不要给客人留下不好印象 6)充分展示个人魅力,推广宣传自身品牌 7)销售人员应严格约束、自律、礼貌的为客人提供最优质的售后服务 3.柜台形象及卫生清洁责任制 1)按公司要求标准化陈列 2)内务货品摆放整洁,归纳清晰 3)私人物品摆放整洁 4)柜台所需设备及物品(税控机、POS机、扫码枪、生财物品及柜台陈列设施等)不得丢失及损坏 5)销售柜台坚决执行公司规定的清洁标准(1、柜台清洁无死角,灯箱明亮无损坏,光影投射位置准确,玻璃及陈列物品清洁无指纹及灰尘)(详见品牌形象篇) 6)柜台卫生监管制度为-当班值日员工做好柜台清洁后,填写店铺每日形象自查表,由店长或对班在检查人一栏签字确认 备注:具体员工准则参照《员工管理制度及行为规范》 3-2仪容仪表

相关主题
文本预览
相关文档 最新文档