diff --git a/docs/_static/fcas-actvlist-curt.png b/docs/_static/fcas-actvlist-curt.png
new file mode 100644
index 0000000..c5a8b49
Binary files /dev/null and b/docs/_static/fcas-actvlist-curt.png differ
diff --git a/docs/_static/fcas-namelist-curt.png b/docs/_static/fcas-namelist-curt.png
new file mode 100644
index 0000000..f9bce93
Binary files /dev/null and b/docs/_static/fcas-namelist-curt.png differ
diff --git a/docs/_static/fcas-namelist-prev.png b/docs/_static/fcas-namelist-prev.png
new file mode 100644
index 0000000..3083725
Binary files /dev/null and b/docs/_static/fcas-namelist-prev.png differ
diff --git a/docs/fcas/index.rst b/docs/fcas/index.rst
index 262a4bc..f50e6ab 100644
--- a/docs/fcas/index.rst
+++ b/docs/fcas/index.rst
@@ -98,5 +98,6 @@ Index
     creation_workflow
     creation_gram
     creation_fail
+    solution_datanote
     solution_workflow
     proposed_technologies
diff --git a/docs/fcas/solution_datanote.rst b/docs/fcas/solution_datanote.rst
new file mode 100644
index 0000000..a30c4a2
--- /dev/null
+++ b/docs/fcas/solution_datanote.rst
@@ -0,0 +1,62 @@
+.. _creation_gram.rst:
+
+Planned Statistics Sources
+====
+
+For obtaining the list of all usernames
+----
+
+In contrast to the earlier approach of gathering statistics for the active 
+users available on FASJSON, this time around the statistics would need to be a
+lot more verbose and detailed. The core part that binds these statistics is the
+nature of the information collected as we would want to ensure that these 
+activities are "objectively" perceived. What looks like a contribution to a 
+certain person should look the same to others as well.
+
+The list of the all available users has been planned to be resourced from the
+authentication database itself, instead of interacting with an HTTP API like 
+FASJSON first and then letting FASJSON connect with the authentication database
+like we did before. This is to ensure that the scheduled runs for the process to
+fetch and update the list of users is not performance intensive and lesser
+time consuming in general than it was before.
+
+Previous architecture
+^^^^
+
+.. image:: ../_static/fcas-namelist-prev.png
+    :target: ../_images/fcas-namelist-prev.png
+
+Planned architecture
+^^^^
+
+.. image:: ../_static/fcas-namelist-curt.png
+    :target: ../_images/fcas-namelist-curt.png
+
+For obtaining the list of active usernames
+----
+
+`Fedora Messaging <https://fedora-messaging.readthedocs.io/>`_ keeps track of
+the activities performed on a certain set of services deployed on the community
+infrastructure. As the act of making contributions would inevitably require the
+interactions with these services - it is very likely that the contribution
+activities would cause the service to publish a message on the Fedora Messaging
+bus, should the relevant schemas be configured correctly.
+
+The historical collection of all messages published on the Fedora Messaging bus
+since the time of its deployment in production has been stored on a database
+service known as `Datanommer <https://github.com/fedora-infra/datanommer>`_ and
+this is something that can be probed into directly without including another 
+element in the system for facilitating the requests, which was previously done
+by `Datagrepper <https://apps.fedoraproject.org/datagrepper/>`_.
+
+Previous architecture
+^^^^
+
+.. image:: ../_static/fcas-actvlist-prev.png
+    :target: ../_images/fcas-actvlist-prev.png
+
+Planned architecture
+^^^^
+
+.. image:: ../_static/fcas-actvlist-curt.png
+    :target: ../_images/fcas-actvlist-curt.png