Split View: IT사업 기획과 제안서 작성 완전 가이드: RFP 분석·ISMP·WBS·비용 산정·SLA까지

Business Planning -> Budget Approval -> RFP Creation -> Bidding/Proposal -> Evaluation/Selection -> Kickoff -> Execution -> Acceptance/Closure -> Operations/Maintenance

# Public IT Project Characteristics
regulatory_environment:
  - National Informatization Act
  - Software Promotion Act
  - Electronic Government Act
  - PPS Contract Regulations

cost_estimation:
  standard: Software Business Cost Estimation Guide (Ministry of Science and ICT)
  methods:
    - Function Point (FP) method
    - Man-Month method

bidding_methods:
  - Open competitive bidding (default)
  - Limited competitive bidding (qualification restricted)
  - Negotiated contract (technology-focused evaluation)

# Private IT Project Characteristics
decision_making:
  - C-Level approval driven
  - Business case (ROI) based
  - Vendor relationships and references critical

contract_types:
  - Fixed Price
  - Time and Material
  - Outcome-based

Standard RFP Structure:

1. Project Overview
   - Background and objectives
   - Project scope
   - Timeline
   - Budget

2. Current System Status
   - Infrastructure architecture
   - Application system inventory
   - Data landscape

3. Requirements
   - Functional Requirements (FR)
   - Non-Functional Requirements (NFR)
   - Data requirements
   - Interface requirements
   - Security requirements

4. Proposal Requirements
   - Technical section (system configuration, architecture)
   - Management section (methodology, organization, schedule)
   - Support section (training, maintenance, technology transfer)

5. Evaluation Criteria
   - Technical evaluation items and scoring
   - Price evaluation method
   - Presentation evaluation

6. Submission Guidelines
   - Submission schedule and method
   - Proposal format specifications
   - Contact information

Go/No-Go Evaluation Matrix (100 points)

Strategic Fit (25 points)
  - Alignment with company business strategy    0-10 points
  - Reference acquisition value                 0-8 points
  - Long-term relationship potential             0-7 points

Competitiveness (25 points)
  - Relevant project experience                 0-10 points
  - Core technology capability                  0-8 points
  - Key personnel availability                  0-7 points

Profitability (25 points)
  - Revenue margin forecast vs. budget          0-10 points
  - Follow-on business potential                0-8 points
  - Resource efficiency                         0-7 points

Risk (25 points)
  - Technical complexity                        0-10 points
  - Schedule realism                            0-8 points
  - Client cooperation level expectation        0-7 points

Decision Criteria:
  80+ points: Go (active participation)
  60-79 points: Conditional Go (conditional participation)
  Below 60 points: No-Go (decline)

Phase 1: Environmental Analysis (approximately 25% of total duration)
  +-- Business Environment Analysis
  |   +-- Organizational strategy and vision analysis
  |   +-- Business process analysis (BPR)
  |   +-- Stakeholder interviews
  +-- IT Status Analysis
  |   +-- Current system architecture analysis
  |   +-- IT resource inventory analysis
  |   +-- IT maturity assessment
  +-- Benchmarking
      +-- Industry peer case studies
      +-- Advanced technology trend research

Phase 2: Future Model Design (approximately 35% of total duration)
  +-- Target Architecture Design
  |   +-- Business Architecture (BA)
  |   +-- Data Architecture (DA)
  |   +-- Application Architecture (AA)
  |   +-- Technology Architecture (TA)
  +-- Gap Analysis (As-Is vs To-Be)
  +-- IT Initiative Identification

Phase 3: Execution Planning (approximately 40% of total duration)
  +-- Initiative Prioritization
  |   +-- Strategic importance
  |   +-- Urgency
  |   +-- Technical feasibility
  |   +-- Inter-initiative dependencies
  +-- Phased Roadmap
  |   +-- Short-term (within 1 year)
  |   +-- Mid-term (1-3 years)
  |   +-- Long-term (3-5 years)
  +-- Investment Budget Estimation
  +-- Governance Structure Design

Standard Proposal Table of Contents:

Part 1: Technical Section
  Chapter 1: Project Understanding
    1.1 Business Background and Environmental Analysis
    1.2 Current System Analysis
    1.3 Key Issue Identification
  Chapter 2: Proposed System
    2.1 System Architecture
    2.2 Functional Design
    2.3 Data Design
    2.4 Interface Design
    2.5 Security Design
  Chapter 3: Development Approach
    3.1 Development Methodology
    3.2 Phase-by-Phase Execution Plan
    3.3 Quality Assurance Plan

