Loading...
HomeMy WebLinkAbout13 TC Technology Agreement Agenda Item # 13 Public Utility District CONSENT To: Board of Directors From: Ian Fitzgerald Date: June 02, 2010 Subject: Consideration to Approve a Professional Services Agreement with TC Technology 1. WHY THIS MATTER IS BEFORE THE BOARD Agreements for professional services which exceed $15,000 require Board approval. 2. HISTORY TC Technology is a software development company, based in Carlsbad, California. The District has worked with this company in the past to design and develop the GIS mobile software (GO!Sync) which has been used within District Vehicles for the past six years. 3. NEW INFORMATION In late 2009, the California Public Utility Commission (CPUC) visited the District offices to inquire about how the District was tracking, documenting, and handling General Order (G.O.) infractions in a timely manner. During that visit, the CPUC stated that the District was considered to be lacking in some areas of the G.O. requirements; particularly: • Inability to provide documentation of a G.O. lifecycle: Patrol Inspection, Detail Inspection, and Corrective Work • Did not have safeguards in place to ensure G.O. infractions were fixed in a set amount of time, and have documentation to prove this was the case • The District needed to develop a plan to cycle for both Patrol and Detailed Inspections To address these deficiencies and develop the necessary tracking tools, staff went to our existing mobile GIS software provider, TC Technology for a proposal. TC Technology was selected because: • The new tracking tool will require integration and compatibility with existing software products from TC Technology • They own the proprietary source code for the mobile GIS Software and Server Integration Therefore, this is a sole source procurement. Staff reviewed both the scope and price of the proposed work with TC Technology, and as a result concluded that the District would be provided software at much less than actual cost, and would continue to receive upgrades over the years at no additional costs. TC Technology would retain the rights to software ownership that could potentially attract more customers and sales to their products. 4. FISCAL IMPACT The Power Supply department has sufficient funds for this project, in the approved FY10 budget. Total cost is $19,250. 5. RECOMMENDATION Approve agreement with TC Technology for the development of a G.O. Inspection extension software. /"-- h? -- Stephen Hollabaugh Michael D. Holley Assistant General Manager General Manager Workflow Integration Scope GO! Sync Mapbook& ProcessMaker (Colosa, Inc) Integration May14, 2010 vf^ .ii,1C Technology 4 x: F 3 .a * R:,. x a F, Ii Z £ F . � s }t-?C Technology Introduction The aim of this document is to outline the remaining work to complete the development of integration components between GO! Sync Mapbook and ProcessMaker(PM). The work outlined here builds on top of work already performed as part of a proof of concept prototype developed for Truckee Donner Public Utility District(TDPUD) by TC Technology(TCT). Background TCT developed a proof of concept prototype to evaluate the viability of the integration of PM and GO! Sync Mapbook. This prototype had the following technical goals: 1. Usability of the PM interface and work flow management 2. Productivity gains leveraged from PM as a workflow management solution 3. Ease of mashing up ArcGIS Server maps into the PM web interface 4. Ease of extending PIVI's capability via web services, specifically for use in a disconnected environment Out of these four goals, all except for goal number 3 was attempted. The remaining three goals were attempted and deemed acceptable. The proof of concept sufficiently proved integration of PM workflow with GO! Sync Mapbook was feasible. These above mentioned goals were tested using these product and custom components: 1. Product components a. GO! Sync Mapbook(version 9.3.72) b. GO! Sync Mapbook Ticket integration c. GO! Sync Mapbook Ticket Broker 2. Custom components a. Server side Ticket Broker adapter b. PM ticket adapter with custom forms c. PM facility selection tool 3. PM a. PM (version 1.2-2985),WAMP setup b. A sample PM workflow simulating a simplified PUC General Order inspection created by TCT 4. Candidate PM Integration Components a. TCT PM ticket adapter b. TCT PM web service c. TCT PM business objects Subsequent to TDPUD's acceptance of the viability of GO! Sync Mapbook and PM integration, TDPUD created a production worthy workflow in PM. This workflow was demonstrated to TCT. All integration efforts by TCT will from here on out utilize this TDPUD custom workflow. CONFIDENTIAL v�, 'M Technology Proposed Solution Integration Architecture PM facilitates the creation of processes,associated web based user interfaces,and custom workflows. PM navigates a case through a workflow of sequenced tasks.A user is assigned to a case as a case proceeds to the next task in the PM workflow. PM's facilitates extending its capability through a web service. This PM web service will be the GO! Sync integration point. GO! Sync Mapbook is a field solution that assumes an occasionally connected environment. This integration architecture will facilitate: 1. Retrieving cases assigned to field workers from PM to Mapbook,when connected. 2. Completing a task associated with a case in the field using Mapbook in a disconnected environment. 3. Returning these completed task associated with a case to PM for further management, when connected. Essentially Mapbook will be an offline proxy to a PM task for cases assigned to field users. Figure 1 illustrates the proposed building blocks for this GO! Sync Mapbook and PM integration solution. CONFIDENTIAL 2 -;;ETC Technology GO!Sync-field side integration Dynamic form approach to be considered. F$,C# t©M�►17t�g�ar��ratf�r"�' Ct�st, , acesslsk+�rPrjectAdapter {BUsP-0. b SM COn ra6il ify)* i�S,Ar0�'@5 11� ker�k. Adap, Custom form `,Par e�ss+ "attar t v �`@fiSl tt approach to be considered. , k.ix�:.�>.4�...4�: z �._ �<..' ,.�$ .?.xF°�.c��. �;t � .>,�� e .. :£x` '.��',,: .€.r.�..�,�'��•.g"??x:" ��%.. .Via.`?:�xz� .G3...... .� •�.'� �``t .> 4 a 3. L.''�6... as i�x ..�§�i'L' t � ':�:':.' .:�h,:.:.�:f.` R. ,i`rLS:.FY':F:'x q '3�.. ..,'FF�.isz�.•i.$}^. .k✓.:>o::o,T,:.� v..a.. `a:�aa:�,L�•�•,�3.�..z, 4Y:.';`i ri'j `a�.�•� ::b�>�. :�. ''.¢¢. �s���?a::=a.'t�:k.,ii..�g�e`i�" ..�3 .x.�4xLx.:i:S:;: HTTP GO!Sync-server side integration ice{c`:c;E.4 ?2 . F�i•;•`�•'•�sn�3 t:,y` 1 S' ,p yS i eta!'+ a E�� i�•�'� ������� ��: ©f S t�rpc@a�l�lakar Tick e �/ocess � #r ii'li�'+7liliAl 7Fr ,��.� ..:�•.F 4�ir�ks..<.� �£.<e� _���'a�a� as �� t7i.,a�'::�..� � �a�,��£a.°a N �t��@�r+��/�T1.���'ifil�`$ sa g .. \. a. • ' tsus .;.<...,M e�ax a a . �. r:..�,�`..< e x.. �3i .:iM=:'<.£`YYtY;:. u ,.\a\,c.$".. rex�x>3S`:'<F`�{:4>.:.•TY`a'.� •e;z.,y <.�:.'£� a&'e z s� ,x,� F• :, +,�:�. °;.','`�� .:...��g, k,=ki:_�.+��<,.�__,.��;.,;aaa;. .�f��� �<_<�_ ���a.��=..����,�gt:��:`F.i,.:��, °a��Fa �=�.s� �� t��?,�@�'�S fi a., `.., " :£.E 3::°i;•t.:'�aF?�a.�ax.c,.L`E..,zk`:: �� t..... §a e:F:Ez.YI��£`�`�'i:.t„� .4� �3F�. Ua�i3F�,.F.F;«.'i'xx`���:�1..��:�a`u�.�4 a`,x. HTTP SS.Custo Fa��ility 1Neb 1�rterfa+ca* '' �ebC�o� N,�-gyp•. *Candidate Product **Custom project ware Components to be managed by TDPUD ***Reusable prototype components El Components to be build as part of this project °�����°'��' TCT existing Product components Figure 1:Proposed integration architecture. CONFIDENTIAL 3 3TC Technology The proposed GO! Sync Mapbook and PM integration components are extensions to current GO! Sync and PM capabilities. For integration with a custom PM workflow to be successful it is assumed that the custom PM process is fully functional, independent of any Mapbook integration (T1 &T2, in Figure 1). Mapbook will simply provide an optional proxy interface to a subset of tasks, presumably the tasks typically performed in the field. This proxy interface will be an optional interface, in other words,field workers will be able to perform the same field tasks using the PM web interface directly instead of byway of the Mapbook PM interface. PM cases assigned to users of Mapbook will be retrieved by GO! Sync Mapbook's Call Manager (F1)from the GO! Sync Server via the web service interface of the Ticket Broker(S2). The Ticket Broker will depend on the GO! Sync PM Ticket Processor(S3)to retrieve the applicable active cases from PM's web service for the particular field user. The name of the PM user and the Mapbook user needs to match to facilitate this case retrieval. All PM cases that are assigned to the field are wrapped into a TCT Ticket and delivered to the.Mapbook device for consumption by Mapbook's PM Ticket adapter(F3). All field actioned PM cases that are return to PM on the server are on the field device again wrapped into a TCT Ticket and integrated back into PM using the above mentioned components,just in reverse order. It is important to note that the content of a case send to Mapbook is limited to the case's specified variable names and values. At this time, no PM web interface information contained in PM Dynaforms or else ware is available from PM's web service to be shared with Mapbook.The following PM Dynaform meta data are examples of what will not be included in the TCT Ticket e.g.: • Layout information • Read-Only field requirements • Require field requirement • Dropdown candidate value list • Custom form or field JavaScript • Field length requirements • Field database binding via SQL • Edit masks • Field type information • Field case transformation • Default values • Hint messages • Validation rules Additionally,the PM web service interface does not currently expose the list of variable names associated with a case and task. CONFIDENTIAL 4 =='fiC Technology As far as the above mentioned resulting Mapbook ignorance to PM Dynaform meta data and task variable name there are three architectural avenues to overcome this hurdle: 1. Dynamically create forms on the client Create case and associated task input forms dynamically in Mapbook using a configuration file that is maintained on the GO! Sync Server and replicated down to the clients.This configuration file can then contain all or a subset of user interface meta data that is not shared with a TCT Ticket. This option is illustrated in Figure 1 by F8. 2. Create custom forms as static assemblies Custom forms are created in code and compiled into assemblies. These assemblies are then included with the Mapbook assemblies and consumed for use when the applicable case for a given task required editing in Mapbook. See F10 in figure 1. 3. Support both options 1 and 2. Option one would present a more flexible approach at the cost of more development time and less flexibility in terms of the look and feel of the form. In the case of option one,should the PM interface be changed a simple parallel configuration file would be required. Option two would provide the most control over the look and feel of the form at the expense of more rigidness since changes to the PM interface might require parallel updates to the custom control user interface binary. The PM Ticket Adapter(F6)will be responsible for displaying TCT tickets representing PM cases assigned to the current Mapbook user. This component will show these tickets in a list box and allow users to navigate to these tickets on the map as well as expose the user interfaces associated with this ticket. This solution will not only enable a field worker to action an existing PM case in the field, but facilitate the creation of a new case. New cases will typically need to be associated with facilities in the field. Where this is the case it is proposed that a simple PM patrol extension (F7) be leveraged to allow field workers to view all candidate patrol facilities within a configurable range from them and simply select this facility from the list,see the facility highlighted on the map,and invoke the applicable case user interface form to start a new case for that particular facility. This PM patrol extension will leverage two existing Mapbook product components,the Proximity Selector(F4)and the GPS Extension (F5). Subsequent to the integration prototype, map interaction between the PM's web interface and an ArcGIS Server mapping service was explored. The aim is to give office users of PM's web interface a spatial perspective of the facilities in question. It is recommended that as part of the development of the PM interfaces using PM core capability TDPUD adds http links to applicable PM web pages. These links will point to,and when clicked on, launch a custom web application (S5). The link will include URL parameters added to the end of the link. These,to be determined parameter items,will e.g.specify a facility unique identifier value and facility type. The custom web application will, using a mapping service(T3),show this facility on the map along with to be determined attribute information for this selected facility. CONFIDENTIAL p; 5 TC Technology Solution Software dependencies The solution components will be built to leveraging the following COTS software components and versions: • GO! Sync Mobile GIS(version 9.3.72) • PM (version 1.2-2985),WAMP setup • ArcGIS Server(version 9.3.1) Change to COTS solution software or COTS software versions may result in a required upgrade to the solution components. Truckee Donner Specific Workflow While the former sections primarily dealt with integration between PM and GO! Sync,the integration's purpose is to support TDPUD's inspection workflow. This section describes TDPUD's workflow and how this integration solution is to support this workflow. In here an emphasis will be placed on the field portion of the workflow and the integration points between Mapbook. The remaining non-field PM tasks in the existing TDPUD PM customization will assume exclusive responsibility for the office workflow. The overriding TDPUD goal for this project is to meet the patrol and detailed inspection data collection requirements of the California Public Utility Commission's(CPUC)General Order 165's report specifications. This General Order requires patrol,detailed, and intrusive inspections of facilities on a given schedule (see Appendix of the report specifications document). In this TDPUD solution the field based Mapbook interface will support three types of inspection: 4. Patrol Inspections 5. Detailed Inspections 6. Corrective Work Inspection These inspections are progressively more inclusive as far as the data collected.The data collected by Detailed Inspections include the data collected during a Patrol Inspections. The Corrective Work Inspection data collected includes the data collected by a Detailed Inspections and therefore a Patrol Inspection too. This approach is based in TDPUD interpretation that when corrective work is performed on a facility the field worker is also in a position to perform a Detailed Inspection; as well as an even more general Patrol Inspection. Likewise,when a field worker is performing a Detailed Inspection the field worker is also in a position to perform a more general Patrol Inspection. This approach in itself will bring significant efficiencies to the inspection process for TDPUD. In the TDPUD workflow a patrol inspection is initiated from Mapbook in the field (although possible to do so using PM's web interface directly). This patrol inspection is initialed in the following three ways: CONFIDENTIAL 6 rTC Technology 1. Using the PM Patrol Extension—Automated When the Proximity Selection extension is switched on,facilities that are in a given range from Mapbook's field device,will be broadcast to the PM Patrol Extension. When a facility that was in range drops out of range, and no manual inspection was performed against the facility during a server side configurable period of time (e.g. 6 months), an automated inspection is created. This configurable period of time will be a single period that applies to all inspections on all devices for all facility types. This automated inspection flags via an inspection ticket the facility to require no further action (inspection result 1. 'No further action work required'). 2. Using the PM Patrol Extension—Manual When the Proximity Selection extension is switched on,facilities that are in a given range of Mapbook's field device will be broadcast to the PM Patrol Extension. When facilities are within range they are listed in the Proximity Selector's Tab. The user can select an item from this list and invoke a Patrol Inspection,see figure 1 below. This will initiate a form that collects the same information as for the PM form for this task, see Figure 2 below for a view of the PM form. Note the forms appearance in Mapbook can be different and can be very different depending on the elected design decision TDPUD makes as outlined in section 3 in the document. �0.ta7'l5 t464'1 R1 s 14694.14"7 s ,4 14653 '• gg h ..._14539 i Ii i r ' 15435 Jt4390 16034 a 4343 j1432E .. ...._... ....,._.... .... 3 1A'iA s feedbed. . 't Lot meet :vcKthtoehaad vodnie ar, v :. Figure 1:Mapbook's Proximity selector and patrol inspection invoke button CONFIDENTIAL =TC Technology Neat Stele PATROL INSPECTION ................................................... Overhead .................................................... ................................................... COMMENTS Submit For Review Figure 2: The PM Detailed Inspection form. Mapbook form will look different. 3. Patrol inspection facility select-and-inspect tool The final way that a patrol inspection is to be created is by a Mapbook patrol inspection select-and-inspect tool. Using the tool a user selects one or more valid facility from the map and the patrol inspection form is invoked for completion by the field user. If a single facility is selected the corresponding for will be invokes that represents the PM form shown in figure 2.Where multiple feature are selected a ticket is created per selected facility, however a different multi patrol inspection form will be completed where only the common fields can be edited. This for will be a static form and not a form that dynamically conforms to PM form changes. Additionally,when multiple feature are selected all feature need to belong to a single Construction Type. A Patrol Inspection performed on a facility using Mapbook will result in on of the following field recommendations: 1. No further action work required 2. Detailed inspection required a. Immediate attention(within 45 days) b. Future attention (within 6 months) In the case of field recommendation 2.a. and 2.b. an office worker will assign the task of performing a detailed inspection to a field worker. All the above mentioned methods of creating a patrol inspection in Mapbook will result in a patrol inspection ticket being created in the field and, upon network availability, uploaded to the server via the Ticket Broker and integrated into PM via the GO! Sync PM Ticket Processor. All patrol inspection ticket initiate a new PM case,as patrol inspections are exclusively a starting point and not a subsequent task in the TDPUD customized workflow. CONFIDENTIAL 8 }TC Technology A detailed inspection action in the field can be in response to: 1. An existing PM case where TDPUD's customized PM workflow requires a detailed inspection as a next task. 2. The initiation of a new case and associated detailed inspection in the field using Mapbook since TDPUD's customize workflow has detailed inspection configured as a flow starting point. Where a detailed inspection on a facility is required as part of a subsequent PM workflow task for an existing case,the case will be assigned to a field worker by an office worker, a standard PM web interface user. When the field worker next connects to the corporate network this PM case will then be assigned to the field user via the Ticket Broker using a TCT Ticket. The user will then select this ticket in the ticket tab of Mapbook to invoke the detailed inspection form. See figure 3 below shows a view of a sample ticket interface that approximates what the PM Ticket Mapbook interface will look like. me 5jttc�than Y tA M- Wi t wspu<u�osa�e�aesn�a P:' " �n ar5eeefi lrao ` .,.. �. .. / } 123456789 Ys Job-2345670M /Sh lob-987654321 i � k 'E�Ak0 0 H Da et Cieatedt ID 7091234568 N Dispatch 8) 654321987 A 0"tch Time 11/12/2008 7:30 AM tf t Job-789123456 i. P'1`t', c Y- Cr Y E q P A3 y C1 K Lot Street Neighborhood Subdivision i-264eIM7.z97 9t09dbtlEiS Net :Scat 1. 12oe ,y Rewae timturas ti.c meo. ................ Figure 3:Mapbook Ticket Tab user interface Once the user selects a ticket the user will be able to invoke the form associated with this ticket, the detailed inspection form. The current field detailed inspection form for PM is shown in figure 4 below. The Mapbook detailed inspection will collect the same data. Note the form's appearance in Mapbook can be different,and can be very different,depending on the elected design decision TDPUD makes as outlined in section 3 in this document. CONFIDENTIAL _'' g Rif I Technology Next Step PATROL INSPECTION Overhead x DETAILED INSPECTION Site Work Pale :.: Pale Top Enclosure Meter Transformer .. In-Line Equipment ".Wires/Connectors COMMENTS Submit For Review Figure 4:PM web interface detailed inspection form. Mapbook form will look different. Where a detailed inspection is performed against a facility in response to a new case for a facility in the field,the field user will be able to create a detailed inspection in one of two ways: 1. Using the PM Patrol Extension—Manual Much like with patrol inspection,when the Proximity Selection extension is switched on, facilities that are in the range of Mapbook will be broadcast to the PM Patrol Extension. When facilities are within range they are listed in the Proximity Selector's Tab. The user can select an item from this list and invoke a Detailed Inspection,see figure 5 below. This will initiate a form that collects the same information as for the PM form for this task,see figure 4 above for a view of the matching PM web interface form. CONFIDENTIAL w=' 10 C Technology Col Sync1`tMepb Q-e'GMD*t.VAXO.J SSU'XT-wd L( �wlElhtMI1S m. r r €Wf,a r.r `tiJ F ` _•si 'Y�: Sett!nos .,. to t l€E Iif S r' ', r. J-. A -1-4667 r+ t s . i1f _44625 V� r ' P,. CT t f. few i 1 i tl. � 63$ 154' f 1� to ^14390 f 1$Q34r r Active Ho offset 14:' - r `•--.... Show Pacro EE Correct i 1A3 143 !� Deter � m r , 14328 ..... - Feedback ....... .........: ....... ... . ..... ' Last results recebld�Y15_47 PM Lot street NeI ghborhood subdMlsdo€ '-10594Sd72fi 533367.tii7 Metan Sce!1 �lOM ._.._.__.,3 Figure 5:Mopbook's Proximity selector and detailed inspection invoke button 2. Detailed inspection facility select-and-inspect tool In this approach to create a detailed inspection is facilitated by a detailed inspection select-and-inspect tool. Using this tool a user selects one or more valid facility from the map and the detailed inspection form (same for as for#1) is invoked for completion by the field user. Where multiple feature are selected a ticket is created per selected facility, however a different multi detailed inspection form will be completed where only the common fields can be edited. This for will be a static form and not a form that dynamically conforms to PM form changes. Additionally,when multiple feature are selected all feature need to belong to a single Construction Type. If a detailed inspection was perform in response to an existing PM case ticket the updated TCT ticket is return to the server where the PM Ticket Processor returns the ticket to PM's control. If the detailed inspection is in response to a new case,a new TCT Ticket is created on the field device and uploaded to the server. In the latter case the PM Ticket Processor will create a new PM case and integrate the field collected data into the case and pass control of the new case to PM. CONFIDENTIAL 11 ,,. ..TC Technology A corrective work inspection action in the field can be in response to: 1. An existing PM case where TDPUD's customized PM workflow requires a corrective work inspection as a next task. 2. The initiation of a new case and associated corrective work inspection in the field using Mapbook. Where a corrective work inspection on a facility is required as part of a subsequent PM workflow task for an existing case,the case will be assigned to a field worker by an office worker, a standard PM web interface user. When the field worker next connected to the corporate network this PM case will then be assigned to the user via the Ticket Broker using a TCT Ticket. The user will then select this ticket in the ticket tab of Mapbook to invoke the corrective work inspection form. See figure 3 in the Detailed Inspection section above for a view of a sample ticket interface that approximates what the PM Ticket Mapbook interface will look like. Once the user selects a ticket the user will be able to invoke the form associated with this ticket, the corrective work inspection form. The current field corrective work inspection form for PM is shown in Figure 6 below. The Mapbook corrective work inspection will collect the same data. Note the form's appearance in Mapbook can be different, and can be very different,depending on the elected design decision TDPUD makes as outlined in section 3 in this document. tan step PATROL INSPECTION Overhead .............................................. DETAILED DISSECTION CORRECTIVE MURK Site Work Pole ..._. Repair Pole Top Enclosure Meter TransformerCOMMENTS In-tine Equipment Wires 1 Connectors Submit For Review .................................. Figure 6:PM web interface corrective work inspection form. Mapbook form will look different. CONFIDENTIAL 12 r:TC Technology Where a detailed inspection is performed against a facility in response to a new case the field user will be able to create a detailed inspection in one of two ways: 1. Using the PM Patrol Extension—Manual When the Proximity Selection extension is switched on,facilities that are in the range of Mapbook's field device will be broadcast to the PM Patrol Extension. When facility is within range they are listed in the Proximity Selector's Tab. The user can select a single item from this list and invoke a Corrective Work Inspection,see figure 7 below. This will initiate a form that collects the same information as for the PM form for this task,see figure 6 above for a view of the matching PM web interface form. �.COt Sye�::Mnfleeij-eefri5/6�a\Se:sANCtl:S$llS.'mot Mw 14614 14667 Y1 :� 14653 !° i 15430 t 4390 16034 lltive:ryv of[set t 4354 Show Patrol Detall Correct y4$28�ay.1• Fecxlhadc ......... ......... ........ ............................ .......... - ..........-.- .......... Lds[reav#a.etervM:2:x54T Ali Lot Street Neighborltioo�- SI bdivisfon ------------------------------- -x saysa TIfi ax¢aranxx nrx.vs +c.asti i,_.w Figure 7:Mapbook's Proximity selector and corrective work inspection invoke button 2. Corrective Work facility select-and-inspect tool The approach for creating a corrective work inspection is facilitated by a corrective work inspection select-and-inspect tool. Using the tool a user selects a single facility from the map and the corrective work inspection form (same for as for#1) is invoked for completion by the field user. If a corrective work inspection was perform in response to an existing PM case ticket the updated TCT ticket is return to the server where the PM Ticket Processor will return the ticket to PM's control. If the corrective work inspection is in response to a new case,a new TCT Ticket is created on the field device and uploaded to the server. In the latter case the PM Ticket Processor will create a new PM case and integrate the field collected data into the case and pass control of the new case to PM. CONFIDENTIAL 13 3TC Technolner Beyond these discussed PM inspection tasks for the TDPUD PM workflow other tasks exist. These other tasks are exclusively managed using PM and its native web interface. These other tasks are managed by TDPUD office workers. Project Tasks 1.0 Client Dynamic PM form creator Static custom PM multiple item edit forms and tools (x2) PM project adapter PM ticket adapter PM patrol extension (automated and manual) 2.0 Server Components GO! Sync PM ticket processor GO! Sync PM ticket integration service and business object Custom facility web application GO! Sync PM ticket processor—installer Custom facility web application—installer 3.0 Project Support Project Management Testing Deployment Software PM Extension Client Software PM Adapter Server Software :Pricing Description Software (PM Extension and Adapter) No Charge Professional Services(reduced cost,fixed price) $19,250.00 Total $19,2S0.00 Conclusion TC Technology recognizes the contribution TDPUD has made to TCT in designing effective field solutions for utility field workers. TCT believes in the additional productivity and quality of service benefit that automated business process and flow management software, extended all the way into the field,can bring to not only TDPUD, but the utility industry.We look forward to delivering to TDPUD a solution that keeps TDPUD recognized as a leader in its industry. CONFIDENTIAL s` 14