MétaCan
Menu
Back to cohort
Record W2807652022 · doi:10.1155/2018/4632195

On the Design Complexity of Cyberphysical Production Systems

2018· article· en· W2807652022 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

VenueComplexity · 2018
Typearticle
Languageen
FieldEngineering
TopicFlexible and Reconfigurable Manufacturing Systems
Canadian institutionsEngineering Link (Canada)
FundersLinköpings Universitet
KeywordsProduction (economics)Computer scienceBiochemical engineeringEngineeringEconomics

Abstract

fetched live from OpenAlex

Establishing mass‐customization practices, in a sustainable way, at a time of increased market uncertainty, is a pressing challenge for modern producing companies and one that traditional automation solutions cannot cope with. Industry 4.0 seeks to mitigate current practice’s limitations. It promotes a vision of a fully interconnected ecosystem of systems, machines, products, and many different stakeholders. In this environment, dynamically interconnected autonomous systems support humans in multifaceted decision‐making. Industrial Internet of Things and cyberphysical systems (CPSs) are just two of the emerging concepts that embody the design and behavioral principles of these highly complex technical systems. The research within multiagent systems in manufacturing, by embodying most of the defining principles of industrial CPSs (ICPSs), is often regarded as a precursor for many of today’s emerging ICPS architectures. However, the domain has been fuzzy in specifying clear‐cut design objectives and rules. Designs have been proposed with different positioning, creating confusion in concepts and supporting technologies. This paper contributes by providing clear definitions and interpretations of the main functional traits spread across the literature. A characterization of the defining functional requirements of ICPSs follows, in the form of a scale, rating systems according to the degree of implementation of the different functions.

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: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.583
Threshold uncertainty score0.448

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.001
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.111
GPT teacher head0.247
Teacher spread0.136 · 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