Category Archives: Standards

The ArchiMate Language as a Foundation for Enterprise Assessment and Transformation

By Iver Band, Enterprise Architect, Cambia Health Solutions and Vice Chair, The Open Group ArchiMate Forum

An Interview with Jan van Gijsen of VIVAT

By Iver Band, Enterprise ArchitectJan is a Senior IT Architect at VIVAT NV, a Netherlands-based insurer and asset manager.  VIVAT has six brands:  Zwitserleven for pension capital management, Zelf for online insurance, Route Mobiel for roadside assistance, travel, and auto insurance;  Reaal for life, property & casualty, and disability insurance; Proteq Dier & Zorg for pet insurance, and ACTIAM for institutional asset management.  In July 2015, VIVAT was acquired by Anbang Insurance Group of China. In its 2015 annual report, VIVAT NV reported over €60 billion in total assets, €4.375 billion in total income, and €109 million in profit. Right now, VIVAT has approximately 3,600 employees, including 630 in IT.

 

Iver: Please briefly describe your professional background and current role at VIVAT.
Jan: I have worked in IT for more than 35 years, the last 15 years as an IT Architect. At the moment I am responsible for the overall use and standardization of ArchiMate® models within the Architecture Department and the analysis and reporting on a consolidated VIVAT level based on these models. Particular concerns are roadmaps, cost management and portfolio management.

Iver: What challenges does the Architecture Department face now that VIVAT is part of the Anbang Insurance Group?
Jan: VIVAT is embarking upon a new phase, which will allow it to place full focus on its policyholders and existing and new customers based upon a new strategy for the future. During the second half of 2015, a thorough and extensive Strategic Review was carried out under the supervision of the new Executive Board. Going forward, VIVAT will focus more on innovation and digitalization, along with plans to further simplify its business processes. VIVAT will also make its organization less complex. Simplifying the operations and the business processes will create a lean, customer-oriented organization. Ultimately, customers will be better served by the company.

VIVAT will implement these change over the course of three years, during which it will create one centralized structure. The company will continue its ongoing digitalization effort and adapt to technological developments, drawing on the innovative capability and experience of its new owner.

Iver: How is the architecture function organized at VIVAT?
Jan: The architecture function is centralized in one department. Within the department the work is organized around the business domains such as Life, Corporate, Individual Life, Property & Casualty, Asset Management and VIVAT.

Iver: Tell me more about the VIVAT domain.
Jan: Our new strategy is driven by the theme “One VIVAT”, which transcends our historic domain silos.  The VIVAT domain provides consolidated views of the entire company and the base for common functionality and strategy across the business domains. We use architectural views of the VIVAT domain as overviews of what is going on in the business domains.

“ArchiMate has been in use since 2006.”

Iver: What is VIVAT’s experience with the ArchiMate language?
Jan: ArchiMate has been in use since 2006. It is mainly used by twelve architects to create, analyze and calculate models.  It is also used by four software engineers for integration designs.

“All the architects are ArchiMate certified.”

Iver: How does VIVAT support architects and engineers in using the language effectively?
Jan: We had a formal training at BiZZdesign and all the architects are ArchiMate certified. For standardization, coaching and review we have an ArchiMate Competence Center with three architects. I am the chairman of this competence center. Most importantly, modelers learn by doing and discover what is working and what is not. For this purpose, we had additional training on stakeholder management and selling skills.

Iver: How is ArchiMate used to support VIVAT’s businesses and corporate functions?  Does usage vary across different areas of the business?
Jan: For every business domain we create and maintain blueprints, which contain the baseline, transition and target models for the three architecture layers: Business, Application and Technology. The details and content depend on the planned changes within the domains. Each blueprint also contains a roadmap with the cost forecast for the next four years. These forecasts are calculated using ArchiMate models.

Iver: Did ArchiMate models play any role in the decision-making and planning for the acquisition by Anbang?
Jan: ArchiMate models were used to show the IT baseline, future plans and cost forecast.  In addition, our ArchiMate models enabled us to respond very quickly to additional questions regarding our IT landscape.

“This opened the door to our decision makers.”

Iver: What have been VIVAT’s greatest successes with the ArchiMate language?
Jan: Developing the roadmaps and cost calculations, and embedding the models in the portfolio and cost management processes. This opened the door to our decision makers.

“You have chosen ArchiMate as a standard.  From now on, you are going to use it as a standard.”

