Integration Toolbox

This database of databases is a planning tool to schedule and prioritize government integration by identifying potentially sharable, cross-departmental databases and business processes.

There are fields for outside agencies to indicate interest in sharing components in order to speed up integrating multiple agencies at once. Searches may be possible to find all potential sharable components between agencies automatically without the need to specify any component or agency.

To integrate a whole government, the first step is to inventory what the government has. That is one of the things that this integration tool will do and it will work best if there is a person specifically defined to be an integration manager in each agency. They will fill out most of the data and use its collaboration features.

All organizations should have their data in one database. For example, the state of New York should have only one version of this containing all state, county and city agencies in one database. There is nothing wrong however, with a single agency using this tool to experiment with its own IT information independently.

If you know of any similar tools, please contact me.

Besides centralizable databases and business processes, this database will contain and cross-reference the following tables:

Agency business needs for the future
Agency business problems

The purpose for including the above is to generate a total view of an agency where data, business processes, business problems and future business requirements can be seen in one place. Then intersections can be found or planned which lead to solutions.

The CEIs' list of waiting-to-be centralized data and business processes as a whole will constitute the government's integration plan.

Definitions

The difference between integration and centralization. This semantic distinction is used only here for this tool. Integration means taking isolated systems and merging them into one. For example, if an agency has a project tracking system and a separate project billing system, integrating them would result in one system that does both. Centralizing means eliminating redundant copies of something and sharing one version of it, for example, all business units in an agency could share the same chart of accounts, all state agencies could share the same table of county codes or all government agencies that manage public parking could use the same parking management system. Used elsewhere on this website, the meaning of integration includes all types of centralization, consolidation, sharing, integration of data and business systems.
(1:M) symbolizes a one-to-many relationship. Many of the fields should be in child tables but were left in the parent table for viewing convenience. It is clearly evident where the child tables should be created.
(PK) means primary key
(A-F) symbolizes the spectrum of levels of something; amount can be A, B, C, D, E, or F. For example, potential sharability of a table of client account codes could have an "A" level. Something with a low potential to be sharable would have an "F" level.
Global integration manager - the person in charge of integrating cross-agency data for one project.
Problem category - problems are categorized so that repeating patterns can be identified and analyzed for solutions
Change opportunities calendar - is put at the top of the menu because this is what the integrators must stay on top of to catch integration opportunities. For example, if a business system will be altered, it means that there is a budget and resources ready to implement change. The CEI must be prepared to be involved in the concept and design phases of change to look for integration possibilities. This is the most important stage of any project and will save the most money by setting up the system correctly and nipping any poor designs in the bud. All planned business software and data changes should be logged in the integration tool. The change opportunities calendar also automatically triggers a review of client wish lists from related components
Problem priority level locally - ranked as A-F level within the agency - pain points
Problem priority level globally (ranked as A-F level) - for example how does it rank amongst a whole state's problems; is it the number 1 problem in the state of Florida?
Overall level of table driven system - is the system table driven correctly, which is good (level A), or are there many functions buried in the programming code which should be transformed into tables to give the organization a more flexible, robust system (level F)? Knowledge of this helps decide whether to repair the system or not.
Ongoing costs due to poor design (1:M) - can be totaled and this is a one to many relationship so the total can be broken down
Core mission (Y or N) - is this component part of the core mission of the agency? For example, if it a personnel system for a licensing agency, it is not part of the core mission, but if it is a licensing system for an agency whose main business is to license individuals, then it is part of the agency's core mission.
Alerts - notify integrators of potential problems
Lost functionality - these records become part of the requirement specifications for a replacement or repaired system
Links to Change Advisory Board, CFO, RFPs and FSRs - integration managers can study emerging project landscape
Interdependent components - allows users to list all related components to facilitate impact analysis, find integration opportunities, etc. Users define what interdependent means.
Integration work description, Integration work initiation date, Integration work completion date, Integration work percentage completed are used to allow summary, detailed and historical reporting of government-wide Integration work. It should be a child file of the parent, but is shown on the parent file for viewing convenience.
Centralization ID - links potentially centralized databases to a parent table of proposed centralization projects

