Monday, November 13, 2017

Digitization of Oceans Reference Architecture TOC

For a sense of where I am going with this series of posts describing a reference architecture for the digitization of oceans, please consider this "table of contents". As I complete items in the list, I will update this TOC;
  1. Introduction - summary of why a series of posts describing a digitization of oceans reference architecture.
  2. What is a reference architecture? - summary of the existing online descriptions of reference architecture and why it is important to building a strong technology ecosystem.
  3. A plethora of end points - with new Internet of Things (IoT) end points coming available with increasing frequency we look to how an oceans reference architecture would facilitate adoption, inter-operability, and innovation.
  4. Communications - description of the current state of data communications above and below the oceans surface. And why it matters to the reference architecture.
  5. What is the digitization of oceans? - a high level description of the digitization of oceans. This will detail the breadth and depth of what is considered the digitization of oceans. This description should also consider the intersection of the different ecosystems of; business, innovation, and knowledge.
  6. What is a digitization of oceans reference architecture? - comprehensive diagram of the entities within the oceans reference architecture with detailed description of each item and their connections (digital or otherwise).
  7. The economic value to be found in the oceans reference architecture - why is a reference architecture valuable for community, business, innovation, etc. And why Atlantic Canada should be a major contributor or primary steward of the reference architecture.
  8. How to create the digitization of oceans reference architecture - what is the road map in completing the first release of a digitization of oceans reference architecture. I purposely say first release as this reference architecture will need constant tending as new technologies and capabilities come available.
Keep in mind this is meant to kick off a conversation about creating a reference architecture for the digitization of oceans. This is NOT something I want to do on my own, or believe I could do effectively on my own without contributions from others and a few years of focused effort. I really want engagement across Atlantic Canada to discuss the idea of creating this reference architecture and to become stewards of the reference architecture as it is used globally for the benefit of everybody.

Disclaimer - All views expressed on this site are my own and do not represent the opinions of any entity whatsoever with which I have been, am now, or will be affiliated. They are views created by my many years as an IT professional and, more importantly, an enterprise architect responsible for building large and distributed systems.

Sunday, November 12, 2017

Reference architecture for the digitization of oceans

I strongly believe one of the cornerstones for the successful digitization of oceans is a reference architecture. I believe this also holds true for the digitization of oil and gas, but I see this digitization as a subset of the oceans. Or more specifically, I see the digitization of maritime oil and gas as a subset of the digitization of oceans. I regress... One of the most important aspects of the reference architecture is its openness (as opposed to proprietary). If we are wanting to spur innovation in Atlantic Canada we need every small, medium, and large organization to realize benefit from shared digital resources. We need a way for all these organizations to openly communicate and build this digital ecosystem. The digitization of oceans reference architecture will define (or utilize existing approaches) the "language" that all oceans technologies communicate with one another and remember their collective history.

An example; the reference architecture would specify the digital messaging structure for an ocean temperature event. Therefore, when a small startup (that specializes in ocean temperature sensors) needs to publish their data they need only comply with messaging structures for ocean temperature. This would allow everyone in the ecosystem to get at their temperature event data as soon as it is available. Also important, is the startups market for ocean temperature sensors customers includes everyone who is aligned with the oceans reference architecture and it's messaging structures.

Another example; the reference architecture would specify the underwater wireless communications approaches and suggested protocols and practices. All allowing the temperature event data to be broadcast and communicated to the historical repository for archiving.

Another example; the reference architecture would specify all the messaging structures and the data storage approaches so the data could be archived and be available through time. The historical archive would allow for retrieval, searching, research, planning, and analysis.

Over the next few weeks I will be publishing a series of blog posts describing, in more detail, all the aspects for building a successful digitization of oceans reference architecture. Next up is; "what is a reference architecture" with focus on oceans technology. Please follow along and make comment. For a table of contents of these coming posts please review a companion post; Digitization of Oceans Reference Architecture TOC

Disclaimer - All views expressed on this site are my own and do not represent the opinions of any entity whatsoever with which I have been, am now, or will be affiliated. They are views created by my many years as an IT professional and, more importantly, an enterprise architect responsible for building large and distributed systems.

