A technical guide to implementing E-Office in government agencies: mapping disposition workflows, deploying servers with Docker, migrating legacy archives, and conducting measurable UAT.
E-Office implementation in government agencies rarely fails because the application is not sophisticated enough. What happens more often: there is no execution plan. From mentoring at several government offices and hospitals, I see the same pattern recurring. Incoming mail is still printed and delivered manually to the third floor, tiered disposition runs in a WhatsApp group, archives pile up in steel cabinets, while the E-Office license has been running for a year but only 20 percent of its features are used. The impact is measurable: average disposition completion time is 3 to 5 working days, and can exceed two weeks for letters requiring cross-departmental approval. This article is not a summary of theory. We will dissect the implementation stages from process mapping, server setup, flow configuration, to old archive migration, with real configurations you can run in a staging environment this week.
The most expensive mistake is buying or installing the application first, then forcing the bureaucratic process to adapt to the application menu. The correct order is reversed. Start by collecting factual data for two weeks: how many incoming and outgoing letters per day, which officials have disposition authority, how many disposition levels on average, and how long each stage takes. At one government office with 40 incoming letters per day, we found 12 tiered dispositions with an average of 3 approval levels, and 60 percent of delays occurred at the second level because the official was on an official trip.
From that data, draft three to five main process paths, no more. For example: Regular Incoming Letter path (secretary, relevant division head, executor), Priority Incoming Letter path (secretary, office head, division head, executor with a 1x24-hour deadline), and Internal Official Note path (staff, subdivision head, section head). Define explicit exit criteria for each stage, for example a stage is declared complete only if there is a disposition note and follow-up attachment, not merely the accept button clicked.
The result of this mapping becomes a reference document that must be signed by the Head of Office or Director. Without that document, each department will consider its own flow the most correct and the project will stop midway. I usually ask for this document to be completed before the staging server is turned on, because changing the flow on paper is far cheaper than changing it after 150 users are accustomed to the application.
For 150 active users with a peak of 40 concurrent users, the specification I use and that has proven sufficient: 4 vCPU, 8 GB RAM, 200 GB SSD, Ubuntu Server 22.04 LTS, PHP 8.1 with mysqli, gd, intl, zip, mbstring extensions, Nginx 1.18 as reverse proxy, and MariaDB 10.6. Increase upload_max_filesize and post_max_size to 20M because letter scans are 2 to 8 MB per file, and set date.timezone to Asia/Jakarta so disposition timestamps do not drift.
For a test environment, Docker Compose speeds up configuration replication to the production server. Here is a minimal example that can be run directly with the docker compose up -d command after the E-Office application folder is placed in the ./eoffice directory.
services:
web:
image: php:8.2-apache
ports: [8080:80]
volumes: [./eoffice:/var/www/html]
depends_on: [db]
db:
image: mariadb:10.11
environment:
MARIADB_DATABASE: eoffice
MARIADB_ROOT_PASSWORD: ganti-saya
volumes: [eodb:/var/lib/mysql]
volumes:
eodb:Three configurations are often missed and have a big impact. First, install TLS with a certificate from an official provider and force HTTP to HTTPS redirect, because official letters contain data that must not pass through plaintext. Second, schedule a daily MariaDB backup at 01.00 with 30-day retention and store a copy in a location separate from the application server. Third, enable access logs and application audit logs for at least 1 year, because government agencies almost always need them during audits.
Do not migrate the entire archive. Start with the last five years or about 2,000 to 5,000 documents, because those are still frequently searched. Prepare a CSV template with mandatory columns: letter number, date, originating agency, subject, classification code, and PDF file path. For scan results, use PDF/A format with 200 to 300 dpi resolution and OCR so the text is searchable; the average size will be 400 to 900 KB per document, so 5,000 archives require about 3 to 4 GB of storage.
After the data is loaded, run UAT for two weeks with 10 representative users from the secretariat, technical department, and one leader. Measure four metrics: average disposition time, number of dispositions that exceed the deadline, percentage of letters successfully found again within 60 seconds, and number of incident tickets per day. Realistic target: disposition time drops from 3 days to under 8 working hours in the second week, and archive search under 60 seconds.
Training should take the form of 5-minute videos per role, not a four-hour session attended by everyone at once. Create only four videos: letter creator, disposition secretary, follow-up executor, and leader. Paste the links on the application login page. This significantly reduces the volume of questions to the IT team compared with mass training.
For one institution with 100 to 200 users, a reasonable range is 6 to 10 weeks: 2 weeks of process mapping, 1 week of infrastructure setup, 1 week of workflow configuration and data migration, 2 weeks of UAT, and the rest for gradual roll-out plus fixes.
Not required. Institutions with limited data center space can use a VPS at a domestic provider with appropriate certification, as long as data is stored in Indonesian territory and there is a clear data processing agreement.
First separate two things: the official refuses to work in the application, or refuses a certified electronic signature. For the first, provide a verification mode through application approval without a certificate. For the second, do not force it; use a gradual approach and start with low-risk document types such as internal official memoranda.
For 150 active users, an on-premise server or mid-range VPS is around 12 to 30 million rupiah per year including storage and backup, plus costs for TLS certificates, domains, and maintenance. It is far cheaper than the cost of paper, internal couriers, and lost disposition waiting time.
Successful E-Office implementation always starts from clear processes, not from application installation. Once official document workflows are documented, servers are ready with TLS and tested backups, five years of archives are migrated neatly, and UAT is measured with metrics, digitalization of correspondence at your institution can run within one quarter. If you are preparing E-Office for a government department, public hospital, or institution with complex multi-level disposition workflows, our team can help from process mapping, infrastructure setup, electronic signature integration, to roll-out assistance and role-based training. Consult your needs to get an architecture design and schedule estimate that suits your institution's conditions.
Related solutions by PT Pilar Inovasi Informatika (Pilar Inovasi IT products): SIMRS (Hospital Information System) E-Office. Need a free consultation?
Belum ada komentar. Jadilah yang pertama!
Baca juga artikel lainnya
