CCapability-led route

ContextCapture Plattform

BEW Berliner Energie und Wärme GmbH

Deadline
01 Sept 2026, 12:00
Value
The official eForms notice contains a EUR 1 placeholder; no usable procurement estimate is published.
Region
Berlin, Germany (NUTS DE300)
Reviewed
16 Aug 2026
Portfolio verdict

Capability-led route

Tier C and no-prime. The technical scope overlaps Digital David's OCR, GIS, integration and secure-cloud capabilities, but the buyer explicitly requires a mature market-tested industrial 3D product. Digital David alone also fails the hard EUR 1.2 million total-turnover threshold in both verified years 2024 and 2025; other financial, reference, headcount, insurance, certification and named-team gates remain unknown because the qualification pack does not contain that evidence.

Recommended actionDo not submit as prime. The company is not eligible alone because the verified 2024 and 2025 turnover is below the EUR 1.2 million annual minimum. Consider only a partner-led route with a mature industrial 3D platform vendor that independently covers the turnover, ContextCapture revenue, headcount, reference, insurance, certification and operating gates before the 21 August 2026 question deadline.

What the opportunity means

Provide, implement and support a mature central platform for 3D representations of BEW energy plants, including point clouds, POIs, OCR, measurements, plant-system integrations, security controls and optional on-premises or SaaS deployment.

Portfolio thesis

OCR-in-point-cloud, GIS/georeferencing, APIs, data workflows, Azure deployment and secure integration align with demonstrated competencies. The procurement nevertheless requires an existing industrial 3D product, two highly specific plant references, ISO 27001 certification, a 15-FTE organisation and financial scale that the company evidence does not meet or prove.

Qualification reality

Digital David demonstrates OCR, GIS, secure integration and complex web-platform delivery, but has no existing mature, market-tested ContextCapture/industrial 3D product. More decisively, verified 2024 and 2025 total turnover is below the mandatory EUR 1.2 million in each year, so Digital David alone fails a hard participation gate.

Portfolio evidence

Products and reusable delivery strengths

Products

Mimirholz-platformUroboros

Competencies

OCR and document intelligencegeospatial and GIS decision supportsecure cloud and systems integrationAPI and data-platform engineeringobservability and operated software quality

Decision gates

Eligibility and delivery gates

  • Company matchMet
    Commercial-register evidence
    MustRequired

    Digital David AG's commercial-register entry is documented in the company qualification pack.

  • Company matchUnknown
    Current bank reference
    MustRequired

    A bank reference no older than three months must be submitted; the evidence pack contains none.

  • Company matchUnknown
    Business liability insurance
    MustRequired

    A policy no older than six months with at least EUR 2 million for property damage and EUR 2 million for personal injury is required. No insurance evidence is present.

  • Company matchUnknown
    Professional financial-loss insurance
    MustRequired

    A policy no older than six months with at least EUR 2 million for financial loss is required. No insurance evidence is present.

  • Company matchNot met
    Total turnover 2023-2025
    MustRequired

    At least EUR 1.2 million total turnover is required in each of 2023, 2024 and 2025. Verified company evidence records EUR 754,500 for 2024 and EUR 874,992.76 for 2025, both below the hard annual threshold; 2023 is not documented.

  • Company matchUnknown
    ContextCapture-platform revenue
    MustRequired

    At least EUR 600,000 revenue in the ContextCapture-platform field is required in each of 2023, 2024 and 2025. The evidence pack has no field-specific revenue split and no 2023 figure.

  • Company matchUnknown
    Permanent workforce and developers
    MustRequired

    At least 15 permanent full-time employees in both 2025 and 2026, including at least three developers, are required. Expert-team evidence is deferred and the qualification pack contains no admissible headcount proof; personnel expense and portfolio descriptions are not used to infer it.

  • Company matchUnknown
    Two comparable industrial-plant references
    MustRequired

    Two 2023-2025 references are required, one completed after 1 January 2024, covering process/production plants with interior and exterior areas, stated area and point counts, customised UX/OCR/object-recognition features, and full reference contacts. No approved reference evidence pack exists.

  • Company matchPartially met
    Established operations and security management
    MustRequired

    The portfolio demonstrates operated cloud software, observability and secure integration, but the submission requires evidence of a multi-level support and escalation model, binding product roadmap, regular penetration tests, continuous monitoring and active vulnerability management for the offered platform. The qualification pack does not prove that complete bundle.

  • Company matchUnknown
    Information-security training
    MustRequired

    Regular employee information-security training must be declared. The evidence pack contains no training record.

  • Company matchUnknown
    Germany/EWR data residency
    MustRequired

    All data must be stored exclusively in Germany or the EEA. No offered deployment or subprocessor evidence exists for this tender.

  • Company matchUnknown
    Certified ISMS
    MustRequired

    A valid ISO/IEC 27001 or equivalent accredited certification and Statement of Applicability must cover the organisation, processes and systems material to delivery. The qualification pack records no certifications.

  • Company matchUnknown
    Project-language evidence
    MustRequired

    Every proposed project person must have C2 English and at least one must have C2 German. Named-expert evidence is deferred and no admissible language proof exists.

  • Company matchUnknown
    Exclusion, supplier-code, sanctions, subcontractor and origin declarations
    MustRequired

    Registers B-G and tender-specific declarations must be completed by every relevant economic operator. The company pack does not pre-authorise these tender-specific declarations.

  • Company matchUnknown
    Signed confidentiality declaration
    MustRequired

    Each applicant/consortium member must sign and submit the buyer's current confidentiality form with the participation request.

  • Company matchNot covered
    Mature market-tested ContextCapture product
    DeliveryNot required

    The complete portfolio map shows relevant OCR, GIS and integration competencies but no existing mature industrial 3D ContextCapture platform. The specification explicitly requires a mature, market-tested product, so a greenfield Digital David prime route is incompatible; a product partner would be required.

  • Company matchUnknown
    Solution Selection mandatory controls
    DeliveryNot required

    The current workbook contains extensive mandatory functional, architectural, security, SaaS, incident-management and continuity rows. Compliance can only be assessed against a selected mature product; no product response exists.

