What this is
The Business Process Hub describes the business processes of the applications the City is assessing, from the application down to the individual steps. For each process it shows the vendor source it comes from, a process map, the steps, who performs them, and draft test scripts.
Where the content comes from
Each process is taken from the vendor's published guide or help topic. The citation is kept with the process, so you can open the page or PDF it came from. Process maps and test scripts are generated from that catalogue. They are drafts for review, not finished procedures.
Finding your way around
- Home: what the catalogue holds. The counts follow the Role, Application and Business process status filters, so they match what you see on the other pages.
- Capabilities: every module grouped by the business capability it supports, such as Finance and Accounting, Procure to Pay or Talent and Learning. Each capability and module shows its status and progress. Open a module to see its processes, and use the process register to sort and filter them.
- Business Processes: browse the catalogue as a tree, from the business capability down to the area, with Expand all and Collapse all above the list. Configuration & Support is one more top-level entry; under it each application lists its own support topics. Search for a process by name or ID. Open a process to see its source, process map, steps, test scripts and training.
- Roles: find the processes, standard operating procedures and test scripts for a job role. Roles are grouped by business capability, and the application follows the role name, for example Buyer (Oracle) or Maintenance Planner (EAM).
- Training: training materials for each process, down to level 3, arranged by business capability and then by job role. Material that covers a whole module is listed at the top of its capability.
- Search box: at the top of every page. Type part of a name or an ID such as C2C-BIL and pick a result.
Every list on the site looks the same: a tree you open with the chevron, the count on the right, and the open item highlighted. Tiles use the same card style as the Capabilities page.
Menu
The Menu button at the top of every page, marked with three bars, holds the display options and the filters. A number on the button shows how many filters are in use.
- Theme: switch between Light mode and Dark mode. The choice is remembered in this browser.
- View: List or Tiles. This chooses how Business Processes, Roles and Training are shown: a tree you expand, or tiles you open one level at a time. The choice applies to these pages and is remembered in this browser.
- Filters: see the next section.
Filters
The same filters are in the Menu on Home, Capabilities, Business Processes, Roles and Training. Clear all in the Menu switches every filter off.
- Application: show only the processes of the chosen applications, for example Oracle Fusion Cloud or Octave EAM. You can choose more than one.
- Business process status: In scope only, Level 4 only, and the catalogue status (Reviewed, Draft, Skeleton). Choose several statuses to see processes that have any of them.
- In scope only: hide processes that are not within the project scope.
- Level 4 only: show only processes that have level 4 steps and a process map.
- Role: show only the processes where a chosen job role acts. You can choose more than one role, and a process is shown when any of them acts in it. Use the search box to find a role, and My roles to choose the roles that belong to you when the site knows them. Your own roles can be applied automatically when you sign in. On the Roles page the filter lists only the chosen roles.
Capabilities page
Modules are grouped by what the business does, not by the application they come from. Each capability and module carries a status:
- Reviewed: every process that can be built has been reviewed.
- Draft: some processes have level 4 steps that are built from the source and not yet reviewed.
- Skeleton: the processes are listed but no level 4 steps are built yet.
- Reference only: the guide holds lists and tables, with no steps to build.
When a capability draws on more than one application, each module is prefixed with its application code, for example ORACLE · MNT, EAM · ATN-EAM or D365 · D365-SVC, so you can see which application provides it. Capabilities served by a single application show no prefix. The same prefix is used in the Business Processes and Training lists.
The bar on each card shows how much of the module is built and how much of that is reviewed. Reference topics are left out of the count. The page remembers the capability or module you looked at last and opens there next time.
Repeated topics
Some modules are built from several vendor guides that each describe the same task for their own product area. Identity and Security Controls, for example, uses the Securing Applications, ERP, HCM and SCM guides, so a task such as creating a role mapping appears in each of them. Every version keeps its own steps. On the Capabilities page the register shows the task once, with a link such as "3 more guides" that opens the other versions. Clear Group repeated topics above the register to list every process separately. A process page lists the same task in other guides, with a link to each.
Setting scope (administrators)
Members of the administrator group see a tick box beside each process, step, area and module on the Business Processes page. Ticking a box changes what you see at once and keeps the change in your browser. Nothing is saved to this site. Choose Export scope changes in the bar at the bottom of the page to download the changes as a file. The Business Architecture Group applies the file, and the change reaches everyone when the site is next published.
Training on a process
A process page lists the training materials stored for that process. A step marked Training was written from a vendor step guide, and the link opens that guide. The guide covers the whole process, not only that step.
How current it is
This site is a read-only copy published on request. It was built on (build ). It does not update by itself. Nothing you do on this site is saved to it, and it cannot be used to enter information. Scope changes made by administrators are only a request until they are applied and the site is published again.
Status labels
- In scope: the process is within the project scope at the time of the build.
- skeleton: the process is listed but its steps are not built yet.
- l4-draft: steps are built from the source and not yet reviewed.
- reviewed: steps were checked against the source.
Questions and corrections
Contact the Business Architecture Group.
Internal use only.