Ontario Skills Passport
Layout structure
Header structure
Display Noc
OSP Occupational Profile

OSP Occupational Profile

Print Occupational Profile

Display page browsing back option list
Display page browsing back option list <<Back
Display Noc Details
NOC Code: NOC Code: 2171 Occupation: Information systems analysts and consultants
Occupation Description: Occupation Description:
Information systems analysts and consultants analyze systems requirements, develop and implement information systems development plans, policies and procedures, and provide advice on a wide range of information systems issues. They are employed in information technology consulting firms and in information technology units throughout the private and public sectors, or they may be self-employed. Information systems analysts and consultants analyze systems requirements, develop and implement information systems development plans, policies and procedures, and provide advice on a wide range of information systems issues. They are employed in information technology consulting firms and in information technology units throughout the private and public sectors, or they may be self-employed.

  • Click on any of the Essential Skills to view sample workplace tasks for this occupation.
  • Scroll down the page to get information on career planning, education and training, and employment and volunteer opportunities.

Table will display the Skill Level for the Noc specified
Essential Skills Essential Skills Levels
Reading Reading 1 2 3 4
Writing Writing 1 2 3 4
Document Use Document Use 1 2 3 4
Digital Technology Digital Technology 1 2 3 4 5
Oral Communication Oral Communication 1 2 3 4
Money Math Money Math 1 2
Scheduling or Budgeting and Accounting Scheduling or Budgeting and Accounting 1 2 3
Data Analysis Data Analysis 1
Numerical Estimation Numerical Estimation 1 2 3
Job Task Planning and Organizing Job Task Planning and Organizing 1 2 3
Decision Making Decision Making 1 2 3
Problem Solving Problem Solving 1 2 3
Finding Information Finding Information 1 2 3
Critical Thinking Critical Thinking 1 2 3 4

  • The skill levels represented in the above chart illustrate the full range of sample tasks performed by experienced workers and not individuals preparing for or entering this occupation for the first time.
  • Note that some occupational profiles do not include all Numeracy and Thinking Essential Skills.

If you would like to print a copy of the chart and sample tasks, click on the "Print Occupational Profile" button at the top of the page.

  • Read comments, suggestions and responses to frequently asked questions posted on Internet 'listservs' and forums. For example, read about new ways to test database platforms. (2)
  • Read messages about ongoing work from co-workers, colleagues and clients. (2)
  • Read about new products in marketing materials such as brochures, pamphlets and product information sheets. For example, learn about ad hoc query and reporting analysis tools that can publish information from data warehouses. (2)
  • Read about new technologies and their applications in professional journals, industry magazines and periodicals. For example, read articles that discuss the arrival of radically restructured database architectures. (3)
  • Read about database applications, application platforms, computer languages and hardware in reference and technical manuals. A strong understanding of information systems technology is required to understand and apply technical information in these lengthy and complex manuals. (4)
  • Read about information systems development projects and requirements in documents such as requests for proposals, business plans and reports. Read these documents for detailed information on a broad range of topics such as technical specifications, project deliverables, timelines and financial constraints. (4)
Back to Top

  • Record items discussed with clients using short notes and log entries. For example, note that clients understand that toolsets such as Oracle Designer are used to model, create and test their database applications. (1)
  • Write memos and email to clients, co-workers and vendors to provide them with work updates and to request information. (2)
  • Write concise statements in defect escalation reports to describe the severity and frequency of application problems. (2)
  • Write policies and procedures to document database application development processes. Policies may be lengthy and are written using clear and concise language to avoid misinterpretation on the part of readers. (3)
  • Write reports describing database audit reviews. Include detailed information about the purpose of the audit, research approaches, constraints and findings. (4)
  • Write database implementation plans to document the requirements, approaches and potential problem areas prior to commencing projects. Enter information under headings such as technical specifications, project objectives, planned activities and deliverables. (4)
  • Write lengthy proposals that include technical specifications, benefits, methodologies and costing. Clearly and concisely present highly technical information in a manner that laypeople can understand and apply. (4)
Back to Top

Document Use
  • Scan tables to locate technical specifications and data such as passwords, dates, names and product identifiers. (1)
  • Record project activities such as dates, times and actions taken in log books. For example, record the length of time that systems are down in log books. (1)
  • Review defect escalation forms written by co-workers and clients to identify the types and severity of database application problems. (2)
  • Review Gantt charts to determine project schedules, resources being allocated and upcoming activities. (2)
  • Review and interpret integrity relationship diagrams to determine key database elements such as entities, attributes, relationships and indexes. (3)
  • Interpret process flow charts to understand what data is captured and how it travels between various applications and hardware components. (4)
  • Interpret lengthy passages of computer language code to determine how an application's functionality such as logical branching or object orientation is achieved. (4)
Back to Top

Digital Technology
  • Use email programs like Outlook and Communicator to send and receive email, and attachments such as spreadsheets, reports and diagrams. (2)
  • Use the Internet to access vendor and client websites, contact members of access list serves, forums and remotely access databases. (2)
  • Use computer and software applications. For example, use advanced features in project management applications such as Project to organize task lists, schedule activities, balance workloads and create Gantt charts. (3)
  • Use spreadsheets such as Excel and Quatro Pro to test data integrity and to create budgets that incorporate formulas and macros. (3)
  • Use word processing. For example, use advanced features such as pagination, footnotes and track changes to create and edit reports and proposals. (3)
  • Use graphics software. For example, use advanced features in diagramming programs such as Visio to create schematics that outline how data flows between applications. (3)
  • Use databases. Conceptualize, design and create data management systems such as database-centric Internet applications, enterprise reporting tools, ad-hoc query and analysis tools, online transaction processing systems and programs which manage the full life-cycle of data and metadata. (5)
  • Do programming and systems software and design. For example, use a variety of computer languages such as JavaScript, VB Script, CodeBase and Visual Basic. For example, write software routines to optimize performance between clients and servers or, in some cases, reduce network traffic and lock contention by executing queries directly on servers. (5)
