WorkflowMaintenance & Engineering

Service Bulletin Evaluation

Service bulletin evaluation on your fleet's own evidence — from effectivity to a signed engineering order in days, not weeks

Every bulletin decided in days on the fleet’s own evidence, every tail and dollar cited.

See one case, screen by screen ↓
demo40minutesfrom a 48-page bulletin arriving to a weighed recommendation on 22 tails
demo2.3to 1one year of avoided removals, with the directive risk added, against the $186,528 one-time cost
demo2.1daysmedian from receipt to a signed decision in the sample quarter, with 34 minutes of engineer review
target100%of Alert bulletins decided inside their 7-day clock
In short

What is Service Bulletin Evaluation?

Service bulletin evaluation is how an airline's engineering department decides, for each manufacturer bulletin, whether it applies to its tails, what it costs, what it buys, and whether to adopt, defer or reject it — and, when adopted, writes the engineering order. Service Bulletin Evaluation puts seven agents on that work: they read the bulletin within the hour, check effectivity down to installed serial numbers, weigh the fleet's own removals, cost and leases, and draft a checked EO, while the engineer decides and signs.

How to choose AI for airlines: a buyer's guide to agentic AI solutions →

Updated

The problem

Why service bulletin evaluation eats 32 engineer-hours a bulletin

Service bulletin evaluation is the work of deciding, for every manufacturer bulletin, whether it applies to your tails, what it costs, what it buys, and whether to adopt, defer or reject it — then writing the engineering order planning and the mechanics can work from. Today SB/AD evaluation starts with a powerplant or systems engineer who reads a long PDF — often 50 to 80 pages — line by line, checks SB effectivity against fleet records by hand, chases kit prices and labor by email and retypes the bulletin into an EO. A fleet of 150 aircraft gets 8–10 of these a month.

The risk sits in what the PDF doesn't tell you. Effectivity done by line number alone misses the compressor swapped in already modified, so the kit count and the records end up wrong. The fleet's own removals and shop teardowns — the evidence that the modification pays — sit in the reliability program, not in front of the engineer. Tails going back to a lessor get a modification no return condition asks for. And without a clock per category, an Alert bulletin waits behind an Optional one.

typical32hoursof engineer time to extract and evaluate one bulletin by hand
typical8–10bulletinsa month for a 150-aircraft fleet, each 50–80 pages
typical7–13×the kit pricethe true cost of embodying a bulletin once labor, access, downtime and records are counted
Where a bulletin's engineer-hours goestimated
By hand32 days
With the solution0.6 days
  • Reading the PDF and pulling out the planning, material and labor data8 → 0.1 d
  • Effectivity tail by tail against configuration and component history7 → 0.1 d
  • Chasing removals, teardown findings, kit prices and labor6 → 0.1 d
  • Checking the check plan and each lease's return conditions3 → 0.1 d
  • Retyping the bulletin into an engineering order6 → 0.1 d
  • Writing up the decision and collecting signatures2 → 0.1 d

Estimated split of the 32 engineer-hours a bulletin takes by hand, and of the roughly half hour of review with the agents.

How it works

How a bulletin moves

Seven specialist agents read, match, weigh and draft every bulletin; the engineer argues, decides and signs.

What comes in
Bulletins in6 portals · manufacturer portals, email, upload
Agents at work
Bulletin readerextract + revision diff
Then
Effectivity agenttail + serial number
Fleet evidence agentremovals, teardowns
Cost and downtime agentkits, labor, slots
Lease agentreturn conditions
Then
SB advisorthe balance + conversation
Then
EO drafter and checkercited, checked EO
A person decides
Systems engineerargues, decides, signs
What comes out
Signed decision
Engineering order
Work packages and kits
One case, step by step

One service bulletin evaluation, from the manufacturer's portal to a released EO