Iver: What have been VIVAT’s greatest challenges with the ArchiMate language?
Jan: Forcing every architect to use ArchiMate exclusively for modeling, and to get rid of all the Visio and PowerPoint models. The breakthrough occurred when my manager told the architects “You have chosen ArchiMate as a standard.  From now on you are going to use it as a standard.”

Iver: What software tools does VIVAT use for ArchiMate modeling?
Jan: BiZZdesign Enterprise Studio.

Iver: Does VIVAT maintain a repository of ArchiMate models?
Jan: We use the BiZZdesign repository. Within the repository we maintain separate models for each business domain. Shared objects are synchronized with a catalog which contains all the standard objects and relations, along with the costing and roadmap information.  This is not an out-of-the-box configuration; it was designed by us.

Iver: Where does the information in the catalog come from?
Jan: The catalog is synchronized with the CMDB for infrastructure and several application portfolio lists. These lists are consolidated in the ArchiMate catalog.  For applications, the catalog is also the base for other functions like cost and incident management. The other parts like processes, organization and relations are extracted from previous models to be reused in new models.

Iver: Let’s return to your personal perspective.  How do you use the ArchiMate language?
Jan: I use ArchiMate more and more as a metamodel to do analysis and reporting, based on a solid repository with all the objects within VIVAT. I use the ArchiMate structures to combine information from several sources for analysis.  I use, for instance, data from contract administration, configuration management (CMDB), planning and administration and the general ledger. The reports contain the results of the analysis as simple graphs or tables with, sometimes, simple ArchiMate models appended. The results of these analyses are stored in the repository and can be used by the other architects to color or label their models.

“Don’t show any models to the decision makers; only show them the results of the analysis of your models.”

Iver: For what business and IT situations would you recommend ArchiMate modeling?
Jan: That depends on the stakeholder with whom you are working. Don’t show any models to the decision makers; only show them the results of the analysis of your models.  For us, ArchiMate is very useful for portfolio and cost management but that depends very much on the maturity of the architecture function and the portfolio and cost management processes. ArchiMate is also very useful for guiding strategic change and application rationalization.

Iver: What do you think of ArchiMate 3.0?
Jan: I have taken a quick look and am very enthusiastic about the extensions around capabilities. For us, that fills in some missing pieces.

“Start small, think big.”

Iver: Do you have any advice for architects who are just starting to use the language?
Jan: Start small, think big. Start with a few architects using an ArchiMate modeling tool. Don’t flatten creativity by defining modelling standards before you have given yourself a chance to discover the strength of the tool and the ArchiMate standard. Once you have experienced how you want to use the tool, then define your standards. Be pragmatic with your standards. Modeling is about the message to your stakeholders and not about following a standard. Force yourself to create all your models in ArchiMate–even small sketches.

Iver: How should organizations select ArchiMate modeling tools?
Jan: First decide how you want to use the tool: for just modeling or also analysis. It also depends on have many people are going to use the tool and if they will have shared or separate models. This will give you the requirements on functionality and cooperation. A simple tool is suitable for just modeling with a few people on separate models. For analysis and a lot of users you need richer functionality, including scripting facilities. For cooperation among a lot of people you need a repository with the ability to control access to models.

Iver: Thank you very much for sharing your deep experience and expertise.  Any final thoughts on how the ArchiMate language can help enterprise and solution architects?
Jan: Formal modelling languages force architects to think more carefully about what they are specifying, so they perform at a higher level. Also, formal models are suitable for analysis and calculations for presentation to senior management, which opens the door to the boardroom and increases the influence of the architecture function.

By Iver Band, Enterprise ArchitectIver Band is an Enterprise Architect at Cambia Health Solutions, where he uses the ArchiMate language continuously to develop strategic architectures, guide solution development, and train other architects. Iver is also Vice Chair of The Open Group ArchiMate Forum, co-author of the ArchiMate certification exams, and a frequent writer and speaker on Enterprise and Solution Architecture.  Iver is TOGAF and ArchiMate Certified, a CISSP, and a Certified Information Professional.

 

ArchiMate® is an Open Group standard.

http://www.opengroup.org  @theopengroup  @ArchiMate_r   #ArchiMate

1 Comment

Filed under ArchiMate®, Enterprise Architecture, Standards, standards, The Open Group, Uncategorized

The Open Group Austin 2016 Event Highlights

By Loren K. Baynes, Director, Global Marketing Communications, The Open Group

During the week of July 18th, The Open Group hosted over 200  attendees from 12 countries at the Four Seasons hotel on the beautiful banks of Lady Bird Lake in Austin, Texas, USA.

On Monday, July 18, Steve Nunn, President and CEO of The Open Group, welcomed the audience and set the stage for all the great upcoming speakers and content.

