Expressions of Interest

Transcription

1 Expressions of Interest Technology Solution for Web-based Aboriginal Heritage Information Management System CLOSING TIME AND DATE: 5:30pm AWST, Wednesday 9 December 2015 ISSUED BY: National Trust of Australia (WA) 1

2 Contents Part A. About this EOI Process Background How this EOI process works Late Lodgement Where to get more information How your EO will be assessed... 5 Part B Project Information Background Summary General Functional Requirements Detailed Functional Requirements Operating Environment & Hardware... 7 Solution Architecture... 7 System Training... 8 Hosting and Support Detailed Specification... 8 High Level System... 8 Search and Discovery... 9 Cataloguing Content Content Display Content Download (Zip and Ship) Product Access Levels Data Storage Assessment Criteria

3 Part A. About this EOI Process 1. Background The National Trust of Australia (WA) in collaboration with BHP Billiton, Rio Tinto and Fortescue Metals Group is undertaking an Expression of Interest (EOI) process to assist in the planning, development and implementation of a Web-based Aboriginal Heritage Information Management System, as set out in Part B of this document. 2. How this EOI process works The purpose of the EOI process is to enable the National Trust to establish the level of interest, capacity and costings for the delivery of a Web-based Aboriginal Heritage Information System. Each Respondent must ensure that they provide all their organisation information requested in Part C of this document, along with a detailed response to each Criterion set out in Part B. The relative importance of each Criterion is identified as a percentage weighting. The closing date for submission is 5:30pm Wednesday 9 December EOI can be submitted by Hand to The National Trust of Australia (WA) The Old Observatory 4 Havelock Street WEST PERTH WA 6010 By Post The National Trust of Australia (WA) PO Box 1162 WEST PERTH WA Karl.haynes@ntwa.com.au All hardcopy submissions must be accompanied with an electronic PDF version. Each submission will be acknowledged within 7 days of the Closing Date of the EOI. 3

4 Once the assessment of each submission is completed each Respondent will be notified of the outcome within 8 weeks of the Closing Date. The National Trust may: a) request more detailed submissions from Respondents; b) enter into direct negotiations with a Respondent in relation to its EOI; c) establish a shortlist of potential service providers and invite them to participate in a competitive Request for Tender; d) decide not to proceed any further; or e) do something other than the above. It is important to note that this EOI process is not a Request for Tenders. It is not a commitment or representation of any kind by the National Trust that it will at any time issue a Request for Tenders for the services described in Part B, or that the National Trust will otherwise seek to procure such services. 3. Late Lodgement EOIs that are not received in full by the Closing Date and Time cannot be evaluated by the National Trust. 4. Where to get more information If you have any queries regarding the EOI process please contact: Karl Haynes Manager Heritage Services National Trust of Australia (WA) Tel: karl.haynes@ntwa.com.au If you have any technical queries Daniel Bruckner Manager Heritage & CIS BHP Billiton Tel: daniel.bruckner@bhpbilliton.com 4

5 5. How your EO will be assessed The National Trust will appoint an assessment panel, which will assess each EOI against the Criterion set out in Part B. As part of the assessment process it will be determined to what extent an EOI may deliver value for money to the National Trust. A value for money assessment does not simply consider price. While price is a factor taken into account, all costs, benefits and risks associated with each EOI will be assessed when making a value for money decision. In addition there are a number of State Supply Commission policies that the National Trust will apply to the EOI process, including but not limited to the following. the Value for Money policy; the Probity and Accountability policy; and the Open and Effective Competition policy Copies of these policies are available to view and download from the State Supply Commission website; Part B Project Information 1. Background The past four decades have seen Western Australian resource companies invest millions in compliance driven archaeological heritage surveys, ethnographies and research projects. As a product of these significant bodies of work, vast and valuable repositories that evidence the culture and history of Australia s first occupants have been generated. However, most of this information is locked away within the disparate archives held by respective mining companies. Despite the best interests of the parties, there are often practical limitations around the way in which Aboriginal groups can readily access this information. Additionally, the technical knowledge associated with managing, updating and curating this material and information in a culturally adequate and meaningful way has become increasingly complex. The Heritage Knowledge Repatriation Project is an initiative aimed at ensuring that the relevant Aboriginal people have appropriate and meaningful access to the cultural heritage information held by participating mining companies. It then remains for the rightful custodians to determine how this information can best be managed in order to continue to enrich Aboriginal culture now and for future generations to come. 2. Summary At a high level the scope of this development project is to: 5