Friday, May 12, 2017

ACAITA Inaugural Meeting St. John's

Three architecturally minded technical professionals got together at the Ship Public House to share a couple of beers, tell a few technical project yarns, and enjoy some traditional music. The conversation was also very candid and at times could have been considered cynical. But... from all this emerged some optimism and some healthy and solid work we can do to support and encourage the growth of technology architecture practices in Newfoundland and the whole of Atlantic Canada.

We all agreed it's a challenging time in Newfoundland. The economy is in decline, the population is aging, the young and up-n-comers are leaving, and the current government is overly focused on the immediate need to get the provincial house in order. So when a few architects and senior software developers get together our pragmatism gets the better of us and we trend toward being pessimistic about the senior technical opportunities available in Newfoundland. We also identified a handful of activities to be optimistic about;
  • St. John's has a growing startup ecosystem - this didn't exist 5 - 7 years ago and now it has a physical space (common ground), a few small and growing technology companies, and s small group of committed people who want to see technology startups thrive in Newfoundland.
  • A technology industry association (NATI) which is committed, effective, and strongly resourced toward building success for the province (and Atlantic Canada as a whole).
  • Strongly positioned for the digitization of two or three industry sectors (Oil and Gas, Fisheries, Arctic Environments). Newfoundland, if it put its mind too it, could be at the table in a big way for the digitization of any of these three industry sectors.
  • Our current federal government is committed to encouraging innovation and in supporting collaborative initiatives that fall well within the digitization of oceans and ocean technology.
We all agreed that participating in the local technology community is important, and we get enjoyment from sharing our technical experiences and understanding other technology project current within St. John's. Having a strong and growing technology architecture community would help in building the local technology economy and opportunities.

Sunday, April 02, 2017

A focused economic sector

Recently I have been working toward growing the Atlantic Canada Association of Information Technology Architects (ACAITA). The idea of creating this group got a lot of support and quickly had 90 members representing all four Atlantic Canadian provinces. A few weeks back a group of us got together in Halifax to discuss the association, its purpose, its road ahead, and other things architectural. I believe for this association to be successful it needs to bring value to its members and to the business communities in which it exists.

Differing ecosystems should work together to progress a focused economic sector.
Over the last few weeks I have had informal conversations with a number of intelligent and supportive people who work for ACOA, NATI, and Industry. I want to provide many thanks to these organizations and their representatives for taking the time and providing insight into how best to build the ACAITA. The subjects we discussed are focused upon growing the association and how best to engage the business community. I also believe that my knowledge as an EA combined with recent research activities around business ecosystem modeling and reference architectures had an influence over the directions these conversations took. Described below are the highlights to these conversations;
  1. ACOA - Atlantic Canada Opportunities Agency
    • The ACAITA needs to define itself and have a comprehensive set of demographic data. Not only we need to know how many members we have and which province they are located, we need to know the total number of architects in the Atlantic provinces, where their focus is, what industries they work, etc.
    • Reach out to industry / business and find out exactly what their architectural needs are and where they see gaps in the workforce or capability.
    • The Oil and Gas sector remains strong for Newfoundland and Labrador and providing architectural support here should be considered a pillar for ACAITA. Becoming champions of the Oil and Gas Reference Architecture could be one of the associations cornerstones.
    • Keeping things Atlantic would support the ACAITA mission. Identify all the main business ecosystems and reference architectures where Atlantic Canada could become internationally recognized would be a solid approach. 
  2. NATI - Newfoundland and Labrador Association of Technology Industries
    • Having ACAITA as a pan-Atlantic organization remains as a very good idea. And looking for NATI equivalents in all the other three provinces would help in getting ACAITA support.
    • From a Technology Industries perspective the Digitization of Oil and Gas is capturing increasing attention and the investments made here should have derived benefit for Atlantic Canada outside Oil and Gas for the near and long terms.
    • NL already has many technology companies within the Oil and Gas sector and identifying all the organizational ecosystems and intrinsic reference architectures would help support ACAITA success and growth.
    • Its important that NL grows technology and digitization capabilities outside of Oil and Gas. And an Association like ACAITA would fit well with growing this derived capabilities perspective.
  3. Industry - conversations with assorted industry professionals
    • Confirmed the focus of Oil and Gas for NL and that growing the architectural capabilities supporting these industries in the province of NL would assist greatly.
    • Mapping out the ecosystems (business, innovation, and knowledge) supported by the intrinsic reference architectures could further pull everything together, It could provide a technology foundation in which to build the Digitization of Oil and Gas. An expertise which NL should own internationally.
