CH2M HILL Polar Services Projects

1. CH2M HILL Polar Services Projects This presentation provides a brief description of the major IT systems developed by the EMS group in support of CH2M HILL Polar Services and the National Science Foundation.

2. REQ & PO System • Used to create requisitions and purchase orders for procuring material and services for the NSF arctic support program. • This system is integrated with the Cargo Tracking System. Purchase orders entered and destined for the field are automatically integrated into the CTS. • Receipt of PO items is acknowledged at the first waypoint in the CTS. • PO items are packaged at the first waypoint, labeled, and sent on to their final destination. • The packages are tracked to their final destination in the CTS. • Secure and confidential.

3. REQ & PO Entry Form

4. Cargo Tracking System • A web-based system used to enter and track cargo from research universities through waypoints to their final destination in the arctic. Also includes retro/return cargo tracking to facilitate returning equipment and samples back to the original research institute at the end of the season. • Authenticated users including researchers and CPS personnel may login to the system to enter their cargo manifest and to create shipments/packages, print shipping labels, and track the location of cargo as it progresses towards its final destination. • Cargo is checked-in at waypoints using the system. • Secure and confidential.

5. CTS Login Screen

6. CTS Create A Package Screen Authenticated users (such as Principal Investigators at university research institutes, or their assistants) may login to the system and create shipments and add packages to their shipment(s). They may use the system to print out shipping labels and package manifests for attachment to their packages. Of special importance is the ability to add “Special Handling Instructions” for any individual package. CPS waypoint receivers take note of any special handling instructions when they review shipments that are coming their way on the Waypoint Receiving screen. Sample Package Manifest: Sample Shipping Label:

7. CTS PO View Screen – PO receiving & packaging Dropdown controls on this form use AJAX autosuggest technology that dynamically filters the list as the user types in the control. May enter partial text in any dropdown and the data will be filtered for all data matching the text entered. Color coding indicates PO received status. Green=100% rec’d, Yellow=partially rec’d White=0% rec’d. Click on PONum – opens PO Receiving Form This screen provides the logged-in CTS administrator the ability to search for POs in the system, check their received status and/or actually receive receive the POs, including partial receipt of POs. PO packages created here are automatically entered into the CTS for tracking to their final destination.

8. CTS Waypoint Receiving Screen • This screen is used to track and receive packages created in the CTS. • Researcher packages have TrackingCode numbers like GT-OlsonK-0042. • GT = Greenland Thule • OlsonK= Researcher username • 0042= serial package number • PO packages have TrackingCode numbers like 367081.05.CGK.42107-pkg02. • (PO Number – serial package number). • The receiver may click on the TrackingCode button for any particular package and discover the package’s contents. • The waypoint receiver will use this screen to receive, return and/or archive packages. • The waypoint receiver may add additional information such as pallet, mission, description or edit the cube dimensions for the packages. • These notes will will help inform the next waypoint what’s coming their way. • The receiver may customize the grid view height, width and page size to that which best suits their needs using the Save Preferences feature. • The waypoint receiver may export the data to excel, markup the spreadsheet with receiving data, and upload the receiving data to this web form. This provides a great simplification for waypoint receiving.

9. Inventory • A web-based system used to track and control inventory for the NSF. • Provides controls to issue, assign, adjust, maintain and audit inventory at locations and/or projects. • Provides controls and reports for capital equipment complete with depreciation schedules and provisions for approved inventory control managers to discontinue items. • Secure and confidential.

10. Inventory Login

11. Inventory Add/Edit Item Form • The “Add” button on the Admin Screen pops-up the Add Item Form wherein items may be added to the Inventory System. • This form includes some very powerful features associated with the controls for ItemName, Category, Mfg, Model#, Size, TagType and Tag#. • These controls use AJAX and autosuggest techniques with typeahead. These controls are sequentially filtered from ItemName through Tag#. • This technique makes it very easy to facilitate the utilization of standardized descriptors and eliminate duplication for data entry. • The form controls are updated dynamically and very rapidly with no postback to the server for page or control updates. • The “Edit” button on the Admin Screen pops-up this form in Edit mode to edit the item selected in the Admin Form Grid. • There is a transaction control at the bottom of this form such that an item may be added or edited and issued to a location or project as physical inventory all in one session, i.e. without leaving this form.

