A History of Computing, Informatics, and Public Information Systems in Türkiye: From IBM 650 to KaraNET, PolNet, and e-Government

The history of computing and informatics in Türkiye spans successive developments in mechanized data processing, electronic computing, scientific computing, computer engineering education, academic networks, closed institutional networks, the Internet, and integrated public information systems. The first use of punched-card systems, electronic computers, international academic links, permanent Internet connectivity, and web servers occurred at different stages.

The institutional development of computing in Türkiye spans public institutions, universities, security and defense infrastructures, and national information systems. Academic studies, graduate theses, records of the Grand National Assembly of Türkiye (TBMM), and institutional histories document different stages of this development. Academic sources record KaraNET as an operational environment for web-based institutional applications by 2003; the institutional records consulted do not specify an exact commissioning date [3], [4].

Data Processing Before Electronic Computers

Information processing in Türkiye predates electronic computers. A 1984 TBMM publication titled Kamu Kurumlarında Bilgisayar Kullanımı (“Computer Use in Public Institutions”) states that mechanization of information processing began in 1934 at T.C. Ziraat Bankası with office machines based on punched-card systems [5].

Punched-card equipment mechanized institutional tasks such as recording, sorting, classifying, counting, and tabulating data. It represented a different technical stage from later electronic general-purpose computers. Public-sector computing nevertheless addressed the same practical need: processing large volumes of institutional data reliably, repeatably, and faster than manual methods allowed.

1960: The First Electronic Computer Used in Türkiye

The General Directorate of Highways (Karayolları Genel Müdürlüğü, KGM) explicitly records that computer use in Türkiye began with the IBM 650 Data Processing Machine, which entered service at KGM in 1960 [6]. KGM’s historical record states that the system was ordered in August 1959 and brought to Türkiye on 30 September 1960 after approximately a year of production [6].

The IBM 650 was a first-generation vacuum-tube computer with magnetic-drum memory. According to KGM, it had a 2,000-word drum memory, accepted data through punched cards, and could perform roughly 78,000 additions/subtractions and 5,000 multiplications per minute [6].

The operational context matters as much as the hardware. Electronic computing in Türkiye did not begin with personal use or office productivity. It was introduced to solve engineering, road infrastructure, planning, inventory, and public-administration problems. From the outset, therefore, the computer entered Turkish institutional life as an engineering instrument for increasing the computational capacity of the public sector.

1964: Scientific Computing in Universities

The establishment of the Institute of Electronic Computing Sciences at Istanbul Technical University (İTÜ) and the commissioning of an IBM 1620 were major milestones in the institutionalization of scientific computing. İTÜ’s historical sources describe the IBM 1620 as the first computing system in Türkiye capable of scientific calculation [7].

The METU Computer Center was established in 1964. In later decades, METU’s computing organization became important not only for user services but also for computer-science education, networking, and the introduction of the Internet in Türkiye [9], [12].

This period marks a transition from simply “operating a machine” toward a broader discipline. Scientific computing combined mathematical modeling, algorithm design, programming, data preparation, and validation of results. From the perspective of today’s Introduction to Computer Engineering, this was the period in which the relationship between hardware and algorithms began to become institutionalized academically.

The Word “Bilgisayar” and the Institutionalization of the Profession

According to Prof. Dr. Aydın Köksal’s first-person historical account, the Turkish word bilgisayar was first used in official correspondence on behalf of Hacettepe University in 1969. Köksal identifies the announcement “Hacettepe Üniversitesi’ne bir Bilgisayar Sistemi kiralanacaktır” as an early institutional use of the term [10].

Hacettepe University’s Department of Computer Engineering states that it was founded in 1971 under the Hacettepe Institute of Informatics and that in 1977 it became one of the first two departments in Türkiye to offer an undergraduate program in Computer Engineering [8]. METU traces the foundations of its department to a service department established in 1967 to teach computer science to other academic units; in 1977 it became the Department of Computer Engineering within the Faculty of Engineering [9].

Köksal’s account states that the first doctoral program in Computer Science Engineering at Hacettepe was defined in 1973, its first eight doctoral students began study in September 1974, and both Hacettepe and METU began admitting undergraduate students in 1977 [10].

It is therefore more accurate to distinguish the different layers of institutionalization rather than assign a single date to “the first Computer Engineering department in Türkiye”:

• 1960s: computer centers and scientific computing,
• 1967-1971: academic organization of computer science,
• 1973-1974: beginning of doctoral education in Türkiye,
• 1977: beginning of undergraduate Computer Engineering education at Hacettepe and METU.

From University Computing Centers to Computer Engineering Degrees

The 2013 study by Kuşcu, Çetiner, and Gökmen connects the emergence of computer engineering in Türkiye with university electronic computing centers [26]. It records the establishment of an Electronic Computing Sciences unit at METU in 1967, postgraduate education beginning in 1971–1972, and the computer engineering undergraduate program opening in 1977–1978. The authors report a first METU graduating cohort of 16 computer engineers in 1981 [26]. The figure refers to METU’s first Computer Engineering graduating cohort in 1981.

