@SimBrief Hello Derek! As always, thank you for the awesome work you do for the community!
A couple things I have noticed with the SWA OFP format (and yes I have confirmed these issues with SWA pilots and dispatchers already so it checks out lol).
1: For all ETOPS OFP planning, SWA now plans a static cost index of 40 for NG fleet and 30 for MAX fleet. Would it be possible to implement this change into the OFP format itself? Its ONLY for ETOPS flights specifically. So basically if you have ETOPS checked, then it should force a CI of 40 for NG fleet or 30 for MAX fleet.
Non ETOPS cost index is AUTO computed by Flight Keys.
2: There is a “see through/transparent” identification code on the dispatch release on each page now.
Its for troubleshooting purposes for the Flight Keys company in Europe. So that if there is an issue with a release, SWA can quickly call Flight Keys and they can look up the release using this unique identifier code. Is that something that we could get added too? Not for additional functionality to the Simbrief system but rather solely just for more immersion on the OFP itself. That would be the only thing I would say is missing at this point.
This is what it looks like. Its on every page of the dispatch release/OFP.
Every page has this type of code and here are a few examples of the code format:
CE020201-E5CF-5A62-CA5A-8F9023C9F700
55Z2D5B1-5868-5DD1-B99F-B92D8386A229
F41048D4-91D5-5DH4-B2B6-4BCB72FD94F5
Its always in that format specifically. Its always a random code but its the same random code on every specific Dispatch Release/OFP.
It doesnt change from page to page. Just changes from release to release if that makes more sense.
Also, for all ETOPS planned flights, at SWA, this remark is required to be on the release for every ETOPS flight. It is automatically included on the release without dispatcher input:
ETOPS OPERATION/MAX DIVERSION TIME: 180
Would it be possible to auto include this remark to the SWA OFP (specifically only if ETOPS is selected)?
This remark would go just below the “FLAG OPERATION” remark that is already included on the Simbrief SWA OFP format.
Lastly, regarding the FL CHANGE section of the release, if there are too many step climbs or step downs planned on the release to fit on the FL CHANGE line, Flight Keys will make FL CHANGE start its own brand new line below TOC. This is what it should look like if many step climbs or step descents are planned on the release:
Would it be possible to implement this format for when FL CHANGE has too many entries to fit on a single line right after TEMP/DEV?
Thank you very much sir for all that you do and I look forward to hearing from you soon!