Msword Template Invoice by anj60002

VIEWS: 66 PAGES: 449

More Info
									ID     Plan      Actual                             Milestone                                 Pre- PM FI AD HR RG AM RL FA IT LP DS DW TR
                        When Executive Sponsor Team agreed to commit to
1    1-Jun-05 1-Jun-05 advancing the Enterprise Resource Planning (ERP)                                 Legend:
                        Implentation Project to replace Datatel and other systems                       ID - a number assigned sequentially to
                        When our Project Organization, staffing and logistics are                       each milestone
2    7-Jul-05  7-Jul-05                                                                            x    Pre- Indicates a pre-requisite milestone
                        finalized and agreed by EST/SC
                        When Project Scope - - mission, objectives, processes and                       The remaining headings represent roles
                                                                                                        from the Project Organization.
3    3-Aug-05 16-Aug-05 processing functions - - is confirmed and agreed by EST/SC                 x

                          When Project Contract has been finalized and signed by
4 30-Jun-05 30-Jun-05                                                                              x
                          Executive Sponsor
                          When Project Organization Planning Session is delivered by
5 10-Aug-05 10-Aug-05                                                                          4   x
                          SunGard SCT and accepted by SC/CPT participants
                          When Detailed Work Plans and Schedules have been
6 27-Sep-05                                                                                    5   x
                          submitted to and formally approved by SC
                          When proposed technology architecture diagram is discussed
7 30-Jun-05 30-Jun-05                                                                                                             x
                          and confirmed by CTS and SCT
 8 8-Jul-05 29-Jul-05     When technology component bill of materials are prepared             7                                  x
 9 15-Jul-05 3-Aug-05     When technology components are procured                              8                                  x
10 15-Aug-05 17-Aug-05    When technology components are installed and configured              9                                  x
                          When licensed software component systems are installed and
11 31-Aug-05 31-Aug-05                                                                        10
                          operational for PT
                          When inventory and procedures to support technology
12                                                                                            10                                  x
                          environments are updated and shared
                          The remaining milestones are not complete yet represent
                          placeholders for Banner-related activities for component
                          systems - - Advancement, Financial Aid, Finance, Human
                          Resources/Payroll and Student:
                          When component system technical and function training has
                          been delivered sufficient to build user interaction prototypes to
A
                          assess standard component system functionality

                          When business requirements gap analysis is confirmed and
B                         agreed by SC sufficient to yield "To Be" functional processes       A

                          When design, configure and mapping of component systems
C                                                                                             B
                          is confirmed and agreed by SC
    When component systems and interfaces are built and tested.
D                                                                 C
    When component system transition, pre-production, user
E   procedures and end-user training has been confirmed and       D
    agreed by SC
    When component system has been migrated to production - -
F                                                                 E
    "Go Live" event
    When component systems are accepted by operations and
G   DU-Implementation Team is disbanned (Project Closure)         F
Tab   Delivery Organization
FI    Finance Process Team
AD    Advancement Process Team
HR    Human Resources/Payroll Process Team
RG    Registrar Process Team
AM    Admissions Process Team
RL    Residence Life Process Team
FA    Financial Aid Process Team
IT    Information Technology Process Team
LP    Luminis Portal Team
DS    Data Standards Team
DW    Reporting Strategy Team
TR    Training Team
SCT   Possible services proposed by SunGard SCT
PM    Program and Project Management team
PT    Project Team
                                                                                 Planned                Actual
ID                           Milestone                           Pre- Owner Start Date End Date   Start Date End Date
                          General Ledger
FO Establish Client Implementation Team.
1
FO Review current policies and procedures relative to the
  2 building and maintaining of the Chart of Accounts.
FO Determine proper chart design to facilitate hard copy
  3 reporting and on-line query screens.
FO Review Validation and Control Forms in light of intended
  4 usage.
FO Determine appropriate values for Validation and Control
  5 Forms needed to support intended processing
    Begin development of a subset of the Banner Chart of
    Accounts on paper.


FO
 6




FO Review the preliminary chart with the appropriate end users
 7 in order to solicit their input
FO Review report processing for report execution.
 8
     Run and review the following chart of accounts reports.




FO
 9




     Analyze accounting logic of transactions pooled into current
 F
     accounting system. Compile listing of all transactions
 10
     utilized in current accounting system.
 F FTMRUCL – Rules Maintenance Form
 11
 F Determine table and form security for users needing access
 12 to Schedule Module forms and reports.
 F Grant table access and set up Form Level security for users
 13 needing access to Schedule forms and reports.
     Assign and distribute passwords and permissions to
F 14 Schedule Module users.
 F Determine hardware and equipment needs for offices
 15 needing access to Schedule Module forms.
 F Wire offices and test equipment.
 16
 F Announce new procedures and provide appropriate forms
 17 for data collection.
 F Write user procedures, reflecting Banner usage and new
 18 policies and procedures, for Chart of Account users.
 F Train end-users in the use of the Chart of Accounts
 19
 F Chart of Accounts in production
 20
                         Finance Specifics
   Develop bank fund as a unique fund code per the
FS FTMFUND table; establish cash and cash equity accounts
 1 using the FTMACCT table; establish banks using the
   GXRBANK table.
   Identify all conversion and interface requirements and make
   determination on the methodology for accomplishing these
   tasks (e.g., manual or automated).




FS
 2




FS Begin analysis and coding process for automated
 3 conversions and interface.
   Follow the Chart of Accounts entry process provided by
FS SCT for guidance including establishment of all required
 4 control accounts. Postings to the general ledger will be
   incorrect if this data is not properly established.
   Validate the entry of the Chart of Accounts by entering
   sample test data against the sample chart in order to
   validate the design of the chart. Enter transactions using
FS
   the journal voucher forms (FGAJVCD and FGAJVCQ).
 5
   Rule classes JE 15, JE16, BDO1, and CRO5 should be
   utilized when entering transaction data via the journal entry
   forms.
FS Run Posting Program (FGRACTG) to generate required
 6 accounting logic and postings to the financial ledger.
   Validate transaction postings by generating the standard
   reports.




FS
 7




FS Refer to the SCT supplied “list of Reports and Parameters”
 8 for other report options
     Validate transaction postings by retrieving the General
     Accounting Query Forms




FS
 9




   Following validation process, determine if the design of the
   subset of the COA is correct. Revise as required. Repeat
FS
   tasks of entering transactions, running posting programs,
10
   and validation process (on-line and hard copy).

FS Continue with the development of additional Chart of
11 Accounts data.
   Repeat tasks of entering transactions, running posting
FS
   programs, and validation process (on-line and hard copy).
12
FS Repeat previous two tasks until chart is finalized.
13
   Process transactions with rule codes that invoke cash
FS accounting logic (e.g., CR05) to various bank accounts
14 defined on the GXRBANK table. Can be done concurrently
   with other transaction input.
FS Run posting process.
15
   Verify transaction postings by retrieving the data posted to
FS the Bank Fund via the FGITBAL form and FGRTBAL
16 report. Can be done concurrently with other transaction
   input.
FS Revise bank table with necessary corrections.
17
FS Analyze current policy and procedure issues in the
18 Purchasing and Accounts Payable offices.

              Biographics and Demographic Data
    Review current policies and procedures relative to
    maintenance of the person/non-person data.


D
1




    Review biographic & demographic data entry forms and
    determine appropriate usage
D
2



  Determine how data will be maintained and tracked in
D Banner
3

    Develop Data entry Standards Procedures
D
4
  Review biographic & demographic data entry forms and
D
  determine appropriate usage.
5
D   Determine appropriate values for Validation Forms needed
6   to support intended processing
D   Determine procedures for record updates as additional
7   information and/or changes are received.
    Revise current policies and prepare new policies as
    required.
D
8



    Determine need and usage of forms used to collect
    information on new/changed person data. Prepare/ revise
    forms in light of Banner values and processing.

D
9




D Review biographic & demographic reports. Determine
10 required revisions and need for additional reports.
     Determine and define interface requirements.




D
11




D    Obtain necessary approvals for new/revised policies,
12   procedures.
D    Send new forms for printing.
13
D    Enter Validation Forms values. Verify entered values and
14   use of forms.
D    Write specifications for report revisions, new reports and
15   required interfaces.
D    Write and test revised/new reports and interfaces.
16
D    Obtain user sign-off on revised/new reports and interfaces.
17
D    Determine table and form security for users needing access
18   to General Person Module forms and reports.
D    Grant table access and set up Form Level security for users
19   needing access to appropriate forms and reports.
D    Assign and distribute passwords and permissions to
20   appropriate modules
     Determine data conversion scope, process, and population
     (both persons and non-persons)
D
21
D    Write and test conversion programs.
22
D    Convert person/non-person data.
23
D    Verify conversion.
24
D    Determine hardware and equipment needs for offices
25   needing access to biographic & demographic forms.
D    Wire and test office equipment.
26
D    Write user procedures, reflecting Banner usage and new
27   policies and procedures, for data entry users.
D    Announce new procedures and provide appropriate forms
28   for data collection.
     Train end-users in the use of the appropriate system
     module
D
29



D Train end-users in report generation.
30
D Biographic & demographic data entry in production.
31

                           Purchasing
P Review current policies and procedures relative to
1 maintenance of purchasing information.
  Determine PO desired layout prior to generating test pattern
P
  for PO stock in order to look at ordering forms or otherwise
2
  developing a PO print solution.
P Determine how Purchasing data will be maintained and
3 tracked in Banner.
P Review Purchasing Module Validation and Control Forms in
4 light of intended usage.
P   Determine appropriate values for Validation and Control
5   Forms needed to support intended processing.
P   Review/revise current policies and prepare new policies as
6   needed.
P   Perform training exercises provided by SCT Consultant.
7
  Make P.O. entries utilizing client documentation as source
P
  document (e.g., requisition, purchase order, bids)
8
    Enter requisition data into Banner Finance utilizing the
    appropriate forms.



P
9
     Enter applicable bid information utilizing the appropriate
     forms.




P
10




     Review the appropriate change order forms.
P
11
     Review the appropriate text entry forms:



P
12
     Validate transaction data on the standard reports.




P
13
     Validate transaction data utilizing the appropriate purchase
     order on-line query forms.




P
14




P    Determine table and form security for users needing access
15   to Purchasing Module forms and reports.
P    Grant table access and form security for users needing
16   access to Purchasing Module forms and reports.
P    Determine hardware and equipment needs for offices
17   needing access to General Student Module forms.
P    Wire offices and test equipment.
18
   Write user procedures, reflecting Banner usage and new
P
   policies and procedures, for General Student Module users.
19
P Announce new procedures and provide appropriate forms
20 for data collection.
     Train end-users in the use of the Purchasing Module
P
21


P Train end-users in report generation.
22
P Purchasing Module in production.
23

                         Approval Processing
     Analyze current approval process for various financial
     transactions (e.g., Requisitions, Purchase Orders, Journal
     Vouchers, etc.) on the appropriate forms.




AP
 1




AP   Determine table and form security for users needing access
 2   to Approvals forms.
AP   Grant table access and form security for users needing
 3   access to Approvals forms.
AP   Determine hardware and equipment needs for offices
 4   needing access to Purchasing Module forms.
AP   Wire offices and test equipment.
 5
AP   Write user procedures, reflecting Banner usage and new
 6   policies and procedures, for Approvals users.
AP   Announce new procedures and provide appropriate forms
 7   for data collection.
     Train end-users in the use of the Approvals process.
AP
 8


     Train end-users in report generation.

                           Accounts Payable
AP   Review current policies and procedures relative to
 1   maintenance of Accounts Payable information.
AP   Determine how Accounts Payable data will be maintained
 2   and tracked in Banner.
AP   Review Accounts Payable Module Validation and Control
 3   Forms in light of intended usage.
AP   Determine appropriate values for Validation and Control
 4   Forms needed to support intended processing.
AP   Review/revise current policies and prepare new policies as
 5   needed.
AP   Perform training exercises provided by SCT Consultant.
 6
     Enter invoice and credit memo data utilizing existing
     invoices as source data.




AP
 7




AP Generate test pattern for check stock in order to look at
 8 ordering forms.
   Run check writing process.
AP
 9


AP Validate check and check stub data.
10
     Run check reconciliation process (after various check
     cycle).



AP
11




AP   Contact banking institutions to discuss requirements for
12   paid check tape interface into Banner.
AP   Determine table and form security for users needing access
13   to Accounts Payable Module forms and reports.
AP   Grant table access and form security for users needing
14   access to Accounts Payable Module forms and reports.
AP   Determine hardware and equipment needs for offices
15   needing access to Accounts Payable Module forms.
AP   Wire offices and test equipment.
16
   Write user procedures, reflecting Banner usage and new
AP
   policies and procedures, for Accounts Payable Module
17
   users.
AP Announce new procedures and provide appropriate forms
18 for data collection.
   Train end-users in the use of the Purchasing Module
AP
19


AP Train end-users in report generation.
20
AP Accounts Payable Module in production.
21
                             Fixed Assets
F   Review current policies and procedures relative to
1   maintenance of Fixed Assets information.
F   Determine how Fixed Assets data will be maintained and
2   tracked in Banner.
F   Review Fixed Assets Module Validation and Control Forms
3   in light of intended usage.
F   Determine appropriate values for Validation and Control
4   Forms needed to support intended processing.
F   Review/revise current policies and prepare new policies as
5   needed.
F   Perform training exercises provided by SCT Consultant.
6
    Create and maintain Fixed Assets information using the
    appropriate forms.




F
7




F   Determine table and form security for users needing access
8   to Fixed Assets Module forms and reports.
F   Grant table access and form security for users needing
9   access to Fixed Assets Module forms and reports.
F Determine hardware and equipment needs for offices
10 needing access to Fixed Asset Module forms.
F Wire offices and test equipment.
11
   Write user procedures, reflecting Banner usage and new
F
   policies and procedures, for Fixed Assets Module users.
12
F Announce new procedures and provide appropriate forms
13 for data collection.
   Train end-users in the use of the fixed Asset Module
F
14


F Train end-users in report generation.
15
F Fixed Asset Module in production.
16

                          Encumbrances
     Validate encumbrance data via the appropriate General
     Accounting on-line query forms.

E
01



E    Correlate information presented on reports with the on-line
02   screens
E    Determine table and form security for users needing access
03   to Encumbrances forms.
E    Grant table access and form security for users needing
04   access to Encumbrances forms.
E    Determine hardware and equipment needs for offices
05   needing access to Encumbrances forms.
E    Wire offices and test equipment.
06
E    Write user procedures, reflecting Banner usage and new
07   policies and procedures, for Encumbrances users.
E    Announce new procedures and provide appropriate forms
08   for data collection.
     Train end-users in the use of the Encumbrances process.
E
09


E Train end-users in report generation.
10

                      Endowment Accounting
EA   Review current policies and procedures relative to
01   maintenance of endowment accounting data.
EA   Determine how Endowment Accounting data will be
02   maintained and tracked in Banner.
EA   Review Endowment Accounting Module Validation and
03   Control Forms in light of intended usage.
EA   Determine appropriate values for Validation and Control
04   Forms needed to support intended processing.
EA   Review/revise current policies and prepare new policies as
05   needed.
EA   Perform training exercises provided by SCT Consultant.
06
EA   Establish System Controls and set up Banner Finance for
07   Endowment Accounting.
EA   Set up a financial manager
08
EA   Create the Endowed Principal Fund for the “Corpus” for all
09   Endowment and Similar funds
EA   Create a Pool Fund for investment purposes
10
EA   Create a Pooled Income Fund for recording the
11   Gains/Losses for investment activity.
EA   Create a Spendable income fund for each Gift.
12
EA   Define account codes for endowment management.
13
EA   Define the investment pool.
14
EA   Link endowment funds to spendable income funds.
15
EA   Record donor-imposed restrictions on spendable income.
16
EA   Record the Purchase Price per Unit.
17
EA   Create and maintain unitized pools
18
EA   Periodically convert gifts and internal transfers into “units”
19   (shares) in a pool
EA   Create a journal voucher to receive an endowed gift
20
EA   Create a journal voucher to transfer a gift to the investment
21   manager.
EA   Run the Unitization Process.
22
EA   Set a spendable rate per unit
23
EA   Run the Distribution of Spendable Income Process.
24
EA   Run the Distribution of Gains/Losses Process.
25
EA   Make distributions to spendable funds.
26
EA   Run the endowment management reports.
27
   Determine table and form security for users needing access
EA
   to Endowment Accounting Module forms and reports.
28
   Grant table access and form security for users needing
EA
   access to Endowment Accounting Module forms and
29
   reports.
   Determine hardware and equipment needs for offices
EA
   needing access to Endowment Accounting Module forms.
30
EA Wire offices and test equipment.
31
   Write user procedures, reflecting Banner usage and new
EA
   policies and procedures, for Endowment Accounting Module
32
   users.
EA Announce new procedures and provide appropriate forms
33 for data collection.
   Train end-users in the use of the Endowment Accounting
   Module
EA
34


EA Train end-users in report generation.
35
EA Endowment Accounting in production.
36

                        Research Accounting
RA   Review current policies and procedures relative to
 1   maintenance of research accounting data.
RA   Determine how Research Accounting data will be
 2   maintained and tracked in Banner.
RA   Review Research Accounting Module Validation and
 3   Control Forms in light of intended usage.
RA   Determine appropriate values for Validation and Control
 4   Forms needed to support intended processing.
RA   Review/revise current policies and prepare new policies as
 5   needed.
RA   Perform training exercises provided by SCT Consultant.
 6
     Create and maintain grant/contract and proposal
     information utilizing the appropriate forms.




RA
 7
     Create and maintain validation data used in the
     management, accounting, and tracking of grant information
     and financial data.




RA
 8
     Generate the standard reports on Grants and Contracts




RA
 9




   Determine table and form security for users needing access
RA
   to Research Accounting Module forms and reports.
10
   Grant table access and form security for users needing
RA
   access to Research Accounting Module forms and reports.
11
RA Determine hardware and equipment needs for offices
12 needing access to Research Accounting Module forms.
RA Wire offices and test equipment.
13
   Write user procedures, reflecting Banner usage and new
RA
   policies and procedures, for Research Accounting Module
14
   users.
RA Announce new procedures and provide appropriate forms
15 for data collection.
     Train end-users in the use of the Research Accounting
     Module
RA
16


RA Train end-users in report generation.
17
RA Research Accounting Module in production.
18

                         Budget Development
B    Review current policies and procedures relative to
1    maintenance of Budget Development information.
B    Determine how Budget Development data will be
2    maintained and tracked in Banner.
B    Review Budget Development Module Validation and Control
3    Forms in light of intended usage.
B    Determine appropriate values for Validation and Control
4    Forms needed to support intended processing.
B    Review/revise current policies and prepare new policies as
5    needed.
B    Perform training exercises provided by SCT Consultant.
6
    Use the appropriate forms to develop a budget in
    preparation for the start of the next fiscal year.




B
7




    Produce and review the standard reports.



B
8




  Determine table and form security for users needing access
B
  to Budget Development Module forms and reports.
9
   Grant table access and form security for users needing
B
   access to Budget Development Module forms and reports.
10
B Determine hardware and equipment needs for offices
11 needing access to Budget Development Module forms.
B Wire offices and test equipment.
12
   Write user procedures, reflecting Banner usage and new
B
   policies and procedures, for Budget Development Module
13
   users.
B Announce new procedures and provide appropriate forms
14 for data collection.
   Train end-users in the use of the Budget Development
   Module
B
15


B Train end-users in report generation.
16
B Budget Development Module in production.
17

                         Year End Processing
B   Review current policies, procedures and requirements
1   relative to year end processing.
B   Determine how year end data will be maintained and
2   tracked in Banner.
B   Review year end processing Validation and Control Forms
3   in light of intended usage.
B   Determine appropriate values for Validation and Control
4   Forms needed to support intended processing.
B   Review/revise current policies and prepare new policies as
5   needed.
B   Perform training exercises provided by SCT Consultant.
6
     Use the appropriate forms to test the procedures
     developed.



B
7




     Generate the standard reports.




B
8




B  Determine table and form security for users needing access
 9 to the year end forms, processes and reports.
B  Grant table access and form security for users needing
10 access to year end forms, processes and reports.
   Determine hardware and equipment needs for offices
B
   needing access to the year end forms, processes and
11
   reports.
B Wire offices and test equipment.
12
B Write user procedures, reflecting Banner usage and new
13 policies and procedures.
B Announce new procedures and provide appropriate forms
14 for data collection.
B Train end-users in the use of the year end processes
15
B Train end-users in report generation.
16
B Year end processes in production.
17
Comments




Pay particular attention to
the following attributes:
Fund Types             Fund
Codes Organization
Codes Program Codes
Account Types Account
Codes      Activity Codes
Location Codes
FGRFNDH Fund
Hierarchy Report
FGRORGH Organization
Hierarchy Report
FGRACTH - Account
Hierarchy Report
FGRPRGH - Program
Hierarchy Report
FGRACTV - Activity
Codes Report
FGRLOCH - Location
Hierarchy Report
FGRACCI - Account Index
Report
Data to consider for
conversion:
Beginning balance sheet
accounts
Operating ledger balances
Fixed Asset data
Beginning budget
balances
Vendor file conversion
Payroll interfaces
Student billing        Cash
collections applicable to
student accounts
1099 file conversion
Plant operations
Reports to include:
G/L Transaction Report
(FGRGLTA) used to validate
detail transaction postings to
the general ledger.
Balance Sheet Report
(FGRBLSH) - used to
validate fund and account
Chart of Accounts
components.
Statement of Revenues,
Expenditures Other Changes
Report (FGRREOB) and
(FGRREOC)
Changes in Fund Balance
Report (FGRCHFB) - used to
validate fund and account
(revenue, expenditures)
Chart of Accounts
components.
Budget Status Report
(FGRBDSC) - used to
validate fund, org, and
account (revenue,
expenditure transfers) Chart
of Accounts components.
Organization Detail Report
(FGRODTA) used to validate
detail transaction posting to
the Banner operating ledger.
Program Detail Report
(FGRPDTA) used to validate
detail transactions postings
to the Banner operating
ledger, including program.
Forms to retrieve:
FGIBAVL - Budget
Availability Status Form
FGIBDST – Organization
Budget Status Form
FGIBSUM – Organization
Budget Summary Form
FGITBAL - General
Ledger Trial Balance Form
FGITRND - Operating
Accounts Transaction
Detail Activity
FGIGLAC - General
Ledger Transaction Detail
Activity         FGIBDSR -
Executive Summary Form
FGIDOCR – Document
Retrieval Inquiry Form
Include review of name
and ID change
procedures, maintenance
of addresses, use of
holds, use of comments,
offices to maintain data
when changes are
necessary, etc.

Review required forms
and values and determine
how they will be used.
Review optional forms and
values and determine
whether and how they will
be used.
Pay particular attention to
name searches to reduce
the number of duplicate
records.
Standards for all Banner
data entry of
biographic/demographic
data.
Cross-Functional Team
needed- determine
owner(s)
Cross-Functional Team
needed
Cross-Functional Team
needed
Identify offices involved in
maintaining records and
cut off points, e.g.
Admissions will change
applicants addresses until
they register, than
Registrar does so.
Include review/preparation
of the following forms:
Initial
biographic/demographic
data collection forms
Name and ID change
forms
Address change forms
Telephone number
change forms
Interfaces to consider:
Interface to Human
Resources System
Interface to Alumni
System             Interface
to Finance System
(vendor names, IDs, and
addresses)       Interface
to Financial Aid System
Interface to Student
System              Other
Systems (list)