The Conclusion
Identify the main industry sectors with Atlantic Canada and begin ecosystem mapping with an eye to defining the intrinsic reference architectures. Engage both IT Architects and organizations (business, innovation, and knowledge) to define and publish documents describing ecosystems and reference architectures.

Wednesday, March 22, 2017

ACAITA Partnership Recommendation

There are a number of groups, professional associations, organizations involved with developing and forwarding the practice of IT architecture. The ones I see relevant to developing an IT Architecture association are as follows;
  1. IASA - An association for all IT Architects
  2. OpenGroup - Vendor neutral IT standards and certifications
  3. AEA - Association of Enterprise Architects
  4. EACOE - Enterprise Architecture Centre of Excellence
  5. FEAC - Training and Certification Institution for Enterprise Architects
  6. ISC - Vendor-neutral education products, career services, and Gold Standard credentials to professionals.
  7. CIPS - Canada's association of Information Technology (IT) professionals
  8. BAG - Business Architecture Guild 

I believe any of these have valuable resources that could support, and be useful to, the ACAITA membership. I believe the IASA provides the broadest view into architecture, where the other organizations are more focused on an area of architecture, such as; security, business, the enterprise, or IT in general.

I recommend the ACAITA aligns itself with two or three of these groups / associations as determined by the resources they can make available toward growing the architectural capabilities of Atlantic Canadians. To start, I believe a few of us should consider becoming full members of the IASA Canada chapter with the intention to form the Atlantic Canada chapter. I also recommend we align ourselves with one or two of the training and certification groups... I believe this can wait until we have our association alignment.

Sunday, March 12, 2017

ACAITA Inaugural meeting Halifax

