Dinah YoungProject Manager / Software Asset Manager| Prince William CountySpringfield, Va, United States
This is more of a software project issue. When we have a vendor come in with their software that we are planning to purchase, one of the first things we ask for is an architecture diagram. We want to see how many servers, how they plan to interact, what ports they need, etc. This information is reviewed by our security and infrastructure team.
It seems that the last several vendors did not have this information. When we asked for it, they replied that they usually do not need to provide this and then they pull together some crazy, inadequate diagram. We end up having to build the diagram for them.
I do not understand why vendors would not have this information readily available and why previous customers have not asked for it. If you are buying a product, wouldn't you want to know the structure and the security measures taken to ensure the data is not accessed? Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The problem is not they needs. The problem is how it will impact on your enterprise architecture. You (or something into your organization) must analyze the impacts at the very begining and obviously that will demand to work with any people involved. Usually, to get some information, it is in the field of business analysis. Here is a way to do that inside an article that was published by the PMI and the IIBA as "best practice". Hope it helps you: https://www.projectmanagement.com/blog-pos...-right-solution
...
1 reply by Dinah Young
May 09, 2018 1:55 PM
Dinah Young
...
I actually have this article printed out and sitting on my desk. I had briefly read over it, but wanted to spend some more time on it.
Saving Changes...
Dinah YoungProject Manager / Software Asset Manager| Prince William CountySpringfield, Va, United States
Just to put some more detail in how my organization is set up. I work for a County Government. There are 38 agencies in the County in addition to the court system (Circuit Court, General District Court, Juvenile Court, etc). Each agency has their own objectives. The agencies are supposed to work with IT when purchasing or replacing a new system. Sometimes they bring us in before making a decision, sometimes it is not until after the decision has been made.
Over a year ago, Circuit Court decided to replace their Records Management System with a new vendor. We were brought in after they selection had been made. We had to work with the vendor and the Court to set up the servers, migrate the data, etc. The money for everything came out of the Court's budget. We were there for support, but we also needed to ensure that the vendor complied with our standards. Step one, what is the architecture you need to set up. Answer, we do not usually create Architectural Diagrams. Our response, you will create them now before we can proceed.
A couple of weeks ago, Fleet Mgt comes to us and tells us they have selected a vendor to replace their Fleet Mgt Maintenance System. They wanted us to use their cloud solution. After looking at the pros and cons it was decided that we will go on-prem. We asked for an architecture of how the servers will be set up. They sent us a basic diagram with swirling lines and boxes and said that they usually do not have these.
These are the situations I was referring to. Saving Changes...
Dinah YoungProject Manager / Software Asset Manager| Prince William CountySpringfield, Va, United States
May 09, 2018 1:29 PM
Replying to Sergio Luis Conte
...
The problem is not they needs. The problem is how it will impact on your enterprise architecture. You (or something into your organization) must analyze the impacts at the very begining and obviously that will demand to work with any people involved. Usually, to get some information, it is in the field of business analysis. Here is a way to do that inside an article that was published by the PMI and the IIBA as "best practice". Hope it helps you: https://www.projectmanagement.com/blog-pos...-right-solution
I actually have this article printed out and sitting on my desk. I had briefly read over it, but wanted to spend some more time on it. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Just to clarify my previous comment. Enterprise architecture is composed by layers/architectures which are: business, application, technology, information, security. The most important ones is business layer/architecture because is the driver to define all the others. So, to be successful, somebody has to make an impact analysis to define who the new initiative will impact into the others. If that is not doing then the probability to fail are higher. Saving Changes...
Dinah YoungProject Manager / Software Asset Manager| Prince William CountySpringfield, Va, United States
True. The business layer and it's impact on the County is managed at a higher level. Before an Agency can decided on a new process or upgrade an existing process, they need to go through the CXO, make sure it aligns with the strategic plan, go through the budget office, and then purchasing.
The CIO of IT needs to approve the technology layer.
Then it comes to me. I am focused on the technology, information and security layers.
...
1 reply by Sergio Luis Conte
May 09, 2018 5:47 PM
Sergio Luis Conte
...
Understood. Then it is more critical to request what you stated into your post. If not a high risk is in place and the risk will impact to you and all your organization. I was on the other side of the desk (as a provider as an integrator of several providers) and I could say why some of them do not have what you request. When i was provider or integrator I always work with the customer to provide as much information we have to minimize the impacts. I did not belongs to sales division and the closer I was from there was accountable for presales then I faced lot of times that my division must make the dreams comes true where dreams were what the sellers sold. So, if you ask me, as lesson learn and if you have the possibility to do that, do not get an agreement or contract with providers that do not give you an architecture map or do not work with you to get one at least.
Saving Changes...
John DuncanRetired| RetiredLebanon, Tn, United States
I think what you're seeing is the knowledge of the sales team vs. the technical team.
The sales team is usually very prepared to pitch the features and benefits, and work on costs some. The technical team comes in behind them, and figures out the details based on number of users, expected transaction volume, uptime requirements, etc. - more of a case-by-case basis.
That may be why they don't have a "standard" diagram at the ready.
(or they want to steer you to the cloud solution...) Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
May 09, 2018 2:20 PM
Replying to Dinah Young
...
True. The business layer and it's impact on the County is managed at a higher level. Before an Agency can decided on a new process or upgrade an existing process, they need to go through the CXO, make sure it aligns with the strategic plan, go through the budget office, and then purchasing.
The CIO of IT needs to approve the technology layer.
Then it comes to me. I am focused on the technology, information and security layers.
Understood. Then it is more critical to request what you stated into your post. If not a high risk is in place and the risk will impact to you and all your organization. I was on the other side of the desk (as a provider as an integrator of several providers) and I could say why some of them do not have what you request. When i was provider or integrator I always work with the customer to provide as much information we have to minimize the impacts. I did not belongs to sales division and the closer I was from there was accountable for presales then I faced lot of times that my division must make the dreams comes true where dreams were what the sellers sold. So, if you ask me, as lesson learn and if you have the possibility to do that, do not get an agreement or contract with providers that do not give you an architecture map or do not work with you to get one at least. Saving Changes...
When you did your RFI or even pre-contract signing, maybe include the requirement for an architecture diagram before selecting a vendor. Saving Changes...
Dinah, I guess part of the conflict we need to define requirements and review requirements then send out RFQ if you know what you really want to implement otherwise send out RFP and let the vendor provide best solution based on their experiences and compare with other vendors, keep cross checking until you award it to the right vendor Saving Changes...
