National Capitol Chapter

So, we are standing up a Chief Data Officer (CDO) function at my agency.  I'm interested in hearing about how others see the CDO function -- what it is, where it lives, what it is responsible for etc.  I see lots of overlap with the CIO and Enterprise Architecture.

Does all of information governance and management live under the CDO now?  What about information/data architecture?  Some folks see info/data management as a subset of info/data architecture, others don't.  I have also seen various takes on the difference between info/data governance and info/data management. Does all of analytics live under the CDO?

I'm going to be chairing the Enterprise Information/Data Governance Board. Does anyone have an example of a charter or description of a similar function?  I'd love to hear some lessons learned too.  I have my own perspective but want to hear from others.




------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------

Laura,

Great to see you here!  In the Department of Defense, the DOD Chief Data Officer is in the Chief Management Officer's office, not under the DOD CIO -- which is where enterprise architecture (and by the way records management policy responsibility) lives.  The DOD CDO position was created in early 2018.  The first and current DOD CIO is Michael Conlin.  Here's a recent article with some of his thoughts.  If you look at the DOD CMO organizational chart, you can see that Mr. Conlin heads up the "Data Insights" office which has Data Governance and Data Science under its purview.  From where I sit, this division of responsibilities between the CDO and the CIO is problematic.

When the CDO position was created, there were some writings that made the distinction between data in "operational systems," and data in "business systems."  The gist was that the new CDO would be focused on data in "operational systems," not "business systems."  I didn't like that as my data at the Joint Staff is mostly "business system" data, but it definitely affects the operational military forces of the U.S.

This construct continued to bug me when the DOD CIO published a Digital Modernization Strategy this past June.  In that document, on page 9, there's a graphic depicting a hierarchy of strategy documents aligned under the National Securit Strategy showing where this digital modernization strategy falls.  There is no data strategy in the hierarchy, but later in the year, a new draft DOD Data Strategy was circulated for coordination.  I do not think that strategy has gone final yet.  There was no cross-reference to the digital modernization strategy in the draft data strategy I saw.  By the way, there are 21 references to "IT architecture" in the digital modernization strategy.

The bottom line, it doesn't look like a clean integration at this point for DOD.  Strategically, I like the old Knowledge Management pyramid model when thinking about this, but I mentally substitute "Decision/Situational Awareness" for "Wisdom" at the top.  Putting data, information, records, knowledge, cyber, IT, Business Process Management (BPM) and related fields in different silos is not helpful. I don't think it's particularly helpful to separate business data from operational data.  When you start exploring Artificial Intelligence (AI), Robotic Process Automation (RPA), etc., the poor organization ensures there will always be missing stakeholders in at least the early meetings on any project.  I also think data is data, whether structured or unstructured, which blurs the distinction between data and information...information sometimes defined as "data in context."

We need to think -- and organize ourselves -- more holistically.  For example, DOD has a fairly new AI strategy which comes under the DOD CIO's office.  The principle document is classified, but here's a good unclassified supplement.  The Joint Artificial Intelligence Center (JAIC), under the DOD CIO, was created as that strategy was being developed.  There may be an informal relationship with the CDO in the CMO's office, but it appears that's it.

I hope this rambling response is at least interesting if not helpful!


------------------------------
Mark Patrick, CIP, CDR USN (Ret.)
Immediate Past Chair, Board of Directors
AIIM International
------------------------------

Original Message:
Sent: 11-22-2019 12:01
From: Laura Downey
Subject: Chief Data Officer

So, we are standing up a Chief Data Officer (CDO) function at my agency.  I'm interested in hearing about how others see the CDO function -- what it is, where it lives, what it is responsible for etc.  I see lots of overlap with the CIO and Enterprise Architecture.

Does all of information governance and management live under the CDO now?  What about information/data architecture?  Some folks see info/data management as a subset of info/data architecture, others don't.  I have also seen various takes on the difference between info/data governance and info/data management. Does all of analytics live under the CDO?

