Five guides, each one owned, versioned and dated.
The Mehrex Trading System is delivered with structured documentation rather than a slide deck and a handover call. This page lists the set, says who each document is for, and explains how to get it.
- Documents in the set
- 5
- Available on request
- 1 of 5
- Provided during engagement
- 4 of 5
One business overview, four companion references.
The guide below is the business and functional overview — the document an evaluation team reads first, and the one that answers “how does this market actually work”. The four companion guides carry the message-level and operational detail, and are provided during the engagement phase together with the associated release notes.
| Document id | Document | Audience | Availability |
|---|---|---|---|
| MEX-ENG-DEL-002 | Guide to the Mehrex Trading SystemThe business and functional overview: market model, modules, order management, execution and interfaces. The document an evaluation team reads first. | Evaluators, market operations, compliance | Available on request |
| MEX-OPS-DEL-001 | Guide to Market Configuration and ManagementThe Market Control Panel manual: instruments, tick tables, calendars, sessions, corporate actions, participant administration and maker–checker approval. | Market operations | Provided during engagement |
| MEX-MKD-DEL-001 | Guide to Market Data ServicesSnapshot and incremental market data, instrument definitions, statistics, and the recovery model for consumers that fall behind. | Market-data consumers, vendors | Provided during engagement |
| MEX-API-DEL-001 | Guide to Trading Services and API ReferenceMessage-level reference for order entry, amendment and cancellation, execution reports, and the FIX 4.4 gateway mapping. | Member firms, integrators | Provided during engagement |
| MEX-CON-DEL-001 | Guide to Connectivity and Customer TestingEnvironments, session management, throttling, cancel-on-disconnect, and the conformance programme members complete before go-live. | Member firms, integrators | Provided during engagement |
How you know which version of a behaviour you are reading about.
Every guide opens with the same front matter. It exists so that a question about market behaviour can be settled by naming a document, a version and a date, rather than by recollection.
- doc-id
- A stable identifier such as MEX-ENG-DEL-002. It never changes, so a query, a defect report or a contract can name a document unambiguously across versions.
- type
- What kind of document it is — a deliverable, a specification, a note. It tells you whether the content is contractual or explanatory.
- status
- Issued or superseded, so you can tell at a glance whether the copy in front of you is the current one or has been replaced by a later version.
- version
- The version of the document, not of the software. Paired with the applies-to field it tells you which build the described behaviour belongs to.
- owner
- A named person, not a department. Every document has someone accountable for its accuracy, and that is who answers a question about it.
- updated
- The date the content last changed, so you can tell at a glance whether what you are reading predates the release you are testing against.
--- title: the document, in full short-title: how it is cited elsewhere doc-id: the stable identifier type: deliverable | specification | note status: issued | superseded version: of the document, not the software owner: a named person applies-to: the component the behaviour belongs to updated: the date the content last changed ---
The front matter every guide opens with, shown as its fields.
Alongside the documents, two things carry change: every change to reference data — instruments, tick tables, lot sizes, price bands, calendars — is published from the Market Control Panel as a versioned bundle, and every software release ships with release notes.
Taken together, that means a member firm can always answer three questions without asking us: which reference-data version the market is running, which release the engine is on, and which document version describes it.
Ask, and say a little about your market.
The Guide to the Mehrex Trading Systemis available on request under a confidentiality undertaking — it contains proprietary information provided for the purpose of evaluating the system, and is not for onward distribution.
The remaining four guides — the Control Panel manual, market data services, the trading API reference, and connectivity and customer testing — are provided during the engagement phase, together with the associated release notes. They are reference documents for people configuring or connecting to a specific configured venue, so they are more use to you then than now.
Tell us your venue type and the asset classes you care about and we will send the guide with the sections that matter to you flagged.
Tell us about your market. We will show you the engine matching.
A live demonstration runs about an hour: the order book, the Control Panel, an auction uncrossing, and a replay of the journal that produced it.