TAFIM

<h2 id="overview">Overview</h2>
The "Technical Architecture Framework for Information Management" (TAFIM) was described in 1995 as:<a class="footnote-ref" id="fnref:2" href="#fn:2">2</a>

<ul><li>a target common conceptual framework or <a href="/facts/Reference_model/TppYy4G8">reference model</a> for an information system infrastructure</li>
<li>and the specific applications that the information system must support.</li></ul>
This architecture, and associated model, is not a specific <a href="/facts/System_design/hFWYoaNP">system design</a>. Rather, it establishes a common vocabulary and defines a set of services and interfaces common to information systems. It identifies <a href="/facts/Technical_standard/P4orT1SM">standards</a> and guidelines in terms of the architecture services and interfaces.
The architecture serves to facilitate the development of plans that will lead to <a href="/facts/Interoperability/7WgqUbXU">interoperability</a> between mission area applications, portability across mission areas and cost reductions through the use of common services.<a class="footnote-ref" id="fnref:3" href="#fn:3">3</a>
TAFIM subsumes the widely accepted <a href="/facts/Open-system_environment_reference_model/a9fIS5ez">Open-system environment reference model</a> within the network services and communications area.

<h2 id="history">History</h2>

The development of TAFIM started around 1986 at the US Defense Information Systems Agency/Center for Information Management. The first concept of TAFIM was derived from the <a href="/facts/National_Institute_of_Standards_and_Technology/gr9Fnh85">NIST</a> <a href="/facts/Application_Portability_Profile/vrlXy1QN">Application Portability Profile</a> and the <a href="/facts/POSIX/mQkSt234">POSIX</a> (or <a href="/facts/IEEE/UddC4pUW">IEEE</a> P1003.00SE) model.<a class="footnote-ref" id="fnref:4" href="#fn:4">4</a>
The first draft of TAFIM was completed in 1991 with the TAFIM Technical Reference Model (TAFIM TRM). Developed by a team led by Burnes St. Patrick Hollyman, James M. Kerr and John Keane, this technical reference model wanted to use <a href="/facts/Open_system_(computing)/tVwr9W6r">open systems</a> and new technologies available in the commercial market, to develop a <a href="/facts/United_States_Department_of_Defense/dWAvf7e3">DoD</a>-wide application.<a class="footnote-ref" id="fnref:5" href="#fn:5">5</a> The TAFIM project has resulted in an eight-volume <a href="/facts/Information_Technology/glMzunwe">Information Technology</a> <a href="/facts/Enterprise_architecture/7UNSuE0l">Architecture</a> "how-to" <a href="/facts/User_guide/sb0Crduq">manual</a>, see image. Before being officially published in 1996 by the Department of Defense, the approach was successfully piloted at both the U.S. Marine Corps and the DoD Health Affairs by teams led by Hollyman, Kerr, Keane.
The original development of <a href="/facts/TOGAF/G8qggAIa">TOGAF</a> Version 1 in 1995 was based on the Technical Architecture Framework for Information Management. The US Department of Defense gave <a href="/facts/The_Open_Group/uRoDdEae">The Open Group</a> explicit permission and encouragement to create TOGAF by building on the TAFIM, which itself was the result of many years of development effort and many millions of dollars of US Government investment.<a class="footnote-ref" id="fnref:6" href="#fn:6">6</a>
The 1996 US DoD publication on TAFIM was the latest version published.<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a> TAFIM has been cancelled as a stand-alone document in 1999.<a class="footnote-ref" id="fnref:8" href="#fn:8">8</a> In 2000 the whole TAFIM concept and its regulations have been re-evaluated and found inconsistent with the newly developed <a href="/facts/DoDAF/fjB2hV0z">DoDAF</a> architecture direction. For this reason all references to TAFIM have been removed from DoD documentation since then.<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a>
TAFIM was abruptly cancelled due to the following flaws:<a class="footnote-ref" id="fnref:10" href="#fn:10">10</a>

<ul><li>TAFIM required a large investment of both time and money</li>
<li>The elapsed time required to produce the architecture makes it close to obsolete before completion</li>
<li>Architectures of such complexity required specialized and reasonably uncommon IT expertise to complete. The end result is normally incomprehensible to a business-oriented audience and is harder to trace to the business strategy</li></ul>
That said, many of the core contributions to IT architectural thinking introduced within the TAFIM effort were retained and built upon through DoDAF, including TAFIM’s central concept of four interdependent architectural views. This concept, in fact, lives on in most modern discussions of IT architectures to this day.