I'm going to be chairing the Enterprise Information/Data Governance Board. Does anyone have an example of a charter or description of a similar function?  I'd love to hear some lessons learned too.  I have my own perspective but want to hear from others.




------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------

Hello Mark!

Thanks for sharing all this info.  Much appreciated.  I'm seeing various versions across the Federal space - -meaning different responsibilities, different division of duties, different places to live, different things included and so on. Owen, while the Federal Data Strategy plus legislation sets out items at the higher level, often the implementation of that is very different across organizations.  I did not know about StratML so thank you for sharing that info.

We are actually writing an enterprise information and data governance management directive (MD).  And the plan was to look at the items already referenced here.  But I'm going to start with the StratML stuff since that seems to take some of the major items from the Federal Data Strategy and legislation -- so part of the work done for us already.


------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------

Original Message:
Sent: 11-23-2019 07:54
From: Mark Patrick
Subject: Chief Data Officer

Laura,

Great to see you here!  In the Department of Defense, the DOD Chief Data Officer is in the Chief Management Officer's office, not under the DOD CIO -- which is where enterprise architecture (and by the way records management policy responsibility) lives.  The DOD CDO position was created in early 2018.  The first and current DOD CIO is Michael Conlin.  Here's a recent article with some of his thoughts.  If you look at the DOD CMO organizational chart, you can see that Mr. Conlin heads up the "Data Insights" office which has Data Governance and Data Science under its purview.  From where I sit, this division of responsibilities between the CDO and the CIO is problematic.

When the CDO position was created, there were some writings that made the distinction between data in "operational systems," and data in "business systems."  The gist was that the new CDO would be focused on data in "operational systems," not "business systems."  I didn't like that as my data at the Joint Staff is mostly "business system" data, but it definitely affects the operational military forces of the U.S.

This construct continued to bug me when the DOD CIO published a Digital Modernization Strategy this past June.  In that document, on page 9, there's a graphic depicting a hierarchy of strategy documents aligned under the National Securit Strategy showing where this digital modernization strategy falls.  There is no data strategy in the hierarchy, but later in the year, a new draft DOD Data Strategy was circulated for coordination.  I do not think that strategy has gone final yet.  There was no cross-reference to the digital modernization strategy in the draft data strategy I saw.  By the way, there are 21 references to "IT architecture" in the digital modernization strategy.

The bottom line, it doesn't look like a clean integration at this point for DOD.  Strategically, I like the old Knowledge Management pyramid model when thinking about this, but I mentally substitute "Decision/Situational Awareness" for "Wisdom" at the top.  Putting data, information, records, knowledge, cyber, IT, Business Process Management (BPM) and related fields in different silos is not helpful. I don't think it's particularly helpful to separate business data from operational data.  When you start exploring Artificial Intelligence (AI), Robotic Process Automation (RPA), etc., the poor organization ensures there will always be missing stakeholders in at least the early meetings on any project.  I also think data is data, whether structured or unstructured, which blurs the distinction between data and information...information sometimes defined as "data in context."

We need to think -- and organize ourselves -- more holistically.  For example, DOD has a fairly new AI strategy which comes under the DOD CIO's office.  The principle document is classified, but here's a good unclassified supplement.  The Joint Artificial Intelligence Center (JAIC), under the DOD CIO, was created as that strategy was being developed.  There may be an informal relationship with the CDO in the CMO's office, but it appears that's it.

I hope this rambling response is at least interesting if not helpful!


------------------------------
Mark Patrick, CIP, CDR USN (Ret.)
Immediate Past Chair, Board of Directors
AIIM International

Original Message:
Sent: 11-22-2019 12:01
From: Laura Downey
Subject: Chief Data Officer

So, we are standing up a Chief Data Officer (CDO) function at my agency.  I'm interested in hearing about how others see the CDO function -- what it is, where it lives, what it is responsible for etc.  I see lots of overlap with the CIO and Enterprise Architecture.

Does all of information governance and management live under the CDO now?  What about information/data architecture?  Some folks see info/data management as a subset of info/data architecture, others don't.  I have also seen various takes on the difference between info/data governance and info/data management. Does all of analytics live under the CDO?

