• Aucun résultat trouvé

Boundary Objects: Improving Inter-organizational Communication

N/A
N/A
Protected

Academic year: 2021

Partager "Boundary Objects: Improving Inter-organizational Communication"

Copied!
1
0
0

Texte intégral

(1)

Contact: Allan Fong | [email protected] | 516.984.3072 | Massachusetts Institute of Technology | Master of Science candidate | Department of Aeronautics and Astronautics Research Advisors: Ricardo Valerdi and Jayakanth Srinivasan | This research is sponsored by members of the LAI Consortium and The Aerospace Corporation

Boundary Objects:

Improving Inter-organizational communication

Boundary Object Attributes

•Medium •Granularity •Staleness Factor •Malleability •Inclusivity •Synchronization •Importance •Layers •Context Type •Traceability

•Map organizational interactions, Design Structure Matrix •Identify key areas of interests

•Correlate boundary object usage and social interactions

*The figures below are notional examples

Motivation

Methodology

Implications

This study focuses on inter-organizational interactions

in large complex system engineering programs. The

aim is to identify and provide ways to reduce

disconnects that occur at organizational boundaries

by effectively using and representing knowledge and

information in boundary objects.

Programs and projects suffering from “organizational” disconnects due to unclear documentation, failure to communicate, etc, will often result in rework and additional resources.

Systems Integrators become the translators and interpreters at these interfaces, managing and regulating the follow of boundary objects between the communities.

Boundary objects are a useful construct to understand the role

and value of Systems Integrator.

Boundary Objects

Boundary objects are

objects that are flexible enough to adapt to local needs yet specific enough to maintain a common identity across different

interpretations (Star and

Griesemer, 1989) A. B. and C. are examples of boundary objects that bridge

knowledge and information gaps by enabling communication, coordination, and collaboration across boundaries.

Systems Integrators

•Identify common sources of organizational disconnects •Categorize successful boundary objects and their attributes •Provide suggestions and recommendations to reduce disconnects

Boundary objects evolve as interfaces changes

System Integrator

Case Studies

•Future Combat System

•Transformation Communications

Satellite (TSAT) system

TACOM 24 Aug 2005, case 05-179

(A) Medium (B) Granularity (C) Staleness Factor (D) Malleability (E) Inclusivity (F) Synchronization (G) Importance (H) Layers (I) Context Type (J) Traceability

Communication Coordination Collaboration

Customer

Prime Contractor

Sub-Contractor

Références

Documents relatifs

In this case, the emblematic object of planning, the schedule, is viewed as a boundary object that sits at the interfaces between five social worlds—maintenance, production,

The results obtained by the observation conducted us to know; the activities performed by the stakeholders (customer, waiter/waitress, cook, owner, and cashier);

By looking into the incentives of all the participants of a project, we will unpack the trading zones of digital history projects, to gain an understand- ing of how

In the case where A, B, C, D are items which can be represented in terms of the same set of features, a formal definition has been proposed for analogical proportions in the setting

Third, I present an overview of electronic cigarette use and its position within harm reduction in the UK and highlight some contextual factors that influence the discourse

This paper is structured as follows. First, a representa- tive scenario is introduced. It consists of an organizational reference model and an example document. Section III

The effect of collaborative scope on firm performance, however, also depends on both mechanisms but in opposite directions: while the influence of collaborative scope on

In this section, we give an overview of different approaches used to manage dependencies between SLAs involved in a service composition according to two main categories: