<!-- تعليمات النموذج الذكي: املأ مواضع [ أضف التفاصيل... ] استنادًا إلى سياق المشروع.

تعريف وسياق:
طلب تقديم العروض يدعو الموردين إلى التنافس على العمل، وهو الوثيقة التي تجعل المنافسة ذات معايير محددة. ويبين ما يُشترى وما يجب على المورد إثباته، وكيفية التعامل مع العروض المقدمة، والمعايير التي يقاس بها كل عرض مع الوزن الذي يحمله كل معيار.

يستقبل من:
*  استراتيجية المشتريات، التي تحدد ما سيُشترى وبأي شروط
*  معايير اختيار المصدر، التي يجب أن تتبعها طريقة التقييم
*  ميثاق المشروع، لأن أهدافه هي ما يجب أن يخدمه العمل المشترى

يقدم معلومات إلى:
*  بيان العمل، الذي يكتب من واقع العرض الفائز ولا يمكن أن يخالف ما طُلب هنا
*  تقرير إغلاق العقد، الذي يقرأ ما تم تسليمه فعليًا مقابل ما تم الاتفاق عليه هنا
*  بطاقة أداء المورد، إذ يقاس الأداء بالمتطلبات المحددة هنا


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


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

توجيهات استيفاء الأقسام:
*  طلب العروض والنطاق: ما يُشترى ومن أذن بالطلب، مع فصل المتطلبات الوظيفية عن غير الوظيفية. العملية والتقييم: كيفية تقديم العروض والتعامل معها، والمعايير الموزونة مع أوزانها.
-->

<h3 align="left">{{اسم_الشركة}}</h3>
<h2 align="left">{{اسم_المشروع}} - {{معرف_المشروع}}</h2>
<h1 align="center">طلب تقديم العروض</h1>

| **تاريخ الإعداد:** {{التاريخ_الحالي}} | **مدير المشروع:** {{اسم_مدير_المشروع}} | **إعداد:** {{معد_الوثيقة}} |
| ---: | ---: | ---: |

---

## طلب العروض والنطاق

### الغرض والصلاحية

[ أضف التفاصيل... ]

---

### نظرة عامة على المشروع

[ أضف التفاصيل... ]

---

### نطاق العمل

[ أضف التفاصيل... ]

---

### التسليمات والجدول الزمني

[ أضف التفاصيل... ]

---

### المتطلبات الفنية

[ أضف التفاصيل... ]

---

### المتطلبات التجارية

[ أضف التفاصيل... ]

---

## العملية والتقييم

### متطلبات التقديم

[ أضف التفاصيل... ]

---

### معايير وأوزان التقييم

[ أضف التفاصيل... ]

---

### الاستفسارات والتوضيحات

[ أضف التفاصيل... ]

---

### الترسية والتعاقد

[ أضف التفاصيل... ]

---

### الاعتماد والموافقات

| الدور | الاسم | التوقيع | التاريخ |
| ---: | ---: | ---: | ---: |
| **مدير المشتريات** | {{اسم_مدير_المشتريات}} | _______________________ | [.... -.... -.... ] |
| **مدير المشروع** | {{اسم_مدير_المشروع}} | _______________________ | [.... -.... -.... ] |
| **رئيس لجنة المناقصات والمشتريات** | {{اسم_رئيس_لجنة_المناقصات}} | _______________________ | [.... -.... -.... ] |
---

<div align="left" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>سجل التدقيق الإلكتروني: Hash SHA256: {{رمز_تجزئة_التدقيق_SHA256}}</span> <br>
 <strong>النموذج:</strong> طلب تقديم العروض | <strong>المرجع:</strong> PMO-04.09.05 <br>
 <i>تاريخ الإنشاء: {{وقت_الإنشاء}}, بواسطة <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">تسليمات</a></i>