I'm going to be chairing the Enterprise Information/Data Governance Board. Does anyone have an example of a charter or description of a similar function?  I'd love to hear some lessons learned too.  I have my own perspective but want to hear from others.




------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------

While roles and responsibilities differ across agencies, the content of strategic and performance plans and reports are common across all organizations, worldwide. That's why StratML Part 1, Strategic Plans, is an international standard (ISO 17469-1) and Part 2, Performance Plans and Reports, was approved as an American national standard (formerly ANSI/AIIM 22:2017).

Part of the problem is that stakeholders have allowed organizations to avoid using voluntary consensus standards based on a false argument that they are somehow "unique" and thus must waste time and resources reinventing those standards. Taxpayers have a right to expect more responsible behavior on the part of their public servants, and it is unfortunate that AIIM has not done a better job of promoting its former intellectual property toward that end.

It would be nice to think AIIM might still prove to be up to the challenge of leadership in that regard.  However, lacking such evidence, my 24-year-long affiliation with this organization will soon be ending.

------------------------------
Owen Ambur
StratML Community
http://stratml.us/
------------------------------

Original Message:
Sent: 11-25-2019 11:37
From: Laura Downey
Subject: Chief Data Officer

Hello Mark!

Thanks for sharing all this info.  Much appreciated.  I'm seeing various versions across the Federal space - -meaning different responsibilities, different division of duties, different places to live, different things included and so on. Owen, while the Federal Data Strategy plus legislation sets out items at the higher level, often the implementation of that is very different across organizations.  I did not know about StratML so thank you for sharing that info.

We are actually writing an enterprise information and data governance management directive (MD).  And the plan was to look at the items already referenced here.  But I'm going to start with the StratML stuff since that seems to take some of the major items from the Federal Data Strategy and legislation -- so part of the work done for us already.


------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA

Original Message:
Sent: 11-23-2019 07:54
From: Mark Patrick
Subject: Chief Data Officer

Laura,

Great to see you here!  In the Department of Defense, the DOD Chief Data Officer is in the Chief Management Officer's office, not under the DOD CIO -- which is where enterprise architecture (and by the way records management policy responsibility) lives.  The DOD CDO position was created in early 2018.  The first and current DOD CIO is Michael Conlin.  Here's a recent article with some of his thoughts.  If you look at the DOD CMO organizational chart, you can see that Mr. Conlin heads up the "Data Insights" office which has Data Governance and Data Science under its purview.  From where I sit, this division of responsibilities between the CDO and the CIO is problematic.

When the CDO position was created, there were some writings that made the distinction between data in "operational systems," and data in "business systems."  The gist was that the new CDO would be focused on data in "operational systems," not "business systems."  I didn't like that as my data at the Joint Staff is mostly "business system" data, but it definitely affects the operational military forces of the U.S.

This construct continued to bug me when the DOD CIO published a Digital Modernization Strategy this past June.  In that document, on page 9, there's a graphic depicting a hierarchy of strategy documents aligned under the National Securit Strategy showing where this digital modernization strategy falls.  There is no data strategy in the hierarchy, but later in the year, a new draft DOD Data Strategy was circulated for coordination.  I do not think that strategy has gone final yet.  There was no cross-reference to the digital modernization strategy in the draft data strategy I saw.  By the way, there are 21 references to "IT architecture" in the digital modernization strategy.

The bottom line, it doesn't look like a clean integration at this point for DOD.  Strategically, I like the old Knowledge Management pyramid model when thinking about this, but I mentally substitute "Decision/Situational Awareness" for "Wisdom" at the top.  Putting data, information, records, knowledge, cyber, IT, Business Process Management (BPM) and related fields in different silos is not helpful. I don't think it's particularly helpful to separate business data from operational data.  When you start exploring Artificial Intelligence (AI), Robotic Process Automation (RPA), etc., the poor organization ensures there will always be missing stakeholders in at least the early meetings on any project.  I also think data is data, whether structured or unstructured, which blurs the distinction between data and information...information sometimes defined as "data in context."

