MétaCan
Menu
Back to cohort
Record W81266829

Creating a Process-Centric Organization at FCC: SOA from the Top Down.

2008· article· en· W81266829 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of the Association for Information Systems · 2008
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBusiness Process Modeling and Analysis
Canadian institutionsnot available
Fundersnot available
KeywordsProcess (computing)Process managementBusinessComputer scienceKnowledge managementProgramming language
DOInot available

Abstract

fetched live from OpenAlex

This case study describes how Farm Credit Canada, which provides financial services for Canadian agricultural businesses, is transforming itself into a process-centric organization. To support this transformation, FCC's IT function has restructured from a silo organization, with each silo supporting applications for a particular business function, to a service-centered model, where applications are constructed according to service oriented architecture (SOA) principles. The transformation is described in six steps.In Step 1, the CEO initiated a culture change initiative that underpinned his vision of creating a customer-centric organization. Step 2 focused on what needed to be done to integrate the corporation's processes and systems to enable it to provide a great customer experience. The outcome was two initiatives, one to redesign the corporation's processes, the other to transform the IT function to support enterprise processes and integration.Step 3 was the transformation of the IT organization. First, the newly appointed CIO assessed the current state of the IT organization (and all current IT projects were halted while this was done). He then designed the new structure, moving away from the old application-centered silo approach to an architecture-centric one supported by SOA principles. The move to the new organizational model was accomplished in just 90 days, a timescale that would have been impossible without the full and active support of the CEO.Proof of concept was undertaken in Step 4 by implementing a carefully chosen business process with SOA. But first, FCC had to make a multimillion investment in the foundational technologies. Once implemented, this redesigned process favorably impressed FCC's senior executives and sent front-line satisfaction with IT soaring. The corporation was then well set to move on to Step 5 the detailed redesign of other processes, and working through the governance issues of managing a process-driven IT organization.The benefits to date of transforming the IT function and its technology were articulated in Step 6. The CIO identified six benefits: (1) Improved and more effective communication between the business and IT; (2) Streamlined business processes; (3) Improved scores for IT staff engagement; (4) Reusable IT assets; (5) Support for the long-term vision; and (6) Proven technical viability of the SOA approach. These last two benefits arose directly from the successful proof of concept (implementing the initial business process).The transformation of FCC to a process-centric organization is continuing apace, and is scheduled for completion by the end of 2011.

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.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.582
Threshold uncertainty score0.725

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0000.003
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.203
Teacher spread0.192 · 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