The same research describes Hacettepe's Informatics Institute foundation in 1971 and undergraduate education beginning in 1977, Ege University's 1970 computing center, and computer engineering at ITU emerging from electrical, electronic, and control engineering [26]. The distinction matters: a computing center provides services; an academic department organizes teaching and research; an undergraduate degree certifies a defined engineering curriculum. Their start dates need not coincide.

The study's 1982–2011 graduation figures are useful as historical evidence of educational expansion, but are not current enrollment or staffing statistics. The wider educational and technical context is developed in History of Engineering in Türkiye.

1986: International Academic Networking Before the Internet

Türkiye’s participation in international computer networks began before its permanent Internet connection. According to Ege University’s institutional Book of Firsts, Ege University connected to EARN on 21 November 1986, and other Turkish universities initially accessed that academic network through Ege University [11].

EARN/BITNET was a separate academic networking ecosystem serving the communication requirements of its time. Türkiye established permanent TCP/IP-based Internet connectivity through METU in 1993.

The distinction is important from a Computer Networks perspective: participation in an international computer network does not necessarily mean participation in the Internet. Protocol families, inter-network routing models, and application services can be fundamentally different.

1990-1993: .tr, Experimental Internet, and the Permanent Link

IANA records show 17 September 1990 as the registration date of Türkiye’s country-code top-level domain, .tr [13]. The domain-name layer is separate from the physical connection but is essential for the institutional scalability of Internet services.

According to METU Computer Center history, METU established an experimental Internet connection to the Netherlands via X.25 in 1992. In April 1993, a 64 Kbps leased line connected METU in Ankara to NSFNET in Washington; METU’s English history states that this connection served the country [12].

The early network history of Türkiye is therefore best read as three different stages:

1. 1986: EARN/BITNET academic networking [11],
2. 1992: experimental Internet access via X.25 [12],
3. 1993: permanent 64 Kbps connectivity to NSFNET [12].

For the global historical context of ARPANET, packet switching, and the transition to TCP/IP, see the ARPANET article.

The First Web Server and Website in Türkiye

The Internet and the World Wide Web are not the same technology. The Internet is an internetworking infrastructure; the Web is an application layer built on technologies such as HTTP, URLs, and HTML.

METU’s Computer Center lists the **first web server and first website operating under the .tr domain** among its pioneering achievements and attributes it to the METU Computer Center [14]. Historical METU records refer to this service as METU-CWIS [12], [14].

Consequently, “Türkiye connected to the Internet in 1993” and “the first web server in Türkiye became operational” should not be collapsed into one event. The former concerns network connectivity; the latter concerns deploying an HTTP/Web service on top of that connectivity.

1996-1997: ULAKBİM and ULAKNET

TÜBİTAK ULAKBİM officially began operations on 1 June 1996. Its institutional history states that ULAKNET was launched in 1997 as a national academic network using a 34 Mbps ATM-based backbone connecting universities and research institutions [15].

This development represented a move from university-specific gateways and links to a national academic-network architecture. In the same period, METU’s IBM SP2 became the first system from Türkiye to enter the TOP500 list, at rank 376, illustrating the parallel development of networking and high-performance computing capacity [12].

Public-Sector Networking: The Communications Master Plan, TUENA, and KamuNet

The PolNet thesis supplied for this study associates the systematic use of ICT in Turkish public administration during the 1980s with the 1983-1993 Communications Master Plan [1]. It describes digital communications from 1983 onward as a matter of national development, security, defense, and international relations, and explains how Internet access, TUENA, ULAKBİM, and KamuNet became part of the shared public-sector ICT agenda during the 1990s [1].

Decisions of the Supreme Council for Science and Technology in 1997 included the National Information Infrastructure Master Plan (TUENA), ULAKBİM, and electronic-commerce networking. KamuNet, in turn, was conceived as an “information highway” in which public institutions would interconnect internally and with one another through network technologies [1]. The Kamu Net Supreme Board and Technical Board established through Prime Ministry Circular 1998/13 were institutional expressions of this coordination effort [1].

At this stage the central question was no longer “does the institution own a computer?” The engineering problem had become:

how to interconnect geographically distributed public units, decide where authoritative data should reside, manage identity and authorization, reduce duplicate data and software, and move inter-agency workflows into electronic form.

Computing in the Turkish Armed Forces: From Communications to Information Systems

Military computing differs from ordinary public-sector automation because communications, security, resilience, authorization, and command-and-control requirements are integral to the problem. Strategic communications, tactical communications, local-area networking, and institutional intranets developed as distinct architectural layers.

The MEBS Tradition

According to the official history of the Turkish Land Forces, today’s Communications, Electronics and Information Systems School and Training Center (MEBS) traces its roots to the Fen Tatbikat Okulu established on 1 September 1926. It became the Communications School Command in 1948, the Communications School and Training Center Command in 1961, and in 1994 took the name Communications, Electronics and Information Systems School and Training Center [16].

The appearance of “Information Systems” in the institutional title in 1994 is a visible historical indicator of the integration of data and information systems into the military communications discipline.

KaraNET and TSKNET

Open sources contain many secondary accounts of KaraNET, but the academically documented evidence is more limited and therefore more valuable.

