Docstoc

NTI Group

Document Sample
NTI Group Powered By Docstoc
					Emergency Notification System (ENS)
  Banner Interface Specification




           Daniel Nichols
            12/11/2007
Overview ............................................................................................................................. 3
Existing ENS Interface ....................................................................................................... 3
Interim Solution .................................................................................................................. 4
Banner Interface .................................................................................................................. 5
   Interface Category:.......................................................................................................... 7
   Direction: ........................................................................................................................ 7
   Related Module(s):.......................................................................................................... 7
   Frequency:....................................................................................................................... 7
   Data Structure: ................................................................................................................ 8
   Extract Rules: .................................................................................................................. 8
Installation........................................................................................................................... 9
Appendix ............................................................................................................................. 9
   Banner to ENS: Transmission Shell Script ................................................................... 10
Overview
Blackboard Connect Inc is a vendor that provides USD with emergency notification
services via their Connect-ED product. USD uses this product to build and maintain an
Emergency Notification System (ENS) that can be used in the event of a campus
emergency. Via this system, appropriate personnel can define messages on the ENS
website for broadcast to all USD students and staff. We periodically send a data file to
the ENS with contact information (phone number, email address, SMS text message
address, etc.) for all USD students and staff. This data is used by ENS to support the
broadcast capability.

Currently, the ENS data file is created via data extracts from Oracle HR (for employee
data), Legacy SIS (for student data) and Luminis (for cell phone data). With the
implementation of Banner, the source of these extracts will have to change.

Existing ENS Interface
The existing ENS interface data flow is as follows:

                                                          Luminis
   Legacy SIS                Oracle HR
                                                        (LUMAPPS)




                           Employee Data
                                                      Cell Phone Data
  Student Data                                         Students and
                                                        Employees




                                IAM




                             ENS Extract




      Student related contact data is extracted from the Legacy SIS system and
       imported into IAM.
      Employee related contact data is extracted from Oracle HR and imported into
       IAM.
      Cell phone (number, provider and SMS text address) data is extracted from
       Luminis (LUMAPPS) and imported into IAM.
      Once in IAM, a consolidated view is used to extract the data in the format that
       ENS needs.

Interim Solution
Currently, the data feed to ENS is run manually. This presents an unacceptable risk in
that only the parties directly involved with the process are aware of, and familiar with the
steps necessary to produce and transmit the file.

Therefore, an interim version of the ENS process will be automated to ensure a regular
refresh of contact data uENSl the Banner process can be built. This interim version will
be structured as follows:

Oracle HR
A weekly job will be schedule to extract the HR data The job runs the procedure
“usd_hr_nti_extract” and produces the HR extract file “usd_hr_nti_data.dat” in the
dirtectory “/dts_dump/legcyInter/IAM”.

Luminis Prod
A weekly job will be schedule to extract the Luminis data The job runs the procedure
“usd_luminis_celldata_extract” and produces the HR extract file
“usd_luminis_celldata.dat” in the dirtectory “/dts_dump/legcyInter/IAM”.

Legacy SIS
A weekly job will be schedule to extract the Legacy SIS data and produce the Legacy
extract file. The file name will be “usd_legacy_nti_data.dat” and will be written to
/dts_dump/legcyInter/IAM.

IAM
In the IAM database, three external files have been defined against the three extract files
defined above.
The Oracle table names are:
     usd_nti_luminis_celldata
     usd_hr_nti_data
     usd_legacy_nti_data

As external tables, they are read-only in Oracle and their data is refreshed anytime the flat
file is updated.

A stored procedure, “usd_nti_group_extract” is defined in IAM and scheduled to run
weekly. This procedure produces the file, “usd_contact_info.txt” and is the file that is to
be transmitted to the vendor.

A record count is compared against a threshold (currently set to plus or minus 5%) to
ensure that a glitch in the process doesn’t result in a clearing of our data file at ENS. If
the record count is within the threshold, the process continues, otherwise the process is
halted and an email is set to the administrator informing them of the issue.

Connect-ED provided a shell script for the automatic transmission of the data file. See the
Appendix.


Banner Interface
Once the Banner implementation is complete, student related demographic data that was
originally fed from the Legacy SIS system will be fed from the Banner General Person
tables. The proposed Banner/ENS interface data flow is as follows:


    Banner
                                                        Luminis
    Student                  Oracle HR
                                                      (LUMAPPS)
    System




                           Employee Data




                                                     Cell Phone Data
  Student Data                                   Students and Employees

                                IAM




                            ENS Extract




While the data flow diagram looks similar to the existing process, internal processing will
be more streamlined.

As all systems after the Banner conversion will be Oracle based, there will be no need to
create an interim extract step prior to the feed to IAM. We will leverage Oracle objects
and features (materialized views, database links, etc) so as to make the process easier and
more straight forward.

All Banner General Person records have an associated SPRIDEN_ID which serves as a
unique key value. The same SPRIDEN_ID will be assumed to exist in Oracle HR, and in
IAM so that a cross-link of the data can be made. The data in Luminis is keyed off of the
GUID (a unique string that equates to username). The IAM system also has the guid
which provides the Luminis cross link.
Interface Category:
The ENS interface will likely be in the category of Static / Evolving. Initially, the
program will be static. The ENS process is still being defined. Currently, it is a largely
manual process. As the process becomes more refined, this interface will likely have to
me modified.

Interfaces created for the Banner project will fall into one of the following categories:
   Category                                        Definition
Unnecessary        We may determine that some existing interfaces are no longer needed.
                   The business processes they support and/or modules they exchange
                   data between may not be required any more.
Static             These are interfaces that will be modified and/or converted and then
                   remain without change or retirement. Most likely data exchanges
                   between student systems and other “permanent” non-Banner systems.
                   (ex: R25, DARS, etc.)
