Please enable JavaScript.

Coggle requires JavaScript to display documents.

BJB (SCOPE & REQUIREMENTS (Information Flows / Integration (ARIS -…

- - - - Design new application
        
        P3373-7
      - Design new component
        
        P3373-18
        
        P3373-32
      - Design new interface
      - Design new infrastructure platform
        
        P3373-32
      - Design new peripheral
        
        P3373-101
      - Design new Information Flow
        
        P3373-38
        
        P3373-44
        
        P3373-105
      - P3373-45
    - - Change existing application
        
        P3373-7
      - Change existing component
        
        P3373-18
        
        P3373-32
      - Change existing information flow
        
        P3373-38
        
        P3373-105
      - Change existing infrastructure platform
        
        P3373-32
      - Change existing interface
      - Change existing peripheral
        
        P3373-101
      - P3373-45
    - - Enquiry FINMA recertification
      - Enquiry GDPR reports
      - Enquiry IT / Business relations
      - Enquiry consistency check
      - Enquiry repository content
  - - - Business Architecture
        Data
      - P3373-46
      - P3373-72
    - - IT Architecture Data
      - P3373-46
      - P3373-72
    - - Personal for
        Responsibilities
    - - User roles for ALFABET
      - P3373-52
    - - Services, Deployments
      - P3373-70
      - P3373-89
    - - IT Architecture Data
      - P3373-70
      - P3373-89
  - - - Application Overview
        
        Tabular (Excel)
        
        Full export of all applications and all
        attributes as a table.
        
        P3373-30 Dynamic
        
        P3373-34
      - Application landscape
        
        Diagram (PDF)
        
        Visual representation of applications
        per domain, sub-domain, or location.
        
        P3373-30 Dynamic
      - Information Flow Overview
        
        Tabular (Excel)
        
        Full export of all information flows and
        all attributes as a table
        
        P3373-30 Dynamic
        
        P3373-34
        
        P3373-41
      - Application without Service
        
        Tabular (Excel)
        
        List of all application that not linked
        with a service from the service center.
        
        P3373-30 Dynamic
      - Component Overview
        
        Tabular (Excel)
        
        Full export of all components and all
        attributes as a table
        
        P3373-30 Dynamic
        
        P3373-34
      - Platform Overview
        
        Tabular (Excel)
        
        Full export of all platforms and all
        attributes as a table.
        
        P3373-30 Dynamic
        
        P3373-34
      - Missing Responsibility
        
        Tabular (Excel)
        
        List of all objects that unmanaged, i.e.
        that do not have a responsible.
        
        can be obsolete
        
        P3373-27
      - Usage tracking
        
        Tabular (Excel)
        
        Export of application usage per user.
        
        .dat
        
        SystemAdmin PDF p.332
      - Change History
        
        Tabular (Excel)
        
        Export of all changes made by user.
        
        Getting Started PDF p.135
    - - Enablement
        
        Tabular (Excel)
        
        List of applications that provide access to personal data according to GDPR.
        This report is already implemented (therefore no detail description) – it need to be ensured that it still works
        
        P3373-12
      - Subject Level 1
        
        Tabular (Excel)
        
        List of processed data categories on a subject according to GDPR.
        This report is already implemented (therefore no detail description) – it need to be ensured that it still works
      - ROPA Controller
        
        Tabular (Excel)
        
        Personal data management overview according to GDPR.
        This report is already implemented (therefore no detail description) – it need to be ensured that it still works
      - ROPA Processor
        
        Tabular (Excel)
        
        Personal data management overview according to GDPR.
        This report is already implemented(therefore no detail description) – it need to be ensured that it still works
  - - - Staging phase - The legacy system JBAR provides the original data for cleansing, transformation and validation purposes.
        
        Cleansing step
        Attributes and content that are not needed anymore will be removed.
        
        Transforming step
        A new object model structure is introduced and mapped to the cleaned data. Furthermore, each enumeration value is analysed and if necessary reformulated.
        
        Validating step
        Validation rules will ensure that the data is consistent before handed over to the loading phase.
      - Loading phase
        ALFABET is importing the data after all steps of the Staging phase are completed.
      - Reconciliation
        uCMDB, ITSMDB, and ARIS synchronize with ALFABET.
      - P3373-15
      - P3373-43
    - - In order to fulfil the transforming process from JBAR to ALFABET, clear and unambiguous definitions are needed. The link to the current valid definitions, proposed future definitions and the approach chosen for this project can be find in the glossary (section 8). As mentioned in the glossary, the distinction between application, component, platform, etc. will be defined in the execution phase of the project. At the same time, the project has to map each data object to the new data model. A case-by-case examination of objects is needed because of poor data quality in JBAR. The current data model of JBAR defines all data objects as application. A distinction is made by a type definition. Table 1 shows the data objects and object types in JBAR as constituted on 11th of October 2018.
  - - - An activity monitor alerts specified users about changes that have been made to specified objects in an object class. The monitor owner must specify a set of attributes that are to be monitored and may specify a set of users that are to be alerted if the monitor is triggered. An email will be sent to the monitor owner and all defined users when the monitor is triggered.
        
        The monitor owner and specified users should be alerted about changes made to the start and end dates of information flows defined for a specific set of applications. In this case, you would define an activity monitor of the type Application with the monitored context Application Information Flows. You would then define the attributes Start Date and End Date to track.
    - - An inactivity monitor alerts the monitor owner and specified users about the absence of activity occurring to specified objects in an object class. The monitor owner must specify a set of objects that are to be monitored and may specify a set of users that are to be alerted if the monitor is triggered. An email will be sent to the monitor owner and all defined users if a specified object is not changed or reviewed within a specified period of time.
        The monitor owner can specify the monitor object as reviewed via the Mark as Reviewed button in the object profile of the targeted object.
        
        The monitor owner and specified users should be alerted if no changes are made to an application. Specified applications should be reviewed on a monthly basis. In this case, you would define an inactivity monitor of the type Application with a monthly frequency.
- - - - 2 Workshop + Concept
        
        12 PT
    - - 1 Workshop + Concept
        
        4 PT
    - - 2 Workhsiop Concept
        
        12 PT
    - - 1 Worksho + Concept
        
        2 PT
  - - - No Report Filter for Report
    - - 5 Workshops in April
        
        1-2 Stakeholder + 1 ALFABET
- - - - Confirmation that the proposed solution covers BJB’s needs that are specified in this RfP document
      - In case you cannot offer a solution that covers all the needs of BJB, please outline which of the requested deliverables cannot be met
  - - - Specifically mention scope of proposed solution (in scope and out of scope)
    - - SCRUM?
  - - - Answered requirements list
    - - Resumes of the project core team, which will support BJB from start of the project until go-live. For each resume please explicitly show:
        
        Project role and seniority
        
        Experience with implementation of relevant vendor products
  - - - Please provide the following details:
        
        • Scope/volume of the implemented solution
        
        • Implementation approach until go-live of full scope and duration
        
        SCRUM
        
        • Vendor’s/Partner’s involvement in the project
        
        • Involvement of customer staff (approximate number)
        
        Team + Core Team
        
        • Success factors of the project
        
        • Managed risks of the implementation
        
        • Lessons learned from previous experience in other projects
- - - - • Scope/volume of the implemented solution
      - • Implementation approach until go-live of full scope and duration
      - • Involvement of customer staff (approximate number)
      - • Success factors of the project
      - • Managed risks of the implementation
      - • Lessons learned from previous experience in other projects
  - - - Description on how each of the described requirements can be fulfilled
        
        Confirmation that the proposed solution covers BJB’s needs that are specified in this RfP document
        
        In case you cannot offer a solution that covers all the needs of BJB, please outline which of the requested deliverables cannot be met
    - - Earliest possible service start
      - Description of the proposed activities / steps and milestones
      - Effort allocated to BJB (per requested role)