Part 2: Management Section
  Chapter 1: Project Management
    1.1 Project Organization
    1.2 Management Approach (Scope, Schedule, Quality, Risk)
    1.3 Communication Management
    1.4 Change Management
  Chapter 2: Staffing
    2.1 Organizational Chart
    2.2 Key Personnel Qualifications
    2.3 Staffing Plan
  Chapter 3: Project Schedule
    3.1 Master Schedule
    3.2 Detailed Phase Schedules

Part 3: Support Section
  Chapter 1: Training and Technology Transfer
  Chapter 2: Warranty and Maintenance
  Chapter 3: Relevant Project Experience

# Project Organization Example
project_organization:
  client:
    role: Project oversight, requirement confirmation, acceptance
    members:
      - Project Owner (PO)
      - Business stakeholders
      - IT department staff

  vendor:
    role: System analysis, design, development, testing
    members:
      PM:
        role: Overall project management
        qualification: PMP certified or 10+ years PM experience in similar projects
      PL:
        role: Technical leadership, architecture design
        qualification: Domain technology expert
      development_team:
        role: Design, development, unit testing
      QA_team:
        role: Integration testing, performance testing, quality management
      DBA:
        role: Data modeling, database tuning

  PMO:
    role: Project audit, quality oversight
    members:
      - Auditor
      - Quality management specialist

WBS Structure Example (Next-Generation System Build)

1.0 Project Management
    1.1 Initiation Phase
        1.1.1 Kickoff Report Preparation
        1.1.2 Kickoff Meeting
        1.1.3 Project Plan Development
    1.2 Execution Management
        1.2.1 Weekly Reports
        1.2.2 Monthly Reports
        1.2.3 Issue/Risk Management
    1.3 Closure Phase
        1.3.1 Final Report Preparation
        1.3.2 Final Presentation
        1.3.3 Deliverable Handover

2.0 Analysis
    2.1 Current System Analysis
        2.1.1 Business Process Analysis
        2.1.2 Data Landscape Analysis
        2.1.3 Interface Inventory Analysis
    2.2 Requirements Analysis
        2.2.1 Requirements Gathering
        2.2.2 Requirements Specification Document
        2.2.3 Requirements Review and Sign-off
    2.3 Analysis Reporting
        2.3.1 Analysis Report Preparation
        2.3.2 Analysis Phase Review Meeting

3.0 Design
    3.1 Architecture Design
    3.2 UI/UX Design
    3.3 Database Design
    3.4 Interface Design
    3.5 Design Reporting

4.0 Implementation
    4.1 Development Environment Setup
    4.2 Common Module Development
    4.3 Business Function Development
    4.4 Interface Development
    4.5 Data Migration Development

5.0 Testing
    5.1 Unit Testing
    5.2 Integration Testing
    5.3 System Testing
    5.4 Performance Testing
    5.5 User Acceptance Testing (UAT)

6.0 Deployment
    6.1 Deployment Plan
    6.2 Data Migration
    6.3 System Cutover
    6.4 Stabilization Operations

# Staffing Plan Example (12-month SI project)
staffing_plan:
  analysis_phase: # Months 1-3
    PM: 1 person (100%)
    PL: 1 person (100%)
    analysts: 3 persons (100%)
    DBA: 1 person (50%)
    total: approximately 5.5 person-months per month

  design_phase: # Months 3-5
    PM: 1 person (100%)
    PL: 1 person (100%)
    designers: 4 persons (100%)
    DBA: 1 person (100%)
    UI_designer: 1 person (100%)
    total: approximately 8 person-months per month

  implementation_phase: # Months 5-10
    PM: 1 person (100%)
    PL: 1 person (100%)
    developers: 8 persons (100%)
    DBA: 1 person (100%)
    QA: 2 persons (50%)
    total: approximately 12 person-months per month

  testing_deployment: # Months 10-12
    PM: 1 person (100%)
    PL: 1 person (100%)
    developers: 6 persons (80%)
    DBA: 1 person (100%)
    QA: 3 persons (100%)
    total: approximately 10.8 person-months per month

Function Point Estimation Procedure:

1. Identify Function Types
   - ILF (Internal Logical File)
   - EIF (External Interface File)
   - EI (External Input)
   - EO (External Output)
   - EQ (External Inquiry)

