IT Master Plan: Blueprint Strategis untuk Transformasi Digital Perusahaan

Panduan Komprehensif dari Network, Server, Aplikasi, hingga Security

Apa Itu IT Master Plan?

IT Master Plan adalah dokumen strategis jangka panjang (biasanya 3-5 tahun) yang menjadi cetak biru pengembangan infrastruktur dan sistem teknologi informasi sebuah organisasi. Ini bukan sekadar daftar pembelian hardware atau software, tapi roadmap komprehensif yang menyelaraskan investasi teknologi dengan tujuan bisnis perusahaan.

Bayangkan IT Master Plan seperti blueprint arsitek untuk membangun gedung pencakar langit—setiap komponen harus dirancang dengan cermat, terintegrasi sempurna, dan mendukung visi jangka panjang.

Mengapa IT Master Plan Sangat Penting?

Tanpa IT Master Plan yang solid, perusahaan akan:

• ❌ Investasi teknologi tidak terarah dan boros
• ❌ Sistem tidak terintegrasi, menciptakan data silo
• ❌ Tidak siap menghadapi pertumbuhan bisnis (scalability issue)
• ❌ Rentan terhadap cyber threats
• ❌ Sulit beradaptasi dengan perubahan teknologi

Dengan IT Master Plan yang baik:

• ✅ Investasi IT aligned dengan strategi bisnis
• ✅ Infrastruktur scalable dan future-proof
• ✅ Efisiensi operasional meningkat
• ✅ Security posture yang kuat
• ✅ Competitive advantage melalui teknologi

Komponen Utama IT Master Plan

IT Master Plan yang komprehensif harus mencakup empat pilar fundamental:

1. Network Infrastructure (Infrastruktur Jaringan)

2. Server & Storage Infrastructure

3. Application Systems (Sistem Aplikasi)

4. IT Security & Governance

Mari kita bahas satu per satu secara detail.

1. Network Infrastructure Master Plan

Network adalah jantung dari seluruh ekosistem IT. Tanpa jaringan yang robust, server tercepat dan aplikasi terbaik pun tidak akan berfungsi optimal.

Komponen Network Master Plan:

A. Network Architecture Design

Current State Assessment:

• Topology yang ada saat ini (Star, Mesh, Hybrid)
• Bandwidth utilization dan bottleneck
• Network devices inventory (router, switch, firewall)
• Coverage area dan blind spots

Future State Design:

• Core Layer: Backbone network dengan redundancy

  • High-speed switches (10Gbps - 100Gbps)
  • Redundant links untuk high availability
  • Load balancing mechanism

• Distribution Layer: Agregasi dari access layer

  • L3 switches untuk routing antar VLAN
  • QoS (Quality of Service) implementation
  • Traffic management

• Access Layer: End-user connectivity

  • PoE (Power over Ethernet) switches untuk IP phones, cameras
  • Port security dan 802.1X authentication
  • VLAN segmentation

B. Wide Area Network (WAN)

Untuk perusahaan dengan multiple locations:

• MPLS (Multiprotocol Label Switching)

  • Dedicated connection antar kantor
  • Guaranteed bandwidth dan SLA
  • Cocok untuk mission-critical applications

• SD-WAN (Software-Defined WAN)

  • Cost-effective alternative to MPLS
  • Intelligent traffic routing
  • Centralized management
  • Path optimization berdasarkan application priority

• Hybrid WAN

  • Kombinasi MPLS untuk critical apps
  • Internet/broadband untuk non-critical traffic
  • Automatic failover

C. Wireless Network (WiFi)

Modern workplace demands robust wireless:

• Coverage Planning

  • Heat map analysis untuk optimal AP placement
  • Eliminate dead zones
  • Capacity planning based on user density

• WiFi Standards

  • WiFi 6 (802.11ax) untuk high-density areas
  • WiFi 6E untuk future-proofing
  • Backward compatibility

• Security

  • WPA3 encryption
  • Network segmentation (Guest, Corporate, IoT)
  • Captive portal untuk guest access
  • 802.1X authentication untuk corporate devices

D. Network Monitoring & Management

• Network Monitoring System (NMS)

  • Real-time monitoring (SNMP, NetFlow)
  • Alert system untuk anomaly detection
  • Performance baseline dan trending

• Network Management Tools

  • Centralized configuration management
  • Automated backup untuk device configs
  • Change management tracking

E. Bandwidth Planning

Proyeksi 3-5 tahun ke depan:

Pertimbangan:

• Video conferencing adoption (50-100 Mbps per concurrent session)
• Cloud applications migration
• IoT devices proliferation
• Future technologies (VR/AR for training, digital twin)

2. Server & Storage Infrastructure Master Plan

Server dan storage adalah fondasi komputasi yang menjalankan semua aplikasi bisnis.

A. Server Infrastructure Strategy

Physical vs Virtual vs Cloud

1. On-Premises Physical Servers

Kapan menggunakan:

• High-performance workloads (database, ERP)
• Compliance requirements (data residency)
• Predictable, steady workloads

Planning:

• Compute Capacity: CPU cores, RAM requirements
• Redundancy: N+1 atau N+2 untuk critical servers
• Lifecycle: 3-5 tahun refresh cycle
• Power & Cooling: UPS capacity, CRAC units

Example Architecture:

Tier 1 (Mission Critical):
- 2x Database Servers (Clustered)
- 2x Application Servers (Load Balanced)
- Uptime: 99.99% (52 minutes downtime/year)

Tier 2 (Business Critical):
- Application servers dengan redundancy
- Uptime: 99.9% (8.76 hours downtime/year)

Tier 3 (Standard):
- Non-critical applications
- Uptime: 99% (87.6 hours downtime/year)

2. Virtualization Strategy

Benefits:

• Resource optimization (1 physical server = 10-20 VMs)
• Faster deployment (minutes vs days)
• Easy backup & disaster recovery
• Cost reduction (hardware, power, cooling)

Technology Options:

• VMware vSphere: Industry standard, mature ecosystem
• Microsoft Hyper-V: Windows-centric environments
• KVM/Proxmox: Open-source, cost-effective

Virtualization Architecture:

Cluster Design:
- 3-5 physical hosts (N+1 redundancy)
- Shared storage (SAN/NAS)
- vMotion/Live Migration capability
- DRS (Distributed Resource Scheduler)
- HA (High Availability) clustering

Resource Allocation:
- CPU overcommit ratio: 3:1 - 5:1
- Memory: No overcommit untuk production
- Storage: Tiered storage (SSD + HDD)

3. Cloud Strategy (Hybrid Cloud)

Cloud Adoption Model:

• IaaS (Infrastructure as a Service)

  • VM instances di AWS EC2, Azure, GCP
  • Use case: Development, testing, burst capacity
  • Cost: Pay-as-you-go

• PaaS (Platform as a Service)

  • Managed databases, containers
  • Use case: Modern applications, microservices
  • Cost: Based on resources consumed

• SaaS (Software as a Service)

  • Office 365, Salesforce, Workday
  • Use case: Standard business applications
  • Cost: Per-user subscription

Hybrid Cloud Architecture:

On-Premises:
- Core ERP, Database (sensitive data)
- Legacy applications
- High-performance computing

Private Cloud:
- Internal applications
- Dev/Test environments
- Control & compliance

Public Cloud:
- Web applications
- Mobile backends
- Analytics & Big Data
- Disaster Recovery site

Cloud Migration Roadmap:

• Year 1: Assessment & pilot (low-risk apps)
• Year 2: Migrate non-critical applications
• Year 3: Core business applications (lift-and-shift atau refactor)
• Year 4-5: Optimize & modernize (cloud-native)

B. Storage Infrastructure

Storage Types & Use Cases:

1. Direct Attached Storage (DAS)

• Connected langsung ke server
• Use case: Local databases, high I/O applications
• Pros: Low latency, simple
• Cons: Not shared, limited scalability

2. Network Attached Storage (NAS)

• File-level storage over network
• Protocols: NFS (Linux), SMB/CIFS (Windows)
• Use case: File shares, home directories, collaboration
• Pros: Easy management, shared access
• Cons: Network dependent, performance limitations

3. Storage Area Network (SAN)

• Block-level storage over dedicated network
• Protocols: Fiber Channel, iSCSI
• Use case: Databases, virtualization, high-performance apps
• Pros: High performance, scalability, redundancy
• Cons: Complex, expensive

Storage Architecture Design:

Tiered Storage Strategy:

Tier 0 - All-Flash Array:
- IOPS: 100,000+
- Use case: Databases, transaction systems
- Capacity: 10-20 TB
- Cost: Highest $/TB

