PMWeb Rev 02

P a g e | 2

Hill International Confidential 2013

TABLE OF CONTENTS

Table of Contents ........................................................................................................................................................................... 2 Section 1.0 – Introduction ............................................................................................................................................................. 3 Section 2.0 – Phases ....................................................................................................................................................................... 4 Section 3.0 – Commercial Pricing Options ................................................................................................................................ 5

Section 3.1 – Phase I Corporate Initiative .............................................................................................................................. 5 Section 3.2 – Phase II – Project Roll-outs ................................................................................................................................ 6 Section 3.3- Phase III - Enterprise Rollout (includes corporate and 4 regions) ................................................................ 7

Section 4.0 – Project Assumptions and Terms ........................................................................................................................... 8 Section 5.0 – SAP Integration Definition – Phase I ..................................................................................................................... 8 Section 6.0 – User Licensing Description ..................................................................................................................................... 9 Section 7.0 – PMWeb Modules .................................................................................................................................................. 10 Section 8.0 – HILL-PCI Implementation Methodology ........................................................................................................... 15 Appendix ....................................................................................................................................................................................... 24

P a g e | 3


SECTION 1.0 – INTRODUCTION

HILL-PCI appreciates the opportunity to submit this proposal to Skanska LA. Skanska LA is currently seeking a software tool to help with procurement, budget/cost management, forecasting, document management, and collaboration.

PMWeb contains multiple modules all integrated in one application that combine Project Management (Including Document Management and Cost/Budget Management), Scheduling, Estimating, and Workflow. PMWeb also contains advanced reporting and is built upon an easy to use web based platform.

P a g e | 4


SECTION 2.0 – PHASES

The following sections of the proposal are based on our recommendation to effectively role out PMWeb in phases and across several offices based on our initial discussions:

Phase I: Corporate

Goal: Implement and configure PMWeb at the corporate office

Deliverables: Corporate rollout based on configuring PMWeb for Skanska LA internal use and deployment in preparation for a pilot project. It has been discussed that the optimal time would be November 2013

Includes a preliminary integration to SAP for Vendors, Cost Codes, and Job Cost data coming from SAP to PMWeb

Includes train the trainer approach for administration, software configuration, and roll-out

Hosting of PMWeb Software will be in the Skanska LA Data Center

Phase II: Pilot Projects

Goal: Utilize PMWeb across new projects in the four regions as they come online

Deliverables: Includes project configuration, training, report writing, and Go-Live support

Project users fully trained to utilize PMWeb and carry that knowledge transfer to future projects

Phase III: Enterprise

Goal: Enterprise rollout of PMWeb

Deliverables: Training to remaining users not on projects

Additional configuration and enterprise dashboard

Finalize SAP integration

Skanska LA PMWeb Administrators full trained to continue to implement with minimal support

Hill International will be using the implementation methodology in Section 8 which outlines roles, responsibilities, and additional deliverables.

P a g e | 8


SECTION 4.0 – PROJECT ASSUMPTIONS AND TERMS

1. Pricing is valid for 60 days 2. Various Software with full terms and conditions will be sent once quote is approved 3. Software and Year 1 Support and maintenance due upon contract execution 4. Professional services are estimated based on initial discussions and may vary +-10% 5. Travel expenses are billed actual cost for flight, hotel, transportation, and per diem 6. Custom Report writing is budgetary and determined by customers request (T&M) 7. Initial Project/Offices Implementations based internal deployment capabilities assessment

SECTION 5.0 – SAP INTEGRATION DEFINITION – PHASE I

1. Integration for Phase I is strictly limited to Vendor, Cost Code, and Actual Job Cost data transfer and will be performed as a Proof of Concept.

2. Phase II may be billed Time and Material or via specific Scope of Work 3. If the SAP consultant is not proficient, Hill Intl reserves the right to supplement with external consultants

billed at their respective rates.

P a g e | 9


