Functional Conceptual Design Document
Sample of Scott Mason’s Documentation Skills
Project ID: CRQ00000011223
Date: 03/26/2023
Current Document Version: 1.2
Page 1 of 8 Document Version: 1.2
1. Introduction
Lists of contacts, contributors, approvers, reviewers, and sponsors are provided in this section in addition to an overview of the project’s scope and objectives and functional requirements, documentation deliverables, and impact assessment and classification methodology.
No | Name Full | Organization | Phone | |
1 | John Smith | CFO | 818 977 9999 | |
2 | Vijay Kumar | Architect | 818 977 9998 | |
3 | Jenny Lewis | AP | 818 977 9997 |
Three documents have been deemed Financial Cloud Data Solution Assessment Project deliverables:
Functional Conceptual Design Document
Technical Conceptual Design Document
Key Design Decisions Document
This Functional Conceptual Design Document's purpose is to conceptualize the functional impact to cloud data structures in terms of how they are consumed by business unit organizations, processes, and applications.
The accompanying Technical Conceptual Design Document's purpose is to conceptualize the technical impact to cloud data usages as they relate to MIS support organizations, interfaces/reports, program module logic, and application configuration.
Where options for execution present themselves throughout this assessment, a series of Key Design Decision Documents (KDDs) will be requested by Approvers or Reviewers of this document, project sponsors or members of the Executive Steering Committee.
The primary objective of this project is to provide – 1) an assessment of the impact of changing the master data definition and usage of a set of intellectual property “labels”, 2) the long-term strategy for the disposition of the Location Exception Table (LET), and 3) the impact and usage map to support the retirement the MPM Attribute Extension Table (MET) – as specified in the Financial Cloud Data Solution Assessment Requirements and Charter Documents.
A secondary objective of this project is to ensure the recommendations made by the Business Process Improvement Team in conjunction with key business unit representatives are feasible from an MIS viewpoint and that there are no impacts left unaddressed.
The intellectual property label list, including the list MET attributes, is as follows:
Requirements – IP MPM Label Fields | |
Business Requirement Name | Requirement Tech Name in SAP ECC |
FB Reporting Group | ZREPG |
Production Entity | ZSPLPROD |
WIII Label | ZWBHVLABEL |
WEI Label | ZWBPILABEL |
Acquisition Code | ZSPLACQC |
Primary DRH | ZDRH |
Alt DRH | ISMLANGUAGES |
Co-Finance | ATWRT |
Video Version Sub-Owner | ZATTYP |
Video Version Participation Label | ZATTYP |
MET - MPM Sub-Owner | ZSUBCODE |
MET - MPM Label | ZLABCODE |
MET - MPM Location | ZLOCOD |
MET - MPM Original Release Date | ZORDATE |
MET - MPM Market Entry | ZENTRYCODE |
MET - MPM Business Unit | ZUNITCODE |
MET - MPM Franchise (Dom) | ZDOMCODE |
MET - MPM Genre | ZGENCODE |
MET - MPM Pay-Per-View Date | ZPVDATE |
MET - MPM Rating | ZRATCODE |
Usage of master data evolves over time, especially as organizations grow, reorganize, and acquire other organizations. It is natural for inconsistent policies and misunderstanding of data definition to develop when there is a lack of data quality enforcement and data governance oversight. Ultimately these situations will result in business process inefficiencies and various other points of pain.
Our Company Sample business units have documented their challenges relating to usage of master data and the resulting impact to financial and 3rd party participant reporting. Corporate Finance and the Business Process Improvement Team have worked closely with them and other corporate areas to identify the root causes behind their need to develop the reporting workarounds in place today.
In late January 2023, The Company Cloud Data Solution Assessment (CCDSA) Project was approved calling for this impact assessment and XBCAS, VHEAS, FCC/IMCC support.
The “Current State” section of the chart below depicts the twelve intellectual property labels and sample values in use today.
The “Future State” section depicts how we could reduce the large number of values (for example, over 661 Production Entities and 708 Video Version Participation Labels) and reduce the total number of fields from twelve, to five or six.
In the December planning phase of the assessment, a survey and recorded video were sent to the representatives of key areas to announce the project, announce the potential for cross-project impacts, describe the types of resources required, and announce the need to begin the marshaling of the forces and to begin the requisition and on-boarding processes if resources were not immediately available.
Category | Disposition Group | Effort Group | Triage Group |
X | X | X | X |
Object | App | Module | Data Structure | Data Object |
A | X | X | X | X |
Category | Disposition Group | Effort Group | Triage Group |
X | X | X | X |
X | X | X | X |
At the January 13, 2023 kick-off we described the details of our metadata collection and assessment approach in preparation for Subject Matter Expert classification activities. The process of classification was created to aid in their research and the categorization of thousands of potential impacts into manageably-sized groups (or “classes”) which could be assessed as a whole rather than one-by-one.
OBJECT CLASSIFICATION | USAGE CLASSIFICATION |
Assessment Framework – What is requested of everyone? Start Here
Impact Analysis Object Classification Conducted by IMCC Project Team Conducted by CRM/SMEs See Appendix Page 27 for List of Values
Conceptual Data Model Functional Conceptual Design Document Produced by IMCC Project Team Each “object class” will be addressed in the functional concept solution document in terms of required changes to: •Process Design •Application Design •Data Function •User Organization Draft produced by IMCC Project Team Reviewed and Approved by CRM/SMEs Next Page © 2012 Warner Bros. Entertainment, Inc. Proprietary & Confidential 10 | Previous Page Impact Analysis Usage Classification Conducted by IMCC Project Team Conducted by CRM/SMEs Data Object Interfaces See Appendix Page 27 for List of Values
Reports
Conceptual Application Diagram Produced by IMCC Project Team Each “usage class” will be addressed in terms of required changes to: •Application Configuration •Program Modules •Data Structure KDDs •IT Support Organization Drafts of all documents will be produced by IMCC Project Team Future Possible Implementations © 2012 Warner Bros. Entertainment, Inc. Proprietary & Confidential Reviewed and Approved by CRM/SMEs 11 |
The results of the Object Classification Assessment are provided in this document | The results of the Usage Classification Assessment are provided in the Technical Conceptual Design document |
X | X | X | X |
The Classification Tool was developed and now holds thousands of objects and usages consumed by our line-of-business and enterprise systems that could be affected by the proposed changes.
These impacts have been categorized into “classes” based on four dimensions:
Category of in-place solution as “Standard” or “Customized”
Disposition of change in terms of number of systems and support groups impacted
Effort in range of hours to implement change
Triage Group identifying who or what would facilitate or control the change
A screen shot of the Classification Tool can be seen below.
This MIS assessment should not only include an evaluation of deployed applications and their up and downstream systems but projects and other initiatives as well that might be impacted by these recommendations. In December a survey was sent to representatives of the key areas asking them to identify in-flight projects or initiatives that might be impacted by the changes. The results of the survey are shown below.