Şenol Çakır’s 2003 master’s thesis in Defense Technologies at İTÜ explicitly states that the web-based expert system developed in the study would operate on the “K.K.K. closed area network (KaraNet)” [3]. The thesis describes an institutional application using electronic forms, a browser-based interface, and a database. This directly demonstrates that, by 2003 at the latest, KaraNET was not merely a physical communications connection; it was an intranet environment capable of hosting web-based institutional applications [3].

Cem Çerkezoğlu’s 2006 Sakarya University master’s thesis states that distance education in the Turkish Land Forces was distributed through the “TSKNET-KaraNET” private internal network [4]. This provides further academic evidence that the network supported organizational training and information services in addition to basic communications.

Şenol Çakır’s 2003 master’s thesis documents KaraNET being used for web-based institutional applications in the Turkish Land Forces by that year [3]. The public institutional records consulted do not specify its exact foundation or commissioning date.

The 2003 thesis describes KaraNET as the closed network of the Turkish Land Forces Command (K.K.K. kapalı alan ağı). TSKNET appears with KaraNET in a 2006 academic study of distance education within the Turkish Armed Forces. Their names are retained as historical Turkish network designations because the publicly available primary technical sources reviewed do not establish a single officially approved expansion in English. [3, 4]

A closed institutional network involves more than limiting Internet connectivity. Identity management, addressing, name resolution, application servers, access policy, and service maintenance are part of its operation. The web-based expert system and distance-learning applications described in the theses show that KaraNET supported multiple institutional services; those records do not establish the network's present-day topology. [3, 4]

TAFICS: Strategic Communications

TAFICS is not the same system as KaraNET. TÜBİTAK BİLGEM’s institutional chronology records that the TAFICS Crypto System Development Project was signed with the Ministry of National Defense on 7 March 1997 [17].

Historically, TAFICS belongs to the strategic communications layer, whereas KaraNET is documented in the context of closed institutional information and intranet services.

TAFICS is identified as the Turkish Armed Forces Integrated Communications System, translated into Turkish as Türk Silahlı Kuvvetleri Entegre Muhabere Sistemi. The Turkish Armed Forces Foundation describes it as an integrated strategic communications infrastructure linking force elements and command levels. An ASELSAN brochure also uses the singular Integrated Communication System; both variants designate the same TAFICS system in the respective official publications. [30, 32]

TÜBİTAK BİLGEM's record of a cryptographic system development project in 1997 documents a dated security-related component of the broader TAFICS program. Identifying TAFICS as a strategic communications layer does not establish its current physical topology, carrier technology, or deployed cryptographic mechanisms. Public documentation supports its historical functions in secure voice/data transport, interconnection, and communications service continuity. [17, 30]

TASMUS: Tactical Area Communications

An ASELSAN technical historical publication states that first-generation TASMUS work began during the 1990s, that the first contract was signed in 1996, and that deliveries began in 2000 and continued in phases until 2005 [18].

TASMUS responds to the requirement for fast and reliable digital data communication among sensors, command centers, computers, and other elements in the tactical area. It should therefore not be treated as the same architectural layer as strategic TAFICS.

TASMUS is Taktik Saha Muhabere Sistemi in Turkish, rendered by ASELSAN as Tactical Area Communication System. The Turkish Armed Forces Foundation describes a tactical system intended to transmit voice, data, and images between deployed units and command elements. Whereas TAFICS provides a strategic communications function, TASMUS addresses communications within tactical deployments. [18, 31, 33]

Mobility, constrained links, and changing deployment conditions make tactical communications an engineering problem involving network planning, traffic priorities, and service continuity. Command-and-control application requirements and interfaces with strategic communications must be assessed as separate functions. Public ASELSAN material distinguishes TASMUS at the tactical layer from TAFICS at the strategic layer. [31, 32]

TAYAS: The Tactical Local Area Network Layer

ASELSAN’s 2019 Annual Report describes TAYAS as a system developed to meet the wired and wireless local-area-network requirements of the Turkish Land Forces in the tactical field. According to the report, TAYAS forms the local networking layer that connects battlefield command-control and information systems with strategic-level TAFICS, tactical-level TASMUS, and satellite systems [19].

On the basis of public historical sources, the architectural distinction can be summarized as follows:

• KaraNET / TSKNET: closed institutional information and intranet services [3], [4],
• TAFICS: strategic communications [17],
• TASMUS: tactical area communications [18],
• TAYAS: tactical local-area networking and connectivity for command-control information systems [19].

The categories distinguish the historically documented roles of strategic communications, tactical communications, local networks, and institutional intranets.

TAYAS stands for Taktik Yerel Alan Ağı Sistemi in Turkish and is identified by ASELSAN as the Tactical Local Area Network System. Its documented components include the TAYAS Server Set (TSS) and TAYAS Network Access Sets (TNAS), which connect command locations and users through wired or wireless local links. [19, 32]

ASELSAN lists Ethernet switches, routers, servers, firewall/intrusion-prevention devices, and wireless access components in the TAYAS architecture. The local network can reach external communications infrastructure through strategic TAFICS links, tactical TASMUS links, or satellite systems where supported. TAYAS is therefore the local access layer; TASMUS addresses tactical-area communications; TAFICS addresses strategic communications. [32]

Computerization of the Turkish National Police

Bekir Enes Arı’s 2014 master’s thesis divides the digital and e-government transformation of the Turkish National Police into three periods [1]:

1. Establishment and Data Processing System Period (1981-1989)
2. Police Computer Network Project Period (1989-1995)
3. Restructuring and PolNet Period (1996-2000)

This periodization closely matches the general architectural evolution of public-sector computing: centralized data processing first, geographically distributed networking next, and then shared databases with integrated applications.

1977: Testimony About Early Computerization Advisory Work

Burak Çakırca's 2009 master's thesis states that Adnan Kahveci, who had an electronics engineering background, took part in early efforts to introduce computing into the Interior Ministry and the Turkish National Police while serving in a technical advisory role in 1977 [27]. The passage is attributed in a footnote to an interview with Vahit Erdem. Kadir Sancak's biographical study describes Kahveci's electronics education at Purdue, medical engineering graduate studies at Missouri, and subsequent academic career [28]. Because that study draws on some of the same secondary works, it is not independent verification of a specific deployed computer system.

Burak Çakırca’s thesis, citing an interview with Vahit Erdem, records Adnan Kahveci’s participation in computerization-related technical consultancy for the Ministry of Interior and the General Directorate of Security in 1977 [27]. The General Directorate’s institutional history dates the Information Processing Center’s operation to 1981 [1]. These records describe different stages of technical consultancy and institutional data-processing capacity.

This distinction improves the historical framework: technical advisory preparation, an operational data-processing center, a distributed computing network, and an integrated application ecosystem are not interchangeable milestones. The educational and professional background is examined separately in History of Engineering in Türkiye.

1981-1989: The Information Processing Center and Early Systems

According to the thesis, the Information Processing Center under the EGM Research and Planning Coordination Department began operations in 1981 and became the Information Processing Department in 1982 [1]. Its stated purpose included providing computer support to police services, improving speed and reliability, establishing computer connections with domestic and foreign institutions, and allowing police personnel to access required information from different parts of Türkiye [1].

From 1983, XL-40 systems were used for data entry at headquarters, followed by Pertec 3200 systems. Unisys A3 systems were used in provincial organizations, and A4, A6, and A17 systems were introduced from 1988. The thesis reports that online operations began at provincial centers and border gates and that the architecture later migrated from the A-series toward PC-based systems [1].

The same thesis states that METU analyzed the Police organization’s computer requirements between 1987 and 1989, that the work was put into implementation by the State Planning Organization in 1990, and that installation continued until 1996 [1]. This is an early example of large-scale cooperation between a public institution and a university.

1989-1995: The Police Computer Network

During the second period a central system was acquired for a national police network, while regional information systems and systems at border gates were interconnected. Personnel-database queries, access to data from remote units, and statistical processing became possible, although a fully shared nationwide data pool had not yet been achieved [1].

The dominant architectural problem had shifted from computing capacity to distributed access and data integration.

1996-2000: PolNet 2000, Transpol, and PolNet

The thesis describes 1996-2000 as a restructuring period in which shared databases and the exchange of photographs, audio, and video became relevant requirements. The PolNet 2000 project, described as a “Police Information System and Computer Network,” was presented at the KamuNet 98 event in 1998 [1].

In 1999 the architecture was separated into two complementary layers:

• Transpol: communications/network infrastructure,
• PolNet: the police information system operating on top of that infrastructure.

The thesis describes Transpol as the infrastructure intended to consolidate multiple communications networks onto a common network base, while PolNet provided information and application services on top of it [1]. İlker Pekgözlü’s academic study of PolNet likewise treats it as one of Türkiye’s early public-sector IT projects and analyzes its project-management dimension using documents and interviews with experts who worked on the project [2].

In the official terminology of the Turkish National Police, POL-NET is Polis Bilişim Ağı (Police Information Network). The 2018 institutional report defines it as an information system supporting police operations through shared data, automation, and nationwide connectivity. The historical PolNet 2000 project must be distinguished from the subsequent institutional system and its expanded service scope. [1, 34]

In Arı's historical account, Transpol refers to the communications transport infrastructure, while PolNet describes the information services and applications built above that infrastructure. No officially verified long English form of Transpol has been established in the consulted sources, so the original project name is retained. This separation between transport and information services is important for explaining changes in network technology without confusing them with the evolution of data and business workflows. [1]

PolNet as a System Ecosystem, Not a Single Application

The historical 2014 view in Arı’s thesis lists many systems within or connected to PolNet, including the Police Information System, Personnel Information System, Electronic Document Management System, Document Archive Management System, EKİP, the Identity Sharing System, MOBESE, Traffic Information System, AFIS, KPL-NET, ASBİS, and e-Passport [1].

It is therefore insufficient to describe PolNet as merely a web application or database. Historically, it is better understood as an enterprise information-system ecosystem combining:

communications network + shared data + institutional applications + authorization + workflow.