</div>
</div>

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://tasleemat.pmo/schemas/completed/PMO-04.09.05.schema.json",
  "title": "Completed Request for Proposal Data Contract",
  "description": "Additive structural schema validating completed Request for Proposal artifact data payloads (PMO-04.09.05).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-04.09.05"
    },
    "metadata": {
      "type": "object",
      "properties": {
        "project_name": {
          "type": "string",
          "minLength": 1
        },
        "project_code": {
          "type": "string"
        },
        "date_prepared": {
          "type": "string",
          "format": "date"
        },
        "project_manager": {
          "type": "string",
          "minLength": 1
        },
        "prepared_by": {
          "type": "string",
          "minLength": 1
        },
        "version": {
          "type": "string"
        },
        "status": {
          "type": "string",
          "enum": [
            "draft",
            "baselined",
            "in_review",
            "approved"
          ]
        }
      },
      "required": [
        "project_name",
        "date_prepared",
        "project_manager",
        "prepared_by"
      ]
    },
    "invitation_and_scope": {
      "type": "object",
      "properties": {
        "purpose_and_authority": {
          "type": "string",
          "minLength": 1,
          "description": "What this request is authorised to invite, and by whom. The authority clause is what makes the contest defensible: it names the instrument that authorised the procurement, so a later reader can tell an invitation the organisation is entitled to issue from a document somebody drafted because they wanted something."
        },
        "project_overview": {
          "type": "string",
          "minLength": 1,
          "description": "The background, the objectives, and the outcome being bought - enough that a supplier who has never heard of the organisation can decide whether this is work they want. A request that describes deliverables without describing the problem produces proposals that are technically compliant and solve something nobody had."
        },
        "scope_of_work": {
          "type": "string",
          "minLength": 1,
          "description": "The work and the boundaries of it, described so that two suppliers would propose the same work from this description alone. The exclusions matter as much as the inclusions, because an omission reads as an inclusion and the supplier who priced it that way is the one whose price becomes impossible to deliver."
        },
        "deliverables_and_schedule": {
          "type": "string",
          "minLength": 1,
          "description": "What will be handed over and by when, milestone by milestone. A supplier prices the schedule it is given, so a schedule stated only as a total duration invites every supplier to assume its own plan and the evaluation to compare plans that were never compared."
        },
        "technical_requirements": {
          "type": "string",
          "minLength": 1,
          "description": "The functional and non-functional requirements the solution must satisfy, separated because they are evaluated differently: a function that is missing is a gap, whereas a performance target that is missed is a shortfall, and a form that treats them as one list cannot say which of the two has occurred."
        },
        "commercial_requirements": {
          "type": "string",
          "minLength": 1,
          "description": "The pricing structure, the currency, what is included and what is billed separately, and the period the price holds for. A request that asks for a price without saying what it must include produces responses that are not comparable, and the cheapest one is then the one that left the most out."
        }
      },
      "required": [
        "purpose_and_authority",
        "project_overview",
        "scope_of_work",
        "deliverables_and_schedule",
        "technical_requirements",
        "commercial_requirements"
      ]
    },
    "process_and_evaluation": {
      "type": "object",
      "properties": {
        "submission_requirements": {
          "type": "string",
          "minLength": 1,
          "description": "How a proposal must be submitted and by when, in a form the buyer can actually open: who may submit, what the deadline means, whether a proposal may be withdrawn before the deadline, and what happens to one that arrives late. Each of these is a point at which a well-meaning supplier can be turned away by accident, and an accident at this point is indistinguishable from a rigged contest."
        },
        "evaluation_criteria_and_weights": {
          "type": "string",
          "minLength": 1,
          "description": "The criteria the proposals will be scored against, each with the weight it carries and what a high score looks like. This is the clause that decides whether the contest was real. Criteria published after the bids are in are not criteria but a justification, and no supplier can appeal to them because no supplier saw them; a stated weight also stops a criterion nobody expected from deciding the outcome."
        },
        "clarifications_and_questions": {
          "type": "string",
          "minLength": 1,
          "description": "How questions are asked, answered, and published, and the date the answer period closes. Two rules carry this section: every answer goes to every supplier, because an answer given to one is a private amendment to the requirement; and the question period closes before submissions open the work of pricing, because a question answered late is answered to whoever has already committed their number."
        },
        "award_and_contract": {
          "type": "string",
          "minLength": 1,
          "description": "How the successful supplier is chosen, what happens next, and what the award does and does not commit anyone to. Naming the route from award to statement of work is what stops the gap between winning and signing from becoming a second negotiation with no rules."
        }
      },
      "required": [
        "submission_requirements",
        "evaluation_criteria_and_weights",
        "clarifications_and_questions",
        "award_and_contract"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "invitation_and_scope",
    "process_and_evaluation"
  ]
}