Steve’s remarks included the recent release of the Open Business Architecture (O-BA) Preliminary Standard Part I to Support Business Transformation.  This is the first in a series of installments that will help Business Architects get to grips with transformation initiatives and manage the demands of key stakeholders within the organization. Steve also referenced William Ulrich, President, Business Architecture Guild, who consulted on the development of the standard.

The plenary began with Jeff Scott, President, Business Innovation Partners, with his presentation “The Future of Business Architecture, Challenges and Opportunities”.  Jeff stated some interesting facts, which included noting that Architects are among the best and brightest members of our organizations.  He also stated that Business Architects need support from a wide group of senior managers, not just the CEO. The ultimate goal of Business Architecture is not to model the organization but to unlock organizational capacity and move forward.

By Loren K. Baynes

Jeff Scott

The Business Architecture (BA) theme continued with Aaron Rorstrom, Principal Enterprise Architect, Capgemini.  Aaron further elaborated on The Open Business Architecture (O-BA) Standard.  The O-BA Standard provides guidance to companies for establishing BA practice and addresses three transformation challenges: consistent communication, alignment and governance, systemic nature.

The sessions were followed by Q&A moderated by Steve Nunn.

Up next was “ArchiMate® 3.0 – A New Standard for Architecture” with Marc Lankhorst, Managing Consultant and Service Line Manager, Enterprise Architect, BiZZdesign and Iver Band, Enterprise Architect, Cambia Health Solutions.

Marc and Iver discussed practical experiences and a Healthcare case study, which included a discussion on personal health and wellness websites.

ArchiMate®, an Open Group standard, provides a language with concepts to describe architectures; a framework to organize these concepts; a graphical notation for these concepts; a vision on visualizations for different stakeholders. ArchiMate 3.0 has recently been released due to: the increasing demand for relating Enterprise Architecture (EA) to business strategy; technology innovations that mix IT and physical world; usage in new domains (i.e. manufacturing, healthcare, retail); improved consistency and comprehensibility; improved alignment between Open Group standards, notably TOGAF®.

The final session of Monday’s plenary featured a panel on “Architecture Standards Development” with Marc Lankhorst, Iver Band, Mike Lambert (Fellow of The Open Group) and Harry Hendrickx (Business Architect, Hewlett Packard Enterprise).  Moderated by Chris Forde, GM, Asia Pacific and VP, Enterprise Architecture, The Open Group, the panel represented a diverse group of the population contributing to the development of open standards.

In the afternoon, sessions were divided into tracks – Security, ArchiMate, Open Business Architecture.

Don Bartusiak, Chief Engineer, Process Control, ExxonMobil Research & Engineering presented “Security in Industrial Controls – Bringing Open Standards to Process Control Systems”.  Don went into detail on the Breakthrough R&D project which is designed to make step-change improvement to reduce cost to replace and to increase value generation via control system.  ExxonMobil is working with The Open Group and others to start-up a consortium of end user companies, system integrators, suppliers, and standards organizations for sustained success of the architecture.

Also featured was “Applying Open FAIR in Industrial Control System Risk Scenarios” by Jim Hietala, VP, Business Development and Security, The Open Group.  The focus of ICS systems is reliability and safety.  Jim also shared some scenarios of recent real life cyberattacks.

The evening concluded with guests enjoying a lively networking reception at the Four Seasons.

Day two on Tuesday, July 19 kicked off the Open Source/Open Standards day with a discussion between Steve Nunn and Andras Szakal, VP & CTO, IBM U.S. Federal. Steve and Andras shared their views on Executable Standards: convergence of creation of open source and innovation standards; the difference between Executable Standards and traditional standards (i.e. paper standards); emergence of open source; ensuring interoperability and standardization becomes more effective of time. They further explored open technology as driving the software defined enterprise with SOA, social, Open Cloud architecture, e-Business, mobile, big data & analytics, and dynamic cloud.

A panel session continued the conversation on Open Standards and Open Source.  The panel was moderated by Dave Lounsbury, CTO and VP, Services for The Open Group.  Panelists were Phil Beauvoir, Archi Product Manager, Consultant; John Stough, Senior Software Architect, JHNA, Inc.; Karl Schopmeyer, Independent Consultant and representing Executable Standards activity in The Open Group.  Topics included describing Archi, Future Airborne Capability Environment (FACE™, a consortium of The Open Group) and OpenPegasus™, an open-source implementation of the DMTF, CIM and WBEM standards.

