The FBI Sentinel Project

2011 ◽  
Vol 13 (3) ◽  
pp. 84-102
Author(s):  
Leah Olszewski ◽  
Stephen C. Wingreen
Keyword(s):  
Enterprise Architecture ◽  
Service Oriented Architecture ◽  
The United States ◽  
Management Skills ◽  
Federal Bureau Of Investigation ◽  
Case File ◽  
Service Oriented ◽  
Commercial Off The Shelf ◽  
Key Events ◽  
It Personnel

In 2000, the United States Federal Bureau of Investigation (FBI) initiated its Trilogy program in order to upgrade FBI infrastructure technologies, address national security concerns, and provide agents and analysts greater investigative abilities through creation of an FBI-wide network and improved user applications. Lacking an appropriate enterprise architecture foundation, IT expertise, and management skills, the FBI cancelled further development of Trilogy Phase 3, Virtual Case File (VCF), with prime contractor SAIC after numerous delays and increasing costs. The FBI began development of Sentinel in 2006 through Lockheed Martin. Unlike in the case of Trilogy, the FBI decided to implement a service-oriented architecture (SOA) provided in part by commercial-off-the-shelf (COTS) components, clarify contracts and requirements, increase its use of metrics and oversight through the life of the project, and employ IT personnel differently in order to meet Sentinel objectives. Although Lockheed Martin was eventually released from their role in the project due to inadequate performance, the project is still moving forward on account of the use of best practices. The case highlights key events in both VCF and Sentinel development and demonstrates the FBI’s IT transformation over the past four years.

The FBI Sentinel Project

2013 ◽  
pp. 298-322
Author(s):  
Leah Olszewski ◽  
Stephen C. Wingreen
Keyword(s):  
Enterprise Architecture ◽  
Service Oriented Architecture ◽  
The United States ◽  
Management Skills ◽  
Federal Bureau Of Investigation ◽  
Case File ◽  
Service Oriented ◽  
Commercial Off The Shelf ◽  
Key Events ◽  
It Personnel

In 2000, the United States Federal Bureau of Investigation (FBI) initiated its Trilogy program in order to upgrade FBI infrastructure technologies, address national security concerns, and provide agents and analysts greater investigative abilities through creation of an FBI-wide network and improved user applications. Lacking an appropriate enterprise architecture foundation, IT expertise, and management skills, the FBI cancelled further development of Trilogy Phase 3, Virtual Case File (VCF), with prime contractor SAIC after numerous delays and increasing costs. The FBI began development of Sentinel in 2006 through Lockheed Martin. Unlike in the case of Trilogy, the FBI decided to implement a service-oriented architecture (SOA) provided in part by commercial-off-the-shelf (COTS) components, clarify contracts and requirements, increase its use of metrics and oversight through the life of the project, and employ IT personnel differently in order to meet Sentinel objectives. Although Lockheed Martin was eventually released from their role in the project due to inadequate performance, the project is still moving forward on account of the use of best practices. The case highlights key events in both VCF and Sentinel development and demonstrates the FBI’s IT transformation over the past four years.

Towards a Virtual Enterprise Architecture for the Environmental Sector

2008 ◽  
pp. 368-378
Author(s):  
Ioannis N. Athanasiadis
Keyword(s):  
Information Management ◽  
Natural Environment ◽  
Enterprise Architecture ◽  
Service Oriented Architecture ◽  
Virtual Enterprise ◽  
Knowledge Exchange ◽  
Daily Basis ◽  
Environmental Information ◽  
Management Ownership ◽  
Service Oriented

This chapter introduces a Virtual Enterprise architecture for environmental information management, integration and dissemination. On a daily basis, our knowledge related to ecological phenomena, the degradation of the natural environment and the sustainability of human activity impacts, is growing. As a consequence raises the need for effective environmental knowledge exchange and reuse. In this work, a solution among collaborating peers forming a Virtual Enterprise is investigated. Following an analysis of the main stakeholders, a service-oriented architecture is proposed. Technical implementation options, using web-services or software agents, are considered and issues related to environmental information management, ownership and standardization are discussed.