We need to think -- and organize ourselves -- more holistically.  For example, DOD has a fairly new AI strategy which comes under the DOD CIO's office.  The principle document is classified, but here's a good unclassified supplement.  The Joint Artificial Intelligence Center (JAIC), under the DOD CIO, was created as that strategy was being developed.  There may be an informal relationship with the CDO in the CMO's office, but it appears that's it.

I hope this rambling response is at least interesting if not helpful!


------------------------------
Mark Patrick, CIP, CDR USN (Ret.)
Immediate Past Chair, Board of Directors
AIIM International

Original Message:
Sent: 11-22-2019 12:01
From: Laura Downey
Subject: Chief Data Officer

So, we are standing up a Chief Data Officer (CDO) function at my agency.  I'm interested in hearing about how others see the CDO function -- what it is, where it lives, what it is responsible for etc.  I see lots of overlap with the CIO and Enterprise Architecture.

Does all of information governance and management live under the CDO now?  What about information/data architecture?  Some folks see info/data management as a subset of info/data architecture, others don't.  I have also seen various takes on the difference between info/data governance and info/data management. Does all of analytics live under the CDO?

I'm going to be chairing the Enterprise Information/Data Governance Board. Does anyone have an example of a charter or description of a similar function?  I'd love to hear some lessons learned too.  I have my own perspective but want to hear from others.




------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------

Mark,

Concerning AI, I think it is HUGE game changer for creating an intelligent information enterprise.  One of the things I'm thinking about is developing an AI strategy and identifying areas or domains where my agency can best apply and exploit AI -- so managing enterprise info/data would be one of those areas.


------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------

Original Message:
Sent: 11-23-2019 07:54
From: Mark Patrick
Subject: Chief Data Officer

Laura,

Great to see you here!  In the Department of Defense, the DOD Chief Data Officer is in the Chief Management Officer's office, not under the DOD CIO -- which is where enterprise architecture (and by the way records management policy responsibility) lives.  The DOD CDO position was created in early 2018.  The first and current DOD CIO is Michael Conlin.  Here's a recent article with some of his thoughts.  If you look at the DOD CMO organizational chart, you can see that Mr. Conlin heads up the "Data Insights" office which has Data Governance and Data Science under its purview.  From where I sit, this division of responsibilities between the CDO and the CIO is problematic.

When the CDO position was created, there were some writings that made the distinction between data in "operational systems," and data in "business systems."  The gist was that the new CDO would be focused on data in "operational systems," not "business systems."  I didn't like that as my data at the Joint Staff is mostly "business system" data, but it definitely affects the operational military forces of the U.S.

This construct continued to bug me when the DOD CIO published a Digital Modernization Strategy this past June.  In that document, on page 9, there's a graphic depicting a hierarchy of strategy documents aligned under the National Securit Strategy showing where this digital modernization strategy falls.  There is no data strategy in the hierarchy, but later in the year, a new draft DOD Data Strategy was circulated for coordination.  I do not think that strategy has gone final yet.  There was no cross-reference to the digital modernization strategy in the draft data strategy I saw.  By the way, there are 21 references to "IT architecture" in the digital modernization strategy.

The bottom line, it doesn't look like a clean integration at this point for DOD.  Strategically, I like the old Knowledge Management pyramid model when thinking about this, but I mentally substitute "Decision/Situational Awareness" for "Wisdom" at the top.  Putting data, information, records, knowledge, cyber, IT, Business Process Management (BPM) and related fields in different silos is not helpful. I don't think it's particularly helpful to separate business data from operational data.  When you start exploring Artificial Intelligence (AI), Robotic Process Automation (RPA), etc., the poor organization ensures there will always be missing stakeholders in at least the early meetings on any project.  I also think data is data, whether structured or unstructured, which blurs the distinction between data and information...information sometimes defined as "data in context."

We need to think -- and organize ourselves -- more holistically.  For example, DOD has a fairly new AI strategy which comes under the DOD CIO's office.  The principle document is classified, but here's a good unclassified supplement.  The Joint Artificial Intelligence Center (JAIC), under the DOD CIO, was created as that strategy was being developed.  There may be an informal relationship with the CDO in the CMO's office, but it appears that's it.