Corvane Airways flies about 300 aircraft of eight types out of its ORD hub. On Oct 1, Revision 1 of SB 787-21-0098 arrives from the airframe manufacturer's portal — the cabin air compressor inlet seal, now raised from Optional to Recommended. Here is that one SB evaluation, screen by screen, in the working solution.

  1. 01Oct 15, morning

    Five bulletins need him, each with the agents' view first

    Marcus Hale · Powerplant and Systems Engineer

    Marcus owns ATA 21 and 36 for the 787 and 777 fleets. His Today screen shows 5 bulletins waiting for him, 2 due within 7 days and 31 decided last quarter. The Alert bulletin on the A321neo main landing gear side-stay bolts is due tomorrow, its EO already drafted and checked. Below it sits the compressor seal bulletin: effective on 22 tails, $186K fleet cost, 41 removals in 18 months, 29 from the seal.

    What the agents did today: “Effectivity agent asked Technical Records (Ana Duarte) to confirm the seal standard on N814CV compressor 3.”

  2. 02Oct 1, 09:12 to 09:52

    The bulletin laid out on a balance

    SB advisor

    The bulletin reader received the 48-page revision at 09:12 and extracted 112 values. By 09:52 the other agents had weighed it. On the left, what adopting costs: 87 kits at $1,150, 609 labor hours at $142, 72 overnight hours inside A-check windows and 22 check slots — $186,528 once. On the right, what it buys: 13 removals a year avoided at $31,000 each, $403,000 a year. The verdict under the beam: Adopt at each tail's next check, 86% confident, about 6 months to pay back.

    “I recommend adopting at each tail’s next check, 86% confident. Ask me anything, or move a weight.”

  3. 03One click

    Every weight opens the record behind it

    Fleet evidence agent

    Marcus clicks the fleet evidence weight. The reliability program passage opens with the words the value was taken from highlighted: 41 unscheduled removals on the 22 tails with the pre-mod seal, 29 traced to the inlet seal by shop teardown, 7 to the bearing and 5 to the motor controller. Mean time between unscheduled removals is 8,600 flight hours against a program target of 14,000.

    “Read by the agents and kept with the decision record. Highlighted: the words the value was taken from.”

  4. 04Effectivity

    22 of 28 tails — and N819CV needs 3 kits, not 4

    Effectivity agent

    The bulletin applies to 787-9 line numbers 0412 through 1103 with compressor 4471-200-07 and seal 4471-218-01. The effectivity agent checked every tail's installed part and serial numbers, not only its line number. Compressor 2 on N819CV, S/N CA-20577, came from N825CV on Mar 18, 2026 already modified. N814CV's compressor 3 came back from a shop visit without its seal standard recorded, so it counts as needing a kit until Technical Records confirms.

    “A line-number check would have ordered 4 kits.”

  5. 05The fleet's own evidence

    Removals by month and cause, tied to the bulletin's reason

    Grace Lindqvist · Reliability Engineer

    Eighteen months of removals, stacked by cause, with every one matched to its shop teardown. The seal removals match the reason in the bulletin — extrusion at high compressor speed — and their share has not fallen. Teardown TR-26-1108 on N809CV reads “Inlet seal extruded at the 4 and 7 o’clock positions, with heat discoloration of the inlet duct.” Two cabin odor reports are linked: flight CV 118 ORD–FRA and CV 86 ORD–NRT. Grace confirmed the causes on Oct 12. It is the kind of removal and teardown data a US carrier's continuing analysis and surveillance system (CASS) under 14 CFR 121.373 typically draws on.

    The fleet evidence agent never reclassifies a removal — the reliability engineer does, and the balance re-weighs.

  6. 06He argues back

    “What about the tails going back to lessors?”

    Marcus Hale · Powerplant and Systems Engineer

    The advisor answers with the clauses. N806CV goes back to Halvorsen Aircraft Leasing on Feb 12, 2027 and N811CV to Brightwater Aviation Capital on Apr 30, 2027, both before their next C-check. Both leases require directives and Alert bulletins only; this one is Recommended, so it is Corvane's choice. Doing both would cost $17,152 — 8 kits, 56 hours — with no return credit. It suggests excluding both with reason LR.

    “The lease agent never excludes a tail itself. It proposes, with the clause; the engineer decides and the reason goes on the record a lessor will read.”

  7. 07Re-weighed

    Two tails out with a reason — still Adopt

    SB advisor

    Marcus excludes both, reason LR, lease return before embodiment. The balance re-weighs at once: 20 tails, 79 kits, 553 hours, $169,376. Adopting still wins at 2.5 to 1, now 91% confident, with payback in about 5 months. On the lease view both tails now read Excluded · LR beside the clause that justifies it, and the reason goes into the EO and the decision record a lessor or an inspector will read. Asked what a lessor will see, the agents answer: at return the records show SB 787-21-0098 R1 as “evaluated, not embodied, at Lessee’s discretion” — what Schedule 6, 4.2(c) allows.

    Advisor: “Done. N806CV and N811CV are out, with reason LR. Now 20 tails, 79 kits, 553 hours: $169,376.”

  8. 08Draft 3

    An engineering order written from the bulletin, then tested line by line

    EO drafter and checker

    The drafter writes EO-2026-0417 in nine sections — purpose, effectivity, compliance, material, tooling, labor, accomplishment, records, references — every line tied to the bulletin. The checker tested it against the bulletin and Corvane's task cards. It caught step 6 reading 95 to 105 ft-lb where the bulletin says in-lb, and draft 1 ordering 88 kits by line number; the drafter fixed both. One real question is left for Marcus: the bulletin's seal-land limit is 0.005 in, Corvane's task card uses 0.004 in. He keeps Corvane's 0.004 in.

    “Only the engineer answers open questions, and nothing reaches the maintenance system without two signatures.”

  9. 09Signed · Oct 15

    He signs Adopt; his manager countersigns; the EO is released

    Marcus Hale and Elena Brandt

    Marcus signs Adopt with reason codes A1, reliability, and A2, cabin air quality — the meaning recorded with his name and the time. Elena Brandt, Manager, Fleet Engineering, adds the second signature. Released to the maintenance system, EO-2026-0417 becomes 20 work packages: 14 in C-checks and 6 in overnight A-checks, with 79 kits requested and lease records updated for 7 leased tails — 16 days inside the clock.

    “Your signature records your name, the time and its meaning. It cannot be edited afterwards.”

  10. 10The plan

    Every tail in a slot it already has

    Tom Reyes · Maintenance Planner

    The cost and downtime agent placed each tail in its next C-check where one falls inside 14 months, otherwise in an overnight A-check with a 9-hour window — no revenue time lost. Tom sees 79 kits at $90,850 with a 10-week lead time, arriving Dec 24, 2026 if ordered today, against a first need on N801CV on Jan 11, 2027: 18 days of margin. He asks which tail is tightest on kit arrival; the answer is N801CV, and if the order goes later than Nov 2, move it to its next A-check. The kit request is his to send.

    “The cost and downtime agent never orders parts; the planner does.”