This tool brings cross collaboration and integration across all government organizations.

It assembles ITIL, Project Management and Enterprise Integration methods together into one organizing tool that promotes the following:

Cross agency data and process sharing
Data harmonization
Project managment
Strategic planning
Metrics generation
EA transition strategy
Business intelligence
Rapid and continuous alignment to organizational mission

Not all features need to be used; only need to
use project portfolio for example

Menu

Login - We will not use your email or phone number for telemarketing.
Change opportunities calendar
Flash tour
Web and text page tour
Govenor's and Legislature's overview. (Get legislators THINKING about cross agency leveraging and eliminating stovepipes. Marketing to change the terminology and stovepipe-think)
Set menu levels (filtered by agency, amount of detail, etc.)
Project managers' menus
Change Control Boards' menus - list all interdepent components and stakeholders
Integration or centralization projects (search by many criteria, e.g., priority, cost, savings, completed, needed, waiting, in progress, potential, agency, core mission, cross-agency initiatives - collaboration: local, global, etc.) Example, list all agencies that are collaborating on projects. List all succesful or almost completed projects.
Prioritized integration and centralization needs
Database of databases
Database of business processes
Summary of loss of functionality costs due to lack of integration or centralization (local or global)
Summary of top business problems (local or global)
Summary of top business needs (local or global)
Summary of one time costs to centralize and integrate (local or global)
Summary of monthly savings due to centralization and integration (local or global)
Locate government integrators (mass email them, etc.)
Periodic assessment and performance review calendar
Periodic business intelligence meetings with execs, etc. calendar
Suggestion box: how to improve this integration tool
Links to Change Advisory Board, CFO, RFPs and FSRs
Auto notification of new or updated information (new integration data, new agency participation, interdependent changes, etc.)
Report of core mission or non-core mission components by agency
Disussion forum (find all topics - by subject or date or person - or add new topic) - executive summary of the tip; include site recommendations.... see the piece of paper in my pocket
Training - descriptions of what intergration projects did wrong and what they did to be successfull
Statistics - what are most popular searches - use to improve system
FAQ
Dictionary to standardize agency definitions
Legislative Summary
Executive Summary
CIO Administrative Requirements Calendar
Export data out
publish to Intranet
publish to Intranet
Export to SQL loader
Export to Excel and mail to me
Export to flat file
Auto mail me whenver there is a match
set up continual match search for this componentent and have it run each day and email me the results and send me SMS message
Links to best practices
Links to best Project Managment knowledge
Weekly reporting of "what's new" and "what we do" web displayed content for each agency so that it builds an environment of collaboration. Need an internal, external and executive privileged versions
Component associatons (problems, agency mission - trace back to what they belong to)
Suggest a new project
Make a suggestion for an existig project, system, database, process, lob, category, program or any other component
Make a suggestion for a project being CURRENTLY CREATED to nip problems in the bud
add granularity to your group - you define the group that will have and its privildges
Governance - Put checkpoints under a GOVERNANCE menu heading
Lessons learned library local (b) global
Add yourself as a stake holder - must be approved by the approver but this will help communications on various levels

NEED TO THINK IF I SHOULD BREAK DOWN COMPONENTS INTO SUB-GROUPS SO PROBLEMS CAN BE UNDER A SUBHEADING FOR EXAMPLE.

FINALLY, NEED TO THINK IF EACH COMPENT NEEDS TO BE CLASSIFIED IN A HEIRARCHY SO THAT INTERDEPENDENCIES CAN BE AUTOMATICALLY DISPLAYED IN THE CORRECT ORDER. OR, SHALL JUST SPECIFIY WHO IS ABOVE AND WHO IS BELOW SO THAT IT DOES NOT NEED NUMBERING, OR SHOULD I HAVE BOTH?

Table of component associations (examples, database, agency, table, business process, computer system, PROBLEMS,customer satisfaction, audits, painpoints)

ComponentCategoryID (example: database)
ComponentID (specfic database)
AssociatedComponentCategoryID (example: table)
AssociatedComponentID (example: specific tables)