Tier 1 - Hybrid (SSD + HDD):
- IOPS: 10,000 - 50,000
- Use case: Virtual machines, applications
- Capacity: 50-100 TB
- Cost: Medium $/TB

Tier 2 - Traditional HDD:
- IOPS: 500 - 5,000
- Use case: File shares, archives (active)
- Capacity: 200-500 TB
- Cost: Low $/TB

Tier 3 - Cold Storage/Archive:
- Tape libraries, cloud storage (S3 Glacier)
- Use case: Backup, compliance, long-term retention
- Capacity: PB scale
- Cost: Lowest $/TB

Data Growth Projection:

Note: Include 50% overhead untuk snapshots, replicas, growth buffer

C. Backup & Disaster Recovery

Backup Strategy - 3-2-1 Rule:

• 3 copies of data
• 2 different media types
• 1 copy offsite

Backup Tiers:

Tier 1 (Critical):
- RPO: 1 hour (max data loss)
- RTO: 4 hours (max downtime)
- Backup: Continuous replication + hourly snapshots
- Retention: 30 days online, 1 year archived

Tier 2 (Important):
- RPO: 24 hours
- RTO: 8 hours
- Backup: Daily full, hourly incremental
- Retention: 14 days online, 90 days archived

Tier 3 (Standard):
- RPO: 24 hours
- RTO: 24 hours
- Backup: Daily incremental, weekly full
- Retention: 7 days online, 30 days archived

Disaster Recovery Site:

• Hot Site: Fully operational, real-time replication (expensive)
• Warm Site: Partial infrastructure, ready in hours
• Cold Site: Empty facility, setup takes days (cheapest)
• Cloud DR: Cost-effective, pay for what you use

3. Application Systems Master Plan

Aplikasi adalah interface antara teknologi dan bisnis. Ini adalah bagian yang langsung dirasakan user dan menghasilkan business value.

A. Application Portfolio Assessment

Kategorisasi Aplikasi:

1. Core Business Applications

• ERP (SAP, Oracle, Microsoft Dynamics)
• CRM (Salesforce, Microsoft Dynamics)
• Financial systems
• HR Management System (HRIS)

Strategy: Maintain, upgrade, atau migrate ke cloud

2. Supporting Applications

• Email (Office 365, Google Workspace)
• Collaboration (SharePoint, Teams, Slack)
• Document Management
• Project Management

Strategy: Maximize cloud/SaaS adoption

3. Custom/Legacy Applications

• In-house developed systems
• Outdated technologies (COBOL, legacy .NET, old Java)

Strategy:

• Retire: If redundant
• Replace: With modern SaaS alternative
• Refactor: Modernize architecture
• Re-platform: Migrate to cloud (lift-and-shift)
• Retain: If still valuable dan stable

4. Emerging/Innovation

• AI/ML applications
• IoT platforms
• Big Data analytics
• Mobile applications

Strategy: Pilot, evaluate, scale

B. Application Architecture Modernization

From Monolithic to Microservices:

Traditional Monolithic:

┌─────────────────────────────┐
│   Monolithic Application    │
│  ┌─────────────────────┐   │
│  │   User Interface    │   │
│  ├─────────────────────┤   │
│  │  Business Logic     │   │
│  ├─────────────────────┤   │
│  │   Data Access       │   │
│  └─────────────────────┘   │
│           ↓                 │
│      Database (Single)      │
└─────────────────────────────┘

Pros: Simple deployment, easier debugging Cons: Hard to scale, single point of failure, technology lock-in

Modern Microservices:

                ┌──────────────┐
                │  API Gateway │
                └──────┬───────┘
         ┌──────────┼──────────┐
    ┌────▼───┐ ┌────▼───┐ ┌───▼────┐
    │Service │ │Service │ │Service │
    │   A    │ │   B    │ │   C    │
    └────┬───┘ └────┬───┘ └───┬────┘
    ┌────▼───┐ ┌────▼───┐ ┌───▼────┐
    │  DB A  │ │  DB B  │ │  DB C  │
    └────────┘ └────────┘ └────────┘

Pros: Independent scaling, technology flexibility, fault isolation Cons: Complex deployment, distributed system challenges

Migration Roadmap:

• Phase 1: Strangler pattern (new features as microservices)
• Phase 2: Extract critical modules
• Phase 3: Break monolith incrementally
• Phase 4: Retire monolith