The Open Group solves business problems with the development and use of open standards.  Interoperability is key.  Generally, no big barriers exist, but there are some limitations and those must be realized and understood.

Steve presented Karl with a plaque in recognition of his outstanding leadership for over 20 years of The Open Group Enterprise Management Forum and OpenPegasus Project.

Rick Solis, IT Business Architect, ExxonMobil Global Services Co. presented “Driving IT Strategic Planning at IT4IT™ with ExxonMobil”.  Business is looking for IT to be more efficient and add value. ExxonMobil has been successfully leveraging IT4IT concepts and value chain. The IT4IT™ vision is a vendor-neutral Reference Architecture for managing the business of IT.  Rich emphasized people need to think about the value streams in the organization that add up to the business value.  Furthermore, it is key to think seamlessly across the organization.

Joanne Woytek, Program Manager for the NASA SEWP Program, NASA spoke about “Enabling Trust in the Supply Chain”.  SEWP (Solutions for Enterprise-Wide Procurement) is the second biggest IT contract in the US government.  Joanne gave a brief history of their use of standards, experience with identifying risks and goal to improve acquisition process for government and industry.

Andras Szakal again took the stage to discuss mitigating maliciously tainted and counterfeit products with standards and accreditation programs.  The Open Trusted Technology Provider™ Standard (O-TTPS) is an open standard to enhance the security of the global supply chain and the integrity of Commercial Off The Shelf (COTS) Information and Communication Technology (ICT). It has been approved as an ISO/IEC international standard.

Afternoon tracks consisted of Healthcare, IT4IT™, Open Platform 3.0™ and Professional Development.  Speakers came from organizations such as IBM, Salesforce, Huawei, HPE and Conexiam.

The evening culminated with an authentic Texas BBQ and live band at Laguna Gloria, a historic lakefront landmark with strong ties to Texas culture.

By Loren K. Baynes

The Open Group Austin 2016 at Laguna Gloria

Wednesday, July 20 was another very full day.  Tracks featured Academia Partnering, Enterprise Architecture, Open Platform 3.0 (Internet of Things, Cloud, Big Data, Smart Cities), ArchiMate®.  Other companies represented include San Jose State University, Quest Diagnostics, Boeing, Nationwide and Asurion.

The presentations are freely available only to members of The Open Group and event attendees.  For the full agenda, please click here.

In parallel with the Wednesday tracks, The Open Group hosted the third TOGAF® User Group Meeting.  The meeting is a lively, interactive, engaging discussion about TOGAF, an Open Group standard.  Steve Nunn welcomed the group and announced there are almost 58,000 people certified in TOGAF.  It is a very large community with global demand and interest.  The key motivation for offering the meeting is to hear from people who aren’t necessarily ‘living and breathing’ TOGAF. The goal is to share what has worked, hasn’t worked and meet other folks who have learned a lot from TOGAF.

Terry Blevins, Fellow of The Open Group, was the emcee.  The format was an “Oxford Style” debate with Paul Homan, Enterprise Architect, IBM and Chris Armstrong, President, Armstrong Processing Group (APG).  The Proposition Declaration: Business Architecture and Business Architects should be within the business side of an organization. Chris took the ‘pro’ position and Paul was ‘con’.

Chris believes there is no misalignment with Business and IT; business got exactly what they wanted.  Paul queried where do the Business Architectures live within the organization? BA is a business-wide asset.  There is a need to do all that in one place.

Following the debate, there was an open floor with audience questions and challenges. Questions and answers covered strategy in Architecture and role of the Architect.

The meeting also featured an ‘Ask the Experts’ panel with Chris Forde; Jason Uppal, Chief Architect, QRS; Bill Estrem, TOGAF Trainer, Metaplexity Associates; Len Fehskens, Chief Editor, Journal of Enterprise Architecture, along with Chris Armstrong and Paul.

Organizations in attendance included BMC Software, City of Austin, Texas Dept. of Transportation, General Motors, Texas Mutual Insurance, HPE, IBM.

A more detailed blog of the TOGAF User Group meeting will be forthcoming.

A special ‘thank you’ to all of our sponsors and exhibitors:  avolution, BiZZdesign, Good e-Learning, Hewlett Packard Enterprise, AEA, Orbus Software, Van Haren Publishing

@the opengroup #ogAUS

Hope to see you at The Open Group Paris 2016! #ogPARIS

By Loren K. BaynesLoren K. Baynes, Director, Global Marketing Communications, joined The Open Group in 2013 and spearheads corporate marketing initiatives, primarily the website, blog, media relations and social media. Loren has over 20 years experience in brand marketing and public relations and, prior to The Open Group, was with The Walt Disney Company for over 10 years. Loren holds a Bachelor of Business Administration from Texas A&M University. She is based in the US.

 

 

Comments Off on The Open Group Austin 2016 Event Highlights

Filed under Accreditations, ArchiMate, ArchiMate®, Association of Enterprise Architects, Business Architecture, Business Transformation, Certifications, Cloud, COTS, Cybersecurity, digital technologies, Digital Transformation, EA, enterprise architecture, Internet of Things, Interoperability, Jeff Kyle, O-TTPS, Open FAIR, Open Platform 3.0, Professional Development, Security, Standards, Steve Nunn, The Open Group Austin 2016, TOGAF®, TOGAF®

The Open Group Launches the Open Business Architecture (O-BA) Preliminary Standard Part I to Support Business Transformation

The first release of a three part standard designed to improve alignment, governance and integration between the different aspects of business transformation projects

The Open Group, the vendor-neutral IT consortium, has today launched the Open Business Architecture (O-BA) Preliminary Standard Part I, an Open Group standard. The standard focuses on transformations to the enterprise or organization, defining an approach that ensures a clear understanding of the business vision by all stakeholders throughout the enterprise transformation lifecycle. Working in accordance with the standard enhances alignment, governance, and integration between all aspects of business transformation projects.

O-BA Part I describes the practice through a Business Architecture framework called the five-ways framework, the structural challenges it tries to resolve, and how these are resolved by applying the standard. Part I is focused on decision-making and direction-setting.

Developed by The Open Group Governing Board Business Architecture Work Group, this is the first installment of a three-part standard. Combined, the three parts of the standard will explicitly address all aspects of a business architecture practice. Not only will it examine the holistic approach in modeling required, but also the way of working and thinking, as well organizing and supporting.

The standard clearly defines the systemic nature of transformations, the varying interests and goals of stakeholders, and prepares for consistent communication of business priorities and needs throughout the transformation lifecycle. It addresses a real need to solve structural challenges in enterprise and organizational transformations.

O-BA Part I is being published initially as a Preliminary Standard since it addresses an emerging area of best practice. It is therefore subject to change before being published as a full Open Group Standard in due course.

“The Open Business Architecture Standard Part I is the first in a series of installments that will help Business Architects get to grips with transformation initiatives and manage the demands of key stakeholders within the organization,” commented Steve Nunn, President and CEO, The Open Group. “Organizations must now take advantage of open standards like O-BA, to support infrastructures that can enable the kind of Boundaryless Information Flow™ today’s digital enterprises need.”

William Ulrich, President, Business Architecture Guild, who has consulted on the development of the standard, added, “Business architecture continues to expand globally, across multiple industries. This is exemplified by the expansion of the discipline at the grassroots level and across standards organizations. Business architecture has reached a stage where business executives are not only taking notice, but taking action.”

“This standard is an answer to the increasing need for a modern practice, as we observe in many communication service providers transforming to digital service providers: focused on business value, centered on customer experience and open to the digital industry ecosystem”, said Giovanni Traverso, Principal Enterprise Architect at Huawei Technologies, Global Technical Services, who are a Platinum member of The Open Group.

Open Business Architecture (O-BA) – Part I, is available to download as a pdf from The Open Group website, and was presented to attendees at The Open Group Austin Event on July 18th.

Global Business Communications

@theopengroup #ogAUS

1 Comment

Filed under Boundaryless Information Flow™, Business Architecture, Business Transformation, Enterprise Architecture, Standards, The Open Group Austin 2016, Uncategorized

The Cloud: What’s UNIX® Got to Do With It?

By The Open Group

Cloud computing has come of age and is the solution of choice for CIOs looking to maximize use of resources while minimizing capital spend.[1] Cloud solutions, whether it is infrastructure, platform or service, have the appeal of business agility[2], without having to understand what is “under the hood”. However, what’s under the hood becomes even more important in a Cloud environment because there can be multiple services running with potential impact on numerous customers and the services provided to them.  For software as a service (SaaS) and platform as a service (PaaS) the hosting operating system is a critical component included in with Cloud environment as it directly impacts the performance of the Cloud solution. For infrastructure as a service (IaaS) the operating system is a critical choice made by the customer.

The CIO View

The CIO loves the idea of having the ability to rapidly provide on-demand ubiquitous computing resources to their company without the management overhead and integration challenges. The hardware infrastructure, network infrastructure, storage, hypervisor and OS must have high availability, scalability, and performance to meet the “5-nines” reliability expected (SCIT Report) with the operating system being especially critical component in that stack.[3]

