I have a very urgent DIRECT CLIENT requirement for *File Maker Developer *in
Lansing, MI. Please Let Me Know If you have available candidate, please
reply with their word resume, location, rate and contact number.

Please send the resumes at r...@cncconsulting.com

Job Title: File Maker Developer
Location: Lansing, MI
Duration: 6 Months

Once a final set of files to upgrade is determined they will be evaluated
and the following documentation will be provided:
the recommended path of upgrade
a list of files that will be upgraded
an estimate of the amount of hours it would take to upgrade the files
an estimated timeline of key project milestones and project completion
based on a hypothetical start date
a list of concerns and problems anticipated with the upgrade and a
recommended path of resolution for each C. FileMaker Pro Upgrade to version
12/13 Upgrade of Filemaker applications and databases to Filemaker Pro
12/13. This includes placing into a server environment from the current
client desktop environment. Technical support from DTMB will be provided to
assist the Technical Consultant with:
providing access to the necessary FileMaker files and copies of the
FileMaker files as requested
providing an onsite work environment for items listed in the SOW
providing remote access, if necessary, for items listed in the SOW
providing hardware and software necessary to run a sample conversion and
evaluation of the files if the contractor's laptop and/or workstations
cannot be used
providing purchase of new server and assistance with implementing new
server environment. TASKS: Leslie's Requests
Add new button layouts for Cisco phones (6 new details) in Orderlog.
Make sure the "highlight" buttons are working correctly on all button
layouts.
Expand the "Billing ID" field in the System 85 application so Secure ID
information is fully displayed when printed. Michelle's Requests:
Fix Verizon Bill so that it will take more than one line of coding for each
wireless number in Sprintcd database. Fix the data joins so that they are
remembered the next time the application is used.
Add "Wireless" to coordinator database data entry screen.
Reorganize billing detail reports on Verizon Bill, Sprint, and AT&T
Wireless Bill so that they are more condensed, take up fewer pages, and are
easier to split up for the bureaus.
Create Data Usage reports in Verizon Bill, Sprint, and AT&T Wireless Bill
so that coordinators can see if wireless modems are being used.
Update names of files and file locations for Sprintcd, Nextel~Sys85, AT&T
Wireless Bill, Verizon Bill to reflect current names and usage.
Eliminate files that are no longer needed and streamline what is currently
used for easy transition to FileMaker 12. Ethan's Requests
Make layout changes to LEASE and expand reporting capabilities Other
Requests
May need to accommodate a limited number of additional requests, if
possible, within the number of agreed upon hours Completion of
documentation per Scope of Work above. Upgrade to FileMaker
version 12/13 Conversion

1. Freeze production
2. Run files through our conversion tool
3. Troubleshoot pre-conversion issues
4. Convert the files 5. Test for corruption
6. Review conversion log
7. Make further changes (as necessary) in pre-conversion files
8. Convert the files again (if step 6 is completed)
9. Review conversion log (if steps 6 and 7 are completed)
10. Serve files in a test environment
11. Make post conversion changes (including, but not limited to: changing
of account names, organizing relationship graphs, making file references
relative when possible, fixing window control and navigation issues,
adjusting printout margins as necessary, verify and adjust functionality as
needed by doing side by side testing)
12. Begin navigation testing using testing documentation (if available) as
a guideline
13. Fix issues found during navigation testing
14. Begin second round of testing
15. Make second round of fixes
16. Confirm all issues have been addressed
17. Create clones of the finished files Deployment

1. Create a checklist of file information
2. Review server settings
3. Run a copy of the FileMaker 5/6 production files through our conversion
tool
4. Convert production files
5. Review conversion log
6. Test for corruption
7. Make any last minute adjustments as noted during production freeze and
testing on the clones
8. Rename converted production files with a "_DATA" suffix or put them in a
separate "DATA" folder
9. Import data from newly converted files into the clones (using multiple
workstations if possible)
10. Complete all tasks in the conversion widget (if needed) using imported
conversion tool data
11. Test for corruption
12. Serve the newly converted solution
13. Test newly converted solution
14. Make any adjustments as necessary in backup (from #12 above) and test
files
15. Place a clean copy of the final solution in place.
16. Go live DELIVERABLES: Deliverables will not be considered complete
until the Agency & DTMB Project Managers have formally accepted them.
Deliverables for this project include:

Completion of tasks for section A, B and C of the SOW above Documentation
for Upgrade to Filemaker Level 12/13 Implementation of the Upgrade to level
12/13 ACCEPTANCE CRITERIA:
* The work performed within section A is accepted as complete by LARA
Project manager and DTMB Project Manager. * The writeup for section B is
clearly written, understood, and accepted as complete by LARA and DTMB.
* The upgrade to Filemaker 12/13 is complete and implemented in production
as approved by Agency & DTMB managers.

Skills Required  Bachelors degree or 7-10 years IT experience with
Filemaker leadership or management experience

Skills Preferred
Experience Required  experience in Filemaker upgrades experience in
Filemaker development
Thanks,

Raj Chouhan - IT Recruiter
201-546-3479Phone
r...@cncconsulting.com

-- 
You received this message because you are subscribed to the Google Groups "SAP 
BASIS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sap-basis+unsubscr...@googlegroups.com.
To post to this group, send email to sap-basis@googlegroups.com.
Visit this group at http://groups.google.com/group/sap-basis.
For more options, visit https://groups.google.com/d/optout.

Reply via email to