MADEKnowledge

MADE Workflows > Exporting Model Information with MADE API

WF48: MADE Model API Export

Pre-Requisites

  • A. MADE Project: a project with an externally configured API Endpoint.

Detailed Steps

  1. Open the Model Export Wizard, via the integration toolbar. Note that MADE must have a current project opened.
  2. Create an API endpoint by inputting host information (Alias, URL), alternatively select an existing API Endpoint. Enter any required login detail and test connection to confirm that the Endpoint is available for export.
  3. Select the request type for the model export (Snapshot is the default setting). If a Delta selection method is chosen, the user is able to filter based on the model hierarchy and, when applicable, specific (self-contained) resources (e.g. maintenance resources).
  4. Select the resource category you wish to export. When conducting a model export, each resource category contains a set of parameters from the model.
  5. Filter selected items for export (only applicable to Delta request export).
  6. Export your model information to your chosen endpoint by selecting Finish. MADE will run a number of export verification checks. Any issues encountered during the export process will be alerted to the user. If the export is successful, the wizard will close automatically.
  7. Model export to your endpoint location is now complete.

Screen-by-screen detail (from embedded screenshots)

  • Step 1: Open Model Export Wizard — Main menu: Integration > Export Model...
  • Step 2: Create or Select API endpoint — Same as WF47: "Select API Server" page, add host via green '+' (Alias, URL, Version, Authentication), Test Connection ("Connection successful"), OK, enter Login Credentials, Try Login, Next.
  • Step 3: Select Request Method Type — "Export Model" dialog, "Select Data" page: Request Method radio buttons — Delta (updates existing data) or Snapshot (replaces existing data when information is already present). Below, the same Data Categories checklist as import (Project, Items, Systems, RAMS, Criticality, Failures, Maintenance, Functions, Sensors) with descriptions.
  • Step 4: Select Resource Category — Check/select desired Data Categories (all shown checked in the example: Project, Items, Systems, RAMS, Criticality, Failures, Maintenance, Functions, Sensors). "Select All" / "Deselect All" available.
  • Step 5: Filter Resource Selection (Delta request export only) — If Delta was chosen, additional "Filtered Selection" pages appear: (a) "Items" — select which model items in the hierarchy to include (checkbox tree, e.g. Vehicle System > Coupling, Driveline, Power Generation > Control Unit/Diesel Engine/Fuel Tank, Vehicle); (b) "Systems, Missions, Functions" — select Mission Profiles and Functions to include (e.g. FHA Functions: "1 - Control Vehicle", "2 - Provide Thrust"; Mission Profiles: Long Trip, New Group, Regular Trip); (c) "Maintenance Actions" — select which Maintenance Actions to include (e.g. Control Unit > Breakdown 1/Breakdown 2/Breakdown Maintenance, Fuel Tank > Breakdown Maintenance). Each page has "Select All" / "Deselect All".
  • Step 6: Export Selection — "Results" page shows Summary: Endpoint, Request Method (e.g. "Export > Snapshot"), Selected Data (e.g. "RAMS, Failures, Systems, Project, Functions, Maintenance, Items, Criticality, Sensors"). Note: unsaved changes are automatically saved before the operation starts. Click Finish.

Outputs

  • I. Model: Exported Model to configured API Endpoint.

Source: Local MADE 3.9.1 installation: com.phm.made.help.plugin/documents/help/pdf/Workflows/WF48-Exporting Model Information with MADE API.pdf · retrieved 2026-07-09