I hope this rambling response is at least interesting if not helpful!


------------------------------
Mark Patrick, CIP, CDR USN (Ret.)
Immediate Past Chair, Board of Directors
AIIM International

Original Message:
Sent: 11-22-2019 12:01
From: Laura Downey
Subject: Chief Data Officer

So, we are standing up a Chief Data Officer (CDO) function at my agency.  I'm interested in hearing about how others see the CDO function -- what it is, where it lives, what it is responsible for etc.  I see lots of overlap with the CIO and Enterprise Architecture.

Does all of information governance and management live under the CDO now?  What about information/data architecture?  Some folks see info/data management as a subset of info/data architecture, others don't.  I have also seen various takes on the difference between info/data governance and info/data management. Does all of analytics live under the CDO?

I'm going to be chairing the Enterprise Information/Data Governance Board. Does anyone have an example of a charter or description of a similar function?  I'd love to hear some lessons learned too.  I have my own perspective but want to hear from others.




------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------

Laura, if you do publish an AI strategy for TSA, I'll look forward to rendering it in StratML format and encouraging:

a) usage of the stratml:Relationship elements to document and link common and complementary objectives across multiple AI plans, and
b) coordination and partnerships to realize those objectives.

According to this site-specific query, about 115 of the >4,000 plans currently in the StratML collection reference "AI".  However, new and better tools, apps, and services are required to enable more efficient and productive discovery and MBO-focused collaboration around objectives of all kinds.

BTW, seeing the word "architecture" in your title, prompts me to wonder whether you know about the Data-Centric Manifesto, whose goal is available in StratML format at http://stratml.us/carmel/iso/part2/DCMOwStyle.xml#_ad4c1cfc-f80e-11e9-ad02-7db98ebabdf6

------------------------------
Owen Ambur
StratML Community
http://stratml.us/
------------------------------

Original Message:
Sent: 11-25-2019 11:45
From: Laura Downey
Subject: Chief Data Officer

Mark,

Concerning AI, I think it is HUGE game changer for creating an intelligent information enterprise.  One of the things I'm thinking about is developing an AI strategy and identifying areas or domains where my agency can best apply and exploit AI -- so managing enterprise info/data would be one of those areas.


------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA

Original Message:
Sent: 11-23-2019 07:54
From: Mark Patrick
Subject: Chief Data Officer

Laura,

Great to see you here!  In the Department of Defense, the DOD Chief Data Officer is in the Chief Management Officer's office, not under the DOD CIO -- which is where enterprise architecture (and by the way records management policy responsibility) lives.  The DOD CDO position was created in early 2018.  The first and current DOD CIO is Michael Conlin.  Here's a recent article with some of his thoughts.  If you look at the DOD CMO organizational chart, you can see that Mr. Conlin heads up the "Data Insights" office which has Data Governance and Data Science under its purview.  From where I sit, this division of responsibilities between the CDO and the CIO is problematic.

When the CDO position was created, there were some writings that made the distinction between data in "operational systems," and data in "business systems."  The gist was that the new CDO would be focused on data in "operational systems," not "business systems."  I didn't like that as my data at the Joint Staff is mostly "business system" data, but it definitely affects the operational military forces of the U.S.

This construct continued to bug me when the DOD CIO published a Digital Modernization Strategy this past June.  In that document, on page 9, there's a graphic depicting a hierarchy of strategy documents aligned under the National Securit Strategy showing where this digital modernization strategy falls.  There is no data strategy in the hierarchy, but later in the year, a new draft DOD Data Strategy was circulated for coordination.  I do not think that strategy has gone final yet.  There was no cross-reference to the digital modernization strategy in the draft data strategy I saw.  By the way, there are 21 references to "IT architecture" in the digital modernization strategy.

