MétaCan
Menu
Back to cohort
Record W4386195813 · doi:10.1002/sys.21716

Team and communication impacts of remote work for complex aerospace system development

2023· article· en· W4386195813 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueSystems Engineering · 2023
Typearticle
Languageen
FieldPsychology
TopicTeam Dynamics and Performance
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsAerospaceContext (archaeology)Work (physics)Bridge (graph theory)Computer scienceKnowledge managementSystems engineeringEngineeringEngineering management

Abstract

fetched live from OpenAlex

Abstract Remote work is becoming increasingly common, a trend accelerated by the global COVID‐19 pandemic. Existing remote work research fails to address the challenges and needs of engineers working remotely in Complex Aerospace System Development (CASD), the field responsible for creating and operating aerospace systems. This article presents an exploratory study to understand the challenges, benefits, and strategies when working remotely in CASD. We interviewed 12 CASD engineers working remotely at a major aerospace corporation. We ground our findings in six characteristics of CASD work (complex systems; design paths and feedback loops; relationships with suppliers, customers and regulators; distinct knowledge and skills; one‐off innovation; and high cost of experimentation) and discuss how each of these characteristics challenges remote work. The findings show that CASD requires many teams to work together, and this is encouraged through informal communication, which almost disappears in a remote setting. CASD requires frequent feedback, and we found that feedback was slow when working remotely. Participants found it challenging to demonstrate systems to customers and verify drawings with suppliers, and the interpersonal relationships, which help to bridge disciplinary divides, were harder to maintain remotely. The one‐off nature of the systems designed meant that conceptual work was important, but participants lacked the virtual tools to do this effectively. Lastly, testing hardware components required close virtual communication between technicians and engineers, which was tricky in a detail‐oriented context. This study motivates areas for future work to better understand and address the nuances of remote work by engineers in CASD.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.409
Threshold uncertainty score0.382

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.028
GPT teacher head0.280
Teacher spread0.252 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it