UNIX, A Robust Platform for Cloud:

The Cloud needs to be highly available, scalable, secure, and robust for high-demand computing.  A certified UNIX® OS can provide this and enables companies to innovate in the Cloud.  A CIO would be looking at each element of the stack with a high degree of assurance that the Cloud solution has been well tested and has proven system and application interoperability, which also simplifies solution integration. The UNIX OS amplifies this simplicity delivering peace of mind for IT directors and above.

Who Is Choosing a UNIX Cloud?

Cloud Solution/Hosting Providers look to a UNIX Cloud infrastructure to service financial institutions looking to support high transactional environments like online and mobile banking marketplace.[4] Moreover, UNIX Cloud infrastructure provides a cost-effective, secure, and redundant environment.[5]

“Verizon serves both customers and employees with a UNIX Cloud infrastructure that implements enhanced agility, superior performance, easy maintainability, and effective cost control,” said Chris Riggin, Enterprise Architect at Verizon.[6]

HPE, IBM, and Oracle have expanded their services offerings to deliver UNIX mission-critical cloud and enterprise infrastructure, including their branded systems.  These UNIX Cloud solutions help their customers continue to scale while delivering business continuity and a low total cost of ownership.[7]

By The Open Group

Get more tools and resources on UNIX innovation on www.opengroup.org/UNIX or review these other resources today:

@theopengroup

© 2016 The Open Group

UNIX® is a Registered Trademark of The Open Group. Oracle® Solaris is a registered trademark of Oracle Corporation. IBM AIX is a trademark of IBM Corporation. HP-UX is a registered trademark of HPE.

 

[1] Harvard Business Review, Cloud Computing Comes of Age, Page 3, 2015, https://www.oracle.com/webfolder/s/delivery_production/docs/FY15h1/doc16/HBR-Oracle-Report-webview.pdf

[2] Harvard Business Review, Cloud Computing Comes of Age, Page 3, 5, 6; 2015, https://www.oracle.com/webfolder/s/delivery_production/docs/FY15h1/doc16/HBR-Oracle-Report-webview.pdf

[3] UNIX: The “Always On” OS, 2016, https://blog.opengroup.org/2016/04/18/unix-the-always-on-os/

[4] Connectria / Sybase Customer Success Story:  http://www.connectria.com/content/case_studies/connectria_flyer_sybase_case_study.pdf

[5] Connectria AIX Hosting: http://www.connectria.com/technologies/aix_hosting.php

[6] UNIX Based Cloud, Harry Foxwell, Principal Consultant, Oracle, February 2016, https://blog.opengroup.org/2016/02/03/the-unix-based-cloud/

[7] a. http://www8.hp.com/us/en/business-solutions/solution.html?compURI=1167850#.VyfQzD9EmPB

  1. https://www.openstack.org/marketplace/distros/distribution/oracle/oracle-openstack-for-oracle-solaris
  2. http://www-03.ibm.com/systems/power/solutions/cloud/

 

Comments Off on The Cloud: What’s UNIX® Got to Do With It?

Filed under Cloud, cloud computing, The Open Group, Uncategorized, UNIX

UNIX®, an Open Group Standard, Makes ISV Engineering’s Job Easier

By Caryl Takvorian, Staff Engineer, Oracle

We deal with hundreds of applications on a daily basis at Oracle® ISV Engineering. Most of them need to support multiple operating systems (OS) environments including Oracle Solaris. These applications are from all types of diverse industries – banking, communications, healthcare, gaming, and more. Each application varies in size from dozens to hundreds of millions of lines of code.

We understand the real value of standards, as we help Independent Software Vendors (ISVs) support Oracle Solaris. Oracle Solaris is UNIX certified and conforms to UNIX, an Open Group standard, providing assurance of stable interfaces and APIs. (NOTE: The UNIX standard is also inclusive of POSIX interface/API standard).  ISVs and application developers leverage these stable interfaces/APIs to make it easier to port, maintain and support their applications. The stable interfaces and APIs also reduce the overhead costs for ISVs as well as for Oracle’s support of the ISVs – a win-win for all involved. ISVs can be confident that the UNIX operating system, the robust foundation below their application, won’t change from release to release.