Consider which records
and data elements to
convert, pre-conversion
data clean-up efforts, post-
conversion verification,
and correction process
Navigation training will
also be required. Most
offices on campus will
need training in
appropriate modules.
Train users using new
procedures manual.
Forms to use include:
FPAREQN – Requisition
Header Form
FPIREQN - Requisition
Query Form     FPARDEL
– Requisition Delete For
FPIORQF – Open
Requisition by FOAPAL
Form          FPIREQS –
Requisition Suspense List
Form
Forms to use include:
FPACTBD - Bid
CreationForm FPABIDH
- Bid Header Form
FPAPRBD – Assign
Prospective Bidders Form
FPABIDE - Bid Entry Form
FPABIDC - Bid
Comparison Form
FPABAWD - Bid Award
Form              FTIABID -
Bid Alpha Search Form
FTIBIDS – Request for Bid
List Validation Form
FTMBCLS - Bid
Classification Maintenance
Form FPAPURR –
Purchase Order Form
FPABLAR – Blanket Order
Form      FPAPDEL –
Purchase/Blanket Order
Delete Form FPAERSD
– Resend EDI
PO/POChanges Form
FPARORD – Rush Order
Form             FPIPORS
– Purchase Order
Suspense List Form
FPAEOCD –
Encumbrance Open/Close
Form             FPIEOCL
– Encumbrance
Open/Close List Form
Forms to include:
FPACHAR – Change
Order Form       FPACDEL
– Change Order Delete
Form
Forms to include:
FOACLAU Clause Entry
Form           FOAPOXT
– Procurement Text Entry
Form FOATEXT –
General Text Entry Form
FOICLAU – Clause List
Form
Reports include:
FGRIDOC – Incomplete
Document Listing Report
FGROPNE – Open
Encumbrances Report
FPABIDD - Print Bid
Forms           FPAPORD
– Purchase Order Form
Print FPARQST – Request
Form Printing FPRBEVL
- Bid Evaluation Report
FPRDELV – Delivery Log
Report         FPROPNP
– Open Purchase Orders
Report         FPROPNR
– Open Request Report
FPRRCDL – Receiving
and Delivery Report
FPRVCAT –Vendor
Products Catalog Report
FPRVVOL – Vendor's
Volume Report
FPTBIDD - Bid Forms
Test Pattern
FPTPORD – Purchase
Order Form Test Pattern
FPTRQST – Request
Form Test Pattern
Forms include:
FPIBLAR – Blanket Order
Activity Form   FPIPURR
– Purchasing Query Form
FPIOPOB – Open
Purchase Order by Buyer
FPIOPOV – Open
Purchase Order by Vendor
FPIOPOF – Open
Purchase Order by
FOAPAL         FOIDOCH
– Document History Form
FTICOMH – Commodity
Hierarchy Form FPIPOHD
– Purchase Order List
Validation Form FPIBORD
– Blanket Order Validation
Form
Navigation and General
Person Module training will
also be required unless
previously provided.




Forms to include:
FOASYSC – System
Control Maintenance Form
FTMAPPQ – Approval
Queue Maintenance Form
FOMAQRC – Approval
Queue Routing Codes
Form            FOIAINP
– Approvals Notification
Form FOAUAPP –
Unapproved Document
Display Form FOAAINP –
Document Approval Form
FOIAPPH – Document
Approval History Form
FOIAPHT - Approval
History Form
Navigation and General
Person Module training will
also be required unless
previously provided.
Testing to include the
following processes:       -
Invoices with vendor
numbers defined on the
Vendor Maintenance form
-Invoices without vendor
numbers                  -
Invoices with multiple due
dates                 -
Invoices with third party
check vendors              -
Recurring payable
transactions; utilizing
Recurring Payables Form
(FAARUIV)            -
Invoices with all the
various bank numbers



Process to include:
FAAONLC - On-line
Check Print Form
FAACHKS - Check
Cancellation Form
Process to include:
FAABREC – Bank
Reconciliation Form,
FARBREC – Bank
Reconciliation Report,
FARBBAL – Bank
Reconciliation Balance
Report, FARAAGE – Bank
Reconciliation Activity
Aging Report, FARCHKR
– Check Register Report




Navigation and General
Person Module training will
also be required unless
previously provided.
Forms to include:
FFAMAST - Fixed Assets
Master Maintenance Form
FFAAADP – Fixed Assets
Depreciation Form
FFAATRF - Fixed Assets
Transfer Maintenance
Form              FFITALV
– Temporary Asset List
Form FFIPALV –
Permanent Asset List
Form
FTMACQM – Acquisition
Code Maintenance Form
FTMDISP - Disposal
Method Code
Maintenance Form
TMASTY – Asset Type
Maintenance Form
FTMDEPR – Depreciation
Method Code
Maintenance Form
FTMACON - Asset
Condition Code
Maintenance Form
FTMTTST - Title-to-Status
Code Maintenance Form
FFRAGRP – Fixed Assets
Master Group Report
FMDPFD – Fixed Assets
Depreciation Summary
Report
PFRMAST – Fixed Assets
Navigation and General
Person Module training will
also be required unless
previously provided.




Forms to include:
FGIENCB – Encumbrance
List Form       FGIENCD
– Detail Encumbrance List
Form FGIOENC –
Organizational
Encumbrance Form
Navigation and General
Person Module training will
also be required unless
previously provided.
Navigation and General
Person Module training will
also be required unless
previously provided.
Forms to include:
FRAPROP -
Grant/Contract Proposal
Maintenance Form
FRABUDG - Grant Project
Budget Maintenance Form
FRABUDT - Grant Project
Budget Totals Form
FOARMDR - Events/Dates
Maintenance Form
FRADATE - Events/Dates
Reminder Form
Forms to include:
FRAGRNT - Grant
Maintenance Form
FRAPAYM -
Grant/Contract Payment
Method Maintenance
Form            FRAINDC -
Indirect Cost Method Code
Maintenance Form
FRACOST - Cost Sharing
Methods Code
Maintenance Form
FRASREQ - Special
Requirements
Maintenance Form
FRAEVNT - Event Codes
Maintenance Form
FRASACT - Sponsor
Account Codes
Maintenance Form
FRAISAC -
Institution/Sponsor
Account Codes
Maintenance Form
Reports to include:
FRRGBFY - Grant Budget
Status Fiscal Year Report
FRRGPPY - Grant Budget
Status Project Report
FRRGCCP - Grants and
Contracts Cash Position
Report         FRRGCDB -
Grants and Contracts
Disbursements Report
FRRGCDB - Grants and
Contracts Disbursements
Report
FRRGITD - Inception-to-
Date Report
Navigation and General
Person Module training will
also be required unless
previously provided.
Forms to include:
FTMOBUD – Operating
Budget Maintenance Form
FBIBUDG – Budget Query
Form            FBABDRA
– Budget Request By
Account Form
FBABDRQ – Budget
Request Form FBABDMN
– Budget Maintenance
Form FBABDDS – Budget
Distribution Parameter
Form            FBABDDA
– Budget Distribution by
Amount Form
FBAMCHG – Mass
Budget Change Form
FBABPRC - Budget
Process Control
Parameter Form




Reports to include:
FBRAPPD – Approved
Distributed Budget Report
FBRAPPR – Approved
Budget Report FBRBDDS
– Budget Distribution
Summary FBRWSKS –
Budget Worksheet Report
Navigation and General
Person Module training will
also be required unless
previously provided.
Forms to include:
FGAYRLM - Year-End
Ledger Maintenance Form
FTMFSYR - System
Control Fiscal year Set-Up
FOASYSC - Define
system-wide defaults
FTMFTYP - Define
Exceptions to system-wide
defaults

Reports to include:
FGRBDRL - End-of-Year
Budget Carry Forward
Report          FGRENRL
- End-of-Year
Encumbrance Carry
Forward Repor
FGRGLRL - Balance
Forward Processing
Report          FGRCLOP
- Close Operating
Accounts Report
                                                                               Planned                Actual
 ID                         Milestone                          Pre- Owner Start Date End Date   Start Date End Date

                    Membership Task Log
      Review current policies and procedures relative to the
      maintenance of membership information.




A1




      Review Membership Module forms and determine
A2    appropriate usage.

      Determine how membership data will be maintained
A3
      and tracked in Banner.
      Determine appropriate values for validation forms
A4
      needed to support intended processing.
      Determine procedure for maintenance validation
A5
      forms.
      Determine procedures for record updates as
A6    membership data changes and new data is obtained.

      Revise current policies and prepare new policies as
A7
      needed.
      Determine need for and usage of paper forms used to
      collect membership data or support processing.
A8
      Gather and annotate any preprinted forms.

      Determine which pre-printed forms will still be
A9
      required after conversion to Banner.
      Review Membership Module reports and processes.
A10   Determine any required revision and need for new
      reports.
      Determine and define interface requirements.

A11


      Obtain necessary approvals for new policies,
A12
      procedure revisions, reports, printed forms.
A13   Design and order new/revised forms.
      Enter validation form values. Verify entered values
A14
      and test on forms.
      Write specifications for report revisions, new reports
A15
      and required interfaces.
A16   Write and test revised/new reports and interfaces.
A17   Obtain user sign-off on reports and interfaces.
      Determine table and process level security for users
A18
      accessing the Membership Module.
      Grant table access and set up process level security
A19
      for users.
      Determine membership conversion scope and
      Consider which records and data elements to
      process.




A20




A21   Write and test conversion program.
A22   Convert membership data.
A23   Verify and correct membership data.
      Write user procedures reflecting Banner usage, new
A24
      policies and procedures.
      Publish and distribute new policies/procedures and
A25
      provide appropriate forms.
      Train end users in the use of the Membership Module.

A26


A27   Train end users in report submission.
      Determine hardware and equipment needs for offices
A28
      needing access to forms.
A29   Wire offices and test equipment.
      Membership Module in production.




A30




      Module Post Implementation Assessment


A31




            Biographic & Demographic Data Entry
     Review current policies and procedures relative to
     maintenance of the person/non-person data.



D1




     Review biographic & demographic data entry forms
     and determine appropriate usage


D2




     Determine how data will be maintained and tracked in
     Banner
D3


     Develop Data entry Standards Procedures
D4


     Review biographic & demographic data entry forms
D5   and determine appropriate usage.

     Determine appropriate values for Validation Forms
D6
     needed to support intended processing
      Determine procedures for record updates as
D7    additional information and/or changes are received.

      Revise current policies and prepare new policies as
      required.

D8




      Determine need and usage of forms used to collect
      information on new/changed person data. Prepare/
      revise forms in light of Banner values and processing.


D9




      Review biographic & demographic reports. Determine
D10   required revisions and need for additional reports.
      Determine and define interface requirements.




D11




      Obtain necessary approvals for new/revised policies,
D12
      procedures.
D13   Send new forms for printing.
      Enter Validation Forms values. Verify entered values
D14
      and use of forms.
      Write specifications for report revisions, new reports
D15
      and required interfaces.
D16   Write and test revised/new reports and interfaces.
      Obtain user sign-off on revised/new reports and
D17
      interfaces.
      Determine table and form security for users needing
D18   access to General Person Module forms and reports.

      Grant table access and set up Form Level security for
D19   users needing access to appropriate forms and
      reports.
      Assign and distribute passwords and permissions to
D20
      appropriate modules
      Determine data conversion scope, process, and
      population (both persons and non-persons)

D21



D22   Write and test conversion programs.
D23   Convert person/non-person data.
D24   Verify conversion.
      Determine hardware and equipment needs for offices
D25   needing access to biographic & demographic forms.

D26   Wire and test office equipment.
      Write user procedures, reflecting Banner usage and
D27   new policies and procedures, for data entry users.

      Announce new procedures and provide appropriate
D28
      forms for data collection.
      Train end-users in the use of the appropriate system
      module

D29



D30   Train end-users in report generation.
      Biographic & demographic data entry in production.
D31


                     Designation Task Log
     Review current policies and procedures relative to
     maintenance of Designations.




D1




     Review Designation Module forms and determine
     appropriate usage.
D2



     Determine how Designation data will be maintained
D3
     and tracked in Banner.
     Determine appropriate values for validation forms
     needed to support intended processing.
D4



     Determine procedure for maintaining validation forms
D5
     that will be used.
     Determine procedures for record updates as
D6
     Designation data is added or changed.
     Revise current policies and prepare new policies as
D7
     needed.
      Determine need for and usage of forms used to
D8    collect Designation data or support processing.
      Gather and annotate any pre-printed forms used.
      Determine which pre-printed forms will still be
D9
      required after con -version to Banner.
      Review Designation Module reports and processes.
D10   Determine any required revisions and need for new
      reports.
D11   Determine and define interface requirements.
      Obtain necessary approvals for new policies,
D12
      procedure revisions, reports, and special forms.
D13   Design and order new/revised forms.
      Enter validation form values. Verify entered values
D14
      and test on forms.
      Write specifications for report revisions, new reports,
D15
      and required interfaces.
D16   Write and test revised/new reports and interfaces.
      Obtain user sign-off on revised/new reports and
D17
      interfaces.
      Determine table and process level security for users
D18   needing access to Designation Module forms and
      reports.
      Grant table access and set up process level security
D19
      for users.
      Determine Designation conversion scope and
      process.


D20
D21   Write and test conversion programs.
D22   Convert Designation data.
D23   Verify and correct Designation data.
      Write user procedures reflecting Banner usage and
D24   new policies and procedures for Designation Module
      users.
      Publish and distribute new polices/procedures and
D25
      provide appropriate forms.
      Train end-users in the use of the Designation Module.

D26


D27   Train end-users in report generation.
      Determine hardware and equipment needs for offices
D28
      needing access to forms.
D29   Wire offices and test equipment.
      Designation Module in production.


D30



D31   Module Post Implementation Assessment

                      Campaign Task Log
      Review current policies and procedures relative to
      maintenance of Campaign information.
F1
      Review Campaign Module forms and determine
      appropriate usage.
F2



      Determine how Campaign data will be maintained and
F3
      tracked in Banner.
      Determine appropriate values for validation forms
F4
      needed to support intended processing.
      Determine procedure for maintaining validation forms
F5
      that will be used.
      Determine procedures for record updates as
      Campaign data is added or changed.
F6


      Revise current policies and prepare new policies as
F7
      needed.
      Determine need for and usage of paper forms used to
      collect Campaign data or support processing. Gather
F8
      and annotate any pre-printed forms.

      Determine which pre-printed forms will still be
F9
      required after conversion to Banner.
      Review Campaign Module reports and processes.
F10   Determine any required revisions and need for new
      reports.
F11   Determine and define interface requirements.
      Obtain necessary approvals for new policies,
F12
      procedure revisions, reports, special forms.
F13   Design and order new/revised forms.
      Enter validation form values. Verify entered values
F14
      and test on forms.
      Write specifications for report revisions, new reports,
F15
      and required interfaces.
F16   Write and test revised/new reports and interfaces.
      Obtain user sign-off on revised/new reports and
F17
      interfaces.
      Determine table and process level security for users
F18   needing access to Campaign Module forms and
      reports.
      Grant table access and set up process level security
F19
      for users.
      Determine Campaign conversion scope and process.
F20


F21   Write and test conversion programs.
F22   Convert Campaign data.
F23   Verify and correct Campaign data.
      Write user procedures reflecting Banner usage and
F24   new policies and procedures for Campaign Module
      users.
      Publish and distribute new policies/procedures and
F25
      provide appropriate forms.
      Train end users in the use of the Campaign Module.

F26


      Determine hardware and equipment needs for offices
F27
      needing access to forms.
F28   Wire offices and test equipment.
F29   Campaign Module in production.
      Module Post Implementation Assessment


F30




                   Gift & Payment Task Log
      Review current policies and procedures relative to
      maintenance of Gift/Pledge Payment information.




G1




      Review Gift/Pledge Payment Module forms and
      determine appropriate usage.
G2



      Determine how Gift/Pledge Payment data will be
G3
      maintained and tracked in Banner.
      Determine appropriate values for validation forms
G4
      needed to support intended processing.
      Determine procedure for maintaining validation forms
G5
      that will be used.
      Determine procedures for record updates as
      Gift/Pledge Payment data changes or new data is
G6
      obtained.

      Revise current policies and prepare new policies as
G7
      needed.
      Determine need for and usage of paper forms used to
      collect Gift/Pledge Payment data or support
G8
      processing. Gather and annotate any pre-printed
      forms.
      Determine which pre-printed forms will still be
G9
      required after conversion to Banner.
      Review Gift/Pledge Payment Module reports and
G10   processes. Determine any required revisions and
      need for new reports.
      Determine and define interface requirements.



G11




      Obtain necessary approvals for new policies,
G12
      procedure revisions, reports, and special forms.
G13   Design and order new/revised forms.
      Enter validation form values. Verify entered values
G14
      and test on forms.
      Write specifications for report revisions, new reports,
G15
      and required interfaces.
G16   Write and test revised/new reports and interfaces.
      Obtain user sign-off on revised/new reports and
G17
      interfaces.
      Determine table and process level security for users
G18   needing access to Gift/Pledge Payment Module forms
      and reports.
      Grant table access and set up process level security
G19   for users needing access to Gift/Pledge Payment
      Module forms and reports.
      Determine Gift/Pledge Payment conversion scope
      and process.




G20




G21   Write and test conversion programs.
G22   Convert Gift/Pledge Payment records.
G23   Verify and correct Gift/Pledge Payment data.
      Write user procedures reflecting Banner usage and
G24   new policies and procedures for Gift/Pledge Payment
      Module users.
      Publish and distribute new policies/procedures and
G25
      provide appropriate forms.
      Train end users in the use of the Gift/Pledge Payment
      Module.
G26


G27   Train end-users in report generation.
      Determine hardware and equipment needs for offices
G28
      needing access to forms.
G29   Wire offices and test equipment.
      Gift/Pledge Payment Module in production.




G30




      Module Post Implementation Assessment


G31




                       Pledge Task Log
     Review current policies and procedures relative to
     maintenance of Pledge information




L1




     Review Pledge Module forms and determine
     appropriate usage
L2



     Determine how Pledge data will be maintained and
L3
     tracked in Banner.
     Determine appropriate values for validation forms
L4
     needed to support intended processing.
     Determine procedure for maintaining validation forms
L5
     that will be used.
     Determine procedures for record updates as Pledge
     data changes or new data is obtained.
L6


     Revise current policies and prepare new policies as
L7
     needed.
     Determine need for and usage of paper forms used to
L8   collect Pledge data or support processing. Gather
     and annotate any pre-printed forms.
      Determine which pre-printed forms will still be
L9
      required after conversion to Banner.
      Review Pledge Module reports and processes.
L10   Determine any required revisions and need for new
      reports.
L11   Determine and define interface requirements.
      Obtain necessary approvals for new policies,
L12
      procedure revisions, reports, and special forms.
L13   Design and order new/revised forms.
      Enter validation form values. Verify entered values
L14
      and test on forms.
      Write specifications for report revisions, new reports,
L15
      and required interfaces.
L16   Write and test revised/new reports and interfaces.
      Obtain user sign-off on revised/new reports and
L17
      interfaces.
      Determine table and process level security for users
L18   needing access to Pledge Module forms and reports.

      Grant table access and set up process level security
L19   for users needing access to Pledge Module forms and
      reports.
      Determine Pledge conversion scope and process.




L20




L21   Write and test conversion programs.
L22   Convert Pledge records.
L23   Verify and correct Pledge data.
      Write user procedures reflecting Banner usage and
L24   new policies and procedures for Pledge Module
      users.
      Publish and distribute new policies/procedures and
L25
      provide appropriate forms.
      Train end users in the use of the Pledge Module.

L26


      Determine hardware and equipment needs for offices
L27
      needing access to forms.
L28   Wire offices and test equipment.
      Pledge Module in production.




L29




      Module Post Implementation Assessment


L30




                   Letter Generation Task Log
      Read and review related info in User and Technical
LG1
      Manual.
      Review the Letter Generation forms for appropriate
LG2
      use.
LG3   Build forms in TRNG.
LG4   Ensure all jobs with this module work in TRNG.
LG5    Move completed forms to TEST.
LG6    Ensure all jobs with this module work in TEST.
LG7    Make screen prints for documentation.
LG8    Move final forms to PROD.
LG9    Determine security for each form/job in module.
LG10   Establish grants/permissions.
       Develop policies and procedures.
LG11


     Determine procedure for maintenance of
LG12 validation/rules forms during implementation, during
     production and for each new aid year.
LG13 Develop plan of action for training end user staff
     Train end user staff
LG14

     Determine current information in legacy system that is
LG15 not provided for in Banner and determine procedures
     w/in Banner.

                Prospect Management Task Log
       Review current policies and procedures relative to the
       maintenance of prospect information.
M1


       Review Prospect Management Module forms and
       determine appropriate usage.
M2
      Determine how prospect data will be maintained and
M3
      tracked in Banner.
      Determine appropriate values for validation forms
M4
      needed to support intended processing.
      Determine procedure for maintenance validation
M5
      forms.
      Determine procedures for record updates as prospect
M6
      data changes and new data is obtained.
      Revise current policies and prepare new policies as
M7
      needed.
      Determine need for and usage of paper forms used to
      collect prospect data or support processing. Gather
M8
      and annotate any preprinted forms.

      Determine which pre-printed forms will still be
M9
      required after conversion to Banner.
M10   Determine any reports that need to be written.
M11   Determine and define interface requirements.
      Obtain necessary approvals for new policies,
M12
      procedure revisions, reports, and printed forms.
M13   Design and order new/revised forms.
      Enter validation form values. Verify entered values
M14
      and test on forms.
M15   Write specifications for reports and interfaces.
M16   Write and test reports and interfaces.
M17   Obtain user sign-off on reports and interfaces.
      Determine table and process level security for users
M18   accessing the Prospect Management Module.

      Grant table access and set up process level security
M19
      for users.
      Determine prospect conversion scope and Consider
      which records and data elements to process.




M20




M21   Write and test conversion program.
M22   Convert prospect data.
M23   Verify and correct prospect data.
      Write user procedures reflecting Banner usage, new
M24
      policies and procedures.
      Publish and distribute new policies/procedures and
M25
      provide appropriate forms.
      Train end users in the use of the Prospect
      Management Module.
M26


M27   Train end users in report submission.
      Determine hardware and equipment needs for offices
M28
      needing access to forms.
M29   Wire offices and test equipment.
M30   Prospect Management Module in production.
      Module Post Implementation Assessment


M31




                    Organization Task Log
      Review current policies and procedures relative to
      maintenance of Organization information.




O1
      Review Organization Module forms and determine
      appropriate usage.
O2



      Determine how Organization data will be maintained
O3
      and tracked in Banner.
      Determine appropriate values for validation forms
      needed to support intended processing.
O4


      Determine procedures for maintaining validation
O5
      forms that will be used.
      Determine procedures for record updates as
O6    Organization data changes or new data is obtained.

      Revise current policies and prepare new policies as
O7
      needed.
      Determine need for and usage of forms used to
O8    collect Organization data or support processing.
      Gather and annotate any pre-printed forms used.
      Determine which pre-printed forms will still be
O9
      required after conversion to Banner.
      Review Organization Module reports. Determine any
      required revisions and need for new reports.
O10


O11   Determine and define interface requirements.
      Obtain necessary approvals for new policies,
O12
      procedure revisions, reports, and forms.
O13   Design and order new/revised forms.
      Enter validation form values. Verify entered values
O14
      and test on forms.
      Write specifications for report revisions, new reports,
O15
      and required interfaces.
O16   Write and test revised/new reports and interfaces.
      Obtain user sign-off on revised/new reports and
O17
      interfaces.
      Determine table and process level security for users
O18   needing access to Organization Module forms and
      reports.
      Grant table access and set up process level security
O19   for users needing access to Organization Module
      forms and reports.
      Determine Organization conversion scope and
      process.




O20




O21   Write and test conversion programs.
O22   Convert Organization data.
O23   Verify and correct Organization data.
      Write user procedures reflecting Banner usage and
O24   new policies and procedures for Organization Module
      users.
      Publish and distribute new policies/procedures and
O25
      provide appropriate forms.
      Train end-users in the use of the Organization
      Module.
O26


O27   Train end-users in report generation.
      Determine hardware and equipment needs for offices
O28
      needing access to forms.
O29   Wire offices and test equipment.
      Organization Module in production.



O30




      Module Post Implementation Assessment


O31




                     Constituent Task Log
     Review current policies and procedures relative to
     maintenance of constituent information.


P1




     Review Constituent Module forms and determine
P2   appropriate usage.

     Determine how Constituent data will be maintained
P3   and tracked in Banner.

     Determine appropriate values for validation forms
     needed to support intended processing.
P4


     Determine procedures for record updates as
     Constituent data changes or new data is obtained.
P5



     Determine procedures for record updates as
     Constituent data changes or new data is obtained.
P6



     Revise current policies and prepare new policies as
P7
     needed.
      Determine need for and usage of paper forms used to
      collect Constituent data or support processing. Gather
P8
      and annotate any preprinted forms used.

      Determine which pre-printed forms will be required
P9
      after conversion to Banner.
      Review Constituent Module reports and processes.
      Determine any required revisions and need for new
P10
      reports.

      Determine and define interface requirements.
P11

      Obtain necessary approvals for new policies,
P12
      procedure revisions, reports, and special forms.
P13   Design and order new/revised forms.
      Enter validation form values. Verify entered values
P14
      and test on forms.
      Write specifications for report revisions, new reports,
P15
      and required interfaces.
P16   Write and test revised/new reports and interfaces.
      Obtain user sign-off on revised/new reports and
P17
      interfaces.
      Determine table and process level security for users
P18   needing access to Constituent Module forms and
      reports.
      Grant table access and set up process level security
P19
      for users.
      Determine Constituent conversion scope and process.




P20




P21   Write and test conversion programs.
P22   Convert Constituent data.
P23   Verify and correct Constituent data.
      Write user procedures reflecting Banner usage and
P24   new policies and procedures for Constituent Module
      users.
      Publish and distribute new policies/procedures and
P25
      provide appropriate forms.
      Train end-users in the use of the Constituent Module.

P26
P27   Train end-users in reporting tools
      Determine hardware and equipment needs for offices
P28
      needing access to forms.
P29   Wire offices and test equipment.
P32   Constituent Module in production.
      Module Post Implementation Assessment


P33




                Population Selection Task Log
      Read and review related info in User and Technical
PS1
      Manual
      Review the Pop Sel. forms for appropriate use




PS2




      Identify all populations that you would need to
PS3   separate from the overall group, in English (for
      reporting, tracking, letters, etc)
PS4   Build rules in TRNG for all populations
PS5   Ensure all jobs with this module work in TRNG
PS6   Build rules in TEST for all populations
PS7    Ensure all jobs with this module work in TEST
PS8    Build rules in PROD for all populations.
PS9    Determine security for each form/job in module.
       Establish grants/permissions
PS10
       Develop policies and procedures


PS11



     Determine procedure for maintenance of
PS12 validation/rules forms during implementation, during
     production and for each new aid year.
     Develop plan of action for training end user staff
PS13
       Train End Users
PS14


     Determine current information in legacy system that is
PS15 not provided for in Banner and determine procedures
     w/in Banner

                Solicitor Organization Task Log
     Review current policies and procedures relative to
     maintenance of Solicitor Organization data.




S1




     Review Solicitor Organization Module forms and
     determine appropriate usage.
S2


     Determine how Solicitor Organization data will be
S3
     maintained and tracked in Banner.
     Determine appropriate values for validation forms
     needed to support intended processing.
S4


     Determine procedure for maintaining validation forms
S5
     that will be used.
     Determine procedures for record updates as Solicitor
S6
     Organization data is added or changed.
     Revise current policies and prepare new policies as
S7
     needed.
     Determine need for and usage of paper forms used to
     collect Solicitor Organization data or support
S8
     processing. Gather and annotate any pre-printed
     forms.
      Determine which pre-printed forms will still be
S9
      required after conversion to Banner.
      Review Solicitor Organization Module reports and
S10   processes. Determine any required revisions and
      need for new reports.
S11   Determine and define interface requirements.
      Obtain necessary approvals for new policies,
S12
      procedure revisions, reports, and special forms.
S13   Design and order new/revised forms.
      Enter validation form values. Verify entered values
S14
      and test on forms.
      Write specifications for report revisions, new reports,
S15
      and required interfaces.
S16   Write and test revised/new reports and interfaces.
      Obtain user sign-off on revised/new reports and
S17
      interfaces.
      Determine table and process level security for users
S18   needing access to Solicitor Organization Module
      forms and reports.
      Grant table access and set up process level security
S19
      for users.
      Determine Solicitor Organization conversion scope
      and process.
S20


S21   Write and test conversion programs.
S22   Convert Solicitor Organization data.
S23   Verify and correct Solicitor Organization data.
      Write user procedures reflecting Banner usage and
S24   new policies and procedures for Solicitor Organization
      Module users.
      Publish and distribute new policies/procedures and
S25
      provide appropriate forms.
      Train end-users in the use of the Solicitor
      Organization Module.
S26


S27   Train end-users in report generation
      Determine hardware and equipment needs for offices
S28
      needing access to forms.
S29   Wire offices and test equipment.
S30   Solicitor Organization Module in production.
      Module Post Implementation Assessment


S31




                 Technical & Systems Task Log
T1    Establish implementation team.
T2    Establish test system.
T3    Establish training/testing facility.
      Determine terminal configurations. Generate
T4    Function Key reference chart depending upon
      terminal configuration.
      Develop documentation distribution list and plan for
T5    reproduction, distribution, and updating manuals

      Distribute training manuals
T6

      Establish grants, user IDs, passwords, and form
T7
      security for training purposes
      Determine operating system/Banner log-in
T8
      procedures.
T9    Establish operations procedures.
T10   Establish backup and restore procedures.
T11   Establish disaster recovery procedures.
      Establish procedures for system maintenance:
T12
      ORACLE Operating System Banner
      Develop and publicize procedures for reporting
T13
      ORACLE errors.
      Develop and publicize procedures for reporting
T14
      Banner errors.
      Secure SCT training agendas, confirm dates and
      participants, schedule use of training facility, distribute
T15
      agenda to key administrators and participants

      Develop institutional task log and implementation
T16
      schedule
      Determine authority and responsibility for
T17
      maintenance of system security.
      Determine hardware requirements for production
T18   system (terminals, printers, modems, controllers, tape
      drives, etc.).
T19   Acquire necessary hardware.
      Establish Conversion Plan: Decide what data is to be
      converted and how and it what order Evaluate data
      to be converted. Make corrections, if necessary
      Write conversion programs or data entry instructions
T20
      for manual conversions Test conversion programs
      or manual instructions (in stages) Verify
      conversions in production system

      Determine disk requirements for production systems.
T21
T22   Create and size production environment
      Develop change control logging procedures for site-
T23
      specific enhancements.
      Develop procedures for production migration (initial
T24   install, stage tapes, site-specific enhancements, etc.)

      Establish grants, user IDs, passwords, form security
T24
      for production operation
      Consider public relations functions. Plan for
T26   notifications to CWS and employees regarding
      implementation of new system.
      Develop an operation‟s production schedule for all
T27
      batch jobs that will be run on a regular basis.
      Establish databases and uses e.g. TRNG, TEST,
      PPRD, PROD
T28


      Establish Banner Documentation link in Database
T29
      (load documentation library)
      Establish default temporary location for Job
T30
      Submission output (local drive)
Comments



Review how
memberships are
tracked, what information
is stored, membership
acknowledgement
process, membership
reminder and renewal
process, third party
memberships,
membership adjustment
policies, cashiering,
interface to finance.


Review required forms
and values and
determine their use.
Review interface to
Banner Finance System
or need to write interface
to other finance system.
Consider which records
and data elements to
convert, pre-conversion
data correction
requirements, and
conversion verification
and correction process.
Identification, constituent
and organization records
must exist before
membership records can
be created. Valid
memberships,
categories, and interests
must exist before
converting memberships.
Membership, interest,
and payment information
must balance.
For membership renewal
and reminders, an
address type is required.
Expiration date must
exist for membership.
Consider how co-
memberships will be
converted.
Navigation and General
Person Module training
will also be required
unless previously
provided.




Constituent and
Organization must
already be in production
or go into production at
the same time as the
Membership Module.
The Cashiering forms of
the Gift and Pledge
Payment Module may
also be needed to go into
production with the
Membership Module.
Determine the
implementation success.
Measure how the
functionality meets the
needs of the users.
Include
review of name and ID
change procedures,
maintenance of
addresses, use of holds,
use of comments, offices
to maintain data when
changes are necessary,
etc.

Review required forms
and values and
determine how they will
be used. Review optional
forms and values and
determine whether and
how they will be used.

Pay particular attention to
name searches to reduce
the number of duplicate
records.
Standards for all Banner
data entry of
biographic/demographic
data.
Cross-Functional Team
needed- determine
owner(s)
Cross-Functional Team
needed
Cross-Functional Team
needed

Identify offices involved
in maintaining records
and cut off points, e.g.
Admissions will change
applicants addresses
until they register, than
Registrar does so.
Include
review/preparation of the
following forms: Initial
biographic/demographic
data collection forms
Name and ID change
forms
Address change forms
Telephone number
change forms
Interfaces to consider:
Interface to Human
Resources System
Interface to Alumni
System
Interface to Finance
System (vendor names,
IDs, and addresses)
Interface to Financial Aid
System           Interface
to Student System
Other Systems (list)
Consider which records
and data elements to
convert, pre-conversion
data clean-up efforts,
post-conversion
verification, and
correction process




Navigation training will
also be required. Most
offices on campus will
need training in
appropriate modules.
Train users using new
procedures manual.
Review how fund
accounts are established,
assigned, and related to
finance system.
Review designations
specific to institutional
units - colleges,
departments, divisions.
Review VSE reporting
process.
Review restricted/non-
restricted designations.

Review required forms
and values and
determine their use.
Review optional forms
and values and
determine their use.


Review tables shared by
Banner Finance (if
applicable) and those
used in other modules of
Banner Advancement
Refer to Banner
Advancement Technical
Training Manual chapter
on conversion.
Designation records must
exist before Campaign,
Pledge and Gift
conversion.
Navigation and General
Person Module training
will also be required
unless previously
provided.




The Designation Module
must already be in
production or go into
production at the same
time as Campaign,
Pledge, and Gift/Pledge
Payment Modules.




Review campaign types,
duration, associated
designations, expenses,
solicitation techniques.
Review required forms
and values and
determine their use.
Review optional forms
and values and
determine their use.




Consider data in the
Designation and Solicitor
Organization Modules
used in the Campaign
Module.
Refer to Banner
Advancement Technical
Manual chapter on
conversion.




Navigation and General
Person Module training
will also be required
unless previously
provided.
Determine the
implementation success.
Measure how the
functionality meets the
needs of the users.




Review how gifts are
tracked, what data is
stored, gift
acknowledgement
process, gifts shared by
spouses, non-cash gifts,
gift solicitation process,
gift adjustment policies,
cashiering, interface to
finance system.

Review required forms
and values and
determine their use.
Review optional forms
and values and
determine their use.
Review Pledge/Gift
Adjustment Form and
Prior Years Adjustment
Rule Form.




Review interface to
Banner Finance System
or need to write interface
to other finance system.
Consider interface from
payroll system to Banner
Advancement
Refer to Banner
Advancement Technical
Manual chapter on
conversion.
A unique number must
be created for each gift.
Constituent Organization,
Campaign, and
Designation history
tables must be updated.
Gifts can only be
converted for valid
constituents and
organizations.
Valid campaigns and
designations must exist
before converting gifts.
Campaign, designations,
and Gift/Pledge Payment
amount must balance.
Consider how gifts
shared by spouses will
be converted.
For pledge payments,
pledges must first exist
and payment detail must
be associated with
pledge detail.
Latest and largest gifts
must be created via the
Navigation and General
Person Module training
will also be required
unless previously
provided.




Constituent,
Organization, Campaign,
Designation, Pledge, and
optionally Solicitor
Organization Modules
must already be in
production or go into
production at the same
time as the Gift/Pledge
Payment Module.

Determine the
implementation success.
Measure how the
functionality meets the
needs of the users.
Review how pledges are
tracked, what data is
stored, pledge
acknowledgement
process, pledge reminder
process, pledges shared
by spouses, non-cash
pledges, pledge
solicitation process, and
pledge adjustment
policies.

Review required forms
and values and
determine their use.
Review optional forms
and values and
determine their use.




Review Pledge/Gift
Adjustment Form and
Prior Years Adjustment
Rule Form.
Refer to Banner
Advancement Technical
Manual chapter on
conversion.
A unique number must
be created for each
pledge.
Constituent Organization,
Campaign, and
Designation history
tables must be updated.
Pledges can only be
converted for valid
constituents and
organizations.
Valid campaigns and
designations must exist
before converting
pledges.
Campaign, designations,
and pledge amount must
balance.
Consider how pledges
shared by spouses will
be converted.
Navigation and General
Person Module training
will also be required
unless previously
provided.




Constituent,
Organization, Campaign,
and Designation Modules
must already be in
production or go into
production at the same
time as the Pledge
Module.

Determine the
implementation success.
Measure how the
functionality meets the
needs of the users.
Who will build letters?
Who will identify need for
new letters?
What is letter gen flow?




Run Receipts
Run Acknowledgments
Create A New Letter




Review how prospects
are identified,
researched, and tracked.

Review required forms
and values and
determine their use.
Review optional forms
and values and
determine their use.
Consider which records
and data elements to
convert, pre-conversion
data correction
requirements, and
conversion verification
and correction process.
Identification, constituent
and organization records
must exist before
prospect records can be
created.
The base Prospect
Information Form
requires a reference
code, rating code,
screening code, staff
type and staff code for all
prospects. Consider
confidentiality of prospect
data.
Navigation and General
Person Module training
will also be required
unless previously
provided.




Determine the
implementation success.
Measure how the
functionality meets the
needs of the users.




Include review of
organizations,
corporations,
foundations, and
matching gift companies.
Review data on matching
gift ratios, tax ID
numbers, standard
industry codes, and
contact people.
Review required forms
and values and
determine their use.
Review optional forms
and values and
determine their use.


Consider tables shared
with Banner Student and
those used by other
modules in Banner
Advancement




Include reports needed to
produce pre-printed
forms. Review Banner
label reports.
Refer to Banner
Advancement Technical
Training Manual chapter
on conversion.
Consider which records
and data elements to
convert, pre-conversion
clean-up efforts, post-
conversion verification
and correction process.
ID records must exist
before Organization
records can be created.
Base Organization
records must be created
to convert organizations
correctly. Category
records must exist in
order for organizations to
be converted correctly.
Navigation and General
Person Module training
will also be required
unless previously
provided.




The Organization Module
must already be in
production or go into
production at the same
time as Constituent,
Prospect Management,
Pledge, and Gift/Pledge
Payment.
Determine the
implementation success.
Measure how the
functionality meets the
needs of the users.
Include review of basic
person data, academic,
employment, children,
prospect tracking,
maintenance of on-line
comments, and access to
giving history data,
confidentiality of records.

Review required forms
and values and
determine their use.
Review optional forms
and values and
determine their use.
Review data entry
standards. Consider
records shared with other
Banner Systems.
Consider any changes in
staff assignments and
associated training
requirements resulting
from policy/procedure
revisions.
Consider any changes in
staff assignments and
associated training
requirements resulting
from policy/procedure
revisions.
Include reports needed to
produce any pre-printed
forms. Review Banner
label reports.
Review Banner Student
to Advancement
Interface, if applicable.
Refer to Banner
Advancement Technical
Manual chapter on
conversion.       Consider
which records and data
elements to convert, pre-
conversion data clean-up
efforts, post-conversion
verification, and
correction process.
Identification and
address records must
exist before Constituent
records can be created.
Donor Category Codes
must exist in order for
Constituent records to be
converted correctly.




Navigation and General
Person Module training
will also be required
unless previously
provided.
Determine the
implementation success.
Measure how the
functionality meets the
needs of the users.




Form to review include:
GLISLCT
GLRSLCT
GLIRSLT
GLAEXTR
GLIEXTR
GLRAPPL
GLIAPPL
GLRVRBL
GLIVRBL
GLROBJT
GLIOBJT
Who will write pop
selects?
What will be the testing
process?
What is the process to
request new pop sel?




Create A New Population
Selection Run An
Existing Population
Selection
Include review of how
solicitations are
organized, who solicits
gifts, what techniques are
used, how solicitors are
assigned prospective
donors, how results are
tracked, how solicitors
are associated with
individual campaigns.

Review forms and values
and determine their use.
All forms in this module
are optional.




Review how solicitor
organizations are
associated with
campaigns in the
Campaign Module.
Include reports needed to
produce any pre-printed
forms.




Refer to Banner
Advancement Technical
Manual chapter on
conversion.
Navigation and General
Person Module training
will also be required
unless previously
provided.




Determine the
implementation success.
Measure how the
functionality meets the
needs of the users.




Develop document and
materials repository on
server.
Clone databases if
necessary. Identify
databases used for
training, testing,
conversion testing, etc.
                                                                                Planned                Actual
 ID                          Milestone                          Pre- Owner Start Date End Date   Start Date End Date

                       Applicant Tracking
      Review current policies and procedures relative to
A1
      maintenance of applicant tracking information.
      Determine how applicant tracking data will be
A2
      maintained and tracked in Banner.
      Define Business Process- How function works
A3
      currently/before Banner implementation.
      Define Business Process- Gaps or deficiencies noted.
A4
      Define Business Process- How function might work
A5
      with Banner.
      Perform training exercises provided by SCT
A6
      Consultant.
      Review Applicant Tracking Module Validation and
A7
      Control Forms in light of intended usage.
      Determine appropriate values for Validation and
A8    Control Forms needed to support intended
      processing.
A9    Review current policies.
      Define utilization analysis statistics and weighted
A10   factors by position group.

      Establish applicant status codes for use on Applicant
A11   Info form: PAAAPPL.

      Establish source of applicant for use on Applicant Info
A12   form: PAAAPPL.

      Define requisition status codes for use on the Position
A13   Requisition form: PAAREQU.
      Establish applicant status codes for use on Applicant
A14   Info form: PAAAPPL

      Establish source of applicant for use on Applicant Info
A15   form: PAAAPPL.

      Define requisition status codes for use on the Position
A16   Requisition form: PAAREQU

      Define codes to indication where an applicant learned
A17   about position or institution.

      Define task (job) descriptions.
A18


      Determine hardware and equipment needs for offices
A19
      needing access to forms.
A20   Wire offices and test equipment.
      Determine security for users needing access to
A21
      module forms and reports.
      Determine need and usage of forms currently used to
A22   collect data or support processing. Gather any pre-
      printed forms used.
A23   Determine if forms need to be revised or changed.
      Revise current policies and prepare new policies as
A24
      needed.
      Announce new procedures and provide appropriate
A25
      forms for data collection.
      Determine if additional reporting or interfaces are
A26
      required. Internal and External.
      Develop reports and interface specifications, if
A27
      needed.
A28   Write and test revised/new reports and interfaces.
      User sign-off on revised/new reports and interfaces.
A29
      Determine if system enhancements/modifications are
A30
      necessary
      Develop enhancements/modification specifications, if
A31
      needed.
      User sign-off on system enhancements/modifications.
A32
      Determine conversion scope and process. Manual vs.
      electronic




A33




A34   Convert data or manually enter information.
      Verify and correct data. Create reports to review
A35
      information.
      Write user procedures, reflecting Banner usage and
A36
      new policies and procedures.
      Train end-users in the use of the module


A37
A38   Train end-users in reporting tools
      Grant table access and form security for users
A39
      needing access to module forms and reports.
A40   Applicant Tracking Module in production.
      Module Post Implementation Assessment


A41




                             Benefits
      Review current policies and procedures relative to
B1
      maintenance of benefits information.
      Determine how benefits data will be maintained and
B2
      tracked in Banner.
      Define Business Process- How function works
B3
      currently/before Banner implementation.
      Define Business Process- Gaps or deficiencies noted.
B4
      Define Business Process- How function might work
B5
      with Banner.
      Perform training exercises provided by SCT
B6
      Consultant.
      Review Benefits Module Validation and Control Forms
B7
      in light of intended usage.
      Determine appropriate values for Validation and
B8    Control Forms needed to support intended
      processing.
B9    Review current policies.
      Use benefits codes to establish benefit packages and
B10
      assign them to specific employee categories.
      Establish benefit/deduction codes and associates
B11   them with various rule combinations.

      Set up for Benefits/Deduction Mass Changes
B12


      Establish codes that identify the relationship to an
      employee that makes a beneficiary eligible for
B13
      benefits.

      Chain related deductions to a primary deduction.

B14


      Data Map with 3rd Party Interfaces such as WinStar


B15



      Define Benefit/Deduction types.
B16


      Determine hardware and equipment needs for offices
B17
      needing access to forms.
B18   Wire offices and test equipment.
      Determine security for users needing access to
B19
      module forms and reports.
      Determine need and usage of forms currently used to
B20   collect data or support processing. Gather any pre-
      printed forms used.
B21   Determine if forms need to be revised or changed.
      Revise current policies and prepare new policies as
B22
      needed.
      Announce new procedures and provide appropriate
B23
      forms for data collection.
      Determine if additional reporting or interfaces are
B24
      required. Internal and External.
      Develop reports and interface specifications, if
B25
      needed.
B26   Write and test revised/new reports and interfaces.
      User sign-off on revised/new reports and interfaces.
B27
      Determine if system enhancements/modifications are
B28
      necessary
      Develop enhancements/modification specifications, if
B29
      needed.
      User sign-off on system enhancements/modifications.
B30
      Determine conversion scope and process. Manual vs.
      electronic




B31




B32   Convert data or manually enter information.
      Verify and correct data. Create reports to review
B33
      information.
      Write user procedures, reflecting Banner usage and
B34
      new policies and procedures.
      Train end-users in the use of the module


B35



B36   Train end-users in reporting tools
      Grant table access and form security for users
B37
      needing access to module forms and reports.
B38   Benefits Module in production.
      Module Post Implementation Assessment


B39



      COBRA Processing
      Establish COBRA plan selections and charges.
B40

      Establish COBRA eligibility rules.
B41

      Define flexible benefits plans and amounts.
B42
      Define default of the control benefit period and
B43   overage/underage codes.

      Identify the statuses claimable for leaves under the
B44
      FMLA.
      Identify reasons for taking family medical leave.
B45

      Establish and control benefits periods for Flexible
      Spending Accounts & benefit codes for those
B46
      accounts. (Use only if not using PTRFBEN &
      PTRFLEX.)
      Specify how many times a life insurance premium
B47   deduction is taken in a given month.

      Establish salary guidelines for use in determining
B48   amount of life insurance coverage.
      Establish Taxable Life Insurance Rules
B49


      Establish parameters referenced by the Life
      Insurance Calc Process (PDPLIFE)
B50


      Define life insurance deduction codes and associates
B51   them with coverage parameters.

      Establish age-adjusted life insurance premium
B52   amounts and associates them with defined deduction
      codes.
B53   COBRA benefits in production

                Biographic & Demographic Data
      Review current policies and procedures relative to
BD1   maintenance of biographic & demographic
      information.
      Determine how biographic & demographic data will be
BD2
      maintained and tracked in Banner.
      Define Business Process- How function works
BD3
      currently/before Banner implementation.
      Define Business Process- Gaps or deficiencies noted.
BD4
      Define Business Process- How function might work
BD5
      with Banner.
      Perform training exercises provided by SCT
BD6
      Consultant.
      Review General Person Module Validation and
BD7
      Control Forms in light of intended usage.
     Determine appropriate values for Validation and
BD8 Control Forms needed to support intended
     processing.
BD9 Review current policies.
     Define district division codes assigned to employees
BD10 on PEAMPLE and to campuses on STVCAMP.

       Define Zip Codes.


BS11




       Define certification codes.
BD12

     Establish employer type codes for use in the
BD13 Experience Information Block of PPAEXPR.

       Define in-house ethnic codes and links them with
       federally defined ethnic categories for EEO reporting.


BD14




       Establish examination codes and associates them
BD15
       with descriptions and grade requirements.
       Define skill codes and competence levels.
BD16
       Associate competence levels with the skill codes
BD17
       defined in the Skill codes Rule Form (PTRSKIL).
       Define Disability accommodations.
BD18


       Define comment codes.
BD19

       Defines codes for academic disciplines. (Not shared
       with Banner Student).
BD20


     Define endorsement codes for use in specifying
BD21 certifying agencies on PPACERT.

       Define Drivers/CDL, etc. license codes
BD22


     Define publication codes for use in the Publications
BD23 window of the General Information Form.

       Define Disability Accommodation Status codes.
BD24


     Determine hardware and equipment needs for offices
BD25
     needing access to forms.
BD26 Wire offices and test equipment.
     Determine security for users needing access to
BD27
     module forms and reports.
       Determine need and usage of forms currently used to
BD28   collect data or support processing. Gather any pre-
       printed forms used.
BD29   Determine if forms need to be revised or changed.
       Revise current policies and prepare new policies as
BD30
       needed.
       Announce new procedures and provide appropriate
BD31
       forms for data collection.
       Determine if additional reporting or interfaces are
BD32
       required. Internal and External.
       Develop reports and interface specifications, if
BD33
       needed.
BD34   Write and test revised/new reports and interfaces.
       User sign-off on revised/new reports and interfaces.
BD35
     Determine if system enhancements/modifications are
BD36
     necessary
     Develop enhancements/modification specifications, if
BD37
     needed.
     User sign-off on system enhancements/modifications.
BD38
       Determine conversion scope and process. Manual vs.
       electronic




BD39




BD40 Convert data or manually enter information.
     Verify and correct data. Create reports to review
BD41
     information.
     Write user procedures, reflecting Banner usage and
BD42
     new policies and procedures.
     Train end-users in the use of the module
BD43


BD44 Train end-users in reporting tools
     Grant table access and form security for users
BD45
     needing access to module forms and reports.
BD46 General Person Module in production.
BD47 Module Post Implementation Assessment
     Determine and define shared tables with other
     modules.
BD48
     Maintain county codes. Shared with other Banner
BD49 systems. May be used for HRIS reporting.

     Define academic degree codes. Shared with other
BD50 Banner Student.

     Define level codes and associates them with
BD51 academic degrees. Shared with Student.

       Define language codes. Shared with Student.
BD52

     Define codes that identify and describe a relationship
BD53 (e.g., to an alumnus or a current employee). Shared
     with Student
     Define academic major, minor, and concentration
     codes. Shared with Student.
BD54


     Define codes that identify and describe medical
BD55 equipment. Shared with Student.

     Define codes that identify and describe medical
BD56 conditions. Shared with Student.

       Establish marital status codes. Shared with Student.
BD57

       Establish nation codes. Shared with Student.
BD58
     Establish port of entry codes for visa data. Shared
BD59 with Student

       Establish religion codes. Shared with Student
BD60

     Establish relation codes for use in emergency contact
BD61 information. Shared with Student.

       Establish codes to identify education systems (high
       schools, colleges). Shared with Student.
BD62


       Establish State codes. Shared with all products
BD63

     Establish telephone number classifications. Shared
BD64 with Student.

     Establish codes for visa types and associates them
BD65 with descriptions and administrative data. Shared
     with Student. Important for HRIS reporting.

                         California Solutions
       Establish methods for calculating pension credit for
       different California pensions.
CA01


     Establish the range of earnings that is excluded in the
CA02 California pension credit calculation.
       SIRS transaction codes for California reporting
CA03


       Establish the SIRS assignment codes for California
       reporting
CA04



                       Canadian Solutions
       Establish department codes for Canada reporting.
CD1

       Establish non-residence codes for Canada reporting.
CD2


       Establish termination reason codes for Canada
CD3    reporting.

       Establish Faculty Type codes for Canada reporting.
CD4


       Establish Employment Type codes for Canada
       reporting.
CD5


       Establish Faculty-FT codes for Canada reporting.
CD6
       Establish Faculty-PT codes for Canada reporting.
CD7


       Establish Category codes for Canada reporting.
CD8


       Maintain grouping codes for Canada reporting.
CD9


       Maintain data elements for Canada reporting
CD10

     Maintain electronic transmittal rules for T4/T4A
CD11 reporting.


                       Committee Values
       Maintain Committee Members role codes.
CV1


       Maintain Committee/Service status codes
CV2


       Maintain Committee/Service type codes.
CV3
                    Compensation Values
     Establish compensation points for use on the Job
C1   Points Factor Assignment form: PEAJFAC.

     Establish job activity codes.
C2

     Establish job change type codes.
C3


                           EEO Values
     Establish salary levels as defined by the US Feds for
     EEO purposes.
E1


     Maintain information on a specified location within a
     parent company.
E2



     Establish job change type codes.
E3

     Maintain information about schools for the EEO-5
E4
     reporting.
     List ethnic categories specified by the US federal
     government for use in EEO/IPEDS reporting.
E5
      List EEO contract group codes as defined by the US
      Federal government.
E6


      Define EEO skill codes as defined by the US federal
      government.
E7



                  Employee Relations Values
      Establish Extended Bargaining Unit status codes
ER1


      Maintain Location Codes
ER2

      Establish union locations for use on the PEABARG
ER3
      Define union and bargaining unit codes.
ER4

      Define the type of Bargaining Unit contract.
ER5


      Establish Seniority Adjustment codes.
ER6



                          Employment
       Review current policies and procedures relative to
EM1
       maintenance of employment information.
       Determine how employment data will be maintained
EM2
       and tracked in Banner.
       Define Business Process- How function works
EM3
       currently/before Banner implementation.
       Define Business Process- Gaps or deficiencies noted.
EM4
       Define Business Process- How function might work
EM5
       with Banner.
       Perform training exercises provided by SCT
EM6
       Consultant.
       Review Employment Module Validation and Control
EM7
       Forms in light of intended usage.
       Determine appropriate values for Validation and
EM8    Control Forms needed to support intended
       processing.
EM9    Review current policies.
       Determine hardware and equipment needs for offices
EM10
       needing access to forms.
EM11   Wire offices and test equipment.
       Determine security for users needing access to
EM12
       module forms and reports.
       Determine need and usage of forms currently used to
EM13   collect data or support processing. Gather any pre-
       printed forms used.
EM14   Determine if forms need to be revised or changed.
       Revise current policies and prepare new policies as
EM15
       needed.
       Announce new procedures and provide appropriate
EM16
       forms for data collection.
       Determine if additional reporting or interfaces are
EM17
       required. Internal and External.
     Develop reports and interface specifications, if
EM18
     needed.
EM19 Write and test revised/new reports and interfaces.
     User sign-off on revised/new reports and interfaces.
EM20
     Determine if system enhancements/modifications are
EM21
     necessary
     Develop enhancements/modification specifications, if
EM22
     needed.
     User sign-off on system enhancements/modifications.
EM23
       Determine conversion scope and process. Manual vs.
       electronic




EM24




EM25 Convert data or manually enter information.
     Verify and correct data. Create reports to review
EM26
     information.
     Write user procedures, reflecting Banner usage and
EM27
     new policies and procedures.
       Train end-users in the use of the module


EM28



EM29 Train end-users in reporting tools
     Grant table access and form security for users
EM30
     needing access to module forms and reports.
EM31 Employment Module in production.
     Module Post Implementation Assessment


EM32



       Define performance review codes.
EM33

     Establish the rules for the Employee Statistics Annual
     Salary Query Form (PEISTAN) to calculate the
EM34
     Projected Stats Annual Salary.

     Define earnings codes that should be excluded in the
     reporting of Assignment Total Hours and Assignment
EM35
     Total Payment during the extract process.

       Define the factors used at your site in calculating total
       annual salary.
EM36



                        Faculty Information
      Define faculty type rules.
FC1
      Define faculty rank rules.
FC2
      Define tenure codes and associate them with rules
FC3
      specifying tenure eligibility and status.
      Define faculty action comment codes.
FC4


      Define EEO rank codes as defined by the US federal
      government.
FC5


      Define sabbatical type codes.
FC6


                   Finanace Shared Values
      Establish Account codes.
FS1
      Establish Bank codes
FS2
      Establish Chart of Account codes
FS3
      Establish Fiscal Year codes.
FS4

      Establish Operating Budget codes.
FS5
       Establish Organization codes.
FS6

       Establish Program codes.
FS7
       Establish Fund codes.
FS8
       Establish Rules Class codes.
FS9
       If Banner Finance is installed, you do not need to use
       this form.
FS10



                 General System Shared Values
       Establish Call List codes.
GS1
       Establish Letter codes
GS2
       Establish Paragraph codes
GS3
       Establish Print codes.
GS4
       Establish System Indicator codes.
GS5

       Configure/Change menus to suit institution‟s
GS6
       preference.
       Configure/Change menus to suit user‟s preference.
GS7


                        Grievance Values
      Define grievance participant type codes.
GV1


      Establish grievance standard results codes.
GV2


      Establish grievance type codes.
GV3

      Establish codes identifying the administrative status of
GV4   a grievance or a health and safety incident.

      Establish codes identifying the status of health and
GV5   safety incident litigation.


                     Health & Safety Values
      Define hazard codes for use on the Health and Safety
HS1   Incident Form: PEAHSIN.

      Defines incident location codes for use on the Health
HS2   & Safety Incident Form: PEAHSIN.

      Define medical codes for use on the Health & Safety
HS3   Incident form: PEAHSIN.

      Define disability codes and descriptions
HS4
       Establish reason codes for associated health and
       safety expenses.
HS5


       Establish codes identifying location types of health
       and safety incidents.
HS6


       Establish health and safety medical type codes as
       defined by OSHA.
HS7


       Establish codes identifying party types of persons
HS8    involved in health and safety incidents.

       Establish Incident type codes.
HS9


       Establish codes identifying precautions that should be
       taken against health and safety hazards.
HS10


       Establish health and safety hazard types.
HS11

     Establish manufacturer codes for use in the Hazard
HS12 Block in PTRHAZD.
       Establish recommendation codes for use with health
       and safety incident claims.
HS13



                              Payroll
       Review current policies and procedures relative to
P1
       maintenance of payroll information.
       Determine how payroll data will be maintained and
P2
       tracked in Banner.
       Define Business Process- How function works
P3
       currently/before Banner implementation.
       Define Business Process- Gaps or deficiencies noted.
P4
       Define Business Process- How function might work
P5
       with Banner.
       Perform training exercises provided by SCT
P6
       Consultant.
       Review Employment Module Validation and Control
P7
       Forms in light of intended usage.
       Determine appropriate values for Validation and
P8     Control Forms needed to support intended
       processing.
P9     Review current policies.
       Define bank codes for direct deposits.
P10
       Define Bank Routing codes
P11

       Define payroll calendar for use in the payroll process.
P12
      Establish deferred pay period rule codes.
P13

      Define earnings codes and associates them with rules
P14

      Define when to default holiday pay into the payroll by
P15   employee class.

      Define institution specific data such as name and
P16
      address, and data for EEO IPEDS reporting.
      Establish job location codes for use on NBAJOBS.
P17
      Define job change reason codes for NBAJOBS.
P18

      Define a set of leave types available to a specified
P19
      group of employees.
      Establish longevity premium pay parameters for a
P20   specified longevity code.

      Define leave reason codes, describe the associated
P21   leave, specify the leave pay and benefit status, and
      indicate COBRA eligibility.
      Establish assignments, computations, and eligible
P22   earnings data for premium pay.

      Define payroll ID codes, describe the associated
P23   payroll, and specify its tax factor and number of pays
      per year.
      Establish premium pay codes and associate them
P24   with base date indicators.
      Specify earnings codes, rates, and retroactive pay
      periods by employee class for use during retroactive
P25
      pay processing.

      Establish deductions to be taken during a
      supplemental payroll for employees in a specified
P26
      benefit category. Used for overloads and bonuses by
      employee class.
      Establish the earn codes to be defaulted during a
      supplemental payroll for a specific employee class.
P27


      Define shift premiums within a specified shift code.
P28
      Define termination codes.
P29

      Establish work periods in accordance with the Fair
P30
      Labor Standards Act.
      Maintain the distribution codes used for 1099-R
P31   reporting.

      Assign codes to logical groups of earnings codes.
P32


      Establish leave category codes
P33

      Establish longevity codes for use in computing
P34   longevity premium pay.
      Establish premium pay category codes.
P35


      Define shift codes.
P36

      Establish workers comp classification codes and
      descriptions
P37


      Determine hardware and equipment needs for offices
P38
      needing access to forms.
P39   Wire offices and test equipment.
      Determine security for users needing access to
P40
      module forms and reports.
      Determine need and usage of forms currently used to
P41   collect data or support processing. Gather any pre-
      printed forms used.
P42   Determine if forms need to be revised or changed.
      Revise current policies and prepare new policies as
P43
      needed.
      Announce new procedures and provide appropriate
P44
      forms for data collection.
      Determine if additional reporting or interfaces are
P45
      required. Internal and External.
      Develop reports and interface specifications, if
P46
      needed.
P47   Write and test revised/new reports and interfaces.
      User sign-off on revised/new reports and interfaces.
P48
      Determine if system enhancements/modifications are
P49
      necessary
      Develop enhancements/modification specifications, if
P50
      needed.
      User sign-off on system enhancements/modifications.
P51
      Determine conversion scope and process. Manual vs.
      electronic




P52




P53   Convert data or manually enter information.
      Verify and correct data. Create reports to review
P54
      information.
      Write user procedures, reflecting Banner usage and
P55
      new policies and procedures.
      Train end-users in the use of the module


P56



P57   Train end-users in reporting.
      Grant table access and form security for users
P58
      needing access to module forms and reports.
P59   Payroll Module in production.
      Module Post Implementation Assessment


P60



      Payroll Check Printing Tasks




      Define Business Process- How function will work with
P61
      Banner.
P62   Investigate paper options.
P62   Investigate printer options.
P63   Establish printers in Banner.
      Conduct Payroll parallel test.




P65




P66   Evaluate payroll results and make corrections.
      Set up specific routing for Time Entry with Approvals
P67

      Define the Shift Codes available for
P68   Web/Departmental time entry purposes.

      Define shift codes usable on Web/Departmental time
P69   entry.


                             Position
      Review current policies and procedures relative to
PT1
      maintenance of position information.
      Determine how position data will be maintained and
PT2
      tracked in Banner.
      Define Business Process- How function works
PT3
      currently/before Banner implementation.
       Define Business Process- Gaps or deficiencies noted.
PT4
       Define Business Process- How function might work
PT5
       with Banner.
       Perform training exercises provided by SCT
PT6
       Consultant.
       Review Employment Module Validation and Control
PT7
       Forms in light of intended usage.
       Determine appropriate values for Validation and
PT8    Control Forms needed to support intended
       processing.
PT9    Review current policies.
       Define Job Progression families.
PT10

       Create position class and associates it with salary
       guidelines, employee class, and employee skill level.

PT11



       Define rules for salaries or hourly rates.
PT12
     Define active and inactive salary groups for each
PT13
     table.
     Establish the parameters used on the Mass Salary
PT14 Update Process to roll data from one salary group to
     another.
     Establish work schedules: day/shift/hours.
PT15
       Identify Dictionary of Occupational Titles.


PT16



       Define Job Progression families
PT17

       Identify Federal Occupational Code records.
PT18

       Identify Federal Occupational Code records.
PT19

       Identify National Occupational Code records.
PT20


       Define work schedule codes.
PT21

     Establish position group codes and associated
PT22 descriptions and salary indicators.

     Determine hardware and equipment needs for offices
PT23
     needing access to forms.
PT24 Wire offices and test equipment.
     Determine security for users needing access to
PT25
     module forms and reports.
       Determine need and usage of forms currently used to
PT26   collect data or support processing. Gather any pre-
       printed forms used.
PT27   Determine if forms need to be revised or changed.
       Revise current policies and prepare new policies as
PT28
       needed.
       Announce new procedures and provide appropriate
PT29
       forms for data collection.
       Determine if additional reporting or interfaces are
PT30
       required. Internal and External.
       Develop reports and interface specifications, if
PT31
       needed.
PT32   Write and test revised/new reports and interfaces.
       User sign-off on revised/new reports and interfaces.
PT33
     Determine if system enhancements/modifications are
PT34
     necessary
     Develop enhancements/modification specifications, if
PT35
     needed.
     User sign-off on system enhancements/modifications.
PT36
       Determine conversion scope and process. Manual vs.
       electronic




PT37




PT38 Convert data or manually enter information.
     Verify and correct data. Create reports to review
PT39
     information.
     Write user procedures, reflecting Banner usage and
PT40
     new policies and procedures.
     Train end-users in the use of the module


PT41



PT42 Train end-users in reporting.
     Grant table access and form security for users
PT43
     needing access to module forms and reports.
PT44 Position Module in production.
       Module Post Implementation Assessment


PT45




                     Security & Installation
       Security Tasks
       Define employee class security.
S1

       Define employer security.
S2

       Define organization level security.
S3

       Establish user Ids and security profiles based on: max
S4     salary level, Employer, Org, and Employee Class.

       Installation Tasks
       Define two fields of concern to HR: Default # of digits
I1     on Zip Code (e.g., 5 or 9), and Century Pivot Point
       (age determining 19XX or 20XX default).
       Turn on electronic approvals, set flag for “super user,”
I2     and set job detail insertion rule.

       SQL Change Pivot Date to 30. Delivered value too
       high for HR use.
I3
      Review settings on the Crosswalk Table. Used
I4    primarily for Object:Access but also in Payroll/W2
      processing.

                            System
      Review conversion of data – Assignments
SY1
      (NBAJOBS, etc.)
SY2   Review conversion of data – Deductions
      Review conversion of data – Direct Deposit Accounts
SY3
      Review conversion of data – Employee (PEBEMPL,
SY4
      etc.)
      Review conversion of data – General Person
SY5
      Information
      Review conversion of data – Position Control and
SY6
      Labor Budget
      Review conversion of data – Totals – 1042S Totals
SY7
SY8  Review conversion of data – Totals – Deduction
     Review conversion of data – Totals - Defer Pay
SY9
     Balances
SY10 Review conversion of data – Totals - Earnings
     Review conversion of data – Totals - Leave Balances
SY11
     Develop the process and type of documentation that
SY12 will be provided to the End User. Local Help? Who
     will administrate and update?
     Load all User/Process Notes. Structure these notes
SY13
     to allow for future upgrades.
     Place documentation on Web to allow team members
SY14
     access when off-site.
     At Go Live, (after conversion) drop data conversion
SY15 users SCTCVT and SCTCVT1 to automatically drop
     unnecessary constraints.
     Re-index and re-size system- after building Pre-
SY16
     Production instance and deleting data.
     Re-index and re-size system- before Load Testing.
SY17
SY18 Re-index and re-size system- At Pre-Production.
SY19 Re-index and re-size system- at Production.
     Develop a method and process to purge old (3 days?)
SY20 files of reports/processes produced by GJAPCTL.


                       Tax Administration
      Establish tax report codes for entry on the Tax Rule
      form.
TX1


      Define and maintain rules for the calculation of taxes
TX2   processed in the tax module.

      Associate filing status information with a specified tax
TX3   code.

      Define rules for electronic processing.
TX4

      Define tax reporting rules.
TX5
      Establish calculation and exemption parameters for a
TX6   specified tax (wage brackets and tax percentages).
       Establish tax code rules.
TX7
       Test Tax Remittance system
TX8
       Verify Tax Remittance
TX9
TX10   Run Process for W2
TX11   Verify W2
TX12   Run Process for 1042s
TX13   Verify 1042s
TX14   Run 941 by quarter
TX15   Run 941 inclusive of all quarters
TX16   Reconcile 941 to W2
Tx17   Tax processing in production.

                        Technical & System
T1     Establish implementation team.
T2     Establish test system.
T3     Establish training/testing facility.
       Determine terminal configurations. Generate
T4     Function Key reference chart depending upon
       terminal configuration.
       Develop documentation distribution list and plan for
T5     reproduction, distribution, and updating manuals

       Distribute training manuals
T6

       Establish grants, user IDs, passwords, and form
T7
       security for training purposes
       Determine operating system/Banner log-in
T8
       procedures.
T9     Establish operations procedures.
T10   Establish backup and restore procedures.
T11   Establish disaster recovery procedures.
      Establish procedures for system maintenance:
T12
      ORACLE; Operating System; Banner
      Develop and publicize procedures for reporting
T13
      ORACLE errors.
      Develop and publicize procedures for reporting
T14
      Banner errors.
      Secure SCT training agendas, confirm dates and
      participants, schedule use of training facility, distribute
T15
      agenda to key administrators and participants

      Develop institutional task log and implementation
T16
      schedule
      Determine authority and responsibility for
T17
      maintenance of system security.
      Determine hardware requirements for production
T18   system (terminals, printers, modems, controllers, tape
      drives, etc.).
T19   Acquire necessary hardware.
      Establish Conversion Plan:
      Decide what data is to be converted and how and it
      what order;
      Evaluate data to be converted. Make corrections, if
      necessary;
T20
      Write conversion programs or data entry instructions
      for manual conversions;
      Test conversion programs or manual instructions (in
      stages);
      Verify conversions in production system
      Determine disk requirements for production systems.
T21
T22   Create and size production environment
      Develop change control logging procedures for site-
T23
      specific enhancements.
      Develop procedures for production migration (initial
T24   install, stage tapes, site-specific enhancements, etc.)

      Establish grants, user IDs, passwords, form security
T24
      for production operation
      Consider public relations functions. Plan for
T26   notifications to CWS and employees regarding
      implementation of new system.
      Develop an operation‟s production schedule for all
T27
      batch jobs that will be run on a regular basis.
      Establish databases and uses e.g. TRNG, TEST,
      PPRD, PROD
T28



      Establish Banner Documentation link in Database
T29
      (load documentation library)
      Establish default temporary location for Job
T30
      Submission output (local drive)
Comments




PTRAFAN -
Availability Factor
Analysis Rule Form
PTRAPPS - Applicant
Status Rule Form

PTRASRC – Applicant
Source Rule Form

PTRAFAN -
Availability Factor
Analysis Rule Form
PTRAPPS - Applicant
Status Rule Form

PTRASRC – Applicant
Source Rule Form

PTRREQS -
Requisition Status
Rule Form
PTVASRC - Applicant
Source Code Valid.
Form
PTVCDES - Position
Class Job Description
Valid. Form
If electronic, write and
test conversion
programs. If manual
gather reports and
spreadsheets with
necessary data.
Determine and
reserve appropriate
labor resources to
complete manual
conversion in
necessary timeframe.




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.




PTRBCAT - Benefit
Category Rule Form
PTRBDCA -
Benefit/Deduction
Rule Form
PTRBDMC –
Benefit/Deduction
Mass Change Rule
Form
PTRBREL -
Beneficiary
Relationship Rule
Form
May not be needed by
Deduction coding.
PTRDCHN -
Benefit/Deduction
Chain Rule Form
PTRFPIN – Foreign
Person Interface Rule
Form PTRTPCD –
Third Party Code Rule
Form

PTVBDTY -
Benefit/Deduction
Type Valid. Rule Form
If electronic, write and
test conversion
programs. If manual
gather reports and
spreadsheets with
necessary data.
Determine and
reserve appropriate
labor resources to
complete manual
conversion in
necessary timeframe.




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.

PTRCBEN - COBRA
Benefit Coverage
Rule Form
PTRCOBR - COBRA
Reason Rule Form

PTRFBEN - Flexible
Benefits Rule Form
PTRFLEX - Flexible
Benefits Period Rule
Form
PTVFMST - FMLA
Status Valid. Form
PTVFREA - FMLA
Leave Reason Valid.
Form
PTRBFSA - Flexible
Spending Accounts
Rule Form

PTRBDFQ - Benefit
Payroll Frequency
Rule Form
PTRCOVR - Life
Insurance Coverage
Rule Form
PTRGTAX - Taxable
Life Insurance
Premium Rules Form

PTRLIFE - Life
Insurance Calc
Process Parameter
Rule Form
PTRLIFI - Life
Insurance Rule Form

PTRPREM - Premium
Rule Form
GTVDICD-- District
Division Validation
Form
Shared with Student &
Finance. Form used
for defaulting City and
State for all Banner
addresses. GTVZIPC -
Zip Code Validation
Form
PTRCERT -
Certification Code
Rule Form
PTREMTY - Employer
Type Code Rule Form

Form linked to
STVETHN in Student.
PTRETHN - Ethnic
Codes Rule Form
(Needs to be
completed in
conjunction with
STVETHN)
PTREXAM - Exam
Code Rule Form
PTRSKIL - Skill
Codes Rule Form
PTRSKLV - Skill
Levels Rule Form
PTVACST –
Accommodation
Status Validation
Form
PTVCMTY - Comment
Code Validation Form

Not shared with
Banner Student.
PTVDISP - Discipline
Code Validation Form

PTVENDS -
Endorsement Code
Validation Form
PTVLCSV –
License/Certification
Status Validation
Form
PTVPUBT -
Publication Code
Validation Form
PTVRQST –
Accommodation
Request Status
Validation Form
If electronic, write and
test conversion
programs. If manual
gather reports and
spreadsheets with
necessary data.
Determine and
reserve appropriate
labor resources to
complete manual
conversion in
necessary timeframe.




Navigation training
will also be required
unless previously
provided.




Modules to consider:
Student System;
Advancement System;
Finance System;
Financial Aid System
STVCNTY - County
Code Validation Form

STVDEGC - Degree
Code Validation Form

STVDLEV - Degree
Level Validation Form

STVLANG -
Language Code
Validation Form
STVLGCY - Legacy
Code Validation Form

STVMAJR -
Major/Minor/Concentr
ation Code Validation
Form
STVMDEQ - Medical
Equipment Code
Validation Form
STVMEDI - Medical
Code Validation Form

STVMRTL - Marital
Status Code
Validation Form
STVNATN - Nation
Code Validation Form
STVPENT - Port of
Entry Validation Form

STVRELG - Religion
Code Validation Form

STVRELT - Relation
Code Validation Form

STVSBGI -
Source/Background
Institution Code Val.
Form
STVSTAT - State
Code Validation Form

STVTELE -
Telephone Type
Validation Form
STVVTYP - Visa Type
Validation Form




PTRPCAL - California
Pension Credit Calc
Rule Form

PTRPCLM California
Pension Credit Limits
Rule Form
PTV87TR - California
STRS MR-87
Transaction Validation
Form
PTVASSN - California
STRS Employee
Assignment Validation
Form



PTRSCDP – Stats
Canada Department
Rule Form
PTVNRSI – Canada
Non-Resident Service
Industry Validation
Form
PTVROER - Canadian
ROE Reason Valid.
Form
PTVSCCT – Stats
Canada Colleges
Faculty Type
Validation Form
PTVSCET – Stats
Canada Employment
Type Validation Form

PTVSCFT - Stats
Canada Full Time
Faculty Type
Validation Form
PTVSCPT - Stats
Canada Part Time
Faculty Type
Validation Form
PTVSTCA – Statistics
Canada Category
Code Valid. Form

PTVSTGR - Statistics
Canada Grouping
Code Validation Form

PXAASCD – Annual
Statistics Canada
Survey Data Form
PXAMTT4 - T4/T4A
Magnetic Tape rule
Form


STVCOMF –
Committee Member
Role/Function
Validation Form
STVCOMS –
Committee/ Service
Status Validation
Form
STVCOMT –
Committee/ Service
Type Validation Form
PTRCFAC -
Compensable Factor
Rule Form
PTVJACT - Job
Activity Code
Validation Form
PTVJCTY - Job
Change Type Code
Validation Form


PTREEOS - EEO
Salary Level Rule
Form (Delivered
values)
Data collected is used
for the EEO-1
Summary Report:
PEREO11
PTRLOCN - EEO1
Location Rule Form
PTVJCTY - Job
Change Type Code
Validation Form
PTRSCHL- School
Rule Form
PTVEEOC - EEO
Ethnic Codes
Validation Form
(Delivered values)
PTVEEOG - EEO
Contract Group
Validation Form
(Delivered values)
PTVESKL - EEO Skill
Code Validation Form
(Delivered values)



PTRBURE –
Bargaining Unit
Relationship Status
Rule Form
PTRLCDE – Location
Code Rule Form

PTRUNLO – Union
Location Rule Form
PTVBARG -
Bargaining Unit
Validation Form
PTVCATY – Contract
and Agreement Type
Validation Form

PTVSARC – Seniority
Adjustment Reason
Code Validation Form
If electronic, write and
test conversion
programs. If manual
gather reports and
spreadsheets with
necessary data.
Determine and
reserve appropriate
labor resources to
complete manual
conversion in
necessary timeframe.
Navigation and
General Person
Module training will
also be required
unless previously
provided.




Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
PTVREVT - Review
Code Validation Form

PTRPSAS - Projected
Statistics Annual
Salary Rule Form

PTRSEHS - Statistics
Earnings History Rule
Form

PTRSTAN - Statistics
Annual Salary
Calculation Rule Form
PTRFTYP – Faculty
Type Rule Form
PTRRANK – Faculty
Rank Rule Form
PTRTENR - Tenure
Code Rule Form
PTVFACC – Faculty
Action Comment
Code Validation Form

PTVRANK - Rank
Code Validation Form
(Delivered values)

PTVSBTY –
Sabbatical Type
Validation Form


FTMACCT - Account
Code List
FTMBANK - Bank
Account Code List
FTMCOAS - Chart of
Accounts List
FTMFSYR - System
Control Fiscal Year
List
FTMOBUD -
Operating Budget List
(Set up a Test Budget
ID)
FTMORGN -
Organization Code
List
FTMPROG - Program
Code List
FTVFUND - Fund
Code List
FTVRUCL - Rule
Class List
PTVORGN -
Organization Code
Valid. Form (if non-
Banner Finance)


GTVCALL – Call List
Code
GTVLETR - Letter
Code
GTVPARA -
Paragraph Code
GTVPTNT - Print
Code
GTVSYSI - System
Indicator Validation
Form
GUTGMNU- Menu
Maintenance Form
GUAPMNU- Personal
Menu Maintenance
Form
PTVGRPT -
Grievance Participant
Type Validation Form

PTVGRSR -
Grievance Standard
Results Validation
Form
PTVGRTP -
Grievance Type
Validation Form
PTVISTA - Incident
Status Validation
Form
PTVLITG - Litigation
Status Validation
Form


PTRHAZD -
Hazardous Materials
Rule Form
PTRHSIL - Health &
Safety Incident
Location Rule Form
PTRHSME - Health &
Safety Medical Codes
Rule Form
PTVDISA - Disability
Status Validation
Form
PTVHSCR – Health &
Safety Cost Reasons
Validation Form

PTVHSLT – Health &
Safety Incident
Location Type
Validation Form
PTVHSMT – Health &
Safety Medical
Condition Type
Validation Form
(Delivered values)
PTVHSPC – Health &
Safety Party Type
Validation Form
PTVHSTC – Health &
Safety Incident Type
Validation Form

PTVHZSP - Hazard
Standard Precautions
Validation Form

PTVHZTC - Hazard
Type Code Validation
Form
PTVMANU -
Manufacturer
Validation Form
PTVRSTA -
Recommendation
Status Validation
Form




GXRBANK – Bank
Code Rule Form
GXVDIRD – Bank
Routing Number
Validation Form
PTRCALN - Payroll
Calendar Rule Form
PTRDFPR - Defer
Pay Period Rule Form

PTREARN - Earnings
Code Rule Form

PTREHOL -
Employee Holidays
Rule Form
PTREMPR - Employer
Rule Form
PTRJBLN - Job
Location Rule Form
PTRJCRE - Job
Change Reason Rule
Form
PTRLEAV - Leave
Codes Rule Form
PTRLGTY - Longevity
Code Rule Form

PTRLREA - Leave
Reason Rule Form

PTRPCAT - Premium
Pay Category Rule
Form
PTRPICT - Payroll
Identification Code
Rule Form
PTRPPAY - Premium
Pay Rule Form
PTRRERN -
Retroactive Pay Earn
Codes Rule Form

PTRSDED -
Supplemental Payroll
Deductions Rule Form

PTRSERN -
Supplemental Payroll
Earn Codes Rule
Form
PTRSHFT - Shift
Premium Rule Form
PTRTREA -
Termination Reason
Rule Form
PTRWKPR - Work
Period Rule Form
PTV1099 – 1099-R
Distribution Code
Validation Form
PTVERGR - Earnings
Group Code
Validation Form

PTVLCAT - Leave
Category Validation
Form
PTVLGCD - Longevity
Code Validation Form
PTVPCAT - Premium
Pay Category
Validation Form

PTVSHCD – Shift
Code Validation Form

PTVWKCP - Workers'
Comp. Classification
Validation Form
If electronic, write and
test conversion
programs. If manual
gather reports and
spreadsheets with
necessary data.
Determine and
reserve appropriate
labor resources to
complete manual
conversion in
necessary timeframe.




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Before payroll can be
implemented, the
Identification Form,
Employee form,
Benefits/Deductions
Form and the Jobs
Form must be
completed.
Test payrolls should
be run several times.
Gross -to Net should
be reviewed as well as
accuracy of benefits
and deductions. This
also includes testing
ALL third party feeds
and interfaces.
Several pays should
be interfaced with
Finance to ensure
correct posting of
expenses.


NTRRQUE – Routing
Queue Rule Form

PTRTESH – Time
Entry Shift Code Rule
Form
PTVTESH – Time
Entry Shift Code
Validation Form
NTRJOBP – Job
Progression Rule
Form
NTRPCLS - Position
Class Rule Form
(NOTE: You must
complete STVCIPC
and PTVESKL before
starting this form.)

NTRSALA - Salary
Rate Rule Form
NTRSGRP - Salary
Group Rule Form
NTRSTRL - Mass
Salary Table Roll Rule
Form
NTRWKSH - Work
Schedule Rule Form
NTVDOTT -
Dictionary of
Occupational Title
Code (DOT)
Validation Form (Not
delivered with seed
data.)
NTVJOBP – Job
Progression Code
Validation Form
NTVJOBP – Job
Progression Code
Validation Form
NTVPFOC - Federal
Occupational Code
(FOC) Val. Form
NTVPNOC - National
Occupational Class
Code (NOC)
Validation Form
NTVWKSH - Work
Schedule Valid. Form

PTRPGRP - Position
Group Rule Form
If electronic, write and
test conversion
programs. If manual
gather reports and
spreadsheets with
necessary data.
Determine and
reserve appropriate
labor resources to
complete manual
conversion in
necessary timeframe.




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.




PSAECLS - Employee
Class Security Form

PSAEMPR - Employer
Security Form

PSAORGN -
Organization Security
Form
PTRUSER - User
Codes Rule Form


GUAINST - Institution
Control Form

NTRINST - Position
Control Installation
Rule Form
GUAINST - Institution
Control Form
(Accomplished by
SCT technical)
GTVSDAX –
Description Table
PTVREPT - Tax
Reporting Code
Validation Form
(Delivered values)
PXACALC - Tax
Calculation Rule Form

PXAFSTA - Tax Filing
Status Rule Form

PXAMTAP - Magnetic
Tape Rule Form

PXAREPT - Tax
Reporting Rule Form
PXATAXS - Tax
Setup Form
PXATXCD - Tax Code
Rule Form
Dependent on
requirements
Dependent on
requirements




Develop document
and materials
repository on server.
Clone databases if
necessary. Identify
databases used for
training, testing,
conversion testing,
etc.
                                                                      Planned
ID                         Milestone                  Pre- Owner Start Date End Date
                 Academic History Task Log
     Review current policies and procedures used in
     processing academic history data.




H1




     Review Academic History Module forms and
     determine appropriate usage.



H2




     Determine how Academic History data will be
H3
     maintained and tracked in Banner.
     Review Academic History Module Validation and
     Control forms in light of intended usage.




H4
      Determine appropriate values for Validation and
H5    Control forms needed to support intended processing.

      Revise current policies and prepare new policies as
H6
      needed.
      Gather and annotate any special forms used.




H7




      Determine which pre-printed forms will still be printed
H8
      using Banner.
      Review Academic History Module reports. Determine
H9    required revisions and need for new reports.

      Determine and define interface requirements.
H10
      Obtain necessary approvals for new policies,
H11
      procedure revisions, reports and special forms.
      Revise forms/prepare new forms.
H12
      Send forms for printing.
H13
      Enter and validate Validation and Control Forms
      values for required data elements.
H14



      Write specifications for report revisions, new reports
H15
      and required interfaces.
      Write and test revised/new reports and interfaces.
H16
      User sign-off on revised/new reports and interfaces.
H17
    Determine table and form security for users needing
H18 access to Academic History Module forms and
    reports.
    Grant table access and form security for users
H19 needing access to Academic History Module forms
    and reports.
    Assign and distribute passwords and permissions to
H20
    Academic History Module users.
    Determine hardware and equipment needs for offices
H21 needing access to Academic History Module forms.

      Wire offices and test equipment.
H22
      Determine Academic History conversion population,
      scope and processes.
H23


      Write and test conversion process.
H24
      Run conversion simulation. Audit data to determine
H25
      that results are correct.
      Perform Academic History conversion.
H26
      Verify data and correct.
H27
      Review sleep/wake processing and determine
      whether it will be used to produce “immediate”
      transcripts.
H28



    Write and test user procedures, reflecting Banner
H29 usage and new policies and procedures, for Academic
    History Module users.

                     Admissions Task Log
     Review current policies, procedures, and activities
     relative to admissions application processing.




A1




     Review Admissions Module forms and determine
     appropriate usage


A2




     Determine how Admissions data will be maintained
A3
     and tracked in Banner.
     Review and determine usage of the Automated
     Decision Calculation and Checklist Processing and
A4   Quick Entry functions and Selective Admissions
     processing in light of intended policies and
     procedures.
     Review and determine the use of the Letter
A5   Generation feature for producing Communication
     Plan, Checklist, Decision, and ad hoc letters.
     Gather and annotate letters to be produced by the
A6   Letter Generation feature. Dissect letters into
     appropriate paragraphs.
     Review Admissions Module Validation and Control
A7
     forms needed to support intended processing.
     Determine appropriate values for Validation and
A8   Control forms needed to support intended processing.
      Determine procedures for record updates as new or
A9
      corrected information is received.
      Determine need and usage of forms used to collect
      application information. Review/revise special forms
      in light of Banner application processing.


A10




      Review Admissions Module reports. Determine
A11
      required revisions and need for additional reports.
      Determine and define interface requirements



A12




      Obtain necessary approvals for new policies,
A13
      procedure revisions, reports and special forms.
A14   Send new forms for printing.
      Enter Validation Forms values. Verify entered values
A15
      and use of forms.
      Build Control Forms for Decision Processing,
A16
      Checklists and Quick Entry. Define letters.
      Write specifications for report revisions, new reports
A17
      and required interfaces.
A18   Write and test revised/new reports and interfaces.
      User sign-off on revised/new reports and interfaces.
A19
    Determine table and form security for users needing
A20 access to Admissions Module forms and reports.

    Grant table and form security for users needing
A21
    access to Admissions Module forms and reports.
    Assign and distribute passwords and permissions to
A22
    Admissions Module users.
      Determine Admissions conversion population and
      process.




A23




A24 Write and test conversion programs.
A25 Convert Admissions records, if desired.
A26 Verify conversion.
    Determine hardware and equipment needs for offices
A27 needing access to Admissions Module forms.

A28 Wire offices and test equipment.
    Write user procedures, reflecting Banner usage and
A29 new policies and procedures, for Admissions Module
    users.
    Announce new procedures and provide appropriate
A30
    forms for data collection.
    Determine a production schedule for letters to
A31
    applicants and admits.
    rain end-users in the use of the Admissions Module


A32



A33 Train end-users in report generation.
      Admissions Module in production.




A34




      Biographic & Demographic Data Entry Task Log

      Review current policies and procedures relative to
      maintenance of the person/non-person data.



D1




      Review biographic & demographic data entry forms
      and determine appropriate usage


D2




      Determine how data will be maintained and tracked in
      Banner
D3
     Develop Data entry Standards Procedures
D4


     Review biographic & demographic data entry forms
D5   and determine appropriate usage.

     Determine appropriate values for Validation Forms
D6
     needed to support intended processing
     Determine procedures for record updates as
D7   additional information and/or changes are received.

     Revise current policies and prepare new policies as
     required.


D8




     Determine need and usage of forms used to collect
     information on new/changed person data. Prepare/
     revise forms in light of Banner values and processing.




D9




    Review biographic & demographic reports. Determine
D10 required revisions and need for additional reports.
      Determine and define interface requirements.




D11




      Obtain necessary approvals for new/revised policies,
D12
      procedures.
      Send new forms for printing.
D13
    Enter Validation Forms values. Verify entered values
D14
    and use of forms.
    Write specifications for report revisions, new reports
D15
    and required interfaces.
    Write and test revised/new reports and interfaces.
D16
    Obtain user sign-off on revised/new reports and
D17
    interfaces.
    Determine table and form security for users needing
D18 access to General Person Module forms and reports.

    Grant table access and set up Form Level security for
D19 users needing access to appropriate forms and
    reports.
    Assign and distribute passwords and permissions to
D20
    appropriate modules
    Determine data conversion scope, process, and
    population (both persons and non-persons)


D21




      Write and test conversion programs.
D22
      Convert person/non-person data.
D23
      Verify conversion.
D24
    Determine hardware and equipment needs for offices
D25 needing access to biographic & demographic forms.

      Wire and test office equipment.
D26
    Write user procedures, reflecting Banner usage and
D27 new policies and procedures, for data entry users.

      Announce new procedures and provide appropriate
D28
      forms for data collection.
      Train end-users in the use of the appropriate system
      module


D29




      Train end-users in report generation.
D30
      Biographic & demographic data entry in production.
D31


                           CAPP Task Log
     Review current policies and procedures used in the
     maintenance of degree programs and processing of
     degree audits.




D1




     Review CAPP forms and determine appropriate
D2
     usage.
     Determine how CAPP data will be maintained and
D3
     tracked in Banner.
     Review CAPP Module Validation forms in light of
D4
     intended usage.
     Determine appropriate values for Validation forms
D5
     needed to support intended processing.
     Define procedure for record updates as program
D6   requirements change and new programs are added.

     Revise current policies and prepare new policies as
D7
     needed.
     Determine need and usage of forms used to collect
     information on new/changed programs. Prepare/
D8
     revise forms in light of Banner values and processing.

    Review CAPP Module reports. Determine required
D9
    revisions and need for new reports.
    Obtain necessary approvals for new policies,
D10
    procedure revisions, reports and special forms.
    Send new forms for printing.
D11
      Enter Validation Forms values. Verify entered values
D12
      and use on forms.
      Write specifications for report revisions, new reports.
D13
      Write and test revised/new reports.
D14
    Determine table and form security for users needing
D16 access to CAPP Module forms and reports.

    Grant table access and form level security for end
D17 users needing access to CAPP Module forms and
    reports.
    Assign and distribute passwords and permissions to
D18
    CAPP Module forms.
    Determine hardware and equipment needs for offices
D19
    needing access to CAPP Module forms.
    Wire offices and test equipment.
D20
    Write user procedures reflecting Banner usage and
D21 new policies and procedures, for CAPP Module users.

      Announce new procedures and provide appropriate
D22
      forms for data collection.
      Train end-users in the use of the CAPP Module.



D23




      Enter Degree Audit program requirements.
D24
      Train end-users in report generation.
D25
      CAPP Module in production.




D26
                       Catalog Task Log
      Review current policies and procedures relative to
      maintenance of the master listing of courses.
C1


      Review Catalog Module forms and determine
      appropriate usage.


C2




      Determine how data will be maintained and tracked in
C3
      Banner.
      Review Catalog Module Validation Forms in light of
C4
      intended usage.
      Determine appropriate values for Validation Forms
C5
      needed to support intended processing.
      Determine procedures for record updates as new
C6
      courses and course changes are received.
      Review current policies and prepare new policies as
C7
      required.
      Determine need and usage of forms used to collect
      information on new/changed courses. Prepare/revise
      forms in light of Banner values and processing.
C8



      Review Catalog Module reports. Determine required
C9
      revisions and need for additional reports.
      Determine and define interface requirements.
C10


      Obtain necessary approvals for new policies,
C11
      procedure revisions, reports and special forms.
      Send new forms for printing.
C12
    Enter Validation Forms values. Verify entered values
C13
    and use of forms.
    Write specifications for report revisions, new reports
C14
    and required interfaces.
      Write and test revised/new reports and interfaces.
C15
      User sign-off on revised/new reports and interfaces.
C16
    Determine table and form security for users needing
C17 access to Catalog Module forms and reports.

    Grant table access and set up Form Level security for
C18 users needing access to Catalog forms and reports.

      Assign and distribute passwords and permissions to
C19
      Catalog Module users.
      Determine Catalog conversion scope and process.




C20




      Write and test conversion programs.
C21
      Convert Catalog records.


C22



      Verify conversion.
C23
      Determine hardware and equipment needs for offices
C24
      needing access to Catalog Module forms.
      Wire offices and test equipment.
C25
    Write user procedures, reflecting Banner usage and
C26 new policies and procedures, for Catalog Module
    users.
      Announce new procedures and provide appropriate
C27
      forms for data collection.
      Train end-users in the use of the Catalog Module.


C28



      Train end-users in report generation.
C29
      Catalog Module in production.


C30




                  General Student Task Log
      Review current policies and procedures relative to
      maintenance of student information.




G1




      Review General Student Module forms and determine
      appropriate usage.




G2
   Determine how General Student data will be
G3
   maintained and tracked in Banner.
   Review General Student Module Validation and
G4
   Control Forms in light of intended usage.
   Determine appropriate values for Validation and
G5 Control Forms needed to support intended
   processing.
   Determine procedures for record updates as new or
   corrected information is received.
G6



      Revise current policies and prepare new policies as
G7
      needed.
      Determine need and usage of forms used to collect
      Student data or support processing. Gather and
      annotate any pre-printed forms used.




G8




      Determine which pre-printed forms will still be printed
G9
      using Banner.
      Review General Student Module reports. Determine
      required revisions (if any) and need for new reports.
G10


      Determine and define interface requirements.


G11



      Obtain necessary approvals for new policies,
G12
      procedure revisions, reports and special forms.
      Design and order new/revised forms.
G13
    Enter Validation and Control Forms values. Verify
G14
    entered values and use of forms.
    Write specifications for report revisions, new reports
G15
    and required interfaces.
    Write and test revised/new reports and interfaces.
G16
      User sign-off on revised/new reports and interfaces.
G17
    Determine table and form security for users needing
G18 access to General Student Module forms and reports.

    Grant table access and form security for users
G19 needing access to General Student Module forms and
    reports.
    Determine General Student conversion scope and
    process.




G20




      Write and test conversion programs.
G21
      Convert Student data.
G22
      Verify and correct Student data.
G23
    Determine hardware and equipment needs for offices
G24 needing access to General Student Module forms.

      Wire offices and test equipment.
G25
    Write user procedures, reflecting Banner usage and
G26 new policies and procedures, for General Student
    Module users.
    Announce new procedures and provide appropriate
G27
    forms for data collection.
    Train end-users in the use of the General Student
    Module
G28



      Train end-users in report generation.
G29
      General Student Module in production.




G30




                     Location Management
     Review current policies and procedures used in
     processing housing, meal, and phone applications
     and assignments; scheduling events and scheduling
     class sections into rooms.




L1




     Review Location Management Module forms and
     determine appropriate usage.


L2




     Determine how data will be maintained and tracked in
L3
     Banner.
     Review Location Management Module Validation and
     Control forms needed to support intended processing.


L4




     Determine appropriate values for Validation and
     Control Forms needed to support intended
     processing.
L5




     Review current policies and prepare new policies as
L6
     required.
      Gather and annotate forms used to support Housing/
      Meal/Phone and event processing.




L7




      Determine which pre-printed forms will still be printed
L8
      using Banner.
      Review Location Management Module reports.
      Determine required revisions and need for additional
L9
      reports.

      Determine and define interface requirements.




L10




    Obtain necessary approvals for new policies,
L11
    procedure revisions, reports and special forms.
    Prepare/revise forms in light of Banner values and
L12
    processing.
L13 Send new forms for printing.
    Enter Validation and Control Forms values. Verify
    entered values and use of forms.
L14


      Write specifications for report revisions, new reports
L15
      and required interfaces.
L16 Write and test revised/new reports and interfaces.
    User sign-off on revised/new reports and interfaces.
L17
    Determine table and form security for users needing
L18 access to Location Management Module forms and
    reports.
    Grant table access and set up Form Level security for
L19 users needing access to Location Management
    Module forms and reports.
    Assign and distribute passwords and permissions to
L20
    Location Management Module users.
    Determine Location Management conversion scope
    and process.




L21




L22 Write and test conversion programs.
L23 Convert Location Management Data.
L24 Verify conversion correct data.
    Determine hardware and equipment needs for offices
L25 needing access to Location Management Module
    forms.
L26 Wire offices and test equipment.
    Write user procedures, reflecting Banner usage and
L27 new policies and procedures, for Location
    Management Module users.
    Announce new procedures and provide appropriate
L28
    forms for data collection.
    Train end-users in the use of the Location
    Management Module


L29




L30 Train end-users in report generation.
      Location Management Module in production.




L31




                        Recruiting Task Log
      Review current policies and procedures relative to
      recruit information processing.




R1




      Review Recruiting Module forms and determine
      appropriate usage.


R2




      Determine how recruiting data will be maintained and
R3
      tracked in Banner.
      Review and determine the use of the Letter
R4    Generation feature for producing recruiting letters and
      materials.
      Review and determine the use of the Communications
R5    Plan feature for automating letters and materials for
      recruits.
      Gather and annotate letters to be produced by the
      Letter Generation feature. Dissect letters into
      appropriate paragraphs.
R6




      Review Recruiting Module Validation and Control
R7
      forms needed to support intended processing.
      Determine appropriate values for Validation and
R8    Control forms needed to support intended processing.

    Determine procedures for record updates as new or
R9
    corrected information is received.
    Review current policies and prepare new policies as
R10
    required.
    Review/revise recruiting data collection/entry forms in
    light of Banner processing.




R11




      Review Recruiting Module reports. Determine
R12
      required revisions and need for additional reports.
      Determine and define interface requirements.


R13



      Obtain necessary approvals for new policies,
R14
      procedure revisions, reports and special forms.
      Send new forms for printing.
R15
    Enter Validation Forms values. Verify entered values
R16
    and use of forms.
    Build Control Forms for Communications Plans,
R17
    Materials, and Letters.
    Write specifications for report revisions, new reports
R18
    and required interfaces.
    Write and test revised/new reports and interfaces.
R19
      User sign-off on revised/new reports and interfaces.
