# data[].attributes.headline
What key activities does your value proposition require? What activities are most important for your distribution channels, customer relationships, etc?

# data[].attributes.subject
What key activities does your value proposition require? What activities are most important for your distribution channels, customer relationships, etc?

# data[].attributes.body
Ticket creation and processing; - The architect of the application would be giving information when needed;

Reporting, Dashboards & Data Access - the main functionality - as an architect, i want to get into the ACS and check out the whole life cycle of the application on a dashboard;

Notification & Communication Capabilities - Automated Notification - Case by case, warning about tags expired, problems in the life cycle overall. Any reports given from the vendors need to be recycled once a year and so reports would be useful;

No Priority Change Approval

Central System for Application Onboarding

Ticket Type –TSR, PIA, CC, ServiceNow (for App ID) - we're not talking much about tickets, but actually for requests for different dependencies (TSR, PIA, and many other) - When we onboard new application, we'll be needing to get all the information needed for the several processes needed for the onboarding conformity;. After validation, we can then create an App ID in SNow;

No Categorization of Tickets

Status -

Transfer Ticket Process Flow (TSR, PIA,CC, ServiceNow (for App ID))

Will the workgroup logic be needed? - Each architect is only responsible for a couple applications. So creating groups would make us able to divide responsabilities and security accesses in the ICM;

# data[].attributes.headline
What core value will we deliver to our audience? Which needs will we be satisfying?

# data[].attributes.subject
What core value will we deliver to our audience? Which needs will we be satisfying?

# data[].attributes.headline
What key resources does your value proposition require?

# data[].attributes.subject
What key resources does your value proposition require?

# data[].attributes.headline
What relationship does the target audience expect you to establish? How can you integrate that into your work in terms of cost and format? 

# data[].attributes.subject
What relationship does the target audience expect you to establish? How can you integrate that into your work in terms of cost and format? 

# data[].attributes.headline
Through which channel does your audience want to be reached? Which channels work best? 

# data[].attributes.subject
Through which channel does your audience want to be reached? Which channels work best? 

# data[].attributes.headline
Which groups are you creating value for?Who is your most important audience?

# data[].attributes.subject
Which groups are you creating value for?Who is your most important audience?

# data[].attributes.body
Architecture Product Control Center (ACS) will be used to track application status from commission with App ID to compliance per Cybersecurity and Privacy.

# data[].attributes.headline
Integrations - Which ones will be only receiving or sending information?

# data[].attributes.subject
Integrations - Which ones will be only receiving or sending information?

# data[].attributes.body
TSR

Archer/TAGS

Old RSAM database

ServiceNow

Archer/PIA

PCF compliance

Kenna for vulnerabilities

Planview

ServiceNow Assets (IT)

Global Asset Registry(non-IT)

We could have other integrations;

# data[].attributes.body
Developers team

Contact with the business stakeholders

ICM structure and codes

# data[].attributes.body
Architects;

Product owners?

# data[].attributes.body
Architects;

Dell application product owners and teams;

Who is the audience of the ACS?

# data[].attributes.body
Atlantico's usual communication plan

# data[].attributes.body
Atlantico's usual communication plan

Meetings for requirements definitions

# data[].attributes.headline
Today, from our understanding, we do not have a functional system for TAGS and other conformity needs. Are the usual forms that will be the content for the ticket creation?

# data[].attributes.subject
Today, from our understanding, we do not have a functional system for TAGS and other conformity needs. Are the usual forms that will be the content for the ticket creation?

# data[].attributes.body
New layout of the project, including fields change and prototype;
Business rules definitions;
Some dashboard views;

# data[].attributes.body
Enhance the dashboards;
Set up the requesting features;
-TSR is the main integration;

# data[].attributes.headline
Platform used to define the strategy of the application door start. 

# data[].attributes.subject
Platform used to define the strategy of the application door start. 

# data[].attributes.headline
Audience: solution architects, along with enterprise architects and business

# data[].attributes.subject
Audience: solution architects, along with enterprise architects and business

# data[].attributes.headline
TAGS is just a dependecy system. It would be a downstream system to be integrated with. We'll manage all TAGs in this system as well as all the compliance requests for a particular application;

# data[].attributes.subject
TAGS is just a dependecy system. It would be a downstream system to be integrated with. We'll manage all TAGs in this system as well as all the compliance requests for a particular application;

# data[].attributes.headline
We are looking at the application life cycle.

# data[].attributes.subject
We are looking at the application life cycle.