C. Integration Architecture

Modern Integration Patterns:

1. API-First Approach

• RESTful APIs untuk semua services
• API Gateway (Kong, Apigee, AWS API Gateway)
• API documentation (Swagger/OpenAPI)
• Rate limiting, authentication, monitoring

2. Enterprise Service Bus (ESB) / Integration Platform

• MuleSoft, Dell Boomi, WSO2
• Message routing, transformation
• Protocol translation
• Centralized monitoring

3. Event-Driven Architecture

• Message brokers (Kafka, RabbitMQ)
• Asynchronous processing
• Real-time data streaming
• Decoupled systems

D. Application Development Strategy

DevOps & CI/CD Pipeline:

Developer → Git → CI Server → Automated Tests → Container Registry → CD Pipeline → Production

Toolchain:
- Version Control: Git (GitHub, GitLab, Bitbucket)
- CI/CD: Jenkins, GitLab CI, Azure DevOps
- Container: Docker, Kubernetes
- Testing: Automated unit, integration, security tests
- Monitoring: Application performance monitoring (APM)

Benefits:

• Faster time-to-market (weeks → days → hours)
• Higher quality (automated testing)
• Reduced deployment risks
• Better collaboration

E. Mobile & Web Strategy

Multi-Platform Approach:

Web Applications:

• Progressive Web Apps (PWA) - works offline, installable
• Responsive design (mobile-first)
• Modern frameworks (React, Vue, Angular)

Mobile Applications:

• Native: iOS (Swift), Android (Kotlin) - best performance
• Hybrid: React Native, Flutter - faster development, code reuse
• Strategy: Evaluate based on complexity, performance needs, budget

Mobile Device Management (MDM):

• BYOD policies
• App distribution
• Security policies (encryption, remote wipe)
• Compliance tracking

4. IT Security & Governance Master Plan

Security bukan add-on, tapi foundational requirement. Di era cyber threats yang semakin sophisticated, security harus embedded di setiap layer.

A. Security Framework

Defense in Depth Strategy (Berlapis):

┌─────────────────────────────────────────┐
│        Layer 7: Policies & Training     │ ← People
├─────────────────────────────────────────┤
│     Layer 6: Application Security       │ ← Code review, WAF
├─────────────────────────────────────────┤
│         Layer 5: Data Security          │ ← Encryption, DLP
├─────────────────────────────────────────┤
│       Layer 4: Endpoint Security        │ ← Antivirus, EDR
├─────────────────────────────────────────┤
│       Layer 3: Network Security         │ ← Firewall, IPS
├─────────────────────────────────────────┤
│         Layer 2: Perimeter              │ ← DMZ, WAF
├─────────────────────────────────────────┤
│      Layer 1: Physical Security         │ ← Access control
└─────────────────────────────────────────┘

B. Network Security

1. Perimeter Security

Firewall Architecture:

• Next-Gen Firewall (NGFW): Palo Alto, Fortinet, Cisco

  • Application awareness
  • Intrusion Prevention (IPS)
  • SSL inspection
  • Threat intelligence integration

• DMZ (Demilitarized Zone)

  • Public-facing servers (web, email, VPN)
  • Isolated dari internal network
  • Dual firewall setup

2. Network Segmentation

Internet
   ↓
┌──────────────┐
│   Firewall   │
└──────┬───────┘
       ├─────→ DMZ (Public Servers)
       │
       ├─────→ Production Network (VLAN 10)
       │
       ├─────→ Development Network (VLAN 20)
       │
       ├─────→ Guest Network (VLAN 30)
       │
       └─────→ Management Network (VLAN 99)

Benefits:

• Contain breaches (lateral movement prevention)
• Better traffic control
• Compliance requirement (PCI-DSS, HIPAA)

3. Intrusion Detection/Prevention (IDS/IPS)

• Network-based (NIDS/NIPS)
• Host-based (HIDS/HIPS)
• Signature-based + Anomaly detection
• Integration with SIEM

4. VPN (Virtual Private Network)

• Site-to-Site VPN: Connect branch offices
• Remote Access VPN: Work from home
• SSL VPN: Browser-based, no client needed
• IPSec VPN: More secure, requires client

Modern Approach: Zero Trust Network Access (ZTNA)

