MétaCan
Menu
Back to cohort
Record W2132547257 · doi:10.5539/jsd.v6n11p1

Infrastructure Management Process Maturity Model: Development and Testing

2013· article· en· W2132547257 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.
fundA Canadian funder is recorded on the work.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueJournal of Sustainable Development · 2013
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBusiness Process Modeling and Analysis
Canadian institutionsUniversity of British Columbia
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsCapability Maturity ModelMaturity (psychological)Service Integration Maturity ModelComputer scienceProcess (computing)Benchmark (surveying)Work (physics)Process managementInformation technology managementKnowledge managementInformation systemTelecommunicationsManagement information systemsBusinessEngineering

Abstract

fetched live from OpenAlex

To better serve society, infrastructure organizations must manage their civil infrastructure systems effectively and efficiently, employing best practices in infrastructure management and relevant information systems. As information systems mature, communications follow a general trend away from informal human-to-human communications towards computer-to-computer information exchange. For efficient implementation of computer-based exchange of information, these communications must be formally described. As part of a larger study into the formalization of communications within the infrastructure industry, this paper examines the level to which work processes and communications are formalized and designed at present within the domain of infrastructure management. The research adopts a maturity model approach. There are many maturity models available in different industries, but their focus is on the maturity of the way work processes and communication are operated and managed, not the way these work processes and communications are formalized and designed. To address the issue, an Infrastructure Management-Process Maturity Model (IM-PMM) is developed to assess the degree to which work processes and communications are formalized within a specific engineering domain, namely infrastructure management. A five-step approach is used to develop the IM-PMM: define the problem, compare existing maturity models, develop the model, apply the model, and evaluate the maturity model. This paper describes the development and application of the Infrastructure Management-Process Maturity Model (IM-PMM) that can benchmark the current level of maturity of work processes and communications in the domain of infrastructure management. The proposed IM-PMM uses a scale of five levels of maturity (stages) and uses three core elements (i.e. process/transaction map definition, actor/role definition, and information definition) to benchmark existing work processes, plus one additional element (message definition) to benchmark existing communications. The proposed model has been applied and tested in the domain of infrastructure management using a structured interview approach. The resulting data show that existing work processes and communications are typically accomplished in an ad hoc manner, emphasizing the need for further improvements in the way that work processes and communications are defined if infrastructure organizations intend to deploy advanced information systems. The proposed IM-PMM would help the transaction development personnel (including transaction analysts, transaction designers, software developers, process modellers, and industry experts) to assess and benchmark the maturity of the work processes and communications in the domain of infrastructure. As part of the evaluation, the proposed IM-PMM is verified through testing and applying it in the domain of infrastructure management; future work will conduct validation through industry expert review.

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.001
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: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.644
Threshold uncertainty score0.981

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0010.002
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.011
GPT teacher head0.208
Teacher spread0.197 · 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