R20
    Determine table and form security for users needing
R21 access to Recruiting Module forms and reports.

    Grant table access and set up Form Level security for
R22 users needing access to Recruiting Module forms and
    reports.
    Assign and distribute passwords and permissions to
R23
    Recruiting Module users.
    Determine Recruiting conversion population and
    process.

R24




      Write and test conversion programs.
R25
      Convert Recruiting records if desired.
R26
      Verify conversion.
R27
    Determine hardware and equipment needs for offices
R28 needing access to Recruiting Module forms.

      Wire offices and test equipment.
R29
    Write user procedures, reflecting Banner usage and
R30 new policies and procedures, for Recruiting Module
    users.
    Determine a production schedule for letters and
R31
    materials to recruit.
    Announce new procedures and provide appropriate
R32
    forms for data collection.
      Train end-users in the use of the Recruiting Module
R33


      Train end-users in report generation.
R34
      Recruiting Module in production.


R35




                     Registration Task Log
      Review current policies and procedures used in
      processing registration and grades.




F1




      Review Registration Module forms and determine
      appropriate usage.


F2




      Determine how Registration data will be maintained
F3
      and tracked in Banner.
      Review Registration Module Validation and Control
      forms in light of intended usage.




F4




      Determine appropriate values for Validation and
F5    Control forms needed to support intended processing.

      Revise current policies and prepare new policies as
F6
      needed.
      Gather and annotate any special forms used in
F7
      processing registrations.
      Determine which pre-printed forms will still be printed
F8
      using Banner.
      Review Registration Module reports. Determine
F9
      required revisions and need for new reports.
F10   Determine and define interface requirements.
      Obtain necessary approvals for new policies,
F11
      procedure revisions, reports and special forms.
F12   Revise forms.
F13   Send new forms for printing.
      Enter Validation and Control Forms values. Verify
F14
      entered values and use of forms.
      Write specifications for report revisions, new reports
F15
      and required interfaces.
F16   Write and test revised/new reports and interfaces.
      User sign-off on revised/new reports and interfaces.
F17
    Determine table and form security for users needing
F18 access to Registration Module forms and reports.

    Grant table access and form security for users
F19 needing access to Registration Module forms and
    reports.
    Assign and distribute passwords and permissions to
F20
    Registration Module users.
    Determine hardware and equipment needs for offices
F21 needing access to Registration Module forms.

F22 Wire offices and test equipment.
    Write user procedures, reflecting Banner usage and
F23 new policies and procedures, for Registration Module
    users.
    Review sleep/wake processing and determine its use
    in production of Student Schedules and Invoices.
F24



      Establish the Registration report production schedule
F25
      and report distribution.
      Train end-users in the use of the Registration Module.


F26



F27 Train end-users in report generation.
    Train end-users in use of sleep/wake processing.
F28

    Inform faculty members of class roster/grade
F29
    collection forms and procedures.
    Conduct full registration simulation. (Mock
F30
    Registration)
    Evaluate results of simulation. Revise procedures if
F31
    required.
      Registration Module in production.




F32




                      Schedule Task Log
      Review current policies and procedures relative to
      maintenance of each semester‟s schedule of classes.




S1
     Review Schedule Module forms and determine
     appropriate usage.


S2




     Determine how data will be maintained and tracked in
     Banner.
S3


     Review Schedule Module Validation and Control
S4
     Forms in light of intended usage.
     Determine appropriate values for Validation and
S5   Control Forms needed to support intended processing

     Determine procedures for record updates as new
S6
     sections and section changes are received.
     Review current policies and prepare new policies as
S7
     required.
     Determine need and usage of forms used to collect
     information on new/changed section. Prepare/revise
     forms in light of Banner values and processing.

S8




     Review Schedule Module reports. Determine
S9
     required revisions and need for additional reports.
      Determine and define interface requirements.




S10




    Obtain necessary approvals for new policies,
S11
    procedure revisions, reports and special forms.
    Enter Validation Forms values. Verify entered values
S12
    and use of forms.
    Send new forms for printing.
S13
      Write specifications for report revisions, new reports
S14
      and required interfaces.
      Write and test revised/new reports and interfaces.
S15
      User sign-off on revised/new reports and interfaces.
S16
    Determine table and form security for users needing
S17 access to Schedule Module forms and reports.

    Grant table access and set up Form Level security for
S18 users needing access to Schedule forms and reports.

      Assign and distribute passwords and permissions to
S19
      Schedule Module users.
      Determine Schedule conversion scope and process.




S20




      Write and test conversion programs, if any.
S21
      Verify conversion/output.
S22
    Determine hardware and equipment needs for offices
S23 needing access to Schedule Module forms.

      Wire offices and test equipment.
S24
    Announce new procedures and provide appropriate
S25
    forms for data collection.
    Establish a Class Schedule production schedule and
S26
    distribution list.
    Determine procedures for Class Schedule distribution.
S27 Information students/faculty of new format/
    procedures.
    Write user procedures, reflecting Banner usage and
S28 new policies and procedures, for Schedule Module
    users.
      Train end-users in the use of the Schedule Module




S29




      Train end-users in report generation.
S30
      Schedule Module in production.




S31




      Send Schedule to printer
S32


                   Student Billing Task Log
      Review current policies and procedures used in
      processing account information.




B1
     Review Student Billing Module forms and determine
     appropriate usage.


B2




     Determine how Student Billing data will be maintained
B3
     and tracked in Banner.
     Review Student Billing Module Validation and Control
     forms in light of intended usage.




B4




     Determine appropriate values for Validation and
B5   Control forms needed to support intended processing.

     Revise current policies and prepare new policies as
B6
     required.
      Gather and annotate any special forms used.




B7




      Determine which pre-printed forms will still be printed
B8
      using Banner.
      Review Student Billing Module reports. Determine
      required revisions and need for new reports.
B9


      Determine interface requirements.


B10




      Obtain necessary approvals for new policies,
B11
      procedure revisions, reports and special forms.
      Revise forms/prepare new forms.
B12
      Send special forms for printing.
B13
    Enter and validate Validation and Control forms
B14
    values for required data elements.
    Write specifications for report revisions, new reports
B15
    and required interfaces.
    Write and test revised/new reports and interfaces.
B16
      User sign-off on revised/new reports and interfaces.
B17
    Determine table and form security for users needing
B18 access to Student Billing Module forms and reports.

    Grant table access and set up form level security for
B19 users needing access to Student Billing Module forms
    and reports.
    Determine hardware and equipment needs for offices
B20 needing access to Student Billing Module forms.

    Determine hardware and equipment needs for offices
B21 needing access to Student Billing Module forms.

      Determine Student Billing conversion scope and
      process.
B22


    Write and test conversion process. Run conversion
B23 simulation. Audit data to determine that results are
    correct.
    Convert Student Billing data
B24
      Verify and correct converted data
B25
    Review sleep/wake processing and determine its use
B26 in production of bills and receipts.

    Establish the Student Billing report production
    schedule and report distribution. Write and test user
B27 procedures, reflecting Banner usage and new policies
    and procedures, for Student Billing Module users.

      Train end-users in the use of the Banner Student
      Billing Module.


B28




      Train end-users in report generation.
B30
      Train end-users in use of sleep/wake processing.
B31
      Student Billing Module in production.




B32




                  Technical & System Task Log
T1    Establish implementation team.
T2    Establish test system.
T3    Establish training/testing facility.
      Determine terminal configurations. Generate
T4    Function Key reference chart depending upon
      terminal configuration.
      Develop documentation distribution list and plan for
T5    reproduction, distribution, and updating manuals

      Distribute training manuals
T6

      Establish grants, user IDs, passwords, and form
T7
      security for training purposes
      Determine operating system/Banner log-in
T8
      procedures.
T9    Establish operations procedures.
T10   Establish backup and restore procedures.
T11   Establish disaster recovery procedures.
      Establish procedures for system maintenance:
T12
      ORACLE; Operating System; Banner
      Develop and publicize procedures for reporting
T13
      ORACLE errors.
      Develop and publicize procedures for reporting
T14
      Banner errors.
    Secure SCT training agendas, confirm dates and
    participants, schedule use of training facility, distribute
T15
    agenda to key administrators and participants

      Develop institutional task log and implementation
T16
      schedule
      Determine authority and responsibility for
T17
      maintenance of system security.
      Determine hardware requirements for production
T18   system (terminals, printers, modems, controllers, tape
      drives, etc.).
T19   Acquire necessary hardware.
T20   Establish Conversion Plan:
      Decide what data is to be converted and how and it
      what order; Evaluate data to be converted. Make
      corrections, if necessary; Write conversion programs
T21
      or data entry instructions for manual conversions;
      Test conversion programs or manual instructions (in
      stages)
T22   Verify conversions in production system
      Develop change control logging procedures for site-
T23
      specific enhancements.
      Develop procedures for production migration (initial
T24   install, stage tapes, site-specific enhancements, etc.)

    Establish grants, user IDs, passwords, form security
T24
    for production operation
    Consider public relations functions. Plan for
T26 notifications to CWS and employees regarding
    implementation of new system.
    Develop an operation‟s production schedule for all
T27
    batch jobs that will be run on a regular basis.
    Establish databases and uses e.g. TRNG, TEST,
    PPRD, PROD
T28



    Establish Banner Documentation link in Database
T29
    (load documentation library)
    Establish default temporary location for Job
T30
    Submission output (local drive)
      Actual
Start Date End Date Comments

                   Include review of at
                   least the following:
                   Grading policy;
                   Grade change
                   processing; Repeat
                   policy; Academic
                   standing and dean‟s
                   list criteria;
                   Academic probation
                   criteria;
                   Degree application
                   procedures;
                   Academic honor
                   criteria;
                   Transfer Course
                   Processing;
                   Transcript hold
                   policies

                   Review optional forms
                   and values and
                   determine whether
                   and how they will be
                   used. Review optional
                   forms and values and
                   determine whether
                   and how they will be
                   used.




                   Detail codes, defined
                   in the Student Billing
                   Module, are used in
                   defining transcript,
                   graduation, and
                   diploma fees. Grades,
                   defined in the
                   Academic History
                   Module, are used in
                   grade processing.
Review both pre-
printed and data
collection forms.
Include review of at
least the following:
Grade mailers;
Transcript request
forms;     Transcripts;
Grade change forms;
Degree application
forms




Especially test use of
grade values,
academic standing
and dean‟s list rules
and repeat course
processing.
Determine whether
detailed or summary
data will be converted.




Determine number of
printers and printer
locations. Develop
sleep/wake routine for
each printer
destination.
Minimum policies to
review:
Initial application
processing;
Returning student
application
requirements;
Required documents;
Admission decision
policies;
Maintenance of high
school qualification
information and
receipt of transcripts;
Maintenance of test
scores


Review required forms
and values and
determine how they
will be used. Review
optional forms and
values and determine
whether and how they
will be used.
Include
review/revision of at
least the following:
Admissions
Application Form;
Supplemental
International
application information
forms; Guardian
information collection




Interfaces to consider:
Load of data from
other sources (Banner
Tape Load process);
Financial Aid interface
Because of the
various inter-
relationships among
forms and modules in
Banner, it is usually
best to begin entering
applications on-line
beginning with
applications for the
implementation term.
(Conversion not
performed for
previous terms).




Navigation and
General Person
Module training will
also be required.
Recruiting Module
training may be
required.
The General Person
Module must already
be in production or go
into production at the
same time as the
Admissions Module.
Because admissions
decisions (student
acceptances) create
General Student
records, the General
Student Module must
be in production at the
same time as the
Admissions Module.




Include review of
name and ID change
procedures,
maintenance of
addresses, use of
holds, use of
comments, offices to
maintain data when
changes are
necessary, etc.
Review required forms
and values and
determine how they
will be used. Review
optional forms and
values and determine
whether and how they
will be used.

Pay particular
attention to name
searches to reduce
the number of
duplicate records.
Standards for all
Banner data entry of
biographic/demograph
ic data.
Cross-Functional
Team needed-
determine owner(s)
Cross-Functional
Team needed
Cross-Functional
Team needed

Identify offices
involved in
maintaining records
and cut off points, e.g.
Admissions will
change applicants
addresses until they
register, than
Registrar does so.
Include
review/preparation of
the following forms:
Initial
biographic/demograph
ic data collection
forms;
Name and ID change
forms;
Address change
forms;
Telephone number
change forms
Interfaces to consider:
Interface to Human
Resources System;
Interface to Alumni
System;
Interface to Finance
System (vendor
names, IDs, and
addresses);
Interface to Financial
Aid System;
Interface to Student
System;
Other Systems (list)




Consider which
records and data
elements to convert,
pre-conversion data
clean-up efforts, post-
conversion
verification, and
correction process
Navigation training will
also be required. Most
offices on campus will
need training in
appropriate modules.
Train users using new
procedures manual.
Define the Major
Functional Areas that
may have a need for
CAPP. Identify the
Administrative
Departments or
Functional Areas that
will have responsibility
for managing and/or
maintaining the data.
Identify the areas of
the system that need
to be in place prior to
the beginning of
CAPP. Outline the
necessary steps
needed to update or
have the system
ready for CAPP
implementation.
Navigation and
General Person
training is also
required unless
previously provided.
Train users using new
procedures manual.




The General Person.
General Student,
Registration and
Academic History
Modules must all be in
production before or
brought into
production at the
same time as the
CAPP Module.
Include review of
current course
proposal, change and
approval process.

Review required forms
and values and
determine how they
will be used. Review
optional forms and
values and determine
whether and how they
will be used.




Include initial data
collection/entry for
current courses, new
courses, approval/
entry for, course
revision/update form.




Interfaces to consider:
Download of data to
print Catalog.
Catalog conversion
can be either a
manual or an
electronic process.
Historical course
changes need to be
considered if
converted Catalog
information for terms
prior to
implementation.
Conversion of pre-
implementation
Catalog entries will
impact Academic
History conversion/
processing.


For electronic
conversion, run
conversion process.
For manual
conversion, enter data
on-line.
Navigation training is
also required unless
previously provided.
Train end-users using
new procedures
manual.


The Catalog Module
must be in production
before the first term‟s
schedule can be
developed.



Include review of
major, residency,
advisor maintenance
and change
processing;
determination of
student classifications;
co-op processing;
maintenance of
student activities;
Veteran‟s certification
policies; etc.


Review required forms
and values and
determine how they
will be used. Review
optional forms and
values and determine
whether and how they
will be used. Which
offices will have
access to
comprehensive forms
such as SGASTDN.
Particular attention to
be paid to withdrawal
processing and
enrollment
processing.




Review data collection
forms: Change of
major; Change of
residency; Advisor
requests; Co-op
assignment
request/approval;
Co-op company
names, addresses,
contacts;
Review pre-printed
forms:
Advisor assignment
forms;
Advisor assignment
forms




Include reports
needed to produce
any pre-printed forms.

Possible interfaces:
Financial Aid System;
Faculty Load System
(advising
assignments)
A student record must
exist for each person
who will register in the
first production
registration. Student
records are required for
each person for whom
Academic History data
will be converted. If prior
Academic History data
will be converted,
Student records must
exist for all academic
history terms. Changes
in major, etc., must be
reflected in converted
data. General Person
data must be converted
for all students who are
converted. Advisors will
need to be authorized in
the Faculty Load Module
before advisor
assignments can be
converted.
Navigation and
General Person
Module training will
also be required
unless previously
provided.


The General Person
Module must already
be in production at the
same time as the
General Student
Module goes into
production. Advisors
will need to be
authorized in the
Faculty Load Module
before advisor
assignments can be
made/changed.
Include review of:
Housing/meal/phone
application policies;
Housing/meal/phone
deposit policies;
Initial assignments,
withdrawals, changes;
Housing/meal/phone
assessment policies;
Roommate application
policies;
Conferences and
special events


Review required forms
and values and
determine how they
will be used. Review
optional forms and
values and determine
whether and how they
will be used.




Student Billing
Validation and Control
forms must also be
reviewed for Housing/
Meal/Phone charge
processing and
refunds.

Student Billing
Validation and Control
forms will also need
appropriate values to
support
Housing/Meal/Phone
processing.
Review both pre-
printed and data
collection forms.
Include, at least:
Housing/Meal/Phone
Application;
Housing/Meal/Phone
Contract;
Room Assignment
Form;            Room
and Board
Bill/Telephone Bill;
Roommate
Request/Change
Form;
Event Scheduling
Request/Verification
Forms;
Phone Request/
Assignment Forms


Include reports
needed to produce
any pre-printed forms.

Interfaces to consider:
Interface to meal plan
provider (Vali-Dyne,
etc.);
Telephone billing
system;
Room Lottery System




Especially test
assessment,
withdrawal, and
refund rules.
Identify possible
conversion processes
for creating buildings
and rooms. It is
usually not possible or
desirable to convert
existing
housing/meal/phone
applications and/or
assignments. Begin
processing for a new
period on-line.




Navigation and
General Person
training is also
required unless
previously provided.
Train users using new
procedures manual.
The General Person
and Student Billing
Modules must be in
production before or
brought into
production at the
same time as the
Location Management
Module. Building and
room definitions must
be in production
before class sections
can be scheduled into
rooms in the Schedule
Module.




Include review of
current recruiting
practices,
communications
plans, materials
production and
scheduling,
visit/appointment
scheduling, collection
and maintenance of
high school/college
background and
contact information,
etc.

Review required forms
and values and
determine how they
will be used. Review
optional forms and
values and determine
whether and how they
will be used
Determine if letters
will be printed directly
from Banner or will
letter generation be
used to create a
datafile for Microsoft
Word or Wordperfect.




Minimum forms to
review:
Inquiry cards;
Requests for material;
High school/college
background
information collection
forms; Appointment
forms; High
school/college visit
forms




Interfaces to consider:
Load of data from
other sources (Banner
Tape Load process)
Consider conversion
of both recruiting
information and high
school/college
information or archive
past data for reporting
purposes.
Navigation and
General Person
Module training will
also be required.


The General Person
Module must already
be in production or go
into production at the
same time as the
Recruiting Module.



Include review of:
Pre-registration
processing;
Walk-in registrations;
Withdrawal policies,
including grades,
refunds and holds;
Registration
assessment rules;
Class roster
distribution;
Grade collection and
maintenance;
Deregistration for non-
payment

Review required forms
and values and
determine how they
will be used. Review
optional forms and
values and determine
whether and how they
will be used.
Detail codes, defined
in the Student Billing
Module, are used in
building Registration
Assessment rules and
refunding rules.
Grades, defined in the
Academic History
Module, are used in
grade processing.
Determine number of
printers and printer
locations. Develop
sleep/wake routine for
each printer
destination.


Navigation training will
also be required
unless previously
provided. Train end-
users using new
procedures manual.

Inform users of printer
destination
parameters.
Registrations depend
upon effective Student
records. The General
Student Module must be
in production before the
Registration Module can
be brought into
production. Registration
assessments create
Student Billing records.
The Student Billing
Module must be in
production before or
brought into production
before the first student
bills are to be processed.
Some registration error
checking (pre-requisites,
duplicate courses) make
use of Academic History
records. If these
functions are to be used,
Academic History
conversion must be
complete and the
Academic History
Module in production.




Include review of
current section
proposal, change and
approval processes;
assignment of rooms;
assignment of faculty;
links; section
enrollments; reserved
seats; wait lists; etc.
Review required forms
and values and
determine how they
will be used. Review
optional forms and
values and determine
whether and how they
will be used.

Will processing be
centralized or
distributed to
departments?




Special forms needed
may include Schedule
Request/Departmental
Offerings Form,
Schedule Change
Form, Section
Cancellation Form,
etc.
Interfaces to consider:
Download of data to
produce Schedule of
Classes if the
Schedule Report
(SSRSECT) does not
include required data
or desired format, or if
graphics are also to
be included;
Interface to Faculty
Load System;
Interface to automatic
scheduler, if one is
used.
Because of changes
from term to term,
actual semester
schedules are seldom
able to be
electronically
converted from other
systems.
Building/rooms and/or
instructor information
may be able to be
converted. (Building
and room definition
occurs in the Location
Management Module;
faculty requires
identification records
and authorizations set
in the Faculty Load
Module).
Navigation, General
Person, and Location
Management Modules
training will also be
required. Train users
using new procedures
manual.




Catalog, General
Person, and Location
Management Modules
must be in production
or go into production
at the same time as
the Schedule Module.




Include review of at
least the following:
Pre-payments;
Deposits;
Payment plans;
Exemptions;
Third party billings;
Non-student accounts;
Miscellaneous
transactions;
Returned check
processing;
Billing cycles;
Collections agency
assignment;
Application of
payment priorities;
Cashier balancing and
approval; General
Ledger account
structure
Review required forms
and values and
determine how they
will be used. Review
optional forms and
values and determine
whether and how they
will be used.




Registration
assessments,
housing/meal/phone
assessments, course
fees, section fees,
application fee
charges (if
automated), transcript
charges (if
automated), and
financial aid
disbursals all use
Detail Codes defined
in the Student Billing
Module. Review use
of Detail Codes in
other modules as well.
Review both pre-
printed and data
collection forms.
Include review of at
least the following:
Invoice/statement
form; Receipt form;
Contract (third party)
authorization form
and bill; Exemption
authorization form;
Installation plan
request/promissory
note; Cashier
balancing/check-out
form; Collection
agency assignment/
notification forms




Include reports
needed to produce
any pre-printed forms.

Interfaces to consider:
Finance System
interface;
Financial Aid System
interface;
Lock box processing
Most often, balances
forward are converted,
not account detail.




Determine number of
printers and printer
locations.




Navigation and
General Person
Module training will
also be required
unless previously
provided. Train end-
users using new
procedures manual.


Inform users of printer
destination
parameters.
The General Person
Module must be in
production before or
brought into
production at the
same time as the
Student Billing
Module. Data defined
in the Student Billing
Module is used to
create assessment
rules for other
modules, and receive
assessments from
other modules.




Develop document
and materials
repository on server.
Clone databases if
necessary. Identify
databases used for
training, testing,
conversion testing,
etc.
                                   Planned
ID   Milestone   Pre-   Owner Start Date End Date
      Actual
Start Date End Date Comments
                                 Planned                Actual
ID   Milestone   Pre- Owner Start Date End Date   Start Date End Date Comments
                                                                                 Planned                Actual
  ID                          Milestone                          Pre- Owner Start Date End Date   Start Date End Date

                        Applicant Budgeting
       Review current policies and procedures relative to the
AB1    maintenance of applicant budget processing
       information.
       Read and review related info in User and Technical
AB2
       Manual.
AB3    Review forms and determine appropriate usage.
       Determine what data will be maintained and tracked in
AB4
       Banner.
       Determine appropriate values for validation forms
AB5
       needed to support intended processing.
       Determine procedure for maintenance validation
AB6
       forms.
AB7    Build forms in TEST.
AB8    Move completed forms to PPRD.
AB9    Make screen prints for documentation.
AB10   Ensure all jobs with this module work in PPRD.
AB11   Move final form values from PPRD to PROD.
AB12   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
AB13
AB14   Develop additional reports as needed.
AB15   Test and sign off each local report.
AB16   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
AB17
       processes.
       Develop and document policies and procedures for
AB18
       extracting and logging corrections
       Write user procedures reflecting Banner usage, new
AB19
       policies and procedures.
       Determine procedure for maintenance of
AB20   validation/rules forms during implementation, during
       production and for each new aid year.
       Publish and distribute new policies/procedures and
AB21
       provide appropriate forms.
       Train end users in the use of corrections processing.


AB22
       Train end users in processes.




AB23




AB24   Train end users in report submission.
       Determine hardware and equipment needs for offices
AB25
       needing access to forms.
AB26   Applicant Budgeting in production.
       Determine current information in legacy system that is
AB27   not provided for in Banner and determine procedures
       w/in Banner
AB28   Module Post Implementation Assessment
                            Applicant Holds
       Review current policies and procedures relative to the
AH1
       maintenance of applicant holds.
       Read and review related info in User and Technical
AH2
       Manual.
       Review Applicant Hold forms and determine
AH3
       appropriate usage.
       Determine what data will be maintained and tracked in
AH4
       Banner.
       Determine appropriate values for validation forms
AH5
       needed to support intended processing.
       Determine procedure for maintenance validation
AH6
       forms.
AH7    Build forms in TEST.
AH8    Make screen prints for documentation.
AH9    Ensure all jobs with this module work in AHRD.
AH10   Move final form values from PPRD to PROD.
AH11   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
AH12
AH13   Develop additional reports as needed.
AH14   Test and sign off each local report.
AH15   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
AH16
       processes.
       Determine when and if conversion of aid history will