Who it’s for

Built for everyone who touches a bulletin.

The same service bulletin evaluation, seen by the five people who carry it — what their week looked like, and what it looks like now.

MH
Marcus HalePowerplant and Systems Engineer · ATA 21 and 36, 787 and 777 fleets
Powerplant and Systems Engineer
Before
“Don't give me the PDF again. Tell me which tails, what it costs, and what our own data says.”
Now
Opens each bulletin already weighed, argues with the advisor in plain words, excludes tails with a reason and signs.
EB
Elena BrandtManager, Fleet Engineering (widebody) · second signature on every adoption
Manager, Fleet Engineering
Before
“If an inspector or a lessor asks why we skipped two tails, the reason has to be on the record.”
Now
Sees the decision, the reason codes, the exclusions and the cost on one screen before she countersigns — or sends it back with a comment.
TR
Tom ReyesMaintenance Planner, heavy checks
Maintenance Planner
Before
“Give me the EO with the kit count right and I'll find the slots.”
Now
Gets every tail already placed in a C-check or an overnight A-check, the kit count right and the lead time checked against the first need.
GL
Grace LindqvistReliability Engineer · runs the reliability program
Reliability Engineer
Before
“The shop teardowns already told us it's the seal. Use them.”
Now
Her removals and teardown causes are on the balance at decision time; if she reclassifies one, the recommendation re-weighs.
SK
Sandra KowalskiDirector of Quality and Continuing Airworthiness
Director of Quality and Continuing Airworthiness
Before
“Show me the decision, the reason, the signatures and the source — on one page.”
Now
Filters an audit trail no one can edit and exports one evidence pack per decision for the FAA principal maintenance inspector, an auditor or a lessor.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven specialist agents read, match, weigh and draft every bulletin; the engineer argues, decides and signs.