12. Inventory ItemTransaction Screen Five main screen sections (four are collapsible) • Selection Criteria – includes a very powerful search mechanism to search by dropdowns and/or free-text. Location and Category consist of hierarchical data, or data trees. The user may search Location and/or Category hierarchies to include descendents by selection of the checkbox next to these dropdowns. The Location and Category data trees may be viewed by clicking on the button adjacent to these dropdowns. (See next screen for example). • ItemTransaction Table – shows details for ItemTransactions returned by the Filter Selection in a Grid. • ItemTransaction Form View – shows details of selected ItemTransaction in a form view where the user does not need to scroll to see all data. (section shown collapsed in this view). • Transactions – For the item selected in the Grid, the following transactions are available: • Adjustment – [Qty, Recommended Qty, Date and Comment available for this transaction type.] • Assignment – [All eight fields editable as part of this transaction type.] • Inventory Audit – [Qty, Date and Comment] • Maintenance – [All eight fields editable as part of this transaction type except for Recommended Qty.] • Footer – Provides selectors for other user options and information including link to Operator’s Manual (Help link) and Version Notes. As versions are released, the design documents and other notes are provided in the Version Notes document. This augments and extends the Operator’s Manual.

13. (showing Category and Location Treeviews, with data fully expanded in both controls) Inventory ItemTransaction Screen The Category and Location Treeviews show the structure of the hierarchical data. The user may use these controls to select an item and the selected value is transferred to the corresponding dropdown as the selected item. Note: BASC L-114 selected in Location Treeview and was transferred to the Location dropdown.

14. Inventory History Screen • Shows the full transaction history for an item from the initial Issue to physical inventory transaction. • Assignment and Maintenance transactions are shown as debit and credit. • User may select which transaction type to view or view all transactions (as shown here). • Clicking on a row shows the Transaction Comments in the bottom textbox. • Form has three main sections. • Selected Item Details (shown expanded) • Transaction History Grid • Footer (shown collapsed)

15. ARLSS • Developed to build and maintain a database of information for research projects in the arctic sponsored by National Science Foundation. • Developed to disseminate this information to the science community and the general public. • Data is managed using a three-tier system consisting of: • A client application wherein ARLSS editors may enter and edit the data while being disconnected from the central database. • A middle-tier webservice that connects the client application to the backend database. • A database, SQL Server. • The system includes other webservices to share information with arctic GIS systems: • EarthSlot - http://www.earthslot.org/ • ARMAP – have built a gateway website for a GIS system built by the University of Texas El Paso. www.armap.org • Secure and confidential.

16. ARLSS Login • Opening the ARLSS client application: • The ARLSS client application is installed and run on the user’s computer. • The deployment strategy uses a new .NET feature called “Click Once” deployment. • The application is deployed, and the user may install the application from the deployment website. • Each time the user opens the application, and is connected to the web, the deployment website is contacted to see if there is a new version available. • If so, the user is notified and presented the opportunity to download and install the latest version. • LOGIN: • The user must login to the application. • User authorization levels: • Editor – allowed to change data and submit to database. • Viewer – allowed to view data only. • Admin – editor plus administration authorization.

17. ARLSS Grant Form • The ARLSS client application is used by ARLSS editors to edit the ARLSS data using a disconnected dataset, or snap shot of the database at the time that they downloaded the data. • This example shows the Grant Form. This is just one of the many forms available for editing the ARLSS data. • As you can see, there are nine tabs on this form alone for editing data. • Some grids include “Edit” buttons that link the user to another form to edit data (as this example shows for the Season Tab). Clicking on the “Edit” button in this grid allows the user to add field teams and other support information for the particular season record. • There are five forms behind the “Maint” menu button for editing: • Addresses • Locations • Code Maintenance • Discipline Code Maintenance • Program Code Maintenance • Data Maintenance • There is a Person Form behind the “Person” menu button. • The “DBUpdate” button turns red and shows the current number of changes in the user’s dataset as the user changes data. This button leads the user to the DBUpdate Form where the user’s data changes may be submitted to the central database.