Official clarifications · selected by AI relevance

Relevant bidder questions

  1. Q1Which confidentiality and data-processing documents are required with the participation request?
    Buyer answer

    The confidentiality declaration must be completed, signed and submitted with the participation request. The Article 28 data-processing agreement is informational in phase 1 and becomes relevant and contractual in the offer phase.

    Portfolio impact

    A signed confidentiality declaration is an immediate phase-1 submission. The AVV must be reviewed for the later solution and supply-chain design but is not yet a signed phase-1 deliverable.

  2. Q2Were hidden rows in Annexes 2 and 3 intentional, and is a pilot or cost-neutral proof of concept planned?
    Buyer answer

    The buyer supplied an adjusted Annex 2 after the hidden-row issue. A pilot/PoC question is not relevant to the participation phase and will only be answered in the later offer phase.

    Portfolio impact

    The current revised Solution Selection workbook must be used. A bidder cannot assume a paid or cost-neutral PoC route when sizing bid cost or product readiness.

  3. Q3What proportion of the stated estate already has scans, 3D point clouds or 360-degree photographs?
    Buyer answer

    The buyer considers this irrelevant to the participation stage and will answer it only in the offer phase.

    Portfolio impact

    The ingestion and migration volume remains unknown, so implementation effort and storage sizing cannot yet be completed.

  4. Q5Does the revised workbook contain 67 SaaS rows, 278 Solution Selection rows and a maximum of 1,159 points?
    Buyer answer

    The buyer did not confirm those counts; it issued another revised Annex 2 dated 10 August 2026.

    Portfolio impact

    The latest official revision controls and must be rechecked for every mandatory row; prior hidden or counted rows cannot be relied upon.

  5. Q6Where must participation forms and mandatory evidence be uploaded, and how are the acknowledgement and criterion checkboxes completed?
    Buyer answer

    Upload all relevant and mandatory documents under 'Eigene Anlagen'; acknowledging all attachments requires no further action. Select 'Ja' for a criterion when the corresponding form has been completed and can be submitted. Registers B-G are uploaded under 'Eigene Anlagen'.

    Portfolio impact

    The phase-1 package must be assembled and named against the register structure; checking portal boxes alone does not supply the evidence.

  6. Q7Can the four E57 plant datasets intended for the test environment be provided before the offer?
    Buyer answer

    No. The question is deferred at participation stage and retrieval of the datasets during the offer phase is not planned.

    Portfolio impact

    Product fitness against the buyer's four acceptance datasets cannot be validated before bidding; this increases technical and presentation risk for any partner solution.