Back to Top

Oral Communication
  • Discuss task lists, schedules and work loads with co-workers and colleagues. (2)
  • Meet clients to discuss topics such as project activities, technical specifications, current business practices, growth plans, regulatory and reporting requirements and security risks. Use clear and succinct language to reduce the chance of misunderstandings. (3)
  • Meet clients to secure new contracts. Discuss your skill sets, project experiences and the benefits that clients will realize. (3)
  • Negotiate project fee schedules, timelines and deliverables. Outline preferred terms and conditions and negotiate concessions as required. (3)
  • Make presentations to clients. For example, present the results of data security audits by providing background information, research findings and the resulting recommendations using language appropriate to the audience's technical backgrounds. (4)
Back to Top

Money Math
  • Pay for supplies using cash or credit cards. (1)
  • Check calculations on supplier invoices and approve payments. Confirm quantities, prices and amounts, check tax calculations and verify totals before paying invoices. (2)
  • Prepare invoices and collect payments for consulting services. Charge for the number of billable hours worked or for milestones reached, and calculate HST amounts. (2)
Back to Top

Scheduling or Budgeting and Accounting
  • Schedule work and determine the amount of time it will take to complete projects. Organize task lists, plan around vacations and holidays and balance workloads to determine the time it will take to complete projects. (3)
Back to Top

Data Analysis
  • Compare application load times to norms to determine if computers and operating systems are running efficiently. (1)
Back to Top

Numerical Estimation
  • Estimate the number of users who will access applications using an analysis of items such as number of points of access and size of user populations. (2)
  • Estimate the amount of time it will take to transfer data from legacy systems to new applications. Consider the type and amount of data and the attributes of both the old and new systems. (2)
  • Estimate the resources needed to install new database platforms such as Linux. Consider the costs associated with similar projects, expected installation times, the availability of skilled labour and other variables. (3)
Back to Top

Job Task Planning and Organizing
  • Information systems analysts and consultants organize their daily activities to meet project deadlines. They generally work on multi-disciplinary teams and may be involved on one or more projects simultaneously. Juggling projects is a necessary part of the work and they frequently have to decide which projects to work on next. They must be prepared to shift priorities if important project delivery deadlines are threatened. (3)
Back to Top

Decision Making
  • Decide what labels to assign to fields and tables. (1)
  • Select programming languages to execute commands. For example, choose JavaScript to create password protection scripts which require users to enter passwords before accessing information. (2)
  • Choose tests to assess the performance of new software applications and platforms such as Oracle 9i, IBM DB2, Microsoft SQL Server and Sybase Adaptive Server Enterprise. For example, use manual or automated tests to ensure that relational databases are performing as expected. (2)
  • Decide to bid on projects. Consider the deliverables, timelines, fee schedules and levels of expertise required. (2)
  • Decide which applications and database platforms will best meet client needs. Factor in the number of users expected, budgets, scalability requirements and the need for web-based technologies such as Java, HTTP, Web Services and XML. (2)
  • Decide how to migrate data from legacy systems to database applications such as DB2 and Sybase by considering data structures, storage requirements and the functionality of new software programs. (3)
  • Decide the priority levels of concurrent projects. Consider how delays will affect each project and how to use available resources to satisfy at least some of the clients. (3)
Back to Top

Problem Solving
  • Deal with clients who lack the technical background needed to understand commonly-used acronyms and information technology jargon. Determine the extent of clients' technical understanding and use more appropriate language. (2)
  • Discover that database applications are not capable of meeting all the technical specifications requested by clients. Consult with clients to discuss the limitations and determine options such as which of the lower priority functions could be abandoned. (3)
  • Clients change specifications after projects have started. Determine the extent of the changes and renegotiate timelines and budgets. (3)
  • Determine that projects will not finish on time due to delays caused by work stoppages, late arriving shipments and technical glitches. Work with suppliers, clients and co-workers to resolve the delays and then establish new timelines. (3)
Back to Top

Finding Information
  • Locate technical specifications, timelines and budgets by referring to proposals, reports and business plans. (1)
  • Seek information about system and software malfunctions from co-workers, colleagues and suppliers. (2)
  • Consult technical manuals to locate specific information such as program codes and executable commands. (3)
Back to Top

Critical Thinking
  • Evaluate the acceptability of software performance. Compare the results of manual and automated tests to technical specifications published by suppliers. Verify specifications such as throughput rates, load times, functionality and connectivity. (2)
  • Evaluate the ability of legacy databases to meet increased data processing and information sharing demands. Consider system architectures, data processing speeds, defect escalation reports and reporting capabilities. (3)
  • Evaluate the adequacy of existing database security measures. Review the security risks presented by current business practices and the protection offered by existing security measures such as the use of passwords, firewalls and virus filters. (3)
  • Assess the suitability of database platforms and software applications such as enterprise reporting tools and online transaction processing systems. Consider client needs and resources, and the costs, technical supports and specifications provided by suppliers. (4)
Back to Top