|
If your company or business needs to obtain the maximum
benefit of all the information available for:
|
|
To generate business opportunities and identify competitive
areas.
|
|
|
It needs to know if the projects that it realizes are
profitable.
|
|
|
To have the right information to be able to take the best
decision.
|
|
|
To have a better knowledge of heir clients.
|
|
Let Secuenzia helps you in:
|
|
|
Having a clearer vision of your requirements for
information management.
|
|
|
Your integration processes.
|
|
|
Making simulations in order to know certainty, if a certain
decision is taken, what would happen in the future?
|
|
|
Choosing the best technological tools according to your
needs.
|
|
What is a DataWareHouse?
|
|
A DataWareHouse goes beyond the transactional and
operational information of the company or organization. A
DataWareHouse contains information stored in a database
designed specifically to improve the efficient analysis
and treatment of information.
A DataWareHouse is usually joined to the Business
Intelligence that is the set of tools and strategies
focused on the administration and creation of knowledge
through the analysis of existing information.
This set of tools and methodologies has the following
characteristics:
|
|
|
Accessibility to the information. Data is the principal
source of this concept, and the first thing that must be
guaranteed for this type of tools and technologies is the
user access to the information with independence of the
origin of this information.
|
|
|
Support in taking a decision. It tries to go beyond in the
presentation of the information, so that the users have
access to analytical tools that allow them to select and to
manipulate only those data in which they are interested.
|
|
|
Guidance to end user. It seeks independence among the
expertise of users and their ability to use these tools.
|
|
Two basic conditions are necessary to manage to extract
this useful knowledge:
|
|
|
We must have sufficient data to work with them and,
moreover, these data must be organized in such a way that
their processing with automated tools of extracting
information can be the most efficient possible.
|
|
|
There must be software tools capable of processing large
amounts of data in a reasonable time. These tools will be
used to extract information from the databases through
answers to specific questions.
|
|
It is important to take into account the pyramid of
information to deal with a DataWareHouse's project, in
order to see what the aims are and where it is necessary to
reach. We can see the stages and aims of the need of
processing the information in the following figure:
|
|
|
|
Before you start a DataWareHouse's project we must take
into account the following:
|
|
|
Multiplicity of Technologies/Platforms for BBDD, languages
of access, platforms HW/SO, interfaces between
applications, tools for the end user...
|
|
|
Difficulty to access to the data of different Information
Systems in order to obtain the necessary reports.
|
|
|
There is not a single and integrated vision of data from
where I can obtain information of my business.
|
|
|
Strategic Risk:
|
|
|
- Non-existence of global strategy of Business
Intelligence in the company.
|
|
|
- Vision of DWH as a system of reports instead of an
analytical system.
|
|
|
- Launch of large projects instead of iterative processes
by functional blocks
|
|
|
- To believe that a strategy BI is a project of systems
and not to involve actively to all employees.
|
|
|
- Non-existence of functional people in charge of the
information, who must validate constantly that data
provided are correct.
|
|
|
- Not having a working team with experience in Business
Intelligence projects.
|
|
|
- Limited extent of vision of the DWH, focusing on a
limited set of users.
|
|
|
Operating Risk:
|
|
|
- To duplicate models of data of the operational systems,
they are directed to the operation not to the analysis.
|
|
|
- Lack of ETL tools, which produces high times of
development of interfaces and complexity in their
maintenances.
|
|
|
- To assume that the information is correct in the
operational without having covered tasks of functional
validation.
|
|
|
- Not to correct the mistakes of data in the sources and
try to do it in the load processes.
|
|
|
- Mechanisms of control of incremental load and automatic
rebooting
|
|
|
- To give more importance to the performance of the tool
than to the quality of data.
|
|
|
Generical Diagram:
|
|
|
