Sei sulla pagina 1di 15

Support Software: A Supply Chain Monitoring Perspective & Utility of Software

Unit 13

Topics to study

Introduction to SCMo Writing a business plan Overview of process documentation system Support software

Objectives of SCMo

Prevention of stock-out and over supply Early warnings and elimination of bull-whip effect Optimised allocation in bottleneck situations due to network-wide inventory and demand transparency Elimination of time lags in the information flow Synchronisation of demand information Smooth and secure supply with minimal safety inventories Increased speed and flexibility of supply networks Reduction of non value adding cost due to trouble shooting efforts and administrative efforts to manage and control material flow Decrease in premium freight Avoidance of scrap due to obsolescence in case of engineering
3

SCMo: Set Up & Features

SCMo Set-Up:
1. 2.

Determination of potentially critical part of the supply chain network Process Mapping, i.e. shortage risk & effect, long lead & reaction times, high total inventory cost, frequent engineering changes

Features

Releases and Iterations ( act of repetitive activity ) planning way to create project plan. Dashboard project status reporting tool To-Do List identify & list the integrated assignment to be doe Integrated Quality Analysis Bug tracking, test case management, QA status charts Time Tracking efficient way of creating more accurate estimate of time
4

Business Plan

A useful document in cases where the project is large.


New Company/JVC New Product Expansion in Capacity New Markets Communicate strategic direction & company objectives Communicate tactical agreements Communicates Budget Requirements Outlines the Financial Implications (costs, revenues etc)

Objectives of a Business Plan


Business Plan: Structure


A typical business plan is divided into 7-9 sections. No page limit, depends on case to case basis. Contains specific information (no ambiguity) Provides the broad framework of the business (markets, sales network, financials, resource etc.)

Business Plan: Structure


Section 1: Executive Summary Section 2: Business Definition


The Opportunity The potential markets Economic Scenario (macro & micro)

Section 3: Sales & Marketing


Markets (STP) Sales Plan Marketing Plan Customer Support Plan

Business Plan: Structure

Section 4: Engineering The Development Plan


Core Technology Development Status Product specifications & features

Section 5: Operations & Manufacturing


Customer Focus Make or Buy Quality/Costs/Delivery Supply Chain Manufacturing Process/equipments

Business Plan: Structure

Section 6: Senior Management


Experience Credibility Organization Structure

Section 7: Financials
Cash Flow Revenue Models 3-5 year estimates on P&L Break Even Point Return on Investment

Section 8: Appendices

Support Software

Even with the availability of various Application Software, the following gaps still remain:
Business processes which are not covered in these software Integration of Multi vendor supported software applications

Dilemma for companies: Whether to look at the same vendors to support such customization (expensive) or not

10

Support Software
ARROW FEDORA VITAL PILIN MS Exchange Server 2003

11

ARROW

Combines Open source and Proprietary software (Fedora, VITAL, OJS) Provides a platform for promoting research output in the ARROW context. Safeguard digital information Gathers institutional research into one place. Allows information from many repositories to be gathered and searched in one step Enables sharing of resources Enables effective communication & collaboration between researchers
12

Project ARROW

ARROW project will:


Identify and test software or solutions to support institutional digital repositories comprising e-prints, digital thesis and electronic publishing

Objective:
Solution for storing any digital output

Arrow & Fedora


Arrow wanted a robust, well developed underlying platform, a flexible object oriented data model to be able to have persistent identifiers down to the level of individual data streams
13

PILIN
PILIN = Persistent Identifiers and Linking Infrastructure The Need:

To manage vast amount of data being generated

Objectives: refer Textbook

14

THANKS..

15

Potrebbero piacerti anche