Means to support collaboration for remote industrial facilities such as mining are an important topic, especially in Australia, where major mining sites can be more than a thousand kilometers from population centres. Software-based collaboration and maintenance solutions can help to reduce costs associated with these remote facilities. In this paper, we report on our collaborative engineering project providing a decision support solution tailored for Australian needs. We present two application examples: one related to incident handling in industrial automation, the other one in the area of smart energy systems.
Early academic approaches feature the term collaborative engineering in @cite_30 and @cite_40 . Means for sharing and collaborative interaction on documents and other resources are presented and most ideas have meanwhile found entry into commercial collaboration frameworks. Further related academic approaches comprise examinations such as the impact of collaborative engineering on software development (see, e.g., @cite_3 ) and collections software challenges for the development of ultra-large scaled systems @cite_11 , where collaboration is limited to the development phase.
@cite_30 @cite_40 @cite_3 @cite_11
2026006690 2135902285 1527822636 101199937
Information shying and decision coordination arc central problems for collaborative product dcvclopmcnt and enterprise-wide coordination. Designcrs, manufacturing cnginccrs, and marketing engineers nccd to assess the impact of their decisions and notify affected parties as the product evolves. Yct, cxisting CAD tools tend to isolate information at tool boundarics, or make overly-strong commitmcnts to an all-encompassing common model. Furthcrmorc, there is oftcn no automatcd support outside of thc design function. The SHADE (SHAred Dcpcndcncy Engineering) project is working on knowlcdge-b cd methods to improve the communication in the product dcvclopmcnt process. Thcre arc three mare components of SHADE: a shared knowledge representation (language and domain-specific vocabulary); protocols for information cxch,’mgc enabling change notification and subscription; and facilitation scrviccs such ,as contcnt-dircctcd routing , nd intelligent matching of information consumers and producers. SHADE is being applied to sew’r d real domains, including the Palo Alto Collaborative Tcstbcd. Abstract A collaborative development environment (CDE) is a virtual space wherein all the stakeholders of a project—even if distributed by time or distance—may negotiate, brainstorm, discuss, share knowledge, and generally labor together to carry out some task, most often to create an executable deliverable and its supporting artifacts. CDEs are particularly useful as places where engineers may collaborate to solve problems. Here we focus on software developers in their tasks of designing, implementing, deploying, and maintaining high quality software-intensive systems where they are physically separated and make use of the Internet as the basis for their interactions. In this paper, we examine the points of friction in the software development process and the mechanisms that reduce that friction. We then survey a variety of sites, both inside and outside the software domain, which provide some of these mechanisms. We conclude with observations as to what a CDE is, what it is not, and what it can become. Abstract : The U. S. Department of Defense (DoD) has a goal of information dominance to achieve and exploit superior collection, fusion, analysis, and use of information to meet mission objectives. This goal depends on increasingly complex systems characterized by thousands of platforms, sensors, decision nodes, weapons, and warfighters connected through heterogeneous wired and wireless networks. These systems will push far beyond the size of today s systems and systems of systems by every measure: number of lines of code; number of people employing the system for different purposes; amount of data stored, accessed, manipulated, and refined; number of connections and interdependencies among software components; and number of hardware elements. They will be ultra-largescale (ULS) systems. The sheer scale of ULS systems will change everything. ULS systems will necessarily be decentralized in a variety of ways, developed and used by a wide variety of stakeholders with conflicting needs, evolving continuously, and constructed from heterogeneous parts. People will not just be users of a ULS system; they will be elements of the system. Software and hardware failures will be the norm rather than the exception. The acquisition of a ULS system will be simultaneous with its operation and will require new methods for control. These characteristics are beginning to emerge in today s DoD systems of systems; in ULS systems they will dominate. Consequently, ULS systems will place unprecedented demands on software acquisition, production, deployment, management, documentation, usage, and evolution practices.