KPS is Kimlik Paylaşımı Sistemi (Identity Sharing System), the authorized online exchange service for population data held in MERNİS. EBYS is Elektronik Belge Yönetim Sistemi (Electronic Document Management System); KGYS is Kent Güvenlik Yönetim Sistemi (Urban Security Management System); AFIS is the widely used abbreviation for Automated Fingerprint Identification System. MOBESE is discussed in its historical context alongside later KGYS systems, without treating every project name across different periods as identical. [1, 34, 35]

The architectural challenge is the participation of multiple data owners and user groups in shared institutional workflows. Identity queries, consistent records, traceable document operations, and authorization boundaries belong to different service responsibilities. Inclusion in an inventory of POL-NET applications does not imply that all data reside in one physical database or that all applications have identical access rights. [1, 34]

Before and After PolNet: Changes in Processing Time

A comparison table in Arı’s thesis, derived from interviews with specialist personnel, reports that person queries fell from 45 minutes to 5 seconds, vehicle queries from 30-40 minutes to 5 seconds, document queries from 15-20 days to 1 minute, and annual statistics preparation from 10-20 days to 1.5-2 hours [1].

These figures must be interpreted correctly. They are not centralized telemetry measurements; the thesis explicitly states that they are historical-operational comparisons obtained through interviews with specialist personnel in the relevant EGM units [1]. Even with that methodological limitation, they demonstrate the nature of the transformation.

The largest gain did not come merely from faster processors. Replacing a workflow such as:

local unit → written request/fax → central unit → central query → response → local unit

with direct authorized electronic query and shared data access represents a redesign of the business process itself.

Real-Time Public Information Systems in Electricity Transmission

Computerization of electricity transmission developed alongside transaction-oriented public computing, but addressed a different requirement: continuous observation and supervision of a physical network. The chapter on the National Dispatch SCADA/EMS System by Bahadır Uçan in TESAB's 2023 electrical history traces dispatch operations from an early 1956 center in Adapazarı to national and regional control facilities [29]. It describes the 1984 project contract, later upgrades, expansion, and remote-terminal integration as historical stages. Those dates describe the reporting period of the publication.

SCADA, Remote Terminal Units, and Energy Management

SCADA supports the acquisition of field observations and equipment status, alarms, and authorized supervisory control. An RTU collects and communicates remote measurements and state indications. An EMS supports network analysis and operational decision-making when the necessary model and data are available. These are different layers rather than interchangeable product names [29]. A centralized institutional service can depend on geographically distributed field equipment.

Timestamps, Data Quality, and Operational Continuity

A time-critical measurement has limited value if its location and measurement time are unknown. Communication delay, clock offset, improper scaling, stale last-known values, and missing data can distort operations. Timestamp quality, priority handling, authorization, redundancy, and fault behavior are therefore systems-engineering requirements rather than incidental user-interface details. Only historically published and general architectural concepts are covered; no current operational topology, access mechanism, or protection settings are disclosed.

Differences from Record-Processing Systems

MERNIS and TAKBIS revolve around the consistency and legal validity of authoritative records. SCADA/EMS emphasizes physical process measurements and time-sensitive situational awareness. Both require authorization, integrity, auditability, resilience, and fault management. The wider electrical-engineering history is examined in History of Engineering in Türkiye.

MERNİS: Common Identity and Centralized Population Data

The official objectives of MERNİS include performing civil-registration operations electronically, creating a central database, assigning the Turkish Republic Identity Number, and providing electronic information services to public institutions [20].

From a systems-engineering perspective, one of MERNİS’s most consequential effects was to provide a common identity field through which citizens could be represented consistently across different public systems. This became a foundational data element for later inter-agency integration.

Arı’s thesis similarly classifies MERNİS as a general system capable of supplying data to other public applications, whereas systems such as UYAP, VEDOP, PolNet, and TAKBİS are treated as institutional or domain-specific systems [1].

MERNİS is the Merkezi Nüfus İdaresi Sistemi (Central Population Administration System). The responsible national authority describes centralized population records and national identity numbers as core capabilities. KPS, the Kimlik Paylaşımı Sistemi (Identity Sharing System), is a separate service that makes authorized subsets of those records available to eligible institutions under the applicable legal rules. [35, 36]

MERNİS concerns the integrity and maintenance of the underlying population records; KPS concerns controlled access to that information across institutions. A shared identifier does not guarantee that every dependent application is synchronized at all times. Change propagation, authorization, and consistency management remain distinct implementation responsibilities. [35, 36]

VEDOP: Transaction Processing and Decision Support in Tax Administration

According to the Revenue Administration’s 2009 Activity Report, the Tax Office Automation Project (VEDOP) began in 1998. Its objectives included computerizing tax-office operations, reducing workload, improving effectiveness and efficiency, and using collected data to build sound decision-support and management-information systems [21].

This objective shows the maturation of public-sector computing. The computer was no longer simply a device that accelerated a manual transaction; it had become a system capable of transforming operational data into management information and decision support.

UYAP: A Shared Digital Workflow for the Judiciary

The Ministry of Justice’s UYAP history traces the first automation work to 1998 and the establishment of the Information Processing Department to 1999. UYAP I central automation began on 28 September 2000; the software was completed and put into operation on 31 December 2001, with web-based software developed across 33 subsystems [22].

