FieldNet 2.x Enhancement TUG – September 8, 2003 Andres Marin, Info Tech Inc.
-
Upload
daniela-perkins -
Category
Documents
-
view
219 -
download
0
description
Transcript of FieldNet 2.x Enhancement TUG – September 8, 2003 Andres Marin, Info Tech Inc.
FieldNet 2.x EnhancementFieldNet 2.x Enhancement
TUG – September 8, 2003Andres Marin, Info Tech Inc.
Project Scope ObjectivesProject Scope Objectives Replace the manual processes used by Michigan DOT to
ensure effective synchronization and balance between CAS and FieldManager
Minimize user involvement and to automate the actual transfer of data between FieldManager and CAS regardless of geographic distances. This will remove many potential points of failure inherent in the current physical transfer of data.
Use new technologies and methodologies to ensure that all data transfers are completed successfully or else completely rolled back with the state of both databases corrected.
Project Scope Objectives Project Scope Objectives (cont)(cont)
Built on Internet standards allowing the ubiquitous, secure and inexpensive automation of business processes.
Implement a scalable and flexible architectural design for future enhancements.
Data transfers will be authenticated, authorized, reliable, secure, accurately routed and delivered to the correct destination.
Project MilestonesProject MilestonesMilestone Target Date Status
Project Kick-Off 11/27/2002 100%
Inception Phase Complete 2/14/2003 100%
Elaboration Phase Complete 6/25/2003 100%
Build Cycle 1 Complete 10/17/2003 80%
Build Cycle 2 Complete 1/28/2004
Build Cycle 3 Complete 8/9/2004
Beta Release – Start 8/9/2004
End of Beta Period 11/5/2004
Field Test Period – Start 11/5/2004
End of Field Test Period 5/13/2005
Production Release 5/13/2005
End of Warranty Period 11/15/2005
Warranty Resolution Release 1/11/2006
Project Phases Scope OverviewProject Phases Scope Overview
Development Phase Scope Summary
Elaboration Phase Functional & Architecture Specifications; Macro Design Specifications; GUI Specifications
Eng. Build Cycle 1 Messaging and FN Server Architecture; Reference Files; Contract Initialization
Eng. Build Cycle 2 Authorization & Authentication; Pay Estimates; Contract Modification; CAS Interface; Implement New User Roles; Contract Transfer
Eng. Build Cycle 3 Contract Transfer; FM & FB workflows; Reports; Administrative Console; Activity Logging; CAS & FM Synchronization; Installation Utility
Current StatusCurrent Status Project Percent Complete: 40% Overall Project Assessment: On schedule and on
budget Build Cycle 1: In progress
– Engineering complete– Alpha testing - 9/12/03– System Design Specification updates - 9/12/03– MDOT QA/QC Test - 9/17/03
Project BudgetProject Budget
MDOT Approved Budget $1,210,000
ITI Approved Budget $439,074
Total Budget $1,649,074
Architecture OverviewArchitecture Overview
M es s ag in g S e rv er
F ie ld Bo o k
F ield N etC lien t
M es s ag in gC lien t
F ield N etS er v er
C o n s tru c t io nAd m in is tr a t io nS y s tem (C AS )
C A S A p p lic a t io nSe r v e r
( B a t c h p r o c e ssin g)
F ie ld M an ag er
F ie ld N etC lien t
M es s ag in gC lien t
Bro w s er
F ie ld N etAd m in is tr a tio n /Au d it in g
F ie ld N etW eb S erv er F ie ld N et
D atab as e
F ie ld N etC lien t
M es s ag in gC lien t
A u th o rizat io n /A u d i t i n g
M es s ag in gC lien t
F IE L D N E T E N H AN C E M E N T - L O G IC IAL V IE WC O M P O N E N T M O D E L - P rel i m i n a ry
G e t/Pu tG e t/Pu t
G e t/Pu tG e t/Pu t
A u th o rizat io n /A u d i t i n g
L EG END :N ew
E x istin g F ig ure 1
Architecture OverviewArchitecture Overview Deployment ModelDeployment Model
Ex tern a lF M /F BUs er s
I n ter n e t
In te rn a lF M /F BUs er s
F ie ld N etS erv er
M es s ag in gS erv e r
C o n tra cto r S it e
A g e n cy S it e
Ex ter n a lF W
I n ter n a lF W
D M Z
h ttp /h ttp s8 0 /4 4 3
C ASS erv e rF W ex te rn al
h t tp /h t tp s8 0 /4 4 3
a p p r o v e d h o st /p o r tSe c ur e A c c e ss/W e bSe r v e r
C AS d b
F ie ld N et d b
Secu
re A
cces
sCl
ient
(MQ
IPT )
Project Risks - SummaryProject Risks - Summary
Key Risk Mitigations – Synchronization with FM– Synchronization with CAS– Synchronization with FM / SM Interface
TRT Questions /AnswersTRT Questions /Answers
FM support of FN Versions– ITI recommends FM 4.X to support FN 2.X
FN will be compatible with latest version of CAS– CAS 5.2a 7/03– CAS 5.3a 1/04– CAS 5.3b 6/04
Licenses changes will not affect “clients” as a result of using IBM WebSphere MQ
FN RDBMS support: Oracle 9.ix