Drawing Scale Changed

One day, you may find the pipeline what you put on which was on grid. but is moved over night. There could be Admin. did something, or... something we don't know. Let's talk about the solution: At first, check the other "good" drawing's scale. Go to View--Property--Grid, then write down the scale number. see the attached picture. Then, go to your drawing which all lines moved. match the scale with the good one.

OPC text missing the position

There is an interet thing happy since last week.

the "..." control the directiong of the OPC. after I changed it to left. the text missing position.

Put a new one, same thing happed.

Site Server Permition_SPPID Installation

I finished Whole process of SPPID installation. and it works well. but after I shared my remote computer with my co-workers, I found they can not open the drawings.

After asked the master, I know there is one more step need to do: right click your Site Server. then click the permissions. add your co-worker's name on it. then refresh the role in Engineering Manager. It work!

The logic is clear: your co-worker need permission to access the reference files. Otherwise, they only can connect with server but doing nothing.

How to get remote VM's shared files

There're several method:

1. Access to the VM directly.

Type \\ the name of VM\ driver$. you can directly get into the shared folder. of course, you need to know this computer's user name and password.

2. Map the shared folder to your computer, similiar as above. more convinient for next time.

3. From the VM go to the server, for example: \\ca-cab...., you suppose have your personal folder there. then put the VM file there. After that you can get your files from your personal folder.

How to add your co-worker to your VM

Two point:

1. Add their user name to your VM.

(a) my computer--Manage

(b) groups--users--property

(c) add

(d) check the dormin name first, then enter your co-workers user name.

2. Add their user name to remote

(a) Contro Panel--System--Remote

(b) click select remote users

(c) check domin first, then add user name, then check names

Now, you can tell your co-workers to try.

XenApp more

XenApp, Virtually Everywhere

This post is apart from Smartplant Automation. But is an imortant application used for virtualization of desktop applications. Here I'll discuss about CITRIX XenApp.

Citrix XenApp is an application delivery solution for application managed in the datacenter virtualized and centralised and delivers the service to the user anywhere and on any device.

Let us view the benefits of Citrix XenApp with smartplant tools. We all know that any EPC project has a minimum life of 3 years upto plant is built (please ignore my lack of knowledge if it is done in shorter duration). In this duration Intergraph release many upgrades for their tool (Including service packs or version). The clients demands that every thing should be done on updated versions of Smartplant tools.

Now if the upgrades require in upgrade of OS (MS Window), or (very rare case) Hardware of systems running the application tool, and we have around 50-100 computers to be upgraded, then it will definitely be a friction for project time as well as cost.

Citrix here plays a very good role to limit the cost and time. If the Application (here Smartplant Tool) is running on CITRIX XenApp, you'll just need to upgrade one server. That's it. You can fire the applications just in single upgrade.

And the tool amdinistrators will support such environment. On local installed application, if any thing needs to be changed (suppose new ItemTag.dll in case of SPPID), it will be applied on each system. But for CITRTX server, change it for one machine and it will be available on every machine.

Hope that is enough for you to understand the key benifit of virtualized, centralized application management system.

Have a Happy Life...

inShare

What’s the optimal XenApp 6.5 VM configuration?

In this blog series I’m taking a look at scalability considerations for XenApp 6.5, specifically:

1. How to estimate XenApp 6.5 Hosted Shared Desktop scalability
2. What’s the optimal XenApp 6.5 VM specification?
3. Hosted Shared Desktop sizing example