Bulletin reader

Checks each of the six manufacturer portals every hour, reads every bulletin and revision, and extracts effectivity, reason, compliance, labor, parts, tooling and the accomplishment steps with the page and paragraph of every value. When a revision arrives it compares it with the last one and re-opens only what changed.

  • Never guesses at an ambiguous effectivity statement — it goes to an engineer
  • Every value carries its page and paragraph
Effectivity agent

Matches each bulletin to the fleet by line number, MSN, installed part and serial numbers and component swap history, counts kits per position, and asks Technical Records for any record that is missing.

  • Never marks a tail not effective without a record
  • A missing record is requested, not assumed
Fleet evidence agent

Gathers the fleet's unscheduled removals, shop teardown findings and cabin and pilot reports for the affected part, and ties them to the reason the bulletin gives.

  • Never reclassifies a removal — the reliability engineer does
Cost and downtime agent

Prices kits, labor, downtime and check slots per tail and per timing option — next check, standalone visits, defer or reject — from the parts system, the cost inputs Finance approved and the check plan.

  • Never orders parts; the planner does
Lease agent

Reads the return conditions and return date of every leased tail in scope and proposes exclusions with the clause cited.

  • Proposes exclusions; never excludes a tail itself
SB advisor

Builds both sides of the balance from the other agents' cited outputs, recommends adopt, defer or reject with a confidence, answers the engineer in conversation and re-weighs when a weight is moved, saying what changed and why.

  • Never signs
  • Never releases an engineering order
  • Every statement cites a source
EO drafter and checker

The drafter writes the engineering order from the bulletin and the airline's task cards; the checker tests every line against both, sends errors back to the drafter and raises only the real questions to the engineer.

  • No release without two signatures
  • Open questions go to the engineer
Systems engineer

Decides and signs; the manager countersigns. The agents propose; a named person decides.

Ask in plain words

Argue with the recommendation, in plain words

Ask about any bulletin, tail, part or lease — or tell the agents what to change. Every answer points to its source.

What about the tails going back to lessors?

Two effective tails go back to lessors before their next C-check: N806CV to Halvorsen Aircraft Leasing on Feb 12, 2027 and N811CV to Brightwater Aviation Capital on Apr 30, 2027. Both leases require directives and Alert bulletins only; this one is Recommended, so it is Corvane's choice. Doing both would cost $17,152 (8 kits, 56 hours) with no return credit. I suggest excluding both with reason LR.

What will a lessor see on the record?

For each excluded tail the decision record and the tail’s history carry the reason code (LR — lease return before embodiment), the lease clause, Marcus Hale’s name and the time. At return the records show SB 787-21-0098 R1 as evaluated, not embodied, at Lessee’s discretion — which is what Schedule 6, 4.2(c) allows.

Why not wait for a directive?

Revision 1 raised the category to Recommended after odor reports at three operators, and no FAA or EASA proposal exists yet. I rate a directive moderate. If one follows, the window is usually shorter and the work unplanned — that is why I weigh it on the “buys” side. Waiting also leaves about 13 removals a year in place.

How many engineer hours did the agents give back last quarter?

About 970 hours (estimated): 31 bulletins decided in Q3 at a median of 34 minutes of review each, against about 32 hours by hand. Median time to a decision fell from 19 days to 2.1.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

