APPEARANCES & EVENTS
JEREMY BOERGER – THE ITAM COACH
CREATOR OF THE PRAGMATIC ITAM METHOD
Year | Event | Topic | Type | Location |
|---|---|---|---|---|
2023 |
| Book Signing | Dayton, OH | |
2023 |
| Book Signing | Columbus, OH | |
2023 |
| Say No to Tech Layoffs (March 1) | Speaking Engagement | Dayton, OH |
2022 |
| Software Asset Management In The Age Of Blockchain | Speaking Engagement | Las Vegas, NV |
2022 |
| Managing Your IT Asset Lifecycle for Fun and Profit | Speaking Engagement | Dayton, OH |
2022 |
| Using Jamf to Meet & Exceed the ISO 19770-1 Requirements | Speaking Engagement | San Diego, CA |
2022 |
| Optimizing ITAM By Understanding Data Theory | Speaking Engagement | Las Vegas, NV |
2022 |
| Dinner with SAM Professionals | Speaking Engagement | Chicago, IL |
2022 |
| Software Asset Management In The Age Of Blockchain | Speaking Engagement | Las Vegas, NV |
2022 |
| The Pragmatic ITAM Method | Podcast | |
2022 |
| Rethinking Information Technology Asset Management | Book Signing | Covington, KY |
2022 |
| Rethinking Information Technology Asset Management | Book Signing | Dayton, OH |
2022 |
| Rethinking Information Technology Asset Management | Book Signing | Dayton, OH |
2021 |
| Audits Aren't Just For Taxes | Podcast | |
2021 |
| Shadow IT and Rethinking ITAM | Podcast | |
2021 |
| Rethinking Information Technology Asset Management | Podcast | |
2021 |
| More Cooperation, Less Cajoling: Getting IT and SAM to Work Together | Speaking Engagement | Chicago, IL |
2021 |
| ITAM in the Age of Blockchain | Speaking Engagement | Nashville, TN |
2021 |
| Software Audit Strategies: Suggestions to Mitigate, Manage, and (Ultimately) Avoid | Speaking Engagement | Nashville, TN |
2021 |
| Software Asset Management in the Age of Blockchain | Speaking Engagement | Virtual |
2020 |
| SAM in the Age of Blockchain | Speaking Egagement | Virtual |
2020 |
| Software Asset Management in the Age of Blockchain | Speaking Engagement | Virtual |
2020 |
| Achieving “Trustworthy Data” with Jamf: How to leverage Jamf to satisfy ISO/IEC 19770:2017 | Speaking Engagement | Virtual |
2020 |
| How Companies Can Save Big With Software Asset Management | Podcast | |
2019 |
| Roundtable Discussion: The State of the Software Request Process | Roundtable Discussion | Chicago, IL |
2019 |
| Optimizing ITAM By Understanding Data Theory | Speaking Engagement | San Diego, CA |
2019 |
| IT Asset Management: The Forgotten Starting Point | Speaking Engagement | New Orleans, LA |
2019 |
| IT Asset Management: The Forgotten Starting Point | Speaking Engagement | Highland Heights, KY |
2018 |
| IT Asset Management: The Forgotten Starting Point | Speaking Engagement | Cincinnati, OH |
2018 |
| Become the Data-Driven SAM Manager | Speaking Engagements | San Francisco, CA |
2018 |
| Become the Data-Driven SAM Manager | Speaking Engagements | Chicago, IL |
2018 |
| IT Asset Management: The Forgotten Starting Point | Speaking Engagement | St. Louis, MO |
2017 |
| How To Leverage Data Theory to Attack Overspend and Defend Security | Speaking Egagement | Chicago, IL |
IBSMA SAM Summit
Internet 2.0 Conference USA (May '22)
Covington Business Council
The Ohio Information Security Conference
Nashville CIO Council
Zoozler Lunch & Learn Series
itSMF FUSION Symposium 
IT Leadership Forum, N KY University
BMC IT Leadership Luncheon for Cincinnati- Do not depend on only one source of information about your computing environment.
Digital Twins take information from sensors sprinkled throughout the physical device and merge them together. Our aforementioned race car would use GPS telemetry, accelerometers in the chassis, and transmission gear turns to calculate speed. And it would display an error message to the pit crew should one, two, or all three begin returning conflicting information.
What would that look like in a CMDB? Modern corporate computing environments have many different scanners, agents, and command & control tools that touch all the laptops, desktops, servers, switches, etc., and do so multiple times per day. If all of these tools are working in the same environment, they should be in agreement. Where these tools agree (and disagree) will help you improve your CMDB by identifying knowledge gaps and keeping it as informed as possible. - Include data maps when modeling service management processes.
You can flow-chart and RACI process designs with the best of them, but how often do you model the data points each step of your service support process produces? And if a particular data point doesn’t populate the expected Configuration Item attribute, do you know how to troubleshoot what went wrong? And when it went wrong?
Digital Twin models track both the item and what the item is doing in the supporting process at any particular point in time. An oxygen sensor at the intake manifold is different from the oxygen sensor in the exhaust manifold – the Digital Twin of our race car example knows which is which and when to expect the sensor’s information.
Your CMDB should also know that an asset reporting back an IP address and an end-user login is no longer sitting in inventory. If an approved change request is also associated with that record, program the CMDB to change the asset’s lifecycle flag accordingly.
Going another step further, your CMDB could be programmed to anticipate the deployed asset’s needs. For example, the end-user logging in should have a job code associated with them in Human Resources. What software do other individuals with that same job code use? Why not automatically deploy the needed software (and purchase new licenses, obviously) based on what other users with the same job codes use? - Automate record updates when appropriate.
In the race car example, if a pit crew chief observes worrisome pressure and temperature information on a tire, orders a pit stop, and the crew replaces the entire wheel. The driver doesn’t have to pull over and troubleshoot on the track. Nor does the pit crew need to stand there and troubleshoot the old wheel while it’s still mounted on the race car. The pit crew chief trusts the Digital Twin to detect the new wheel assembly and baseline the telemetry from the new sensors, all while the driver gets back to the race.
The same should be expected of your CMDB. Few, if any, modern corporate IT service departments troubleshoot and repair in the field. Nowadays, the solution to an end user’s complaint is “swap with like replacement.” So why require your Tier 1 and Tier 2 technicians to type out all of their troubleshooting steps before closing the trouble ticket? Improve your CMDB and automate the process – the record updates, the system notifications, etc. – so your end-user can get back to productive work.