The bottom line, it doesn't look like a clean integration at this point for DOD.  Strategically, I like the old Knowledge Management pyramid model when thinking about this, but I mentally substitute "Decision/Situational Awareness" for "Wisdom" at the top.  Putting data, information, records, knowledge, cyber, IT, Business Process Management (BPM) and related fields in different silos is not helpful. I don't think it's particularly helpful to separate business data from operational data.  When you start exploring Artificial Intelligence (AI), Robotic Process Automation (RPA), etc., the poor organization ensures there will always be missing stakeholders in at least the early meetings on any project.  I also think data is data, whether structured or unstructured, which blurs the distinction between data and information...information sometimes defined as "data in context."

We need to think -- and organize ourselves -- more holistically.  For example, DOD has a fairly new AI strategy which comes under the DOD CIO's office.  The principle document is classified, but here's a good unclassified supplement.  The Joint Artificial Intelligence Center (JAIC), under the DOD CIO, was created as that strategy was being developed.  There may be an informal relationship with the CDO in the CMO's office, but it appears that's it.

I hope this rambling response is at least interesting if not helpful!


------------------------------
Mark Patrick, CIP, CDR USN (Ret.)
Immediate Past Chair, Board of Directors
AIIM International

Original Message:
Sent: 11-22-2019 12:01
From: Laura Downey
Subject: Chief Data Officer

So, we are standing up a Chief Data Officer (CDO) function at my agency.  I'm interested in hearing about how others see the CDO function -- what it is, where it lives, what it is responsible for etc.  I see lots of overlap with the CIO and Enterprise Architecture.

Does all of information governance and management live under the CDO now?  What about information/data architecture?  Some folks see info/data management as a subset of info/data architecture, others don't.  I have also seen various takes on the difference between info/data governance and info/data management. Does all of analytics live under the CDO?

I'm going to be chairing the Enterprise Information/Data Governance Board. Does anyone have an example of a charter or description of a similar function?  I'd love to hear some lessons learned too.  I have my own perspective but want to hear from others.




------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------

The W3C's AI Knowledge Representation Community Group has been struggling to focus on a deliverable(s).  However, it now appears progress might be made by rendering a performance plan for the group in StratML Part 2, Performance Plan/Report, format.  That means adding performer stakeholder roles and performance indicators to the group's plan, which is available in StratML Part 1, Strategic Plan, format at http://stratml.us/drybridge/index.htm#AIKRCG

To the degree that others may be developing AI strategies, it would be good to facilitate coordination by using the stratml:Relationship elements to strategically align and link common and complementary objectives within as well as across those plans.  It would be highly appropriate for the CDOs to lead such an effort, capitalizing on the specialized capabilities of not only of each agency but also industry consortia, like the W3C, AIIM, etc.

------------------------------
Owen Ambur
StratML Community
http://stratml.us/
------------------------------

Original Message:
Sent: 11-25-2019 11:45
From: Laura Downey
Subject: Chief Data Officer

Mark,

Concerning AI, I think it is HUGE game changer for creating an intelligent information enterprise.  One of the things I'm thinking about is developing an AI strategy and identifying areas or domains where my agency can best apply and exploit AI -- so managing enterprise info/data would be one of those areas.


------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA

Original Message:
Sent: 11-23-2019 07:54
From: Mark Patrick
Subject: Chief Data Officer

Laura,

Great to see you here!  In the Department of Defense, the DOD Chief Data Officer is in the Chief Management Officer's office, not under the DOD CIO -- which is where enterprise architecture (and by the way records management policy responsibility) lives.  The DOD CDO position was created in early 2018.  The first and current DOD CIO is Michael Conlin.  Here's a recent article with some of his thoughts.  If you look at the DOD CMO organizational chart, you can see that Mr. Conlin heads up the "Data Insights" office which has Data Governance and Data Science under its purview.  From where I sit, this division of responsibilities between the CDO and the CIO is problematic.

When the CDO position was created, there were some writings that made the distinction between data in "operational systems," and data in "business systems."  The gist was that the new CDO would be focused on data in "operational systems," not "business systems."  I didn't like that as my data at the Joint Staff is mostly "business system" data, but it definitely affects the operational military forces of the U.S.