AH17
       take place
AH18   Determine conversion requirements
AH19   Complete conversion in TEST
AH20   Complete conversion in PROD
       Develop and document policies and procedures




AH21




       Write user procedures reflecting Banner usage, new
AH22
       policies and procedures.
       Publish and distribute new policies/procedures and
AH23
       provide appropriate forms.
       Train end users in the use of Applicant Holds


AH24



AH25   Train end users in processes.
AH26   Train end users in report submission.
       Determine hardware and equipment needs for offices
AH27
       needing access to forms.
AH28   Wire offices and test equipment.
AH29   Applicant Holds processing in production.
       Determine current information in legacy system that is
AH30   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


AH31




                        Applicant Messages
       Review current policies and procedures relative to the
AM1
       maintenance applicant messages
       Read and review related info in User and Technical
AM2
       Manual.
AM3    Review forms and determine appropriate usage.
       Determine what data will be maintained and tracked in
AM4
       Banner.
       Determine appropriate values for validation forms
AM5
       needed to support intended processing.
       Determine procedure for maintenance validation
AM6
       forms.
AM7    Build forms in TEST.
AM8    Make screen prints for documentation.
AM9    Ensure all jobs with this module work in AMRD.
AM10   Move final form values from PPRD to PROD.
AM11   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
AM12
AM13   Develop additional reports as needed.
AM14   Test and sign off each local report.
AM15   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
AM16
       processes.
       Determine when and if conversion of aid history will
AM17
       take place
AM18   Determine conversion requirements
AM19   Complete conversion in TEST
AM20   Complete conversion in PROD
       Develop and document policies and procedures




AM21




       Write user procedures reflecting Banner usage, new
AM22
       policies and procedures.
       Publish and distribute new policies/procedures and
AM23
       provide appropriate forms.
       Train end users in the use of the Pell Module.


AM24



AM25   Train end users in processes.
AM26   Train end users in report submission.
       Determine hardware and equipment needs for offices
AM27
       needing access to forms.
AM28   Wire offices and test equipment.
AM29   Applicant Message processing in production.
       Determine current information in legacy system that is
AM30   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


AM31




                       Applicant Tracking
       Review current policies and procedures relative to the
AT1
       maintenance of applicant tracking information.
       Read and review related info in User and Technical
AT2
       Manual.
       Review Applicant Tracking Module forms and
AT3
       determine appropriate usage.
       Determine what data will be maintained and tracked in
AT4
       Banner.
       Determine appropriate values for validation forms
AT5
       needed to support intended processing.
       Determine procedure for maintenance validation
AT6
       forms.
AT7    Build forms in TEST.
AT8    Move completed forms to PPRD.
       Determine if any tracking items will be batch posted.
AT9
       Build population selection/batch posting rules in
AT10
       PPRD.
AT11   Make screen prints for documentation.
AT12   Ensure all jobs with this module work in PPRD.
AT13   Move final form values from PPRD to PROD.
AT14   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
AT15
AT16   Develop additional reports as needed.
AT17   Test and sign off each local report.
AT18   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
AT19
       processes.
       Develop and document policies and procedures




AT20




       Populate Rule and Validation forms for Tracking
AT21
       Letter
AT22   Create Population Selections For Tracking Letter
       Create Template Tracking Letter in MSWord /
AT23
       WordPerfect
AT24   Run Letter Generation Processes
AT25   Extract Letter from Banner Jobsub to local PC
       Merge Tracking Letter Extract into Template Tracking
AT26
       Letter
       Determine procedure for Tracking Letter Generation
AT27
       Develop and document policies and procedures for
AT28
       students selected for verification
       Determine Applicant Tracking conversion scope and
AT29   consider which records and data elements to process.

AT30   Write and test conversion program.
AT31   Convert Applicant data.
AT32   Verify and correct data.
       Write user procedures reflecting Banner usage, new
AT33
       policies and procedures.
       Publish and distribute new policies/procedures and
AT34
       provide appropriate forms.
       Train end users in the use of the Applicant Tracking
       Module.
AT35
       Train end users in processes.




AT36




AT38   Train end users in report submission.
       Determine hardware and equipment needs for offices
AT39
       needing access to forms.
AT40   Wire offices and test equipment.
AT41   Applicant Tracking in production.
       Determine current information in legacy system that is
AT42   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


AT43




                            Batch Posting
       Review current policies and procedures relative to the
UD1
       maintenance of batch posting processing
       Read and review related info in User and Technical
UD2
       Manual.
       Review Batch Posting forms and determine
UD3
       appropriate usage.
       Determine what data will be maintained and tracked in
UD4
       Banner.
       Determine appropriate values for validation forms
UD5
       needed to support intended processing.
       Determine procedure for maintenance validation
UD6
       forms.
UD7    Build forms in TEST.
UD8    Make screen prints for documentation.
UD9    Ensure all jobs with this module work in UDRD.
UD10   Move final form values from PPRD to PROD.
UD11   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
UD12
UD13   Develop additional reports as needed.
UD14   Test and sign off each local report.
UD15   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
UD16
       processes.
       Determine when and if conversion of aid history will
UD17
       take place
UD18   Determine conversion requirements
UD19   Complete conversion in TEST
UD20   Complete conversion in PROD
       Develop and document policies and procedures




UD21




       Write user procedures reflecting Banner usage, new
UD22
       policies and procedures.
       Publish and distribute new policies/procedures and
UD23
       provide appropriate forms.
       Train end users in the use of Batch Posting Forms.


UD24
       Train end users in processes.
UD25


UD26   Train end users in report submission.
       Determine hardware and equipment needs for offices
UD27
       needing access to forms.
UD28   Wire offices and test equipment.
UD29   Batch Posting processing in production.
       Determine current information in legacy system that is
UD30   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


UD31




             Biographic & Demographic Data Entry
       Review current policies and procedures relative to
       maintenance of the person/non-person data.



D1
     Review biographic & demographic data entry forms
     and determine appropriate usage


D2




     Determine how data will be maintained and tracked in
     Banner
D3


     Develop Data entry Standards Procedures
D4


     Review biographic & demographic data entry forms
D5   and determine appropriate usage.

     Determine appropriate values for Validation Forms
D6
     needed to support intended processing
     Determine procedures for record updates as
D7   additional information and/or changes are received.
      Revise current policies and prepare new policies as
      required.


D8




      Determine need and usage of forms used to collect
      information on new/changed person data. Prepare/
      revise forms in light of Banner values and processing.




D9




      Review biographic & demographic reports. Determine
D10   required revisions and need for additional reports.
      Determine and define interface requirements.




D11




      Obtain necessary approvals for new/revised policies,
D12
      procedures.
D13   Send new forms for printing.
      Enter Validation Forms values. Verify entered values
D14
      and use of forms.
      Write specifications for report revisions, new reports
D15
      and required interfaces.
D16   Write and test revised/new reports and interfaces.
      Obtain user sign-off on revised/new reports and
D17
      interfaces.
      Determine table and form security for users needing
D18   access to General Person Module forms and reports.

      Grant table access and set up Form Level security for
D19   users needing access to appropriate forms and
      reports.
      Assign and distribute passwords and permissions to
D20
      appropriate modules
      Determine data conversion scope, process, and
      population (both persons and non-persons)


D21




D22   Write and test conversion programs.
D23   Convert person/non-person data.
D24   Verify conversion.
      Determine hardware and equipment needs for offices
D25   needing access to biographic & demographic forms.

D26   Wire and test office equipment.
      Write user procedures, reflecting Banner usage and
D27   new policies and procedures, for data entry users.

      Announce new procedures and provide appropriate
D28
      forms for data collection.
      Train end-users in the use of the appropriate system
      module


D29




D30   Train end-users in report generation.
      Biographic & demographic data entry in production.
D31
                     Correction Processing
       Review current policies and procedures relative to the
CP1    maintenance of correction processing information.

       Read and review related info in User and Technical
CP2
       Manual.
CP3    Review forms and determine appropriate usage.
       Determine what data will be maintained and tracked in
CP4
       Banner.
       Determine appropriate values for validation forms
CP5
       needed to support intended processing.
       Determine procedure for maintenance validation
CP6
       forms.
CP7    Build forms in TEST.
CP8    Move completed forms to PPRD.
CP9    Make screen prints for documentation.
CP10   Ensure all jobs with this module work in PPRD.
CP11   Move final form values from PPRD to PROD.
       Ensure FTP process is working to extract correction
CP12
       file.
CP13   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
CP14
CP15   Develop additional reports as needed.
CP16   Test and sign off each local report.
CP17   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
CP18
       processes.
       Develop and document policies and procedures for
CP19
       extracting and logging corrections
       Write user procedures reflecting Banner usage, new
CP20
       policies and procedures.
       Develop and document policies and procedures for
CP21
       importing correction ISIR Files
       Publish and distribute new policies/procedures and
CP22
       provide appropriate forms.
       Train end users in the use of corrections processing.


CP23
       Train end users in processes.




CP24




       Determine procedure for maintenance of
CP25   validation/rules forms during implementation, during
       production and for each new aid year.
CP26   Train end users in report submission.
       Determine hardware and equipment needs for offices
CP27
       needing access to forms.
CP28   Wire offices and test equipment.
CP29   Correction Processing in production.
       Determine current information in legacy system that is
CP30   not provided for in Banner and determine procedures
       w/in Banner
CP31   Module Post Implementation Assessment

                            Direct Loans
       Review current policies and procedures relative to the
DL1
       maintenance of direct loan information.
       Read and review related info in User and Technical
DL2
       Manual.
       Review Loan Module forms and determine
DL3
       appropriate usage.
       Determine what data will be maintained and tracked in
DL4
       Banner.
       Determine appropriate values for validation forms
DL5
       needed to support intended processing.
       Determine procedure for maintenance validation
DL6
       forms.
DL7    Build forms in TEST.
       Build population selection/batch posting rules in TEST
PB8
DL9    Move completed forms to PPRD.
DL10   Determine if any items will be batch posted
DL11   Make screen prints for documentation.
DL12   Ensure all jobs with this module work in PPRD.
       Build population selection/batch posting rules in
DL13
       PROD
DL14   Move final form values from PPRD to PROD.
DL15   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
DL16
DL17   Develop additional reports as needed.
DL18   Test and sign off each local report.
DL19   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
DL20
       processes.
       Develop and document policies and procedures




DL21




       Determine conversion scope and consider which
DL22
       records and data elements to process.
DL23   Write and test conversion program.
DL24   Convert data.
DL25   Verify and correct data.
       Write user procedures reflecting Banner usage, new
DL26
       policies and procedures.
       Publish and distribute new policies/procedures and
DL27
       provide appropriate forms.
       Train end users in the use of the Loans Module.


DL28



       Train end users in processes.




DL29




DL30   Train end users in report submission.
       Determine hardware and equipment needs for offices
DL31
       needing access to forms.
DL32   Wire offices and test equipment.
DL33   Direct Loans in production.
       Determine current information in legacy system that is
DL34   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


DL35




                         Electronic Loans
       Review current policies and procedures relative to the
EL1
       maintenance of loan information.
       Read and review related info in User and Technical
EL2
       Manual.
       Review Loan Module forms and determine
EL3
       appropriate usage.
       Determine what data will be maintained and tracked in
EL4
       Banner.
       Determine appropriate values for validation forms
EL5
       needed to support intended processing.
       Determine procedure for maintenance validation
EL6
       forms.
EL7    Build forms in TEST.
       Build population selection/batch posting rules in TEST
PB8
EL9    Move completed forms to PPRD.
EL10   Determine if any items will be batch posted
EL12   Ensure all jobs with this module work in PPRD.
       Build population selection/batch posting rules in
EL13
       PROD
EL14   Move final form values from PPRD to PROD.
EL15   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
EL16
EL17   Develop additional reports as needed.
EL18   Test and sign off each local report.
EL19   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
EL20
       processes.
       Develop and document policies and procedures




EL21




       Determine conversion scope and consider which
EL22
       records and data elements to process.
EL23   Write and test conversion program.
EL24   Convert data.
EL25   Verify and correct data.
       Write user procedures reflecting Banner usage, new
EL26
       policies and procedures.
       Publish and distribute new policies/procedures and
EL27
       provide appropriate forms.
       Train end users in the use of the Loans Module.


EL28



       Train end users in processes.




EL29




EL30   Train end users in report submission.
       Determine hardware and equipment needs for offices
EL31
       needing access to forms.
EL32   Wire offices and test equipment.
EL33   Electronic Loans in production.
       Determine current information in legacy system that is
EL34   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


EL35




                        Funds Management
       Review current policies and procedures relative to the
FM1
       maintenance of funds information.
       Read and review related info in User and Technical
FM2
       Manual.
       Review Funds Management Module forms and
FM3
       determine appropriate usage.
       Determine what data will be maintained and tracked in
FM4
       Banner.
       Determine appropriate values for validation forms
FM5
       needed to support intended processing.
       Determine procedure for maintenance validation
FM6
       forms.
FM7    Build forms in TEST.
FM8    Move completed forms to PPRD.
FM9    Make screen prints for documentation.
FM10   Ensure all jobs with this module work in PPRD.
FM11   Move final form values from PPRD to PROD.
FM12   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
FM13
FM14   Develop additional reports as needed.
FM15   Test and sign off each local report.
FM16   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
FM17
       processes.
       Develop and document policies and procedures




FM18




       Determine Funds Management conversion scope and
       consider which records and data elements to process.

FM19




FM20   Write and test conversion program.
FM21   Convert data.
FM22   Verify and correct data.
       Write user procedures reflecting Banner usage, new
FM23
       policies and procedures.
       Publish and distribute new policies/procedures and
FM24
       provide appropriate forms.
       Train end users in the use of the Funds Management
       Module.
FM25



       Train end users in processes.


FM26



FM27   Train end users in report submission.
       Determine hardware and equipment needs for offices
FM28
       needing access to forms.
FM29   Wire offices and test equipment.
FM30   Funds Management in production.
       Determine current information in legacy system that is
FM31   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


FM32




                      History & Transcripts
       Review current policies and procedures relative to the
HT1    maintenance of historical records and the production
       of transcripts.
       Read and review related info in User and Technical
HT2
       Manual.
       Review History Module forms and determine
HT3
       appropriate usage.
       Determine what data will be maintained and tracked in
HT4
       Banner.
       Determine appropriate values for validation forms
HT5
       needed to support intended processing.
       Determine procedure for maintenance validation
HT6
       forms.
HT7    Build forms in TEST.
HT8    Make screen prints for documentation.
HT9    Ensure all jobs with this module work in HTRD.
HT10   Move final form values from PPRD to PROD.
HT11   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
HT12
HT13   Develop additional reports as needed.
HT14   Test and sign off each local report.
HT15   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
HT16
       processes.
       Determine when and if conversion of aid history will
HT17
       take place
HT18   Determine conversion requirements
HT19   Complete conversion in TEST
HT20   Complete conversion in PROD
       Develop and document policies and procedures




HT21




       Write user procedures reflecting Banner usage, new
HT22
       policies and procedures.
       Publish and distribute new policies/procedures and
HT23
       provide appropriate forms.
       Train end users in the use of History & Transcripts.


HT24



HT25   Train end users in processes.
HT26   Train end users in report submission.
       Determine hardware and equipment needs for offices
HT27
       needing access to forms.
HT28   Wire offices and test equipment.
HT29   History & Transcript processing in production.
       Determine current information in legacy system that is
HT30   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


HT31




                     Initial Set-Up Record Load
       Read and review record creation and dataload related
RC1    information in User and Technical Manuals.

       For Unix clients, ensure the $DATA_HOME/Financial
       Aid directory is built. For VMS clients, ensure the
RC2
       DATA$HOME directory is built.

       Install FTP software installed on local PC‟s.


RC3



       Install the FILECAT.exe program to PC.
RC4

       Review and Populate tables necessary for the
RC5
       Dataload process in TEST environment.
       Establish a log sheet to enter results and job number
RC6    from each process of the Dataload.
       Create a directory on your PC to place copies of the
RC7
       ISIR records that you have loaded.
       Move SARA files from EdConnect Software to local
RC8
       PC.
       Rename SARA files to xxxxesar.tap where „xxxx‟ = the
RC9
       aid processing year.
RC10   Concatenate multiple files with FILECAT.
       FTP the xxxxesar.tap file from the local PC to the
RC11   Dataload directory. Only one xxxesar.tap file can
       exist at a time in the Dataload directory.
RC12   Perform Dataload Process.
       Move completed Forms to TEST database.
RC13

       Establish and document procedures for the dataload
RC14
       process.
       Establish and document procedures for working files
RC15
       in the temporary tables (RCRSUSP).
RC16   Move final values from TEST to PROD.
       Determine Security Setup on each form and process.
RC17
       Establish grants and permissions in TEST
RC18
       environment
       Establish grants and permissions in PROD
RC19
       environment.
       Develop and document policies and procedures:




RC20




       Determine current information in legacy system that is
RC21   not provided for in Banner and determine procedures
       w/in Banner.

                         Letter Generation
       Read and review related info in User and Technical
LG1
       Manual.
       Review the Letter Generation forms for appropriate
LG2
       use.
LG3    Build forms in TRNG.
LG4    Ensure all jobs with this module work in TRNG.
LG5    Move completed forms to TEST.
LG6    Ensure all jobs with this module work in TEST.
LG7    Make screen prints for documentation.
LG8    Move final forms to PROD.
LG9    Determine security for each form/job in module.
LG10   Establish grants/permissions.
       Develop policies and procedures.


LG11



       Determine procedure for maintenance of
LG12   validation/rules forms during implementation, during
       production and for each new aid year.
LG13   Develop plan of action for training end user staff
       Train end user staff
LG14


LG15   Letter Generation processing in production.
       Determine current information in legacy system that is
LG16   not provided for in Banner and determine procedures
       w/in Banner.
       Module Post Implementation Assessment


LG17




                         Needs Analysis
       Review current policies and procedures relative to the
NA1
       maintenance of needs information.
       Read and review related info in User and Technical
NA2
       Manual.
       Review Needs Analysis Module forms and determine
NA3
       appropriate usage.
       Determine what data will be maintained and tracked in
NA4
       Banner.
       Determine appropriate values for validation forms
NA5
       needed to support intended processing.
       Determine procedure for maintenance validation
NA6
       forms.
NA7    Build forms in TEST.
NA8    Move completed forms to PPRD.
       Build population selection/batch posting rules in
NA10
       PPRD.
NA11   Make screen prints for documentation.
NA12   Ensure all jobs with this module work in PPRD.
NA13   Move final form values from PPRD to PROD.
NA14   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
NA15
NA16   Develop additional reports as needed.
NA17   Test and sign off each local report.
NA18   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
NA19
       processes.
NA20   Develop and document policies and procedures
       Write user procedures reflecting Banner usage, new
NA21
       policies and procedures.
       Publish and distribute new policies/procedures and
NA22
       provide appropriate forms.
       Train end users in the use of the Needs Analysis
       Module.
NA23



       Train end users in processes.




NA24
        Train end users in processes.




NA24
cnt'd




        Determine procedure for maintenance of
NA25    validation/rules forms during implementation, during
        production and for each new aid year.
        Determine and Test values in the Need Analysis
NA26
        Module may be batch posted
NA27    Train end users in report submission.
       Determine hardware and equipment needs for offices
NA28
       needing access to forms.
NA29   Wire offices and test equipment.
NA30   Needs Analysis in production.
       Determine current information in legacy system that is
NA31   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment




                    Packaging & Disbursements
       Review current policies and procedures relative to the
PD1    maintenance of packaging and disbursement
       information.
       Read and review related info in User and Technical
PD2
       Manual.
       Review Packaging & Disbursement Module forms and
PD3
       determine appropriate usage.
       Determine what data will be maintained and tracked in
PD4
       Banner.
       Determine appropriate values for validation forms
PD5
       needed to support intended processing.
       Determine procedure for maintenance validation
PD6
       forms.
PD7    Build forms in TEST.
       Build population selection/batch posting rules in TEST
PB8
PD9    Move completed forms to PPRD.
PD10   Make screen prints for documentation.
PD11   Ensure all jobs with this module work in PPRD.
       Build population selection/batch posting rules in
PD12
       PROD
PD13   Move final form values from PPRD to PROD.
PD14   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
PD15
PD16   Develop additional reports as needed.
PD17   Test and sign off each local report.
PD18   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
PD19
       processes.
       Develop and document policies and procedures




PD20




       Determine conversion scope and consider which
PD21
       records and data elements to process.
PD22   Write and test conversion program.
PD23   Convert data.
PD24   Verify and correct data.
       Write user procedures reflecting Banner usage, new
PD25
       policies and procedures.
       Publish and distribute new policies/procedures and
PD26
       provide appropriate forms.
       Train end users in the use of the Packaging &
       Disbursements Module.
PD27
       Train end users in Packaging processes.




PD28
       Train end users in Disbursement processes.




PD29




PD30   Train end users in report submission.
       Determine hardware and equipment needs for offices
PD31
       needing access to forms.
PD32   Wire offices and test equipment.
PD33   Packaging & Disbursements in production.
       Determine current information in legacy system that is
PD34   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


PD35




                            Pell Payment
       Review current policies and procedures relative to the
PP1
       maintenance of Pell payment information.
       Read and review related info in User and Technical
PP2
       Manual.
PP3    Review the EDE forms for appropriate use
PP4    Read User manuals from Dept of ED
PP5    Ensure PC and Modem meet specs
       Review Pell Module forms and determine appropriate
PP6
       usage.
       Determine what data will be maintained and tracked in
PP7
       Banner.
       Determine appropriate values for validation forms
PP8
       needed to support intended processing.
       Determine procedure for maintenance validation
PP9
       forms.
PP10   Build forms in TEST.
       Ensure that moving flat files back and forth from PC
PP11
       and Banner is enabled
PP12   Make screen prints for documentation.
PP13   Ensure all jobs with this module work in PPRD.
PP14   Move final form values from PPRD to PROD.
PP15   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
PP16
PP17   Develop additional reports as needed.
PP18   Test and sign off each local report.
PP19   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
PP20
       processes.
       Develop and document policies and procedures




PP21




       Write user procedures reflecting Banner usage, new
PP22
       policies and procedures.
       Publish and distribute new policies/procedures and
PP23
       provide appropriate forms.
       Train end users in the use of the Pell Module.


PP24
       Train end users in processes.




PP25




PP26   Train end users in report submission.
       Determine hardware and equipment needs for offices
PP27
       needing access to forms.
PP28   Wire offices and test equipment.
PP29   Pell processing in production.
       Determine current information in legacy system that is
PP30   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


PP31




                       Population Selection
       Read and review related info in User and Technical
PS1
       Manual.
       Review the Population Selection forms for appropriate
PS2
       use.
PS3    Build forms in TRNG.
PS4    Ensure all jobs with this module work in TRNG.
PS5    Move completed forms to TEST.
PS6    Ensure all jobs with this module work in TEST.
PS7    Make screen prints for documentation.
PS8    Move final forms to PROD.
PS9    Determine security for each form/job in module.
PS10   Establish grants/permissions.
       Develop policies and procedures.


PS11




       Determine procedure for maintenance of
PS12   validation/rules forms during implementation, during
       production and for each new aid year.
PS13   Develop plan of action for training end user staff
       Train end user staff
PS14


PS15   Population Selection processing in production.
       Determine current information in legacy system that is
PS16   not provided for in Banner and determine procedures
       w/in Banner.
       Module Post Implementation Assessment


PS17




                Satisfactory Academic Progress
       Review current policies and procedures relative to the
SAP1   maintenance of satisfactory academic progress
       processing
       Read and review related info in User and Technical
SAP2
       Manual.
       Review SAP forms and determine appropriate usage.
SAP3
       Determine what data will be maintained and tracked in
SAP4
       Banner.
       Determine appropriate values for validation forms
SAP5
       needed to support intended processing.
       Determine procedure for maintenance validation
SAP6
       forms.
SAP7   Build forms in TEST.
SAP8   Make screen prints for documentation.
      Build population selection/batch posting rules in
SAP9
      TRNG
SAP10 Ensure all jobs with this module work in SAPRD.
SAP11 Move final form values from PPRD to PROD.
SAP12 Develop specifications for additional reports.
      Set priorities and time frames for each special report.
SAP13
SAP14 Develop additional reports as needed.
SAP15 Test and sign off each local report.
      Build population selection/batch posting rules in TEST
SAP16
SAP17 Determine security for each form/job in module.
      Establish grants/permissions for all forms and
SAP18
      processes.
      Determine when and if conversion of aid history will
SAP19
      take place
