<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hi all: I contacted some folks with the GeoConnections
program in NR Canada about their process. Here’s the 10 cent tour from
Brian McLeod, CGDI Standards and Architecture Coordinator with GeoConnections :<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText>“<i><span style='font-family:"Cambria","serif"'>As
Tom mentions, we went thru a two stage process to assess and procure the
potential technologies for use in the Canadian Geospatial Data Infrastructure.<o:p></o:p></span></i></p>
<p class=MsoPlainText><i><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></i></p>
<p class=MsoPlainText><i><span style='font-family:"Cambria","serif"'>The first
stage was an Request for Information on geoportals in general. Anyone was free
to respond, and we received several responses to specific criteria that we put
in the RFI (fairly broad). We used the OGC Geospatial Portal reference
architecture (<a href="http://www.opengeospatial.org/standards/dp">http://www.opengeospatial.org/standards/dp</a>)
as one of the background documents for the RFI.<o:p></o:p></span></i></p>
<p class=MsoPlainText><i><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></i></p>
<p class=MsoPlainText><i><span style='font-family:"Cambria","serif"'>All who
responded to the RFI were invited to give presentations and demonstrations on
whatever geoportal technologies they were supporting. <o:p></o:p></span></i></p>
<p class=MsoPlainText><i><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></i></p>
<p class=MsoPlainText><i><span style='font-family:"Cambria","serif"'>Following
the RFI, a process was done to create an RFP that combined some of the
technical knowledge obtained from the RFI with user/business requirements from
our stakeholders. After this an RFP was released and Compusult was the
successful bidder. <o:p></o:p></span></i></p>
<p class=MsoPlainText><i><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></i></p>
<p class=MsoPlainText><i><span style='font-family:"Cambria","serif"'>Our procurement
was only for technology, however we did build in a number of operational
requirements (like performance metrics) that the technology was to support.
Government staff are the operators of the geoportal, and provide end-user
support. A number of our requirements related to configurability of the
geoportal so we would not be reliant on the contractor if we required changes
modifications to the user interface, controlled vocabularies, and other
components of the application. Note that the RFP did not prescribe a COTS or
Open Source solution, as either would have been acceptable. <o:p></o:p></span></i></p>
<p class=MsoPlainText><i><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></i></p>
<p class=MsoNormal><i><span style='font-family:"Cambria","serif"'>I agree with
your concern that implementation costs/resources are typically underestimated,
or not properly accounted for in geoportal technology procurement. In Canada,
mostly thru the GeoConnections program that supports our national spatial data
infrastructure we have seen evidence of several major geoportal projects that
rise and fall due to the inability of the receptor organization to sustain and
maintain the technology and associated user/business processes required to
operate the technology. I don't have anything specific that could be shared,
but feel free to contact me if you want to discuss this issue further.</span></i><span
style='font-family:"Cambria","serif"'>”<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-family:"Cambria","serif"'><o:p> </o:p></span></p>
<p class=MsoNormal>A formal RFI process might not be a bad idea in this case.
It sounds kinda what folks have been going though in an informal manner to
date. I’ve asked Brian if we could see the RFI and RFP solicitation
documents. I figure those would be good validation documents at the very least.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Steve<o:p></o:p></p>
</div>
</body>
</html>