Table of databases (I think much of this belongs under Project table)

ComponentCategoryID
ComponentID
Name of database
Short description
Detailed description
Business category (1:M)
Business process ID (1:M)
Business system ID (1:M)
Local sharability potential (A-F)
Local sharability success level (A-F)
Global sharability potential (A-F)
Global sharability success level (A-F)
Centralization ID (1:M)
Potential integration level (A-F) (1:M)
Integration project ID (1:M)
Date of planned update (very important) (1:M)
How sure is it that planned update will happen (very important) (A-F)(1:M)
Planned update description (1:M)
Entities interested in sharing (1:M) (Agency ID, or contact info)
Experts on this database (1:M)
Global integration manager for this database and their backups (1:M)
Sharability documentation, general information and discussion history or where this information is located
Repairs needed (1:M) (past, present and future) (repair category and repair description fields in the child record)
Overall level of normalization
Overall level of disrepair
Ongoing cost to maintain (1:M)
Ongoing financial costs due to poor design (1:M)
Ongoing worker hours due to poor design (1:M)
Functionality lost due to poor design level (A-F)
Details of functionality lost due to poor design (1:M)
One time cost to modernize or replace
Potential monthly savings amount if repaired or replaced
Core mission (Y or N)
How often does this component change (A-F with F meaning never) and why
Part of a vendor licensed product that government cannot legally share (Y or N)
Is this a desired new component that does not exist yet (Y or N)
Does this no longer exist (Y or N) (this record should be kept for historical reasons)
Does this no longer exist because successful integration has replaced it (Y or N)
Date created
Date terminated
Date this component was reviewed and analyzed (1:M)
Who reviewed and analyzed this component (1:M)
Alerts (1:M)
Alerts notification schedule (1:M)
Percentage of original project completed
Integration work description (1:M)
Integration work initiation date (1:M)
Integration work completion date (1:M)
Integration work percentage completed (1:M)
Interdependent components (1:M) (component ID, notes, etc.)
Platform (1:M)
Vendor name, Product name (1:M)
Geographical location (1:M)
Where does this go? Redundandt? need to flag new projects as EA or non-EA as a one-to-many
relationship maybe with name of person, and date so the history of
evaluations can be seen. Maybe at one time it was non-EA, now is. Maybe
need t have the lastest as the dominant status of it
At what stage did this database become analysed for alignment to EA?
At what date, time, did this database become analysed for alignment to EA?
Who analyzed this for alignment to EA? What department? Oversight, external or internal?

Table of Default checkoff categories (these are the default ones recommended by the agency administrator)

checkoff category ID
Comments
Links to best practices

Table of checkoff categories (for all governments)

Checkoff category ID
check off category (Data examples:
CHECKOFF on internal data harmonization y_or_n
CHECKOFF on external data harmonization y_or_n
CHECKOFF on Normalization y_or_n
CHECKOFF on internal integration y_or_n
CHECKOFF on SOA/extrernal integration y_or_n
CHECKOFF on alignment to mission y_or_n
CHECKOFF on problem table y_or_n)
CHECKOFF on users having ability to write in suggestions or complaints while on the system to a centalized problem area y_or_n)
agency education is a checkpoint
programmer and database developers educations is a checkpoint
all managers and executive education is a checkpoint
Is all you need to do is add 2 fields to make it universal for all agencies?
Security checkoff
If the new system has metrics built into it. Meetings between PMO office and metrics-providing-coders and the CEI to have business intelligence meetings on how to set up the metrics- case by case basis - http://www.whitehouse.gov/omb/egov/a-2-prm.html
MUST designate ONE main person that is reponisble
for assuring that EA/Integration factors are fully processed
Put in a warning (volunatry) each time someone logs on that there has been some role assigned to make sure all EA/Intergration requirements are met and they must sign off on it
Need to have new item to be asked at all checkpoints! Was it reviewed for "extra field concept"? This means that before the design has started, has anyone reviewed the IT system to see that if only a few extra fields identifying which organization it is, would all that would be necessary to turn the IT system into a universally usable system

