Group items tagged

The tag-management industry is growing rapidly, as tags are critical to gathering data about your customers.

It's the early days for tag management, but the industry is growing rapidly because it's not so much about tags, but about the bigger challenge of using digital data.

Where does tag management fit in the data picture? Here's an example someone shared with me recently: He had gone to an antivirus product's website, read the reviews, and bought the software. In the days that followed, however, he suddenly began to see banner ads from that same software maker whenever he visited CNN, ESPN, and other favorite websites. The software maker knew he had visited its website, but not that he already bought the product. They were retargeting him with banner ads at unnecessary cost and no purpose.

a lot of articles calling data scientists and statisticians the jobs of the future

there are more immediate needs that, when addressed, will have a much greater business impact.

Right now we have huge opportunities to make the data more accessible, more “joinable” and more consumable. Leaders don’t want more data – they want more information they can use to run their businesses.

SuiteCRM was forked from the 6.5.x branch of SugarCRM because a segment of the community felt that SugarCRM Inc. was paying too much attention to its commercial editions and dragging its feet on updating the community edition. In addition to packaging up the latest SugarCRM codebase, SuiteCRM added a number of third-party extensions, resulting in a new system that is comparable to SugarCRM Professional in terms of features and functionality.

These are few of the benefits of implementing a good quality CRM All of your clients’ information is stored in one place, it’s easy to update and share with the whole team. Updates by colleagues should be saved immediately. Every member of your team will be able to see the exact point when your business last communicated with a client, and what the nature of that communication was. CRMs can give you instant metrics on various aspects of your business automatically.  Reports can be generated. These can also be used to forecast and plan for the future. You will be able to see the complete history of your company’s interaction with a client. Calendars and diaries can be integrated, relating important events or tasks with the relevant client.  Suitable times can be suggested to contact customers and set reminders.

Finding one system that will fit your needs in one package may not be possible, so be aware that you may need to customise it to fit into your company. There are infinite possibilities here so don’t get too carried away as costs will rise accordingly.

Ensure that the CRM works on mobile devices and can be accessed remotely. Employees aren’t necessarily sat at their desks when it needs to be used or updated. Real-time updates are necessary for ensuring that clients aren’t contacted twice with the exact same follow up.

For the fourth consecutive year, Gartner, Inc. has named Oracle as a Leader in its “Magic Quadrant for Master Data Management of Product Data Solutions.” (1)

“MDM is a technology-enabled discipline in which business and IT staff work together to ensure the uniformity, accuracy, stewardship, semantic consistency and accountability of the enterprise's official, shared master data assets. Master data is the consistent and uniform set of identifiers and extended attributes that describes the core entities of the enterprise, such as customers, prospects, citizens, suppliers, sites, hierarchies and chart of accounts,” according to Gartner.

By enabling organizations to consolidate product information from heterogeneous systems, Oracle Product Hub creates a single view of product information that can be leveraged and shared across functional departments in the enterprise, as well as externally with trading partners.

Schema on write This is the traditional approach for Business Intelligence. A model, often dimensional, is built as part of the design process. This model is an abstraction of the complexity of the underlying systems, put in business terms. The purpose of the model is to allow the business users to interrogate the data in a way they understand.

The model is instantiated through physical database tables and the date is loaded through an ETL (extract, transform and load) process that takes data from one or more source systems and transforms it to fit the model, then loads it into the model.

The key thing is that the model is determined before the data is finally written and the users are very much guided or driven by the model in how they query the data and what results they can get from the system. The designer must anticipate the queries and requests in advance of the user asking the questions.

1. Project Sponsorship and Governance 2. Project Management 3. Development Team (Core Team) 4. Extended Project Team

1. Project Sponsorship and Governance IT and the business should form a BI steering committee to sponsor and govern design, development, deployment, and ongoing support. It needs both the CIO and a business executive, such as CFO, COO, or a senior VP of marketing/sales to commit budget, time, and resources. The business sponsor needs the project to succeed. The CIO is committed to what is being built and how.

2. Project Management Project management includes managing daily tasks, reporting status, and communicating to the extended project team, steering committee, and affected business users. The project management team needs extensive business knowledge, BI expertise, DW architecture background, and people management, project management, and communications skills. The project management team includes three functions or members: Project development manager - Responsible for deliverables, managing team resources, monitoring tasks, reporting status, and communications. Requires a hands-on IT manager with a background in iterative development. Must understand the changes caused by this approach and the impact on the business, project resources, schedule and the trade-offs. Business advisor - Works within the sponsoring business organization. Responsible for the deliverables of the business resources on the project's extended team. Serves as the business advocate on the project team and the project advocate within the business community. Often, the business advocate is a project co-manager who defers to the IT project manager the daily IT tasks but oversees the budget and business deliverables. BI/DW project advisor - Has enough expertise with architectures and technologies to guides the project team on their use. Ensures that architecture, data models, databases, ETL code, and BI tools are all being used effectively and conform to best practices and standards.