Oracle Solaris is unique in which it goes the extra mile by providing a binary application guarantee since its 2.6 release. The Oracle Solaris Binary Application Guarantee reflects the confidence in the compatibility of applications from one release of Oracle Solaris to the next and is designed to make re-qualification a thing of the past. If a binary application runs on a release of Oracle Solaris 2.6 or later, including their initial release and all updates, it will run on the later releases of Oracle Solaris, including their initial releases, and all updates, even if the application has not been recompiled for those latest releases. Binary compatibility between releases of Oracle Solaris helps protect your long-term investment in the development, training and maintenance of your applications.

It is important to note that the UNIX standard does not restrict the underlying implementation. This is key particularly because it allows Oracle Solaris engineers to innovate “under the hood”. Keeping the semantics and behavior of system calls intact, Oracle Solaris software engineers deliver the benefits of improved features, security performance, scalability, stability, etc. while not having a negative impact on application developers using Oracle Solaris. A sample list of applications supporting Oracle Solaris 11 can be found here.

By Caryl Takvorian, Staff Engineer, Oracle

Caryl Takvorian is a Principal Engineer in the Oracle ISV Engineering organization where he is the Solaris, Security and Telco lead. He has more than 20 years of experience with Solaris at Sun Microsystems, and now Oracle, helping ISVs adopt new technologies and develop software on Solaris. He joined SunSoft’s Developer Support organization in the UK in 1998 and from there moved to Market Development Engineering and now ISV Engineering at Oracle.

Caryl holds a French computer science engineering degree as well as an MSc in computer science from a US university. He lives near Southampton with his wife and his 4-year-old son.

Learn more about UNIX:

UNIX® is a registered trademark owned and managed by The Open Group. POSIX® is a registered Trademark of The IEEE.  Oracle Copyright 2016. All rights reserved.

 

Comments Off on UNIX®, an Open Group Standard, Makes ISV Engineering’s Job Easier

Filed under operating system, Oracle, Standards, UNIX

From Solution to Enterprise Architecture with the ArchiMate® Language:  An Interview with Ryan Kennedy

By Iver Band, Enterprise Architect at Cambia Health Solutions and Vice Chair, The Open Group ArchiMate Forum

I recently sat down with my Cambia Health Solutions colleague Ryan Kennedy.  Ryan is an architect with whom I have worked over the last year and a half on a variety of projects that benefit Cambia’s Healthcare consumer and group customers.  After noticing how Ryan has used the ArchiMate® language to expand his personal contribution to the company, I decided to get his perspective on the language, including the new ArchiMate 3.0 standard.


Iver
: What is your professional background?

Ryan
: Prior to becoming an architect, I was a software development engineer for over a decade, designing and implementing solutions across a broad range of organizations, from stable enterprise to volatile startup.

Iver
: How did you encounter the ArchiMate language?

Ryan
: Part of the onboarding process for new architects at my company is a bootcamp-style introduction to the ArchiMate language and its practical application.

Iver
: What were your first impressions?

Ryan
:  My first impression of ArchiMate was that it is very easy to learn if you know Unified Modeling Language (UML).  My second thought was, “Wow, now I can design all the things!”  It is a quantum leap from a grammar that can describe software, to a palate capable of representing the remainder of the enterprise.

Iver
: How have you used the language since then?

Ryan
: I use ArchiMate almost daily, and I treasure the power it gives me to quickly and effectively communicate my solutions to all manner of stakeholders, from business owners to software developers.

Iver
: For what would you recommend the language?

Ryan
: For any aspect of the enterprise that needs design, description or analysis for a broad range of stakeholders.  This includes motivation, strategy, business process, applications, technology, implementation, and migration.

Iver
: What are you doing with the language now?

Ryan:
My current duties mostly revolve around design and estimation of new feature work for sizing, budgeting, and ultimately making implementation choices.  For a new capability, I usually start with the business concerns.  For more technical solutions, I may start at the application or technology layer.  Either way, the traceability of cost and value across layers is what I’m usually trying to communicate at this phase, along with risk analysis.Iver: What are your impressions of the ArchiMate 3.0 language?

Ryan
: Capabilities!  Making capabilities first-class citizens should help us improve our portfolio planning and valuation.  Also, groupings really mean something now which is cool.  If your organization is anything like mine, tagging is important for your data.  Groupings are a great way to tag your ArchiMate concepts.  Also, you may have the same actual concept represented as different ArchiMate concepts in different viewpoints.  Groupings can keep these things together as an abstract, layer-agnostic concept.  Further, you can then describe relationships between aspects of disparate concepts, which should allow a lot more freedom and nuance in your design.Iver: What additional uses of the language do you see based on the 3.0 version?

Ryan
: With the addition of the strategy and physical capabilities, the language is capable of modeling almost any aspect of business or technology.

