Phase Highlights - What's involved
Use the Current Phase Inventory report on the DEAR Reporting Site for the scope of data collection (NOTE: This report will filter out systems that are currently being worked on by the blueprint teams). Each step takes about 5-20 minutes per system depending on the complexity of the system (i.e. number of sub-systems)
Phase 3a
Phase 3b
- Step C Create BRM relationships
- Step D Update C&A System to Member System relationships
- Step E Making Person and Organization Role relationships - optional
Supporting Documents
- Phase 3 Training Workshop Documents (Agenda)
- Go to Phase 3 FAQs on this activity
- Read the wizard tutorial PRM and BRM section
- DOI Reporting Site for Nightly Reports (DOI Network Only)
- Review the DOI PRM and the DOI BRM v2.0
- NOTE: IAWG Data Validation Phase III kickoff call summary notes - July 19th, 2003
Steps
Step A--Validate Phase 2 Data Load
Validate your Phase 2 efforts. Go to Phase 2 Guidance to review the scope of Phase 2. Check that these are correct:
- deployment information updates
- SRM/TRM updates
- C&A System member systems
- system interface diagrams
- added bureau systems
Use reports, the wizard, and the FAQs to help you validate. It should take you about a minute for a monolithic system or 2-5 minutes for a tiered system.
Step B--Create PRM Relationships
In the DOI PRM, map investments to Intermediate Outcomes or End Outcomes.
To defend your investment, you need to understand how it fits into a system and is managed, and how it supports the overarching DOI Strategic Plan. If the investment doesn't focus on DOI's mission, maybe it should be funded more by other agencies. On the other hand, if many systems are supporting the same intermediate outcomes, maybe the investments can be combined.
Use these concepts for mapping:
- Would outcomes worsen, or not be met at all, if you removed this investment?
- Does the investment help measure the outcome, so removing the investment would mean the outcome isn't measured as accurately?
- Can you map to intermediate outcomes? This is better since they are children of end outcomes, and so are more detailed.
- Would the outcome be negatively affected without the investment? (Don't map the investment as supporting the outcome unless this is true.)
Use the Offline Data Collection Spreadsheet to streamline collection from multiple system owners. Then load results using the wizard.
Step C-- Create BRM Relationships
Map DOI BRM Functions and Activities to Sub-systems. The Guidance includes:
- Intro to the DOI BRM v2.0 and changes
- Reference Model Report Support
- How to link Functions/Activities to your Systems/Sub-systems
- How to load into your BEAR via the System Wizard
Use the (ZIPPED) Offline Data Collection Spreadsheet to streamline collection from multiple system owners. Then load results using the wizard.
Step D-- Create C&A System to Member System
Synchronize C&A Command Center and DEAR by verifying C&A System and their Member Systems. The Guidance includes:
- Validate your BEAR System Inventory with the C&A Command Center inventory
- Systems not in Command Center, validate if part of a C&A System
Use the Offline Data Collection Spreadsheet to streamline collection from multiple system owners. Then submit changes to your BITSM and DEAR Admin.
- NOTE: Command Center and DEAR are Synchronized on a Quarterly Basis. Command Center is the Source of Record for C&A Systems and the C&A Attributes. DEAR is source of record for mapping C&A Systems to DEAR Systems. A C&A System cannot be added to Command Center without first aligning with DEAR.
Step E--Making Person and Organization Role Relationships (Optional)
We've focused on systems and investments where you are the managing partner. What if you aren't the managing partner but you use, fund, host or in general dedicate resources (time, money, people, etc.)?
For instance, BLM tried to create a report to show all systems that needed the Citrix ICA client on the user's desktop. The organization role had not yet been populated, so the report created only included BLM-managed systems requiring the client.
The solution was to capture how BLM uses the Citrix ICA client for other systems; that is, the Uses relationship. Since BLM uses inter-department and inter-agency systems (like DEAR) that use an ICA client, capturing BLM's Uses relationship to other systems lets BLM to create a more complete report that shows how the system is actually used across the enterprise.
There are many cases across the bureaus where, if organization role relationships aren't populated, BEAR reports may not show the whole systems environment, leading to bad decisions based on the bad information.
If you analyze any of the reference models back to systems, you can also use person and organization roles to show where you use, fund, or host a system beyond your managing portfolio. For example, you might want to know:
- All the systems in your organization using Citrix as a technical service specification
- All systems cross-referenced with ones you manage or fund
- All systems you host that provide ad-hoc reporting, and the technologies they're based on
To make the person or organization role relationships, collect the information with the Offline Data Collection Spreadsheet, then submit a help desk ticket for a DEAR administrator to check and batch load the data into your BEAR.