8/12/2019 CH-13 Support Software

1/15

Unit 13Support Software: A Supply ChainMonitoring Perspective & Utility of

Software

8/12/2019 CH-13 Support Software

2/15

Topics to study

Introduction to SCMo

Writing a business plan Overview of process documentation system

Support software

2

8/12/2019 CH-13 Support Software

3/15

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

8/12/2019 CH-13 Support Software

4/15

4

SCMo: Set Up & Features

SCMo Set-Up:1. Determination of potentially critical part of the supply chain network

2. 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 AnalysisBug tracking, test case management,

QA status charts

Time Tracking efficient way of creating more accurate estimate oftime

8/12/2019 CH-13 Support Software

5/15

5

Business Plan

A useful document in cases where the project islarge.

New Company/JVC

New Product

Expansion in Capacity

New Markets

Objectives of a Business Plan Communicate strategic direction & company objectives

Communicate tactical agreements Communicates Budget Requirements

Outlines the Financial Implications (costs, revenues etc)

8/12/2019 CH-13 Support Software

6/15

6

Business Plan: Structure

A typical business plan is divided into7-9 sections.

No page limit, depends on case tocase basis.

Contains specific information (noambiguity)

Provides the broad framework of thebusiness (markets, sales network,financials, resource etc.)

8/12/2019 CH-13 Support Software

7/15

7

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

8/12/2019 CH-13 Support Software

8/15

8

Business Plan: Structure

Section 4: Engineering The DevelopmentPlan

Core Technology Development Status Product specifications & features

Section 5: Operations & Manufacturing Customer Focus Make or Buy Quality/Costs/Delivery Supply Chain Manufacturing Process/equipments

8/12/2019 CH-13 Support Software

9/15

9

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

8/12/2019 CH-13 Support Software

10/15

10

Support Software

Even with the availability of variousApplication Software, the following gaps

still remain: Business processes which are not covered in thesesoftware

Integration of Multi vendor supported softwareapplications

Dilemma for companies: Whether tolook at the same vendors to support suchcustomization (expensive) or not

8/12/2019 CH-13 Support Software

11/15

11

Support Software

ARROW

FEDORA

VITAL PILIN

MS Exchange Server 2003

8/12/2019 CH-13 Support Software

12/15

12

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

8/12/2019 CH-13 Support Software

13/15

13

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 havepersistent identifiers down to the level of individual datastreams

8/12/2019 CH-13 Support Software

14/15

14

PILIN

PILIN = Persistent Identifiers andLinking Infrastructure

The Need:To manage vast amount of data being

generated

Objectives: refer Textbook

8/12/2019 CH-13 Support Software

15/15

15

TH NKS