مراقبة مخاطر الموردين والمورّدين

المتطلبات تصف قدرات يحتاجها النمط في بيئتك، مو الموردين اللي لازم تشتريهم. أي نظام يملأ متطلباً يحقّقه — وهذا اللي يخلّي الكتالوج قابلاً للنقل عبر الذيل الطويل من أدوات الشركات الصغيرة والمتوسطة.

1. vendor_master

   مطلوبقراءةطلب

   The list of vendors being monitored, with the context that matters.

   شكل البيانات

   Per-vendor: legal name, business identifiers, contract terms, spend, criticality tier, contact owners.
   يُملأ عادةً بواسطة

   • vendor master in the ERP or procurement system
   • contract management system with vendor records
   • vendor onboarding database
2. external_risk_signal_sources

   مطلوبقراءةدفعة

   Public sources of risk-relevant data: news, regulatory filings, security advisories, ratings.

   شكل البيانات

   Per-vendor signals with source, date, signal type, severity hint.
   يُملأ عادةً بواسطة

   • news monitoring service with vendor entity matching
   • credit rating feed
   • security advisory feeds
   • regulatory filing alerts
   • data breach notification services
3. internal_performance_signal

   مطلوبقراءةدفعة

   How the vendor is performing in the actual relationship: deliveries, defect rates, response times, invoicing accuracy.

   شكل البيانات

   Per-vendor performance metrics over time with thresholds and trend.
   يُملأ عادةً بواسطة

   • procurement system with delivery and quality records
   • AP system with invoicing accuracy data
   • internal SLA tracking
   • contract management system with performance attestations
4. compliance_artifact_tracker

   مطلوبقراءةمجموعة

   Vendor-provided compliance documents and their expiration: certifications, insurance, financial statements.

   شكل البيانات

   Per-vendor per-document: type, valid-from, valid-to, status (current/expiring/expired).
   يُملأ عادةً بواسطة

   • compliance document store in the procurement system
   • vendor portal where they submit certifications
   • structured tracking in the GRC system
5. risk_destination

   مطلوبكتابةحدث

   Where rising risk signals surface for the vendor owners and procurement team.

   شكل البيانات

   Per-vendor risk score with reason codes, evidence, suggested actions, priority based on vendor criticality and risk severity.
   يُملأ عادةً بواسطة

   • risk view in the procurement system
   • weekly digest to vendor owners
   • chat alerts for material changes
6. incident_response_route

   مطلوبكتابةحدث

   Where confirmed high-severity issues go for immediate action: supplier on hold, contract review, contingency activation.

   شكل البيانات

   Incident with full context, suggested response options, financial and operational impact estimate.
   يُملأ عادةً بواسطة

   • procurement leadership alerts with clear action options
   • incident management process in the GRC system
   • structured escalation to procurement, legal, and finance