2. Assess Function Complexity
   - Low, Average, High
   - Based on DET (Data Element Types) and RET/FTR criteria

3. Calculate Unadjusted Function Points
   - Apply weights based on function type and complexity

   Weights by Function Type:
   ILF: Low=7, Average=10, High=15
   EIF: Low=5, Average=7, High=10
   EI:  Low=3, Average=4, High=6
   EO:  Low=4, Average=5, High=7
   EQ:  Low=3, Average=4, High=6

4. Apply Adjustment Factors
   - Scale adjustment, application type adjustment, language adjustment, etc.

5. Calculate Final Development Cost
   Cost per Function Point x Adjusted Function Points = Development Cost

# Man-Month Based Cost Estimation Example
labor_cost_estimation:
  grade_based_monthly_rates: # 2026 baseline (illustrative)
    professional_engineer: 12,500,000 KRW/month
    senior_engineer: 10,800,000 KRW/month
    advanced_engineer: 9,200,000 KRW/month
    intermediate_engineer: 7,600,000 KRW/month
    junior_engineer: 5,800,000 KRW/month

  staffing_plan:
    PM_senior: 12 person-months
    PL_advanced: 12 person-months
    analysts_advanced: 9 person-months (3 persons x 3 months)
    designers_intermediate: 12 person-months (4 persons x 3 months)
    developers_intermediate: 48 person-months (8 persons x 6 months)
    QA_intermediate: 9 person-months (3 persons x 3 months)
    DBA_advanced: 12 person-months

  direct_labor_total: approximately 900,000,000 KRW

total_project_cost:
  direct_labor: 900,000,000 KRW
  overhead: 990,000,000 KRW # 110% of direct labor
  technical_fee: 378,000,000 KRW # 20% of (direct labor + overhead)
  direct_expenses: 150,000,000 KRW # equipment, SW licenses, training
  total_cost: 2,418,000,000 KRW
  profit: 241,800,000 KRW # 10% of total cost
  total_project_budget: 2,659,800,000 KRW # approximately 2.66 billion KRW

ROI Calculation Framework:

1. Tangible Benefits
   - Business processing time reduction: 200M KRW/year (labor savings)
   - Manual error reduction: 50M KRW/year (rework cost savings)
   - Operational efficiency: 300M KRW/year (process automation)
   - Subtotal: 550M KRW/year

2. Intangible Benefits
   - Improved decision-making speed
   - Enhanced customer satisfaction
   - Strengthened data-driven management capability
   - Reduced regulatory compliance risk

3. ROI Calculation
   5-year total benefits: 550M KRW x 5 years = 2,750M KRW
   5-year TCO: 6,090M KRW

   Simple ROI = (Total Benefits - Total Cost) / Total Cost
              = (2,750 - 6,090) / 6,090
              = -54.8%

   However, including intangible benefits and opportunity costs:
   Adjusted total benefits: 1,500M KRW/year (including intangible benefits)
   5-year adjusted benefits: 7,500M KRW

   Adjusted ROI = (7,500 - 6,090) / 6,090 = 23.2%
   Break-even Point (BEP): Approximately 4 years and 1 month

# SLA Definition Example
service_level_agreement:
  service_availability:
    target: 99.95%
    measurement_period: monthly
    excluded_time: planned maintenance (2nd Sunday monthly 02:00-06:00)
    calculation: '(Total service time - Downtime) / Total service time x 100'
    penalties:
      99.90_to_99.95: 5% reduction of monthly maintenance fee
      99.50_to_99.90: 10% reduction of monthly maintenance fee
      below_99.50: 20% reduction of monthly maintenance fee

  response_time:
    online_transactions: average under 3 seconds (under 5 seconds during peak)
    batch_processing: completed within designated time window
    report_generation: within 30 seconds

  incident_response:
    critical: response within 30 minutes, resolution within 4 hours
    major: response within 1 hour, resolution within 8 hours
    minor: response within 4 hours, resolution within 24 hours
    informational: response within 8 hours, resolution within 3 business days

SLA Improvement Cycle (PDCA):

Plan
  - Define SLA metrics and target levels
  - Establish monitoring framework
  - Stakeholder alignment

Do
  - SLA-based service operations
  - Real-time monitoring
  - Incident response process execution

Check
  - Monthly/quarterly SLA achievement analysis
  - Root cause analysis for non-compliance items
  - Trend analysis and forecasting

Act
  - Identify and execute improvement initiatives
  - Adjust SLA standards (as needed)
  - Optimize operational processes