Merged threads on ASCO code confusion
May 21st 2010, 12:04 pm
#92
Just Joined
Joined: Jan 2010
Posts: 17
Re: ASCO 2231-79
This is entirely my opinion so don't take it as gospel, but I don't think we'll be screwed, it's just a case of waiting to see where it fits in the new codes. Something that was on the MODL before as a highly regarded specialisation has to fit in somewhere.
May 21st 2010, 12:47 pm
#93
Forum Regular
Joined: Jul 2009
Posts: 157
Re: ASCO 2231-79
Maybe ACS will understand the difference, but that may be asking too much.
May 21st 2010, 1:48 pm
#94
Forum Regular
Joined: Dec 2009
Location: New Jersey
Posts: 113
Re: ASCO 2231-79
Hi guys, I tend to feel the skills of many of us, such as .Net, Java, data warehousing - anything which involves programming- coding (not administration\support) can be projected as the software engineer\programmer codes which are in the SOL. It entirely depends on how we project our roles to DIAC. I am into datawarehousing, the development part, so I do not see any reason why I should not project myself as a software engineer. This is my opnion -
261112 Systems analyst
261311 Analyst programmer
261312 Developer programmer
261313 Software engineer
All the above seem to look for people who do programming, regardless of the technology...
261112 Systems analyst
261311 Analyst programmer
261312 Developer programmer
261313 Software engineer
All the above seem to look for people who do programming, regardless of the technology...
All Java/J2EE/.Net people should project themselves as Analyst Programmer or Software Engineer. If you are involve in Designing stuff and have worked as Team Lead then apply as Software Engineer but if you are working as part of a team and doing just development then apply as Analyst Programmer.
Just my opinion.
Hi,
I'm about to receive my ACS letter and a bit in the same situation. I expect to be given the code 2231-79 (Datawarehousing Specialist).
I'm thinking of asking a review to be reassessed as systems analyst. I'm involved in Data Warehousing development projects and my role involves data modelling, architecture design, definition of specifications, supervision of developments and project management.
It's just that I'm specialized in the field of Data Warehousing and Business Intelligence, all my experience is in this speciality only.
I'm about to receive my ACS letter and a bit in the same situation. I expect to be given the code 2231-79 (Datawarehousing Specialist).
I'm thinking of asking a review to be reassessed as systems analyst. I'm involved in Data Warehousing development projects and my role involves data modelling, architecture design, definition of specifications, supervision of developments and project management.
It's just that I'm specialized in the field of Data Warehousing and Business Intelligence, all my experience is in this speciality only.
Just my opinion.
May 21st 2010, 2:14 pm
#95
Forum Regular
Joined: Jan 2010
Posts: 120
Re: ASCO 2231-79
I think to class a .NET developer as a Web Developer is short sighted in todays age.
I myself develop for both online and offline applications using .NET. With cloud based computing and data sharing, the line between traditional installed applications and web applications is virtually non-existant. We try and develop our applications to run through a browser so we can deliver cross-platform compatability and this is this future.
I saw somebody post that .NET developer = Web Developer which isn't on the new SOL. I'm hoping that the people at ACS see beyond this and consider the relevance and importance of how applications/software is developed via browsers/internet and .NET developers aren't just 'web developers'
I myself develop for both online and offline applications using .NET. With cloud based computing and data sharing, the line between traditional installed applications and web applications is virtually non-existant. We try and develop our applications to run through a browser so we can deliver cross-platform compatability and this is this future.
I saw somebody post that .NET developer = Web Developer which isn't on the new SOL. I'm hoping that the people at ACS see beyond this and consider the relevance and importance of how applications/software is developed via browsers/internet and .NET developers aren't just 'web developers'
May 21st 2010, 2:16 pm
#96
Forum Regular
Joined: Dec 2009
Location: New Jersey
Posts: 113
Re: ASCO 2231-79
I think to class a .NET developer as a Web Developer is short sighted in todays age.
I myself develop for both online and offline applications using .NET. With cloud based computing and data sharing, the line between traditional installed applications and web applications is virtually non-existant. We try and develop our applications to run through a browser so we can deliver cross-platform compatability and this is this future.
I saw somebody post that .NET developer = Web Developer which isn't on the new SOL. I'm hoping that the people at ACS see beyond this and consider the relevance and importance of how applications/software is developed via browsers/internet and .NET developers aren't just 'web developers'
I myself develop for both online and offline applications using .NET. With cloud based computing and data sharing, the line between traditional installed applications and web applications is virtually non-existant. We try and develop our applications to run through a browser so we can deliver cross-platform compatability and this is this future.
I saw somebody post that .NET developer = Web Developer which isn't on the new SOL. I'm hoping that the people at ACS see beyond this and consider the relevance and importance of how applications/software is developed via browsers/internet and .NET developers aren't just 'web developers'
May 21st 2010, 2:48 pm
#97
Forum Regular
Joined: Jul 2009
Posts: 157
Re: ASCO 2231-79
would it surprise you of it was a case of someone not seeing the all important "dot" in [dot]Net and ignorant of the .Net technology as a product was simply thinking that net = web so implicity "net developer" = "web developer"?
May 21st 2010, 3:24 pm
#98
Forum Regular
Joined: Mar 2010
Posts: 31
Re: ASCO 2231-79
It's a bit of a mess with these new ANZSCO codes.
After having a look on the ANZSCO web site, it's true that I could also go for Software Engineer instead of Systems Analyst. I'm really confused now, things were much simpler when codes were based on specializations rather than roles.
After having a look on the ANZSCO web site, it's true that I could also go for Software Engineer instead of Systems Analyst. I'm really confused now, things were much simpler when codes were based on specializations rather than roles.
May 21st 2010, 4:09 pm
#99
Forum Regular
Joined: Dec 2009
Location: New Jersey
Posts: 113
Re: ASCO 2231-79
It's a bit of a mess with these new ANZSCO codes.
After having a look on the ANZSCO web site, it's true that I could also go for Software Engineer instead of Systems Analyst. I'm really confused now, things were much simpler when codes were based on specializations rather than roles.
After having a look on the ANZSCO web site, it's true that I could also go for Software Engineer instead of Systems Analyst. I'm really confused now, things were much simpler when codes were based on specializations rather than roles.
May 21st 2010, 4:45 pm
#100
Forum Regular
Joined: Mar 2010
Posts: 31
Re: ASCO 2231-79
The problem is that given the previous SOL, many applicants like me have already built their CVs and experience letters to reflect a particular specialization in order to get a positive assessment from ACS.
Now, with the new SOL, we have to be reassessed again and I wonder how ACS will handle these reviews. If I had known, I would certainly have remained more generic in my letters / CV and not insisted on the Data Warehousing speciality (although in this field, I do have experience with multiple technologies). Will we be required to submit new experience letters etc? I really don't know how our cases will be reviewed by ACS (i mean those who have a positive assessment in ASCO and who want a switch to ANZSCO).
Now, with the new SOL, we have to be reassessed again and I wonder how ACS will handle these reviews. If I had known, I would certainly have remained more generic in my letters / CV and not insisted on the Data Warehousing speciality (although in this field, I do have experience with multiple technologies). Will we be required to submit new experience letters etc? I really don't know how our cases will be reviewed by ACS (i mean those who have a positive assessment in ASCO and who want a switch to ANZSCO).
I think its much simpler now. You don't need to worry about the assessment when you have experience in multiple technologies. It is more generic now and you have freedom to build your case as per your roles and responsibilities more easily for assessment rather worrying about putting technology keywords in your resume/cv and experience letters.
May 21st 2010, 4:51 pm
#101
BE Enthusiast
Thread Starter
Joined: Feb 2009
Location: Lahore
Posts: 307
May 21st 2010, 5:16 pm
#102
Forum Regular
Joined: Mar 2010
Posts: 31
Re: ASCO 2231-79
I'm not trying to speculate on anything, by reassessment I meant a review.
I'm pretty sure a review will be required by ACS because I asked the question to my ACS CO and she said, to quote her exact words:
Applicants who hold, or are about to hold, an assessment outcome letter with an ASCO code issued by the ACS prior to 1 July 2010, will be advised on the assessment outcome review process in due course.
When I asked more details, the answer I got was:
You will be notified in due course. Please keep an eye on the ACS website.
These answers seem pretty logical to me, a direct mapping between ASCO and ANZSCO for IT occupations is simply not possible although some people here persist to believe that a conversion table will allow them to use their existing letters which are in ASCO.
Imagine someone has a positve assessment with ASCO 2231-79 specializing in a particular technology. You can't know by a simple mapping if on new SOL, that person is a programmer, a systems analyst or software designer because the codes are now role-based while they were technology-based before in the case of those 2231-79 codes. I believe that ACS will have to look at cases individually and then grant a new ANZSCO code if they believe that the person is on new SOL.
Concerning the details of the review process, we have to wait for more info from ACS, I just hope we won't be asked to pay again for that.
I'm pretty sure a review will be required by ACS because I asked the question to my ACS CO and she said, to quote her exact words:
Applicants who hold, or are about to hold, an assessment outcome letter with an ASCO code issued by the ACS prior to 1 July 2010, will be advised on the assessment outcome review process in due course.
When I asked more details, the answer I got was:
You will be notified in due course. Please keep an eye on the ACS website.
These answers seem pretty logical to me, a direct mapping between ASCO and ANZSCO for IT occupations is simply not possible although some people here persist to believe that a conversion table will allow them to use their existing letters which are in ASCO.
Imagine someone has a positve assessment with ASCO 2231-79 specializing in a particular technology. You can't know by a simple mapping if on new SOL, that person is a programmer, a systems analyst or software designer because the codes are now role-based while they were technology-based before in the case of those 2231-79 codes. I believe that ACS will have to look at cases individually and then grant a new ANZSCO code if they believe that the person is on new SOL.
Concerning the details of the review process, we have to wait for more info from ACS, I just hope we won't be asked to pay again for that.
May 21st 2010, 6:21 pm
#103
Forum Regular
Joined: Mar 2010
Posts: 247
Re: ASCO 2231-79
I'm not trying to speculate on anything, by reassessment I meant a review.
I'm pretty sure a review will be required by ACS because I asked the question to my ACS CO and she said, to quote her exact words:
Applicants who hold, or are about to hold, an assessment outcome letter with an ASCO code issued by the ACS prior to 1 July 2010, will be advised on the assessment outcome review process in due course.
When I asked more details, the answer I got was:
You will be notified in due course. Please keep an eye on the ACS website.
These answers seem pretty logical to me, a direct mapping between ASCO and ANZSCO for IT occupations is simply not possible although some people here persist to believe that a conversion table will allow them to use their existing letters which are in ASCO.
Imagine someone has a positve assessment with ASCO 2231-79 specializing in a particular technology. You can't know by a simple mapping if on new SOL, that person is a programmer, a systems analyst or software designer because the codes are now role-based while they were technology-based before in the case of those 2231-79 codes. I believe that ACS will have to look at cases individually and then grant a new ANZSCO code if they believe that the person is on new SOL.
Concerning the details of the review process, we have to wait for more info from ACS, I just hope we won't be asked to pay again for that.
I'm pretty sure a review will be required by ACS because I asked the question to my ACS CO and she said, to quote her exact words:
Applicants who hold, or are about to hold, an assessment outcome letter with an ASCO code issued by the ACS prior to 1 July 2010, will be advised on the assessment outcome review process in due course.
When I asked more details, the answer I got was:
You will be notified in due course. Please keep an eye on the ACS website.
These answers seem pretty logical to me, a direct mapping between ASCO and ANZSCO for IT occupations is simply not possible although some people here persist to believe that a conversion table will allow them to use their existing letters which are in ASCO.
Imagine someone has a positve assessment with ASCO 2231-79 specializing in a particular technology. You can't know by a simple mapping if on new SOL, that person is a programmer, a systems analyst or software designer because the codes are now role-based while they were technology-based before in the case of those 2231-79 codes. I believe that ACS will have to look at cases individually and then grant a new ANZSCO code if they believe that the person is on new SOL.
Concerning the details of the review process, we have to wait for more info from ACS, I just hope we won't be asked to pay again for that.
May 21st 2010, 6:27 pm
#104
Forum Regular
Joined: Dec 2009
Location: New Jersey
Posts: 113
Re: ASCO 2231-79
The problem is that given the previous SOL, many applicants like me have already built their CVs and experience letters to reflect a particular specialization in order to get a positive assessment from ACS.
Now, with the new SOL, we have to be reassessed again and I wonder how ACS will handle these reviews. If I had known, I would certainly have remained more generic in my letters / CV and not insisted on the Data Warehousing speciality (although in this field, I do have experience with multiple technologies). Will we be required to submit new experience letters etc? I really don't know how our cases will be reviewed by ACS (i mean those who have a positive assessment in ASCO and who want a switch to ANZSCO).
Now, with the new SOL, we have to be reassessed again and I wonder how ACS will handle these reviews. If I had known, I would certainly have remained more generic in my letters / CV and not insisted on the Data Warehousing speciality (although in this field, I do have experience with multiple technologies). Will we be required to submit new experience letters etc? I really don't know how our cases will be reviewed by ACS (i mean those who have a positive assessment in ASCO and who want a switch to ANZSCO).
For the individuals like you who already have done their assessments, If ACS go for re-assessment/reviews, you are not going to have any trouble to become Software Engineer or Analyst Programmer. What I am trying to say is, a person who is working as .Net/J2EE/Data Warehousing specialist IS ALSO A ANALYST PROGRAMMER/SOFTWARE ENGINEER by default. Without having these roles you cannot be a specialist. Having said that, with the same evidences you have provided to ACS, they can put you in Analyst Programmer/Software Engineer category without any trouble. Assessors in ACS are not non-computing people (like they are in USA with immigration dept). They understand the difference between technology and roles that's why they are running an skill assessment organization. They know What is Computer Science?, What is Software Engineering? and What is Project Management? period.
I believe DIAC has modified the SOL with having ACS suggestions/proposals in their minds.
All above is my own opinion.
May 22nd 2010, 10:06 am
#105
Forum Regular
Joined: May 2010
Posts: 62
Re: ASCO 2231-79
Hi all,
This is the LETTER I GOT AS A REPLY FROM ACS WHEN I RAISED THE QUERY "Equaivalent ANZSCO Code for the ASCO code 2231-79 (SAP SPECIALIST)?"
Hope it's of some help
- Buvan
Dear applicants,
It is intended that the new SOL would apply to all new GSM applications made from the date of implementation, except where transitional arrangements are likely to be provided for. Subject to the approval of the Governor-General in Council of amendments to the Migration Regulations 1994, it is intended that a new SOL would come into effect from 1 July 2010, along with the transitional provisions.
Subject to the approval of the Governor-General in Council of the proposed legislative amendments, it is intended that a number of transitional arrangements would be introduced to minimise the impact of this change on international students.
Further information is available on the DIAC's website at: http://www.immi.gov.au/skilled/gener.../whats-new.htm
Up to and including 30 June 2010, assessment outcome letters will be issued in ASCO codes only
From and including 1 July 2010, assessment outcome letters will be issued in ANZSCO codes only
Applicants who hold, or are about to hold, an assessment outcome letter with an ASCO code issued by the ACS prior to 1 July 2010, will be advised on the assessment outcome review process in due course.
For more details about our process, please visit http://www.acs.org.au/index.cfm?acti...killassessment <http://www.acs.org.au/skills>
Regards,
Skills Assessment Support Officer
[email protected]
This is the LETTER I GOT AS A REPLY FROM ACS WHEN I RAISED THE QUERY "Equaivalent ANZSCO Code for the ASCO code 2231-79 (SAP SPECIALIST)?"
Hope it's of some help
- BuvanDear applicants,
It is intended that the new SOL would apply to all new GSM applications made from the date of implementation, except where transitional arrangements are likely to be provided for. Subject to the approval of the Governor-General in Council of amendments to the Migration Regulations 1994, it is intended that a new SOL would come into effect from 1 July 2010, along with the transitional provisions.
Subject to the approval of the Governor-General in Council of the proposed legislative amendments, it is intended that a number of transitional arrangements would be introduced to minimise the impact of this change on international students.
Further information is available on the DIAC's website at: http://www.immi.gov.au/skilled/gener.../whats-new.htm
Up to and including 30 June 2010, assessment outcome letters will be issued in ASCO codes only
From and including 1 July 2010, assessment outcome letters will be issued in ANZSCO codes only
Applicants who hold, or are about to hold, an assessment outcome letter with an ASCO code issued by the ACS prior to 1 July 2010, will be advised on the assessment outcome review process in due course.
For more details about our process, please visit http://www.acs.org.au/index.cfm?acti...killassessment <http://www.acs.org.au/skills>
Regards,
Skills Assessment Support Officer
[email protected]