18. ARLSS DBUpdate Form • The ARLSS editor uses the DBUpdate Form to submit changes they have made in their local dataset to the database through the webservice. • The user may review the data and any changes on this form prior to submitting the data by selecting the tab for any table of interest. (Currently 18 tables). Note each tab contains three grids showing: • All Data • Data Added or Edited • Data Deleted • To quickly jump to the tab for which the user has added, edited or deleted data, the user may double-click on any table names listed in the “Tables with Changes” textbox. • To send the data changes to the webservice and update the central database, the ARLSS editor clicks the “Update central DB” button. • All data changes are submitted. • Any webservice errors or messages are shown in the “Webservice Messages” textbox. • All changes are accepted in the local dataset and the DBUpdate button turns back to color green. • The user may synchronize his/her dataset using the “Synch” button. This downloads a new snap shot of the database.

19. ARMAP • A public website used as the front-end for GIS interactive mapping applications built by the Systems Ecology Lab at the University of Texas El Paso. • Used to add more information to the GIS application including: • Links to other information. • Map Gallery - downloadable images created from the system • A Text Search page wherein the user may run queries against the ARLSS database and receive an ARLSS report based on his/her custom query. • A contact page • This is a public website. Also includes a Section 508 compliant accessible website.

20. ARMAP Home Page www.armap.org • The ARMAP website is a front-end for interactive mapping applications built by the Systems Ecology Lab at the University of Texas El Paso. • The interactive mapping applications allow users to zoom to areas of interest in the arctic and select layers of information and even save or print maps. • There is a wealth of information that the user may obtain in a very interactive way using these applications. • The ARMAP website provides a launching point for the interactive mapping applications and provides complimentary, additional data. • The ARMAP website also provides an alternative method to query for data using Text Search. Note the “Text Search” link in the site menu. • The interactive mapping application draws data directly from the ARLSS database using the ARLSS webservice. • Both the interactive mapping application and the Text Search page produce ARLSS reports.

21. Report Services • A reporting service integrated with SQL server. Also provides a secure reporting portal wherein report access may be controlled by NT groups to control user access to reports and folders. The portal includes many additional features including user-enabled subscription services that allow the user to request that reports be delivered to the user on a scheduled basis or delivered as the result of some other trigger. • Some of the major reports currently served using Report Services: • NSF Capital Equipment - Inventory • ARLSS Medical Clearance • ARLSS Travel Clearance • PFS - Job Cost Detail • CTS ReqPO Cost Detail • Secure and confidential

22. SQL Server Report Services • Many custom reports are written and provided for CPS management using SQL Server Report Services

23. Issue Manager • A web-based application used to track issues (sometimes referred to as bugs) for all of the software systems that we build and maintain. • System includes categories for all applications, and users may subscribe to any desired application to monitor issues and/or status. • Users may enter text describing an issue, a severity and upload screen-shots regarding the issue. • Users may use the system to request a new feature for an application. • User gets notified as the developer assigned to resolve the issue sends messages and statuses using the system. • The user who submitted the issue may finally close out the issue. • Secure and confidential.

24. Summit Work Order • A web-based application used to track work orders at Summit, Greenland. • This is an adaptation of the Issue Manager system for use as a Work Order system. • Secure and confidential.

25. CPS Planning Extranet • CPS has built and manages and maintains several web-based project extranets for CPS's clients. • CPS Planning Extranet includes: • Three access levels (guest, editor and administrator). • File upload (editors may upload files). • File upload approval mechanism (admin approves or rejects files). • File check-in and check-out. • Notifications as new items are added to the site. • Secure and confidential.

26. CH2M HILL Polar Services websitewww.polar.ch2m.com • A public website developed to provide information about the services provided by CH2M HILL Polar Services for the National Science Foundation and the arctic research community. Also developed as a site for the general interest and edification of the general public.

27. CH2M HILL Polar Services Home Page • Site designed and developed by MicroSource, Inc. in 2002 using VB.NET. • EMS keeps and maintains the source code and performs any site modifications or updates. • The site is designed with a content management system (CMS) and uses an SQL Server database for content storage and management. • PFS personnel are the content managers, and are able to remotely login to the site and edit the content using the CMS.