Connect your external BI tools to Meisterplan and easily visualize the most important project information.
- What's Possible with Our Reporting API
- How to Get Started
In this video we give you an overview of all the reporting options Meisterplan has to offer:
What's Possible with Our Reporting API
Want to sync data between Meisterplan and other systems? Use the Meisterplan REST API.
The Reporting API is an interface that lets you transfer Meisterplan data into reporting tools such as Microsoft Power BI. In these BI tools, you can customize reports to prepare for and make better decisions in board meetings.
The Reporting API provides read access to the following Meisterplan data:
- Projects and their details (e.g., Status, Business Goal incl. colors, Rank)
- Milestones (incl. milestone dependencies and project phase colors)
- Allocations (e.g., who is scheduled on which project and for how long, spread over weeks/months)
- KPIs (e.g., Total Cost, Allocation Total, CapEx Total, OpEx Total, Benefit Total, Net Value)
- Resources (incl. capacities and calendars)
- Roles (incl. capacities)
- OBS units
- Actual Time Worked (as imported per resource and project; learn more here)
- Capacity of default calendar (for calculating FTE)
Each of these endpoints provides thematically connected data (e.g., projectname, projectstart) that can be combined to create the report you need. You can also convert the data provided (e.g., calculate allocation days from allocationHours).
You need to have the Access Meisterplan APIs and Connect External Applications right to access the Reporting API.
Reporting API for On Premise
The Reporting API can also be used with On Premise systems. To do so, change the URL of each endpoint to read as follows:
More Options for Report Customization
Your management gets reports from different departments and has come to expect certain visualizations of data that cannot be recreated in integrated reports. Import your Meisterplan data into your reporting tool and customize your reports visually and functionally to match your company's expectations.
Create Reusable Reports
Load relevant data from Meisterplan into your preferred BI tool and then analyze your data. Save your customized reports so you can refresh the report data before the next meeting and save valuable time.
How to Get Started
All you need to access your Meisterplan data with your BI tool is in most cases an API token. Here are several options how to use the Reporting API.
Templates for a Quick Start
An easy way to get started is with our report templates for MS Power BI. You do not need to be experienced with the program to quickly create your first reports with them, and you can customize them to suit your company's requirements.
You can create meaningful reports just as easily with our report template for Tableau. This template presents your project portfolio as a graphically appealing Bubble Chart and can be customized quickly.
Connect Your Tool Without a Template
You can also prepare customized reports by connecting your Meisterplan system with a BI tool without using any of the templates described above. Find a detailed description of how to load Meisterplan data in MS Power BI in this article. If you want to load Meisterplan data in Tableau, go to this article.
The Reporting API also allows you to create reports directly in MS Excel 2019. Enter the endpoints of the Reporting API as a web source and export the data into an Excel file for further editing.
You can connect the Reporting API with all BI tools that have a REST interface, e.g., Qliksense, Eazy BI or Tibco Spotfire. Find all the details you need to connect your tool in our Reporting API documentation.
The Reporting API is based on the REST (short for "Representational State Transfer") standard and therefore offers the most flexibility and security. In contrast to the REST API, however, the Reporting API does not need paging, meaning all lines are queried all at once and not in packages. The Reporting API also uses a de-normalized data model which means that project name, scenario name and other fields are not queried in addition to the respective ID and do not have to be mapped later.