Table of checkoff statuses (for one specific project or component)

CheckoffCategoryID
ComponentCategoryID
ComponentID
Component checkoff (data examples:
CHECKOFF on internal data harmonization y_or_n
CHECKOFF on internal data harmonization (date, who, comments)
CHECKOFF on external data harmonization y_or_n
CHECKOFF on external data harmonization (date, who, comments)
CHECKOFF on Normalization y_or_n
CHECKOFF on Normalization(date, who, comments)
CHECKOFF on internal integration y_or_n
CHECKOFF on internal integration(date, who, comments)
CHECKOFF on SOA/extrernal integration y_or_n
CHECKOFF on SOA/extrernal integration(date, who, comments)
CHECKOFF on alignment to mission y_or_n
CHECKOFF on problem table y_or_n)

EA/Integration alignment history

ComponentCategoryID
ComponentID
AlignmentHistoryID
AlignmentHistoryNarrative
Date
PersonID

does the ieTool need to have child field for all of the areas/databases where this HAS been already harmonized and
places where it NEEDS to be harmonized?

Table of suggestions

ComponentCategoryID
ComponentID
SuggestionID
SuggestionNarrative
Internal suggestion urgency level (1 urgent 2 normal 3 low)
Externall suggestion urgency level (1 urgent 2 normal 3 low)
PersonID
Date

Table of collaboration experts