<h2 id="tafim-topics">TAFIM topics</h2>
<h3>DoD technical and data standards</h3>
Defense’s technical and data standards are designed to enable systems to easily interoperate and transfer information. Its standard definitions for data elements are intended to ensure that users of all Defense systems define the same data in the same way and have a common understanding of their meaning. Defense has developed or is in the process of defining technical standards in the 1990s with the Technical Architecture Framework for Information Management (TAFIM), the Joint Technical Architecture (JTA), and the Defense Information Infrastructure Common Operating Environment (DII COE).<a class="footnote-ref" id="fnref:11" href="#fn:11">11</a>
The Defense Information Systems Agency (DISA) is responsible for developing, obtaining from commercial sources, and maintaining the compilation of Defense Information Infrastructure technical standards, and it is responsible for maintaining a Defense data dictionary system as a repository of data requirements and for facilitating the cross-functional coordination and approval of standard formats, definitions, etc. PSAs, the military services, Defense agencies, and Joint Chiefs of Staff are responsible for reaching agreement on the standards and approving them as DOD standard data elements. DISA is then responsible for disseminating the approved standard data elements for use throughout the Department.<a class="footnote-ref" id="fnref:12" href="#fn:12">12</a>

<h3>DoD Standards-Based Architecture Planning Process</h3>

The Standards-Based Architecture (SBA) planning process. defined by the TAFIM, consists of seven distinct, but interdependent, phases. Each phase of the SBA process is intended to create specific deliverable products and or documents, that guide the subsequent phase. The seven phases are briefly outlined below.<a class="footnote-ref" id="fnref:13" href="#fn:13">13</a>

<ul><li>Phase 1, Initiation and Architecture Framework : The methodology begins with a proper initiation of the process within the host organization. This involves developing a set of strategic drivers for the organization. Further, a business model is reviewed or built to establish a strategic target operation model.<a class="footnote-ref" id="fnref:14" href="#fn:14">14</a></li>
<li>Phase 2. Baseline Characterization : This grounding phase intends to determine the organization's current architecture. It is an assessment of the current environment, which results in a characterization in four key dimensions or views: work, information, application and technology.<a class="footnote-ref" id="fnref:15" href="#fn:15">15</a></li>
<li>Phase 3. Target Architecture : The various views of the framework are modeled in terms of a desirable target architecture, usually 3 to 5 years in the future.<a class="footnote-ref" id="fnref:16" href="#fn:16">16</a></li>
<li>Phase 4. Opportunity Identification : Step from the conceptual reflection to practical realities and implementation, with determination of development projects needed.<a class="footnote-ref" id="fnref:17" href="#fn:17">17</a></li>
<li>Phase 5. Migration Options : Links the reality of the present with the desirability of the target architecture by establishing one or more plateaus representing practical migration stages.<a class="footnote-ref" id="fnref:18" href="#fn:18">18</a></li>
<li>Phase 6. Implementation Planning : Phase results in a detailed implementation plan for the first plateau of the migration effort.<a class="footnote-ref" id="fnref:19" href="#fn:19">19</a></li>
<li>Phase 7. Institutionalizing the <a href="/facts/Information_Technology_Architecture/A6k3coAm">ITA</a> Process : This phase is intended to keep the architecture alive and well by continuously improving it.<a class="footnote-ref" id="fnref:20" href="#fn:20">20</a></li></ul>
<h3>Integrated Model of Architectural Views</h3>

The "Integrated Model of Four Architectural Views" is part of the target architecture, defined in the TAFIM. It gives a vision on the organization in all of its architectural views, especially the work architecture. The model, see figure, depicts an overall framework to develop the target architecture deliverable. Each view of the target architecture has some overlap with aspects of the other views. This overlap supports the argument that the model depicts the developing of a single, integrated architecture.<a class="footnote-ref" id="fnref:21" href="#fn:21">21</a>
The entire enterprise, as defined, includes Work organization, Information, Application, and Technology. This leads to the four different views:<a class="footnote-ref" id="fnref:22" href="#fn:22">22</a>

<ul><li>Work Organization View : The work view of architecture is developed by identifying specific classes of users within the business environment (e.g. executives, planners, administrators, engineers, recruiters), business location (e.g. headquarters, sales office, plant, warehouse); and the logical representation of the business functions that are required to deliver products and services.</li>
<li>Information Management View  : The information architecture of the enterprise will contain three levels of detail, subject areas, data groups, and data attributes.</li>
<li>Application View  : This view focuses on the opportunities to autonomate aspects of work and or the access to information needed to perform work.</li>
<li>Technology Infrastructure View : This areas of architecture uses specific component-level models to provide the basic for linking the technology view of the architecture to the work, information, and application views. The linchpin is the generic application environment.</li></ul>

This gallery with the four views shows the interrelationship between the four views as mentioned earlier. In the view models of later <a href="/facts/Enterprise_Architecture_framework/kq1FCjjT">Enterprise Architecture frameworks</a>, such as the <a href="/facts/DoDAF/fjB2hV0z">DoDAF</a> the views are presented in layers and no longer interconnected.

