Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: No Action
    • Labels:
      None
    • Environment:

      Data Model

    • Proposal:
      Hide

      Ned Preaward Catalogue Request - with also the above elements

      Show
      Ned Preaward Catalogue Request - with also the above elements

      Description

      one of TC440 main objective is a stand-alone pre-award catalogue request
      message. This is a message used by the contracting authority to describe
      the requirements on the items the contracting authority intends to
      tender. Up to now, the pre-award catalogue request was part of the Call
      for tenders message and thus bound to the Call for tenders message of
      UBL. As it should be now a stand-alone message, we can't use the Call
      for tenders message anymore. As an alternative we consider the UBL's
      catalogue request message. But as you may be know, this message is
      intended to be used in post-award processes, for instance, in BII's
      multi-party catalogue profile. So, there are some business terms in the
      transaction model that can't be bound to an appropriate syntax element
      of UBL's catalogue request message. The most important business terms are

      • Item request minimum price
      • Item request maximum price
      • (Requested) Delivery period
      • Item property request description (cac:AdditionalProperty has no
        description element)
      • Item property request classification (with cardinality of 0..* instead
        of 0..1 of cac:Item/cac:AdditionalProperty/cbc:NameCode
      • Estimated value
      • Total budget amount

        Attachments

          Activity

            People

            • Assignee:
              gkholman Ken Holman
              Reporter:
              olema@digst.dk Ole Madsen (Inactive)
            • Watchers:
              2 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: