EXHIBIT 3-D Core System Integration Plan Template by cometjunkie43

VIEWS: 9 PAGES: 11

									                  Fairfax County Government / Fairfax County Public Schools RFP
                         System Implementation Services for SAP Software




                              EXHIBIT 3-D
                  Core System Integration Plan Template




RFP10-125118-10                                                                   Exhibit 3-D - 1
 Fairfax County Government
Fairfax County Public Schools




  Core System Integration Plan v 1

              Drafted by
               XXXXX



                        
                        
                        
                        
        12000 Government Center Pkwy 
              Fairfax, VA 22035 




                   Date




                                        2
                                                          TABLE OF CONTENTS

1.      INTRODUCTION...................................................................................................... 4

2.      CORE PRODUCTS.................................................................................................. 5
2.1.             Core System ..............................................................................................................................................5

2.2.             Product 1 ...................................................................................................................................................5

2.3.             Product 2 ...................................................................................................................................................5

2.4.             Product 3 ...................................................................................................................................................5


3.      INTERFACES .......................................................................................................... 6

4.      HIGH LEVEL DATA FLOWS................................................................................... 7

5.      INTEGRATION TIME LINE...................................................................................... 8

6.      KEY INTEGRATION POINTS.................................................................................. 9
6.1.        Data Flow 1 ...............................................................................................................................................9
   6.1.1.      High Level Mapping of Data Elements involved in this Data Flow ..............................................9
   6.1.2.      Process Flows .....................................................................................................................................9
      6.1.2.1.   Create Record....................................................................................................................................9
      6.1.2.2.   Read Record.....................................................................................................................................9
      6.1.2.3.   Update Record ..................................................................................................................................9
      6.1.2.4.   Delete Record....................................................................................................................................9

6.2.        Data Flow 2 .............................................................................................................................................10
   6.2.1.      High Level Mapping of Data Elements involved in this Data Flow ............................................10
   6.2.2.      Process Flows ...................................................................................................................................11
      6.2.2.1.   Create Record..................................................................................................................................11
      6.2.2.2.   Read Record...................................................................................................................................11
      6.2.2.3.   Update Record ................................................................................................................................11
      6.2.2.4.   Delete Record..................................................................................................................................11

6.3.             Repeat Section 6.1 Format for each Data Flow....................................................................................11




                                                                                                                                                                      3
1. INTRODUCTION

 The County is procuring various systems and subsystems from Vendor 1, Vendor2, and Vendor 3, to
 meet the strategic and operational needs of the County. As a part of the procurement process a
 series of workshops entitled ‘The Fit and Gap Process’ were held. As a part of the Fit and Gap
 process the County outlined its vision of an integrated system that meets the County’s short term and
 long term goals. The following list describes at a high level the business objectives of this integration
 effort:
      a) Build an integrated solution that meets the strategic, tactical and operational needs of the
         County.
      b) Build the solution using best of breed COTS solutions and standard interfaces to enable the
         County to evolve and upgrade to newer features and functionality.
      c) Provide tools and applications to field personnel to improve operational effectiveness and
         tactical efficiency.
      d) Provide tools and data to County management to meet strategic goal of continuous
         operational improvement.
      e) Use a single system for entering and updating personnel and roster information and update
         other systems as required
      f) Implement systems in a manner that will allow the County to evolve the operations and
         business practices with minimal impact and rework.


 This document identifies the vendors, systems, sub systems, interfaces and data flows along with the
 implementation timeline needed to achieve those goals.




                                                                                                     4
2. CORE PRODUCTS
 Several core products are to be implemented in support of the County’s stated goals. They include:


 2.1.        Core System
             Brief Description of Product Functionality


 2.2.        Product 1
             Brief Description of Product Functionality


 2.3.        Product 2
             Brief Description of Product Functionality


 2.4.        Product 3
             Brief Description of Product Functionality




 Although each of these components provides unique functionality, these sub-systems will share
 common data elements. This Document and the Interface Control Documents will identify which
 application will be used to resolve duplicate data entry and which will be the System of Record.




                                                                                                    5
3. INTERFACES

    All integration that is proposed within this vision is being accomplished with various interfaces. The
    interfaces are identified below. The final interface configurations have not been determined at this
    time. All interfaces will be further identified within an Interface Control Document (ICD). Each ICD
    will require additional information gathering from Fairfax. Information including, but not limited to
    connection type, bidirectional vs. unidirectional, field mapping and error reporting will be clearly
    identified within each ICD. Every ICD will require the review and signed approval of Fairfax prior to
    any work starting on the interface. The diagram below represents a typical interface approval,
    development, testing and go-live process.


       <Insert ICD Approval Process here>




The following interfaces are within the scope of this integration and are being provided as a deliverable by
the vendor.




       < Insert official list of interfaces here>




                                                                                                      6
4. HIGH LEVEL DATA FLOWS
   The following schematic depicts the envisioned integration points and data flows between the four
   core products being integrated under this plan. Points of integration at the data level include: core
   personnel data, roster data, event and unit data, vehicle and equipment data and personnel skills
   data.




Interface Name                     Description                          Maps to Data Flow




                                                                                                     7
5. INTEGRATION TIME LINE

  The timeline below shows the desired sequential delivery of the core products and key integration
  points.




  The County’s solution requirements as documented in the County’s RFP describe the full expected
  functionality that will result from the Integration of these systems. In addition to this Integration Plan,
  Interface Control Documents (ICD) and Acceptance Test Plans (ATP) will be created for integration of
  these systems. The ICDs will focus on the design aspects defining what will be built and how it will
  work (i.e., frequency of data transmission); where applicable optional approaches will be provided.
  The ICD will also “map” the function(s) to its respective requirement(s) and map the associated data
  flows. The baseline Acceptance Test Plan will provide a “checklist” of every function available for the
  respective application.

  The County’s Integration effort will proceed accordingly with timelines listed above. It will be broken
  down into the following phases:

      1. Phase 1: Briefly describe Phase

      2. Phase 2: Briefly describe Phase

      3. Phase 3: Briefly describe Phase

      4. Phase 4: Briefly describe Phase




                                                                                                       8
6.   KEY INTEGRATION POINTS

     6.1.   Data Flow 1
            6.1.1.High Level Mapping of Data Elements involved in this Data Flow



            High Level Description of the Data Flow 1

                          Existing System                     Product 1                  Data Example


               tblEmployment.EmployeeIDNumber   RscMaster_EmployeeID_Ch(per02)               47438

               tblMainIdentity.FN               RscMaster_FName_Ch(per02)                    Buster

               tblMainIdentity.MI               RscMaster_MName_Ch(per02)                      P

               tblMainIdentity.LN               RscMaster_LName_Ch(per02)                    Brown

               tblMainIdentity.City             RscMaster_City_Vc(per02)                   Sharpsburg

               tblMainIdentity.State            RscMaster_State_Ch(per02)                     MD




            6.1.2.Process Flows

            In order to harmonize data, the County wants to define standardized processes for creating,
            deleting and updating data. The following processes have been defined.

                6.1.2.1. Create Record
                     < Insert Swim Lane Diagram Here>

                6.1.2.2. Read Record
                     < Insert Swim Lane Diagram Here>

                6.1.2.3. Update Record

                     < Insert Swim Lane Diagram Here>

                6.1.2.4. Delete Record




                                                                                                          9
                 Sample “To Be” Swim Lane




             It is the responsibility of the Integrator to provide a comprehensive ICD for each
             Interface/Data Flow.




6.2.         Data Flow 2


   6.2.1.High Level Mapping of Data Elements involved in this Data Flow



   High Level Description of the Data Flow 2

                 Existing System                     Product 1                Data Example


       tblEmployment.EmployeeIDNumber   RscMaster_EmployeeID_Ch(per02)            47438

       tblMainIdentity.FN               RscMaster_FName_Ch(per02)                 Buster




                                                                                             10
       tblMainIdentity.MI              RscMaster_MName_Ch(per02)                      P

       tblMainIdentity.LN              RscMaster_LName_Ch(per02)                    Brown

       tblMainIdentity.City            RscMaster_City_Vc(per02)                   Sharpsburg

       tblMainIdentity.State           RscMaster_State_Ch(per02)                     MD




   6.2.2.Process Flows

   In order to harmonize data, the County wants to define standardized processes for creating,
   deleting and updating data. The following processes have been defined.

        6.2.2.1. Create Record
             < Insert Swim Lane Diagram Here>

        6.2.2.2. Read Record
             < Insert Swim Lane Diagram Here>

        6.2.2.3. Update Record

             < Insert Swim Lane Diagram Here>

        6.2.2.4. Delete Record




6.3.         Repeat Section 6.1 Format for each Data Flow




                                                                                               11

								
To top