OpenText Documentum is a full-fledged and mature server-based Document Management System which is accepted e.g. by the FDA and therefore widespread in pharmaceutical companies.
Compared with cloud computing technologies that are very strong in providing elastic (scalable) services OpenText Documentum products could be regarded as inflexible and monolithic / layered applications. Although they seem to be the exact opposite of the flexible Microservice architecture approach used for cloud native application design, there are ways to combine OpenText Documentum products with cloud computing technologies. read more
I usually write blog posts about general IT trends and about the paths and aberrations of digital transformation. I have always avoided writing articles about us, fme AG. Today, for once, I want to break that rule. Sometimes you walk out of a customer meeting and ask yourself: “What in God’s name do some so-called cloud consultants tell clients? Why are they confusing their clients more than neutrally showing them the options for the way to the cloud?
The list of ways a company can leverage its applications into the cloud is long. Thus also a term variety prevails which is confusing.
In today’s world, companies need to act quickly and remain flexible. Cloud-based platforms offer the optimal basis for this. In industrial manufacturing, the use of the cloud has been established for some time. The life sciences industry is just taking off in this area.
The term »cloud« has been a constant companion in the IT industry for almost ten years now. But everyone has different ideas about it. Some of the definitions differ greatly from each other, so that every discussion about “cloud” starts with a joint definition of terms.
Containers, here I will call them more specific Linux containers, are in short modularized software installations. Think of a container as an isolated area with a self-contained service. The container consists of all dependent software the service needs to run. Each container / service can connect to other containers / services. Because the containers are isolated to each other, they are not able to interfere with others in terms of software versions and runtime behavior. For each container you can plan separately on which Linux operating system, web server, language interpreter, etc. your service will rely on — which best fits to your needs. That means, that for example for excessive use of threading or performance needs a single service could be written in Go Lang based on Alpine, while another one uses Apache with PHP also on Alpine and a third one needs to comply with prerequisites using Tomcat with Java on CentOS. All this is possible with containers even running on the same host.
Last week I attended the Tech-Conference of Amazon Web Services – AWS re:Invent 2017 in Las Vegas. It lasted five days, a period of time that is not always easy to take off from your daily work. Following are the most important pieces of content from my perspective in 7-10 min for reading.
* 10 Seconds Management Spoiler *
Serverless, Machine Learning, the Machine Learning Camera DeepLens, Alexa for Business and Kube as a managed service are the main highlights of this year’s re:Invent. By extending and making existing and established services such as EC2, S3, Glacier or DynamoDB more flexible, AWS helps customers to map many requirements directly in the managed service and reduce the need for workaround implementations. It will be fascinating and at times frightening, what will be possible in the future due to the combination of these powerful services.
In my last blog post, ‘Digital Transformation Is About More than Just IT,’ I wrote about a fortunate trend, whereby more and more companies are taking a more holistic approach to the digital transformation. We know that IT alone is not the solution to the challenges posed by the digital transformation. More and more companies are slowly realizing that the digital transformation affects not only the IT department but also all other areas of the company.
But training courses and consulting services that are currently being offered give a different impression. Discussions revolving around the digital transformation primarily address the challenges in today’s business world, and terms such as ‘agility’ and ‘new business models’ crop up as the important key terms. Well-known companies that were once successful are mentioned as examples of organizations that did not manage to get on the right path towards digitalization. The training courses and consulting services then frequently put forward new IT procedures and technologies – such as cloud computing, microservices, DevOps, and big data – as solutions to the challenges of our time. However, IT departments are often not trusted to successfully introduce such modern solutions.
I’ve been in the Document Management System (DMS) / Enterprise Content Management System (ECMS) market for more than 20 years. Sometimes very focused on a specific aspect e.g. Technical Documentation, sometimes more general e.g. ECMS platform and sometimes with focus on an industry segment e.g. Life Science. I have seen a lot of vendors, products and technologies coming and going. The latest acquisition and certainly the biggest one was just a week ago. Hopefully, this will not reduce the power of innovation.
Preface: From January 2016 to July 2016, I wrote my master’s thesis at fme in Brunswick, Germany. In the following blog post I am summarizing my thesis and thank all these people who supported me. Especially, my advisor and the IT department.
Tobias Stein, September 2016
Exponential data growth rates make the management of content an enormous challenge for organizations. Terms like »information overload« and »content chaos« express the inefficient situation regarding content management on an enterprise-wide scale. Employees search for documents in different versions, languages and formats across various repositories and systems through the entire company. However, these documents contain important and decision-relevant information that are becoming a key business resource. Moreover, compliance with statutory regulations and technical requirements with respect to storing huge amounts of data are complicated.