Event-Driven Service-Oriented Architectures for E-Business

2010 ◽  
pp. 952-962
Author(s):  
Olga Levina ◽  
Vladimir Stantchev
Keyword(s):  
Distributed System ◽  
Enterprise Architecture ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Reference Architecture ◽  
Service Oriented Architectures ◽  
Application Systems ◽  
Event Driven ◽  
Service Oriented ◽  
Definition Of

E-Business research and practice can be situated on following multiple levels: applications, technological issues, support and implementation (Ngai and Wat 2002). Here we consider technological components for realizing business processes and discuss their foundation architecture for technological enabling. The article provides an introduction to the terms, techniques and realization issues for eventdriven and service-oriented architectures. We begin with a definition of terms and propose a reference architecture for an event-driven service-oriented architecture (EDSOA). Possible applications in the area of E-Business and solution guidelines are considered in the second part of the article. Service-oriented Architectures (SOA) have gained momentum since their introduction in the last years. Seen as an approach to integrate heterogeneous applications within an enterprise architecture they are also used to design flexible and adaptable business processes. An SOA is designed as a distributed system architecture providing a good integration possibility of already existing application systems. Furthermore, SOA is mostly suitable for complex and large system landscapes.

Convergence of Interoperability of Cloud Computing, Service Oriented Architecture and Enterprise Architecture

2013 ◽  
Vol 4 (1) ◽  
pp. 43-51
Author(s):  
Susan Sutherland
Keyword(s):  
Cloud Computing ◽  
Enterprise Architecture ◽  
Service Oriented Architecture ◽  
Proof Of Concept ◽  
Cloud Computing Service ◽  
Architectural Model ◽  
Service Oriented ◽  
State Of Art ◽  
Dynamic Links

The research identifies the gap that there is a convergence of interoperability of Cloud Computing (CC), Service Oriented Architecture (SOA) and Enterprise Architecture (EA). Furthermore, it outlines the existing non dynamic links between EA and SOA that are currently practiced in the industry and confirmed by scholarly articles; and provides a state of art of the link that could exist in practice between cloud computing and SOA as researched from the published scholarly material. This researched paper also refers to the planned research to test this theory first by developing a logical architectural model of such a feasibility followed by a Proof of Concept

Transitioning Business Processes to a Collaborative Business Environment with Mobility

2009 ◽  
pp. 73-82
Author(s):  
Bhuvan Unhelkar ◽  
Amit Tiwary ◽  
Abbass Ghanbary
Keyword(s):  
Web Services ◽  
Enterprise Architecture ◽  
Business Processes ◽  
Service Oriented Architecture ◽  
Business Environment ◽  
Web Based ◽  
Software Applications ◽  
Comprehensive Service ◽  
Service Oriented ◽  
Web Based System

Web Services (WS) technologies create the potential for an organization to collaborate with partners and customers by enabling its software applications to transact over the Internet. This collaboration is achieved by carefully incorporating Web Services in the organization’s software applications, resulting in comprehensive Service-Oriented Architecture (SOA) for the enterprise. This incorporation of WS-enabled applications and components in the organization’s overall enterprise architecture requires understanding of the service at three interrelated yet distinct layers: policies, activities, and standards. This chapter describes how the existing business processes of an organization are transitioned in to collaborative business processes that would result in a Collaborative Web- Based System (CWBS). The ideas presented in this chapter have been validated through an action-research carried out by the authors in a large energy supplier organization in Melbourne, Australia.

A Comparative Analysis of the Integration of SOA Elements in Widely-Used Enterprise Architecture Frameworks

2013 ◽  
Vol 9 (2) ◽  
pp. 54-70 ◽  
Author(s):  
Ayed Alwadain ◽  
Erwin Fielt ◽  
Axel Korthaus ◽  
Michael Rosemann
Keyword(s):  
Decision Support ◽  
Comparative Analysis ◽  
Enterprise Architecture ◽  
Service Oriented Architecture ◽  
It Alignment ◽  
Architecture Framework ◽  
Service Oriented ◽  
Architecture Frameworks ◽  
Enterprise Architecture Framework ◽  
Over Time