<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Enterprise_Architecture_framework/kq1FCjjT">Enterprise Architecture framework</a></li>
<li><a href="/facts/Enterprise_Architecture_Planning/JSWwt7bM">Enterprise Architecture Planning</a></li>
<li><a href="/facts/GERAM/0h8fS6qT">GERAM</a></li>
<li><a href="/facts/Open_System_Environment_Reference_Model/a9fIS5ez">Open System Environment Reference Model</a></li>
<li><a href="/facts/Treasury_Information_System_Architecture_Framework/NJYt1cMc">Treasury Information System Architecture Framework</a></li>
<li><a href="/facts/Treasury_Enterprise_Architecture_Framework/rzU0jdU1">Treasury Enterprise Architecture Framework</a></li>
<li><a href="/facts/TOGAF/G8qggAIa">TOGAF</a></li>
<li><a href="/facts/Technical_architecture/A6k3coAm">Technical architecture</a></li></ul>

Wikimedia Commons has media related to TAFIM.

This article incorporates <a href="/facts/Copyright_status_of_works_by_the_federal_government_of_the_United_States/Q1jvr96g">public domain material</a> from websites or documents of the <a href="/facts/United_States_Army/WACWBEK9">United States Army</a>.

<h2 id="external-links">External links</h2>
<ul><li><a href="https://web.archive.org/web/19970526140125/http://www-library.itsi.disa.mil/tafim/tafim3.0/pages/tafim.htm">TAFIM website, 1997</a> at archive.org</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">NHSITRC (2005). Consolidated References Archived 2009-01-09 at the Wayback Machine IT Planning and Management Guides, List of Resources. Last Updated: May 4, 2005. Accessed 12 Dec 2008. <a href="https://www.acf.hhs.gov/nhsitrc/it_planning/consolidated_definitions/consol_ref.html" target="_blank">https://www.acf.hhs.gov/nhsitrc/it_planning/consolidated_definitions/consol_ref.html</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">Constance Golden (1995). A STANDARD SATELLITE CONTROL REFERENCE MODEL. NASA. <a href="https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19950011177_1995111177.pdf" target="_blank">https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19950011177_1995111177.pdf</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">Constance Golden (1995). A STANDARD SATELLITE CONTROL REFERENCE MODEL. NASA. <a href="https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19950011177_1995111177.pdf" target="_blank">https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19950011177_1995111177.pdf</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">Constance Golden (1995). A STANDARD SATELLITE CONTROL REFERENCE MODEL. NASA. <a href="https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19950011177_1995111177.pdf" target="_blank">https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19950011177_1995111177.pdf</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">Patricia A. Oberndorf and Anthony Earl (1998). Department of Veterans Affairs Reference Models[permanent dead link‍]. SEI Carnegie Mellon University. <a href="http://www.va.gov/oirm/architecture/ita/seireport.doc" target="_blank">http://www.va.gov/oirm/architecture/ita/seireport.doc</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">Welcome to TOGAF Version 9 -- The Open Group Architecture Framework Accessed 03 Feb 2009. <a href="http://www.opengroup.org/architecture/togaf9-doc/arch/" target="_blank">http://www.opengroup.org/architecture/togaf9-doc/arch/</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">Jaap Schekkerman (2003). How to Survive in the Jungle of Enterprise Architecture Frameworks. p.173. <a href="/wiki/Jaap_Schekkerman" target="_blank">/wiki/Jaap_Schekkerman</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">NHSITRC (2005). Consolidated References Archived 2009-01-09 at the Wayback Machine IT Planning and Management Guides, List of Resources. Last Updated: May 4, 2005. Accessed 12 Dec 2008. <a href="https://www.acf.hhs.gov/nhsitrc/it_planning/consolidated_definitions/consol_ref.html" target="_blank">https://www.acf.hhs.gov/nhsitrc/it_planning/consolidated_definitions/consol_ref.html</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">Jaap Schekkerman (2003). How to Survive in the Jungle of Enterprise Architecture Frameworks. p.173. <a href="/wiki/Jaap_Schekkerman" target="_blank">/wiki/Jaap_Schekkerman</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">Perks, C., and Beveridge, T. (2003). Guide to Enterprise IT Architecture. New York, NY: Springer. <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">GAO (1998) DEFENSE IRM United States General Accounting Office. <a href="http://www.gao.gov/archive/1998/ai98005.pdf" target="_blank">http://www.gao.gov/archive/1998/ai98005.pdf</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">GAO (1998) DEFENSE IRM United States General Accounting Office. <a href="http://www.gao.gov/archive/1998/ai98005.pdf" target="_blank">http://www.gao.gov/archive/1998/ai98005.pdf</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996 <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996 <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996 <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996 <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996 <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996 <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996 <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996 <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996 <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">Department of Defense (1996). Technical Architecture Framework for Information Management. Vol. 4. April 1996 <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
</ol>

TAFIM open-in-new

TAFIM