We’ve been collecting information for many years, driven by the usual suspects: compliance and fear. Now it’s time to take advantage of the information we’ve gathered by shifting our focus from the people who felt they had to keep it to the people who can actually use it. In short, it’s time to reap the benefits of the hard work we have already done. Learn how American Nuclear Insurers is using their information today, the process that got them there, and the technology it took to make it happen. Learn about the current state of Information Management in AIIM’s latest report: http://info.aiim.org/2017-state-of-information-management

1. Harvest Time in the Information Garden
Expanding the definition of information
and keeping the promises we’ve made

3. Background – What’s in a Title?
Programmer Analyst – Methods
Analyst – Project Manager –
Consultant – Manager – Director – VP

4. What’s in a Job?
Programmer Analyst – Methods
Analyst – Project Manager –
Consultant – Manager – Director – VP
• I managed people
• I made processes more efficient
• I brokered information
• I helped people do their job!
What would you
say…you do
here? (1)

5. What’s in a Descriptor?
• Development – SDM/70, Structured
Analysis, JAD, RAD, Scrum, Agile,
Object-Oriented, Waterfall, Spiral,
Rapid Prototyping, Extreme
Programming…
• Data – Flat, Hierarchical, Network,
Relational, Object-Oriented…
• Languages – Too many to list at 28 pt“Modern” is fleeting

6. And Yet…
We agonize over whether ECM is still a thing

7. Systems Development and
ECM – Not so different
What Did I Do?

8. Systems Development / ECM Design
• Follow agreed upon best practices
• Use best-of-breed technology
• Teach people how to use the system
• Drive (mandate) adoption
• Focus on security
• Monitor compliance

9. In an Ideal World
Business Process Technology Stack
(2)

10. In the Real World
Business Process Technology Stack

11. As a Result?
• Data processing systems saved time & money
• Reporting systems facilitated communication
• Content management systems aided in
communication, compliance and governance,
but…
– Eye-roll-inducing terms abounded
– We created better silos

12. However…
We did put stuff in those silos

13. Eureka
What if…
We reach inside the silos and give people the
information they need to do their jobs?

14. A little bit of information
about two solutions we’ve
built and one we’re building
Examples

15. Our approach to organizing
and delivering information
for Emergency Response
Stuff We Have to Know

16. Emergency Response
• It’s what we do
• We have all the information we
need
– It’s not enough to have it
– It’s not enough to be able to find it
• We need to deliver “Situationally-
Relevant Information”(3)
It’s Thornton’s
fault

17. SharePoint On-Prem
• Everything we have
• A place for everything
• Everything in its place
• Everything you would
expect from SharePoint

18. SharePoint Online
• Everything we might need
• A place for everything
• Everything in its place
• Still, everything you would
expect from SharePoint

19. iPad App
• Everything we need
• Everything where we want
it to be
• (Almost) Everything you would
expect from an iPad app

20. iPad App
Build with and hosted
on Seattle Cloud

21. SharePoint vs. SharePoint
“This is so much better
than going into
SharePoint”

22. Learn Through Usage
iPad – user comment:
“we had a lot of
documents available at
the drill, but there were
no copiers. Is there any
way I can capture this
stuff through this app?”
– Yes, yes there is

23. It’s Not Pretty…But it Works

24. “If only HP knew what HP
knows, we would be three
times more productive” (4)
Lew Platt
Stuff We Do Know

25. What ANI Knows (well, one thing, we know more than this)
• Entity relationships – Who owns what
sites?
• Site relationships – How many units?
• Premium data – How much do we
charge?
• Rating information – Why do we charge
that?
• Inspection & Recommendations – The
story.
• FMMR(5) – Can we mitigate the risk?

26. Delivering What We Know
• Data created / imported
to SQL Server
• Documents & metrics in
SharePoint
• Collected by PowerBI
• Delivered to SPO &
mobile devices

27. Delivering What We Know
• Data created / imported
to SQL Server
• Documents & metrics in
SharePoint
• Collected by PowerBI
• Delivered to SPO &
mobile devices

28. In a small organization, you
never know who will have to
answer a question
What We Should Know

29. Stuff We Should Know (SWsK)
• After Fukushima – required
reading list on SharePoint
– Worked well, but most people
printed articles to read later
– Lots of information like that – more
paper? No!
• ANI sourced and curated

30. SWsK - Content
• Attributes of:
– Our business
– Our members
– The industry we insure
• Interesting items in the news
– About the above and in general

31. SWsK – Implementation
• Recommended articles
• RSS feeds
• Custom search
Automated and
manually fed

32. SWsK – Implementation
• Prepared by Subject Matter Expert
• Curated news
• Driven by database systems
Mostly static but news
and analysis mixed in

33. SWsK – Implementation
• Driven by user experience
• SharePoint Online and In-App
• Crowdsourcing
Manual process up front
but automatic from
arrival in the app

34. SWsK – Process
• Submit
• Recommend
• Archive
• Share
• * Veto *
10 Minutes (max)
invested per article

35. Nothing earth-shattering,
this stuff just makes sense
Lessons Learned

36. Lessons Learned
• Don’t agonize over terms
– They don’t matter!
– Nobody wants to hear them
• Adapt faster
– Keep an open mind and keep plans flexible
– Roadmaps are so 1990

37. Lessons Learned
• Technology only matters when it doesn’t work
– People don’t care how cars, ATMs, Mass Transit,
Major Appliances (…) and the Internet work
– Give them what they want and be happy
• Process doesn’t have to be permanent
– An interim solution is acceptable to most people
– Change as the technology involved changes

38. Lessons Learned
• Level of detail should scale
– Drill-down / Summarize options are important
• Sooner is better than perfect (in most cases)
– People appreciate having something
– People like to influence the ongoing design
– Maybe you never need the perfect thing

39. Lessons Learned
• Focus on what they need – When they need it
– The device they want to use
– We started with the stuff we already had
– Added the stuff we could easily replicate into an
accessible form
– Only then talked about what we had to add

40. It’s coming faster than you
think with very little warning
Future

42. Expand Sources & Capabilities
• Build on success to date
• Replicate additional data sources
into web-accessible platforms
• Add GIS capability to Emergency
Response
• Continue to explore Power BI and
Seattle Cloud capabilities
This does nothing but
grow going forward

43. Daniel Antion
Vice President Information Services
American Nuclear Insurers
dantion@nuclearinsurance.com
http://noFacilities.com

45. Attributions
1. Bob – From Office Space – Best IT movie ever
(this is a official review, I get to use photo)
2. Noun Project (we subscribe)
3. Situationally-Relevant Information – Thornton
May case study on ANI
4. I heard Andrew McAfee (MIT) quote Lew Pratt
during a keynote address at the old Enterprise
2.0 conference.
5. Ed Everett VP Engineering, ANI – Find – Measure
– Mitigate – Respond