1 / 52

Scope Page 3 - 1

3/2/2012 3:14 AM. Scope Page 3 - 2. . . Session Plan. CVISN Architecture overview (10 min)Key concepts: information exchange, standard IDs, Web, EDI, DSRC (15 min)

lilia
Download Presentation

Scope Page 3 - 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. 3/3/2012 6:20 PM Scope Page 3 - 1

    2. 3/3/2012 6:20 PM Scope Page 3 - 2 Session Plan CVISN Architecture overview (10 min) Key concepts: information exchange, standard IDs, Web, EDI, DSRC (15 min) “How to” steps (20 min) Breakout Plan (15 min) Breakout (90 min) Review and, if necessary, complete Pre-Work Start Action Plan, Decision Table, State System Change Summary LUNCH State presentations & questions (30 min) Total Time = 170 min (2 hrs, 50 min) + 55 min lunch break

    3. 3/3/2012 6:20 PM Scope Page 3 - 3 Session Objectives Understand the cornerstone CVISN operational concepts and architectural guidelines Snapshots for routine data exchanges Standard identifiers Use Web standards for person-to-computer exchanges Use EDI standards for computer-to-computer exchanges Use DSRC standards for vehicle-to-roadside exchanges Outline the steps for completing your state’s CVISN system design Establish the framework for completing your state’s CVISN system design

    4. 3/3/2012 6:20 PM Scope Page 3 - 4 NOTE that the components that support CVISN Level 1 functions are marked with a checkmark on this and the next few pages. NOTE that the components that support CVISN Level 1 functions are marked with a checkmark on this and the next few pages.

    5. 3/3/2012 6:20 PM Scope Page 3 - 5 The CVISN Architecture Flow Diagram depicts the CVO data flow among subsystems and between CVO subsystems and external entities. This diagram was used to coordinate with the National Architecture Team and to drive CVISN architecture refinement. The subsystems and equipment packages shown relate to the processes defined in the process architecture. The flows were used to derive requirements for standardized EDI and DSRC exchanges. Credential and Tax Administration processes are mapped to the Commercial Vehicle Administration Center Subsystem. Roadside Operations processes are mapped to the Commercial Vehicle Check Roadside Subsystem. Safety Assurance processes are split into the CV Safety Administration and Roadside Safety Inspection equipment packages. Vehicle Operation processes are mapped to the Commercial Vehicle Subsystem. Fleet Management Processes are mapped to the Fleet and Freight Management Center Subsystem. General ITS Functions are depicted through interactions with general ITS subsystems from each of the CVO-unique subsystems. Conventions used on the figure: Any subsystem that has unique requirements imposed by commercial vehicle operations is shown inside a shadowed box on the figures. Entities external to the ITS information systems are shown in ovals. In National Architecture terminology, these are “terminators.” Connections and data exchanges shown on the figures are marked with different line types to differentiate the means of communication used. The CVISN Architecture Flow Diagram depicts the CVO data flow among subsystems and between CVO subsystems and external entities. This diagram was used to coordinate with the National Architecture Team and to drive CVISN architecture refinement. The subsystems and equipment packages shown relate to the processes defined in the process architecture. The flows were used to derive requirements for standardized EDI and DSRC exchanges. Credential and Tax Administration processes are mapped to the Commercial Vehicle Administration Center Subsystem. Roadside Operations processes are mapped to the Commercial Vehicle Check Roadside Subsystem. Safety Assurance processes are split into the CV Safety Administration and Roadside Safety Inspection equipment packages. Vehicle Operation processes are mapped to the Commercial Vehicle Subsystem. Fleet Management Processes are mapped to the Fleet and Freight Management Center Subsystem. General ITS Functions are depicted through interactions with general ITS subsystems from each of the CVO-unique subsystems. Conventions used on the figure: Any subsystem that has unique requirements imposed by commercial vehicle operations is shown inside a shadowed box on the figures. Entities external to the ITS information systems are shown in ovals. In National Architecture terminology, these are “terminators.” Connections and data exchanges shown on the figures are marked with different line types to differentiate the means of communication used.

    6. 3/3/2012 6:20 PM Scope Page 3 - 6 CVISN Level 1 Deployment Summary CVISN is the collection of information systems and communications networks that provide support to commercial vehicle operations (CVO). The definition of CVISN Level 1 has been baselined to allow definition of a specific set of initial capabilities that can be deployed by a state and its motor carriers. In the future, additional capabilities may be added to CVISN. Interface standards either exist or are being developed to support CVISN Level 1 capabilities. TIME: 1 minute This slide defines what CVISN Level 1 is. The information is provided for reference. TIME: 1 minute This slide defines what CVISN Level 1 is. The information is provided for reference.

    7. 3/3/2012 6:20 PM Scope Page 3 - 7 A reminder - CVISN Level 1 An organizational framework for cooperative system development has been established among state agencies and motor carriers. A State CVISN System Design has been established that conforms to the CVISN Architecture & can evolve to include new technology & capabilities. All the elements of 3 capability areas (below) have been implemented using applicable architectural guidelines, operational concepts, & standards: Safety Information Exchange ASPEN (or equivalent) at all major inspection sites Connection to SAFER to provide exchange of interstate carrier and vehicle snapshots among states Implementation of CVIEW (or equivalent) system for exchange of intrastate snapshots within state and connection to SAFER for exchange of interstate snapshots Credentials Administration Automated processing (i.e., carrier application, state application processing, credential issuance, fuel tax filing) of at least IRP & IFTA credentials; ready to extend to other credentials (intrastate, titling, OS/OW, carrier registration, HazMat). Note: Processing does not necessarily include e-payment. Connection to IRP & IFTA Clearinghouses At least 10% of the transaction volume handled electronically; ready to bring on more carriers as carriers sign up; ready to extend to branch offices where applicable Electronic Screening Implemented at a minimum of one fixed or mobile inspection site Ready to replicate at other sites

    8. 3/3/2012 6:20 PM Scope Page 3 - 8 Cornerstone concepts in CVISN lay the groundwork for information exchanges (page 1 of 2) Exchange “snapshots” of carrier and vehicle safety and credentials information to improve CV safety and processes. Using standard snapshots simplifies the definition of new interfaces. Use primary identifiers in information exchanges for carriers, vehicles, transponders, drivers, international trips, & shipments so that different agencies/systems within the same state can find the records they need to share (and likewise across state boundaries).

    9. 3/3/2012 6:20 PM Scope Page 3 - 9 Cornerstone concepts in CVISN lay the groundwork for information exchanges (page 2 of 2) Use World Wide Web (WWW or Web) standards for person-to-computer interchanges so that private businesses can use any commercial browser to interact with a public agency Web site. Use standard electronic data interchange (EDI) transactions for computer-to-computer interchanges so that public agency systems and private businesses can exchange information using open standards, and so that the information can be processed by the computers. XML may prove to be a viable alternative for some EDI transactions. Use Dedicated Short Range Communications (DSRC) standard transponders, readers, and message sets so that a vehicle can take advantage of ITS services without changing equipment when traveling across many states.

    10. 3/3/2012 6:20 PM Scope Page 3 - 10 To support all three capability areas, snapshots are assembled & stored by SAFER and CVIEW to facilitate the exchange of safety & credentials information among systems. A snapshot is a collection of carrier, vehicle, and driver (future) information assembled from authoritative or indirect sources by CVIEW or SAFER. Snapshots reflect the state of those data when the information was provided to SAFER/CVIEW. SAFER assembles snapshots for interstate carriers and vehicles. The state CVIEW assembles snapshots for intrastate carriers, vehicles, and drivers. Snapshot data are stored in SAFER and CVIEW. A snapshot is a collection of carrier, vehicle, and driver (future) information assembled from authoritative or indirect sources by CVIEW or SAFER. Snapshots reflect the state of those data when the information was provided to SAFER/CVIEW. SAFER assembles snapshots for interstate carriers and vehicles. The state CVIEW assembles snapshots for intrastate carriers, vehicles, and drivers. Snapshot data are stored in SAFER and CVIEW.

    11. 3/3/2012 6:20 PM Scope Page 3 - 11 Primary Identifiers used for CVISN Level 1 make it possible to exchange information. For reference, more details are provided at the end of this session. Primary Carrier ID consists of ID Type (USDOT or state-specific) Jurisdiction Code, if intrastate Carrier-Specific ID Carrier/Terminal ID Vehicle IDs consist of VIN assigned by manufacturer or Vehicle Plate ID Country Code Jurisdiction Code License Plate ID Transponder ID - ID Definition Flag (current or after standards adopted), and Transponder Serial Number Driver Country Code Jurisdiction Code Driver-specific IDFor reference, more details are provided at the end of this session. Primary Carrier ID consists of ID Type (USDOT or state-specific) Jurisdiction Code, if intrastate Carrier-Specific ID Carrier/Terminal ID Vehicle IDs consist of VIN assigned by manufacturer or Vehicle Plate ID Country Code Jurisdiction Code License Plate ID Transponder ID - ID Definition Flag (current or after standards adopted), and Transponder Serial Number Driver Country Code Jurisdiction Code Driver-specific ID

    12. 3/3/2012 6:20 PM Scope Page 3 - 12 Primary Identifiers used for other functions make it possible to exchange information.

    13. 3/3/2012 6:20 PM Scope Page 3 - 13 The CVISN architecture connects subsystems via a combination of WWW, EDI and DSRC interface standards Architecture is a framework which lays out a blueprint for construction. The architecture defines the functions associated with ITS user services, the physical entities or subsystems within which such functions reside, the data interfaces and information flows between physical subsystems, and the communications requirements associated with information flows. The CVISN architecture is the ITS/CVO information systems and networks portion of the National ITS Architecture. The large boxes represent the four CVO subsytems of the National ITS Architecture. (The smaller boxes are subsytems that are not specifically CVO).Architecture is a framework which lays out a blueprint for construction. The architecture defines the functions associated with ITS user services, the physical entities or subsystems within which such functions reside, the data interfaces and information flows between physical subsystems, and the communications requirements associated with information flows. The CVISN architecture is the ITS/CVO information systems and networks portion of the National ITS Architecture. The large boxes represent the four CVO subsytems of the National ITS Architecture. (The smaller boxes are subsytems that are not specifically CVO).

    14. 3/3/2012 6:20 PM Scope Page 3 - 14 All EDI transactions should be acknowledged using TS 997. All credentialing activities use TS 286. For IFTA, TS 150, 151, 813, and 826 are also used. Inspection systems can use TS 284 and 824. Snapshots are exchanged using TS 285 and 824. All EDI transactions should be acknowledged using TS 997. All credentialing activities use TS 286. For IFTA, TS 150, 151, 813, and 826 are also used. Inspection systems can use TS 284 and 824. Snapshots are exchanged using TS 285 and 824.

    15. 3/3/2012 6:20 PM Scope Page 3 - 15 DSRC standards define how commercial vehicles and roadside readers should communicate. IEEE 1455-1999, ...a standard for exchanging vehicle/roadside information, providing for bi-directional wireless message transmission and device control compatible with but independent of the ASTM efforts. ASTM ver 7 ASTM PS 105-99, Standard Specification for DSRC - Data Link Layer, ...Specification for the protocol (data link) communications. Supports both synchronous and asynchronous modes for operations. ASTM PS 111-98, Standard Specification for Dedicated Short Range Communications (DSRC) -Physical Layer, ...Specification for the RF characteristics (physical layer) for DSRC operating in the range of 902-928 MHz. Supports both active and backscatter transponders. ASTM ver 6 ASTM Standard for Dedicated, Short Range, Two-Way Vehicle to Roadside Communications Equipment, Draft 6, 23 February 1996. Recall the layers of the Open Systems Interconnection Model: IEEE standard covers layer 7 and the interaction with layer 2 ASTM PS 111-98 covers layer 1 ASTM PS 105-99 draft covers layer 2 ASTM ver 6 covers layers 1, 2, and 7Recall the layers of the Open Systems Interconnection Model: IEEE standard covers layer 7 and the interaction with layer 2 ASTM PS 111-98 covers layer 1 ASTM PS 105-99 draft covers layer 2 ASTM ver 6 covers layers 1, 2, and 7

    16. 3/3/2012 6:20 PM Scope Page 3 - 16 States are encouraged to implement CVISN Level 1 capabilities incrementally in a series of steps using a structured process. TIME: 1 minute The first workshop (Scope Workshop) is intended to help states develop a preliminary top-level system design. States are encouraged to implement CVISN Level 1 capabilities incrementally in a series of steps using a structured process. A phase is a period of time defined for planning purposes to allow incremental delivery of a complex system. “Phase n” refers to multiple phases, each 3-6 months long. The first phase is devoted to system design and program/project planning. Each subsequent phase focuses on delivering a coordinated set of product versions (a.k.a. releases) that incrementally build to the overall CVISN Level 1 capability. For each phase, states are encouraged to update the Program Plan and System Integration Schedule. In this Scope workshop, we focus on step 1A - developing a top-level design. TIME: 1 minute The first workshop (Scope Workshop) is intended to help states develop a preliminary top-level system design. States are encouraged to implement CVISN Level 1 capabilities incrementally in a series of steps using a structured process. A phase is a period of time defined for planning purposes to allow incremental delivery of a complex system. “Phase n” refers to multiple phases, each 3-6 months long. The first phase is devoted to system design and program/project planning. Each subsequent phase focuses on delivering a coordinated set of product versions (a.k.a. releases) that incrementally build to the overall CVISN Level 1 capability. For each phase, states are encouraged to update the Program Plan and System Integration Schedule. In this Scope workshop, we focus on step 1A - developing a top-level design.

    17. 3/3/2012 6:20 PM Scope Page 3 - 17 The CVISN implementation process as presented in the workshops The first phase (1A, 1B, 1C) is devoted to system design and program & project planning. The first 2 workshops are related to this phase. Each subsequent phase focuses on delivering a coordinated set of product versions (a.k.a. releases) that incrementally build to the overall CVISN Level 1 capability. For each phase, states are encouraged to update the Program Plan, State CVISN System Design, and System Integration Schedule.

    18. 3/3/2012 6:20 PM Scope Page 3 - 18 Each state develops a top-level design by adding CVISN capabilities to existing systems (Phase 1A) Use this as an overhead transparency, pointing to it as you move through the description of each step. Walk through the details of the process for Phase 1A, using the explanatory text on the next several pages. Even though the steps are shown as sequential, the process actually involves a great deal of feedback and iteration. Throughout the process, identify issues, actions and decisions. Publish the final results as a State CVISN Design Description. Use this as an overhead transparency, pointing to it as you move through the description of each step. Walk through the details of the process for Phase 1A, using the explanatory text on the next several pages. Even though the steps are shown as sequential, the process actually involves a great deal of feedback and iteration. Throughout the process, identify issues, actions and decisions. Publish the final results as a State CVISN Design Description.

    19. 3/3/2012 6:20 PM Scope Page 3 - 19 Steps in the Top-Level Design Process 1. Characterize your current system design. (Pre-Work B; C; D; E) 2. Identify where your current and planned operational concepts and design are and are not compatible with CVISN. (Pre-Work A, COACH Part 1; F) 3. Make a proposed master state system design template. Include all the systems in your state that support CVO. Start by reviewing the generic template and tailoring it to your state. (Pre-Work G) Make a proposed master network design template. Include all the computers and networks that support the systems on your system design template. Start with the state system design template, and review the generic network template, tailoring them to your state. (Pre-Work H)

    20. 3/3/2012 6:20 PM Scope Page 3 - 20 Steps in the Top-Level Design Process Think about the key operational scenarios you want to affect during the CVISN program. See Chapter 5 in the CVISN Guide to Top-Level Design, for a list of Level 1 scenarios. Identify threads of activity corresponding to those operations. Use the COACH (CVISN Architecture and Operational Compatibility Handbook) checklists as reminders of what your state intends to do. Use a copy of your state’s CVISN system design template to illustrate what systems will interact to support the operational scenario. We call this drawing a “functional thread diagram.” (Workshop sessions 5, 6, 8). Keep the scenario steps at about the same level of detail as in the examples you’ll see in sessions 5, 6, and 8. Each step should “name” the information being exchanged and what format (e.g., EDI TS 286) will be used for the exchange. Also describe, at a high level, the processing performed. Keep the scenario steps at about the same level of detail as in the examples you’ll see in sessions 5, 6, and 8. Each step should “name” the information being exchanged and what format (e.g., EDI TS 286) will be used for the exchange. Also describe, at a high level, the processing performed.

    21. 3/3/2012 6:20 PM Scope Page 3 - 21 Steps in the Top-Level Design Process Example of Functional Thread Diagram to Depict Operational Scenario

    22. 3/3/2012 6:20 PM Scope Page 3 - 22 Steps in the Top-Level Design Process 5a. Summarize system interactions using three copies of your state system design template, one for “Carrier-Related Interfaces”, another for “Interfaces within the State”, and a third “State Interfaces with CVISN Core Infrastructure.” On each of these system design interface summary drawings, indicate whether legacy system interfaces (LSIs) or legacy modifications (LMs) will be required for the functions being supported. 5b. Reflect the operational scenarios on your network template. Show which computers will connect, and what networks and protocols will support those connections. (Workshop Sessions 5, 6, 8, 10)

    23. 3/3/2012 6:20 PM Scope Page 3 - 23 Steps in the Top-Level Design Process 6. Identify the scope of the system changes/additions needed to become (more) compatible with CVISN to support the operational scenario. Consider issues such as connectivity, interfaces, system capacity, data compatibility, process/policy changes, institutional barriers, etc. (Workshop Sessions 5, 6, 8, 10)

    24. 3/3/2012 6:20 PM Scope Page 3 - 24 Breakout Goals Establish the framework for assessing the scope of the CVISN Program in your state Start the lists you’ll keep building throughout the workshop Review/Create the Proposed CVISN System Design template and Network Template for your state. These will also be used throughout the workshop.

    25. 3/3/2012 6:20 PM Scope Page 3 - 25 What inputs are needed? What outputs are created? Inputs: All Pre-Work Blank tables Sample templates Outputs: Action Plan Decision Table State System Change Summary State Proposed CVISN System Design template State Proposed Network Template

    26. 3/3/2012 6:20 PM Scope Page 3 - 26 Breakout Plan 90 minutes Step 1. ~5 min. Assign roles and make sure that all decisions, actions, and system change highlights will be recorded in your Action Plan, Decision Table, and State System Change Summary. Decide who will maintain the master State CVISN System Design template throughout the workshop. Decide who will update the Network template to show the emerging Top-Level Physical System Design throughout the workshop. Step 2. Review/complete the Pre-Work. Don’t let indecision slow you down too much. A. ~5 min. Review Pre-Work Status Summary. Verify that everyone has all Pre-Work. Deal with any outstanding questions or issues. B. ~20 min. Review the COACH checklists, highlighting where the state is not committed to CVISN Level 1 items. Summarize your goals and objectives, comparing them to the CVISN Level 1 high-level description on page 3-7.

    27. 3/3/2012 6:20 PM Scope Page 3 - 27 Breakout Plan 90 minutes Step 2. Review/complete the Pre-Work. (continued) C. ~30 min. Review the Current Systems State System Design template and Network template. Review the Proposed CVISN System templates. If you know you need to add a system, add it. If you know you need to change one, include a “legacy modification” (LM) box. If you think you need to build a new interface to connect with a legacy system, include a “legacy system interface” (LSI) box. If you aren’t sure, record an action. If you make decisions about what to change/not change, record a decision. D. ~15 min. Review the Keys/Identifiers Used in Your Databases against the recommended standard identifiers (please see pages 3-49 through 3-51 for details). Note any potential problems. Step 3. ~ 5 min. Update the State System Change Summary by entering every state system you wound up with on the Proposed State CVISN System Design template. For step 2C, show the Generic State System Design Template and instructions for completing (pages 43-44). Then show the Generic Network Template and instructions for completing (pages 45-46). Explain step 2D. The idea for the primary identifiers is that they will be used in all standard information exchanges. Do all the state systems that need to exchange information currently have the primary identifier information? In a form that is translatable to the format shown? If not, is there some work-around? Explain step 3. Show the Generic State System Design Template (page 43) and the State System Change Summary (page 35).For step 2C, show the Generic State System Design Template and instructions for completing (pages 43-44). Then show the Generic Network Template and instructions for completing (pages 45-46). Explain step 2D. The idea for the primary identifiers is that they will be used in all standard information exchanges. Do all the state systems that need to exchange information currently have the primary identifier information? In a form that is translatable to the format shown? If not, is there some work-around? Explain step 3. Show the Generic State System Design Template (page 43) and the State System Change Summary (page 35).

    28. 3/3/2012 6:20 PM Scope Page 3 - 28 Breakout Plan 90 minutes Step 4. ~10 min. Make copies (at least 5 of each; transparencies, pages in a file, or hardcopies, whichever you think you will use) of your templates for use in later sessions. Record issues or questions about CVISN Level 1, the workshop process, or the templates for discussion in the main session. Get ready to present your results to the main group. A sample presentation outline is shown on page 3-47 (and in the template file for this session, given to the Facilitator on Day 0). Plan on ~10 minutes to report. Assemble the material for the presentation. If you do it electronically, copy the file onto a floppy disk and take it with you to the main meeting room. Otherwise, make transparencies. If necessary, carry flip chart pages with you to the main meeting room for reference. If you have time, make a copy for each member of your team and for the master book. For step 4, refer them to page 47 for the sample presentation outline.For step 4, refer them to page 47 for the sample presentation outline.

    29. 3/3/2012 6:20 PM Scope Page 3 - 29 Team Roles Facilitator _________________________ Presenter _________________________ Scribe _________________________ Time Keeper _________________________ CSA _________________________ Change the roles for each breakout session (except facilitator and CSA)

    30. 3/3/2012 6:20 PM Scope Page 3 - 30 Action Plan Worksheet State _________________, Page __ of __

    31. 3/3/2012 6:20 PM Scope Page 3 - 31 Action Plan Worksheet State _________________, Page __ of __

    32. 3/3/2012 6:20 PM Scope Page 3 - 32 Key to Action Plan Table’s Columns (tailor to suit you, if needed) No. = sequential number to keep track of actions Type = interface issue (I), operating procedure issue (OP), policy issue (PO), system capacity/design issue (S) System = name of the system in your state that the question is related to Question/Status = statement of the issue or question to be addressed; may turn into the answer when the issue is closed Due = specific date, or schedule milestone Assigned to = who (specific person’s name, if possible) the action is assigned to

    33. 3/3/2012 6:20 PM Scope Page 3 - 33 Decision Table State _________________, Page __ of __

    34. 3/3/2012 6:20 PM Scope Page 3 - 34 Decision Table State _________________, Page __ of __

    35. 3/3/2012 6:20 PM Scope Page 3 - 35 State System Change Summary State _________________, Page __ of __

    36. 3/3/2012 6:20 PM Scope Page 3 - 36 State System Change Summary State _________________, Page __ of __

    37. 3/3/2012 6:20 PM Scope Page 3 - 37 State System Change Summary State _________________, Page __ of __

    38. 3/3/2012 6:20 PM Scope Page 3 - 38 State System Change Summary State _________________, Page __ of __

    39. 3/3/2012 6:20 PM Scope Page 3 - 39 Issues/Questions about CVISN Level 1, the workshop process, the templates, . . .

    40. 3/3/2012 6:20 PM Scope Page 3 - 40 Pre-Work Status Summary (partial)

    41. 3/3/2012 6:20 PM Scope Page 3 - 41 State CVISN Goals and Objectives

    42. 3/3/2012 6:20 PM Scope Page 3 - 42 State CVISN Goals and Objectives (Continued)

    43. 3/3/2012 6:20 PM Scope Page 3 - 43 Generic State System Design Template

    44. 3/3/2012 6:20 PM Scope Page 3 - 44 State System Design Template - Instructions The state system design template will be used to illustrate operational scenarios. This diagram is the one that the CVISN Model Deployment states found most useful for team communications. Everyone can see his or her own functional area on this diagram. The template can be used in many different ways, as you learned in the Understanding ITS/CVO Technology Applications course. In the Scope workshop, you’ll use this template for illustrating both operational scenarios and system interfaces. Make one diagram for your Current State System Design, and another for your Proposed State System Design. Include all the major functions in your state that support CVO. There should be exactly one box representing each major function. Start by reviewing the generic template, then tailor it to your state. Recall your program objectives, and the answers you gave when completing the COACH Part 1 tables. Remove functions that don’t relate to your CVISN program. Add a box for each major function that is missing. The generic state system design template reflects the generic CVISN state design. The CVISN System Design Description explains more about the generic design. The small LSI and LM boxes on the generic state system design template refer to Legacy System Interfaces and Legacy Modifications. The state chooses whether to modify the legacy system (LM - legacy modification) to support EDI (and other new functions and interfaces), or to create a Legacy System Interface (LSI) to deal with the EDI-to-native form interface. Many CVISN Model Deployment states are implementing a mix of LSIs and LMs. In this template, it is not important to group the functions that are handled within the same computer, nor to show how systems are connected through networks

    45. 3/3/2012 6:20 PM Scope Page 3 - 45 Generic Network Template

    46. 3/3/2012 6:20 PM Scope Page 3 - 46 Network Template - Instructions The network template shows how your state allocates the major functions to computers, and how those computers are connected using various kinds of network technologies. Make one diagram for your Current Network configuration, and another for your Proposed Network configuration. To make your master network template, review the generic network template. Tailor the generic network template to your state. Start by including all the computers and networks that support the systems you included in your current systems inventory. Next, be sure that the existing major functions on your system design template are allocated to some computer on the network and design template. As necessary, add computers and network components. If you don’t know what kind of computer or what networking technology you’ll use, put in a placeholder. The drawing will mature as you work through the design process. This template is used to show network connections, as well as the allocation of software products to computers. Proposed new computers and network connections can be added. As you make decisions, show which network protocols you’ve selected for each segment. The diagram can be used to verify how two or more systems are connected physically, and where network “translations” are needed. It can also show where potential bottlenecks exist. On the network template, each small box represents a computer system. The state should show all the computer systems that support (or will support) the CVISN program functions. List the major functions (software applications) handled by that computer inside the box. Group the small boxes into large boxes according to the state agency or facility that is responsible for the computers. Show LANs and WANs as lines connecting the computers. We recommend that you adopt some convention for distinguishing between existing and proposed computers and connections. For instance, you might make existing computers white, and new ones shaded. You might show existing connections as solid lines and new ones as dashed. Different dashed line types can be used to indicate different network protocols, if you like. Every function box on your state system design template should be allocated to some computer on this template. This includes each of the individual LSI boxes. Often for credentials-related products, the LSIs are small applications running on the same computer as the Credentialing Interface. LMs are modifications to existing systems, and usually are not shown as separately allocated functions on the network template.

    47. 3/3/2012 6:20 PM Scope Page 3 - 47 Sample Presentation Characterize current state design Current State System Design Template Current State Network Template Brief verbal description Summarize CVISN program goals Preliminary proposed state design Proposed State System Design Template Proposed State Network Template Brief verbal description If you have recorded actions, decisions, and information about system changes, then present the initial Action Plan, Decision Table, State System Change Summary Issues or questions

    48. 3/3/2012 6:20 PM Scope Page 3 - 48

    49. 3/3/2012 6:20 PM Scope Page 3 - 49

    50. 3/3/2012 6:20 PM Scope Page 3 - 50

    51. 3/3/2012 6:20 PM Scope Page 3 - 51

    52. 3/3/2012 6:20 PM Scope Page 3 - 52

More Related