6 Deliver the capability for Aboriginal groups to search and locate areas of interest via interactive maps and textual searches and manage associated Heritage information. Deliver the capability for Aboriginal Groups to upload and maintain Heritage information. Deliver the capability for Aboriginal Groups to view Heritage information and metadata via an, intuitive, easy to use online portal. Deliver the capability for Aboriginal Groups to apply and maintain security and access levels to Users of their information. Additional scope components of this project include, but are not limited to: Ability to provide WMS services for use in Geographic Information Systems Fully searchable documents and metadata with error correction Access to all information through analytical tools Open Source Solution or transferrable IP Be OGC compliant Provision and cost details for system hosting Training Bug fix and technology upgrades to ensure currency into the future; and Initial hosting, support activities to run the Heritage Information Management System. The long term requirement will be for the Heritage information to be hosted and maintained within a sustainable framework (i.e. Statutory Body, Museum etc.). Heritage information components of this project include, but are not limited to: Digital Shapefiles Heritage Reports Metadata Multimedia files (i.e., video, photo, sound files, etc.) Transcripts Field Notes 3. General Functional Requirements The high level scope for the Web-based Aboriginal Heritage Information Management System is to: Supply a simple registration and authentication tool for Users to request and subsequently access the System; Provide tools for Indigenous Groups to create and maintain their data; Provide tools for users to discover (browse), view and download information at their user level; Provide tools to search and show search results using an interactive map interface; and Permit users of OGC compliant GIS client to browse Indigenous Data Storage and 6

7 Distribution System WMS within their local systems using analytical tools Ability for Users to link data, manage relationships 4. Detailed Functional Requirements The technology solution for this project has not been determined, however the technology must demonstrate scalability and sustainability with respect to, but not limited to: Extract/Consume from existing systems whilst maintaining data integrity and spatial associations data storage data management Searching technology (both textual and spatial) distribution access and availability User tracking Version control follow industry standards with respect to; o web development o security o database storage Operating Environment & Hardware The ultimate goal is for the Web-based Aboriginal Heritage Information Management System to be hosted within a sustainable and future proof operating environment (e.g. Statutory Body, Museum, etc.). Respondents should document the operating environment requirements for their solution with this in mind. The proposed solution will need to meet industry standards as it may be integrated with existing database and web application infrastructure. Respondents are requested to list the technologies proposed for each component of their solution and any platform dependencies. Solution Architecture The solution should comprise of separate data storage and portal server components and have the ability to expand to additional data stores in the future (scalability). Similarly, it should be possible for the administration of these system components to be carried out by one or many people/organisations remotely. The solution should also provide a level of security so that culturally appropriate access protocols can be established and maintained. 7

8 System Training The solution is expected to be delivered with system documentation, training and Help for the various system components and roles. Training will also be required for system owners such that they will be able to maintain and administer their own User s and data content. Hosting and Support In the initial phase of the project, it may be a requirement for respondents to host the web site and relevant data stores as well as provide ongoing support and maintenance. Costs for these services are required as part of this EOI. Ongoing support, bugfixes and updates are required no matter where the system will be finally hosted. 5. Detailed Specification The following sections lists key functionality that is required in the solution. High Level System The system must have the following high level functionality Role Description a) System Indigenous Data Storage and Distribution System b) System Spatially enable all relevant information c) System Ability to have separate Sites and Logins/Accounts for different Indigenous Groups d) Admin Ability Indigenous Groups to administer their own Site. Add products, remove products and change access levels to products. e) Admin Ability Indigenous Groups to administer to add, remove, edit user login details and track user activities f) User Ability for Users to register for use of a specific Indigenous Group s Site. Registration will require User s to enter basic details (Name, Password, Organisation, ) g) User Provide an interface which supports user driven searching of indigenous content via combination or product names and spatial location/ place names (browse) h) System Textual searching will search all relevant data and metadata i.e Location Names, Metadata, Key words, Excutive Summaries, Document content. i) Admin Ability for a System Administrator to maintain entire system and help Indigenous Groups j) System Ability for User to download content provide the User has the correct privileges to access the content 8