TodayThe engineer's day in service bulletin evaluation: bulletins waiting, clocks due within 7 days, each bulletin with the agents' view and one step, and what the agents did today.
The bulletin backlogEvery service bulletin for eight fleets with category, effective tails, received and due dates, status and the agents' view — including the two still being read.
The balanceThe service bulletin cost-benefit balance: what adopting costs against what it buys, the Adopt recommendation with confidence and payback, and the SB advisor conversation beside it.
Every weight has a sourceClicking a weight opens the reliability program passage behind it, with the words the value was taken from highlighted.
Argued and re-weighedThe engineer asks about lease returns, excludes two tails with reason LR, and the balance re-weighs to 20 tails, 79 kits and $169,376 — still Adopt.
SB effectivity by tailService bulletin effectivity checked against installed part and serial numbers for all 28 787-9s — 22 in scope, 87 kits — with the swapped, already-modified compressor on N819CV.
The fleet's own evidenceRemovals by month and cause, mean time between removals against target, teardown quotes and the cabin odor reports linked to the bulletin's reason.
Leases and redeliveryLeased tails in scope with lessor, return date, next C-check, what each lease requires at return, the exclusions the agents suggest, and questions to ask the agents about the lessor's record.
The draft engineering orderEngineering order creation from the bulletin: EO-2026-0417 with every line cited, and the EO checker's two fixes and one question for the engineer.
Sign-off and releaseDecision, reason codes, the engineer's signature and the manager's countersignature, and the EO released as 20 work packages.
The planEach tail placed in its next C-check or an overnight A-check, the kit count, price and lead time against the first need, with the agents ready to answer which tail is tightest on kit arrival.
Audit trailEvery action by people and agents with its source, filterable, uneditable, and exportable as an evidence pack.
Your rulesClocks per bulletin category, the second-engineer confidence threshold, signatures, reason codes and the cost inputs every balance uses.
Governance

Built for continuing airworthiness: cited, signed, on the record.

Every value cites its sourceEvery weight on the balance and every cited number opens the passage it came from — the bulletin paragraph, the component record, the removal, the teardown, the lease clause — with the words highlighted.
The engineer decides and signsA decision needs a reason code — A1–A4 to adopt, D1–D3 to defer, R1–R3 to reject — and the engineer's signature with its meaning. Overruling the advisor needs a note, and the advisor's view stays on the record.
Two signatures before any releaseEvery adoption needs a second signature from the Manager, Fleet Engineering, who can countersign or send it back with a comment. The setting is locked on: Corvane's engineering procedures require it.
Exclusions carry their reasonA tail leaves the engineering order only with a reason code — LR lease return, PM post-mod part installed, RT retirement or sale — and the reason stays in the decision record and in each tail's history.
Clear limits on the agentsAgents never sign, never release an engineering order, never order parts and never reclassify reliability data. Missing configuration records go to Technical Records instead of being assumed.
An audit trail no one can editEvery action by people and agents is recorded with its source, kept for the life of each aircraft plus 2 years, and exports as one evidence pack: the bulletin, effectivity, fleet evidence, the balance and conversation, lease clauses, the EO and the signatures.
Configuration

Your engineering procedures, not ours

Clocks, review thresholds, signatures and cost inputs are settings; a change to a clock, the threshold or a cost input goes on the audit trail.

SettingDefaultChoose from
Alert bulletins7 days from receipt to a signed decisionStep up or down a day at a time
Recommended bulletins30 daysStep up or down a day at a time
Optional and Informational bulletins60 and 90 daysStep up or down a day at a time
Second engineer below confidence75%50% to 95%, in steps of 5
Close not-effective bulletins automaticallyOff — an engineer confirms every closureOn · Off
Second signature for every adoptionOn — Manager, Fleet EngineeringRequired by Corvane's engineering procedures
Reason codes requiredOnA1–A4 adopt · D1–D3 defer · R1–R3 reject · LR, PM, RT exclusions
Cost inputsLabor $142/h · compressor removal $31,000Also out-of-service hour for a standalone visit $1,500 and aircraft on ground $12,000 an hour · approved by Finance
Connections

Works with the systems engineering already runs on

Manufacturer portalsairframe, engine and component bulletins and revisions, checked every hour
Maintenance information systemconfiguration, component history and work packages
Reliability programunscheduled removals, teardown findings, cabin reports
Lease recordsleases, return dates and return conditions
Parts and purchasingkit prices, lead times and purchase requests
Email and calendarAlert notices, clock warnings and signature requests
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
100%
of Alert bulletins decided inside their 7-day clock
Alert bulletins decided on time
estimated
$403Ka year
of compressor removals avoided on one bulletin, from the fleet’s own data
Old seal≈ 27 removals a year
Improved seal≈ 14 a year
estimated
3,000hours
of engineer time back a year: review in 30 minutes, not 32 hours
By hand32 h per bulletin
With agents≈ 30 min review