SECTION 6.0 – USER LICENSING DESCRIPTION PMWeb Full and Guest License Description PMWeb Full User License … all-inclusive access to the entire PMWeb Enterprise Platform plus the comprehensive ability to create records and documents throughout (according to the Users security settings set by the system administrator). It is important to note that a Full User License is easily re-assignable if and when necessary by the client. PMWeb Collaborative User License … designed for external collaborators and view only Executives. Guest Users have access to the entire PMWeb Enterprise Platform (according to the Users security settings set by the system administrator and can create records in the system according to the chart below. Collaborative User Can: • Create and Submit Engineering forms • Create and Submit and Online Invoice • Create and submit an Online Bid • Create and Submit a Timesheet • Create and Submit a Tenant Request • View, upload and download documents as part of Workflow participation • Participate in any record in the database if they are included in the workflow For Instance: • Full User can control a Budget while a Guest User cannot • Full User can issue a Contract while a Guest User cannot • Full User can change a Schedule while a Guest User cannot • Full User can create Companies while a Guest User cannot • Full User can create Projects while a Guest User cannot • Full User can define Programs or Lists while a Guest User cannot

P a g e | 10


SECTION 7.0 – PMWEB MODULES

PMWeb consists of 5 main features or modules. Each of the modules are sold separately but are fully integrated with one another. We have identified that the first 3 modules will be used at Skanska LA, and module 4 and 5 may be used at a later time. To show the completeness and tool all 5 modules are summarized, however, the cost proposals are for the first 3 modules. These are the modules:

1. Visual Workflow 2. Project Management (consists of Cost Management and Engineering Forms combined) 3. Scheduling 4. Planning/Estimating 5. Asset Management

The following pages describe each of the main modules as well as the Core Module which is included with the system.

The PMWeb core was built from the ground up using cutting-edge SQL Server and Web technology. Users have the responsiveness and familiarity of a desktop solution coupled with the portability of a 100% Web application.

Modular and Scalable Portfolio, Program and Project Dashboards Business Intelligence Reporting Report Drill-down to Transactions Drag and Drop Security Settings Enterprise-wide Calendar With Public and Private Events Unlimited User-defined Fields Central List of Companies, Departments, Addresses and Contacts The Revolutionary PMWeb Grid Control Customizable User Home Page Multi-currency and Multi-language Multi Browser

P a g e | 11


The advanced tools of the Visual Workflow Platform lie at the heart of PMWeb. Because it was built from the ground up to work directly within each PMWeb record type - including Custom Forms- Visual Workflow gives you the advanced tools you need to design, monitor and manage your collaboration and approval processes, all from a single sign in. Design your own records with Workflow’s Custom Form Builder and use the PMWeb File Manager to upload, manage and archive digital files in a folder structure you create.

Parallel or serial workflow Conditional workflow based on document content Drag and drop interface Unlimited workflow templates Single sign in for users creating and collaborating on records Review-only steps Automated Process Management Rules (such as limits of authority) Route digital files using Workflow Automatic Email Notifications using default or custom templates

Combining the flexibility and ease of use of traditional project cost management with powerful features usually found only in enterprise accounting systems, PMWeb Cost Management is the platform you need to manage costs – from your smallest project to the largest. Highlighting the module are Cost Worksheets: user-definable spreadsheets within PMWeb that display cost information the way you want to see it – and each automatically includes full drilldown capability, all the way to the transaction level. Create system worksheets to share across projects or create project-specific ones as needed. Advanced but easy-to-use budgets, contracts, commitments, invoices, funding and change management add up to the complete package.

User-defined cost worksheets with drill-down to transaction level Funding by portfolio, program and project Itemized forecasting Earned Value – easy to setup and update Multiple methods for creating cash flows Flexible change management process User-defined budget code structure with any number of code levels Enter production records (work completed) against contracts, commitments and companies Import actual costs to requisitions with the click of a button Budget requests let your budgets evolve while retaining transactional history Use journal entries to adjust any cost amounts. Route for approval using Visual Workflow. Copy/Paste from existing Project or Excel lets you create new Budgets with a few clicks.

P a g e | 12


All of the documents you need to manage your projects in a revolutionary Web design. Drag and drop to Daily Reports and Punch Lists; create Rich text Format Correspondence without leaving PMWeb; link multiple records together for quick reference; paste from MS Word without losing formatting; assign documents to users’ calendars; merge to MS Word, Excel…

RFIs Submittals Meeting Minutes Drawing Lists Drawing Sets Daily Reports Punch Lists Transmittals Action items RTF Correspondence (Rich Text Format captured in actual fields and shows in reports)

Planning/Estimating: Answer a few simple questions to quickly create a conceptual estimate; add 100 items to your estimate by dragging and dropping a single folder; build an intricate assembly using advanced formulas and user-defined variables - all of these are possible in PMWeb Estimating.

Familiar spreadsheet grids Export To and From Excel Even Copy and Paste From Excel User-definable Items, Formulas and Assemblies Conceptual Estimating Items list Capital Planning Module included with link to Estimating features Building Information Modeling (BIM) Integration Online Procurement Generate Related Records (budgets, for example) With 1 Click Unlimited User-defined Fields Unlimited Attachments and Rich Text Notes

P a g e | 13


PMWeb offers a complete scheduling solution with critical path management, drag and drop Gantt chart, base-lining and more. Because Scheduling - like all PMWeb modules - is multi-project, features such as Resource Availability and Project Portfolio Management (PPM) views are ready to use out of the box. The Scheduling module also includes Timesheets (multi-project and multi-resource) and Risk Analysis.

Claim analysis – compare schedules across periods and/or across projects Links to Primavera P6 and Microsoft Project included Timesheets that flow to the Cost Management module Risk analysis that links to Portfolio Planning Use Gantt chart interactively to link tasks, enter completed status, flag tasks and more Cash flow & income reports directly from the schedule Use any schedule as a template Base percent complete on timesheets View resource availability across all projects and periods

Create on-demand or recurring Work Orders, link them to Maintenance Contracts and drop them on the interactive Dispatch Board to schedule them. PMWeb Asset Management lets you to track unlimited Inventory Locations, link Inventory to any asset in the system and pull from stock to Work Orders. Use Equipment records to log usage and a detailed Work Order history, be alerted to upcoming scheduled maintenance milestones and link to or nest other pieces of equipment as components or assemblies.

Asset Explorer – interactive tree view of all of your assets Work Requests (from tenants or employees) that can be rolled over as work orders Lease and Space Management View the dispatch board across days, weeks and months Preventive maintenance planning Interactive Google map views of assets and work orders Maintenance contracts Track equipment you own, install or maintain Unlimited inventory locations and sub-locations Track inventory by stock #, lot # and serial #.

P a g e | 14


PMWeb TOOLBOX – Additional Features:

Custom Form Builder – create unlimited custom forms that automatically integrate with PMWeb ‘s workflow, attachments, security, and notes features.

Document Manager - file management with check-in, check-out, versioning and attributes Timesheets – enter all labor for multiple users and across multiple projects on one screen. Integration Manager – tool for automating integration between PMWeb and other systems. Risk Analysis – quantify and mitigate project risks Stage Gates –create custom stages and gates for each phase of your project that integrate throughout

PMWeb. LDAP Integration Active Directory Integration for single sign on purposes

P a g e | 15


SECTION 8.0 – HILL-PCI IMPLEMENTATION METHODOLOGY The PMWeb Implementation Methodology provides our clients with a proven process of successfully deploying software. Our approach provides a standardized method for managing the entire planning, testing and implementation process while building a solid foundation to help ensure a successful deployment and adoption for our clients. We realize there are often several versions of standard practices used within large organizations. Our tools and engagement methodology provide the flexibility and standardization to bring success to an entire organization, at all levels. Our implementation methodology incorporates years of hands-on experience with industry-accepted processes and procedures. Our experience has shown that a successful implementation requires 2 key elements:

1. End User Involvement – We strongly believe in involving end users of the system immediately and often. By doing this they quickly begin to understand how the system works and provide intelligent feedback as to how it can be adjusted to better meet their needs. This requirement is met in a couple of ways:

a. The implementation team is largely made up of client staff and not consultants, because they understand their own needs better than anyone. This also ensures that once the implementation is complete and the consultants leave, the client will have a solid team in place to be able to mold and modify the system as their needs change. (please see the next section on the make-up of the implementation team)

b. Piloting - Super Users will begin using the system on one of their jobs as soon as possible to test and pilot the configuration and ensure that it will be appropriate for the eventual end users.

2. Agility – We have found that it is extremely important for user adoption and satisfaction that the implementation team be able to receive feedback and quickly incorporate that feedback into the system. The best feedback cannot be given until a person is able to actually use an aspect of the system. We achieve this through the “agile” implementation approach outlined in the next section, Implementation Stages.

Project Manager A dedicated team led by an experienced Project Manager is critical to the success of an enterprise implementation. The enforcement of control and monitoring mechanisms that are used to monitor and manage the overall project and sub-projects is important. The Project Manager will also recognize and address potential problems before they negatively impact the project. Proactive Communication Throughout the implementation, our project team will be proactive in communicating with your staff. We will provide status updates to address operational needs and to ensure effective communication between all team members. The Project Manager will report progress since the previous reporting period (typically weekly).The status reports will contain the following information:

ACCOMPLISHMENTS ACTIVITIES IN PROGRESS

OUTSTANDING PROBLEMS OUTSTANDING ISSUES PROJECT STATUS

What was completed in the reporting period, including issues that were resolved

Those activities that are underway at the end of the reporting period

External items that have an effect on the project

Project-related items that are being worked on at the end of the week (i.e., those issues on the issues log that are still “open”)

The status of each task underway or scheduled to be underway at the end of each project reporting period

P a g e | 16


Change Control The PMWeb Project Manager is responsible for ensuring that the project is developed and executed according to the agreed-upon scope, schedule, and budget over the entire life of this project. This responsibility includes preparing status reports that identify decisions that need to be made regarding changes to the scope, schedule and budget. A Change Control process will be used to request enhancements or to report problems for all project development activities. An enhancement request is a request for a new feature or improvement that is not currently in scope. Submittal of enhancement requests or problem reports will be through the change control process. They will be reviewed and prioritized by the project manager. Problem reports will be prioritized and fixed accordingly. The enhancement requests will be provided for a decision on inclusion in the current project or deferral. Implementation Stages

P a g e | 17


Stage 1: Project Initiation Project Initiation begins as soon as the PMWeb software is purchased. The software is installed either on the client’s servers or on PMWeb’s, depending on which option was selected. Initial set up then begins with:

• The import of companies, contacts, and logos • Creation of PMWeb accounts for the Implementation Team • Email setup

A pre-kickoff conference call will also be scheduled between the PMWeb Owner and the Lead Consultant. During this call they will:

• Identify who will be filling implementation team roles • Discuss the vision or key business purposes for purchasing and implementing the software • Review the implementation process • Plan for the Kickoff Meeting

During Project Initiation the PMWeb Owner should be providing report samples and process information to the Lead Consultant so he can begin discovery and preparations for the next stage.

Output

At the end of Project Initiation PMWeb will be installed and set up with the initial general configurations that will allow the team to begin working in the system.

P a g e | 18


Stage 2: Kickoff and Discovery The first time the entire Implementation Team is together is during the kick-off meeting. Everyone on the team should attend the meeting in person as it is used to set expectations for how the implementation will proceed and how the team will work together. This meeting typically is comprised of a main introduction portion and a series of other meetings that span 2-3 days. The primary focus is to:

• Outline the overall needs/requirements of the system • Determine what PMWeb features will be needed and prioritize the release of those features in a

Feature Road Map • Identify milestones and plan releases • Determine how often the implementation team will be able to meet for configuration sessions • Determine length of configuration sprints (typically 2 weeks) • Perform Super user training • Begin configuration sessions

Output

1. Project Charter – The PMWeb-Hill team, with the client’s assistance, will create a Project Charter. We will take conversations from the first demonstrations and use them as a reference point for the overall goals and priorities of the PMWeb Implementation. Any existing documentation created from previous company process documentation is valuable and will be used to expedite this process.

The Project Charter is a document that helps define an organization’s primary goals, objectives and priorities. The Project Charter provides:

• Justification for project undertaking • Identification of business objectives • Delineation of roles and responsibilities • Project Scope and deployment plan • Key stakeholder identities • Project constraints and risks • Direction of the solution • Overall plan of how the solution will be used in the organization • A document that can be updated as an organization’s needs and usage evolves • The Project Charter will help to prioritize the importance of the initiative and serve as a

reference of authority for the execution of the project.

2. Project Schedule – An anticipated Release configuration sprint schedule will be included as part of the Project Charter. This schedule is meant to be a guideline and will be evaluated and adjusted after every Configuration Sprint to ensure the highest priority features are configured first.

P a g e | 19


Stage 3: Configuration Sprints A Configuration Sprint consists of the following elements:

1. Sprint Planning Meeting: (1 hour) at the beginning of a sprint (2 weeks) • Review Feature backlog • Identify high priority items including changes from user feedback that will be configured in the

next Sprint.

2. Configuration Sessions: 1-2 sessions (2 hours) per week • The PMWeb-Hill Consultant shows the way that the out-of-box feature functions • The team discusses the current process or requirement and identifies any gaps that need to be

addressed with configuration • Action items are identified and logged in a PMWeb meeting record • In between configuration sessions the PMWeb-Hill consultants are making configuration changes

and the Super Users and PMWeb Owner are testing and piloting those changes.

3. Sprint Review: (1 hour) at the end of a sprint (2 weeks) • Often combined with the Sprint Planning meeting for the next sprint • The meeting is open to anyone that wants to see the progress of the implementation. • The implementation team demonstrates the features worked on during the sprint with

configurations and feedback from the spring incorporated. • Identify outstanding issues and add them to the feature backlog

Output

The key output for each configuration sprint is a fully functioning and configured feature or set of features in PMWeb. These features could be deployed to the user base, and should be used by the super users in their pilot projects. Where appropriate for the feature these configurations would include:

• Report Modifications or creating new Bi or PMWeb reports • Nomenclature and list changes • Workflow defined and configured • Process and/or training documentation created • Configurations tested by Super Users and PMWeb Owner

P a g e | 20


Stage 4: Release During a release the end users are given access to the features that were configured during the configuration sessions. Releases might not go out to all users at the same time; instead they might be aligned with a certain set of users or projects according to their current needs or construction phase. The reason for this is that it is always best to train users just before they are going to need to use a feature or functionality so it is fresh in their minds when they go to use the system. We like to call this Just-In-Time Training, and we have found it is the most successful way to ensure people get the most out of training and minimizes the amount of re-training required. Once a release is completed the release plan is reviewed and re-prioritized if necessary, and the next release begins with its first Configuration Sprint.

Output

The output for a release is a user base that is trained to use the specific features configured in the release. There are several options for training the users (see the next section), so it will be up to the implementation team to determine what the most appropriate method will be for each set of users and their circumstances. We recommend using the train the trainer approach as much as possible where the Super Users are trained through-out the configuration sprints, and they in turn train their user groups. Depending on the size of the release the implementation team might decide to spend a whole configuration sprint to focus just on training and supporting the users before continuing configurations.

P a g e | 21


Training PMWeb-Hill recognizes that end-user acceptance is one of the most important factors for the success of rolling out a new application. We strive to provide the best and quickest support possible for the end users. This begins with the proper training and support of the client’s team that will be in charge of the management of the application. Our goal is to train your staff so that they can be as self-sufficient as possible. In addition to on-site training and the standard technical support, the PMWeb-Hill team will also have designated consultants that are part of the client’s implementation team available for phone, email and online meetings. There are various ongoing training activities that take place throughout the project lifecycle not just during releases. TRAINING DESCRIPTION

PILOT TEAM / SUPER USER TRAINING

The initial Pilot Team or Super User training begins with an overview and general training during the Kickoff Meeting and then continues throughout all of the configuration sessions. This hands-on training prepares the Core Team for performing their own functional test of the configurations, through piloting them on their own projects, and allows them to provide immediate feedback.

PMWEB ADMINISTRATORS TRAINING

Advanced administrators training prepares the PMWeb Administrator to take ownership of the system configurations and maintenance. It should be set up shortly after the kickoff meeting so he can immediately begin configuring the system with the Lead Consultant during configuration sprints.

END USER TRAINING

End User training begins with an overview and general training during the Release Stage and then continues to the specific set of features that a particular group needs to be trained on for that particular Release.

E-TRAINING

PMWeb-Hill can also create custom e-training courses to reduce initial and long-term training costs. This tool can be used as an introductory course for all users to get a basic understanding of how the system is used by the company. Additional one-on-one and small-group training will still be required, especially for advanced users, but the e-training allows for more productive and streamlined advanced training sessions for all users.

P a g e | 22


Implementation Team

The chart above and the table below describes the make up the implementation team that have yielded the best results in the most effective and successful implementation projects. As was described at the beginning of this implementation methodology it should be evident in the table below that the client has a large part of the execution and should fill several of the key roles.

PMWEB CLIENT

P a g e | 23


Role Responsibilities Capabilities

• Manages Feature Backlog (i.e., implementation priorities)

• Manages the budget • Stake Holder feedback and communication • Tests and accepts configurations • Communication with Leadership • Removes obstacles • Manages and coordinates internal resources • May be helped by a business analyst to gather

feedback and test configurations

• Should be decisive and empowered to make decisions about how the system will be used and configured.

• Needs to have a deep understanding of what the company and users need out of the system.

• Learns how to configure PMWeb • Responsible for managing PMWeb

o Creating new users o Creating new projects o Modifying workflow o Configuration changes o Identifying feature upgrades

• Gathers user feedback and presents it to the PMWeb Owner and Core Team

• Needs to have a good understanding of technology

• For large projects or

programs PMWeb-Hill can provide an onsite PMWeb Administrator to augment the client’s staff if needed

• Become an expert in the software • Typically the first people to use the software • Test configurations and provide feedback • Evangelize/promote the software in the

company • Train other users • Create end user documentation • Gathers user feedback and presents it to the

PMWeb Owner and Core Team

• There should not typically be more than a few Super Users

• Guides the team through the implementation process

• Teaches the core team (Train the Trainer) how to use and configure the system

• Helps PMWeb Owner define and prioritize Feature Backlog

• Leads Configuration sessions • Provides Implementation and Product expertise • Manages and coordinates PMWeb-Hill

resources

• Has a deep understanding of both PMWeb and best practices in the industry

• Create custom reports • Modify existing reports to meet customer needs • Database or Integration customizations

• Is an expert in PMWeb, MS SQL, and MS SQL tools

• Initially this roll will be filled by

PMWeb-Hill, but a client team member can be trained to fulfill these responsibilities.

PMWEB OWNER

PMWEB ADMIN

SUPER USERS

LEAD CONSULTANT

REPORT DEVELOPER

PMWEB CLIENT

P a g e | 24


APPENDIX

System Requirements

Version 4.0 2013

System Requirements Please review the system requirements for your PMWeb application to ensure that the servers and client computers meet the following minimum or recommended requirements, and that the versions for the following applications are already installed and functioning correctly.

PMWeb System Requirements Copyright © 2013 v13.3 Page 2 of 3

PMWeb Server Minimum Hardware # of Users Minimum CPU Minimum RAM Minimum Storage

1-10 Intel® Pentium Dual Core 2.0GHz 4GB or more 40GB



Recommended Hardware # of Users Recommended CPU Recommended RAM *Storage

1-10 Intel® Pentium Quad Core 2.0GHz 4GB or more 80GB



*Additional storage space maybe required depending on individual client needs.

External Web URL • An external Web URL is required to license PMWeb. (IP addresses will not be licensed)

Operating System Software • Microsoft® Windows Server 2008 R2

Database Software • Microsoft® SQL 2008 R2 (Must be installed using the following collation: SQL_Latin1_General_CP1_CI_AS)

Reporting Software • Microsoft® SQL Report Server (Included with SQL)

Internet Information Services (IIS)

• Enable .Net 3.5

• Enable IIS Management Console

• Enable All Application Development Features (.NET Extensibility, ASP, ASP.NET, etc…

Internet Connection One of the following: • DSL/Cable, • Fiber Optic, • T1 / T3

NOTE: Microsoft Internet Explorer is not required as a web browser, but the IE system files must be present in order to install Microsoft Data Access Components (MDAC).

PMWeb System Requirements Copyright © 2013 v13.3 Page 3 of 3

PMWeb Client Minimum Hardware

Minimum CPU Minimum RAM Minimum Storage

Intel® Pentium 4 HT 1.8GHz 512MB or more 40GB

Recommended Hardware Recommended CPU Recommended RAM Storage

Intel® Pentium Dual Core 2.0GHz 2GB or more 80GB

Operating System Software One of the following:

• Microsoft® Windows 7 (All versions) • Microsoft® Vista (All versions) • Microsoft® Windows XP (Professional) SP2

Internet Connection One of the following:

• DSL / Cable • Fiber Optic • T1 / T3

Web Browser One of the following:

• Google Chrome • Firefox • Internet Explorer (IE) • Safari

Optional Software

• Microsoft® Office 2010 • Microsoft® Office 2007 • Microsoft® Office 2003

Display

• 1280x1024, True Color (32-bit) or higher – (Wide-screen resolution is highly recommended) • 1024x768, True Color (32-bit)

Documents

PMWeb Rev 02