Upload
others
View
1
Download
0
Embed Size (px)
Citation preview
(
(
(
Purpose:
Summary:
IRM as a basis for' long range planningand systems coordination
Fredrik Runnquist, Manager Administration DevelopmentPhilips E1ettronikindustricr ADS-175 88 JARFALLASWEDEN Telephone: 0758-22008
Orjan Grape, consultantSAGUS ADDolinders Plan 2S-112 24 STOCKHOLMSWEDEN Telephone: 08-132985
The intention is to describe an approach used at PhilipsElektronikindustrier to combine the IRM-study with longrange planning of Administration Development
Presentation and discussion of methods for systems coordinationand planning of AD, based on an information- and systemstructure study carried out in 1986. This study has been thebasis for long range planning and development of databasesand applications.
Contents: 1. Information and system structure study- background- methodology- implementation- results
2 Administration Development Plan
3. Project initialization and planning
4. Findings
Philips Eleklronlkfndustrler AB
Fredrlk nunnqulSI. Orion Grope Information and system structure study
[ B_A_C_K_G_R_O_U_N_D ~J
* REQUIREMENTS FOR FLEXIBILITY- knowledge of business objects and their relations (- knowledge of external factors and effects- flexible information systems- models and support for simulating and prognoses
* IRREGULAR AND BADLY COORDINATEDADMINISTRATION DEVELOPMENT
* TASK DISTRIBUTION AND SYSTEMS INTERFACEPROBLEMS
* INFORMATION AND SYSTEMS STRUCTURE- lack of common concepts- bad system structure ("bridges", "islands" etc)- redundancy in information storage and processing- difficulties to find stored info and to determine
quality of information as well as responsible persons.
-1-
Philip s Eleklronlkrnduslrler J\B
Fredrlk "unnquISl. O'lan'Grape Information and system structure study
" [~__M_ET_H_O_D_O_LO_G_y__~JFlexibility
Confusion of concepts Responsibility for dltl ?System dill dictionary? no.... f' f . ~
• 0-1 bl ,........ty 0 In ormlhon <LOU:U Irepro ems'. Whit kind of systems do we need to denio?
ENTERPRISE MODELLING
(c )
IDECOMPOSITION DIAGRAMSBusiness objects as subject areas, functions,goal, critical success factors, organization,data processing applications etc.
ENTITY- RELATIONSHIP MODELSAn overwiew map of the data needed torun the enterprise
DATA FLOW DIAGRAMSData flow between subject areas, functions
1"-. I11111 111111111111111n INFORMATION PROCESSING MATRICESMatrices showing relations between data andbusiness functions, data processing appl. etc.
ANA YSIS Analysis of information and system structure,DP applications etc.
•Basis forAD - planning
INFORMATION AND SYSTEM ARCHITECTUREDescription of changes and recommendations formeasures needed for each system area
I - future data processing (appl. and databases)
~rechnical enVimnme~t (hardware. communic.)
: System design ::: principles and .:i;: rules ,.
Systemscoordination
Projects concerning"urgent" interfaceproblems
Systemsadministration
-2-
Philips Eleklronlklnduslrler AD
Fre.rlk Runnqul't. OrJan Grape Information and system structure study
IMPLEMENTATION J~~ DATA flOW DIAGRAMS
INFORMATIONPROCESSING MATRICES
ANALYSIS OPTHE ENTERPRI'SE
• BASED UPON THE PRINCIPLES OF IRM, ie
THE INFORMATION IS REGARDED AS ACOMMON AND ESSENTIAL RESOURCE INTHE BUSINESS ACTIVITY.
• A DATA- DRIVEN DEVELOPMENT PLANDERIVES FROM 2 PRINCIPLES:
- START ON A STABLE PLATFORM
- THE INFORMATION REQUIREMENTS,PROCEDURES AND THE ORGANIZATIONSTRUCTURES CHANGE MORE OFTENTHAN THE DATA STRUCTURES OF THETHE ENTERPRISE
-3-
(
(
(
l
Philips Eleklronlklnduslrlcr AB
Fre.rl' "unnqul,'. Orlan Grape Information and system structure study
[~.__I_M_P_l_E_M_E_N_T_A_T_lo__~J
* THIS WAS REAUZED AS A SEPARATE PROJECTDURI G 5 MONTHS
Steeringgroup: AD - policyboardProject group: 2 pers.Reference group: 1·1 persons, top and middle
management
Representong alU bus9lflless areas and witha good! knowledge of current business
Working sessions completed andbacked - up llIat hornell
* FOCUS! G ON I!IPIFU ARY· AREAS SUCH ASMARKETING/S l.U G, DEVELOPMENT,PRODUCT~O , D~STR~BUTION,CUSTOMER
SUPPORT AND THEN MANAGEMENT ANDFINANCE
* ENTERPRISE MODELS (OWERVIEW)
* USING DRAWING -TOOL AND SINCE1987 CASE-TOOL
-4-
Philips Eleklronlklnduslrler AD
. Fredrl> Runnqul,t. O~on Grope Infonnation and system structure study
[~ R_E_S_U_L_T_S ~J~~Gr.J~ INFORMATION AND~~g SYSTEM ARCHITECTURE
SySlems
Ildmlnlslrallon
ProjeCIS concerning- urgenl- Interlaceproblems
jj:-:.:.:.:.:.:.:.:.:.: ...: ...:.:....
* INCREASED KNOWLEDGE ABOUT BUSINESSOBJECTS AND THEIR RELATIONS
* CASE-TOOL USED FOR DOCUMENTATION
* BASIS FOR URGE T ACTIONS
Oasis torAD - planning
* SYSTE AREAS IN EED OF NEW ORCHANGED DATA PROCESSING- PROJECT MANAGE E T- MARKETING/SELLING AD INISTRATION- TECHNICAL AD INISTRATION- RESULT CONTROL
-5-
(
Philips Eleklronlklnduslrler An
Fre"'1< nunnqulst, Orion Grope Information and system structure study
l_' R_E_S_U_L_T_s ~J
Systemscoordination
(
( * A FUNCTION FOR SYSTEMS COORDINATION
- INFOR ATION AND SYSTEMS DICTIONARY,DESCRIPTiONS OF BUSINESS ACTIVIT!ES
- -REFEREE- FOR SOLVING DIFFERENTOPINIONS ABOUT INTERFACES BETWEENTHE PROJECTS AND THE SYSTEMS
(- ACCOMPLISH ANALYSIS IN ORDER TO
ACHIEVE MORE EFFECTIVE SYSTEMSINTEGRATION AND COORDINATION
- NEW SYSTEMS DEVELOPMENT MODEL
-6-•
Philips E Ie t<.lronlklndustrler AU
Fredrlk RUnnqulSt. Or)on Grope Infonnation and system structure study
[~ R_E_S_U_L_T_S ~J".::,:,:,::",::""::,;,:::,::",,:::,"::,:::::,,,.,:::'::::::
:i: Systems design!:::! principles and!::' rules::~~! ~!!".:::::::::::::;:::::::::::::::::::::::::;::::::::::::::::::.. "
. * SYSTEMS DESIGN PRINCIPLES AND RULES
- DATA-DRIVEN DEVELOPMENT
- DEVELOPING AND CONSIDERING THECOMPLETE SYSTEM (data processing,personnel, organization and routines)
- DEVELOPMENT AND LIFE CYCLETERMINATION FUNCTION BY FUNCTIONAND STEP BY STEP
- EFFECTIVE AND HIGH QUALITY DEVElOPMENT, WITH PROTOTYPING AND QUAUTYCONTROL AIMED AT -DOING THE RIGHTTHING FROM THE START-
- APPLICATION DEVELOPMENT PRINCIPLES:
* 0 l Y 1 TERMINAL OR PC AT EACH DESK* APPOINT FUNCTION RESPONSIBLE FOR
DATA* ACQUIRE DATA ONLY ONCE AND AS
CLOSE TO SOURCE AS POSSIBLE-7-
(
(
Philips Eleklronlklnduslrlcr AS
Fredrlk.. nunnquisi. Orlan Grape
GENERAL:
AD-PLAN
COMPANY GOALS
PROFITABILITY
GROWTH VOLUME
PRODUCT - LIFE - CYCLES
(
ADMINISTRATIVE: lEAD - TIME
EFFICIENCY
ORGANIZATIONALSTRUCTURES
-8-
I
Philips Elektronlklndustrlcr AD
Fredrlk nunnquisi. OrJan Grape AD-PLAN
( APPLICATION AREAS)
DIVISIONA B
* SYSTEM STRUCTURE - ++
* MARKET ADMINISTRATION + + + (
* PROJECT MANAGEMENT ++ +
* PRODUCT MANAGEMENT ++
* MPS - ++
* LOGISTICS - -
* ECONOMY + ++
* PERSONNEL - -
* OFFICE AUTOMATION ++ ++
* INTEGRATION OF TECNICAlAND ADMINISTRATION DP + ++
+ +: Priority
+ :Priority partly
..:. : No priority
-9-
Phlllp5 Eleklronlklnduslrler AS
Fredrl k nunnqulsi. Orlan Grope Project initialization and planning
[_•. P_R_O_C_E_D_U_R_E__~J
COMPANYGOALS
INFORMATIONAND SYSTEMSSTRUCTURESTUDY
PRIORITY
N
H
T
.. ~ E
C
NOPRIORITY
PRIORITYPARTLY+
PRIORITIES
PERAPPLIC. AREA
++
ADPOLICYBOARD.CEO
(
(
L
G
o
o
y
II
~ IPROJECT ~SPECIFICATION.. Goals" Borderlines.. Organization
ADPOLICYBOARD.CEO
.. Markets
.. Products
.. Economy
.. Quality
.. Personnel
( ADDEPARTEMENGOALS
( )
PROJECTS- 10-
Philips Eleklronlklnduslrler AD
fredrlk Runngulsl, Orlan Grape
[~ F_IN_D_I_N_G_S__~)
1. APPROACES THAT TURNED OUTTO BE SUCCESSFUL
II
/""""
- ACTIVE AD-DEPARTEMENT ROLE
- BOTTOM UP AND TOP DOWN
- PAY-OFF CALCULATION AS AN ACTIVE TOOL
- 11 -