Palveluvaraston käyttöönotto kokoonpanoteollisuudessa

Tutkimuksen tavoitteena oli selvittää palveluvarastoinnin vaikutukset hankinnan kokonaiskustannuksiin ja luoda palveluvaraston toimintakonsepti. Toimintakonsepti pitää sisällään informaatio- ja materiaalivirtojen hallinta- ja ohjausprosessit toimittajan, palveluvaraston ja diplomityön kohdeyrityksen välillä. Tutkimuksen alussa tehtiin kustannusvertailu kahden vaihtoehtoisen toimittajan välillä. Toinen vaihtoehdoista edellyttää välivarastointia palveluvarastossa. Kustannusvertailun pohjalta kohdeyrityksessä päätettiin vaihtaa toimittajaa ja ottaa käyttöön palveluvarasto. Palveluvaraston toimintakonseptin luomista varten yrityksessä perustettiin projektiryhmä. Tutkimuksen kirjoittaja toimi projektiryhmän vetäjänä. Tutkimuksessa luotiin palveluvaraston toimintakonsepti, joka perustuu vendor- managed inventory-toimintamalliin. VMI-toimintaa varten kehitettiin ohjausraportti, jonka avulla kohdeyritys voi valvoa varastotasoja palveluvarastossa, ja jonka avulla toimittajat ohjaavat varastotäydennyksiä palveluvarastolle. Palveluvaraston ja kohdeyrityksen välille luotiin lisäksi RFID-teknologiaa hyödyntävä tilausprosessi. Kohdeyrityksessä voidaan tulevaisuudessa hyödyntää palveluvarastoa kansainvälisen hankinnan logistiikan hallintaan.

Warehouse, PNG Coffee Industry Board Office and Warehouse, Goroka

View of exterior wall to warehouse.

Downpipes, PNG Coffee Industry Board Office and Warehouse, Goroka

Detailed view of downpipes and drainage grill.

PNG Coffee Industry Board Office and Warehouse, Goroka

View past tiered amphitheatre and offices above to air strip beyond.

View along western elevation, PNG Coffee Industry Board Office and Warehouse, Goroka

View past timber blinds to balcony and timber sunscreens.

Under construction, PNG Coffee Industry Board Office and Warehouse, Goroka

View of post being hoisted into position during construction.

Warehouse, PNG Coffee Industry Board Office and Warehouse, Goroka

View of warehouse exterior.

Pole detail, PNG Coffee Industry Board Office and Warehouse, Goroka

Detailed view of poles used in construction. Poles were spliced in their length with steel bars (like 3 pin plugs) and these joints were restrained from splitting with steel strap belts. The belts were tightened with opposing wedges like the old Greene & Greene wrought iron detail.

Warehouse, PNG Coffee Industry Board Office and Warehouse, Goroka

View of warehouse exterior.

Roof structure, internal, PNG Coffee Industry Board Office and Warehouse, Goroka

View to underside of roof with steel beam and insulation.

Post and beam connection, PNG Coffee Industry Board Office and Warehouse, Goroka

Detailed view of cast iron brackets connecting beams and posts.

Front elevation, PNG Coffee Industry Board Office and Warehouse, Goroka

View of front elevation with entrance from exterior.

Post and beam connection, PNG Coffee Industry Board Office and Warehouse, Goroka

Detailed view of cast iron brackets connecting beams and posts.

Agile modeling data warehouse development

Most of the traditional software and database development approaches tend to be serial, not evolutionary and certainly not agile, especially on data-oriented aspects. Most of the more commonly used methodologies are strict, meaning they’re composed by several stages each with very specific associated tasks. A clear example is the Rational Unified Process (RUP), divided into Business Modeling, Requirements, Analysis & Design, Implementation, Testing and Deployment. But what happens when the needs of a well design and structured plan, meet the reality of a small starting company that aims to build an entire user experience solution. Here resource control and time productivity is vital, requirements are in constant change, and so is the product itself. In order to succeed in this environment a highly collaborative and evolutionary development approach is mandatory. The implications of constant changing requirements imply an iterative development process. Project focus is on Data Warehouse development and business modeling. This area is usually a tricky one. Business knowledge is part of the enterprise, how they work, their goals, what is relevant for analyses are internal business processes. Throughout this document it will be explained why Agile Modeling development was chosen. How an iterative and evolutionary methodology, allowed for reasonable planning and documentation while permitting development flexibility, from idea to product. More importantly how it was applied on the development of a Retail Focused Data Warehouse. A productized Data Warehouse built on the knowledge of not one but several client needs. One that aims not just to store usual business areas but create an innovative sets of business metrics by joining them with store environment analysis, converting Business Intelligence into Actionable Business Intelligence.

Desenho e implementação de um data warehouse para a empresa AdClick

Esta dissertação incide sobre a problemática da construção de um data warehouse para a empresa AdClick que opera na área de marketing digital. O marketing digital é um tipo de marketing que utiliza os meios de comunicação digital, com a mesma finalidade do método tradicional que se traduz na divulgação de bens, negócios e serviços e a angariação de novos clientes. Existem diversas estratégias de marketing digital tendo em vista atingir tais objetivos, destacando-se o tráfego orgânico e tráfego pago. Onde o tráfego orgânico é caracterizado pelo desenvolvimento de ações de marketing que não envolvem quaisquer custos inerentes à divulgação e/ou angariação de potenciais clientes. Por sua vez o tráfego pago manifesta-se pela necessidade de investimento em campanhas capazes de impulsionar e atrair novos clientes. Inicialmente é feita uma abordagem do estado da arte sobre business intelligence e data warehousing, e apresentadas as suas principais vantagens as empresas. Os sistemas business intelligence são necessários, porque atualmente as empresas detêm elevados volumes de dados ricos em informação, que só serão devidamente explorados fazendo uso das potencialidades destes sistemas. Nesse sentido, o primeiro passo no desenvolvimento de um sistema business intelligence é concentrar todos os dados num sistema único integrado e capaz de dar apoio na tomada de decisões. É então aqui que encontramos a construção do data warehouse como o sistema único e ideal para este tipo de requisitos. Nesta dissertação foi elaborado o levantamento das fontes de dados que irão abastecer o data warehouse e iniciada a contextualização dos processos de negócio existentes na empresa. Após este momento deu-se início à construção do data warehouse, criação das dimensões e tabelas de factos e definição dos processos de extração e carregamento dos dados para o data warehouse. Assim como a criação das diversas views. Relativamente ao impacto que esta dissertação atingiu destacam-se as diversas vantagem a nível empresarial que a empresa parceira neste trabalho retira com a implementação do data warehouse e os processos de ETL para carregamento de todas as fontes de informação. Sendo que algumas vantagens são a centralização da informação, mais flexibilidade para os gestores na forma como acedem à informação. O tratamento dos dados de forma a ser possível a extração de informação a partir dos mesmos.