*Data Modeler* *Client: Horizon Blue Cross Blue Shield*
*Duration: 1 year+* *Location: Newark, NJ (PA, NJ, DE, NY, VA, DC ONLY)* *Need candidates from above locations only and they must be able to do F2F in Newark, NJ* *Summary: *A data modeler builds data models that describe data and its relationships in a consistent way to support business and technical objectives. *Qualifications: Qualifications* *Education/Experience* - Requires Bachelor's degree from an accredited college or university, preferably in Computer Science, Information Systems, or related field. - 10+ Years of experience in Data Modeling (Conceptual, Logical and Physical). Must be able to design and explain using entities, attributes, hierarchies, inheritance, relationships and their associated meta data. Must be familiar with master data concepts such as Party, Product, Location, Agreement as well as patterns such as Data Vault - 5+ Years of Healthcare experience (Preferably at an Insurance Carrier) -3+ Years of experience in designing XML Schemas and functional mapping specifications for enterprise data services - 3 years of experience with data modeling. Usually data modelers will have focused on modeling for transactional or analytic systems, which require distinct approaches. - Experience in transactional and operational, analytical, and MDM modeling techniques. - Experience with Data Governance processes Additional Licensing, Certifications, Registrations Knowledge - Knowledge of database management system (DBMS) physical implementation, including tables, joins and views. - Understanding of dimensional modeling, snowflakes, slowly changing *Responsibilities: *1.Understand, define and structure how data relates to business operations and capabilities through an enterprise data model. 2.Analyze business requirements and functional specifications as a guide to data modeling. 3.Choose a suitable data modeling approach for each project, such as by assessing the suitability of existing data models. 4.Build data models with the flexibility to change when business requirements change. 5.Reconcile multiple logical source models into a single, logically consistent model. 6.Ensure the proposed model follows data architecture guidelines and best practices. 7.Rationalize the relationships expressed in the logical data model to the schema of the physical data store (that is, database tables and columns). 8.Develop data modeling best practices, guidelines and standards for Data Architecture COE. Regards, Parul Gupta, IT-Technical Recruiter P: 609-632-1299, E: pgu...@sourceinfotech.com 3840 Park Avenue, Suite C-205, Edison, NJ-08820 Hangout: <http://www.inceptdatasolutions.com/> guptaparul...@gmail.com *------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------* *Disclaimer:** If you are not interested in receiving our e-mails then please reply with a "REMOVE" in the subject line at * *rem...@sourceinfotech.com* <rem...@sourceinfotech.com> *for automatic removal. And mention all the e-mail addresses to be removed with any e-mail addresses, which might be diverting the e-mails to you. We are sorry for the inconvenience.* -- You received this message because you are subscribed to the Google Groups "oraapps" group. To unsubscribe from this group and stop receiving emails from it, send an email to oraapps+unsubscr...@googlegroups.com. To post to this group, send email to oraapps@googlegroups.com. Visit this group at https://groups.google.com/group/oraapps. For more options, visit https://groups.google.com/d/optout.