• “Never trust, always verify”
• Identity-based access
• Micro-segmentation
• Continuous authentication

C. Endpoint Security

1. Antivirus/Anti-Malware

• Traditional signature-based
• EDR (Endpoint Detection & Response): Behavioral analysis, threat hunting
• XDR (Extended Detection & Response): Cross-layer correlation

2. Endpoint Management

• Patch management (OS, applications)
• Configuration management
• Inventory tracking
• Remote control capability

3. Data Loss Prevention (DLP)

• Prevent sensitive data exfiltration
• USB port control
• Email filtering
• Cloud app monitoring (CASB)

4. Mobile Device Security

• MDM (Mobile Device Management)
• MAM (Mobile Application Management)
• Containerization (separate work/personal data)

D. Application Security

Secure Development Lifecycle:

Requirements → Design → Development → Testing → Deployment → Maintenance
     ↓            ↓          ↓            ↓          ↓            ↓
Security     Threat    Secure      Security   Security   Patch
Requirements Modeling  Coding      Testing    Hardening  Management

Key Practices:

• SAST (Static Application Security Testing): Code analysis
• DAST (Dynamic Application Security Testing): Runtime testing
• Dependency scanning: Check for vulnerable libraries
• Penetration testing: Ethical hacking

Web Application Firewall (WAF):

• Protect against OWASP Top 10
• SQL injection, XSS, CSRF prevention
• API protection
• Bot management

E. Data Security

1. Data Classification

2. Encryption Strategy

Data at Rest:

• Database encryption (TDE - Transparent Data Encryption)
• File system encryption
• Full disk encryption (BitLocker, FileVault)

Data in Transit:

• TLS 1.2+ untuk semua komunikasi
• VPN untuk remote access
• Encrypted email (S/MIME, PGP)

Data in Use:

• Homomorphic encryption (emerging)
• Secure enclaves (Intel SGX)

3. Backup Encryption

• Encrypt backup data
• Secure key management
• Test restoration regularly

F. Identity & Access Management (IAM)

1. Authentication

Multi-Factor Authentication (MFA):

• Something you know (password)
• Something you have (token, phone)
• Something you are (biometric)

Implement MFA for:

• All admin accounts (100%)
• Remote access (100%)
• Sensitive applications (100%)
• All users (recommended)

Password Policy:

• Minimum 12 characters
• Complexity requirements
• Password history (prevent reuse)
• Regular expiration (controversial, trend moving away)
• Passwordless authentication (FIDO2, biometric)

2. Single Sign-On (SSO)

• One login untuk multiple applications
• SAML 2.0, OAuth 2.0, OpenID Connect
• Improved user experience
• Centralized access control

3. Privileged Access Management (PAM)

• Vault untuk privileged credentials
• Session recording
• Just-in-time access
• Regular credential rotation

4. Role-Based Access Control (RBAC)

User → Role → Permissions

Example:
- Finance Manager → Finance Role → Access GL, AP, AR
- HR Staff → HR Role → Access HRIS, payroll
- Developer → Dev Role → Access dev environment only

Principle of Least Privilege:

• Users get ONLY permissions they need
• Regular access reviews
• Automatic de-provisioning (when leaving)

G. Security Monitoring & Incident Response

1. SIEM (Security Information & Event Management)

Purpose:

• Centralized log collection
• Real-time correlation
• Threat detection
• Compliance reporting

Popular Solutions:

• Splunk, IBM QRadar, Microsoft Sentinel
• ELK Stack (open-source)

Key Use Cases:

• Failed login attempts
• Privilege escalation
• Data exfiltration attempts
• Malware detection
• Compliance violations

2. Security Operations Center (SOC)

Tiers:

• Tier 1: Alert monitoring, initial triage
• Tier 2: In-depth investigation
• Tier 3: Advanced threat hunting, forensics

Options:

• In-house SOC: Full control, expensive
• Managed SOC (MSOC): Outsourced, 24/7 coverage
• Hybrid: Mix of in-house + managed

3. Incident Response Plan

Phases:

1. Preparation: Playbooks, tools, training
2. Detection: Identify security incidents
3. Containment: Limit damage, isolate affected systems
4. Eradication: Remove threat, patch vulnerabilities
5. Recovery: Restore normal operations
6. Lessons Learned: Post-mortem, improve

Incident Classification:

• Severity 1 (Critical): Active breach, data loss

  • Response: Immediate (15 mins)
  • Escalation: CISO, CEO

