Documents Technologies Associate - Mobile, AL
Xerox · Mobile, AL · 3 wk ago
On-siteInformation TechnologyFull-time
We need to produce HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About the role:" then a long description of duties. It also includes some details about Windows Print Administration knowledge, inventory, etc. There's no explicit "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". However there are some details like "after business hours rate will be assessed and quoted as an additional cost." That's not pay specifics. No explicit pay or schedule. There's mention of "initial response within 2 hours" etc. That could be considered schedule? Not really. There's no explicit benefits. So we likely only have "About the role" and maybe "Responsibilities" (the duties). Could also have "Qualifications" from Windows Print Administration knowledge etc. But those are more like requirements. The posting includes "Technologist will have available..." etc. It includes knowledge requirements: Windows Print Administration knowledge includes: set up printers, troubleshoot, desktop troubleshooting, maintain inventory, etc. That could be considered Requirements or Qualifications. We need to decide.
We must not create sections with filler like "not specified". So only include sections where there is real specific content.
We have:
- About the role: we have a paragraph starting "About the role: The Document Technologist Services shall:" then a list of duties.
We could treat that as About the role section.
Then we could have Responsibilities: maybe the bullet list of duties.
But we must not duplicate content. The instructions: Use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About the role:" then a long description of duties. It also includes some details about Windows Print Administration knowledge, inventory, etc. There's no explicit "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". However there are some details like "after business hours rate will be assessed and quoted as an additional cost." That's not pay specifics. No explicit pay or schedule. There's mention of "initial response within 2 hours" etc. That could be considered schedule? Not really. There's no explicit benefits. So we likely only have "About the role" and maybe "Responsibilities" (the duties). Could also have "Qualifications" from Windows Print Administration knowledge etc. But those are more like requirements. The posting includes "Technologist will have available..." etc. It includes knowledge requirements: Windows Print Administration knowledge includes: set up printers, troubleshoot, desktop troubleshooting, maintain inventory, etc. That could be considered Requirements or Qualifications. We need to decide.
We must not create sections with filler like "not specified". So only include sections where there is real specific content.
We have:
- About the role: we have a paragraph starting "About the role: The Document Technologist Services shall:" then a list of duties.
We could treat that as About the role section.
Then we could have Responsibilities: maybe the bullet list of duties.
But we must not duplicate content. The instructions: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it.
We need to preserve ALL substantive information; do NOT invent or summarize away detail.
We need to remove boilerplate etc.
Thus we need to extract substantive content: The role description includes many duties. We can put them under Responsibilities as a list. The "About the role" could be a short prose summarizing the role? But we already have the duties. The "About the role:" heading is present in the source; we could keep that as a section with prose that introduces the role, then responsibilities as list.
But we must not repeat the job title as a heading; that's fine.
We need to decide which sections to include.
Potential sections:
- About the role: we have a paragraph: "The Document Technologist Services shall: ..." Actually that's the start of duties. Could treat that as About the role prose.
- Responsibilities: list of duties (the many bullet points). Could be a
.
- Requirements / Qualifications: Windows Print Administration knowledge details, inventory maintenance, etc. Could be under Requirements.
- Skills: maybe the same as requirements? Might be redundant.
We need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But the instruction says use headings for those specific names if content exists. We could have Requirements and Qualifications separate if we have distinct content.
Let's parse the content for requirements/qualifications:
From text:
"Technologist will have available, for approved client Personnel, a mutually agreed upon process to request after hour technical support for business continuity and client Major Incident Support Model, after business hours rate will be assessed and quoted as an additional cost."
That's not a requirement.
"Xerox On-Site Document Technologist supporting the Customer’s Output Environment must have Windows Print Administration knowledge"
Then list:
"How to set up printers on Windows servers
How to troubleshoot basic print issues on the print server
Desktop troubleshooting knowledge on how to install and update drivers on the client workstation and servers
Maintain an inventory of Equipment within the Output Environment
Maintain inventory list on customer portal to be updated within 5 business days of change
List should include Equipment model, location, IP address, and print server where the Equipment is defined
Monitor disengagement of Equipment or end of life for Equipment in the Output Environment and recommend alternatives
Make recommendations on Equipment best practices, settings, print drivers, etc.
Provide recommendations and input into best practices related to all aspects related to Equipment print drivers, Equipment settings, etc. as well as best practices related to print administration
Create Equipment configuration documentation based on Customer provided requirements, as mutually agreed to by the Parties
Document Technologist Services shall conduct Equipment testing in a Customer designated site.
The Document Technologist may support On-Site Maintenance Services resources, as applicable and as time permits in the sites that they are physically responsible for
Note: Customer shall provide laptop and access to client network and enable remote access to the Output Environment (Customer network) for the Xerox Document Technologist Services.
Manage XWS for network
Business Critical devices, (shop floor and warehouse) initial response within 2 hours in Mobile and Grand Prairie (Client must supply list of the serial numbers that are designated as critical devices).
Supply replacement should be replacing one off the shelf, available for client employee replacement
Managing New Devices- systems updates within 5 business days
Communication with Carrier
Update in client system in CMDB report
Adding new device to XSM/XDM
Removing traded device from inscope on XSM/XDM
Removing and adding appropriate device in Xerox billing system
Adding and removing appropriate device in XWS
End User Training Provided to appropriate end users within 60 days of implementation of Xerox implemented services or equipment (non Xerox equipment or services acquired on contract will be provided training from an alternative source depending on the equipment or services being implemented)
End user training on RFID and XWS use
Any new features added to solution after initial implementation of device
Provide training on installation of supplies
Provide new user training if requested
Client to provide communication and coordination of training campaign
Reporting during QBR presentation the following to be included: Initial response time from request
Response time for critical devices
First time fix rate
Resolution time
Downtime documentation of technologist including trends quarter over quarter
Preventative calls derived from Predictive AI compared to total service calls showing trend quarter over quarter
Percentage of call delayed due to parts not being available
Service Escalation Rate based on service calls that needed to be escalated past the field technician
Repeat Service Rates- showing the percentage of devices requiring a repeat service call for the same issue with in the quarter including trends quarter over quarter.
Contingency plan for PTO and Emergency absence Onsite Resources in Grand Prairie and Mobile will back each other up for remote services.
When an onsite resource is out, Xerox will have a backup resource to manage the break/fix and supply responsibilities."
That's a huge list of duties and responsibilities. Many of these are responsibilities, not requirements.
Thus we could have:
- About the role: short prose (maybe the first sentence: "The Document Technologist Services shall: ..."? Actually that's part of duties.)
Better: About the role: a brief description: "The Document Technologist Services role involves assisting customer print teams, developing standards, reviewing configurations, troubleshooting, installing drivers, testing equipment, managing inventory, providing training, reporting metrics, etc." But we must not summarize away detail; we need to preserve ALL substantive information. If we create a prose summary, we would be summarizing, which is not allowed. So we must keep the details as they are, likely in a list under Responsibilities.
Thus we could have only one section: Responsibilities, with a containing all the duties as - items. That would preserve all detail. The "About the role:" heading could be omitted because we are not repeating job title, but we could keep it as a heading with a short prose that is not summarizing? The source says "About the role: The Document Technologist Services shall:" then the list. If we treat "About the role:" as a heading and then put the list as responsibilities, we would be splitting the content: the heading's prose is just the colon and then the list. But we could put the heading and then the list directly under it (no extra prose). That would be okay:
About the role
...
. That would preserve all content (the list). The heading "About the role:" is present in source; we can use it.
Thus we output:
About the role
- Assist Customer print team to develop and document standards for network printers and multi-function printer configurations, network connectivity, and Equipment MFP services integration and implementation
- Review and approve Equipment configurations and update any applicable documentation for network Equipment printers and MFPs considered for installation by Customer
- Assist Customer application owners to troubleshoot application or mainframe printing problems utilizing network printing Equipment (printers and MFPs)
- Install, test, troubleshoot and approve the Equipment print drivers for the related network printing Equipment) in the required printing environments per Customer request.
- Test all Equipment (Xerox printers and MFPs) models, print drivers, and firmware software in the Customer lab environment or designated Site (Note: Xerox Production Equipment is tested in the field)
- Perform tasks as outlined in schedule B, XPSAS
- Engage 3rd level technical support for network-attached Equipment Xerox printers and MFPs) connected to the Customer network.
- Technologist will have available, for approved client Personnel, a mutually agreed upon process to request after hour technical support for business continuity and client Major Incident Support Model, after business hours rate will be assessed and quoted as an additional cost.
- Xerox On-Site Document Technologist supporting the Customer’s Output Environment must have Windows Print Administration knowledge
- How to set up printers on Windows servers
- How to troubleshoot basic print issues on the print server
- Desktop troubleshooting knowledge on how to install and update drivers on the client workstation and servers
- Maintain an inventory of Equipment within the Output Environment
- Maintain inventory list on customer portal to be updated within 5 business days of change
- List should include Equipment model, location, IP address, and print server where the Equipment is defined
- Monitor disengagement of Equipment or end of life for Equipment in the Output Environment and recommend alternatives
- Make recommendations on Equipment best practices, settings, print drivers, etc.
- Provide recommendations and input into best practices related to all aspects related to Equipment print drivers, Equipment settings, etc. as well as best practices related to print administration
- Create Equipment configuration documentation based on Customer provided requirements, as mutually agreed to by the Parties
- Document Technologist Services shall conduct Equipment testing in a Customer designated site.
- The Document Technologist may support On-Site Maintenance Services resources, as applicable and as time permits in the sites that they are physically responsible for
- Note: Customer shall provide laptop and access to client network and enable remote access to the Output Environment (Customer network) for the Xerox Document Technologist Services.
- Manage XWS for network
- Business Critical devices, (shop floor and warehouse) initial response within 2 hours in Mobile and Grand Prairie (Client must supply list of the serial numbers that are designated as critical devices).
- Supply replacement should be replacing one off the shelf, available for client employee replacement
- Managing New Devices- systems updates within 5 business days
- Communication with Carrier
- Update in client system in CMDB report
- Adding new device to XSM/XDM
- Removing traded device from inscope on XSM/XDM
- Removing and adding appropriate device in Xerox billing system
- Adding and removing appropriate device in XWS
- End User Training
- for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. We need to preserve ALL substantive information; do NOT invent or summarize away detail. We need to remove boilerplate etc. Thus we need to extract substantive content: The role description includes many duties. We can put them under Responsibilities as a list. The "About the role" could be a short prose summarizing the role? But we already have the duties. The "About the role:" heading is present in the source; we could keep that as a section with prose that introduces the role, then responsibilities as list. But we must not repeat the job title as a heading; that's fine. We need to decide which sections to include. Potential sections: - About the role: we have a paragraph: "The Document Technologist Services shall: ..." Actually that's the start of duties. Could treat that as About the role prose. - Responsibilities: list of duties (the many bullet points). Could be a
- .
- Requirements / Qualifications: Windows Print Administration knowledge details, inventory maintenance, etc. Could be under Requirements.
- Skills: maybe the same as requirements? Might be redundant.
We need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But the instruction says use headings for those specific names if content exists. We could have Requirements and Qualifications separate if we have distinct content.
Let's parse the content for requirements/qualifications:
From text:
"Technologist will have available, for approved client Personnel, a mutually agreed upon process to request after hour technical support for business continuity and client Major Incident Support Model, after business hours rate will be assessed and quoted as an additional cost."
That's not a requirement.
"Xerox On-Site Document Technologist supporting the Customer’s Output Environment must have Windows Print Administration knowledge"
Then list:
"How to set up printers on Windows servers
How to troubleshoot basic print issues on the print server
Desktop troubleshooting knowledge on how to install and update drivers on the client workstation and servers
Maintain an inventory of Equipment within the Output Environment
Maintain inventory list on customer portal to be updated within 5 business days of change
List should include Equipment model, location, IP address, and print server where the Equipment is defined
Monitor disengagement of Equipment or end of life for Equipment in the Output Environment and recommend alternatives
Make recommendations on Equipment best practices, settings, print drivers, etc.
Provide recommendations and input into best practices related to all aspects related to Equipment print drivers, Equipment settings, etc. as well as best practices related to print administration
Create Equipment configuration documentation based on Customer provided requirements, as mutually agreed to by the Parties
Document Technologist Services shall conduct Equipment testing in a Customer designated site.
The Document Technologist may support On-Site Maintenance Services resources, as applicable and as time permits in the sites that they are physically responsible for
Note: Customer shall provide laptop and access to client network and enable remote access to the Output Environment (Customer network) for the Xerox Document Technologist Services.
Manage XWS for network
Business Critical devices, (shop floor and warehouse) initial response within 2 hours in Mobile and Grand Prairie (Client must supply list of the serial numbers that are designated as critical devices).
Supply replacement should be replacing one off the shelf, available for client employee replacement
Managing New Devices- systems updates within 5 business days
Communication with Carrier
Update in client system in CMDB report
Adding new device to XSM/XDM
Removing traded device from inscope on XSM/XDM
Removing and adding appropriate device in Xerox billing system
Adding and removing appropriate device in XWS
End User Training Provided to appropriate end users within 60 days of implementation of Xerox implemented services or equipment (non Xerox equipment or services acquired on contract will be provided training from an alternative source depending on the equipment or services being implemented)
End user training on RFID and XWS use
Any new features added to solution after initial implementation of device
Provide training on installation of supplies
Provide new user training if requested
Client to provide communication and coordination of training campaign
Reporting during QBR presentation the following to be included: Initial response time from request
Response time for critical devices
First time fix rate
Resolution time
Downtime documentation of technologist including trends quarter over quarter
Preventative calls derived from Predictive AI compared to total service calls showing trend quarter over quarter
Percentage of call delayed due to parts not being available
Service Escalation Rate based on service calls that needed to be escalated past the field technician
Repeat Service Rates- showing the percentage of devices requiring a repeat service call for the same issue with in the quarter including trends quarter over quarter.
Contingency plan for PTO and Emergency absence Onsite Resources in Grand Prairie and Mobile will back each other up for remote services.
When an onsite resource is out, Xerox will have a backup resource to manage the break/fix and supply responsibilities."
That's a huge list of duties and responsibilities. Many of these are responsibilities, not requirements.
Thus we could have:
- About the role: short prose (maybe the first sentence: "The Document Technologist Services shall: ..."? Actually that's part of duties.)
Better: About the role: a brief description: "The Document Technologist Services role involves assisting customer print teams, developing standards, reviewing configurations, troubleshooting, installing drivers, testing equipment, managing inventory, providing training, reporting metrics, etc." But we must not summarize away detail; we need to preserve ALL substantive information. If we create a prose summary, we would be summarizing, which is not allowed. So we must keep the details as they are, likely in a list under Responsibilities.
Thus we could have only one section: Responsibilities, with a
- items. That would preserve all detail. The "About the role:" heading could be omitted because we are not repeating job title, but we could keep it as a heading with a short prose that is not summarizing? The source says "About the role: The Document Technologist Services shall:" then the list. If we treat "About the role:" as a heading and then put the list as responsibilities, we would be splitting the content: the heading's prose is just the colon and then the list. But we could put the heading and then the list directly under it (no extra prose). That would be okay:
About the role
- ...
About the role
- Assist Customer print team to develop and document standards for network printers and multi-function printer configurations, network connectivity, and Equipment MFP services integration and implementation
- Review and approve Equipment configurations and update any applicable documentation for network Equipment printers and MFPs considered for installation by Customer
- Assist Customer application owners to troubleshoot application or mainframe printing problems utilizing network printing Equipment (printers and MFPs)
- Install, test, troubleshoot and approve the Equipment print drivers for the related network printing Equipment) in the required printing environments per Customer request.
- Test all Equipment (Xerox printers and MFPs) models, print drivers, and firmware software in the Customer lab environment or designated Site (Note: Xerox Production Equipment is tested in the field)
- Perform tasks as outlined in schedule B, XPSAS
- Engage 3rd level technical support for network-attached Equipment Xerox printers and MFPs) connected to the Customer network.
- Technologist will have available, for approved client Personnel, a mutually agreed upon process to request after hour technical support for business continuity and client Major Incident Support Model, after business hours rate will be assessed and quoted as an additional cost.
- Xerox On-Site Document Technologist supporting the Customer’s Output Environment must have Windows Print Administration knowledge
- How to set up printers on Windows servers
- How to troubleshoot basic print issues on the print server
- Desktop troubleshooting knowledge on how to install and update drivers on the client workstation and servers
- Maintain an inventory of Equipment within the Output Environment
- Maintain inventory list on customer portal to be updated within 5 business days of change
- List should include Equipment model, location, IP address, and print server where the Equipment is defined
- Monitor disengagement of Equipment or end of life for Equipment in the Output Environment and recommend alternatives
- Make recommendations on Equipment best practices, settings, print drivers, etc.
- Provide recommendations and input into best practices related to all aspects related to Equipment print drivers, Equipment settings, etc. as well as best practices related to print administration
- Create Equipment configuration documentation based on Customer provided requirements, as mutually agreed to by the Parties
- Document Technologist Services shall conduct Equipment testing in a Customer designated site.
- The Document Technologist may support On-Site Maintenance Services resources, as applicable and as time permits in the sites that they are physically responsible for
- Note: Customer shall provide laptop and access to client network and enable remote access to the Output Environment (Customer network) for the Xerox Document Technologist Services.
- Manage XWS for network
- Business Critical devices, (shop floor and warehouse) initial response within 2 hours in Mobile and Grand Prairie (Client must supply list of the serial numbers that are designated as critical devices).
- Supply replacement should be replacing one off the shelf, available for client employee replacement
- Managing New Devices- systems updates within 5 business days
- Communication with Carrier
- Update in client system in CMDB report
- Adding new device to XSM/XDM
- Removing traded device from inscope on XSM/XDM
- Removing and adding appropriate device in Xerox billing system
- Adding and removing appropriate device in XWS
- End User Training
- containing all the duties as
- items. That would preserve all detail. The "About the role:" heading could be omitted because we are not repeating job title, but we could keep it as a heading with a short prose that is not summarizing? The source says "About the role: The Document Technologist Services shall:" then the list. If we treat "About the role:" as a heading and then put the list as responsibilities, we would be splitting the content: the heading's prose is just the colon and then the list. But we could put the heading and then the list directly under it (no extra prose). That would be okay: