Creating a Process-Centric Organization at FCC: SOA from the Top Down.
Bibliographic record
Abstract
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.012 | 0.006 |
| Scholarly communication | 0.007 | 0.004 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".