This construct continued to bug me when the DOD CIO published a Digital Modernization Strategy this past June.  In that document, on page 9, there's a graphic depicting a hierarchy of strategy documents aligned under the National Securit Strategy showing where this digital modernization strategy falls.  There is no data strategy in the hierarchy, but later in the year, a new draft DOD Data Strategy was circulated for coordination.  I do not think that strategy has gone final yet.  There was no cross-reference to the digital modernization strategy in the draft data strategy I saw.  By the way, there are 21 references to "IT architecture" in the digital modernization strategy.

The bottom line, it doesn't look like a clean integration at this point for DOD.  Strategically, I like the old Knowledge Management pyramid model when thinking about this, but I mentally substitute "Decision/Situational Awareness" for "Wisdom" at the top.  Putting data, information, records, knowledge, cyber, IT, Business Process Management (BPM) and related fields in different silos is not helpful. I don't think it's particularly helpful to separate business data from operational data.  When you start exploring Artificial Intelligence (AI), Robotic Process Automation (RPA), etc., the poor organization ensures there will always be missing stakeholders in at least the early meetings on any project.  I also think data is data, whether structured or unstructured, which blurs the distinction between data and information...information sometimes defined as "data in context."

We need to think -- and organize ourselves -- more holistically.  For example, DOD has a fairly new AI strategy which comes under the DOD CIO's office.  The principle document is classified, but here's a good unclassified supplement.  The Joint Artificial Intelligence Center (JAIC), under the DOD CIO, was created as that strategy was being developed.  There may be an informal relationship with the CDO in the CMO's office, but it appears that's it.

I hope this rambling response is at least interesting if not helpful!


------------------------------
Mark Patrick, CIP, CDR USN (Ret.)
Immediate Past Chair, Board of Directors
AIIM International

Original Message:
Sent: 11-22-2019 12:01
From: Laura Downey
Subject: Chief Data Officer

So, we are standing up a Chief Data Officer (CDO) function at my agency.  I'm interested in hearing about how others see the CDO function -- what it is, where it lives, what it is responsible for etc.  I see lots of overlap with the CIO and Enterprise Architecture.

Does all of information governance and management live under the CDO now?  What about information/data architecture?  Some folks see info/data management as a subset of info/data architecture, others don't.  I have also seen various takes on the difference between info/data governance and info/data management. Does all of analytics live under the CDO?

I'm going to be chairing the Enterprise Information/Data Governance Board. Does anyone have an example of a charter or description of a similar function?  I'd love to hear some lessons learned too.  I have my own perspective but want to hear from others.




------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------

The requirements for CDOs set forth in the OPEN Government Data Act (OGDA) are available as a model plan in StratML Part 2, Performance Plan/Report (formerly ANSI/AIIM 22:2017), format at http://stratml.us/carmel/iso/part2/PP4CDOwStyle.xml

The template can be opened for editing for use by agencies by clicking on the link at http://stratml.us/drybridge/index.htm#OGDA

More than a dozen of DHS's plans are available in StratML format at http://stratml.us/drybridge/index.htm#DHS and several dozen DoD plans at http://stratml.us/drybridge/index.htm#DOD  TSA's plan should (and may soon) be among them:  https://www.tsa.gov/sites/default/files/tsa_strategy.pdf

When agencies begin complying with section 10 of the GPRA Modernization Act (GPRAMA), value-added shared services will enable far more efficient and effective coordination and collaboration within as well as across agencies (eventually at all levels of government, worldwide).  Fortunately, in Circular A-11 OMB has announced its intention to pilot implementation of that (nearly nine-year-old) provision of law with a few agencies this year.  However, prompt and effective implementation should be a top priority for all of the CDOs.

It would be good if AIIM could help lead the way, through the application of its former intellectual property.

------------------------------
Owen Ambur
StratML Community
http://stratml.us/
------------------------------

Original Message:
Sent: 11-22-2019 12:01
From: Laura Downey
Subject: Chief Data Officer