Interpreted scope

Delivery shape

  • Provide a mature, market-tested central platform for visualising and using 3D representations of BEW process and production plants, indoors and outdoors.
  • Ingest and manage point clouds and models including E57, IFC and CAD, with project-level revision/history management, 360-degree and overview navigation, search, filters and measurement tools.
  • Create, geolocate, navigate, filter, import and manage points of interest, including media and links to plant systems.
  • Integrate SAP PM, DAISY DMS, Aveva PI and COMOS, including bidirectional COMOS access and documented, testable, versioned APIs or scripting interfaces.
  • Use OCR to recognise KKS and other labels in imagery, position text in the point-cloud model and export recognised text as XML or JSON for downstream integration.
  • Deploy preferably in BEW's own Windows/RHEL/Azure/Azure Stack HCI/AKS environment, or conditionally as SaaS, and deliver installation, configuration, release management, security and operational support.
  • Provide a test instance using four buyer E57 datasets, technical and security concepts, training for 11 key users, a product roadmap, support structures and a 99.5% service level.

Bid package

Required submissions

  • German-language electronic participation request through Deutsche eVergabe by 1 September 2026 at 12:00
  • Register A: covering letter and company presentation including complete group and ownership structure
  • Registers B-E: competition-register information, mandatory/facultative exclusion declarations, BEW supplier-code acceptance and Russia-sanctions declaration on the buyer's form
  • Register F: subcontractor declaration, including a signed no-subcontractor notation if none are planned
  • Register G: company-origin declaration for every economic operator
  • Bank reference no older than three months
  • Current business-liability and professional-financial-loss insurance policies meeting the EUR 2 million limits
  • Turnover declarations for total and ContextCapture-platform revenue for 2023, 2024 and 2025
  • Headcount declaration for 2025 and 2026, including developer count
  • Register K with two qualifying references and complete reference-contact data
  • Evidence of operational/support processes, roadmap, penetration testing, monitoring and vulnerability management
  • Declarations/evidence for security training, Germany/EEA data storage and ISO 27001/equivalent certification plus SoA
  • Proof of C2 English for all project personnel and C2 German for at least one proposed project member
  • Signed buyer confidentiality declaration for every applicant/consortium member
  • Capacity-provider evidence and commitment declarations at phase 1 if relying on another undertaking
  • All files uploaded under 'Eigene Anlagen', structured and named against the register/criterion headings; the full participation package is in German

Commercial reading

Contract and pricing terms

  • The official notice describes a three-year framework agreement with renewed competition and one 12-month extension option; the exact phase-2 contract form remains to be finalised.
  • The price sheet evaluates either preferred deployment in BEW's environment or SaaS, enterprise licensing, an option for 10 additional concurrent users, interfaces to SAP PM/COMOS/Aveva PI/DMS, key-user training, and senior developer, junior developer and project-manager rates.
  • All required software, licences and certificates must be identified and priced; installation/configuration belongs in project costs, while operation and updates belong in recurring charges.
  • Electronic invoicing is required and payment is 30 days net. General terms state prices are net plus applicable VAT and travel time is not remunerated unless otherwise agreed.
  • Annual solution availability is 99.5%. Service credits are 1% of annual volume at 98.5-99.5%, 5% below 98.5% to 96.5%, and 10% below 96.5%; repeated class 3/4 breaches and average annual availability below 95% support early termination.
  • Regular support hours are 08:00-16:30 on Berlin working days. The published service table sets incident recovery below five working days, disaster-recovery recovery below 20 working days and defined priority-2/3 response and resolution targets.
  • The supplier bears end-to-end responsibility for product, integrations, third-party modules, security, maintenance and continued support. Subcontractor security obligations must flow down and BEW retains audit rights.
  • The EUR 1 notice value is a placeholder and must not be used for bid economics. Existing-scan proportions, pilot/PoC terms and four E57 acceptance datasets are not available in phase 1.

Evidence trail

Sources and bidder information

Authoritative Deutsche eVergabe public bidder communication checked on 2026-08-16T22:22:00+02:00 through the official package. Seven public messages were available through 14 August 2026; six are decision-relevant below. The question deadline is 21 August 2026 at 12:00 Europe/Berlin.

Package reviewed 16 Aug 2026, 22:22

Research files

Documents used for this evaluation