Temporary         These are interfaces that will be modified and/or converted, but will
                  only be necessary until some subsequent Banner module(s) are
                  implemented. At that point, the data will all be internal to the Banner
                  system and thus the interface will not be needed.

New               As the Banner application is implemented, new business processes will
                  be established. These new business processes will create the need to
                  communicate between system where there was no need and/or no
                  capability to do so before. This will require the creation of new
                  interfaces.
Evolving          These may be “Static”, “Temporary” and/or “New”. They are unique in
                  that they will change multiple times (evolve) as the Banner project
                  progresses.


Direction:
The ENS interface will extract data from the Banner, Oracle HR and Luminis and add
data to the IAMPROD system. The direction is, FROM: Banner, TO: IAM


Related Module(s):
The data that this interface deals with is General person data. The events in Banner that
will require new data to be transmitted to IAM will occur in the Admissions module.


Frequency:
The individual data feeds (Oracle HR, Luminis, Legacy and Banner) will run daily. The
transmission to ENS will run weekly.
Data Structure:
The data file sent to the ENS is an ASCII flat, comma delimited file. The data elements in
the file are as follows:
          Column                        Description
REFERENCE_CODE              SPRIDEN_ID
FIRST_NAME                  Person First name
LAST_NAME                   Person last name
STATUS                      Student program (if Any)
                                 Undergraduate
                                 Graduate
                                 Law
LANGUAGE                    Primary Language
GROUP1                      HR Group 1
GROUP2                      HR Group2
CONTACT_TYPE                Person Type
                                 Staff
                                 Faculty
                                 Student
HOME_PHONE                  Home Phone Number
WORK_PHONE                  Work Phone Number
MOBILE_PHONE                Cell Phone Number
HOME_PHONE_ALT              Alternate Home Phone Number
MOBILE_PHONE_ALT Cell Phone Alternate
PRIMARY_PHONE               Primary Phone Number
EMAIL_ADDRESS               Email Address
SMS_ADDRESS                 SMS Text Address


Extract Rules:
      Oracle HR: Pull data for all employees that are not terminated
      Banner: Pull data for all students that are registered for at least one class in the
       current term or higher.
Installation
The ENS interface process is a production system. The Banner interface will replace one
of the existing components. As such, the remaining parts of the production process will
be left as is.

The installation steps described will be only those necessary to implement the Banner
replacement component.

   1. Log in to the Banner Production database as user BANINST1.
   2. Create the Oracle directory BANNER_DTS_ENS by running the following SQL
      command:
       CREATE OR REPLACE DIRECTORY BANNER_DTS_ENS AS '/dts_dump/legcyInter/IAM/ENS'
   3. Compile the package and body: usd_banner_nti_extract
   4. The package contains the public procedure: extract_data. Schedule to run once per
      day.
   5. Contact Bob Purcell in the VAX Cobol group and ask that he stop the VAX
      extract of ENS data.

The remaining components of the ENS process will run as before. This entire process
may be reviewed at a later date to create a single data feed from banner.


Appendix
The overall process for the ENS extract is as follows:
   1. A daily extract job runs in Oracle HR (usd_hr_nti_extract) to extract current
      employees. The file (usd_hr_nti_data.dat) is written to the share drive
      /dts_dump/legcyInter/IAM/NTI
   2. A daily extract job runs in Luminis (usd_luminis_celldata_extract) to extract cell
      phone data. The file (usd_luminis_celldata.dat) is written to the share drive
      /dts_dump/legcyInter/IAM/NTI
   3. A daily extract job runs on Legacy (COBOL based) to extract current students.
      The file (usd_legacy_nti_data.dat) is written to the share drive
      /dts_dump/legcyInter/IAM/NTI

       *** Once Banner Registration is implemented, the student data component of this
       process will be changed to pull data from Banner. Instead of a COBOL program,
       a stored procedure (usd_banner_nti_extract) will be used. The file
       (usd_banner_nti_data.dat) will be written to the share drive
       /dts_dump/legcyInter/IAM/ENS

   4. A weekly job runs in the IAM system (usd_nti_group_extract) to consolidate the
      above data file, format them appropriately and transmit the resulting combination
      file to ENS. The record count for the ENS extract is compared to the previous run.
      If the record count is within a 5% plus or minus threshold, the resulting data file is
      transmitted to ENS using the send.sh shell script.
Banner to ENS: Transmission Shell Script
/usr/bin/curl -L -A "Autoscript (.sh)" -F fNTIUser=xxxxxxx -F
fNTIPass=yyyyyyy -F fContactType=All -F fRefreshType="Student,Staff" -F
fPreserveData=0 -F fSubmit=1 -F
fFile=@/dts_dump/legcyInter/IAM/NTI/usd_contact_info.txt
https://www.nticonnected.com/contacts/importer.asp -o
"/dts_dump/legcyInter/IAM/NTI/NTI_XMIT_output.txt"

Where xxxxxxx = the USD User name and yyyyyy = the USD password
Appendix

USD Custom Interface Objects
The following USD custom objects make up the Banner / ENS Interface
              Object Name                       Owner                   Type
LUM_DTS_ENS                                Luminis Production         Directory
                                                 SYS
USD_LUMINIS_CELLDATA_EXTRACT Luminis Production                       Procedure
                                              LUMAPPS
USD_EMERGENCY_CONTACT                      Luminis Production           Table
                                              LUMAPPS
USD_ENS_GROUP_EXT                           IAM Production             Package
                                                xx_ecp
USD_ENS_LUMINIS_CELLDATA                    IAM Production          External Table
                                                xx_ecp

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:9/16/2011
language:Swedish
pages:11