My last post provided guidance on how to estimate XenApp density based on processor specification and user workload.  In the second post of the series, I’m taking a look at the optimal specification for the XenApp virtual machines themselves.
In an ideal world, every project would include time for scalability testing so that the right number of optimally specified servers can be ordered.  However, there are various reasons why this doesn’t always take place, including time and budgetary constraints.  Architects are all too often asked for their best guess on the resources required.  I’ve been in this situation myself and I know just how stressful it can be.  If you over specify you’re going to cost your company money whilst under specifying reduces the number of users that can be supported, or even worse – impacts performance.
XenApp Server Virtual Machine Processor Specification
In most situations, testing has shown that optimal scalability is obtained when 4 virtual CPUs are assigned to each virtual machine.  When hosting extremely resource intensive applications, such as computer aided design or software development applications, user density can sometimes be improved by assigning 6 or even 8 virtual CPUs to each virtual machine.  However, in these situations consider using XenDesktop rather than XenApp so that you have a granular level of control over the resources that are assigned to each user.
User Density per XenApp Server Virtual Machine:
The user density of each 4vCPU virtual XenApp server will vary according to the workloads that they support and the processor architecture of the virtualization host:

• Dual Socket Host: You should expect approximately 36 light users, 24 normal users or 12 heavy users per XenApp virtual machine.
• Quad Socket Host: You should expect approximately 30 light users, 20 normal users or 10 heavy users per XenApp virtual machine.

Depending on your worker group design, you may have a blend of light, normal and heavy users on each XenApp virtual machines.  In these situations, adjust your density estimates based on the overhead of each workload type (light=1.5, normal = 1, heavy =0.5).  For example:
Dual Socket Host -

• 30% light : (36 / 100%) * 30 = 11
• 60% normal : (24 / 100%) x 60 = 14 users
• 10% heavy : (12 / 100%) * 10 = 1 user

Total number of users per XenApp virtual machine = 26
Number of XenApp Servers per Virtualization Host
When determining the optimal number of virtual XenApp servers per virtualization host, divide the total number of virtual cores by the number of virtual processors assigned to each XenApp virtual machine (typically 4).  For example, a server with 32 virtual cores should host 8 virtual XenApp servers (32 / 4 = 8).  There is no need to remove server cores for the hypervisor because this overhead has been baked into the user density overheads discussed in the first blog.
One of the questions I get asked most is whether the total number of virtual cores includes hyper-threading or not.  First, what is hyper-threading and what does it do?
The Citrix XenDesktop and XenApp Best Practices whitepaper states:

Hyper-threading is a technology developed by Intel that enables a single physical processor to appear as two logical processors. Hyper-threading has the potential to improve the performance of workloads by increasing user density per VM (XenApp only) or VM density per host (XenApp and XenDesktop). For other types of workloads, it is critical to test and compare the performance of workloads with Hyper-threading and without Hyper-threading. In addition, Hyper-threading should be configured in conjunction with the vendor-specific hypervisor tuning recommendations. It is highly recommended to use new generation server hardware and processors (e.g. Nehalem+) and the latest version of the hypervisors to evaluate the benefit of Hyper-threading. The use of hyper-threading will typically provide a performance boost of between 20-30%.

Testing has shown that optimal density is obtained when the total number of virtual cores includes hyper-threading.  For example, a server with 16 physical cores should host 8 XenApp VMs – 32 virtual cores (16 physical cores x 2) / 4 virtual CPUs per XenApp virtual machine = 8 XenApp virtual machines.
A common mistake is to perform scalability testing with one virtual XenApp server and to multiply the results by the number of virtual machines that the host should be able to support.  For example, scalability testing might show that a single XenApp server virtual machine can support 60 concurrent ‘Normal’ users.  Therefore, a 16 physical core server with 8 XenApp server virtual machines should be able to support 480 concurrent users.  This approach always overestimates user density because the number of users per virtual machine decreases with each additional XenApp VM hosted on the virtualization server.  The optimal number of concurrent normal users for a 16 physical core server will be approximately 192 with around 24 users per virtual machine.
Memory Specification
The amount of memory assigned to each virtual machine varies according to the memory requirements of the workload(s) that they support.  As a general rule of thumb, memory requirements should be calculated by multiplying the number of light users by 341MB, normal users by 512MB and heavy users by 1024MB (this number includes operating system overhead). Therefore, each virtual machine hosted on a dual socket host should typically be assigned 12GB of RAM and each virtual machine hosted on a quad socket host should be assigned 10GB of RAM.
The following table shows typical memory specifications for each processor specification:

