I’ve been seeing an uptick in interest in digital preservation recently. We are a few decades into the digital age and even without the push to digitally transform everything, people are realizing that they have a lot of digital information. I am surrounded by people who are using a digital records system I put in place over a decade ago. This puts that system into the realm of digital preservation. As per AIIM in their 2017 Digital Preservation Market Research:
The capabilities to ensure the readability and usability of digital information that must be retained for longer than 10 years.
I used to think ten years was a long time. It isn’t. People are also realizing that while storing large volumes of electronic documents is easier than paper, you have to take greater care. I have books that are older than 100 years in my house. The only accessible, viable, digital content I have over 25 years old are some music compact discs.
As we create more and more digital information, we need to start thinking more about long-term preservation.
In 2014, the White House issued a Presidential Memorandum on Modernizing and Streamlining the U.S. Immigrant Visa System for the 21st Century. It called for the Department of Homeland Security (DHS) and the Department of State (DoS) to streamline and improve the legal immigration system. Specifically, it spells out the need to :
Modernize the information technology infrastructure underlying the visa processing system with the goal to reduce redundant systems, improve the experience of applicants, and enable better oversight.
As part of our ongoing support of the U.S. Citizenship and Immigration Service (USCIS), TeraThink was engaged to implement a digital solution to automate USCIS’ implementation. The solution required integration not only with USCIS’ own internal modernization program, but also that of other Federal agencies. We took an API first approach, using MuleSoft to orchestrate all the interactions between the different players. The end result was a successful launch and the creation of a new content services foundation for USCIS.
In an earlier blog, I wrote about a couple of takeaways regarding improvements to the ServiceNow platform from our trip to Knowledge18, Those weren’t the only key takeaways from ServiceNow’s annual conference. There was a lot of focus on improving the user experience for both the producers and consumers of ServiceNow’s features and value. Having seen many projects succeed or fail based not upon features but upon user experience, this was exciting to see.
In May, my colleagues and I attended ServiceNow’s annual conference, Knowledge18. We joined over 18,000 attendees in Las Vegas to meet, learn, share, and collaborate on all things ServiceNow. They presented a wide range of valuable content spanning all aspects of the platform. This ranged from in-depth solution-focused sessions, to industry-based workshops, to a roadmap of functionality coming to the platform.
Two of my takeaways from the conference centered on the platform improvement and their increased focus on the customer.
Last month I had the pleasure of going to San Antonio for the 2018 AIIM Conference. As always, AIIM hosted some great conversations and informative presentations. Some of the discussions focused around emerging technologies in the information space, blockchain, and artificial intelligence.
Lots of new technology were discussed in a panel run by Alan Pelz-Sharpe. He and his panelists; Andrea Chiappe, Kashyap Kompella, and Dan Abdul; broke the technologies down and how they impact the world of information management. Alan noted that during his preconference session, a surprising number of people were already very familiar with these new technologies. That is a refreshing realization. Broad understanding in the industry is critical towards creating practical applications with any new technology.
Microservices is the latest architectural approach to scaling applications. Their smaller, more atomic size, allows for greater agility as the impact of each iteration is more contained. This makes continuous integration and development easier as the burden of testing is less and deployment iterations are more limited in scope.
As we look to utilize Mule, and other systems, in this environment, we need to make sure that their configurations can automatically reflect their environment. As we build applications at scale and move out of the development lab, this becomes a real need. Luckily, the Spring Cloud Configuration server lets us do exactly that.
A few weeks back, I spoke on an Information Coalition webinar with Nick Inglis about getting Beyond the Hype of Content Services. We discussed content services and tried to separate the reality from the hype. If you been following, there is a lot of hype out there and has been since Gartner stopped tracking ECM (enterprise content management) and switched to content services. This has fed people’s instinct to equate content services with ECM. Many vendors and consultants are now taking their marketing messaging and simply substituting one term for the other. Even more distracting are people that reflexively reject content services because they assume the person using the term is just doing a term swap.
The truth is that content services is not ECM. It is an approach to implementing solutions that support an ECM strategy and providing sound information governance. Content services doesn’t eliminate the need for an ECM strategy or information governance. In fact, if you don’t have a strategy or proper governance, you might end up addressing the wrong things.
You still need a plan. To determine how to implement it, you need to know what content services is and how it can make a difference.
TeraThink recently attended the 2018 Association of Government Accountants (AGA) National Leadership Training (NLT) symposium in Washington D.C. It was our first AGA event since rolling out our expanded offerings after our merger with Dominion Consulting. I attended with Jim Levitan, Howard Campbell, Leslie Hubbard-Darr, Matt Duffy, and Rodney Taylor.
Held February 27-28, the 2018 NLT was one of the largest ever, with 862 participants. The conference served as an excellent platform to learn about the latest trends in Federal financial management in a shared-experience environment. Additionally, it helped showcase TeraThink services at our booth in the exhibitor’s hall.
Recently, I was at the local NCC-AIIM Chapter meeting. Russ Stalters was visiting from Texas and shared the story about how he created a new, 200+ person, data management team for the BP Gulf Coast Restoration Organization. A separate organizational entity from BP, the organization was stood up in 90 days from vision to operation. It was an impressive tale involving massive amounts of information being absorbed and managed in a highly visible environment.
As Russ spoke, it became clear that two of the key lessons were around agile processes and content analytics. It generated some great discussion that took us well past the scheduled time. I wanted to take some time to share some of the highlights.
As success with DevOps continues to make progress, it ventures into taking on other areas where traditional SDLC / IT practices have been less than optimal. Alongside this need, the IT Security technical landscape has been in rapid transition, making it near impossible for security teams to keep up with both increased DevOps velocity and the changing security landscape. Now, teaming up security in the continuous integration (CI) and continuous delivery (CD) model has a potential to be a game changer.
In the beginning, the movement started out being called DevOpsSec. ‘Sec’ was appended on to the end – almost like a caboose on a train – an afterthought. But in reality, security must be thought of, designed, and practiced throughout the process. In light of this, the more current term is DevSecOps – one where we weave security into our integration. Originally, marketing hype from each security software vendor clouded the concept. But, the movement is less about tools, and more about the way in which we work together, in parallel.