{
  "form_name": "Request for Proposal",
  "document_reference": "PMO-04.09.05",
  "_llm_instructions": "Populate the fields of 'Request for Proposal' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.09.05.",
  "fields": {
    "f01_Purpose_and_Authority": {
      "section": "Invitation and Scope",
      "label": "Purpose and Authority",
      "guidance": "What this request is authorised to invite, and by whom. The authority clause is what makes the contest defensible: it names the instrument that authorised the procurement, so a later reader can tell an invitation the organisation is entitled to issue from a document somebody drafted because they wanted something.",
      "value": ""
    },
    "f02_Project_Overview": {
      "section": "Invitation and Scope",
      "label": "Project Overview",
      "guidance": "The background, the objectives, and the outcome being bought - enough that a supplier who has never heard of the organisation can decide whether this is work they want. A request that describes deliverables without describing the problem produces proposals that are technically compliant and solve something nobody had.",
      "value": ""
    },
    "f03_Scope_of_Work": {
      "section": "Invitation and Scope",
      "label": "Scope of Work",
      "guidance": "The work and the boundaries of it, described so that two suppliers would propose the same work from this description alone. The exclusions matter as much as the inclusions, because an omission reads as an inclusion and the supplier who priced it that way is the one whose price becomes impossible to deliver.",
      "value": ""
    },
    "f04_Deliverables_and_Schedule": {
      "section": "Invitation and Scope",
      "label": "Deliverables and Schedule",
      "guidance": "What will be handed over and by when, milestone by milestone. A supplier prices the schedule it is given, so a schedule stated only as a total duration invites every supplier to assume its own plan and the evaluation to compare plans that were never compared.",
      "value": ""
    },
    "f05_Technical_Requirements": {
      "section": "Invitation and Scope",
      "label": "Technical Requirements",
      "guidance": "The functional and non-functional requirements the solution must satisfy, separated because they are evaluated differently: a function that is missing is a gap, whereas a performance target that is missed is a shortfall, and a form that treats them as one list cannot say which of the two has occurred.",
      "value": ""
    },
    "f06_Commercial_Requirements": {
      "section": "Invitation and Scope",
      "label": "Commercial Requirements",
      "guidance": "The pricing structure, the currency, what is included and what is billed separately, and the period the price holds for. A request that asks for a price without saying what it must include produces responses that are not comparable, and the cheapest one is then the one that left the most out.",
      "value": ""
    },
    "f07_Submission_Requirements": {
      "section": "Process and Evaluation",
      "label": "Submission Requirements",
      "guidance": "How a proposal must be submitted and by when, in a form the buyer can actually open: who may submit, what the deadline means, whether a proposal may be withdrawn before the deadline, and what happens to one that arrives late. Each of these is a point at which a well-meaning supplier can be turned away by accident, and an accident at this point is indistinguishable from a rigged contest.",
      "value": ""
    },
    "f08_Evaluation_Criteria_and_Weights": {
      "section": "Process and Evaluation",
      "label": "Evaluation Criteria and Weights",
      "guidance": "The criteria the proposals will be scored against, each with the weight it carries and what a high score looks like. This is the clause that decides whether the contest was real. Criteria published after the bids are in are not criteria but a justification, and no supplier can appeal to them because no supplier saw them; a stated weight also stops a criterion nobody expected from deciding the outcome.",
      "value": ""
    },
    "f09_Clarifications_and_Questions": {
      "section": "Process and Evaluation",
      "label": "Clarifications and Questions",
      "guidance": "How questions are asked, answered, and published, and the date the answer period closes. Two rules carry this section: every answer goes to every supplier, because an answer given to one is a private amendment to the requirement; and the question period closes before submissions open the work of pricing, because a question answered late is answered to whoever has already committed their number.",
      "value": ""
    },
    "f10_Award_and_Contract": {
      "section": "Process and Evaluation",
      "label": "Award and Contract",
      "guidance": "How the successful supplier is chosen, what happens next, and what the award does and does not commit anyone to. Naming the route from award to statement of work is what stops the gap between winning and signing from becoming a second negotiation with no rules.",
      "value": ""
    }
  }
}