Customer/User Job-to-be-Done or Problem

When looking at demand data/job postings, I want to know what occupations job postings represent so I can better understand the labor market conditions in AUZ, NZL and SGP. This understanding needs to be at a tactical level appropriate to my query and precise enough and broad enough to make decisions on.

Additionally the comparison with other Lightcast data through a common standard standard (Lightcast Occupation Taxonomy) is useful when comparing international markets.

NB - This work is separate from the roll-out of LOTv6 on legacy Emsi global postings, and refers to the logacy BG data in these three primary geographies. It is essentially a “like for like” replacement for clients used to using BGTOccs. The LOTv6 launch will include SpecOccs for the first time in these geographies.

Value to Customers & Users

We are introducing the Lightcast Occupation Taxonomy in our main markets and we want to give customers in these geo’s the ability to use the data in the same way.

Customers will be able to understand global labor market demands better through a unified taxonomy that is both very granular (specialized occupation) but also rolls up to useful levels. This will enable strategic, tactical and operational decision making based on (near) real time demand data information.

Order of magnitude the total value of customers switching from legacy systems to go-forward is around $3 million in conjunction with ANZCO and SSOC.

Value to Lightcast

Migrating customers from legacy systems to systems that use the One Index. Required for feature parity Labor Insights <> Analyst/Spotlight.

Order of magnitude the total value of customers switching from legacy systems to go-forward is around $3 million in conjunction with ANZCO and SSOC.

This project fits in with both the Global Growth and Competitive Advantage initiatives.

Target User Role/Client/Client Category

All lightcast job posting end users for API’s and Snowflake. Will enable delivery via front end tools (Spotlight) at a later stage.

Specifically customers accustomed to working with the Lightcast Occupation Taxonomy.

All APAC customers currently on BG cloud wanting to switch over to go-forward products.

Delivery Mechanism

API’s and Snowflake.

Documentation in knowledge base.

Success Criteria & Metrics

Tagging all English global postings in AUS, NZL, and SGP with an Lightcast Occupation classification

Stretch goal of tagging all English documents in non-core geo’s (Example: Philippines, India, etc)

 Scope of PI#4

 Scope of PI#5

Success Criteria & Metrics (multiple PI’s)

Aspects that are out of scope (of this phase)

Out of scope; Front end work, other classifications. BG Cloud

Solution Description

Dependencies

LOT v6 for English (UK?) postings

Legal and Ethical Considerations

Just answer yes or no.

High-Level Rollout Strategies

Roll out on API and Snowflake as initial delivery scope. Additionally will inform Legacy Burning Glass customers in Australia and New Zealand specifically.

After evaluation and feedback, new development and rollout based on specific feedback.

Risks

Bad crosswalk/rules resulting in poor tagging

Open Questions

What are you still looking to resolve?

• Todo: Data quality assurances

• Will the data be ready in time for Micro to deliver their part within the timeline of this PI?

Useful links:
Summary of data needs:
https://economicmodeling.atlassian.net/wiki/spaces/DQ/pages/2674229283

Complete with Engineering Teams

Estimated Costs

Direct Financial Costs

Are there direct costs that this feature entails? Dataset acquisition, server purchasing, software licenses, etc.?

Team Effort

Each team involved should give a general t-shirt size estimate of their work involved. As the epic proceeds, they can add a link to the Jira epic/issue associated with their portion of this work.