• Severity 2 (High): Potential breach, system compromise

  • Response: 1 hour
  • Escalation: IT Manager

• Severity 3 (Medium): Security policy violation

  • Response: 4 hours
  • Escalation: Team lead

• Severity 4 (Low): Minor issues

  • Response: 24 hours
  • Escalation: Not required

H. Compliance & Governance

Relevant Standards/Regulations:

1. ISO 27001 (Information Security Management)

• International standard
• Risk-based approach
• 114 security controls
• Annual audit

2. PCI-DSS (Payment Card Industry)

• Required jika process credit cards
• 12 requirements, 78 sub-requirements
• Quarterly vulnerability scans
• Annual penetration testing

3. GDPR (General Data Protection Regulation)

• EU citizens’ data protection
• Right to be forgotten
• Data breach notification (72 hours)
• Heavy fines (up to 4% revenue)

4. SOC 2 (Service Organization Control)

• For service providers
• Trust principles: Security, Availability, Confidentiality
• Type 1 (point in time) vs Type 2 (period of time)

5. Indonesian Regulations

• UU ITE (Informasi dan Transaksi Elektronik)
• Peraturan OJK (untuk financial services)
• Permenkominfo No. 20/2016: Data center & disaster recovery

Governance Framework:

Board of Directors
        ↓
    IT Steering Committee
    (Business + IT Leaders)
        ↓
    ┌───────────────┬──────────────┐
    ↓               ↓              ↓
IT Strategy    IT Projects    IT Operations
                   ↓
            Project Governance
            - Approval process
            - Budget control
            - Risk management
            - Performance tracking

IT Policies (Essential):

• Acceptable Use Policy
• Information Security Policy
• Password Policy
• Remote Access Policy
• Data Classification Policy
• Incident Response Policy
• Business Continuity Policy
• Vendor Management Policy

I. Security Awareness & Training

Human adalah weakest link!

Training Program:

• New Employee: Security basics, policies
• Annual Refresher: All employees
• Role-Specific: Admin training, developer secure coding
• Phishing Simulation: Quarterly tests

Topics:

• Password hygiene
• Phishing recognition
• Social engineering
• Physical security
• Incident reporting
• Data handling

Metrics:

• Training completion rate
• Phishing simulation click rate
• Time to report incidents
• Security policy violations

Implementation Roadmap

Year 1: Foundation

• Q1-Q2: Assessment & planning

  • Current state analysis
  • Gap analysis
  • Prioritization
  • Budget approval

• Q3-Q4: Quick wins & foundation

  • Network upgrades (critical bottlenecks)
  • Security basics (MFA, patching, backups)
  • Virtualization pilot
  • Cloud strategy finalization

Year 2: Modernization

• Server consolidation & virtualization
• Storage upgrade (tiered storage)
• Application assessment complete
• Security monitoring (SIEM implementation)
• First cloud migration wave

Year 3: Transformation

• Microservices migration start
• Hybrid cloud maturity
• Advanced security (EDR, SOAR)
• Network modernization (SD-WAN)
• DevOps adoption

Year 4-5: Optimization

• AI/ML integration
• Automation & orchestration
• Continuous improvement
• Emerging technologies evaluation
• Infrastructure refresh planning

Key Success Factors

✅ Executive Sponsorship: C-level buy-in dan budget commitment ✅ Business Alignment: IT roadmap sejalan dengan business strategy ✅ Change Management: Proper communication, training, support ✅ Agile Approach: Iterative implementation, not big bang ✅ Risk Management: Identify dan mitigate risks early ✅ Vendor Management: Strategic partnerships ✅ Skills Development: Upskill internal team ✅ Metrics & KPIs: Measure progress dan value realization

Conclusion

IT Master Plan adalah living document yang harus:

• Reviewed dan updated annually
• Flexible untuk accommodate changes
• Balanced antara innovation dan stability
• Fokus pada business value, bukan hanya technology

Ingat: Teknologi adalah enabler, bukan tujuan akhir. IT Master Plan yang sukses adalah yang membantu organisasi mencapai business objectives dengan lebih efisien, secure, dan scalable.

Butuh bantuan menyusun IT Master Plan untuk organisasi Anda? Pertimbangkan untuk engage dengan IT consultant atau certified enterprise architect yang berpengalaman.