인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
디자인 및 창작 · SKILL.md

e-procurement-strategy

e-procurement-strategy

Design e-procurement strategies — platform evaluation, workflow digitization, catalog management, approval automation, and adoption planning. TRIGGER when: user says /e-procurement-strategy or asks about digital procurement.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: e-procurement-strategy description: > Design e-procurement strategies — platform evaluation, workflow digitization, catalog management, approval automation, and adoption planning. TRIGGER when: user says /e-procurement-strategy or asks about digital procurement. argument-hint: "[procurement process to digitize]" user-invocable: true

E-Procurement Strategy

Process

Step 1: Assess Current State

DimensionAssessment
Manual processesWhich procurement steps are paper/email-based?
SystemsCurrent tools (ERP, spreadsheets, email)
Pain pointsSlow approvals, maverick spend, poor visibility
VolumePurchase orders per month, suppliers managed

Step 2: Evaluate Platforms

CriteriaWeightPlatform APlatform B
Requisition to PO20%X/10X/10
Catalog management15%X/10X/10
Approval workflows15%X/10X/10
Supplier portal15%X/10X/10
ERP integration20%X/10X/10
Reporting/analytics15%X/10X/10

Step 3: Design Digital Workflows

ProcessCurrentTargetAutomation
RequisitionEmail formSelf-service portalAuto-routing
ApprovalEmail chainRule-based workflowAuto-approve under threshold
PO creationManual entrySystem-generatedAuto-PO for catalog items
Invoice matchingManual3-way matchAuto-match and pay

Step 4: Plan Adoption

PhaseDurationScope
Pilot1-2 monthsOne department, top suppliers
Expand2-3 monthsAll departments
OptimizeOngoingAdvanced features, analytics

Output Format

## E-Procurement Plan
### Current State: [Pain points and volumes]
### Platform: [Recommendation with rationale]
### Workflows: [Digitization plan]
### Timeline: [Phased rollout]
### ROI: [Expected savings and efficiency gains]

Quality Checklist

  • Current pain points documented
  • Platform evaluated against requirements
  • Workflows designed for automation
  • Adoption plan includes training
  • ROI estimated

Edge Cases

  • For small organizations, lightweight tools may suffice over full P2P suites
  • If ERP integration is critical, prioritize native connectors
  • For regulated industries, ensure audit trail capabilities
저장한 Skills