UYAP’s key engineering effect was to digitize judicial processes not merely at the level of scanned documents but at the level of data, document management, authorization, and workflow. Historical comparisons reproduced in Arı’s thesis show that several document-transfer and statistical-preparation processes were reduced from hours or days to minutes or seconds [1].

As with PolNet, the gain came not only from faster hardware but from removing physical document circulation and repeated data entry.

UYAP was introduced as Ulusal Yargı Ağı Projesi (National Judiciary Network Project), and the operational platform is called Ulusal Yargı Ağı Bilişim Sistemi (National Judiciary Network Information System). According to the Ministry of Justice, it supports electronic judicial and administrative workflows and authorized integration across relevant organizational units. The term network therefore covers document handling, case processing, electronic signatures, time-related records, and role-specific access, not merely the transport infrastructure. [22, 37]

Case-data integrity, traceability of operations, and access authorization are separate design obligations. Electronic signature verification is not a substitute for defining workflow permissions or retaining records in accordance with procedural requirements; these functions require their own controls. [37]

TAKBİS: Property Data as a Central Information Infrastructure

According to the General Directorate of Land Registry and Cadastre, the TAKBİS project was launched in 2001; land-registry records were digitized and transferred to a central database, enabling online service at registry offices [23]. More detailed institutional historical records show that the first-stage contract was signed on 26 December 2000 and that analysis and design were conducted in 2001 [23].

TAKBİS is not merely an automation system for title-deed transactions. Property and spatial data form foundational inputs for urban planning, taxation, legal transactions, expropriation, and geographic information systems. TAKBİS consequently became an important component of Türkiye’s national master-data ecosystem.

e-İçişleri: Integrating Central and Provincial Administration

Şafak Başa’s academic study describes e-İçişleri as an e-government project developed to move the work and transactions of Ministry of Interior central units, governorships, district governorships, and provincial administrations into electronic form and to support information exchange with other public institutions [24].

Institutional Ministry records state that the project was developed in 2005 and that processes across central and provincial administration were moved into electronic form; the Ministry-developed Electronic Document Management System introduced in 2010 further reduced time and cost in official correspondence [24].

The engineering challenge is much larger than building a web application. Integrating central and provincial administration requires the coordinated design of:

• institutional identity and authorization,
• legally compliant electronic signatures,
• document standards,
• organizational hierarchy,
• distributed user administration,
• audit trails and accountability.

This also connects directly with the concerns covered in Information Technology Law and Cybersecurity Engineering.

The e-Government Gateway as a Common Access Layer

According to the official e-Government Gateway presentation, the platform was created to deliver electronic public services rapidly and securely through a single authentication point and has been in service since 18 December 2008 [25].

The e-Government Gateway integrates services from multiple public institutions through a shared service-access layer. Its architectural components include:

institutional/domain systems → integration services → common identity and authorization → e-Government service layer

MERNİS, UYAP, TAKBİS, and other institutional systems continue to own their domain data and process logic; the e-Government Gateway provides a common access surface for citizens and institutions.

Five Architectural Periods in Public-Sector Computing

The history becomes clearer when organized by the system problem being solved rather than by hardware brands alone.

The 1930s–1950s were characterized by the mechanization of large records through punched-card and electromechanical data processing, with Ziraat Bankası among the institutional examples. In the 1960s–1970s, the need for greater computational capacity and scientific processing encouraged centralized computers and batch architectures; KGM IBM 650 and İTÜ IBM 1620 illustrate this phase.

During the 1980s–1990s, geographically dispersed institutions increasingly relied on WANs, terminals, client-server systems, and intranets. EARN/TÜVAKA, the Police Computer Network, and KaraNET belong to this networking context. From the late 1990s through the 2000s, shared data and institutional workflows encouraged web-based enterprise systems and centralized or shared-data architectures, exemplified by PolNet, MERNİS, VEDOP, UYAP, and TAKBİS.

From the late 2000s onward, inter-agency interoperability became increasingly associated with service integration, common identity, and federated gateway architectures. e-İçişleri and the e-Government Gateway exemplify this direction. These periods describe overlapping architectural tendencies rather than sharply separated technical eras.

These are not rigid boundaries. Legacy and newer architectures often coexisted for long periods.

Chronological Summary

