Case Study

1
Case Study
2
Study1

• Decision-making process
• a- Top management handles strategic, operational,
  tactical and routine decisions
• b- Routine decisions are delegated to middle
  management
• c- Routine decisions are delegated to empowered
  employees
• d- Tactical decisions are delegated to middle
  management
• e- Tactical and routine decisions are delegated
  to empowered employees
• f- Operational decisions are delegated to middle
  management
• g- Operational, tactical and routine decisions
  are delegated to empowered employees
• Infostructure configuration
• a-Traditional type (Mostly stand-alone set-up -
  Often less than 1 computer per employee)
• b-Network type (wherever they physically are,
  computers are part of the infostructure when
  connected)
• c-Individual type (computers, assigned to
  individuals, can be part of the infostructure
  when plugged in the office, or not)
• d-Landscape type (most computers are permanent
  parts of the infostructure, wired to fixed
  workstations)
• Autonomy of infostructure components
• a-Very little or not at all, it is a
  mainframe-based, monolithic, one-string type of
  structure
• b-Some components are autonomous, but the main
  part is a traditional one-string structure
• c-Most components are autonomous and independent,
  integration in networks is/would be difficult
• d-Very highly, all components are configurated to
  be usable autonomously or in different types of
  networks with highest flexibility

3
Study2

• Customization of infostructure components
• a-Very little or not at all, you use mostly
  standard versions
• b-Some components are customized, others are
  standard
• c-Very highly, most components have been
  adapted/developed especially for your
  organization
• d-Very highly, most components (or at least their
  user's interface) are customized to the
  individual user's needs
• Compatibility of infostructure components
• a-Very little or not at all, most components are
  customized for a stand-alone use
• b-Some components are compatible, others are not
• c-Most components are compatible within the
  internal infostructure, but not externally
• d-Very highly, most components are compatible
  with each other and with external
  hardware/software/systems
• Re-usability of infostructure components
• a-Yes, it is a priority - all developments are
  programmed in reusable modules, data are
  separated from programming
• b-Sometimes, it depends on the type of
  programming you do
• c-Not really, most programming is done with one
  particular goal in mind, reusability is not a
  priority
• d-Your organization does not do (nor does it
  commission) any significant programming

4
Study3

• Products customization
• a- None Customers cannot choose anything
• b- Minimal Customers choose within existing
  range (choice of size, color, etc.)
• c- Moderate Customers can select prepared
  options for a relatively unique end-result
• d- Optimal Customers help design a unique
  product for their unique needs
• Products Delivery
• a- Customers must go to distribution points
  (usually quite far)
• b- Customers must go to distribution points
  (usually close-by)
• c- Customers can get delivery at a place chosen
  by them
• d- Customers must go to suppliers place
• Office Structure
• a- Office is adapted to molecular work
• b- Office is not adapted to molecular work

5
Study 4

• Select an answer for each of above questions, and
  justify this answer with examples and concrete
  observations
• Review the above presentation, try to apply to
  the case study and explain findings
• Review the textbook, find the topics that are
  affected by molecularization, and explain using
  the case study as concrete example
• Provide conclusions and recommendations what
  should your case study do to improve its
  molecularization level?