- Minimise Costs
- Avoid full scale implementation
- Reduce risk and resources
- Tailor requirements
Proof of Concept workshops are Aspen Basic Engineering (ABE) projects that involve configuration of ABE and an onsite workshop to discuss the results. The ABE project can be configured in one of two ways. A custom project utilises customer specific documentation and functionality where as a pilot is a fixed project utilising out of the box documentation and IPPD enhanced functionality.
Both types of project are used to demonstrate and test the feasibility of Aspentechs ABE software to see if customer needs can be met without the expense of a full implementation. Proof of Concept workshops are the preferred method to trial ABE software as it reduces risk.
In our experience most customers opt for the custom project to ensure their specific documentaton and functionality is configurable in a software like ABE. However, for a few customers they want to see an enhanced out of the box configuration without the requirement to share specific documentation or technologies at an early stage of feasibility.
Proof of Concept requirements is a list of tasks that are required to be configured in ABE to test the feasibility of the software according to the customer needs. These tasks vary from customer to customer dependent on the nature of the customers business.
For most customers, the use of their own deliverables (PFD Legend, Datasheets, Equipment Lists, Customer / Client Logos, Calculation sheets etc) within ABE is expected as a minimum. These deliverables can be configured into an ABE library to test the feasibility for project use.
Generally, in a Proof of Concept workshop, the customer will request a test case to be simulated in the ABE environment. This test case is typically a subset of a front end engineering design (FEED) package that has already been completed. The test case may include one or all of the following
- Transfer basis of design data to equipment datasheets
- Import of simulation data
- Reproduce 1 or 2 PFDs and Heat Material Balance / Equipment Table / Units Legend
- Populate PFD major equipment with simulation data
- Display simulation data on out of the box datasheets
- Configure 2 customer datasheets and/or equipment lists
- Import / Export equipment data from calculation program for one equipment
- Testing customer data with data in ABE
It is the customers expectations that the chosen design can be achieved in ABE. A number of factors will determine the success criteria, this varies for each customer.
A typical scope for a Proof of Concept will vary from customer to customer, but as a minimum we recommend the following to highlight some key features of the ABE software...
- 1-2 PFDs (electronic format of dwgs and symbols, in AutoCAD or Microstation)
- 2-3 Equipment datasheets, i.e. Pump, Vessel, Shell & Tube Exchanger
- 2 Simulations each representing a different process case for the diagram above (AspenPlus, Aspen Hysys, ProII)
- 1 calculation sheet, maybe Pump or Vessel
- Sample Equipment naming - optional
- Sample equipment breakdown (Plant Breakdown Structure) - optional
- Onsite workshop to convey results - optional
For customers who are concerned about intellectual property and want avoid using company specific data, a fixed pilot project which highlights some of the key features of the ABE software may be preferred. These key features and a more detailed explanation of the Proof of Concept workshop is available from the download section. To discuss pilot projects and the options available please contact us.