ComponentCategoryID (data: problems, a database, or business process or business computer systems collaboration experts (this is business software, like Java code or PL/SQL code, for example, a personnel system)
ComponentID
PersonID
Comments
Date

Table of EA alignment analysis stages (at what point was this object first analyzed for EA alignment?)

General (E.g., Change Control Board, Conceptual Design, FSR, Oversight Committe, ?)
Specific

Table of tables

ComponentCategoryID
ComponentID
Database ID (1:M)
Short description
Detailed description
Global integration manager for this table and their backups (1:M)
Approximate number of records
Part of a vendor licensed product that government cannot legally share (Y or N)
Is this a desired new component that does not exist yet (Y or N)
How often does this component change (A-F with F meaning never) and why
Date created
Date terminated
Date this component was reviewed and analyzed (1:M)
Who reviewed and analyzed this component (1:M)
Alerts (1:M)
Alerts notification schedule (1:M)
Percentage of original project completed
Integration work description (1:M)
Integration work initiation date (1:M)
Integration work completion date (1:M)
Integration work percentage completed (1:M)
Interdependent components (1:M) (component ID, notes, etc.)
Platform (1:M)
Geographical location (1:M)

Table of business computer systems (this is business software, like Java code or PL/SQL code, for example, a personnel system)

ComponentCategoryID
ComponentID
Computer system short description (e.g., distributed cost system)
Computer system long description
Business category (1:M)
Sharability potential locally (A-F)
Sharability potential globally (A-F)
Current shared level locally (A-F)
Current shared level globally (A-F)
Date created
Date of planned updates (very important) (1:M)
Overall level of table driven system (A-F with A being the best)
Ongoing costs due to poor design or not fixing or replacing it (1:M)
Ongoing lost functionality due to poor design or not fixing or replacing it (A-F) (1:M)
Detailed description of ongoing lost functionality due to poor design or not fixing or replacing it (1:M)
Potential savings amount
One time cost to modernize or replace
Ongoing cost to maintain (1:M)
Entities interested in sharing (1:M)
Experts on this system (1:M)
Global integration manager for this computer system and their backups (1:M)
Sharability documentation, general information and discussion history or where this information is located
Core mission (Y or N)
Part of a vendor licensed product that government cannot legally share (Y or N)
Is this a desired new component that does not exist yet (Y or N)
How often does this component change (A-F with F meaning never) and why
Date created
Date terminated
Date this component was reviewed and analyzed (1:M)
Who reviewed and analyzed this component (1:M)
Alerts (1:M)
Alerts notification schedule (1:M)
Percentage of original project completed
Integration work description (1:M)
Integration work initiation date (1:M)
Integration work completion date (1:M)
Integration work percentage completed (1:M)
Interdependent components (1:M) (component ID, notes, etc.)
Platform (1:M)
Vendor name, Product name (1:M)
Geographical location (1:M)

Table of business process categories (1 single statewide table)

ComponentCategoryID
ComponentID
Business process category short description (e.g., public parking lot management)
Business process category - detailed description
Related categories (1:M) (ID and notes)

Table of business process categories collaboration experts (1 single statewide table)

Business process category ID
RoleID

Table of business processes

(not a computer system, just the process, like, "regulating fishing limits")

ComponentCategoryID
ComponentID
Business process category (1:M)
Computer system ID (1:M)
Business process description
Database ID (1:M)
Global integration manager for this business process and their backups (1:M)
Core mission (Y or N)
Part of a vendor licensed product that government cannot legally share (Y or N)
Is this a desired new component that does not exist yet (Y or N)
How often does this component change (A-F with F meaning never) and why
Date created
Date terminated
Date this component was reviewed and analyzed (1:M)
Who reviewed and analyzed this component (1:M)
Alerts (1:M)
Alerts notification schedule (1:M)
Percentage of original project completed
Integration work description (1:M)
Integration work initiation date (1:M)
Integration work completion date (1:M)
Integration work percentage completed (1:M)
Interdependent components (1:M) (component ID, notes, etc.)
Platform (1:M)
Geographical location (1:M)

Table of problem categories (1 single statewide table)

ComponentCategoryID
Problem category name
Problem category description
Related problem categories (1:M)

problem category
1. lack of feature
2. bug
3. past bug that was fixed

solution category
1. new IT feature
2. bug fix
3. IT centralization
4. data harmonization
5. IT integration
6. SOA
7. shared process

Table of problems

ComponentCategoryID
ComponentID
Agency ID
Problem category ID
Experts on this problem (1:M)
Problem description short summary
Problem description - detailed as desired
Date problem first appeared
Related computer system ID (1:M)
Related database ID (1:M)
Problem priority level locally
Problem priority level globally
Business process ID
Estimated monthly cost of not repairing it
Estimated repair cost
Estimated time to repair
Problem solution completed (Y or N)
Date problem solved
Core mission (Y or N)
Clients (1:M)
Date this problem was reviewed and analyzed (1:M)
Who reviewed and analyzed this problem (1:M)
Alerts (1:M)
Alerts notification schedule (1:M)
Percentage of original project completed
Interdependent components (1:M) (component ID, notes, etc.)
Has this problem been solved by (a) integration (b) new system (c) (d) programming fix (e) other
Give details how problem wias fixed (400 char)

Table of problem collaboration experts

Problem ID
PersonID
Comments

Table of alerts - latest messages emailed to you about events here.

Table of agencies

Agency ID (auto created from year_month_day_sec_agency_name)
Agency name
Agency internal ID (what they use themselves)
Agency description
Integration history (1:M) (When was formal agency-wide and statewide integration initiated? By whom.)
How much of the agency integration information analysis is currently completed (percentage)
Brief overview of agency integration current status (human text)
Location of centralized integration documentation
When will most of the agency integration be completed
Potential overall integration level internally (A-F)
Current overall integration level internally (A-F)
Potential overall integration level externally (A-F)
Overall integration level externally (A-F)
CEI ID (integration manager for whole agency) and their backups (1:M)
Historic CEIs and their backups (1:M)
Country (headquarters)
State or province (headquarters)
Street 1,2, 3, 4
City
Definition of agency scope (from agency scope table .e.g, US federal agancy, California state agency, etc.)
Does agency have EA/Integration analysis check points?
Comments on Does agency have EA/Integration analysis check points?
have EA or centralized location for EAdocuments
links to WWW EA tutorials are a check point

Table of ageny collaboration experts

Agency ID
PersonID
Comments

Table of agency EA/Integration checkpoints

Agency ID
Checkpoint ID
Checkpoint location
Checkpoint description (e.g., PMO, Dept. of Finance Oversight, Budget)
Date checkpoint was established (year, month, day, decade fields)

Table of agency EA/Integration checkpoints personnel

Checkpoint ID
PersonID

Table of EA/Integration checkpoint instances (This must be supplied by the checkpoint person)

Checkpoint instance ID
Checkpoint instance description
Checkpoint ID
Project ID
Comments

Table of EA/Integration checkpoint instances times and people

Checkpoint instance ID
Checkpoint date
PersonID
Comments

Table of chief of enterprise integration personnel (integration manager for each agency)

PersonID
Agency ID

Table of genral government categories

Category (Military, Justice)
Category ID
Comments

Table of general governemt categories collaboration experts

Government category ID
PersonID
comments

Table of SPECIFIC government categories

Category (Military - procurement, Justice - witness protection)
Category ID
Comments

Table of SPECIFIC governemt categories collaboration experts

Government specific category ID
PersonID
comments

Table of SM Topics

SM topic
SM topic ID
SM comments
Agency ID

Table of SM Topics collaboration experts

SM topic ID
PersonID
Comments

Table of SMEs (subject matter experts)

SM topic ID
PersonID
Comments

Table of LOBs (lines of business)

get fields from some EA page

Table of LOB collaboration experts

LOB ID
PersonID
Comments

Table of data harmonization (data harmonizor at EPA http://iaspub.epa.gov/edr/COMPARE_TOOL$.STARTUP
has a data steward field)

source of the data
structured or unstructured
Database ID (1:M)
discussion (who, time, comments) 1:M

Table of Searchable Harmonization Databases

Agency ID
URL
Method to search

Table of persons

PersonID (automatically created by system) made of year_month_day_hour_min_second from system time (YYYMMDDhhmmss) plus user_email, for example, 20070301220159alexglaros@surfermall.com
person password (that they choose, must be encrypted) (required) (do not use same password that you use for banking or important systems)
person password hint
person first name
person last name (family name)
person middle name(s)
person previous names(1:M)
person_integration_goals
person information (what are their interests, etc.)
person email (1:M) note to user: fogotten passwords will be e
mailed to all of these email addresses (1 email address required)
person website (1:M)
person telephone(1:M)
person telephone_description(1:M) (e.g., cell phone, home, etc.)
person_willing_to_receive_phone_calls_y_or_n (default yes)
person_willing_to_receive_emails_from_other_users_y_or_n (default yes)
person_latest_will_accept_phone_calls
person_earliest_will_accept_phone_calls
person_will_accept_phone_calls_sun_or_sat_y_or_n
person_time_zone
person street address1
person street address2
person street address3
person street address4
person city
person state or if outside US other category of area
person country (validated from table)
person valid user y_or_n (invisible to user)
DataModelingSkillLevel (Need to "highly recommend" filling out the data_modeling_skill_level field because an important part of integrating all government will be done by people using data modeling)

Table of projects

Project ID (users don't see this. Make it a unique primary key consisting of concatenated sysdate (YYYMMDDhhmmss) plus user_email, for example, 20070301220159alexglaros@surfermall.com)
Agency ID (1:M)
Project acrynom if any (e.g., SAM)
Project short description
Project detailed description
Documentation, general information and discussion history or where this information is located
Components_that_are_part_of_this (1:M)
Is integration/centralization planned in a stepwise manner or all at once
Alerts (1:M)
Alerts notification schedule (1:M)
Sponsor (1:M)
Date this was reviewed and analyzed (1:M)
Who reviewed and analyzed this (1:M)
Percentage of original project completed
Integration work description (1:M)
Integration work initiation date (1:M)
Integration work completion date (1:M)
Integration work percentage completed (1:M)
Interdependent components (1:M) (component ID, notes, etc.)
Platform (1:M)
Geographical location (1:M)
Stage: Suggested,conception,study,planning, implementatin,completed, retired
EA_designed_y_or_n

Table of Programs

Program ID
Program short description
Program longer detailed description
Agency ID (1:M)

Role category table

Role category ID
Role category name (stakeholder, PM, agency, sponsor)
Role category description
Comments

Role table (humans)

Role category ID
Role ID
Role description (public stakeholder for fishing permit project, fiishing license programmer)
Comments

NOTE: NEED TO RETAIN HISTORICAL RECORDS OF WHICH HUMAN DID WHAT WHILE IN A SPECIFIC ROLE

Component Category Table (smallest granularity)

Component category ID
Component category (field, table, database, business process, person, hardware, agency, role)
Comments

Change control - Interdependency table

ComponentCategoryID (example: database)
ComponentID (specfic database)
AssociatedComponentCategoryID (example: table)
AssociatedComponentID (example: specific tables)
Internal Comments
Public suggestions

Change Control Notification table (stake holders)

Role ID I think I have to redundantly contain both RoleID and PersonID in each
record instance cause otherwise, how would I know when the person left the
job, and or temporarily came back to do work on one thing only
Component ID
Contact procedure
Internal Comments
Public suggestions

Table of general standards
Need a general standards table so that non-IT type components and roles can be standardized. This can be menued from the "what we do" areas also. Discussion forums can be generated for this purpose.

GeneralStandardID
GeneralStandardShortDescription (e.g., Cost Allocation)
GeneralStandardDetailedDescription (e.g., for accounting department, should this activtiy be called "Cost Allocation", or "Distributed Cost"
GeneralStandardFinalComments

Table of general standards integration experts

GeneralStandardID - for example, chart of accounts, etc
RoleID

Table of general standards conversations

GeneralStandardID
PersonID
Comments
Date-time

Table of which items slipped by without checkoff (e.g.,
data fields got named without being harmonized with related already-existing systems so can determine the reasons.

Group granularity and SQL statements for scope of privildges

EditingGroupID

Table of Discussion Groups

DiscussionGroupID
DiscussionGroupTitle
DiscussionGroupShortDescription (e.g., Metrics)
DiscussionGroupLongDescriiption
DiscussionGroupURL

Table of Discussion Group Discussions

DiscussionGroupID
PersonID
Date, time
DiscussionGroupComments

Table of Metrics

ComponentID
have a checkoff box for if the new system has metrics built into it
need a metrics discussion group
need maintenance metrics and cost metrics
need work saved metrics and customer satisfaction metrics
build all of these into each system and have a checkoff box for each one

New menu item: create an interdepency table (more than one table can be created for the same components, so that you can create general overviews, middle views and detailed views)

Change control - Interdependency table
1. ComponentCategoryID (example: database)
2. ComponentID (specfic database)
3. InterdependencyID (e.g., narrow billing server)
4. InterdependencyIDOrder (type increments of 100 to place the order
of this component)
5. InterdependencyDescription
6. AssociatedComponentCategoryID (example: table)
7. AssociatedComponentID (example: specific tables)
8. InternalComments
9. PublicSuggestions
Change Control Notification table (stake holders)
1. RoleID
2. ComponentID
3. ComponentCategoryID
4. Contact procedure
5. InternalComments
6. PublicSuggestions

Table of Permissions
ComponentID
RoleID

Table of PermissionsDependencies (Needs more granularity)
1. ComponentCategoryID (example: database)
2. ComponentID (specfic database)
3. AssociatedComponentCategoryID (example: table)
4. AssociatedComponentID (example: specific tables)

Table of Project Denials by DOF

AgencyID that denied the project
BusinesUnitID that denied the project
Followup on what consequences were for denial (1:M)

Table of Strategic Goals. - Must align to the mission of the organization. Can be linked to each project and program.

Table of security classifiction - need a class table for object security level for example, database is public or confidential; how to pick out both types in the same table?

Table of access rights - field on each component - oversight requirement field - for congress or dof also need viewable by field so one agency can show records or tables only to people on a certain list, but need only a simple flag to indicate yes or no on this so that it doesn't slow system down ... save this for last because it could slow the system down

Table of Variances - exceptions to components that could not comply with integration, SOA, EA, etc.

need forum to discuss hardware experience - hardware reviews - ongoing hardware problems - and SMEs for that

Note: all tables will have these fields:

Date this record was created
Who created record
Date this record was modified (1:M)
Who modified record (1:M)