We had an outstanding inaugural meeting of the Atlantic Canada Association of Information Technology Architects (ACAITA). Seven Halifax members (and one ST. John's member) came out to the 2nd Floor of the Lower Deck to share some nachos, some great conversation about the state of Enterprise Architecture (and beyond), and to share a few beers. It was so great to meet like minded technical people who are very interested in talking about IT Architecture. I enjoyed the conversation, as it was as broad as it was deep. I'll summarize what I took from the evening in three main themes;

The Highlights

These are what I consider the highlights of the discussion. It may have been different for other participants, this is what stood out for me.
  • Attracting Diversity - we need diversity in the group! It would make the group stronger, more resilient to changes, and help it last beyond one or two peoples efforts. When we talked diversity it mostly focused on a good spread of ages and experience and how there was much that could be shared to bring younger IT people into the architect roles. The diversity also included discussion from the broader sense of gender and ethnic / cultural background. In the end, it was mostly focused on age and experience and including as much diversity as we could.
  • Atlantic Canadian Architects are well prepared - the Atlantic Canada market is smaller for IT Architects, and yet, the responsibilities and opportunities are not specialized, the IT Architects in Atlantic Canada have therefore developed broad experience. In other words, they have filled many of the Architectural roles because the work needed to get done and they were the most appropriate to get it done. This is a real strength for IT Architects in Atlantic Canada. To be a good Architect you need to see the big picture and having a wide range of experience is essential.
  • Remain Technology Agnostic - we agreed that it is best to remain technology agnostic. This means we never align ourselves with a particular vendor, framework, approach, methodology, partner, certification, training, etc. This means that we encourage discussion about everything architectural and how different technologies and approaches work together and the best way to get something done. This means we encourage involvement from all vendors, frameworks, methodologies, etc... in the end, deepening our understanding of how to work with all vendors products, methodologies, frameworks, etc... is best for everyone. 

The Summary

In addition to the highlights there are other discussion themes worth mentioning
  • We have a good number of very experienced Architects in Atlantic Canada who have worked internationally and across all the different architectural disciplines. When you consider our associations vision to become internationally known for our architectural abilities we already have a very solid foundation.
    The many roles of the IT Architect.
  • These kinds of groups / associations have come and gone over the past 30 years and it is a good idea to start meeting again. There is great value both for the profession and for the technology industries in Atlantic Canada. Mostly, its having other architects to discuss how to best get things done and to deepen understanding of emerging technologies. We also need to reach out to the younger IT professionals to be sure the IT Architecture within Atlantic Canada stays strong and healthy. 
  • Having this as an Atlantic Canada initiative is a really good idea. This mostly comes from Atlantic Canada being a relatively small market and many IT professionals know one another. It is also well aligned with how many public and private organizations function within Atlantic Canada. When wanting to partner and get support from these organizations it is important that we span all four Atlantic provinces so we can reduce duplication of effort and have broader impact in all we do.

The Next Steps

  • Get together often, formally and informally - yes, it is a good idea to have formalized meetings and events, but it is also a good idea to get together informally for Lunch, or a game of pool, and just talk architecture. We agreed we need as many informal meetings as formal meetings.
  • Use the #ACAITA hashtag - whenever you post or use online networks / media use the #ACAITA hashtag. This hashtag will assist in bringing the communities online discussion together and followed. 
  • Attend all kinds of events as a ACAITA member - discussing architecture (as a member of the ACAITA) at the many technology and other events will bring our association more attention. Good IT architecture is needed wherever a technology initiative is underway. Get involved, reach out, talk architecture.
  • Identify all the IT Architecture and related education programs in Atlantic Canada - we agreed it would be very useful to gather a list of as many of the computer science, technology and business programs that wouldbe interested in IT architecture.
  • Identify the Architectural Groups we could consider partnering - we also need to consider all the existing associations that would be useful to align ourselves. This could be of great assistance to our collective success, but also save us a lot of time and effort by learning from those who have gone before us.

Sunday, March 05, 2017

A bold vision for Atlantic Canada Association of IT Architects

I had a bit of an epiphany when thinking about the purpose of the Atlantic Canada Association of IT Architects. I was thinking about to things;
  1. What is going to attract membership to share with, and access, the association.
  2. How are we going to engage public and private sector organizations is a meaningful way.
My thinking ended up rewriting the vision statement for the organization to be much more bold and broad. I changed the vision to be;
Our Vision is for Atlantic Canada to become world renowned for our Information Technology Architectural excellence. This excellence will support, and be a pillar for, the technology sector economy within all four provinces of Atlantic Canada. Overall the ACAITA will increase the awareness, effectiveness, and value of Information Technology Architecture for practitioners and organizations. Atlantic Canada will be recognized worldwide for its Architectural excellence and effectiveness.

The rational for this altered vision is to attract members and engage the sector. More specifically, I believe the following themes are important when wanting to fulfill these two key aspects of building an association (and community).
  • We need a massive way to inspire people to become members, and to contribute. Even though there is already a sharing economy within most technology communities, a lot of what people are looking for is access. Access to knowledge, access to education, access to mentorship, access to other professional associations, access to learning materials, access to conferences, access to opportunities, etc... As much as people want to share, they also want access to resources. I believe the association can leverage its membership, and bold vision, to create partnerships and ease peoples access to resources.
  • To become further engaged with the public and private sectors we need to continue to contribute in a meaningful, and economic way. We need to offer exemplary skills and knowledge that are recognized worldwide further attracting technology projects to Atlantic Canada. 
  • As an association we need funding sources. As active contributors to the Atlantic provinces economic future it will be easier to establish partnerships and find sources of funding if we are recognized as adding value and essential resources.

What are your thoughts to my thinking in having a more bold and broad vision for the ACAITA?