Mistake 1.  Not putting a strong interdisciplinary team together. It is impossible to put together an analytics platform without understanding the needs of the customers who will use it.  Sounds simple, right?  Who wouldn’t do that?  You’d be surprised how many analytics projects are wrapped up by IT because “they think” they know the customer needs.  Not assembling the right team is clearly the biggest mistake companies make.  Many times what is on your mind (and if you’re an IT person willing to admit it) is that you are considering converting all those favorite company reports.  Your goal should not be that.  Your goal is to create a system—human engineered with customers, financial people, IT folks, analysts, and others—that give people new and exciting ways to look at information.  It should give you new insights. New competitive information.  If you don’t get the right team put together, you’ll find someone longing for the good old days and their old dusty reports.  Or worse yet, still finding ways to generate those old dusty reports. Mistake 2.  Not having the right talent to design, build, run and update your analytics system.  It is undeniable that there is now high demand for business analytics specialists.  There are not a lot of them out there that really know what to do unless they’ve been burned a few times and have survived and then built successful BA systems.  This is reflected by the fact you see so many analytics vendors offer, or often recommend, third-party consulting and training to help the organization develop their business analytic skills.  Work hard to build a three-way partnership between the vendor, your own team, and an implementation partner.  If you develop those relationships, risk of failure goes way down.

Mistake 3.  Putting the wrong kind of analyst or designer on the project. This is somewhat related to Mistake 2 but with some subtle differences.  People have different skillsets so you need to make sure the person you’re considering to put on the project is the right “kind.”  For example, when you put the design together you need both drill-down and summary models.  Both have different types of users.  Does this person know how to do both?  Or, for example, inexperience in an analyst might lead to them believing vendor claims and not be able to verify them as to functionality or time to implement. Mistake 4.  Not understanding how clean the data is you are getting and the time frame to get it clean.  Profile your data to understand the quality of your source data.  This will allow you to adjust your system accordingly to compensate for some of those issues or more importantly push data fixes to your source systems.  Ensure high quality data or your risk upsetting your customers.  If you don’t have a good understanding of the quality of your data, you could easily find yourself way behind schedule even though the actual analytics and business intelligence framework you are building is coming along fine. Mistake 5.  Picking the wrong tools.  How often do organizations buy software tools that just sit on the shelve?  This often comes from management rushing into a quick decision based on a few demos they have seen.  Picking the right analytics tools requires an in-depth understanding of your requirements as well as the strengths and weaknesses of the tools you are evaluating.  The best way to achieve this understanding is by getting an unbiased implementation partner to build a proof of concept with a subset of your own data and prove out the functionality of the tools you are considering. Bottom Line.  Think things through carefully. Make sure you put the right team together.  Have a data cleansing plan.  If the hype sounds too good to be true—have someone prove it to you.

You can’t learn data visualization by memorizing a set of rules. You must understand why things work the way they do.

you must be able to think statistically

This doesn’t mean that you must learn advanced mathematics, nor can you do this work merely by learning how to use software to calculate correlation coefficients and p-values.

ERP vendor selection. As the following graph shows, the primary candidates for ERP software were SAP, Oracle, Microsoft, Epicor, and Infor:

The cloud question. Despite the hype, only 14 percent of respondents are using ERP delivered as Software as a Service (SaaS). Although the best cloud vendors can deliver superior security and reliability than most internal IT departments, market momentum to ERP in the cloud is not there yet, as the following diagram illustrates:

Important lessons. Implementing an ERP system is always complex because the deployment drives changes to both data and processes that extend across departmental boundaries inside the organization.

The best practice in business intelligence delivery is always to build a data warehouse.

Pure transactional reporting is problematic. There are, of course, the usual performance issues. Equally troublesome is the difficulty in distilling a physical model down to a format that is easy for business users to understand. Dimensional models are typically the way business users envision their business: simple, inclusive structures for each entity. The standard OLTP data model that takes two of the four walls in the conference room to display will never make sense to your average business user.

Trainerul Octavian Pantis, managing director TMI Training & Consulting. El este autorul cartii "Musai List", un best-seller in domeniu.

Great design, high-quality code, strong business sponsorship, accurate requirements, good project management, and thorough testing are some of the obvious requirements for successful analytics systems.

As a professional in the field, you must be able to do these things well because they form the foundation of a good analytics implementation.

Successful analytics professionals should follow a set of guiding principles.