Don’t forget to allocate memory for the Hypervisor.  With XenServer, this is 752MB by default.
Depending on hardware costs, it may make sense to reduce the number of XenApp server virtual machines per virtualization host.  For example, instead of purchasing a virtualization host with 80 virtual cores and 256GB of memory you could reduce the number of XenApp server virtual machines per host from 20 to 19 so that only 192GB of memory will be necessary (2GB for the hypervisor).  Although this reduces user density by approximately 30 light /20 normal/10 heavy users per host, it also saves 64GB of memory.
Depending on the hardware specification selected, you may find that your hardware specification allows you to assign more than 12GB of memory to each XenApp virtual machine.  It makes sense to use all of the memory available.
Disk Input Output Operations per Second (IOPS)
Regardless of whether local or shared storage is used, the storage subsystem must be capable of supporting the anticipated number of IOPS.  As a general rule of thumb, each light user requires an average of 2 steady state IOPS, each normal user requires an average of 4 steady state IOPS and each heavy user requires an average of 8 steady state IOPS.  Therefore:
Dual Socket Host -

• Light users: 36 users x 2 IOPS = 72 steady state IOPS per XenApp virtual machine
• Normal Users: 24 users x 4 IOPS = 96 steady state IOPS per XenApp virtual machine
• Heavy users: 12 users x 8 IOPS = 96 steady state IOPS per XenApp virtual machine

Quad Socket Host -

• Light users: 30 users x 2 IOPS = 60 steady state IOPS per XenApp virtual machine
• Normal Users: 20 users x 4 IOPS = 80 steady state IOPS per XenApp virtual machine
• Heavy users: 10 users x 8 IOPS = 80 steady state IOPS per XenApp virtual machine

It is hard to estimate the number of IOPS generated per user during logon because the logon rate, logon actions and logon time varies significantly between implementations.  Also, it is not possible to provide estimates based on user workload type because this is unrelated.  Some businesses may experience the majority of their logons between 08:30 and 09:00 while others may have multiple shifts.  Regardless, a hard disk write-cache on local (at least 1GB) and shared storage can be used to help soak up short periods of heavy disk utilization.
I realize that some of these recommendations can be hard to follow for first timers which is why the last post in this series will walk you through an example XenApp sizing exercise.  Stay tuned!
For more information on recommended best practices when virtualizing Citrix XenApp, please refer to CTX129761 – Virtualization Best Practices.
Andy Baker – Architect
Worldwide Consulting Solutions
Twitter: @adwbaker
XenDesktop Design Handbook
Project Accelerator

SPPID_All tools can not open

After double click Drawing Manager, The error message is: DrawingManagerEXE has encountered a problem and needs to close. We are sorry for the incomvenience.

Solution:
1. Go the the personal folder. for example: PeterJohn (M:), then find the file Thinstall. open it. Or click Start--Run--M:\Thinstall to open the folder.
2. Find the folder Intergraph_SPPID_xxxx. (xxxx is the package number.it may be different.), then rename it.
3. Double click Drawing Manager (the whole SPPID package will be recreated.), then you will be able to open it.
4. Connect it with ini file again. It suppose to work well.
Good luck!

SPPID_Cannot get permission after be added into Administrator role

My co-worker helped me figure out a problem recently.

I have a remote VM.

My name has been added into administrator group. and I have run into SPPID Engieer Manager, refreshed the role in every projects. but I still cannot get full authority.

Finally, I refreshed the server, then it works.

By logic: refresh serve is the method to refresh your role. as you added your role in server. That make sense.

SPPID_Can not break the line between two nozzles

In order to put the Heat Tracing segment break in the middle of two nozzles. We need break the line between two nozzles. Most of times, we can break the line easily, but sometimes, we can not. Why?

Here is one reason:

