Factsheets
Name and Alias
When naming an item please avoid acronym and use the full name in the Name field and use the Alias field for any acronym. An example of this would be Advance Scheduling System aka A55. The benefit of this approach means that reporting has meaningful names while also possible to search using acronyms.
Provide a concise description of the application, keep in mind that the reader is likely not to have as much knowledge of the systems as yourself, so keep it high level and business focused.
Subscriptions
Collecting and maintaining accurate data is crucial for EAM. To address the challenge of managing large amounts of data and ensuring its accuracy over time, it's important you take responsibility and accountability and contribute in your specific area of knowledge and expertise. By subscribing to Fact Sheets ensures the right people are notified and have a clear call-to-action to maintain and administer the data.
Subscription Types
There are two types of subscriptions
Responsible
These users are in charge of keeping the Fact Sheet up to-date and correct. The subscribed user actively participates in the content creation and updates of the Fact Sheet.
Observer
These users are notified and kept up-to-date regarding changes to Fact Sheets. They can also participate in Surveys but are not responsible for maintaining the information in the Fact Sheets.
Subscription Roles
We have identified 10 roles that help define your purpose with the factsheet.
Business Analyst
Responsible for analysing business needs and identifying solutions that align with organisational goals.
While it is possible for a BA to take responsibilities for any factsheet it is expected to concentrate on the following:
Business Context
Goals
Objectives
Business Owner
Accountable for defining and prioritising business requirements, ensuring they meet strategic objectives.
A Business Owner can be responsibility for or an observer of any factsheet but with a focus on the following:
Business Capability
Organisation
Process
Application
Collaborator
Enthusiastic partner who facilitates communication and coordination between stakeholders to drive shared outcomes.
Feel free to collaborate on any fact.
Enterprise Architect
Oversees the design and implementation of an organisation's overall architecture, integrating technology and business strategy.
An EA is responsible for any factsheet.
Programme Manager
Leads a program of related projects, ensuring alignment with organisational objectives and managing resources effectively.
A Programme Manager can only be responsible for
Initiative
Project Manager
Manages a specific project, overseeing scope, schedule, budget, and quality to deliver desired outcomes.
A Project Manage may be responsible or just observe
Initiative.
Solution Architect
Designs and implements solutions that meet specific business needs, considering technical, functional, and operational requirements.
Technical Architect
Develops and maintains the technical aspects of an organisation's architecture, ensuring scalability, reliability, and security.
Technology Owner
Generally Technology senior leader, who will provide strategic guidance over the application or service and is the relationship owner between solution provider and business owner.
Quality Seal
This provides a level of data integrity. While it's possible for any users (with non viewer role ) to change any factsheet, the Quality Seal prompts those responsible (see above) to confirm the changes and certify the factsheet is accurate.
The 4 stages of a quality seal
Approved
Broken / Check Needed
Draft
Rejected
Lifecycle
TODO
Tags
TODO
Completion Percentage
By having a high completion percentage reflects back that the factsheets have been considered and well maintained. One very simple way to increase the percentage is to select Leave empty against properties that are not relevant to a factsheet.
For instance, it is rare for an application to have a Child relationship
Last updated