admin on February 4th, 2012
Customer Relationship Management (CRM) is one of those magnificent concepts
that swept the business world in the 1990’s with the promise of forever changing
the way businesses small and large interacted with their customer bases. In the
short term, however, it proved to be an unwieldy process that was better in
theory than in practice for a variety of reasons. First among these was that it
was simply so difficult and expensive to track and keep the high volume of
records needed accurately and constantly update them.
In the last several years, however, newer software systems and advanced
tracking features have vastly improved CRM capabilities and the real promise of
CRM is becoming a reality. As the price of newer, more customizable Internet
solutions have hit the marketplace; competition has driven the prices down so
that even relatively small businesses are reaping the benefits of some custom
CRM programs.
In the beginning…
The 1980’s saw the emergence of database marketing, which was simply a catch
phrase to define the practice of setting up customer service groups to speak
individually to all of a company’s customers.
In the case of larger, key clients it was a valuable tool for keeping the
lines of communication open and tailoring service to the clients needs. In the
case of smaller clients, however, it tended to provide repetitive, survey-like
information that cluttered databases and didn’t provide much insight. As
companies began tracking database information, they realized that the bare bones
were all that was needed in most cases: what they buy regularly, what they
spend, what they do.
Advances in the 1990’s
In the 1990’s companies began to improve on Customer Relationship Management
by making it more of a two-way street. Instead of simply gathering data for
their own use, they began giving back to their customers not only in terms of
the obvious goal of improved customer service, but in incentives, gifts and
other perks for customer loyalty.
This was the beginning of the now familiar frequent flyer programs, bonus
points on credit cards and a host of other resources that are based on CRM
tracking of customer activity and spending patterns. CRM was now being used as a
way to increase sales passively as well as through active improvement of
customer service.
True CRM comes of age
Real Customer Relationship Management as it’s thought of today really began
in earnest in the early years of this century. As software companies began
releasing newer, more advanced solutions that were customizable across
industries, it became feasible to really use the information in a dynamic way.
Instead of feeding information into a static database for future reference,
CRM became a way to continuously update understanding of customer needs and
behavior. Branching of information, sub-folders, and custom tailored features
enabled companies to break down information into smaller subsets so that they
could evaluate not only concrete statistics, but information on the motivation
and reactions of customers.
The Internet provided a huge boon to the development of these huge databases
by enabling offsite information storage. Where before companies had difficulty
supporting the enormous amounts of information, the Internet provided new
possibilities and CRM took off as providers began moving toward Internet
solutions.
With the increased fluidity of these programs came a less rigid relationship
between sales, customer service and marketing. CRM enabled the development of
new strategies for more cooperative work between these different divisions
through shared information and understanding, leading to increased customer
satisfaction from order to end product.
Today, CRM is still utilized most frequently by companies that rely heavily
on two distinct features: customer service or technology. The three sectors of
business that rely most heavily on CRM — and use it to great advantage — are
financial services, a variety of high tech corporations and the
telecommunications industry.
The financial services industry in particular tracks the level of client
satisfaction and what customers are looking for in terms of changes and
personalized features. They also track changes in investment habits and spending
patterns as the economy shifts. Software specific to the industry can give
financial service providers truly impressive feedback in these areas.
Who’s in the CRM game?
About 50% of the CRM market is currently divided between five major players
in the industry: PeopleSoft, Oracle, SAP, Siebel and relative newcomer
Telemation, based on Linux and developed by an old standard, Database Solutions,
Inc.
The other half of the market falls to a variety of other players, although
Microsoft’s new emergence in the CRM market may cause a shift soon. Whether
Microsoft can capture a share of the market remains to be seen. However, their
brand-name familiarity may give them an edge with small businesses considering a
first-time CRM package.
PeopleSoft was founded in the mid-1980’s by Ken Morris and Dave
Duffield as a client-server based human resources application. In 1998,
PeopleSoft had evolved into a purely Internet based system, PeopleSoft 8.
There’s no client software to maintain and it supports over 150 applications.
PeopleSoft 8 is the brainchild of over 2,000 dedicated developers and $500
million in research and development.
PeopleSoft branched out from their original human resources platform in the
1990’s and now supports everything from customer service to supply chain
management. Its user-friendly system required minimal training is relatively
inexpensive to deploy. .
One of PeopleSoft’s major contributions to CRM was their detailed analytic
program that identifies and ranks the importance of customers based on numerous
criteria, including amount of purchase, cost of supplying them, and frequency of
service.
Oracle built a solid base of high-end customers in the late 1980’s,
then burst into national attention around 1990 when, under Tom Siebel, the
company aggressively marketed a small-to-medium business CRM solution.
Unfortunately they couldn’t follow up themselves on the incredible sales they
garnered and ran into a few years of real problems.
Oracle landed on its feet after a restructuring and their own refocusing on
customer needs and by the mid-1990’s the company was once again a leader in CRM
technologies. They continue to be one of the leaders in the enterprise
marketplace with the Oracle Customer Data Management System.
Telemation’s CRM solution is flexible and user-friendly, with a
toolkit that makes changing features and settings relatively easy. The system
also provides a quick learning environment that newcomers will appreciate. Its
uniqueness lies in that, although compatible with Windows, it was developed as a
Linux program. Will Linux be the wave of the future? We don’t know, but if it
is, Telemation’s ahead of the game.
The last few years…
In 2002, Oracle released their Global CRM in 90 Days package that promised
quick implementation of CRM throughout company offices. Offered with the package
was a set fee service for set-up and training for core business needs. .
Also in 2002 (a stellar year for CRM), SAP America’s mySAP began using a
“middleware” hub that was capable of connecting SAP systems to externals and
front and back office systems for a unified operation that links partners,
employees, process and technologies in a closed-loop function.
Siebel
consistently based its business primarily on enterprise size businesses willing
to invest millions in CRM systems, which worked for them to the tune of $2.1
billion in 2001. However, in 2002 and 2003 revenues slipped as several smaller
CRM firms joined the fray as ASP’s (Application Service Providers). These
companies, including UpShot, NetSuite and SalesNet, offered businesses CRM-style
tracking and data management without the high cost of traditional CRM start-up.
In October of 2003, Siebel launched CRM OnDemand in collaboration with IBM.
Their entry into the hosted, monthly CRM solution niche hit the marketplace with
gale force. To some of the monthly ASP’s it was a call to arms, to others it was
a sign of Siebel’s increasing confusion over brand identity and increasing loss
of market share. In a stroke of genius, Siebel acquired UpShot a few months
later to get them started and smooth their transition into the ASP market. It
was a successful move.
With Microsoft now in the game, it’s too soon to tell
what the results will be, but it seems likely that they may get some share of
small businesses that tend to buy based on familiarity and usability. ASP’s will
continue to grow in popularity as well, especially with mid-sized businesses, so
companies like NetSuite, SalesNet and Siebel’s OnDemand will thrive. CRM on the
web has come of age!
This article on the “The History of CRM” reprinted with
permission.
Copyright © 2004-2005 Evaluseek Publishing.
Fractional Horsepower Motors Minka Aire Ceiling Fans
admin on January 25th, 2012
Introduction
Many organisations roll-out SharePoint without considering the resources needed to own and manage SharePoint, especially the human resources. The initial focus is often placed on the technical side of the development and the initial go-live, ongoing management of the site is given little thought. One area that is often given the least resources to is training, which is more often than not a mistake. Without adequate training for all users concerned the SharePoint deployment will fail.
This document seeks to detail the five skilled separate concerns needed to manage and leverage SharePoint and the training required for each.
Although this article details these concerns separately this doesn’t mean that they cannot be performed by the same person. The only caveat to that is that the main SharePoint owner should never be in IT – this is explained in a separate document that is available titled Seven Pillars of SharePoint.
It should also be noted that the specifications of concern is not absolute, and as every organization is different so are the responsibilities allocated to a skill. These responsibilities should be tuned to suit the internal layout of your organization and the skills you have in-house. This document will guide you through identifying the skilled areas and should help you to choose the moat appropriate member of staff to fulfil each role.
Skills Required
Once SharePoint has been deployed in your organization there are several skills needed to maintain the system and to develop it in line with your corporate strategy. These skills are best viewed as separate concerns, and if possible best serviced by different people. Obviously this is not always the case, but by analysing the skills matrix as if it were separate people it is much easier to understand.
There are four main players in the world of SharePoint – SharePoint System Administrator, Super User, SharePoint Designer and Web Developer. These terms will be referred to continually throughout this document.
We have chosen to omit the fifth player from this diagram -the End User. End Users contribute to SharePoint but are not required for developing the system; we will discuss End Users at the end of this document.
Skill Area 1 – SharePoint System Administrator
Perhaps one of the most misunderstood skills in SharePoint is that of the System Administrator. Many people confuse the System Administrator with a concept referred to as a SharePoint Administrator (we refer to this role as the Super User). Instead of explaining the differences between the two roles I’ll explain the function of the SharePoint System Administrator in detail in this section and the Super User in detail further on in this document.
The SharePoint System Administrator is concerned primarily with the back-end functions of SharePoint focusing on how it integrates with other server applications.
Responsibilities
Selecting the correct version of SharePoint.
Specifying the most suitable set up for anticipated load.
Deploying SharePoint correctly.
Configuring email (incoming).
Configuring email (outgoing).
Ensuring Anti-virus is operable.
Configuring start-up security.
Configuring shared services.
Configuring search.
Backup.
Restore.
Disaster Recovery.
Other duties focusing on the Central Administration Page
Skills
Anybody carrying out this function should have a minimum of two years working as a system administrator on Windows Server, SQL, and Exchange. They should be fully conversant with Domain Name Systems (DNS) and Active Directory.
Training As a bolt-on to existing skills as listed above the System Administrator would benefit from a 5 day SharePoint Administrators course. Make sure this is a System Administrator course not a SharePoint Administrator course!
Work Load
It is anticipated that once the SharePoint system is in and robust the additional burden on the administrator will be an additional 1% of their existing workload.
Skill Area 2 – Super User
This individual has the most important function within SharePoint, they are responsible for configuring SharePoint to match 70% of the organizations bespoke needs. This is the role that is sometimes referred to as SharePoint Administrator, as they administer the SharePoint front-end environment. Once the System Administrator has installed SharePoint and confirmed that it has been robustly installed the Super User takes over.
This role is non-technical (meaning no knowledge of code, or computer systems is required) and we strongly recommended that this role is given to someone outside of IT. This is because the focus of this role should be on the I (information) and not on the T (technology). In our experience a member of the IT team will focus on the technology because this is what they know. This role is suited to a Business Analyst, as they have the skills to analyse problems and find solutions most suited to the current organizational strategy. The Super User uses the out-of-the-box SharePoint features available to meet the requirements of the business. They will focus on using the Site Actions button to deliver the needs of the business.
Responsibilities
Managing site collections.
Configuring security at site level.
Creating and owning sub-sites.
Creating lists, blogs, wiki’s etc.
Creating and configuring site features.
Mapping business issues to SharePoint functions.
All configurations under the site actions button.
Creating site level policies.
Skills
This individual must be a good communicator at all levels and have excellent presentation skills. They need to be able to understand the business and analyse business problems. The Super User must have a solid understanding of how SharePoint can be configured out-of-the -box. The Super User must have excellent business analyst skills and needs to be able to map business problems onto SharePoint functionality.
Training
This user will need 5 days Super User training course and a 3 day End User training course. This will give them a full understanding of the out-of-the-box capabilities of SharePoint.
Work Load
The Super User can expect to have 100% of their time dedicated to working with SharePoint sites. There time will be split between developing new uses of SharePoint and monitoring and maintain existing SharePoint sites.
Skill Area 3 – SharePoint Designer
A further 20% of the organizations bespoke needs can be customized by the SharePoint Designer. The customisations performed by this individual are changes that cannot be done through the SharePoint user interface i.e. the site actions button. Once the Super User has exhausted all possibilities through the site actions button the SharePoint Designer comes in.
The three main areas SharePoint designer is used for is branding, creating workflows and connecting to external data sources. This document will split the SharePoint Designer skill set into these three different work streams, to clarify the different skills needed for each. This does not mean that three different people have to commit to each area in fact one person could manage all three strands.
SharePoint Designer (Banding)
This person will be responsible for managing the look and feel of the SharePoint site, this will involve creating page layouts, making changes to the master pages, and responsibility for the aesthetics of the site. This person should have knowledge of accessibility standards when designing to ensure the design is as inclusive as possible as well as being pleasing to the eye.
Responsibilities
Creating page layouts.
Editing the master page.
Giving guidance on design best practice.
Skills
The person performing this function needs to have a thorough understanding of the web and preferably come from a web design background. Knowledge of Cascading Style Sheets (CSS) and HTML is very desirable. As mentioned above knowledge of accessibility standards is also desirable.
Training
This user will need a 5 day SharePoint Designer course, preferably aimed at web and graphic designers.
Work Load
The SharePoint Designer usually has a 100% time allocation at the beginning of a deployment and thereafter a reducing amount of commitment. The work load typically consists of smaller projects delegated to them by the strategy team.
SharePoint Designer (Workflow)
Workflow is an important part of any SharePoint deployment, SharePoint designer has extremely powerful capabilities for developing bespoke workflow. The person responsible for this will work with the Super User to examine business processes and translate them into SharePoint designer workflows.
Responsibilities
Examining user requirements.
Designing workflows and building them.
Testing and evaluating existing workflow.
Skills
This person needs to have a broad understanding of current business processes and analytical skills. Experience of previous work in business processing mapping is desirable.
Training
This person will need a 5 day SharePoint Designer course.
Workload
The SharePoint Designer usually has a 100% time allocation at the beginning of a deployment and thereafter a reducing amount of commitment. The work load typically consists of smaller projects delegated to them by the strategy team.
SharePoint Designer (Database Access)
Businesses will have information and data stored in multiple storage sites across multiple locations. One good point about SharePoint is that you can access information held in other locations through SharePoint. SharePoint designer can be used to create access to this information so it can be used again and again.
Responsibilities
Creating data access modules. Ensuring data protection laws are upheld.
Skills
The person in this role will need to have an understanding of data and a technology named ActiveX Data Objects (ADO). Previous experience of writing databases is an advantage. Knowledge of the Data Protection Act is also desirable.
Training
This person will need a 5 day SharePoint designer course.
Workload
The SharePoint Designer usually has a 100% time allocation at the beginning of a deployment and thereafter a reducing amount of commitment. The work load typically consists of smaller projects delegated to them by the strategy team.
Skill Area 4 – Web (.NET) Developer
The remaining 10% of an organization’s bespoke SharePoint needs can be achieved by calling on the services of a Web (.NET) Developer. This person should be a last resort when it comes to SharePoint development, SharePoint works best when the out-of-the-box features are leveraged fully.
This individual will be able to carry out deep customization and provides the ability to achieve very tight integration between SharePoint and legacy systems. Custom web parts and complicated workflow processes can be designed b a Web (.NET) Developer. A Web Developer would only be called when both the Super User and the SharePoint Designer have exhausted all other options.
Responsibilities
Developing solutions / features within best practice guidelines.
Working with and leveraging the object model.
Working with and leveraging SharePoint web services.
Creating web parts.
Creating user controls.
Implementing events.
Developing complex asynchronous workflows.
Deploying solutions and features with best practice.
Working with enhanced security.
Creating code in keeping with best practice.
Skills
The Web (.NET) Developer will need to have a minimum of 3 years.NET development experience. They must have experience of developing for the browser and have been working with ASP.NET 2 for at least 12 months.
Their core skills will need to be:
Understanding the SharePoint object model, and
Working with workflows
Training
This user will need a 5 day SharePoint Developer course.
Work Load
The Web Developers work load will be very dependent upon the needs of the business and specifically the level of integrating with legacy systems.
Once again, in the initially stages of deployment the Web Developer will be heavily utilized and after a period will have less demands made on their time. Web Developers will be called on an ad-hoc basis to complete project
Skill Area 5 – End User
Last but not least, the End User will also need some SharePoint skills. Although the skills required are minimal, End Users will still require training to build their confidence and acceptance of the site. When End Users are given proper training and told explicitly what is expected of them when using the site the more likely it is to be a success. The general rule for training End User with SharePoint is to focus on small skills based learning packages and make sure users are comfortable with them. It is always best to train in fewer areas well than cover lots of topics without users really understanding.
Responsibilities
Navigate through the site and find content.
Organise themselves with alerts and RSS feeds to keep updated.
File documents in the appropriate place.
File documents with the appropriate metadata for searching.
Skills
End Users do not need any specific skills and providing that they have had some exposure to the internet they will be capable of working with SharePoint.
The training provision is mainly to build confidence initially and acceptance of the site.
Training
End Users require a 1 day session as close to go-live as is possible. This session should focus on the tasks they are going to complete on a day to day basis.
Work Load
The End User can expect to interact with the SharePoint site 100% of the time on an ongoing basis. This of course will very much depend on the tasks required to be performed by the End User can the function of the site. End Users make up the majority of SharePoint users.
Bad Credit Credit Card
admin on January 23rd, 2012
Windows 7, the latest operating system from Microsoft is also their first operating system that automatically synchronizes the PC clock to an internet source of UTC time (Coordinated Universal Time). From the moment a Windows 7 computer is switched on and is connected to the Internet it will request time signals from the Microsoft time service – time.windows.com.
While for many home users this will save them the hassle of setting and correcting their clock as it drifts, for business users it may be problematic as internet time sources are not secure and receiving a time source through the UDP port on the firewall could lead to security breaches and as Internet time sources can’t be authenticated by NTP (Network Time Protocol) the signals can be hijacked by malicious users.
This internet time source can be deactivated by opening the clock and date dialogue box, and opening the Internet Time tab, clicking the ‘Change’ setting button and unchecking the ‘Synchronize with an Internet time server option.’
Whilst this will unsure no unwanted traffic will be coming through your firewall it will also mean that the Windows 7 machine will not be synchronized to UTC and its timekeeping will be reliant on the motherboard clock, which will eventually drift.
To synchronize a network of Windows 7 machines to an accurate and secure source of UTC then the most practical and simplest solution is to plug in a dedicated NTP time server. These connect directly to a router or switch and enable the safe receiving of an atomic clock time source.
NTP time servers use the highly accurate and secure GPS signal (Global Positioning System) available everywhere on the planet or more localized long wave radio signals transmitted by several national physics laboratories such as NIST and NPL.
Pheonix University