In recent years, enterprise architecture (EA) has captured increasing interest as a means to systematically consolidate and manage various enterprise artefacts in order to provide holistic decision support for business/IT alignment and business/IT landscapes management. To provide a holistic perspective on the enterprise over time, EA frameworks need to co-evolve with the changes in the enterprise and its IT over time. In this paper the authors focus on the emergence of Service-Oriented Architecture (SOA). There is a need to integrate SOA with EA to keep EA relevant and to use EA products to help drive successful SOA. This paper investigates and compares the integration of SOA elements in five widely used EA frameworks: Archimate, The Open Group Architecture Framework (TOGAF), Federal Enterprise Architecture Framework (FEAF), Department of Defence Architecture Framework (DoDAF) and the Ministry of Defence Architecture Framework (MODAF). It identifies what SOA elements are considered and their relative position in the overall structure. The results show that services and related elements are far from being well-integrated constructs in current EA frameworks and that the different EA frameworks integrated SOA elements in substantially different ways. The results can support the academic EA and SOA communities with a closer and more consistent integration of EA and SOA and support practitioners in identifying an EA framework that provides the SOA support that matches their requirements.

Framework of Knowledge and Intelligence Base

Data Mining ◽  
2013 ◽  
pp. 474-502
Author(s):  
Marc Rabaey ◽  
Roger Mercken
Keyword(s):  
Decision Making ◽  
Cloud Computing ◽  
Information System ◽  
Enterprise Architecture ◽  
Service Oriented Architecture ◽  
Naturalistic Decision Making ◽  
Military Organization ◽  
Knowledge Culture ◽  
It Systems ◽  
Service Oriented

This chapter introduces the concept of the “Intelligence Base,” developed in a study on the information requirement of the management of an (military) organization. The purpose of the study was to conceive, for each level of an organization, an appropriate Decision Support System (DSS) and/or Knowledge and Information System. All systems would eventually have been integrated in an overall Enterprise Architecture (EA). By discussing the OODA-cycle of John Boyd and the Naturalistic Decision Making (NDM) the authors show that the concept of Intelligence Base can be a DSS for very demanding environments. Related topics are knowledge, culture, and real options (business example). The proposed framework is based on Service-Oriented Architecture (SOA) and Cloud Computing, which will determine the configuration of the Information Technology (IT) systems.

Towards Whole-of-Government EA with TOGAF and SOA

2012 ◽  
pp. 177-204 ◽  
Author(s):  
Awel S Dico
Keyword(s):  
Enterprise Architecture ◽  
Service Oriented Architecture ◽  
Current State ◽  
Architecture Framework ◽  
Service Oriented ◽  
Technical Factors ◽  
Government Enterprise ◽  
Value Realization ◽  
Strategic Transformation ◽  
Limited Scope

Governments around the world have acknowledged the complexity associated with public sector transformation and have initiated enterprise architecture programs to help manage those complexities and enable the desired strategic transformation. Along with the EA program, governments have adopted some sort of EA framework and/or Service Oriented Architecture (SOA) individually or in integrated form. However, the majority of those EA programs are of limited scope in both EA and SOA practices, and are not comprehensive enough to deal with and manage the associated complexities. As a result, those EA programs suffer from the inability to leverage EA and SOA benefits across agencies or jurisdictional boundaries. Currently, the majority of government agencies use EA and SOA within the agency boundaries to deliver solutions by focusing on technical factors that define detailed blueprints of systems, data, and technology. What is needed rather is effective Whole-of-Government Enterprise Architecture (EA) that facilitates the alignment of individual agencies’ visions with the Whole-of-Government vision to enable sustainable government transformation. Research has pointed out that the Whole-of-Government EA is currently at the conceptual level and still has a long way to go to reach the maturity level required for value realization. This chapter first gives a brief analysis of the current state of enterprise architecture in governments to highlight the current challenges. It then discusses the various scopes of Whole-of-Government EA and recommends the plausible EA approach to enable sustainable connected government based on The Open Group Architecture Framework (TOGAF) and SOA.

Sign in / Sign up

Export Citation Format

Share Document