• 1934: punched-card-based mechanized data processing at Ziraat Bankası [5].
• 1960: IBM 650 at KGM; the first electronic computer used in Türkiye [6].
• 1964: IBM 1620 at İTÜ for scientific computing; period of the establishment of the METU Computer Center [7], [12].
• 1969: institutional use of the word “bilgisayar” at Hacettepe [10].
• 1973-1974: institutionalization of doctoral study in Computer Science Engineering at Hacettepe [10].
• 1977: undergraduate Computer Engineering education begins at Hacettepe and METU [8], [9], [10].
• 1981-1982: EGM Information Processing Center and Information Processing Department [1].
• 1986: EARN connection through Ege University [11].
• 1989-1995: Police Computer Network period [1].
• 1990: IANA registration date of the .tr domain [13].
• 1992: experimental METU-Netherlands X.25 Internet connection [12].
• 1993: permanent 64 Kbps METU-NSFNET connection [12].
• 1993 period: first .tr web server/site at the METU Computer Center [14].
• 1994: METU IBM SP2 becomes the first TOP500 system from Türkiye [12].
• 1994: “MEBS” becomes part of the institutional name in the Turkish Land Forces history [16].
• 1996: ULAKBİM begins operations; first TASMUS contract [15], [18].
• 1997: ULAKNET; TAFICS Crypto System Development Project [15], [17].
• 1998: VEDOP begins; PolNet 2000 is presented at KamuNet 98 [1], [21].
• 1999: Transpol/PolNet architectural separation [1].
• 2000-2001: early stages of UYAP I and TAKBİS [22], [23].
• By 2003: academic documentation of web-based institutional applications on KaraNET [3].
• 2005: e-İçişleri [24].
• 2008: e-Government Gateway begins service [25].

Conclusion

The history of computing in Türkiye is too layered to be summarized as “the first computer arrived in 1960 and the Internet arrived in 1993.”

The IBM 650 at KGM represents the introduction of electronic computing into public engineering. İTÜ and METU represent the institutionalization of scientific computing and computer science. Hacettepe and METU represent the formation of Computer Engineering education. Ege University and TÜVAKA represent the international academic-network era. METU represents the transition to the Internet and the early Web, while ULAKBİM represents the institutionalization of a national academic network.

In defense and security, systems such as KaraNET, TAFICS, TASMUS, TAYAS, Transpol, and PolNet should be distinguished as institutional intranet, strategic communications, tactical communications, local-area networking, and application/information-system layers, rather than grouped under one generic heading. This produces a more technically accurate historical account.

With MERNİS, VEDOP, UYAP, TAKBİS, and e-İçişleri, public-sector computing moved beyond internal automation toward nationwide data and workflow infrastructures for identity, property, taxation, justice, security, and administration. The e-Government Gateway did not replace those domain systems; it added a common identity and service-access layer above them.

Across roughly nine decades, the central engineering problem has remained recognizable: collect authoritative data from the right source, process it reliably, deliver it to an authorized user at the required time, and preserve the integrity of the transaction. What changed was the scale of the solution—from punched cards to centralized computers, from centralized computers to networks, from networks to integrated databases, and from institutional databases to an interoperable distributed digital state.

Architectural continuity in public information systems

The development of public-sector computing in Türkiye is not solely a sequence of hardware models and institutional launch dates. Batch processing within agencies, terminal and network access, centralized registries, interagency exchange and shared digital service gateways represent changes in where records are produced, validated and used during public workflows.

Population records, land registries, taxation and judicial case management each have different legal objects and transaction semantics. MERNİS, TAKBİS, VEDOP and UYAP illustrate these distinct domains. Their common systems-engineering requirements include stable record identity, traceable transactions, controlled concurrent modification, access authorization and interoperability across organizational boundaries.

A communications network and a shared information model are different architectural layers. Similarly, exposing an electronic application interface does not by itself characterize every back-office processing stage. Historical analysis therefore distinguishes network infrastructure, transactional systems, authoritative registries and citizen-facing service delivery, allowing each institutional development to be described within its actual functional scope.

Institutional Records and Technical Architecture

In early computerization, the equipment model, installation date, and operational purpose often appear in different documents. Proof that an institution used computers does not by itself identify the data model, programmer, or network architecture. Reconstructing technical design requires application specifications, training material, data dictionaries, maintenance records, and period-specific hardware documents.

Making a service accessible electronically is not identical to establishing a centralized record system. The user interface may be online while validation, authorization, or archival processes still depend on physical records. Historical comparisons should distinguish access channels, data integrity, organizational authority, disaster recovery, and cross-system exchange.

References

**[10]** A. Köksal, “Röportaj: Prof. Dr. Aydın Köksal,” BM Dergi — Official Publication of the Chamber of Computer Engineers. BMO.

**[19]** ASELSAN, 2019 Annual Report, “TAYAS — Tactical Local Area Network System,” 2019. ASELSAN.

**[18]** ASELSAN, “Taktik Sahada Haberleşmenin Garantisi: TASMUS-G,” technical historical publication. ASELSAN.

**[32]** ASELSAN. (2017). TAYAS: Tactical Local Area Network System. Official technical product brochure.

**[33]** ASELSAN. (2020). 2020 Annual Report. Sections on TASMUS and TAYAS communication systems.

**[5]** B. Altıntaş and N. Çelebiler, “Kamu Kurumlarında Bilgisayar Kullanımı,” study prepared for the Ministry of Finance and Customs, TBMM Proceedings, 17 Jan. 1984. TBMM.

**[27]** B. Çakırca, Gelişmekte Olan Bir Ülkede Temiz Siyasetçi Örneği: Adnan Kahveci, master's thesis, Abant İzzet Baysal University, 2009, biographical and technical-advisory sections; citing an interview with Vahit Erdem.

**[1]** B. E. Arı, E-Devlet ve Türk Emniyet Teşkilatı: PolNet Örneği, Master’s thesis, Uludağ University, Institute of Social Sciences, Bursa, 2014. Uludağ University AVESİS.

