Define Context Actors Can be Groups, Roles, Systems Examples KHP, Dispatchers, EADCR
Define Context Messages Any Information sent from one place to another, In any format Example, accident form, dispatch notice All Types Text, voice, radio, form, report, video, image, ect
Define Context Actors outside of topic area Actors inside of topic area
Actors Can be Groups, Roles, Systems Bureau Of Computer Services Bureau Chief Bureau Chief Of Computer Services CPMS CMS Email System Area Engineer Designer Ben Nelson DB2 Don’t use personal names or technology, both will change Use the level of Detail that is appropriate for the topic.
Messages Actor A Actor B Daily Report Financial Transaction Voice Message Yearly Report Request for Information Batch File Form Signature XML data Role Specific information Receipt Acknowledgement If in doubt put it down, You can clarify it later For every Yin there is a Yen. Look for the completeness
There are a lot already done, Identify your topic and request all current messages for that topic
Give feed back if someone else’s model is not accurate
KDOT's Business Partners KDOT Accident Reports, Traffic Impact Incidents Road Conditions, Traffic Status Vehicle Accident Analysis "Drug Testing"/Drivers License Checks, Project Plans, Vehicle Usage, Payment Information Invoices, Transportation Statistics, GIS Views Research Information Incidents, Problems, Permit Applications 511 responses, KANROAD responses, Project Information Invoices, Permit Applications, Contract Status, Utility GIS Info Project Plans, Project Schedules Contracts, Payments and Schedules Design Plans, Weekly Accomplishments, Invoices, Collaboration Requests for Bids, Contracts, Plans, Change Orders Bids, Invoices, Status reports Project Plans, Invoices, Contracts Funding Limits 5 year plans, TIP Plan Invoices, Local Payments Project Plans, Invoices, Contracts Funding Limits 5 year plans, TIP Plan Invoices, Local Payments Grants, Loans Vehicle Information, Inspection Information Vehicle Reports, Applications, Ridership Information Permits, Road Conditions, Detours etc. Travel and traffic info, Road Conditions, Detours Incidents, Problems, Permit Applications Info req., incidents, problems Req. for info, eGov transactions Requested info, eGov transactions Consultants, Design Contractors Cities Counties Public Transit Authorities Law Enforcement Other State Agencies Universities and Colleges Public Utilities Truckers, Trucking Co Motorists Other States and Federal Agencies
The Models don’t appear complete, What did I do wrong
For 30 years we have been building solutions to feed stuff to agency Staff. Then they do something with it. They:
Import it to Excel/Access
Generate form letters from Word, Mail out packets
Separate and distribute to other parties
Incorporate this with other information and create reports then distribute
If It goes to someone in your agency, Find out what they do with it. If they do nothing with it it may be a dead end. (mostly they just don’t think about what they do as adding value)
Basically keep asking questions until you see the real end customer And then ask what the real end customer does with it.
Things you can do for clarity Put the Organization roles inside the Organization units KDOT Supplier KDOT Purchaser Request Bid Current Bid Purchase Order Item requested & shipping order Payment Invoice ACTORS Messages Purchaser Payment staff Receipt clerk Salesman Shipping Officer Billing Officer Connect the messages to the roles, You can see there is now multiple parties involved in approval and authorities
If possible Identify the Key of the message (IE Project ID, Voucher Number)
You can do this for your project,
We will work with you to do this for total agency models.
Agency and Your Business Partners PS We may not be the only agency who works with these business partners KDOT Supplier KDOT Purchaser Request Bid Current Bid Purchase Order Item requested & shipping order Payment Invoice ACTORS Purchaser Payment staff Receipt clerk Salesman Shipping Officer Billing Officer These are Relationships to manage & points for competition Suppliers Customers Citizens Legislature Other Agencies Cities Counties
When you connect message flows to technical implementations, you can
Use the Context Models to identify big picture needs and changes
Develop Macro level considerations for Technology Architecture replace-ability.
Develop Phased evolutions for legacy systems.
Why Do I care about a message? Every Message becomes a program eventually. And each program is tied to associated technologies and is an investment for KDOT. When you look at a message in current solution and you look at the message in Future solution. Look for technology and customization options that you can add to make life easier for our customers CMS System Contractor Area Engineer Contractor Status Report Mainframe DB2 Views XXX Program XXX Server Web Server Business Objects Server SSL Layer Program XXX Client Contract ID Option AE ID Option Schedule Options Authenticate Parameters Report Parameters Data Service USER Sees this We Build this
Understanding relationship between your Business, Its strategy, Its business Partners, and current and future IT Systems.
Clarity is good,
Use Big Pictures and Big Paper, Or High level and low levels related. This is not a 8 ½ X 11 exercise.
Focus on KDOT’s Process, Supporting Data and Communication Methods Today’s Session Strategy objectives goals critical success factors Organization Structure business units roles skills business partners Business Processes activities goals workflow Information data letters/faxes drawings email Applications programs systems spreadsheets Technology software hardware network Enterprise Architecture