<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>IRM as a basis for' long range planning and systems coordination</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Fredrik Runnquist</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Manager Administration Development</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Orjan Grape</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>consultant</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>SAGUS AD Dolinders Plan</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>STOCKHOLM SWEDEN Telephone:</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Philips E1ettronikindustricr AD S-175 88 JARFALLA SWEDEN Telephone: 0758-22008</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>The intention is to describe an approach used at Philips Elektronikindustrier to combine the IRM-study with long range planning of Administration Development Presentation and discussion of methods for systems coordination and planning of AD, based on an information- and systemstructure study carried out in 1986. This study has been the basis for long range planning and development of databases and applications.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Purpose:
Summary:
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
~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 COORDINATED</p>
      <p>ADMINISTRATION DEVELOPMENT
* TASK DISTRIBUTION AND SYSTEMS INTERFACE</p>
      <p>PROBLEMS
* 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.
Philip s Eleklronlkrnduslrler J\B
Fredrlk "unnquISl. O'lan'Grape Information and system structure study
"
[~
_ _M_ET_H_O_D_O_LO_G_y_ _
~J
(</p>
      <p>Flexibility</p>
      <p>Confusion of concepts Responsibility for dltl ?
System dill dictionary? no.... f' f ~</p>
      <p>•LO0U-:U1Ireproblems,........ty 0 In ormlh.on &lt;
'. Whit kind of systems do we need to denio?</p>
      <p>ENTERPRISE MODELLING
c</p>
      <p>)
I</p>
      <p>DECOMPOSITION DIAGRAMS
Business objects as subject areas, functions,
goal, critical success factors, organization,
data processing applications etc.</p>
      <p>ENTITY - RELATIONSHIP MODELS
An overwiew map of the data needed to
run the enterprise</p>
    </sec>
    <sec id="sec-2">
      <title>DATA FLOW DIAGRAMS Data flow between subject areas, functions</title>
      <sec id="sec-2-1">
        <title>Systems­ administration</title>
      </sec>
      <sec id="sec-2-2">
        <title>Projects concerning "urgent" interface problems</title>
        <p>1"-. I11111 111111111111111n INFORMATION PROCESSING MATRICES
Matrices showing relations between data and
business functions, data processing appl. etc.</p>
        <p>ANA YSIS</p>
        <p>Analysis of information and system structure,
DP applications etc.</p>
        <p>INFORMATION AND SYSTEM ARCHITECTURE
Description of changes and recommendations for
measures needed for each system area</p>
        <p>I - future data processing (appl. and databases)
~rechnical enVimnme~t (hardware. communic.)</p>
      </sec>
      <sec id="sec-2-3">
        <title>Systems coordination</title>
      </sec>
      <sec id="sec-2-4">
        <title>Basis for AD - planning</title>
        <p>: System design ::
: principles and .:i
;: rules ,.
Philips Eleklronlklnduslrler AD
Fre.rlk Runnqul't. OrJan Grape Information and system structure study</p>
        <p>IMPLEMENTATION
~~ DATAflOWDIAGRAMS</p>
        <p>INFORMATION</p>
        <p>PROCESSING MATRICES
ANALYSISOP
THE ENTERPRI'SE
(
• BASED UPON THE PRINCIPLES OF IRM, ie
THE INFORMATION IS REGARDED AS A
COMMON AND ESSENTIAL RESOURCE IN
THE BUSINESS ACTIVITY.
• A DATA- DRIVEN DEVELOPMENT PLAN
DERIVES FROM 2 PRINCIPLES:
- START ON A STABLE PLATFORM
- THE INFORMATION REQUIREMENTS,
PROCEDURES AND THE ORGANIZATION
STRUCTURES CHANGE MORE OFTEN
THAN THE DATA STRUCTURES OF THE
THE ENTERPRISE
Philips Eleklronlklnduslrlcr AB
Fre.rl' "unnqul,'. Orlan Grape Information and system structure study
[~.</p>
        <p>__I_M_P_l_E_M_E_N_T_A_T_l_o_
~J
* THIS WAS REAUZED AS A SEPARATE PROJECT</p>
        <p>DURI G 5 MONTHS
(</p>
        <p>Steeringgroup: AD - policyboard
Project group: 2 pers.</p>
        <p>Reference group: 1·1 persons, top and middle
management
Representong alU bus9lflless areas and with
a good! knowledge of current business
Working sessions completed and
backed - up llIat hornell
( * FOCUS! G ON I!IPIFU ARY· AREAS SUCH AS
MARKETING/S l.U G, DEVELOPMENT,</p>
        <p>PRODUCT~O , D~STR~BUTION,CUSTOMER
l SUPPORT AND THEN MANAGEMENT AND</p>
        <p>FINANCE
* ENTERPRISE MODELS (OWERVIEW)
* USING DRAWING -TOOL AND SINCE
1987 CASE-TOOL</p>
        <p>-4</p>
        <p>Infonnation and system</p>
        <p>structure study
[~
SySlems­
Ildmlnlslrallon</p>
        <p>ProjeCIS concerning
- urgenl- Interlace
problems</p>
        <p>R_E_S_U_L_T_S
~~Gr.J~
~~g</p>
        <p>INFORMATION AND
SYSTEM ARCHITECTURE</p>
        <p>~J
* I N C R E A S E D K N O W L E D G E A B O U T B U S I N E S S</p>
        <p>O B J E C T S A N D T H E I R R E L A T I O N S
* C A S E - T O O L U S E D F O R D O C U M E N T A T I O N
* B A S I S F O R U R G E T A C T I O N S</p>
        <p>Oasis tor</p>
        <p>AD - planning
* S Y S T E A R E A S I N E E D O F N E W O R</p>
        <p>C H A N G E D D A T A P R O C E S S I N G
- P R O J E C T M A N A G E E T
- M A R K E T I N G / S E L L I N G A D I N I S T R A T I O N
- T E C H N I C A L A D I N I S T R A T I O N
- R E S U L T C O N T R O L
Philips Eleklronlklnduslrler An
Fre"'1&lt; nunnqulst, Orion Grope Information and system structure study</p>
        <p>R_E_S_U_L_T_s
Systems
coordination
~J
(
(
( * A FUNCTION FOR SYSTEMS COORDINATION
- INFOR ATION AND SYSTEMS DICTIONARY,</p>
        <p>DESCRIPTiONS OF BUSINESS ACTIVIT!ES
- -REFEREE- FOR SOLVING DIFFERENT
OPINIONS ABOUT INTERFACES BETWEEN
THE PROJECTS AND THE SYSTEMS
- ACCOMPLISH ANALYSIS IN ORDER TO
ACHIEVE MORE EFFECTIVE SYSTEMS</p>
        <p>INTEGRATION AND COORDINATION
- NEW SYSTEMS DEVELOPMENT MODEL</p>
        <p>Infonnation and system structure study
[~</p>
        <p>R_E_S_U_L_T_S
".::,:,:,::",::""::,;,:::,::",,:::,"::,:::::,,,.,:::'::::::
:i: Systems design!:
::! principles a n d !
:~:~!' r u l e s : :~!!
".:::::::::::::;:::::::::::::::::::::::::;::::::::::::::::::.. "
~J
. *</p>
        <p>S Y S T E M S</p>
        <p>D E S I G N</p>
        <p>P R I N</p>
        <p>C I P L E S A N D</p>
        <p>R U L E S</p>
        <p>D A T A - D</p>
        <p>R I V E N</p>
        <p>D E V E L O P M E N T
D E V E L O P I N G A N D C O N S I D E R I N G T H E
C O M P L E T E S Y S T E M ( d a t a p r o c e s s i n g ,
p e r s o n n e l , o r g a n i z a t i o n a n d r o u t i n e s )
D E V E L O P M E N T A N D L I F E C Y C L E
T E R M I N A T I O N F U N C T I O N B Y F U N C T I O N
A N D S T E P B Y S T E P
EFFECTIVE A N D H I G H Q U A L I T Y D E V E l O P ­
M E N T , W I T H P R O T O T Y P I N G A N D Q U A U T Y
C O N T R O L A I M E D A T - D O I N G T H E R I G H T
T H I N G F R O M T H E
STARTA P P L I C A T I O N D E V E L O P M E N T P R I N C I P L E S :
* 0 l Y 1 T E R M I N A L OR P C A T E A C H D E S K
* A P P O I N T F U N C T I O N R E S P O N S I B L E F O R</p>
        <p>D A T A
* A C Q U I R E D A T A O N L Y O N C E A N D A S</p>
        <p>C L O S E T O S O U R C E A S P O S S I B L E</p>
        <p>- 7
(
(</p>
        <p>COMPANY GOALS</p>
        <sec id="sec-2-4-1">
          <title>PROFITABILITY</title>
          <p>GROWTH VOLUME
PRODUCT - LIFE - CYCLES
ADMINISTRATIVE: lEAD - TIME</p>
        </sec>
        <sec id="sec-2-4-2">
          <title>EFFICIENCY</title>
          <p>ORGANIZATIONAL</p>
        </sec>
        <sec id="sec-2-4-3">
          <title>STRUCTURES</title>
          <p>( APPLICATION AREAS)
* SYSTEM STRUCTURE
* MARKET ADMINISTRATION
* PROJECT MANAGEMENT
* PRODUCT MANAGEMENT
* MPS
* LOGISTICS
* ECONOMY
* PERSONNEL
* OFFICE AUTOMATION
* INTEGRATION OF TECNICAl</p>
          <p>AND ADMINISTRATION DP
+ +: Priority
+ :Priority partly
..:. :No priority</p>
          <p>DIVISION
A B
- ++
+ + + (
++ +
++
- ++
-
+ ++
-
++ ++
+ ++
(</p>
          <p>Project initialization and planning</p>
          <p>~J
~</p>
          <p>PROJECT
SPECIFICATION
.. Goals
" Borderlines
.. Organization</p>
          <p>NO
PRIORITY</p>
          <p>I
I</p>
          <p>I
~</p>
          <p>PROJECTS
ADPOLICY
BOARD.</p>
          <p>CEO</p>
          <p>PRIORITIES</p>
          <p>PER
APPLIC. AREA
.. ~ E</p>
          <p>T
C
H
N
o
L
o
G
y
[~
_
~)
1. APPROACES THAT TURNED
TO BE SUCCESSFUL
OUT</p>
          <p>/ I I """"
- ACTIVE AD-DEPARTEMENT ROLE</p>
          <p>BOTTOM UP AND TOP DOWN
PAY-OFF CALCULATION AS AN ACTIVE TOOL
( 2. RESULTS
- CONTINOUS PLANNING IN THE BUDGET</p>
          <p>PROCESS ACCOMPLISHED
- FLEXIBILITY ACHIEVED
- DETAIL DISCUSSIONS VANISHED
( 3. FUTURE?
\
- KEEP IT SIMPLE
- IS SYSTEMS COORDINATION</p>
          <p>NECESSARY?</p>
        </sec>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>