See the end of right nozzle, there is an inconsistency. If you click the right line, then break in the middle of nozzles. It won't work because the inconsistency. It you can not break a line with different information. either you need fix the inconsistency first or click the left line, then break in the middle of nozzle. It will works.

again: if you just put the Heat Tracing break at the middle of two nozzles. you can put the label on it, but it doesn't work. The Administrator may receive complain: the Heat Tracing break doesn't work. actually, the line hasn't yet broken.

SPPID_How to deal with “Dead Lines”

Some reason, the line changed into light brown color, and thicker several time than normal.

And sometimes, it even cannot be deleted.

It is not only bothered the drafters, but also the administrators.

There is a procedure to deal with those “Dead lines”.

1.    At first, move the lines to a Test drawing. By this way, the drafter can continue work on his drawing. And administrator can win enough time to deal with the problem. Just make sure: disconnected the relation between this line with other components.

2.    In the test drawing, delete all the information carrying from that drawing which has trouble.

3.    Normally, there should be couple of runs on this line. Combine all the runs into one run. It won’t work with the combine command, please directly drag the line together.

4.    Save the result, then click the line and delete it.

*As I have deleted the line successfully, so I don’t have the pictures with me know, later I will paste the pictures once I see the problem again.

SPPID_How to change white item into original color

Sometimes, after drawing crushed, some items changed into white color.

For example, the underground symbol was changed into white by some reasons.

Solution:

Click the item, then click construction status in the properties.You can find it is blank. pick up "New", then it will back to the original color. if it is underground item: pick up "New" first, then change back to "underground". it will works.

SPPID_Some components changed into white color

It suppose to be related with the line define when we draw it by Smart Sketch.
Haven't yet confirm.

SPPID_When some component can not be replaced

For example: You want to change a ball valve into gate valve, just click "replace mode". but if you want to ball valve drain into gate valve drain, probably it won't work. At this moment, you may disconnect the pipeline with the drain, then click "replace mode", it will works. it also work when some valves can not be replaced.

SPPID_Flow unit converter tip

Engineer want Capacity: 697 dm3/s (11051 gallon/min)

When we input 697 dm3/s, it shows 11048 gallon/min automatically.
Normally, people will think the unit covert in SPPID is wrong. but if we put 697.2 dm3/s. It will shows 11051 gallon/min exactly.

SPPID_EDE view setting for LDT

At least there're 3 items should be lifted out.
1. do not report.
2. connectors zero length.
3. supply by.

SPPID_How to move one component to another one

Sometimes, we need move one component connect to another one; in another word, reduce the line between these two component into "zero".
The correct way is:
1. make sure everything is on grid.
2. click one component, then click move.
3. when the arrow point is close to another component, the line will shows red, then you can see clearly the connect point. just release your left mouse key, it will automatically connect to the point.
4. check the property, the "connector zero length" will show "True".

SPPID_How to define the line between Control valve and Reducer

There are two lines between control valve and reducer.
In the real construction work, these two lines are not exist. but on P&ID drawings, it need shows.
The problem is: if we define it " do not report false", these lines will showing on LDT; it we define it "do not report true", it will affect LDT from and to. I found the easy way is define the "do not report" blank. when we generate LDT, we only pick up "do not report false".

SPPID_LDT crushed in the middle of work

Sometimes the LDT report crushed in the middle of work.
when we redo another one by same name. It shows us: "that excel sheet is still running. you can not replace it."
We need go to Task Manager. Find "EXCEL.EXE", then click "End Process".

You will be ok to redo another report.

Excel_How to compare two excel sheets (LDT)

Currently, we upload LDT (excel file) to SPPID, then download LDT from SPPID. It save us time to put every data in the property. but we still need check if there're any difference between upload file and download file.
Now, we just need install this small software:
Spreadsheet Compare. http://sourceforge.net/projects/spreadshcompare/
It's 100% free.

After install it, you need open two excel sheets. then click Add-Ins, then click Compare. Very handy.