مُصمِّم نموذج التشغيل بالذكاء الاصطناعي

نظرة عامة

الفوائد

ماذا يفعل

• يُقيّم كل عملية من حيث إمكانية تسليمها

  التكرار، والانضباط بالقواعد، وتوافر الأدلة، وتكلفة الخطأ. معظم الشركات تفشل في واحد منها على الأقل، والمخطط لا يفحص ذلك أبدًا.

• يصمم التسليمات، لا الصناديق

  ما ينتجه كل وكيل، ومن يراجعه، وما يحدث عند وقوع خطأ، والإنسان المحدد بالاسم الذي يملك النتيجة. العمل يعيش في الأسهم.

• يحدد ما يجب أن يبقى بشريًا

  عمل متكرر ومحكوم بقواعد ومع ذلك يجب ألا يُسلَّم. أثمن قائمة في التقرير، والقائمة التي لا ينشرها أحد.

• يرتب التسلسل بحسب التبعية والعائد

  لا بحسب القسم ولا بحسب الحماس. بعض العمل لا يمكن أن يبدأ إلا بعد وجود بيانات غير موجودة حاليًا، وهو يُصرّح بذلك.

• يحدد ما يجب أن يكون صحيحًا أولًا

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

• لا يُنشئ شيئًا

  لا يغيّر أي تنظيم، ولا يشتري شيئًا، ولا يضبط شيئًا. كل مخرجاته خطة يقرر بشأنها أشخاص.

ما الذي يتغيّر

كيف يعمل

يعمل هذا الوكيل على الخادم عبر بيئة تشغيل PROMIVO. يُسجَّل كل تشغيل خطوة بخطوة، ويُفحص إذن كل استدعاء أداة قبل تنفيذه.

1. 1المدخليُتحقَّق منه وفق مخطّط مدخلات الوكيل
2. 2النموذجclaude-opus-5 مع تحويل احتياطي تلقائي
3. 3الأدواتsearch_knowledge, extract_structured_data
4. 4الصلاحياتينفّذ إجراءات READ تلقائيًا؛ وما فوقها ينتظر الموافقة
5. 5المخرجنتيجة منظّمة مطابقة لمخطّط المخرجات
6. 6التسجيلالرموز والمدة وكل خطوة مسجّلة

عرض توضيحي

بيانات تجريبيةIllustrative sample output, abridged.

{
  "company": "A dealership group",
  "currency": "USD",
  "industry": "Automotive retail and service",
  "headcount": 240,
  "departments": []
}

{
  "escalate": true,
  "sequence": [
    {
      "phase": "First — read-only, evidence already exists",
      "unblocks": "Nothing depends on these, which is why they go first: they return value while the harder prerequisites are being cleared.",
      "processes": [
        "Warranty claim documentation check",
        "Duplicate payment review"
      ],
      "prerequisitesToClearFirst": [
        "Load the manufacturer's warranty standard into a knowledge base."
      ]
    },
    {
      "phase": "Second — needs data that does not exist yet",
      "unblocks": "Capacity planning across all four sites.",
      "processes": [
        "Technician utilisation analysis"
      ],
      "prerequisitesToClearFirst": [
        "Job times are recorded on paper at two sites. Until that changes, no analysis of this is possible and no agent fixes it."
      ]
    }
  ],
  "disclaimer": "A design, not a deployment. Nothing has been configured, purchased or enabled; no headcount reduction is estimated and no recommendation is framed as replacing a role; savings are estimates from the figures you supplied and are stated net of the effort to supervise them; and no vendor or product is named.",
  "assumptions": [
    "Hours removed are calculated from the run frequency and durations you supplied, and are estimates.",
    "Supervision effort assumes one reviewer per recommendation."
  ],
  "recommended": [
    {
      "process": "Warranty claim documentation check before submission",
      "readOnly": true,
      "department": "Service",
      "buildEffort": "Days",
      "whoChecksIt": "The warranty administrator, who already reviews the claim run.",
      "prerequisite": "The manufacturer's documentation standard has to be in a knowledge base. It currently exists as a PDF on one person's laptop.",
      "agentProduces": "A list of claims that would fail, with the specific element missing from each.",
      "agentReceives": "Repair orders with narrative, operation codes, parts and technician certifications.",
      "whenItIsWrong": "A claim is submitted that would have failed anyway, or a good claim is queried. Both cost minutes, not money.",
      "accountableRole": "Service Manager",
      "capabilityNeeded": "Read each repair order against the manufacturer's documentation standard and report what would be reversed at audit.",
      "netOfSupervision": 44,
      "runEffortPerMonth": "About 2 hours of review",
      "hoursRemovedPerMonth": 46
    }
  ],
  "countHonesty": "Six recommendations from 41 processes reviewed. A diagram of this company would have shown one agent per role and produced around forty. Thirty-five of those touch work that runs under twice a month, has no exportable evidence, or must stay human — and each would still have been something to configure, pay for and watch.",
  "mustStayHuman": [
    {
      "reason": "Frequent enough and rule-bound enough to look automatable. It decides an employment outcome, and a wrong call ends someone's job on a machine's say-so.",
      "process": "Deciding a technician's disciplinary outcome after a workshop incident",
      "department": "People",
      "couldAnAgentHelpAtAll": "It can assemble the evidence pack — records, timelines, policy clauses — so the person deciding has everything. It must not weigh it."
    },
    {
      "reason": "A licensed technician's signature is the product. Nothing here can carry it.",
      "process": "Signing off a vehicle as roadworthy after repair",
      "department": "Service",
      "couldAnAgentHelpAtAll": "It can check the job record is complete before it reaches them, which is a paperwork step and not a judgement."
    }
  ],
  "escalationReason": "Two processes the brief asked to automate decide employment and licensed sign-off outcomes, and one recommendation depends on job times that are currently recorded on paper.",
  "notAnAgentProblem": [
    "Chasing parts orders takes 30 hours a month because the supplier portal has no export. Fixing the export removes the work entirely; an agent would automate a workaround and make it permanent.",
    "Two teams re-key the same customer record. That is one integration, not an agent."
  ]
}

المتطلبات

حالات الاستخدام

التسعير

الأسئلة الشائعة

التقييمات

تُفتح التقييمات بعد أن يشغّل العملاء هذا الوكيل.