Iver
: What are your tips for getting started with the language?

Ryan
: Flashcards!  There are a lot of concepts to memorize!  Other than that, my UML background was enough to become fluent in ArchiMate in a few weeks, and I’m fortunate to have expert peer reviews for continuous improvement. If you have no visual modeling background, a formal course is probably in order.
By Iver Band, EA, Cambia SolutionsRyan Kennedy (left) giving his impressions of the ArchiMate language to Iver Band at Cambia Health Solutions in
Portland, Oregon

Iver Band
 is an Enterprise Architect at Cambia Health Solutions, where he uses the ArchiMate language continuously to develop strategic architectures, guide solution development, and train other architects. Iver is also Vice Chair of The Open Group ArchiMate Forum, co-author of the ArchiMate certification exams, and a frequent writer and speaker on Enterprise and Solution Architecture.  Iver is TOGAF and ArchiMate Certified, a CISSP, and a Certified Information Professional.

@theopengroup  @ArchiMate_r  #ArchiMate

1 Comment

Filed under ArchiMate®, Enterprise Architecture, Enterprise Transformation, Standards, standards, The Open Group

UNIX®: Lowering the Total Cost of Ownership

By The Open Group

The value of UNIX, as a technology and as a standard, has clearly been significant over its 45-year history as a technology and its 20-years as an open standard leading to tremendous innovation across numerous industries.  Developers, integrators and customers have benefited from its origins as open development platform to becoming an open standard. Recent blog articles have showcased how UNIX makes software development easier[1], is highly available[2], more secure[3] and scalable.  Total cost of ownership (TCO) is another area that has benefited from the UNIX standard and the operating systems that are UNIX certified.  For this article, TCO is primarily defined as the cost of acquisition, maintenance, and updating of a solution.

UNIX, an Open Group standard, enables customers’ choices in the building blocks for their desired solution. The choices come from the numerous UNIX certified operating systems on the market today – IBM AIX, HPE HP-UX, Inspur K-UX and Oracle Solaris to name a few.  The acquisition cost, as a part of the total cost of ownership, is also lower because of the compatibility and interoperability benefits of the UNIX standard.  IT organizations do not have to spend time fighting integration interoperability and incompatibility issues often found in non-certified operating systems.  Bottom line is that there is greater choice with less integration overhead leading to lower cost of acquisition.

The UNIX standard benefits the maintenance component of TCO ensuring there is compatibility and interoperability at the level of the operating system (OS) and the software dependencies on that OS. A UNIX certified OS also provides assurance of a level of quality with more than 45,000 functional tests having been passed to achieve certification. Of course, the other benefit of the UNIX standard is that it provides consistent system commands regardless of what UNIX OS is running in your data center so you don’t need train administrators on multiple operating systems or even have different administrators for different operating systems. An estimated 49% of system downtime is caused by human error, which should be mitigated by having custom ways to manage systems. UNIX provides greater determinism, which helps reduce maintenance component of TCO.[4]

The UNIX standard improves cost for system updates. While most OS vendors have their own method of doing system updates, there is greater confidence with UNIX compliant OS that regardless of how the update occurs the software and overall solution can rely on the continued assurance of consistent APIs, behavior, etc.  This turns out to be important as solutions get bigger and more complex the need to ensure continuity becomes particularly critical. Having standards in place help ensure that continuity in an ever changing solution.

TCO is greatly reduced because a UNIX certified operating system lowers the acquisition, maintenance and updating costs. The benefits of UNIX mentioned above also hint at reduced administrative, training and operational costs which also reduces the total cost of ownership which also should be consider in evaluating solution cost. IT decision makers should consider how choosing an operating system that is UNIX certified will benefit the TCO profile of their solution(s). This is especially true because making standards a requirement, during acquisition, costs so little yet can have such substantial benefits to TCO, enabling accelerated innovation and demonstrating good IT governance.

Cost of Ownership Price Tag Good Value Investment ROI

Get more information on UNIX with new tools and resources available at www.opengroup.org/UNIX or review some selected resources below:

[1] https://blog.opengroup.org/2016/03/11/unix-allowing-engineers-to-engineer

[2] https://blog.opengroup.org/2016/04/18/unix-the-always-on-os/

[3] https://blog.opengroup.org/2016/03/24/o-armor-unix-armor/

[4] https://blog.opengroup.org/2016/04/18/unix-the-always-on-os/

@theopengroup

 

Comments Off on UNIX®: Lowering the Total Cost of Ownership

Filed under Standards, The Open Group, Uncategorized, UNIX