logging in or signing up MEA4 Tito1 Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 68 Category: Education License: All Rights Reserved Like it (0) Dislike it (0) Added: February 20, 2008 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript Helping Departments Develop E-Commerce Applications: ﴀ ﴀ 1 Helping Departments Develop E-Commerce Applications John Chapman Washington State University October, 2004 Overview of WSU: Overview of WSU Research university 22,000+ students Four campuses Multiple learning centers Distance education programSlide3: WSU Campus LocationsGoal of Presentation: Goal of Presentation Describe how central IT at WSU has made it easy and cheap for departments to develop e-commerce applications.Presentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental needs for e-commerce applications Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) ConclusionPresentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications and IT staff Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Three E-commerce Servers : Three E-commerce Servers Cybersource Payment Manager 3.5 Real-time credit card authorizations over the Internet Accepts transactions from web and client-server applications Current version runs on Windows 2000 with SQL Server database Costs us about $3800 per year for software maintenance First purchased in 1997 Overview of E-commerce applications at WSUThree E-commerce Servers : Three E-commerce Servers Pay Central Payment Gateway 2.5 Accepts eCheck transactions from web applications Accepts a nightly batch of employee reimbursements from our legacy payables system Creates and FTPs a daily ACH file to the bank Current version runs on Windows 2000 with SQL Server Costs us about $4800 per year for maintenance and support Implemented in January 2003 Overview of E-commerce applications at WSUThree E-commerce Servers : Three E-commerce Servers Diebold Card Systems CS Gold Cougar CASH Debit Account Dining accounts Residence hall access Vending machines Tuition Housing Many other uses Oracle 9i Database on Windows 2000 Overview of E-commerce applications at WSUSummary of E-commerce Activity at WSU : Summary of E-commerce Activity at WSU 40+ applications Growth rate of 25-50% per year since 1998 Over 155,000 credit card transactions for over 56 million in the last twelve months Over 6800 eCheck transactions for over 4.5 million in the last twelve months Overview of E-commerce applications at WSUPresentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Slide12: Overloaded Wide range of technical expertise Staff turnover and continuity Variety of platforms and languages Very tight budgets Departmental e-commerce applications Departmental IT OrganizationsSlide13: Controls and security Lower costs – greater purchasing power Efficiencies DON’T want many e-commerce solutions Advantages to Using Central IT E-commerce Services Departmental e-commerce applications Presentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications and IT staff Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Slide15: No start-up costs No vendor software required No set-up or configuration fee Currently no fee for new merchant number Priority 1 – Make it CHEAP Cost to DepartmentsSlide16: Low on-going costs Low credit card fees No per-transaction fee Additional savings from reduced staff time No card-swipe monthly rental fee Save staff time with self-service aps Priority 1 – Make it CHEAP Cost to DepartmentsSlide17: Servers and software housed at WSU E-commerce servers and software are centrally funded Credit card software maintenance ~ $3,800 annually E-Check software maintenance ~ $4,800 annually Priority 1 – Make it CHEAP E-Commerce Costs at WSUPresentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications and IT staff Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Slide19: All E-commerce transactions use XML-RPC XML-RPC is a web service XML-RPC is a precursor to SOAP Priority 2 – Make it EASY Accessing WSU E-Commerce ServersSlide20: Simple and easy to use Most implementations are free Available from many different languages and platforms Priority 2 – Make it EASY Characteristics of XML-RPCPartial list of implementations: Partial list of implementations Priority 2 – Make it EASY AOLserver: client/server (Aaron Swartz, et. al.) Apache: client/server (Andrew Bihun) AppleScript: client (Late Night Software) ASP: client/server (David Carter-Tod) Axapta: client/server (Greg Pierce) C/C++: client/server (Eric Kidd/FirstPeer) C: client/server (Epinions) Chicken: client/server (Felix Winkelmann) Cold Fusion: client/server (Rob Blitz) COM: client (EnAppSys) Delphi/Kylix: client/server (Cliff Baeseman) Dylan: client/server (Chris Double) Eiffel: client/server (Glenn Maughan) Erlang: client/server (Joakim Grebeno) Flash: client (Patrick O'Lone) Frontier/Radio UserLand: client/server (UserLand) Guile: client/server (Evan Prodromou) Internet Explorer: client (Olav Junker Kjær) J2ME: client (Kyle Gabhart) Java: client (Josh Lucas) JavaScript: client (Jan-Klaas Kollhof) K: client/server (Christian Langreiter) KDE: client/server (Kurt Granroth) Lingo: client (Stefan Rinner) Lisp: client/server (Daniel Lundin) Microsoft .NET: client/server (Nicholas Christopher) Mozilla: client (Samuel Sieb) Objective C: client/server (Marcus Müller) Perl: client/server (Ken MacLeod) PHP: client/server (Simon Willison) Pike: server (Pitrich Information Technologies) Python: server (Jan-Klaas Kollhof) REALBasic: client (Sam DeVore) Rebol: client/server (Thomas Jensen) Ruby: client/server (Michael Neumann) Scheme: client (Pete Hopkins) Squeak: client (Christian Langreiter) Tcl: client (Vitessa) Tintware: client/server (Michael K Montague) WebObjects: client/server (Hannes Wallnöfer/Jim Roepcke) Zope: client/server (PythonWare/Eric Kidd/UserLand) Slide22: Program passes parameters to the XML-RPC client Program invokes an XML-RPC client and specifies a URL, method name and parameter list The XML-RPC client wraps the parameters in XML Priority 2 – Make it EASY How XML-RPC WorksSlide23: The XML-RPC client sends the parameters to the specified location via HTTP or HTTPS The XML-RPC server unpacks the parameters and passes them to the server program The server program processes the parameters and passes the results back to the XML-RPC client. Priority 2 – Make it EASY How XML-RPC Works (continued)Slide24: <?xml version="1.0"?><methodCall><methodName>authcap</methodName> <params> <param> <value> <struct> <member> <name>merchant</name> <value> <string>WSU_PRESS</string> </value> </member> <member> <name>legacy_account</name> <value> <string>601</string> </value> </member> <member> <name>card_num</name> <value> <string>4234567890123456</string></value></member> How XML-RPC Works (continued) Priority 2 – Make it EASY Parameters are wrapped in XML during transportSlide25: Unix/Apache Windows/IIS Linux/Interchange E-commerce Vendor Software XML-RPC (server) Priority 2 – Make it EASY E-commerce Architecture using XML-RPC Payment Gateway XML-RPC (client) VBScript/ASPSlide26: Web Application E-commerce Server Priority 2 – Make it EASY Web Application to E-commerce Server Data Flow URL and Method Name (Host and Name of e-commerce routine) Amount Primary Id: (Student Id, Customer #, Invoice #) Secondary Id: (Name, Address, Phone) Payment Info (Merch Num, Card num, Bank Acct Num, etc.) Accounting Info (Acct Num, Revenue Source, etc.) Other (Browser IP, Acctg Feed Ind) Response Code Unique Trans Id Data Flow Using XML-RPCXML-RPC Code Example (client): XML-RPC Code Example (client) Priority 2 – Make it EASY '----------------------------------------------------------- ' prepare parameters for the call to the XML-RPC routine '----------------------------------------------------------- set dict=Server.createObject("Scripting.Dictionary") dict("merchant") = "transcript" dict("payment_option") = "425" dict("card_num") = "4234567890123456" dict("exp_date") = "1104" dict("amount") = "10100" dict("primary_id") = "90559799" set paramList(0) = dict '---------------------------------------------------- ' Call xml-rpc server routine '---------------------------------------------------- answer = xmlRPC("https://WSUXXX.it.wsu.edu/xml-rpc/authcap.asp", "authcap", paramList) set return_dict = answer(0) '---Process the returned parameters if return_dict("return_code") = "0" then 'card was successfully charged response.write ("<p> " & return_dict("return_message")) response.write ("<p> Seq. Number is: " & return_dict("cpm_sequence_num")) response.write ("<p> Auth Code: " & return_dict("approval_code")) .Slide28: Applications are de-coupled from the vendor e-commerce software Don’t have to dictate to departments what language/platform they have to use It is simple, available and very easy to use. Its free! Priority 2 – Make it EASY Why we like XML-RPCPresentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications and IT staff Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Slide30: Automated recording of revenue in the accounting system Reduced departmental staff time Provided administration and reporting tool Daily fraud reporting Priority 3 – Make it EFFICIENT Improved Work FlowSlide31: Web Application E-commerce Server Priority 3 – Make it EFFICIENT URL and Method Amount Primary Id: (Student Id, Customer #, Invoice #) Secondary Id: (Name, Address, Phone) Payment Info (Merch Num, Card num, Bank Acct Num, etc.) Accounting Info (Acct Num, Revenue Source, etc.) Other (Browser IP, Acctg Feed Ind) Response Code Unique Trans Id Recording Revenue in Accounting (Automated) Enterprise Server Legacy Accounting System Accounting Info Nightly Batch ProcessSlide32: Enterprise Server Priority 3 – Make it EFFICIENT Recording Revenue in Accounting (Manual) Legacy Accounting System Daily Transactions Complete Cash Deposit Form (requires two signatures) Form data is entered by Controller's Office staffSlide34: No Cash Deposit form No card swipes No dual entry Self-service aps Priority 3 – Make it EFFICIENT Reduced Departmental Staff TimeSlide35: E-commerce Server Priority 3 – Make it EFFICIENT Administration and Reporting Tool WSU Foundation Athletics WSU Press Controller’s Office Downloads by Merchant and Date Range Returns, Miscellaenous charges, Reconciliation, Troubleshooting and Reporting E-commerce Administrative Application Slide36: Emailed each morning to business managers Top 10 occurrences of: Card number Primary Id IP of customer's browser Priority 3 – Make it EFFICIENT Daily Fraud Reporting Credit Card Count Dollar Amount XXXXXXXXXXXX4700 13 7065.5300 XXXXXXXXXXXX5015 11 2051.4600 XXXXXXXXXXXX8200 10 10960.3200 * * * Primary Id Count Dollar Amount 10390885 7 12014.0000 10734898 7 4072.6300 10581476 6 4620.0000 * * * IP Address Count Dollar Amount 64.126.137.9 12 8034.5000 64.126.190.197 9 7954.6800 * * * Presentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications and IT staff Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Slide38: Controls and security Lower costs – greater purchasing power Efficiencies Conclusion Advantages of Central IT E-commerce SolutionSlide39: Centrally funded No purchased software required No set-up fees No per-transaction charges Very low discount and interchange fees No charge for merchant numbers Conclusion Make it CHEAPSlide40: E-commerce services use XML-RPC Platform and language of preference Easy to use Simple, intuitive parameters Conclusion Make it EASYSlide41: Revenue posted daily to departmental account(s) Reduced departmental staff time E-commerce Administrative Application Daily fraud reporting Conclusion Make it EFFICIENTSlide42: Conclusion Questions? You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
MEA4 Tito1 Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 68 Category: Education License: All Rights Reserved Like it (0) Dislike it (0) Added: February 20, 2008 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript Helping Departments Develop E-Commerce Applications: ﴀ ﴀ 1 Helping Departments Develop E-Commerce Applications John Chapman Washington State University October, 2004 Overview of WSU: Overview of WSU Research university 22,000+ students Four campuses Multiple learning centers Distance education programSlide3: WSU Campus LocationsGoal of Presentation: Goal of Presentation Describe how central IT at WSU has made it easy and cheap for departments to develop e-commerce applications.Presentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental needs for e-commerce applications Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) ConclusionPresentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications and IT staff Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Three E-commerce Servers : Three E-commerce Servers Cybersource Payment Manager 3.5 Real-time credit card authorizations over the Internet Accepts transactions from web and client-server applications Current version runs on Windows 2000 with SQL Server database Costs us about $3800 per year for software maintenance First purchased in 1997 Overview of E-commerce applications at WSUThree E-commerce Servers : Three E-commerce Servers Pay Central Payment Gateway 2.5 Accepts eCheck transactions from web applications Accepts a nightly batch of employee reimbursements from our legacy payables system Creates and FTPs a daily ACH file to the bank Current version runs on Windows 2000 with SQL Server Costs us about $4800 per year for maintenance and support Implemented in January 2003 Overview of E-commerce applications at WSUThree E-commerce Servers : Three E-commerce Servers Diebold Card Systems CS Gold Cougar CASH Debit Account Dining accounts Residence hall access Vending machines Tuition Housing Many other uses Oracle 9i Database on Windows 2000 Overview of E-commerce applications at WSUSummary of E-commerce Activity at WSU : Summary of E-commerce Activity at WSU 40+ applications Growth rate of 25-50% per year since 1998 Over 155,000 credit card transactions for over 56 million in the last twelve months Over 6800 eCheck transactions for over 4.5 million in the last twelve months Overview of E-commerce applications at WSUPresentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Slide12: Overloaded Wide range of technical expertise Staff turnover and continuity Variety of platforms and languages Very tight budgets Departmental e-commerce applications Departmental IT OrganizationsSlide13: Controls and security Lower costs – greater purchasing power Efficiencies DON’T want many e-commerce solutions Advantages to Using Central IT E-commerce Services Departmental e-commerce applications Presentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications and IT staff Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Slide15: No start-up costs No vendor software required No set-up or configuration fee Currently no fee for new merchant number Priority 1 – Make it CHEAP Cost to DepartmentsSlide16: Low on-going costs Low credit card fees No per-transaction fee Additional savings from reduced staff time No card-swipe monthly rental fee Save staff time with self-service aps Priority 1 – Make it CHEAP Cost to DepartmentsSlide17: Servers and software housed at WSU E-commerce servers and software are centrally funded Credit card software maintenance ~ $3,800 annually E-Check software maintenance ~ $4,800 annually Priority 1 – Make it CHEAP E-Commerce Costs at WSUPresentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications and IT staff Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Slide19: All E-commerce transactions use XML-RPC XML-RPC is a web service XML-RPC is a precursor to SOAP Priority 2 – Make it EASY Accessing WSU E-Commerce ServersSlide20: Simple and easy to use Most implementations are free Available from many different languages and platforms Priority 2 – Make it EASY Characteristics of XML-RPCPartial list of implementations: Partial list of implementations Priority 2 – Make it EASY AOLserver: client/server (Aaron Swartz, et. al.) Apache: client/server (Andrew Bihun) AppleScript: client (Late Night Software) ASP: client/server (David Carter-Tod) Axapta: client/server (Greg Pierce) C/C++: client/server (Eric Kidd/FirstPeer) C: client/server (Epinions) Chicken: client/server (Felix Winkelmann) Cold Fusion: client/server (Rob Blitz) COM: client (EnAppSys) Delphi/Kylix: client/server (Cliff Baeseman) Dylan: client/server (Chris Double) Eiffel: client/server (Glenn Maughan) Erlang: client/server (Joakim Grebeno) Flash: client (Patrick O'Lone) Frontier/Radio UserLand: client/server (UserLand) Guile: client/server (Evan Prodromou) Internet Explorer: client (Olav Junker Kjær) J2ME: client (Kyle Gabhart) Java: client (Josh Lucas) JavaScript: client (Jan-Klaas Kollhof) K: client/server (Christian Langreiter) KDE: client/server (Kurt Granroth) Lingo: client (Stefan Rinner) Lisp: client/server (Daniel Lundin) Microsoft .NET: client/server (Nicholas Christopher) Mozilla: client (Samuel Sieb) Objective C: client/server (Marcus Müller) Perl: client/server (Ken MacLeod) PHP: client/server (Simon Willison) Pike: server (Pitrich Information Technologies) Python: server (Jan-Klaas Kollhof) REALBasic: client (Sam DeVore) Rebol: client/server (Thomas Jensen) Ruby: client/server (Michael Neumann) Scheme: client (Pete Hopkins) Squeak: client (Christian Langreiter) Tcl: client (Vitessa) Tintware: client/server (Michael K Montague) WebObjects: client/server (Hannes Wallnöfer/Jim Roepcke) Zope: client/server (PythonWare/Eric Kidd/UserLand) Slide22: Program passes parameters to the XML-RPC client Program invokes an XML-RPC client and specifies a URL, method name and parameter list The XML-RPC client wraps the parameters in XML Priority 2 – Make it EASY How XML-RPC WorksSlide23: The XML-RPC client sends the parameters to the specified location via HTTP or HTTPS The XML-RPC server unpacks the parameters and passes them to the server program The server program processes the parameters and passes the results back to the XML-RPC client. Priority 2 – Make it EASY How XML-RPC Works (continued)Slide24: <?xml version="1.0"?><methodCall><methodName>authcap</methodName> <params> <param> <value> <struct> <member> <name>merchant</name> <value> <string>WSU_PRESS</string> </value> </member> <member> <name>legacy_account</name> <value> <string>601</string> </value> </member> <member> <name>card_num</name> <value> <string>4234567890123456</string></value></member> How XML-RPC Works (continued) Priority 2 – Make it EASY Parameters are wrapped in XML during transportSlide25: Unix/Apache Windows/IIS Linux/Interchange E-commerce Vendor Software XML-RPC (server) Priority 2 – Make it EASY E-commerce Architecture using XML-RPC Payment Gateway XML-RPC (client) VBScript/ASPSlide26: Web Application E-commerce Server Priority 2 – Make it EASY Web Application to E-commerce Server Data Flow URL and Method Name (Host and Name of e-commerce routine) Amount Primary Id: (Student Id, Customer #, Invoice #) Secondary Id: (Name, Address, Phone) Payment Info (Merch Num, Card num, Bank Acct Num, etc.) Accounting Info (Acct Num, Revenue Source, etc.) Other (Browser IP, Acctg Feed Ind) Response Code Unique Trans Id Data Flow Using XML-RPCXML-RPC Code Example (client): XML-RPC Code Example (client) Priority 2 – Make it EASY '----------------------------------------------------------- ' prepare parameters for the call to the XML-RPC routine '----------------------------------------------------------- set dict=Server.createObject("Scripting.Dictionary") dict("merchant") = "transcript" dict("payment_option") = "425" dict("card_num") = "4234567890123456" dict("exp_date") = "1104" dict("amount") = "10100" dict("primary_id") = "90559799" set paramList(0) = dict '---------------------------------------------------- ' Call xml-rpc server routine '---------------------------------------------------- answer = xmlRPC("https://WSUXXX.it.wsu.edu/xml-rpc/authcap.asp", "authcap", paramList) set return_dict = answer(0) '---Process the returned parameters if return_dict("return_code") = "0" then 'card was successfully charged response.write ("<p> " & return_dict("return_message")) response.write ("<p> Seq. Number is: " & return_dict("cpm_sequence_num")) response.write ("<p> Auth Code: " & return_dict("approval_code")) .Slide28: Applications are de-coupled from the vendor e-commerce software Don’t have to dictate to departments what language/platform they have to use It is simple, available and very easy to use. Its free! Priority 2 – Make it EASY Why we like XML-RPCPresentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications and IT staff Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Slide30: Automated recording of revenue in the accounting system Reduced departmental staff time Provided administration and reporting tool Daily fraud reporting Priority 3 – Make it EFFICIENT Improved Work FlowSlide31: Web Application E-commerce Server Priority 3 – Make it EFFICIENT URL and Method Amount Primary Id: (Student Id, Customer #, Invoice #) Secondary Id: (Name, Address, Phone) Payment Info (Merch Num, Card num, Bank Acct Num, etc.) Accounting Info (Acct Num, Revenue Source, etc.) Other (Browser IP, Acctg Feed Ind) Response Code Unique Trans Id Recording Revenue in Accounting (Automated) Enterprise Server Legacy Accounting System Accounting Info Nightly Batch ProcessSlide32: Enterprise Server Priority 3 – Make it EFFICIENT Recording Revenue in Accounting (Manual) Legacy Accounting System Daily Transactions Complete Cash Deposit Form (requires two signatures) Form data is entered by Controller's Office staffSlide34: No Cash Deposit form No card swipes No dual entry Self-service aps Priority 3 – Make it EFFICIENT Reduced Departmental Staff TimeSlide35: E-commerce Server Priority 3 – Make it EFFICIENT Administration and Reporting Tool WSU Foundation Athletics WSU Press Controller’s Office Downloads by Merchant and Date Range Returns, Miscellaenous charges, Reconciliation, Troubleshooting and Reporting E-commerce Administrative Application Slide36: Emailed each morning to business managers Top 10 occurrences of: Card number Primary Id IP of customer's browser Priority 3 – Make it EFFICIENT Daily Fraud Reporting Credit Card Count Dollar Amount XXXXXXXXXXXX4700 13 7065.5300 XXXXXXXXXXXX5015 11 2051.4600 XXXXXXXXXXXX8200 10 10960.3200 * * * Primary Id Count Dollar Amount 10390885 7 12014.0000 10734898 7 4072.6300 10581476 6 4620.0000 * * * IP Address Count Dollar Amount 64.126.137.9 12 8034.5000 64.126.190.197 9 7954.6800 * * * Presentation Outline: Presentation Outline Overview of e-commerce applications at WSU Departmental e-commerce applications and IT staff Priority 1 – Make it CHEAP Priority 2 – Make it EASY Priority 3 – Make it EFFICIENT (by improving work flow) Conclusion Slide38: Controls and security Lower costs – greater purchasing power Efficiencies Conclusion Advantages of Central IT E-commerce SolutionSlide39: Centrally funded No purchased software required No set-up fees No per-transaction charges Very low discount and interchange fees No charge for merchant numbers Conclusion Make it CHEAPSlide40: E-commerce services use XML-RPC Platform and language of preference Easy to use Simple, intuitive parameters Conclusion Make it EASYSlide41: Revenue posted daily to departmental account(s) Reduced departmental staff time E-commerce Administrative Application Daily fraud reporting Conclusion Make it EFFICIENTSlide42: Conclusion Questions?