Wasting Time? Time is wasted when:- A group of people must wait for one person.- A Team cannot readily access the same document or data.- A Task must be redone due to insufficient supervision.
'Horizontal' Software may be called a Suite - or a Platform. - It is very flexible & made to Create new information.- Can be used to create Vertical (specific) Applications.- An example would be 'Adobe Creative Suite'or MS Office.Vertical Software is developed for a specific set of Tasks.
The Platform is Broad & flexible by Design.- WYSIWYG Design tools for Novices autogenerates code.- Powerful Editors allow Experts to further customize.- Includes an underlying and thoroughly integrated database.- Robust, multiuser access without onerous fees.
Wasting Talent? Talent is wasted when:- An Expert is assigned a task that is suitable for a Novice.- A Novice is assigned a Task that way over his/her head.- A Novice that is eager to learn new skills is denied access.- Team members are pigeonholed. Latent talent, undeveloped.
There is another 'Great Divide' and that is the one between the Haves and the Have Nots. Younicycle is affordably priced for any business, not just the 'Fortunate 500'. Available as a SaaS (online) or as a Server package.
'Vertical' Software is often called an 'Application'. - It is typically developed for a specific set of tasks.- Is 'powered by' the underlying Horizontal Platform.- An example would be 'Recruiting' or 'Benefit Enrollment'.
Wasting Money? Money is wasted when:- Multiple software packages must be purchased.- Multiple licenses or 'seats' must be purchased for each.- Multiple user interfaces must be learned (extra training).
The Great Divide is Knowledge. If you have the required depth of Knowledge, you can accomplish difficult tasks but without it, you will either 'give up', assign or pay an Expert or purchase yet another limited use software application.
Cost? 1) Server package for $400. No limit on number of users.2) Online vsn (SaaS) = $480 per year (3 users).3) Custom programming from $25 to $75 per hour.
Many spokes. Younicycle's framework will allow you to create many types of Vertical Applications, defined only by your imagination. An Actuary - or a Recruiter, a Benefit Consutant or Insurance Carrier can create compelling, plug-in Solutions.
Need an Edge? Many possibilities:1) Create Customer Solutions & give to them for Productivity.2) Create and sell as a suppemental source of revenue.3) Create, give it away - but charge for added customization.4) Become a Partner. Sell Younicycle + your Solutions.
One wheel. We've designed the IT Vehicle so that:1) Experts can work side-by-side with Novices.2) WYSIWYG Tools auto generate complex code.3) Each 'mini-app' you create can be shared (or sold).
Getting there is the hard part ... but we've made the trip much easier. We have spent many years 'blazing a trail' and building the IT vehicle that can get you there, safely & affordably. Yes, it is easier - but Easy is a relative term.
Start here. Get there. It's a given that you want to provide superior service for your customers and always keep a responsible. technological edge. But how? Younicycle can give you that edge - & be white-labeled for your identity.
It's coming. Like it or not, your competitors are standing outside your customers' front door and can be invited in with a few clicks of a mouse. We have the high tech and you, the relationships. Let's talk while the sun is still out.
Personalizing your Employee Communications is critical whenever personal Knowledege is required. Use Retirement as an example. Why would an employee care about John or Jane Doe's retirement security? Meaningless, inaccurate information is not only irrelevant, it's dangerous. Do it right.
The 3 Steps for effective Employee Communications:1) Inform: Let them know it exists. Where? When?2) Educate Employees: What is it? How does it work?3) Personalize the content. John Doe is not real.
Employers: Collaborate internally, with us or other Vendors 1) We (or other Vendors) can provide Full service2) Do it yourself (DIY). You can always ask for help.3) Initial full service -> then DIY in the future.
Your Employee Benefits may be very Cool - but will be ineffective if they remain Hidden. Employee Benefit Statements help your Group understand & appreciate their Personal, Big Picture. We have more than 20 years of experience and know all the possible pitfalls.
Poor Henry. Overcome by events beyond his control.Approximately 3 minutes.
Section 1 For your HRIS (data) person
Start at the Finish?What do you want to deliver?
"Employee benefit statements" is too vague."Employee benefit statements with a1...z33.", is better.
If you know exactly what you want, then it is easy to 'back into' (derive the data items) that need to be collected.
But now, your goals are probably not that precise. That's OK. We'll start General, then refine the list.
Your Employee Benefit Statements Goals will eventually become concrete - the sooner the better.
As your Communication Goals solidify, so will the Employee Benefit Statements Data Requirements.
"Employee benefit statements" is too vague."Employee benefit statements with a1...z33.", is better.
If you know exactly what you want, then it is easy to 'back into' (derive the data items) that need to be collected.
But now, your goals are probably not that precise. That's OK. We'll start General, then refine the list.
Your Employee Benefit Statements Goals will eventually become concrete - the sooner the better.
As your Communication Goals solidify, so will the Employee Benefit Statements Data Requirements.
Census (General)employee _iddivisiondeptlocationemployee _lastemployee _firststreet_address_1street_address_2citystatezipemployee _pay_typeemployee _pay_freqpay_period_hoursemployee _statusemployee birth_dateorig_hire_dateseniority_date
1) Multiple Tables (or xls) are fine2) CSV, Tab Separated, Pipe, User defined or xls. 3) Required - EOL (end of line) between employee or data rows/records. 4) Required - Column headers (names) for each employee or benefit table.5) Required- Descriptive def for each Column header.6) Helpful - Benefit CODES Tables with column descriptors7) Helpful - Detail on any Known Column or employee constraints8) Helpful - Relations diagram (hand drawn is fine)9) Required - SSN employee 'file' = {SSN, name, EE_ID, EEaddress}. SSN (9 char) should only appear in this file. ENCRYPT his file.10) Do not - Send EBCDIC. Convert to ASCII.11) Do - place all files in 1 folder, then zip, encrypt.
12) Do - request email receipt.13) Avoid- Reports lacking employee & benefit keysExample:
EE_ID would have been helpful as it would likely be the linking key field to the census_table.
ee_id ben code eeded freq1234 med 028 33.42 26 den 003 7.15 26 vsn 002 1.86 26 life 044 0.00 26
Example12345petrolwidgetsnorthHEMMAHENRY123 ANYWHERE LN.APT # 99ROCHESTERNY14611S2680FT11/12/19517/9/198811/1/1988
Benefits (General)employee _idemployee _lastemployee _firstbenefit _typebenefit _descbenefit type_codebenefit _type_descemployee _dedemployee _ded_freq
Example12345HEMMAHENRY01MEDICAL11SINGLE54.2226
Here's how it worksSince you probably do not know the precise, End Result for your employee benefit statements, we'll start with the 'basics' and build as we go.
You may know you are going to "Benefit Statements Land" but do not know the exact 'Street Address'.
Don't give your HRIS folks lengthy directions until you know your destination.
Here's how it should work:1) Your HRIS person gathers 'sample data' which we'll use to set up a sample database. This will also 'test' the very basics under Section 1.2) We receive your Content Source Documents & review, comparing these written documents to your Sample Tables and data. This usually uncovers questions.3) We also use your requested Styling & Images along with your Content Source Docs to begin writing the initial 'Copy' and combining to begin creating a Sample Template. This Template will be the preliminary design for your Project's output. Meanwhile, we are working on a Sample Template.4) We complete the Sample Template, you review and pick at it until it is Complete.
This is your top priority as it will dictate the eventual, 'Employee Benefit Statements Precise data list'.
You may know you are going to "Benefit Statements Land" but do not know the exact 'Street Address'.
Don't give your HRIS folks lengthy directions until you know your destination.
Here's how it should work:1) Your HRIS person gathers 'sample data' which we'll use to set up a sample database. This will also 'test' the very basics under Section 1.2) We receive your Content Source Documents & review, comparing these written documents to your Sample Tables and data. This usually uncovers questions.3) We also use your requested Styling & Images along with your Content Source Docs to begin writing the initial 'Copy' and combining to begin creating a Sample Template. This Template will be the preliminary design for your Project's output. Meanwhile, we are working on a Sample Template.4) We complete the Sample Template, you review and pick at it until it is Complete.
This is your top priority as it will dictate the eventual, 'Employee Benefit Statements Precise data list'.
Section 2 -Data & the Workflow of a Project
Section 1- For HRIS PersonSection 2- Benefit statements Data & the Workflow of a Project
We take data for employee benefit statements in its "Best - Current available form". This makes life much easier for your HRIS Specialist or IT Team member.
Employee Benefit Statements Data Requirements
?
Most Vendors for Employee Benefit Statements insist on 'Flat File". It is unlikely that your HRIS stores employee data in Flat File Tables as it is 'bad design'. It is usually much easier for you to give us employee files (Tables) as they are on your system. We create the Joins, which should reduce your time, increase the overall flexibility & 'reuseability' of the employee benefit statements Project. If we begin the employee benefit statements project thoughtfully, you'll be able to rapidly create targeted employee communications at any time in the future.
Comp (General)employee _idemployee _pay_ratewhateverwhateverwhatever
Example123452000############
Table 1 Employee Census (+ or -) depends on the Project & your System
Table 2 Comp (+ or -)
Table 3 Benefits (+ or -)Initially Optional-Later Mandatory
Example below shows 'Starter Tables' for Employee Benefit Statements - Precise data requirements depend on the Project and your Future Plans
Next: Employee Benefit Statements Access