“demo” = seen in the working solution, on its sample fleet data · “target” = the design goal, measured in the live solution · “estimated” = our estimate (the split of a bulletin's engineer-hours, and the engineer hours given back last quarter) · “typical” = published figures (an aviation maintenance software provider's published analysis of SB and AD processing — 32 engineer-hours a bulletin, 8–10 bulletins a month for 150 aircraft, 50–80 pages each; an aviation training and consultancy firm's guidance on service bulletin embodiment — 7–13 times the kit price; EASA CAMO.A.315(b)(4) on assessing non-mandatory modifications; 14 CFR 121.373 on continuing analysis and surveillance). People, airlines, lessors, tails, bulletins, engineering orders and part numbers named on this page are fictional — characters and sample data in the working solution.

Questions

What airline engineering teams ask us about service bulletin evaluation.

What is service bulletin evaluation?

Service bulletin evaluation is how an airline's engineering department decides, for each manufacturer bulletin, whether it applies to its tails, what it costs, what it buys, and whether to adopt, defer or reject it — and, when adopted, writes the engineering order. Service Bulletin Evaluation puts seven agents on that work: they read the bulletin within the hour, check effectivity down to installed serial numbers, weigh the fleet's own removals, cost and leases, and draft a checked EO, while the engineer decides and signs.

Is a service bulletin mandatory?

Not by itself. A service bulletin is the manufacturer's instruction and recommendation; an airworthiness directive (AD) is what makes action mandatory, and an AD may call up a bulletin's instructions. That difference between an airworthiness directive and a service bulletin is why each category gets its own clock — Alert 7 days, Recommended 30, Optional 60 by default — and why the advisor weighs the likelihood of a directive on the balance.

How do airlines decide to adopt, defer or reject a service bulletin?

Through a service bulletin assessment: a service bulletin cost-benefit analysis on their own fleet, with the decision and its justification recorded. For an EASA operator this is the non-mandatory modification assessment that CAMO.A.315(b)(4) asks a continuing airworthiness management organization to have a procedure for. Here the SB advisor puts kits, labor, downtime and check slots against removals avoided, fleet evidence, directive risk, cabin air and lease value, recommends one with a confidence, and the engineer signs the decision with a reason code.

How is service bulletin effectivity checked tail by tail?

Service bulletin applicability is decided tail by tail. The effectivity agent tests every tail against line number, MSN, installed part and serial numbers and component swap history, not only the line-number range. It found a compressor swapped in already modified, so one tail needed 3 kits, not 4, and it asks Technical Records for any record that is missing rather than assuming.

How does a service bulletin become an engineering order?

Going from SB to EO is the EO drafter's job: it writes the engineering order from the bulletin and your task cards — purpose, effectivity, compliance, material, tooling, labor, steps, records and references, every line cited. The EO checker tests each line, sends errors back to the drafter, and leaves only real questions for the engineer. Once two people have signed, the EO is released to the maintenance system as work packages.

Does it take leases and aircraft redelivery into account?

Yes. The lease agent reads the return conditions and return date of every leased tail in scope and proposes exclusions with the clause cited — for example, tails returning before their next check under leases that require only directives and Alert bulletins. The engineer decides, and the reason code goes on the record a lessor will read.

Do engineers stay in control of the decision?

Yes. The agents recommend, explain and draft; they never sign, release an engineering order, order parts or reclassify reliability data. The engineer can move any weight, overrule the advisor with a note, exclude tails with a reason and sign; the Manager, Fleet Engineering adds the second signature before anything is released.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your engineering procedures, task cards, cost inputs and a sample of past bulletins and fleet records — and it goes live once every quality gate has passed. We will walk you through it on your own bulletins first.

See it on
your bulletins.

We'll run Service Bulletin Evaluation on a sample of your own bulletins and fleet records.