17 January, 2013


Third generation Amazon Kindle, showing text f...
Third generation Amazon Kindle, showing text from the novel Moby-Dick. Esperanto: Amazon Kindle de la tria generacio, montranta originan tekston el la romano Moby-Dick. (Photo credit: Wikipedia)

For sometime now, I have been downloading e-books from one site that has continued to supply the materials on a regular basis. So if you are hunting for an e-book source, here it is:


I am just sharing the link, and I leave you to check and verify its legitimacy.

Till then!
Enhanced by Zemanta

11 January, 2013

AutoCR Sections: The Parts That Make the Whole

English: Change Management's Proposal flow Ita...
English: Change Management's Proposal flow Italiano: Change Management,flusso delle fase di proposta della RFC (Photo credit: Wikipedia)

I am gathering all my wits to put this article up, as it means a total recall for me. I mean, from this moment forward, I would have to do my best to bring to mind the struggle and the pain, the obstacles and difficulties that I faced, and how I searched and sifted through the web articles that I found, tried and tested, and finally, to get a working model, fully functional, complete to the last letter of the specifications, and with some extra thrown in at that!

To begin with, let me list down the sections needed for the Automated Change Request System:
  • Home/Default page
  • Change Request Form for Manufacturing Device
  • Change Request Form for Starting Material
  • Page for Viewing CRs in Progress
  • Page for Viewing Closed CRs
  • Page for Viewing Closed CR Details


The Home/Default Page

The home or default page, is where any user, especially new, can get to know what this automated change management system is all about. This page also enumerates those data fields that are opened up for self-management by those data owners, like Qual engineers, Customer Service personnel, Product Engineers, etc., etc.

A simple process flow for the AutoCR is also included, so the user knows how the process works.

Our hotline, to be called if there is any issue or query, is put in as well. Now I say this is a must!

And finally, a note at the bottom of the list of updatable items points out the fact that anything not in the list will go through the normal change management – this is where we have our say to accept or reject.

That’s all for now. I will keep my posts short and (quickly) readable.

Till then!


Next: The Form for updating Manufacturing Device data
Enhanced by Zemanta

02 January, 2013

The Automated Change Request System

English: Clean room of a semiconductor manufac...
English: Clean room of a semiconductor manufacturing (Photo credit: Wikipedia)

Automated Change Request System: brief description

In my work, we handle the creation of Mfg Devices where the process flow is defined, along with all the other relevant customer data. The data set is critical as this is broadcasted and linked up into all the other subsystems, and one small mistake will stop the flow of data. Such is the criticality of data flow in semiconductor manufacturing (as in all other industries and professions).

Anyway, critical as they are, a large percentage of these are controlled and managed by the respective owners of the data, like process engineering looking after the processes, customer service handle the customer data, etc., etc.

Thus said, if a change is needed, our team, while we are the guardian of the manufacturing execution system, has no say or can’t be questioning why they do what they do. And so the passing of hands to make a change (add, edit, or delete) is simply a non-value-added step in the change management process. And since it is done manually, there is a waiting time introduced, especially on heavy-load days. And if that is not enough, a computerized system with manual intervention is still prone to error, with each manual job an entry point for mistakes (even with a simple copy-and-paste method). How much more manual typing and eyeballing?

Lastly, the very limitation of the manual process is that we work from 8am to 5pm, 5 days a week. We usually don’t get a peaceful weekend, as what they always say, if there is anything that is urgent and we would get called just to do something which doesn’t need our brain power and intellect, but simply to login, type some chars, press a button, and it’s done!

So after many years of going through the motion, we thought, and thought, and thought, and the automated change request system was conceived.
Enhanced by Zemanta

My Automated Change Request Web Apps


The last weeks of December, 2012 was very encouraging. I stopped posting articles on my blogs somewhere in the middle of the year as I was too tied up with my small projects, and while many did not materialize due to resource issues, the very critical ones did come through.

And that was not without the many searches I did in the web, and the many articles I’ve come across with, and the very thorough filtering of what is needed, until finally - the fully operational, fully functional, working to the last letter of the specification – the intranet web apps was deployed.

And starting here, I will detail out the sections, and the web pages that I referenced for the parts and pieces required that made up the whole.

This is my project: Automated Change Request System.
Enhanced by Zemanta