HomeMy WebLinkAboutContract 26039 CITY SECRETARY
WNTRACT NO. a=
AMENDMENT TO CITY SECRETARY
CONTRACT NO. 25527
COUNTY OF TARRANT §
STATE OF TEXAS §
THIS agreement is made between the City of Fort Worth ("City"), acting by and through
Charles R. Boswell, its duly authorized Assistant City Manager, and Evergreen Systems
Inc. ("Evergreen"), acting by and through Richard Stark, its duly authorized Chief Financial
Officer.
WHEREAS, the City and Evergreen have entered into that certain agreement identified as
City Secretary Contract No. 25527 for the development of an online service order system
according to a scope of services specified in attachments to said City Secretary Contract
for compensation not to exceed $147,695.00; and
WHEREAS, it is the mutual desire of the parties to amend said City Secretary Contract No.
25527, to change the scope of services and increase the amount of compensation;
NOW, THEREFORE, THIS CONTRACT FURTHER WITNESSETH:
1.
SECTION 1.1 "Evergreen's Services" of City Secretary Contract No. 25527, currently on
file in the office of the City Secretary of the City of Fort Worth is hereby amended to read
as follows:
Evergreen hereby agrees to provide the City's Information Technology Solutions
Department ("IT Solutions") with professional consulting and software development
services to assist IT Solutions in the development of an online service order system
interfaced to an online billing system for use by IT Solutions customers (collectively the
"Project"). The project is deliverable in three portions, Fixed Price (Attachment A); Time
and Materials (Attachment B); and Additional Services (Attachment C), described in detail,
attached hereto and hereby made a part of this agreement for all purposes. The City and
Evergreen may change the scope of the Project by substituting an amended Attachment
"A," "B," or "C," signed by both the City and Evergreen, which shall then be attached to this
agreement and made a part of this Agreement for all purposes. Because Attachment "C"
amends the original contract, if any provision in Attachment "C" conflicts with any provision
in Attachments "A" and "B," Attachment "C" shall take precedence.
Additionally, SECTION 3. "COMPENSATION" of the said contract is hereby amended to
read as follows:
The City shall pay Evergreen a sum not to exceed $216,020.00 for all services
1
FT. wimv Va".
provided and expenses incurred in the carrying out and fulfillment of Evergreen's duties
and obligations under this agreement. The specific services and expenses involved in
each step of the Project are described in Attachments "A," "B" and "C." if the City is not
s,atsified with Evergreen's performance at any step or point in the Project, the City shall
notify Evergreen in writing and may suspend payment for the services that are
unsatisfactory until the problem is remedied. In such an event, the parties shall negotiate
and endeavor in good faith to remedy or mitigate the problem in a timely manner. In no
event shall the City's aggregate financial obligations to Evergreen under this Agreement
exceed $216,020.00 If this Agreement is terminated prior to the date that Evergreen
provides all services required hereunder, Evergreen shall, at the City's request, complete
the step or line item of work, as provided in Attachments "A," "B" and "C," on which
Evergreen is working at the time, and the effective date of termination shall be extended
if necessary until Evergreen has completed the step or line item of work.
2.
All other terms, provisions, conditions, covenants and recitals of said City Secretary
Contract No. 25527 which are not expressly amended herein shall remain in full force and
effect during the term hereof.
IN WITNESS WHEREOF, the parties hereto have executed this Agreement in Fort Worth,
Tarrant County, Texas, this day of , 2000.
CITY OF FORT WORTH V ERG 114 S T S T EMS INC.
By: - j
CCharles R. Boswell Richard Stark
Assistant City Manager Chief Financial Officer
TEST:
City Secretary
APPROVED AS TO FORM AND LEGALITY:
_
2-a contract Authorization
,4'�CITY TTORNEY D,O�
G�Zy�7 Date
Date
Attachment C
Addendum
The City of Fort Worth has accepted the following technical design
documents and statements of work, upon which additional costs are based.
These documents are as follows and are incorporated into this Attachment C
as a complete scope of work for the Project.
1. Detailed Technical Design- Coding of Migration-Customizations, dated May
1, 2000 and accepted May 5, 2000
2. Detailed Technical Design- End User Web Site (KML), dated May 9, 2000
and accepted May 17, 2000
3. Detailed Technical Design- End User Web Site (WEB), dated May 25,2000
and accepted May 26,2000.
4. Tivoli Service Desk Change Management User; Problem Management User
Training Services Statement of Work, dated and accepted May 25,2000
5. Tivoli Service Desk, Change Management Admin. Problem Management
Admin Training Services Statement of Work, dated and accepted May
25,2000
The following additional costs are associated with the scope of work for the
Project.
Task Description Number of Das Cost
Scope Changes
Additional days for 14 $21,000
Coding of Migration-
Customizations
Additional days for End 9.5 $14,250
User Web Site (KML and
WEB
Subtotal $35,250
Less Evergreen Discount 10%
Total-Scope Changes $31172S
Traininq Services
Tivoli Service Desk User $18,000
Training
Tivoli Service Desk $15,000
Admin Training
Expenses-Not to Exceed $3,600
Total-Training $36,600
Services
Grand Total- $68,325
Additional Costs
Plus- Original Contract $147,695
New Contract Total 216 020
Ak,&A, ALA&
Evergreen Systems,Inc.
Tivoli Service Desk 6.0
Coding of Migration-Customizations
Detailed Technical Design
Updated May 1, 2000
City of Fort Worth
Evergreen Systems,Inc. Prepared By: David M.Broom
1851 Ale-rander Bell Drive Development Systems
Suite 450 (904) 910-3291
Reston, Virginia 20191 David.Broom c everereensys.com
QT MCIMA ff
Table-ofContents
Tableof Contents............................................................................................................................................2
Tableof Figures..............................................................................................................................................4
Introduction.....................................................................................................................................................5
DocumentDefinition.......................................................................................................................................6
INTRODUCTION............................................................................................................................................6
PROJECTSCOPE............................................................................................................................................6
APPENDICES.................................................................................................................................................7
ProjectDefinition............................................................................................................................................8
Assumptions....................................................................................................................................................9
Objectives......................................................................................................................................................10
Resources......................................................................................................................................................11
Strategy.........................................................................................................................................................12
ProjectScope.................................................................................................................................................14
SYSTEM REQUIREMENTS/ARCHITECTURE................................................................................................14
Screensand Logic.........................................................................................................................................16
(Tivoli Service Desk/Problem Management 6.0 Customizations)..............................................................16
CALL REGISTRATION NOTEBOOK...............................................................................................................16
Workflowmodifications:................................................................................................................................... 16
Workflowmodifications:............... ................... .............................................................................................16
PROBLEMSTATUS NOTEBOOK...................................................................................................................22
Workflowmodifications:...................................................................................................................................22
Workflowmodifications:...................................................................................................................................22
MAINFRAME-PAYROLL MASTER EXTRACT/TSD 6.0 SYNCHRONIZATION UTILITY................................29
PeopleUpdate...............................................................................................................................................29
Workflowmodifications:...................................................................................................................................30
MAINFRAME- MARS EXTRACT/TSD 6.0 SYNCHRONIZATION UTILITY..................................................32
FACUpdate..................................................................................................................................................32
Workflowmodifications:...................................................................................................................................32
NOTIFICATIONSTEXT.................................................................................................................................34
Workflowmodifications:...................................................................................................................................34
GROUP TRACKING THROUGH-OUT A CASES LIFECYCLE............................................................................35
Workflowmodifications:............................................................................................................ ......................35
ADD/EDITNIEW PEOPLE............................................................................................................................37
Workflowmodifications:...................................................................................................................................37
POST-MIGRATION SQL TRANSACTION TO MOVE TPM 5.0.2 FAC FLEX FIELD DATA INTO THE NEW
PROB_FAC TABLE...................................................................................................................................39
ASSETNOTEBOOK......................................................................................................................................40
Workflowmodifications:...................................................................................................................................40
Workflowmodifications:............................................................................................................ ......................40
CHANGENOTEBOOK..................................................................................................................................46
Workflowmodifications:...................................................................................................................................46
AppendixA — Test Cases......................................................................................................52
TestCase Documenation...............................................................................................................................52
MIGRATION/CUSTOMIZATION NOT AFFECTING THE USER INTERFACE......................................................52
DatabaseModifications........................................................................................................................52
Altering Tables,Views,Triggers,Stored Procedures,and Constraints..............................................................52
Performance.......................................................................................................................................................52
BusinessRules.......................................................................................................................................52
ConditionalLoading of Fields...........................................................................................................................52
USER INTERFACE MODIFICATIONS.............................................................................................................53
State Transition Conditions...................................................................................................................53
FormInitialization.............................................................................................................................................53
FormIn-Use.......................................................................................................................................................53
Notebooks..........................................................................................................................................................53
MIGRATION/CUSTOMIZATION FUNCTIONAL RESULTS...............................................................................53
2
Behaves as Documented........................................................................................................................53
Certification.......................................................................................................................................................53
Acceptance Test Instructions.................................................................................................................53
Migration of Current Customizations Test Cases..........................................................................................54
<TITLE OF MIGRATED/CUSTOMIZED TASK TO BE TESTED>. (CODE COMMENT REFERENCE NUMBER).........54
TestCase(I).......................................................................................................................................................54
TestCase(2).......................................................................................................................................................54
TestCase(3).......................................................................................................................................................54
Appendix B — SQL Modifications................................................................................55
3
Table of Fizures
Figure 1 displays the Call Registration Notebook.........................................................................................17
Figure 2 displays the Problems Page of the Problem Status Notebook.........................................................23
Figure 3 displays the Payroll Master/TPM 6.0 System Integration.............................................................31
Figure 4 displays the MARS/TPM 6.0 System Integration.........................................................................33
Figure 5 displays the Work with Problems Inquiry Screen...........................................................................35
Figure 6 displays the Add Person Dialog......................................................................................................37
Figure 7 displays the Asset Notebook...........................................................................................................41
Figure 8 displays the Change Notebook........................................................................................................51
4
Introduction
The following is a detailed design document, which describes the Migration-Customizations for Tivoli
Service Desk 6.0 with the latest PTF's. The following detailed design was derived from the Statement of
Work dated October 08, 1999 and supporting information gathered during the kickoff meetings from
January 12, 2000 through January 14, 2000.
The summary of Migration-Customizations is included in this detailed design is as follows:
W TPM 6.0 Customizations.
W TAM 6.0 Customizations
W TCM 6.0 Customizations
W TNM 6.0 Implementation
W Architectural Hardware/Software Design Recommendations
W Post-Development Configuration
W Custom SQL Scripts
q:> Product Administration Settings
W INI file Settings
W People/Contact/UserProfrle Definitions
W Terminology Settings
W Flex Field Usage and Definitions
This document describes,at a detailed level,the tasks involved to implement the solution. The document
provides screen information, database modifications,and text message modifications. The customization
tasks and estimates are based upon Evergreen Systems'understanding of the requirements through
conversations between Evergreen Systems, Inc. and The City offort Worth.
Modifications to Evergreen Systems'understanding of the requirements may affect the estimates associated
with the defined project. The figures represented within this document are to be considered only estimates
and Evergreen Systems, Inc. shall not be deemed to be in breech or default if they are not met. These
customizations will require modifications to the database,source code and dialog boxes used to display the
application information.
All modifications will follow Tivoli Systems Integration Services Customization Standards.
5
Document Definition
This document contains several major sections.These sections are described below.
Introduction
'I;> Project Definition
Definition of the problem to be solved by the project
,I;> Assumptions
Basic assumptions that are made in defining the project
q:> Objectives
Objectives, for which the project will be measured, including technical,profit performance,
quality,etc.
'I;> Resources
Resources are necessary to complete the project. Resources can include people,equipment,
facilities and materials.
tl:> Strategy
A detailed strategy will be used in implementing the project.
Project Scope
tl:> System Requirements/Architecture
This section contains the required or expected information about the hardware and
Software that will support the Custom Solution as described within this document.
Legend
This section contains a Legend that describes symbols,which will be used throughout the
document.
tl;> Screens and Logic (TSD 6.0)
This section contains screen prints and information about the functionality of all
customizations to TSD 6.0 and customizations that will be carried over from EA 5.0.2 during
the migration.
6
Appendices
* Estimate
This appendix contains an estimate of the days required to complete the requested migration
and modifications for the Custom Solution.
* Outage Relationship List Functionality
This appendix contains the table relationships for various new tables included in this design.
* Database Modifications (TSD 6.0)
This appendix contains the estimated database modifications. All Custom Solutions attempt
to maintain"normalization'of the database tables. The Code Construction phase of this
implementation may require modifications to this section of the document.
* Acceptance
This appendix contains a sign off sheet for acceptance of the defined customizations.
* Test Plan Approach
This appendix contains a description of Evergreen Systems, Inc.test plan in a high-level
scope.
7
Proiect Definition
The project definition for the TSD 6.0 Migration and customizations for The City of Fort Worth is
defined as follows:
1. To customize TSD 6.0 to The City of Fort Worth's specifications.
2. Migrate from Tivoli Product Suite 5.0.2 to TSD 6.0
3. Following is the format of code commenting used at the module-level.
(*ES1CNIT Begin CFV blig-Custom Evergreen Systems,Inc.(xxx) mm/dd/yy hh:mm:xNl ESICNIT*)
(*Begin ESICFNVxxx-yyyy##k*)
(*End ESICFWxxx-yyyy-##N*)
(*ESICdIT End CFW hlig-Custom Evergreen Systems,Inc.(xxx)mm/dd/yy hh:mm:xdl ESICNIT*)
xxx=Programmers Initials
mm/dd/yy=date of modification
hh:mm:xM=time of modification, example( 13:25 PM)
ESICFWxxx-yyyy###=xxx=programmer initials,yyyy=year,
###=unique identifier documented in MODAPISD.KB
4. Additional documentation will be provided in the code within module
MODAPISD.KB. This code module is used to fully document each modification,
and houses any additional function,procedures, or events.
8
Assumptions
=> All modifications will be performed using Tivoli Systems Coding Standards.
=> A separate SQL script will be created for all database modifications. This complies with
Tivoli Systems Coding Standards. The name is MODAPISD.SQL.
=> The scope of the first deliverable is defined in the Technical Design Document. Any
additional requirements will impact the deliverable and delivery dates.
=> Stable environment,both a production and test environment will be built.
This migration/customization and integration effort performed by Evergreen Systems will
require that The City of Fort Worth provide certain support. This support is detailed below:
Information Support Services Representative-A representative from the Information
Support Services Center must be available, on call, for the entire Evergreen Systems
development phase and during any on location visits. This person must have authority to
make decisions regarding operations,system configurations and design specifications.
Database Analyst-A database analyst or someone equally familiar with The City of
Fort Worth's database structures may be required on a part-time basis.
9
Obiectives
':;.> To migrate Expert Advisor S.0.2 and Expert Foundation Manager 5.0 with all requested
customizations to TSD 6.0,and change TSD 6.0 to meet The City of Fort Worth's
requirements.
10
Resources
Position` ems :: Responsibilities Commitment -
Project Managers Single point of contact and decision- Key team member
(The City of Fort Worth) maker representing The City of fort High availability
Worth TSD 6.0 Implementation Team in
defining project definition,planning,
scheduling and controlling of the
implementation.Provides direction to
the Evergreen Systems Development
Team regarding approvals and
enhancements to the application design
and implementation. David Bragg
Project Manager Single point of contact for the City of Key team member
(Evergreen Systems) Fort Worth TSD 6.0 Implementation High availability
Team in conveying definition,planning,
scheduling and controlling of the
enhancement implementation. Aid in
the implementation deployment and
training processes Clyde Wimbrough
Jennifer Zimmerman
Lead Consultant Single point of contact for the City of Key team member
(Evergreen Systems) Fort Worth TSD 6.0Implementation High availability
Team in conveying detailed technical
issues regarding the effort of the TSD
6.0 Migration and Customization
Solution. This individual will aid the
City of Fort Worth TSD 6.0
Implementation Team in defining the
custom requirements and defining those
requirements in terms of technical
specifications regarding the project.
Testing,onsite implementation and David Broom
rollout are also areas of responsibility Doug McElhaney
for this individual. Todd Wilson
Support Center Analysts Provide input to the design and Limited team member
(The City of Fort Worth) implementation process of the proposed Limited availability
application enhancements.
Maintenance of the production and test
environments on the file server for the
application. Security,disaster recovery,
normal maintenance of a client-server-
based application. TBD
Database Administrator Maintenance of the production and test Limited team member
(The City of Fort Worth) environments on the database server for Limited availability
the application. Security,disaster
recovery,normal maintenance of a client
-server-based application. TBD
11
StrateZV
The following describes the process that will be employed to accomplish the requested TSD 6.0 Migration
and enhancementslcustomizations as authorized by the implementation team:
q+ Requirements Analysis/Gathering
There may be a need for an onsite Requirements Gathering trip in order to gather the proper level
of detail and understanding of the scope for the project. Upon approval to proceed with the
requested project,the Detailed Technical Design effort will begin with the Requirements
Gathering trip to analyze the requirements and begin scoping the requested project.
tb Detailed Technical Design
Detailed Technical Design preparation,code construction,and testing should be completed in
Evergreen Systems'Development Services corporate offices. The Detailed Technical Design
Document will be produced from the requirements gathered during the onsite trip,via conference
calls,faxed documents,etc.
The support organization's implementation team will be asked to approve the Detailed Technical
Design prior to the code construction phase of the project to define the scope,planning,scheduling
and resource commitments of the project. Once the Detailed Technical Design has been reviewed
and the estimate,scope,plan and the associated costs have been approved by the support
organization's implementation team,the development of the Migration and Custom Solution
project can be scheduled. The Tivoli Systems Integration Services Project Manager will produce a
projected plan of delivery.
Deliverable: Detailed Technical Design Document
Project Estimate
Test Plan
1;� Migration and Custom Solution Construction
As stated above,the Migration and Custom Solution Construction phase of the project should be
completed at the Evergreen Systems Development Services corporate offices. The migration and
enhancements will be tested against the specification of the project as defined in the Detailed
Technical Design prior to delivery to the support organization.
Deliverable: Migration Instructions
Deliver customized code base every 2 weeks
Implementation Instructions— These instructions will be delivered when
the final code is delivered
Detailed Project Documentation
Custom Solution Deliverable
W Onsite Implementation
The migration and custom implementation will be performed in a planned,phased rollout that will
include training of the administrator of the application in the implementation of the Custom
Solution,the development ofand implementation into a test environment and final production
deployment of the Custom Solution. The enhanced application will be implemented within the
Information Support Services Center organization's test environment for testing by the
implementation team prior to the production implementation and rollout of the Custom Solution.
Deliverable: Test Environment
On-Site and Off-Site Testing
On-Site Acceptance
12
tb Acceptance/Warranty
Once the project has been successfully deployed and tested onsite for the City of Fort Worth and
found to meet the defined requirements of the project as detailed within the Detailed Technical
Design,the Evergreen Systems Development Services Project Manager will submit a letter of
acceptance to support organization's implementation team.
The acceptance letter acknowledges completion of the first phase of the proposed solution and will
serve as a point of evaluation to continue with additional phases of the project. The implemented
solution will be warranted against defects due to workmanship for a warranty period of ninety(90)
days without charge to the support organization team.
W Acceptance/Warranty
Once the project has been successfully deployed and tested onsite for the City of Fort Worth and
found to meet the defined requirements of the project as detailed within the Detailed Technical
Design,the Evergreen Systems Development Services Project Manager will submit a letter of
acceptance to support organization's implementation team.
The acceptance letter acknowledges completion of the first phase of the proposed solution and will
serve as a point of evaluation to continue with additional phases of the project. The implemented
solution will be warranted against defects due to workmanship for a warranty period of ninety(90)
days without charge to the support organization team.
W Proiect Manazement
Project management for the proposed project will be provided by the Evergreen Systems
Development Services organization based from the corporate office. The Evergreen Systems
Project Manager will work in conjunction with the support organization's Project Manager in
maintaining the project plan,scope,scheduling and resource commitments.
Deliverable: Project Status every Monday morning throughout the Project Implementation
13
Probw Scope
System Requirements/Architecture
The following describes the environment into which the project will be implemented:
Client
Operating System: Windows NT,Windows 95/98
Application: TSD 6.0
Tool: Tivoli-Application Software Expert 6.0
Database Server
Operating System Windows NT
RDBMS: Microsoft SQL Server 7.0
Application Server
Operating System Windows NT
File Server/Monitor Server/Secondary Application Server
Operating System Windows NT
GUI Server—1
Operating System Windows NT
Master Server/GUI Server—2
Operating System Windows NT
JWo,r
® MS SQL
Server 7.0
lion Pra ary
Applicata Server
File Server
Monitors Server
Secondary Application Server
p®
GUI Server-1
Corporate Web Server
Mast erver
GUI -2
14
Legend
Symbol '" ' r Deseri tion
NEW This symbol will be used to indicate that a new field is being added to a screen
UPDATE This symbol will be used to indicate that an existing field's functionality has been
updated
REMOVE This symbol will be used to indicate that and existing customized field in the
Tivoli Product Suite 5.0.2 will not be used in TSD 6.0
NO CHANGE or This symbol will be used to indicate that an existing field's functionality has not
NC been changed
15
Screens and Logic
Tivoli Service Desk/Problem Management 6.0 Customizations)
Call Registration Notebook
The Call Registration Notebook has been modified to fulfill requirements for The City of Fort Worth's TSD
6.0 Migration and Implementation Solution. Control Fields added to The Registration Page for FAC:
The following non-stored fields will be added to the Call Registration Notebook as combo boxes:
:Field Prom"'{ s . W jeld:C6itrol NainO�a4AVN, -
Fund Code fCode
Account# acctNum
Center center
Percentage percentage
A table list will be added above these fields that displays what FAC data is currently associated to the
current problem ticket. Records are added to this table list by filling out the above-mentioned combo
boxes,then clicking the Add button next to the table list. Next to the table list are three(3)buttons,Add,
Edit,and Delete. These buttons control the data in the table list using the values currently stored in the
combo boxes mentioned above. More than one FAC record can be associated to each problem ticket.
Workflow modifications:
The workflow will be effected by the fact that each of the above combo box fields will required to
have a value before the Add and Edit buttons will be enabled for use. The Delete button will be
enabled when a record is highlighted in the Associated FAC table control. Each of the above
combo boxes will be preloaded with all possible values from new corresponding ADVISOR
tables. The user can select values out of the combo boxes in any order,when any of the combo
boxes are selected and a value is set by the agent the other combo boxes without selected values
will have their lists reloaded with only associated values for the combination of FAC values
currently visible in the other combo boxes. Further descriptions of this modification can be found
in the"Screen Attributes/Functionality"Section of this document.
When the agent attempts to save the problem ticket a check will be done to validate the
percentages entered for the associated FAC records. If the percentage does not equal 100%then
the agent will receive an error message and will not be allowed to save the problem until the
percentage of associated FAC records equals 100%.
Fund Account Validation: If the agent changes the Center,then use the first three digits of the Center#to
ascertain the department#. This department#will then be compared to the department number of the
contact shown on the Call Registration notebook. If the contacts department#does not match the
department#ascertained from the center#,then display a warning message to the agent explaining that this
contact should not be allowed to use the selected center#. The agent will be allowed to override the
warning and select the center#that does not correctly match the contacts department.
Workflow modifications:
The workflow will be affected when the department#does not match the contacts department#or
when the fund account center is changed. The agent will be presented with a warning message.
The agent can accept the center#or reject the center#from the warning message screen. If the
agent accepts the warning message,then the center#will stay on the Call Registration screen. If
the agent rejects the center#,then the center#on the Call Registration screen will be cleared out,
and the cursor will be placed in the center#field. The same logic above applies when the agent
changes the contact id or fund account center anytime during the Call Registration Notebook. Add
Validation to verify that all three FAC values match a value in the ASSOC_FUND table. If not,
then a warning message will be displayed and the FAC values will need to be revised
16
Figure 1 displays the Call Registration Notebook
00:00:06 031Q�x,
t. +s r F ' y ;_ Canponerilrtamehan M
`4 J
Fist Namx Last Nana Sf '
Phones �-' Cmporert
Y
LacMiorc"`�.a �_ 0�9siaaborc �� Ibmc
PtabiamCcdq: OPEN _ _ --
lm%*V Cal J � TYPa
L;S -M4 LOWe, � a.it �' ? - i. , y -,, .. 1'T�k2k.
pswnaledFudAecwts,e x ., a - Oesa4tiorti�' ~.� �a�"'��i�s �ro� Sy'N-"7
F Accwt# Center
i
r
J
_ s
F,Not7YCanH
=tiist of= v"=F,uud`Aecouiit_ =Add/Edit/Delete
=associated= - - _ -'-
K selection:�_. :--selected c_oinW..bd es �"
Fund"' Coiiibo Boxes. =into list-Wassociated
accounts .and Percenta¢e ==Fund Accounts
'--
17
Screen Attributes/Functionality
Call Registration Notebook Regis ation Page 4 CALLS.DF[REGISTERCALLI
Key Field Prom t Attributes ' ;3 Comments
NEW Associated Type : Table • This table control will store the
Fund Control Name . FAC data entered by the agent In a
Accounts PROB_FUND_ACCOUNTS table named PROB_FAC with the
Read Only :N/A value of lite current problem ld.
Mandatory :N/A • The data in this table control Is
Disabled :No manipulated by the Add,Edit,and
Caps Only :No Delete buttons next to it.
Data Type :Record . When one of the records In this
Max Length :N/A table control is highlighted,then
Default Value :N/A the FAC combo boxes below
Columns should be updated to display the
FUND CODE values in this controls columns.
ACCOUNT . Also when one of the records in
CENTER this table control is highlighted,
PERCENTAGE then the items available In the FAC
PROBFAC ID—Zero Length combo boxes need to be refined to
only items matching the
relationships of the other two
combo boxes.
• See Appendix C—SOL
Modifications
NEW Add Type :Button • This button is disabled initially.
Control Name . • If any one of the FAC combo boxes
FAC ADD BUTTON or Percentage does not have a
Read Only :N/A value selected,then thisJleld will
Mandatory :N/A be disabled.
Disabled : Yes • An exception to enabling this
Caps Only :No button would be if the table control
Data Type :N/A already has a record that matches
Max Length :N/A lite selected FAC combo box values
Button Type : Text currently displayed.
• A check will be done just before
adding lite FAC data into the
PROB_FUND ACCOUNTS table
control on this screen. The check
will determine if the percentage
being added to this list causes the
list to have a percentage greater
titan 100%. If the percentage Is
greater then give the agent a
warning and don't insert the FAC
data into the
PROB_FUND ACCOUNT table
control. Additionally the FAC
values will be validated against the
ASSOC FAC table,if a matching
set of values is not found,then a
warning message will be displayed,
and the recorded will not be
inserted into the screen or
18
database.
• When this button is click the values
in the FAC combo boxes and
percentage field will be formatted
along with the problem id into a
record and stored in the
PROB_FAC table,and inserted
into the
PROB_FUND_ACCOUNTS table
control list on this notebook.
NEW Edit Type :Button • This button is disabled initially.
Control Name . • This button will be enabled when at
FAC_EDIT_BUTTON least one value gists in the table
Read Only :N/A list and a record is highlighted.
Mandatory :N/A • An exception to enabling this
Disabled : Yes button would be if not all FAC
Caps Only :No combo boxes and percentage have
Data Type :N/A a value displayed.
Max Length :N/A • When this button is clicked the
Button Type : Text currently highlighted record in the
table list will be removed and the
record in the
PROB FUND_ACCOUNT will be
deleted. Then the values in the
FAC combo boxes will be
formatted along with the problem
id into a record,and stored in the
PROB_FAC table,and inserted
into the
PROB_FUND_ACCOUNTS table
control list on this notebook.
• A check will be done just before
updating the FAC data into the
PROB_FUND ACCOUNTS table
control on this screen. The check
will determine if the percentage
being updated to this list causes the
list to have a percentage greater
than 100%. If the percentage is
greater then give the agent a
warning and don't update the FAC
data into the
PROB_FUND ACCOUNT table
control.. Additionally the FAC
values will be validated against the
ASSOC FAC table,if a matching
set of values is not found,then a
warning message will be displayed,
and the recorded will not be
inserted into the screen or
database.
NEW Delete Type :Button • This button is disabled initially.
Control Name . • This button will be enabled when at
FAC_DEL_BUTTON least one value exists in the table
Read Only :N/A list and a record is highlighted.
19
Mandatory :NIA • When this button is clicked the
Disabled : Yes table control list record that is
Caps Only :No high-lighted will be removed and
Data Type :N/A the corresponding PROB FAC
Max Length :N/A table record will be deleted.
Button T e : Text
NEW Fund Code Type : Combo Box • This combo box will be initially
Control Name :fCode loaded with all fund codes found in
Read Only : YES the FUNDS table.
Mandatory : YES • This combo box will be read-only.
Disabled :No • A blank entry value will be
Caps Only :No included in this combo box. This
Data Type :String will allow the agent to clear the
Max Length :4 displayed value in this combo box
Default Value :No • Wit en a fiend code value is selected
by the agent a routine will be
executed that reduces the entries in
the Accounts,and Center combo
boxes,only if they do not already
have selected values. The routine
that handles this logic will
determine the values of the other
combo boxes by comparing
associations with die fund code
and other selected FAC combo box
values to table ASSOC FAC.
• See Appendix C—SOL
Modifications
NEW Account Type :Combo Box • This combo box will be initially
Control Name :acctNum loaded with all accounts found in
Read Only : YES the ACCTS table.
Mandatory : YES • This combo box will be read-only.
Disabled :No 0 A blank entry value will be
Caps Only :No included in this combo box. This
Data Type :String will allow the agent to clear the
Max Length : 6 displayed value in this combo box-
Default
oxDefault Value :NO • When an account value is selected
by the agent a routine will be
executed that reduces the entries in
the Fund Code,and Center combo
boxes, only if they do not already
have selected values. The routine
that handles this logic will
determine the values of the other
combo boxes by comparing
associations with the account and
other selected FAC combo box
values to table ASSOC FAC.
• See Appendix C—SQL
Modi rcations
NEW Center Type :Combo Box • This combo box will be initially
Control Name :center loaded with all centers found in the
Read Only : YES CENTERS table.
Mandatory : YES • This combo box will be read-only.
Disabled :No • A blank enity value will be
20
Caps Only :No included in this combo boy- This
Data Type :String will allow the agent to clear the
Max Length :12 displayed value in this combo boy-
Default Value :NO • When an center value is selected by
the agent a routine will be executed
that reduces the entries in the
Fund Code,and Account combo
bores,only if they do not already
have selected values. The routine
that handles this logic will
determine the values of lite other
combo boxes by comparing
associations with the center and
other selected FAC combo box
values to table ASSOC FAC.
• See Appendix C—SQL
Modi tcations
NEW Percentage% Type :Entry • This field is required before lite
Control Name :percentage Add,and Edit buttons are enabled.
Read Only :No . Validation needs to be added to this
Mandatory : Yes fields logic to not allow an agent to
Disabled : Yes enter a value greater titan 100.
Caps Only :No
Data Type :Integer
Max Length :3
Default Value :NO
UPDATE Done Type :Button • When this button is clicked a check
Control Name :ok_button will be done to verify that
Read Only :No associated fund accounts for this
Mandatory :No problem have a total percentage of
Disabled : Yes 100%.
Caps Only :No . If the percentage does not equal 0
Data Type :N/A or 100,then a message box will
Mor Length :N/A appear that asks lite agent to
Default Value :NO correct this problem before
completing the request.
21
Problem Status Notebook
The Problem Status Notebook has been modified to fulfill requirements for The City of Fort Worth's 7SD
6.0 Migration and Implementation Solution.
Flex Fields added to The Problems Page:The following flex fields will be added to the Problem Status
Notebook:
`FI&Qie1d jTsed :0z',TAW. Vrrainola ' =Used _s= " =.FieldT M e ,,. k
�F#a
FLX PRO TIME1 Act Time Spent En Field "
FLX PRO VCHR1 Resolved By Entry Field
Workflow modifications:
No workflow modifications are required. Each of these fields will be updateable.
Control Fields added to The Registration Page for FAC:The following non-stored fields will be added
to the Problem Status Notebook as combo boxes:
i`eld Prain�"f �, �� �r,�• �-± �;l~'ield'Control Name��. �
Fund Code (Code
Account# acctNum
Center center
Percentage percentage
A table list will be added above these fields that displays what FAC data is currently associated to the
current problem ticket. Records are added to this table list by filling out the above-mentioned combo
boxes,then clicking the Add button next to the table list. Next to the table list are three(3)buttons,Add,
Edit,and Delete. These buttons control the data in the table list using the values currently stored in the
combo boxes mentioned above. More than one FAC record can be associated to each problem ticket.
Workflow modifications:
The workflow will be affected by the fact that each of the above combo box fields will be read-
only and mandatory before being able to add a FAC record to the table list. Each of the above
combo boxes will be preloaded with all possible values from new corresponding ADVISOR tables
when appropriate. The Add,Edit,and Delete buttons will be enabled and disabled based on the
data available for FAC on this notebook. Further descriptions of this modification can be found in
the"Screen Attributes/Functionality"Section of this document.
22
Figure 2 displays the Problems Page of the Problem Status Notebook
tt t _ O x
_..,»_,„,w...r��m.�a�awx.+E +...n.: ,r— _� � 4•��' w,��..0p0�II.�. r�,,,�..,w.
Cafe_� I TIRI 32
rrw1PM,t ..�`� 1 s :,l _BUrdat. d
U
� .. F___ — -----
,Time spent o- - Items
:�. DpmDate: �osrz000~ M.O&*
-�Open T'M:me: 7 01:08 Problem Type:
>OoseDate ddlyyyy' Problantoda 1FIANSFERF)ED. r; .".,.,x, .-
Gose Tia 1? mmn Caiuc _
��N_ .-'•� �^' W'4 ; .s. ra•••�,,. .. � ....i?- .�` +a�o>r•:�6._- •tilt
AssoaatedFe+dAccoii_ets ,�vtet RmSmeSpeerx�liesorved8y` .
Fund. AW# Centa „
tahn:
e#` elate testettet :,
FvdCode` #� Cella percent 3 ui e
Ot AN
•Dane i t` 5Pr' Lherget�.s
.'
_Listiof_ _- .undAccount Added="
,:associated aaEselection'-Z.. : :- :selected combo;boxes. Problems""""
_._.
Fund �-=--ComboBoxes into list of_associated== able_F1ez�
AOdUiuts ' ndfereentaee'. :tip and Accounts --- Fields'""
Before this problem'Y.
,can be stored_thee- --
percentages-must =r
`.eaua1.100%..
23
Screen Attributes/Functionality
Problem Status Notebook 4 RESUME.DF[EDITPROBLEMFORMJ
K = -� FieldProm t Attributes Comments
NEW Associated Type : Table • This table control list will be
Fund Control Name . initially loaded with all FAC data
Accounts PROB_FUND ACCOUNTS associated to the current problem
Read Only :N/A id. No record in this list will be
Mandatory :N/A highlighted during screen creation.
Disabled :No • This table control will store the
Caps Only :No FAC data entered by the agent in a
Data Type :Record table named PROB_FAC with the
Max Length :N/A value of the current problem ld.
Default Value :N/A • The data in this table control is
Columns manipulated by the Add,Edit,and
FUND CODE Delete buttons.
ACCOUNT • When one of the records in this
CENTER table control is highlighted,then
PERCENTAGE the display of the FAC combo
PROBFAC ID—Zero Length boxes below should be updated to
display the values in this controls
columns.
• Also when one of the records in
this table control is highlighted,
then the items available in the FAC
combo boxes need to be refined to
only items matching the
relationships of the other two
combo boxes.
• See Appendix C—SOL
Modi hcations
NEW Add Type :Button • This button is disabled initially.
Control Name . . If any one of the FAC combo boxes
FAC ADD BUTTON does not have a value selected,then
Read Only :N/A this field will be disabled.
Mandatory :N/A . An exception to enabling this
Disabled : Yes button would be if the table control
Caps Only :No already has a record that matches
Data Type :N/A the selected FAC combo box values
Max Length :N/A currently displayed.
Button Type : Text • When this button is click the values
in the FAC combo boxes will be
formatted along with the problem
id and Percentage into a record
and stored in the PROB_FAC
table,and inserted into the
PROB_FUND-ACCOUNTS table
control list on this notebook.
• A check will be done just before
adding the FAC data into the
PROB_FUND_ACCOUNTS table
control on this screen. The check
will determine jthe percentage
being added to this list causes the
list to have a percentage greater
than 100%. If the percentage is
24
greater then give the agent a
warning and don't insert the FAC
data into the
PROB_FUND ACCOUNT table
control.. Additionally the FAC
values will be validated against the
ASSOC FAC table,tf a matching
set of values is not found,then a
warning message will be displayed,
and the recorded will not be
inserted into the screen or
database.
NEW Edit Type :Button • This button is disabled initially.
Control Name . • This button will be enabled when at
FAC_EDIT_BUTTON least one value exists in the table
Read Only :N/A list and a record is highlighted.
Mandatory :N/A • An exception to enabling this
Disabled : Yes button would be if not all FAC
Caps Only :No combo bores and the percentage
Data Type :N/A have a value displayed
Max Length :N/A • When this button is clicked the
Button Type : Text currently highlighted record in the
table list will be removed and the
record in the
PROS FUND_ACCOUNT will be
deleted. Then the values in the
FAC combo boxes and percentage
will be formatted along with the
problem id into a record,and
stored in lite PROB_FAC table,
and inserted into the
PROB_FUND_ACCOUNTS table
control list on this notebook.
• A check will be done just before
updating the FAC data into the
PROB_FUND_ACCOUNTS table
control on this screen. The check
will determine if the percentage
being updated to this list causes the
list to have a percentage greater
than 100%. If the percentage is
greater then give the agent a
warning and don't update the FAC
data into the
PROB_FUND ACCOUNT table
control.. Additionally the FAC
values will be validated against the
ASSOC FAC table,if a matching
set of values is not found,then a
warning message will be displayed,
and the recorded will not be
inserted into the screen or
database.
NEW Delete Type :Button • This button is disabled initially.
Control Name • This button will be enabled when at
25
FAC_DEL_BUTTON least one value exists in the table
Read Only :N/A list and a record is highlighted.
Mandatory :N/A • When this button is clicked the
Disabled : Yes table control list record that is
Caps Only :No highlighted will be removed and
Data Type :N/A the corresponding PROS—FA C
Max Length :N/A table record will be deleted.
Button TE,e ext
NEW Fund Code Type :Combo Box • No value will be initially displayed.
Control Name :fCode • This combo box will be read-only.
Read Only : YES • A blank entry value will be
Mandatory : YES included in this combo box. This
Disabled :No will allow the agent to clear the
Caps Only :No displayed value in this combo box.
Data Type :String . This combo box will be initially
Max Length :4 loaded with all fund codes found in
Default Value :No the FUNDS table.
• When a fund code value is selected
by the agent a routine will be
executed that reduces lite entries in
lite Accounts, and Center combo
boxes,only if they do not already
have selected values. The routine
that handles this logic will
determine lite values of the other
combo boxes by comparing
associations with the fund code
and other selected FAC combo box
values to table ASSOC FAC.
• See Append&C—SQL
Modifications
NEW Account Type : Combo Box . This combo box will be initially
Control Name :acclNum loaded with all accounts found in
Read Only : YES lite ACCTS table.
Mandatory : YES . This combo box will be read-only.
Disabled :No . A blank entry value will be
Caps Only :No included in this combo box. This
Data Type :String will allow the agent to clear the
Max Length : 6 displayed value in this combo box.
Default Value :NO . When an account value is selected
by lite agent a routine will be
executed that reduces the entries in
the Fund Code, and Center combo
boxes, only if they do not already
have selected values. The routine
that handles this logic will
determine the values of lite other
combo boxes by comparing
associations with the account and
other selected FAC combo box
values to table ASSOC FAC.
• See Append&C—SOL
Modifications
NEW Center Type :Combo Box . This combo box will be initially
i Control Name :center loaded with all centers found in lire
26
Read Only : YES CENTERS table.
Mandatory : YES • This combo box will be read-only.
Disabled :No . A blank entry value will be
Caps Only :No included in this combo box. This
Data Type :String will allow the agent to clear the
Max Length : 12 displayed value in this combo box.
Default Value :NO . When an center value is selected by
the agent a routine will be executed
that reduces the entries in the
Fund Code,and Account combo
boxes,only if they do not already
have selected values. The routine
that handles this logic will
determine the values of the other
combo bores by comparing
associations with the center and
other selected FAC combo box
values to table ASSOC FAC.
• See Appendix C—SQL
Modifications
NEW Act Time Type :Entry • The value displayed in this entry
Spent Control Name field will be the value that was
FLX_PRO_TIME] stored in the flew field for this
Read Only :No problem.
Mandatory :No • This field is updateable
Disabled :No
Caps Only :No
Data Type :String
Max Length :10
Default Value :NO
NEW Resolved By Type :Entry • The value displayed in this entry
Control Name . field will be the value that was
FLX_PRO_VCHRI stored in die flew field for this
Read Only :No problem.
Mandatory :No • This field is updateable
Disabled :No
Caps Only :No
Data Type :String
Max Length :45
Default Value :NO
NEW Percentage % Type :Entry • The agent must enter a value
Control Name :percentage between 0 and 100 before the Add,
Read Only :No Edit buttons will be enabled
Mandatory : Yes
Disabled : Yes
Caps Only :No
Data Type :Integer
Max Length :3
Default Value :NO
UPDATE Done Type :Button • When this button is clicked a check
Control Name :ok_button will be done to verify that
Read Only :No associated fund accounts for this
Mandatory :No problem have a total percentage of
Disabled : Yes 100%.
Caps Only :No • If the percentage does not equal 0
27
Data Type :N/A or 100,then a message box will
Max Length :N/A appear that asks the agent to
Default Value :NO correct this problem before
comp ing the request
28
Mainframe - Payroll Master Extract/TSD 6.0 Synchronization Utility
People Update
The City of Fort Worth currently runs a weekly process to update the TPM 5.02 ADVISOR database
people,contacts,people/contacts and location related tables. An automated application will be created to
replicate this process against the new TSD 6.0 ADVISOR database data structure to fulfill requirements for
The City of Fort Worth's TSD 6.0 Migration and Implementation Solution.
Impacted TSD 6.0 Tables: The following tables will be impacted by the new weekly synchronization
utility:
► PEOPLE&ORG_MEMBERSHIP&PEOPLE_LOCATION
Reports Generated: Evergreen Systems will create the following reports. These reports can be run at
anytime by The City of Fort Worth from MS Access. An attempt will be made to allow users the ability to
run these reports from the TSD application.
► People that are Contacts without Organizational associations
► People that are Contacts without a Department or Division
► People that are Contacts whose Department does not match correctly to their Location
► People that are Contacts whose Department does not match correctly to their Organization
► People that are Contacts where there organization,department,or division changed via this
utility.
► People that are Contacts where the department does not match the location table.
Also an exception report generated by the Synchronization Utility will be available in the form of a log file
named SYNCPEO(date&time].LOG. The date and time will be the date and time the utility started.
People Table fields updated by this Utility:The following fields will be inserted or updated into the
people and organization membership table by this utility. Not all fields will come from the Payroll Extract,
and some fields will be manipulated in format by this utility:
PEOPLE TABLE
► People ID - Auto Generated
► Contact ID
► Employee ID
► Last Name
► First Name
► Middle Name
► Phone
► FLX_PEO_VCHRI(fund)
► FLX_PEO_VCHR2(center)
ORC MEMBERSHIP
► Org Member ID - Auto Generated
► Organization ID - Determined based on flx_peo_vchr2,else match to
flx_org_vchrl using 1"3 chars of flx_peo_vchr2 and padded zeros.
o. People ID - Auto Generated
PEOPLE LOCATION
► People ID - From People Table
► Location ID - Determined based on department number in the Toms.txt file. Then
match that department number to the location table. If an exact match is found,then create a
new record in this table.
► Contact ID- From People Table
29
Workflow modifications:
The new synchronization utility can be initiated manually if needed via the TSD Administrator
icon bar,or menu bar. This utility will be executed automatically by a batch scheduling system.
This utility will have a code base of KML,not MS Access. Also,the only database tables that will
be affected are the PEOPLE and ORG_MEMBERSHIP tables. This utility will compare the
organization membership data to be updated to a person to existing organizations in the
ORGANIZATION table. If the organization does not already exist an exception will be logged. If
the synchronization utility fails to complete successfully within a certain period of time an email
notification will be fired to a person or group. A person or group can be configured to receive this
notification,by checking a Synchronization Utility Notification checkbox found in People and
Group dialogs.
30
Figure 3 displays the Payroll Master/TPM 6.0 System Integration
Payroll Master Extract FY e'.,.
Wll Read Extract File - —
Mairifran a TCS Batch S heduling
,File Server Appli ticn
Start Utility
PEOPLE
PEOPLE LOCATION --Insert/Update TSD 6.0
Database
ORG MEMBERSHIP
31
Mainframe - MARS Extract/TSD 6.0 Synchronization Utility
FAC Update
An automated application will be created to import structured Fund,Account, and Center data from the
MARS system into the TSD 6.0 ADVISOR database to fulfill requirements for The City of Fort Worth's
TSD 6.0 Migration and Implementation Solution.
New TSD 6.0 Tables: The following tables will be created to store Fund, Account,and Center data and
their associations:
► FUNDS
► ACCOUNTS
► CENTERS
►
ASSOC—FAC
Reports Generated: An exception report will be generated by the Synchronization Utility and will be
available in the form of a log file, named"SYNC FAC[date&time].LOG. The date and time will be the date
and time the utility started.
See Appendix C—SQL Modifications
Workflow modifications:
The new synchronization utility can be initiated manually if needed via the TSD Administrator
icon bar,or menu bar. This utility will be executed automatically by a batch scheduling system.
This utility will only insert or delete MARS data,no contingencies exist for existing FAC data that
is removed and maybe associated with problems,assets, or changes. The ASSOC_FAC table will
store the relationships. If the synchronization utility fails to complete successfully within a certain
period of time an email notification will be fired to a person or group. A person or group can be
configured to receive this notification, by checking a Synchronization Utility Notification
checkbox found in People and Group dialogs.
32
Figure 4 displays the MARS/TPM 6.0 System Integration
-MARS Master Extract File .
D '3 h�4 YY Y P::.
�4 _ Read Extract File - —
Mainframe '� TCS¢ z Batch S heduling
' Y File'Server ,.. Appli ation
Start Utility
i rn''t'F[11VOS
4Y-A6COUNTS
Insert/Update—f4
pdate TSD 6.A
.CENTERS.;`_ :'., Database
r; ASSOC FAC a
33
Notifications Text
All notification methods will be modified to fulfill requirements for The City of Fort Worth's TSD 6.0
Migration and Implementation Solution.
Additional information to be included in all Notifications:The following table lists the additional
PROBLEM VIEW fields that will be added to the text of all notifications:
Addifion'filII'ext
SEVERITY
CONTACT NAME
PHONE NUMBER
LOCATION
PROBLEM DESCRIPTION
Workflow modifications:
No workflow modifications are required.
34
Group Tracking Through-out a Cases Lifecycle
Store the Group Id field in the Problems table when problems are transferred to groups to fulfill
requirements for The City of Fort Worth's TSD 6.0 Migration and Implementation Solution.
Use Group Id field of Problems Table:The group id field in the problems table is not used,but it will be
at City of Fort Worth with code customizations. This field will be added to the Work with Problems
Inquiry screen as well.
Workflow modifications:
When a problem is transferred to a group that group id will be stored in the group id field of the
Problems table as well as the Prob Transfer table. When problems are transferred to an
individual,the group id will not be changed,and like wise when problems are transferred to a
group,the user id will not be changed.
Figure 5 displays the Work with Problems Inquiry Screen.
x
orr Con poneol lrionne6on
caper - - Systaa
Code:
CnDo�t
-
cakm _ 1 Hein
SaWan D: LP';
Lacahorr . JTypa r _
Orpanaaborc
Node Names
r Prolan Open Daie Rape
Start Data $ ddlm
End Data dd/j5w
- 0x
OK Clear J Grow Search
GraglD: GroWRdes .
r Ch'Prt,_
llow:problem. uaew' w r cti� *��' I
—searc es by�roup� r��%�
Grows lid
0 Name SieID
$atset doM Cava 1
35
Screen Attributes/Functionality
Problem Inquiry Dialog 4 PROBLEMS.DF[PROBLEM INQUIRY}
TieldPmf4lributs ' a mrI4
NEW Group M Type :Entry • None
Control Name :GROUP ID
Read Only :No
Mandatory :No
Disabled :No
Caps Only :No
Data Type :String
Max Length :15
Default Value :NO
NEW Binoculars Type :Button • When this button is clicked call the
Control Name . Pick Groups TPM built-in function
GRP_BROWSE_BUTTON to allow the agent to select a group
Read Only :N/A id to auto-fill into the Group Id
Mandatory :N/A field of this form.
Disabled :No
Caps Only :No
Data Type :N/A
Max Length :N/A
Button Type :Image
36
Add/EdWew People
The Call Registration Notebook has been modified to fulfill requirements for The City of Fort Worth's TSD
6.0 Migration and Implementation Solution.
Flex Fields added to The General Page:The following flex fields will be added to the Person Notebook
as entry fields:
.Fl xORM Used . y' '. 'Terminolo Used:
FLX PEO VCHRl Fund
FLX PEO VCHR2 Center
Workflow modifications:
No workflow modifications are required. Although these flex fields will be loaded via the
synchronization utility describe in an above section.
Figure 6 displays the Add Person Dialog
, .
E31 x
General 1 Contacts 1 User's
General Wormation
Last Name:
First Name:
Middle Name:
Employee Number" Alk P
F
)�, five
Organizations rNotificat,
Organization Default Me tho - dress Def
� I
,I
i
i
►J
Add.. ew $emove Default T � Aid. Edj,.. R Deja.R
OK l d ,Pr
-`-PEOPLE emove-this
table tlez�.,` his Geld�- liis:field
romp-T-S—k uld::_— =promPfsLould'— exdield.
fields _ eFuiia-no FCennfer-no
e arEment. EC-tion
37
Screen Attributes/Functionality
Problem Status Notebook 4 PEOPLE.DF[PEOPLENOTEBOOK[, FORM[GENERALFORM]
Key Field Prom t, Attributes � Comments ? •>, j b''=
NEW Fund Type :Entry . The value displayed in this entry
Control Name . field will be the value that was
FLX PEO VCHRI stored in the,Jlex field for this
Read Only :No person.
Mandatory :No . This field is updateable
Disabled :No
Caps Only :No
Data Type :String
Max Length :4
Default Value :NO
NEW Center Type :Entry . The value displayed in this entry
Control Name . field will be the value that was
FLX PEO VCHR2 stored in the,Jlex field for this
Read Only :No person.
Mandatory :No • This field is updateable
Disabled :No
Caps Only :No
Data Type :String
Max Length : 12
Default Value :NO
REMOVE SSN Type :Entry • Nothing. This field will be
Control Name . removed
FLX PEO VCHR3
Read Only :No
Mandatory :No
Disabled :No
Caps Only :No
Data Type :String
Max Length :12
Default Value :NO
38
Post-Migration SQL Transaction to move TPM 5.0.2 FAC Flex Field Data
into the new PROB FAC table
The City of Fort Worth currently stores FAC data associations to problems within Flex Fields of the
PROBLEMS table. One of the Migration-Customizations is to store this FAC data in a separate table
named PROS FAC. After the migration is complete SQL Transactions should be run to move this FAC
data from the PROBLEMS table Flex Fields into the PROB_FAC table. Once the data is moved the Flex
Fields formally used to store the FAC data in the PROBLEMS table should be cleaned. This process is
being do to fulfill requirements for The City of Fort Worth's TSD 6.0 Migration and Implementation
Solution.
Since the TPM 5.0.2 Flex Field customization only allowed for one(1)FAC association to a problem this
utility will create only one PROB_FAC record per problem in the City of Fort Worth's ADVISOR
database.
problem_id problem—id
PROBLEMS flx_pro_vchr2 fund code PROB FAC `T
TABLE TABLE= _M
flx_pro_vchr3 center
fix—pro_intl account
39
Asset Notebook
The Asset Page of the Asset Notebook has been modified to fulfill requirements for The City of Fort
Worth's TSD 6.0 Migration and Implementation Solution.
Control Fields added to The Acquisition Page for FAC:The following flex fields will be used to store a
single FAC record per asset:
Fieldpcom � '" ' ��
irle1d Control Name
Fund Code FLX VAL VCHRI
Account# FLX VAL VCHR2
Center FLX VAL VCHR3
Control Fields added to The Asset Page:The following fields will only display values associated to the
selected location:
`Field Preru Of'4x� 1.`.: -Field Cdntrol Name
DEMARC FLX LOC VCHRI
Location Addr Location address
An agent will be able to select values from these combo boxes that will be associated to the current asset.
Each of these fields will be required to have a value before an Asset can be created or updated. The values
displayed in each combo box will be derived from a new relational FAC tables. See Appendix C—SOL
Modifications. These tables hold the relationship between fund codes,accounts,and centers. Based on
agent value selection for each combo box the other combo boxes display list will be reduced based on its
relationship to the other FAC combo boxes.
Workflow modifications:
The workflow will be affected by the fact that each of the above FAC combo box fields will be
read-only and mandatory before begin able to Add or Update an asset. These fields will not be
included on any inquiry screens or reports within the TSD product.
Workflow modifications:
The DEMARC flex field will be added to the Location edit screen to allow for edits by the user.
40
Figure 7 displays the Asset Notebook
�Add AssetX
And I AttrhAt s Contracts Acgr+ Lease M4itenance.Fm i F OU&e s Charges Events) fK'
Valuation �,� - .• _: s+-
AcsRiai Dates Depreciation Method
attaght tree Ys
Disposal Date _ �/yysy - _ -- [3 f•pole Decinig Balance
Depieaation Months
-: - - — - Associated FundArxant µ�
Cut
e a Code: Fund CW' �,-Accow t it ;Center
SalvapeVakre�
vw
BookyVakim
' Irmed Value: j' :jrm ied:Acquisition
a S
t
L
-K° Cancel
"Associate a sin le^
.Fund Account to':
a single asset.�=�--
41
y
Figure 8 displays the Asset Notebook
A�tielTa¢ ... r r;.z�.a. �rz..,._r.,�„• .i ,, aeTa - -- - - -
CodCGdef »
a
,r
J DEMARC�
Paean _ (OfrIECh011
gemah° ^A
417-1 fail,
.._: :"may..�'”' b }✓ -,;. .�� _ . .. _.; .,.� � ,s +�.;•• »- � : - y,.�-.-
is •• -tx ,Iva,
Al
Locatioii=Flex
Fields:
42
Screen Attributes/Functionality
Problem Status Notebook 4 I ASSET.DF[ASSETNBI,FORM[ASSETVALUATION)
Key Field Prom" t Attributes x. J° = Comments
NEW Fund Code Type :Combo Box . No value will be initially displayed
Control Name . Unless the asset is being edited,in
flx einv_vchrl which case the current value of this
Read Only : YES field will be displayed as the
Mandatory : YES current value.
Disabled :No . This combo box will be read-only.
Caps Only :No . A blank entry value will be
Data Type :String included in this combo box This
Max Length :254 will allow the agent to clear the
Default Value :No displayed value in this combo box
• This combo box will be initially
loaded with all fund codes found in
the FUNDS table.
• When a fund code value is selected
by the agent a routine will be
executed that reduces the entries in
the Accounts,and Center combo
boxes,only if they do not already
have selected values. The routine
that handles this logic will
determine the values of the other
combo boxes by comparing
associations with thefund code
and other selected FAC combo box
values to table ASSOC FAC.
• See Appendix C—SOL
Modifications
NEW Account Type :Combo Box . No value will be initially displayed
Control Name . Unless the asset is being edited,in
flx einv_vchr2 which case the current value of this
Read Only : YES field will be displayed as the
Mandatory : YES current value.
Disabled :No 0 This combo box will be read-only.
Caps Only :No . A blank entry value will be
Data Type :String included in this combo box This
Max Length :254 will allow the agent to clear the
Default Value :NO displayed value in this combo box
• This combo box will be initially
loaded with all accounts found in
lite ACCOUNTS table.
• When an account value is selected
by lite agent a routine will be
executed that reduces lite entries in
lire Fund Code,and Center combo
boxes,only if they do not already
have selected values. The routine
that handles this logic will
determine the values of the other
combo boxes by comparing
associations with the account and
other selected FAC combo box
values to table ASSOC FAC.
43
• See Appendix C—SQL
Modi hcations
NEW Center Type :Combo Box . No value will be initially displayed.
Control Name . Unless the asset is being edited,in
fLx einv_vchr3 which case the current value of this
Read Only : YES field will be displayed as the
Mandatory : YES current value.
Disabled :No • This combo box will be initially
Caps Only :No loaded with all centers found in the
Data Type :String CENTERS table.
Max Length :254 . This combo box will be read-only.
Default Value :NO . A blank entry value will be
included in this combo box. This
will allow the agent to clear the
displayed value in this combo box.
• When an center value is selected by
the agent a routine will be executed
that reduces the entries in the
Fund Code,and Account combo
boxes,only if they do not already
have selected values. The routine
that handles this logic will
determine the values of the other
combo boxes by comparing
associations with the center and
other selected FAC combo box
values to table ASSOC FAC.
• See Appendix C—SOL
Modifications
UPDATE Ok Type :Button • When this button is clicked a check
Control Name :ok_button will be done to verb that
Read Only :No associated fund accounts for this
Mandatory :No asset.
Disabled : Yes . If not all fund account combo
Caps Only :No boxes have a value then the request
Data Type :N/A to complete the add or update will
Max Length :N/A be rejected with a message box
Default Value :NO stating so.
• The values shown in the Fund
Account combo boxes will be
stored in a associated table name
ASSET FUNDS
44
Screen Attributes/Functionality
Problem Status Notebook 4 I ASSET.DF[ASSETNB[,FORM[AEVASSET[
Key FieldProm't Attributes Comments �F.-a
NEW DEMARC Type :Entry • This is a read-only field
Control Name :fir loc_vchr] • When an asset is displayed,and a
Read Only : YES location exists for the asset this
Mandatory :NO field will be populated with
Disabled :No appropriate value from the
Caps Only :No locations table.
Data Type :String
Max Length :254
Default Value :No
NEW Loc Addr Type :Entry • This is a read-only field.
Control Name :flx loc vchr2 • When an asset is displayed,and a
Read Only : YES location exists for lire asset this
Mandatory :NO field will be populated with
Disabled :No appropriate value from the
Caps Only :No locations table.
Data Type :String
Max Length :254
Default Value :NO
45
Change Notebook
The Change Notebook has been modified to fulfill requirements for The City of Fort Worth's TSD 6.0
Migration and Implementation Solution.
New Page added to Change Notebook
Control Fields added to The Fund Account Page on the Change Notebook: The following non-stored
fields will be added to the Fund Accounts of the Change Notebook as combo boxes:
Field Prom`t' --ik4 'f : :Field Control Name :,`f—:K i
Fund Code FCode
Account# AcctNum
Center Center
Percentage Percentage
A table list will be added above these fields that displays what FAC data is currently associated to the
current change record. Records are added to this table list by filling out the above-mentioned combo boxes,
then clicking the Add button next to the table list. Next to the table list are three(3)buttons,Add,Edit,and
Delete. These buttons control the data in the table list using the values currently stored in the combo boxes
mentioned above. More than one FAC record can be associated to each change record.
Workflow modifications:
The workflow will be affected by the fact that each of the FAC combo box fields will be read-only
and mandatory before being able to add or edit a FAC record to the table list. The assumption is
that web-front-end users will submit change requests,and a change agent will update the change
requests with the appropriate fund accounts on this page of the Change Notebook. Change
requests will not be updateable without at least one(1)Fund Account association. Each of the
FAC combo boxes will be preloaded with all possible values from new corresponding FAC
ADVISOR tables.•The Add,Edit,and Delete buttons will be enabled and disabled based on the
data available in the FAC combo boxes on this notebook. Further descriptions of this
modification can be found in the"Screen Attributes/Functionality"Section of this document.
46
Screen Attributes/Functionality
Problem Status Notebook 4 RCHG.DF[CHANGE NOTEBOOKI,FORM[FAC FORMI
K � Field Pro!i t Attributes Comments = � �v
NEW Associated Type : Table This table control list will be
Fund Control Name . initially loaded with all FAC data
Accounts CHG FUND ACCOUNTS associated to the current change id
Read Only :N/A No record in this list will be
Mandatory :N/A highlighted during screen creation.
Disabled :No • This table control will store the
Caps Only :No FAC data entered by the agent in a
Data Type :Record table named CHG_FAC with the
Max Length :N/A value of the current change id.
Default Value :N/A • The data in this table control is
Columns manipulated by the Add,Edit,and
FUND CODE Delete buttons.
ACCOUNT • When one of the records in this
CENTER table control is highlighted,then
PERCENTAGE the display of the FAC combo
CHGFAC ID—Zero Length boxes below should be updated to
display the values in this controls
columns.
• Also when one of the records in
this table control is highlighted,
then the items available in the FAC
combo boxes need to be refined to
only items matching the
relationships of the other two
combo boxes.
• See Appendix C—SOL
Modifications
NEW Add Type :Button • This button is disabled initially.
Control Name . • If any one of the FAC combo boxes
FAC ADD BUTTON does not have a value selected,then
Read Only :N/A this field will be disabled.
Mandatory :N/A • An exception to enabling this
Disabled : Yes button would be if the table control
Caps Only :No already has a record that matches
Data Type :N/A the selected FAC combo box values
Max Length :N/A currently displayed.
Button Type : Text 0 When this button is click the values
in the FAC combo boxes will be
formatted along with the problem
id and Percentage into a record
and stored in the CHG FAC table,
and inserted into the
CHG_FUND_ACCOUNTS table
control list on this notebook.
• A check will be done just before
adding the FAC data into the
CHG_FUND ACCOUNTS table
control on this screen. The check
will determine if the percentage
being added to this list causes the
list to have a percentage greater
than 100%. If the percentage is
47
A
greater then give the agent a
warning and don't insert the FAC
data into the
CHG_FUND ACCOUNT table
control. . Additionally the FAC
values will be validated against the
ASSOC FAC table,if a matching
set of values is not found,then a
warning message will be displayed,
and the recorded will not be
inserted into the screen or
database.
NEW Edit Type :Button • This button is disabled initially.
Control Name . • This button will be enabled when at
FAC EDIT BUTTON least one value gists in the table
Read Only :N/A list and a record is highlighted.
Mandatory :N/A • An exception to enabling this
Disabled : Yes button would be if not all FAC
Caps Only :No combo boxes and the percentage
Data Type :N/A have a value displayed.
Max Length :N/A . When this button is clicked the
Button Type : Text currently highlighted record in the
table list will be removed and the
record in the
CHG_FUND_ACCOUNT will be
deleted Then the values in the
FAC combo boxes and percentage
will be formatted along with the
change id into a record, and stored
in the CHG FAC table,and
inserted into the
CHG FUND—ACCOUNTS table
control list on this notebook.
• A check will be done just before
updating the FAC data into the
CHG_FUND—ACCOUNTS table
control on this screen. The check
will determine if the percentage
being updated to this list causes the
list to have a percentage greater
than 100%. If the percentage is
greater then give the agent a
warning and don't update the FAC
data into the
CHG—FUND—ACCOUNT table
control.. Additionally the FAC
values will be validated against the
ASSOC_FAC table,if a matching
set of values is not found,then a
warning message will be displayed,
and the recorded will not be
inserted into the screen or
database.
NEW Delete Type :Button • This button is disabled initially.
Control Name . This button will be enabled when at
48
FAC_DEL_BUTTON least one value exists in the table
Read Only :N/A list and a record is highlighted.
Mandatory :N/A • When this button is clicked the
Disabled : Yes table control list record that is
Caps Only :No high-lighted will be removed and
Data Type :N/A the corresponding CHG FAC table
Max Length :N/A record will be deleted.
Button Type : Tett
NEW Fund Code Type :Combo Box • No value will be initially displayed.
Control Name :fCode • This combo box will be read-only.
Read Only : YES • A blank entry value will be
Mandatory : YES included in this combo box. This
Disabled :No will allow the agent to clear the
Caps Only :No displayed value in this combo box.
Data Type :String • This combo box will be initially
Max Length :4 loaded with all fund codes found in
Default Value : YES the FUNDS table.
• When a fund code value is selected
by the agent a routine will be
executed that reduces the entries in
the Accounts, and Center combo
bores, only if they do not already
have selected values. The routine
that handles this logic will
determine the values of the other
combo bores by comparing
associations with the fund code
and other selected FAC combo box
values to table ASSOC FAC.
• See Appendix C—SQL
Modifications
NEW Account Type :Combo Box 0 This combo box will be initially
Control Name :acctNum loaded with all accounts found in
Read Only : YES the ACCTS table.
Mandatory : YES • This combo box will be read-only.
Disabled :No • A blank entry value will be
Caps Only :No included in this combo box. This
Data Type :String will allow the agent to clear the
Max Length : 6 displayed value in this combo box
Default Value :NO . When an account value is selected
by the agent a routine will be
executed that reduces the entries in
the Fund Code, and Center combo
bores,only if they do not already
have selected values. The routine
that handles this logic will
determine the values of the other
combo bores by comparing
associations with the account and
other selected FAC combo box
values to table ASSOC FAC.
• See Appendix C—SQL
htorli tcations
NEW Center Type :Combo Box • This combo box will be initially
Control Name :center loaded with all centersfound in lite
49
Figure 9 displays the Change Notebook
. ,• x
t �
General Fund}lccount 1 Cost Reasons 1 Approvals)Asiets 1 impact: basks Prohfemv�y 1 rE °
�mc�— � 7�f <,z�'?F s r'. ,rr � n .€. �" �s34,' '�'r%' .. x,,, i"'x'�r•"""w��
� Assoc�ated Fund Acycixrits �, z X: ,. ,
I
> + a 1 �z 71,411—
OA Code• Amount# :Center » A
Delele�s '
Fund Code Amountia Center x`a Percentagen.
Y
71
P►1low_ nultiple�Funcl��
—Accounts,:to be_associated _
,ith'Fa-_singie ch'ange,'request
51
Appendix A — Test Cases
Test Case Documenation
Documented Procedures:
The Test Plan Approach to be used by Evergreen Systems, Inc. will include, but is not
limited to the details described below. The Migration/Customization Design document
was approved with a test certification & signature section for each
migration/customization item. At the beginning of each week an Evergreen Systems, Inc.
developer, not the developer that writes the migration/customization, will test each
completed migration/customization item. Once the migration/customization item is
tested to certification by the Evergreen Systems, Inc. developer he/she will sign off on the
migration/customization item and report any problem issues to the actual
migration/customization developer. This information will be passed via the weekly status
report to the customer. During the migration/customization process the Evergreen
Systems, Inc. developer will create a Test Case for each item migrated/customized. This
Test Case will be based on the information below:
Migration/Customization NOT affecting the User Interface
Database Modifications
Altering Tables, Views, Triggers, Stored Procedures, and Constraints
Based on SQL Scripts and migration/customization documentation provided for each
migration/customization item validate that the install via TSDBUILD functions correctly. Also validate
that the fields included in the added/modified tables or views are correct for the migration/customization
documented. Individually test each trigger or stored procedure based on the internal logic for each. In
other words each condition within the trigger or stored procedure should be rigorously tested via TSD 6.0
to insure proper behavior for each.
Performance
This can only be completely validated against a production like database. Although, by watching out for
common queries or user behaviors within each migration/customization item reasonable assumptions can
be made. For each instance an index or indexes should created. If the index does not improve performance
remove it from the SQL-Script.
Business Rules
Conditional Loading of Fields
Some migration/customization items include logic to only load specific data into data entry, list box,or
combo box fields. This loading process is usually based on business rules. These rules are included in the
migration/customization documentation and each one will be validated.
52
C) Check"Fail' to indicate that the test results are not acceptable.
d) All Failures must have a reason given for the failure on the Reason
for Failure line.
e) Your name must appear on each test case sheet to indicate that
you performed the test
f) The date of each test case execution must be on each sheet.
g) General Comments are optional and at your discretion.
Migration of Current Customizations Test Cases
<Title of migrated/customized task to be tested>. (code comment reference
number)
Test Case(1)
• Step(1)
• Step(2)
• Step(3)
• Etc...
Test Case(2)
• Step(1)
• Step(2)
• Step(3)
• Etc...
Test Case(3)
• Step(1)
• Step(2)
• Step(3)
• Etc...
54
Appendix B — SQL Modifications
FUNDS
FUND ID CHAR(15) NOT NULL
DESCRIPTION CHAR(30) NULL
MODIFY DATETIME INT NOTNULL
ACCOUNTS ASSOC-FAC
ACCOLNT_ID CHAR(15) NOTNULL FUND_lD CHAR(15) NOT NULL
DESCRIPTION CHAR(30) NULL ACCOUNT_ID CHAR(IS) NOT NULL
MODIFY DATETUIE INT NOT NULL CENTER 1D CHAR(40) NOTNULL
DESCRIPTION CHAR(30) NUL
MODIFY DATETIME MT NOTNULL
CENTERS
CENTER_ID CHAR(40) NOT NULL
DESCRIPTION CHAR(30) NULL
MODIFY DATEM INT NOT NULL
PROB FAC
PROBFAC ID VA.RCHAR(IS) NOT NULL
PROBLEM ID VARCHAR(15) NOT NULL
FUND ED N
CHAR(15) NOT ULL
ACCOUNT_ID CHAR(15) NOT NULL
CENTER ID CHAR(40) NOTNULL
PERCENTAGE PIT NOT NULL
MODIFY DATETWE INT NOT NULL
CHG FAC
CHGFAC IDVARC}IAR(IS) NOT NULL
CHANGE ID INT NOT NULL
FUND_IDCHAR(15) NOT NULL
ACCOUNT_ID CHAR(15) NOT NULL
CENTER_ID CHAR(40) NOT NULL
PERCENTAGE Nr NOT NULL
MODIFY DATETIME INT NOT NULL
Primary Keys SOL
Alter Table<<tab_qual>>.PROB_FAC Add Primary Key(problem_id)
Alter Table<<tab_qual>>.CHG_FAC Add Primary Key(problem_id)
Indexes Required SOL
Create Unique Index CFWO1_PROBFAC ON<<tab_qual>>.PROB_FAC(problem_id,fund_id,
account_id,center_id)<<ON_INDEX_SEGMENT`>>
Create Unique Index CFW02_CHGFAC ON<<tab_qual>>.CHG_FAC(problem_id,fund_id,account—id,
center id)<<ON_INDEX_SEGMENT>>
Additional Required SOL
Insert Into<<tab_qual».COUNTERS(counter_name,next—number)values(`PROBFAC_ID', 1 )
Insert Into<<tab_qual».COUNTERS(counter—name,next number)values(`CHGFAC_ID', 1 )
55
- w
City of Fort Worth Acceptance
City of Fort Worth accepts the information and design specifications contained in the Tivoli Service Desk
6.0 Coding of Migration-Customizations Detailed Technical Design Document updated May 1,2000.
The undersigned agrees to the scope,definition, and timetable of the project proposed in this document.
The undersigned also understands that Evergreen Systems,Inc.will not schedule work until a signed copy
of this agreement is provided to the Development Project Manager listed below.
Evergreen Systems,Inc. Project Manager: Clyde Wimbrough
City of Fort Worth:
�5t4 Vl D R. Bf cfC' C/Fd S S Z o00
Signature Printed Name and Title Date
A copy of this agreement must be returned to Evergreen Systems,Inc. 1851 Alexander Bell Drive,Suite
450,Reston, VA.20191,OR Faxed to(703)390-1266
56
y.s.s
A46AAL A&AAL A&A-
A6AAL&AAA
ALA&uA�A�,&..A,
Evergreen Systems,Inc.
Tivoli Service Desk 6.0
End User Web Site (KML)
Detailed Technical Design
May 9, 2000
City of Fort Worth
Evergreen Systems,Inc. Prepared By: Douglas J.McElhaney
1851 Alexander Bell Drive Development Systems
Suite 450 703 919 4427
Reston, Virginia 20191 Dou9.McElhanevaever greens,;.corn
6/23/00 2i'
Table of Contents
Tableof Contents............................................................................................................................................2
Introduction.....................................................................................................................................................3
DocumentDefinition.......................................................................................................................................4
INTRODUCTION............................................................................................................................................4
PROJECTSCOPE............................................................................................................................................4
APPENDICES.................................................................................................................................................5
ProjectDefinition............................................................................................................................................6
Assumptions....................................................................................................................................................7
Objectives........................................................................................................................................................8
Resources........................................................................................................................................................9
Strategy.........................................................................................................................................................10
ProjectScope.................................................................................................................................................12
SYSTEM REQUIREMENTS/ARCHITECTURE................................................................................................12
Screensand Logic.........................................................................................................................................14
(Tivoli Service Desk/Application Server 6.0 Customizations)...................................................................14
APPLICATION SERVER MAIN SCREEN ........................................................................................................14
(Tivoli Service Desk/Question Matrix Section)..........................................................................................15
QUESTION MATRIX MAIN SCREEN.............................................................................................................15
QUESTION MATRIX MODIFICATION SCREEN..............................................................................................17
MULTIPLE CHOICE RESPONSE SCREEN......................................................................................................20
(Tivoli Service Desk/Problem Cause Routing Section)..............................................................................22
PROBLEM CAUSE NOTIFICATION ROUTING SCREEN...................................................................................22
PROBLEM CAUSE NOTIFICATION ROUTING EDIT SCREEN..........................................................................24
(Tivoli Service Desk/Resume Notebook)....................................................................................................26
PROBLEM STATUS SCREEN—WORK HISTORY PAGE OF RESUME NOTEBOOK............................................26
(Tivoli Service Desk/Model Notebook)......................................................................................................27
CHANGE MODEL SCREEN—GENERAL PAGE OF MODEL NOTEBOOK..........................................................27
Appendix A—Estimate of Application Server Modifications,Tivoli Service Desk 6.0 Modifications, and
creationof End User Web Site......................................................................................................................28
Appendix B—SQL Information for New Tables..........................................................................................30
Prepared By: Douglas J. McElhaney
2
Introduction
The following is a detailed design document,which describes the End User Web Site Development. The
following detailed design was derived from the Statement of Work dated November 11, 1999 and
supporting information gathered during the kickoff and other meetings from January 12, 2000 through
April 12, 2000.
The summary of End User Web Site Development is included in this detailed design as follows:
TSD 6.0 Application Server Customizations
TSD 6.0 KML and DF Modifications for supporting Data
q� Architectural Hardware/Software Design Recommendations
Post-Development Configuration
Custom SQL Scripts
This document describes, at a detailed level,the tasks involved to implement the solution. The document
provides screen information and database modifications. The customization tasks and estimates are based
upon Evergreen Systems'understanding of the requirements through conversations between Evergreen
Systems, Inc. and The City of Fort Worth.
Modifications to Evergreen Systems'understanding of the requirements may affect the estimates associated
with the defined project. The figures represented within this document are to be considered only estimates
and Evergreen Systems, Inc. shall not be deemed to be in breech or default if they are not met. These
customizations will require modifications to the database, source code and dialog boxes used to display the
application information.
All modifications will follow Tivoli Systems Integration Services Customization Standards.
Prepared By: Douglas J. McElhaney
3
Document Definition
This document contains several major sections. These sections are described below.
Introduction
tk, Project Definition
Definition of the problem to be solved by the project
W Assumptions
Basic assumptions that are made in defining the project
W Objectives
Objectives, for which the project will be measured, including technical, profit performance,
quality,etc.
W Resources
Resources are necessary to complete the project. Resources can include people, equipment,
facilities and materials.
W Strategy
A detailed strategy will be used in implementing the project.
Project Scope
W System Requirements/Architecture
This section contains the required or expected information about the hardware and
Software that will support the Custom Solution as described within this document.
W Screens and Logic (TSD 6.0)
This section contains screen prints and information about the functionality of all
customizations to TSD 6.0.
Prepared By: Douglas J. McElhaney
4
Appendices
A. Estimate
This appendix contains an estimate of the days required to complete the requested migration
and modifications for the Custom Solution.
B. SQL Modifications/Additions
This appendix contains the scripts for all database modifications and additions.
Prepared By: Douglas J.McElhaney
5
Proiect Derinition
The project definition for the End User Web Site Development is defined as follows:
1. To create a web site that will allow CFW employees access to the Tivoli Service
Desk system. This access will allow the logged in user the ability to submit
problems,submit changes using pre-defined change categories and models and the
ability to view the status of any item submitted. The web site will also allow certain
users to approve changes.
2. Modify the TSD 6.0 Application Server to provide processing functionality for the
new data submitted via the web.
3. Following is the format of code commenting used at the module-level when modify
TSD code.
(*ESICMT Begin CFW Evergreen Systems,Inc.(xxx) mm/dd/yy hh:mm:xM ESICMT*)
(*Begin ESICFWxxx-yyyy###*)
(*End ESICFWxxx-yyyy###*)
(*ESICMT End CFW Evergreen Systems,Inc.(xxx)mm/dd/yy hh:mm:xNl ESICMT*)
xxx=Programmers Initials
mm/dd/yy=date of modification
hh:mm:xM=time of modification, example( 13:25 PM)
ESICFWxxx-yyyy444=xxx=programmer initials, yyyy=year,
444=unique identifier documented in MODAPISD.KB
4. Additional documentation will be provided in the code within module
MODAPISD.KB and MODAPI.DF. This code module is used to fully document
each modification, and houses any additional function,procedures,or events.
Prepared By: Douglas J. McElhaney
6
Assumptions
=> All modifications will be performed using Tivoli Systems Coding Standards.
=> A separate SQL script will be created for all database modifications. This complies with
Tivoli Systems Coding Standards. The name is MODAPISD.SQL.
=> The scope of the first deliverable is defined in the Technical Design Document. Any
additional requirements will impact the deliverable and delivery dates.
=> Stable environment, both a production and test environment will be built.
=> This customization and integration effort performed by Evergreen Systems will require that
The City of Fort Worth provide certain support. This support is detailed below:
Information Support Services Representative-A representative from the Information
Support Services Center must be available, on call, for the entire Evergreen Systems
development phase and during any on location visits. This person must have authority to
make decisions regarding operations,system configurations and design specifications.
Database Analyst-A database analyst or someone equally familiar with The City of
Fort Worth's database structures may be required on a part-time basis.
Prepared By: Douglas J.McElhaney
7
Objectives
To create a user-friendly web site that will allow CFW employees to easily interact with the
support center. Additionally,the TSD 6.0 product will be modified to appropriately process all
incoming requests to meet The City of Fort Worth's requirements, which were:
This system shall be capable of the following.
1. Be accessible via the City's intranet from any networked workstation.
2. Consist of a series of easily navigable and understandable screens that collects customer-
provided information necessary for ISS to provide a request and charge the customer for this
request;the screens shall be fully customizable to meet changing customer and ISS
requirements for information.
3. A request for service should be capable of accepting various file attachments, such as
word processing documents, spreadsheets or graphics files prior to submission so they will be
routed to the appropriate destination with the request.
4. Route a request for service to the appropriate ISS or contractor destination for action;
routing shall be changeable,as conditions require.
5. Provide the information necessary for the creation of a work order, in a format that can be
fully customized to meet work unit needs.
6. Upon submission by a customer,the system shall authenticate the following information
prior to acceptance and routing of the request to the appropriate ISS destination:
a) Accounting system validity of fund and center information provided by customer.
b) Authority of requesting customer to submit the request and authorize payment from the
given fund and center.
7. The authority of a requesting customer to submit the request and authorize payment from
the given fund and center shall be determined by the use of a special ISS-issued credit card.
The credit card number shall reference said information and provide secure access to the
request for service system.
8. Provide fund, account and center(FAC) information that can be read by other
components of the billing system as necessary.
9. Allow up to 26 concurrent credit card numbers and FACS for intra-or inter-departmental
split funding of requests. Multiple FACs allocated on a percentage basis. Screen shows sum
of allocated percentages so it's easy to tell when they add to 100%. The purpose of this is to
allow up to 26 different customers to participate in a single project.
10. Online help.
11. Interface with Tivoli to allow customer-generated updates of asset and people
information.
Prepared By: Douglas J. McElhaney
8