v7 Guide : SimBrief Integration

[DisposableHero]

As you may have noticed, phpVMS v7 comes with built in SimBrief API integration and aircraft can be configured in some different ways to achieve better planning results. Below you can find some key instructions and settings with their effects.

 

Main Requirement is a valid SimBrief API key, to get one kindly check SimBrief documents (website/support forum) and complete your application, when you have your key ready, just insert it in settings.

 

While waiting for your API key you can define your Subfleets and Aircraft as below;

 

Subfleet Definitions;

 

Here only important field is "SimBrief Type", when it is defined it will be used for all aircraft under this subfleet. And it simply overwrites the Aircraft ICAO code during planning. If your pilots are using only one simulator (like X-Plane) and only one aircraft addon for this subfleet (like Zibo), then you can simply add your Zibo B737-800X SimBrief Airframe ID here at this field.

 

 

Aircraft Definitions;

 

This is the most important part, as it allows fine tuned planning compared to a generic subfleet airframe definition. As you can see, we do have the same "SimBrief Type" field here too. This affects only the aircraft, and has priority over the subfleet definition. So if you have a really specific SimBrief Airframe for a particular aircraft and want it to be the default, then you can enter the id here. (Also it is possible to use this field as a replacement ICAO code. Imagine you are using an Airbus CEO but want this aircraft to use Airbus NEO standards at SimBrief, so you define A321 as the ICAO code, but use A21N as the SimBrief Type.)

 

FIN, SELCAL and HEX CODE (ICAO 24-bit, transponder identification code) are optional and have no direct effect on the flight plan you will generate but the weights below are important. When defined, these weights are passed to SimBrief for flight planning purposes, so better define them according to the aircraft you are trying to simulate within phpVMS.

 

You can see that the DOW is empty (0) in the example, this is not a mistake but done on purpose. You will see it later.

 

Using SimBrief Airframes (sb airframes) ;

 

phpVMS is able to get and store all publicly available SimBrief Airframes / SimBrief Layouts during install and update them weekly (with cron), also it is possible for admins to manually trigger an update whenever they wish to. Also it is possible to add your own / custom airframes to the system easily.

 

 

As like SimBrief itself, airframe definitions are "ICAO Code" based, once you define and save your custom airframe at SimBrief, you can simply copy the airframe ID and add it to phpVMS by giving it a nice looking unique name and the aircraft ICAO type code you wish to use.

 

Also, if you do not want to use the built in SimBrief airframes and have only your custom airframes listed, then you need to enable the respective setting from Admin > Settings. This logic also applies to passenger and baggage weights being used for planning. Imagine you have an airframe definition (either created by you, or a public one provided by SimBrief), using 100 kg for passengers and 20 kg for their bags. But you do not want to use those weights because you have some custom weights for scheduled/non-scheduled flights, even better you control your baggage weights per airport with some custom code etc. Then you need to enable the respective setting to pass in your weights to SimBrief.

 

 

How does it work, how is the priority logic defined ? Why the DOW is empty in the example ?

 

• Subfleet SimBrief Type = Empty
• Aircraft SimBrief Type = Empty
• Aircraft ICAO Code = A321
• Aircraft DOW = Empty
• Aircraft MLW = Empty
• SimBrief Provided Airframes = Fenix A321 IAE, Fenix A321 CFM, ToLiss A321, Your Custom A321

 

As you know, each addon aircraft have their own basic empty weights and mostly they are hard coded (for SimBrief it is the DOW - Dry Operating Weight / OEW - Operating Empty Weight). So we leave it empty, to be able to use the DOW from SimBrief Airframe definitions. When planning, the dropdown will show you 5 items, the list is above and there will be a "SimBrief Default" entry (which is the basic definitions of SB). If you select Fenix A321 IAE, then its DOW will be used, along with its performance definitions (like fuel factor, engine thrust rating and others), equipment etc. But the weights you defined will be sent to SimBrief to overwrite those values.

 

If you do not select one, it is ok too as the defaults provided by SimBrief along with the data you are sending (like weights and other stuff) will be used. But if you are after precise flight planning, then it is better to either have your main types defined at SimBrief and a matching airframe should be selected.

 

Subfleet SB Type > Aircraft SB Type > Selected Airframe > Aircraft specific details (like weights, SELCAL, HEX, FIN, VA specific custom RMK field)

 

With this order and logic you can have base airframes for your fleet, like PMDG B738, Zibo B738, LevelUp B738 (same example can be extended to Fenix, ToLiss, Aerosoft, Flight Factor group) and then define aircraft specific changes at phpVMS because in a fleet some aircraft have different MZFW or MLW's but they do share the generic specifications. Like a B738 can have 79013, 77000 or 75000 KG MTOW depending on the certification, instead of defining different airframes at SimBrief, you can simply pass that info during planning.

 

Recent changes at SimBrief allow pilots to have precise performance calculations, specific limitations and if certified some nice ETOPS abilities, to be able to use them with phpVMS, defining airframes at SimBrief and using their ID's during planning will be the best option (considering some items still not available at api access, this method will eliminate those cases too).

 

Climb / Cruise / Descent Profiles and Layout Options

 

All these are also obtained from SimBrief and tied to Aircraft ICAO type codes, so when you select an A321 from your fleet to generate a flight plan, you will see the profiles SimBrief offer for that type in general. Additionally the layout is automatically selected if an airline match is found, if not SimBrief Default (LIDO) is used.

 

What about General Aviation and Really Custom Airframe Support

 

GA is supported by SimBrief up to a point, so we do have the same, even though the examples above are based on airliners, logic remains same for GA aircraft too. And you can still define your custom (non-existing airframe at SimBrief) as per their documentation, have a profile for it and use it at phpVMS. Considering that nothing offered by SimBrief, your custom airframe will be the only option at the dropdown.

 

Hope this help, safe flights.