So, we are standing up a Chief Data Officer (CDO) function at my agency.  I'm interested in hearing about how others see the CDO function -- what it is, where it lives, what it is responsible for etc.  I see lots of overlap with the CIO and Enterprise Architecture.

Does all of information governance and management live under the CDO now?  What about information/data architecture?  Some folks see info/data management as a subset of info/data architecture, others don't.  I have also seen various takes on the difference between info/data governance and info/data management. Does all of analytics live under the CDO?

I'm going to be chairing the Enterprise Information/Data Governance Board. Does anyone have an example of a charter or description of a similar function?  I'd love to hear some lessons learned too.  I have my own perspective but want to hear from others.




------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------

TSA's plan is now available in StratML format at http://stratml.us/drybridge/index.htm#TSA

The DoD plans referenced in Mark's message are also in the StratML collection, at http://stratml.us/drybridge/index.htm#DODDMS & http://stratml.us/drybridge/index.htm#DODAIS

Regarding his comment about the need to think more holistically, compliance with these provisions of the eGov Act, enacted in 2002, would make it far easier to do so:  http://stratml.us/references/eGovXML.htm#202b & http://stratml.us/references/eGovXML.htm#207d

If and, hopefully, when agencies use the StratML standard to comply with section 10 GPRAMA and document their stakeholders, doing so will automatically put them in partial compliance with those provisions of the eGov Act as well.  AIIM could contribute significantly toward that end by publishing a best practice document along these lines:  http://stratml.us/references/AIIM-BP-StratML.pdf

BTW, besides directing agencies to publish their strategic plans and performance reports in machine-readable format, section 10 of GPRAMA also prohibits them from spending money to print them -- presumably because Congress must have believed they were spending too much trying to make themselves look good rather than simply reporting their actual performance in non-glossy, more readily usable format.

------------------------------
Owen Ambur
StratML Community
http://stratml.us/
------------------------------

Original Message:
Sent: 11-23-2019 11:05
From: Owen Ambur
Subject: Chief Data Officer

The requirements for CDOs set forth in the OPEN Government Data Act (OGDA) are available as a model plan in StratML Part 2, Performance Plan/Report (formerly ANSI/AIIM 22:2017), format at http://stratml.us/carmel/iso/part2/PP4CDOwStyle.xml

The template can be opened for editing for use by agencies by clicking on the link at http://stratml.us/drybridge/index.htm#OGDA

More than a dozen of DHS's plans are available in StratML format at http://stratml.us/drybridge/index.htm#DHS and several dozen DoD plans at http://stratml.us/drybridge/index.htm#DOD  TSA's plan should (and may soon) be among them:  https://www.tsa.gov/sites/default/files/tsa_strategy.pdf

When agencies begin complying with section 10 of the GPRA Modernization Act (GPRAMA), value-added shared services will enable far more efficient and effective coordination and collaboration within as well as across agencies (eventually at all levels of government, worldwide).  Fortunately, in Circular A-11 OMB has announced its intention to pilot implementation of that (nearly nine-year-old) provision of law with a few agencies this year.  However, prompt and effective implementation should be a top priority for all of the CDOs.

It would be good if AIIM could help lead the way, through the application of its former intellectual property.

------------------------------
Owen Ambur
StratML Community
http://stratml.us/

Original Message:
Sent: 11-22-2019 12:01
From: Laura Downey
Subject: Chief Data Officer

So, we are standing up a Chief Data Officer (CDO) function at my agency.  I'm interested in hearing about how others see the CDO function -- what it is, where it lives, what it is responsible for etc.  I see lots of overlap with the CIO and Enterprise Architecture.

Does all of information governance and management live under the CDO now?  What about information/data architecture?  Some folks see info/data management as a subset of info/data architecture, others don't.  I have also seen various takes on the difference between info/data governance and info/data management. Does all of analytics live under the CDO?

I'm going to be chairing the Enterprise Information/Data Governance Board. Does anyone have an example of a charter or description of a similar function?  I'd love to hear some lessons learned too.  I have my own perspective but want to hear from others.




------------------------------
Laura Downey, PhD
Chief, Applied Architecture
TSA
------------------------------