SAP20 Determine conversion requirements
SAP21 Complete conversion in TEST
SAP22 Complete conversion in PROD
        Develop and document policies and procedures




SAP23




      Write user procedures reflecting Banner usage, new
SAP24
      policies and procedures.
      Publish and distribute new policies/procedures and
SAP25
      provide appropriate forms.
      Train end users in the use of User Defined Forms.


SAP26



        Train end users in processes.


SAP27



SAP28 Train end users in report submission.
      Determine hardware and equipment needs for offices
SAP29
      needing access to forms.
SAP30 Wire offices and test equipment.
SAP31 SAP processing in production.
      Determine current information in legacy system that is
SAP32 not provided for in Banner and determine procedures
      w/in Banner
      Module Post Implementation Assessment


SAP33




                       Short Term Credit
      Review current policies and procedures relative to the
STC1
      maintenance of short term credit processing
      Read and review related info in User and Technical
STC2
      Manual.
      Review Short Term Credit forms and determine
STC3
      appropriate usage.
      Determine what data will be maintained and tracked in
STC4
      Banner.
      Determine appropriate values for validation forms
STC5
      needed to support intended processing.
      Determine procedure for maintenance validation
STC6
      forms.
STC7 Build forms in TEST.
STC8 Make screen prints for documentation.
STC9 Ensure all jobs with this module work in PPRD.
STC10 Move final form values from PPRD to PROD.
STC11 Develop specifications for additional reports.
        Set priorities and time frames for each special report.
STC12
STC13 Develop additional reports as needed.
STC14 Test and sign off each local report.
STC15 Determine security for each form/job in module.
      Establish grants/permissions for all forms and
STC16
      processes.
      Determine when and if conversion of aid history will
STC17
      take place
STC18 Determine conversion requirements
STC19 Complete conversion in TEST
STC20 Complete conversion in PROD
      Develop and document policies and procedures




STC21




      Write user procedures reflecting Banner usage, new
STC22
      policies and procedures.
      Publish and distribute new policies/procedures and
STC23
      provide appropriate forms.
        Train end users in the use of Short Term Credit
        Forms.
STC24



STC25 Train end users in processes.
STC26 Train end users in report submission.
      Determine hardware and equipment needs for offices
STC27
      needing access to forms.
STC28 Wire offices and test equipment.
STC29 Short Term Credit processing in production.
      Determine current information in legacy system that is
STC30 not provided for in Banner and determine procedures
      w/in Banner
      Module Post Implementation Assessment


STC31




                       Student Employment
        Review current policies and procedures relative to the
SE1     maintenance of student employment processing

        Read and review related info in User and Technical
SE2
        Manual.
        Review Student Employment forms and determine
SE3
        appropriate usage.
        Determine what data will be maintained and tracked in
SE4
        Banner.
       Determine appropriate values for validation forms
SE5
       needed to support intended processing.
       Determine procedure for maintenance validation
SE6
       forms.
SE7    Build forms in TEST.
SE8    Make screen prints for documentation.
SE9    Ensure all jobs with this module work in PPRD.
SE10   Move final form values from PPRD to PROD.
SE11   Develop specifications for additional reports.
       Set priorities and time frames for each special report.
SE12
SE13   Develop additional reports as needed.
SE14   Test and sign off each local report.
SE15   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
SE16
       processes.
       Determine when and if conversion of aid history will
SE17
       take place
SE18   Determine conversion requirements
SE19   Complete conversion in TEST
SE20   Complete conversion in PROD
       Develop and document policies and procedures




SE21




       Write user procedures reflecting Banner usage, new
SE22
       policies and procedures.
       Publish and distribute new policies/procedures and
SE23
       provide appropriate forms.
       Train end users in the use of Student Employment
       Forms.
SE24
       Train end users in processes.




SE25




SE26   Train end users in report submission.
       Determine hardware and equipment needs for offices
SE27
       needing access to forms.
SE28   Wire offices and test equipment.
SE29   Student Employment Module in production.
       Determine current information in legacy system that is
SE30   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


SE31




                        Technical & System
T1     Establish implementation team.
T2     Establish test system.
T3     Establish training/testing facility.
       Determine terminal configurations. Generate
T4     Function Key reference chart depending upon
       terminal configuration.
       Develop documentation distribution list and plan for
T5     reproduction, distribution, and updating manuals

       Distribute training manuals
T6

       Establish grants, user IDs, passwords, and form
T7
       security for training purposes
       Determine operating system/Banner log-in
T8
       procedures.
T9     Establish operations procedures.
T10    Establish backup and restore procedures.
T11    Establish disaster recovery procedures.
       Establish procedures for system maintenance:
T12
       ORACLE; Operating System; Banner
       Develop and publicize procedures for reporting
T13
       ORACLE errors.
       Develop and publicize procedures for reporting
T14
       Banner errors.
      Secure SCT training agendas, confirm dates and
      participants, schedule use of training facility, distribute
T15
      agenda to key administrators and participants

      Develop institutional task log and implementation
T16
      schedule
      Determine authority and responsibility for
T17
      maintenance of system security.
      Determine hardware requirements for production
T18   system (terminals, printers, modems, controllers, tape
      drives, etc.).
T19   Acquire necessary hardware.
      Establish Conversion Plan: Decide what data is to be
      converted and how and it what order; Evaluate data
      to be converted. Make corrections, if necessary;
      Write conversion programs or data entry instructions
T20
      for manual conversions; Test conversion programs
      or manual instructions (in stages); Verify
      conversions in production system

      Determine disk requirements for production systems.
T21
T22   Create and size production environment
      Develop change control logging procedures for site-
T23
      specific enhancements.
      Develop procedures for production migration (initial
T24   install, stage tapes, site-specific enhancements, etc.)

      Establish grants, user IDs, passwords, form security
T24
      for production operation
      Consider public relations functions. Plan for
T26   notifications to CWS and employees regarding
      implementation of new system.
        Develop an operation‟s production schedule for all
T27
        batch jobs that will be run on a regular basis.
        Establish databases and uses e.g. TRNG, TEST,
        PPRD, PROD
T28



        Establish Banner Documentation link in Database
T29
        (load documentation library)
        Establish default temporary location for Job
T30
        Submission output (local drive)

                          Title IV Processing
        Review current policies and procedures relative to the
TIV1
        maintenance of Title IV processing
        Read and review related info in User and Technical
TIV2
        Manual.
        Review Title IV forms and determine appropriate
TIV3
        usage.
        Determine what data will be maintained and tracked in
TIV4
        Banner.
        Determine appropriate values for validation forms
TIV5
        needed to support intended processing.
        Determine procedure for maintenance validation
TIV6
        forms.
TIV7    Build forms in TEST.
TIV8    Make screen prints for documentation.
TIV9    Ensure all jobs with this module work in PPRD.
TIV10   Move final form values from PPRD to PROD.
TIV11   Develop specifications for additional reports.
        Set priorities and time frames for each special report.
TIV12
TIV13   Develop additional reports as needed.
TIV14   Test and sign off each local report.
TIV15   Determine security for each form/job in module.
        Establish grants/permissions for all forms and
TIV16
        processes.
        Determine when and if conversion of aid history will
TIV17
        take place
TIV18   Determine conversion requirements
TIV19   Complete conversion in TEST
TIV20   Complete conversion in PROD
        Develop and document policies and procedures




TIV21




        Write user procedures reflecting Banner usage, new
TIV22
        policies and procedures.
        Publish and distribute new policies/procedures and
TIV23
        provide appropriate forms.
        Train end users in the use of Title IV Forms.


TIV24



        Train end users in processes.




TIV25




TIV26   Train end users in report submission.
        Determine hardware and equipment needs for offices
TIV27
        needing access to forms.
TIV28   Wire offices and test equipment.
TIV29   Title IV processing in production.
        Determine current information in legacy system that is
TIV30   not provided for in Banner and determine procedures
        w/in Banner
        Module Post Implementation Assessment


TIV31




                         User Defined Forms
        Review current policies and procedures relative to the
UD1
        maintenance of user defined forms.
        Read and review related info in User and Technical
UD2
        Manual.
        Review User Defined forms and determine
UD3
        appropriate usage.
        Determine what data will be maintained and tracked in
UD4
        Banner.
        Determine appropriate values for validation forms
UD5
        needed to support intended processing.
        Determine procedure for maintenance validation
UD6
        forms.
UD7     Build forms in TEST.
UD8     Make screen prints for documentation.
UD9     Ensure all jobs with this module work in UDRD.
UD10    Move final form values from PPRD to PROD.
UD11    Develop specifications for additional reports.
       Set priorities and time frames for each special report.
UD12
UD13   Develop additional reports as needed.
UD14   Test and sign off each local report.
UD15   Determine security for each form/job in module.
       Establish grants/permissions for all forms and
UD16
       processes.
       Determine when and if conversion of aid history will
UD17
       take place
UD18   Determine conversion requirements
UD19   Complete conversion in TEST
UD20   Complete conversion in PROD
       Develop and document policies and procedures




UD21




       Write user procedures reflecting Banner usage, new
UD22
       policies and procedures.
       Publish and distribute new policies/procedures and
UD23
       provide appropriate forms.
       Train end users in the use of User Defined Forms.


UD24



UD25   Train end users in processes.
UD26   Train end users in report submission.
       Determine hardware and equipment needs for offices
UD27
       needing access to forms.
UD28   Wire offices and test equipment.
UD29   User Defined Forms processing in production.
       Determine current information in legacy system that is
UD30   not provided for in Banner and determine procedures
       w/in Banner
       Module Post Implementation Assessment


UD31
Comments
Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Assign a student to a
Budgeting Group through
Immediate Process;
Assign a student to a
Budgeting Group manually;
Assign students to
Budgeting Groups through
Batch Process;
Changing an aid period for
an individual student;
Changing an aid period for
a group of students;
Assigning a Mixed
Enrollment Budget;
Changing or adjusting a
Budget Component;
Adding a Budget
Component for an
individual student;
Changing or adding a
Budget Component for a
group of students;
Using the ROARMAN Form
for Applicant Budgets;
Producing the Applicant
Budget Report
Develop paper for
how documents will
flow from point of
arrival.     Determine
procedure for
maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid year.
Develop plan of action
for training end users




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.     Determine
procedure for
maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid year.
Develop plan of action
for training end users
Navigation and
General Person
Module training will
also be required
unless previously
provided.




Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.     Determine
what kind of tracking
letters to send and
how often.
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid year.
Develop plan of action
for training end user
staff.
Automated or manual.




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Auto-Assign a Student to a
Tracking Group;
Manually Assign a Student to a
Tracking Group;
Manually Add Tracking Items
to a Student File;      Assign
a Student to a Tracking Group
Through Immediate Process;
Assign a Student to a Tracking
Group manually;
Assign Students to Tracking
Groups Through Batch
Process;                Adding
a Tracking Requirement or an
Internal Document;
Adding a Non-Coded Tracking
Requirement;
Updating the Status of a
Tracking Requirement
Updating the Status of a Non-
Coded Tracking Requirement
Adding a Tracking
Requirement to a Group of
Students (E.G. Entrance
Interview, Distance Learning
Requirements for New Term);
Adding a Fat Requirement in
Batch;                  Adding
an Exit Interview Requirement
in Batch; Generating a
Missing Information Letter
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.;
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid
year.;
Develop plan of action
for training end users




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Batch Post an item to
a Population Selection




Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.


Include review of
name and ID change
procedures,
maintenance of
addresses, use of
holds, use of
comments, offices to
maintain data when
changes are
necessary, etc.
Review required forms
and values and
determine how they
will be used. Review
optional forms and
values and determine
whether and how they
will be used.

Pay particular
attention to name
searches to reduce
the number of
duplicate records.
Standards for all
Banner data entry of
biographic/demograph
ic data.
Cross-Functional
Team needed-
determine owner(s)
Cross-Functional
Team needed
Cross-Functional
Team needed
Identify offices
involved in
maintaining records
and cut off points, e.g.
Admissions will
change applicants
addresses until they
register, than
Registrar does so.
Include
review/preparation of
the following forms:
Initial
biographic/demograph
ic data collection
forms;
Name and ID change
forms;
Address change
forms;
Telephone number
change forms
Interfaces to consider:
Interface to Human
Resources System;
Interface to Alumni
System;
Interface to Finance
System (vendor
names, IDs, and
addresses);
Interface to Financial
Aid System;
Interface to Student
System;
Other Systems (list)
Consider which
records and data
elements to convert,
pre-conversion data
clean-up efforts, post-
conversion
verification, and
correction process




Navigation training will
also be required. Most
offices on campus will
need training in
appropriate modules.
Train users using new
procedures manual.
Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Export EDE
Corrections; Import
EDE Corrections;
EDE Dataload;
Resolving Suspended
Records; Printing
ISIR's; Extracting
Correction and ISIR
Request Files;
Reviewing Batches
that have been sent to
CPS; Resubmitting
a Batch to CPS;
Loading Rejected ISIR
Correction Files;
Generating a Report
of Corrections that
have been sent to
CPS
Develop paper for
how documents will
flow from point of
arrival.;
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid
year.;
Develop plan of action
for training end users


Automated or manual.
Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Create Loan origination
records;
Print Promissory Notes;
Extract Loan origination
records;
Upload origination
acknowledgements;
Dl Promissory Note
Manifest;
Upload Promissory Note
acknowledgements;
Extract origination change
records; Upload
origination change
acknowledgement records
Print Disclosure
Statements;
Record cash draw-downs;
View Dl account
summaries;
Disburse Loans; Extract
Loan Disbursements;
Upload Disbursement
acknowledgements;
Dl Disbursement Matching
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.;
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid
year.;
Develop plan of action
for training end users


Automated or manual.
Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Create Electronic Loan
Applications;
Extract Loan Applications
for transmittal;
Upload Loan Application
status records;
Load EFT to holding table;
Record receipt of EFT
cash;
Post EFT to Data to Loan
records;
Disburse EFT to student
accounts;
Review EFT rosters loaded
and awaiting posting
Create Aging Report of non-
disbursed Loans;
Report students not fully
funded from Loans;
Return Loan proceeds to
lender
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.;
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid year.
Develop plan of action
for training end user
staff.


Automated or
manual.;
Funds codes must
exist for each aid year
to be able to do aid
history conversion
Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Create New Funds;
Maintain Existing
Funds; Monitor
Fund Information




Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid year.
Develop plan of action
for training end users




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.




Ensure these
directories have „write‟
privileges.

All information
brought into and
retrieved from Banner
must be moved to a
local PC via FTP.

This program is used
to concatenate
several files into one.


Unless otherwise
noted, print all jobs to
DATABASE
Optional
Binary mode




Make screen prints or
extract data for
backup.
Who is allowed to create
SPRIDEN records?; Will
recruitment records be
created as part of data
load?;
What are data entry
standards for institution?;
Who maintains (owns)
name, address, etc
changes?;
Ensure matching rules are
adequate to prevent
creation of Duplicate
PIDMs.;
Distribute procedures to
key personnel for review
and approval.;
Determine procedure for
maintenance of
validation/rules forms
during implementation,
during production and for
each new aid year.;
Develop a plan of action for
training office staff Train
end user staff.
Who will build letters?;
Who will identify need
for new letters?;
What is letter gen
flow?




Run Tracking Letters;
Run Award Letters;
Create A New Letter




Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Enter a Manual Need Analysis
Record;                 Correct
a Need Analysis Record;
Calculate Need Analysis for an
Individual Student;
Calculate Need Analysis Using
the Immediate Process Form;
Calculate Need Analysis in
Batch;
Reset Need Analysis
Calculation to an Original
(CPS) Calculation;
Change the Current Record;
Lock or Unlock the Current
Record;
Override EDE Need Analysis
Calculation Assumptions;
Override ISIR Rejects;
Review Comment Code Text;
Resolve A C Flag;
Review an NSLDS Record;
Create a Manual NSLDS
Record to Resolve a Default or
Overpayment;
Override NSLDS Edits to
Resolve a Default or
Overpayment;
Complete Verification Using
the Verification Form;
Simulate a Need Analysis
Calculation
Enter Professional Judgment
Adjustments for a Need
Analysis Calculation;
Change The EFC To A Non-
Nine-Month EFC;         Override
Dependency Status;
Select a Student for
Verification
Update the Pell Verification
Status;
Log EDE and Need Analysis
Corrections for the Audit Trail;
Delete an ISIR Correction;
Add Institution Id to a
Student's ISIR;
Request a Duplicate ISIR;
Print the Basic Applicant
Report
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.;
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid
year.;
Develop plan of action
for training end users


Automated or manual.
Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Assign a student to a
Packaging Group through
Immediate Process;
Assign a student to a
Packaging Group manually;
Assign students to Packaging
Groups through Batch
Process;       Offering an
Award Package using
Automatic Packaging to an
individual student      Offering
an Award Package using
Automatic Packaging to a
group of students;      Offering
an Award Package using
Automatic Packaging through
Immediate Process;         Using
the ROARMAN Form for
Applicant Packaging;
Packaging a Fund manually;
Changing the Offered Amount
of a Fund;      Changing the
status of a Fund or canceling a
Fund manually;        Accepting
a lower amount of a Fund than
what was offered;
Changing the term distribution
of a Fund;      Changing the
scheduled disbursement
date(s) for a Fund;
Changing the memo expiration
date(s) for a fund;
Canceling a Fund in batch;
Locking a Fund to prevent
changes from being made;
Requesting an Award Letter or
canceling an Award Letter for a
student;       Resolving an
Run the Disbursement
Process from Immediate
Process;        Run the
Disbursement Process
in batch;       Generating
the Student Aid
Disbursement Report
(displays disbursement
results);      Generating
the Disbursement
Validation Report
(displays whether a
student is still eligible for
aid that had been
disbursed Previously);
Generating the Applicant
Disbursement Report
(displays detailed
information about an
applicant‟s
disbursements);
Resolving disbursement
errors;
Maintain Contract
Assignment;
Maintain Exemption
Assignment;
Roll
Contracts/Exemptions
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.;
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid
year.;
Develop plan of action
for training end users




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Awarding the Pell
Grant on-line;
Awarding the Pell
Grant using the
Immediate Process
Form;
Awarding the Pell
Grant in batch;
Adjusting a Pell Grant
award;
Manually creating an
initial Pell origination
record;
Deleting an initial Pell
origination record;
Creating an initial Pell
origination record In
batch;
Manually selecting a
record for Pell
origination;
Manually creating an
updated Pell
origination record
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.




Who will write pop
selects?
What will be the
testing process?
What is the process to
request new pop sel?
Create a new
Population Selection;
Run an existing
Population Selection




Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.;
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid
year.;
Develop plan of action
for training end users




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Assign students to
SAP Groups;
Generate SAP Letters
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.;
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid
year.;
Develop plan of action
for training end users
Navigation and
General Person
Module training will
also be required
unless previously
provided.




Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.;    Determine
procedure for
maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid
year.;
Develop plan of action
for training end users




Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Authorize a student to
work;
Entering additional
authorizations/placements;
Deleting an authorization to
work;
Manually entering student
employment earnings;
Adjusting student
employment earnings;
Printing the Student
Employment Authorization
Report;
Printing the Student
Employment Departmental
Pay Period Report;
Printing the Payroll
Exception Report;
Printing the Student
Employment Earnings
Control Report; Running
the Payroll Load Process
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.




Develop document
and materials
repository on server.
Clone databases if
necessary. Identify
databases used for
training, testing,
conversion testing,
etc.
Develop paper for
how documents will
flow from point of
arrival.;
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid
year.;
Develop plan of action
for training end users
Navigation and
General Person
Module training will
also be required
unless previously
provided.
Processes to include:
Maintaining Title IV
authorization codes
(Student Accounts);
Applying Title IV
payments (Student
Accounts);
Unapplying charges
and payments to
reflect Title IV funds
(Student Accounts);
Refunding Title IV
funds to the student
(Student Accounts);
Maintaining Original
Charges (Registrar);
Maintaining the
withdrawal status of
students (Registrar);
Calculating Title IV
repayment amounts
(Financial Aid);
Disbursing R2T4
amounts (Financial
Aid)
Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
Develop paper for
how documents will
flow from point of
arrival.;
Determine procedure
for maintenance of
validation/rules forms
during
implementation,
during production and
for each new aid
year.;
Develop plan of action
for training end users
Navigation and
General Person
Module training will
also be required
unless previously
provided.




Determine the
implementation
success. Measure
how the functionality
meets the needs of
the users.
                                                                                   Planned                 Actual
ID                          Milestone                              Pre- Owner Start Date End Date    Start Date End Date Comments
     When proposed technology architecture diagram is
 1                                                                      Greg
     discussed and confirmed by CTS and SCT
     When technology component bill of materials are prepared
 2                                                                  1   Greg             8-Jul-05
 3   When technology components are procured                        2   John             15-Jul-05
 4   When technology hardware is racked                             3   Sheryl           5-Aug-05
     When operating systems are installed on pre-production
 5                                                                  4   Greg            10-Aug-05
     hardware
 6   When SEED, TRAIN, PREPROD Databases are loaded                 4   Greg            19-Aug-05
     When 3rd party applications are installed in pre-production
 7                                                                  4   Greg            19-Aug-05
     When BANNER Applications are installed and configured
 8                                                                  6   Greg            26-Aug-05
     on pre-production hardware
 9   When Web access is enabled in pre-production                       Greg            30-Aug-05
     When pre-production environment is ready for development
10                                                                  8   Greg            31-Aug-05
11 When operating systems are installed on production               3   Greg
   When PROD database instance is transitioned from pre-
12                                                                      Greg
   production
13 When 3rd party applications are installed in production              Greg
14 When BANNER Applications are installed on production             8   Greg
15 When web access is enabled in production                        14   Greg
16 When production environment is ready for deployment             10   Greg
   When inventory and procedures to support technology
17                                                                  7   Greg
   environments are updated and shared

                     Technical & System Tasks
T1   Establish implementation team.
T2   Establish test system.
T3   Establish training/testing facility.
     Determine terminal configurations. Generate
T4   Function Key reference chart depending upon
     terminal configuration.
      Develop documentation distribution list and plan for
T5    reproduction, distribution, and updating manuals

      Distribute training manuals                                 Develop document
T6                                                                and materials
                                                                  repository on server.
      Establish grants, user IDs, passwords, and form
T7
      security for training purposes
      Determine operating system/Banner log-in
T8
      procedures.
T9    Establish operations procedures.
      Establish backup and restore procedures.
T10
      Establish disaster recovery procedures.
T11
    Establish procedures for system maintenance:
T12
    ORACLE; Operating System; Banner
    Develop and publicize procedures for reporting
T13
    ORACLE errors.
    Develop and publicize procedures for reporting
T14
    Banner errors.
    Secure SCT training agendas, confirm dates and
    participants, schedule use of training facility, distribute
T15
    agenda to key administrators and participants

    Develop institutional task log and implementation
T16
    schedule
    Determine authority and responsibility for
T17
    maintenance of system security.
    Determine hardware requirements for production
T18 system (terminals, printers, modems, controllers, tape
    drives, etc.).
      Acquire necessary hardware.
T19
    Establish Conversion Plan: Decide what data is to
    be converted and how and it what order; Evaluate
    data to be converted. Make corrections, if necessary;
    Write conversion programs or data entry instructions
T20
    for manual conversions; Test conversion programs
    or manual instructions (in stages); Verify
    conversions in production system

      Determine disk requirements for production systems.
T21
      Create and size production environment
T22
    Develop change control logging procedures for site-
T23
    specific enhancements.
    Develop procedures for production migration (initial
T24 install, stage tapes, site-specific enhancements, etc.)

    Establish grants, user IDs, passwords, form security
T24
    for production operation
    Consider public relations functions. Plan for
T26 notifications to CWS and employees regarding
    implementation of new system.
    Develop an operation‟s production schedule for all
T27
    batch jobs that will be run on a regular basis.
    Establish databases and uses e.g. TRNG, TEST,             Clone databases if
    PPRD, PROD                                                necessary. Identify
                                                              databases used for
T28
                                                              training, testing,
                                                              conversion testing,
                                                              etc.
    Establish Banner Documentation link in Database
T29
    (load documentation library)
    Establish default temporary location for Job
T30
    Submission output (local drive)
                                 Planned                Actual
ID   Milestone   Pre- Owner Start Date End Date   Start Date End Date Comments
                                 Planned                Actual
ID   Milestone   Pre- Owner Start Date End Date   Start Date End Date Comments
                                 Planned                Actual
ID   Milestone   Pre- Owner Start Date End Date   Start Date End Date Comments
                                 Planned                Actual
ID   Milestone   Pre- Owner Start Date End Date   Start Date End Date Comments

								
To top