**[29]** B. Uçan, “Milli Yük Tevzi SCADA/EMS Sistemi” [National Load Dispatch SCADA/EMS System], in E. Özdemirci and H. Gürbüz (eds.), Cumhuriyetin 100. Yılında Türkiye Elektrik Tarihi, TESAB, 2023, pp. 533–560. ISBN 978-625-94054-1-4. TESAB.

**[4]** C. Çerkezoğlu, Kara Kuvvetleri Komutanlığında Uzaktan Eğitim Uygulamaları, Master’s thesis, Sakarya University, Institute of Social Sciences, Sakarya, 2006. Sakarya University Open Academic Archive.

**[11]** Ege University, Ege Üniversitesi İlkler Kitabı, “Türkiye’de ilk EARN bağlantısı,” p. 72. Ege University.

**[6]** General Directorate of Highways, “Türkiye’de Kullanılan İlk Bilgisayar — IBM 650,” institutional history. KGM.

**[23]** General Directorate of Land Registry and Cadastre, “Tapuda Yeni Dönem Başladı — TAKBİS Tamamlandı.” TKGM.

**[8]** Hacettepe University Department of Computer Engineering, “Undergraduate Program and History.” Hacettepe University.

**[2]** İ. Pekgözlü, “e-Devlet Projelerinin Yönetilmesi: PolNet Projesi Örneği,” Sosyoekonomi, vol. 17, no. 17, 2012. doi: 10.17233/se.78159.

**[13]** Internet Assigned Numbers Authority, “Delegation Record for .TR.” IANA.

**[7]** Istanbul Technical University Foundation, “Bilim, Araştırma, Geliştirme ve Öğretimde Çağdaşlaşmada Öncü İstanbul Teknik Üniversitesi,” historical record. İTÜ Foundation.

**[28]** K. Sancak, “Farklı Bir Siyasetçi: Adnan Kahveci,” Trabzon'un Kültürel Yüzü, pp. 22–28, engineering education and academic career passages.

**[14]** Middle East Technical University Computer Center, “BİDB’nin Bilişimde Öncü Çalışmaları Nelerdir?” METU FAQ.

**[12]** Middle East Technical University Computer Center, “History.” METU Computer Center.

**[9]** Middle East Technical University Department of Computer Engineering, “About the Department — History.” METU.

**[26]** Ö. Kuşcu, H. Çetiner, and H. T. Gökmen, “Tarihçe ve Akademik Kadro Açısından Türkiye'de Bilgisayar Mühendisliği Eğitimi” [Computer Engineering Education in Türkiye in Terms of History and Academic Staff], Suleyman Demirel University Journal of Natural and Applied Sciences, vol. 17, no. 1 (Special Issue), pp. 38–44, 2013.

**[25]** Republic of Türkiye e-Government Gateway, e-Government Gateway Presentation, noting service since 18 Dec. 2008. turkiye.gov.tr.

**[20]** Republic of Türkiye Ministry of Interior, General Directorate of Civil Registration and Nationality, “MERNİS Projesi Hedefleri.” NVİ.

**[22]** Republic of Türkiye Ministry of Justice, “UYAP Information System — Stages and History.” UYAP.

**[36]** Republic of Türkiye, General Directorate of Civil Registration and Nationality. (n.d.). Central Population Administration System (MERNİS).

**[35]** Republic of Türkiye, General Directorate of Civil Registration and Nationality. (n.d.). Identity Sharing System (KPS).

**[37]** Republic of Türkiye, Ministry of Justice. (n.d.). UYAP Information System: General Information.

**[21]** Revenue Administration, 2009 Activity Report, “Vergi Dairesi Otomasyon Projeleri (VEDOP),” 2009. GİB.

**[24]** Ş. Başa, “e-Devlet Çalışmalarına Bir Örnek: ‘e-İçişleri Projesi’,” Sosyoekonomi, vol. 17, no. 17, 2012. doi: 10.17233/se.47636.

**[3]** Ş. Çakır, Kara Kuvvetleri Mesaj İşleme ve Sınıflandırma Uzman Sistemi, Master’s thesis, Istanbul Technical University, Institute of Science and Technology, Defense Technologies Program, Istanbul, 2003. İTÜ POLEN.

**[17]** TÜBİTAK BİLGEM, “Chronology — 1997: TAFICS Crypto System Development Project.” TÜBİTAK BİLGEM.

**[15]** TÜBİTAK ULAKBİM, “Who We Are?” TÜBİTAK ULAKBİM.

**[30]** Turkish Armed Forces Foundation. (2024). TAFICS: Integrated Communications System of the Turkish Armed Forces.

**[31]** Turkish Armed Forces Foundation. (2024). TASMUS: Tactical Area Communications.

**[16]** Turkish Land Forces Command, “Communications, Electronics and Information Systems (MEBS) School and Training Center — History.” Turkish Land Forces.

**[34]** Turkish National Police, Ministry of Interior. (2018). 2018 Institutional Financial Status and Expectations Report. POL-NET, EBYS, and KGYS sections.