Solutions

Quick and strategic solutions.

Start-up of Business Intelligence systems and project management, from the initial analysis to end-user training.

Areas of analysis

Business Intelligence has no departmental boundaries: it applies wherever there is data to be read. These are the areas I work on most often.

Sales

Understanding the market

Statistical analysis, lead time and deliveries, product and customer loyalty, customer data sheets and rating: knowing who buys, what it really earns and how promptly they pay.

Purchasing

Keeping supply under control

Purchasing and delivery analysis, purchase requisitions and orders, goods received notes, supplier data sheets and rating: knowing who you can count on, and on what terms.

Production

Measuring efficiency

OEE analysis, defects and scrap, department, project and labour efficiency: finding out where time is lost and where margin is lost.

Finance and control

Keeping the books in check

Credit and debit analysis, timeliness of proceeds and payments, credit lines, financial statements, project income statement, industrial cost control: financial health in readable figures.

Logistics

Keeping stock moving

Inventory handling, warehouse load percentage, cross analysis, freight rate and transportation cost incidence: which items turn over and which tie up capital.

People

Reading the cost of labour

Labour cost by department and project, standard and overtime hours, absenteeism, effective hourly cost: understanding where people’s time goes.

Business Intelligence

How I work with data

The starting point is always the database, often organised through datawarehouse systems or sets of datamarts. From there you build what is actually needed: reports, charts, tables and key indicators (KPIs), arranged so that whoever has to decide gets straight to the point.

The technical part, though, is only half the work. The other half is understanding the objective before touching the data, identifying the process that leads to the result, and reconciling the numbers before handing them over. I have gathered my views on the method and its implications on a separate page.

The method
01AnalysisFunctional and technical:what is needed and where from.02ReconciliationThe numbers must add upbefore they are handed over.03DevelopmentBuilding reports, dashboardsand indicators.04FeedbackThe client’s sign-off:insisted on, not waited for.05MaintenanceThe system changes as thecompany changes.06DocumentationA trace remains of howevery figure is made up.01AnalysisFunctional and technical:what is needed and where from.02ReconciliationThe numbers must add upbefore they are handed over.03DevelopmentBuilding reports, dashboardsand indicators.04FeedbackThe client’s sign-off:insisted on, not waited for.05MaintenanceThe system changes as thecompany changes.06DocumentationA trace remains of howevery figure is made up.

Project Management

Not just data.

My experience in the world of corporate ERP allowed me to follow a number of activities (not only data analysis oriented), coordinate resources and perfect management techniques, eventually consolidating a professional figure that is key to every business process.

Managing operations

Process analysis

The initial assessment, useful to define a development roadmap for the project.

Timing

Planning, scheduling, monitoring and controlling all project activities.

Project documentation

The overall project vision, the plans, the schedule and the risk analysis.

Pre-sales assessment

The activity that takes place before closing the sale, promoting products or services in a given market.

Managing resources

Coordination

Connecting and integrating the different parties in order to reach the agreed objective.

Go live

The culmination of the implementation: the moment the software becomes available to use.

Training

Support and explanation on the functions the final users will work with in the system.

Let’s talk about your business enrico.michelin@gmail.com +39 349 400 8055

or on LinkedIn