The single most important question that an architect needs to be able to answer is, "What alternatives did you consider, and why did you choose to do it this way?" As per your experience you may have capibilites to care about these things.
As Enterprise Architect, you should look for the things that how the solution fits into the business??
If you have done work as a Solutions Architect and you have designed the solution, determines technology, plataforms etc then you can proeed towards Enterprise Architech.
I suppose one of the key things is that you've got to understand the problems in terms of multiple levels of abstraction. That's not very easy, because each level of abstraction has its own restrictions and domain of applicability, yet there is coupling between the levels too. Details matter, yet can overwhelm. Finding a good balance, especially one that you can explain to others, is difficult.
Lots of different idioms and practices is essential if you want to do any serious software architecture. Sometimes the greatest lesson you can learn from a particular framework/approach is how not to do something. And learning how to recognize a bad design will be indispensible when you design higher-level systems and frameworks of your own
You can start learning design patterns and systems designs would help even more. That is, concepts as explored in Design Patterns (GoF), Patterns of Enterprise Application Architecture (PoEAA), embedded systems, real-time systems, interprocess communications, etc.
Especially useful are state machines, operations research and systems engineering, which are applied in software architecture.
But of everything there is to learn to improve your software development skillset, the most critical is state machines.
Utilize and improve your development skill, operation management, data/schema design, infrastructure planning, support service and as Enterprise Architech keep yourself in the the business approaches like cost cuttins etc.
Here is some links that help you what to learn and do in next time to be on this job profile:
Senior developer role to architect role
Standard practices for an architect
Would experience in multiple programming languages/frameworks assist one in becoming a software architect?