ArticlesBlog

Industry Day 9: Common Services Platform Marketplace Demonstration

Industry Day 9: Common Services Platform Marketplace Demonstration


Please stand by for realtime captions.>>Hello everyone we will get started in a
another minute or two. We will be with you shortly.>>Hello everyone. Welcome to the integrated
environment nine industry day. We will be talking about the common services
platform marketplace. We will have a demonstration
for you of the marketplace itself. As I mentioned this is the ninth time
that we have gathered for one of these presentations. We look forward
to dialogue with you today. You will be able to hear us, but you
will not be able to communicate verbally back with us. In your
open program you will see the chat log and chat box in there. Throughout
the presentation today you can type in questions or other bits of
information that you want to share with us. We will be receiving that
life as we go through the program this afternoon. We will post a summary
of all of the questions that you all post in there. At the end of
today’s presentation we will have a question and answer session where our
speaker will try to answer as many of the questions as we can
get through. Any that we do not will be posted on our public interact
page. Think that most everybody on the line is familiar with. We
will also post the presentation decked — deck on interact later
with the program. For the time being you can access it in the files
portion of the chat log just by clicking on it. You can download to
these presentation anytime that you would like while we are going through
it this afternoon. Again I think most of you are pretty familiar
with our interactive site and know that you can always get us there
with any questions, comments or things that you want to share
with us. And of course you can always email us at CDER . We monitor that
email box pretty regularly everyday. — Today we have two presenters
that will be walking through the program this afternoon.
The first we want — introduce you to at our last industry day
our new assistant Commissioner who has taken over here at IAEA.
We will do an update of where we are within the program and what brought
us to today’s presentation and that he will turn it over
to Navin to walk of — everyone through the rest of the program this
afternoon. Really without any further ado I will turn over to
Eric and we will get started.>>Thank you. Here is a brief agenda of our
event today. We will be showing you are common services market place
and provide invitation — information on the IAEA application developer
process. Will provide a brief background before turning things over
to Navin.>>For those of you less familiar I wanted
to share with you what IAEA. It is the residential you government
initiative managed by GSA that oversees the operations and modernization
of 10 federal award management systems. We seek to use innovative
processes and technologies to improve the systems and operations
for though who Edward a minister or receive federal financial
assistance contracts and intergovernmental transactions. IAEA is
governor for the award committee for government. Or the ace and his:
within GSA by the Federal acquisition service and the IT groups
here. IAE Has a broad scope. In sale alone and have 1.8 million
entity management records. 538. 538,000 of which are active registrants.
In fiscal year 2014 more than 1 trillion and federal assistance and
awards across 3.3 million transactions were reported. IAE Have more
than five —1 million hits or views per month.>>IAE 10 standalone system will be delighted
to what environment of your — under the banner of Sam.gov. This
modernized environment lacked other data factory or app store and
will offer any benefits to our users including single sign-on capabilities
unified built in security, open data, API cost standardized
authentication and role processes and standardized tools and business
rules. As many of you are aware right now we’re in the — Mr. large
cap modernization effort that will offer great benefits to our users.
As part of this effort we created a single foundational common services
that form that will allow for faster delivery of new software
cost savings shared security increased software quality and data integration
across the system. Now I will turn over to Navin to show you what
we have built so far.>>Thank you Eric. As Eric said, we spent
a lot of time the last 12 months including planning and effort to build
out a platform that we can use to launch applications that will actually
expand through general-purpose capabilities of at all of
the applications that we need here can be built on a common background
using common user bases caught using common tools so that this product
— program to manage the activities and watch capabilities as rapidly
as possible while also being assured that our capabilities or
applications are secure that they are sustainable. That they are transportable
across infrastructure back and as we need them to
be as well as supporting a modern approach to application development.
Whatever our basic core tenets is the [ Technical difficulties – Please
stand by ]>>We want to expand into some more of the
tools as we execute in the near term. We want to find out what developers
want to use an integrated into a platform. That doesn’t in
coordination across the board with all of our GSA counterparts to
make sure that standard matters in security matters. That we can continue
patching within the platform itself.>>We also went to create a certain amount
of controls around the relevant access. We have a team of folks were
focused on so that they really are the ones that will push applications
through the process of going through the development environment
and test environment to the staging environment and the production environment.
They are really muscled for that and what that really means
to us as an organization is that we have an independent eye on the
technical quality of the applications for quality assurance. There
is a process. But additionally we are removing — we are coordinating
heavily between the ops teams and development teams to make
sure that the applications are deployable. That they do work in our environment.
That they can scale in our environment and will be stable
within our environment as well. That means that as a developer if you
are used to a traditional that I need to be the ones to have my hands
— I want to go on developing my own laptop and buildout capabilities
that might Despina Exley fit with the capabilities that are working
out with the operational environment. We want to kind of
salt some of those problems through automation. That includes
more integration. More processes and eventually we would like to
see continuous deployment practices.>>This is a very basic view of what this
looks like. The reason why we are talking about this — I see that people
are having audio problems. I will try to get a little closer.
Hopefully that makes things better. This is a very basic view of
how we want to do this work. We wanted to address the vendor for
as. What are the responsibility of? We have a that are to donors
that are defining in that. All of this goes in the end to be able
to develop in an agile fashion. We want to be working across these
teams using the common service platform to create projects but letting
the core development teams work independently of the platform.
We don’t really want to put us in a situation where there is a deep — deeply
integrated tie between the core applications rendered and
the common services platform vendor.>>Hold on. We are going to pause quickly
so that people can dial in and see if the audio issues — we will be
back in about 60 seconds. Hopefully we can address the audio editions
— issues so people can hear what I am saying.>>[ Pause ]>>Hopefully everyone has had a chance to
dial in via phone line. I think that should address the issues. This
is a very basic idea. If you are a core vendor than this is what you
are doing. You are building out your code and writing your unit
test that will get run automatically everything of time you are checking
in code. You are checking in the code to LowestMed to make
it work. We have a way that we are doing this for those of you that are
familiar. Of enterprise that we are running internally that if we
do open source we’re pushing all of that code out to GitHub public. That
is an expectation for anybody that is working with us that we push
out our code to the public and as we work with our security folks
and get mature with our processes we would actually want to work in
[ Indiscernible ] as well.>>There are other folks involved. We have
our product owners. We had — we have the modified version of the skilled
agile framework to do our work. We work at the portfolio level because
they are 10 capabilities that we are working with that
we have to manage in a unified manner. But at the team level it is
scrawled — scrum. we are working through and support that through the
automation. That is what we are trying to do. We have 18 that is going
to create independent taps and test test and validate that the acceptance
criteria is met and code is deployable and works in a real
environment. Wehave coordination with our security team as well.
This is again something that I would say. There is a lot more to these
processes. I basically put some highlights and put them on. I am
sure that people who have done scrum forever would have questions. This
is just a very high level view of those capabilities as we move
forward. What do we have right now clear quick –? We have a capabilities
around Java. Angular For our capabilities for Java. Wehave we used
Postgres and Mongo for database environment. We have a elastic search.
Wehave GitHub. We used docker for container is — containerization.
Everything that we do within our environment. We actually containerized
using docker. We have a docker registry within the platform
that has good docker images. With every build a new informationally
build an image that gets pushed out to run and execute. End of
the scale horizontally. That is a very key part of all of this. That
we want to use that docker to scale horizontally and skill are
transportable application. As we go forward what we are looking at is
how do we can — engage the development ops team. To make sure that it
is develop all and runnable without using our CSP in the background for
development herbalist — purposes externally. That is how we do good
open-source work. You shouldn’t have to have a CSP behind you to
build the application. That is another element to that that we want to
make sure that we have created as part of our process flow.>>We have a how much of CI capabilities that
we have and the environment it we’re also adding to the environment
as we go forward. Wehave Jenkins which you will see in the environment
now to run automated test and build within our environment.
We use — we are also adding in the Simian Army for performance
tasting — testing and selenium for user interface testing that we
want to do the same thing for Jenkins that we do for everything else.
Those tests need to run as you build codes. Every build every push or
nearly every push depending on how many pushes we are talking about will
start executing these activities to make sure that the code still
runs that the tests are to — tester still passing. We’re really focused
on driving ourselves the qualities are automation of our task. Not
all of the elements are totally in place yet but we are building these
out. Of these capabilities that we have right now are sufficient
through our applications. We will be maturing the processes
and integrating more rigorous and robust continuous integration
capabilities throughout. We actually have in the document PowerPoint to
get help repository with our architecture that has been active for
security purposes. You can see all of the tools and capabilities that
we actually have within this environment of their on-site.>>This is actually another thing that creates
expectation what — run what you as a core developer would need to
do if you’re going to work with our environment. You really looking at
this and saying we have a scale back to our framework. The way that
we have embedded it is that we have quarterly releases with two weeks
rent. The reason why we have quarterly releases is that we have many teams
running that are actually interdependent. They are dependencies
between them and in order to successfully manage the dependency
with the framework that is kind of what we have figured out mates good
sense in terms of execution. And relaxed three months we have
tested it out and we have had some work with the core developer and
place and light up some of the changes to the platform with the actual
core developments that was concurrently going on as we figured out let’s
modify the process and make it better. What we saw was working as
it was designed that we were able to contain within a quarterly release
the dependencies and execute them amongst them as we go forward
those enter dependencies become very important to us. There is a reason
that it’s called the innovative award assignment. The data within
the integrated award environment is proven integrations. Within
the IAEA wehave opportunities and wehave contract options.
Wehave our registrants. Right now if you go to Sam and FBO there are
very little things that ties those three best things to get any rigorous
manner and a manner that is useful to the public at large and
vendor at large. To the contracting officer. There is still a lot
of disconnect between the capabilities. Even as we build wehave a unified
view of the data in the end and that also dries to a unified view
of our API to be able to work together. This is why we grow towards
this model. We are defining what we would see as what do we mean by Don
in each of these phases. At a relief level what do we mean by Don?
Everything have to be tested. Wehave what we are calling infrastructure
capabilities. That I could just launched directly from code into
a working environment. Wehave automated testing. All of those things
are required to say that the release is complete. What do we mean by
future? Those are some of the things that might take a couple of Sprint
to execute on. Then we have the user story. That is a real piece
of business that we are executing on within two weeks and built within
the two weeks using the process. How do we actually talk their building
those things out and what you actually need to do within that environment.
What we are really saying is if you build within the two
weeks don’t build something that isn’t 508 compliant within
the two weeks and then come back and say we are going to go fix that later
on. You can account for that as we think about what do the two weeks
mean for us. We are going to build the capabilities to post an opportunity
but in the two weeks we do all of this testing. And we use automation
around that as well. So this is the approach that we are taking.>>I think I have touched a fair amount of
this. All of the code will be public and we are working on making sure
that we can actually work in the clear. Working in the clear will be
something that is very valuable to us as we go forward. Agile development.
The Scrum on a two weeks Sprint cycle. And quarterly releases
in our safe model. And API first model. This is something that I didn’t
touch on here. What is an API first model. It means that everything
that we do from a business perspective is available by an — by an API.
We’re talking about posting an opportunity there will be an API
to be used to post the opportunity. And at API is what you build
your application on top of. Those things need to come first. We’re actually
using hypermedia model called HAL for this work which will allow
us to have independent developers pulling out the APIs and individual
applications but allow the developers to reuse the data and business
capabilities. The elements as we go forward. The vast majority
of our data is public which does mean that we are going to use APIGovernor
to connect our data out to API data.gov and make it available
with all of the throttling and things that we need to to maintain
our performance requirements. But if it is public we don’t
want to restrict or prevent people from using that. Really think that
we are going to create some grievance around are who can write to the
data set. If you want to go and create the better version — the best
example would be that we have contact writing systems that are out
there that need to write to the SB S data and to opportunity data sets.
So we work with those folks to create and give them the right access
data that they can use those great APIs. The reason that we want
to create a little bit of control is that it is the IE response ability
to be good data stewards. That has certain implications. — Around
the legality of we we are pushing into the data and we have to
control.>>What this a lot — allows us to do is to
create a fabric across IAE that allows us to see data well and allows
for the discovery of the data within the field. And to be able to execute
within a shared environment even with different vendors. — Across
the platform.>>Let’s do a quick demonstration. I’m not
going to touch on everything that we can do within these environments.
I just want to show you a couple of key screens about how
we go into the deployment for the application.>>Wehave the marketplace. This is what our
developer user would really be interacting with. This is for developers,
not for the general public. I
created a couple of things. Let’s create a
new application. So you are a little bit — we
will show you a little bit of the basics. This is industry daypart one.
Right now what we have is a very basic and it will create services of
the side and what we call a component environment. What we are working
to as well is to increase the flexibility for defining the DevOps frame
and scalability of their application. Right now application scalability
with a little bit of manual requirements to make that work. We
will have that into the market place as we go forward. I will create
an application. What is happening here. What happens when I go create
an application is that I have — you can see that I have part two and
three coming up. Part one. What is happening here is the service
that have just requested is now being creative. That is one part of this
world. This is all running on AWS — for those of you that are
familiar with RDS and for the database back ends we have several that
are being lost with this to support the application. You will note
that we have four different environments. Components. Minimum capacity
which is — components would be that you are a developer and working
every day. You are checking in code. That is where you are working.
Minimum capacity would be where DevOps will live at the end
of the Sprint. This is always up to date to a Sprint. It would be
where your potential increments in face would reside at any point
— given point in time. That is for our independent testing and users.
Production life is where you’ll start hammering at the production.
That is where you would be going in and figuring out what business
database falls in. What happens when I start using the Simian
Army to create chaos within the environment? And then master which is
production. Rather than waiting. And we will not wait for these to
get permission. This is about between a five minutes and 10 minute
process were not only are we just creating the servers but we are running
scripts to revisit the individual service within our configuration
that supports the things that we need to be able to support in the
software that we need to support. And then we are doing some additional
things as well to ensure that it happens.>>Let’s talk a little bit here about some
of the roles that we can provide here. Wife is what I did was essentially
created a project within this environment. We can create project
editors. The project managers can create developers. I’m not going
to walk through this whole process but they could also create DevOps
you — users. Each user has a different role. A developer can
check in code into the component branch which I will show you in
a moment half but nowhere else. The DevOps user is the only you can
move codes up between those ranches. Those are the sort of things that
we are supporting within this environment. We also have productivity
here to a couple of other capabilities which I actually do not think
that I have access to within this user. Within the IA data language
is an underlying support for the shared data environment that all of
the data within IE will reside in and a lot of the lead APIs for example
will come out of that environment a lot of our analytics woken without
that environment. We’re using this within that environment and
also connecting to API data.gov. Let’s go to part 2. I’ve created
part 2. I created that a little bit earlier. What you can see here
is there is a provisioning for the services that are complete. So let’s
go look at that one. Let’s go look at the actual list of services.
So here the services are associated with the particular part two. It
service really is an application. It is a component of an application.
What I’m going to do is that we have a sample service that would
actually go. The sample service is really three capabilities. Three
services. API driven services. One unit — user interface service
in a doctor composer is up with all of those three things together.
Let’s go create that service. And that takes just a few moments.
There are a couple of minutes here where there is some soccer work
happening in the backend and a push over to GitHub normally what I
would do is click on this and click on component. So in this case the
code populated immediately. What happened here was that the
sample service created within our environment this is actually still
building out. But within the part to Dr. service you see that I have
a GitHub depository. Here in the UI service in about four or five minutes
you’ll see a bunch of codes that I will show you. What you’ll notice
for those of you that are familiar with GitHub therefore branches.
The four branches with no coincidence matter dreck we to those environments
that we referred to earlier. In fact I check into one of these
branches is a push to that environment. We are using the tools like
gets pro and Jenkins to really make that push happen. At this point
what I would say — you can see here within a few minutes that the
code is not up in the environment. What I can do is go back to this
soccer service. And I could just say diploid. We set ourselves up
in this environment. If I say that I want to go in and the — deploy
the dock are composed service it will go and hit all the three services
that we saw earlier in start working on deploying them. These
one of the services is being worked to deploy. You can see here that there
is a Jenkins flow here that asserting to build out the capability
and push it up into a working environment. That takes — with all
of the Jenkins work and all the docket — docker work takes about
10 to 15 minutes. Rather than making you sit here and watch the screen
I went and created part three for the discussion. This is exactly
the same sample service. What you have here in
the docker service is a URL. A deployed this about 50 minutes before this presentation.
So I have a URL. One of the things that that we have done here is created
a virtual desktop environment for developers to basically be
able to come in. This — we did is partly because what we didn’t want
to do was force people into the GSA to sit here and be part of the environment
to go through all of the badging. But in order to do that we
created the CDI environment. So that we could control the
network but also give ourselves the ability to allow the developers
to launch this stuff into a working environment that they share
together and still hit the URL research. This is a URL that you can see
that I launched. It is in this environment. You could see the line application.
You can add a line and type in the Apple — information.
Then you add the wine and we should be able to see that in the database.
Actually I do not think that I hit that one. So that should come up
shortly. Because this is running on a very small environment everything
kind of runs slow in this environment. We don’t want to necessarily
run the largest services unless we need to. That is kind of
our flow. What I can do here, I can go to the UI service. You can
see here that we have the code. Our Java code. This is actually the
code for the front page of the user interface. And I can just do this.
Because I’m a developer I am allowed to submit to comp. At that point
it starts running the deployment process in the background. The
whole process which is another five minutes of waiting. We will not
do that. At the very and I may hit refresh so that you can see that.
That kicks off the go process and test process and deploy processes
in the background. There is a lot of work going into make sure that
the processes happen. It is something that assures us as IAE as a program
that was we’re building and deploying is actually going to work within
our environment. Hopefully a gives you the capability to work
without having to worry about all of the application — all of the
infrastructure things of the world. The plumbing as a code because
you are going to get tied into the access management capabilities. The
data capabilities. Of a see our platform and hosting capabilities.
The shared search capabilities. All of that so becomes available
to you as a developer through these — this environment. We’re looking
to make this environment better and easier to use to execute
on using the shared services throughout the IAE environment. This
is a bit different than the bare-bones path. We’re making decisions
and taking advantage to a certain extent that IAE is IAE. There is a
scope to the environment that we wanted to take advantage of. It isn’t
necessarily that I would be the first person to argue — this is not
a general-purpose platform. It is not really designed to be.
But as we work through other people within GSA I think we’re going
to see a lot of the features here that go directly into something
that would be a general- purpose capability for a path that would go
together — that different — it creates a larger environment. It is
something that is maybe not as lightweight as a very simple style of platform
or service. But is something that provides a bit of control and
evidence around all of this that isn’t too intrusive to you as a
developer. At this point I’m ready to take some questions. I know that
questions have come up. Any questions that you have, make sure that you
put into the chat log and we will start answering them.>>The first question. Will one of the services
already in IAE has the underlying data sets or will developers
need to work with IAE directly? Absolutely. The idea of API first
is absolutely not that the developers work at IAE directly to access
public data. Deal in place we with the direct interaction with
IAE would be for access to data that would — is sensitive PII kind of
data. Data that isn’t public or data that you want to write. If
you want to make a better widget for writing opportunities which we
certainly want to encourage people to do as we develop the APIs. We have
to create an — agreement to do those right. But we want to encourage
that. It is on us to not be too stingy with that as we go forward and
actually find the right way
to execute within that environment.>>Within our environment — in IAE we talk
a little — a lot about systems like FBO but we don’t talk — we are
really shifting our language as we modernize towards the data
in the world. What is the IAE data. Date is opportunity. It would be
information about registering with those who want to do business
with the federal government. It is information about contract
actions that are placed currently in FPDS. Those are the big three.
But we also have exclusions. Those who cannot do business with
the federal government. With information about past performance. Some
of that is very much not public. Those things all tie together. What
is the available data first. There is a roadmap that we use that
we work with IAE as being and ACE covered the government — E- government
program. And I believe we are hosting right now as appropriate
to the environment. The issue becomes that the roadmap has application
sensitive information in it. So some of it we can publish
in some — we are looking into how much we can publish and push
other into the world without running into data issues. But we really
talked about the opportunities work. We talked about looking
at our contract actions and what we are calling FPDS right now. And
our grants programs catalog for domestic federal assistance. Through
FDA as well. Those data sets will become available in the near
term and what we would want to do is similar to what we have done
in the past with open IAE. So this is what we have done in the past with
open IAE. We published information about our OPI and take feedback
through regarding what do our APIs look like and what data is available.>>We will absolutely consider the process
right now. We push data out to data.gov. We publish our APIs. The information
about our APIs on data.gov. We’re using API.data.gov as we go
forward for managing our APIs as well in the public sphere. The changes
that you would see would be regarding how we are publishing our
data is really pub — primarily around good usable business oriented
APIs. That is the big thing. We work with our user base in — to
see whether their methods — what other transformations that we might
want to do with the data using the tools that we have within the common
service platform to make it more easily accessible to them. For
those of you that are doing integration for example with the Sam
data extract those things are not going away. We are fully aware that
us touching any of our existing interfaces really create a lot of
problems — problems for folks that are doing integration. A lot of
the work if you are looking at doing and that a lot of the work will be
taking the APIs and making sure that the APIs trend to legacy interfaces
so the legacy interfaces can be maintained over time because we have
when IAE integrations with more than 120 or 150 applications across
the federal government and we are very aware of any breakage of those
innovations causing significant emission problems through every
one of those client agencies out there. We are very aware of that.
We had a question about debugging tools. We had it within our environment
— we have docker with a debugging enabled so that in this case
what are we talking about. Without of it — available is the Java
capabilities. Being able to do Java debugging is actually unable to
the doctor containerization through the component branches. As well as
what the advantages of doing it this way. You can still work within
your own local environment to do your own debugging before
pushing in two component as well but it is absolutely key that we do
enable debugging through an easy means through the docker instance.
Have actually done this using a clip as well as other work as well
as we’re just using the standard Java debugging. That is a key component
as we add new languages in it. We cannot put ourselves in
a position where debugging is feasible as new language is get added.
That is something — that is why we wouldn’t turn around and say to use
this language. We want to make sure that all of this stuff works for
you.>>I think unless there are any last questions,
— you demonstrated the development of an interface for the capability
to develop a website — Web service work IAE data can be
conceived by application. The interface — of the user interface that
you saw was actually user interface. But as I said there are three services
that were part of the whole capability that we have launched.
Two of them were actually in that APIs. Where using that model for that
work. And the Web service interfaces are certainly part of that
model. As I just said to building out that ability to support leave
— labor advantage will require us to build sub services because that
is what both Sam and FPDS have built into her right now. That hopefully
answers the question. And then know what great question
on the certain design elements. Absolutely. We have adopted the
CIO playbooks design standards with are linked in the chat. We
adopted them within days. Walked into work the day after I saw that
and said this is what we are going to use. We started using it. The marketplace
itself has not then styled towards that but the applications that
we have been working on lately have been. And quite successfully so.
I think that everybody is trying to use those capabilities.>>Hopefully — we will let you type in any
additional — there are a couple of good last questions. The APIs for
existing applications will they work?>>Yes. The idea would be that we need to
— we will be replicating those in — interfaces in place. And more
likely — likely than not the model that we would use that we build
a negative HAL driven API that has a fa�ade of regiment that translates
into an interface that does not extract out of the data. Whatever
we need to do that to support the legacy interfaces as we go forward.
What we hope is that over time the folks that are doing integration
with us will find it more useful to be integrated directly to the
rest capabilities. The rest driven how during capabilities because
that would give them access to the other IAE capabilities directly
through the URLs within that API. We hope that that is something that
we work to overtime as we do this modernization.>>We are actually working. Monitoring. We’re
going to be building in a couple of customized dashboards using the
design APIs for monitoring of the infrastructure plus capabilities that
would work more at a docker level and component level to put together
some dashboards. We want to work with our DevOps teams to define
what those requirements are. We have a number of tools and I don’t
have them in the top of my head but they are listed in the architecture
document that was linked to earlier in the presentation. Feel free
to go in there and take a look. They are all there.>>Yes. To answer the last question. Of those
all be ready as part of the FBO and FPDS modernization. Spike yes
we arty worked with these the last which was awarded in September if
I recall correctly and we have Artie begun work in his environment.
We have arty figured out that we need to go in and approve this and
get better processes around this. We have to document this a little bit
better. So we are learning using that process. And hopefully as we go
forward — is not our hope — but it is our intent that we are going
to be publishing all of the documents and processes at least along with
our acquisitions if not onto public websites if necessary.>>We are going to close out and think everybody
for your attention. And of course, keep typing questions into
the test for another four or five minutes and we will post them onto interact
the answers to the questions as we go forward. Some of the questions
we will be able to answer and some of them we will not. But I
hope that for those of you who are looking to work with us and become
developers of a platform have a better sense of what we are doing here
and how it might work for you. Thank you very much. Stay tuned for
information about the next industry days. We are using the user
chattels of — channels of interactive the emails that you signed up
for to give you information about what comes next for us. Think you very
much and have a good afternoon.>>[Event Concluded]

Comment here