9 Search and Discovery To support the search and discovery of products store within the system, the solution must provide the following Role Description a) User Ability to search for indigenous products by the following means What was the Title of the document Who was the author What year was it captured What state does the product belong Name of the Indigenous Group Name of the Native Title People Type of product o Document o Multimedia Spatially marque an area over a map Combinations of the above Browse perspectives Search interfaces should include list of Product names Document Multimedia b) System Search interfaces should include list of locations State (Western Australia) Regions (Pilbara, Kimberley) Native Title area (WA) Place Names (Perth, Newman) c) Advanced Searching should include the ability to search an entire document for keywords (see cataloguing) d) System The map interface should support zoom in zoom out pan, Go to Place Name i.e. Go To Newman e) System The map interface should support mouse over information f) System The map interface should support toggling of map layers g) System The map interface should have a series of base maps that give context even at large scales i.e. GA 50K Maps sheets h) System The map interface should support connection to existing WMS map as services and be OGC compliant. 9

10 i) System The map interface should support a Marquee Tool for selecting an area to find what Products exists within the area selected J) User Ability for users to link data, manage relationships (eg. Facebook) Cataloguing Content To support the cataloguing of products within the system, the solution must provide the following Role Description a) System Minimum metadata elements including but not limited to Date Author Region Document Type Related Personal Owner Custodian Steward Spatial location (either point or bounding box) b) System Ability to catalogue multiple Product formats Microsoft office Formats PDF Multimedia (AVI, OGG, WMA, MPEG,MP4, WAV,MKV) Spatial Files (Shp, DXF, TAB,) OCR of relevant documents that are not in digital format yet c) System Ability to catalogue as a minimum an Executive Summary for each product d) System Ability for textual based Products to be stored in such a manner that the entire document contents are searchable e) System Ability for each catalogued Product to have a security level so that it can be controlled by each individual Indigenous Group. Security maybe implemented as follows Protected - No details available Read-only Metadata viewable but not downloadable Downloadable Product plus metadata downloadable Shared Available to be found via other Indigenous Groups Site f) System A GOOGLE like experience in Searching 10

11 Content Display To support the display and visualisation of searched Products stored within the system, the solution must provide the following Role Description a) System List the Products found via the search showing key metadata elements such as Product Type Date Author Owner Executive Summary b) System Highlighting the point or area on the map when the found product is selected in the list of results. c) System Ability to extract/download the metadata as an XML file. d) System Ability to extract/download the entire document, provide the product/user access level allows it. Content Download (Zip and Ship) To support the display and visualisation of searched Products stored within the system, the solution must provide the following Role Description a) System Allow the searched Products to be downloaded b) System If multiple Products selected, then system must be able to Zip and Ship them so that users can download them. c) System Only Products with appropriate access levels can be downloaded d) System Enforce a hard limit on the size of the downloadable zip files (i.e. 200MB). This will depend on the infrastructure that the system is hosted. 11

12 Product Access Levels To support the Search and Discovery of Products stored within the system, the solution must provide the following Security Role Description a) User Ability for Indigenous Group administrator to have full control over the Access levels to all Products within their Site. b) Access Levels to define What Products can and cannot be viewed What Products can and cannot be downloaded Which Products can and cannot be manipulated Which Products can be viewed from other Indigenous Sites c) System Cultural access protocols and technical security access protocols Data Storage To support all of the functionality within the system, the solution must provide the following Security a b Role Description Ability to expand the data storage Ability to store ALL products in the most efficient manner d) Follow industry standards with respect to large format storage for both spatial and non-spatial data 12

13 6. Assessment Criteria Summary of Criteria 1. Demonstrated organisational capability and skills and experience to undertake projects of a similar nature, including relevant technical and general experience: a. Provide examples of similar projects undertaken b. Provide CVS of persons who will be assigned to this project detailing education, qualifications, relevant experience and knowledge. 2. Response to Detailed Functional Requirements a. Operating Environment & Hardware b. Solution Architecture High Level System Search and Discovery Cataloguing Content Content Display Content Download Product Access Levels Data Storage c. System Training d. Hosting and Support e. Costing of Proposal 3. Proposed approach, methodology and project plan of the services offered including a demonstrated understanding of the required tasks. Weighting 30% 40% 30% Total 100% 13

14 Part C Organisation Details Respondent Information Name of legal entity: ACN: Trading name: ABN (if applicable): Contact person: Contact person position title: Registered address or address of principal place of business: Telephone number: Other Details Are there any circumstances, arrangements or understandings which constitute, or may reasonably be perceived to constitute an actual or potential conflict of interest with either the Respondent s obligations under this Request for EOI or any potential involvement of the Respondent in the provision of services as described in Part B? (Yes / No) If yes, please provide detail of the actual or potential conflict of interest, and the Respondent s strategy for managing it: 14